Jen,

Excellent!

I've updated the portlet's wiki page <http://www.ja-sig.org/wiki/x/f4x7> 
to include a link to the source code and your install tips.

I've also updated the UW Feedback Portlet wiki page 
<http://www.ja-sig.org/wiki/x/Ly8> to reflect its retirement to an SVN 
branch.

Andrew

Jen Bourey wrote:
> OK, I've checked in the new feedback portlet.  To deploy it, download 
> it from https://www.ja-sig.org/svn/portlets/FeedbackPortlet/trunk.  
> Run a "mvn install" in the root directory, then use the "ant 
> deployPortletApp" task to deploy the resulting war.  The portlets 
> should work in either 2.6 or 3.
>
> If you're looking for the old feedback portlet, I've archived it in 
> the branches.
>
> - Jen
>
>
> On Jan 30, 2008 5:13 PM, Eric Dalquist <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>     No, the old version was only a one time code dump of a portlet
>     authored
>     here at UW and we would probably look at using the new version
>     anyways.
>
>     +1 for this approach from me.
>
>     -Eric
>
>     Drew Wills wrote:
>     > Jen,
>     >
>     > I'm all for replacing the old with the new unless some new
>     compelling
>     > evidence in favor of keeping the old comes to light.
>     >
>     > Questions (basically restatements of yours):
>     >   - Have there been any recent updates to the old version?
>     >   - Is anyone currently using the old version?  If so, is there any
>     > feature gap?
>     >
>     > If no one speaks up on behalf of the existing Feedback portlet, I'd
>     > think you're free to replace it.
>     >
>     > drew
>     >
>     >
>     > Jen Bourey wrote:
>     >> I'd like to go ahead and get this in the ja-sig repository, but I
>     >> want to minimize confusion with the other feedback portlet.  Are
>     >> there critical features present in the other portlet that aren't in
>     >> the unconference version?  Do we want to have two versions?  A
>     >> suggestion was put forward in IRC chat to replace the trunk of the
>     >> current FeedbackPortlet with the unconference version, but I wanted
>     >> to see if anyone is currently relying on the trunk.
>     >>
>     >> What would other people like to do?  Should we combine the
>     projects,
>     >> or keep two versions?  If we combine them, would people like
>     the new
>     >> version to go into the trunk, or into a branch until more
>     people have
>     >> looked at it?
>     >>
>     >> - Jen
>     >>
>     >>
>     >> On Jan 23, 2008 10:29 AM, Jen Bourey <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>
>     >> <mailto:[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>>> wrote:
>     >>
>     >>     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 use! ful.
>     >>
>     >>     - Jen
>     >>
>     >>
>     >>
>     >>
>     >>     On Jan 22, 2008 11:46 AM, Drew Wills <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>
>     >>     <mailto:[EMAIL PROTECTED] <mailto:[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] <mailto:[email protected]>
>     >>         <mailto:[email protected]
>     <mailto:[email protected]>> as:
>     >>         [EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>
>     <mailto:[EMAIL PROTECTED] <mailto:[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]
>     <mailto:[email protected]> as:
>     >> [EMAIL PROTECTED] <mailto:[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


-- 
Join your friends and colleagues at JA-SIG 2008 - "Higher Education Solutions: 
The Community Source Way!"
April 27th - 30th, 2008 in St. Paul, Minnesota USA

Featuring CAS, DSpace, Fedora, Fluid, Internet2, Kuali, Sakai, uPortal, and 
more!
Information/Registration at: 
http://www.ja-sig.org/conferences/08spring/index.html

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