Overview

Maintainers Contributors Summits are being designed to replace the current Hackfest concept. Instead of being open to the public, Maintainers Summits are invitation only events that are designed for existing project maintainersContributors Summits are intended for an advanced technical contributor audience, including core contributors, TSC members, and working group chairs; however, may be open to other contributors based on a nomination process. Maintainers . Contributors Summits will be limited to no more than 50 people to ensure that progress can be made on shared Hyperledger technical goals. These goals will be pre-defined prior to the start of the summit to ensure that the right people are present.

While anyone is welcome to join the Contributors Summits, they are not be suitable for people with no knowledge of Hyperledger and its projects. Also, the expectation for Contributors Summits should be that the conversation will be deep technical conversations. If you are looking for events that are open to the publicdesigned for new contributors, please check out the Bootcamps section  section of the Wiki. 

Goal

The goal for a maintainers summit Contributors Summit is to encourage cross collaboration amongst the different projects that are part of Hyperledger. This cross collaboration can come in the form of education deep technical dives about each of the projects, specific work surrounding an architectural component of the frameworks (e.g., common consensus mechanisms), contribution or review of cross-project whitepapers developed by the different working groups, or other items that the maintainers contributors feel is important to ensuring that we are one community.

Timing

Maintainers Contributors Summits will last for three (3) days and be held twice a year or more frequently if the technical community finds a need.

Program Committee

The program committee will be responsible for determining who receives an invite to the Maintainer Summit and for developing the program agenda. The program committee will be made up of five people, one of which will be a Hyperledger Community Architect. The other four members of the committee will be members of the TSC since the TSC is responsible for the technical direction of Hyperledger. These four members can be different people for each summit or they can be the same for the term of the TSC.

Determining Who is Invited

A short list of contributors will be created that includes:

Who Should Attend

It is highly recommended that people with a deep understanding of the technical aspects of the Hyperledger projects should attend the Contributors Summits. This would include

• TSC members
• Working group chairs and vice chairs
• Active Core Contributors - defined  defined as the most prolific contributors who have between them contributed 80% of the code and have made a contribution in the last 6 months (as of January 15th, using the project reports tool, this list included 54 people)

In addition to the above, anyone that suggests a topic is added to the short list of names.

The program committee will use this list to determine who should receive an invite.

Agenda Creation

• Those with specific deep technical knowledge to contribute towards the development of the Hyperledger projects

As noted in the overview, anyone is welcome to join the Contributors Summits with the understanding that the focus will be advanced technical topics.

Agenda Creation

It is extremely important that the Agenda be created prior to the summit. This will ensure that the correct people attend. The goal of the Contributors Summit The summit's agenda will be created by the program committee, but will require input from the technical community regarding the items that need to be discussed. The goal of the maintainers summit should be top of mind when deciding what topics are added to the agenda. The topics should focus on:

...

The first two days of the agenda will be from the proposed [summit-topic] emails. The last day will be reserved for an unconfernece unconference style agenda to handle topics that come up during the actual summit.

...

•  Bootcamps work for entry point into the community. Maintainers Summits are for core developers to work on shared technical goals. Do we need another type of event for those in the middle? 
•  How do we break up the 50 people between the different projects, TSC members, and working group chairs? Today we have 11 TSC members, 12 projects, and 5 WGs. Assuming no overlap and one person per project and WG, that is already 28 people.
•  Should we have a program committee for deciding both who should get an invite, as well as, what topics will be on the agenda?
•  How will a short list of names be determined for consideration of receiving an invite?
•  How much time should be set aside for a Maintainers Summit?
•  How often will Maintainers Summits occur?