From Fedora Project Wiki
mNo edit summary
m (Move ref 2 to a better location)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{header|ambassadors}}
{{header|ambassadors}}
{{lang|en|page=Ambassadors/Latam/EventOrganizationGuideLine}}
{{autolang|base=yes}}
= Event Organization Guidelines =


== ¿Por qué una guía de eventos? ==
== Why an event Guideline? ==


Following these simple steps will allow us to help you have the most successful event possible.  If you skip any of the steps it is harder for us to help you.  If you are asking for funding, it is critical that you complete all of the steps or we will not be able to fund your event.


Seguir estos simples pasos nos permitirá ayudarte a tener el evento más exitoso posible. Si te saltas alguno de estos pasos, será más difícil para nosotros ayudarte. Si estás pidiendo fondos (financiamiento), es crítico que sigas todos los pasos o no estaremos en la capacidad de financiar tu evento.
== Tasks ==
=== Pre-event tasks ===


== Tareas ==
Ambassadors (or other subproject contributor that wants to be sponsored by the Fedora Ambassadors) needs to do the next steps BEFORE the event:
=== Tareas pre-evento ===


Los embajadores (o colaboradores de otros subproyectos que pretenden recibir patrocinio de Fedora Project) deberán realizar los siguientes puntos antes del evento:
# Create a wiki page for the event in the [[Events/Latam| new structure]]: Create a wiki page providing general information about the event in the Fedora Project wiki. We suggest you to use the templates <ref>We are working in the template, trying to improve it and locate it in a better place in the wiki</ref>. Doing the wiki page, you will help us:
## Know about the event
## Help future collaborators to participate/help/attend to the event
## Make measurement/statistics
# Create a ticket (In your region pagure.io): If you are asking for Fedora Project's sponsorship, it's absolutely necessary to create a new ticket/issue pagure.io. The ticket must be created, at least, 3 days before the next meeting ([https://apps.fedoraproject.org/calendar/ambassadors| Fedora Ambassadors Regional Meetings @ FedoCal]) to be discussed, and must contain the "meeting" tag to be considered on the agenda. If the ticket is for requesting funds, we suggest you to wait until your ticket gets approved to start expending money. In special cases (Great and important events announced out of the time rule mentioned before) we suggest to use a special tag (meeting+openFloor),to discuss this ticket if meeting time allows the discussion. Please take into consideration that these kind of tickets may not be discussed if there is no time.
# Add the event to the [https://apps.fedoraproject.org/calendar/Events/| FedoCal] (linking to the wiki page of the event)


# Crear página wiki del evento <ref>Se está trabajando en la estructura de la ubicación de dichos eventos</ref>
=== Post-event Tasks ===
# Crear una página que contenga información general del evento en la wiki de Fedora Project. Sugerimos usar los templates <ref>Se está creando un nuevo template, mejorado y mejor ubicado en la wiki</ref>. Haciendo la página wiki del evento nos ayudaras a:
# Event Reports<ref>Consider that even if you aren't requesting sponsorship, Event reports are really useful to the project.</ref>:
## Conocer de qué se trata el evento
## Owner @ CommBlog: The event creator must create an article in the [https://communityblog.fedoraproject.org/writing-community-blog-article/| CommBlog]
## Ayudar a futuros colaboradores a participar/ayudar/asistir al evento
## Attendees @ [https://fedoraproject.org/wiki/Planet| Planet]:
## Realizar métricas/estadisticas
### Ambassador attendees needs to create a report in their personal blog. This report needs to be linked to the planet [[Planet| Planet]].
# Crear un ticket ([https://pagure.io/ambassadors-latam/tasks/issues| pagure.io]): Si se requiere el patrocinio de Fedora Project, es absolutamente necesario crear un ticket (issue) en pagure.io. El ticket deberá ser creado, como mínimo, 3 días antes de la próxima reunión ([https://apps.fedoraproject.org/calendar/ambassadors| Fedora Latam Meeting @ FedoCal]), y deberá contener el tag "meeting" para ser considerado en agenda. Si el ticket es para solicitar patrocinio de Fedora Project, sugerimos esperar a que el ticket sea aprobado para efectuar erogaciones. En casos especiales (eventos importantes anunciados fuera del tiempo anteriormente mencionado) se propone que se utilice un tag especial (meeting+openFloor), para que en caso de que el tiempo del meeting alcance se puedan atender estos issues. Por favor tomar consideración de que este tipo de tickets no necesariamente serán discutidos.
### Attendees from other sub-projects that have been sponsored by the Fedora Project need to be identified by the event owner and need to create a report in their personal blog. If the attendee doesn't have a blog, the report needs to be created on the wiki. Another option is to use the Owner's blog to publish the report.
# Añadir el evento a [https://apps.fedoraproject.org/calendar/Events/| FedoCal] (link a la página wiki)
## Attendees+Owner @ Wiki:
 
### All attendees needs to add a link to their individual reports on the event's wiki page.
 
### All attendees need to add a link to the event's wiki page on their wiki user page. This helps ambassadors and others know what events have you attended.
=== Tareas post-evento ===
# Request reimbursement (only if applicable).
# Reporte de evento:
## Dueño @ CommBlog: El creador del evento debe crear artículo en [https://communityblog.fedoraproject.org/writing-community-blog-article/| CommBlog]
## Asistentes @ [https://fedoraproject.org/wiki/Planet/es |Planet]:
### Asistentes embajadores que hayan asistido deben crear el reporte en su blog personal <-> Este reporte debe ser enlazado al [[Planet/es| Planet]].
### Asistentes de otros subproyectos que hayan sido sponsoreados deben ser representados por el Dueño deben realizar el reporte en sus blogs personales, y en caso de no tenerlo, en la wiki, debe realizar el reporte directamente en la Wiki; otra alternativa sería que utilice el blog del dueño del evento para publicar su reporte.
## Asistentes+Dueño @ Wiki: Todos los asistentes deben colocar el link de los reportes en la wiki del evento.
## Añadir link de reporte en blog personal a la página Wiki del evento.
## Añadir link de la página wiki del evento en su página personal en wiki. Este punto permitirá a los demás embajadores poder saber los eventos a los que han asistido desde la página de perfil de cada contribuyente.
# Solicitar reembolso (sólo si corresponde)






{{reflist}}
{{reflist}}

Latest revision as of 15:54, 11 June 2018

Event Organization Guidelines

Why an event Guideline?

Following these simple steps will allow us to help you have the most successful event possible. If you skip any of the steps it is harder for us to help you. If you are asking for funding, it is critical that you complete all of the steps or we will not be able to fund your event.

Tasks

Pre-event tasks

Ambassadors (or other subproject contributor that wants to be sponsored by the Fedora Ambassadors) needs to do the next steps BEFORE the event:

  1. Create a wiki page for the event in the new structure: Create a wiki page providing general information about the event in the Fedora Project wiki. We suggest you to use the templates [1]. Doing the wiki page, you will help us:
    1. Know about the event
    2. Help future collaborators to participate/help/attend to the event
    3. Make measurement/statistics
  2. Create a ticket (In your region pagure.io): If you are asking for Fedora Project's sponsorship, it's absolutely necessary to create a new ticket/issue pagure.io. The ticket must be created, at least, 3 days before the next meeting (Fedora Ambassadors Regional Meetings @ FedoCal) to be discussed, and must contain the "meeting" tag to be considered on the agenda. If the ticket is for requesting funds, we suggest you to wait until your ticket gets approved to start expending money. In special cases (Great and important events announced out of the time rule mentioned before) we suggest to use a special tag (meeting+openFloor),to discuss this ticket if meeting time allows the discussion. Please take into consideration that these kind of tickets may not be discussed if there is no time.
  3. Add the event to the FedoCal (linking to the wiki page of the event)

Post-event Tasks

  1. Event Reports[2]:
    1. Owner @ CommBlog: The event creator must create an article in the CommBlog
    2. Attendees @ Planet:
      1. Ambassador attendees needs to create a report in their personal blog. This report needs to be linked to the planet Planet.
      2. Attendees from other sub-projects that have been sponsored by the Fedora Project need to be identified by the event owner and need to create a report in their personal blog. If the attendee doesn't have a blog, the report needs to be created on the wiki. Another option is to use the Owner's blog to publish the report.
    3. Attendees+Owner @ Wiki:
      1. All attendees needs to add a link to their individual reports on the event's wiki page.
      2. All attendees need to add a link to the event's wiki page on their wiki user page. This helps ambassadors and others know what events have you attended.
  2. Request reimbursement (only if applicable).


  1. ↑ We are working in the template, trying to improve it and locate it in a better place in the wiki
  2. ↑ Consider that even if you aren't requesting sponsorship, Event reports are really useful to the project.
Retrieved from "https://fedoraproject.org/w/index.php?title=Ambassadors/Latam/EventOrganizationGuideLine&oldid=520365"