Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Governance Reset #15390

Open
6 tasks
lucasgonze opened this issue Mar 11, 2024 · 5 comments
Open
6 tasks

Proposal: Governance Reset #15390

lucasgonze opened this issue Mar 11, 2024 · 5 comments
Labels
type: proposal Proposals and design documents

Comments

@lucasgonze
Copy link
Contributor

lucasgonze commented Mar 11, 2024

Proposal: Governance Reset

This ticket obsoletes and updates #15376

Problem

Magma governance is mainly obsolete cruft. It was originally structured to fit a Meta-centric orientation. In the shift to independence and a proper open source community the governance has not kept up.

Solution

Revisit every aspect of governance:

  • Rewrite charter
  • Rewrite all github.com/magma/community documents and community-related documents in the magma repository.
  • Proposed new structure for the TSC, including quorum changes
  • Ensure compliance with legal constraints
  • Shepherd votes by current TSC to put changes into practice
  • Build consensus and buy-in to the greatest extent possible

Non-goals

Changes to the formal non-profit. However I will probably have to research and document what the non-profit is.

Advocacy. Though I will and do have personal points of view, they are out of scope in this proposal.

Changes

Timeout

Proposed timeout on membership:

Three months without any participation in any way
Three TSC votes without participation

When a member departs, a call for an election to fill their seat will be made.

Address questions:

How long can the seat be vacant?
If a TSC member is on timeout - can (s)he be reinstated?
What happens to the quorum rules when a TSC membership is cancelled and there are less than 5 members?

Formalize Participation and Non-Participation

We need to define the participation in a vote properly. Not participating in a vote as a form of statement (ex. the member is so agains something so he dosn't want to vote in order not to contribute to that motion at all) is a valid way to express disagreement. This form of not participating should not lead you to disqualification from TSC, therefore maybe we should consider if there was activity not only formal vote. Also, we need to make sure we give enough time for the TSC member to be active on the vote, so just saying not participating in three votes without adding a perspective of a timeline can lead to automatic disqualifications. Ex: we call for 3 votes in a single day and all 3 are voted (pass of fail), the people who had not voted are on this issues will be automatically subject of the rule of not participating in 3 votes since there is no time frame.

Proposal: add abstention (or "present") to vote options.

Abstention preserves TSC seat.
Abstention doesn't count in quorum.

Quorum rules determined by number of voters on last vote.

Snap elections need to be accounted for.

Add "not participating in three votes AND not voting for three weeks" to timeout rules.

Add guiding principles about fairness to community and also fairness to the voter in the power to express themselves. Create a text preamble.

New plurality approach

A sensible way to have a flexible quorum of 3-5 members

This ticket absorbs and moots #15375

Tasks

Professional writing for the new documentation.

Eliminate out of date documentation that would contradict new structures.

Talk to Legal at Linux Foundation.

Coordinate with Board of Directors for non-profit

Initiate a vote under the old roles to accept the new rules

Operational Issues

I am requesting $4,000 to execute this proposal.

Note that I am making this proposal as an independent and not under the OSPOCO banner.

@lucasgonze lucasgonze added the type: proposal Proposals and design documents label Mar 11, 2024
@jordanvrtanoski
Copy link
Contributor

I second this proposal

@lucasgonze
Copy link
Contributor Author

Motion to vote: Lucas.
Seconded: Jordan.
Next: call for vote.

@jordanvrtanoski
Copy link
Contributor

jordanvrtanoski commented Mar 19, 2024

Vote: +1 (vote "for")

@lucasgonze
Copy link
Contributor Author

@panyogesh
Copy link
Contributor

+1

lucasgonze added a commit to magma/Governance that referenced this issue Apr 25, 2024
lucasgonze added a commit to lucasgonze/magma that referenced this issue Apr 29, 2024
…gma#15390

On investigation I determined that the Magma_Technical_Charter_Final_1-26-2021.docx.pdf file was superceded by a later version dated  March 15, 2021 and located at /Governance/blob/main/CHARTER.md. To preserve governance history I have preserved the contents of this file but am renaming it to make the status clear.

As part of the governance reset I have removed links to the Community repo.

Signed-off-by: Lucas Gonze <lucas@gonze.com>
lucasgonze added a commit to lucasgonze/magma that referenced this issue Apr 29, 2024
…gma#15390

On investigation I determined that the Magma_Technical_Charter_Final_1-26-2021.docx.pdf file was superceded by a later version dated  March 15, 2021 and located at /Governance/blob/main/CHARTER.md. To preserve governance history I have preserved the contents of this file but am renaming it to make the status clear.

As part of the governance reset I have removed links to the Community repo.

Updated README to add Nathaniel Bennett.

Signed-off-by: Lucas Gonze <lucas@gonze.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: proposal Proposals and design documents
Projects
None yet
Development

No branches or pull requests

3 participants