Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Not to mention the situations where you are a committer on the project and it rejects you because you didn't sign off your own commit.

+1 for seeking a path forward

I think Trivial is the key here that we could lean in on, if there is no potential IP involved then we should do our best on streamlining those commits, and have a signed off requirement on things more substantial.  Even 'no signed off required for a 5 or less lines' would be an improvement I think.


jesse mcconnell

On Thu, Mar 4, 2021 at 9:16 AM Liviu Ionescu <ilg@xxxxxxxxxx> wrote:

> On 4 Mar 2021, at 16:51, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
> I have done a scientific measurement. See below how the process works in practice [1] with drop-off percentages in each step of the process.

Regardless of the actual calculation, I fully agree with Wim, there are many Eclipse Foundation procedures that are far from developer friendly (to put it politely).

Given that many projects moved to GitHub, a simple GitHub account should be enough for contributors.

Not directly related, but similar in results, is the absurd strictness of GitHub access rights, even for project leads and committers.

For example, if I want to set the Embedded CDT description in GitHub, an operation that usually takes less than a minute, I cannot do it myself, I have to open a Bugzilla ticket and some authorised Foundation administrator will do it for me.

Completely inefficient, as many other Foundation procedures. :-(



cross-project-issues-dev mailing list
To unsubscribe from this list, visit

Back to the top