Authors: | Adam Chodorowski
Neil Cafferkey |
---|---|
Copyright: | Copyright © 1995-2015, The AROS Development Team |
Version: | 50056 |
Date: | 2015-02-09 |
Status: | Done. |
We have quite few active developers, which unfortunately means that progress is quite slow. We simply need more people to help us out! There is a huge number of tasks that are in need of a dedicated developer. They range from large projects to small ones, from hardware hacking, through high-level system programming to application programming. There is basically something for everyone who wishes to contribute, regardless of how proficient they are in coding!
For those of you who aren't programmers, there are still plenty of tasks that you can help with! This includes writing documentation, translating programs and documentation to other languages, creating nice graphics and hunting bugs. These tasks are just as important as coding!
This is a list of some tasks that we need help with and which nobody is currently working on. It's by no means a complete list; it simply contains the most prominent things that we need help with in AROS.
Implementing missing libraries, resources, devices or parts of these. See the detailed status report for more information what bits are missing.
Implementing or improving hardware device drivers:
Porting to other architectures. Some examples of hardware for which no maintained AROS port exists or has been started:
Implementing missing Preferences editors:
Improving the C link library
This means implementing missing ANSI (and some POSIX) functions in the clib, to make it easier to port Unix software (e.g. GCC, make and binutils). The biggest thing missing is support for POSIX style signalling, but there are some other functions missing as well.
Implementing more datatypes and improve existing ones
The number of datatypes available in AROS is quite small. Some examples of datatypes that need improvement to become usable or need implementing from scratch:
Porting third-party programs:
Want to join the development effort? Great! Then join the development mailing lists you are interested in (at least joining the main development list is highly recommended) and request access to the Subversion repository. That's it. :)
Writing a short mail to the development list containing an introduction about yourself and what you want to help out with is encouraged. If you have any problems, please don't hesitate to send a mail to the list or ask around on the IRC channels. Also, before starting to work on something specific, please write a mail to the list stating what you are about to do or update the task database. This way we can make sure people don't work on the same thing by mistake...
The AROS repository is running on a password protected Subversion server, which means that you need to request access to it to be able to collaborate in the development.
Please email your request to the Subversion administrator. Your mail should include your real name and preferred user name. An account will then be created with a temporary password. Once you receive notification of account creation, you can change your password through the trac interface.
For information on how to use the AROS SVN server, please read "Working with SVN". Even if you already know how to use SVN it is useful to look through that page, as it contains information and tips specific to the AROS repository (such as how to log into it).