Re: Is cocoon dead ?
Hi all, for anyone interested more in contributing for make things change rather than ranting about autopsy and post-mortem status, I'd strongly suggest to take a look at [1], if need subscribe to dev@ ML, and join the discussion there. Regards. [1] http://markmail.org/message/n3xt6yio6vikanuh -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Re: Is cocoon dead ?
Hi Robby others, I'm not judging the steps that have been taken. I'm just wondering why there was such a decline in active community. IMHO, moving to Maven, 2.2 and 3.0 make sense, but there's something missing that you need if you want to keep your userbase broad involved: decent documentation and an acceptable learning curve ! And remember, an autopsy has a function: learn from previous mistakes. Bart On Sun, Nov 11, 2012 at 9:40 PM, Robby Pelssers robby.pelss...@nxp.comwrote: Hi Bart, I'd say we've learned people are reluctant to change.. even developers. But to be honest.. it was C2.2 forcing me to learn maven and I've been using it ever since for all new projects. Same holds true for Spring actually. And where I could understand the drop back then, maven or Spring can hardly be considered to be valid reasons not to use newer versions of Cocoon. I think I can agree on two things: C2.1 and C2.2 are pretty complete in what they have to offer. They are also pretty well documented. But most advanced users have moved to C2.2 or C3 and can't offer good support for the older versions. I guess it's the developers own responsibility to (NOT?) upgrade on a regular basis and dealing with corresponding consequences of his choice. C3 is already used in production and in my opinion easier to use. The biggest problem is it's still coined alpha. We should really focus on getting c3 1.0 out which will give users a more confident feeling API's won't break that easily. Robby -Original Message- From: Bart Remmerie [mailto:remme...@gmail.com] Sent: Sunday, November 11, 2012 9:21 PM To: users@cocoon.apache.org Cc: users@cocoon.apache.org Subject: Re: Is cocoon dead ? Just being critical analytical: where die we observe the big drop in community activity ? Switch to Maven move from 2.1.11 to next version ? (just a guess) = What can we learn from this ? Bart Remmerie Op 11-nov.-2012 om 18:13 heeft Michael Müller michael.muel...@mueller-bruehl.de het volgende geschreven: Francesco, I observe this list for years now (since I started using Cocon 2.1). And I recongnized some activities, especially from you. But since a couple of years I'm using a) a different technology (JSF) for my web pages and b) I'm waiting for Cocoon 3.0 to become ready. Even there are some acitivies, it seems to be a never ending story. I guess it would be helpfull to schedule some dates for beta and release. If it is so much to do right now, maybe this version might be feature-reduced and some of the planned features will be postponed to a version 3.1? Otherwise I'm afraid this project is dead - even though there are some activities. If your horse is dead, don't try to ride it anymore. Change the horse. (similar to Dakota saying) Herzliche Grüße - Best Regards, Michael Müller Am 10.11.2012 14:00, schrieb Francesco Chicchiriccò: Hi all, I think e-mails like the one below are not helpful at all. First of all, even though most of critical aspects of our current situation are reported, some things are barely wrong: down the same page you find the next most recent news is a year and a half old Open your favorite browser at http://cocoon.apache.org/ and read that latest two news are dated July 2nd and March 3rd 2012 When people ask about C2.x (and the latest released version is 2.2) nobody wants to talk about it (except others desperate for information about some aspect of C2); Just browse http://cocoon.markmail.org and judge by yourself whether this is true or not. There are no books on anything later than 2.1, which is about a decade old. Just point again your favorite browser to http://www.apache.org/dist/cocoon/ and you will see that Cocoon 2.1.11 was released on Jan 14th 2008. Perhaps 80% of the official documentation is either TBW or skeletal, and the only people who know the inside of Cocoon well enough to complete it keep asking others to do that. This is absolutely false for C2.X and only partially true for C3. Beware, I am not stating that the Cocoon status is healthy, new releases with bugfixes and new features are regularly made available and documentation is accurate and complete. I am only trying to look at the Cocoon project for what it is *today*: a project with: * very few active committers * almost no occasional contributors * still a lot of interested people: most because they are running an ancient Cocoon version, few because they've heard of Cocoon only recently In my opinion, a dead project is a project in which no one is interested, and Cocoon is not (yet?) that far. Remembering that Cocoon - like as any other project at ASF - is exclusively made up by volunteer contribution, I'd rather start a [DISCUSS] thread to see what needs to be done and who is available to help instead of such acid and unproductive e-mails. WDYT? Regards. On
Re: Is cocoon dead ?
On Mon, Nov 12, 2012 at 10:28:39AM +0100, Francesco Chicchiriccò wrote: Hi all, for anyone interested more in contributing for make things change rather than ranting about autopsy and post-mortem status, I'd strongly suggest to take a look at [1], if need subscribe to dev@ ML, and join the discussion there. Regards. [1] http://markmail.org/message/n3xt6yio6vikanuh Thank you. I've read that thread and am encouraged. If I find something I can contribute, I surely will. I want Cocoon to prosper: I'm invested in a project that is heavily dependent on Cocoon. I've tried several times to find the place to start reading the code, and never found it. Maybe it's time to try again. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgp1gCVviM4dA.pgp Description: PGP signature
Encouraging more volunteers
I note that the link Getting Involved | How to Contribute leads to a page topped by this: How to contribute? Code TBD If someone could find a few minutes to fill this in, I think it would remove some friction. Further down that page: General documentation These instructions only work if you have an active account in our Daisy CMS and got the doc editor role assigned. If you haven't, create your account at http://cocoon.zones.apache.org/daisy/registration and ask at dev[_at_]cocoon.apache.org for editing rights. The link returns 404. Still further down, there is a link to Cocoon Site Overview. That link also returns 404. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgpAXVdAXQNnV.pgp Description: PGP signature
Re: XInclude in sitemap.xmap
I am doing two project.
A personal one with C3.0, and one for a product, and using C2.2.
This issue is happening with C3.0.
I didn't get a chance to test the files you sent me.
However, from the logs (which are really hard to read), it looks like
I am having issues with the baseUrl.
I looked into the source, and tried to set
baseUrl=full-path-to-my-repo, but that didn't work either.
Would be nice to see a document describing the attributes to be set on
each transformer.
A clear error message can be a lot of help as well.
Thank you.
On Mon, Nov 12, 2012 at 2:23 AM, Francesco Chicchiriccò
ilgro...@apache.org wrote:
On 12/11/2012 07:59, Mansour Al Akeel wrote:
Here's what I am doing:
map:match pattern=article/{id}
map:generate
src={global:base.repo.path}/articles/{map:id}/index.xml /
map:transform type=xinclude /
map:serialize type=xhtml /
and this is error:
[...]
Hi,
did you take a look at sample sitemap.xmap [1] (around line 387) and
specifically xinclude.xml [2]?
BTW: which version are you running? From the reported stacktrace I
understand C3, but some of your earlier questions were referring to C2.2
Regards.
[1]
https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sample/src/main/resources/COB-INF/sitemap.xmap
[2]
https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sample/src/main/resources/COB-INF/aggregation/xinclude.xml
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
Re: XInclude in sitemap.xmap
On 13/11/2012 05:49, Mansour Al Akeel wrote:
I am doing two project.
A personal one with C3.0, and one for a product, and using C2.2.
This issue is happening with C3.0.
I didn't get a chance to test the files you sent me.
Ok, take a look there, then: using the XInclude transformer should be
pretty straightforward.
However, from the logs (which are really hard to read), it looks like I am
having issues with the baseUrl.
I looked into the source, and tried to set baseUrl=full-path-to-my-repo,
but that didn't work either.
Again, please take a look at [1] and [2].
Would be nice to see a document describing the attributes to be set on each
transformer.
XInclude transformer hasn't changed much since C2.1 [3] / C2.2 [4].
A clear error message can be a lot of help as well.
Definitely: in your case, though, I suspect that something really
basic is getting wrong.
Please share your files if you'd like to get more in-depth help.
Regards.
On Mon, Nov 12, 2012 at 2:23 AM, Francesco Chicchiriccò
ilgro...@apache.org wrote:
On 12/11/2012 07:59, Mansour Al Akeel wrote:
Here's what I am doing:
map:match pattern=article/{id}
map:generate
src={global:base.repo.path}/articles/{map:id}/index.xml /
map:transform type=xinclude /
map:serialize type=xhtml /
and this is error:
[...]
Hi,
did you take a look at sample sitemap.xmap [1] (around line 387) and
specifically xinclude.xml [2]?
BTW: which version are you running? From the reported stacktrace I
understand C3, but some of your earlier questions were referring to C2.2
Regards.
[1]
https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sample/src/main/resources/COB-INF/sitemap.xmap
[2]
https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sample/src/main/resources/COB-INF/aggregation/xinclude.xml
[3] http://cocoon.apache.org/2.1/userdocs/xinclude-transformer.html
[4] http://cocoon.apache.org/2.2/core-modules/core/2.2/985_1_1.html
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
Re: Encouraging more volunteers
On 12/11/2012 19:49, Mark H. Wood wrote: I note that the link Getting Involved | How to Contribute You mean http://cocoon.apache.org/1273_1_1.html leads to a page topped by this: How to contribute? Code TBD If someone could find a few minutes to fill this in, I think it would remove some friction. Definitely: what if we grab http://openjpa.apache.org/get-involved.html from OpenJPA? It seems very nice to me. Further down that page: General documentation These instructions only work if you have an active account in our Daisy CMS and got the doc editor role assigned. If you haven't, create your account at http://cocoon.zones.apache.org/daisy/registration and ask at dev[_at_]cocoon.apache.org for editing rights. The link returns 404. Still further down, there is a link to Cocoon Site Overview. That link also returns 404. Daisy is not used anymore for managing the website(s), but some references are still around: thanks for reporting, I am going to remove such elements. We currently manage the website(s) via the maven site plugin (site sources are at [1] [2]): the major drawback is that you need to be committer to contribute documentation; the advantage is that you can always open an issue on JIRA [3] [4] and attach a patch :-) Anyway, I've opened [5] for fixing the stuff reported in this e-mail. Regards. [1] https://svn.apache.org/repos/asf/cocoon/trunk/site [2] https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/parent/src/site [3] https://issues.apache.org/jira/browse/COCOON [4] https://issues.apache.org/jira/browse/COCOON3 [5] https://issues.apache.org/jira/browse/COCOON-2329 -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
