[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipse.org-architecture-council] Ability to assign git issues to non-committers
- From: Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
- Date: Tue, 13 Nov 2018 15:43:27 +0000
- Accept-language: en-US
- Delivered-to: email@example.com
- Thread-index: AQHUeukosHSdUyvLZUGQj6bTHqrpB6VN4TIAgAAE+oD///Kg4A==
- Thread-topic: [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.
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.
eclipse.org-architecture-council mailing list
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.