FAD Documentation Managua 2013

In other languages: English (en) español (es) português do Brasil (pt-br) [edit]

Introduccion

The Fedora team at Nicaragua (can tell us FedoraNi) has been doing activities to improve the capacities of users to help them became collaborators with activities like Fedora School. This has include de very basic skills like FAS account, wiki editing to create profile, ssh connection, gpg keys, translation among other stuff. We like to spand the abilities of local collaborators to help Fedora Project. One of the voids that we have is local knowledge of documentation skills. We propose a FAD of Documentation with two objectives. First, built local expertise that can be shared. Second, practice completing or updating documents that need some work.

Purpose

1. Our purpose at organize this documentation activity day is to complete with these following goals:
   • Create a local documentation team.
   • Diversify the habilities of locar contributors

Persons interested in participating in the FAD

• Neville A. Cross
• William Moreno
• Eduardo Mayorga
• Your name
• Your name

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: Hotel Mansión Teodolinda
2. Date: Ago 17 y 18 2013
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 Community Architecture 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