Message: Re: anonymous svn access Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: anonymous svn access 

Forum: Installation and Configuration
Re: None anonymous svn access (Yngve Inntjore Levinsen)
Re: None RE: anonymous svn access (Makoto Asai)
Date: 20 Jun, 2011
From: Yngve Inntjore Levinsen <Yngve Inntjore Levinsen>

--Boundary-01=_hw2/N42TN3kH2G2
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Dear Makoto and developers,

Don't worry, I was just curious if I overlooked some information, and I respect your decision which I have no problem with. Of course for most people it is the releases which are of importance in any case. Considering argument 1, I think most people understand that changes in a repository that are not on a stable branch should be considered premature for general adoption. Your 2. argument is a very good one which I did not realize.

Considering your developing model where you have as I understand it many parts which cannot yet go into a public repository etc, it sounds to me like you would benefit a lot by using a distributed version control system like e.g. git or mercurial. That way you could make public a repository which only contained branches that were released, and it would be easier for outside users to submit patches and follow what is going on.. Finally my impression having used svn for 1.5 years and now git for ~2 years, is that git is far superior when it comes to merging etc (something I assume you have to do a lot with your developing model). Just my 5 cents.

Best Regards,
Yngve

 Mandag 06 juni 2011 20.04.13 skrev Asai, Makoto :
> Dear Yngve,
> 
> I'm afraid we do not offer public read access to our 
> SVN repository. There are several reasons which led 
> us to this, and here is a couple of them.
> 
> 1) We use SVN as the repository of our developing code 
> partly as a mean for exchanging/sharing the code among 
> developers and synchronizing its development. Such code 
> is often too premature and in some cases incomplete and
> unsuitable for public view. 
> 
> 2) Some of the code in our repository, in particular 
> in physics modules, are developed by PhD students and 
> Post-docs in our collaborating institutes/universities. 
> We cannot publicize their work until corresponding papers 
> are submitted. I hope you understand that preserving the
> academic work done by contributors to Geant4 is a real 
> concern we cannot ignore.
> 
> For all publicly released code, including patch releases,
> we offer LXR code browser, which offers even better 
> services compared to SVN browser.
> 
> Kind regards,
> Makoto Asai
> 
> 
> 

--Boundary-01=_hw2/N42TN3kH2G2
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta name="qrichtext" content="1" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Monospace'; font-size:9pt; font-weight:400; font-style:normal;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Dear Makoto and developers,</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Don't worry, I was just curious if I overlooked some information, and I respect your decision which I have no problem with. Of course for most people it is the releases which are of importance in any case. Considering argument 1, I think most people understand that changes in a repository that are not on a stable branch should be considered premature for general adoption. Your 2. argument is a very good one which I did not realize.</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Considering your developing model where you have as I understand it many parts which cannot yet go into a public repository etc, it sounds to me like you would benefit a lot by using a distributed version control system like e.g. git or mercurial. That way you could make public a repository which only contained branches that were released, and it would be easier for outside users to submit patches and follow what is going on.. Finally my impression having used svn for 1.5 years and now git for ~2 years, is that git is far superior when it comes to merging etc (something I assume you have to do a lot with your developing model). Just my 5 cents.</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Best Regards,</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Yngve</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"> Mandag 06 juni 2011 20.04.13 skrev Asai, Makoto :</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Dear Yngve,</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; I'm afraid we do not offer public read access to our </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; SVN repository. There are several reasons which led </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; us to this, and here is a couple of them.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; 1) We use SVN as the repository of our developing code </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; partly as a mean for exchanging/sharing the code among </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; developers and synchronizing its development. Such code </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; is often too premature and in some cases incomplete and</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; unsuitable for public view. </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; 2) Some of the code in our repository, in particular </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; in physics modules, are developed by PhD students and </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Post-docs in our collaborating institutes/universities. </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; We cannot publicize their work until corresponding papers </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; are submitted. I hope you understand that preserving the</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; academic work done by contributors to Geant4 is a real </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; concern we cannot ignore.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; For all publicly released code, including patch releases,</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; we offer LXR code browser, which offers even better </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; services compared to SVN browser.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Kind regards,</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Makoto Asai</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p></body></html>
--Boundary-01=_hw2/N42TN3kH2G2--

 Add Message Add Message
to: "Re: anonymous svn access"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews


[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]