project readiness not ready for discussion

Dave Huseby <dhuseby@...>


I've been working on trying to come up with a coherent checklist with descriptions for all of the areas of concern that make a project "ready" and how we measure that in each stage of the project lifecycle. I'm not quite ready to present it but I plan on sending it out to the TSC tomorrow or Friday for discussion ahead of next week's call.

My main focus is to identify the roles of the people involved in an open source project and also take the different stages we've already identified and then describe the primary concerns for a project to be "ready" at each stage and how the expectations for the people in each role at each stage. I'm weaving in the already "blessed" documents that the TSC has already approved for the exit criteria by using them as the minimum set of goals for a project to accomplish in each stage of their life cycle.

If you have any thoughts on things you'd like to see me include in this report, reply to this email and let me know. The draft I send out will be just the first iteration and I'm hoping that it will undergo several cycles of revisions until we get to something that outlines exactly what we should be looking for and measuring with analytics as well as the cultural goals of a project that contribute to project health and resiliency.

So no project readiness in tomorrow's TSC call but look for the initial draft of the report soon.

David Huseby
Security Maven, Hyperledger
The Linux Foundation

Join to automatically receive all group messages.