[Freemint-list] Github access rights

[Miro Kropáček]

>
> As I understand, the rules are:
> - wiki can be edited by... any GitHub user, or only members? To be
> verified.
> - website can be edited by all members (have to be manually added)
> - repositories can only be written by their specific teams
>
Yeah, we have to wait for the first non-member wiki contributor to verify
this. :-)


> So if a GitHub user wants to contribute to code but does not plan to edit
> the website, he doesn't need to become a member.
> However, regular contributors should be encouraged to become members, as
> they could occasionally improve the website without pull requests.
>
Yep. There's one more category but I think it just complicates things, you
can name someone as a "contributor" so he gets write access but is excluded
from some things. Perhaps easier to have just one team with write access
and that's it.

Beware, git filter-branch and other rebase break all the branches. I learned
> that when creating binutils/gcc repositories. I had to start over many
> times
> because of that.
>
Me too, me too. :D That's why I want to do this as early as possible with
as many logins as possible.

So be sure to make a backup (dumb! backup is GitHub :-) ) before doing that.
> Maybe the conclusion could be that it's already too late.
>
It shouldn't be that dramatic, even github encourages people to do that:
https://help.github.com/articles/changing-author-info ... what I truly hope
(and this I have to verify first ) is that forks (like
github.com/mikrosk/freemint) don't break. If they do, then *now* is really
the time to do that. ;-)

-- 
MiKRO / Mystic Bytes
http://mikro.atari.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.atariforge.org/pipermail/freemint-list/attachments/20170126/1eb6dd83/attachment.html