From Fedora Project Wiki

Line 5: Line 5:
#* Create a strategy for latam ambassadors to improve their activities(events, meetups, enrollment process, etc) to align to new fedora objectives.
#* Create a strategy for latam ambassadors to improve their activities(events, meetups, enrollment process, etc) to align to new fedora objectives.
#* Create complementary rules for event organization/coordination, fund request, tickets management process and similar task.
#* Create complementary rules for event organization/coordination, fund request, tickets management process and similar task.
#* Establish procedures for the planning of budgets according to the last changes in the fedora project.
#* Establish a internal council for meeting chairing and their work rules.
#* Establish a internal council for meeting chairing and their work rules.
#* Establish a ticket reviewer, their work rules and ticket review criteria.
#* Establish a ticket reviewer, their work rules and ticket review criteria.
Line 10: Line 11:
#* Establish a strategy for swags production and distribution for all latam countries.
#* Establish a strategy for swags production and distribution for all latam countries.
#* Create strategies for reimbursement process for latam countries.
#* Create strategies for reimbursement process for latam countries.
#* Establecer eventos importantes en los que se deben de priorizar recursos y participación.
#* Establish criteria to prioritize important events to allocate resources.
#* Create a calendar of important events in Latin America (FLISOL, FISL, LATINOWARE, etc) and by individual countries.


== Impact ==
== Impact ==

Revision as of 00:43, 23 April 2017

This is the main page for Latam Ambassadors FAD, which is a FAD focused on Fedora Ambassadors internal organization.

Purpose

  1. Basically our purpose is create a work plan for Latam Ambassadors aligned to new Fedora Project objetives with the following primary goals:
    • Create a strategy for latam ambassadors to improve their activities(events, meetups, enrollment process, etc) to align to new fedora objectives.
    • Create complementary rules for event organization/coordination, fund request, tickets management process and similar task.
    • Establish procedures for the planning of budgets according to the last changes in the fedora project.
    • Establish a internal council for meeting chairing and their work rules.
    • Establish a ticket reviewer, their work rules and ticket review criteria.
  2. In addition, we will attempt to complete the following secondary goals as time allows:
    • Establish a strategy for swags production and distribution for all latam countries.
    • Create strategies for reimbursement process for latam countries.
    • Establish criteria to prioritize important events to allocate resources.
    • Create a calendar of important events in Latin America (FLISOL, FISL, LATINOWARE, etc) and by individual countries.

Impact

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

  • Tener un concejo que lleve las reuniones apropiadamente y se encargue de coordinar todos las actividades de los embajadores de latam.
  • Al establecer politicas complementarias se logrará mejorar el tiempo de aprobación de los tickets y la calidad de los mismos.
  • Las estrategicas que se elaboren deberan hacer crecer la comunidad tanto en cantidad de participantes como en participacion activa y productiva.

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


Detailed Work Items & Final Attendees

Participants

Name Remote? Country
Alex Irmel Oviedo Solis Peru
Aly yuliza Machaca Mamani Peru
Bernardo Hermitaño Peru
Tonet Jallo Peru
Renne Lujano Peru
Itamar Reis Peixoto Brasil
Athos Coimbra Ribeiro Brasil
Abdel Martinez Panama
Neville Cross Nicaragua
Eduardo Echeverria Colombia
Edwind Richzendy Contreras X Venezuela
Antonio Salles Chile
Fredy Condori Bolivia
Adrian Soliard Argentina
Brian Exelbierd EEUU

Schedule

Thursday, 2017-06-XX

Time Speaker Talk / Activity Details
09:00 - 09:30 Organizing team Reception of attendees
09:30 - 09:45 Alex Oviedo Presentation and welcome talk
09:45 - 10:00 All attendees Self introduction Every attendee should introduce himself (name. nickname, country, etc)
10:00 - 11:00 Brian Exelbierd Introduction to Fedora* Introduce to the fedora community and their new objetives and policies.
11:00 - 12:00 Someone here Work session 01: Complementary rules (Diagnostics) Present a diagnostic based on current rules about amounts, process, etc
12:00 - 13:00 All attendees Work session 01: Complementary rules (Proposals review) Show and discuss proposals.
13:00 - 15:00 LUNCH LUNCH LUNCH
15:00 - 15:30 All attendees Work session 01: Complementary rules (Proposals review) Show and discuss proposals.
15:30 - 16:00 All attendees Work session 01: Complementary rules (Approval of proposals)
17:00 - 18:00 Someone here Talk Talk for all people
18:00 - 19:00 Someone here Talk Talk for all people

Friday, 2017-06-XX

Time Speaker Talk / Activity Details

Saturday, 2017-06-XX

Time Speaker Talk / Activity Details

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: Colegio de Ingenieros del Peru - Sede Departamental Cusco
  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