« Back in Europe | Main | ApacheCon Sessions Finished »
December 10, 2005
Cocoon reloaded continued
Ok, I'm honest: I'm really happy that I'm currently on vacation and don't have time/connection to participate in the ongoing discussions on the cocoon dev list. I just looked into my mail box and decided to simply skip all those threads there.
The only mail I read was the last one from Stefano and I think he's mostly right (ok, I only read the last paragraphs of that one...so don't know if he's right at the beginning). Now, we're discussing "real blocks" for more than three yours now and we're still not there. A lot of work has been done recently and the goal seems near. In addition, we have very good plans for improved build and deployment handling, which is currently a nightmare. So, I really think we should finish this first before putting to much energy in an unknown future. I'm really wondering how a "new" Cocoon should be done. We were not able to attract developers to help with implementing blocks or the maven stuff. Most of this is done by one or two people. Why should this be different for starting a new version? I think the danger of a one-man show is very high.
Unfortunately, this is also true for the great portal engine. Apart from Ralph and myself, no new developers joint in. There might be several reasons for this; one is definitly the lack of documentation which I hopefully start in the next weeks. On the other hand, many companies are already using the Cocoon portal or plan to use it - and there are several really big ones in the play. So I think there is definitly a misbalance here between users and developers. And if this will not change in the near future than I'm really wondering what will happen with the portal part.
Ah, and I'm happy to meet some more of the Jetspeed guys at the ApacheCon. The first 2.0 release of Jetspeed will happen soon and I'm really interested in what they have to offer.
Posted by cziegeler at December 10, 2005 02:07 AM