Community: ContribEx Guide Needs to Recommend Mailing List Best Practices

[chris-short]

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:
As a Kubernetes community member, it is difficult to attain a good signal-to-noise ratio with regards to GitHub notifications and mailing list messages.

What you expected to happen:
I'd like to get some guidance on how to be an effective communicator in the Kubernetes community. In other words, not be deluged by all the e-mail. Specifically, what to do with GitHub and Gmail to surface the pertinent content and purge the less personally meaningful content.

How to reproduce it (as minimally and precisely as possible):
Join as a Member, help out with more than one SIG.

Anything else we need to know?:
N/A

Environment:

• Kubernetes version (use kubectl version): N/A
• Cloud provider or hardware configuration: N/A
• OS (e.g. from /etc/os-release): N/A
• Kernel (e.g. uname -a): N/A
• Install tools: N/A
• Others:

cc @castrojo @bgrant0607 @idvoretskyi
/sig contributor-experience
/area contributor-guide

[castrojo]

This should probably live in k/community/communication/ as a separate document (the README covers general communication topics and we shouldn't clutter that). Then we link it from that top level README and then also add it to the communication section of the contributor guide.

I'm thinking:

• Collected mailing list filters from people
• Links to mailing list etiquette documents (likely some good ones out there we can just link to).
• Maybe a list of all the mailing lists in one place generated from sigs.yaml?

[idvoretskyi]

https://groups.google.com/forum/#!msg/kubernetes-dev/5qU8irU7_tE/aZov0LpCBwAJ

[castrojo]

/help

[k8s-ci-robot]

@castrojo:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

[fejta-bot]

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

[cblecker]

/remove-lifecycle stale

[cblecker]

Something to add to this:
Yeah, it's a bit of a mess right now with notifications.. and I'm not a fan of the whole mailing list mirrors (biggest reason is there is no way to unsubscribe from a thread if it was incorrectly mentioned).

[guineveresaenger]

Motion: while this is important to do, it shouldn't be a blocker to publishing the contributor guide.

[bgrant0607]

My conclusion is that notifications are hopeless. I'd be fine with getting rid of all the SIG-related github teams and mailing-list mirrors.

[bgrant0607]

To be clear: I'm am completely DoSed by notifications, so it's all white noise to me.

[castrojo]

I'd like to take this on as part of the mailing list moderator work. I can write something up to make this better, and we should probably take a hard look at having multiple teams and lists per SIG.

I don't have a solution for github notifications, it feels like we're all over it, and the best way to handle that is to interface with the github folks directly.

[fejta-bot]

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

[nikhita]

/remove-lifecycle stale

[fejta-bot]

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

[idealhack]

/remove-lifecycle stale
/lifecycle frozen

[nzoueidi]

/remove-lifecycle frozen
/lifecycle active

I am working on this.