>
> However, I think the public would loose out on a lot of good portlets
> people are willing to share. I think there should a standard
> repository, like commons-portlets, to house these contributions.
>
Hence the proposal to expose this concrete contribution as a Bugzilla RFE, for the moment. I don't think we are ready yet for opening a portlets module.
What is the purpose of http://jakarta.apache.org/jetspeed/site/catalog.html, then? That seems like the natural place to put access to user contributed portlets. I understand the official Jetspeed team can't take responsibility for the quality of the code in user contributed portlets. But, IMHO, the Apache/Jetspeed team should provide a catalog of contributed portlets, at least links to sites where other people host their own portlets.
There is people who cannot put the code in a public HTTP or FTP server, due to company policy or availabilty. Also, here there was a specific request "how do I i18n it?", which would benefit from interaction with other users (each could write their own language translation, for instance). So, while listing it in this page is good, it will not be always possible or the only alternative.
This is the reason (mostly the interaction for i18n) why I suggested the bugzilla enhancement as a good "repository. Also that, while we are not ready for opening a portlets module yet, a discussion portlet seems a good candidate for a "core", "optional" or even "demo" general purpose portlet.
Regards,
Santiago- Jasen.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
