Documentation Stable Release Updates

[Phil Bull]

Hi Matt,

On Sun, 2008-01-13 at 11:10 +0000, Matthew East wrote:
> Thanks for these. Ok, first of all it's key for me that any proposal
> needs to factor in the chance for translators to have a chance to
> update the translations of the documentation whenever a string change
> occurs. That's doable - we just need to include the requirement for
> the translators to be notified in good time of an update to the
> documentation before it happens and ensure that the new string is in
> Rosetta.
> 
> For that reason alone I think I prefer your first suggestion of a
> fixed schedule "documentation service pack" about 3 months after the
> release because this gives the necessary structure. However, you're
> right that it's a reasonable amount of work in circumstances where the
> docteam doesn't really have that many substantive contributors. But,
> we can give it a try.

As long as the process is reasonably well planned/scheduled, we should
be able to avoid situations where we run out of the time or manpower to
complete the updates. Mentoring students would be able to play a big
role in preparing the updates, too.

> I'm not keen on only updating the website, I think that if we're going
> to go to the effort, we might as well go the whole way.

I agree. What is currently involved in updating the website?

I'd like to move ahead with this. Would you like me to contact the
release team and ubuntu-translators to get their input?

Thanks,

Phil

-- 
Phil Bull
http://www.launchpad.net/people/philbull