[Q-e-developers] Anonymous SVN access [again]
Filippo SPIGA
filippo.spiga at quantum-espresso.org
Wed Apr 13 19:42:47 CEST 2016
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."
More information about the developers
mailing list