[David Brinza]

Originally Posted by seanwitte

Its very clear and I think you're doing a disservice to the rest of the community by debating this. Whether you agree with the rule or not (and I don't) you cannot work on code related to the competition robot outside of the build season, fix-it windows, and competition events. There is no way to police this so you're on your honor not to cheat. If you work with a practice robot and modify code with the intent of replicating those changes at the event then you are violating the rules. If you're testing and tracking bugs with the necessary fixes outside of the fix-it window then you're cheating. I don't think its good for the program, but those are the rules.

I had asked a rhetorical question - sorry that you misunderstood my intent. I fully agree with what you say and had hoped that someone would come out and make a strong statement. This forum has been relatively silent with regard to the Q&A response to the question I had submitted over a week ago regarding software work outside of the FIX-IT WINDOWS. I thought the response from FIRST was very clear. It is our intention to do software development only during FIX-IT WINDOWS and at competitions.

I was taken by surprise with the response to the more recent Q&A regarding software for the practice robot. We have a practice robot, but we will only write and test code for it during FIX-IT WINDOWS. I think the response to that question can create more confusion amongst teams.