Dear All,

 

Thank you to all who have responded so far – some interim results

 

So, reasonably widespread support for the move amongst the wider community… Additionally comments follow:

 

Git is a recipe for chaos.

6/15/2016 5:58 PM View respondent's answers

It should be noted that some people's opinion hold more water that others. Another point is that this is unlikely to happen before the next major release of Phenix in July/August-ish.

6/15/2016 5:21 PM View respondent's answers

We should try to make this move ASAP. Developing under GIT is much much more easy than SVN!

6/15/2016 1:35 PM View respondent's answers

for old fashioned svn fans: remember that github servers can work with svn without affecting the workflow of git users

6/15/2016 10:25 AM View respondent's answers

Git has significantly more functionality than svn that I would take advantage of right away.

6/14/2016 5:10 PM View respondent's answers

The distributed nature of Git makes it easier for me to make local commits and push them to the official (master) repo only after I am confident.

6/14/2016 2:10 PM View respondent's answers

Integrate dependencies Scons, Boost and ccp4io as submodules and ccp4io_adaptbx as a subtree

6/14/2016 1:20 PM View respondent's answers

I support this

6/14/2016 1:17 PM View respondent's answers

 

These are deliberately taken verbatim.

 

Some commentary / editorial:

 

The strength of support should ideally be modulated by the number of commits to the repository – and the extent to which the groups in question depend on stability in cctbx. The point above reflects this that some opinions hold more water than others. The comment about the next phenix release is slightly frustrating if understandable, since the last time we discussed it the stopper was … the next phenix release. I’m not going to argue with this though, since I feel if we make this move we need to have complete support from everyone it will affect, democratic majority is not enough.

 

We (DIALS-East) have found some huge benefits with using git – the major one I find is the ability to cherry pick change sets for identified point release versions (being able to add fixes for bug # n, m to 1.2.4 to make 1.2.5 for example; this falls down with the associated cctbx changes though)

 

Possibly the only practical way to make this change is to have a (virtual) workshop where the interested parties make the necessary changes to e.g. build systems after the Phenix release?

 

The survey remains open for more contributions, I just said I would report back after getting 10-20 and have 15 responses J

 

Cheerio Graeme

 

 

 

 

… is there any enthusiasm out there for moving cctbx to git? The more I work with git the more I wish this existed properly for cctbx.

 

I’ve raised this a bunch of times and always it is “not right now” however “a good idea” – this’ll be the last time I ask…

 

Could we move to git, please? I note the bootstrap script for Windows now has a git dependency even!

 

Am happy to help if I can with anything though I think it should be pretty simple… was for DIALS & xia2 J

 

Thanks Graeme

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom