Boost logo

Boost :

Subject: Re: [boost] [GitHub] [PR] setting default branch to 'develop'
From: Louis Dionne (ldionne.2_at_[hidden])
Date: 2015-10-29 14:39:11

Vladimir Prus <vladimir.prus <at>> writes:

> On 29-Oct-15 4:07 AM, Louis Dionne wrote:
> > Also, shouldn't I be the one to have sufficient admin rights to change
> > that kind of thing? I don't like the idea that anyone with sufficient
> > rights within 'boostorg' can do as they please with my repository ('my'
> > taken lightly).
> Until yesterday (almost literally), it was not possible to give you admin
> permissions for 'hana', without also giving you admin permissions for every
> other repository in the 'boostorg' organization. I've now tweaked the
> settings so that you can add/remove collaborators on 'hana'.

Thanks a lot! I now also have access to the repository hooks and other things
I lost when transferring to boostorg. That's much better!

> Note, however, that those with sufficient permissions in the 'boostorg'
> organization will always be able to change settings on 'boostorg/hana'.
> While any changes will be mentioned on the mailing list, and generally
> un-doable, it's just not possible to lock your repository, nor would it
> be reasonable to ask people to individually tweak settings on 100+
> repositories.

When a library has an active maintainer, I think the very least would be to
ask the maintainer for such things before doing them, especially if they are
undoable. I might be a control freak, but I don't like the idea that someone
can play around with a setup that I might have spent several hours setting up
and potentially break it. The very least would be to announce such changes on
the mailing list, ask for feedback and see if anyone disagrees. Once some
agreement has been reached (and I'm not asking for consensus), we could then
proceed with the changes.


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