Yes. That was the point of all this. TM is dead. It will need to be rebooted or archived.
I’m not sure Nick’s question has been answered though. Does anyone want these contributions to keep RSE alive? It seems existing projects have adapted to its removal.
Doug.
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
On Behalf Of Greg Watson
Sent: Wednesday, January 31, 2018 3:30 PM
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled
The last commit was by Kaloyan Raev in April last year, so it is pretty much inactive at this point.
Are your fixes to the code base or to the build? If the latter, then I can probably take a look. If the former, then it might be better to take
Wayne up on his suggestion.
Greg
OK, but what happens if the project is dead, no longer being developed, and was kicked off the simrel train for its inactivity / failure to declare intent on time?
I'll happily contribute the fixes, but if no one reviews them or if they're bigger than the 1000 LOC limit, we're going to have a bad time. :)
On Wed, Jan 31, 2018 at 12:29 PM, Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
You don't need to be a committer to make a contribution. In fact, that's the exact opposite of how it's supposed to happen.
The existing committers can then choose to nominate you as a committer to support that contribution.
In exceptional circumstances, the PMC can declare a project dysfunctional and ask me to just appoint committers, but that is only if we believe that the circumstances are indeed exceptional.
On Wed, Jan 31, 2018 at 12:16 PM, Nick Boldt <nboldt@xxxxxxxxxx> wrote:
Yes, that's what I was suggesting. We contribute the handful of fixes in Rob's fork back to the master repo on
git.eclipse.org, build it on a HIPP, and contribute it into Photon.0.M6.
If someone nominates me as a committer to TM/RSE, I'll make this happen.
On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt <nboldt@xxxxxxxxxx> wrote:
Should we want to re-include RSE in Photon, we could do so for M6 if someone grants me a place to publish it & permission to do so. We've got a fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and it currently builds
against Photon.0.M4. This could easily be moved to an Eclipse HIPP, such as this one [2], if I can get permission to edit jobs there & publish to
download.eclipse.org.
The only way forward, should we want to re-include RSE in Photon, would be that Rob and you get the patches you authored merged in the actual TM/RSE repository at
Eclipse.org.
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt /
http://nick.divbyzero.com
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Wayne Beaton
Director of Open Source Projects
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt /
http://nick.divbyzero.com
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
