Skip to content

docs(governance): reflect the real status of the procedure and roles #287

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.

Sign up for GitHub

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

Open
bfabio wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −11
Open

docs(governance): reflect the real status of the procedure and roles #287

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 0 additions & 8 deletions governance/charter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,14 +30,6 @@ level.

# Roles and duties

### Chair ([@ruphy](https://github.com/ruphy))

* Plans, organizes agenda and moderates meetings
* Prepares and shares milestones and deadlines
* Oversees the voting procedure
* Is the ultimate responsible for the development of the project
* Has administrative access on GitHub and other platforms

### Maintainer ([@bfabio](https://github.com/bfabio), [@sebbalex](https://github.com/sebbalex))

* Maintains the non-Standard side of repositories
Expand Down
6 changes: 3 additions & 3 deletions governance/procedure-proposing-changes-and-voting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@ participation from everyone but restrict the voting to public servants, for this
only open to members of the [Steering Committee](charter.md#steering-commitee-publiccodeymlsteering-committee),
typically one per country.

[The Chair](charter.md#roles-and-duties) of the Steering committee is responsible for holding a
regular vote, which happens as deemed necessary. Once the voting starts, it stays open for a week.
Votes are held following an [experimental cadence defined here](https://github.com/publiccodeyml/publiccode.yml/discussions/228#discussioncomment-14314999).
Once a vote opens, it remains open for two weeks.

Voting happens on formal proposals opened as Pull Requests through expressing a clear intention to
*approve*, *reject*, or *abstain*. This can be done by either using GitHub's code review feature,
Expand Down Expand Up @@ -65,7 +65,7 @@ so.

### Results of the vote and implementation of the changes

After a week from the vote has passed, the Chair formally announces the results.
After the voting session ends, the results are announced.

The Maintainers act accordingly to reflect the changes on GitHub and proceed to queue the changes in
the next release cycle.
Expand Down