Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2015-10-11

["Andreas K. Huettel" <dilfridge@gentoo.org>]

Am Mittwoch, 30. September 2015, 20:15:37 schrieb Michał Górny:
> 
> I would like to get a final decision/vote on what to do about projects,
> herds, etc. and the relevant metadata.

Here's my alternative proposal how to solve this. It takes a slightly more 
radical approach and tries to replace the old mess not with a newer mess but 
with a true simplification. Expanded from [1].

a) Remove the word "herd" from docs and specifications.

b) Package is "in herd" -> package is "maintained by project"

c) In metadata.xml, replace <herd>x<herd>  ->  <project>y<project>
This needs (as Ulrich has already pointed out) a short-name y for each 
project, to be defined on its wiki page.
E.g., "Gentoo KDE project" has shortname kde.

d) Simple and stupid mapping for e-mail aliases: 
project shortname y -> e-mail alias is y-project@g.o
Legacy (e.g. y@g.o) addresses will be forwarded.

e) Since per GLEP 39 only developers can be project members, let's introduce 
"contributors" which are listed on the wiki project page together with the 
members.

f) The project e-mail alias is automatically populated from the wiki page 
(members and contributors).
* We may want to introduce a tick mark on the member listing ("Receives 
project mail"), if not all project members want to be on the alias.
* This introduces the simplification that alias members are a subset of 
project members & contributors. I.e., noone not listed on the project page can 
get project mail.
* Obviously there are exceptions to this rigid structure for few special teams 
(sec, infra, ...)

Thoughts?
Andreas

[1] https://archives.gentoo.org/gentoo-dev/message/7fa1dd0095297d1c3365d432058a088f

-- 
Andreas K. Huettel
Gentoo Linux developer (council, perl, libreoffice)
dilfridge@gentoo.org
http://www.akhuettel.de/