search

kubernetes / community

Kubernetes community content
Apache License 2.0
11.98k stars 5.17k forks source link

ContribEx Guide Needs to Recommend Mailing List Best Practices #1724

Closed chris-short closed 5 years ago

chris-short commented 6 years ago

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:

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

castrojo commented 6 years ago

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:

idvoretskyi commented 6 years ago

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

castrojo commented 6 years ago

/help

k8s-ci-robot commented 6 years ago

@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](https://github.com/kubernetes/community/issues/1724): >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/devel/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
fejta-bot commented 6 years ago

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 commented 6 years ago

/remove-lifecycle stale

cblecker commented 6 years ago

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 commented 6 years ago

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

bgrant0607 commented 6 years ago

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 commented 6 years ago

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

castrojo commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

/remove-lifecycle stale

fejta-bot commented 5 years ago

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 commented 5 years ago

/remove-lifecycle stale /lifecycle frozen

ezzoueidi commented 5 years ago

/remove-lifecycle frozen /lifecycle active

I am working on this.