As agreed with Rob, I have put together a list of information, that would have me problems and time for all those that helped me.
This list is just a starting point (all the information is out there, so it should just be a list with links) Suggested reading for all volunteers: - Where do I find information (wiki, cwiki, mailing lists) ? - What can I do to help ? - How is the organization (contributor, committer etc....all the way up) ? - Who is who ? (It would be good to have a list of the key persons) ? - What are our relationship to other openOffice packages (can I use my contribution elsewhere) ? Suggested reading for Wiki contributors - Which writing rules do we have (do I change a page directly or use talk) - How is the content controlled, basically I can write anything, are there any QA ? - How is the structure of Wiki ? (and temporary, which parts are old and outdated) ? - Who do I contact if I have problems/questions/need guidance ? Suggested reading for a translator - Where do I find correct information about localization (some wiki pages are misguiding, and l10n.openoffice.org is NOT a good starting point) - Where can I see status of the ongoing translations ? . Which tools do I need and how do I use them (any standards) ? - Who do I contact to get started ? Suggested reading for a tester - How can I help testing ? - Is it possible to test in my native language ? - Which tools do I need ? - How do I report bugs ? - Who do I contact, if I want to be a tester ? Suggested reading for a developer - Where do I find guidance on how to write a source code (naming standards etc.) ? - Where do I find build instructions (I found 5 different for Ubuntu...the last one was pretty good, but I still had to ask on dev for the last bit (a simple flag was wrong)) - Where do I find source ? - When do I need to use the sources, and when to use extensions ? - Where do I find the bug reporting system ? - How can I "reserve" a bug for me to solve ? Then of course as you grow more into the community you get more questions (like CMS etc), but I think to cover that would be too much.
