docs: add governance (bdfl) - #2
Open
Abusalah0 wants to merge 1 commit into
Open
Conversation
Open
Member
Author
|
this is a comprehensive bdfl, if you guys see it overkill we can subtract sections |
Member
|
I think this is too verbose. I'll have a look and see where we can cut and merge sections. |
Member
Author
|
Me too, I put everything I can so we can choose exactly what we need, i think a governance should not exceed a 100 lines anyway. |
dotacow
approved these changes
Aug 3, 2026
Comment on lines
+5
to
+11
| ## 1. Scope | ||
|
|
||
| The csi-rs project develops open-source Rust software for collecting, transporting, processing, storing, and visualizing Wi-Fi Channel State Information on ESP devices and host systems. | ||
|
|
||
| This governance policy applies to all repositories owned by the csi-rs organization unless a repository contains an approved supplementary governance document. | ||
|
|
||
| Repository-specific governance may define additional responsibilities, such as release managers or component owners, but it must not contradict this organization-wide policy. |
Member
There was a problem hiding this comment.
Most of this should exist in the README rather than this file
Comment on lines
+21
to
+23
| The BDFL has final authority over the direction and governance of the project. In normal operation, however, decisions should be delegated to repository maintainers and reached through open discussion and consensus. | ||
|
|
||
| The term “for life” does not require the BDFL to serve permanently. The BDFL may resign, appoint a successor, become unable to serve, or be removed under the exceptional circumstances defined in this document. |
Comment on lines
+29
to
+37
| ### Openness | ||
|
|
||
| Technical proposals, decisions, and their reasoning should normally be recorded in public issues, pull requests, discussions, or project documentation. | ||
|
|
||
| Security matters, conduct reports, personal information, and other sensitive matters may be handled privately. | ||
|
|
||
| ### Technical merit | ||
|
|
||
| Decisions should be based on technical evidence, maintainability, compatibility, user impact, project scope, and the long-term health of the ecosystem. |
Comment on lines
+147
to
+159
| Examples include: | ||
|
|
||
| * Breaking changes to a public Rust API. | ||
| * Changes to the device-to-host command protocol. | ||
| * Changes to serialized CSI or configuration formats. | ||
| * Removing support for an ESP chip, development board, or operating mode. | ||
| * Introducing a major dependency or runtime requirement. | ||
| * Splitting, merging, renaming, transferring, or archiving a repository. | ||
| * Creating a new official csi-rs repository. | ||
| * Changing licensing or package ownership. | ||
| * Making incompatible changes between firmware, server, and client releases. | ||
| * Changing release or compatibility policy. | ||
| * Modifying project governance. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I added a full bdfl governance file to fully explain the governance and responsibility to contributors and maintainers