Do you plan to put some public archive of the old threads of your Jetspeed2 mailing list in order to understand what was already discussed.
No, that was discussed under NDA
Even for those that are also JCP member and are under the same NDA at least from the Community Review in May?
Now that the JSR168 is public, this may help Jetspeed becomes more transparent... It looks like that there are today the ones that know and that speak in private and the others that are trying to guess what is happening (even if they are also JCP member and were under the same NDA before today)... Not very cool for an open source project :-((
Well from my perspective you are being unfair.
We could not discuss the details of the Portlet API up until recently.
I am a member of the Portlet API representing Apache.
I do not represent a company, Im not paid to participate, yet I try to represent the best interests of the Jetspeed community.
The expert group could not allow me to share the details of JSR 168 with my team on our public list.
So I proposed to the group that I would share the information with the Jetspeed developers, much like they share information with their corporate developers.
This was agreed upon, and the jetspeed2 mailing list was created.
The other choice would have been to do nothing at all, and wait until public release for making any discussions.
I don't like the closed nature of it, but this is the way that the JCP currently works.
If you don't like it, I suggest you get involved in the Java standards process and work towards changing it.
Keep cool. This was nothing against you and I'm convinced you did an excellent job and the best as you could in this heavy political mess that the JCP is. Moreover it seems to me that the transparency issue of the JCP was already discussed in JavaOne, on TheServerSide or even in the Apache Committees. So this is perhaps something that will change in the future (OASIS with the WSRP was a bit more open as all the archives of the mailing list, spec drafts,... were public during the process and I hope it will be the case for the JCP soon).
I just wanted to aks why your J2 mailing list was not open to ALL JCP members starting from the Community draft in May. Becoming a JCP member is free for individuals and this may have help gather the community around J2 faster. Looks like all the large IT vendors did not wait for the final release to already implement 99% of the API, write articles,...
On the other side, I'm sure lots of the current Jetspeed readers (especially us ;-) ) are waiting to know a bit more about the architecture, plans, vision,... of Pluto/J2 before taking some implementation decision. As we all have our internal deadlines and milestones, opacity during this JSR (and all the successive delays) was (is) clearly not a good thing. One of the reason to choose open source libraries is the fact that you can access at any time to the source code and are free if necessary to help and push the product ahead (or fork the code if the vision is not the same). Here, the effect of the JCP looks like exactly the opposite. Lots of the possible committers were then just taking a wait and see attitude (including us ;-) ). Quite a shame for the Jetspeed project (but I agree that it is clearly not your fault, don't take it personal)!
Cheers
St�phane
- -- --- -----=[ scroisier2 at jahia dot com ]=---- --- -- - www.jahia.org : A Collaborative Source CMS and Portal Server
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] +01 707 773-4646
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
