proposal: move new projects to stage 2 (openjs-foundation#229)

Refs: openjs-foundation#165
Refs: openjs-foundation#232

proposals/README.md

@@ -12,11 +12,10 @@ Anyone may submit an idea for a policy or program following the [staging process
 
 * [Code of Conduct approach](./stage-1/CODE_OF_CONDUCT)
 * [Collab Summit](./stage-1/COLLAB_SUMMIT)
-* [Project Onboarding](./stage-1/PROJECT_ONBOARDING)
 
 ## Stage 2
 
-There are currently no Stage 2 proposals.
+* [Project Onboarding](./stage-2/PROJECT_ONBOARDING)
 
 ## Stage 3
 

proposals/stage-1/PROJECT_ONBOARDING/NEW_PROJECT_APPLICATION.md → proposals/stage-2/PROJECT_ONBOARDING/NEW_PROJECT_APPLICATION.md

@@ -1,55 +1,43 @@
-# Project Name
+# ${Project Name}
 
 ## Project Champion
 
 Who is the main point of contact during the application process?
 
-## CPC Champion (optional)
-
-If you have a champion from the Cross Project Council (CPC) please identify them. If you do not currently have one we will identify someone to support your project.
-
 ## Description
 
-A rough description of the project
+A rough description of the project in less than 100 words.
 
 ## Statement of alignment with OpenJS Foundation charter and mission
 
-Please refer to [TBD][]
-
-## Current Code of Conduct (CoC)
+Please refer to [the Cross Project Council's Charter](https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md).
+Please keep your answer to less than 250 words.
 
-Include a link
-
-## Current Project License
+## List of all repos that are part of the project
 
-Include a link
-
-## Current Source Control
-
-Link to Github or other source control
+Include links and license information
 
 ## Issues Tracker
 
 Link to GitHub or other tracker
 
-## External Dependencies
-
-Full list of dependencies in your source tree including licenses.
+## Current Code of Conduct
 
-## Release Methodology and mechanics
-
-How often do you release and where are the releases made. Do you have a Long-Term Support (LTS) program?
+Include a link
 
-## List of Committers
+## Vendored Dependencies (Optional)
 
-Full list of individuals with a commit bit to your project and their corporate affiliation if applicable.
+Full list of dependencies in the source tree of all repos. Please include licenses if you can.
+A full audit of all vendored dependencies will be required before your project can officially
+join the foundation, but this can be done later with foundation support.
 
 ## Governance Structure
 
 * Is there a leadership team?
 * Who are the members of the leadership team?
-* How are members of the leadership team nominated
-* How are commiters nominated?
+* How are members of the leadership team nominated?
+* How are individuals outside of leadership given commit access?
+* Please share links to all existing documentation e.g. GOVERNANCE.md / CONTRIBUTING.md
 
 ## Desired Initial Project Phase
 
@@ -73,18 +61,17 @@ Does your project currently receive funds? Who do they come from and what are th
 
 ## Infrastructure Needs or Requests
 
-What needs will your project have from the foundation?
+What needs will your project have from the foundation? Feel free to provide a list.
 
 ## Onboarding Checklist
 
-This is an informational checklist to help projects onboard into the OpenJS Foundation - tasks we will complete together after your project has been accepted into the foundation. If you have any questions or need help, the OpenJS Foundation CPC is available to assist.
+This is an informational checklist to help projects onboard into the OpenJS Foundation - tasks we will complete together after your project has been accepted into the incubation process. If you have any questions or need help, the OpenJS Foundation CPC is available to assist.
 
 - [ ] Adopt the OpenJS Foundation Code of Conduct
 - [ ] Update project CoC reporting methods to include OpenJS Foundation escalation path
 - [ ] Transfer official domains to OpenJS Foundation
 - [ ] Identify and document other core project infrastructure
-- [ ] If choosing to use a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO),
-      make selection and implement appropriate tool
+- [ ] If choosing to use a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO), make selection and implement appropriate tool
 - [ ] Add or Update Governance.md document (required for Impact stage)
 - [ ] Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)
 - [ ] Project Charter is published on website or github
@@ -99,6 +86,6 @@ This is an informational checklist to help projects onboard into the OpenJS Foun
   * infrastructure
   * legal/governance help
 
-## Unresolved Question
+## Questions?
 
 What questions do you have? What questions might arise during your application?

proposals/stage-1/PROJECT_ONBOARDING/README.md → proposals/stage-2/PROJECT_ONBOARDING/README.md

@@ -1,5 +1,5 @@
 # Project Onboarding Checklist Proposal
-> Stage 1
+> Stage 2
 
 ## Champion
 
@@ -33,21 +33,25 @@ Initially we should measure this document's success by how well it helps us onbo
 
 We need to share a workflow and understanding of what steps are required to bring in projects to the OpenJS Foundation. This process is an attempt to organize our ideas and our work to make that happen effectively. This process should be explicit and consistent to make applications fair for all projects.
 
-## Unresolved Question
+## Unresolved Questions
+
+* Should all existing projects be expected to go through check list?
+* Suggestion: group all the per-repo info we're looking for in one place (such as issue trackers, lists of committers, links to documentation such as Governance.md ) 
+* Clarification: to vendor dependencies include transitive dependencies as well? Also dev, prod dependencies or both?
+* Suggestion: include a tool such as https://www.npmjs.com/package/license-checker for grabbing dependency info
+* Suggestion: clarify the purpose of the request for list of committers (for staging purposes) and what measurements are to be used.
+* Clarification: what kind of information do we want to gather on a 'whole project' vs. 'per repo' basis bearing in mind there may be some variability across some project repositories.
 
-* Should there be a quiet period?
-* Should all emeritus projects be expected to go through this process?
-* Should projects be able to enter as `Impact Level`?
 
 ## What is necessary to complete this proposal
 
 Agreement on the initial checklist items; interim owners/helpers for each of the tasks.
 
 - [x] [Template for Project Applications](./NEW_PROJECT_APPLICATION.md)
 - [x] [Onboarding Check List](./NEW_PROJECT_APPLICATION.md#onboarding-checklist)
-- [ ] [Update to Project Progression](https://github.com/openjs-foundation/bootstrap/pull/158)
+- [ ] [Update to Project Progression](https://github.com/openjs-foundation/cross-project-council/pull/165)
 - [ ] Potential changes to CPC Charter
-- [ ] Discussion/approval by bootstrap committee
+- [ ] Discussion/approval by the Cross Project Council
 - [ ] Discussion/approval by the Board
 - [ ] Adoption by the CPC
 - [ ] Run existing projects through the process