Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I know the solution. Starting this year, students will be forced to contribute to a project they use, care about or, at the very least, truly want to use in the long term. Not one they found randomly on Github.

I expect that most of the open-source projects the students care about will be in GitHub.

So perhaps a better solution was to teach them to setup their own git repo in a cheap or free uni server.



> So perhaps a better solution was to teach them to setup their own git repo in a cheap or free uni server.

And then lose access after graduating. Great idea!


Tell the students that they will receive a one week notice during the middle of the semester that they need to migrate their git repo to a new server, then teach them the 2 or 3 commands they will need to enter to do this.

They will then understand that it is extremely easy to move a git repo.


It's just an educational exercise to teach students to setup and mantain their own git server.

Obviously students don't expect to use uni servers forever. They can setup their own with the lessons learned.


Probably but I never got why that is. It seems a school could be there in all kinds of ways for the entire duration of the career.


Any Git clone is also technically a Git server, so no, they don't lose access to their own filesystem after graduating.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: