Skip to content

Commit

Permalink
doc: update readme for CPC
Browse files Browse the repository at this point in the history 
Currently still specific to Bootstrap.

Old README is archived in artifacts

Refs: https://github.com/nodejs/TSC/blob/master/README.md
  • Loading branch information
@MylesBorins
MylesBorins committed May 20, 2019
1 parent 6cba4d6 commit b8ea5de
Show file tree
Hide file tree
Showing 2 changed files with 61 additions and 29 deletions.
47 changes: 18 additions & 29 deletions README.md
View file
Original file line number Diff line number Diff line change
@@ -1,43 +1,32 @@
# Foundation Bootstrap Team
# The OpenJS Foundation Cross Project Council

This is the operating repository for the Foundation Bootstrap Team.
The OpenJS Foundation Cross Project Council (CPC) is the technical governing body of the OpenJS Foundation. It is described in the [CPC Charter](./CPC-CHARTER.md)

The Foundation Bootstrap Team is the temporary body tasked with managing community recommendations for the transition of the merged Node.js and JS Foundation to a permanent governance model.
## CPC Scope

The files in this repository are living documents and will never represent finished governance. Once we reach consensus on governance, this repository will be archived and the documents will be moved to their new home in a Foundation specific Github org.
**The CPC is responsible for ensuring collaboration is the driving principle within a Project, between OpenJS Foundation Projects, and between OpenJS Foundation Projects and the broader community.**

Until such a time that this group has consensus on a new governance model, and the Foundation has any legal requirements satisfied, all projects, programs, and committees will continue to operate unchanged.
The CPC exercises autonomy in managing its responsibilities and seeks agreement from the OpenJS Foundation Board on any change to the scope of those responsibilities.

Upon enactment of this new governance model, this working body will be disbanded.
### OpenJS Fondation Projects

> Note: If there is to be an extended Bootstrap transition committee to, for example, provide oversight in the organization's first year, those criteria must be defined as a new program in the proposed governance model. There is no extension of **this** specific group's life-cycle.
* To be filled in

## OpenJS Foundation Members

## Definitions
Throughout this repository we may use assorted acronyms and jargon to describe many complex concepts. This language is subject to change as we iterate on proposals. To help onboard and level-set, we will maintain an active list of commonly used language here. If you see domain specific language used in this repository that is not represented here, please add it!
### Voting Memberss

| Vocabulary | Definition |
|---|---|
| Bootstrap | This repo, team, and process. |
| Contributor | You, and anyone that interacts with this repo. |
| Ignition | The decision to move forward with the new governance structure. |
| TLCs | The Top Level Councils of the project – Currently proposed as CPC and C3 (defined below) |
| CPC | A new proposed Top Level Committee – The "Cross Project Council |
| C3 | A new proposed Top Level Committee – The "Cross Community Council |
| CNCF | The Cloud Native Computing Foundation (Prior Art) |
| COC | Code of Conduct |
| MVF | Minimum Viable Foundation – The bare minimum governance documentation to operate a function joint foundation |
| Proposal | The staged proposal feedback and iteration process followed in the `/proposals` directory. |
### Regular Members

## Deliverables
The deliverables from this body will be:
### Observers

- [ ] A recommendations document to help inform the new Foundation's by-laws.
- [ ] A recommendations document to help inform the TLCs' charters.
- [ ] A collection of fully drafted governance documents required for "Ignition". This is "Minimum Viable Foundation" (MVF).
- [ ] A collection of program, initiative, and governance recommendation documents not required for MVF. After Ignition these will be passed to the appropriate bodies (CPC, C3, etc.) to execute.
## Policy Change Proposal Process


## Making proposals
The OpenJS CPC is chartered to oversee the technical governance of all OpenJS Projects and Working Groups under the OpenJS Foundation. The CPC establishes the default governance, conduct, and licensing policies for all Projects. Projects have broad powers of self-governance.

Anyone may submit an idea for a policy or program following the [staging process](STAGING_PROCESS.md).

The pull request can be labeled cross-project-council-agenda to request that it be put on the agenda for the next CPC meeting.

The OpenJS Foundation Board of Directors retains certain rights (especially legal considerations). If the CPC endorses a proposal, they will escalate to the OpenJS Foundation Board of Directors when required to do so.

43 changes: 43 additions & 0 deletions artifacts/BOOTSTRAP_README.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
# Foundation Bootstrap Team

This is the operating repository for the Foundation Bootstrap Team.

The Foundation Bootstrap Team is the temporary body tasked with managing community recommendations for the transition of the merged Node.js and JS Foundation to a permanent governance model.

The files in this repository are living documents and will never represent finished governance. Once we reach consensus on governance, this repository will be archived and the documents will be moved to their new home in a Foundation specific Github org.

Until such a time that this group has consensus on a new governance model, and the Foundation has any legal requirements satisfied, all projects, programs, and committees will continue to operate unchanged.

Upon enactment of this new governance model, this working body will be disbanded.

> Note: If there is to be an extended Bootstrap transition committee to, for example, provide oversight in the organization's first year, those criteria must be defined as a new program in the proposed governance model. There is no extension of **this** specific group's life-cycle.

## Definitions
Throughout this repository we may use assorted acronyms and jargon to describe many complex concepts. This language is subject to change as we iterate on proposals. To help onboard and level-set, we will maintain an active list of commonly used language here. If you see domain specific language used in this repository that is not represented here, please add it!

| Vocabulary | Definition |
|---|---|
| Bootstrap | This repo, team, and process. |
| Contributor | You, and anyone that interacts with this repo. |
| Ignition | The decision to move forward with the new governance structure. |
| TLCs | The Top Level Councils of the project – Currently proposed as CPC and C3 (defined below) |
| CPC | A new proposed Top Level Committee – The "Cross Project Council |
| C3 | A new proposed Top Level Committee – The "Cross Community Council |
| CNCF | The Cloud Native Computing Foundation (Prior Art) |
| COC | Code of Conduct |
| MVF | Minimum Viable Foundation – The bare minimum governance documentation to operate a function joint foundation |
| Proposal | The staged proposal feedback and iteration process followed in the `/proposals` directory. |

## Deliverables
The deliverables from this body will be:

- [ ] A recommendations document to help inform the new Foundation's by-laws.
- [ ] A recommendations document to help inform the TLCs' charters.
- [ ] A collection of fully drafted governance documents required for "Ignition". This is "Minimum Viable Foundation" (MVF).
- [ ] A collection of program, initiative, and governance recommendation documents not required for MVF. After Ignition these will be passed to the appropriate bodies (CPC, C3, etc.) to execute.


## Making proposals

Anyone may submit an idea for a policy or program following the [staging process](STAGING_PROCESS.md).

0 comments on commit b8ea5de

Please sign in to comment.