Status

 

Possible values:

* "PROPOSED" in Grey specifies that discussion is underway. 

* "READY FOR VOTE" in Blue specifies that the proposal has been finalized and is ready for the TSC to vote.

* "RESOLVED" in Green specifies that the decision was made by the TSC.

BlockingLinks to pages for projects or initiatives that are blocked by this decision
OutcomeAddressed with the publication of the guide on how to raise an issue with the TSC
Minutes LinkProvides a link to the minutes where the decision was made by the TSC. The minutes will have the vote result (e.g., unanimously approved)


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

Include any tasks here that need to be completed once the decision has been approved by the TSC

Reviewed By