BlackSheep As i'm kinda butting in, i would like to know what are the "top" priorities for now and what could be done first after those "top" docs.
Before talking about priorities, it might be good to come up with an exhaustive list of what needs to be done. We could review what we've got and brainstorm a bit about possible new approaches ... then organize and prioritize.
That's the main reason I suggested that we have meetings.
How could we do those ? What is already existing for now and do we have to separate docs meeting from the existing staff meeting ?
Although docs are mentioned at the staff meetings now and then, the focus is really on the programming end ... digging deeply into the subject of docs work would bring the programming discussion to a crashing halt, so the details are generally left in the air.
I think meetings would be good way to get everyone one the same page, and allow them to share ideas, e.g. even though I'm mostly going to be concerned with l10n docs, I might have an idea that @luceos could use effectively for the extension documentation. That sort of thing.
We're using Skype for staff meetings, and we could probably use the same setup for documentation meetings. However I don't think we have access to a whiteboard there ... we could consider other options if we really need something like that.
What tools do you want to use to keep tracks of who's writing what and for assign task to somebody ?
That's a good question ... I don't have any experience with such tools, but some sort of collaborationware might be very useful for tracking progress of various documents.
Do you have a problem with me kicking your virtual butt on some tasks ? I really don't whant to stress you out.
... Not to mention that the person doing the butt-kicking can also get stressed out by that job! ?
I'm hoping there won't be too much need for butt-kicking. Adding some structure to the process should be enough. Break the job down into manageable chunks and prioritize them properly, and people will find it easy to contribute.