Here's my 2 cents. (Wrote this up yesterday)
My thoughts on what the standard should be:
- Allow C++ style comments
- 1 of the properties of each upload should be "Target System". Right now there only is 5: 'PBASIC Stamp (EDU)', 'PBASIC Stamp (Full)', 'PIC18Fxx (EDU)', 'PIC18Fxx (Full)', and 'None'. 2 of the same processor can be selected (not EDU/Full specific)
- Hardware info should be noted and ALIASed. (is that a word?) This allows for rapid integration.
- Actual formating should be uniform with the default code (except for the C++ comment thing)
- any TABS included will be changed to 4 spaces on upload (or just rejected outright)
- only debuged code should be uploaded.
- upload as file(s), NOT textbox.
- allow multiple files in upload
- a set of standard libs, functions, etc. are provided ('#include <Repositroy.h>') (Or assumed to be provided)
- items-in-progress should be marked as such
- currently, only .h, .c, .bsx, and .zip files are allowed for actual code (Probably will expand)
Zips can contain full projects, but files MAY be filtered out as deemed necessary by the moderator(s) - tools, etc. are kept seperate from code. all tools must be open source. (A 'tool' is anything related to code but is not actually code itself)
- all code has same EULA: 1) Code is given AS IS. 2) give credit where credit is due. 3) may NOT use code to make money.
- White space should be included where the C spec allows.
- PLENTY OF COMMENTS
- a whitepaper/explainitory file can be included (seperate from code, but accesed together)
- I know there's more...
I'm focusing more on the repository than the code itself.
Some stuff from the first thread:
- Integration into CD. [...]
- More nesting of categories. I know that isn't an issue (yet), but if this thing takes off...
[...] - Improved interface (I'm too used to CD!)
I am willing to help hammer this thing out/code it/whatever. Be warned: I'm 15 (almost 16) and don't have any
professional coding expierience. I encourage the guys who end up making this (Why just the profesionals?) to get a forum, but I think keep it public. Those who aren't actually writting should try to restrain from posting there, but I think they should be able to.
What's the noun for "a piece of code that is uploaded to a code repository"?