Task Force Proposal: Badging/Lifecycle

[tkuhrt]

Introduction/background material

Today's Hyperledger Project Lifecycle, represents a lifecycle in which projects only move forward through the different stages. In past TOCs, we have talked about whether this should change and whether we should instead represent the state of a project with some form of badging to allow people to be able to quickly determine the health and status of a project. In addition, the Governing Board has requested that we take another look at how best to represent the current status of project's within Hyperledger. There are a couple of different options that this task force might consider:

1. Modify the current project lifecycle to have an annual review process to verify that a project's current status meets the criteria for its current state. This change may require renaming the "Graduated" state to reflect that this stage is not an achieved and done stage. This change may also require updating the lifecycle to ensure that each of the states and the criteria for each state is documented to ensure the annual review process can objectively determine the correct state based on the project status.
2. Look to implement objective badges for Hyperledger projects that can replace the current lifecycle that can be updated in during the quarterly reporting step so that people will understand the current project status.

Background Material:

• Hyperledger Project Lifecycle
• Previous Badging Proposal and Discussion
• Previously Proposed Badges
• LF Networking Project Lifecycle (contains an incubation reversal review)

Task to be completed

Determine how to update the project lifecycle and whether that will involve the introduction of badging.

List of deliverables or work products

• [ ] Updated project lifecycle
• [ ] Badges and badging process (optional)

Time to complete (no more than 6 months)

TBD

Leader

Rama

Initial participant list

Venkatraman Ramakrishna (Rama) Bobbi Muscara