Dspace (prior to version 7) used Cocoon 2.2, and enhanced its functionality, for instance, integration with Lucene SOLR. Look for the XMLUI section available from:

https://github.com/DSpace/DSpace/releases/tag/dspace-6.4

Release Notes:

https://wiki.lyrasis.org/display/DSDOC6x

I always continued to use Cocoon version 2.1x, and am hoping to use LLMs to help me refactor some of its code. I am not a JAVA developer. There were a few old code samples many (many years) ago adding some java classes, which I believe were never fully integrated into 2.13.

I still love 2.1x, and would like to see better html parser cleanup than jsoup/niko, hardening security issues, and wow, if the python integrator package could ever be upgraded, that would tie in nicely with the wide use of python language.

Cocoon pipelines are awesome.

Dan

========================


On 2024-09-13 8:15 a.m., Cédric Damioli wrote:
Do you think there exist "multiple" forks ?
I'm now aware of Gabriel's but are there any others ?

Cédric

Le 13/09/2024 à 15:58, Christofer Dutz a écrit :

It does seem as if multiple people claimed to still be using Cocoon, but maintaining their own forks.

Why not bring exactly this back to the upstream project and join forces in maintaining it?

Chris

*Von: *Cédric Damioli <cdami...@apache.org>
*Datum: *Donnerstag, 12. September 2024 um 19:31
*An: *dev@cocoon.apache.org <dev@cocoon.apache.org>
*Betreff: *Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic

Hi,

Sadly, there's not enough motivated individuals to keep the project running as is. When we ran a poll 10 months ago, very few people actually volunteered to help keeping Cocoon 2.3 alive, and the reality of these past 10 months is that nobody has barely done anything to move forward.

Anyway, now that the Attic vote has passed, we have to move forward with the due process.

Cédric

Le 11/09/2024 à 13:27, Gabriel Gruber a écrit :

    >> Can you explain why you didn't via
    https://github.com/apache/cocoon ?

    Hmm, good question actually. I wasn’t aware that the PR
    functionality was actually really used to add enhancements to the
    project and I always felt a little bit lost with the
    formal/administrative rules to get patches to the project,
    without being an official committer.

    Anyway I would be willing to add all necessary changes to make
    cocoon compatible with spring 5+ in a PR

    Cheerio,

    Gabriel

    *From: *Torsten Curdt <tcu...@apache.org> <mailto:tcu...@apache.org>
    *Date: *Wednesday, 11. September 2024 at 10:59
    *To: *dev@cocoon.apache.org <dev@cocoon.apache.org>
    <mailto:dev@cocoon.apache.org>
    *Subject: *Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache
    Attic

        It is sad, to let such a powerful project die. Having said
        that, we are using it still in production and trying to apply
        security patches on our own fork to make it compatible with
        newer versions of spring and java.

        If the project would continue on github, I can just stress
        again that I would be very happy to participate and share all
        our patches.


    Can you explain why you didn't via https://github.com/apache/cocoon ?

    Just trying to understand whether github would really make a
    difference.

    While I am still +1 for the attic (because I don't see anyone
    working on Cocoon in any form),
    it feels a little sad if there are individually maintained forks
    that could as well be part of the project.

    cheers,
    Torsten

Reply via email to