-
Notifications
You must be signed in to change notification settings - Fork 39
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
Creating private issues for student data archival requests! #2866
Comments
@felder's suggestion is to move such requests to a ticketing system of choice - Service Now or JIRA. To be discussed during the November sprint planning meeting. |
Yeah, this was the reason I had initially used the email address in the note. |
A bit off topic: |
Thanks a lot, @flawnn for starting the discussion again. Hoping that GitHub prioritizes this feature soon. Thanks for giving us a heads-up! Appreciate it. |
@flawnn thanks! I wonder if github even has any interest in solving this issue though. "Privacy" is something github charges for, although I guess I could see them including this feature in paid plans. We also do have plans to automate this in the future so that students can securely obtain their files and they don't have to wait for support to do the retrieval. |
Summary
Currently, our data archival requests are out to the public. It may not be an ideal scenario as all the student email details are publicly accessible which may not align with FERPA requirements. We should explore creating private issues for such requests so that student details are held privately.
My initial exploration led me to find this github issue to allow private issues in a public repository. Despite this being a feature requested way back in 2013, Github has not solved it, unfortunately (at least based on my current understanding). So creating this issue to explore alternate scenarios where such requests details are held private by using other suggested options such as GitLab or creating a private repository to handle this issue from now on.
Tasks to complete
The text was updated successfully, but these errors were encountered: