Add base descriptions for all of the potential "Content" subteam roles for the Contributor Summit. This is a jumping-off point for filling these in as the new Events team does its work.
This commit is contained in:
Josh Berkus
parent
bdaf7efc29
commit
cb096fad8e
|
|
@ -0,0 +1,34 @@
|
|||
# Content SubTeam
|
||||
|
||||
The Content subteam of the events team is responsible for programming and content for periods
|
||||
of the contributor summit.
|
||||
|
||||
The membership of this team depends on the activities that will actually take place during that
|
||||
particular Contributor Summit. As such, there are a variety of roles, but not all roles
|
||||
will be present for all Summits. The mix of content is generally determined by the Content Coordinator
|
||||
and the Event Lead in the first 2-3 weeks of event planning, so many of these roles
|
||||
will be chosen after that.
|
||||
|
||||
All roles may have shadows. Click the role name for that role's Handbook.
|
||||
|
||||
| Role | Needed For | Notes |
|
||||
|------|------|------|
|
||||
| [Content Coordinator] | Almost all Summits | |
|
||||
| [New Contributor Workshop] Lead | Summits with an NCW track | Also some standalone NCW events |
|
||||
| [Programmed Sessions] Lead | Summits with an advance session submission process | |
|
||||
| [Contributor Workshops] Lead | Some Summits with a session proposal process | |
|
||||
| [Unconference] Lead | Summits with an Unconference Track | |
|
||||
| [SIG Meet & Greet] Lead | If including a SIG M&G at the end of the NCW | |
|
||||
| [SIG Face-to-Face] Lead | If there will be SIG F2F sessions | |
|
||||
| [Social Event Content] Lead | Summits with a Social Event | |
|
||||
| [Awards Ceremony] Leads | If giving contributor awards | |
|
||||
|
||||
[Content Coordinator]: ./content-coordinator.md
|
||||
[New Contributor Workshop]: ./new-contributor.md
|
||||
[Programmed Sessions]: ./session-manager.md
|
||||
[Unconference]: ./unconference.md
|
||||
[Contributor Workshops]: ./contributor-workshops.md
|
||||
[SIG Face-to-Face]: ./sig-f2f.md
|
||||
[SIG Meet & Greet]: ./sig-meet.md
|
||||
[Social Event Content]: ./social-content.md
|
||||
[Awards Ceremony]: ./awards-ceremony.md
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
# Awards Ceremony Handbook
|
||||
|
||||
## Overview
|
||||
|
||||
The Awards Ceremony coordinators collect information on desired awards and nominees from the community, determine the form and schedule for the community awards, and ensure that awarding community members and award recipients are present for the ceremony. They also source award trophies or tokens. Because of the nature of these awards, these activities need to be carried out semi-confidentially in order to ensure that award recipients are not prematurely notified.
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
TODO
|
||||
|
||||
## Activities
|
||||
|
||||
WIP
|
||||
|
||||
## Time Commitment
|
||||
|
||||
TODO
|
||||
|
||||
## Instructions and Tips for Specific Tasks
|
||||
|
|
@ -0,0 +1,43 @@
|
|||
# Content Coordinator Handbook
|
||||
|
||||
## Overview
|
||||
|
||||
The Content Coordinator leads and manages the content programs associated with the event. They work with the Event Lead to determine which content programs the event will have, recruits the content leads and shadows for each content program, and coordinates between the programs to make sure they all work together. They are also a backup for any content lead who is unable to fulfill their duties, and execute any content tasks that don't fall to the content program leads.
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
TODO
|
||||
|
||||
## Activities
|
||||
|
||||
The following list of activities is for a large Contributor Summit with multiple Content Programs. For smaller summits, many of these activities will be unnecessary, and timelines can be shortened.
|
||||
|
||||
### Weeks 1-3
|
||||
|
||||
* Work with Event Lead to determine Content Strategy for the event.
|
||||
* Determine what Content Programs the event will have.
|
||||
* Recruit Leads & Shadows for each Content Program.
|
||||
* Post "Save the Date" placeholders for the Summit, and messages to contributors.
|
||||
* If having preprogrammed content, draft application form for submissions.
|
||||
|
||||
### Weeks 3-6
|
||||
|
||||
* Issue Call for Sessions if having preprogrammed content.
|
||||
* Organize Content Team to solicit SIGs/WGs/Teams directly for content.
|
||||
*
|
||||
|
||||
WIP
|
||||
|
||||
Work with Lead on content strategy
|
||||
Use previous surveys, events, focus groups, and anything else needed to determine content ideas
|
||||
If an unconference is a part of the day, recruit a coordinator to help plan and facilitate
|
||||
Help keep event site up to date with the most recent content changes
|
||||
Decide what trainings should be provided that would be valuable in a face to face setting (example: SIG Chair Training)
|
||||
Coordinate speakers, teachers, and folks to deliver the content
|
||||
|
||||
## Time Commitment
|
||||
|
||||
TODO
|
||||
|
||||
|
||||
=======
|
||||
|
|
@ -0,0 +1,21 @@
|
|||
# Contributor Workshops Handbook
|
||||
|
||||
## Overview
|
||||
|
||||
The Contributor Workshop team recruits, selects, and schedules "advanced" workshops for current Kubernetes contributors to improve their skills during the Contributor Summit. Such workshops might include hands-on demonstrations of build or testing tasks, live interactive reviews of PRs, KEPs, API changes, or similar, documentation writing, or other long-form activities involving some hands-on-keyboard participation.
|
||||
|
||||
This is distinct from the [New Contributor and Intermediate Contributor workshops](./new-contributor.md), although the CW team will work with that team.
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
TODO
|
||||
|
||||
## Activities
|
||||
|
||||
WIP
|
||||
|
||||
## Time Commitment
|
||||
|
||||
TODO
|
||||
|
||||
## Instructions and Tips for Specific Tasks
|
||||
|
|
@ -1,30 +1,4 @@
|
|||
# Content Lead Handbook
|
||||
|
||||
## Overview
|
||||
Lead and execute on the overall content for all personas of contributors based on
|
||||
goals set forth
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
TODO
|
||||
|
||||
## Activities
|
||||
|
||||
Work with Lead on content strategy
|
||||
Use previous surveys, events, focus groups, and anything else needed to determine content ideas
|
||||
If an unconference is a part of the day, recruit a coordinator to help plan and facilitate
|
||||
Help keep event site up to date with the most recent content changes
|
||||
Decide what trainings should be provided that would be valuable in a face to face setting (example: SIG Chair Training)
|
||||
Coordinate speakers, teachers, and folks to deliver the content
|
||||
|
||||
## Time Commitment
|
||||
|
||||
TODO
|
||||
|
||||
|
||||
=======
|
||||
|
||||
New Contributor Content Lead
|
||||
# New Contributor Content Lead
|
||||
|
||||
## Overview
|
||||
The New Contributor Content Lead is in charge of planning and executing the New Contributor Workshop at the Kubernetes Contributor Summit. They will coordinate with the overall Events Team and the organizers of related activities aimed at new contributors.
|
||||
|
|
@ -33,21 +7,21 @@ The New Contributor Content Lead is in charge of planning and executing the New
|
|||
|
||||
The New Contributor Content Lead must be a current, active Kubernetes contributor who is knowledgeable of the community and organizational structure of the Kubernetes project, as well as familiar with building and developing Kubernetes.
|
||||
They should have experience and be comfortable with teaching in a workshop setting and presenting interactively in front of an audience.
|
||||
Additionally, they must be able to relate to and empathize with newcomers of many different experience levels.
|
||||
Additionally, they must be able to relate to and empathize with newcomers of many different experience levels.
|
||||
As this role is part of a subproject of SIG-contributor-experience, the New Contributor Content Lead must be a member of SIG-contributor-experience.
|
||||
|
||||
## Activities
|
||||
## Activities
|
||||
|
||||
*These tasks reflect a rough timeline leading from the end of the previous Contributor Summit to the currently planned one.*
|
||||
- Attend event planning meetings in preparation for the Contributor Summit, where applicable
|
||||
- Create a Workshop Content Proposal and link in an Issue to k/community:
|
||||
- determine sessions and their overall topic (e.g. How We Communicate, Code Base Walkthrough, etc)
|
||||
- determine what difficulty/experience levels will be offered, if any, and coordinate with Lead
|
||||
- determine workshop capacity, and coordinate with Lead
|
||||
- determine workshop capacity, and coordinate with Lead
|
||||
- determine room requirements (size, number, table/chair layout, A/V) and coordinate with the planning team
|
||||
- Coordinate with New Contributor Content Shadows to prepare them for leading this role.
|
||||
- Recruit and coordinate with workshop teachers for any sessions/topics you do not wish to teach yourself (e.g. invite someone to speak on "Communication in the Kubernetes Project").
|
||||
- Make modifications and continuous improvements to the new contributor workshop template.
|
||||
- Make modifications and continuous improvements to the new contributor workshop template.
|
||||
Incorporate feedback from previous New Contributor Workshops.
|
||||
Shadows and co-presenters are expected to assist and review these updates.
|
||||
[Past presentations are linked here](https://github.com/cncf/presentations/tree/master/kubernetes) - please make a copy of the existing deck before updating/editing.
|
||||
|
|
@ -0,0 +1,21 @@
|
|||
# Programmed Sessions Handbook
|
||||
|
||||
## Overview
|
||||
|
||||
The Programmed Sessions lead recruits, selects, and schedules planned short-form sessions for the Contributor Summit. These sessions cover topics of interest to regular contributors, such as contribution tasks, project changes, discussions of architectural changes and features, mentorship and sustainability, or testing and conformance.
|
||||
|
||||
This is distinct from Contributor Workshops (which are long-form, always-interactive sessions), and an Unconference, which are sessions NOT selected in advance. If the Summit has those types of sessions as well, the PS team will coordinate with other teams to work out a balanced schedule.
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
TODO
|
||||
|
||||
## Activities
|
||||
|
||||
WIP
|
||||
|
||||
## Time Commitment
|
||||
|
||||
TODO
|
||||
|
||||
## Instructions and Tips for Specific Tasks
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
# SIG Face-to-Face Handbook
|
||||
|
||||
## Overview
|
||||
|
||||
The SIG Face-to-Face (F2F) Lead recruits, selects, and schedules "face-to-face" sessions run by each SIG, WG, or Team. F2Fs are open-form discussion sessions, usually structured as SIG meetings, but sometimes task-based or topic-based discussions. The F2F lead does not select topics or activities for the F2F sessions, except making sure that they *have* a topic or activity.
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
TODO
|
||||
|
||||
## Activities
|
||||
|
||||
WIP
|
||||
|
||||
## Time Commitment
|
||||
|
||||
TODO
|
||||
|
||||
## Instructions and Tips for Specific Tasks
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
# SIG Meet & Greet Handbook
|
||||
|
||||
## Overview
|
||||
|
||||
The SIG Meet & Greet lead recruits and arranges staffing for a session at the Summit for contributors to meet up with SIG approvers or representatives, both to allow new contributor to select a SIG the want to participate in, and for current contributors to chat with SIGs about outstanding work. The Meet & Greet may involve a "bring your own PR" exercise as well, in which case the lead ensures that attendees and SIGs are prepared for it.
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
TODO
|
||||
|
||||
## Activities
|
||||
|
||||
WIP
|
||||
|
||||
## Time Commitment
|
||||
|
||||
TODO
|
||||
|
||||
## Instructions and Tips for Specific Tasks
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
# Social Event Content Handbook
|
||||
|
||||
## Overview
|
||||
|
||||
The Social Event Content Lead is responsible for arranging and recruiting activities and/or displays during the Social Event for the Summit. The content should celebrate contributing to Kubernetes and/or help contributors meet and enjoy time together. These may include slide shows, presentations, guided socialization exercises, or even music or art.
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
TODO
|
||||
|
||||
## Activities
|
||||
|
||||
WIP
|
||||
|
||||
## Time Commitment
|
||||
|
||||
TODO
|
||||
|
||||
## Instructions and Tips for Specific Tasks
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
# Unconference Handbook
|
||||
|
||||
## Overview
|
||||
|
||||
The Unconference Lead is responsible for managing the unconference process, from session proposals to group selection to scheduling unconference sessions. The lead must decide how session proposal and selection will work at this particular summit, and then carry it out, driving participation as well.
|
||||
|
||||
If there are other types of content at the Summit, the Unconf lead will coordinate on sessions and schedules.
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
TODO
|
||||
|
||||
## Activities
|
||||
|
||||
WIP
|
||||
|
||||
- Solicit non-selected programmed session proposers to partcipate in the unconference.
|
||||
|
||||
## Time Commitment
|
||||
|
||||
TODO
|
||||
|
||||
## Instructions and Tips for Specific Tasks
|
||||
Loading…
Reference in New Issue