Jump to: navigation, search

Difference between revisions of "CloudAppHack-WG"

(→‎Co-Chairs of this Working Group)
 
(42 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
== Cloud Application Hackathon Working Group ==
+
= About Hackathons =
−
CloudAppHack-WG
+
​OpenStack Hackathons bring together hundreds of technologists in a supportive learning environment to practice their skills with the latest cloud tools. Hackathons are hard work to run, requiring 3-6 months of planning, but the value of a hackathon is multifold:
 +
* Help app developers build knowledge and skill for cloud-native applications
 +
* Develop new relationships and discover new talent in your local community
 +
* Practice collaboration and working as a team across various roles
 +
* Understand the value of open source and how to participate in the open source community
  
−
=== Overview ===
+
== Further info about hackathons ==
−
The Cloud Application Hackathon working group actively supports community members who wants 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.
+
Prior to contacting the Hackathon-WG to request support for organising a hackathon, please read over the material provided here: https://www.openstack.org/community/events/openstackhackathons/
  
−
=== Goals ===
+
= Cloud Application Hackathon Working Group =
−
* Grow a vibrant and inclusive community of cloud application developers who actively use OpenStack as their cloud application infrastructure platform
+
Tag for Hackathon Working Group = #Hackathon-WG
−
* Act as an additional point of contact for guidance in developing a successful, safe, inclusive and rewarding hackathon
+
* Please make sure to append the subject line of your User Committee maling list emails with "[Hackathon-WG] <Email subject line>"
−
* Assist in the organization of OpenStack App Hackathon events in your respective communities and to consolidate global activities
+
* For social media and any other documents created relating to this WG please use the hashtag: #hackathon-wg
−
* Facilitate activities correspondent to the App Hackathon wherever we can without impeding the interested group’s schedules or progress
 
−
* Build personal relationships between AppDev and DevOps communities (tribes) for the purpose of better understanding how resources are exposed (via API/SDK) and how they are consumed
 
−
* Establish AppDev champions who regularly participate and are aware for the wide ranging cloud app techniques and events which produce cloud applications
 
  
−
=== Goals out of Scope ===
+
== Working Group Overview ==
−
* Develop Applications, Tools and Services atop OpenStack
+
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.
  
−
=== Community Contributions ===
+
=== What can you ask this Working Group to do? ===
−
* Encourage the development of a broad OpenStack community and ecosystem of partners in support of DevApp Hackathons
+
Please email the chairs of this WG via the User Committee mailing list to ask them for help to:
−
* Facilitate training activities in OpenStack
+
* Review and approve your application for running an OpenStack Hackathon (see application form below).
−
* Transmit the interested community objectives and ideas to the OpenStack foundation in an easy, fast and organized manner to speed-up the event’s organization
+
* Help you understand the timelines of tasks for setting up and running a hackathon, i.e. usually 6-9 months.
−
* Provide guidance on the community’s requirements and actively provide contacts who can solve problems stopping progress
+
* Connect you with like-minded Open Source developers and community leaders who can support your hackathon application.
−
* Expectations Management for communities looking forward to run a hackathon
+
* 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.
−
* Provide an up-to-date list of DevApp Hackathon events to the user-committee and maintain an available list of past, present and future hackathons
+
* Setup up your cloud application infrastructure for the event (OpenStack + APIs/SDKs + Orchestration Language + C/PaaS + etc + ???)
−
* Maintain ongoing communication with the user-committee to provide a forum for wider discussion on how the Application Develop Community is growing
+
* Request names of previous hackathon organisers who can help provide guidance on your hackathon.
−
* Develop a task timeline for each hackathon and follow up with the interested community group
+
* Provide introduction to the OpenStack Foundation and other sponsors for supporting resources.
−
* Overview the compliance of minimum membership requirements
+
* Act as an additional point of contact for guidance in developing a successful, safe, inclusive and rewarding hackathons.
−
* Help finding additional stakeholders, sponsors and community collaborators to co-host the event
+
* Empower you to run a hackathon for your local Open Source communities, while assuring you are connected with international cloud app expertise.
−
* Recruit community members who want to be part of an open team that meets and works towards
+
* Facilitate activities leading up to the hackathon, without impeding the local group’s schedules or progress.
 +
* Provide skill guidance from a range of communities (AppDev, DevOps, SysAdmin, NetEng, SREs, UXers, etc) for the purpose of better hackathon team cohesion.
 +
* 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 / screencasts, 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/audit 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/
 +
* Get your hackathon listed / promoted on the OpenStack website: https://www.openstack.org/community/events/openstackhackathons/
  
−
=== Organization ===
+
=== Out of Scope for this WG ===
 +
This working group does NOT:
 +
* build applications
 +
* provide guidance on how application should be built
 +
* provide funding for hackathons
  
−
[https://drive.google.com/file/d/0B_6QD8ZT8P4gSHROWVp2YUl0YTQ/view?usp=sharing Organigram]
+
== How to Engage with this Working Group ==
 +
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
  
−
=== Meetings ===
+
=== How to apply for help from this WG? ===
 +
To run an officially approved OpenStack Hackathon, you will need to apply to the Hackathon Working Group Chairs for approval.
 +
Please email the User Committee Mailing list (above) with the Subject line of "[hackathon-wg] request for approval of hackathon <CityXYZ>"
 +
Included in this email should be information on:
 +
# Your name, email and any identifiers (IRC, Twitter, etc).
 +
# Your role and organisation affiliation, e.g. Research Community Manager for the University of Melbourne.
 +
# Your preferred video conference channel (skype/zoom/hangouts/etc) for having a meeting with one of the chairs of the hackathon-wg.
 +
# Where your hackathon is going to take place, i.e. which city and in affiliation with which companies and/or (ideally) Universities.
 +
# Is this going to be an Open event (i.e. public competition open for anyone), or a private internal event (company wide training on private cloud)?
 +
# Date range for when you would like the hackathon to take place.  Please keep in mind planning for hackathons of more than 200 people is around 6-9 months.
 +
# Possible number of participants including age, range and demographic of target audience. NB team sizes are usually 3-6 people per team.
 +
# Description of event theme, including pre-training learning objectives and overall hackathon theme (prizes)?
 +
# Areas of support where you feel you will need help and guidance?
 +
# Have you contacted your local OpenStack community Ambassador and discussed this proposal with them?
 +
# Number of judges you will require during the hackathon? e.g. minimum of 3 judges per 9 teams.
 +
# Number of coaches/mentors you will require in training build-up and on-hand during the event?#Have you created a project schedule/timeline? See 'hackathon organisers kit' for examples.
 +
# Have you created a project budget? See 'hackathon organisers kit' for examples.
 +
# What pre-event training do you plan on having an in what format? e.g. video training tutorials sent a month in advance or face-to-face training the week before.
  
−
==== Every second Tuesday of every month through Google Hangouts ====
+
==== When will you interact with this WG ====
 +
Process flow (timeline) for hackathon organisers to engage the hackathon-wg:
 +
# Idea and interest: so you'd like to positively impact impact your local community by organising an Open Source cloud hackathon?!
 +
# Let us know: send an email to the User Committee Mailing List including the above information on your hackathon.
 +
# Helps on the way: Open Source is ALL ABOUT COMMUNITY - we'll get you connected with your local user groups and global community stakeholders.
 +
# Create a plan: all great events begin with a plan.  Ask for example and guidance on your great event vision!
 +
# Getting serious: let the organisation begin: details, details, detials.  Don't be afraid to ask help us to connect you with previous hackathon organisers!
 +
# Main event: with weeks to go let's start to discuss the gaps and concerns you may have prior to the hackathon.
 +
# Wrap-up: now that you've had a successful hackathon , let's review the lessons learned and capture them for future events around the world!
  
−
* May 10, 2016
+
=== Co-Chairs of this Working Group ===
−
* June 14, 2016
+
Please Cc the co-chairs of the Working Group into any correspondence.
−
* July 12, 2016
+
* Michael Jenkins, Birkbeck, University of London.
−
* August 09, 2016
+
* Gonzalo de la Torre, University of Texas San Antonio.
−
* September 13, 2016
 
−
* October 11, 2016
 
−
* November 08, 2016
 
−
* December 13, 2016
 
  
−
=== Current Hackathons ===
+
=== Further information ===
−
# [http://hackathon.openstackgdl.org/ Guadalajara Hackathon]
+
Please see the Foundation's website for further information on previous hackathons: https://www.openstack.org/community/events/openstackhackathons/
−
# Prague Hackathon - TBD
 
−
# UTSA Hackathon - TBD
 
−
 
 
−
== Lead Hacker Checklists for Cloud Application Hackathon Event ==
 
−
 
 
−
The 'lead hacker' is responsible for the overall success of the event.  You should be a well organised person, able to kindly delegate tasks and humbly ask for help. You will have run events before with an understanding for basic community principles: especially inclusion, kindness and 'a steady hand' when things get stressful.
 
−
 
 
−
Your objectives as the "Lead Hacker":
 
−
 
 
−
* Assemble a team of event organisers who are passionate for building up your local community.
 
−
* Organise weekly/fortnightly meetings to bring the event organising team together to communicate.
 
−
* Answer questions daily, being on-call wherever you are needed.  Promote, promote, promote.
 
−
* Be the cheerleader, help people, do everything you can to make the event a positive organised experience for everyone.
 
−
 
 
−
=== Checklists for the 'Lead Hacker' ===
 
−
 
 
−
The below checklists are intended to provide the minimum viable set of tasks which will need to be completed for the hackathon.  Naturally, you will add on additional tasks to make your event even better and we would highly encourage you to create your own checklists and share them back with the community.
 
−
 
 
−
Are you ready to help make the world a better place where apps can work on any open cloud?
 
−
 
 
−
=== Pre Event Checklist ===
 
−
 
 
−
To do four months prior to the hackathon taking place:
 
−
 
 
−
# Contact the OpenStack [https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups_and_Teams Cloud Application Hackathon Working Group] to find an Ambassador who can support you throughout the event.  A liaison from the OpenStack Foundation will be assigned to support you.
 
−
# Recruit the x10 event organisers who will help you achieve a successful hackathon event, show them this repository with a list of checklists for the roles they will need to undertake as part of the event organising team.
 
−
# Lock down a venue, i.e. lock down the date and tell a new person every day about the Hackathon.  Hint: use any contacts you have at Universities as the Uni will often sponsor the event by donating the space.
 
−
# Come up with the main theme (aka "tag line') of your event, how can you get all the "idea people" to come to this event and participate.  Your event logo will represent this tag line.  Your logo will be used on everything. Hint: what is happening at the time of your planned event, any news headlines likely - be timely!
 
−
# Organise a simple one page website with basic instructions on how to get involved.  Ask your friendly OpenStack liaison to help provide examples of past events.  Don't forget: pictures, video and more pictures.
 
−
# Draw up a floorplan to share with everyone showing spaces marked out for: opening ceremony stage, team spaces, food/drink areas, judging areas (if not the stages), and closing ceremony.
 
−
# Run regular weekly/fortnightly conference calls to make sure your organising team is on track - have fun, encourage smiles as this event is about having fun with ideas!
 
−
# Your hackathon begins with the informal training events which happen once month building up to the event, make sure the cloud and trainers are ready.  <-- this is where teams will form.
 
−
# Gather team leaders every week to keep updated on advancements and next steps
 
−
# Make sure you have all 10 of your event organising team and that they are on course to deliver. One leader is needed for each one of the following concentrations:
 
−
    * Marketing (Social Media, Website, Physical Propaganda)
 
−
    * Pre-Trainings
 
−
    * Sponsors
 
−
    * Registration and Help-Desk
 
−
    * Venue-Logistics
 
−
    * Advocates-Judges
 
−
    * Mentors
 
−
    * Cloud, Network, WiFi
 
−
    * Volunteers
 
−
    * Community Manager
 
−
 
 
−
The process is simplified in the following steps:
 
−
 
 
−
====  Step 1: Interest & Idea ====
 
−
Concept
 
−
 
 
−
When
 
−
 
 
−
How large
 
−
 
 
−
==== Step 2: Let us Know ====
 
−
Fill out Application Form
 
−
 
 
−
Community support
 
−
 
 
−
Industry support
 
−
 
 
−
Academia support
 
−
 
 
−
Other
 
−
 
 
−
==== Step 3: Helps on the way ====
 
−
Identify support members
 
−
 
 
−
Project lead
 
−
 
 
−
Supporters
 
−
 
 
−
Volunteers
 
−
 
 
−
Mentors
 
−
 
 
−
Judges
 
−
 
 
−
Identify facilities or venue
 
−
 
 
−
Identify overall requirements
 
−
 
 
−
==== Step 4: Create a plan ====
 
−
Project plan
 
−
 
 
−
High-level design
 
−
 
 
−
Support commitment
 
−
 
 
−
==== Step 5: Getting serious ====
 
−
Design
 
−
 
 
−
Media coverage
 
−
 
 
−
Budget and funding
 
−
 
 
−
=== Event Checklist ===
 
−
 
 
−
==== The following is an example of a 3 day Hackathon event ====
 
−
 
 
−
Hackathon: Day 1
 
−
 
 
−
08:00 Cluster setup, Infrastructure
 
−
 
 
−
10:00 Settup and Assembly
 
−
 
 
−
12:00 Rehearsal
 
−
 
 
−
15:00 Start of Activities
 
−
 
 
−
15:00 - 22:00: Registration
 
−
 
 
−
17:30: Opening Ceremony, Team presentation, Sponsors
 
−
 
 
−
17:45:  OpenStack Community Presentation
 
−
 
 
−
18:00:  OpenStack WG+Projects
 
−
 
 
−
18:15:  Keynote
 
−
 
 
−
18:30: Agenda + Rules + Q&A
 
−
Housekeeping (11pm - 6am)
 
−
 
 
−
18:45: Mentors Introduction
 
−
 
 
−
19:00: Judges Introduction
 
−
 
 
−
19:15: Closure Talk, Coding start!
 
−
 
 
−
19:30: Networking
 
−
Team formation for individual registers.
 
−
Meet your mentor.
 
−
 
 
−
21:00: Mentor’s checkpoint #1 - Meet your mentor + Kickoff
 
−
 
 
−
22:00: Dinner
 
−
 
 
−
22:00: Team checkpoint: Teams/Tables, Judges needed
 
−
 
 
−
24:00: Midnight Snack
 
−
 
−
Hackathon: Day 2
 
−
 
 
−
09:00: Breakfast
 
−
 
 
−
09:00: Team’s checkup: Entry form Leaders
 
−
 
 
−
10:00: Opening greetings (Day 2, agenda) + Q&A
 
−
 
 
−
10:30: Mentor’s checkpoint #2 - Architecting the app
 
−
 
 
−
14:00: Lunch
 
−
 
 
−
18:30: Mentor’s checkpoint #3 - OpenStack integration & code review
 
−
 
 
−
20:00: Dinner
 
−
 
 
−
24:00: Midnight Snack
 
−
 
 
−
Hackathon: Day 3
 
−
 
 
−
09:00: Breakfast
 
−
 
 
−
10:00: Opening greetings (Day 3, agenda) + Q&A
 
−
 
 
−
10:30: Mentor’s checkpoint #4 - Deployment
 
−
 
 
−
13:00: Coding stops!
 
−
 
 
−
13:00 - 14:00: Mentor’s checkpoint #5 - Teams prepare their pitch + deliverables and submit to judges
 
−
 
 
−
13:00 Mentors and Judges (Pre-selection mentors assignment)
 
−
 
 
−
14:00 - 15:00: Pre-selection round
 
−
 
 
−
* In parallel, each team will present to its assigned judge and they will be graded using the rubric, selecting the best 3 to 5 apps to the finals
 
−
9 mins per team including Q&A
 
−
 
 
−
15:00: Lunch + teams pitch rehearsal (after their presentation with judges)
 
−
 
 
−
15:00 - 16:00: Mentors focus group (Research study)
 
−
 
 
−
15:00 - 16:00: Judge's deliberation (Leaders and Judges) and selection of the best 3 to 5 apps to the finals
 
−
 
 
−
15:15: Get the teams top ten and Leader announces them (#topsecret)
 
−
 
 
−
15:30: leaders entertaining participants #FunnyHack
 
−
Explaining RankTab
 
−
 
 
−
16:00 - 16:30: Finalist announcement
 
−
 
 
−
16:00 - 16:15: Teams goes up at stage
 
−
16:30: Finals
 
−
* The 3 to 5 best teams will be pitch their app to the audience
 
−
* 10 minutes per team (3 min pitch/demo, 2 min to evaluate)
 
−
* 5 min team to set up
 
−
 
 
−
17:30: Audience will select the 1st, 2nd and 3rd place.
 
−
 
 
−
* The selection will be thru votes with an electronic app, token or paper ballots; selecting the 1 to 3 the best apps, like the process to select the name of the next release of OpenStack.
 
−
 
 
−
* In case of a draw, judges will have the final decision.
 
−
 
 
−
18:00: Awards ceremony
 
−
 
 
−
* Thanks to
 
−
- Sponsors
 
−
- Judges
 
−
- Mentors
 
−
 
 
−
19:00: Closing Celebration + Cocktail
 
−
 
 
−
=== Post Event Checklist ===
 
−
 
 
−
# Send hackathon event survey
 
−
# Provide survey results to upcoming hackathon events leaders
 
−
 
 
−
=== Additional Resources, Examples and Precedents ===
 
−
 
 
−
* Example from Guadalajara's Hackathon
 
−
[https://www.youtube.com/watch?v=aSj7h04C_eE Hackathon Experience Video]
 
−
[https://docs.google.com/document/d/1KO3LdLmw3LePttW4mY0EhMKVoq1IhyF64f7DwVNkkpo/pub Frequently Asked Questions Guide]
 
−
[http://hackathon.openstackgdl.org/ Guadalajara Hackathon Portal]
 
−
 
 
−
* Interesting resource worth reading.
 
−
* Some precedents of how other open communities do this.
 
−
* A helpful person worth contacting and having a chat.
 
−
* Why use checklists?  Humans are not great at remembering stuff, this is how mistakes happen, people forget things when they are in stressful situations (like events), checklists are great for focusing the mind and result in significant productivity gains.  Read more about this in a book called, 'The Checklist Manifesto'.
 
−
 
 
−
== Contact Information ==
 
−
 
 
−
=== Co-Presidents - Newton Release ===
 
−
 
 
−
==== Michael Jenkins ====
 
−
Skype: michael.jenkins886
 
−
md.jenkins@icloud.com
 
−
LinkedIn: https://tw.linkedin.com/in/mjenkins3
 
−
 
 
−
==== Gonzalo De La Torre ====
 
−
US: (210) 837-0335
 
−
Skype: gonzalo-de-la-torre
 
−
Google Hangouts: latioz@gmail.com
 
−
LinkedIn: https://www.linkedin.com/in/gonzaloutsa
 

Latest revision as of 07:50, 15 June 2017

About Hackathons

​OpenStack Hackathons bring together hundreds of technologists in a supportive learning environment to practice their skills with the latest cloud tools. Hackathons are hard work to run, requiring 3-6 months of planning, but the value of a hackathon is multifold:

  • Help app developers build knowledge and skill for cloud-native applications
  • Develop new relationships and discover new talent in your local community
  • Practice collaboration and working as a team across various roles
  • Understand the value of open source and how to participate in the open source community

Further info about hackathons

Prior to contacting the Hackathon-WG to request support for organising a hackathon, please read over the material provided here: https://www.openstack.org/community/events/openstackhackathons/

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

Working Group Overview

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 (see application form below).
  • 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.
  • Setup up your cloud application infrastructure for the event (OpenStack + APIs/SDKs + Orchestration Language + C/PaaS + etc + ???)
  • 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 international cloud app expertise.
  • Facilitate activities leading up to the hackathon, without impeding the local group’s schedules or progress.
  • Provide skill guidance from a range of communities (AppDev, DevOps, SysAdmin, NetEng, SREs, UXers, etc) for the purpose of better hackathon team cohesion.
  • 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 / screencasts, 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/audit 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/
  • Get your hackathon listed / promoted on the OpenStack website: https://www.openstack.org/community/events/openstackhackathons/

Out of Scope for this WG

This working group does NOT:

  • build applications
  • provide guidance on how application should be built
  • provide funding for hackathons

How to Engage with this Working Group

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

How to apply for help from this WG?

To run an officially approved OpenStack Hackathon, you will need to apply to the Hackathon Working Group Chairs for approval. Please email the User Committee Mailing list (above) with the Subject line of "[hackathon-wg] request for approval of hackathon <CityXYZ>" Included in this email should be information on:

  1. Your name, email and any identifiers (IRC, Twitter, etc).
  2. Your role and organisation affiliation, e.g. Research Community Manager for the University of Melbourne.
  3. Your preferred video conference channel (skype/zoom/hangouts/etc) for having a meeting with one of the chairs of the hackathon-wg.
  4. Where your hackathon is going to take place, i.e. which city and in affiliation with which companies and/or (ideally) Universities.
  5. Is this going to be an Open event (i.e. public competition open for anyone), or a private internal event (company wide training on private cloud)?
  6. Date range for when you would like the hackathon to take place. Please keep in mind planning for hackathons of more than 200 people is around 6-9 months.
  7. Possible number of participants including age, range and demographic of target audience. NB team sizes are usually 3-6 people per team.
  8. Description of event theme, including pre-training learning objectives and overall hackathon theme (prizes)?
  9. Areas of support where you feel you will need help and guidance?
  10. Have you contacted your local OpenStack community Ambassador and discussed this proposal with them?
  11. Number of judges you will require during the hackathon? e.g. minimum of 3 judges per 9 teams.
  12. Number of coaches/mentors you will require in training build-up and on-hand during the event?#Have you created a project schedule/timeline? See 'hackathon organisers kit' for examples.
  13. Have you created a project budget? See 'hackathon organisers kit' for examples.
  14. What pre-event training do you plan on having an in what format? e.g. video training tutorials sent a month in advance or face-to-face training the week before.

When will you interact with this WG

Process flow (timeline) for hackathon organisers to engage the hackathon-wg:

  1. Idea and interest: so you'd like to positively impact impact your local community by organising an Open Source cloud hackathon?!
  2. Let us know: send an email to the User Committee Mailing List including the above information on your hackathon.
  3. Helps on the way: Open Source is ALL ABOUT COMMUNITY - we'll get you connected with your local user groups and global community stakeholders.
  4. Create a plan: all great events begin with a plan. Ask for example and guidance on your great event vision!
  5. Getting serious: let the organisation begin: details, details, detials. Don't be afraid to ask help us to connect you with previous hackathon organisers!
  6. Main event: with weeks to go let's start to discuss the gaps and concerns you may have prior to the hackathon.
  7. Wrap-up: now that you've had a successful hackathon , let's review the lessons learned and capture them for future events around the world!

Co-Chairs of this Working Group

Please Cc the co-chairs of the Working Group into any correspondence.

  • Michael Jenkins, Birkbeck, University of London.
  • Gonzalo de la Torre, University of Texas San Antonio.

Further information

Please see the Foundation's website for further information on previous hackathons: https://www.openstack.org/community/events/openstackhackathons/

Retrieved from "https://wiki.openstack.org/w/index.php?title=CloudAppHack-WG&oldid=154711"