From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2018-07-29
Date: Sat, 14 Jul 2018 22:50:31 +0200 [thread overview]
Message-ID: <1531601431.1025.13.camel@gentoo.org> (raw)
In-Reply-To: <20180714192940.uctz43livjvxhyxj@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
W dniu sob, 14.07.2018 o godzinie 14∶29 -0500, użytkownik Matthew Thode
napisał:
> On 18-07-14 21:10:11, Michał Górny wrote:
> > W dniu sob, 14.07.2018 o godzinie 18∶21 +0200, użytkownik Manuel Rüger
> > napisał:
> > > On 13.07.2018 10:37, Ulrich Mueller wrote:
> > > > In two weeks from now, the newly elected council will have its first
> > > > meeting. This is the time to raise and prepare items that the council
> > > > should put on the agenda to discuss or vote on.
> > > >
> > > > Please respond to this message with agenda items. Do not hesitate
> > > > to repeat your agenda item here with a pointer if you previously
> > > > suggested one (since the last meeting).
> > > >
> > > > The agenda for the meeting will be sent out on Sunday 2018-07-22.
> > > >
> > > > Please reply to the gentoo-project list.
> > > >
> > > > Ulrich
> > > >
> > >
> > > As the council represents the Gentoo Developer community, the council
> > > members should behave as role models for this community.
> > >
> > > I would like each council member to explicitly state their agreement to
> > > our Code of Conduct.
> > > https://wiki.gentoo.org/wiki/Project:Council/Code_of_conduct
> >
> > The request for the new Council members to reiterate their
> > acknowledgement of Code of Conduct -- which they obviously implicitly
> > agreed to -- sounds like a serious implicit accusation. Isn't making
> > such an accusation a violation of Code of Conduct itself though?
> >
>
> I don't think of it as an accusation, more of a 'swearing in' as they
> are moving into a new office.
>
Having more context to this than you do, I think it's an elaborate
scheme of petty vengeance. Thus, it's doubly offensive since Council is
being used here as a tool to developer's private vendetta.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2018-07-14 20:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 8:37 [gentoo-project] Call for agenda items - Council meeting 2018-07-29 Ulrich Mueller
2018-07-13 9:48 ` Michał Górny
2018-07-13 13:57 ` Brian Dolbec
2018-07-13 17:50 ` Ulrich Mueller
2018-07-13 17:59 ` Kristian Fiskerstrand
2018-07-13 18:12 ` Ulrich Mueller
2018-07-13 18:19 ` Raymond Jennings
2018-07-13 18:25 ` M. J. Everitt
2018-07-13 18:28 ` M. J. Everitt
2018-07-13 18:43 ` Rich Freeman
2018-07-13 19:20 ` Ulrich Mueller
2018-07-13 19:33 ` Alec Warner
2018-07-13 19:41 ` Rich Freeman
2018-07-13 20:24 ` Ulrich Mueller
2018-07-13 19:51 ` Michał Górny
2018-07-14 3:23 ` Brian Dolbec
2018-07-14 16:21 ` Manuel Rüger
2018-07-14 17:33 ` William Hubbs
2018-07-14 17:47 ` Manuel Rüger
2018-07-14 18:06 ` William Hubbs
2018-07-14 18:38 ` Ulrich Mueller
2018-07-14 18:49 ` Manuel Rüger
2018-07-14 20:37 ` William Hubbs
2018-07-15 13:17 ` Kristian Fiskerstrand
2018-07-14 19:10 ` Michał Górny
2018-07-14 19:29 ` Matthew Thode
2018-07-14 20:50 ` Michał Górny [this message]
2018-07-14 21:15 ` Manuel Rüger
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=1531601431.1025.13.camel@gentoo.org \
--to=mgorny@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