FAD G11N 2015

This is the main page for the 2015 I18n Team FAD, which is a FAD (a mini-conference) focused on working on Fedora 24 development plans, brainstorming on Fedora globalization workflow and deciding strategy for Fedora different products.

Purpose

Fedora internationalization group has spread across the regions. We would like to propose 3 days of FAD and we would like to do following activities/tasks.

Task list:

• Fedora globalization
  • synchronize l10n, i18n and Zanata.
• Deciding g11n mission in the rise of Fedora.Next products. Workstation, Server and Cloud.
• Fedora 24
  • Development plans
  • Change proposals
• Test day improvements plan.
• Listing out Fedora language support status. Crosscheck with (CLDR or Wikipedia list)
• Deciding on Fedora locale related default fonts selection procedure.
• Working on Glibc locale-archive split into different locales.
• Identifying and Filling missing bits of "How to loosely organize a community"

Impact

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

• Synchronization between 3 groups i18n, zanata and l10n under the globalization initiative.
• Test day improvement. Better planning, more relevant test case and more contribution on testday.
• Globalization plans for Fedora products Workstation, Server and Cloud by understanding there requirements.

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

• Fedora.Next initiative :- Understanding and planning for globalization requirement of different products.
• Creating a Free (as in Freedom) distribution
  • Produce robust time-based releases every six months :- Development plans just after F23 will help to complete change proposals well in F24 release cycle.
• Building open source software communities
  • Be on the leading edge of free and open source technology :- Fedora distribution has been remained leading the globazation development. Most of innovations first happens into Fedora and then other distribution adopts it. Example. IBus, Locales, Predictive text input method and Various fonts.
• Promote a global perspective by supporting as many languages and geographic locales as possible
  • We will identify Fedora present situation from language support and will plan to cover more languages.
• Developing the science and practice of building communities
  • Use existing models that work, (re)building on them only as needed in each case :- i18n, l10n and zanata groups already doing most of the things out of this. Going through this can provide more inputs on how can we build more community around it.

Detailed Work Items & Final Attendees

Name	Remote/Local/Travel	Thu	Fri	Sat	Core Tasks
Pravin Satpute	Travel				FAD Organizer + Documentation + Development
Jens Petersen	Travel				Development
Peng Wu	Travel				Development
Akira TAGOH	Local				Development
Parag Nemade	Travel				Development
Alex Eng	Remote/(Travel if possible)				Zanata
Takao Fujiwara	Local				Development
[Your Name Here]

Planning Prerequisites

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

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

Plan

1. Location: Tokyo, Japan
2. Date: 5-7th November, 2015
3. Schedule TBD
4. Thursday Schedule

Time	Scheduled activity

1. Friday Schedule

Time	Scheduled activity

1. Saturday Schedule

Time	Scheduled activity

1. • Participants arrive at THIS_TIME_AND_DATE
   • PravinS arrive on xyz date
   • Will add other people who are traveling
   • Participants leave at THIS_TIME_AND_DATE
   • PravinS leave on xyz date
2. Important skills (any of the following)
   • Fonts
   • IME (IBus, SCIM)
   • Encoding (Unicode)
   • CLDR.
   • Language experts.
3. 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?
4. 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!

Attendee	Status	Arrival	Departure	~Travel cost	Hotel	Notes	Funding request (US $)
1. Pravin Satpute	Still Planning

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: Will use redhat facility in planned location.
   • address and travel details for the space
4. Supplies:
   • Not presently.

Total budget: $(A+B)