public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Agenda for the council meeting 2017-12-10 18:00 UTC
Date: Sat, 9 Dec 2017 23:21:57 +0000	[thread overview]
Message-ID: <robbat2-20171209T225505-275809568Z@orbis-terrarum.net> (raw)
In-Reply-To: <16099994.eYkbcOoAGA@pinacolada>

[-- Attachment #1: Type: text/plain, Size: 2350 bytes --]

I did wish to participate re two items here, but regretfully I will be
travelling at the time, and it's unlikely that I will have connectivity.

On Sat, Dec 09, 2017 at 08:39:54PM +0100, Andreas K. Huettel wrote:
> 3. Final review of GLEP 74 [4,5]
> --------------------------------
> Full-tree verification using Manifest files
The implementation is done, some tweaks were made since the previous
month's version.

> 4. Restricting gentoo-dev/-project posting [6]
> ----------------------------------------------
> * Restricting posting to both gentoo-dev and gentoo-project, while creating a 
>   gentoo-experts list?
> * Restricting posting to gentoo-dev and moving all official business there?
> * Restricting posting to gentoo-dev and moving all official business to a 
>   revived restricted gentoo-council list?
> * Moderating lists instead?
I had not weighed in publicly on this before, but wish to make a
statement.
The original split of gentoo-dev to gentoo-project included
moderation of gentoo-dev, however that was never really implemented,
mostly for technical reasons, and a decreased need after the split.

I oppose a further split of -dev/-project/-experts, and instead
propose better list policies of -dev. If it's technical, even coming
from an expert user, it probably belongs on -dev. If it's about the
organizational structures of Gentoo, it belongs on -project.
How do we keep the threads more on-topic? Moderation maybe, but I'm
not convinced that is best.

mlmmj, the list manager app that has powered the lists since 2004/Oct/28
has served us well. However, it needs to be replaced.  Upstream progress
has stalled, and the codebase is not trivial to improve. It lacked
features that are ever more relevant (spam, real moderation,
web-interfaces).

Mailman is my leading replacement candidate, as they have resolved many
of the issues that prevented it's choice ~13 years ago (mostly around
Unicode). It would give improved moderation & subscription control,
amongst other improvements. Also in Python3 rather than the unique style
of C used by mlmmj.

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Asst. Treasurer
E-Mail   : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]

  reply	other threads:[~2017-12-09 23:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-09 19:39 [gentoo-project] Agenda for the council meeting 2017-12-10 18:00 UTC Andreas K. Huettel
2017-12-09 23:21 ` Robin H. Johnson [this message]
2017-12-09 23:41   ` Andreas K. Huettel
2017-12-10  7:25   ` Brian Dolbec
2017-12-10  7:54     ` Alice Ferrazzi
2017-12-10  8:17     ` Hans de Graaff
2017-12-10  8:29     ` Michał Górny
2017-12-10 15:24       ` Brian Dolbec

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=robbat2-20171209T225505-275809568Z@orbis-terrarum.net \
    --to=robbat2@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