[Nuttyman54]

just a fewthings to say:

Everyone here seems to be focussing on the fix-it window IMMEDIATELY after ship. there are duplicate windows following each regional competition per <R20>.

that said
1) I agree with everyone who thinks the first fix-it window should be more flexible than just two 5-hour work periods. Alternatively, give teams a break and move the post-ship fix-it window to the two days immediately preceding the first regional event.

2) I see no reason that they have to limit programming to that period alone. Why not let teams experiment with new controls (ie. steering wheels)? As it is, teams attending multiple regionals have MORE programming time than everyone else. I know our programmers would KILL for more time, because they know they're not going to get very much at the events.

3) If a team gets their spare parts made by a machine shop, does that shop have to complete the parts within the fix-it window?