[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

I like the idea. Everything that can help projects to be more attractive to contributors is always a big win.

I think the main limitation here is tooling. On the GitHub side, a non-committer can be assigned to a github issue iif they are external-collaborator on the repo (read-only access is enough). 

The Eclipse Foundation does not grant projects the permission to edit the list of collaborators. The projects teams are set by some Foundation tooling based on the project committers lists. 

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.

I guess that for such a thing to be planned, the first step is to open a bug on https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=GitHub

Cheers,

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

Le 11 nov. 2018 Ã 23:04, Nanivadekar, Nikhil <Nikhil.Nanivadekar@xxxxxx> a Ãcrit :

+ 1 on this.
We just had 3 PRs raised by 3 different contributors, 1 of them is a committer and 2 of them are non-committers. This leads to bad contributor experience. I did not realize that this was a GitHub specific setting, but rather a default behavior.
It will be super helpful if we could let the committers assign issues to non-committers.
 
Thanks,
Nikhil.
 
 
The Goldman Sachs Group, Inc. All rights reserved.
See http://www.gs.com/disclaimer/global_email for important risk disclosures, conflicts of interest and other terms and conditions relating to this e-mail and your reliance on information contained in it.  This message may contain confidential or privileged information.  If you are not the intended recipient, please advise us immediately and delete this message.  Seehttp://www.gs.com/disclaimer/email for further information on confidentiality and the risks of non-secure electronic communication.  If you cannot access these links, please notify us by reply message and we will send the contents to you.
 
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx <eclipse.org-architecture-council-bounces@xxxxxxxxxxx> On Behalf Of Emily Jiang
Sent: Sunday, November 11, 2018 2:55 PM
To: eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx>
Subject: [eclipse.org-architecture-council] Ability to assign git issues to non-committers
 
Dear all,
 
In MicroProfile community, a few people expressed their frustration on the fact that it is impossible to assign any git issues to non MicroProfile committers. I am sure we are not alone. I thought to bring this for wider discussion on some possible solutions. Thoughts?
 
-- 

Thanks
Emily
=================
Emily Jiang




Your Personal Data: We may collect and process information about you that may be subject to data protection laws. For more information about how we use and disclose your personal data, how we protect your information, our legal basis to use your information, your rights and who you can contact, please refer to: www.gs.com/privacy-notices
_______________________________________________
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