Open lemmy opened 3 years ago
The repository name should change from RFCs
to something that better communicates that this is also about bigger enhancements still in the requirements phase? It also has to be made clear that proposers cannot expect others to do the work; proposing an enhancement ideally creates synergies, but the proposer is the driver.
Shall we add "foster wide industry adoption" to the goals?
I'm not about process, but anyway. It may be worth to create an issue template with recommended fields and parts of RFC. GH allows to create it, see https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
@ligurio Great idea, do you know of a popular/matching template we could re-use?
I would start with at least following sections:
I hope it would enough for start.
P.S. see also RFC templates in reactjs project, tensorflow and rust-lang.
Update: GH discussions can be used for discussing RFCs, we found it very convenient in our project.
The Technical Charter provides scaffolding: https://foundation.tlapl.us/docs/TLA%2B%20Project%20Technical%20Charter.pdf
What should the TLA+ enhancement process look like?
Goals
TODO