How to organize a GNOME-related Hackfest
A hackfest is an event where people gather to work on a specific topic. You are welcome to organize new hackfests and can request sponsorship for these from the GNOME Foundation.
What type of events does this page cover?
This page is for creating any event that you want to be listed on https://wiki.gnome.org/Hackfests
There are other types of events that you can organize which are not covered here. You may also be interested in:
BoFs at Conferences
Other events recommended by the Engagement Team
Who is responsible for what?
As the organiser, you are expected to:
- set up the hackfest page on this wiki
- arrange the venue
work with the Engagement team to promote the event
- ensure that attendees send in travel and accommodation sponsorship requests well in advance
- help attendees and travel committee with accommodation and travel suggestions
The GNOME Foundation can support events by helping you:
- understand the processes of setting up a hackfest
- identify and invite the right attendees
understand how to request Travel and accommodation sponsorship
- find sponsors
- find a venue
- promote the event
Step by step guide
- You (the organiser):
- pick potential dates
- pick potential venue
- talk to key attendees to confirm attendance
- You pin down the details of the hackfest, completing your hackfest event page.
- You announce the event as needed (normally on at least one GNOME mailing list).
If you expect attendees to need travel sponsorship, you should contact all attendees and ask them to send their requests to the Travel Committee as soon as they start considering attending the hackfest and ideally no later than 8 weeks before the hackfest.
- Attendees send in their travel requests.
If you would like the board to give you assistance, you will need to email the board with what you want the board to do for you at firstname.lastname@example.org. Please note that you do not need the Board's approval to organize a hackfest, they are there to assist you if you need help.
- The board will discuss your request and contact you with a response.
If you would like the engagement team to promote your event, help you with marketing material, or send you stickers and SWAG for your event, you will need to email the engagement team with your request and a link to your hackfest page at email@example.com
- Event happens.
- Attendees blog about event.
- Attendees receive reimbursements for any Travel Committee requests.
Things to consider
Start planning early: last minute hackfests are expensive and more difficult to attend. (I.e., we recommend 2-6 months in advance.)
Location. How difficult is it to get there from your continent? Other continents? (E.g., Amsterdam is easier for people to get to than Isle of Man.)
Attendees. Who do you definitely want to attend? Who has committed? What costs will they have? Do you need help reaching out to other groups or identifying participants? (E.g. if you have 5 attendees in Europe and 1 on a tropical island, hold the event in Europe, not on the tropical island.)
- Venue. How many people are attending? Is there reliable internet and can you use IRC/git? Try to get at least two quotes from hotels; ask them for a conference rate.
- Agenda. Why do you want to have this Hackfest? What do you aim to accomplish during the Hackfest?
- Schedule. It helps to have an idea of when you expect things to happen. This will help set everyone's expectations and can allow people to comment if they think something is unreasonable or of concern.
- Local outreach. Can you invite any local groups? Can you get the local students involved?
Miscellaneous notes about reports, blogging, ''etc.''
Here are some guidelines:
You should promote the event and report on it. If you are a Foundation member, we encourage you to blog posts on blogs.gnome.org so they show up on Planet GNOME
Sponsored attendees use a Sponsored by the GNOME Foundation badge (available on the Travel Committee page) for your blog, avatar, tweets, etc. You are even invited to create a few real-life badges with the SVG made by Vinicius Depizzol.
- Try to write a report for each day of the event, be detailed about what was discussed, some keywords that help for this type of writing: who (said it/did it), what (is it/does it do), why (is it being done/it needs work), how (is the goal progressing/the team organised).
Make sure any marketing you do for the event is in compliance with GNOME's trademark guidelines.
Take lots of pictures! (after asking if people mind). Consider sharing some of those with the wider GNOME community and GNOME Engagement team so we can use them to promote GNOME. Find out how to submit photos to GNOME.
Create a tag/hashtag for your event in Flickr, Twitter, identi.ca, Facebook, with the same name as the wiki page if possible, for example: #bananahackfest2010 or #BananaHackfest2010, whatever reads better in the service that you are using.