Quote:
Originally posted by Joel J.
Perhaps the best way to avoid these ambiguous, and inconsistent updates is to put together a team of veteran FIRSTers, each with an expertise in a specific area of an update, to serve as "editors" of sorts to a pre-release of a team update. FIRST could also release a "'beta' copy," as Joe J said, of the Update, and allow 1-2 days for arguments against/for changes outlined in the update.
|
I think this is an excellent idea, Joel. You may have read some of my ranting about the issue of rules that are unclear, ambiguous, and changed at the last minute (remember the change in the # of pneumatic cylinders allowed halfway into the buildtime last year?) As I have said before, this is not a trivial matter. The failure to provide clear, reasonable rules and not change them, in my opinion, a threat to the future of FIRST. It is extremely aggravating for a coach who puts his/her life on hold and puts in hundreds of hours to have to deal with this sort of thing. The issue here is clear, responsible communication, which I believe is at the core of "Gracious Professionalism." I think that the idea of "beta testing" the rules with FIRST veterans is similar to submitting a manuscript to the review board of a journal.