Skip to content
main
Switch branches/tags
Code

Latest commit

* ci(automation): add dead link checking

* fix: add private repo to skip list

* fix: unbreak Contributor Covenant link

* fix: old meeting deep link

* fix: broken proposal links

* fix: update broken links to PROJECT_PROGRESSION

* fix: update broken link to EXPECTATIONS

* fix: updated broken links to INDVIDIUAL_MEMBERSHIP

* fix: remove broken link to repo that doesn't exist

* fix: update broken link to CPC charter proposal

* fix: update link to FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md

* fix: make a markdown link work by using correct syntax

* fix: update AJV contributing link

* fix: add space to unbreak links

* chore: remove link to broken/removed PR in the Node.js org

* chore: update broken links that have transitioned to openjs-foundation from nodejs

* fix: update k8s links

* fix: update link to use correct branch/filename

* chore: remove broken link to ancient Project Progression proposal

* fix: update old broken link to Community Board Representation proposal

* fix: use HEAD rather than master

* Revert "fix: update link to use correct branch/filename"

This reverts commit f167243.

* chore: use `HEAD` instead of `master`

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix: update old link to repo that doesn't exist to working link

* chore: reflect change from "staging process" to "proposal process"

* fix: use permanent link to Node.js contributing file

* re-add broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* add missing trailing newline

* chore: main > head

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* chore: main > head

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* chore: fix missing broken link

* docs: remove reference to non-existent document

* docs: link fixes

* doc: fix AMP contributing link

* docs: link fixes in proposals readmes

* docs: more link changes

* docs: fix old broken github link

* Globally replace all /master/ and /main/ to /HEAD/

* Travel fund request: Unicode Conference, 13-16 October (#800)

* chore: Rename TRAVEL_FUND/2020.md -> TRAVEL_FUND/2021.md

* Add travel fund request for Unicode Conference

* Update Dojo CoC (#799)

Leverage the OpenJSF reporting email address rather than a dead Google form.

* ci(automation): add dead link checking

* fix: add private repo to skip list

* fix: unbreak Contributor Covenant link

* fix: old meeting deep link

* fix: broken proposal links

* fix: update broken links to PROJECT_PROGRESSION

* fix: update broken link to EXPECTATIONS

* fix: updated broken links to INDVIDIUAL_MEMBERSHIP

* fix: remove broken link to repo that doesn't exist

* fix: update broken link to CPC charter proposal

* fix: update link to FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md

* fix: make a markdown link work by using correct syntax

* fix: update AJV contributing link

* fix: add space to unbreak links

* chore: remove link to broken/removed PR in the Node.js org

* chore: update broken links that have transitioned to openjs-foundation from nodejs

* fix: update k8s links

* fix: update link to use correct branch/filename

* chore: remove broken link to ancient Project Progression proposal

* fix: update old broken link to Community Board Representation proposal

* fix: use HEAD rather than master

* Revert "fix: update link to use correct branch/filename"

This reverts commit f167243.

* chore: use `HEAD` instead of `master`

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix: update old link to repo that doesn't exist to working link

* chore: reflect change from "staging process" to "proposal process"

* fix: use permanent link to Node.js contributing file

* re-add broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* fix broken link

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* add missing trailing newline

* chore: main > head

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* chore: main > head

Co-authored-by: Jordan Harband <ljharb@gmail.com>

* chore: fix missing broken link

* docs: remove reference to non-existent document

* docs: link fixes

* doc: fix AMP contributing link

* docs: link fixes in proposals readmes

* docs: more link changes

* docs: fix old broken github link

* Globally replace all /master/ and /main/ to /HEAD/

* doc: update alternate process

* doc: remove dead link from old CPC charter doc

* doc: remove unnecessary link that doesn't work

* ci: rename to link-checker

* fixup

Co-authored-by: Jordan Harband <ljharb@gmail.com>
Co-authored-by: Eemeli Aro <eemeli@gmail.com>
Co-authored-by: Dylan Schiemann <dylan@dojotoolkit.org>
4201e8a

Git stats

Files

Permalink
Failed to load latest commit information.

The OpenJS Foundation Cross Project Council

The OpenJS Foundation Cross Project Council (CPC) is the technical governing body of the OpenJS Foundation. It is described in the CPC Charter

CPC Scope

The CPC's primary role is to foster an environment of collaboration. That environment extends within and between OpenJS Foundation Projects, OpenJS Collaboration spaces, and the larger community.

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.

OpenJS Foundation Projects

The following projects are official OpenJS Foundation projects. If you are interested in bringing your project to the OpenJS Foundation, please read our Project Progression and New Project Application documents, or contact any CPC member with questions.

Impact Projects

Project Charter Contributing Code of Conduct
logo of project Appium Appium Contributing Guide Code of Conduct
logo of project Dojo Dojo Contributing Guide Code of Conduct
logo of project Electron Electron Contributing Guide Code of Conduct
logo of project jQuery jQuery Contributing Guide Code of Conduct
logo of project Node.js Node.js Contributing Guide Code of Conduct
logo of project webpack webpack Contributing Guide Code of Conduct

At-Large Projects

Project Charter Contributing Code of Conduct
logo of AMP project AMP Contributing Guide Code of Conduct
logo of project architect architect Contributing Guide Code of Conduct
logo of project ESLint ESLint Contributing Guide Code of Conduct
logo of project Esprima Esprima Contributing Guide
logo of project Express Express Contributing Guide Code of Conduct
logo of project Fastify Fastify Contributing Guide Code of Conduct
logo of project Globalize Globalize Contributing Guide
logo of project Grunt Grunt Contributing Guide Code of Conduct
logo of project HospitalRun HospitalRun Contributing Guide Code of Conduct
logo of project Interledger.js Interledger.js Contributing Guide
logo of project Intern Intern Contributing Guide
logo of project JerryScript JerryScript Contributing Guide
logo of project Libuv Libuv Contributing Guide
logo of project Lodash Lodash Contributing Guide
logo of project Marko Marko Contributing Guide Code of Conduct
logo of project messageformat messageformat Contributing Guide Code of Conduct
logo of project Mocha Mocha Contributing Guide Code of Conduct
logo of project Moment Moment Contributing Guide
logo of project Node-RED Node-RED Contributing Guide Code of Conduct
logo of project nvm nvm Charter Contributing Guide Code of Conduct
logo of project PEP PEP Contributing Guide Code of Conduct
logo of project QUnit QUnit Contributing Guide Code of Conduct
logo of project WebdriverIO WebdriverIO Contributing Guide Code of Conduct
logo of project webhint webhint Contributing Guide Code of Conduct

Emeritus Projects

Project Charter Contributing Code of Conduct
logo of project Chassis Chassis Contributing Guide Code of Conduct
logo of project jQuery Mobile jQuery Mobile Contributing Guide Code of Conduct
logo of project jQuery UI jQuery UI Contributing Guide Code of Conduct
logo of project RequireJS RequireJS Contributing Guide Code of Conduct
logo of project Sizzle Sizzle Contributing Guide Code of Conduct

Incubating Projects

Project Charter Contributing Code of Conduct
logo of project ajv Ajv Contributing Guide Code of Conduct
logo of project LoopBack LoopBack Contributing Guide Code of Conduct
logo of project NativeScript NativeScript Contributing Guide Code of Conduct

OpenJS Collaboration spaces

The following are official OpenJS Collaboration spaces. If you are interested in fostering collaboration with the support of the OpenJS foundation through a collaboration space, please read our Collaboration Space Progression

  • There are currently no collaboration spaces.

CPC Meetings

The CPC meets weekly. We publish meeting agendas as issues, and also publish meetings on our calendar. (iCal) (Add to Google Calendar)

CPC members should attend as many meetings as possible, and non-members are welcome to join as observers. To add an item to the agenda, create an issue and add the cross-project-council-agenda label.

CPC Members

Voting Members

Impact Project Representatives

Each Impact Project may appoint 2 representatives to the CPC as outlined in the CPC Charter

At Large Project Representatives

According to the CPC Charter, each of the At Large and Incubating Projects may nominate a candidate to fill one of two voting seats on the CPC which represent this group of projects as a whole. From those nominees, two voting members are chosen via an election process outlined in the CPC Governance.

  • Eemeli Aro (@eemeli, Mozilla)
  • Tobie Langel (@tobie, UnlockOpen)

Elected by Regular Members

According to the CPC Charter, up to two regular members can be elected as voting members. The two regular members elected as voting members are currently:

Collaboration space representatives

Members of the Collaboration spaces at the Core stage may nominate a candiate for one of the voting seats on the CPC which represents the Collaboration spaces. Currently there are no spaces at the Core stage and therefore no representative.

Regular Members

Anyone who has been active in the foundation or one of its member projects, as described in the CPC Governance may request to become a regular member by opening a PR to add themselves to the list of regular members. Outgoing Voting members automatically become Regular members, although they must remain active to retain their status.

Regular Member emeriti

Observers

Anyone can be an Observer. Observers are free to attend meetings and participate in the work of the CPC as well as the consensus seeking process. Observers are encouraged to participate and volunteer but should refrain from disrupting or blocking progress. Observers are expected to participate in a positive and collaborative manner as well as following the code of conduct and member expectations like other CPC participants. If an Observer fails to meet these expectations they can be excluded from future CPC meetings based on a standard CPC motion.

Policy Change Proposal Process

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

Anyone may submit an idea for a policy or program following the proposal process.

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.

Communication Channels

CPC discussion generally happens via GitHub issues and during our regular public meetings, which are open to CPC members and observers.

In addition, the OpenJS Foundation maintains a number of mailing lists. Project participants are strongly encouraged to subscribe to the projects@lists.openjsf.org list for technical updates and discussion.

Discussion should be held in the open whenever possible. However, if you need to raise a private concern with the CPC and you feel it is inappropriate for public discussion, you can email the cpc-private@lists.openjsf.org list. Depending upon the circumstances, the CPC may request that you resubmit the issue in a public forum.

Getting Help

Project Resources & Travel Fund

OpenJS Foundation projects and their community members are able to take advantage of several services and benefits, including the Travel Fund Program. Details can be found in the /project-resources directory.

OpenJS Foundation Collaboration spaces are able to take advantage of several services and benefits as outlined in COLLABORATION_NETWORK.md.

Help with project infrastructure

In almost all situations, the best way to get support is to email operations@openjsf.org with your request. For example:

  • Requesting DNS changes
  • Adding a project-specific mailing list to lists.openjsf.org
  • Updates to links on https://openjsf.org
  • Storing/sharing credentials through LastPass
  • Third-party services which require payment (subject to Board approval)

Help with membership

Members of the OpenJS Foundation can email operations@openjsf.org with any questions.

Help with legal questions (for existing projects only)

Projects with questions on relevant legal topics are encouraged to email the legal-questions mailing list. This is a private list, and we will route your question appropriately.

In order to mail this list, you must be subscribed to at least one other OpenJS Foundation mailing list.

Help with press and media

The OpenJS Foundation has marketing staff which can provide guidance on inbound media requests. Please reach out to pr@openjsf.org.

If you have project-related news that you wish to share, please contact marketing@openjsf.org. If you need a place to post your news, Foundation staff can review whether it is appropriate for the OpenJS Foundation blog. If it makes sense, Foundation staff can also include your news in the summaries sent to the projects mailing list, or schedule posts on Foundation social channels.

If you run your project's social media and would like the Foundation to share or retweet project news, please DM the Foundation's account or send an email with a link to marketing@openjsf.org.

All other topics

For any other topics which aren't covered above, please email operations@openjsf.org.

About

OpenJS Foundation Cross Project Council

Resources

License