Happy New Year Everyone!
After some delay[1] replying to comments and making a few dozen changes or
suggestions in the comments of the pull request
<
https://github.com/operate-first/community/pull/107>, we are ready for the
final steps to consensus and ratifying Governance 1.0.
This is mostly self-driven (below) but if one or two of you can help keep
track to make sure we are resolved before 11 January, I would greatly
appreciate it (and have a more restful last week of PTO.)
We are still on track[2] for having 11 January 2022 as the next deadline
for achieving consensus. That means before Tuesday 11 January:
1. We resolve any blockers or open discussions.
- People who need to review and respond: @akrawczy,
@amarrich, @anishasthana, @durandom, @fungi, @jeremyeder, @stefwalter,
@tumido
2. No new blockers are found/created.
3. All discussions are resolved as completed or postponed for the Gov 1.1
discussions.
We currently have the appearance of a consensus draft, meaning we have
achieved or held this state:
- The current draft contains all of the committed fixes or responses raised
so far
- The subsequent commits to PR#107 are viewable in my fork
<
https://github.com/quaid/community/blob/main/governance.md>
- The pull request has my suggestions for changes in response to various
comments, which are ready for the original commenters to review and approve
for committing. There are no blocking (-1) objections raised.
- All of the open comments have been addressed (as commits, as suggested
fixes ready for feedback from the original poster or anyone else, and as
comments.)
Folx listed above with open comments or suggestions to review, please check
your link(s) below :
If the fix I made clearly resolved the issue, I made the commit to the pull
request. In the cases below, I have comments and/or a suggested change for
you to respond to. Leave a comment specifying if my suggestion or response
is good enough, or if more change or response is needed.
@akrawczy
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
@amarrich, @fungi:
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
@anishasthana, @durandom:
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
@jeremyeder:
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
@stefwalter:
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
@tumido:
https://github.com/operate-first/community/pull/107/files/092e770de008cf2...
I will continue to be on vacation until 10 January. Hopefully this round-up
and status is enough for everyone to do their part and things come to a
natural conclusion. It would also be most welcome if one or two of you
stepped up to help get things aligned for an 11 January ratification.
Kind regards,
- Karsten
[1] CW: death and dying
My plans to queue up fixes and replies-to-comments by 18 Dec (for all of
you to review while I began my vacation was shattered by my Father's
hospitalization on 15 Dec and eventual death on 21 Dec 2022 at 79 years
old. We had known since August that Donald Leon Wade had less than a year
to live, and sadly that came to pass on the longest night of the year.
For those who already heard, who sent me support and condolences, who took
a moment to hold us in your thoughts, or to send us our prayers, I thank
you. If anyone wants to reach out, please do so off-list and directly to
me. If you'd like to talk, I welcome that, just contact me directly to get
my number, or dial the digits if you have them.
[2] Proposed timeline:
On Wed, Dec 8, 2021 at 1:10 PM Karsten Wade <kwade(a)redhat.com> wrote:
Hi all,
# Timeline
My proposal is we decide on this governance by consensus, the model for
that is spelled out in the governance.
Because we have no other way to decide things at this point, we are going
to do the strange thing of adopting consensus as the model for this
decision. This means, if you disagree you can try to convince all of us to
use a different decision model. If you agree, you are free to +1 this
section of my email.
08 Dec -- Proposed governance raised
15 Dec -- First call for consensus is made, giving a chance for any
blockers (-1) to be raised
18 Dec -- If consensus is reached, governance is adopted. If there are
blockers, we continue to work through them.
21 Dec -- If we still have blockers and have not reached consensus, then
we hold over to January 2022.
11 Jan -- Second call for consensus is made, regardless of open blockers.
Call for consensus at this point includes if the community is going to
proceed regardless of blockers, or for us to identify which blockers we
want to resolve.
Weekly until closed -- We move through the blockers or decide every week
by consensus to no longer try to work through a blocker.
--
Karsten Wade [he/him/his] | Senior Community Architect | @quaid
Red Hat Open Source Program Office (OSPO) : @redhatopen
The Open Source Way :
https://theopensourceway.org
Operate First :
https://operate-first.cloud