What happens to docs

[Dimitris Glezos]

On Wed, May 18, 2011 at 6:00 AM, John J. McDonough <wb8rcr at arrl.net> wrote:
> Whenever you make a significant change in a project, any project, you
> need to identify the new or affected tasks and adjust the schedule
> accordingly.

Honestly, I think what was needed was done.

We started enough time before the Docs string freeze and announced in public
the current issues & plan. Docs was on the call to give a +1 and the Board's
opinion was taken into account as well. We migrated one project of this type
and prepared very detailed migration instructions for the rest. One person in
Docs was identified to migrate more projects and act as the local expert. To
override the locale naming issue, new teams were created and the tx-client was
adapted early on.

Yes, we could be more active in monitoring the docs migration process, but I
don't see how the Board could help with that. There was plenty of time to ask
questions and manage things, IMHO.

-d


> The Board decided not to do that.  Whether they were fixated on a
> specific release date, felt somehow magic would happen, or were simply
> clueless I can't say.  But the board decided not to schedule the tasks
> necessary to accommodate the tx change, so those tasks never happened.
>
> Now it's a surprise?



-- 
Dimitris Glezos

Transifex: The Multilingual Publishing Revolution
http://www.transifex.net/ -- http://www.indifex.com/