[These are *draft* procedures, to be amended by the web-translators team and pending discussion/ideas/corrections with the team leaders.] Finding a Translation Team ========================== The existing translation teams are listed at README.translations as "Translations underway". The list includes details about the project page and the team leader. In case your language is not listed there, it means that * There is no team established and no pages translated * Some pages were translated by occasional contributors, but no team has been formed * The page is not updated with the current team information In all cases, if you can't find a team for your language, please contact us at . Joining an Existing Team ======================== First, register an account at Savannah, if you don't already have one. When you login, go to "My groups [link]" and fill in the name of the project in the field "Request for inclusion"; then complete the form and submit it. That way, we will be able to see the date when you sent your request and take necessary steps in case the team leader is inactive. It is certainly fine to have private exchange by mail, Jabber or IRC with the team leader in parallel to your request for inclusion to the project. Most probably you'll want to learn more about the established translation process and on the other hand, the leader might want to inform you about the project's internal procedures. If you don't hear from the team leader in two weeks, inform us about it at . Create a New Team ================= If there is no team for your language, you might consider establishing one. This is a very important activity and has always been a priority for the GNU Project. As a team leader you will have certain responsibilities. The first thing to do is to read README.translations and all the guidelines/extra information linked from that page. Checkout the www.gnu.org CVS repository [link] to get an idea about the HUGE amount of work that has do be done. Don't despair -- one by one, that job can be accomplished, exactly in the same way the GNU operating system was developed. Let us know at that you intend to start a new team and send us the questionnaire [link]. Be fair and answer to the questions with your own words, as you feel or think on the topic. Do not answer with links to gnu.org articles -- we are quite familiar with them. The purpose of the questionnaire is to enable us to make a judgement (albeit vague) about your motivation and dedication, and understanding of some core values of the Free Software Movement. We will reply with comments or directions. Register an account at Savannah and apply for a new "www.gnu.org" translation project. The project name should be "www-$LANGCODE" [FIXME: with or without dash?], i.e. for Swedish that would be "www-sv". We maintain a list of articles that are of high priority [link] to translate -- it is a very good idea to start with them. Until you are granted CVS write access, send all translations as html attachments to us [FIXME: include general guidelines about editing the HTML code, etc., perhaps would fit in the next section]. Responsibilities of the team leader [FIXME, FIXME harder, FIXME a lot] ----------------------------------- Recommendations for the team's organization [FIXME -- to be extended] ------------------------------------------- Do not work alone -- we require translations to be made by teams for several specific reasons. As a beginning, find at least one person to proof-read your translations before you submit them. This activity is as important as the translating process -- often you will make errors or your wording will be unclear or ambiguous. Others spot such issues much easier than you (and vice versa). Becoming a team leader ====================== [FIXME: To be discussed further, and we'll base it on the outcome and lessons learnt from the current Norwegian case, which will be the "guinea pig" for this procedure, as it seems.] Granting write CVS access ========================= You have to submit your first several translations to . You will probably receive advices and recommendations. When we feel that you are doing well, you will be granted write access. Be careful -- you will have the right to edit the whole "www" tree and basically the web pages of every project.