-
Notifications
You must be signed in to change notification settings - Fork 2
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
Resolve vs Response times and guarantees #6
Comments
I just wanted to provide an example:
|
@bradrydzewski, good catch. I think "Diagnose and Resolve" needs to become "Diagnose and Respond", both in the heading and the text of the current section. Care to try your hand at a PR? Edit |
absolutely, I will send a pr :) |
I have noticed many support contracts provide an SLA for response times, but do not actually guarantee resolution. As a non-lawyer I could interpret this as developer agrees to fix bugs that I report which I would not want to agree to without a premium. In some cases I may disagree with the a bug report and determine the software is working as intended. Or I might decide the bug is an edge case and is not something I plan to fix. Or the bug may be in the prior version of software and require an upgrade but I do not want to be obligated to backport the fix.
With that being said, some larger enterprise customers may be willing to pay a premium for such language. It would be awesome if I could use your node build tools to choose between a couple of options.
The text was updated successfully, but these errors were encountered: