In Flavio's defense, I'd like to restructure this conversation.
Undoubtedly, he's put great effort in this work.
From a deployment's point of view, it's a contribution.
From Gonzalo's POV, it's a burden because Flavio hasn't taken up
learning to master Git.
From Localizer's POV it's a burden because, in their view, it implies
double the strings.
These are representatives up "upstream".
In my humble opinion, the situation is out of balance. We cannot dismiss
contributions
merely because people have not learnt all the tools. This also goes for
localization team,
because really, from a friendly fork's POV, doing a simple msgmerge
command imports
all of the necessary translations from upstream (or the other way around).
In any case, the amount of user visible strings in TamTamMini is negligible.
I spent the last month trying to get "mantainers" to respond to requests
to update
GTK2 branches with translations, with barely any response except Manuq
and Gonzalo,
and only the first actually took action on my request.
Really, things could be simpler for downstream, especially
Activity-wise. Sugar per
se is a different matter because luckily, we have Daniel Narvaez, but
who knows
how long he'll put up with us.
The Sugar Network's proposed workflow is that anybody can upload a
bundle. It is
not mandatory that everything has to be "just right". I would encourage
Flavio, who has
already offered, to mantain a fork of TamTamMini with his changes, in
git, and either
create a new Activity Id and name for it or we can see about the new
features in
Sugar Network/ASLO that will enable non-mantainer uploads. For the case
where
alternative implementations of the same activity exist, by default the
system will
offer the one from the original author.
If the activity really works better, perhaps we will even include it in
Hexoquinasa, our
downstream of Platform Team's Deployment Platform, built for Perú.
Love for TamTam Suite really is welcome from this side of the island.
Regards,
Sebastian
El 17/11/13 12:12, Chris Leonard escribió:
On Sat, Nov 16, 2013 at 6:50 PM, Flavio Danesse
<fdane...@activitycentral.com> wrote:
On the issue of separating the application from the rest of the suite, I did
because it was the only way to understand it, correct the code and port it
to gtk3. The code of the suite is filled with errors and unused files. Now,
this application is much easier to maintain and extend. The same applies to
the translation patch, most not used by TamTamMini.
The TamTam Suite was set up to use a common set of translations on
purpose. Some time ago, they were all completely separate and it was
a big burden on localizers to repeat the translation work multiple
times.
Free and open discussion between developers and localization
stakeholders arrived at the current configuration. As the maintainer
of Pootle, I am not excited about seeing this collaborative agreement
undone and I will need some convincing on the need for splitting the
suite before hosting a fork of your TamTamMini in Pootle.
We need more open discussion, and less forking to move together as a community.
cjl
Sugar Labs Translation Team Coordinator
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
