[P&S Initiative] Shared folders with access control

[Gman0909]

Description

Currently, we have a simplistic shared folder that admins of a JupyterHub can write to, and everyone else can only read from. This works for some subset of use cases, but not all. It would be very useful to have a way for users to create ad hoc shared folders that they can share with specific other users, based on either JupyterHub group memebership or just by username. This would allow students to collaborate together, as well as allow for designated 'collection zones' set up by admins for students to submit work.

What is the benefit of solving the problem?

Instructors can work together on materials before sharing it with students (https://github.com/2i2c-org/infrastructure/issues/262)
Students can collaborate together on same or similar notebooks, for particular assignments
Researchers can more easily collaborate with each other

How will we know when the problem has been solved?

Community leaders are able to set up groups of users with access to a specific folder or list of folders in their hub.
How could we measure the impact or benefit of the solution?
See how many users are creating such shared folders

Documents and Resources

Asked for in the following places
https://github.com/2i2c-org/infrastructure/issues/2306
https://github.com/2i2c-org/infrastructure/issues/262
CryoInTheCloud/hub-image#43
https://github.com/2i2c-org/infrastructure/issues/2052

Tasks

• Identify key community contacts from whom to gather feedback
• Contact our community contacts to gather needs and wants
• Scope out a solution based on identified needs
• Develop and test the solution at the earliest stage of functional completion. Iterate if needed
• Make the solution replicable
• Deploy at scale
• Communicate to our communities that the solution is available

Definition of Done

• The feature/service is technically complete
• It’s been tested with one or more users (if applicable)
• It’s been deployed to a production cluster
• It has been shown to be replicably deployable
• It is well documented
• It has been added to our product menu.
• Lessons learned have been documented