- 1 Cloud Application Hackathon Working Group
- 2 Incorporating User Research at Hackathons
- 3 Contact Information
Cloud Application Hackathon Working Group
Tag for Hackathon Working Group = #Hackathon-WG Please make sure to append the subject line of your User Committee maling list emails with "[Hackathon-WG] <Email subject line>" For social media and any other documents created relating to this WG please use the hashtag: #hackathon-wg
The Cloud Application Hackathon working group actively supports community members who want to organize and run a cloud application hackathon for their community. The working group (WG) will share it’s collective knowledge, exchange of best practices, documentation, and provide mentorship. This WG is a place for hackathon organisers to come and receive planning advice which is practical and helps the organiser achieve event success by leveraging the capabilities of the global OpenStack community.
What can you ask this Working Group to do?
Please email the chairs of this WG via the User Committee mailing list to ask them for help to:
- Review and approve your application for running an OpenStack Hackathon.
- Help you understand the timelines of tasks for setting up and running a hackathon, i.e. usually 6-9 months.
- Connect you with like-minded Open Source developers and community leaders who can support your hackathon application.
- Acquire guidance on how to setup your event steering committee, i.e. your hackathon committee will help seek sponsorship, mentors, infrastructure and other event resourcing.
- Request names of previous hackathon organisers who can help provide guidance on your hackathon.
- Provide introduction to the OpenStack Foundation and other Sponsors for supporting resources.
- Act as an additional point of contact for guidance in developing a successful, safe, inclusive and rewarding hackathons.
- Empower you to run a hackathon for your local Open Source communities, while assuring you are connected with the international expertise.
- Facilitate activities leading up to the hackathon, without impeding the local group’s schedules or progress.
- Encourage enhanced relationships between developer communities (AppDev, DevOps, SysAdmin, NetEng, SREs, UXers, etc) for the purpose of better understanding one another.
- Introduce hackathon champions who regularly participate and are aware for the wide range of cloud application tools, connectors and technologies.
- Provide contacts who are willing to partner in supporting the logistics of the event.
- Suggest whom in the community can provide pre-training for teams, including videos, on-site training and other learning resources.
- Provide guidance on how to recruit community volunteers to support the hackathon training activities and competition.
- Provide oversight of the judging process to assure equity and fairness.
- Liaise between the local hackathon organisers and the OpenStack User Committee: https://www.openstack.org/foundation/user-committee/
- Getting your hackathon listed on the OpenStack Hackathon website: https://www.openstack.org/community/events/openstackhackathons/
Goals out of Scope
This working group does NOT:
- build applications
- provide guidance on how application should be built
- provide funding for hackathons
Please email the user committee mailing list with the subject tag of [hackathon-wg] to request a meeting with the chairs of the hackathon working group: http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
Co-Chairs of this Working Group
- Michael Jenkins, Birkbeck, Unviersity of London.
- Gonzalo de la Torre, University of Texas San Antonio.
Please see the Foundation's website for further information on previous hackathons: https://www.openstack.org/community/events/openstackhackathons/
Incorporating User Research at Hackathons
Collecting feedback from participants is not only a great way to improve future hackathons, but also get insight on how application developers use OpenStack to ultimately improve its UX. Danielle Mundle (IRC: uxdanielle) has put together some draft resources for potential hackathon research activities. Please feel free to add ideas or otherwise edit the etherpads to reflect your input.
Main etherpad for Hackathon Research: https://etherpad.openstack.org/p/newton-osux-HackathonSurveyResearch
Suggestions for how/when to leverage user research at hackathons
- Survey for basic feedback on hackathon experience/coordination - After the hackathon ends (either before they leave, or within 2 days of participation): https://etherpad.openstack.org/p/newton-osux-HackathonSurveyResearch (beginning at "Taiwan Survey Questions")
- Survey for demographic information on hackathon attendees - Before the official hackathon kickoff/at registration: https://etherpad.openstack.org/p/Hackathon-researchEntrySurvey (Example survey format: https://www.surveymonkey.com/r/T62J95S )
- Survey for experience using OpenStack at the hackathon - While awaiting the judges final decision: https://etherpad.openstack.org/p/Hackathon-researchExitSurvey (Example survey format: https://www.surveymonkey.com/r/T5KVSDZ )
- Survey for issues encountered using OpenStack DURING the hackathon - During active hacking time/whenever issues are encountered in real-time: https://etherpad.openstack.org/p/Hackathon-researchEventReporting (Example survey format: https://www.surveymonkey.com/r/T5Q2TDW )
- Focus group for attendee feedback - While awaiting the judges final decision: https://etherpad.openstack.org/p/Hackathon-researchAttendeeFacilitatorGuide
- Focus group for mentor feedback - After the first day of hacking, around 4-5pm: https://etherpad.openstack.org/p/Hackathon-researchMentorFacilitatorGuide
Co-Presidents - Newton Release
Gonzalo De La Torre
US: (210) 837-0335
Google Hangouts: firstname.lastname@example.org