Document org-wide process for offtopic troll issue response
Organization or repository
Describe the issue
I'd like the README at https://github.com/kubernetes/org#readme to signpost people (me!) to advice about how a maintainer can and should respond if offtopic troll issues come up. (the response is likely to be to lock the issue, but it's a rare enough concern that we might not remember the details)
/kind feature /sig contributor-experience I think
Opinion (specifically about the one from earlier):
- Lock immediately (maybe also snapshot)
- Flag @kubernetes/owners
- Org-level ban
- Delete
@sftim One approach would be to add github guidelines in the set of guidelines we have for most of the collaboration platforms: https://github.com/kubernetes/community/tree/master/communication.
Yup - that is the place with all our comm policies / procedures.
Hi @sftim , I would like to work on this issue, can you help me with what I need to add and where? Thanks
Hi @Nivedita-coder--I'd be happy to guide you on how to move forward with this if you're still interested in taking it on! :) @sftim would that work for you?
Hi @Nivedita-coder--I'd be happy to guide you on how to move forward with this if you're still interested in taking it on! :) @sftim would that work for you?
Yes, I'm interested. It will be great for me ,Thanks @celanthe! :)
/assign
An update on this, I met with @Nivedita-coder yesterday 1/27/21 via Zoom and walked her through how to structure a new PR that will address this issue and includes the changes suggested here! :)
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-contributor-experience at kubernetes/community. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
/remove-lifecycle rotten /lifecycle frozen
/priority important-longterm /milestone v1.23 /help @celanthe @Nivedita-coder any progress on this? please /remove-help and /assign yourselves if you're still working on this
@spiffxp: 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:
/priority important-longterm /milestone v1.23 /help @celanthe @Nivedita-coder any progress on this? please /remove-help and /assign yourselves if you're still working on this
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.