Really what ever is appropriate is fine. As long as you know in advance
that I will be posting these questions through the process. I think the
best place to start is where you feel documentation is needed most right
now. I also think that the easier it is for first timers to understand
Struts and how it works, the more likely you will have committed users and
thus more feedback and thus better development. I also think we you all
need to package a war file in which System.outs can be generated in a clear
way to demonstrate the steps Struts goes through from request to response.
That helps users understand visually as well as with the documentation. I
know you have debug level output but they dont go method to method for EACH
AND EVERY METHOD. Obviously this is not the war file to be developing with,
but would be excellent to study Struts.
Aside from that I think that Documentation can be done on a piece by
piece basis.
What do you think?
----- Original Message -----
From: "Ted Husted" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, June 16, 2001 11:40 AM
Subject: Re: I would like to offer myself to help with documentation
> Personally, I don't think that your questions would "clutter up" the
> list. If you don't understand it, then it's (very) likely that many
> others do not either. Moreover, the developer's list is intended for
> discussions about developing and packaging struts, and it * is * the
> appropriate place to post questions about drafting documentation.
>
> Are you talking about refactoring the current Users Guide, adding
> additional chapters, like maybe a tutorial, or starting with a clean
> slate?
>
> Any known documentation issues should be logged in bugzilla, which would
> include enhancement requests.
>
> < http://nagoya.apache.org/bugzilla/ >
>
> I've been working on some additional material, like Strut by Strut and
> the kickstart FAQ (see husted.com/about/struts). The first part of the
> FAQ is really done, and I put in under the Jakarta FAQ-o-Matic (but I
> see that it's down again (sigh) -- anyone what to propose an alternative
> here? It's an embarrasment.)
>
> I'm also about ready to release a major update to Strut by Strut, but
> I'm not sure whether to propose that for the package or leave it as a
> Resource.
>
> There was also an update to the Resource page, which includes a number
> of recent 3rd party tutorials and articles, but was inadvertently left
> out of yesterday's 1.0. See
>
> < http://husted.com/about/struts/resources.html >
>
> for a copy of what I just added to 1.1.
>
> -- Ted Husted, Husted dot Com, Fairport NY USA.
> -- Custom Software ~ Technical Services.
> -- Tel 716 737-3463.
> -- http://www.husted.com/about/struts/
>
> Jonathan wrote:
> >
> > Hello all.
> > It seems that there is a back log of documentation to do and I would
like to
> > offer to help with it as I am very good at explaining things. It also
helps
> > me understand the framework in a deeper way. However, because I am
still
> > relatively green with Struts (3 months) I will need to correspond with
some
> > of you outside of the list to get questions answered (I dont want to
clutter
> > up the list with these questions). I can complete sections according to
> > when you want them, or I can do it in the order I want.
> >
> > If this is ok with you all and you are interested, please send me an
email
> > at mailto:[EMAIL PROTECTED]
> >
> > Let us all salute the Sixers on their valiant effort last night
>
