You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a Professor at Stanford, and I'm teaching an Operating Systems course that uses Pintos for its class projects. I'm writing because I see that this repository is publicly accessible and appears to contain a complete set of solutions for the projects. This is a problem for us, because it makes it very easy for students to cheat. Even if they just look at your solution, and don't copy it, that will still reduce the educational experience for them. Would you be willing to take down this repository or at least make it private? If so, that would be a great help for us.
The text was updated successfully, but these errors were encountered:
Sorry about that, I am trying to apply the student pack of Github but it seen to be a little trouble that my school email couldn't be accepted by Github.
Sorry about that, I am trying to apply the student pack of Github but it
seen to be a little trouble that my school email couldn't be accepted by
Github.
—
Reply to this email directly or view it on GitHub #1 (comment).
You can make it private now, since GitHub is now free to use private repositories.
Not only Stanford, many universities are using PintOS as their Operating Systems course project as well.
I'm a Professor at Stanford, and I'm teaching an Operating Systems course that uses Pintos for its class projects. I'm writing because I see that this repository is publicly accessible and appears to contain a complete set of solutions for the projects. This is a problem for us, because it makes it very easy for students to cheat. Even if they just look at your solution, and don't copy it, that will still reduce the educational experience for them. Would you be willing to take down this repository or at least make it private? If so, that would be a great help for us.
The text was updated successfully, but these errors were encountered: