[Fwd: [uportal-dev] uPortal3 Community Goals and Objectives: A common path forward...]
colin.clark at utoronto.ca
Thu Jul 5 21:00:01 UTC 2007
For those of you who aren't already on the uportal-dev list, I thought
you might be interested in an update on the plans for merging uPortal
2.x and 3.
This is great news for Fluid as is will vastly simplify how we integrate
our components with uPortal. I was in Denver for the meeting where this
was decided and expressed how impressed I was with the JA-SIG community
process. Nice work!
-------- Original Message --------
Subject: [uportal-dev] uPortal3 Community Goals and Objectives: A common
Date: Mon, 02 Jul 2007 20:03:50 -0400
From: William G. Thompson, Jr. <wgthom at rutgers.edu>
Reply-To: uportal-dev at lists.ja-sig.org
To: uportal-dev at lists.ja-sig.org
Those of you who where lucky enough to have attended the best JASIG
Conference to date are already well aware of the exciting events that
have unfolded this past week. For all the others, this is an open
invitation to join party and help continue to this great open source
experiment called uPortal.
Already heady from the EDUCAUSE Catalyst Award announcement, the
community crafted a common path forward toward the much anticipated
uPortal3 release. The ultimate goal is a uPortal3 GA release ready for
production deployment by Winter 2007 that meets the community goals for
a next generation Enterprise Portal Platform and leverages the best of
Discussions on the common path forward started at the the uPortal
Developer lunch on Monday, continued through the conference and
culminated at the BarCamp on Wednesday.
The common path forward provides a platform for evolution & innovation
based on a modern software architecture, thus achieving the original
goals of uPortal3, while leveraging as much as possible the production
tested, scalable, award winning, rock solid uPortal2 code base.
A draft of the Community Goals and Technical Deliverables for uPortal3
GA Winter 2007 is now available in the wiki at:
This draft represents my personal take on the community consensus at the
conference and needs to be discussed, vetted, modified, corrected, and
spell checked before it can become an actionable plan. :)
I took the liberty to seed the Project Team section of the doc with
examples for Eric, Elliot and myself. If you are interested in
collaborating on any of the technical deliverables please go ahead add
yourself to the list. Rutgers will be adding at least one developer,
maybe two, to the list shortly.
Even if you can't yet commit to any of the deliverables, please don't
hold back any comments, questions, suggestions, etc on the common path
William G. Thompson, Jr.
Associate Director - Architecture & Engineering
Enterprise Systems and Services, Rutgers University
voice: 732 445-5428 | fax: 732 445-5493 | wgthom at rutgers.edu
You are currently subscribed to uportal-dev at lists.ja-sig.org as:
colin.clark at utoronto.ca
To unsubscribe, change settings or access archives, see
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
More information about the fluid-work