[Freemint-list] Github access rights

[Miro Kropáček]

>
> As far as I understand, everyone is allowed to clone FreeMiNT
> repositories to their own account, then make Pull Requests if they want
> to contribute to our official sources.
>
Yes.

So as far as I understand, the only advantage of being a
> standard member would be write access to the FreeMiNT wiki, if we decide
> to do so.
>
The wiki has also separate per-project permissions, at least as far as I
understand it. I have set it for FreeMiNT so that everyone can contribute
(with a github account). So everyone is welcome to make changes. Btw the
wiki is a separate git repository, although not so visible (users are
expected to use the web ui).

1) As maintainer, Alan should have the Write permission to all the
> repositories.
>
No question about that.

2) Other people should only have Read permission, so they will need to
> make Pull Requests if they want to contribute. Then Alan will have to
> accept or reject the Pull Request.
>
If you also mean me and you, from my side it's OK, there's no more work to
setup anything, so I will happily with making PRs, as this is the case
already.

1) For Alan, it is some amount of work and responsibilities to review
> and accept Pull Requests. Maybe the Write rights could be granted to a
> few other people, at least for some repositories. This has to be discussed.
>
Alan seems to be busy for the past few days but he has agreed to this
approach AFAIR. Apart from him, there's Olivier and Arnaud as gemlib
contributors and Gerhard as a toshyp and occasional gemlib contributor.
Helmut seems to be departed from freemint development at least since 2014
(or better said I'm not sure how to interpret his attitude "I work only on
my branch and I don't plan to merge it back")


> 2) There is a special case for the freemint.github.io repository. It is
> the source of our new official website https://freemint.github.io/
> Who should have the permissions to modify it?
> Technically, it will just be a matter of giving the Write permission to
> some Member for that particular repository.
>
Yeah, we'd need to create a so called 'team' of website contributors, it's
in github main settings. Actually, we'd need perhaps something as:

   - freemint-team (freemint, mintlib, fdlibm - Alan)
   - gem-team (lib = gemlib, cflib, gemma - Arnaud, Olivier, Gerhard)
   - git-team (git - me)
   - toolchain-team (gcc, binutils - Vincent)
   - website-team (I'd say pretty much anyone

The rest (qed, init stuff, ...) I'd let it be, i.e. wait until someone
actually makes a contribution and then decide whether it's worth creating
another team. For instance Gerhard used to update Smurf, Phoenix and this
kind of stuff but I'm not sure what are his plans now.

3) About the FreeMiNT Wiki: https://github.com/freemint/freemint/wiki

This is easy, see above. I think the wiki isn't something which needs hard
supervision. If somebody goes crazy, we can still look it up in git log and
revert.


> We must find a good balance so anyone with goodwill can easily
> contribute, without the risk of trashing everything.
>
True. Luckily for us, we nearly all know each other, so risking that
somebody would appear and destruct everything is minimal.

-- 
MiKRO / Mystic Bytes
http://mikro.atari.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.atariforge.org/pipermail/freemint-list/attachments/20170125/34b7f84b/attachment-0001.html