Originally, some torrent fields were included in the BitTorrent client's implementations but not defined in any specification (BEP). It's what we call "Original unofficial specification"

Some of them were described here.

It would be nice to describe them in a proper way and later include links to the BEP in the documentation wherever those fields are used.

cc @da2ce7

• State the TEP purpose
• Incorporate the links to the contributing file
• Incorporate a link to the template
• Create the First TEP-0001 about the TEPS purpose, requirements and process
• List the most recent TEPS creating an index file where it displays the TEP number, Title and Status and last update date

Use of asymmetric cryptography for user accounts and their authentication.

Draft:
https://github.com/da2ce7/torrust-teps/blob/tep-asymmetric_key_client_authentication/TEP-0012.md

Python has a nice overview of their PEP's on peps.python.org. I think this would be nice to have as well for Torrust.

We need a template for the TEPs.

Examples:

• https://github.com/scikit-learn/enhancement_proposals/blob/master/slep_template.rst
• https://github.com/jupyter/enhancement-proposals/blob/master/jupyter-enhancement-proposal-guidelines/JEP-TEMPLATE.md

We need a CONTRIBUTING file with guidelines on how to submit TEPS (Torrust Enhancement Proposals) to the project.

Example: https://github.com/python/peps/blob/main/CONTRIBUTING.rst