Anaconda doc - lets go!!

I don't want to sound like a control freak here but I have a plan to 
organise this motley crew of willing contributors ...

Alexander has offered to set up wiki on his server for us. It seems like 
'twiki' is actually more suitable for what we want as it has 'control 
revision' built in which seems more useful for our purposes. If you 
agree Alexander - could you check out twiki and see about getting it 
running on your server - maybe on the weekend if you have the time ...

Grant Hill and Paul Frieds have very kindly offered their services to 
translate the doc into whatever formatting style redhat like to have for 
it to be a part of their official documentation project ...

With little 'twiki' experience, I am interested in seeing how smoothly 
collaboration will be using a twiki server for this project, but I'm 
pretty sure it will work out fine - and soon we will have a 'near final' 
copy of a complete 'anaconda customisation' document. Once people are 
happy with what we have achieved through the use of the twiki - we will 
pass it on to Grant and/or Paul and see what they can come up with!

I am even suggesting a mini-roadmap coz it seems that it is quite easy 
to lose track of things and let it fall into the 'yeah i will do that 
later - right after i organise my bookmarks list' category - and you 
know what that means ... ;)

_*week*_                                                       _*goal*_
today - 2004-01-18                  set up twiki server
2004-01-19 - 2004-01-25        set up twiki accounts for contributors 
and start posting/editing
2004-01-26 - 2004-02-08         continue editing/adding/etc. and 
discussing (2 weeks should be good i think)
2004-02-09 - 2004-02-22         'final' revision gets passed to 
formatters and they get 2 weeks to make it all look great!
2004-02-23 - 20040-2-29         last minute cleanups - and submitted to 
redhat on the 29th!! (only happens once every 4 years so lets make it 
special!!)

Sorry about the crappy formatting above but thunderbird tabs are a bit 
dodgy.
This is not intended to offend anybody with strict time limits and 
please feel free to make any suggestions.

The only other thing I am not sure about is how we can collaborate in 
real time if need be - maybe this can be done effectively with twiki (no 
idea) or maybe we can set up a channel on irc.freenode.net (eg. 
#anaconda-doc). Anyway we need a central place for communication because 
I dont think this list is appropriate for the traffic we are likely to 
generate ... Any suggestions on this?

And finally - if there are no objections to the above 'roadmap' - i say 
we try to stick to it as best we can and in the foreseeable future - the 
masses will have access to an incredible doc that just might spawn many 
more cool custom distros based on the great foundation set up by the 
Fedora team ...

cheers and away!!!

pantz

--
Before you criticize someone, walk a mile in their shoes ...
That way when you do criticize them, you're a mile away and you have their 
shoes!



--
fedora-docs-list mailing list
fedora-docs-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-docs-list