Meetings

[thefro526]

We only have 2 or 3 'mandatory' meetings during build. The first meeting is Kick-Off and the Second and Third are brainstorming.

Other than that, we don't force anyone to show up. To be considered for the Championship a student needs to log at least 2 build sessions a week out of a total of 10 to 11 sessions.

Usually, this leads to a core group of students that know the robot inside and out, and a lot of less involved members that still can say they 'worked' on the robot.

We're hoping to change this in the coming season, by switching up some build methods and finding more things for people to do. We'll see if it works.

[superbotman]

At the begining of the year our mentor tells the team, "The world belongs to those who shows up". Then he lets people decide if they want to come or not, no team meeting is mandatory for everyone. However, the less you show up, the worse your chances of being on the team the following year are. Meetings about competitions and important events are mandatory if you want to attend the event.

[Chris is me]

Kickoff is mandatory for the team, as are officer elections and occasional meetings in the fall. I don't think we've had an instance of someone not showing up to mandatory meetings and still demanding to travel.

We try to bring anyone we can to competitions, because we've found it takes one competition to really inspire students into putting extraordinary effort into the team. They really seem to bring the best out of students. While some slow starters may not be of the best benefit to the team initially, the team exists to help students, not just the other way around.