FAD Fedora Warao 2013 startup

This is the main page for NAME_OF_EVENT, which is a FAD focused on TOPIC_OF_HACKATHON.

Purpose

1. Our purpose is to build Fedora Warao l10n/i18n team with the following primary goals:
   • Add Warao to glibc (wba)
   • Train translators
   • Setup infrastructure for new language wba including resources such as mailing lists, etc.
2. In addition, we will attempt to complete the following secondary goals as time allows:
   • Train on packaging to complement
   • Train on Fedora Documentation Project
   • Train on developing apps with l10n/i18n support.

Detailed Work Items & Final Attendees

• See FAD_Fedora_Talk_2009_game_plan

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

Plan

1. Location: Tucupita, Delta Amacuro State, Venezuela.
2. Dates: : February 21st-22th 2013
3. Schedule
   1. Day 1
      • Participants arrive at 9am February 21th
      • Introduction, welcome.
      • Warao in glibc, the starting point.
      • Building wba team in i18n/l10n.
      • Fedora infrastructure and resources build up.
      • Introduction to software translation
      • Transifex and Fedora
      • Participants leave at 5pm February 21th
   2. Day 2
      • Participants arrive at 9am February 22th
      • ¿Anaconda in Warao?
      • Deciding major pieces of software to start translating
      • Publican and Fedora Documentation Project, creating Fedora Documentation in Warao.
      • Participants leave at 5pm February 22th
4. Important skills (one or more)
   • skill
   • skill
   • skill
5. Personnel (people who might fit the bill)
   • Guillermo Gómez (Caracas/Venezuela, trainner) Confirmed? (Y/N)
   • Eduardo Echeverría (Valencia/Venezuela, trainner) 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 Community Architecture team. If you can find other ways to fund your FAD, that's great too!

Contributor	Dept	Arrv	Dept	Arrv	Cost
Guillermo Gómez	Travel to FAD, Feb.20th	Travel to FAD, Feb.20th	Travel from FAD, Feb.23rd	Travel from FAD, Feb.23rd	Ticket cost
Eduardo Echeverría	Travel to FAD, Feb.20th	Travel to FAD, Feb.20th	Travel from FAD, Feb.23rd	Travel from FAD, Feb.23rd	Ticket cost
Carlos Marcano	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