I'm delighted to see DBD::mysql maintenance moving again.
On Wed, Aug 28, 2013 at 09:02:07AM +0200, H.Merijn Brand wrote:
>
> What I do not know how to do is make you a committer to this repo with
> you also being a committer to all projects in perl5-dbi and I do not
> know Tim's policy/policies in this.
Anyone can fork a repo and send a pull request in the normal way.
There's no "need" to give out commit bits for direct access by default.
On the other hand, it's nice to reduce friction for regular contributors.
I think the way this might work via the GitHub team mechanism is:
* "DBD-Foo" - One team per driver. Push, pull, and administrative access to the
repo for that driver.
* "Contributors" - push and pull access (no admin) to ALL repos in the org.
Trust level:
0: fork and send pull requests
1: "Contributors" = "a commit bit for the perl5-dbi org"
2: "Contributors" + "DBD-Foo"
I figure that we'd add anyone who's a regular/trustworthy contributor
to the Contributors team.
Driver authors/admins can add people to their own "DBD-Foo" team.
Sound ok?
Tim.
p.s. There's an "Owners" team with full access to all repositories and
have admin rights to the organization itself. We have 5 people already
and I don't see a need to add more at the moment.
