Move all 'product feature ideas' away from this repo's issues into ProductBoard

[yuvipanda]

Context

As part of #3702, we're trying to clean up the list of open issues in this repository. One important category of issues is 'product ideas' or 'feature requests', which should now live in Product Board.

Proposal

Go through all the open issues here in this repository, and move them into productboard. This would probably entail having to reformat them into a story form or similar. The open issue can then be closed, with a link to the appropriate product board item.

Since we're moving stuff away from a public GitHub repository, it's important that the appropriate productboard location is also public. https://github.com/2i2c-org/meta/issues/900 tracks the issues in dealing with that.

Updates and actions

No response

[yuvipanda]

Here's a collected list of issues (sorting from oldest first):

• Generate human-readable page with packages installed in user image features#1
• Add admin functionality to download *all* users' home directories features#2
• Create UI/UX around choosing / generating environments features#3
• Naming conventions for shared folders features#4
• Allow admins to rename user home directories features#5
• Persist a user's custom environment between sessions features#6
• Launch user sessions in multiple cluster from a single hub features#7
• Design offboarding process that hub admins can use to offboard their users features#8
• Allow JupyterHub admins different cloud permissions than standard users features#9
• Enhance user experience around cloud storage via better integration with jupyterlab and notebook server environment features#10
• [LEAP] GitHub sub-groups don't appear as part of parent groups for the purposes of Hub access features#11
• https://github.com/2i2c-org/infrastructure/issues/1414
• Explore using billing alerting infrastructure directly from the cloud provider features#13
• User experience for a multi-hub service for University of Toronto features#14
• Batch job support for Pangeo hubs features#15
• Report Docker Image in Login Page or JupyterLab UI features#16
• Letting JupyterHub groups be used to provide access to shared NFS folders features#17
• Access to buckets on AWS and GCP from local computers features#22
• Recommendations of in-user-image and local computer tools to work against object storage features#18
• Plan for Real Time Collaboration roll out features#19
• Add SFTP service to basehub features#20
• Improving secondary RStudio UI: "shut down" and "sign out" features#21
• JupyterHub admin managed shared storage for users features#23
• Document how to make a maintenance announcement features#24
• Community facing information about grafana monitoring - access and monitoring guidance features#25
• Proto-goal: Allow hub admins to modify profileLists features#26
• Proto-goal: Formalize a paid event support policy for all our customers features#27
• Support for Canvas Authentication for cloudbank hubs features#28
• A procedure for communicating breaking changes is needed #3017
• Feature Request: History of recently used custom images features#29
• Tracking issue for VEDA work on QGIS  #3367
• Document how to pass tokens from auth_state to the user environment #3636
• Automatically pull ghg-docs repo on server start on GHG hub (same as VEDA hub) #3565
• Document how to support a sequence of hubs with an external home page features#30
• How to customize a JupyterHub and BinderHub landing pages features#31

These will be coalesced into a number of productboard items

[yuvipanda]

I'm going to comment on the appropriate issue with a productboard link for each of them, but not actually close it until we have a way to make this publicly visible

[Gman0909]

Thanks @yuvipanda. As you port this list to PB, I would recommend being as strict as you can when considering how many of these are "nice to have" versus "must have", and determine whether some of these might warrant being culled. Moving ideas across systems and into a new process is a golden opportunity to do some house clearing.

[yuvipanda]

I don't want to close any of the issues until we figure out https://github.com/2i2c-org/meta/issues/900. So I'm going to create a temporary 'feature-requests' repo, and move all these issues there so it can clean up the infrastructure repo.

[yuvipanda]

I've moved all the issues, and @Gman0909 had earlier created appropriate productboard items. I am going to link them as appropriate before calling this one done.

[Gman0909]

Does this issue still need work or can we call it done?