-
Notifications
You must be signed in to change notification settings - Fork 28
Feat/add scs 0005 project governance #813
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
Merged
Merged
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
9cfa25c
very very first work on describing the project governance
fkr 97b48f0
speling
fkr c4474a1
fix: linter
jschoone c50acef
suggestions from yesterdays's PB.
fkr 9207b42
fix: linter
jschoone 9270937
add a paragraph on how to join the github org
fkr a649686
clarification on how the spokesperson of the project board is elected.
fkr 6cea633
add a comment regarding on how to nominate people.
fkr 4b0dfc0
fix: style/language
jschoone f09ba81
Update scs-0005-v1-project-governance.md
jschoone 45dec50
Update 2024-12-project-board-nominees.md
jschoone bd79d3a
ease it a bit and by thus avoiding an initial exception
fkr 0daa7f8
rework the voting process according to the discussion in yesterday's …
fkr 606c788
details on IAM system
fkr f0a2efb
Update Standards/scs-0005-v1-project-governance.md
fkr bde6fbd
Update Standards/scs-0005-v1-project-governance.md
fkr b0cb6a9
linting
fkr 48e079c
add proper link
fkr 9b2d506
no stabilized_at: field at this stage
fkr 561390e
Language fixes
garloff 5f0bfb2
More language fixes
garloff f831897
Even more language fixes.
garloff 2fb2ff0
Update Standards/scs-0005-v1-project-governance.md
fkr 3eb00ce
Merge branch 'main' into feat/add-scs-0005-project-governance
garloff 6b96f60
Update Standards/scs-0005-v1-project-governance.md
fkr 5ef3dc8
markdown lint
fkr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| # Nominees 2024-12 Project Board | ||
|
|
||
| For the term 2024-12 - 2025-12 the following people are nominated / have nominated themselves: | ||
|
|
||
| | Name | Github Handle | E-Mail | | ||
| | -----| ------------- | ------ | | ||
| | | | | |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,115 @@ | ||
| --- | ||
| title: Sovereign Cloud Standards | ||
| type: Procedural | ||
| status: Draft | ||
| track: Global | ||
| description: | | ||
| SCS-0005 outlines the structure and governance of the SCS community by the SCS Project Board and how this is elected. | ||
| --- | ||
|
|
||
| ## Introduction | ||
|
|
||
| The [Sovereign Cloud Stack (SCS)](https://scs.community) provides standards | ||
| for a range of cloud infrastructure types as well as a modular open-source | ||
| reference implementation. | ||
| The project is governed by the _SCS Project Board_. | ||
|
|
||
| ## Role of the _SCS Project Board_ | ||
|
|
||
| The role of the _SCS Project Board_ is the overall governance of the SCS Community and Project. | ||
| This happens together with the _Forum SCS-Standards_ of the Open Source Business Alliance. To further | ||
| underline this alignment, the _Forum SCS-Standards_ is part of the _SCS Project Board_. | ||
| The _SCS Project Board_ itself is elected by the _SCS Community_. | ||
|
|
||
| ### Definitions | ||
|
|
||
| #### _SCS Project_ | ||
|
|
||
| The _SCS Project_ is the Open-Source project that consists of the software, documentation, documents, blog posts as well as the people ("_SCS Community_") working on this. | ||
|
|
||
| #### _SCS Community_ | ||
|
|
||
| The collective of people, companies, and organizations promoting the idea of the _SCS Project_ as well as the people working on the various aspects. | ||
|
|
||
| #### _SCS GitHub Organization_ | ||
|
|
||
| The _SCS GitHub Organization_ is this: [https://github.com/sovereigncloudstack](https://github.com/sovereigncloudstack) | ||
|
|
||
| ### Roles in the _SCS GitHub Organization_ | ||
|
|
||
| #### Members | ||
|
|
||
| Joining the SCS GitHub Organization as a contributor results in being assigned the **member role** in the organization. Members are contributors or collaborators who: | ||
|
|
||
| - Actively contribute to projects within the organization. | ||
| - Have repository-specific access based on their contributions. | ||
| - Are eligible to vote in elections and nominate candidates for the _SCS Project Board_. | ||
| - Must adhere to the [Code of Conduct](https://github.com/SovereignCloudStack/.github/blob/main/CODE_OF_CONDUCT.md). | ||
|
|
||
| #### Owners | ||
|
|
||
| Members of the _SCS Project Board_ are also designated as **owners** of the SCS GitHub organization. Owners have administrative privileges, including: | ||
|
|
||
| - Managing organization-level settings. | ||
| - Onboarding new members. | ||
| - Enforcing compliance with governance and community standards. | ||
|
|
||
| This alignment ensures that governance roles in the SCS Project Board directly translate into operational responsibilities within the GitHub organization. | ||
|
|
||
| ## Joining the SCS GitHub Organization | ||
|
|
||
| Since being part of the GitHub organization comes with a set of responsibilities, joining the SCS GitHub Organization can be done by: | ||
|
|
||
| - being invited by the _SCS Project Board_ | ||
| - submitting a request to be onboarded as a member to the _SCS Project Board_ | ||
| - have existing members of the GitHub organization nominate you | ||
|
|
||
| One of these items is sufficient. | ||
|
|
||
| Actively contributing to one or several of the projects under the governance of the SCS project board should typically result in a membership. Please be aware of our [Code of Conduct](https://github.com/SovereignCloudStack/.github/blob/main/CODE_OF_CONDUCT.md). | ||
|
|
||
| ## Election of the _SCS Project Board_ | ||
|
|
||
| ### Term | ||
|
|
||
| The _SCS Project Board_ is elected for the term of one year. Elections are done | ||
| within the last six weeks of the calendar year. | ||
|
|
||
| ### Seats on the board | ||
|
|
||
| The _SCS Project Board_ contains five seats. One of these seats is filled by | ||
| the delegate of the _Forum SCS-Standards_. The other four seats are voted upon. | ||
|
|
||
| ### Nominations | ||
|
|
||
| Every person who is part of the Sovereign Cloud Stack GitHub organization can be | ||
| nominated for the board. Likewise, one can nominate oneself. | ||
| The nomination is done by adding the person with the following data to the file corresponding to the term in the Community-Governance folder in the [Standards](https://github.com/sovereignCloudStack/standards/) repository. Obviously, the person, that is to be nominated, should be asked before being added to the file. | ||
|
|
||
| ### Eligible for voting | ||
|
|
||
| Every person who is a member of the GitHub organization "Sovereign Cloud Stack" is eligible for voting. In order to be able to vote an onboarding onto the Identity Management of the SCS community needs to happen. | ||
|
|
||
| ### Electoral management | ||
|
|
||
| The voting process is governed by the _Forum SCS-Standards_. | ||
| Voting is done using the [Condorcet Internet Voting Service](https://civs.cs.cornell.edu). This is the same system as is [being used by the OpenInfra foundation](https://wiki.openstack.org/wiki/Election_Officiating_Guidelines#Running_the_election_itself). | ||
|
|
||
| ### Voting period | ||
|
|
||
| The voting will be open for a week. | ||
|
|
||
| ### Announcement | ||
|
|
||
| The voting will be announced on the SCS-Members Mailinglist as well as on the [General & Announcements](https://matrix.to/#/#scs-general:matrix.org). Enlisted voters will receive e-mails to the email address used in the SCS community's Identity Management system. | ||
|
|
||
| ### Mechanisms | ||
|
|
||
| Each eligible voter is asked to rank the candidates according to their priorities. | ||
| The four favorite choices among all voters will be elected into the _SCS Project Board_. | ||
|
|
||
| ## Roles in the _SCS Project Board_ | ||
|
|
||
| Among the elected Project Board a spokesperson is nominated. The spokesperson is | ||
| elected by a simple majority vote among the members of the project board. The | ||
| spokesperson is elected for the whole term. | ||
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.