Fedora Atomic WG Meeting Minutes 2017-12-13
by Jason Brooks
logs: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-12-13/fedora_atom...
#fedora-meeting-1: fedora_atomic_wg
Meeting started by jbrooks at 16:30:03 UTC (full logs).
Meeting summary
roll call (jbrooks, 16:30:08)
action items from last meeting (jbrooks, 16:34:40)
https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraprojec...
(jbrooks, 16:38:03)
ACTION: maxamillion to confirm and close #376 (jbrooks, 16:41:34)
meeting tickets (jbrooks, 16:42:03)
377 - Voting Process (jbrooks, 16:42:46)
https://pagure.io/atomic-wg/issue/377 (jbrooks, 16:42:55)
363 Quorum Rules (jbrooks, 16:44:19)
https://pagure.io/atomic-wg/issue/363 (ashcrow, 16:44:23)
ACTION: jberkus to post a revised quorum proposal (jbrooks, 16:45:44)
360 - Decide strategy for including container runtimes in Atomic Host
(jbrooks, 16:46:11)
https://pagure.io/atomic-wg/issue/360 (jbrooks, 16:46:20)
Open Floor (jbrooks, 16:48:16)
Sent PR for updating cloud-utils package in Fedora to 0.30 -
https://src.fedoraproject.org/rpms/cloud-utils/pull-request/1 (ksinny,
16:48:54)
Sent PR for adding a post on Composing custom OSTree update for Fedora
27 atomic Host on projectatomic blog -
https://github.com/projectatomic/atomic-site/pull/496(ksinny,
17:01:10)
ACTION: cverna to talk to releng about doing a container release since
we just released FAH (dustymabe, 17:09:40)
https://dustymabe.com/2017/08/29/atomic-host-101-lab-part-0-preparation/
(dustymabe, 17:12:21)
https://github.com/projectatomic/atomic-site/pull/496 (dustymabe, 17:14:35)
ACTION: jberkus to review/merge the PR to update official docs from
f25 to f27 (dustymabe, 17:14:58)
Meeting ended at 17:17:10 UTC (full logs).
6 years, 4 months
[atomic-wg] Issue #377: Idea: Voting Process
by Steve Milner
smilner reported a new issue against the project: `atomic-wg` that you are following:
``
When the group can not come to a 100% (or whatever percentage is deemed enough) consensus we could have an in chat +1/-1 vote called by the meeting leader. This could be for anything from continuing a discussion on a topic, to moving the conversation to pagure, to making a decision in the meeting. If the +1/-1 result ends in a positive integer then the proposal passes.
* +1, -1, +1, +1 = 2 == PASS
* +1, -1, +1, -1 = 0 == FAIL
* -1, -1, +1, -1 = -1 == FAIL
Calling a vote would be at the discretion of the meeting leader and should generally called when:
* A clear decision is required
* The conversation is not leading to a conclusion/actionable result
* A barometer of the room on a topic is needed
If an item **requires** an outcome yet the team is unable to agree on one via the voting process the issue would then be escalated to the proper Fedora committee/working group.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/377
6 years, 4 months