Separate github teams by semester

[janka102]

I believe suggested by @jakeloo, each semester should have a new team for dvcoders members. This makes it easier to remove old/inactive members if need be. Any other pros/cons?

Currently we just have Developers and Kernel.

Name suggestions:

• Developers-[sem][yr], ex Developers-sp17

• [sem][yr]-Developers, ex sp17-Developers

• devs-[sem][yr], ex devs-sp17

• devs-[semester]-[year], ex devs-spring-2017

• Pretty much any variations of the above

• Figure out if they can be automatically created or needs to be manually created

• Update github signup code

[jakeloo]

my vote, [group]-[semester]-[year] in lowercase.
developers-spring-2017

group creation: https://developer.github.com/v3/orgs/teams/#create-team

let's also rename Developers to developers-legacy or nuke it.
kernels can be kept the same, but moving forward (next semester) let's move it toward the new format.

[janka102]

OK sounds good. Just changed the current one to legacy. Another question would be when do we starting adding to the next semesters' team. Like when is the cut off for putting people into Spring vs Fall teams. For Spring it could be after last day in December maybe? and Fall could be after last day in May.