[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Ability to assign git issues to non-committers

"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'm not sure this is desirable. 



MikaÃl Barbero 
Team Lead - Release Engineering | Eclipse Foundation
ð (+33) 642 028 039 | ð @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration

Le 12 nov. 2018 Ã 15:06, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> a Ãcrit :

On Nov 12, 2018, at 15:01, MikaÃl Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> wrote:

To make it work, the Foundation would need to provide some tooling (PMI?), so that projects member could set an Eclipse account as a collaborator to a project, and the tooling would define the associated github account as a external-collaborator on corresponding github repos automatically. Defining this "collaborator" relationship on the EF side makes sense as the collaborator will eventually require an Eclipse account to sign the ECA.


So there is no such limitation in Bugzilla, i.e. any committer can assign bugs to non-committers. I wonder if it would make sense to add all registered Bugzilla users (everyone with an Eclipse.org account) automatically to a collaborators team on the Eclipse GitHub org?

-Gunnar

--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/







_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: 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.

Attachment: signature.asc
Description: Message signed with OpenPGP