[Mark McLeod]

Lots of useful stuff can be included in a repository.

On a side note, one of the management questions that needs to be addressed is how and how much to control submissions? Also, there will need to be a version process in place to handle error corrections and expanded/changing capabilities.
I'm thinking mostly along the lines of quality control answering such questions as “has the code been tested and debugged?” Oftentimes when we're debating coding issues on the Programming Forum we'll post code suggestions off the tops of our heads, but there will be typos or logic errors that didn't necessarily seem important in the original context. Later you'll see the code with errors popup again in postings as someone attempts to use it "as is," not understanding that there are or may be bugs. We may want to consider some kind of peer review or monitoring.

Other issues are standards, e.g., coding, interface compatibility, documentation, etc. It's easy for you experienced programmers out there to handle the myriad styles one encounters by getting submissions from across all of FIRST, but the majority of Team programmers tend to be new to programming and are sometimes thrust into the job. The repository has to be made both easy for newbies (at least with the simpler/common functions), as well as easy for the rest of us to help newbies chose and integrate functions appropriate to their level of understanding.

Most of the programming mentors are out there driving home lessons in coding standards, testing procedures, configuration management, etc. These are second nature to us and need to be communicated through any repository. I don’t mean to say everyone will accept, implement, or follow the same standards, but there should be some basic standards in place to set a good example for new programmers to follow.