Hello Mark, > >>> I think it would make sense to at least provide read access to the real > >>> group workspace (if you're paranoid then maybe only to group members, > >>> but then comes the question, how can anybody become a group member?). > >> > >> I'll see if we could arrange that. I believe that it is our > >> intention anyway - once we move to Mercurial each "group" will have > >> their read/write mercurial workspace and members of the group > >> will have read and in some cases write access. > >> > >> But at this point even a read-only svn workspace would help. > > svn, or Mercurial?
Both is perfectly fine for me. Personally I'd prefer hg. > Would updates from the Sun-internal group workspaces once or twice a day > be sufficient? (More than that could be tricky.) Sure. That is much better than once in 2-3 weeks or so ;-) > We're looking into setting something up short-term in order to ease this > particular pain point. Due to hardware limitations it likely won't be > available to the general public, but we want to do whatever we can to > facilitate collaborative development even prior to the full Mercurial > changeover. Great! Thanks for going through this. /Roman -- Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org aicas Allerton Interworks Computer Automated Systems GmbH Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-0 USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe Geschäftsführer: Dr. James J. Hunt
