-
Notifications
You must be signed in to change notification settings - Fork 1
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
Document where users can submit feedback on the VEDA JupyterHub (GitHub discussions?) #55
Comments
/cc @batpad |
@maxrjones I think that's a great idea! Just want to check if folks feel things are getting fragmented or so - @j08lue @freitagb would you folks have thoughts or opinions on enabling Discussions in this repository and using that to gather user feedback and discuss questions around the VEDA Jupyterhub that maybe a bit different from "Issues". @maxrjones if there's no objections, let's connect and I can go ahead and enable Discussions here. |
Yes! Ways of getting support around VEDA services could use better documentation. 🙏 @wildintellect has earlier led a spike on choosing and setting up a central support system, possibly across MAAP and VEDA (and maybe more). I think it was not conclusive, though, and we continued to use MAAP Slack for first-level support and tickets on various repos for second-level, @wildintellect? Perhaps a good occasion to revisit this? GitHub Discussions on a central repo or several ones was one of the options considered. |
We had big questions - this was one of mine...
I we tabled this in the past, because we did not have a lot of users we needed to support, besides EIS and MAAP (both using MAAP). |
Thanks for this context! If I'm interpreting those threads correctly, people were leaning towards a Discourse server that spans multiple NASA-funded groups (e.g., VEDA, MAAP, CryoCloud, OpenScapes, possibly even TOPS) which would take coordination with other group leaders. So, let's table this issue as pending an outcome from https://github.com/NASA-IMPACT/veda-architecture/issues/255. I will comment there about my interest in moving that forward. |
@maxrjones 👍 and if you need something more immediately to refer users to, I think can always ask them to make issues in this repository with any problems they are facing or questions. |
Is there already a standard place for VEDA JupyterHub users to submit feedback on their experiences? If not, could we enable discussions on this repo to be that place? I'd like to include a note in NASA-IMPACT/veda-docs#165 (or a follow-up PR) about how to give feedback on the VS Code integration.
The text was updated successfully, but these errors were encountered: