[cctbxbb] Moving cctbx to git

[Billy Poon]

Hi everyone,

The bootstrap.py script has been updated to pull sources from GitHub. As a
consequence, your svn copy of cctbx_project will not be automatically
updated by bootstrap.py.

To manually update your cctbx_project directory (since you should still be
committing changes with svn), please run

svn update

while in the cctbx_project directory.

--
Billy K. Poon
Research Scientist, Molecular Biophysics and Integrated Bioimaging
Lawrence Berkeley National Laboratory
1 Cyclotron Road, M/S 33R0345
Berkeley, CA 94720
Tel: (510) 486-5709
Fax: (510) 486-5909
Web: https://phenix-online.org

On Fri, Nov 4, 2016 at 10:24 AM, <markus.gerstel at diamond.ac.uk> wrote:

> Hello everyone,
>
>
>
> As Aaron requested – here is an update regarding the move to GitHub.
>
>
>
> At this time if you want to commit code: **keep committing to
> Sourceforge**.
>
> Do not worry about leaving uncommitted changes in your SVN tree. Those can
> be migrated later.
>
>
>
> The Sourceforge cctbx repository history has now been migrated to GitHub.
> The repository lives at https://github.com/cctbx/cctbx. Please do not
> commit to this repository yet!
>
> Over the next few days the bootstrap script will be modified alongside the
> build servers to point to the GitHub repository. This means there will only
> be limited testing, and the produced builds will lag behind the development
> effort.
>
>
>
> To be listed as a developer on https://github.com/cctbx you need to set
> your visibility to public at https://github.com/orgs/cctbx/people.
>
> You can also view some fancy graphs about the cctbx project history at
> https://github.com/cctbx/cctbx/graphs/contributors
>
>
>
> If you haven’t done it before, now is a good time to set up your local
> installation of git to use your name and mail address with
>
> git config --global user.name "John Doe"
>
> git config --global user.email your_email at example.com
>
> as well as this setting to avoid merge commits:
>
> git config --global pull.rebase true
>
> Note that you must set these on every computer you use! You may want to
> keep a copy of those commands around in case you ever get a new computer.
>
> You should use mail addresses registered with your github account, or – if
> you enable it in your github account – the anonymous address offered by
> github.
>
>
>
> You may want to use the time to sort out your ssh access keys with your
> GitHub account, and play around with git a bit. You can test that
> everything works using the temporary sandbox repository of cctbx. Here are
> some commands to get you started:
>
> git clone git at github.com:cctbx/cctbx-playground.git
>
> cd cctbx-playground
>
> echo some text >> some-file
>
> git add some-file
>
> git commit –m "some commit"
>
> git push
>
> git log
>
> Then go to https://github.com/cctbx/cctbx-playground/commits/master to
> see how other people will see your commits.
>
>
>
>
>
> The next steps:
>
>
>
> **Tuesday 8th November 2016, 11:59pm Pacific Time**
>
> **= Wednesday 9th November 2016, 07:59am GMT:**
>
> Sourceforge: Committing allowed. GitHub: Checkout/Cloning allowed,
> **Read-only**.
>
> We will update our build servers and the bootstrap script to refer to the
> git repositories.
>
> All commits still run into Sourceforge, and will be copied over to GitHub
> automatically
>
> every couple of hours. Since the build servers will only see code on
> GitHub,
>
> testing and deployment will be limited during this period.
>
>
>
> **Tuesday 22nd November 2016, 11:59pm Pacific Time**
>
> **= Wednesday 23rd November 2016, 07:59am GMT:**
>
> Sourceforge: **Read-only**. GitHub: Committing allowed
>
> We should have achieved a stable build on both Jenkins and Buildbot by
> this time.
>
> Change any website pointers from SF to GitHub.
>
> Instructions to migrate local developer repositories will be sent around.
>
> All future commits should go to GitHub only.
>
> Remaining commits on Sourceforge will be migrated to GitHub.
>
>
>
> -Markus
>
>
>
>
>
> Dr Markus Gerstel MBCS
>
> Postdoctoral Research Associate
>
> Tel: +44 1235 778698
>
>
>
> Diamond Light Source Ltd.
>
> Diamond House
>
> Harwell Science & Innovation Campus
>
> Didcot
>
> Oxfordshire
>
> OX11 0DE
>
>
>
>
>
> --
>
> 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
>
>
> _______________________________________________
> cctbxbb mailing list
> cctbxbb at phenix-online.org
> http://phenix-online.org/mailman/listinfo/cctbxbb
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://phenix-online.org/pipermail/cctbxbb/attachments/20161108/9ddf2c71/attachment.htm>