Update the README to clarify support resources #802
Conversation
|
Some projects such as Puppet will disable issues and have the community use their ticketing system. If this is highly valuable for Sensu and is done across all the projects, then we should do it, but it does come at a cost. Users have to have an account there and it takes extra steps. The extra steps add friction to the process that will discourage some folks from participating. |
|
I'm not suggesting that we take community participation out of GitHub. We're talking about end-user support (i.e. GitHub issues vs Sensu support) and making it clear to users that where they should expect to get support from (read: not Puppet Inc). There's certainly some grey area in there which is why I wanted to discuss and clarify it here before we commit any changes. |
|
👍 I think we should make it clear where they should go for support when they have questions about the module not working as expected etc. We can then create issues against the module here. I don't think we should remove the ability of users to add issues here themselves though, as this might be what they're used to and we should let them continue if they choose. Obviously the SLAs won't apply with issues submitted directly to the repo though. |
|
SGTM, thanks @agoddard @ghoneycutt! |
|
v2.33.1 |
Users should rely on Sensu, not Puppet Inc, for support of this module. This clarification was requested by our friends at Puppet.
@ghoneycutt @agoddard Any concerns wrt directing users to our support page rather than opening issues here instead?