-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RTMs not being honored #334
Comments
I think that the community should atleast help to assist with tagging of the issues, this could help devs decide what to focus on. Each repo could have a predefined set of tags people could choose from it could also be helpful if there is predefined severity tags. This could make triage easier. |
I'd gladly help to label issues, but I fail to see how that could be done as github permission model doesn't include such an option for non members of an organization. A kind of bot reading comments to add labels? |
Closing this as I'm not active in this project anymore and it doesn't look like this is going to get any attention given the delay thus far. |
As stated here in our OSS Practices, each of our repos should have a stated Response Time Maximums for both Issues and Pull Requests.
Examples can be found on the ones listed below, but it's a widespread problem across a huge number of our repos (eg: outside our primary repos)
https://github.com/chef/mixlib-install/issues
https://github.com/chef/omnibus-toolchain/issues
https://github.com/chef/appbundler/issues
https://github.com/habitat-sh/builder/issues
Unfortunately, for quite some time, these commitments have not been met (even pre-acquisition). We need to assess the viability of these commitments and either ensure we are meeting them, or adjust them for current staffing levels with the expectation that they'll be re-assessed when staffing shifts.
The text was updated successfully, but these errors were encountered: