Processes in the L10N team

[Dimitris Glezos]

O/H Bart Couvreur έγραψε:
> Dimitris Glezos schreef:
>>> The L10N project shouts "I need resurrection" with all it's strength.
> So, to
>>> have something to hold onto, I copied the above points here:
>>>
>>>   http://fedoraproject.org/wiki/L10N/Tasks
>>>
>>> Ideas, comments, suggestions?
>>>
>>> -d
>>>
>>>
>>> [1]: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207095
>>>
> Nice list Dimitris, I totally agree.

I'm glad the initial list seems sane to most of you. :)

I have updated the list with some of the ideas dropped on the lists:

  http://fedoraproject.org/wiki/L10N/Tasks

The main problem I see right now is that we must all understand that for these
issues to be resolved, we should actually work on them. It was a bit surprising
to see that nobody has edited the page or subscribed to receive changes on it.

So please people, *get involved*, otherwise these problems will remain problems.
If the Translation project wants people to bother helping it, it should start
helping itself first.

We can start by breaking the big ideas into smaller tasks that could be handled
by 1,2 persons each. The smaller/simpler/modular the better.

> An idea:
> -> get hooked up in the Fedora Account System, now people on l10n and
> docs need 2 accounts to get work done, cut it down to 1
> -> get a seperate cvsroot on cvs.fp.org with only .po / .pot -files.
> -> try to get into Jesse Keating's pungi, for l10n-inclusion (not so
> sure if this is possible, if not just a hook in the build system)
> -> set up an sort of sponsor-managed cvs or dir in the cvsroot (as
> extras, docs) so only language maintainers can commit (this may mean a
> lot of pain for the maintainer, but gives more control) and those
> files get into the build system
> -> (try to) migrate the web-interface and maybe add an
> online-translation system to it, so we create a low barrier to the
> project and thus more contributors + QA
> -> hook up a commit-mailinglist (or maybe just this one??)
> -> ....

These sound good and concrete ideas (except the online-translation system).
There are people to help out and give information; but someone else should be
the coordinator (aka the guy that does the correctly correlates tasks, people
and time).

I would suggest to remove them from the "task ideas" list and put them on a
schedule table with target dates. This way related efforts (RelEng, Docs,
Infrastructure) could help you out where needed to get the above implemented. :)

> Maybe we could call for a meeting with Fedora Infrastructure and Docs
> when this list is ready and get this "issue" off our back :)

+1. I'm sure both of these groups are willing to support us in the organization
of our processes. I'm also sure they are not willing to do the coding or the
maintenance of them.

-d


-- 
Dimitris Glezos
Jabber ID: glezos at jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/


"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--