|They currently "have no limit imposed".|
So, it should be possible to create "Eclipse Foundation members" teams (one per org managed by the Foundation) with read permission to every repositories. We will still need to find a way to do that while being respectful of github api rates...
One more question: what do you think about the spamming? Each individual with an Eclipse account associated to a github ID will receive an invite for each orgs the Foundation is managing. Why would someone get an invite to join the eclipse-cbi and the eclipse-sirius organizations when she is only interested in contributing to eclipse-ee4j?
I don't think it's reasonable to do that, especially in the GDPR context. IMO, the safe way is for account.eclipse.org
to provide a mean to join these teams easily.
_______________________________________________eclipse.org-architecture-council mailing listeclipse.org-architecture-council@xxxxxxxxxxxhttps://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-councilIMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
You're correct Gunnar. I was focusing on using collaborators for that purpose, not team.
Does any of you know the size limit of a team? If there is any, can child team be used as a workaround?
"External collaborators" is not a team concept, it's a per-repository setting.
You proposal would mean adding every BZ accounts as external contributor to each and every github repo managed by the Foundation.
I don't think so. The documentation is pretty clear:
> If you have write access to a repository, you can assign issues and pull requests to yourself, collaborators on personal projects, *or* members of your organization with read permissions on the repository.
Thus, it should be possible to create a single team per org that gets read permissions to all repositories.