[Installation Guide] I've changed my mind again!

[Phil Bull]

Hi guys,

I've changed my mind about how best to approach the Installation guide.
As you may be aware, I attended a conference last weekend on writing
open source documentation, and came back with lots of new ideas and a
(hopefully) better idea of how to run a documentation project. I'd like
to try and apply some of these ideas to the IG if I may.

My first plan is to recruit a small team of contributors and assign
specific roles within that team. Each person would have a well-defined
set of responsibilities and definite goals to work towards. We would
meet on a regular basis and report back to the Doc team regularly too.
The roles which I think make the most sense are Project Manager (me),
Editor, three Writers, Technical Reviewer and User Testing Manager,
which makes seven in total.

The advantages of working in a structured team, as I see it, are that
people will have a better idea of what is expected of them, there will
be an obvious "go-to guy" responsible for a certain aspect of the guide,
and communication should be faster. If the guide is successful, it would
also be something for people to put on their CVs/resumes (effective
teamworking is still a skill, right?).

The caveats are that the size of the team is fixed (no room for
latecomers) and that a greater (but not unrealistic) time commitment
will be required from team members.

So, what do you guys think about this? Worth a try?

Thanks,

Phil

-- 
Phil Bull
https://launchpad.net/people/philbull