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 for a text on how we make decisions #69

Merged
merged 2 commits into from
Dec 4, 2018
Merged

Conversation

jgbarah
Copy link
Contributor

@jgbarah jgbarah commented Nov 27, 2018

After some discussion in the mailing list (see [1] [2] for conclusions, and whole thread [3] [4] for context), I've drafted this proposal which hopefully captures the result of that discussion.

Any feedback is welcome.

[1] https://lists.linuxfoundation.org/pipermail/chaoss/2018-November/000173.html

[2] https://lists.linuxfoundation.org/pipermail/chaoss/2018-November/000186.html

[4] https://lists.linuxfoundation.org/pipermail/chaoss/2018-November/000157.html

[3] https://lists.linuxfoundation.org/pipermail/chaoss/2018-November/000169.html

After some discussion in the mailing list (see [1] [2] for conclusions, and whole thread [3] [4] for context), I've drafted this proposal which hopefully captures the result of that discussion.

Any feedback is welcome.

[1] https://lists.linuxfoundation.org/pipermail/chaoss/2018-November/000173.html

[2] https://lists.linuxfoundation.org/pipermail/chaoss/2018-November/000186.html

[4] https://lists.linuxfoundation.org/pipermail/chaoss/2018-November/000157.html

[3] https://lists.linuxfoundation.org/pipermail/chaoss/2018-November/000169.html
@geekygirldawn
Copy link
Member

geekygirldawn commented Nov 27, 2018

This is still a bit ambiguous. I would prefer to make it clear that discussions happen in the calls, but that decisions are made on the mailing list.

Maybe a few edits:

  • (line 69)The basic decision-making mechanism for CHAOSS is lazy consensus, which occurs on the relevant mailing list. Each of the software projects or working groups will try to reach consensus on their decisions, after giving a reasonable opportunity to people contributing in them to express their opinion. When a discussion about a decision happens outside of the mailing list in the periodic calls or other communication channels, a proposal for a decision will be sent to the appropriate mailing list(s). The decision should be finalized on the mailing list using lazy consensus after giving people who did not participate in the original discussion time to review, comment, and participate.
  • (line 71) When the issues under discussion are perceived to be of importance to the whole CHAOSS community, the same process will be carried on at the CHAOSS level, using the general periodic calls and other communication means for discussion with the final decision being made on the mailing list using lazy consensus.

…eived

Dawn Foster sent some feedback, which I incorporate here.
@jgbarah
Copy link
Contributor Author

jgbarah commented Nov 27, 2018

Thanks, Dawn. I fully agree, your redaction is much better. I've added it to the pull request.

I've just added a note about lazy consensus, taking the wording from Apache, just to avoid problems if the link stop working for some reason.

@geekygirldawn
Copy link
Member

This looks great, thank you!

Copy link
Member

@GeorgLink GeorgLink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jgbarah

I realize that I rarely give a "defined time window" for lazy consensus - thanks for giving an example at the end.

@jgbarah
Copy link
Contributor Author

jgbarah commented Nov 27, 2018

@GeorgLink, let's thank Apache, I just copied and pasted from their definition, which includes the time frame. And yes, I also think it is a very good idea to specify a reasonable time frame.

@germonprez germonprez merged commit 5777946 into master Dec 4, 2018
@GeorgLink GeorgLink deleted the jgbarah-patch-1 branch March 20, 2019 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants