Hi! I work for a non-profit teaching development.
We have a Github organisation, containing all staff and students alike.
Current setup:
- Staff have access to all relevant repo’s for them
- Students are grouped in teams (per class) and get access to repo’s based on that
- Student repo’s are their own (public or private but shared with teacher)
We are thinking about using Github Classroom: its overview and easy access rights seem like a real asset.
In the current setup, this would lead to a surge in student repo’s in the main organisation.
Our concern is that this will quickly become unmaintainable. (even taking into account the deletion of student repo’s when a class is removed after graduation)
How are you tackling this? What would be the best structure to be considered?
I didn’t find any mention of suborganisations, so currently researching if having two organisations can be a good idea: one for staff & staff projects, and one for staff both with students included.
Approach doesn’t seem ideal, as the two organisations would technically be treated as completely different, potentially leading to problems when sharing or copy-pasting from one to the other, using teams, …
1 post - 1 participant