[ahartnet]

When I was a mentor for 1646 at Purdue back in...2007 (I think?) we tried to do rotation, but with mentors - not students. We were doing this because all the team mentors were college students though (no professional engineers, and just 1 un-involved teacher that was the non-college/high school student), and it was tough to take that much time away from a college course load

What we basically did was something a schedule like this A+B team (get everyone on the same page); A team (X meetings in a row); A+B team (one night, update B team on A team problems/solutions/progress), B team (X meetings in a row), then repeat.

This doesn't meet your needs exactly. It might be feasible to have your different subteams on different schedules so that the A+B team nights isn't the whole team, but only say the whole manipulator subsystem or whatever.

It's simultaneously great and not-helpful that all your non-building subsystem teams are also involved in the robot building process. It'd be great if they could just meet somewhere with some computers or wifi access and get some of the work done remotely. That might help some nights, but it doesn't sound like it would be a solution.

Best of luck to y'all this year. It's a problem that needs a solution, but like you mentioned it's a good kind of problem to have!