Marc Paré a écrit :
Le 2010-10-26 01:33, andre999 a écrit :
Juergen Harms a écrit :
A couple of loose ideas that come when following the discussion:
1. Have packages pass "description QA" reading, done by non-technical
users (if implemented, easy with packages that are new or underwent a
major new release, how also catch packages that just "are around")?
2. As an alternative to direct mail to developpers, create some kind
of "fast-track" mailbox - rules to be defined - with a triage team to
make the link to the developpers (maybe not even with developpers, but
with "writers")? - would also allow to keep track of what is going on,
and serve as a "filter".
3. I suggest to separate the question of translation and of the
quality of descriptions - they have different priorities and
implications.
Normally translation is made on the current source text, and often in
real time. That is, as soon as a change is made in the text, it is
immediately available for translation. This process is used by
Openoffice and Mozilla (Firefox, Seamonkey, Thunderbird), for example,
So for package description, as soon as any description (or change) is
posted, it would be immediately available for translation, by the
various localisation groups.
So would this be possible to do with Mageia? We should be able to
manage this.
Marc
I and others have already suggested this in various posts, and I sure
hope that we implement this. It is very doable.
Since Mozilla started it, it has dramatically improved the completeness
of French translations, in which I was involved, even though many
translators at first complained about having to react in real time.
Virtually all localisations - except EN-US :) - showed significant
improvements in completeness, a number reaching 100%. A rare feat before.
The new LibreOffice is using this method, as was done under OpenOffice.
Because of restrictions by Sun (continued by Oracle), LibreOffice has to
redo all the translations.
A big job, but this method really helps. Sun insisted that all
contributors had to submit a hard-copy signed contract to assign their
copyright to Sun, which severely limited contributions, including my own.
LibreOffice is initially using about the same organisation, but no
copyright assignment.
Interestingly, much like Mageia, LibreOffice has attracted most of the
key contributors. But surprisingly, Oracle is insisting that
contributors decide : OpenOffice or LibreOffice, but not both. Note
that most of the development work on OpenOffice has been done by
contributors paid by Sun/Oracle, unlike the situation with Mandriva.
