Expanded Readme and TEP-0001, and TEP Index Documentations. Used the PEP documentation as a guideline.
@WarmBeer @josecelano @da2ce7
Please review.
We had initially spoken of keeping it simple. However we needed to document the whole process and content that we should expect in such a document. The PEP is rather extensive but it covers many areas that we will have to deal with in the future. I simplified it a little though it was rather complex and relatively extensive.
Ensure that everyone listed as a sponsor or co-author of the TEP who has write access to the TEP repository is added to .github/CODEOWNERS_.- .. _Torrust issue tracker: https://github.com/Torrust/cTorrust/issues
We maybe should look into creating a page that displays all the issues from all the repositories - such as indicated in the original PEP like for example: Centralized pooled issues .. _Torrust issue tracker: https://github.com/torrust/issuetracker/issues
Expanded Readme and TEP-0001, and TEP Index Documentations. Used the PEP documentation as a guideline.
@WarmBeer @josecelano @da2ce7 Please review.
We had initially spoken of keeping it simple. However we needed to document the whole process and content that we should expect in such a document. The PEP is rather extensive but it covers many areas that we will have to deal with in the future. I simplified it a little though it was rather complex and relatively extensive.
We will also have to implement:
TEP repositoryis added to.github/CODEOWNERS_.- .. _Torrust issue tracker: https://github.com/Torrust/cTorrust/issues