Re: Helping translators do their work

[Graham Percival]

On Sat, Feb 13, 2010 at 01:39:08AM +0100, Francisco Vila wrote:
>   e600412e50db9e8ee3b9e408527322b84b946f52 Doc build: make
> screenshot-tutorials shared.
> 
> one tends to think that only blocks of text were moved or files
> renamed. It is impossible, (and check scripts do not help on that) to
> guess that in the meantime some random lines were touched.

I don't know what you mean by "some random lines were touched".
The material was moved, and then the macros were called.  If we
didn't add those macros, the docs would be broken.  I think we
should try to keep git compilable at all times, if possible.

> I'd beg for you to separate moving/renaming from editing into
> separate commits. Updating becomes a nightmare otherwise. Thank
> you!

Sorry, can't do.  Even leaving aside the question of whether or
not that change should have been separated into multiple commits
(and I would argue that it shouldn't be), we simply do not have
the doc resources to play games.


We currently have two (2) people working on the docs.  Neither of
them has push ability.  Neither of them have made 3 good patches
in a row.  They're learning, and I have high expectations of them
in the future, but it'll be a few months before they've got the
hang of things.

The LilyPond project has approximately 5% of the "documentation
power" that we had during the height of GDP.  I cannot accept any
policy changes which make life harder for documentation
contributors.

If we get a lot of new doc contributors during GOP... and if they
learn quickly... and if they stick around afterwards... then maybe
in 12 months I could consider adding some odd policies about
commits to help the translators.  But until/unless that happens,
we'll maintain the status quo.

Sorry,
- Graham