Re: [boost] [git] What about unmaintained libraries?

Subject: Re: [boost] [git] What about unmaintained libraries?
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2012-12-26 03:10:56

On Wed, Dec 26, 2012 at 12:59 AM, Dave Abrahams <dave_at_[hidden]> wrote:
>
> on Mon Dec 24 2012, Andrey Semashev <andrey.semashev-AT-gmail.com> wrote:
>
>> Thank you for the clarifications, Beman.
>>
>> On December 24, 2012 8:42:10 PM Beman Dawes <bdawes_at_[hidden]> wrote:
>>>
>>> All public repos are part of boost-lib, so those that have overall
>>> write permission for https://github.com/boost-lib can modify any
>>> component library's public repo, and that includes apply changes to
>>> permissions as well as changes to the actual library.
>>
>> So, is the library repo an independent repo on GitHub that is somehow
>> linked to boost-lib (like svn externals), or is it more like a
>> subdirectory within boost-lib?
>
> http://github.com/boost-lib is the GitHub "organization" (similar to a
> user) that owns the repositories.  It is not itself a repository.
> http://github.com/boost-lib/boost is a repository that refers to the
> individual repositories as submodules.
>
>> From what you say about permissions it looks like the latter is closer
>> to the truth and in that case it is logical that permissions of owners
>> of boost-lib also apply to the subprojects.
>
> You can read about how GitHub "organization" permissions work on the
> GitHub website.
> https://help.github.com/articles/what-are-the-different-access-permissions

Thanks, this seems like what I've been missing.