Subversion software versioning system.

[A Marchini]

I had been thinking, that with the addition of a software slant to the server here, that perhaps we could set up a version control server for things devised here .
This would include :
micro controller code
plug in code
miscellaneous control software for public use

Anyways, a central repository, with version storage capabilities would actually save space on the server, since from one revision of code to another, we only save the changes, not the entire source tree over and over.
It also gives a way to visibly display differences between one version to the next, and to log the changes made in a central database.

One more thing, having all the software in one place makes it easier to find (especially if you are interested in a prior version).

This is just a thought, a repository is relatively easy to create from what I understand.

Subversion is a good mix of software control.
Tony

[DynamoBen]

How about opening a sourceforge.net page?

[A Marchini]

How about opening a sourceforge.net page?


My only problem with that is that it takes away from the "one stop shopping" (so to speak) that is doityourselfchristmas.com. You would have to leave this site to get access to it.

Also I am not sure of the flexibility of the source control system there.

If done in one SVN repository (im not saying that SVN is unique in this), then all projects could exist in a structure not unlike a bunch of disk drive folders.

Tony M.

[Macrosill]

Tony,
I am not really sure what it is you are asking for. I do not know what "software slant to the server" is. Can you explain it further?

[Mudsculpter]

I don't know fully what he's talking about but a Download page that contains Vixen, Renard download links (that are locked from member posts) on the Index page would be nice.

[A Marchini]

Tony,
I am not really sure what it is you are asking for. I do not know what "software slant to the server" is. Can you explain it further?

I guess I didn't put it very clearly. There could be a rise in conversations and projects revolving around software. The server where we have everything now could serve another role (as if it didn't do enough alread). This new role would be a central repository for all software projects. This repository would be structured and used only for the sharing , mantenece and upkeep of software (light control related of course).

Subversion runs as a server (like Apache) and allows for software to be checked out, modified and then checked back in. This has the benefit of allowing changes to be managed and it allows multiple people to work on the same software and not crush each others changes. There is also logging and such. Not to mention, the design of the versioning system stores source code changes, not a complete copy, so if there were a lot of versions lying around, they would generally take less space, then just having a complete copy of each change stored on the server. Also each change can be copied from a prior revision, even deletions, so someone could potentially delete the entire repository, but one would only need to copy forward a prior revision before the delete, to restore it all.

I only bring it up that if the future brings more diversity to the software base (currently consisting of Vixen plugins, and microcontroller code) were Linux and Mac players may want to play as well, then it could be helpful.

I guess this is just too esoteric for the community at large.

Just posting stuff to the Wiki should be sufficient for now.

Tony M.

[DynamoBen]

Tony I like the idea, assuming its not too much work to implement. People can choose to use it, or not. While the wiki is nice its not really well suited for cooperative projects, and version control.