yogsototh/deft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org

Browse source
This commit is contained in:
Yann Esposito (Yogsototh) 2020-11-26 10:29:43 +01:00
parent 4f13c41c2d
commit f2b435fae4
Signed by untrusted user who does not match committer: yogsototh
GPG key ID: 7B19A4C650D59646
1 changed files with 6 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org
View file

@ -14,21 +14,12 @@ I hope not to trigger the need for a meta-meta-document ;).
* Problem
We are mixing dev focused RFC with broader
We miss correct RFC templates.
We do not have proper RFC template.
Developer focused RFCs and Feature specification RFC should probably have distinct templates.
* Proposed Solutions
For any newcomer it will be difficult to keep track of previous team
decisions.
Here are my proposed templates.
We already have a =dev= label we should probably use for dev-only
RFC regarding our coding conventions, toolings, libraries, frameworks, are
mixed with RFC focused on writing a specification to deliver features.
We are dependent on =github= issue tracker for essential knowledge for our team.
* Solution
We should have a document that keep track of our RFCs final decisions.
So if an RFC is about coding conventions, we should probably amend the
=CONTRIBUTING.org= file with a link to the RFC issue.
** Template Dev