public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: desultory <desultory@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2019-07-21
Date: Fri, 12 Jul 2019 23:28:09 -0400	[thread overview]
Message-ID: <6fda60ea-d54d-161f-dafb-a6a7e81b8ca6@gentoo.org> (raw)
In-Reply-To: <w6gzhlptzf0.fsf@kph.uni-mainz.de>

On 07/07/19 15:30, Ulrich Mueller wrote:
> In two weeks from now, the newly elected Council will have its
> constituent 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 2019-07-14.
> 
> Please reply to the gentoo-project list.
> 
> Ulrich
> 
Since that I was directed to ask the council for their opinion regarding
proctors handling of CoC matters by a member of proctors.

Does the council consider that proctors internally formulating new
policies, issuing a warning for having violated such (still unpublished)
policies, and refusing to reply as a team when asked (by multiple
individuals) to clarify what the new policies in fact were is a suitable
usage of the authority delegated to proctors by the council?


  parent reply	other threads:[~2019-07-13  3:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07 19:30 [gentoo-project] Call for agenda items - Council meeting 2019-07-21 Ulrich Mueller
2019-07-07 20:51 ` Michał Górny
2019-07-07 21:00 ` Michał Górny
2019-07-08  4:43   ` Ulrich Mueller
2019-07-08  5:36     ` Michał Górny
2019-07-08 13:50       ` Rich Freeman
2019-07-09  9:58         ` Ulrich Mueller
2019-07-12 19:56       ` Andreas K. Huettel
2019-07-21  0:22         ` Andrew Savchenko
2019-07-09  9:28   ` Lars Wendler
2019-07-10 13:55     ` William Hubbs
2019-07-10 14:07       ` Michael Everitt
2019-07-10 15:48         ` William Hubbs
2019-07-20 23:57       ` Andrew Savchenko
2019-07-20 23:48   ` Andrew Savchenko
2019-07-21  1:11     ` Raymond Jennings
2019-07-21  6:28     ` Michał Górny
2019-07-21 11:25       ` Andrew Savchenko
2019-07-21 11:52         ` Raymond Jennings
2019-07-21 13:33         ` Michael Orlitzky
2019-07-09  9:02 ` Haelwenn (lanodan) Monnier
2019-07-13  7:39   ` Ulrich Mueller
2019-07-13 10:53     ` Haelwenn (lanodan) Monnier
2019-07-13  3:28 ` desultory [this message]
2019-07-13  4:11   ` Matthew Thode
2019-07-13  6:56   ` Michał Górny
2019-07-13  7:09     ` Ulrich Mueller

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=6fda60ea-d54d-161f-dafb-a6a7e81b8ca6@gentoo.org \
    --to=desultory@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