Overview of Proposal
The typical situation is that a project is launched on the premise that it will support several DLT platforms but end up only supporting one. In this case a rollover was considered but got little support and was seen as too narrowly focused. The question is more broadly about how a project that has deviated from its original intended goal should be dealt with. It would seem sensible to at least recognize the deviation somehow - possibly with a charter revision.
Initial discussion on this topic can be found on the Summary & RFC page.
Formal Proposal(s)
Add a page providing information on how to raise an issue with the TSC so that this kind of issue can be addressed.
See https://github.com/hyperledger/tsc/pull/15
Action Items
- Type your task here, using "@" to assign to a user and "//" to select a due date
Reviewed By
- Angelo De Caro
- Arnaud J Le Hors
- Arun S M
- Baohua Yang
- Bobbi Muscara
- Danno Ferrin
- David Enyeart
- Gari Singh
- Grace Hartley
- Hart Montgomery
- Maria Teresa Nieto
- Mark Wagner
- Nathan George
- Tracy Kuhrt
- Troy Ronda
3 Comments
Arun S M
Answering to the comment on Re: Summary & RFC
Gari Singh
If a project changes its mission or charter, that information should be reflected/updated wherever the project is described in detail.
Arun S M
Observations/comments/feedbacks heard so far: