Decide about member/external collaborator type for non alliance users

[yaSebastian]

What

A decision has to be made about the user type of non alliance users.

Two options are available:

• Member
• External collaborator

Personal opinion

I would suggest external collaborator, though those come with some limitations. You can read about those under the following links:

• https://stackoverflow.com/questions/42512787/difference-between-organisation-member-and-outside-collaborator-in-github#comment112817378_42513996
• https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator

[yaSebastian]

@MoriartyJr , do you have an opinion on this? Can you please add it? Final decision has to be made by the alliance, most likely Armin Pelka.

[lombardi-antonio]

I would tend to the outside collaborator as well. Especially if the EnOcean Alliance decides to host more private repositories on this organization in GitHub, if some will contain sensible data, that should not be accessible by everybody.

The Limitations are mainly in the creation and administration of the Teams, something that I would prefer not every collaborator be able to do anyways. Furthermore if an outside collaborator needs access to all the repositories we could create a Team that will do just that and let that collaborator be a member of that team.