[MINC-development] MINC and Subversion

[Jon Harlap]

not to mention that file based doesn't work so well when you have 
multiple developers working on a respository, as jason and i saw when 
setting up the brain-view subversion repository...  you have to set up 
silly hacks in order to allow all the developers to write to the 
repository directory and not create inaccessible files for the other 
developers...

on the plus side, you can use any form of apache auth module you like, 
and you can even combine several - so if you used PAM with ldap on the 
systems, you could use the same LDAP for subversion over http as well... 
  and for added security you can use ssl (https) - so if you wanted to 
allow collaborators who don't have bic accounts to access the subversion 
repos, you could actually create client certs for those users and accept 
equally the LDAP and SSL client cert credentials, so both internal and 
external users can access the repos.  isn't apache fun? ;)

j



Jason Lerch wrote:
> Sylvain MILOT wrote:
>> Sounds good to me Andrew. As for access, as you pointed out to me in our
>> previous exchange, I vote in favor of a file based svn, as opposed to an
>> http based - as I don't see the need to maintain a whole new set of
>> usernames and passwords.
>>   
> I'd argue for the opposite - there's an increasing number of MINC 
> users/developers outside of Montreal, and it seems silly to have to give 
> them local accounts for repository access when instead you could give 
> them an account just for subversion (plus get much finer level access 
> control in the process).
> 
> Jason
>> S
>>
>>
>> On Wed, 9 May 2007, Andrew Janke wrote:
>>
>>   
>>> Hi all,
>>>
>>> After a bit more goading I think I may have finally come to some sort
>>> of agreement (with myself) regarding svn for use with MINC and the
>>> various packages that we distribute.  I know that there are at least 2
>>> of you who still like CVS (and I do too! :) but feel the change is
>>> warranted.
>>>
>>> So what is the plan?   the plan is to finally use the placeholder on feeble:
>>>
>>>    feeble/cvs.bic.mni.mcgill.ca:/public-cvsroot
>>>
>>> Of course the above needs to be renamed slighty!
>>>
>>> Any recomendations on how we should structure the new repository?  I
>>> for one am all for a very simple flat structure something akin to
>>> this:
>>>
>>>    prod/
>>>       minc/
>>>       mni-autoreg/
>>>
>>>    dev/
>>>       minc_dev/
>>>       ...
>>>
>>> Where prod = production == all the packages that we distribute and dev
>>> == just that.
>>>
>>> thoughts?
>>>
>>>
>>> --
>>> Andrew Janke   (a.janke at gmail.com || http://a.janke.googlepages.com/)
>>> Canberra->Australia    +61 (402) 700 883
>>> _______________________________________________
>>> MINC-development mailing list
>>> MINC-development at bic.mni.mcgill.ca
>>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>>>
>>>     
>> ---
>> Sylvain Milot (sylvain at bic.mni.mcgill.ca)
>>               (bicadmin at bic.mni.mcgill.ca)
>> Brain Imaging Centre
>> Montreal Neurological Institute
>> 3801 University Street
>> Webster 2B, Room 208
>> Montreal, Qc., Canada, H3A 2B4
>> Phone  : (514) 398-4965, Fax: 398-8948
>> Mobile : (514) 712-1768
>> Office : 527 Av Des Pins O., Room 204
>>          Montreal, Qc., H2W 1S4
>> _______________________________________________
>> MINC-development mailing list
>> MINC-development at bic.mni.mcgill.ca
>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>>   
> 
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development