Dear community,
With finally the release for Jetspeed-2.1.2 behind us, the time has come to
think of and start some large scale enhancements and changes.
Some of the biggest improvements and features on my wish list, and for which I
already know others have interest in too, are:
- moving from our maven-1 and maven-2 hybrid build environment to *one*, clean
maven-2 build environment
- align with the latest Pluto 1.1.x container (and possibly even the near 1.2.x
version)
- start working on full JSR-286 Portlet API 2.0 support (which requires
aligning with at least the Pluto 1.2.x version)
- review and redesign our portal security model and implementation
- multiple authentication/authorization schemas to support truly separated access &
maintenance of "communities" in one portal
- review and redesign our portlet preferences model and implementation (Java
preferences)
- design and implement a new decorator model and api to allow much easier and
cleaner definition of layout and portlet decorations
- possibly a JCR based portal registry and page/site management
- better support for and possible even out-of-the-box integration with
Geronimo/Glassfish/Jetty/JBoss/Websphere/WebLogic
- Jetspeed "light" (no need for database persistence and much simplified
page/site management)
I invite everyone to comment, vote, and propose other critical features you are
"dying" for *and* are willing to invest time and energy in bringing it about.
Note: none of this "list" is fixed or definitive, its just my (and some others)
initial feature list.
But also note: in line with our Apache development model, *only* those features people are really willing and able to invest time and energy in (discussing,
designing, coding, reviewing, testing, commenting, etc.) can and will be realized.
Some of the above possible features are going to effect our current API,
component model and our build setup.
To protect our current users, I've created a new branch JETSPEED-2.1.3, for
continued support and bug fixing based on the 2.1.2 release.
This allow us to start working in the trunk with possibly some hefty changes,
refactoring etc. needed for changes like I described above.
And in anticipation of our probable move to a maven-2 build environment, I
bumped the trunk development version to 2.2-SNAPSHOT.
For us committers, this has a major consequence: *any* change committed to the JETSPEED-2.1.3 branch or trunk needs to be reviewed if it is valid and/or
required for inclusion in the other svn tree (trunk or branch) as well. If so, it needs to be committed twice, possibly even refactored for that purpose!
Now, as far as I'm concerned, we should not introduce new features or big
enhancements in the JETSPEED-2.1.3 branch anymore but reserve those for trunk
only.
If large scale development would commence in the branch, we will endanger the
2.2-SNAPSHOT trunk development big time.
To be able to reach a new Jetspeed 2.2 release ASAP, trunk development needs to
be our first and highest priority.
Apache is all about community based development, and I'm inviting all of you to actively participate and help us out with questions, proposals, patches, test
reports or any other contribution as much as you can.
Let's all work together to make Jetspeed 2.2 the best Open Source Enterprise
Portal so far.
Regards,
Ate
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
