|
| 1 | +# Contributors Awards Ceremony Playbook |
| 2 | + |
| 3 | +Kubernetes has a tradition of yearly peer awards. |
| 4 | +These are commonly handed out during the end-of-year Contributor Summit. |
| 5 | +The CNCF typically has awards as part of KubeCon + CloudNativeCon, the Kubernetes awards are a compliment to those, and are meant to be peer awards. |
| 6 | + |
| 7 | + |
| 8 | +## Ideals and Values |
| 9 | + |
| 10 | +Typically each SIG will nominate two(2) recipients for an award. |
| 11 | +Ultimately the individual SIGs are responsible for their award nominations, in certain cases there may be an example of excellent work that requires more than two awards, co-chairs should use their judgement to determine if this is the case. |
| 12 | + |
| 13 | +Here are a few suggestions or ideas that make for a good award nominee: |
| 14 | + |
| 15 | +- Contributions to the project |
| 16 | + - Should consider contributions to the SIG and to upstream Kubernetes |
| 17 | + - Many contributors work on other projects, these awards are specific to Kubernetes itself |
| 18 | + - In some cases a top-level CNCF award nomination might be more appropriate |
| 19 | + - Should consider contributions to other SIGs, especially cross-SIG collaboration |
| 20 | + - Should consider large multi-cycle work that encompasses multiple releases |
| 21 | +- Kubernetes Values |
| 22 | + - Is the person exemplifying the Kubernetes values? |
| 23 | + - Remember that non-code contributions are important! |
| 24 | +- Community Input |
| 25 | + - Leads should take input from other SIG members, larger SIGs might consider mentioning the awards ahead of time to allow members to communicate nominations to leads. |
| 26 | +- Celebrate the Individuals as people |
| 27 | + - Awards are affiliation-free and earned by individuals, we do not mention vendors at all as part of this process |
| 28 | + - Vendors are encouraged to celebrate individuals via their own social properties, the awards themselves will remain neutral |
| 29 | +- Spread the Wealth |
| 30 | + - Should consider lookin at underserved areas of the project |
| 31 | + - For every "rock star" there's probably a few people quietly doing excellent work. |
| 32 | + - Should consider past awards, having the same person winning the award repeatedly shouldn't be the norm. |
| 33 | + |
| 34 | +## Process |
| 35 | + |
| 36 | +### Coordinating with the CNCF |
| 37 | + |
| 38 | +Typically a representative from the CNCF will be assigned to assist with the awards. |
| 39 | +Payment of the vendor MUST happen through the CNCF, do NOT pay for community awards with your work credit card, keep the awards affiliation free. |
| 40 | + |
| 41 | +Coordinate with the CNCF to determine the budget to ensure that the awards fit within it. |
| 42 | +Shipping costs and other fees like customs, etc. might be taken into account so it's important to set this goal first before proceeding. |
| 43 | + |
| 44 | +The CNCF will also help brainstorm awards and recommend vendors, if you need it. |
| 45 | +Generally speaking we try to come up with something creative and unique. |
| 46 | + |
| 47 | +### Determining the Award |
| 48 | + |
| 49 | +Our community is clever and unconventional, the awards should be classy, but quirky. |
| 50 | +The awards should also be a "surprise" when unveiled, discussion about the awards are done publically as part of SIG Contributor Experience. |
| 51 | +The contributor summit subproject owners will determine how best to keep this open secret, usually leaving out the award specifics from the meeting notes or meeting recordingss are enough to keep it fun and a surprise. |
| 52 | + |
| 53 | +Here are some examples of past awards: |
| 54 | + |
| 55 | + |
| 56 | +### Choosing a Vendor |
| 57 | + |
| 58 | +Vendors are important! |
| 59 | +Our community is spread all over the world, so when choosing a vendor consider if they can ship to where our contributors are, not just the US and EU. |
| 60 | + |
| 61 | +### Checklist |
| 62 | + |
| 63 | +- [ ] Contributor Summit Planning Begins |
| 64 | +- [ ] Event Team should assign someone as the Awards Lead and one or two shadows |
| 65 | +- [ ] Awards Team determines what kind of award for that Contributor Summit |
| 66 | +- [ ] Awards team should plan for 3 weeks of vendor research |
| 67 | +- [ ] Once an Award has been selected, the vendor needs to be approved by the CNCF Representative |
| 68 | + - [ ] Can they ship to the countries we need? |
| 69 | + - [ ] Do they accept our payment options? |
| 70 | + - [ ] Ideally the vendor can handle accepting a planning spreadsheet from us so they can produce the awards. |
| 71 | + - [ ] Customs considerations |
| 72 | + - [ ] Other things Deb looks for go here |
| 73 | +- [ ] Create an Awards Spreadsheet |
| 74 | + - [ ] With the Kubernetes Gsuite Account |
| 75 | + - [ ] Only the Awards team, the CNCF Representative, the lead of the Contributor Summit Planning, and SIG Contributor Experience should have access to this sheet. |
| 76 | + - [ ] Awards Nomination should be announced to the SIG Chairs/TLs via their normal channels. |
| 77 | + - [ ] Awards team collects nominations from the SIGs and fills out the tracking sheet. |
| 78 | + - [ ] Name, Address, Phone number, github handle, email - Vendors will usually need more info depending on customs |
| 79 | + - [ ] CNCF Representative proofs and ensures the sheet has all the fields/information that the vendor requires. |
| 80 | + - [ ] Do not assume that nominators, coworkers, etc. have spelled submissions correctly, you need to double check each name and address, having to redo an award because of a typo can get expensive. |
| 81 | +- [ ] Coordinate with the Marketing Team |
| 82 | + - [ ] Awards tweets for the ceremony |
| 83 | + - [ ] Awards tweets for the winners |
| 84 | + - [ ] Blog post announcing the winners, and linking to the contributor site page |
| 85 | + - [ ] Amplify awardee social media posts when they post pics of their awards, thanking people, etc. |
| 86 | + |
| 87 | +### Awards Ceremony |
| 88 | + |
| 89 | +The Awards Ceremony is typically done as part of the Contributor Summit. |
| 90 | +There may be cases where the ceremony is separate or virtual, here are some tips: |
| 91 | + |
| 92 | +- Ceremony should be fun, but taken seriously. |
| 93 | + - Awards team should either be the hosts or select someone appropriate to be the hosts. |
| 94 | + - The ceremony is all about the awardees and celebrating their achievements. |
| 95 | + - [link to last one] |
| 96 | +- Ceremony should be easy to share and easy for other contributors to celebrate. |
| 97 | + - Pregenerate tweets so people can share. |
| 98 | + - Try to mention names and github/twitter/social handles so that it's easier for the audience to share |
| 99 | + - (This should be rewritten so it doesn't sound so partisan but whatever, jorge) - If you have time find tell one of their coworkers in the project so that their employer knows that they're getting an award, we want companies to celebrate and reward when their employees do awesome things. Get them in on the secret. :D |
| 100 | +- During actual Contributor Summits |
| 101 | + - It might be more efficient for the team to bring one example of the award from the vendor to show as part of the ceremony instead of bringing all the awards to the event! |
| 102 | + - Consider awardee's travel luggage, in many cases drop shipping will be much easier and cheaper. |
| 103 | +- Virtual Contributor Summits |
| 104 | + - Usually a picture of the award is sufficient and then drop ship the rest. |
| 105 | +- Awardees should be made aware of logistics |
| 106 | + - The awards are given during the time right up to the end of year holidays, shipping after the holidays is usually easier, awardees should be given a general idea of when the award ships. |
0 commit comments