...
- (Tracy) The TSC has mentioned that they are not interested in bringing in additional distributed ledger projects. There should be a distinct advantage for a new distributed ledger project. This will be similar for other type of projects. In general, if a project is similar to an existing project, there should be a distinct advantage that the project brings over and beyond the existing project and that this cannot be contributed directly to the existing project.
- (Hart) I think it should be the case that a new project should bring something to the table that current projects don't. But I think this language might be a little too strong.
- (
Tracy) Based on the HIP template, dependent project's maintainers must sign off on the proposal before it is considered by the TSC.(Danno) What is a dependent project? What is the difference between a dependent project and one used as a library vs. an optional integration? What if multiple projects are integrated, can one block admission?
- (Arun) https://hyperledger.github.io/hyperledger-hip/ lists that a new project proposal must be floated in mailing list such as TSC's before submitting a HIP.
Charter
(Arun) The project at the time of proposal must meet Hyperledger's charter as defined and amended on time to time. (Leaving it out on purpose, this is expected and implicit).(Arun) TSC may decide to go through in depth and understand the project, ask for special sessions. There is no fixed timeline as to when TSC makes a decision. Project proposal can bring the topic back to TSC if there are no action items pending and all questions are answered with documents to demonstrate the completion.(Hart) This seems like rules for the TSC rather than guidelines for the project. Can we rephrase this so it tells the submitters what to expect rather than sets rules for the TSC?(Arun) Right, makes sense.
...