Hi all,
As a "dummy" developer in all this java portal world (I am an abap/c#
developer) but really willing to get into it, I could contribute
testing/following the howtos in the documentation, giving the point of
view of someone how is learning, etc.
So, if the list of docs/tasks exists, I could also have a look.
regards,
David.
On May 4, 2009, at 8:11 PM, Mansour Al Akeel wrote:
Ron:
I agree with you, ad I think it's great time to start fixing the docs
for 2.2. Depending on my availability, I will be will to help. If you
know or if you have compiled a list of what topics/order I need to
follow to improve the docs, this will help me a lot.
On Mon May 04,2009 09:33 am, Ron Wheeler wrote:
This has been a chronic problem and there is an interest in the user
community to work with David and the Hippo team to try to fix this.
There is a lot of documentation but it is really written for the
developers
and requires way too much reading between the lines.
I have tried in the past to describe a set of documentation that my
guys
could have used to get started.
Is there anyone else who would like to work on documentation? With
version
2.2 about to be released, it is not a bad time to take a run at the
documentation.
Ron
[email protected] wrote:
Totally frustrated!
Using Jetspeed2 ( Or at least trying to ) the documentation is
extremely
poor for the uninitiated and there seems to be a dearth of any
hardcopy
support.
Just getting installed and running on Ubuntu was enough to grey
the little
hair I have left! Now that we have overcome that obstacle I cannot
connect
to my Mysql database because the app is not aware of my mysql
connector
file and there is no documentation to tell me how to tell the app
to use
a certain connector.
Sure there is a little insert on updating the build.properties
file but I
am not even close to the stage of doing builds, just trying to use
the
demo apps to get the blasted thing going.
Its not surprising that big business runs a mile when faced with
open
source stuff. The learning curve is simply made too expensive by
poor low
level documentation. No description of the tree structure, poor
prerequisites requirements, interdependencies and too much to
mention.
--
This message was sent on behalf of [email protected] at
openSubscriber.com
http://www.opensubscriber.com/messages/[email protected]/topic.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: jetspeed-user-
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]