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 11:10:16 +01:00
parent f11bab6f41
commit d88bfbf0c1
Signed by untrusted user who does not match committer: yogsototh
GPG key ID: 7B19A4C650D59646
1 changed files with 10 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -90,7 +90,7 @@ Describe the objective of this RFC.
+ pros
+ cons
**** Considerations
**** Furter Considerations and Remarks
Generic place to put comment not suitable in any other subsection.
Typically, we could add
@ -98,11 +98,14 @@ Typically, we could add
+ Security
+ Communication
** Considerations
** Further Considerations and Remarks
*** =dev= label
Here are my proposed templates.
We already have a =dev= label we should probably use for RFC meaningful
only for developpers, and we should continu to use the =Epic= label for
issues whose goal is the provide a spcecification document that we could
give to Managers with an Execution Plan.
We already have a =dev= label we should probably use for RFC whose audience
is just the iroh team.
*** =Epic= label
We should continu to use the =Epic= label for issues whose goal is to
produce a specification document along with an execution plan.