I agree. My efforts to get my hands around jetspeed haven't been successful
(0/2) and a 1.0 release needs docs if it's to actually be used by anyone.
I've been using the slashcode.com code thus far which is perl/apache/mysql
based but would like to ultimately move to a java based solution as the
product database system I'm using uses this architecture. It'll be bad
enough for my successor to have to deal with my java code and more so if
it's intertwined with slash's perl code on apache/linux.
Please, just spend a week on the docs and I can virtually guarantee you'll
have *ALOT* more support from users interested in helping to extend the
technology.
I know it ain't cool for someone who isn't contributing to complain but the
reality is if the barrier to entry re: installation and configuration is too
high most will pass. :-\
That being said, thanks for the wonderful work you've been doing thus far
and I'll be keeping my ear to the ground for developments!
Will
----- Original Message -----
From: "mark abram" <[EMAIL PROTECTED]>
To: "JetSpeed" <[EMAIL PROTECTED]>
Sent: Sunday, March 05, 2000 5:59 PM
Subject: Re: Jetspeed 1.0... "Release early, release often" ???
> Kevin,
>
> My suggestion would be to spend a fare amount of time on detail
> documentation
> for users and developers. I was trying to get as much info on JetSpeed as
> possible
> and beleive me there is not much. However, if you can get good
documentation
> how
> you started, framework and principles then more developers will help. The
> idea would be
> to provide developers at large with some sort of schema/template for
> designing and coding new
> portlets for JetSpeed. There is a huge need for JetSpeed.
>
> regards,
> ma
>
> "Kevin A. Burton" wrote:
>
> > So it has been bothering me for a while that Jetspeed is not 1.0. I
> > really think that I have overshot a little with my requirements.
> >
> > The only things that are necessary for Jetspeed 1.0 are to improve user
> > preferences. Specifically the ability for someone to logon and then
> > pick from a set of Portlets that they want to run.
> >
> > However, I think that Jetspeed is ready. The portlet API IMO is done.
> > We just need to find bugs...
> >
> > So what I am thinking about is to stop development on this version..
> > clean and test a couple of things. and then release.
> >
> > This would have the following benefits:
> >
> > - establish Jetspeed as a now solid product
> > - bring in people that might be interested in building a Portal with
> > Jetspeed and if they find that they want to hop on anythign in TODO then
> > great. Personally for what I want to do now with it I don't need
> > per-user subscription (but it would be cool)
> >
> > Thoughts? I am probably going to clean up everything and start to hack
> > on docs tomorrow.
> >
> > It would be cool to get this out before ApacheCon but I don't want to
> > push it and introduce bugs. This really doesn't have anything to do
> > with it but I just thought of this tonight.
> >
> > It would also be cool to get artwork in before 1.0 but we can wait.
> >
> > Kevin.
> >
> > --
> > Kevin A Burton ([EMAIL PROTECTED])
> > http://relativity.yi.org
> > Message to SUN: "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]
>
>
>
> --
> --------------------------------------------------------------
> 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]
>
--
--------------------------------------------------------------
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]
