Visit Savannah
This section reserved for guidelines, How Tos or anything else that will assist Contributors, developers and admins with this project.
This page is where you will find instructions on how to use CVS, the mailing lists and the tools involved in translating application interfaces... I just haven't got 'round to writing them all yet. (sorry). In the mean time there is :
In this section we will step through the process of configuring and using some of the tools you will need to fully utilise this resource. We assume here that you have a fairly "normal" install on a Linux or FreeBSD box. We don't go through the details of any distributions package management tools. Where they are mentioned they will refer to a Debian based system.
If you are new to development level applications (tools) you may find all of this a little overwhelming at first. Please don't break your install trying to force things into place; drop us a line and ask for help. Remember unless you are doing lots of development stuff it may not be worth your while. You can still contribute with almost no tools beyond a text editor. a mail app and a browser. Take it in bite sized chunks. .... Well if I haven't scared you off ... lets go.
First consider Joining Savannah. Supporting GNU is always a "good thing". Once you have joined savannnah you may readily join us. Visit the Joining the Project page for more instructions.
A reasonably brief overview of Kjartan Maraas' Gnome Translation Guide is at this site: Translation of the GNOME desktop environment : This document gives you an overview of the processes involved with the code itself. Here at the Tetum project we hope to keep that at arms length for you.
Due to a "break in" the methods and clearances required to access the project CVS are in a state of flux.
This page is likely to be reasonably up to date: https://savannah.gnu.org/cvs/?group=tetum (the tetum CVS instructions)
Please contact me for help if you require it: gossner IHA arcom dot com dot au
Developers please note that GnuPG clearances will soon be required as well.
Not withstanding the above .. anonymous downloads (which is probably what you want) are done as follows:
This project's CVS repository can be checked out through anonymous CVS over SSH with the following instruction set.
The module you wish to check out must be specified as the modulename. When prompted for a password for anoncvs, simply press the Enter key.
The SSHv2 public key fingerprints for the machine hosting the cvs trees are:
RSA: 1024 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5
DSA: 1024 4d:c8:dc:9a:99:96:ae:cc:ce:d3:2b:b0:a3:a4:95:a5
export CVS_RSH="ssh"
cvs -z3 -d:ext:anoncvs@savannah.gnu.org:/cvsroot/tetum co tetum
export CVS_RSH="ssh"
cvs -z3 -d:ext:anoncvs@savannah.gnu.org:/webcvs/tetum co tetum
When you update your sources from within the module's directory (with cvs update) you do not need the -d option anymore.
cvs up
Is all you will need to do (from within the source directory).. That is: a directory with a CVS subdirectory in it. That way you only download the changes and not the entire tree all over again.
Please note you can not UPload (commit) files this way (you need to be a project member for that)
Ask for help.. It IS confusing the first few times :)