I'm pretty sure the following flow is possible:
- A student in a Github organization gets an assignment Github repository, which is private.
- The student logs into RStudio Cloud and starts a new project in her own workspace from this private Github repo.
- The only difference when uploading a private vs. a public repo is that with a private repo RC asks for Github user + password.
- The student solves assignment and can then make here project public, available for everyone with a link to see.
And thus, the point of having a private repo for an assignment can be completely bypassed using RC.
For comparison, Binder does NOT currently allow you to do this, see here: https://github.com/jupyterhub/binder/issues/183
Is there a way to prevent/control this? Obviously this student shouldn't do this and even without this students can cheat but it's a clear gateway for cheating.. @mine