So it is starting to come to my attention that there are certain hot
spots that are within Jetspeed and aren't documented.
- Adding users to Turbine (as well as general Turbine administration)
- Authenticating users
- What the individual packages do
- UML
- Manipulating the site with skins.
- Where does the database/XML come into play.
- Management of the Persistent Document cache
- Management of OCS feeds
First off it is important to realize that Jetspeed is a work in
progress. The above are examples of areas within Jetspeed that will
change in the future. There is very little documentation within the
above regions. Why? Because these are going to change and it makes no
sense to work out documentation now.
Just a break down of what needs to change before a major documentation
effort should be done:
- Adding users to Turbine (as well as general Turbine administration)
- We need to work on a shared Turbine/Jetspeed admin console. I have
a proposal drawn up I just haven't submitted it yet.
- Authenticating users
- This area is one that needs work. We need to have an admin console
(see above) and documentation on how to snap other
authentication mechanisms in. Also user preferences haven't been
integrated into Jetspeed yet and I would like to see this happen soon.
- What the individual packages do
- I plan on improving this in 1.2. Per package docs need to be done.
- UML
- Time is a factor. I am going to do a proposal for a smarter
"remote content" engine and will do UML on this version.
- Manipulating the site with skins.
- Again user specific. Also the PSML implementation should fix some
of this.
- Where does the database/XML come into play.
- This is still up in the air. There are a lot of technologies here
that are competing :(. Ozone, Turbine, Castor, Quick, JXML, etc.
- Management of the Persistent Document cache
- Now the the Turbine scheduler is done this can be implemented to
start when Jetspeed starts. It won't be a remote JVM process any more.
Also there will be an admin console soon. (anyone want to write one?)
- Management of OCS feeds
- Turbine scheduler also. In 1.1 this was improved but 1.2 should go
a step further by pulling down the documents as they are found and pre
caching them.
So I hope this helps to make sense of things. IMO software needs to be
evolutionary. Massive feature creep is one of the major evolutionary
steps.
Kevin
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
