Boost logo

Boost :

Subject: Re: [boost] [GitHub] Transferring a new library's repo to boostorg?
From: Beman Dawes (bdawes_at_[hidden])
Date: 2014-08-13 15:28:59

On Wed, Aug 13, 2014 at 10:38 AM, Daniel James <dnljms_at_[hidden]> wrote:

> On 13 August 2014 15:09, Beman Dawes <bdawes_at_[hidden]> wrote:
> > describes "Creating
> a
> > new library from an existing Git repository". It seems to cover the case
> > where the existing git repo isn't in the exact boost branch
> organizational
> > structure required.
> That was the procedure for libraries that were in subversion but had
> their own separate github modules, so it only applied to odeint and
> predef. It should probably be deleted now.

OK, done. Rewrite started to reflect use of github transfer mechanism.

> > The Boost Endian library is ready to be moved to boostorg on GitHub so it
> > can be tested on develop, checked by release managers, and otherwise
> > readied to be added to 1.57.0. It is already on GitHub and AFAIK has the
> > usual boost branch and directory structure.
> >
> > GitHub has a mechanism to transfer a repo between users or organizations.
> > This would seem the easiest and most direct approach for boost endian. Is
> > there any reason not to give it a try, and if it works as advertized then
> > add it to as an
> > additional option?
> We've already used the github transfer mechanism for a couple of
> modules. It requires that the person transferring in is in a team with
> admin rights.

Since I have admin rights, I went ahead and transferred the endian repo.
Very quick, easy, and nice. Cloned it locally, did a merge develop ->
master, pushed, check logs, etc. Slick.

If we don't want to give people admin rights, then it
> might be best to transfer to the repo to an admin user, and then let
> them transfer the module into the organisation.

That sounds workable. I'll write some strawman wording, then ask you to
review it.



Boost list run by bdawes at, gregod at, cpdaniel at, john at