You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to support projects in navigating CNCF services, the existing services page only mentions the CNCF servicedesk as the location where "unlisted" services may be requested.
Could each identified service include a link with where the request for the service is intended to be routed? As I understand it some, but not all services, may be requested via this repo, and others on the service desk only. This may result in confusion for projects who file a service desk ticket but are then directed to file a GH issue or to update an existing issue.
Additionally, some of the content is a bit out of date, for instance - we don't have SIGs anymore, they're TAGs.
Thank you!
The text was updated successfully, but these errors were encountered:
This came up recently while discussing with a CNCF project maintainer. It might be helpful to document this as well -- for a non-technical issue, how does one determine if they should open a ServiceDesk ticket vs open an issue in this repo, especially if no senstive information is being discussed?
Unless it's a licensing exception request (which #313 resolves but needs updating + proper review), Servicedesk is the right place for this as of right now.
While trying to support projects in navigating CNCF services, the existing services page only mentions the CNCF servicedesk as the location where "unlisted" services may be requested.
Could each identified service include a link with where the request for the service is intended to be routed? As I understand it some, but not all services, may be requested via this repo, and others on the service desk only. This may result in confusion for projects who file a service desk ticket but are then directed to file a GH issue or to update an existing issue.
Additionally, some of the content is a bit out of date, for instance - we don't have SIGs anymore, they're TAGs.
Thank you!
The text was updated successfully, but these errors were encountered: