In the timeseries hackathon, we noticed that to allocate late comers (people who join after the teams being already built) we have to completely re-do the teams (basically, it seems to be a random team assignment based on a provided list).
A good upgrade to this, since this situation causes some entropy at the beginning of a hackathon, would be for the "team-builder" to first check if there are already teams and, if so, only allocate the new people to already existing teams.
An important note from @cimendes, this would need to obey to the constraint of the team size limit.
In the timeseries hackathon, we noticed that to allocate late comers (people who join after the teams being already built) we have to completely re-do the teams (basically, it seems to be a random team assignment based on a provided list).
A good upgrade to this, since this situation causes some entropy at the beginning of a hackathon, would be for the "team-builder" to first check if there are already teams and, if so, only allocate the new people to already existing teams.
An important note from @cimendes, this would need to obey to the constraint of the team size limit.