[tomboy-list] Fwd: About addin repository,

[Greg Poirier]

On Mon, Apr 18, 2011 at 4:09 PM, Luc Pionchon <pionchon.luc at gmail.com>wrote:

> On Tue, Apr 12, 2011 at 17:35, Greg Poirier <grep at binary-snobbery.com>
> wrote:
> > On Tue, Apr 12, 2011 at 7:15 AM, Luc Pionchon <pionchon.luc at gmail.com>
>
>> Another strong point is to get them into the gnome i18n loop,
> >> targeting at an uniform and coherent translation between addins and
> >> tomboy.
>

Okay, this seems to require a few things:

1) All add-ins have to be written with l10n in mind, i.e. coding using the
gettext catalog and their strings must end up in the .po files.

2) All add-ins must use the same language style when originally written,
otherwise any chance of coherence is really.

3) The add-in repository _must_ be on git.gnome.org


> (*) In fact there are a bit more for maintainers to consider than just
> marking strings.
>

This would now be up to the add-in developers.


> banshee community extensions appear untranslated on my system. It
> feels like they are second class software.
>

The extensions are user contributions. They aren't maintained or developed
by the Banshee team, but by individual users. There are, of course, special
cases that end up becoming wildly successful, popular, and have developers
behind them that work well in tandem with the Banshee team, but that case is
rare. What I am trying to avoid is a situation where the Tomboy maintainers
are responsible for doing more than cursory evaluation of the quality of an
extension.

If one of the other maintainers wants to step up and proxy all of the add-in
commits, bugs, etc, that's fine. I am more interested in simply making the
code more readily and easily available in a centralized location.


> A grep gives me 51 languages for banshee, and 8 for community extensions.


I would assume that's because Banshee uses the Gnome Translation Project
(GTP), but the community extensions do not.


> It's not much about control, more about agreeing within the community.
> As you are renaming, it might be a good opportunity to initiate the
> discussion with the others applications that have plug-ons... Overall
> I think it's English that is lagging behind. Developers tend to care
> less. The translations I saw did their magic.


I can't argue with you here. I think it would be a good idea to look into
some kind of terminology standardization across GNOME. If anyone knows the
best forum in which to bring this up, I'd greatly appreciate the nudge.


> Southeastern is very relative :)
>
>
:) Of course. I am fairly new to the international scene. I, of course,
meant the Southeastern United States, where addin' would be "adding" without
the g... short for mathematics.


> So initially I meant that
> - It would be great if add-ins are (also) available through the
> distribution packages
>

I would prefer that they be a separate package, but yes.


> - It would be great if add-ins are included into the localization loop
>

This is I think what will be difficult. I do have an idea here, however:

I believe we can have our cake and eat it too with a little bit of setup on
our end. If we host the add-in repository on Gitorious, as Banshee does, and
then regularly synchronize that repository (say on a nightly basis) with a
git.gnome.org repository (either a new module or the tomboy module), then we
could allow commits from external sources as well allowing the add-ins to be
in the GTP loop.

If anyone knows of a reason NOT to do this, or why it wouldn't work, please
let me know. I can't think of a down-side, personally.

-- 
greg poirier
guy on phone: okay.  i'm at the corner of despair and mediocrity.  which way
do i go from here?
girl on other end: left.  despair should take you all the way to ponce.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.beatniksoftware.com/pipermail/tomboy-list-beatniksoftware.com/attachments/20110419/7f9895ea/attachment.htm>