From: Nils Freydank <holgersson@posteo.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] [RFC] Splitting developer-oriented and expert user mailing lists
Date: Tue, 05 Dec 2017 12:05:02 +0100 [thread overview]
Message-ID: <28538350.vs65LcvSRA@pygoscelis> (raw)
In-Reply-To: <1512406941.2112.4.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Am Montag, 4. Dezember 2017, 18:02:21 CET schrieb Michał Górny:
> W dniu pon, 04.12.2017 o godzinie 14∶18 +0100, użytkownik Dirkjan
>
> Ochtman napisał:
> > On Sun, Dec 3, 2017 at 10:43 PM, Michał Górny <mgorny@gentoo.org> wrote:
> [...]
>
> I'm all for it, as long as someone is actually going to do the necessary
> work within the next, say, 4 weeks. I'd really like to avoid once again
> having no resolution whatsoever just to wait for never-to-come upgrade.
>
> I should point out that this includes:
> [...]
> 2. Establishing a clear policy on how moderation should be performed.
> Without a clear policy, the effects could be far worse than status quo.
I’m working on a draft for a ruleset and will send it to the list (as a new
thread). However, this may take until the end of this week.
> 3. Establishing a good and trusted moderators team. Normally I'd say
> ComRel could do that but given their inability to react within the last
> year...
>
> So, anyone volunteering to do the work?
I would do it, but IMHO it’s inappropriate if I would do that as a non-dev/
normal user.
--
GPG fingerprint: '766B 8122 1342 6912 3401 492A 8B54 D7A3 FF3C DB17'
Holgersson
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-05 11:05 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 23:18 [gentoo-dev] [RFC] Splitting developer-oriented and expert user mailing lists Michał Górny
2017-12-03 1:33 ` R0b0t1
2017-12-03 22:03 ` Michał Górny
2017-12-04 5:59 ` R0b0t1
2017-12-04 17:28 ` Michał Górny
2017-12-06 7:42 ` R0b0t1
2017-12-03 18:01 ` kuzetsa
2017-12-03 18:34 ` Vincent-Xavier JUMEL
2017-12-03 21:31 ` Michał Górny
2017-12-04 20:29 ` Vincent-Xavier JUMEL
2017-12-04 21:21 ` William L. Thomson Jr.
2017-12-03 18:52 ` Alec Warner
2017-12-03 21:26 ` Michał Górny
2017-12-04 1:25 ` [gentoo-project] " Alec Warner
2017-12-03 19:19 ` Róbert Čerňanský
2017-12-03 21:35 ` Michał Górny
2017-12-04 18:11 ` Christopher Head
2017-12-04 18:34 ` kuzetsa
2017-12-04 19:31 ` Róbert Čerňanský
2017-12-03 20:30 ` Dirkjan Ochtman
2017-12-03 21:29 ` William Hubbs
2017-12-03 21:43 ` [gentoo-project] " Michał Górny
2017-12-03 22:33 ` Gerion Entrup
2017-12-03 23:23 ` Richard Bradfield
2017-12-04 13:18 ` [gentoo-project] " Dirkjan Ochtman
2017-12-04 17:02 ` Michał Górny
2017-12-05 11:05 ` Nils Freydank [this message]
2017-12-03 21:16 ` Damo Brisbane
2017-12-03 21:22 ` Damo Brisbane
2017-12-03 22:06 ` [gentoo-dev] Re: [gentoo-project] " Matt Turner
2017-12-04 17:05 ` Michał Górny
2017-12-04 0:37 ` Matt Turner
2017-12-04 0:51 ` Rich Freeman
2017-12-04 1:19 ` kuzetsa
2017-12-04 13:15 ` M. J. Everitt
2017-12-04 18:51 ` William L. Thomson Jr.
2017-12-04 18:57 ` kuzetsa
2017-12-04 19:19 ` William L. Thomson Jr.
2017-12-06 6:35 ` R0b0t1
2017-12-04 19:17 ` Alec Warner
2017-12-04 19:37 ` William L. Thomson Jr.
2017-12-04 19:54 ` Alec Warner
2017-12-04 21:08 ` William L. Thomson Jr.
2017-12-04 21:36 ` OT " William L. Thomson Jr.
2017-12-04 21:39 ` Kristian Fiskerstrand
2017-12-07 18:06 ` William L. Thomson Jr.
2017-12-08 20:22 ` That's all folks. (Re: OT Re: [gentoo-dev] Re: [gentoo-project] [RFC] Splitting developer-oriented and expert user mailing lists) Andreas K. Huettel
2017-12-08 20:30 ` Peter Stuge
2017-12-08 20:43 ` Gordon Pettey
2017-12-08 20:46 ` Alexander Berntsen
2017-12-10 0:29 ` Daniel Campbell
2017-12-10 1:13 ` Rich Freeman
2017-12-10 4:31 ` Daniel Campbell
2017-12-10 14:55 ` Rich Freeman
2017-12-10 8:21 ` Michał Górny
2017-12-10 8:24 ` R0b0t1
2017-12-10 19:54 ` kuzetsa
2018-02-11 19:42 ` Matthew Thode
2017-12-11 10:30 ` Andrew Savchenko
2017-12-08 7:43 ` OT Re: [gentoo-dev] Re: [gentoo-project] [RFC] Splitting developer-oriented and expert user mailing lists R0b0t1
2017-12-09 1:20 ` Georg Rudoy
2017-12-09 1:57 ` R0b0t1
2017-12-09 2:18 ` R0b0t1
2017-12-04 20:15 ` Ulrich Mueller
2017-12-04 1:07 ` [gentoo-dev] " kuzetsa
2017-12-04 1:19 ` Peter Stuge
2017-12-04 2:56 ` kuzetsa
2017-12-04 6:02 ` R0b0t1
2017-12-04 20:30 ` Daniel Campbell
2017-12-05 8:59 ` Peter Stuge
2017-12-05 21:16 ` Daniel Campbell
2017-12-05 22:12 ` Rich Freeman
2017-12-05 22:19 ` Kristian Fiskerstrand
2017-12-05 22:25 ` Rich Freeman
2017-12-05 22:27 ` Kristian Fiskerstrand
2017-12-05 22:37 ` Rich Freeman
2017-12-05 22:41 ` Kristian Fiskerstrand
2017-12-05 23:01 ` Kristian Fiskerstrand
2017-12-05 23:14 ` [gentoo-project] " Rich Freeman
2017-12-05 23:12 ` Rich Freeman
2017-12-06 12:16 ` kuzetsa
2017-12-05 22:46 ` William L. Thomson Jr.
2017-12-05 23:02 ` Rich Freeman
2017-12-05 23:22 ` William L. Thomson Jr.
2017-12-05 23:25 ` Kristian Fiskerstrand
2017-12-05 23:40 ` William L. Thomson Jr.
2017-12-06 8:51 ` Andreas K. Huettel
2017-12-06 17:44 ` William L. Thomson Jr.
2017-12-07 2:48 ` R0b0t1
2017-12-05 23:34 ` William L. Thomson Jr.
2017-12-06 7:22 ` R0b0t1
2017-12-06 13:04 ` Rich Freeman
2017-12-07 2:36 ` R0b0t1
2017-12-04 23:58 ` kuzetsa
2017-12-05 21:53 ` Aaron W. Swenson
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=28538350.vs65LcvSRA@pygoscelis \
--to=holgersson@posteo.de \
--cc=gentoo-dev@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