During the lifetime of the project we'll need many to do many different tasks. This is a list of project roles that may be available. Note that some roles are more urgent now than others. "Performance developer", for example, is useless right now. Pick as many project roles as you would like. :-)
- C Developer: Will develop ISO C code. One of the main roles of the project. Must have good knowledge of the standard.
- Low level developer: Will develop assembly and low level, not necessarily standard code. Must have knowledge of the specific low level tools we're using or targeting (ex: binutils, kernels, architectures)
- Tester: Will develop unit tests and port standard applications to our environment, to be used as test cases. Must have great knowledge of the standards. Testers need to become happy whenever they find a bug. See the guide for testers for details on how to write tests in libposix.
- Web designer: Will design the interface of our web pages. Includes the home page, the wiki and other web apps we may use. Should be an artist capable of designing clean websites.
- Web developer: Will program the designs made by the web designer. Must be good with CSS, HTML, etc.
- Web editor/blogger/"PR guy": etc Will edit and mantain content the website, making announcements and possibly moderating vandalism. Should just be well informed about what's going on in the project.
- Build system developer/ports mantainer: Will develop code for compiling and installing the library in some set of architectures. Must have knowledge of the build system used, toolchains, cross-compiling, emulators, Unix distros, etc.
- Performance developer: Will optimize code. Must have knowledge of profiling tools and low level tools/architecture details.
- Support/Debugger: Will answer user doubts, track and report bugs and debug or assign them. Must be patient.
- Roadmap manager: Will define sub-goals to the project, assign tasks for other project roles, report progress and possibly reevaluate and reorganize goals. Should have experience in management.
- Code reviewer: Will review code, specially third party contributions, approve and disapprove them, suggest changes. Will also clean up existing code. Must have good knowledge of the standard and should have experience in writing clean and safe code.
- Spammer: Will advertise libposix. Must tell your friends about your project, blog, e-mail, etc. :-P