[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

FYI, a ticket has been opened recently by the openj9 project. While I think that long term we may want to capture the concept of "external collaborators" in the Eclipse Foundation database, I've proposed a solution on the ticket that requires no development and can be setup rather quickly

https://bugs.eclipse.org/bugs/show_bug.cgi?id=541770#c13

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 21 nov. 2018 Ã 23:46, Emily Jiang <emijiang6@xxxxxxxxxxxxxx> a Ãcrit :

Thanks for the useful ideas! Can we do anything in Eclipse Foundation or we have to ask github? Who should take the next step?

Thanks
Emily

On Tue, Nov 13, 2018 at 3:48 PM Nanivadekar, Nikhil <Nikhil.Nanivadekar@xxxxxx> wrote:
Can we ask GitHub support to allow maintainers of the repo to assign issues to contributors who have expressed interest. The expressed interest can be a comment on the issue itself or some other way. We can tag people on GitHub on comments, it is just about assigning it.
WDYT?


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.  See http://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.

-----Original Message-----
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx <eclipse.org-architecture-council-bounces@xxxxxxxxxxx> On Behalf Of Doug Schaefer
Sent: Tuesday, November 13, 2018 8:43 AM
To: eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-architecture-council] Ability to assign git issues to non-committers

Actually, allowing the contributor to self-select what organizations they want to be members of would be pretty nice. But I get that costs dev time from the web team.

Doug.

-----Original Message-----
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx <eclipse.org-architecture-council-bounces@xxxxxxxxxxx> On Behalf Of Gunnar Wagenknecht
Sent: Tuesday, November 13, 2018 6:29 AM
To: eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-architecture-council] Ability to assign git issues to non-committers


> On Nov 13, 2018, at 12:11, MikaÃl Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> 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.

I agree, the invitation email/experience is annoying. If there is an easy way to do it via the accounts portal then this should be sufficient.

-Gunnar



--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, https://urldefense.proofpoint.com/v2/url?u=http-3A__guw.io_&d=DwIGaQ&c=yzoHOc_ZK-sxl-kfGNSEvlJYanssXN3q-lhj0sp26wE&r=NrrbvTHWa2Nbp_kAN0Hl1o3lM1WAwSes64uBjxjNhMc&m=4zp0ZyZZ8LoEZORDb_HZQMkJ9klLlS_7P87sF4Up7nE&s=WQkay_0gNs9z-TNwSq2thI7KqndoXeDnUGx13pn9OnU&e=






_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipse.org-2Darchitecture-2Dcouncil&d=DwIGaQ&c=yzoHOc_ZK-sxl-kfGNSEvlJYanssXN3q-lhj0sp26wE&r=NrrbvTHWa2Nbp_kAN0Hl1o3lM1WAwSes64uBjxjNhMc&m=4zp0ZyZZ8LoEZORDb_HZQMkJ9klLlS_7P87sF4Up7nE&s=qtDoSd7AIOV_mRqTu24wkLeKAB09hNr1wDPeTnn2tQQ&e=

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.
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_eclipse.org-2Darchitecture-2Dcouncil&d=DwIGaQ&c=7563p3e2zaQw0AB1wrFVgyagb2IE5rTZOYPxLxfZlX4&r=h7JOQQIGild4afzuJspD2UtIxQINBIgyaphkOA7Zg1k&m=_oxx_FyUq8AHmgwSmaKvWFTXVodQnM2b6WnqGZCtu3Y&s=uUdQAvcovhNiS2aV8-ARG-hYFo-ymYQYrXETJBhO30A&e=

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.

________________________________

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<http://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.


--
Thanks
Emily
=================
Emily Jiang
ejiang@xxxxxxxxxx
_______________________________________________
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