This begs the question of what you're looking to get out of a git/VCS setup. Unless you're forcing everyone to setup their own Gitlab instance, is your CS depar

This begs the question of what you're looking to get out of a git/VCS setup. Unless you're forcing everyone to setup their own Gitlab instance, is your CS department looking to offer a handful of students limited experience with a single task? Or are you looking to use VCS to benefit all of your students during the entirety of their time in your program? The entire idea behind using VCS in education is to enable better/deeper learning. Github lets students jump right into versioning their work and collaborating with classmates/instructors with minimal fuss and zero overhead. Not to mention that exploring Github can help introduce them to the open source community. Plus, they don't have to deal with IT department BS, worrying about when their old work will be deleted, or the myriad of other factors that can impact how students integrate git into their work. From a departmental perspective, where time and resources are always stretched it's a no-brainer. Besides, at least Github isn't Blackboard. :shudders: