Drop Community Effort issue designation

[agjohnson]

This is a meta-issue. Currently, issues that are outside the focus of the core team, such as internal installations and non-supported platforms, are given the designation of "Community Effort" [1]. We've documented our open source philosophy [2] that describes why we don't support these issues. Instead of leaving these issues open, does it make more sense to just close the issue and point the issuer to Stack Overflow? The core team will not address these issues directly, so leaving them open seems like a miscommunication. The flip side is that these issues are usually resolvable and are more likely to be resolved here if they are open.

cc @humitos @ericholscher

1: https://github.com/rtfd/readthedocs.org/issues?q=is%3Aopen+is%3Aissue+label%3A%22Community+Effort%22
2: http://docs.readthedocs.io/en/latest/open-source-philosophy.html

To resolve this issue:

• Update docs on contribution
• Re-triage issues labeled "Community Effort" -- note: there might be some actual issues to keep here

[humitos]

I think it's a really tough and rude (in some way) decision but I think it's necessary because of this miscommunication that you has mentioned, but I think we should continue marking those issues as "Community Effort", close them and explain why they are closed, at least linking the philosophy.

Pointing the issuer to Stack Overflow also sounds reasonable to me.

[ericholscher]

Yea, I'm +1 on closing them. Leaving them open presents a false hope of them being worked on, but as far as I can tell, they haven't really ever been addressed. Until we have members of the core team that are actively supporting local installs and want to help offer support to others, it seems like we are better off closing them with a message about priorities.

[agjohnson]

I'm mostly on the fence here, so sounds like we can make this change. I updated the description here with work items for whoever gets to it. I thought the canned responses were project-wide, but for whatever reason, GitHub didn't make those a project setting. Here's my normal response either way:

This bug is being marked as community effort. The core team will try to facilitate resolution with this issue, but without the resources to support external installations outside of our production environment, we must rely on the community to help.

You can read more information on our philosophy around supporting Read the Docs as an open source and volunteer run effort here:
http://docs.readthedocs.io/en/latest/open-source-philosophy.html

[stsewd]

We don't have the Community Effort label anymore, is this issue solved?

[ericholscher]

Yep. 👍

[RichardLitt]

We don't have the Community Effort label anymore, is this issue solved?

We do! There are some issues with it. I think we ought to delete the label if we're not going to be using it anymore. It's also still mentioned in docs/contribute.rst.

[stsewd]

Ups, wrong repo. Yeah, we still have the community effort label, but it was dropped in #4180, we need to update the rest of the docs to match the changes