You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Cédric Damioli <cd...@apache.org> on 2023/12/01 17:00:08 UTC
[DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Hi,
Second thread to discuss about Cocon 2.x branch, with the latest
release, 2.3.0, just being rolled out.
Cocoon 2.2 was initially meant to implements all stuff developed during
the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.
We'd like to know whether you'd prefer:
[ ] retiring Cocoon 2.x
[ ] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
somehow involved
Please note that the above proposal is not a formal vote, but more like
a open poll, so that everyone could speak out.
Should we continue the project and this branch particularly, there are
recent threads on this list proposing to switch to Git, to upgrade
dependencies, build system, ...
Cédric
Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> Dear Cocoon users and developers,
>
> Sorry for crossposting here, I wanted to be sure that all involved
> people were aware of the ongoing discussions.
>
> We recently pushed a new release of Cocoon, 11 years after the
> previous one. This release gathers all changes made in between as well
> as two security fixes discovered last year.
> The journey to roll this release out was definitively not an easy one,
> and it's now time to think about what should be next for the project.
>
> We currently officially maintain 3 branches, not compatible with each
> others and having evolved differently over the years : 2.1.x, 2.2/2.3
> and 3.0, and we do not have enough active developers to be able to
> continue to properly and correctly maintain them.
>
> For a project as old as Cocoon (21 years!), there may be many users
> around here still using one branch or another, which could be
> interested to step up, contribute and try to revive the project, or at
> least some parts of it.
>
> I will soon start 3 threads on the developers list to decide what to
> do about each of the 3 branches (retiring or not), so I encourage
> volunteers to bring their voices.
>
> Best regards,
> Cédric, on behalf of the Apache Cocoon PMC
>
--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org
Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Posted by Carlos Armando Chávez Chavarría <cc...@agssa.net>.
In the company I work sometime ago it was created a fork from the branch
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X-dojo1_1
As far I remember someone at apache created that version to upgrade the
DojoToolkit java script framework.
In our fork I worked to make it work in Java 1.8, then Java 11 and later
in Java 17.
In our fork I worked to make it work the XSP as well in those java versions.
In our fork I have the Dojotoolkit updated to the version 1.17.2
There is some issue about the flowscript framework that in our fork
still using the Rhino version rhino1.5r4-continuations-R26.jar but that
branch was updated to the version s-1.6R5.jar but that version break our
application.
I don't think there is people using that branch, we still have a active
application using that, but the changes I made was mostly to make it run
on newer java versions and some minor fixes.
On 1/12/23 12:27, Christofer Dutz wrote:
> I'd be -1 on retiring 2.x.
>
> I put in the work to fix things, cause I still think there's valid
> usecases for it.
>
> I would be willing to help and try to see, if we can reinitialize a
> small community around it.
>
> Chris
>
> Gesendet von Outlook für Android <https://aka.ms/AAb9ysg>
> ------------------------------------------------------------------------
> *From:* Cédric Damioli <cd...@apache.org>
> *Sent:* Friday, December 1, 2023 6:42:08 PM
> *To:* dev@cocoon.apache.org <de...@cocoon.apache.org>
> *Subject:* Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon
> project)
>
>
> Le 01/12/2023 à 18:00, Cédric Damioli a écrit :
> >
> > We'd like to know whether you'd prefer:
> > [ ] retiring Cocoon 2.x
> > [ ] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
> > somehow involved
> >
> I'd vote +0 for retiring 2.x, holding my thoughts until the result of
> this thread.
> I personally don't use it nor plan to use it, but with my PMC member hat
> on, I see that there's still some interest around here.
> The current PMC and committers roster is not sufficient to keep the
> project alive, but with new volunteers, why not ...
>
> Cédric
--
Saludos.
Carlos Armando Chávez Chavarría.
AG Software, S.A.
Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Posted by Christofer Dutz <ch...@c-ware.de>.
I'd be -1 on retiring 2.x.
I put in the work to fix things, cause I still think there's valid usecases for it.
I would be willing to help and try to see, if we can reinitialize a small community around it.
Chris
Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
________________________________
From: Cédric Damioli <cd...@apache.org>
Sent: Friday, December 1, 2023 6:42:08 PM
To: dev@cocoon.apache.org <de...@cocoon.apache.org>
Subject: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Le 01/12/2023 à 18:00, Cédric Damioli a écrit :
>
> We'd like to know whether you'd prefer:
> [ ] retiring Cocoon 2.x
> [ ] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
> somehow involved
>
I'd vote +0 for retiring 2.x, holding my thoughts until the result of
this thread.
I personally don't use it nor plan to use it, but with my PMC member hat
on, I see that there's still some interest around here.
The current PMC and committers roster is not sufficient to keep the
project alive, but with new volunteers, why not ...
Cédric
Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Posted by Cédric Damioli <cd...@apache.org>.
Le 01/12/2023 à 18:00, Cédric Damioli a écrit :
>
> We'd like to know whether you'd prefer:
> [ ] retiring Cocoon 2.x
> [ ] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
> somehow involved
>
I'd vote +0 for retiring 2.x, holding my thoughts until the result of
this thread.
I personally don't use it nor plan to use it, but with my PMC member hat
on, I see that there's still some interest around here.
The current PMC and committers roster is not sufficient to keep the
project alive, but with new volunteers, why not ...
Cédric
Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Posted by Gabriel Gruber <ga...@workflow.at>.
Sorry, just to clarify: [+1] on
reviving/maintaining Cocoon 2.3+, meaning that you volunteer to be somehow involved. Main point for us never considering C3 was that it somehow never left alpha state and that it did not support cocoon forms AFAIKT
Cheers, Gabriel
Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
________________________________
From: Christofer Dutz <ch...@c-ware.de>
Sent: Sunday, December 3, 2023 12:03:43 PM
To: dev@cocoon.apache.org <de...@cocoon.apache.org>
Subject: AW: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Even if in the end we decide to keep 2.3.x running, we probably should go through the module list and retire some of the modules. I know that for some I couldn’t update to good versions, as the technology they use was abandoned. So, cutting the hair of our modules, might be necessary.
Chris
Von: Gabriel Gruber <ga...@workflow.at>
Datum: Samstag, 2. Dezember 2023 um 12:25
An: dev@cocoon.apache.org <de...@cocoon.apache.org>
Betreff: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
-1 on retiring cocoon 2.3.x. It needs some more love in maintaining but it works even with spring 5 and java 11(for us). Would like to see it run with spring boot.
Migrating to github and having a fork/PR workflow could bring some Traktion on it's own from willing supporters/users.
What could be a valid goal would maybe to repackage cocoon with docker so that it can be easily used by 2.1.x users?
Cheers,
Gabriel
Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
________________________________
From: Peter Hunsberger <pe...@gmail.com>
Sent: Friday, December 1, 2023 9:45:24 PM
To: dev@cocoon.apache.org <de...@cocoon.apache.org>
Subject: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
On Fri, Dec 1, 2023 at 11:00 AM Cédric Damioli <cd...@apache.org>> wrote:
Hi,
Second thread to discuss about Cocon 2.x branch, with the latest
release, 2.3.0, just being rolled out.
Cocoon 2.2 was initially meant to implements all stuff developed during
the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.
We'd like to know whether you'd prefer:
[-1 ] retiring Cocoon 2.x
[+0] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
somehow involved
Please note that the above proposal is not a formal vote, but more like
a open poll, so that everyone could speak out.
Should we continue the project and this branch particularly, there are
recent threads on this list proposing to switch to Git, to upgrade
dependencies, build system, ...
Cédric
Not sure I can really commit to helping much, other than testing releases, I don't see having the time to dive into the code anymore but I do still see people using this code base.
Peter Hunsberger
Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> Dear Cocoon users and developers,
>
> Sorry for crossposting here, I wanted to be sure that all involved
> people were aware of the ongoing discussions.
>
> We recently pushed a new release of Cocoon, 11 years after the
> previous one. This release gathers all changes made in between as well
> as two security fixes discovered last year.
> The journey to roll this release out was definitively not an easy one,
> and it's now time to think about what should be next for the project.
>
> We currently officially maintain 3 branches, not compatible with each
> others and having evolved differently over the years : 2.1.x, 2.2/2.3
> and 3.0, and we do not have enough active developers to be able to
> continue to properly and correctly maintain them.
>
> For a project as old as Cocoon (21 years!), there may be many users
> around here still using one branch or another, which could be
> interested to step up, contribute and try to revive the project, or at
> least some parts of it.
>
> I will soon start 3 threads on the developers list to decide what to
> do about each of the 3 branches (retiring or not), so I encourage
> volunteers to bring their voices.
>
> Best regards,
> Cédric, on behalf of the Apache Cocoon PMC
>
--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org<http://www.ametys.org>
AW: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Posted by Christofer Dutz <ch...@c-ware.de>.
Even if in the end we decide to keep 2.3.x running, we probably should go through the module list and retire some of the modules. I know that for some I couldn’t update to good versions, as the technology they use was abandoned. So, cutting the hair of our modules, might be necessary.
Chris
Von: Gabriel Gruber <ga...@workflow.at>
Datum: Samstag, 2. Dezember 2023 um 12:25
An: dev@cocoon.apache.org <de...@cocoon.apache.org>
Betreff: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
-1 on retiring cocoon 2.3.x. It needs some more love in maintaining but it works even with spring 5 and java 11(for us). Would like to see it run with spring boot.
Migrating to github and having a fork/PR workflow could bring some Traktion on it's own from willing supporters/users.
What could be a valid goal would maybe to repackage cocoon with docker so that it can be easily used by 2.1.x users?
Cheers,
Gabriel
Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
________________________________
From: Peter Hunsberger <pe...@gmail.com>
Sent: Friday, December 1, 2023 9:45:24 PM
To: dev@cocoon.apache.org <de...@cocoon.apache.org>
Subject: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
On Fri, Dec 1, 2023 at 11:00 AM Cédric Damioli <cd...@apache.org>> wrote:
Hi,
Second thread to discuss about Cocon 2.x branch, with the latest
release, 2.3.0, just being rolled out.
Cocoon 2.2 was initially meant to implements all stuff developed during
the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.
We'd like to know whether you'd prefer:
[-1 ] retiring Cocoon 2.x
[+0] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
somehow involved
Please note that the above proposal is not a formal vote, but more like
a open poll, so that everyone could speak out.
Should we continue the project and this branch particularly, there are
recent threads on this list proposing to switch to Git, to upgrade
dependencies, build system, ...
Cédric
Not sure I can really commit to helping much, other than testing releases, I don't see having the time to dive into the code anymore but I do still see people using this code base.
Peter Hunsberger
Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> Dear Cocoon users and developers,
>
> Sorry for crossposting here, I wanted to be sure that all involved
> people were aware of the ongoing discussions.
>
> We recently pushed a new release of Cocoon, 11 years after the
> previous one. This release gathers all changes made in between as well
> as two security fixes discovered last year.
> The journey to roll this release out was definitively not an easy one,
> and it's now time to think about what should be next for the project.
>
> We currently officially maintain 3 branches, not compatible with each
> others and having evolved differently over the years : 2.1.x, 2.2/2.3
> and 3.0, and we do not have enough active developers to be able to
> continue to properly and correctly maintain them.
>
> For a project as old as Cocoon (21 years!), there may be many users
> around here still using one branch or another, which could be
> interested to step up, contribute and try to revive the project, or at
> least some parts of it.
>
> I will soon start 3 threads on the developers list to decide what to
> do about each of the 3 branches (retiring or not), so I encourage
> volunteers to bring their voices.
>
> Best regards,
> Cédric, on behalf of the Apache Cocoon PMC
>
--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org<http://www.ametys.org>
Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Posted by Gabriel Gruber <ga...@workflow.at>.
-1 on retiring cocoon 2.3.x. It needs some more love in maintaining but it works even with spring 5 and java 11(for us). Would like to see it run with spring boot.
Migrating to github and having a fork/PR workflow could bring some Traktion on it's own from willing supporters/users.
What could be a valid goal would maybe to repackage cocoon with docker so that it can be easily used by 2.1.x users?
Cheers,
Gabriel
Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
________________________________
From: Peter Hunsberger <pe...@gmail.com>
Sent: Friday, December 1, 2023 9:45:24 PM
To: dev@cocoon.apache.org <de...@cocoon.apache.org>
Subject: Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
On Fri, Dec 1, 2023 at 11:00 AM Cédric Damioli <cd...@apache.org>> wrote:
Hi,
Second thread to discuss about Cocon 2.x branch, with the latest
release, 2.3.0, just being rolled out.
Cocoon 2.2 was initially meant to implements all stuff developed during
the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.
We'd like to know whether you'd prefer:
[-1 ] retiring Cocoon 2.x
[+0] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
somehow involved
Please note that the above proposal is not a formal vote, but more like
a open poll, so that everyone could speak out.
Should we continue the project and this branch particularly, there are
recent threads on this list proposing to switch to Git, to upgrade
dependencies, build system, ...
Cédric
Not sure I can really commit to helping much, other than testing releases, I don't see having the time to dive into the code anymore but I do still see people using this code base.
Peter Hunsberger
Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> Dear Cocoon users and developers,
>
> Sorry for crossposting here, I wanted to be sure that all involved
> people were aware of the ongoing discussions.
>
> We recently pushed a new release of Cocoon, 11 years after the
> previous one. This release gathers all changes made in between as well
> as two security fixes discovered last year.
> The journey to roll this release out was definitively not an easy one,
> and it's now time to think about what should be next for the project.
>
> We currently officially maintain 3 branches, not compatible with each
> others and having evolved differently over the years : 2.1.x, 2.2/2.3
> and 3.0, and we do not have enough active developers to be able to
> continue to properly and correctly maintain them.
>
> For a project as old as Cocoon (21 years!), there may be many users
> around here still using one branch or another, which could be
> interested to step up, contribute and try to revive the project, or at
> least some parts of it.
>
> I will soon start 3 threads on the developers list to decide what to
> do about each of the 3 branches (retiring or not), so I encourage
> volunteers to bring their voices.
>
> Best regards,
> Cédric, on behalf of the Apache Cocoon PMC
>
--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org<http://www.ametys.org>
Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)
Posted by Peter Hunsberger <pe...@gmail.com>.
On Fri, Dec 1, 2023 at 11:00 AM Cédric Damioli <cd...@apache.org> wrote:
> Hi,
>
> Second thread to discuss about Cocon 2.x branch, with the latest
> release, 2.3.0, just being rolled out.
> Cocoon 2.2 was initially meant to implements all stuff developed during
> the 2.1 cycle on top of Spring and Maven, to drop old Avalon dependencies.
>
> We'd like to know whether you'd prefer:
> [-1 ] retiring Cocoon 2.x
>
> [+0] reviving/maintaining Cocoon 2.x, meaning that you volunteer to be
> somehow involved
>
> Please note that the above proposal is not a formal vote, but more like
> a open poll, so that everyone could speak out.
>
> Should we continue the project and this branch particularly, there are
> recent threads on this list proposing to switch to Git, to upgrade
> dependencies, build system, ...
>
> Cédric
>
Not sure I can really commit to helping much, other than testing releases,
I don't see having the time to dive into the code anymore but I do still
see people using this code base.
Peter Hunsberger
> Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
> > Dear Cocoon users and developers,
> >
> > Sorry for crossposting here, I wanted to be sure that all involved
> > people were aware of the ongoing discussions.
> >
> > We recently pushed a new release of Cocoon, 11 years after the
> > previous one. This release gathers all changes made in between as well
> > as two security fixes discovered last year.
> > The journey to roll this release out was definitively not an easy one,
> > and it's now time to think about what should be next for the project.
> >
> > We currently officially maintain 3 branches, not compatible with each
> > others and having evolved differently over the years : 2.1.x, 2.2/2.3
> > and 3.0, and we do not have enough active developers to be able to
> > continue to properly and correctly maintain them.
> >
> > For a project as old as Cocoon (21 years!), there may be many users
> > around here still using one branch or another, which could be
> > interested to step up, contribute and try to revive the project, or at
> > least some parts of it.
> >
> > I will soon start 3 threads on the developers list to decide what to
> > do about each of the 3 branches (retiring or not), so I encourage
> > volunteers to bring their voices.
> >
> > Best regards,
> > Cédric, on behalf of the Apache Cocoon PMC
> >
>
> --
> Cédric Damioli
> CMS - Java - Open Source
> www.ametys.org
>
>