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

Juried Application of the 'Has Consensus' Label #57

Open
qwertyone opened this issue Jan 25, 2018 · 3 comments
Open

Juried Application of the 'Has Consensus' Label #57

qwertyone opened this issue Jan 25, 2018 · 3 comments

Comments

@qwertyone
Copy link
Contributor

The Problem

Label Management is a key component of managing the process for the group. However, it is too open for individual members to tag proposals with important governance state labels. As a matter of governance, the 'Has Consensus' tag clearly indicates the following:

  • time for the open review of a written proposal has been provided for useful and specific feedback
  • a group of people from the collective have read and reviewed the proposal during a regular governance meeting Weekly meeting procedure for goverenace  #47
  • comments are reviewed during this meeting for merit and discussion
  • questions are raised occur during this meeting
  • that the actions written in the proposal are to be carried further upon acceptance
  • further changes to the proposal are written with a new proposal to carry things forward

Considering these 6 facts, this label plays an important role and should be restricted in use. No single person should have the ability to either undo or apply this label except after this regularly occurring open meeting that has been set aside for this purpose.

Group proposal

The application of the 'has consensus' occurs immediately after the proposal review during the regular governance meeting, in the presence of members from the collective. The tag is specifically applied by the person charged with the review meeting, not a role.

This wording will be introduced into the proposal process outline at the end of the next consensus period. Remedies to address such behavior outside of the normal flow will be discussed further and introduced into the Code of Conduct.

Implications

Better management of the group governance process is an immediate benefit whereby individuals do not undermine the momentum of the group through time consumption strategies. More proposals shall be closed as a result and future efforts can be traced to the evolution of work already performed.

Additionally, most likely the result of miscommunications and misunderstandings, conflicts of opinions and approaches between members will be prevented with the strict control of access of this particular tag. It removes the ability of individuals having the ability to meddle in regular flow of the larger group's agreed-to procedures and prevents future false accusations.


Use comments to share your response or use emoji 👍 to show your support. To officially join in, add yourself as an assignee to the proposal. To break consensus, comment using this template. To find out more about this process, read the how-to.

@qwertyone qwertyone self-assigned this Jan 25, 2018
@neilthemathguy
Copy link

neilthemathguy commented Jan 31, 2018

As per title Juried Application of the 'Has Consensus', could you complete the proposal description with section Person or People Who Added the Proposal to GitHub It would be helpful to list the members that comprises the jury.

Thanks!

@markwhiting
Copy link
Member

More information remains unofficial, and hence does not hold up consensus. You're welcome to revise this over the next 24.

@neilthemathguy
Copy link

Thanks. Do you know who are the group members official/unofficial associated with this proposal?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants