Re: Hyperledger Labs versus Project incubation status

Hart Montgomery <hmontgomery@...>

Hi Dave,

Thanks a lot for the thoughtful email.  I totally agree with you:  we need to have a lot more clarification as to what sort of projects are likely to be approved for incubation.

Even if there are not "hard and fast" guidelines, an explanation of things that are likely to make people favor a proposal versus things that are likely to get a proposal rejected would be immensely useful.  For instance, even though it appears to have never been written down anywhere, it has always been an unstated rule that projects without maintainers from at least two distinct companies are not approved.  We've never approved a project without contributions from two different entities, but we've also never put this down on paper either.  So just explaining stuff like this would be very useful.

I would also suggest that we add text encouraging project proposers to ask individual TSC members for feedback before sending the proposal to the whole group.  For the projects that I helped to propose, this was immensely useful and I got great feedback that made the project proposal phase go much more smoothly than I otherwise would have expected.

Anyways, we can put off discussion of this until after the global forum, but I agree that it is something we should address.

Thanks a lot for your time, and have a great day.


From: tsc@... <tsc@...> on behalf of David Enyeart <enyeart@...>
Sent: Friday, June 4, 2021 1:53 PM
To: Hyperledger List <tsc@...>
Subject: [Hyperledger TSC] Hyperledger Labs versus Project incubation status

TSC members,

I know we are all busy with Global Forum for the next week, but after that I think it would be good to come back to the topic of project incubation status versus lab in a future TSC meeting.

The line between labs and project incubation is too blurred, both for new contributors and for TSC members that must evaluate project proposals. Everybody I have talked to internally and externally has struggled to understand the difference. Even people that have been around a long time struggle with the question when making or evaluating a new code contribution. And as we saw with the latest project proposal, the lack of criteria exasperated what can already be a torturous process for all involved.

As a new TSC member who didn't have the benefit of precedent with respect to project proposal evaluations, it was a difficult decision for me whether to speak my mind or not when the process was moving faster than I was comfortable with given a number of unknowns. I've been trying to think about what might have improved the experience for all. I liked Hart's suggestion in RocketChat about project incubation guidelines. For example, for projects that have not been open source previously, perhaps they should be required to start as a lab for a short time so that they can contribute their code in a welcoming environment and get familiar with open source licenses and processes prior to the public scrutiny of a project proposal evaluation. And with the latest proposal, it may have also helped to facilitate some discussions and collaboration prior to the project proposal submission and evaluation.

Dave Enyeart

Join to automatically receive all group messages.