Other languages English ; Français ; |
Contents
Maintainer groups
Maintainer groups are... groups of packagers and developers who join their efforts to maintain a set of packages: kernel, basesystem, KDE, rpm stack, GNOME, drivers, mageia tools, etc.
Each group has a dedicated mailing list which gets notifications from bugzilla when bug reports are assigned to the group, or changes are made to bug reports already assigned to the group.
How to join a group?
- Introduce yourself on the dev@ml.mageia.org mailing list, saying which group you are joining.
- Subscribe to the appropriate mailing list (see table below).
- Add your name in the table below.
Joining a group is open to packagers and developers, of course, but also to anybody interested in helping by testing, diagnosing issues, helping other users on bugzilla, etc.
You can also silently join the mailing lists out of curiosity and follow what happens there... Maybe at some point you'll find a task that's perfect for you and others will probably help if you need some hand-holding at first.
List of groups
Name | Focus | Mailing list | Packagers and developers: Name (Nickname) | Group animator |
Base system |
binutils, glibc, gcc, etc.
Exact scope to be defined. Maybe we should create a toolchain group for gcc and others. To be discussed. |
basesystem@ml.mageia.org | Pascal Terjan (pterjan)
José Jorge (zezinho) |
|
Kernel and drivers |
Packaging of the linux kernel and drivers | kernel@ml.mageia.org | Rémi Verschelde (Akien) Pascal Terjan (pterjan) Shlomi Fish (shlomif/rindolf) Jim Locker (jiml8) |
|
Mageia Tools |
Development and packaging of Mageia's own tools: installer, drakxtools, manatools, etc. |
mageiatools@ml.mageia.org | Thierry Vignaud (tv)
Angelo Naselli (anaselli) |
|
ISO building |
Group for all those who take part in building the installation and Live ISO images | isobuild@ml.mageia.org | Papoteur
Neal Gompa (Conan_Kudo/Pharaoh_Atem/Son_Goku) |
|
RPM stack |
Group for maintaining the RPM stack, and other packaging-related packages. Note that including urpmi seems unwanted, see bug #21790, comment #2, so let's keep that one in the Mageia Tools group | rpmstack@ml.mageia.org | Thierry Vignaud (tv)
Neal Gompa (Conan_Kudo/Pharaoh_Atem/Son_Goku) |
Neal Gompa: candidate |
KDE |
Packaging of KDE / Plasma, Qt and related applications | kde@ml.mageia.org | Nicolas Lécureuil (neoclust)
David Geiger (daviddavid) |
Nicolas Lécureuil |
GNOME |
Packaging of GNOME and GTK | gnome@ml.mageia.org | Pascal Terjan (pterjan)
Olav Vitters (ovitters) |
Language stacks
Name | Focus | Mailing list | Packagers and developers: Name (Nickname) | Group animator |
Java |
Java stack | java@ml.mageia.org | Nicolas Lécureuil ( neoclust ) | Nicolas Lécureuil ( neoclust ) |
Perl |
Perl stack | perl@ml.mageia.org | Shlomi Fish ( shlomif / rindolf),
Sandro CAZZANIGA ( kharec ), Bruno Cornec (bcornec), |
|
PHP |
PHP stack | php@ml.mageia.org | Marc Krämer (mokraemer) | |
Python |
Python stack | python@ml.mageia.org | Rémi Verschelde (Akien), Shlomi Fish ( shlomif / rindolf) |
Maintainers database management
Each group animator creates a user in identity.mageia.org, with a private email from his and a login that is built from the mailing list name. Please follow this convention precisely so that we can use it in the future in tools for QA, bug squad or packagers. Example : a "kde" user for the kde@ml.mageia.org group. This group user must have an SSH key that the animator can use with mgarepo in order to update the maintainers database with it. A request to the sysadmin team will need to be made so that the group user is able to update the maintainers database. If the group animator is temporary unavailable and changes are needed to the maintainers database, contact the sysadmins so that they can make the needed changes. If the group animator left, she should ideally hand the group user to the new group animator who'll take care to change the email to hers and change the SSH key. If a group animator gives no news and a new group animator is chosen, contact the sysadmin team so that they can change the email and password for this account and clear the SSH key.
This is a temporary solution until we can provide better tools for managing package ownership by groups.