Re: BoF item 7/14: dead modules

2012-08-03 Thread Rūdolfs Mazurs
Hi all,

I don't think it would be good idea to base module death only on past
commits. Take galeon — it is rather actively translated, but Wikipedia
states it has been discontinued 3 years ago [1]. Even if we only
consider non-translation commits, there might be only bug fixes, that no
one wants to release.

The idea behind removing dead modules form D-L is to save translators
time, so it should be done quickly (ideally one day after final
release). Since galeon is replaced by epiphany, new releases are not
needed. So we should ask maintainer, if [s]he believes, if the software
is to see next release, when there are suspicions of dying software.

On the other hand, there might be other software, that is useful and
being used, but not actively developed, which should see translation
update releases, even if there is no maintainer.

[1] http://en.wikipedia.org/wiki/Galeon

C , 2012-08-02 22:05 +0200, Gil Forcada rakstīja:
 Hi all,
 
 As I said in previous mails, let this mail be a kickstart for giving
 feedback about the items that are defined on
 https://live.gnome.org/TranslationProject/Events/GTPBoFGUADEC2012 
 
 In this mail please give feedback about the dead modules item.
 
 Cheers,



signature.asc
Description: This is a digitally signed message part
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: BoF item 7/14: dead modules

2012-08-03 Thread Andre Klapper
On Fri, 2012-08-03 at 16:46 +0300, Rūdolfs Mazurs wrote:
 I don't think it would be good idea to base module death only on past
 commits. Take galeon — it is rather actively translated, but Wikipedia
 states it has been discontinued 3 years ago [1]. Even if we only
 consider non-translation commits, there might be only bug fixes, that no
 one wants to release.

25 commits in total in Galeon for the last two years:
  git log --after=2010-08-03 --pretty=oneline | wc -l
25 translation commits in Galeon in the last two years:
  git log --after=2010-08-03 --pretty=oneline -- po/ | wc -l
= 25 - 25 = 0. No single code commit.

 So we should ask maintainer, if [s]he believes, if the software
 is to see next release, when there are suspicions of dying software.

Yes, but this will require a lot of work, plus a careful wording, as
“there's no point at which he [a maintainer] consciously realizes that
he can no longer fulfill the duties of the role” (Karl Fogel: Producing
Open Source Software, page 216).

 On the other hand, there might be other software, that is useful and
 being used, but not actively developed, which should see translation
 update releases, even if there is no maintainer.

Indeed a module can be small, well-defined, considered feature-complete,
and very mature, so code changes are not needed. 
It does not necessarily have to be obsolete/deprecated/legacy just
because there is no activity.

andre
-- 
mailto:ak...@gmx.net | failed
http://blogs.gnome.org/aklapper

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: BoF item 3/14: Outreach

2012-08-03 Thread Andre Klapper
Concentrating on one aspect in this message:
Outreach for languages where we do not have any activity.
This would require progress on step 13 first (identifying dead teams).
I once wrote a draft for an email and actually used in privately to
contact some team leaders last year:
https://live.gnome.org/AndreKlapper/ContactingTranslationTeams
Additions, editing, comments are welcome.

My feeling though is that we (instead of the maintainer) should try to
do the outreach once it's clear that the language team is not active,
because if the team members didn't have time or care about translating
GNOME, why should they have time or care about finding people to
translate GNOME? :)

andre
-- 
mailto:ak...@gmx.net | failed
http://blogs.gnome.org/aklapper

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: BoF item 13/14: translation team inactive

2012-08-03 Thread Andre Klapper
Data could be gathered by having a complete git checkout and using git
log iterating over /po/xy.po files. I tried this in 2010:
http://people.gnome.org/~aklapper/guadec2010/git-translations.sh
My coding skills are lousy as you can easily spot, but maybe it provides
an idea. :P
Results (number of commits per language file in the last two years) are
available for each team at the bottom of
http://people.gnome.org/~aklapper/guadec2010/git-translations.ods

We probably need agreement when to consider a team as in a dangerous
situation (potentially inactive).
Proposing after 8 months without a commit (so we would not lose two full
release cycles if contacting and trying to do outreach).

andre
-- 
mailto:ak...@gmx.net | failed
http://blogs.gnome.org/aklapper

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: BoF item 4/14: Splitting modules

2012-08-03 Thread Johannes Schmid
Hi!

See https://live.gnome.org/TranslationProject/SplittingModules

Overall we wanted to base the Supported language status on having
translated at least 80% of Core, Core Apps, Extra Apps and
Accessibility. Furthermore, we *might* want to create a Basic Support
status for having translated Core and Core Apps to give more motiviation
to small teams.

We still need feedback if there are any UI strings in the Libraries
section that are shown to the user. (Excluding cryptic error messages
and properties displayed in glade).

Regards,
Johannes

Am Donnerstag, den 02.08.2012, 22:04 +0200 schrieb Gil Forcada:
 Hi all,
 
 As I said in previous mails, let this mail be a kickstart for giving
 feedback about the items that are defined on
 https://live.gnome.org/TranslationProject/Events/GTPBoFGUADEC2012 
 
 In this mail please give feedback about the Splitting modules item.
 
 Cheers,
 -- 
 Gil Forcada
 
 [ca] guifi.net - una xarxa lliure que no para de créixer
 [en] guifi.net - a non-stopping free network
 bloc: http://gil.badall.net
 planet: http://planet.guifi.net



signature.asc
Description: This is a digitally signed message part
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: BoF item 4/14: Splitting modules

2012-08-03 Thread Chris Leonard
On Fri, Aug 3, 2012 at 1:46 PM, Johannes Schmid j...@jsschmid.de wrote:
 Hi!

 See https://live.gnome.org/TranslationProject/SplittingModules

 Overall we wanted to base the Supported language status on having
 translated at least 80% of Core, Core Apps, Extra Apps and
 Accessibility. Furthermore, we *might* want to create a Basic Support
 status for having translated Core and Core Apps to give more motiviation
 to small teams.

 We still need feedback if there are any UI strings in the Libraries
 section that are shown to the user. (Excluding cryptic error messages
 and properties displayed in glade).

Johannes,

One of the main reasons I've mentioned the OLPC Release Set

http://l10n.gnome.org/releases/olpc/

as a potential starting point for localizers is that it represents the
Gnome packages that are pulled down by OLPC (typically via Fedora RPM
repos) to create the Gnome side of the Sugar/Gnome dual-boot OS image,
as well as a few Gnome core infrastructure modules that lay a little
deeper in the stack of what is a fairly minimalist GNU/Linux Fedora
spin.

It's value as a point of comparison is not so much that it is want is
needed for an OLPC XO laptop, but rather that it is a module
collection that has been culled down by intense size pressures (one GB
total storage on an XO-1) and therefore is one specific example of a
minimal set.

I've done my best to keep the packages displayed in the OLPC Release
Set current by going through the packages.txt file in OLPC releases as
they become available, a pending major release by OLPC is complicating
this a little at the moment.  I should explain that at the present,
time while there is an ongoing transition from GTK2 to GTK3 in the
Sugar / OLPC OS stack, I have chosen to only point to the GTK3 master
branch versions of packages.  This release set is intended to be more
forward-looking in terms of L10n needs/wants and not necessarily about
back-filling translations on existing releases, although the reality
of the situation is that an OLPC release will likely be one or more
release cycles back from Gnome master when it goes out the door given
that it largely draws from Fedora RPM repos and lags the Fedora
release cycle.

Taking a look at the libraries (or other packages)  included in the
OLPC release set might give you some ideas about what it might be
worth including in a priority L10n target set.  You will need to take
into account that given it's focus on children in the educational
setting, the inclusion of things like gcompris are driven because they
are educational games and not because they are needed to make a
minimal Gnome desktop sign and dance.

Just a thought for your consideration.  Consider it one downstream's
very-specific POV as measured by the packages pulled from Gnome.

cjl
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


String additions to 'gnome-user-share.master'

2012-08-03 Thread GNOME Status Pages
This is an automatic notification from status generation scripts on:
http://l10n.gnome.org.

There have been following string additions to module 'gnome-user-share.master':

+ If this is true, Bluetooth devices can send files to the user's Downloads 
directory when the user is logged in.
+ If this is true, the Public directory in the user's home directory will 
be shared over Bluetooth when the user is logged in.
+ If this is true, the Public directory in the user's home directory will 
be shared over the network when the user is logged in.
+ Unable to launch the Personal File Sharing Preferences

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.
http://git.gnome.org/browse/gnome-user-share/log/?h=master
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: BoF item 11/14: improvements to D-L

2012-08-03 Thread Fran Dieguez

Hi!,

I'been working in D-L, mostly learning Django for helping more in the 
future.


I wrote the wiki page https://live.gnome.org/DamnedLies/NewTheme for 
contacting with the Design theme and try to get them involved in the 
design.
You can checkout the code from the D-L repository in the branch 
newtheme:

http://git.gnome.org/browse/damned-lies/log/?h=newtheme

Next week I have some spare time and I will work more in D-L.

Cheers.

On Xov 02 Ago 2012 22:05:48 CEST, Gil Forcada wrote:

Hi all,

As I said in previous mails, let this mail be a kickstart for giving
feedback about the items that are defined on
https://live.gnome.org/TranslationProject/Events/GTPBoFGUADEC2012

In this mail please give feedback about the improvements on D-L item.

Cheers,




--
Fran Diéguez
http://www.mabishu.com
GPG: 43DD 1B00 035F A764 4986  E695 98BB 6626 A2A4 F9B8
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n