celebrating orgs with full time maintainers
parispittman opened this issue · comments
Problem Statement
hiring and retaining full time maintainers (those who are contributing at 75% or higher of their time) should be celebrated because it's hard for managers and businesses to justify this kind of contribution.
Proposed Solutions
- add a page on k8s.dev/orgs with company logos who currently employ full time OWNERs to areas of Kubernetes
- add booth signage to companies who meet this criteria at kubecon/cloudnative cons (thanks to @eddiezane for this idea and adding some in Detroit!)
Cost
n/a; professional signage could have a cost for #2 or we could allow companies to do their own
Open Questions
- How do we know for sure that someone is full time on the project? [possible solution: add names and/or handles publicly or privately, community moderation, private emails to steering@, steering reviews on a yearly basis as part of annual reports, etc]
Next Steps
- discuss at an upcoming steering committee meeting
- PR a prototype into the k8s.dev website repo
@caniszczyk is going to ask marketing to help with this for kubecon and setting up a program that could help with this
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
How do we know for sure that someone is full time on the project? [possible solution: add names and/or handles publicly or privately, community moderation, private emails to steering@, steering reviews on a yearly basis as part of annual reports, etc]
That's a good question, we could survey the contributor mailinglist periodically perhaps?
We discussed this again at the chairs and tech leads meeting today.
It seemed like we have two threads:
- Celebrating employing and supporting contribution / maintainers,
- A tangent on the LetsEncrypt style promoting project / infra sponsors, which we should probably suggest / do through CNCF as an addition to the Infra Credits program (AWS, GCP, Equinix, Fastly, ...).
For both it would be nice to do something like this photo by @eddiezane
I think we should bring up both with CNCF to see what they're interested in doing because if we get support for 2) which is more clearly tied to existing programs then it might make sense to expand it to also cover 1) which is what this issue originally brought up.
But if not, I think the organization can do something ourselves.
A couple possibilities were brought up today, e.g. devstats, but there's concern about including everyone.
Currently I'd suggest we ask for private feedback from dev@kubernetes.io (all project members should be on this list) to tell us if they feel their employer supports them in contributing / should be recognized for this and which employer that is.
We can then either organize producing and distributing signs like this ourselves or through the CNCF, pending further feedback on that aspect.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale