From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2014-04-08
Date: Sun, 6 Apr 2014 14:34:52 +0200 [thread overview]
Message-ID: <201404061435.00789.dilfridge@gentoo.org> (raw)
In-Reply-To: <53342A5F.70903@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 3174 bytes --]
Am Donnerstag, 27. März 2014, 14:40:47 schrieb Anthony G. Basile:
> Hi everyone,
>
> The council will be meeing on April 8, 2014 at 1900 UTC. Please bring
> forward any agenda items you would like discussed.
>
> --Tony
Here are several resolution drafts which I would like to ask my council
colleagues to vote on. Part of the text is based on suggestions by other
council members.
1) The council strongly disapproves of any developers unilaterally reverting
QA team actions. While the case decision lies with QA and ComRel teams, the
council welcomes the idea of immediate sanctions in such a case. An individual
developer who disagrees with an action made in the name of QA, whether the
action is proper or not, MUST follow the escalation procedures set forth in
GLEP 48, and is encouraged to work with QA, ComRel or eventually the council
to settle any concerns. The council will follow up on any accusations of QA
abuse the same way as on any commit that is in conflict with a QA action.
2) The council recognizes that there are some open questions around when
individuals in QA ought to take action, and how internal disagreements get
resolved. The council would like to ask QA to design its own operating
procedures and publish them. There should be a reasonably clear process so
that QA members can act in the confidence that they are doing things properly,
and the rest of the community can be assured that there is accountability. The
council requests an update on the progress of establishing procedures prior to
its next monthly meeting.
3) The council believes that a wide announcement and if needed discussion of
changes to central parts of Gentoo (as, e.g., system packages, profiles,
global use-flags) should be preferred. In particular, only informing "relevant
people" makes no sense if others will also be affected.
4) While it is any developer's choice not to participate on the gentoo-dev and
gentoo-project mailing lists, they nevertheless serve as main communication
channels. If something has been discussed there, and then action has been
taken, the council regards ignorance of the discussion not as a good
foundation for protests against the actions.
5) The council encourages teams maintaining central parts of Gentoo to accept
new developers as team members and teach them the required knowledge and
intricacies. We consider this important to ensure long-term continuity and
increase the bus factor in critical areas.
Rationale:
about 1)
If a cop pulls you over, you don't beat him up or just drive on. Even if you
think the traffic light was still yellow or even green.
about 3)
Nobody asks for consensus (which we'll never get, I'm being realistic (and it
should be pink with yellow stripes)).
Whether discussion is needed, well if I announce something, either discussion
will follow or not. I've made announcements about the profiles already that
didnt get a single reply. Either noone understood what I was writing, or noone
disagreed...
--
Andreas K. Huettel
Gentoo Linux developer
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2014-04-06 12:35 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 13:40 [gentoo-project] Call for agenda items - Council meeting 2014-04-08 Anthony G. Basile
2014-03-29 12:50 ` Anthony G. Basile
2014-03-29 13:26 ` hasufell
2014-03-29 13:29 ` Anthony G. Basile
2014-03-29 13:49 ` hasufell
2014-03-29 14:17 ` Anthony G. Basile
2014-03-29 13:30 ` Tom Wijsman
2014-03-29 14:07 ` Anthony G. Basile
2014-03-29 14:36 ` William Hubbs
2014-03-29 19:46 ` Rich Freeman
2014-03-29 23:12 ` Andreas K. Huettel
2014-03-30 0:37 ` William Hubbs
2014-03-30 1:35 ` Rich Freeman
2014-03-30 2:20 ` William Hubbs
2014-03-30 2:33 ` Rich Freeman
2014-03-30 11:00 ` Anthony G. Basile
2014-03-30 11:22 ` Tom Wijsman
2014-03-30 11:32 ` Anthony G. Basile
2014-03-30 15:14 ` Tom Wijsman
2014-03-30 13:51 ` Rich Freeman
2014-03-30 12:22 ` hasufell
2014-03-30 15:09 ` Andreas K. Huettel
2014-03-31 16:00 ` Samuli Suominen
2014-03-31 23:46 ` Patrick Lauer
2014-03-30 8:33 ` Michał Górny
2014-03-30 8:43 ` Patrick Lauer
2014-03-30 11:52 ` Michał Górny
2014-03-30 14:07 ` Rich Freeman
2014-03-30 16:05 ` Ulrich Mueller
2014-03-30 16:27 ` Michał Górny
2014-04-01 11:46 ` Ruud Koolen
2014-03-30 9:23 ` Rich Freeman
2014-03-30 13:56 ` Joshua Kinard
2014-03-30 15:47 ` Michał Górny
2014-03-30 23:05 ` Joshua Kinard
2014-03-30 23:43 ` Rich Freeman
2014-03-31 3:13 ` Richard Yao
2014-03-31 6:07 ` Michał Górny
2014-03-31 10:56 ` Joshua Kinard
2014-03-31 15:44 ` Michał Górny
2014-03-31 17:27 ` Rich Freeman
2014-03-31 17:56 ` Ian Stakenvicius
2014-03-31 18:12 ` Douglas James Dunn
2014-04-01 0:20 ` William Hubbs
2014-04-01 6:32 ` Ulrich Mueller
2014-03-31 15:58 ` Brian Dolbec
2014-03-31 16:19 ` [semi-OT] " Andreas K. Huettel
2014-03-30 15:35 ` Ciaran McCreesh
2014-03-30 16:27 ` Rich Freeman
2014-03-30 16:31 ` Ciaran McCreesh
2014-03-30 16:39 ` Rich Freeman
2014-03-30 16:48 ` Ciaran McCreesh
2014-03-30 16:59 ` Rich Freeman
2014-03-30 17:01 ` Rich Freeman
2014-03-30 17:05 ` Ciaran McCreesh
2014-03-30 16:40 ` Rich Freeman
2014-03-30 23:44 ` Douglas James Dunn
2014-03-30 23:54 ` Rich Freeman
2014-03-30 23:59 ` Douglas Dunn
2014-03-31 0:24 ` Douglas Dunn
2014-03-30 23:47 ` Denis Dupeyron
2014-04-06 12:34 ` Andreas K. Huettel [this message]
2014-04-06 12:47 ` hasufell
2014-04-06 12:52 ` Ciaran McCreesh
2014-04-06 12:53 ` hasufell
2014-04-06 15:10 ` Samuli Suominen
2014-04-06 15:29 ` Alexander Berntsen
2014-04-06 16:17 ` Tom Wijsman
2014-04-06 17:01 ` hasufell
2014-04-06 17:03 ` Rich Freeman
2014-04-06 17:22 ` Tom Wijsman
2014-04-06 17:48 ` hasufell
2014-04-06 18:19 ` Tom Wijsman
2014-04-07 15:08 ` hasufell
2014-04-07 16:46 ` Tom Wijsman
2014-04-06 20:02 ` Rick "Zero_Chaos" Farina
2014-04-06 17:02 ` Rich Freeman
2014-04-06 21:22 ` Pacho Ramos
2014-04-07 11:36 ` Tom Wijsman
2014-04-07 11:49 ` Rich Freeman
2014-04-07 12:36 ` Tom Wijsman
2014-04-07 12:44 ` Samuli Suominen
2014-04-07 12:58 ` Tom Wijsman
2014-04-07 13:30 ` Rich Freeman
2014-04-07 15:09 ` Tom Wijsman
2014-04-07 16:36 ` Chris Reffett
2014-04-07 18:25 ` Rich Freeman
2014-04-07 18:45 ` hasufell
2014-04-07 20:06 ` Tom Wijsman
2014-04-07 20:01 ` Pacho Ramos
2014-04-07 14:52 ` Samuli Suominen
2014-04-07 15:30 ` Tom Wijsman
2014-04-06 15:31 ` Jeroen Roovers
2014-04-06 15:30 ` Samuli Suominen
2014-04-06 15:44 ` Ciaran McCreesh
2014-04-06 16:30 ` Tom Wijsman
2014-04-06 16:19 ` Tom Wijsman
2014-04-06 16:09 ` Tom Wijsman
2014-04-06 21:25 ` Joshua Kinard
2014-04-06 21:33 ` Ciaran McCreesh
2014-04-07 8:00 ` Patrick Lauer
2014-04-07 14:51 ` Ciaran McCreesh
2014-04-07 15:38 ` Tom Wijsman
2014-04-07 18:42 ` Joshua Kinard
2014-04-06 17:33 ` Rick "Zero_Chaos" Farina
2014-04-07 5:47 ` Samuli Suominen
2014-04-07 11:51 ` Tom Wijsman
2014-04-07 7:49 ` Patrick Lauer
2014-04-07 8:02 ` Samuli Suominen
2014-04-07 8:26 ` Patrick Lauer
2014-04-07 11:54 ` Samuli Suominen
2014-04-07 12:48 ` Tom Wijsman
2014-04-07 14:49 ` Ciaran McCreesh
2014-04-07 14:58 ` Samuli Suominen
2014-04-07 15:12 ` Ciaran McCreesh
2014-04-08 0:37 ` Patrick Lauer
2014-04-08 4:32 ` Samuli Suominen
2014-04-07 14:53 ` Ciaran McCreesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201404061435.00789.dilfridge@gentoo.org \
--to=dilfridge@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox