Interested in translating Amarok's website

Sun May 24 20:39:44 CEST 2009

Hi Natán :)

Great to hear you want to help us with the website. We are always
looking for help there.

The pages that could really need translating at the moment are the
support and contribute page. I attached the code for those two. Do as
much of it as you want and then send them back to me so I can add them
to the website. Once you have done a few translations you'll get
access so you can do it yourself if you want.

The next release announcement is between one and two weeks away. If
you want you can help with that later on as well.

If you have questions please ask here or in our IRC channels #amarok
and #rokymotion on freenode.

Cheers
Lydia

-- 
Lydia Pintscher
Amarok community manager
kde.org - amarok.kde.org - kubuntu.org
claimid.com/nightrose
-------------- next part --------------
<p>New to Amarok? Have a question about Amarok? Don't worry! The Amarok team is here to help you.<br>
There are three main ways of getting support.</p>
<p>
<b>1. IRC</b><br>
Getting Help on IRC is the easiest and quickest way of getting support. Given below is a list of Amarok channels on irc.freenode.net.
<ul>
<li>Amarok's main English-only IRC channel: #amarok</li>
<li>Amarok's German language IRC channel: #amarok.de</li>
<li>Amarok's French language IRC channel: #amarok.fr</li>
<li>Amarok's Spanish language IRC channel: #amarok.es</li>
</ul>
Please be patient if you don't get an answer within a few minutes.
<br>
If you don't know what IRC is or would like to learn more about it's use, consider reading the following introductory articles:
<ul>
<li><a href="http://home.epix.net/%7Eircadmin/index.html">Introduction to IRC</a></li>
<li><a href="http://amarok.kde.org/blog/archives/43-The-Rules-of-IRC-Support.html">The Rules of IRC Support</a></li>
<li><a href="http://en.wikipedia.org/wiki/List_of_IRC_clients">List and Comparison of various IRC Clients</a></li>
</ul>
</p><p>
<b>2. Amarok Forum</b><br>
Go to the <a href="http://amarok.kde.org/forum/">Amarok forum</a>. Before posting your query in the forums you must be a registered user of the forums. Registration is free and can be done by simply filling out a form <a href="http://amarok.kde.org/forum/index.php?action=register">here</a>. If you are new to the forum, you may refer to the introductory <a href="http://amarok.kde.org/forum/index.php?action=help">help page</a>. For other languages the links are listed below:
<ul>
<li><a href="http://amarok.kde.org/forum/index.php/board,21.0.html">Chinese</a></li>
<li><a href="http://amarok.kde.org/forum/index.php/board,13.0.html">French</a></li>
<li><a href="http://amarok.kde.org/forum/index.php/board,14.0.html">German</a></li>
<li><a href="http://amarok.kde.org/forum/index.php/board,15.0.html">Spanish</a></li>
</ul>
Please search the forum for similar posts as many of the frequently asked questions have been previously asked.
</p><p>
<b>3. E-Mail</b><br>
Mailing lists are a way for large groups of people to keep in touch. You can subscribe yourself to the <a href="https://mail.kde.org/mailman/listinfo/amarok">Amarok mailing list</a> (english-only). You can post a message to all the list members, by sending an email to amarok at kde.org. You do not need to be subscribed to post to this list.
Please do consider going through the <a href="http://mail.kde.org/pipermail/amarok">archives of the mailing list</a> as your question might have been answered before.
<br>
You can also reach the above mailing list by using our <a href="http://amarok.kde.org/contact">contact page</a>. Note that your message will be delivered to a public mailing list.
<br>
If you are new to mailing lists or know very little of them, consider going through the following introductory articles:
<ul>
<li><a href="http://www.gweep.ca/%7Eedmonds/usenet/ml-etiquette.html">Mailing List Etiquette</a></li>
<li><a href="http://www.catb.org/%7Eesr/faqs/smart-questions.html">How To Ask Questions The Smart Way</a></li>
</ul>
</p>
-------------- next part --------------
<p>Amarok is a large project and there are many ways to contribute as well as many different levels of commitment. So, whatever your skills and available time may be, we can likely benefit from your help.
</p><p>
Overall, the different forms of contribution can be split up into the following categories:
</p><p>
<b>Promotion</b>
<br>The Amarok project, like other Free Software projects, thrives on publicity. Being more visible means getting more users, which in turn leads to more contributors. The Amarok promotion team goes by the name of Rokymotion and hangs out on IRC channel #rokymotion on irc.freenode.net. The following things are some of what Rokymotion works on:
<ul>
<li>The Amarok project <a href="http://amarok.kde.org">home page</a>.
<li>Release announcements for new versions.
<li>Promotional blog posts and articles, such as the <a href="http://amarok.kde.org/en/Insider">Amarok Insider</a>.
<li>Manning the Amarok booth and giving talks at conferences and other events.</li>
</ul>
Rokymotion also takes care of many other things, and new ideas are always welcome. If this interests you, join the Rokymotion IRC channel #rokymotion on irc.freenode.net to help spread the word.
</p><p>
<b>Artwork</b>
<br>
The Amarok project uses a lot of custom artwork. Both for the application itself, such as Amarok specific icons, boot splash screen and many other elements and for the webpage and promotional material. So if you are a wiz with gimp, inkscape or the likes, perhaps artwork is the way to contribute. To get in touch with us, log onto IRC channel #amarok or #rokymotion on irc.freenode.net.
</p><p>
<b>Testing / Bug reporting</b>
<br>
The Amarok code base is always evolving, and testing it for usability and bugs is very important. As is bug triaging (verifying already reported bugs, and removing bug reports that are no longer valid). To have a look at the currently open bugs, or to report new ones, go to <a href="http://bugs.kde.org">our bugtracker</a> and search for Amarok. It is also a good idea to log on to our main IRC channel on #amarok on irc.freenode.net where you can be helped getting started with testing or bug reporting.
</p><p>
<b>Code</b>
<br>
As Amarok is primarily a software project, code contributions are always welcomed. There are 2 main ways to write code for Amarok.
<br><br>
Application code: Amarok is written in C++ using the Qt and KDELibs toolkits. While the Amarok code base is quite large, it is also very compartmentalized, meaning that it is relatively easy to work on a small part of Amarok without knowing about how everything else works. A good starting point is to select a bug or personal annoyance and then to try to fix it.
<br><br>
Scripts: It is also possible to write Amarok scripts that expand the application in some way. These scripts are written in QtScript, which is basically JavaScript with access to the full Qt API. Getting started with this is relatively simple and a guide to Amarok 2 scripting can be found <a href="http://amarok.kde.org/wiki/Development/Scripting_HowTo_2.0">here</a>.
<br><br>
It is also possible to write a specific type of script that adds content from a remote source as an Amarok service. A guide on how to do this can be found <a href="http://amarok.kde.org/wiki/Development/Scripted_Services_Tutorial_2.0">here</a>.
<br><br>
Before starting any kind of development, it is recommended to drop by our IRC channel #amarok on irc.freenode.net.
</p>
<p>
<b>Donations</b>
<br>
If you can't help with any of the above we are always grateful for a donation by using the PayPal on the left side of this page. For other ways of donating money please come to our IRC channel #amarok on irc.freenode.net. Donations are mainly spent on infrastructure like our server, test hardware and to pay travel costs for our team members to conferences like Akademy.
</p>