[Mageia-sysadm] perl team alias?

Buchan Milne bgmilne at staff.telkomsa.net
Wed Aug 17 10:11:54 CEST 2011


On Wednesday, 17 August 2011 00:51:48 Michael Scherer wrote:
> Le dimanche 14 août 2011 à 14:15 +0200, Jerome Quelin a écrit :
> > hi,
> > 
> > up till now, i was the only one taking care of the perl stack within
> > mageia. however, kharec is joining me in this effort, and i have a
> > padawan interested to help perl packaging in mageia.
> > 
> > to that end, i was wondering whether it'd be possible to have an alias
> > such as perl at xxx.mageia.org - or whatever scheme you want, i don't
> > really care. this would allow to assign perl bugs to this alias when
> > triaging them. or add this alias as cc: to make sure the perl team is
> > aware of them.
> > 
> > i don't want a mailing list, since dev questions, comments and other
> > should go to -dev.  however, if you have another solution to provide,
> > let me know!
> 
> While I would not be against creating sub team ( because that's what it
> is ), I would rather have people first think to the various governance
> issues and problem before proposing a technical solution.
> 
> Aliases are obscure per definition, and assigning something to a aliases
> would mean that most people would not know who is in CC ( especially
> with regards to our privacy policy ).
> 
> We do need to decide who decide a new aliases should be given, and what
> it entails ( ie, what would perl take in account ? all perl modules ?
> all perl software ? ). And who decide who goes in the aliases/team.
> This would also have a impact on the maintainer db at various level,
> technical and organisational, etc.

Is there yet a maintainer DB? I would be in favour of a system of maintainer 
groups, where a group may have multiple maintainers, and multiple packages, 
and have an alias, and/or aliases for each package in the group, with 
recipients being the members of the group.

Such a group may also require an owner, who would have the ability to add or 
remove packages or maintainers.

> To me, the answer would still be to have auto assignement of CC based on
> maint db + a subscription database, but so far, no one coded it.

Well, I would think it *should* be the maintainer database, and just have a 
postfix alias map for it.

Regards,
Buchan


More information about the Mageia-sysadm mailing list