Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic
Cédric Damioli <[email protected]> Thu, 12 Sep 2024 19:30:53 +0200
| Newsgroups | gmane.text.xml.cocoon.devel |
|---|---|
| Organization | Apache Software Foundation |
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --------------mIK08Hwask18DmCzeN8sIOcO Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 <[email protected]> > *Date: *Wednesday, 11. September 2024 at 10:59 > *To: *[email protected] <[email protected]> > *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 > --------------mIK08Hwask18DmCzeN8sIOcO Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hi,<br> <br> Sadly, there's not enough motivated individuals to keep the project running as is.<br> 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.<br> <br> Anyway, now that the Attic vote has passed, we have to move forward with the due process.<br> <br> Cédric<br> <br> <br> <div class="moz-cite-prefix">Le 11/09/2024 à 13:27, Gabriel Gruber a écrit :<br> </div> <blockquote type="cite" cite="mid:AS2PR02MB96560B69BE2C9F40C18818609F9B2@AS2PR02MB9656.eurprd02.prod.outlook.com"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style>@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:"Yu Gothic"; panose-1:2 11 4 0 0 0 0 0 0 0;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face {font-family:Aptos; panose-1:2 11 0 4 2 2 2 2 2 4;}@font-face {font-family:"\@Yu Gothic"; panose-1:2 11 4 0 0 0 0 0 0 0;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:10.0pt; font-family:"Aptos",sans-serif;}a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;}span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Aptos",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;}div.WordSection1 {page:WordSection1;}</style> <div class="WordSection1"> <div> <div> <p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">>> </span><span style="font-size:12.0pt">Can you explain why you didn't via <a href="https://github.com/apache/cocoon" moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/apache/cocoon</a> ?</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p> </div> </div> <p class="MsoNormal"><span lang="DE" style="font-size:11.0pt"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">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.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Anyway I would be willing to add all necessary changes to make cocoon compatible with spring 5+ in a PR<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Cheerio,<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Gabriel<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p> <div id="mail-editor-reference-message-container"> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> <p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Torsten Curdt <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br> <b>Date: </b>Wednesday, 11. September 2024 at 10:59<br> <b>To: </b><a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br> <b>Subject: </b>Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic<o:p></o:p></span></p> </div> <div> <div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div> <div> <p class="MsoNormal"><span style="font-size:12.0pt">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.<o:p></o:p></span></p> </div> <div> <p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p> </div> <div> <p class="MsoNormal"><span style="font-size:12.0pt">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.<o:p></o:p></span></p> </div> </div> </blockquote> <div> <p class="MsoNormal"><span style="font-size:12.0pt"><br> Can you explain why you didn't via <a href="https://github.com/apache/cocoon" moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/apache/cocoon</a> ?<br> <br> Just trying to understand whether github would really make a difference.<br> <br> While I am still +1 for the attic (because I don't see anyone working on Cocoon in any form),<br> it feels a little sad if there are individually maintained forks that could as well be part of the project.<br> <br> cheers,<br> Torsten<o:p></o:p></span></p> </div> </div> </div> </div> </div> </div> </blockquote> <br> </body> </html> --------------mIK08Hwask18DmCzeN8sIOcO--