Open Stack

TL;DR = having run/participated in 50+ hackathons over the past decade here
are my top 3x risks and top 3x success factors for running a hackathon,
which we should make communities aware of prior to their commitment to run
a hackathon.
--------------------------------

Many thanks to Gonzalo and Michael for your leadership of the
CloudAppHack-WG as co-chairs. We continue to receive interest from around
the world requesting the opportunity to run a cloud application hackathons
+[the cloud app training which precedes a hackathon event].  The
CloudAppHack-WG will help assure these event-series are community oriented
and lead as per the Open principles[1].

Of significant importance is the "draft application for running a
hackathon" - my comments below as I will not be able to attend the meeting,
as I'll be Zzzz'ing in an APAC timezone ;-)  nb meeting minutes greatly
appreciated.

​
goo.gl/08grC6  <-- I would encourage feedback on this form by all WGs (esp
AppEco-WG and ISV-WG] as it will be the process by which the Foundation can
be actioned to support a Cloud Application Hackathon.  Further discussion
TBD on the way in which Hackathons are supported and branded as "Official
OpenStack App Hackathons".

>From my personal PoV there three key characteristics of a successful
hackathon and three key risks, I list them below and would suggest that
they be part of the discussion around the application process prior to a
hackathon being approved by the CloudAppHack-WG:

Hackathon Success Criteria:

 - (1) As much, if not more effort put into organising pre-training events
than the main hackathon event days themselves.  The pre-trainings will
result in teams ready to compete, i.e. you wouldn't expect to show up to a
marathon and win without training.
 - (2) a minimum of 10+ people who can play the role of event organisers
(see list of roles below or at this repo:
https://github.com/DFFlanders/CloudAppHack), i.e. a hackathon is a much
more involved and complex event than any other community run event which
must be *team organised*.
 - (3) Collaboration with the Foundation is the best way to assure global
reach and awareness.  These event can be so much larger than the some of
their parts if we collaborate.  As Guadalajara can attest, the Foundation
is very light touch and primarily there to assure amplification of your
events achievements.

Hackathon Risk Criteria:

 - (i) a working operational cloud ready a month in advance and used during
all pre-trainings to assure its resilience and redundancy.  A back-up cloud
should also be ready as the event will fail if the cloud fails.
 - (ii) Multi-company/community participation.  Many OpenStack days are run
by one company which does not uphold our value for open community [1].
Hackathons should above all else, bring multiple companies/communities
together to compete in the open - it is this open competition of a
hackathon which makes us better as an OpenSource community IMHO.
 - (iii) sponsorship which is appropriate and practical for the communities
growth, i.e. sending 1 or 2 teams to the summit and/or other OpenStack
community events is not a cheap endeavour but is the best way to assure our
community is creating a community domino affect.  The utilisation of the
CloudAppHack-WG as the central coordinator of sponsorship opportunities
will assure resources are spread evenly and fairly without burning out our
sponsors support.

All the above my own personal PoV, not necessarily shared by the Foundation.
Greatly appreciated for anyone wiling to represent these points during the
call this Thursday.

[1]= https://wiki.openstack.org/wiki/Open

Kind Regards,

Flanders

On Tue, Sep 20, 2016 at 6:38 AM, Gonzalo De La Torre <
gonzalo_delatorre at live.com> wrote:

> Good day everyone,
>
> We would like to invite all community parties who are interested in
>
> Organizing a Hackathon to the next CloudAppHack-WG meeting which will be
> held on:
>
>
> Date: Thursday  Sep 22nd
> Time: 9:30 CST
> Place: Google Hangouts
> Link: https://hangouts.google.com/call/mrrocwqtlrhgjpni3rfk6kh334e
>
>
> During the meeting, we will be inviting some of the leaders from
>
> the OpenStack Guadalajara Hackathon to review some of the key points to
> consider when
>
> running a national hackathon for each of their programmed activities. In
> addition, I would
>
> like to invite all community members to give their input regarding the key
> aspects to
>
> consider in order for the community to support an OpenStack Hackathon.
>
>
> Meeting Agenda:
>
> A. Introduction to Interested Communities
>
> http://labs.cloudapphack.eu/
>
> http://cloudapphack.eu/
>
>
> B. Team Organization Key Points - OpenStack Guadalajara Leaders
>
>   1.  Marketing (Social Media, Website, Physical Propaganda)
>
>   2.  Pre-Trainings
>
>   3.  Sponsors
>
>   4.  Registration and Help-Desk
>
>   5.  Venue-Logistics
>
>   6.  Advocates-Judges
>
>   7.  Mentors
>
>   8.  Cloud, Network, WiFi
>
>   9.  Volunteers
>
>   10. Community Manager
>
>
> C. Application for Running a Hackathon - Review
>
> ​​
> goo.gl/08grC6
>
>
> D. Outreach to Communities
>
> Next steps to take to start and promote Hackathons for the following
> communities:
>
>
>   1.  Australia / AsiaPac Cloud App Hackathon
>
>   2.  2nd Annual Taiwan+China Cloud App Hackathon
>
>   3.  University Global Sprint Hackathon
>
>   4.  EU-Wide Cloud App Hackathon
>
>
> Feel free to follow our WG Updates at:
>
> https://wiki.openstack.org/wiki/CloudAppHack-WG
>
>
>
> Best regards,
>
>
> Gonzalo De La Torre
>
> US: +1 (210) 837-0335
>
> MX: +52 (33) 8421 9335
>
> Skype: gonzalo-de-la-torre
>
> Twitter: @OpenStack_Guy
>
> Google Hangouts: latioz at gmail.com
>
> LinkedIn: https://www.linkedin.com/in/gonzaloutsa
>
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>
>


-- 
Flanders | OpenStack Foundation | Community Manager (Cloud Application
Communities)
http://superuser.openstack.org/articles/meet-openstack-s-community-wrangler-david-flanders
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160920/98e58f45/attachment-0001.html>