I happen to agree with all of this talk re: documentation. What about starting a Wiki? The Apache project has one set up. How do we get a sub-wiki on there?
This way, those of us who are interested in this (passionately) can work together. Jason -----Original Message----- From: Stefan Rennick Egglestone [mailto:[EMAIL PROTECTED] Sent: Friday, April 30, 2004 5:21 AM To: Jetspeed Users List Subject: Re: Documentation Coming from the perspective of someone who's just starting out with Jetspeed, I'm quite happy to contribute ideas about what would make learning Jetspeed easier for myself as I find my way through. As a start, if it's useful to anyone, I can spend a few weeks learning and then write something up and post it to the mailing list? Stef Visvanath, Sridhar (Cognizant) wrote: >Stefan, What you say makes sense. >But, What I understand from Alberto is this : >All he needs is a Architecture diagram as to how jetspeed interfaces with other such engines like turbine, torque etc., >He is ready to put in his effort. All he requires is architecture diagram from folks who are already knowledgable. Obviously a newbie cannot come up with this when so much effort has already happened. > >Alberto, I guess maybe you can ask the developer mailing list to give u an architecture diagram on jetspeed. And then we can work through making a document. > >Thanks & Regards >Sridhar Visvanath >******************************************************************* >If you do not stand for something, you'll fall for everything >******************************************************************* > > > >-----Original Message----- >From: Stefan Rennick Egglestone [mailto:[EMAIL PROTECTED] >Sent: Friday, April 30, 2004 2:33 PM >To: Jetspeed Users List >Subject: Re: Documentation > > >I've got to say, you're pushing this a bit hard. There are plenty of >example portlets in Jetspeed. Read the tutorial, work out what you need >to know, look for example portlets that do it, look at their code to see >how they work. If you want to know about turbine, veloctiy etc read >their project pages. There's probably as much information out there as >in a manual, but it's a bit distributed. Use your brain and work through it. > >And if you have success, start writing a manual, contribute it and maybe >other people will add bits too. I'm a newbi who's slowly learning my way >through Jetspeed, and I certainly would. > >Not meaning to be rude or anything, but you've got as much time as >anyone else who's worked on the project. > >Stef :-) > >Alberto Rodriguez Galdo wrote: > > > >>Absolutely rigth. >> >>Some kind of documentation is a must in this kind of products, not >>only how-to-program-portlets guides but an entire architecture and >>philosophy description. >> >>Just for the mortal of us to understand wich is the role of Turbine, >>Velocity, Castor, fulcrum, ecs and village (for instance) in Jetspeed. >> >>Please be kind and put some effort in writing such a manual, i would >>help in any manner you like (first i need to understand jetspeed myself). >> >>greets >> >> >> >>At 17.47 28/4/04 +0200, you wrote: >> >> >> >>>Hi >>> >>>Is there any book covering programming and deploying JetSpeed? >>> >>>I need it very much now. It is urgent >>> >>>thank in advance >>> >>>David Cornide >>> >>> >>>--------------------------------------------------------------------- >>>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] >> >> >> > > > >This message has been scanned but we cannot guarantee that it and any >attachments are free from viruses or other damaging content: you are >advised to perform your own checks. Email communications with the >University of Nottingham may be monitored as permitted by UK legislation. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > >----------------------------------------------------------------------- - > >This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. >If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. >Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly >prohibited and may be unlawful. > > Visit us at http://www.cognizant.com > > > >----------------------------------------------------------------------- - > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. --------------------------------------------------------------------- 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]
