What Features Should the Default Code REALLY include?

[Astronouth7303]

I think CD is a great place for a repository, though it is a bit specialized.

Would the repository be just for .c and .h files, or could we include software? Examples: Lookup table generators, dashboards, etc.

[Tom Bottiglieri]

I am up for the repository idea. I have already started making libraries of my own source code for different drive techniques and other random tasks that I may want to use on the robot someday.

[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.

Originally Posted by 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.

(Wow! This thread has divulged off-topic... Anyway...)

The question is go with a new repository or build on the old one (http://nrg.chaosnet.org/repository/)?

And, if "build on the old one" is the plan, what are the top 5 [specific] features you would like to see added?

[Max Lobovsky]

Originally Posted by SilverStar

(Wow! This thread has divulged off-topic... Anyway...)

The question is go with a new repository or build on the old one (http://nrg.chaosnet.org/repository/)?

And, if "build on the old one" is the plan, what are the top 5 [specific] features you would like to see added?

Well it would be very nice if it was integrated with CD, maybe you could merge your code in. Other than that, i think the main feature it needs is some way to manage changes to the code. A bugzilla installation would be pretty cool, but it is kinda pointless when the biggest piece of code so far is like 15 lines. Actually, now that i mention it, a bugzilla installation for the default code is really needed. Im sure there have been at least 15 or 20 different changes and improvements posted about the default code.

Version editting at the nrg.chaosnet.org respository has been added.

[Max Lobovsky]

Originally Posted by SilverStar

Version editting at the nrg.chaosnet.org respository has been added.

Wow, that was quick. Were you working on it before, or did you just write that stuff?

[phrontist]

UPDATE:

I just took a long hard look at the NRG system. It's beautiful. I look foward to contributing code!

[Max Lobovsky]

[edit] this is in reply to phrontist mentioning CVS in the previous post. he apparently deleted that [/edit]

a CVS system would be great, though im sure something must already exist that would be appropriate for our needs. I looked at some CVS systems at the beginning of this season and realized that they are way way overkill for the few hundred lines we call software. If a CVS-lite doesn't exist, then we should sure make it!

I don't think we really need a CVS system for the code repository, but i was saying this just because it would be a very useful tool for most teams. For the code repository, the code base will probably small enough so it makes more sense to discuss individual changes on a forum or something like that.

Originally Posted by maxlobovsky

Wow, that was quick. Were you working on it before, or did you just write that stuff?

Just wrote it.

[Astronouth7303]

Originally Posted by SilverStar

(Wow! This thread has divulged off-topic... Anyway...)

The question is go with a new repository or build on the old one (http://nrg.chaosnet.org/repository/)?

And, if "build on the old one" is the plan, what are the top 5 [specific] features you would like to see added?

1. Integration into CD (Or access from). I'm thinking like a Whitepapers section in the programming forum.
2. More nesting of categories. I know that isn't an issue (yet), but if this thing takes off...
3. Whitepaper doc to go with code.
4. Multiple file grouping (.h and .c together, for example)
5. Improved interface (I'm too used to CD!)

[Joe Johnson]

I typed up a long message about coding standards for sharing code and then decided that starting a new thread was better.

See this thread: http://www.chiefdelphi.com/forums/sh...590#post259590


Please read through to the end because there is a call for volunteers at the end -- FIRST may need you...


Joe J.

[Max Lobovsky]

Originally Posted by Astronouth7303

1. Integration into CD (Or access from). I'm thinking like a Whitepapers section in the programming forum.
2. More nesting of categories. I know that isn't an issue (yet), but if this thing takes off...
3. Whitepaper doc to go with code.
4. Multiple file grouping (.h and .c together, for example)
5. Improved interface (I'm too used to CD!)

I'm sure Silver Star will have it done for you in a second

Originally Posted by Astronouth7303

1. Integration into CD (Or access from). I'm thinking like a Whitepapers section in the programming forum.
2. More nesting of categories. I know that isn't an issue (yet), but if this thing takes off...
3. Whitepaper doc to go with code.
4. Multiple file grouping (.h and .c together, for example)
5. Improved interface (I'm too used to CD!)

1. CD Integration - There is access from CD. Go to the front page of CD and click FIRST Code Repository.
2. More nesting - Infinite nesting is possible with the current system. Just click "Make a new folder" checkbox after clicking the "Add" link. Put in a Folder title, and select the parent folder. Don't put code or description. (This has been there for a while now).
3. I shall add this - for now, you can put 'whitepapers' in the description box.
4. This is already there! Just put both in the "Source code" box. I will add multiple boxes, but it seems unnecessary.
5. Can't do ...

Originally Posted by SilverStar

1. CD Integration - There is access from CD. Go to the front page of CD and click FIRST Code Repository.
2. More nesting - Infinite nesting is possible with the current system. Just click "Make a new folder" checkbox after clicking the "Add" link. Put in a Folder title, and select the parent folder. Don't put code or description. (This has been there for a while now).
3. I shall add this - for now, you can put 'whitepapers' in the description box.
4. This is already there! Just put both in the "Source code" box. I will add multiple boxes, but it seems unnecessary.
5. Can't do ...

Infinte nesting now enabled for all users (anyone who is logged in can now add folders, subfolders, subsubfolders, etc.)