Subject: Re: [boost] [git] Why are we using Github (was: The any library does not pull cleanly because of a forced update on develop and master)
From: Daniel Pfeifer (daniel_at_[hidden])
Date: 2013-12-12 11:28:55
2013/12/12 Beman Dawes <bdawes_at_[hidden]>:
> On Thu, Dec 12, 2013 at 6:12 AM, Mathias Gaunard <
> mathias.gaunard_at_[hidden]> wrote:
>> On 11/12/13 23:19, Cox, Michael wrote:
>>> If we are still in the acceptance phase of the git conversion
>>> (based on some of the comments in the thread this was taken from), maybe
>>> should reconsider Github? What were the advantages of Github vs. other
>>> public repositories like Bitbucket?
>> I believe the reason Github was chosen is that it is perceived that Github
>> has better social features for code review, pull requests etc.
> IIRC, the conversion team started out using other hosts (Gitorious?
> Bitbucker?) but switched to Github because of problems they encountered
> with the other sites.
The problem with Gitorious was the performance and Bitbucket did not
exist when this decision was made. The reasons why GitHub was picked
may be outdated.
Our Boost-Jenkins has pushed the modularized repositories to both
GitHub and Bitbucket.
>> Before considering moving to Bitbucket, I recommend simply asking the
>> Github team whether it's possible to add restrictions on a case by case
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk