You're right, I'll leave it to the active committers to decide. And this 
discussion should be happening on the tm-dev list so they see it.

Sent from my BlackBerry - the most secure mobile device - via the Rogers Network
From: mist...@redhat.com
Sent: January 31, 2018 5:33 PM
To: cross-project-issues-dev@eclipse.org
Reply-to: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been 
disabled




On Wed, Jan 31, 2018 at 11:14 PM, Doug Schaefer 
<dschae...@blackberry.com<mailto:dschae...@blackberry.com>> wrote:
Does anyone want these contributions to keep RSE alive?

I don't think the opinion of others should be used as a criterion here. The 
thing is that if Nick, Rob or whoever have authored good patches, it's still 
better to contribute them into the project, independently of what others want 
to do or not with RSE. No-one is allowed to claim that a project is dead if it 
still has contributors/contributions. If the patches are proposed and seem good 
but don't get merged for other non-technical reason and contributors are still 
interested in getting those patches merged, then it's worth an escalation plan 
to turn contributors into committers.
In general, having people authoring commits can be seen as a sign that at least 
those who did the work probably have interest in authoring the commits, ie 
keeping RSE alive in that case. So to me, whenever there is a contribution, it 
shows that the project can still be perceived as alive and that no other 
discussion is necessary before applying the typical EDP processes to make sure 
project can be as successful as contributors can make it.
To sum up, we don't need to discuss RSE state any more, the patches authored by 
Rob and Nick can be a sufficient sign that RSE is still alive and we just have 
to make sure the efforts stored on a GitHub branch can be turned into activity 
in the origin code base if committers want it.

Cheers,
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to