You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Sathwik B P <sa...@gmail.com> on 2018/10/09 10:21:57 UTC
Is it time for Retire Apache ODE?
Hi Devs/Users,
I had started this dicussion thread over an year ago
[
https://lists.apache.org/thread.html/29951cfa866d36d16a5c80b51838b9cc2f5228020d110f607e8b0e1c@%3Cdev.ode.apache.org%3E].
Nothing has much moved forward since then. Our last 2 reporting cycles have
been very dull without much of activity. We do not see any other PMC
members active apart from taking part in the voting of releases.
I presume, we probably do not have the active PMC quorum to fix any
security issues in present and future.
Incase any other PMC member is willing to take over the Chair position and
carry on from here and not want to retire the project, raise your hand and
I will initiate the process.
Otherwise,
" I propose to move Apache ODE to the Attic."
If the PMC agrees, I will start a vote. Let me know your suggestions.
For the users, this basically means if the PMC agrees to the voting and
successfully votes to retire the project, then the project will not be
actively maintained, no future releases, no bug fixes,no security patches.
The source code will be available to all in read only mode, though one can
fork your own copies of the repo on github.com/apache/ode.
regards,
ODE PMC Chair
Fwd: Is it time for Retire Apache ODE?
Posted by Sathwik B P <sa...@gmail.com>.
forwarding to user mailing list.
---------- Forwarded message ---------
From: Sathwik B P <sa...@gmail.com>
Date: Tue, Oct 9, 2018 at 3:51 PM
Subject: Is it time for Retire Apache ODE?
To: <de...@ode.apache.org>
Hi Devs/Users,
I had started this dicussion thread over an year ago
[
https://lists.apache.org/thread.html/29951cfa866d36d16a5c80b51838b9cc2f5228020d110f607e8b0e1c@%3Cdev.ode.apache.org%3E].
Nothing has much moved forward since then. Our last 2 reporting cycles have
been very dull without much of activity. We do not see any other PMC
members active apart from taking part in the voting of releases.
I presume, we probably do not have the active PMC quorum to fix any
security issues in present and future.
Incase any other PMC member is willing to take over the Chair position and
carry on from here and not want to retire the project, raise your hand and
I will initiate the process.
Otherwise,
" I propose to move Apache ODE to the Attic."
If the PMC agrees, I will start a vote. Let me know your suggestions.
For the users, this basically means if the PMC agrees to the voting and
successfully votes to retire the project, then the project will not be
actively maintained, no future releases, no bug fixes,no security patches.
The source code will be available to all in read only mode, though one can
fork your own copies of the repo on github.com/apache/ode.
regards,
ODE PMC Chair
Re: Is it time for Retire Apache ODE?
Posted by Tammo van Lessen <tv...@gmail.com>.
Hi Paul, all,
Very well put. It's difficult to let a good friend go, but I think, too,
the time has come for ODE to be retired.
Thanks,
Tammo
Paul Brown <pa...@gmail.com> schrieb am Di., 9. Okt. 2018, 18:33:
> ODE has had a long life, especially when I think back to some of the
> initial work in 2002-2003.
>
> It can head for the attic with honor.
>
> On Tue, Oct 9, 2018 at 03:22 Sathwik B P <sa...@gmail.com> wrote:
>
> > Hi Devs/Users,
> >
> > I had started this dicussion thread over an year ago
> > [
> >
> >
> https://lists.apache.org/thread.html/29951cfa866d36d16a5c80b51838b9cc2f5228020d110f607e8b0e1c@%3Cdev.ode.apache.org%3E
> > ].
> >
> >
> > Nothing has much moved forward since then. Our last 2 reporting cycles
> have
> > been very dull without much of activity. We do not see any other PMC
> > members active apart from taking part in the voting of releases.
> >
> > I presume, we probably do not have the active PMC quorum to fix any
> > security issues in present and future.
> >
> > Incase any other PMC member is willing to take over the Chair position
> and
> > carry on from here and not want to retire the project, raise your hand
> and
> > I will initiate the process.
> > Otherwise,
> > " I propose to move Apache ODE to the Attic."
> > If the PMC agrees, I will start a vote. Let me know your suggestions.
> >
> > For the users, this basically means if the PMC agrees to the voting and
> > successfully votes to retire the project, then the project will not be
> > actively maintained, no future releases, no bug fixes,no security
> patches.
> > The source code will be available to all in read only mode, though one
> can
> > fork your own copies of the repo on github.com/apache/ode.
> >
> > regards,
> > ODE PMC Chair
> >
>
Re: Is it time for Retire Apache ODE?
Posted by Paul Brown <pa...@gmail.com>.
ODE has had a long life, especially when I think back to some of the
initial work in 2002-2003.
It can head for the attic with honor.
On Tue, Oct 9, 2018 at 03:22 Sathwik B P <sa...@gmail.com> wrote:
> Hi Devs/Users,
>
> I had started this dicussion thread over an year ago
> [
>
> https://lists.apache.org/thread.html/29951cfa866d36d16a5c80b51838b9cc2f5228020d110f607e8b0e1c@%3Cdev.ode.apache.org%3E
> ].
>
>
> Nothing has much moved forward since then. Our last 2 reporting cycles have
> been very dull without much of activity. We do not see any other PMC
> members active apart from taking part in the voting of releases.
>
> I presume, we probably do not have the active PMC quorum to fix any
> security issues in present and future.
>
> Incase any other PMC member is willing to take over the Chair position and
> carry on from here and not want to retire the project, raise your hand and
> I will initiate the process.
> Otherwise,
> " I propose to move Apache ODE to the Attic."
> If the PMC agrees, I will start a vote. Let me know your suggestions.
>
> For the users, this basically means if the PMC agrees to the voting and
> successfully votes to retire the project, then the project will not be
> actively maintained, no future releases, no bug fixes,no security patches.
> The source code will be available to all in read only mode, though one can
> fork your own copies of the repo on github.com/apache/ode.
>
> regards,
> ODE PMC Chair
>
Re: Is it time for Retire Apache ODE?
Posted by Tammo van Lessen <tv...@gmail.com>.
Hey Olly,
If I'm not mistaken, there is no unreleased code in the branch we were
usually releasing from. Regarding a trunk release, I'm afraid it would
involve an unjustifiable effort bring it into a shape that meets our
quality criteria. There should be at least a beta release (because this
branch has never been released so far) and I doubt we would get valuable
feedback, given the shrunk user base. In fact, it is unclear if there still
is one. Thus, it would require to thoroughly test all potential
compatibility issues, which is nothing we can do in our spare time. Our
attempts to let the developer community grow failed, and we did a lot to
keep ODE's lights on, although there was no public interest in it anymore.
But now I believe retirement is the best option for ODE (and its
maintainers).
Thanks,
Tammo
Oliver Kopp <ko...@gmail.com> schrieb am Mi., 10. Okt. 2018, 07:22:
> Hey,
>
> We are still building on Apache ODE. Could you make a last release
> before moving it to attic? Thus, the Apache ODE project would have a
> defined state and not some unreleased long-written source code lying
> around.
>
> Cheers,
>
> Oliver
> Am Di., 9. Okt. 2018 um 12:22 Uhr schrieb Sathwik B P <
> sathwik.bp@gmail.com>:
> >
> > Hi Devs/Users,
> >
> > I had started this dicussion thread over an year ago
> > [
> >
> https://lists.apache.org/thread.html/29951cfa866d36d16a5c80b51838b9cc2f5228020d110f607e8b0e1c@%3Cdev.ode.apache.org%3E
> ].
> >
> >
> > Nothing has much moved forward since then. Our last 2 reporting cycles
> have
> > been very dull without much of activity. We do not see any other PMC
> > members active apart from taking part in the voting of releases.
> >
> > I presume, we probably do not have the active PMC quorum to fix any
> > security issues in present and future.
> >
> > Incase any other PMC member is willing to take over the Chair position
> and
> > carry on from here and not want to retire the project, raise your hand
> and
> > I will initiate the process.
> > Otherwise,
> > " I propose to move Apache ODE to the Attic."
> > If the PMC agrees, I will start a vote. Let me know your suggestions.
> >
> > For the users, this basically means if the PMC agrees to the voting and
> > successfully votes to retire the project, then the project will not be
> > actively maintained, no future releases, no bug fixes,no security
> patches.
> > The source code will be available to all in read only mode, though one
> can
> > fork your own copies of the repo on github.com/apache/ode.
> >
> > regards,
> > ODE PMC Chair
>
Re: Is it time for Retire Apache ODE?
Posted by Oliver Kopp <ko...@gmail.com>.
Hey,
We are still building on Apache ODE. Could you make a last release
before moving it to attic? Thus, the Apache ODE project would have a
defined state and not some unreleased long-written source code lying
around.
Cheers,
Oliver
Am Di., 9. Okt. 2018 um 12:22 Uhr schrieb Sathwik B P <sa...@gmail.com>:
>
> Hi Devs/Users,
>
> I had started this dicussion thread over an year ago
> [
> https://lists.apache.org/thread.html/29951cfa866d36d16a5c80b51838b9cc2f5228020d110f607e8b0e1c@%3Cdev.ode.apache.org%3E].
>
>
> Nothing has much moved forward since then. Our last 2 reporting cycles have
> been very dull without much of activity. We do not see any other PMC
> members active apart from taking part in the voting of releases.
>
> I presume, we probably do not have the active PMC quorum to fix any
> security issues in present and future.
>
> Incase any other PMC member is willing to take over the Chair position and
> carry on from here and not want to retire the project, raise your hand and
> I will initiate the process.
> Otherwise,
> " I propose to move Apache ODE to the Attic."
> If the PMC agrees, I will start a vote. Let me know your suggestions.
>
> For the users, this basically means if the PMC agrees to the voting and
> successfully votes to retire the project, then the project will not be
> actively maintained, no future releases, no bug fixes,no security patches.
> The source code will be available to all in read only mode, though one can
> fork your own copies of the repo on github.com/apache/ode.
>
> regards,
> ODE PMC Chair