>> 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>
Date: Wednesday, 11. September 2024 at 10:59
To: dev@cocoon.apache.org <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