Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-architecture-council] Main remaining obstacles for contributors: req Eclispe account to sign ECA

Hi all,

Yesterday, we acknowledged all the major progress made by Eclipse Foundation to simplify contributions for everyone; and we were short of ideas when brainstorming about "what's next".

I moved Tycho to GitHub yesterday and got a reminder about what is the main obstacle for new contributors this day, after a contributor closed an interesting PR by lack of motivation to carry on contributions process. The actual reason was actually already mentioned by Jonah recently:
The main issue I see now are some people not willing to *create an Eclipse.org account to sign the ECA*. That doesn't seem specific to Eclipse.org account but more people fed up with creating new accounts here and there.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=571711 (and duplicates) was suggested to improve things here by facilitating creation of an Eclipse.org account. But we should probably think further: do we really want contributors to have an Eclipse.org account to contribute? Isn't it enough to let them just sign the ECA (similarly to other vendors/communities)? I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=572724 to ask for a way to get ECA signed without creating an account. IMO, this would be more profitable, and maybe simpler to deploy and use, than the "Login with GitHub" story.

I probably won't be participating in the next AC call because of an upcoming baby, but I think this topic can be made in the agenda and discussed. One possible outcome is that -if AC agrees with that- AC makes a recommendation to EMO to prioritize bug 572724 over bug 571711.

Cheers,
--
Mickael Istria
Eclipse IDE developer, for Red Hat Developers

Back to the top