Community: Define more roles for SIG network

Created on 15 Feb 2019  路  7Comments  路  Source: kubernetes/community

Taking some inspiration from https://github.com/kubernetes/community/issues/3076

I think some well-defined roles will help increase contribution and provide opportunities for recognition. Starting this as a place to discuss which roles make sense for the SIG.

These can be regularly rotating positions (e.g., each release cycle, or something similar) to encourage more folks to get involved! As suggested by @parispittman, it would be awesome if each role also had an "understudy" or partner to help spread knowledge.

Here are a few roles I think would be great to have as a starting point for discussion. Obviously they'll need a bit more definition!

New contributor / community ambassador

Responsible for helping to welcome new contributors to the SIG, representing the interests of new contributors and the rest of the Kubernetes community (maybe two distinct roles?)

Triage captain

Responsible for organizing the triage of new bugs and issues related to SIG network, maintaining issue backlog.

Test captain

Responsible for health of automated tests, and SIG network test coverage.

Project manager

Responsible for helping to define project road map for SIG network.

Docs captain

Responsible for health of SIG network docs

lifecyclfrozen sinetwork

Most helpful comment

I'd be happy to volunteer for PM, or if that's taken/contentious, new contributor/community ambassador.

All 7 comments

/sig network

I'd be delighted to help out as triage captain/understudy .

How about a role for someone who undertakes to hang out in #sig-network on Slack and give pointers to people who show up with generic questions (e.g. "that would be better asked in $product slack" or "suggest you file an issue on GitHub") ?.

cc: @bowei

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/lifecycle frozen

I'd be happy to volunteer for PM, or if that's taken/contentious, new contributor/community ambassador.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ehashman picture ehashman  路  4Comments

bboreham picture bboreham  路  4Comments

parispittman picture parispittman  路  3Comments

nikhita picture nikhita  路  4Comments

justaugustus picture justaugustus  路  5Comments