Public repository for governance issues and documents
Перейти к файлу
David Sanders ae6d587973
chore: add @samuelmaddock and @dsanders11 to Upgrades WG (#587)
2024-11-19 12:00:53 -08:00
.github ci: fix lint workflow (#573) 2024-05-15 10:31:44 +02:00
archived/2021-02-22/wg-qa chore: de-commission and Archive QA Working Group (#404) 2021-08-07 13:23:42 -05:00
charter chore: add emeritus members to working groups (#563) 2023-11-27 13:09:02 -05:00
playbooks chore: update code of conduct violations playbook (#544) 2023-06-13 06:55:45 -07:00
policy chore: fix broken link (#540) 2023-05-09 12:22:27 -07:00
wg-administrative chore: Felix is back on wg-admin (#582) 2024-09-12 13:30:50 -07:00
wg-api docs: define practices for third-party extensible APIs (#586) 2024-10-10 14:26:57 -04:00
wg-community-safety chore: add new members to community and safety WG (#584) 2024-09-19 12:18:12 -07:00
wg-ecosystem chore(wg-ecosystem): add Node version policy and cleanup (#578) 2024-07-25 11:03:31 -07:00
wg-infra docs: document the current state of npm access (#581) 2024-09-09 16:30:21 -04:00
wg-outreach docs: Add alicelovescake to wg-outreach (#571) 2024-04-02 10:05:22 -07:00
wg-releases chore: move inactive members to emeritus members (#572) 2024-05-03 11:32:11 -04:00
wg-security doc: initial document for GHSA triage and publish (#583) 2024-10-16 10:46:55 +02:00
wg-upgrades chore: add @samuelmaddock and @dsanders11 to Upgrades WG (#587) 2024-11-19 12:00:53 -08:00
.markdownlint.json chore: enable remaining linting rules (#543) 2023-06-08 16:20:29 -07:00
.markdownlintignore build: lint Markdown (#535) 2023-05-09 09:09:00 -07:00
CODE_OF_CONDUCT.md copy CoC from 'electron/electron' (#41) 2019-03-13 09:53:05 -05:00
README.md build: lint Markdown (#535) 2023-05-09 09:09:00 -07:00

README.md

Electron Governance

The Electron governance system is comprised of Working Groups that oversee different aspects of the Electron ecosystem, and an Administrative working group that functions to resolve conflicts between them.

Working Groups

+----------------------------------------------------------------------------+
|                            Electron Governance                             |
|                          Development & Moderation                          |
|                                                                            |
|                                                                            |
|                               WORKING GROUPS                               |
| +----------------------+ +----------------------+ +----------------------+ |
| |         API          | |  Community & Safety  | |       Ecosystem      | |
| +----------------------+ +----------------------+ +----------------------+ |
| +----------------------+ +----------------------+ +----------------------+ |
| |       Outreach       | |       Releases       | |       Security       | |
| +----------------------+ +----------------------+ +----------------------+ |
|             +----------------------+  +----------------------+             |
|             |       Upgrades       |  |    Infrastructure    |             |
|             +----------------------+  +----------------------+             |
+----------------------------------------------------------------------------+

Definitions

  • A maintainer is anyone who plays an active role in governance.
  • A collaborator is active in the community, but not in governance.
  • A participant is anyone who is a maintainer or collaborator.
  • A working group is a group of maintainers that is formed to take responsibility for certain aspects of the Electron project. Normally these groups will meet regularly but in some cases will only meet as required to fulfill their responsibilities.
  • A chair leads a working group.

Responsibilities

All Working Groups have these core responsibilities:

  • They shall decide for themselves, and publicly post, their rules, e.g. how decisions are made, when meetings are held, and who may attend.
  • They shall select a chair to represent the group.
  • They shall keep meeting notes, including agenda items, discussion points, and outcomes for everyone to review.
  • They shall be collaborative and work in good faith with other Working Groups.

See charter/README.md for more information.

Code of Conduct

The Electron organization and all repos therein adhere to the following Code of Conduct.

License

Electron is licensed with an MIT License.