Process for moving projects to ocaml-community

[Drup]

The current process seems to be to give rights to anyone who wants to move a project over, and since you need admin rights to transfer a project, that's what they get.

Needless to say that this is not going to fly for long. :)

I propose to distinguish various group of people:

1. Admins that can do anything,
2. People that want to maintain/contribute to specific packages, but are not (yet!) people you would trust with life&death power over the entire org. This would be for people who are frequent community member and maintain several packages
3. Maintainer of a single package, such as newly migrated packages. Those don't have to be org members and can simply be given rights to that package.

When migrating a repository, the person who wants to migrate would transfer the repository to one of the admins, who would then move it to the organization. That person would then be given rights to the specific packages, or added as org member in group 2., as deemed appropriate.

Thoughts ?

[pmetzger]

This seems like an entirely reasonable segregation of duties. So far I haven't been averse to giving organization membership to people requesting to move things because everyone involved has been someone well known in the community, but that will inevitably change. Some set of rules seems necessary, and your proposal feels like a good one.

I'd like to hear what other people think, but presuming there is consensus, I think we should go with this general idea.

One modification I would note is we need a category 0. for the organization owners, which is a role GitHub requires. There need to be several, for redundancy, and such people need to be well trusted. I gave @bluddy an owner tag temporarily so that someone could recover things in case I got hit by a bus, but we should figure out more permanently which three people have the "master keys".

[pmetzger]

FYI, we probably need to figure out how to map 1, 2, and 3 to various github settings to implement them.

[Drup]

The mapping is trivial. It already correspond to fairly obvious github roles.

[pmetzger]

Well, so there are only two roles that the system provides, "owner" and "member", plus it allows us to set outside collaborators for particular repositories. It doesn't seem to allow assignment of differing levels of ability to members except by assigning them to teams.

[Drup]

Small brush up of the roles. Adminstrators should now be able to fully migrate a repository from start to finish, and should be able to add other adminstrators and external contributors.

[pmetzger]

So how should we change the language in the README etc?

[c-cube]

is there a setting to allow people to transfer to the organization directly, and then have someone here (and admin, or maybe just a member) approve the transfer request? It seems weird that to transfer to individual accounts you don't need any right, but that for organization it's so complicated.

[Drup]

As far as I know, there is no such thing, no :/