Revert "Add initial descriptions for all potential content roles for Contributor Summits. Much more detailed handbook work needs to be filled in, but this creates the documentation framework that shows what various memembers of the Content team are doing, and they can fill in the roles as they perform them."
This reverts commit 57f868254d.
This commit is contained in:
Josh Berkus
parent
57f868254d
commit
bdaf7efc29
|
|
@ -18,8 +18,8 @@ the logistical and operational pieces together.
|
|||
| Registration Lead | [Registration Handbook] | |
|
||||
| Marketing Lead | [Marketing Handbook] | |
|
||||
| CNCF Events Manager | CNCF | CNCF will staff this |
|
||||
| Content Coordinator | [Content Handbooks] | |
|
||||
| New Contributor Workshop Lead | [Content Handbooks] | Events Lead and General Content will determine this |
|
||||
| Overall Content Lead | [Content Lead Handbook] | |
|
||||
| New Contributor Workshop Lead | [Content Lead Handbook] | Events Lead and General Content will determine this |
|
||||
| Accessibility, Inclusiveness, and Diversity | TODO | |
|
||||
|
||||
|
||||
|
|
@ -65,4 +65,4 @@ We don't coordinate meetups. CNCF leads these efforts and their information can
|
|||
[here]: https://github.com/cncf/meetups
|
||||
[Event Lead Handbook]: ./events-lead.md
|
||||
[Marketing Handbook]: ./marketing/README.md
|
||||
[Content Handbooks]: ./content/README.md
|
||||
[Content Lead Handbook]: ./content-lead.md
|
||||
|
|
|
|||
|
|
@ -0,0 +1,67 @@
|
|||
# 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
|
||||
|
||||
## 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.
|
||||
|
||||
## Skills and Qualifications
|
||||
|
||||
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.
|
||||
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
|
||||
|
||||
*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 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.
|
||||
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.
|
||||
- Work with Registration to:
|
||||
- disseminate course materials (slides) in advance
|
||||
- ensure participants sign the CLA
|
||||
- ensure attendees meet technical and experience requirements for their course
|
||||
- obtain a comprehensive list of names, emails, and github handles
|
||||
- Incorporate the new contributor playground into the workshop.
|
||||
Create a New Contributor Workshop folder specific to this event, with teachers' and participants' github handles in the OWNERS file - [here is an example](sigs.k8s.io/contributor-playground/seattle)
|
||||
- Coordinate with the [SIG Meet and Greet organizer](sig-contrib-events.md) (may be a different role to be determined by core team)
|
||||
- Ensure to advertise the SIG-Intros
|
||||
- Solicit feedback from workshop participants
|
||||
|
||||
## Time Commitment
|
||||
|
||||
1-2 hours/week most of the time, 4-5 in the weeks leading up to KubeCon, depending on previous teaching/shadowing experience.
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
# 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
|
||||
Loading…
Reference in New Issue