Quote:
Originally posted by Joe Johnson
P.S. Wouldn't it be nice if they published a "beta" copy before they put out the "Final" release. This would allow us all preview it for consistency and clarity as well as for fidelity to the prior updates and jive.ilearning messages. I think this would be a lot less work for FIRST in the long run.
|
On that note, has anyone mentioned on these forums, in a thread I may have overlooked the idea of bringing up this problem at the next team forum? 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. Of course, it would be totally FIRST's decision if a change to the beta copy of the team update would be made, but on paper it sounds as though it would work out nicely. BTW: we aren't all English majors here
.