Editing Parliamentary Procedures
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
ADOPTED BY the Governance Working Group on 27 Jan 2022 | ADOPTED BY the Governance Working Group on 27 Jan 2022 | ||
Current as of 27 Jan 2022 | |||
0L follows a light, informal set of parliamentary procedures designed to assure that the will of the community is reflected in decisions and that the rights of minority groups and absent individuals are preserved. The rules have been chosen to streamline processes and not create an overly burdensome standard for running meetings and advancing initiatives. These rules are subject to revision and are maintained by the Governance Working Group. | 0L follows a light, informal set of parliamentary procedures designed to assure that the will of the community is reflected in decisions and that the rights of minority groups and absent individuals are preserved. The rules have been chosen to streamline processes and not create an overly burdensome standard for running meetings and advancing initiatives. These rules are subject to revision and are maintained by the Governance Working Group. | ||
# Agendas | |||
# Meeting agendas are intended to be flexible, without required notice or publication periods. Ideally, agendas will be publicized in advance for the benefit of attracting attendees and providing the basics needed for an informed discussion. | ## Meeting agendas are intended to be flexible, without required notice or publication periods. Ideally, agendas will be publicized in advance for the benefit of attracting attendees and providing the basics needed for an informed discussion. | ||
# Creation of Working Group agendas is the responsibility of the working group’s Coordinator, but this may be delegated. | ## Creation of Working Group agendas is the responsibility of the working group’s Coordinator, but this may be delegated. | ||
# Quorum | |||
## A meeting is said to have quorum when at least 3 persons are in attendance, of whom at least two hold key roles (i.e., Coordinator, Broker, Archivist) | |||
# A meeting is said to have quorum when at least 3 persons are in attendance, of whom at least two hold key roles (i.e., Coordinator, Broker, Archivist) | ## No official business can be transacted in the absence of a quorum, and the meeting notes should simply indicate who was in attendance and that quorum was not achieved. | ||
# No official business can be transacted in the absence of a quorum, and the meeting notes should simply indicate who was in attendance and that quorum was not achieved. | # Facilitation | ||
## Working Group meetings are facilitated by the working group’s Coordinator. The Archivist is empowered to chair the meeting in the absence of the Coordinator. | |||
## General Community Meetings are led by volunteers from the community. | |||
# Working Group meetings are facilitated by the working group’s Coordinator. The Archivist is empowered to chair the meeting in the absence of the Coordinator. | # Meeting Minutes | ||
# General Community Meetings are led by volunteers from the community. | ## Working Groups are required to keep minutes of all meetings, including who was present for the meeting. | ||
### Note that “present” is somewhat discretionary. As a guideline, if a person is in the meeting for at least 50% of the session they should be considered present. | |||
### The Archivist has reasonable latitude to vary from this, and an exact measure is not required. The decision of the archivist is final. | |||
# Working Groups are required to keep minutes of all meetings, including who was present for the meeting. | ## The working group Archivist is charged with transcribing the minutes and posting them publicly for the community. | ||
## Note that “present” is somewhat discretionary. As a guideline, if a person is in the meeting for at least 50% of the session they should be considered present. | ### In the event the Archivist is not able to perform this function, this duty must be delegated and completed. | ||
## The Archivist has reasonable latitude to vary from this, and an exact measure is not required. The decision of the archivist is final. | ## Audio & Video | ||
# The working group Archivist is charged with transcribing the minutes and posting them publicly for the community. | ### Audio or video recordings of meetings can substitute for written minutes, but must be posted in a publicly accessible location. | ||
## In the event the Archivist is not able to perform this function, this duty must be delegated and completed. | ### Weekly Community (and other large scale) Meetings should be recorded and published to the 0L YouTube channel | ||
# Audio & Video | ### The use of audio and video recordings has privacy implications, and the person doing the recording must disclose the recording at the beginning of the session and ask if there are any objections. If there is an objection, there will be no recording. | ||
## Audio or video recordings of meetings can substitute for written minutes, but must be posted in a publicly accessible location. | ## If written minutes are used, the minutes are considered to be final, and not subject to revision, if no one voices objection to the published minutes within 2 days of publication of the minutes by the Archivist. | ||
## Weekly Community (and other large scale) Meetings should be recorded and published to the 0L YouTube channel | ## When a vote is taken, the minutes must record | ||
## The use of audio and video recordings has privacy implications, and the person doing the recording must disclose the recording at the beginning of the session and ask if there are any objections. If there is an objection, there will be no recording. | ### The outcome, including number of voted for, against, and abstentions (see, Sec. 5.6) | ||
# If written minutes are used, the minutes are considered to be final, and not subject to revision, if no one voices objection to the published minutes within 2 days of publication of the minutes by the Archivist. | ### Who, if any, voted against the proposal and, (see, Sec. 5.7) | ||
# When a vote is taken, the minutes must record | ### Who, if any, abstained. (see, Sec. 5.7) | ||
## The outcome, including number of voted for, against, and abstentions (see, Sec. 5.6) | ## When a proxy is exercised, the details must be recorded in the minutes. (see, sec. 5.3.4.2) | ||
## Who, if any, voted against the proposal and, (see, Sec. 5.7) | ## In the absence of a quorum, the meeting minutes need to reflect only that | ||
## Who, if any, abstained. (see, Sec. 5.7) | ### Quorum was not achieved, and | ||
# When a proxy is exercised, the details must be recorded in the minutes. (see, sec. 5.3.4.2) | ### Who was present (see, Sec. 2.2) | ||
# In the absence of a quorum, the meeting minutes need to reflect only that | # Working Group Voting Process (*Interim Process) | ||
## Quorum was not achieved, and | ## While the eventual goal is to manage all voting on-chain, until those mechanisms are adopted, all votes shall be manually recorded and documented in the relevant meeting minutes | ||
## Who was present (see, Sec. 2.2) | ## Process/Steps for voting on a proposal inside a working group: | ||
### Proposal is explained | |||
### Motion is made | |||
# While the eventual goal is to manage all voting on-chain, until those mechanisms are adopted, all votes shall be manually recorded and documented in the relevant meeting minutes | ### Motion is seconded | ||
# Process/Steps for voting on a proposal inside a working group: | ### Discussion/Debate | ||
## Proposal is explained | ### Discussion closed | ||
## Motion is made | ### Simple Yes/No vote of those present | ||
## Motion is seconded | ### Result of vote recorded clearly in the minutes (see, Sec. 4.5 & 4.6) | ||
## Discussion/Debate | ## Eligibility to vote | ||
## Discussion closed | ### Eligibility is based on presence and participation; to have an informed opinion on the matters under consideration requires familiarity with the issues and the context. | ||
## Simple Yes/No vote of those present | ### Anyone who has attended at least 2 of the previous 4 meetings of the working group is permitted to vote in the working group. | ||
## Result of vote recorded clearly in the minutes (see, Sec. 4.5 & 4.6) | #### Attendance will be verified by reference to the minutes. | ||
# Eligibility to vote | ### Anyone who is deemed to be an active member of the project is permitted to vote in the working group, where active member is defined as someone who has contributed in a meaningful fashion to the task or proposal under vote. | ||
## Eligibility is based on presence and participation; to have an informed opinion on the matters under consideration requires familiarity with the issues and the context. | #### The Broker and the Coordinator of the group where the vote is occurring are vested with discretion to determine whether an individual is an active member for purposes of this section. | ||
## Anyone who has attended at least 2 of the previous 4 meetings of the working group is permitted to vote in the working group. | #### In the event of a disagreement between the Broker and the Coordinator, the Archivist will provide the decision. | ||
### Attendance will be verified by reference to the minutes. | ### Exceptions | ||
## Anyone who is deemed to be an active member of the project is permitted to vote in the working group, where active member is defined as someone who has contributed in a meaningful fashion to the task or proposal under vote. | #### Coordinators’ Working Group: Only Coordinators are permitted to vote on matters within that working group. | ||
### The Broker and the Coordinator of the group where the vote is occurring are vested with discretion to determine whether an individual is an active member for purposes of this section. | #### Anyone holding one of the key roles in a working group (i.e., Coordinator, Broker, Archivist) can always vote in the group where they hold the role. | ||
### In the event of a disagreement between the Broker and the Coordinator, the Archivist will provide the decision. | ### Proxies | ||
## Exceptions | #### Proxy voting is permitted. | ||
### Coordinators’ Working Group: Only Coordinators are permitted to vote on matters within that working group. | #### To give a proxy, a person must notify the working group of their intention by posting in the working group’s Discord channel in advance of the meeting, describing the proxy, who it is given to, and what is in scope. | ||
### Anyone holding one of the key roles in a working group (i.e., Coordinator, Broker, Archivist) can always vote in the group where they hold the role. | #### When a proxy is exercised in a vote, the meeting minutes must record who exercised the proxy vote, who assigned the proxy to that person, and the vote that was cast. | ||
## Proxies | #### Proxies must be specific to the matter under vote; not a general grant of authority to act. | ||
### Proxy voting is permitted. | ## Most matters require a simple majority (51% or greater) of those present during the meeting. | ||
### To give a proxy, a person must notify the working group of their intention by posting in the working group’s Discord channel in advance of the meeting, describing the proxy, who it is given to, and what is in scope. | ## No specific notice period is required prior to a vote. | ||
### When a proxy is exercised in a vote, the meeting minutes must record who exercised the proxy vote, who assigned the proxy to that person, and the vote that was cast. | ### An exception to this rule will be made where at least 2 members of the working group request a notice period, in which case the matter will be published to the working group’s Discord channel for a period of not less than 5 days. | ||
### Proxies must be specific to the matter under vote; not a general grant of authority to act. | ## Election of the Key Roles (i.e., Coordinator, Broker, Archivist) requires a three-fifths supermajority (60% or greater). | ||
# Most matters require a simple majority (51% or greater) of those present during the meeting. | ### If no candidate receives the required percentage, the field of candidates will be reduced to the 2 individuals that received the largest numbers of votes and the vote repeated. For this “runoff election” the candidate who receives a simple majority will be the winner. | ||
# No specific notice period is required prior to a vote. | ## All votes are executed by either voice or roll call, and the outcome shall be reported in the minutes. | ||
## An exception to this rule will be made where at least 2 members of the working group request a notice period, in which case the matter will be published to the working group’s Discord channel for a period of not less than 5 days. | ## The meeting minutes should indicate who, if anyone, voted against the proposal or abstained from the vote. | ||
# Election of the Key Roles (i.e., Coordinator, Broker, Archivist) requires a three-fifths supermajority (60% or greater). | # Protocol Voting Process | ||
## If no candidate receives the required percentage, the field of candidates will be reduced to the 2 individuals that received the largest numbers of votes and the vote repeated. For this “runoff election” the candidate who receives a simple majority will be the winner. | ## Voting on proposals related to the 0L protocol are cast on-chain by the Validator operators. | ||
# All votes are executed by either voice or roll call, and the outcome shall be reported in the minutes. | ## Proposals requiring a vote must be posted in the appropriate Discord channels. | ||
# The meeting minutes should indicate who, if anyone, voted against the proposal or abstained from the vote. | ## The voting period for any proposals shall be | ||
### Not less than 7 days except for | |||
### Urgent matters, e.g., security patches or incident response, which may require a shorter period | |||
# Voting on proposals related to the 0L protocol are cast on-chain by the Validator operators. | ## All proposals are passed with a two-thirds super majority (67%) of the active validators. | ||
# Proposals requiring a vote must be posted in the appropriate Discord channels. | # Community-wide Voting (*Interim Process) | ||
# The voting period for any proposals shall be | ## While the eventual goal is to manage all voting on-chain, until those mechanisms are adopted, proposals that require broader community participation will follow the process outlined in this section. | ||
## Not less than 7 days except for | ## Only working groups may sponsor a proposal for a community-wide vote. | ||
## Urgent matters, e.g., security patches or incident response, which may require a shorter period | ### Individuals wishing to put a proposal to community vote should engage with a relevant working group and petition that working group to sponsor the proposal. | ||
# All proposals are passed with a two-thirds super majority (67%) of the active validators. | ## Once a working group votes to sponsor a proposal, the proposal will be added to GitHub and it will be posted to the #community-proposals-for-review channel in Discord for a period of public review and comment. | ||
### | |||
### Sponsored proposals must be discussed at the next weekly community mtg (someone from the sponsoring working group should present the proposal to the community). | |||
# While the eventual goal is to manage all voting on-chain, until those mechanisms are adopted, proposals that require broader community participation will follow the process outlined in this section. | ### After the presentation to the community, the proposal must remain visible on the relevant Discord channel for no less than 2 days, and no more than 5 days. | ||
# Only working groups may sponsor a proposal for a community-wide vote. | ### Proposals must be open for comment. | ||
## Individuals wishing to put a proposal to community vote should engage with a relevant working group and petition that working group to sponsor the proposal. | ### If, during the comment period, at least 5 persons interact with the post (i.e., by leaving either a comment or an emoji), the proposal is advanced to the Coordinators’ Working Group. | ||
# Once a working group votes to sponsor a proposal, the proposal will be added to GitHub and it will be posted to the #community-proposals-for-review channel in Discord for a period of public review and comment. | ### If a proposal fails to gain 5 interactions after a period of 5 days, it is sent back to the sponsoring working group. | ||
## | #### If a proposal is sent back to a working group, the group may again vote to sponsor it and the process repeats | ||
## Sponsored proposals must be discussed at the next weekly community mtg (someone from the sponsoring working group should present the proposal to the community). | ## The Coordinators’ Working Group must perform at least one of these actions: | ||
## After the presentation to the community, the proposal must remain visible on the relevant Discord channel for no less than 2 days, and no more than 5 days. | ### Send the proposal back to the working group that sponsored it for revision (note: the typical response when the feedback was negative in whole or part), | ||
## Proposals must be open for comment. | #### If a proposal is sent back to a working group, the group may choose to modify it and vote again to sponsor it, in which case the process in Sec. 7.3 repeats | ||
## If, during the comment period, at least 5 persons interact with the post (i.e., by leaving either a comment or an emoji), the proposal is advanced to the Coordinators’ Working Group. | ### Schedule further discussion of the proposal (note: this is the recommended precursor to a vote), | ||
## If a proposal fails to gain 5 interactions after a period of 5 days, it is sent back to the sponsoring working group. | ### Schedule a vote on the proposal. | ||
### If a proposal is sent back to a working group, the group may again vote to sponsor it and the process repeats | ### Should the Coordinators’ Working Group be faced with multiple proposals, the group has the discretion to sequence the voting in such manner as they see fit to best advance the needs of the community. | ||
# The Coordinators’ Working Group must perform at least one of these actions: | ## Eligibility and process for casting community-wide votes is TBD | ||
## Send the proposal back to the working group that sponsored it for revision (note: the typical response when the feedback was negative in whole or part), | |||
### If a proposal is sent back to a working group, the group may choose to modify it and vote again to sponsor it, in which case the process in Sec. 7.3 repeats | |||
## Schedule further discussion of the proposal (note: this is the recommended precursor to a vote), | |||
## Schedule a vote on the proposal. | |||
## Should the Coordinators’ Working Group be faced with multiple proposals, the group has the discretion to sequence the voting in such manner as they see fit to best advance the needs of the community. | |||
# Eligibility and process for casting community-wide votes is TBD | |||