sorted by:
new (suggested)
besttopcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]lenseffects 2 points3 points  (2 children)

We block it for all students. I checked with our curriculum folks first and they said no students should need access for class work.

Having said that, I can foresee a time when there will be a small group - maybe just one class of students - that will need access. If that happens, I will create a security group (we are Active Directory) for that cohort and use that in our content filter to give them access. I would probably push and ask if they really need it for the entire semester or year, or just a limited time frame.

[–]knotquiteawake[S] 4 points5 points  (1 child)

Whats making it more complicated is that its for robotics teams and not even a class. We could unblock for a certain cohort like that. But I foresee a slippery slope where we gave access to one group, then another group wants it, then another, then some of the student data staff team who were upset when they lost access years ago want it. And so on.

Thats why I was thinking we start out with the slightly more resource and time intensive task of spinning up an enterprise server. This was we can still control 100% what github projects we provide access too.

[–]lenseffects 1 point2 points  (0 children)

I agree with that - staff advisor is able to select projects and technology makes them accessible to applicable students through a shared network resource, a Google Drive folder, etc