...
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
...
The program committee will use this list to determine who should receive an invite. NOTE:
| Note |
|---|
|
Program Agenda Creation
...
|
Agenda Creation
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:
- 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 for an unconfernece Linux Kernel Summits also reserve space for an unconference style agenda to handle topics that come up during the actual summit.
...