The OpenJS Foundation Cross Project Council (CPC) is the technical governing body of the OpenJS Foundation. It is described in the CPC Charter
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.
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.
| Project | Charter | Contributing | |
|---|---|---|---|
 |
Appium | Contributing Guide | |
 |
Dojo | Contributing Guide | |
 |
Electron | Charter | Contributing Guide |
 |
jQuery | Contributing Guide | |
 |
Node.js | Contributing Guide | |
 |
webpack | Contributing Guide |
| Project | Charter | Contributing | |
|---|---|---|---|
 |
Ajv | Contributing Guide | |
| kepler.gl | Contributing Guide | ||
 |
NativeScript | Contributing Guide | |
| vis.gl | Contributing Guide |
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
| Name | Repository | Authority Delegation | Description |
|---|---|---|---|
| Ecosystem Report | Repository | No | JavaScript ecosystem annual end-users poll and report |
| Open Visualization (OpenVis) | Repository | No | Visualization libraries based on JavaScript and WebGL |
| Package Metadata Interop | Repository | No | Interoperability of package.json across the JS ecosystem |
| Package Vulnerability Management & Reporting | Repository | No | Package vulnerability management and reporting |
| Security | Repository | No | Documentation and coordination of the Foundation's security effort |
| Standards | Repository | Yes | Facilitate the engagement of projects and collaborators in standards organizations |
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.
- Joe Sepi (@joesepi, IBM)
- Tobie Langel (@tobie, UnlockOpen)
CPC Directors represent the Foundation's projects and related communities to the Board.
Each Impact Project may appoint 2 representatives to the CPC as outlined in the CPC Charter
- Appium
- Jonathan Lipps (@jlipps)
- Kazuaki Matsuo (@KazuCocoa)
- Dojo
- Dylan Schiemann (@dylans, Living Spec)
- Electron
- Erick Zhao (@erickzhao, Slack)
- Michaela Laurencin (@mlaurencin, Microsoft)
- jQuery
- Node.js
- webpack
- Claudio Wunder (@ovflowd)
- Even Stensberg (@evenstensberg)
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.
- Jordan Harband (@ljharb, HeroDevs)
- Ulises Gascón (@UlisesGascon, NodeSource)
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:
Members of the Collaboration spaces at the Core stage may nominate a candidate 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.
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. Outgoing Voting members automatically become Regular members, although they must remain active to retain their status.
- Abigail Cabunoc Mayes (@abbycabs)
- Adrian Estrada (@edsadr)
- Alexander Akait (@alexander-akait)
- Chris de Almeida (@ctcpip)
- Christian Bromann (@christian-bromann)
- Claudio Wunder (@ovflowd)
- Cody Zuschlag(@codyzu)
- Darcy Clarke (@darcyclarke)
- Divy Tolia (@designmoreweb)
- Dylan Schiemann (@dylans)
- Eemeli Aro (@eemeli)
- Erick Zhao (@erickzhao)
- Ethan Arrowood (@Ethan-Arrowood)
- Even Stensberg (@evenstensberg)
- Jean Burellier (@sheplu)
- Joe Sepi (@joesepi)
- Jon Church (@jonchurch)
- Jonathan Lipps (@jlipps)
- Jordan Harband (@ljharb)
- Jory Burson (@jorydotcom)
- Kazuaki Matsuo (@KazuCocoa)
- Marco Ippolito (@marco-ippolito)
- Matteo Collina (@mcollina)
- Mert Can Altin (@mertcanaltin)
- Michael Dawson (@mhdawson)
- Michaela Laurencin (@mlaurencin)
- Michał Gołębiowski-Owczarek (@mgol)
- Mike Samuel (@mikesamuel)
- Mohammed Keyvanzadeh (@VoltrexKeyva)
- Natalia Venditto (@anfibiacreativa)
- Nick O'Leary (@knolleary)
- Nitin Kumar (@snitin315)
- Paula Paul (@paulapaul)
- Rick Markins (@rxmarbles)
- Rich Trott (@Trott)
- Rifa Achrinza (@achrinza)
- Ruy Adorno (@ruyadorno)
- Sara Chipps (@sarajo)
- Sean Larkin (@TheLarkInn)
- Shelley Vohr (@codebytere)
- Timmy Willison (@timmywil)
- Tobie Langel (@tobie)
- Ulises Gascón (@ulisesgascon)
- Waleed Ashraf (@waleedashraf)
- Wes Todd (@wesleytodd)
- Yagiz Nizipli (@anonrig)
- Abraham Jr Agiri (@codeekage)
- Antón Molleda (@molant)
- Ben Hutton (@relequestual)
- Ben Michel (@obensource)
- Christopher Hiller (@boneskull)
- Dhruv Jain (@maddhruv)
- Kris Borchers (@kborchers)
- Marcin Hoppe (@MarcinHoppe)
- Myles Borins (@MylesBorins)
- Parris Lucas (@GrooveCS)
- Sendil Kumar (@sendilkumarn)
- Tierney Cyren (@bnb)
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.
- Project Progression - This describes the different stages a project can go through at the Foundation, from applying to retiring, and provides relevant processes and checklists for moving along them.
- New Project Application Template - Template document that should be used by projects that want to apply to the Foundation.
- Project Charter Template - Template document to be used by new projects to write their charter as part of onboarding.
- Project Security Reporting - Describes the requirements for reporting security vulnerabilities.
- IP_Policy Guidance - Outlines the relevant aspects of the Foundation's IP policy to make it easier for new projects to implement them.
- Guide to Community Health Files - Provides guidance on how to organize community health files, as well as which files are expected for OpenJS Foundation Projects
- Code of Conduct - This is the canonical version of the code of conduct adopted by the Foundation and all of its projects.
- Code of Conduct Policy - This describes the Foundation's policy for code of conducts.
- Incident Management Processes - This explains how the CoC Team and projects handle code of conduct violations and how, when, and to whom they need to be escalated.
- Member Expectations - Additional behavior expectations of CPC members and project leaders.
- CPC Charter - The CPC's charter describes the CPC's mission as defined in the Bylaws.
- OpenJS Cross Project Council Governance - Describes how the CPC operates.
- Expectations of the Community Board of Directors Representatives - Description of the role and responsibilities of the Community Board of Directors Representatives.
- GitHub organization Management Policy - Policy for managing the CPC's GitHub organization.
- Community / Travel Fund - OpenJS Foundation projects and their community members are able to take advantage of our community fund.
- OpenJS Ecosystem Sustainability Program - The Ecosystem Sustainability Program is an opt-in OpenJS partner program to help secure outdated software and create new revenue streams for our projects.
The OpenJS CPC is chartered to oversee the technical governance of all OpenJS Projects and Collaboration spaces 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 by opening an issue in this repository. The issue should be reviewed at 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.
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.
OpenJS Foundation Collaboration spaces are able to take advantage of several services and benefits as outlined in COLLABORATION_NETWORK.md.
OpenJS projects that have formally engaged with LF IT to support one or more of their services should follow this guide for requesting support.
In almost all situations, the best way to get support is to file a ticket with The Linux Foundation. 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)
Current and prospective members of the OpenJS Foundation can file a ticket with the service desk for help with topics such as billing, logo management on the website, etc.
Projects with questions on relevant legal topics are encouraged to email the legal-questions mailing list. This is a private list with closed membership, 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, such as main.
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.
For any other topics which aren't covered above, please file a ticket with the service desk.