Creating a structured event report template is essential for Fedora event organizers to document key details, assess outcomes, and share insights with the community. Below is a template aligned with Fedora’s guidelines:

Event Report Template

  1. Event Overview
    • Event Name: [Insert event name]
    • Date(s): [Insert event date(s)]
    • Location: [Insert event location]
    • Event Description: [Provide a brief description of the event’s purpose and focus]
    • Event Owners: [List Fedora contributors responsible for the event, including links to their personal wiki pages]
    • Fedora Representatives: [List Fedora representatives at the event, specifying their roles, with links to their personal wiki pages]
  2. Event Details
    • Event Schedule: [Outline the schedule, highlighting sessions, workshops, or activities that took place during the event]
    • Event Budget: [Provide an overview of the budget allocated and spent for the event]
    • Travel Subsidy Requests: [Document any travel subsidies requested or granted]
  3. Attendance and Engagement
    • Number of Attendees: [Provide an estimate or exact number of participants]
    • Fedora Booth Activity: [Describe the level of activity and engagement at the Fedora booth, if applicable]
    • Common Questions and Feedback: [Summarize frequent inquiries or feedback received about Fedora]
  4. Outcomes and Impact
    • Successes: [Highlight what worked well during the event]
    • Challenges: [Discuss any obstacles encountered and how they were addressed]
    • Lessons Learned: [Share insights gained that could benefit future events]
    • Mindshare Initiatives: [Reflect on how the event contributed to building users or contributors to specific Fedora solutions]
  5. Post-Event Actions
    • Follow-ups: [Detail any actions taken/to be taken after the event, such as contacting leads or sending materials]
    • Event Report Publication: [Indicate where the event report will be published, such as the Fedora Community Blog or personal blogs that are connected to Planet Fedora]
    • Reimbursement Requests: [If applicable, note that a reimbursement request has been submitted to the Event Requests repository]
  6. Additional Information
    • Ideas/Brainstorming: [Document any ideas or suggestions for future events]
    • Important Links: [Include links to relevant resources, presentations, blog posts about the event or materials from the event]

Submission Guidelines:

Leave a Reply

Your email address will not be published. Required fields are marked *