Re: Proposed Graduation Requirement for Projects Integrating with DLTs
toggle quoted messageShow quoted text
One thing I didn't add because my proposal was already too long is the fate of projects that are single-dlt and how to handle them. I think we already have a process where they are folded into their parent projects as sub projects. This includes new projects that would be propsed, the TSC decision could be to be added to a certain project as a sub-project (assuming the project will accept it). Examples (drawn from past project proposals https://wiki.hyperledger.org/display/TSC/Project+Proposals):
Justina, Fabric Go SDK, Fabric Python SDK, chaintool, Java Chaincode support for Hyperledger Fabric, Exerciser for the Hyperledger Fabric v0.2, Fabric Desktop,
Most of these are from the very early days of hyperledger and these were all folded into fabric. Explorer looks like it was initially proposed as just Fabric explorer, so I would expect sub projects can gain top level status by growing to multiple DLT/MPSs
The open question would be how to handle a single DLT project proposal for a non-hyperledger DLT. For example, something for Corda, Polkadot, Hedera, or Cosmos. It may not be worth spending cycles on however because I don't see the advantage of such a project looking for a home in Hyperledger as most of those have their own foundations and divergent communities.
On Mon, Jun 7, 2021 at 6:11 PM Danno Ferrin <danno.ferrin@...> wrote: