You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Michael McGrady <mi...@michaelmcgrady.com> on 2004/07/10 15:09:43 UTC
Ready to Help: Guide Wanted!
Okay, Struts! I am CVS ready (sort of) and ready to work on Struts.
I am not at all new to Stuts and understand the whole very well. But, I am
completely new to this open source work. Someone want to "mentor" me in
and give me a step-by-step guide to helping out? You tell me what needs to
be done and I will do it. Starting with something simple might be
good. Right now I have no idea how to go about being a help. I learn
quick but learn best from hands on. Thanks.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Ready to Help: Guide Wanted!
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
Thanks, Ted,
I am on the job. ///;-)
Michael
At 06:54 AM 7/10/2004, you wrote:
>If you wanted to start with the documentation, I noticed that there are
>some items in the Newbie FAQ
>
>* http://struts.apache.org/faqs/newbie.html
>
>that could be integrated into the main documentation, particularly the
>ones regarding ActionForms. It's mainly cut and paste from one XML doc to
>another, and then recompiling the web site to see if it renders. (There's
>a special Ant target for just recompiling the web site.)
>
>You can then create a diff (or patch) of the changes. There are some good
>instructions here:
>
>* http://www.netbeans.org/community/contribute/patches.html
>
>And attach the diff to a Bugzilla report.
>
>Another thing would be to review the enhancement reports, especially those
>with patches, and form your own opinion as to whether they patch should be
>applied or retired, and append your comment to the report. A summary
>report regarding all the reports would also be nice, if someone were
>administratively-inclined. [But I think you already said that
>infrastructure wasn't your thing :)]
>
>If you think a patch is worthwhile, do be sure to try it yourself. New
>features should be accompanied by new tests, even if it is just something
>we can click on through Taglib-Exercises.
>
>-Ted.
>
>On Sat, 10 Jul 2004 06:09:43 -0700, Michael McGrady wrote:
> > Okay, Struts! I am CVS ready (sort of) and ready to work on Struts.
> >
> > I am not at all new to Stuts and understand the whole very well.
> > But, I am completely new to this open source work. Someone want to
> > "mentor" me in and give me a step-by-step guide to helping out?
> > You tell me what needs to be done and I will do it. Starting with
> > something simple might be good. Right now I have no idea how to go
> > about being a help. I learn quick but learn best from hands on.
> > Thanks.
> >
> > Michael
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For
> > additional commands, e-mail: dev-help@struts.apache.org
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Ready to Help: Guide Wanted!
Posted by Ted Husted <hu...@apache.org>.
If you wanted to start with the documentation, I noticed that there are some items in the Newbie FAQ
* http://struts.apache.org/faqs/newbie.html
that could be integrated into the main documentation, particularly the ones regarding ActionForms. It's mainly cut and paste from one XML doc to another, and then recompiling the web site to see if it renders. (There's a special Ant target for just recompiling the web site.)
You can then create a diff (or patch) of the changes. There are some good instructions here:
* http://www.netbeans.org/community/contribute/patches.html
And attach the diff to a Bugzilla report.
Another thing would be to review the enhancement reports, especially those with patches, and form your own opinion as to whether they patch should be applied or retired, and append your comment to the report. A summary report regarding all the reports would also be nice, if someone were administratively-inclined. [But I think you already said that infrastructure wasn't your thing :)]
If you think a patch is worthwhile, do be sure to try it yourself. New features should be accompanied by new tests, even if it is just something we can click on through Taglib-Exercises.
-Ted.
On Sat, 10 Jul 2004 06:09:43 -0700, Michael McGrady wrote:
>�Okay, Struts! �I am CVS ready (sort of) and ready to work on Struts.
>
>�I am not at all new to Stuts and understand the whole very well.
>�But, I am completely new to this open source work. �Someone want to
>�"mentor" me in and give me a step-by-step guide to helping out?
>�You tell me what needs to be done and I will do it. �Starting with
>�something simple might be good. �Right now I have no idea how to go
>�about being a help. �I learn quick but learn best from hands on.
>�Thanks.
>
>�Michael
>
>
>�--------------------------------------------------------------------
>�- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For
>�additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org