Hi all,
Myself, Ozzy and Liam Fraser wanted to ask a few questions about community documentation.
We had a discussion on this forum a few weeks ago regarding the best way to produce it:
(quote)
I think the documentation being:
1) "born" on the wiki
2) peer reviewed on the wiki (and approved)
3) then translated by community members
4) then published as a full article or PDF
…is a good place to start, unless anyone has any more suggestions?
(end quote)
And this seemed to be the general concensus of the thread...
The first thing We're planning on creating is a "getting started" guide for the RasPi ,that takes a user from opening the box, connecting it up, installing an OS and tools, right up to creating the RasPi shooter game that Liam has been creating you tube tutorials on.(A bit like you got with a Commodore 64, just to get you started)
So before I go into any detail about the sections and content we think we need, and the people who have already signed up to help us we just need to ask the community a couple of questions:
1) Is anybody else already working on something like this that we shoudl team up with? (Eben and Liz just emailed us, and don't seem to think so)
2) Can we create some new pages under the eLinux wiki to host this (to the nice people at eLinux)?
3) Can we get volunteers to translate this for us into different languages from the wiki as it develops?
If this looks like the best way to go I'll post more information here about what we would like to create, whos already agreed to help us, and how you can get involved yourself, once we've got some feedback from the forum.
Best regards,
Turbo, Ozzy and Liam