FAD I18N 2017

This is the main page for the 2017 Internationalization (i18n) Group FAD, which is a FAD (a mini-conference) focused on working on Fedora 27 development plans, Resolving open bugs and analysis of activities done for F25/F26 and deciding strategy for different Fedora products.

Purpose

Fedora G11N group had first ever in Nov 2015. It was huge and successful FAD, summary is available in Docs. Thanks to support from Fedora Council and Also Red Hat G11N group for budget. Though we called it as a FAD but it went like mini-conference with many more domain experts participation.

Though we had good G11N FAD but it also increased total budget. This time due to budget restriction, we are thinking to have individual FAD's. This FAD page is for i18n FAD. I am expecting soon proposal for Translation FAD mostly somewhere in EMEA.

Primary Goals

Long term direction for Fedora internationalization

Fedora project is witnessing number of different kind of developments activities across different project. Namely Server, Cloud and Workstation. History shows i18n group has been more closely interacted with Workstation group activities only. I18N has wide scope and for every project thought must be given for its internationalization. It brings up two option

• Participate in the development from the beginning
• Provide guidelines to be followed during start of the projects.

Discussing on this line and deciding direction for i18n.

Fedora 27+ development plans

G11N FAD Nov 2015 was happened around the release of Fedora 23. Planning did in this FAD helped to whole G11N group not only for Fedora 24 but also for Fedora 25. FAD is ideal place for discussion on future developments plan and brainstorming. This planning will help for at least Fedora 27, 28 and may be for 29 as well.

• Fedora 27
• Fedora 28

Participation in Fedora programs like Outreachy, GSoc

Participating in this program by adding open projects and guiding students for understanding and motivating to be long time i18n contributors.

Glibc and Unicode CLDR sync

Unicode CLDR is growing and well adapted by almost all major OS. Glibc still maintaining its own localedata and time has come to sync it with Unicode CLDR. Definitely Glibc dont want to be huge resource for locale like Lib ICU but minimal locale data as Glibc doing presently.

This has been long pending task and need to do initial architecture for this.

Flatpack and i18n

There has been some offline discussions about this during DevConf. Planning for further dig down into it.

NGEN achitecture for G11N

This discussion started during FAD 2015. Couple of ideas were discussed by participants but never took off due to other high priority task. Fedora has been always remained pioneer in implementing innovative changes.

Secondary Goals

• Reviewing outputs from FAD 2015.
• Bug triaging.
• Social gathering

Impact

The completion of these goals will create the following positive change within the project:

• Innovative change proposals for upcoming Fedora releases.
• More wider coverage of Fedora products from i18n.
• More participation of i18n group in programs like GSoc and Outreachy.

These outcomes connect with the following Fedora Community Objectives by explain connection here.

• University Involvement Initiative
  • With drafting projects to participate in GSoc and Outreachy it can help to get more involvement from University involvement.
• Fedora Modularization
  • Upcoming developments plan's are going to aligned with modularization.
• Building open source software communities
  • This is connected with the Be on the leading edge of free and open source technology and Promote a global perspective

Detailed Work Items & Final Attendees

Name	Remote/Local/Travel	Sun	Mon	Tue	Core Tasks
Pravin Satpute	Travel	yes	yes	yes	Organizer + Documentation + Development
Sundeep Anand	Travel	yes	yes	yes	Documentation + Development
Jens Petersen	Travel	yes	yes	yes	Development
Parag Nemade	Travel	yes	yes	yes	Development
Add Your Name	--	--	--	--	Role+Tasks

Planning Prerequisites

See the How to organize a FAD list; you can keep your to-do list here.

• Completed work item
• Work out budget
• Decide on Dates and Location
• Arrange Facilities
• List Resources
• Be Somewhat Structured
• Arrange Lodging
• Arrange Refreshments
• Arrange a Social Event
• Another action item
• Another action item
• Another action item

Time and Place

• Location: Not finilized yet. Tentative list as follows
  • Singapore
    • Central to all participants and less travel cost.
  • Pune, India
    • More local contributors, Office facility
  • Tokyo, Japan
    • Huge i18n demands, local contributors, Office facility
  • Brisbane, AUS
    • More local contributors, Office facility

• Date: In between Sept-Nov 2017.

Plan

1. Location:
2. Date:
3. Schedule
   • Participants arrive at THIS_TIME_AND_DATE
   • Schedule item
   • Schedule item
   • Schedule item
   • Participants leave at THIS_TIME_AND_DATE
4. Important skills (one or more)
   • skill
   • skill
   • skill
5. Personnel (people who might fit the bill)
   • Name (location, role) Confirmed? (Y/N)
   • Name (location, role) Confirmed? (Y/N)
   • Name (location, role) Confirmed? (Y/N)
   • others?
6. Other considerations
   • Contributor V can offer a living room for evening social gatherings.
   • Contributor W has a car and is willing to do airport pick-ups.
   • Contributor X needs as much advance notice as possible.
   • Contributor Y has a schedule that is better on Fridays than on Tuesdays, and prefers weekend times after 4:28 AM.
   • Contributor Z is allergic to peanuts.

Logistics

Snacks/Beverages: Details go here.

Lunch: Details go here.

Dinner: Details go here.

Budget

If you want funding from Red Hat, ask the OSAS team. If you can find other ways to fund your FAD, that's great too!

Contributor	Dept	Arrv	Dept	Arrv	Cost
Name	Travel to FAD, departure	Travel to FAD, arrival	Travel from FAD, departure	Travel from FAD, arrival	Ticket cost
Name	Travel to FAD, departure	Travel to FAD, arrival	Travel from FAD, departure	Travel from FAD, arrival	Ticket cost
Name	Travel to FAD, departure	Travel to FAD, arrival	Travel from FAD, departure	Travel from FAD, arrival	Ticket cost

1. Travel: $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
2. Housing: $B for hotel, etc. needed to have attendees sleep during the FAD
   • link to hotel room booking website, if applicable
3. Space: $C for renting space to hack in, if applicable
   • address and travel details for the space
4. Supplies: $D for anything else you may need
   • item
   • item
   • item

Total budget: $A+B+C+D