├── .github └── ISSUE_TEMPLATE │ ├── all-other-issues.md │ ├── growth-plan-checklist-template.md │ ├── project-onboarding-checklist-template.md │ ├── project-post-graduation-checklist-template.md │ └── project-sunsetting-cheklist-template.md ├── GROWTH_PLAN_TEMPLATE.md ├── LICENSE └── README.md /.github/ISSUE_TEMPLATE/all-other-issues.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: All other issues 3 | about: If your issue doesn't fit the other templates, please open a custom issue 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | 15 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/growth-plan-checklist-template.md: -------------------------------------------------------------------------------- 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 - ${Project Name} 10 | 11 | ${Link to growth plan} 12 | 13 | - [ ] Fill in [growth plan template](https://github.com/openjs-foundation/project-status/blob/master/GROWTH_PLAN_TEMPLATE.md) 14 | - [ ] Submit growth plan to CPC for approval 15 | - [ ] Obtain growth plan approval from CPC 16 | - [ ] Complete growth plan 17 | - [ ] Submit completed growth plan to CPC for graduation approval 18 | - [ ] Impact stage graduation 19 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/project-onboarding-checklist-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Project Onboarding Checklist 3 | about: For capturing action items related to onboarding new / incubating projects 4 | title: "[ONBOARDING] ${Project Name}" 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Project Onboarding Checklist - ${Project Name} 11 | 12 | 13 | 14 | **Stage: ${Project Stage} 15 | 16 | - [ ] Adopt the [OpenJS Foundation Code of Conduct](https://code-of-conduct.openjsf.org/) 17 | - [ ] Update project CoC reporting methods to include OpenJS Foundation escalation path 18 | - [ ] List official domains that the project commits to transfer to the OpenJS Foundation following graduation 19 | - [ ] Identify and document other core project infrastructure 20 | - [ ] Adopt either the [Contributor License Agreement (CLA) or the Developer Certificate of Origin (DCO)](https://github.com/openjs-foundation/cross-project-council/blob/master/IP_POLICY_GUIDANCE.md#4-adopting-the-dco-or-a-cla) 21 | - [ ] Add or Update Governance.md document (required for Impact stage) 22 | - [ ] Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md) 23 | - [ ] Publish Project Charter on website or GitHub (see [charter template](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_CHARTER_TEMPLATE.md)) 24 | - [ ] Update [legal copyright notice](https://github.com/openjs-foundation/cross-project-council/blob/master/IP_POLICY_GUIDANCE.md#2-copyright-notices) on GitHub 25 | - [ ] Add [copyright notices for project website footers](https://github.com/openjs-foundation/artwork#copyright-notices-for-project-website-footers) to project website 26 | - [ ] Add [OpenJS Foundation logo](https://github.com/openjs-foundation/artwork#openjs-foundation-logos) to project website 27 | - [ ] [Add Project logo](https://github.com/openjs-foundation/artwork#preparing-artwork-for-contribution) to OpenJS Foundation website 28 | - [ ] Add Project to the [CPC repo's README.md](https://github.com/openjs-foundation/cross-project-council/blob/master/README.md#incubating-projects) as an Incubating project 29 | - [ ] List trademarks the project commits to transfer to the OpenJS Foundation following graduation 30 | - [ ] If project is using crowdfunding platforms, add disclaimer to platforms 31 | - [ ] Identify individuals from the project to join the CPC [by opening an issue in the CPC repository](https://github.com/openjs-foundation/cross-project-council/issues/new) 32 | - [ ] Document project and foundation contacts for: 33 | * marketing & social media 34 | * infrastructure 35 | * legal/governance help 36 | - [ ] Publish security policy (see [PROJECT_SECURITY_REPORTING](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_SECURITY_REPORTING.md)) 37 | - [ ] Work with the foundation to sign a [Project Contribution Agreement](https://docs.google.com/document/d/1Luq5JSUeDPGxj3vyttQvgItHPmj7v39QoKZqpJ9x_sU/edit?usp=sharing) (if needed) 38 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/project-post-graduation-checklist-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Project Post-graduation Checklist 3 | about: For capturing action items committed to during onboarding but which weren't 4 | actionable until the project had graduated. 5 | title: "[POST-GRADUATION] ${Project Name}" 6 | labels: post-graduation 7 | assignees: '' 8 | 9 | --- 10 | 11 | ## Project Post-graduation Checklist - ${Project Name} 12 | 13 | 14 | 15 | **Stage: ${Project Stage} 16 | 17 | - [ ] Transfer previously indicated official domains to OpenJS Foundation, if any 18 | - [ ] If relevant, implement the appropriate tool to enforce CLA or DCO 19 | - [ ] Transfer previously indicated trademarks to the OpenJS Foundation, if any 20 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/project-sunsetting-cheklist-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Project Sunsetting Checklist 3 | about: For capturing action items related to moving a project to Emeritus Stage 4 | title: "[SUNSETTING] ${Project Name}" 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Project Sunsetting Checklist - ${Project Name} 11 | 12 | 13 | 14 | - [ ] Decide in collaboration with the CPC whether the project needs to be archived or whether a call for maintenance is warranted 15 | - [ ] Confirm all official domains that the project owns have been transfered to the OpenJS Foundation 16 | - [ ] Cancel all cost-incurring infrastructure deployed by the project which is no longer necessary for Emeritus stage 17 | - [ ] Provide admin access to all infrastructute deployed by the project which isn't cancelled 18 | - [ ] Update project website, charter, and README to reflect Emeritus Stage 19 | - [ ] If the project is making a call for maintenance, provide clear way to contact the CPC 20 | - [ ] Archive the project 21 | - [ ] Move [project logo](https://github.com/openjs-foundation/artwork) to Emeritus Stage section 22 | - [ ] Move project logo on OpenJS Foundation website to Emeritus Stage section 23 | - [ ] Mark project in the [CPC repo's README.md](https://github.com/openjs-foundation/cross-project-council/blob/master/README.md#incubating-projects) as Emeritus 24 | - [ ] Update security policy (see [PROJECT_SECURITY_REPORTING](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_SECURITY_REPORTING.md)) 25 | -------------------------------------------------------------------------------- /GROWTH_PLAN_TEMPLATE.md: -------------------------------------------------------------------------------- 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} | | 28 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # project-status 2 | 3 | Public repo to manage the processes of project onboarding and growth plan approval and monitoring. 4 | 5 | ## Resources for onboarding projects 6 | 7 | * [Onboarding checklist](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/PROJECT_PROGRESSION.md#onboarding-checklist) 8 | 9 | * [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/HEAD/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/HEAD/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/HEAD/PROJECT_PROGRESSION.md#iv-annual-review-process). 21 | 22 | --------------------------------------------------------------------------------