I agree, it is a social issue in most cases. But in this case, we don't want to have code(which can be considered as scientific results. Its is mainly numerical solutions to 3D ultrasound wave propagation) to be public before we have published the results. The software is going to be one of the main results the main developers PhD, so he does not want experimental code to be public, but finished code is something he wants to be public so other people can use it, make changes and comment on the solutions used. The current code is the result of two PhD degrees and is a very powerful tool that we would like to share with anyone interested.
But this may be such a special case that we should come up with our own solution instead. Its just so nice to have the code here, and we have a Google Group for the user community as well. Thor Andreas On Nov 19, 4:38 pm, Ben Collins-Sussman <[EMAIL PROTECTED]> wrote: > Isn't this a simple social issue? > > In traditional software development, one simply makes 'releases': the > verified code is tagged, and a release tarball is put up in the > "downloads" area. Ordinary users are instructed to checkout either a > 'stable tag' of the code or to grab the latest release tarball. > Developers are instructed to use the latest 'trunk' code, which has > giant warnings all over it that it's unstable/untested/unverified. If > an ordinary user ignores all the warnings and checks out the trunk > code anyway, well, then, she gets what she deserves. :-) > > On Wed, Nov 19, 2008 at 7:35 AM, thorsan <[EMAIL PROTECTED]> wrote: > > > Thanks for your response. > > > The reason for hiding some code is that we want to have it for > > internal testing before it is released. Some of the code is background > > for work which is to be scientifically published, so until its > > published and the code verified we want to have it open only to the > > developers. The software we are developing is a simulation tool for > > ultrasound wave propagation. We only want people to have access to > > verified code. > > > Thor Andreas > > > On Nov 19, 11:33 am, "Thomas Johnson" <[EMAIL PROTECTED]> wrote: > >> It can't be done with the Google Code toolset -- hiding the > >> development process generally goes against the spirit of Open Source. > >> In any case, it's probably more complex and time-consuming to keep the > >> development private. > > >> That being said, you might have some luck keeping a private > >> repository, and using some of the existing SVN tools to support your > >> needs. I would imagine that you could use svnadmin dump and dumpfilter > >> tools to prune out the unwanted dev branches, and then svnsync to the > >> public site. > > >> As an alternative, you could use Git's subversion tracking > >> functionality to only follow one branch. You could probably manage to > >> update from the dev svn repository, then do some kind of git-svn > >> switch, followed by a rebase and dcommit to the public repository. > > >> As another alternative, just wait patiently for the much anticipated > >> Distributed Version Control System support and then do a mix of > >> private development with pushes of the master/public branch to the > >> public repository. > > >> In any case, these approaches are all harder than just keeping the > >> whole thing public. If you're just worried about people using broken > >> code, you can just make sure that developers know that they need to > >> keep "trunk" stable and compiling, with extra branches for dev, > >> unstable, stable, and release. > > >> Out of curiousity, what are your reasons for favouring partially > >> closed development? > > >> On Wed, Nov 19, 2008 at 10:53 AM, thorsan <[EMAIL PROTECTED]> wrote: > > >> > Thanks for a swift response. > > >> > OK, Ill do that. > > >> > A second question: > > >> > I would like to restrict access to the repository so that read only > >> > users only have access to a certain branch. We have several branches > >> > but we only want open access to the release branch. Can this be done? > > >> > Thanks, > >> > Thor Andreas > > >> > On Nov 18, 7:33 pm, "Daniel O'Brien" <[EMAIL PROTECTED]> wrote: > >> >> Not currently, though you could file this as a feature request against > >> >> our support project:http://code.google.com/p/support/issues/list > > >> >> Daniel > > >> >> On Nov 18, 8:03 am, thorsan <[EMAIL PROTECTED]> wrote: > > >> >> > Hi > > >> >> > Is it possible to track the number of checkouts from the read only > >> >> > repository? > > >> >> > Thanks, > >> >> > Thor Andreas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
