kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updates events-team registration handbook

This commit is contained in:
Nabarun Pal 2019-09-09 20:37:11 +05:30
parent 2bb44fea2c
commit 7000e795b5
No known key found for this signature in database
GPG Key ID: 611D5079D826B150
1 changed files with 42 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
events/events-team/registration/README.md
View File

@ -3,7 +3,7 @@
The Registration lead role is charged with handling all aspects of attendee The Registration lead role is charged with handling all aspects of attendee
registration workflow; including before the event and potentially day-of. This registration workflow; including before the event and potentially day-of. This
includes: includes:
- Creating the registration system or coordinating with the CNCF Events manager - Creating the registration system or coordinating with the CNCF Events manager
to make one. to make one.
@ -60,19 +60,45 @@ workshop organizers.
In addition to any path specific questions, all attendees should be asked the In addition to any path specific questions, all attendees should be asked the
following: following:
| Question | Required | Notes | | Question | Type | Required | Notes |
|----------------------------------------------------------------|----------|---------------------------------------------------------------| |----------------------------------------------------------------|-----------|----------|---------------------------------------------------------------|
| Name | yes | | | Name | Free Text | Yes | |
| Email | yes | | | Email | Free Text | Yes | |
| GitHub Handle | yes | | | GitHub Handle | Free Text | Yes | |
| Signed the CLA | yes | Provide link to CLA | | Signed the CLA | Dropdown | Yes | Provide link to CLA. Options: Yes, No - but will do before workshop, No - cannot sign due to work resrictions. |
| Food Restrictions | yes | values: `none`, `Gluten Free`, `Vegetarian`, `Vegan`, `Other` | | Food Restrictions | Dropdown | Yes | Options: `none`, `Gluten Free`, `Vegetarian`, `Vegan`, `Other` |
| Swag Related Question | yes* | Swag question is generally shirt size. | | Swag Related Question | Dropdown | Yes | Swag question is generally shirt size. |
| Social Event | yes* | Required if there is an independent social event. | | Social Event | Dropdown | Yes | Required if there is an independent social event. |
| Emergency Contact | No | | | Emergency Contact | Free Text | No | Name and Phone Number. Phone number to be verified. |
| How can we make this a valuable event for you? | No | | | How can we make this a valuable event for you? | Free Text | No | |
| If you had a speaking slot, what would you like to talk about? | No | | | If you had a speaking slot, what would you like to talk about? | Free Text | No | |
| Where did you hear about the Contributor Summit? | Checkbox | No | Options: `Twitter`, `mailing list`, `GitHub`, `community meeting`, `SIG/WG Meeting`, `Slack`, `Other` |
Following are some of the path specific questions that have been asked in the past:
**New Contributor**
| Question | Type | Required | Notes |
|----------------------------------------------------------------|-----------|----------|---------------------------------------------------------------|
| Laptop availability for workshop | Dropdown | Yes | Should be mentioned that workshop can still be attended if laptop is not available and pair with other participants. Options: Yes, No - do not have a laptop, No - have one but cannot install software on it without IT approval |
| Have you joined the kubernetes slack? If so, what is your handle? | Free Text | No | |
| If you had a speaking slot, what would you like to talk about? | Free Text | No | |
| Are there any areas of Kubernetes you're already interested in contributing to? | Checkbox | No | Options: `API`, `CLI`, `testing`, `docs`, `community`, `release`, etc |
| Are there any SIG's you are interested in joining? | Free Text | No | |
| What are you hoping to get out of the contributor summit? | Free Text | No | |
| Experience with Go | Dropdown | No | Rate from 1 to 5, with 1 being no experience |
| Experience with kubernetes as a user | Dropdown | No | Rate from 1 to 5, with 1 being no experience |
| Experience of developing application that integrate with kubernetes | Dropdown | No | Rate from 1 to 5, with 1 being no experience |
**Active Contributor**
| Question | Type | Required | Notes |
|----------------------------------------------------------------|-----------|----------|---------------------------------------------------------------|
| Are you member of a Kubernetes Github Org? | Dropdown | Yes | |
| What SIG's or WG's are you most active in? | Checkbox | Yes | Options: List of the SIG's and WG's |
| What session(s) would like to see at the summit? what would make this event valuable to you? We've changed content based on contributor feedback to this question in the past. | Free Text | No | |
Additionally, a separate form can be created for registering the `summit staff`.
### Selecting the Registration System ### Selecting the Registration System
@ -100,7 +126,7 @@ a system include:
TODO: insert link/note to reg system used for KubeCon CN TODO: insert link/note to reg system used for KubeCon CN
--> -->
In past events, registration systems that have been used were [Google Forms], In past events, registration systems that have been used were [Google Forms],
[SurveyMonkey], and [cvent]. All have their pluses and minuses. [SurveyMonkey], and [cvent]. All have their pluses and minuses.
[Google Forms] is flexible and easy to get data in and out of, as it is [Google Forms] is flexible and easy to get data in and out of, as it is
essentially just a form on top of a spreadsheet. However, it lacks useful other essentially just a form on top of a spreadsheet. However, it lacks useful other
@ -128,13 +154,13 @@ that may mean asking them to switch tracks.
A few scenarios that have occurred: A few scenarios that have occurred:
**A person has signed up for the New Contributor Workshop, but in their **A person has signed up for the New Contributor Workshop, but in their
comments have mentioned they are unfamiliar with Kubernetes.** comments have mentioned they are unfamiliar with Kubernetes.**
They may have interpreted the event as an _"Introduction to Kubernetes"_ from an They may have interpreted the event as an _"Introduction to Kubernetes"_ from an
end-user perspective. In this case it is best to reach out to them and provide end-user perspective. In this case it is best to reach out to them and provide
more context for the event. They will likely apologize and ask to be removed. more context for the event. They will likely apologize and ask to be removed.
**A person who looks to be an Active Contributor has signed up for the New **A person who looks to be an Active Contributor has signed up for the New
Contributor Track.** Contributor Track.**
This could be accidental, or in some scenarios a non-code contributor is looking This could be accidental, or in some scenarios a non-code contributor is looking