-
Notifications
You must be signed in to change notification settings - Fork 18
Update user support section #219
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| ## Support | ||
|
|
||
| **For questions and support, we recommend using [GitHub Discussions](https://github.com/dandi/helpdesk/discussions/new?category=q-a)** 🙏 | ||
|
|
||
| Additional support channels: | ||
|
|
||
| | Channel | Best For | | ||
| |---------|----------| | ||
| | ✨ [GitHub Issues](https://github.com/dandi/helpdesk/issues) | Report bugs and request features | | ||
| | 💬 [Slack](https://dandiarchive.slack.com/) | Interact with the DANDI community (available after [registration](./getting-started/creating-account.md)) | | ||
| | ✉️ [Email](mailto:help@dandiarchive.org) | Communicate privately | | ||
| | 🌟 [NeuroStars with the `dandi` tag](https://neurostars.org/tag/dandi) | Interact with the global neuroscience community | | ||
kabilar marked this conversation as resolved.
Show resolved
Hide resolved
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also have discussions which is more prominently used than issues. It is a bit unclear what should be an issue vs discussion, what about:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link to discussions is on the top but I agree that maybe we can expand on what should go to each section.
Perhaps here we can clarify that issues are for infrastructure, technical and software errors and in the top add a bullet point with the list of things are welcomed in the discussions:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding examples could be helpful as long as there aren't "too many" per section. Above all I think we should strive to keep things minimal since the docs are already overwhelming to many users
We can always (and often do) transfer issues to their appropriate destinations without the user needing to worry about that, too (which can inhibit willingness to raise out of concern of not raising in the right place)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think 3 to 6 short bullet points as above can give a flavor of the type of questions that make sense for the help channel without being too many. The idea is to help the user orient themselves among the many available help channels. That is, to answer the question: where should I go with problem x.
I do agree that it can be overdone to the point of being intimidating rather than helpful. It is a fair point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @h-mayorquin, @CodyCBakerPhD. I agree with Cody and would prefer to keep things minimal here, and we can transfer as needed.
Regarding
Where should I go with problem x?, I would say that everything should go to GitHub Discussions. And we can triage from there. So the user does not have to make any decision and can just post their question.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense.