[Q-e-developers] Anonymous SVN access [again]

Filippo SPIGA filippo.spiga at quantum-espresso.org
Wed Apr 13 20:28:58 CEST 2016


Ciao Stefano,

I've just dig into my mailbox (that looks like a black hole) and indeed Nicola wrote to Paolo on February 1st asking about SVN access. At that time I do not recall the GIT repository for read-only access was already in place, I suspect we created it around the same period to overcome a problem related to SVN Access Control List on QE-FORGE (problem that btw still exist).

We probably never announced formally about the private read-only QE mirror GIT repository (a good time will be with the new release next week, plus including something in the documentation as well) but we always accommodated who had the need to access to it. Nicola never got in contact again with us about his specific issue, not a single email to support at qe-forge.org for what I know. That's why he got no access until now. But now I fixed it, he will receive an email from me with the details.

Regards

--
Mr. Filippo SPIGA, M.Sc.
Quantum ESPRESSO Foundation
http://www.quantum-espresso.org ~ skype: filippo.spiga

*****
Disclaimer: "Please note this message and any attachments are CONFIDENTIAL and may be privileged or otherwise protected from disclosure. The contents are not to be disclosed to anyone other than the addressee. Unauthorized recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission."

> On Apr 13, 2016, at 7:07 PM, Stefano de gironcoli <degironc at sissa.it> wrote:
> 
> ciao Filippo,
> 
> quite simple indeed ... except that when Nicola Colonna (already 
> registered under qe-forge and developer with me of the ACFDT code, 
> strongly tight to QE but independent) asked for such an access his 
> request was dismissed, the reason being not to inflate the number of 
> developers...
> So if you are going to give a go to everybody has a good reason to need 
> access to the QE repository, please give access to Nicola as well.
> 
> ciao,
> 
>   stefano
> 
> 
> On 13/04/2016 19:42, Filippo SPIGA wrote:
>> On Apr 13, 2016, at 4:10 PM, Lorenzo Paulatto <lorenzo.paulatto at impmc.upmc.fr> wrote:
>>> Nevertheless, I used to recommend to students and collaborators to always work
>>> on top of SVN, knowing that the pain of integrating a code written on top of
>>> an old static version of QE would be worst than any transient instability of
>>> the SVN version. Also, as it is usually falling on my shoulders, it may be
>>> delayed until it is unpractical. I stress, also people working on clearly
>>> separate projects, often hosted on the qe-forge, are affected as they cannot
>>> keep the interface between their code and QE up to date.
>>> 
>>> I know that a GIT repository is supposed to exist somewhere (I could do one
>>> myself, to be fair), I guess that having access to it can solve the points 1
>>> and 2; but it is not as readily available as SVN used to be. I would really
>>> like to have an official, simple way to allow people to access  (read-only) the
>>> development files and their history.
>> 
>> Who are those people? Do you have names to tell us?
>> 
>> The simple way/procedure is the following: if we receive an inquiry via "support at qe-forge.org" then we ask the person to REGISTER to qe-forge (if not done already) and then I authorize everybody needs for a good reason (not just curiosity). Process this requires less than a day (I do not live in front of a computer, so it is not a immediate procedure). Then those new users can access the q-e-private and keep aligned their own private code when they want and how they want.
>> 
>> I believe is very simple.
>> 
>> --
>> Mr. Filippo SPIGA, M.Sc.
>> Quantum ESPRESSO Foundation
>> http://www.quantum-espresso.org ~ skype: filippo.spiga
>> 
>> *****
>> Disclaimer: "Please note this message and any attachments are CONFIDENTIAL and may be privileged or otherwise protected from disclosure. The contents are not to be disclosed to anyone other than the addressee. Unauthorized recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission."
>> 
>> 
>> _______________________________________________
>> Q-e-developers mailing list
>> Q-e-developers at qe-forge.org
>> http://qe-forge.org/mailman/listinfo/q-e-developers
> 
> _______________________________________________
> Q-e-developers mailing list
> Q-e-developers at qe-forge.org
> http://qe-forge.org/mailman/listinfo/q-e-developers





More information about the developers mailing list