(→Contact/join the team) |
(→Mailing lists) |
||
| Line 23: | Line 23: | ||
= Mailing lists = | = Mailing lists = | ||
| − | * [https://mageia.org/ | + | * [https://ml.mageia.org/l/info/sysadmin-discuss Sysadmin discussion list] |
* Other lists can be found [https://ml.mageia.org/l/lists/sysadmin on this page] (commits, bugs, reports, etc ...) | * Other lists can be found [https://ml.mageia.org/l/lists/sysadmin on this page] (commits, bugs, reports, etc ...) | ||
Revision as of 17:50, 6 April 2013
Contents
Contact/join the team
- join the IRC channel and/or subscribe to the sysadmin-discuss mailing-list
- team is built from: see mga-sysadmin ldap group
Participating to the team
The whole infrastructure is managed by Puppet and SVN. The repository is public, and can be found at: http://svnweb.mageia.org/adm/
If you wish to join the team, the recommended way is to study how the infrastructure is organized, and start sending patchs, like any free software project.
To get a checkout of our puppet configuration, you use :
svn co svn://svn.mageia.org/svn/adm/puppet/
To test it, you should use a virtual machine, running Mageia, and you will need a recent puppet backport ( > 2.6.0 ). Any virtualisation technology should work.
Infrastructure clone
To replicate our own infrastructure for test purpose, the main puppet server should be on a computer who can be contacted on puppetmaster.$yourdomain. It is much easier to call the computers like we do ( valstar being the main node ), see [1] ). Using our configuration will automatically run a svn checkout in /etc/puppet on the puppetmaster, so take care if you plan to use git-svn or similar. For the more advanced tests, a ldap directory is needed, even if almost empty.
Mailing lists
- Sysadmin discussion list
- Other lists can be found on this page (commits, bugs, reports, etc ...)
User accounts requests
Requests about user accounts or additional permissions should be done using bugzilla on the Infrastructure -> Account request component.
