Great! Once I get it posted maybe we can determine whether there are any other features that should be added.
I also really like the idea of having a consolidated email list. I worry that needing to create a separate JIRA instance, email list, svn location, etc. will be too much overhead for new projects and might prevent people from sharing their work. I also worry that separating out all the lists will prevent people from hearing information that they might be interested in. I know I'd prefer to just join one portlet email list and hear about all updates, rather than needing to join a new list every time a portlet I'm interested in is created. Especially since many portlet projects might be fairly small, it seems to make sense not to create too much administrative infrastructure around them. As we add portlets to the uPortal distribution or create a portlets package, having a consolidated email list may become even more useful. - Jen On Jan 22, 2008 11:46 AM, Drew Wills <[EMAIL PROTECTED]> wrote: > Great work Jen! I'll be talking to the schools I work with suggesting > they put it in their portals. > > Jason Shao 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. > > +1 from me for consolidated email lists (Eric's version) -- also for > consolidated JIRA & Confluence space, etc. At least, I suggest that > small, general-purpose JA-SIG portlets -- harmless ones that most > schools should at least consider deploying -- can share an > infrastructure. Anything big or specific, like SIS integrations or > perhaps a suite of personal data tools that work together, probably can > and should be separate. > > Insisting that every portlet must have its own version of these > resources seems like a big barrier to entry for a little portlet. I'm > afraid it will influence folks to hold on to things they might have > contributed. > > And if you create a new email list for each portlet, who will sign up? > I suspect each individual portlet won't generate much traffic -- keeping > them together means that anyone who subscribes will get some good info > about new portlets or cool new features in existing ones. > > drew wills > > -- > Andrew Wills > UNICON, Inc. > Office: (480) 558-2476 > http://code.google.com/p/cernunnos/ > > -- > 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 > -- 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
