Difference between revisions of "AMule devs"
(typo works-->work) |
|||
| Line 4: | Line 4: | ||
== The Team == | == The Team == | ||
| − | These are the people who | + | These are the people who work on aMule: |
=== Developers === | === Developers === | ||
Revision as of 06:26, 8 December 2004
Contents
The aMule Project
The aMule project is led by a bunch in people who toil away in front of their computers, so that you can enjoy a stable and featureful P2P client. This page is about us.
The Team
These are the people who work on aMule:
Developers
- deltaHF: Webmaster, Admin and from-time-to-time-coder ;)
- Jacobo221: Our man-for-all
- Kry: Main developer and Admin
- lfroen: Core/GUI dedicated guy.
- Phoenix: Code janitor junior.
- thepolish: aMule tools coder.
- Unleashed: Sometimes around ;)
- Xaignar: Code janitor extraordinaire!
- GonoszTopi: External Connections developer.
- falso: CAS coder.
- Hetfield: Admin, pretty-no-free-time coder.
Testers
- Citroklar: Tester, slave-work-coder (sometimes)
- ender`: Tester
- nachbarnebenan: Tester, and life-complicator by using large&strange nicks ;-P
- nich: Tester
- Stefanero: Supporter, Tester, and aMuleWeb Guru
Others
Former Team-members
These are people who have worked on aMule in the past. Please note that this list doesn't include the people from before aMule forked off from xMule, nor does it include people from the LMule days. If you wish to learn more about those, please visit the websites of those projects.
Developers
- Bigbob: Also known as Creteil; aMule project creator.
- Madcat: The one and only kitty dev.
- shakraw: aMuleWeb mantainer.
Testers
Others
- uberpenguin: uberpenguin is extremely difficult to classify... Let us call him the 'official bystander to *mule'.
- niet: DNS stuff, XAS, tester.
Helping
We can always use another helping hand, and if you are interested, then I'd encourage you to contact us and see if you can help us. Currently, what we need the most is developers and testers, though also translators and others.
Becoming a Developer
To become a aMule Developer (tm), you'll need at the very least a working knowledge of C++, since that is the language in which aMule is written. You'll also need to learn about the GUI toolkit used by aMule: wxWidgets.
However, we do not require that you are an expert, only that you are willing to help and willing to learn.
If you are interested, then simply drop by on IRC and let us know. Currently we use a private CVS server, but after you've submitted a patch or two you can easily get r/w access to it.
Besides IRC, you can post patches on aMule's Development forum. After a few good patches, you might become a developer.
We can use your skills if you are using one of the platforms where we aim at being usable on: Unix, Solaris, Macs and Windows. And if your operating system of choice isn't on that list, then maybe you can help add it.
Becoming a Tester
We need people who are willing to create complete bug-reports, as the standard is pretty low regarding user reports. This is rather simple, but takes patience. Please contact us on IRC for more information and read this guide on creating useful backtraces.
Becoming a Translator
aMule already includes translations for a number of languages, however, we'll always welcome more, and even if your language of choice has been done already, then perhaps you can help improve it. Please see the Translations forum for more information on current translations, or contact us on IRC. Also, take a deep look into the aMule translation howto.
Of course, you can also work on translating this wiki's articles. There's still a lot of work to do!
