swag ideas for OWNERs

[parispittman]

Describe the issue

one of the staple pieces of swag we have is the kubernetes contributor patch that we give away during contributor events. now that we have a function in prow that flags new OWNERs (reviewers, approvers) with information and a swag opportunity, should we customize a patch or another piece of swag for them as an extra special thank you? OWNERs are taking on a lot of responsibility - way more than the casual contributor. Any ideas?

Ideas:

• k8s logo patch with "subproject owner" text or maybe their GitHub handle?
• k8s apparel and accessories (sizing will be an issue that will need to be solved for if its that kind of apparel) with GitHub handle
  • hoodie
  • lapel pin

Estimated yearly $:
max 5-7k
assumptions:
$50/pp (estimating a high cost)
no more than 100 a year
including estimated shipping costs since that will be our large hit; folks can pick up at kubecon but will still have

Updates:
I filed a servicedesk ticket to see what our options are here; sounds like we can definitely have a process with codes and could power the codes in an automated way/not have too many humans in the middle. Will start the set up process post KubeCon EU.

/sig contributor-experience

[ameukam]

Kubernetes Hoodie with the Github handle of the contributor. I saw this for Github employees.

[dims]

circular lapel pin with k8s logo inside and /approve and /lgtm on the border ( i treasure one similar to this for openstack that says "+2" - i think swag from HP )

[chris-short]

Standard Kubernetes patch with OWNER embroidered in/on to it

[mrbobbytables]

+1 with contribex chair hat on to start the process.
FWIW - I would avoid custom hoodies, they're nice but very $$$$$ - pins/patches and the like are much more reasonable.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.