Skip to content

Commit 893e93e

Browse files
joesepichristian-bromanntobie
authored
Add Growth plan template (#56)
Co-authored-by: Christian Bromann <[email protected]> Co-authored-by: Tobie Langel <[email protected]>
1 parent 4e3eadb commit 893e93e

File tree

3 files changed

+60
-2
lines changed

3 files changed

+60
-2
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Growth Plan Checklist
3+
about: For capturing action items related to growth plan for progression to Impact stage
4+
title: "[GROWTH PLAN] ${Project Name}"
5+
labels: 'Growth Plan'
6+
assignees: ''
7+
---
8+
9+
**Growth plan:** ${Link to growth plan}
10+
11+
- [ ] Fill in [growth plan template](https://github.com/openjs-foundation/project-status/blob/master/GROWTH_PLAN_TEMPLATE.md)
12+
- [ ] Submit growth plan to CPC for approval
13+
- [ ] Obtain growth plan approval from CPC
14+
- [ ] Complete growth plan
15+
- [ ] Submit completed growth plan to CPC for graduation approval
16+
- [ ] Impact stage graduation

GROWTH_PLAN_TEMPLATE.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# ${PROJECT} Growth Plan
2+
3+
_Note: the purpose of the growth plan is to provide a roadmap for a project to move from Growth stage to Impact stage._
4+
5+
## Growth stage requirements
6+
7+
_Note: in theory, Growth stage requirements should already be met by all Growth stage projects.
8+
As requirements might have changed after a project was accepted at the Growth stage, this isn't necessarily always the case.
9+
So making sure that all Growth requirements are met is a good first step in any Growth plan._
10+
11+
| Requirement | Current status | Desired status | Plan | Timeline | Completed |
12+
| --- | ---| --- | --- | --- | --- |
13+
| Project shows substantial adoption in production environments or usage within the ecosystem | {CURRENT_STATUS} | 2 | {PLAN} | {DATE} | <!----> |
14+
| Substancial ongoing flow of commits and merged contributions. | {CURRENT_STATUS} | {DESIRED_STATUS} | {PLAN} | {DATE} | <!----> |
15+
| Sufficient level of community participation to meet goals outlined in growth plan. | {CURRENT_STATUS} | {DESIRED_STATUS} | {PLAN} | {DATE} | <!----> |
16+
| Accepts security reports and publicly disclose them after the fix has been made available. | {CURRENT_STATUS} | {DESIRED_STATUS} | {PLAN} | {DATE} | <!----> |
17+
18+
## Impact stage requirements
19+
20+
| Requirement | Current status | Desired status | Plan | Timeline | Completed |
21+
| --- | ---| --- | --- | --- | --- |
22+
| Governing body of >= 5 members of which no more than 1/3 is affiliated with the same employer. | {CURRENT_STATUS} | {DESIRED_STATUS} | {PLAN} | {DATE} | <!----> |
23+
| Publicly documented governance, decision-making, contribution, and release processes. | {CURRENT_STATUS} | {DESIRED_STATUS} | {PLAN} | {DATE} | <!----> |
24+
| Healthy number of regular committers from at least two organizations. | {CURRENT_STATUS} | {DESIRED_STATUS} | {PLAN} | {DATE} | <!----> |
25+
| Adopted the Foundation Code of Conduct. | {CURRENT_STATUS} | {DESIRED_STATUS} | {PLAN} | {DATE} | <!----> |
26+
| Public list of project adopters. | {CURRENT_STATUS} | {DESIRED_STATUS} | {PLAN} | {DATE} | <!----> |
27+
| {OTHER_METRICS_DEFINED_WITH_CPC} | {CURRENT_STATUS} | {DESIRED_STATUS} | {PLAN} | {DATE} | <!----> |

README.md

+17-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,21 @@
1-
# project-onboarding
2-
Public repo to manage the process of onboarding projects
1+
# project-status
2+
3+
Public repo to manage the processes of project onboarding and growth plan approval and monitoring.
34

45
## Resources for onboarding projects
56

7+
* [Onboarding checklist](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md#onboarding-checklist)
8+
69
* [OpenJS Foundation Marketing Support Opportunities](https://docs.google.com/presentation/d/1xWsohwo-SwKjR-GuThi0BVwz3ni7KLp3vIBTuAbMQRY/edit#slide=id.g5ce6a1b7ed_5_14): A presentation from the marketing team about resources available to you to market your project
10+
11+
# Growth plan process
12+
13+
Project which want to move to [Impact stage](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md#impact-stage) need to provide and implement a Growth Plan. There is a [growth plan template](GROWTH_PLAN_TEMPLATE.md) available as a starting point.
14+
15+
## Process
16+
17+
* Project fills in the growth plan template. (The growth plan can be hosted on the project's own infrastructure or in the `growth-plan` directory of this repository.)
18+
* The project decides itself of the goals it sets in the growth plan according to the [Impact stage acceptance criteria](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md#impact-stage) and sets the roadmap for meeting them.
19+
* The growth plan is then submitted to the Cross Project Council (CPC) for approval by filing a _Growth Plan Checklist_ issue in this repository.
20+
* The CPC regularly checks on the progress of the growth plan according to its [review process](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md#iv-annual-review-process).
21+

0 commit comments

Comments
 (0)