Hello all: I think we have enough resources by now to make some improvement to the docs. Personally, I truly appreciate this, and I think it's motivating to see users willing to help and improve the documentation.
How about we get something rolling here ? After reading this thread, and reviewing the documentation available on the site, I would say there is enough documentation, and some of them are in depth. I agree with Ron Wheeler, that documentation requires reading between lines. Which is something we don't do often, especially those of us who like google. We like to search by key word and get to the topic we are looking for. This suggests the need for searching functionality, which we don't have now. So let's work with what we have. There's is always room for improvement, and here is where the wiki comes in. Users who kindly offered to contribute and help in the documentation, can start by visiting the wiki and then going to http://wiki.apache.org/portals/Jetspeed2 Using the drop down menu and choosing "Show Local Site Map" we can get a nice view for the available topics to browse and pick from. If You think there is something missing from the main site, and from the wiki, then feel free to add a page. If the page is there, but what you wanted, was not covered, or you noticed the explanation was not deep, then you can add to it. This will help us maintain the docs in one searchable location. If a page is very well written, and very helpful, the jetspeed team may move that page to the main site documentation, and of course preserving the credits for the author(s). How is that ? Any comments, ideas ? If you don't have a topic to write about or enough skills to start, but you want to help and learn as you go, then PERSISTENCE "AND" WRITING DOCUMENTATION is a great way to start. I do have some topics for a newbie to write about, and I will help as much as I can in that. Email me to discuss this. Again, contribution is very welcome and needed and appreciated 8) On Mon May 04,2009 04:05 pm, Brad Gardner wrote: > I'd be interested in joining in to help with documentation. As you said, > its been a bit of an issue for a while from what I can tell. I've been > spending my time getting up to speed on the development side of it, but > documentation would be a good place to get familiar and involved with the > project as well. > > *Brad Gardner* > Mailto: bgardne...@gmail.com > > > > On Mon, May 4, 2009 at 9:33 AM, Ron Wheeler > <rwhee...@artifact-software.com>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 > > > > imoleswo...@gmail.com 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 imoleswo...@gmail.com at > >> openSubscriber.com > >> > >> http://www.opensubscriber.com/messages/jetspeed-user@portals.apache.org/topic.html > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org > >> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org > >> > >> > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org > > For additional commands, e-mail: jetspeed-user-h...@portals.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
