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

To include information regarding how long the summit Contributors Summits will last and how often will it occur.

Determining Who is Invited

To include information on determining who will receive an invite. With the Linux Kernel Summits, a short list of names is determined using a script (get more information) and a program committee uses that list to determine who should receive an invite. In addition, anyone that suggests a topic is added to the short list of names.

Program Creation

...

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

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 as the most prolific contributors who have between them contributed 80% of the code and have made a contribution in the last 6 months
• 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 should be top of mind when deciding what topics are added to the agenda. The topics should focus on:

• items that enhance cross collaboration amongst projects
• items that are easier to resolve in person than over email

...

• "information sharing" topics if they are clearly of interest to the wider development

...

• community (i.e., advanced training in topics that would be useful to

...

• all projects)

. Topics are will be suggested by the technical community. The TSC mailing list will be used for topic suggestions. The email should be prefixed with [summit-topic]. The email should contain the following information:

• Topic Title
• Topic Description
• Why This Topic is Important
• Projects Impacted
• Suggested Time Required to Cover and Discuss

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

Open Questions

•  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?