What is a bootcamp?

A Bootcamp is where we help get community members up to speed on how to contribute.  Most of the participants are fairly new and we understand that contributing to your first project can be daunting.  This process take the fear out of the process.  This is not just for coders!  This can be as simple as helping create documentation, to use cases, to helping a group get organized, and of course bug reports and fixing bugs.

For existing contributors and maintainer, this is the ideal place to recruit more help for your project or group.  Are you a new group that doesn't have a good "getting started.md?"  Come to this event and mentor people to actually get started and the new people can write the document as you take them through the process.  Are you an older group that needs some help on Use cases?  Ask for contributions here!  Are you a mature project that needs people to report bugs or help you flush out a old bug report?   To get people to attend and help you - Create a breakout session on the Grid for a particular bootcamp.  Be sure to grab as much time I you realistically need.  Do you need a roadmap?  Ask for a PM or couple to join your breakout session.  And lastly, do you really just need to onboard a bunch of newbies to your platform or tool?  Try out your new training materials here and see how they work!

Who should attend and why?

Anyone that wants to contribute.  This includes: developers, designers, writers, organizers, artists, and of course Project managers.

Upcoming BootCamps:

Can I do a bootcamp?

Possibly -  Please contact the Community Architects team at community-architects@hyperledger.org

Or on Rocketchat https://chat.hyperledger.org/channel/community-architects

But for Official sponsorship of a Bootcamp we will need to start a ticket in JIRA. 

We don't have a large staff at Hyperledger, so the more work you take off of our shoulders, the more likely we are to approve your event. 

We only do Hyperledger events.  They need to be Open Source.  The focus needs to be contributing to the existing community.  We like ones that are attached and have the support of a larger event as experience has taught us those have better attendance.

What is does a Typical Agenda look like?

First each of the various targeted Projects, Work Groups, and Labs does a short intro to the entire group.

These intros are to recruit contributors.  The presentations need to be interesting and explain what the participants will get out of the next two days. It is ideal to have different groups at different levels.  Some groups maybe working on introductory materials, others maybe bug fixing, and a few maybe talking about use cases for desired features.

Everyone then breaks out into small groups to work thru the tutorials or getting started documentation.  A few of the Breakouts maybe to talk about usecases or even fix bugs depending on levels of expertise.  If it is a Lab or a new project they may help the group lead create the getting started materials.

Finally,  at the end of the last day, everyone publishes their work and what they have learned to share with future learners.   If they succeeded at getting documentation changes, patches, bug fixes etc accepted, they get a badge or an award for completion.