Difference between revisions of "CloudAppHack-WG"
| Line 35: | Line 35: | ||
=== Meetings === | === Meetings === | ||
| − | Every second Tuesday of every month through Google Hangouts | + | ==== Every second Tuesday of every month through Google Hangouts ==== |
| − | * July 12 | + | * May 10, 2016 |
| − | * August 09 | + | * June 14, 2016 |
| − | * September 13 | + | * July 12, 2016 |
| − | * October 11 | + | * August 09, 2016 |
| − | * November 08 | + | * September 13, 2016 |
| − | * December 13 | + | * October 11, 2016 |
| + | * November 08, 2016 | ||
| + | * December 13, 2016 | ||
=== Current Hackathons === | === Current Hackathons === | ||
| − | [http://openstack.tumblr.com/ Guadalajara Hackathon] | + | # [http://openstack.tumblr.com/ Guadalajara Hackathon] |
| − | Prague Hackathon | + | # Prague Hackathon |
| − | + | == 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. | 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" | + | 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 | + | 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? | 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: | To do four months prior to the hackathon taking place: | ||
| − | |||
| − | + | # Contact the OpenStack #Cloud Application Hackathon Working Group [https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups_and_Teams] 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. | ||
| − | + | To do one month before the hackathon happens: | |
| − | + | # Make sure you have all 10 of your event organising team and that they are on course to deliver | |
| − | + | === Event Checklist === | |
| − | + | Tasks to achieve during the event: | |
| − | - | + | # 1st do-->confirm |
| + | # 2nd read-->do | ||
| + | # 3rd | ||
| + | # 4th | ||
| + | # 5th | ||
| + | # 6th | ||
| + | # Announce when the next CloudApphack is likely to happen. | ||
| + | # Thank yous to your amazing event organisers, mentors, sponsors and participants <-- cannot begin to express how important this is! | ||
| − | + | === Post Event Checklist === | |
| − | + | Tasks to achieve after the event: | |
| − | |||
| − | |||
| − | + | # 1st do-->confirm | |
| + | # 2nd read-->do | ||
| + | # 3rd | ||
| + | # 4th | ||
| + | # 5th | ||
| + | # 6th | ||
| + | # 7th | ||
| + | # Confirm date of next hackathon | ||
| − | + | === Additional Resources, Examples and Precedents === | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | * Example from Taipei | |
| − | + | * Example from Guadalajara's Hackathon [https://docs.google.com/document/d/1KO3LdLmw3LePttW4mY0EhMKVoq1IhyF64f7DwVNkkpo/pub Frequently Asked Questions guide] | |
| − | + | * 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 ==== | ==== Michael Jenkins ==== | ||
Skype: michael.jenkins886 | Skype: michael.jenkins886 | ||
Revision as of 04:30, 27 June 2016
Contents
Cloud Application Hackathon Working Group
CloudAppHack-WG
Overview
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.
Goals
- Grow a vibrant and inclusive community of cloud application developers who actively use OpenStack as their cloud application infrastructure platform
- Act as an additional point of contact for guidance in developing a successful, safe, inclusive and rewarding hackathon
- Assist in the organization of OpenStack App Hackathon events in your respective communities and to consolidate global activities
- 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
- Develop Applications, Tools and Services atop OpenStack
Community Contributions
- Encourage the development of a broad OpenStack community and ecosystem of partners in support of DevApp Hackathons
- Facilitate training activities in OpenStack
- 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
- Provide guidance on the community’s requirements and actively provide contacts who can solve problems stopping progress
- Expectations Management for communities looking forward to run a hackathon
- 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
- Maintain ongoing communication with the user-committee to provide a forum for wider discussion on how the Application Develop Community is growing
- Develop a task timeline for each hackathon and follow up with the interested community group
- Overview the compliance of minimum membership requirements
- Help finding additional stakeholders, sponsors and community collaborators to co-host the event
- Recruit community members who want to be part of an open team that meets and works towards
Organization
Meetings
Every second Tuesday of every month through Google Hangouts
- May 10, 2016
- June 14, 2016
- July 12, 2016
- August 09, 2016
- September 13, 2016
- October 11, 2016
- November 08, 2016
- December 13, 2016
Current Hackathons
- Guadalajara Hackathon
- Prague Hackathon
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 #Cloud Application Hackathon Working Group [1] 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.
To do one month before the hackathon happens:
- Make sure you have all 10 of your event organising team and that they are on course to deliver
Event Checklist
Tasks to achieve during the event:
- 1st do-->confirm
- 2nd read-->do
- 3rd
- 4th
- 5th
- 6th
- Announce when the next CloudApphack is likely to happen.
- Thank yous to your amazing event organisers, mentors, sponsors and participants <-- cannot begin to express how important this is!
Post Event Checklist
Tasks to achieve after the event:
- 1st do-->confirm
- 2nd read-->do
- 3rd
- 4th
- 5th
- 6th
- 7th
- Confirm date of next hackathon
Additional Resources, Examples and Precedents
- Example from Taipei
- Example from Guadalajara's Hackathon Frequently Asked Questions guide
- 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
