> a jasig-portlets meta-project

+1.

I encourage creation of jasig-portlets-dev@ for facilitating community, comradery, and collaboration among the portlet developers in JA-SIG.  It might immediately fill a niche of those common portlet development questions (how do I share information between a portlet and a servlet, how do I offer file upload and download, how do I get one of these dreaded Maven 2 build thingies to work, ...)  The JA-SIG community context seems enough to me to make this forum worth creating despite their being more general (Yahoo Portlets dev list, e.g.) places to discuss these issues, beyond the bounds of our higher-education open source developer community.

I echo Jason's hopes for more ambitious uses for such a list, including coordinated releases of bundles of portlets (or, as incremental progress, GA versioned releases of even individual portlets).

This relates to prior discussions of recruiting someone to coordinate the "projectifying" higher education portlet initiatives into living breathing open source projects incubated and thriving under JA-SIG.


However, I don't regard a generic jasig portlets email list as a sufficient substitute for project-specific lists. 

> portlet-specific infrastructure makes the possibility of our really cool "XXX" portlet

+1

Having an email list specific to the Bookmarks Portlet, e.g., is part of the "trappings of projectness" that make it feel like a real project. Just the other day I cited this portlet's email lists as part of what makes it a real project.

Tightly scoped lists also make the email easier to manage.  Yes, the bookmarks email list is very low traffic.  But every message on that list is about this portlet, not some other technically totally unrelated portlet.  I think it's best for every portlet to have its own developer and adopter lists.

Andrew


Jason Shao wrote:
On Jan 21, 2008, at 11:56 AM, Eric Dalquist wrote:

One idea is perhaps a jasig-portlets-user and jasig-portlet-dev list to consolidate a bit as we don't have much portlet related email traffic on any list as of yet.? 

I suspect that portlet-specific infrastructure makes the possibility of our really cool "XXX" portlet also looking open to deployers on non-uPortal platforms, wheras jasig-portlets feels like it's a JA-SIG specific portlet bundle.

In actuality if we have a bunch of portlets, a jasig-portlets meta-project, which perhaps did a coordinated bundled release (a la Eclipse's callisto, europa releases) and perhaps worked with the uP steering committee to identify portlets to include with a uPortal distributions (uPortal Complete?) seems like it might be particularly worthwhile.

Jason

--

Jason Shao
Application Developer
Rutgers University, Office of Instructional & Research Technology
v. 732-445-8726 | f. 732-445-5539 | [EMAIL PROTECTED] | http://jay.shao.org



-- 
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev



Reply via email to