Best Hosted SVN?

[cbale2000]

Originally Posted by EHaskins

Google code projects must be public and under an open source license, so it isn't applicable for them.

If you really need a private solution you will probably want to self-host it.

Granted, however the likelihood of anyone actually finding the SVN who doesn't already have the address is slim to none, especially if you intentionally label it something random. While granted it isn't secure, if all he's using it for is like FRC code or whatever other personal projects, no one will ever bother messing with it.

I've used Google code for personal (though, granted, not privacy sensitive) files for a while now with no problems. You get 100mb of free storage, which pretty much covers any sort of coding most can do.

There are other options out there (some site offer password access, and of course there is private hosting) but I prefer the simplicity of Google code, especially if you already have a Google account, its one less thing to sign up for.

My 2 cents.

[EHaskins]

Originally Posted by cbale2000

Granted, however the likelihood of anyone actually finding the SVN who doesn't already have the address is slim to none, especially if you intentionally label it something random. While granted it isn't secure, if all he's using it for is like FRC code or whatever other personal projects, no one will ever bother messing with it.

...

There are other options out there (some site offer password access, and of course there is private hosting) but I prefer the simplicity of Google code, especially if you already have a Google account, its one less thing to sign up for.

My 2 cents.

I completely agree, but one of their requirements was private hosting so I felt it should be pointed out.

I would suggest they reconsider needing a private repository, but that is their decision.

[EricVanWyk]

Originally Posted by EHaskins

I would suggest they reconsider needing a private repository, but that is their decision.

Personally, I wish that all teams would make their code available to the public. I don't believe that the perceived advantage of locking away your secret sauce outweighs the real benefit to other teams trying to learn.

Put another way, would the entire community be better off if everyone closed their source or opened it? If your answer to the global case does not match your answer to your personal case, you may want to stop and think a bit.

*gets off soapbox*

[cbale2000]

That is actually a very good point now that you mention it (and though this is getting a bit off topic), maybe it would be a good idea for someone to setup like an open source FIRST code repository (not necessarily an SVN) that teams could post pieces of code, then explain what they do and how they do it.

Not only would it benefit new teams that might not have experienced coders, but it would also be of help to veteran teams looking for alternative solutions to coding problems. Like a coding Dev community but for FIRST (Granted there are subforums for such things, but nothing that currently quite encompasses this idea).

Oh the possibilities.

[NickE]

Originally Posted by cbale2000

That is actually a very good point now that you mention it (and though this is getting a bit off topic), maybe it would be a good idea for someone to setup like an open source FIRST code repository (not necessarily an SVN) that teams could post pieces of code, then explain what they do and how they do it.

Not only would it benefit new teams that might not have experienced coders, but it would also be of help to veteran teams looking for alternative solutions to coding problems. Like a coding Dev community but for FIRST (Granted there are subforums for such things, but nothing that currently quite encompasses this idea).

Oh the possibilities.

http://www.chiefdelphi.com/forums/sh...threadid=70865

[cbale2000]

Wow, that was fast! Nice job!