Skolelinux is an effort created and run by volunteers, for Skolelinux to work we need people to pitch in and help, as there's more then enough work to go around. Since you're reading this page you're least interested in helping, which is great :-)
Regardless wether you're a regular enduser, computer-guru, or somwhere in between, and regardless of how much time you have there will be something you can do. Here's a short list of suggestions (if you want to help and don't know how, please contact the localization team coordinator of your language, or the development list):
How to get your work into Skolelinux depends mainly on wether you're just sending in one little improvement (don't be shy every little bit helps), or wether you intend to be a regular contributor.
In the first case simply send your improvement to the international development mailinglist firstname.lastname@example.org (NOTE: this is an english speaking list).
In the second case it's best to become a Skolelinux developer. To do so you need to:
subscribe to the international devel mailinglist (instructions for doing so can be found here).
You should use this list to get help with any problems you run into, keep everybody abreast of your progress, ...
Get yourself SVN access, you need to do this in 2 places:
follow the instructions for gaining SVN access to the Skolelinux SVN.
Create yourself a useraccount on alioth (sourceforge for Debian), and request acess to the debian-edu project.
NOTE: should you have any problems using SVN don't hesitate to ask for help.
contact the coordinator for your country (if any) to let him now what you're working on. If you're the first person in your country to start working on Skolelinux you should add yourself to the kontakt.html.en page (in the www/i18n/ dir of SVN) so people will know you are the one to contact if they want to pitch in.
On the technical side of things this if very little work: adding support for a new language to Skolelinux only takes a couple of hours. Also you don't need any special knowledge to add support for your language, all it takes is a little time and effort.
Once the technical side is taken care of you might want to take a look at the translating the documentation and website (which is considerably more work), and/or promoting Skolelinux at your local schools.
Here's a list of the different steps in adding support for a new language to Skolelinux:
Find out how to get your changes into Skolelinux.
In the Skolelinux svn-directory src/task-skolelinux/lists/ you need to add the packages needed to support your language (KDE translations, ispell dictionaries, etc.) to the file task-Skolelinux-workstation.txt.
Add the packages needed to support your language (KDE translations, ispell dictionaries, etc). to the workstation profile.
in the Skolelinux SVN-directory src/locale-config-Skolelinux:
add appropriate values for your language to the configuration scripts in the conffiles.d subdirectory (by adding an extra entry to the case statement in each script).
Change update-locale-config.1 (the man page) so it reflects the support for the added language (keep the languagelist alphabetically).
in the debian-edu SVN-directory (on alioth) src/debian-edu-config:
in the debian-edu SVN-directory (on alioth) src/debian-edu-install:
translate the po-debconf template for the Skolelinux specific installation questions.
You do this by copying the debian/po/templates.pot file to debian/po/CC.po (CC is again the language code for the new language), and translate the strings in the new CC.po file (use poeditor, or kbabel to do this)
NOTE: sveral of the strings in the po-debconf template have a comment marking them as debian installer main-menu items. For Usability is important that all menu items have a consistent style. Thus you might want to check in with the debian-l10n team for your language to ensure this.
Translate the Skolelinux webmin-modules (copy the en.pot to CC.po, and translate using your favorite po-tools):
Check if the po-debconf template for shadow is translated (you'll find it in the Skolelinux SVN-directory src/rebuilds/shadow/debian/po/). If not translate it.
NOTE: if you update or, add a translation you should make sure the changes are incorporated into debian proper. To get a po-debconf translation added/updated in debian proper you should send in the new translation as a wishlist bug. When creating the bug report don't forget to tag it 'patched', and also include [INTL:CC] in the subject (where CC is the language code of the new translation).
Translate the documentation:
All documentation is now translated using .po files. This means that to start a new translation you need to copy the <document>.en.pot to <document>.CC.po (where CC is the language code of the new translation), and translate it with your preferred po-editor.
Currently there are 3 pieces of documentation to translate:
The architecture document which describes the architecture of a Skolelinux network. You'll find the en.pot file in the former cvs at www/arkitektur/arkitektur.en.pot.
In addition to translating the .po file you'll need to create a localized version of the network-arch_en.dia file by copying the english version to network-arch_CC.dia and adapting the strings in it using the program dia.
The Administration Manual , you'll find the .pot file in the svn-dir www/dokumentasjon.
Then there's the Requirements Specification document which is located in the SVN-dir www/qualityManagement/DQ.
Translate the developer website
If necessary help out with the translation of programs used by Skolelinux: