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

Request: Update Services page with places for requesting services #611

Open
TheFoxAtWork opened this issue Aug 3, 2023 · 5 comments
Open
Assignees

Comments

@TheFoxAtWork
Copy link
Contributor

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!

@amye
Copy link
Contributor

amye commented Aug 3, 2023

This is actually a mirror of https://github.com/cncf/servicedesk - @jeefy @krook for discussion next week

@nikhita
Copy link
Member

nikhita commented Aug 3, 2023

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?

@amye
Copy link
Contributor

amye commented Aug 3, 2023

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.

@nate-double-u
Copy link
Member

The old "navigating CNCF services" URL now forwards to https://contribute.cncf.io/resources/project-services/cncf-support/ (and the https://github.com/cncf/servicedesk page links there as well).

We've made a lot of updates to the CNCF Support info, and (correct me if I'm wrong here, @jeefy) they should all be requested through the service desk web portal now (https://contribute.cncf.io/resources/project-services/faq/#how-do-i-file-a-ticket-with-the-service-desk).

Do these changes solve your concerns?

@TheFoxAtWork
Copy link
Contributor Author

Not entirely.

If i'm a project maintainer with a particular question about license exceptions, or even to file an exception, the page does not correctly direct me to where i need to go. The link for CNCF Service Desk is somewhat buried to submit an inquiry, and the license exception process (not discussed on the page or linked to the policy) is through the issue template on the foundation repo, not service desk.

there is still an outdated reference to SIGs on the site, but that is less pressing.

The original concern was around discoverability of where to go to request support.

the page provided ( https://contribute.cncf.io/resources/project-services/cncf-support/) Does not link to the Service Desk at all.

the top level page (https://contribute.cncf.io/resources/project-services/) does, but only as the following comment:

it’s completely OK to reach out to staff via the CNCF ServiceDesk and ask for help.

which seems more appropriate for general questions rather than specific.

Ideally, and simply, adding the below to the cncf-support page would resolve this issue, with the additional below amendment regarding licensing:

To request support for any of these services or to ask general questions, please file a service desk ticket here: https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1

for License exception requests, please refer to the CNCF license exception policy and file an exception issue here: https://github.com/cncf/foundation/issues/new/choose

Does this make sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants