Minutes of G11N (i18n focused) meeting - 2015-12-09
by pravin.d.s＠gmail.com
Hi All,
We had good meeting today. Minutes are as follows.
=====================
#fedora-meeting: g11n
=====================
Meeting started by pravins at 06:02:58 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2015-12-09/g11n.2015-12-0...
.
Meeting summary
---------------
* agenda and roll call (pravins, 06:03:06)
* LINK: https://fedoraproject.org/wiki/I18N/Meetings/2015-12-09
(pravins, 06:03:06)
* LINK: https://admin.fedoraproject.org/voting/open (pravins,
06:04:58)
* Upcoming schedule (pravins, 06:07:12)
* 2016-01-12 Change Checkpoint: Proposal submission deadline
(System Wide Changes) (pravins, 06:07:26)
* not scheduled yet Side Tag Builds Deadline (pravins, 06:07:26)
* not required Mass Rebuild (pravins, 06:07:26)
* 2016-02-02 Branch Fedora 24 from Rawhide (Rawhide becomes future
F25) (pravins, 06:07:26)
* 2016-02-16 Alpha Freeze (*) (pravins, 06:07:26)
* 2016-02-16 Software String Freeze (pravins, 06:07:27)
* 2016-02-16 Change Checkpoint: Completion deadline (testable)
(pravins, 06:07:29)
* 2016-02-16 Bodhi activation point (pravins, 06:07:31)
* Outstanding task (pravins, 06:10:03)
* #36: gnome redesign plans for control-center Region and Languages
(anishpatil) (pravins, 06:10:03)
* LINK: https://fedorahosted.org/i18n/ticket/36 (pravins, 06:10:03)
* LINK: https://bugzilla.gnome.org/show_bug.cgi?id=756939 (pravins,
06:11:34)
* ACTION: anish_ to update bug report to disable xkb layouts for
Indian language in gnome. (pravins, 06:11:59)
* New topics (pravins, 06:12:09)
* #43: G11N FAD in 2015 (pravins) (pravins, 06:12:16)
* LINK: https://fedorahosted.org/i18n/ticket/43 (pravins, 06:12:16)
* ACTION: pravins to work this week for G11N FAD summary post on
community blog. (pravins, 06:16:27)
* #57: Fedora 24 change planning (pravins) (pravins, 06:18:13)
* LINK: https://fedorahosted.org/i18n/ticket/57 (pravins, 06:18:13)
* mfabian has moved glibc_subpackaging change proposal to Fedora 24.
(pravins, 06:22:27)
* LINK:
https://docs.google.com/document/d/17LU-PmtuirbGd7wfxUuKTz7X6fsv82PVPgZaD...
(pravins, 06:25:25)
* fujiwarat to rename bin/ibus-fbterm and bin/ibus-fbterm-launch to
libexec/ibus-fbterm-backend and bin/ibus-fbterm. (pravins,
06:33:44)
* IDEA: PoC of NextGen G11n workflow (Jens/Zanata?) (pravins,
06:34:05)
* IDEA: Automatic testing (Akira) (pravins, 06:34:14)
* IDEA: Description support of the configuration in fontconfig (Akira)
(pravins, 06:34:21)
* #58: Prioritizing bugs for Fedora 24 release (pravins) (pravins,
06:40:32)
* LINK: https://fedorahosted.org/i18n/ticket/58 (pravins, 06:40:32)
* LINK:
https://fedoraproject.org/wiki/G11N/Fedora_24_G11N_Enhancements
(pravins, 06:41:27)
* ACTION: Every i18n members to find some bugs from dashboard and add
if for Fedora 24 planning page. (pravins, 06:53:24)
* New task (pravins, 06:53:45)
* #56: Fedora 21 EOL Bugs triaging (pravins) (pravins, 06:53:46)
* LINK: https://fedorahosted.org/i18n/ticket/56 (pravins, 06:53:46)
* ACTION: pravins to close F21 EOL triage ticket with list of bugs
closed without any triaging. (pravins, 07:00:03)
* Open Floor (pravins, 07:00:22)
Meeting ended at 07:09:45 UTC.
Action Items
------------
* anish_ to update bug report to disable xkb layouts for Indian language
in gnome.
* pravins to work this week for G11N FAD summary post on community blog.
* Every i18n members to find some bugs from dashboard and add if for
Fedora 24 planning page.
* pravins to close F21 EOL triage ticket with list of bugs closed
without any triaging.
Action Items, by person
-----------------------
* pravins
* pravins to work this week for G11N FAD summary post on community
blog.
* pravins to close F21 EOL triage ticket with list of bugs closed
without any triaging.
* **UNASSIGNED**
* anish_ to update bug report to disable xkb layouts for Indian
language in gnome.
* Every i18n members to find some bugs from dashboard and add if for
Fedora 24 planning page.
People Present (lines said)
---------------------------
* pravins (165)
* juhp (31)
* zodbot (19)
* fujiwarat (9)
* mfabian (3)
* epico (3)
* suanand (1)
* paragan (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Regards,
Pravin
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 4 months
L10N String Breakage monitoring
by pravin.d.s＠gmail.com
Hi all,
Bringing this topic from meeting discussion to mailing list for
wider audience.
Often after completion of translation package get updated with more
string or sometime translated .po file does not get pulled while
building package. This causes L10N string breakage.
Anaconda is major candidate where we fail often with string breakage.
We started this discussion in Fedora 23. Now we are thinking how we
could monitor this better. Following are some initial discussions
happened in G11N meeting. Just though to share with you all :)
Regards,
Pravin Satpute
05:17:28 <pravins> #idea String Breakage monitoring (Jens, Akira)
05:18:01 <pravins> juhp: tagoh_ any further idea on this.
05:18:14 <pravins> I think we are tracking in i18n side.
05:19:20 <pravins> We did not had any discussion last time, since juhp
and tagoh_ both were not available :)
05:19:25 <juhp> I have been thinking about it a little...
05:19:37 <tagoh_> not started to work on that but we know where
upstream repo is from zanata. it could be used to check by comparing
the POT in zanata and upstream?
05:20:08 <pravins> nice idea.
05:20:24 <pravins> How about discussing this as well in mailing list?
Even devel list is fine i think.
05:20:54 <juhp> my current idea is to try track koji builds for some
specific packages looking for string changes
05:21:36 <fujiwarat> upstream is unstable.
05:21:55 <juhp> part of it might be also tracking out of date POT/po files
05:21:59 <pravins> umm, to me comparing .pot periodically or with
script looks more promising.
05:22:33 <pravins> #idea String breakage monitoring - 1. Comparing POT
in Zanata and upstream.
05:22:43 <aeng> how often do we check?
05:22:55 <pravins> We do not
05:23:01 <aeng> or plan to do the comparison?
05:23:16 <tagoh_> assuming that they are properly branching and link
to zanata. if it doesn't work, they might use zanata wrongly I
suppose.
05:23:57 <pravins> aeng: that is idea proposed by tagoh_ and juhp ,
to have some script or automation.
05:24:23 <juhp> what is in zanata might not be in fedora though
05:24:29 <aeng> yup
05:24:45 <pravins> #idea String breakage monitoring - 1. Track Koji
builds for some specific packages looking for string changes.
05:24:48 <tagoh_> juhp: right. so need to pick up projects we want to
keep on track
05:25:06 <juhp> aeng, I would suggest daily or whenever there is a
build - depending on the approach we take
05:25:16 <pravins> as we discussed Anacodda is major candidate here :)
05:25:31 <juhp> tagoh_, ah no - I mean strings in zanata might not be
in fedora :)
05:25:44 <juhp> additionally we might want to track projects not in Zanata
05:26:16 <aeng> so the script might need to be dynamic enough
05:26:25 <juhp> but leveraging zanata for this certainly also makes
some sense :)
05:26:52 <juhp> or maybe we should look at both zanata, upstream and
package content
05:27:06 <juhp> aeng, yeah
05:27:13 <tagoh_> juhp: what is the original POT to compare then?
checking on the buildsys would need a cache to check right?
05:27:41 <juhp> tagoh_, right so the script might have to
generate/cache POT files even
05:28:23 <juhp> but if we really what to track fedora string breakage
then seems to me we need to look at what is actually in Fedora
05:29:51 <juhp> also s/breakage/changes/
05:30:16 <pravins> yeah, comparing with Fedora make sense
05:30:23 <tagoh_> hm, that said those translations are coming from zanata :)
05:31:30 <tagoh_> and detecting on the build time doesn't address
anything. we can just know "they broke it again".
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 4 months
Reminder: Fedora G11N meeting focused on I18N tomorrow @ 06:00 UTC
by Pravin Satpute
Hi all,
We have meeting tomorrow At #fedora-meeting (Freenode). Agenda is
available at [1].
Action items, by person from 25th Nov meeting
1. anish_
1. anish_ to update bug report to disable xkb layouts for Indian
language in gnome.
2. epico
1. paragan ueno epico tagoh___ to triage open bugs for Fedora 21.
3. fujiwarat
1. fujiwarat to set deadline for "Merge IBus fbterm into ibus core"
4. paragan
1. paragan to create ticket for Automation of langpack LiveCD for
better tracking status.
2. paragan ueno epico tagoh___ to triage open bugs for Fedora 21.
5. pravins
1. pravins to ask all FAD attendees for summaries and reports.
2. pravins to work on Collaborating summary post on G11N Fedora
activities day.
3. pravins to drop email on i18n list with all missed idea for F24.
4. pravins to create Wiki for listing bugs for Fedora 24.
5. pravins to drop email on i18n list with open bugs
6. ueno
1. paragan ueno epico tagoh___ to triage open bugs for Fedora 21.
7. *UNASSIGNED*
1. All FAD attendees to upload report/summaries blog link on ticket #43
2. Everyone to select few bugs from Bug list for Fedora 24
development cycle.
3. resolve "Questions on Translation work flow for Fedora Website"
by Next week G11N meeting.
Thanks,
Pravin Satpute
1. https://fedoraproject.org/wiki/I18N/Meetings/2015-12-09
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 4 months
Short summary on G11N FAD @ Tokyo - Activities & Experience
by Ani Peter
Dear All,
I have been fortunate to be part of the Indian L10n communities since
almost 10 years and have got the opportunity to attend many community
events around the globe. G11N FAD 2015 in Tokyo from Nov 1-3, 2015 was
one of the best and memorable event I have ever attended in my life.
Fedora and the g11n activities are always closed to heart and we, team
members, communicate with each other over email or IRC. This is the
first time we ever got to meet many of the members in person and discuss
on many different issues, ideas, project plans etc and finalize in just
no time.
We had 3 full packed days discussing on the items listed here [1]. From
the initial preparations for this meet till last day at Tokyo was very
exciting. We used to meet almost daily to finalize the agenda, plan the
schedule and thus was able to make this event a success with the
collective effort of many. I would like to take this opportunity to
thank Jens-san and Pravins for making this possible.
I would like to share the summary of my activities and contributions at
the G11n FAD meet.
_*DAY 1*_
Met all the participants in the morning in front of Red Hat Tokyo
office, many of them the first time after working together for 10 years,
and I would say one of the happiest moment during the FAD. The day began
with introductions and updating the status of our work & contribution to
G11N. Noriko and I presented the Fedora L10n status with a short
presentation listing the points to be discussed [2]. I have strongly
raised the importance of having L10n focused events and sprints to
promote and increase Fedora translations & localization. We mostly spend
this day discussing and preparing the requisites for the G11N wiki page.
Noriko (L10n), Alex (Zanata) and I sat down together to prepare the G11N
presentation slide, which is very generic and anyone from the G11N team
can use these slides for their presentations at different community
events. Later sat down with Michelle and Pravin to discuss on how we
can popularize this and make videos or slide shows to improve the wiki
home page. Later in the evening, we enjoyed the hangout talk with
Cambodian team who had localization sprint for Khmer language. They
shared their experience and we suggested them on how to promote the idea
of conducting more online and localization sprint events to improve
Fedora in different local languages and improve the quality of translations.
_*DAY 2*_
The second day began with the hangout talk with Fedora Project Leader,
Mathew Miller. It was interesting to hear from him and share each others
idea to improve and promote Fedora. Later, joined the discussion on
introducing new FGSco structure proposal to strengthen the G11N team,
increasing participation from L10n, I18n, QE and Zanata. This discussion
is to be continued during the g11n monthly meetings to finalize the plan
with the community members and implement it.
Post lunch, I was with Alex and Carlos Munoz to discuss and analyze the
feedback collected from the latest Zanata survey [3]. Luke Brooker had
sent us the feedback consolidated together which helped us to discuss
and decide on the action plans for various items. We ended the day with
an awesome team dinner at Local India near to the office and had a
wonderful the evening.
_*DAY 3*_
Third day was entirely utilized for Fedora Localization & QA (FLTG)
related discussions. Michelle, Noriko and I were together to determine
the important packages to localize and be tested during the QA activity
days. We always missed a pointing place for new joiners or translators
where they can find the most important or essential packages to be
translated. This was finalized in this discussion. Parag helped us to
sort out some confusions regarding the final list of packages. Later,
post lunch we moved to the 'Software deadline change for F24' discussion
which was raised by Noriko. We had rigorous discussions on various
points like changing deadline proposals etc, but finally arrived at a
consensus for no-go to this proposal. We have decided to keep watch on
how the existing proposal really affects the packages & the translations
and also I18N members will start seeking and developing a script to
auto-detect string breaks. L10n members to monitor the breaks and
generate statistics, based on which we can take a call on this proposal
later after the next release.
Towards the end of the day, all the attendees were to present a summary
of the activities done during the FAD. An important task I have taken up
is to prepare the proposal for Fedora L10n sprints and drive it . We
were able to start all the days on time and were on schedule and thus
well organized, which helped us to complete discussing all items listed
in the agenda.
The hospitality and homely atmosphere in Tokyo made all of us
comfortable and enjoy the meet. I enjoyed my stay in Tokyo and glad
could meet some of the best people. Weather was also in our favor.
Apologies for submitting the report very late. But better late than
ever. Now its action time and need to implement many things that we have
discussed and decided during the FAD. Looking forward to work with the
team to make the Fedora G11N efforts to a success
Thanking you
Best regards
Ani
[1]:
https://docs.google.com/document/d/17LU-PmtuirbGd7wfxUuKTz7X6fsv82PVPgZaD...
[2]:
https://docs.google.com/presentation/d/12Ffl1fRnLWahtmrvDCWEdgr671doJWjS3...
[3]:
https://lists.fedoraproject.org/archives/list/g11n%40lists.fedoraproject....
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 4 months