Skip to content
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

Arbitrary definitions can lead to problems of interpretation #23

Closed
santosomar opened this issue May 14, 2024 · 2 comments
Closed

Arbitrary definitions can lead to problems of interpretation #23

santosomar opened this issue May 14, 2024 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation tc-discussion Further TC discussion is needed

Comments

@santosomar
Copy link
Contributor

          I do agree with @tschmidtb51 that arbitrary definitions can lead to problems.

But there are products out there with at least three different "levels" of support and I suspect others might have more.
So, I do believe that the standard should allow for "a list of support definitions" the interpretation of which can be up to the user.

e.g. RedHat has "Full Support", "Maintenance Support", "Extended Update Support"
Ubuntu has something similar.

We need to be able to model those kinds of things and I don't think the standard should mandate how many levels are allowed.
"paid/unpaid" -> this seems more like an attribute on a support level.

Originally posted by @lfrancke in #13 (comment)

@santosomar santosomar self-assigned this May 14, 2024
@santosomar santosomar added documentation Improvements or additions to documentation tc-discussion Further TC discussion is needed labels May 14, 2024
@santosomar
Copy link
Contributor Author

To address this we have opened:
#27 #28 #29 #30 #31 #32

@santosomar
Copy link
Contributor Author

Closing this issue and working through the new issues mentioned above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation tc-discussion Further TC discussion is needed
Projects
None yet
Development

No branches or pull requests

1 participant