[Bf-docboard] Bf-docboard Digest, Vol 92, Issue 9

[Ivan Paulos Tomé]

Hi,
Here is Ivan Paulos Tomé. ( greylica )

There are lots of resources for translators to start working on Blender,
the translate Addon is one of them, amongst others. The question is
not the problem when integrating launchpad with Blender, the question
is how to make sure the three resources we have today get to the public in
a way
they will use it and not leave or abandon until the end of the translations.

I mean, if you setup a project in the launchpad, how to make sure team
leaders will always be coordinating their collaborators in a way the
translations start and end ?
Who is rensponsible for their translation branches and uploading files
to the SVN repository, integrating all of the possible resources ?

For example, i'm using Poedit, the translate Addon, the python
tooltip and my team/users/friends/teachers suggestions to
make sure my po is ok, then I upload to the Blender SVN repo.
I'm working with a 6~8 persons team in the PT and PT_BR U.I.
translations.

So, we have:

1) the normal way (using Poedit or strings translation softwares
out there),
2) we have the Translate Addon, and this Addon can be used to send a file
to the team leader for translation coordination,
3) We also have other implementations, like the
launchpad implementations, wiki implementations, HTML translations, etc.

Understand me, I'm not against the last resources I have mentioned (3),
but unless you have team leaders or coordinators always available to
users/translators, you will setup a useful system taht will be abandoned,
because you need a person to verify and merge strings,
and after merging, the same person will need to compile/test
the .mo generated and then, upload to the Blender SVN repo.

I'm not telling this is impossible, and I'm not telling that the Launchpad
will not work or it's useless because of the SVN syncronization.

I'm telling that if you can't find persons responsible for those tasks,
the translations will get abandoned again in Launchpad or any other
resources created to facilitate users/translators life, sooner or later.

If you could make sure the teams have at least one responsible/leader
always available to their collaborators, and open to new experiences,
like selective merges, SVN operations, po string comparisons,
 you have 90% of guaranteed success.

So, when you setup Launchpad, send team leaders to our IRC channel,

Our IRC channel is #blenderwiki

We have been using the same channel for the translations and blenderwiki.

Team leaders of the Blender translations at the #blenderwiki channel means
 we may have the best of both worlds, because those friends will have
a chance to integrate their Blender UI translations with Blender wiki
translations,
and they will have friends to teach them how work with the SV, setup
accounts
for uploading POT files, etc.

Positive Vibrations !

Ivan Paulos Tomé
Greylica - My Brain is Grey Like Yours !
www.blenderfarmbrasil.com.br


2012/10/26 <bf-docboard-request at blender.org>

> Send Bf-docboard mailing list submissions to
>         bf-docboard at blender.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.blender.org/mailman/listinfo/bf-docboard
> or, via email, send a message with subject or body 'help' to
>         bf-docboard-request at blender.org
>
> You can reach the person managing the list at
>         bf-docboard-owner at blender.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Bf-docboard digest..."
>
> Today's Topics:
>
>    1. Going the Launchpad way, again (Eduard Gotwig)
>
>
> ---------- Mensagem encaminhada ----------
> From: Eduard Gotwig <gotwig at ubuntu.com>
> To: Bastien Montagne <montagne29 at wanadoo.fr>, Blender Documentation
> Project <bf-docboard at blender.org>, bf-blender developers <
> bf-committers at blender.org>
> Cc:
> Date: Thu, 25 Oct 2012 19:47:16 +0200
> Subject: [Bf-docboard] Going the Launchpad way, again
> Hey,
>
> I want to ask, if you are interessted, in going the launchpad way, again.
>
> At least for translations, I would find it quite nice.
>
>
> As I am in the bf-commiters lp group, I already changed some info, that is
> important for the current version of Blender.
>
> For the translations, we would have to register a special translator
> account for the SVN translation branches, I suggest to use directly trunk,
> becouse the special reviewer, translator rights can be set than, directly
> trough launchpad itself. People would not have to review stuff from the
> branches branch first, but could use launchpad for that, instead.
>
> The problem is, that the trunk branch is not always the newest one, but
> the branches branch is. But than reviewers would have to check always all
> these commits for branches, again. Double effort, IMHO.
>
> I also created a request for the Launchpad team, to help us (also becouse
> we can't setup the vcs import without them):
>
> https://answers.launchpad.net/launchpad/+question/212315
>
> I also have problems in setting up the bug tracker correctly.
>
> I DON'T want that we use any launchpad internal stuff, like for bug
> reporting, etc., becouse than we would have to merge this stuff upstream.
>
> If we can use as much import processes as possible, it could help us to
> speed up the Blender developement process
>
> I dropped, the outdated bug tracker and translation imports.
>
> Any thoughts?
>
> Greetings, Eduard Gotwig
>
> _______________________________________________
> Bf-docboard mailing list
> Bf-docboard at blender.org
> http://lists.blender.org/mailman/listinfo/bf-docboard
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20121026/3f0c4715/attachment.htm