Understand which Working Group is responsible for a specific decision about Electron.
Learn how to become a chair or join a Working Group in the Electron project.
Reference the shared Code of Conduct or the definitions of maintainer, collaborator, and participant.
| electron/governance | shannhk/hermes-agent-control-room | itsinseong/value-for-fable | |
|---|---|---|---|
| Stars | 162 | 177 | 136 |
| Language | Shell | Shell | Shell |
| Setup difficulty | easy | hard | easy |
| Complexity | 1/5 | 4/5 | 2/5 |
| Audience | developer | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
This repository documents how the Electron open source project governs itself. Electron is the framework that lets developers build desktop applications using web technologies, and this repo explains who makes decisions about the project and how those decisions actually get made, rather than containing any part of Electron itself. The governance model is organized around Working Groups, each responsible for a different area. The README lists groups covering the public API, community safety and moderation, the broader ecosystem of related tools and repositories, outreach and communication, releases, security, technical upgrades, and infrastructure. Each working group is expected to decide and publicly post its own internal rules, such as how it makes decisions, when it meets, and who may attend, and each keeps its own meeting notes and associated documents inside this repository. An Administrative Working Group sits above the others and exists specifically to resolve conflicts between working groups when they disagree. Every working group selects a chair to represent it, and the chair role rotates on a defined schedule described in a separate charter document rather than being permanent. The README also defines the project's core vocabulary: a maintainer is anyone who plays an active role in governance, a collaborator is active in the community but not in governance, and a participant is anyone who counts as either one. All working groups and participants are expected to follow a shared Code of Conduct kept in this repository. The project is released under the MIT License, a permissive license that allows reuse with attribution. The content here is mostly documentation and process definitions rather than application source code.
Documentation of how Electron's open-source project is governed, through separate Working Groups and a shared charter.
Mainly Shell. The stack also includes Markdown.
Use, copy, modify, and distribute this project's content freely, including for commercial purposes, as long as you keep the copyright notice.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.