Yes. Your best bet is to keep the dev version on a private server or
the like (even use a different hosting service if you have to) and
then svnsync or submit patches to google code when you feel like it.
In any case, the source that you put on Google Code will have to
remain under an open source license, so be prepared to lose a bit of
control over the usage and viewing of your code. Robby O'Connor also
brings up a good point -- one of the interesting notions of open
source is transparency. Your development decisions should be visible
to the public, no matter how brilliant (or otherwise) they may be.
There's no harm in it, really.
Also, out of curiousity, why do you want to keep the dev version private?
On 5/12/08, Chris Nystrom <cnyst...@gmail.com> wrote:
> On Sat, May 10, 2008 at 6:58 PM, LuaPineapple <evilpineap...@cox.net> wrote:
> > How would I do this? Although our project is open source we want to
> > keep the dev version in our own little group.
> Host it on your own site and then use a firewall to control access.
> Chris
> --
> E-Mail: Chris Nystrom <cnyst...@gmail.com>
> Saving the world from web programming.
> http://www.newio.org - AIM: nystromchris
