The aMule Project
The aMule project is led by a bunch of people (tho some rumours say they are monkeys) who toil away in front of their computers, so that you can enjoy a stable and featureful P2P client. This page is about them.
These are the people who work on aMule:
- GonoszTopi: External Connections developer and substitute admin.
- Phoenix: Code janitor junior and mostly absent admin.
- Wuischke: Coder, janitor, politician, does-everything-noone-else-want-to-do.
- Stu Redman: Coder, specially Windows related.
- Citroklar: Tester, slave-work-coder (sometimes)
- ender`: Tester
- nachbarnebenan: Tester, and life-complicator by using large&strange nicks ;-P
- nich: Tester
- skolnick: Solaris tester
- Stefanero: Supporter, Tester, and aMuleWeb Guru
Special Gold Guest Members
- Bigbob: Also known as Creteil; aMule project creator.
- Madcat: The one and only kitty dev.
- Tiku: And God said: Let there be lMule!
- bootstrap: IRC bot (bootbox) and aMule SVN hoster
- uberpenguin: uberpenguin is extremely difficult to classify... Let us call him the 'official bystander to *mule'.
- niet: DNS stuff, XAS, tester.
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.
- deltaHF: Webmaster, Admin and from-time-to-time-coder ;)
- falso: CAS coder.
- Hetfield: Ex-Admin, pretty-no-free-time coder.
- Jacobo221: Our man-for-all
- Ken: The big Mac guy.
- Kry: Developer and admin.
- lfroen: Core/GUI dedicated guy.
- thepolish: aMule tools coder.
- shakraw: aMuleWeb mantainer.
- Unleashed: Sometimes around ;), not anymore.
- Xaignar: Code janitor extraordinaire!
Is this Team competent enough?
There is a private IRC channel where aMule developers talk about future plans, developing roadmaps and help each other. Many people wonder how's life in that channel. It is well known that a good working environment grants an efficient development. Now, get a random example of what the Team's working environment is (Parental advisory: Keep your children away from this link!).
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 C++ is the language in which aMule is written. You'll also need to learn about the GUI toolkit used by aMule: wxWidgets. In addition, you are required to our Coding Style rules or we will beat you to death with a sockful of rocks. We do not require that you be an expert, only that you are willing to help and learn.
If you are interested, then simply drop by the IRC Channel and let us know. Currently, we use a private SVN server, but after you've submitted a patch or two you can easily get r/w access to it. You can also post patches on the Development forum, however, virtually all discussions regarding development happens on IRC.
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 look at the aMule translation howto.
BTW, you can also help with translating aMule wiki articles. There's always lots of work to do. =)
Contacting the aMule Team is easy. Choose between any of the listed ways in the contact article. Just please do it once, avoiding spam or floods.