Becoming an Exclaim Developer

Filed Under: Project Information

Should you wish to join the Exclaim Project team, we have a detailed process and set of requirements. You will not be able to become a developer without following these.

We require developers with experience with the C programming language and assembly language for the architecture(s) that you wish to work with. On IA-32 and AMD64 we use AT&T-style (as used by GAS) assembly rather than Intel-style. You must also have experience with operating system development. Being able to follow a tutorial such as bkerndev is NOT sufficient to fulfill this condition.

1. Make sure that you fulfill the requirements above.
2. Get familiar with the Exclaim code, check out a copy with Subversion and learn how it works. Feel free to play around. If you wish to know more about anything in the code, ask in IRC. Do NOT PM the developers with questions.
3. If you changed the tree, svn revert it to the original state, and make some useful patches. Currently we want around 10 useful and well built patches. Make sure you follow our Syntax Guidelines and TODO list, as patches not following these can not be accepted. Bug fixes are always welcome. If you wish to work on a TODO list item, please ask in IRC before doing so.
4. When you have made your patches, dump them on the Exclaim Pastebin or any other service, and then contact lsproc on IRC.

When lsproc receives the patches, the following will happen:

1. Check they build and work as intended, without affecting any other part of the system.
2. Ensure that the patches can be included in current tree, e.g. don't conflict with anything else going on, and do fit with the TODO schedule.
3. Ensure the patch follows the syntax guidelines.
4. If all of these have passed, then the patches go to Alex, who then tests them for the highest of quality standards (which are very picky). He has the last word, regardless of what lsproc says.

If the patches are approved, then Alex will consider giving you write access to the SVN tree. You will find out if you get accepted, and if not, why not.

We operate a very strict policy in order to retain the quality and stability of our kernel, as well as to help stop it from drifting from it's goals. Please do not let the complexity of this put you off, as we are fair in our judging and failing will not disqualify you from ever joining.