On Mon, Nov 20, 2023 at 3:35 AM Christofer Dutz <christofer.d...@c-ware.de> wrote:
> Hi Gabriel, > > > > I was more referring to the first response and I have seen loads of > similar responses when initiating Attic discussions in the past with other > projects. I just wanted to make it clear, that a projects livelihood is > defined by the people giving and not the people wanting ;-) > > > > Becoming a contributor is easy. Perhaps it would make sense for us to > formally switch to Git, because then it would be a lot simpler: > > - Create a fork > - Do your changes in that fork > - Create a PR > - Have someone merge these changes > - Hopefully get voted in as committer soon > > Perhaps switching to Git would be a good first step. > > > +1 for switching to Git Peter Hunsberger > Chris > > > > > > *Von: *Gabriel Gruber <gabriel.gru...@workflow.at> > *Datum: *Montag, 20. November 2023 um 10:26 > *An: *dev@cocoon.apache.org <dev@cocoon.apache.org> > *Betreff: *Re: Now that the release is out, what's next? > > Hello Christopher, > > just to make it clear. I AM willing to participate and contribute. I was > the pushing force on the Spring 4 dependency upgrade. And meanwhile our > cocoon 2 instance runs on spring 5 and java 11 – so I have some stuff, > which I would love to get into the OS project again. > > As I said I would like to contribute further to make cocoon 2 compatible > with state-of-the-art dependencies like java 21 and spring 6. > > However I need some help to become a formal contributor. Maybee you could > help me in that? > > Thank you > > Gabriel > > > > > > *From: *Christofer Dutz <christofer.d...@c-ware.de> > *Date: *Monday, 20. November 2023 at 10:08 > *To: *dev@cocoon.apache.org <dev@cocoon.apache.org> > *Subject: *AW: Now that the release is out, what's next? > > Hi all, > > > > let me mention one thing here … Open-Source is not a need-driven thing, > that anyone is entitled to exist to solve one owns needs. It’s an > initiative-driven thing that anyone can participate. > > > > So, if you need some open-source solution, you should consider actively > contributing. Because if nobody contributes, then the open-source project > will die and move into the attic. > > > > An alternative for this is that people and companies can pay someone else > to participate in their place. > > > > But in the end, if nobody works on it, it’s going to go into the attic. > > > > I hope with my general overhaul of the build and project structure, I have > made contributing and releasing a lot simpler, but I’m not planning on > keeping the lights on, if I’m the only one working. > > > > Chris > > > > > > > > *Von: *Gabriel Gruber <gabriel.gru...@workflow.at> > *Datum: *Sonntag, 19. November 2023 um 19:55 > *An: *dev@cocoon.apache.org <dev@cocoon.apache.org> > *Betreff: *Re: Now that the release is out, what's next? > > Hi cocoon team, > > > > as we are still using cocoon 2.2 in PROD as base for our product, we have > a high interest that the open source project stays alive. Our main > motivation here would be framework and java compatibility as well as > security patches. > > > > Of course I am also willing to actively support and maintain. A great > improvement would be, if the source-code could move to github. > > > > Thanks Chris for your enormous efforts to get this release through! Thanks > to all the committers for building such a great and long lasting project. > > > > Gabriel > > > > *From: *insigh...@gmail.com <insigh...@gmail.com> > *Date: *Sunday, 19. November 2023 at 19:36 > *To: *dev@cocoon.apache.org <dev@cocoon.apache.org> > *Subject: *Re: Now that the release is out, what's next? > > I mentioned this early, the DSpace Content Management project used Cocoon > 2.2 until version 6.4 (v7 moved to Angular JS). They integrated with Solr > and did a bunch of other things that may be worth a look. > > The Cocoon interface was called xmlui (look for the subfolder), and > available via Github: > > https://github.com/DSpace/DSpace/releases > > Source Code: > https://github.com/DSpace/DSpace/archive/refs/tags/dspace-6.4.tar.gz > > Great work on continuing the Cocoon legacy! > > Dan > > > > On 2023-11-19 10:20 a.m., Christofer Dutz wrote: > > Hi folks, > > > > So, it seems that we finally have finished the last missing steps to > formally get the release out the door. Now I think comes a time where we > should reflect and discuss, what should happen with the Project. > > > > So instead of simply saying: Releasing it was such a struggle (not > technically, but from a participation side) I wouldn’t say this project is > healthy and we should discuss a move into the Attic. > > > > However, I could also imagine that the changes I implemented in the build > might encourage some folks to give it another go. > > > > I know when I was doing projects with Cocoon as part of my day-job 20 > years ago, Cocoon 2.2 sort of completely broke my flow. Not only my > inexperience with Maven, but also that of Spring and the versioning scheme > where all sorts of cocoon modules had different versions just made me give > up at that time and switch to Adobe Flex ;-) > > > > Now (15 years later) Maven and Spring have evolved and with the cleanups > in the build, it should be a lot simpler to work with Cocoon and with all > modules sharing the same version, also this should be a lot simpler. > > > > So, I would like to ask you folks: > > - Should we aim directly for the Attic? > - Does anyone want to revive the project? (I’m intentionally not only > addressing committers and PMC members, but also people wanting to keep the > project alive) > > > > > > Chris > >
