Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

I want to follow up and testify how successful this change is. People without an ECA or without any idea of the process, flow in easily as contributors. I also want to say how successful the move to Github can be. In the BIRT project, we were able to attract a couple of highly skilled developers w

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Hey All, Great news!! *Comment # 30 * Cheers, Wim On Tue, Mar 16, 2021 at 1:29 PM Wim Jongman wrote: > > > On Tue, Mar 16, 2021 at 1:01 AM Jonah Graham > wrote: > >> The Architecture Council discussed this at the most recent meeting

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

On Tue, Mar 16, 2021 at 1:01 AM Jonah Graham wrote: > The Architecture Council discussed this at the most recent meeting - see > notes https://wiki.eclipse.org/Architecture_Council/Meetings/Meeting_Notes > - below I quote the relevant part: > > >- 'Signed Off By' requirements (from cross plat

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

The Architecture Council discussed this at the most recent meeting - see notes https://wiki.eclipse.org/Architecture_Council/Meetings/Meeting_Notes - below I quote the relevant part: - 'Signed Off By' requirements (from cross platform list topic, https://bugs.eclipse.org/558653) - Wor

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Right! I did not know that was an option. Basically, it means that the technology is there to always require it and to switch it off for committers. Al we need is the final last option to switch it off for people that have signed the contributor agreement. Cheers, Wim On Mon, Mar 15, 2021 a

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Denis, Is that a hard and fast rule everywhere? Because I get forced to sign on the jetty.git website repository on git.eclipse.org Jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Mon, Mar 15, 2021 at 2:09 PM Denis Roy wrote: > As per the bug, Signed-off-by is NOT required for committe

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

As per the bug, Signed-off-by is NOT required for committers on that project. You are a committer on that project. s/Yay/Boo/ On 2021-03-15 3:05 p.m., Wim Jongman wrote: > I have seen that the BIRT project does NOT require the dreaded > "signed-off by:" footer. Yay, maybe it is already working:

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

sorry: https://github.com/eclipse/birt/pull/610 shows it better On Mon, Mar 15, 2021 at 8:05 PM Wim Jongman wrote: > I have seen that the BIRT project does NOT require the dreaded "signed-off > by:" footer. Yay, maybe it is already working: > > e.g. https://github.com/eclipse/birt/pull/616 > > O

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

I have seen that the BIRT project does NOT require the dreaded "signed-off by:" footer. Yay, maybe it is already working: e.g. https://github.com/eclipse/birt/pull/616 On Thu, Mar 4, 2021 at 5:20 PM Gunnar Wagenknecht wrote: > > On Mar 4, 2021, at 16:47, Jesse McConnell > wrote: > > > > I adde

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

> On Mar 4, 2021, at 16:47, Jesse McConnell wrote: > > I added an action item to discuss on AC call next week. Thanks Jesse. I also added the other two items in the thread to the list. For visibility, the bug (with further details) around "Signed-off by" is: https://bugs.eclipse.org/558653 Thi

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

> On 4 Mar 2021, at 17:46, Frederic Gurr > wrote: > > Hi, > > This is mostly off-topic, but it needs to be set right. > > On 04.03.21 16:16, Liviu Ionescu wrote: >> Not directly related, but similar in results, is the absurd strictness of >> GitHub access rights, even for project leads and

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

I added an action item to discuss on AC call next week. -- jesse mcconnell jesse.mcconn...@gmail.com On Thu, Mar 4, 2021 at 9:33 AM Ed Merks wrote: > Folks, > > I did repeatedly try to get this change, posting arguments such as this > below (in which I did to remove some email addresses to not

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Hi, This is mostly off-topic, but it needs to be set right. On 04.03.21 16:16, Liviu Ionescu wrote: > 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 descr

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Folks, I did repeatedly try to get this change, posting arguments such as this below (in which I did to remove some email addresses to not post them here).  I got Matthias Sohn to also back up the arguments.  But so far to no avail... I can try again, but it seems pointless to repeat the sam

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 streaml

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

> On 4 Mar 2021, at 16:51, Wim Jongman 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 pr

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Hi Wim, Thanks for sharing your methodology. I can't speak for the 1% result, but it does not surprise me. The Step 8 is the biggest PITA for contributors on the GitHub PR flow. Many (most?) PR contributors on github never rebase or amend their commits (for other projects). I have had to regularly

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

We at Xtext see a similar result, especially with changes done via github web. Telling people to clone and signoff for a trivial fix often leads to omitting the PR and recreate the change ourselves. Am 04.03.21 um 15:51 schrieb Wim Jongman: > > 2. ay: You did not sign the ECA. > 3. 21% of the co

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Hi, > >> We lose 99% of our casual contributors. >> > > Can you share some insight on how you got this high number? > 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. Cheers, Wim [1] *This is the origin

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Hi, > We lose 99% of our casual contributors. > Can you share some insight on how you got this high number? 1. Merge the new user and ECA signing process into one fluent wonderful > experience. > We currently redirect all users to the ECA form on login if they don't have one on file. 2. Get ri

Re: [cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

On Thu, Mar 4, 2021 at 2:52 PM Wim Jongman wrote: > We lose 99% of our casual contributors. > That's a huge exaggeration ;) But thanks for bringing attention on this important topic! I agree the "Signed-Off-By" is becoming a point of friction and making the contribution barrier higher than for

[cross-project-issues-dev] The "new user -> ECA -> signed-off by" workflow is broken

Hi, We lose 99% of our casual contributors. I suggest that we pay someone to fix the following. 1. Merge the new user and ECA signing process into one fluent wonderful experience. 2. Get rid of the "Signed-off-by" requirement in commit messages. VSCode's CLA Process -> (takes less than a minute