Jonathan Porterfield wrote:
> Does anyone know of any large corporate entities that are proceeding with
> Jetspeed implementations? I think I saw some reference to an IBM project
> including integration with Notes.(??)
>
> I am in charge of development of extranets for a large corporation. I am
> intrigued by the functionality that is emerging within Jetspeed, and am
> equally disappointed by the vapor-ware currently available from iPlanet,
> Oracle and others.
>
I am aware of some projects using Jetspeed for building portals, but since I'm
sure they are "public", I'll let their respective owners speak about them
themselves if they want to.
I *do* work for a large corporation though...
However, note that the current Jetspeed distribution is aimed mainly for
workgroup portals. Building a large corporation portal with Jetspeed would
require some large customization (mainly using a SQL or LDAP backend for
property storage instead of flat files backends).
I know several people are working on such backend implementations but I've
not seen yet anything contributed back.
> However for a company with lots of cash to blow on such things, name brands
> tend to get things sold internally. It's the old "Noone gets fired for
> buying IBM..." scenario. Basically, I am looking for references to include
> in a project proposal and tool-selection justification.
>
> In addition, is there a roadmap for stabilization of the application for an
> initial release? I'm looking for milestones where requirements are frozen
> (no more scope-creep), etc ...
>
The main advantage you have in using Jetspeed is that you have control on
your engine: you can fix bugs, add functionalities and incorporate them back
into the main source so that they'll become standard features maintained and
evolved by the community, or simply develop internal features that you can
keep and maintain yourself.
If you IT department has any level of technical expertise, this is a very good
way to leverage the investment made in skilled engineers over investment made in
products, because your engineers (once they have acquired the knowledge of the
workings of Jetspeed) will be able to deliver solutions more quickly and better
suited to the need of your company than it's possible with an off the shelf
product.
If you don't have the technical expertise within your department I'd advise you
to contract an integrator to deliver and maintain a portal solution for your
needs. This integrator will use whatever package he thinks will fullfill your
need at the best price.
Using Jetspeed as an off the shelf product within a corporation without
great java/IT skills is a goal of project, but we're not quite there yet.
About the evolution of the project, there's no definite milestone plan except
in very broad terms:
Missing features for 1.3a2:
- profile customization
- portlet unique id within PSML
- interface based PSML Java API
Missing features for 1.3a3/b1:
- integration of new Portlet API
- implementation of SQL/LDAP backends for Registry/PSML
- upgraded syndication engine
From b1 on to release:
- portlet development
- bug fixes
- performance work
- documentation
--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
