Quote:
|
Originally Posted by JVN
So... new clarification/change on R17... good enough?
|
Good direction - at least it gives us Saturdays back. Our primary programming mentor is only available on Tuesday evenings and Saturday mornings.
But there's work to be done for next year's rule. Paul promises some post-competition comments, which I look forward to seeing. I will just say now that FIRST has to define what their purpose is in limiting post-ship modifications. Once that purpose is defined, the mechanism of implementing it will become apparent, as will how the rule should read.
If the intent is to allow teams 10 hours per week, why not just say that? Does it matter if it is divided into two periods of 5 hours, or 3 periods of 3, 3, and 4 hours? We don't want to get ridiculous with it, using a chess timer to or timeclock to check in and check out each individual minute. Just come up with a way to have more flexibility.
I don't want a continuous Fix-It Window. But I don't want to be out of technical compliance with a rule simply because our schedule doesn't fit the schedule of every other team in the country, while still meeting the spirit of the rule.