Hi all, I think most are aware of this, but the Duke team is fully supportive and think we should make the move in a smart way but sooner rather than later. Personally, I find the developing under GIT to be more intuitive and thus easier to handle than SVN. If I am reading this thread correctly, it looks like we may have a volunteer to transition cctbx to git... Bradley On Wed, Jun 15, 2016 at 6:47 AM, wrote:

Hi Rob,

I think this is an important point you make. Given that there are now a number of projects making heavy use of the cctbx (both using and contributing) with competing development and release schedules, the current paradigm of everyone developing on trunk is liable to cause problems. Moving to git should make things easier in this regard, although we would still have to agree on suitable working practices within the new system.

Cheers,

Richard

Dr Richard Gildea Data Analysis Scientist Tel: +441235 77 8078

Diamond Light Source Ltd. Diamond House Harwell Science & Innovation Campus Didcot Oxfordshire OX11 0DE

________________________________________ From: [email protected] [[email protected]] on behalf of R.D. Oeffner [[email protected]] Sent: 15 June 2016 11:27 To: [email protected]; phenixdev Subject: [cctbxbb] Not wishing to raise this again but...

Personally I think moving the cctbx to git is a great idea as it would make it easier and safer when developing and testing new features. Given so many teams are using the cctbx this seems like a compelling reason for it to be moved.

We had a chat a while ago with Berkeley about this but I've forgotten what the consensus was.

Rob

...

Message: 1 Date: Tue, 14 Jun 2016 12:10:03 +0000 From: To: Subject: Re: [cctbxbb] Not wishing to raise this again but... Message-ID: <13999B6FC038EB44B067771E3CFBD091BC327D8E@exchmbx03> Content-Type: text/plain; charset="us-ascii"

Hi All,

This sounds like it is heading in a pragmatic direction - I would find it very helpful to gauge feeling for or against this. To make this simple I have attempted (starting from a completely ignorant position) to put together one of those online survey things:

https://urldefense.proofpoint.com/v2/url?u=https-3A__www.surveymonkey.co.uk_r_GXPY5JW&d=CwIFAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=ccS9o0fGEme0ntdO5ou7Yj-7_hYZiIFtS6BwbAzEXq0&m=O88OuzV6oJPUZ9yv4jTscGoctGvF-amJ1fY0RYT-jV4&s=kknIGnajopP5v7b1l_rFmA3Kn4y9CRJl5PBOaHNTPC0&e=

...

If you could pick an option that would be great, explaining why would be even better, or hitting reply-all to this thread would also work (as has previously done so) I'll collate answers over the next few days & feed back when we have (say) 10-20 or a few days have passed

...

From experience with moving xia2 & DIALS it was surprisingly straightforward (an opinion)

Thanks & cheerio Graeme

-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: 14 June 2016 12:18 To: [email protected] Subject: Re: [cctbxbb] Not wishing to raise this again but...

Hi Pavel,

I volunteered to do this some time ago, just like for DIALS, and would still be happy to do this. We can do the move slowly, so allow users (developers) with a git repository while development still happens in SVN for say a couple of weeks, and I would be happy to run the git support for that time and for the aftermath of the move.

Best wishes -Markus

-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Pavel Afonine Sent: 14 June 2016 12:11 To: cctbx mailing list Subject: Re: [cctbxbb] Not wishing to raise this again but...

Hey there!

Well I guess I say something even though I don't have much to say really. I've been contributing to CCTBX for the past 13 years, so I feel like this conversation is not too irrelevant to me to say the least.

I don't have strong opinion about staying with svn vs moving to git. I routinely contribute to CCTBX (which is SVN-based) and I routinely contribute to my other activity - Q|R (Quantum Refinement, which is hosted by GitHub). I'm comfortable with both environments as I'm using only the minimal functionality of both: check in, check out, diff.. period. I'm not interested in branching/etc sophistication; this is just because the way I structure my workflow..

My current understanding is that moving CCTBX to use git boils down to: - actually someone doing it; AND - taking good proper responsible care of the aftermath (if any).

So far no-one volunteered to embrace this challenge, as far as I know.

In summary I think we should move to git, at least to follow the vector of progress.

All the best, Pavel

_______________________________________________ cctbxbb mailing list [email protected]

https://urldefense.proofpoint.com/v2/url?u=http-3A__phenix-2Donline.org_mailman_listinfo_cctbxbb&d=CwIFAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=ccS9o0fGEme0ntdO5ou7Yj-7_hYZiIFtS6BwbAzEXq0&m=O88OuzV6oJPUZ9yv4jTscGoctGvF-amJ1fY0RYT-jV4&s=Ph52yw5GPDYL2mH55ZhW4b88vb_vos0_okA1yBPOtw8&e=

-- 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