Typos, English grammar, trivial formatting.
converted to 1.6 markup
|No differences found!|
This is a guide for Developers to help New Contributors learn all the necessary steps to become a Developer:
1. Explain our way of working: Introduce yourself and the Debian-Edu/Skolelinux project and some specifications about the project. Describe our way of working and the differences between democracy and our doocracy.
2. Explain our infrastructure: Explain all four servers (administrator, developer, user and maintainer). Tell them which services are on which machine.
3. Explain our Subversions: The new one should have some experience in using Subversion. Show them both subversions and explain their use. Also make sure that the new Developer creates an alioth account. Make sure that there are commits from the newbie before you leave this point.
4. Explain the packages: There should be some knowledge about our three main packages. Explain the metapackage and its use. (debian-edu) Explain the install package and how it is created. (debian-edu-install) Last but not least, you should explain the configuration package and especially the use of cfengine. Maybe some small examples can help (debian-edu-config).
5. Explain the archive: If the new Developer is also an uploader you should explain to them our archive structure. After you explained it, you should also give some details about the dput/dupload-tools and the importance of using gpg-signatures (debsign).
6. Start team working: Explain to the new contributor that it is important to work in a team. For that, we have to communicate. It is necessary to use IRC and the Mailinglist. Both are important, and more or less necessary! You can offer your help, but if the new Developer has questions or is not sure about a bug fix or whatever, it is important that they bother the whole team and not you everytime! For that you have to make sure that they understand the importance of team working.
Note: This is just a guide to what you can teach/help a new Developer who wants to have some introduction first. Feel free to help on other steps, but the parts above are a kind of basic knowledge.