You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Adrian Lanning <al...@hotmail.com> on 2004/06/28 18:04:28 UTC
thoughts on encouraging user development
Hi all,
I'm new to this list and looking forward to contributing. Recent list messages have implied a lower community involvement in submitting patches and helping out. I know its not an emergency or anything but I thought I'd throw some ideas out and try to stimulate some discussion on it.
At the risk of sounding silly I'd like to suggest that the first steps in encouring users to patch and contribute more might be trying to get the word out that the developers Want more user contribs (marketing) and making it easy to find out How to do it (usability).
I'm new to open-source development and contributing so maybe the contributing process is common knowledge. But it took me a lot longer than I would have expected to find out how to contribute to Struts. My original plan after not finding something on the Struts website was to email Ted Husted and ask him how to contribute. (I choose Ted simply because I own his book.) :-) Then I happened to find something about emailing patches to the dev list.
Only in doing my due-diligence for this letter did I happen across this page which outlines the process:
http://jakarta.apache.org/struts/faqs/helping.html
It would be interesting to see if just putting little links like, "Wanna contribute to Struts? Click Here!" around the Struts website (especially the main page) has a noticable effect. Also, putting a message from the developers on the main page about, "Ready for the next version? Help us get there faster!" might help get the message across that not only is it ok to contribute, the developers actually want you to.
(Now I'm not trying to say that people think developers don't want contributions. I don't know. I'm just throwing out some ideas on how to encourage more user involvement.)
Thoughts?
Adrian Lanning
Re: thoughts on encouraging user development
Posted by Joe Germuska <Jo...@Germuska.com>.
I think Adrian raises some good points. Adrian, note that we accept
patches to the docs as gladly as we accept patches to the code!
I hate to leave it at that, but I'm not sure when I'll have time to
do any closer review of the docs, and I certainly can't volunteer
anyone else to do it!
Joe
At 12:04 PM -0400 6/28/04, Adrian Lanning wrote:
>Hi all,
>
>I'm new to this list and looking forward to contributing. Recent
>list messages have implied a lower community involvement in
>submitting patches and helping out. I know its not an emergency or
>anything but I thought I'd throw some ideas out and try to stimulate
>some discussion on it.
>
>At the risk of sounding silly I'd like to suggest that the first
>steps in encouring users to patch and contribute more might be
>trying to get the word out that the developers Want more user
>contribs (marketing) and making it easy to find out How to do it
>(usability).
>
>I'm new to open-source development and contributing so maybe the
>contributing process is common knowledge. But it took me a lot
>longer than I would have expected to find out how to contribute to
>Struts. My original plan after not finding something on the Struts
>website was to email Ted Husted and ask him how to contribute. (I
>choose Ted simply because I own his book.) :-) Then I happened to
>find something about emailing patches to the dev list.
>
>Only in doing my due-diligence for this letter did I happen across
>this page which outlines the process:
>http://jakarta.apache.org/struts/faqs/helping.html
>
>
>It would be interesting to see if just putting little links like,
>"Wanna contribute to Struts? Click Here!" around the Struts website
>(especially the main page) has a noticable effect. Also, putting a
>message from the developers on the main page about, "Ready for the
>next version? Help us get there faster!" might help get the message
>across that not only is it ok to contribute, the developers actually
>want you to.
>
>(Now I'm not trying to say that people think developers don't want
>contributions. I don't know. I'm just throwing out some ideas on
>how to encourage more user involvement.)
>
>Thoughts?
>
>Adrian Lanning
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn
back; I'll know I'm in the wrong place."
- Carlos Santana
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [OT] Re: Opening Salvo 'n CVS: step two: build time
Posted by Martin Cooper <ma...@apache.org>.
On Mon, 5 Jul 2004, Craig McClanahan wrote:
> Michael McGrady wrote:
>
>> I have successfully, and without too much difficulty, now uploaded the
>> struts src code into the wincvs as follows:
>>
>> 1. Downloaded and installed Python 2.3.4 from http://www.python.org/.
>> 2. Downloaded and installed WinCVS13b18 from http://www.wincvs.org/.
>> 3. Rooted around in
>> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
>> 4. Got a reference to a WinCVS manual at
>> http://cvsgui.sourceforge.net/howto/index.html.
>> 5. Downloaded PuTTY from
>> http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
>> 6. Jettisoned PuTTY and went to SecureCRT at
>> http://www.vandyke.com/products/securecrt/.
>> 7. Got the jakarta cvs info source from Ted Husted:
>> http://jakarta.apache.org/site/cvsindex.html.
>> 8. Uploaded jakarta-struts with:
>> Module name and path on the server = "jakarta-struts"
>> Local folder to checkout to = "C:\Program Files\GNU\WinCvs 1.3\"
>> CVSROOT = ":pwerver:anoncvs@cvs.apache.org:/home/cvspublic"
>>
>> I presume that I will want to do this all over and to find a more suitable
>> place to put the code, once I decide how to go about building the code. I
>> know there is a split of preferences between Maven and Ant going on.
>> Could the adherents of each train of thought please give me what they
>> would do to build? All the gory details are encouraged. Thanks. Who
>> knows? Maybe in a week or so I might become useful. ??
>>
>> Michael
>>
> I'm only familiar with the command line compilation environments (once you've
> got the source code checked out). In either the Ant or Maven case, you'll
> want to install CYGWIN (http://www.cygwin.com) to give yourself a set of
> command line tools that is like those available on Unix and Linux systems.
Just wanted to point out that cygwin (or other Unix-like tool set) is not
actually required, for either the Ant or Maven approaches. If you're more
comfortable with Windows tools, you can skip this step.
--
Martin Cooper
> Then:
>
> For either type of build:
> - I recommend using J2SE 1.4.2 (the latest production JDK)
> from (http://java.sun.com/j2se). That's what the nightly builds
> are created with, and in general it has better performance than
> 1.3 (or earlier) JDKs.
>
> For an Ant-based build:
> - Download and install Ant (http://ant.apache.org) 1.5.4 or later
> per website instructions.
> - Examine the documentation on the Struts website for all the
> dependent libraries you'll need (basically all available from
> <http://jakarta.apache.org>).
> - Configure a "build.properties" file in the top-level directory of your
> "jakarta-struts" source tree to point at where you have downloaded
> all the dependencies. The simplest way to create this is to copy
> "build.properties.sample" to "build.properties" and edit the paths.
> - Open a command line window and navigate to the top-level
> "jakarta-struts" directory.
> - Execute "ant clean dist".
>
> For a Maven-based build:
> - Download and install Maven (http://maven.apache.org)
> 1.0-rc4 or later per website instructions.
> - Open a command line window and navigate to the top-level
> "jakarta-struts" directory.
> - Execute "maven clean dist".
> - (I'm sure that there's a Maven option that does enough to
> create just the JAR files needed to test, instead of all the
> extra reports that Maven likes; I don't use Maven regularly,
> so you'll need to ask someone else about that.)
>
> Note that, while easier to set up, the Maven build is still experimental.
> The Ant build is the official one.
>
> Craig McClanahan
>
>
>
> ---------------------------------------------------------------------
> 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: [OT] Re: Opening Salvo 'n CVS: step two: build time
Posted by Craig McClanahan <cr...@apache.org>.
Michael McGrady wrote:
> I have successfully, and without too much difficulty, now uploaded the
> struts src code into the wincvs as follows:
>
> 1. Downloaded and installed Python 2.3.4 from http://www.python.org/.
> 2. Downloaded and installed WinCVS13b18 from http://www.wincvs.org/.
> 3. Rooted around in
> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
> 4. Got a reference to a WinCVS manual at
> http://cvsgui.sourceforge.net/howto/index.html.
> 5. Downloaded PuTTY from
> http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
> 6. Jettisoned PuTTY and went to SecureCRT at
> http://www.vandyke.com/products/securecrt/.
> 7. Got the jakarta cvs info source from Ted Husted:
> http://jakarta.apache.org/site/cvsindex.html.
> 8. Uploaded jakarta-struts with:
> Module name and path on the server = "jakarta-struts"
> Local folder to checkout to = "C:\Program Files\GNU\WinCvs 1.3\"
> CVSROOT = ":pwerver:anoncvs@cvs.apache.org:/home/cvspublic"
>
> I presume that I will want to do this all over and to find a more
> suitable place to put the code, once I decide how to go about building
> the code. I know there is a split of preferences between Maven and
> Ant going on. Could the adherents of each train of thought please
> give me what they would do to build? All the gory details are
> encouraged. Thanks. Who knows? Maybe in a week or so I might become
> useful. ??
>
> Michael
>
I'm only familiar with the command line compilation environments (once
you've got the source code checked out). In either the Ant or Maven
case, you'll want to install CYGWIN (http://www.cygwin.com) to give
yourself a set of command line tools that is like those available on
Unix and Linux systems. Then:
For either type of build:
- I recommend using J2SE 1.4.2 (the latest production JDK)
from (http://java.sun.com/j2se). That's what the nightly builds
are created with, and in general it has better performance than
1.3 (or earlier) JDKs.
For an Ant-based build:
- Download and install Ant (http://ant.apache.org) 1.5.4 or later
per website instructions.
- Examine the documentation on the Struts website for all the
dependent libraries you'll need (basically all available from
<http://jakarta.apache.org>).
- Configure a "build.properties" file in the top-level directory of your
"jakarta-struts" source tree to point at where you have downloaded
all the dependencies. The simplest way to create this is to copy
"build.properties.sample" to "build.properties" and edit the paths.
- Open a command line window and navigate to the top-level
"jakarta-struts" directory.
- Execute "ant clean dist".
For a Maven-based build:
- Download and install Maven (http://maven.apache.org)
1.0-rc4 or later per website instructions.
- Open a command line window and navigate to the top-level
"jakarta-struts" directory.
- Execute "maven clean dist".
- (I'm sure that there's a Maven option that does enough to
create just the JAR files needed to test, instead of all the
extra reports that Maven likes; I don't use Maven regularly,
so you'll need to ask someone else about that.)
Note that, while easier to set up, the Maven build is still
experimental. The Ant build is the official one.
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [OT] Re: Opening Salvo 'n CVS: step two: build time
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
I have successfully, and without too much difficulty, now uploaded the
struts src code into the wincvs as follows:
1. Downloaded and installed Python 2.3.4 from http://www.python.org/.
2. Downloaded and installed WinCVS13b18 from http://www.wincvs.org/.
3. Rooted around in
http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
4. Got a reference to a WinCVS manual at
http://cvsgui.sourceforge.net/howto/index.html.
5. Downloaded PuTTY from
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
6. Jettisoned PuTTY and went to SecureCRT at
http://www.vandyke.com/products/securecrt/.
7. Got the jakarta cvs info source from Ted Husted:
http://jakarta.apache.org/site/cvsindex.html.
8. Uploaded jakarta-struts with:
Module name and path on the server = "jakarta-struts"
Local folder to checkout to = "C:\Program Files\GNU\WinCvs 1.3\"
CVSROOT = ":pwerver:anoncvs@cvs.apache.org:/home/cvspublic"
I presume that I will want to do this all over and to find a more suitable
place to put the code, once I decide how to go about building the code. I
know there is a split of preferences between Maven and Ant going on. Could
the adherents of each train of thought please give me what they would do to
build? All the gory details are encouraged. Thanks. Who knows? Maybe in
a week or so I might become useful. ??
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [OT] Re: Opening Salvo 'n CVS: step one
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
Many thanks!
At 12:22 PM 7/5/2004, Ted Husted wrote:
>If you mean Apache projects don't require a uniform set of tools, that's
>correct. Many people want to use the same CVS client or IDE to work on ASF
>code as they do at work, so we don't prescribe which to use. Developers
>are invited to use whatever client software they like, so long as it can
>hook up to our CVS (or SVN), web, and mail servers. The standard procedure
>for accessing our CVS with the client of your choice are here:
>
>http://jakarta.apache.org/site/cvsindex.html
>
>At the bottom are links with instructions for various Unix and Windows
>clients.
>
>-Ted.
>
>On Mon, 05 Jul 2004 12:06:42 -0700, Michael McGrady wrote:
> > I am somewhat surprised that there is not a standard procedure for
> > doing this sort of thing. Accordingly, I guess I will just have to
> > take my time and eventually get there, since I have other things to
> > do than work on struts open source. I am going to keep track of
> > what I do so that hopefully others will be able to use the process
> > in the future, sort of like code reuse. Not complaining! It is
> > just that I love to code and am not crazy about learning new
> > administrative nuances.
> >
> > Please let me know if I am screwing up. So far, this is what I
> > have done.
> >
> >
> > 1. Downloaded and installed Python 2.3.4 from
> > http://www.python.org/. (APPARENTLY REQUIRED BY WinCVS)
> > 2. Downloaded and installed WinCVS13b18 from
> > http://www.wincvs.org/. 3. Rooted around in
> > http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 4
> > . Got a reference to a WinCVS manual at
> > http://cvsgui.sourceforge.net/howto/index.html. 5. Downloaded
> > PuTTY from
> > http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html. 6.
> > Jettisoned PuTTY
> > 7. Went to SecureCRT at
> > http://www.vandyke.com/products/securecrt/. 8. Completely screwed
> > up setting up WinCVS following the outdated instructions at jakarta
> > and decided to get back to this tomorrow.
> >
> >
> > At 07:52 AM 7/5/2004, you wrote:
> >> I probably wouldn't start with jcvs. For Windows, a good place to
> >> start is with PuTTY and WinCVS or TortoiseCVS. (I haven't used
> >> TortoiseCVS myself but TortoiseSVN is excellent.) For Unix, the
> >> standard command line version might be simplest.
> >>
> >> A good place to get "your feet wet" is with a SourceForge
> >> project, since the procedure there is so well documented.
> >>
> >> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
> >>
> >>
> >> You might try getting an anonymous checkout of, say,
> >> struts.sf.net first, to confirm that you have a working
> >> infrastructure, and then give Apache Struts another try.
> >>
> >> -Ted.
> >>
> >>
> >> On Mon, 05 Jul 2004 06:18:19 -0700, Michael McGrady wrote:
> >>
> >>> I am attempting to download struts cvs with jcvs ii. I am a
> >>> new user of CVS. I am essentially a coder and have not master
> >>> the finer arts of administrating these jobbers. Guess it is
> >>> time I learned, so here goes.
> >>>
> >>> I am getting the following error:
> >>>
> >>>
> >>> The CVS Request failed.
> >>> Failed to open socket to connect to cvs server
> >>> '2401@cvs.apache.org/home/cvspublic'.
> >>> could not create INETD connection for
> >>> '2401@cvs.apache.org:/home/cvspublic' -->
> >>> cvs.apache.org:/home/cvspublic could not create INETD
> >>> connection for '2401@cvs.apache.org:/home/cvspublic' -->
> >>> cvs.apache.org:/home/cvspublic
> >>>
> >>>
> >>> ** The command completed with an error status
> >>>
> >>>
> >>> I have used the PServer option and have the username as
> >>> anoncvs. My CVS Modules is "checkout". My CVS Server is
> >>> "cvs.apache.org:/home/cvspublic". My CVS Repository is
> >>> "/home/cvspublic". My Checkout Directory is "jakarta-struts".
> >>> And my arguments is "-d".
> >>>
> >>> Then I click "Checkout Module" and get the error. Any ideas?
> >>>
> >>>
> >>> ----------------------------------------------------------------
> >>> ---- - 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
>
>
>
>---------------------------------------------------------------------
>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: [OT] Re: Opening Salvo 'n CVS: step one
Posted by Ted Husted <hu...@apache.org>.
If you mean Apache projects don't require a uniform set of tools, that's correct. Many people want to use the same CVS client or IDE to work on ASF code as they do at work, so we don't prescribe which to use. Developers are invited to use whatever client software they like, so long as it can hook up to our CVS (or SVN), web, and mail servers. The standard procedure for accessing our CVS with the client of your choice are here:
http://jakarta.apache.org/site/cvsindex.html
At the bottom are links with instructions for various Unix and Windows clients.
-Ted.
On Mon, 05 Jul 2004 12:06:42 -0700, Michael McGrady wrote:
> I am somewhat surprised that there is not a standard procedure for
> doing this sort of thing. Accordingly, I guess I will just have to
> take my time and eventually get there, since I have other things to
> do than work on struts open source. I am going to keep track of
> what I do so that hopefully others will be able to use the process
> in the future, sort of like code reuse. Not complaining! It is
> just that I love to code and am not crazy about learning new
> administrative nuances.
>
> Please let me know if I am screwing up. So far, this is what I
> have done.
>
>
> 1. Downloaded and installed Python 2.3.4 from
> http://www.python.org/. (APPARENTLY REQUIRED BY WinCVS)
> 2. Downloaded and installed WinCVS13b18 from
> http://www.wincvs.org/. 3. Rooted around in
> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 4
> . Got a reference to a WinCVS manual at
> http://cvsgui.sourceforge.net/howto/index.html. 5. Downloaded
> PuTTY from
> http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html. 6.
> Jettisoned PuTTY
> 7. Went to SecureCRT at
> http://www.vandyke.com/products/securecrt/. 8. Completely screwed
> up setting up WinCVS following the outdated instructions at jakarta
> and decided to get back to this tomorrow.
>
>
> At 07:52 AM 7/5/2004, you wrote:
>> I probably wouldn't start with jcvs. For Windows, a good place to
>> start is with PuTTY and WinCVS or TortoiseCVS. (I haven't used
>> TortoiseCVS myself but TortoiseSVN is excellent.) For Unix, the
>> standard command line version might be simplest.
>>
>> A good place to get "your feet wet" is with a SourceForge
>> project, since the procedure there is so well documented.
>>
>> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
>>
>>
>> You might try getting an anonymous checkout of, say,
>> struts.sf.net first, to confirm that you have a working
>> infrastructure, and then give Apache Struts another try.
>>
>> -Ted.
>>
>>
>> On Mon, 05 Jul 2004 06:18:19 -0700, Michael McGrady wrote:
>>
>>> I am attempting to download struts cvs with jcvs ii. I am a
>>> new user of CVS. I am essentially a coder and have not master
>>> the finer arts of administrating these jobbers. Guess it is
>>> time I learned, so here goes.
>>>
>>> I am getting the following error:
>>>
>>>
>>> The CVS Request failed.
>>> Failed to open socket to connect to cvs server
>>> '2401@cvs.apache.org/home/cvspublic'.
>>> could not create INETD connection for
>>> '2401@cvs.apache.org:/home/cvspublic' -->
>>> cvs.apache.org:/home/cvspublic could not create INETD
>>> connection for '2401@cvs.apache.org:/home/cvspublic' -->
>>> cvs.apache.org:/home/cvspublic
>>>
>>>
>>> ** The command completed with an error status
>>>
>>>
>>> I have used the PServer option and have the username as
>>> anoncvs. My CVS Modules is "checkout". My CVS Server is
>>> "cvs.apache.org:/home/cvspublic". My CVS Repository is
>>> "/home/cvspublic". My Checkout Directory is "jakarta-struts".
>>> And my arguments is "-d".
>>>
>>> Then I click "Checkout Module" and get the error. Any ideas?
>>>
>>>
>>> ----------------------------------------------------------------
>>> ---- - 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
[OT] Re: Opening Salvo 'n CVS: step one
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
I am somewhat surprised that there is not a standard procedure for doing
this sort of thing. Accordingly, I guess I will just have to take my time
and eventually get there, since I have other things to do than work on
struts open source. I am going to keep track of what I do so that
hopefully others will be able to use the process in the future, sort of
like code reuse. Not complaining! It is just that I love to code and am
not crazy about learning new administrative nuances.
Please let me know if I am screwing up. So far, this is what I have done.
1. Downloaded and installed Python 2.3.4 from http://www.python.org/.
(APPARENTLY REQUIRED BY WinCVS)
2. Downloaded and installed WinCVS13b18 from http://www.wincvs.org/.
3. Rooted around in
http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
4. Got a reference to a WinCVS manual at
http://cvsgui.sourceforge.net/howto/index.html.
5. Downloaded PuTTY from
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
6. Jettisoned PuTTY
7. Went to SecureCRT at http://www.vandyke.com/products/securecrt/.
8. Completely screwed up setting up WinCVS following the outdated
instructions at jakarta and decided to get back to this tomorrow.
At 07:52 AM 7/5/2004, you wrote:
>I probably wouldn't start with jcvs. For Windows, a good place to start is
>with PuTTY and WinCVS or TortoiseCVS. (I haven't used TortoiseCVS myself
>but TortoiseSVN is excellent.) For Unix, the standard command line version
>might be simplest.
>
>A good place to get "your feet wet" is with a SourceForge project, since
>the procedure there is so well documented.
>
>http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
>
>You might try getting an anonymous checkout of, say, struts.sf.net first,
>to confirm that you have a working infrastructure, and then give Apache
>Struts another try.
>
>-Ted.
>
>On Mon, 05 Jul 2004 06:18:19 -0700, Michael McGrady wrote:
> > I am attempting to download struts cvs with jcvs ii. I am a new
> > user of CVS. I am essentially a coder and have not master the
> > finer arts of administrating these jobbers. Guess it is time I
> > learned, so here goes.
> >
> > I am getting the following error:
> >
> >
> > The CVS Request failed.
> > Failed to open socket to connect to cvs server
> > '2401@cvs.apache.org/home/cvspublic'.
> > could not create INETD connection for
> > '2401@cvs.apache.org:/home/cvspublic' -->
> > cvs.apache.org:/home/cvspublic could not create INETD connection for
> > '2401@cvs.apache.org:/home/cvspublic' -->
> > cvs.apache.org:/home/cvspublic
> >
> >
> > ** The command completed with an error status
> >
> >
> > I have used the PServer option and have the username as anoncvs.
> > My CVS Modules is "checkout". My CVS Server is
> > "cvs.apache.org:/home/cvspublic". My CVS Repository is
> > "/home/cvspublic". My Checkout Directory is "jakarta-struts". And
> > my arguments is "-d".
> >
> > Then I click "Checkout Module" and get the error. Any ideas?
> >
> >
> > --------------------------------------------------------------------
> > - 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: Opening Salvo 'n CVS
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
Thanks, Joe,
Even though I have reluctantly jettisoned JCVS, because I like to support
Java products, this was helpful for my understanding.
Michael
At 11:53 AM 7/5/2004, you wrote:
>I don't use JCVS, but I'm wondering if you should remove the path segment
>from your "CVS Server" configuration. That is, change
>cvs.apache.org:/home/cvspublic
>to
>cvs.apache.org
>
> From the error message, I'm assuming that it is trying to use your whole
> "CVS Server" setting as a domain name, which it isn't.
>
>Joe
>
>At 6:18 AM -0700 7/5/04, Michael McGrady wrote:
>>I am attempting to download struts cvs with jcvs ii. I am a new user of
>>CVS. I am essentially a coder and have not master the finer arts of
>>administrating these jobbers. Guess it is time I learned, so here goes.
>>
>>I am getting the following error:
>>
>> The CVS Request failed.
>> Failed to open socket to connect to cvs server
>> '2401@cvs.apache.org/home/cvspublic'.
>> could not create INETD connection for
>> '2401@cvs.apache.org:/home/cvspublic' --> cvs.apache.org:/home/cvspublic
>> could not create INETD connection for
>> '2401@cvs.apache.org:/home/cvspublic' --> cvs.apache.org:/home/cvspublic
>>
>> ** The command completed with an error status
>>
>>I have used the PServer option and have the username as anoncvs. My CVS
>>Modules is "checkout". My CVS Server is
>>"cvs.apache.org:/home/cvspublic". My CVS Repository is
>>"/home/cvspublic". My Checkout Directory is "jakarta-struts". And my
>>arguments is "-d".
>>
>>Then I click "Checkout Module" and get the error. Any ideas?
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>For additional commands, e-mail: dev-help@struts.apache.org
>
>
>--
>Joe Germuska
>Joe@Germuska.com
>http://blog.germuska.com
>"In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back;
>I'll know I'm in the wrong place."
> - Carlos Santana
>
>---------------------------------------------------------------------
>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: Opening Salvo 'n CVS
Posted by Joe Germuska <Jo...@Germuska.com>.
I don't use JCVS, but I'm wondering if you should remove the path
segment from your "CVS Server" configuration. That is, change
cvs.apache.org:/home/cvspublic
to
cvs.apache.org
From the error message, I'm assuming that it is trying to use your
whole "CVS Server" setting as a domain name, which it isn't.
Joe
At 6:18 AM -0700 7/5/04, Michael McGrady wrote:
>I am attempting to download struts cvs with jcvs ii. I am a new
>user of CVS. I am essentially a coder and have not master the finer
>arts of administrating these jobbers. Guess it is time I learned,
>so here goes.
>
>I am getting the following error:
>
> The CVS Request failed.
> Failed to open socket to connect to cvs server
>'2401@cvs.apache.org/home/cvspublic'.
> could not create INETD connection for
>'2401@cvs.apache.org:/home/cvspublic' -->
>cvs.apache.org:/home/cvspublic
> could not create INETD connection for
>'2401@cvs.apache.org:/home/cvspublic' -->
>cvs.apache.org:/home/cvspublic
>
> ** The command completed with an error status
>
>I have used the PServer option and have the username as anoncvs. My
>CVS Modules is "checkout". My CVS Server is
>"cvs.apache.org:/home/cvspublic". My CVS Repository is
>"/home/cvspublic". My Checkout Directory is "jakarta-struts". And
>my arguments is "-d".
>
>Then I click "Checkout Module" and get the error. Any ideas?
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>For additional commands, e-mail: dev-help@struts.apache.org
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn
back; I'll know I'm in the wrong place."
- Carlos Santana
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Opening Salvo 'n CVS
Posted by Ted Husted <hu...@apache.org>.
I probably wouldn't start with jcvs. For Windows, a good place to start is with PuTTY and WinCVS or TortoiseCVS. (I haven't used TortoiseCVS myself but TortoiseSVN is excellent.) For Unix, the standard command line version might be simplest.
A good place to get "your feet wet" is with a SourceForge project, since the procedure there is so well documented.
http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
You might try getting an anonymous checkout of, say, struts.sf.net first, to confirm that you have a working infrastructure, and then give Apache Struts another try.
-Ted.
On Mon, 05 Jul 2004 06:18:19 -0700, Michael McGrady wrote:
> I am attempting to download struts cvs with jcvs ii. I am a new
> user of CVS. I am essentially a coder and have not master the
> finer arts of administrating these jobbers. Guess it is time I
> learned, so here goes.
>
> I am getting the following error:
>
>
> The CVS Request failed.
> Failed to open socket to connect to cvs server
> '2401@cvs.apache.org/home/cvspublic'.
> could not create INETD connection for
> '2401@cvs.apache.org:/home/cvspublic' -->
> cvs.apache.org:/home/cvspublic could not create INETD connection for
> '2401@cvs.apache.org:/home/cvspublic' -->
> cvs.apache.org:/home/cvspublic
>
>
> ** The command completed with an error status
>
>
> I have used the PServer option and have the username as anoncvs.
> My CVS Modules is "checkout". My CVS Server is
> "cvs.apache.org:/home/cvspublic". My CVS Repository is
> "/home/cvspublic". My Checkout Directory is "jakarta-struts". And
> my arguments is "-d".
>
> Then I click "Checkout Module" and get the error. Any ideas?
>
>
> --------------------------------------------------------------------
> - 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
Opening Salvo 'n CVS
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
I am attempting to download struts cvs with jcvs ii. I am a new user of
CVS. I am essentially a coder and have not master the finer arts of
administrating these jobbers. Guess it is time I learned, so here goes.
I am getting the following error:
The CVS Request failed.
Failed to open socket to connect to cvs server
'2401@cvs.apache.org/home/cvspublic'.
could not create INETD connection for
'2401@cvs.apache.org:/home/cvspublic' --> cvs.apache.org:/home/cvspublic
could not create INETD connection for
'2401@cvs.apache.org:/home/cvspublic' --> cvs.apache.org:/home/cvspublic
** The command completed with an error status
I have used the PServer option and have the username as anoncvs. My CVS
Modules is "checkout". My CVS Server is
"cvs.apache.org:/home/cvspublic". My CVS Repository is
"/home/cvspublic". My Checkout Directory is "jakarta-struts". And my
arguments is "-d".
Then I click "Checkout Module" and get the error. Any ideas?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: thoughts on encouraging user development
Posted by Joe Germuska <Jo...@Germuska.com>.
>Some people might feel that voting for a bug actually "counts" as a stronger
>comment, especially since they can leave a limited number of bugs yet leave
>comments all over. Also, some might choose not to comment when whatever
>comment they might already make has already been said by somebody else.
>
>Maybe there's a way to disable voting for bugs if votes don't count anyway,
Personally, I think votes "count." I don't think they should be
disabled, and I think that they are as effective a way as any for
community members to demonstrate their interest in a ticket.
Furthermore, I'd rather people vote than simply add "me too" to the
comments.
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn
back; I'll know I'm in the wrong place."
- Carlos Santana
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: thoughts on encouraging user development
Posted by Hubert Rabago <ja...@yahoo.com>.
--- Ted Husted <hu...@apache.org> wrote:
> I can personally guarantee that if two or three developers post to a ticket
> and say "works for me", especially if they are names that I've seen before,
> the patch will be (and has been) applied. [Of course, whether it "sticks"
> is up to the rest of the committers :)]
I have no doubt about that. What I tried to point out is my observation that
people don't seem to try out a patch just by pure coincidence. Out of the
few who do nightly builds to use in their production apps, coincidentally
trying out the very same patch out of the two dozen reports with patches seem
like long odds. My suggestion was for a committer who's interested in
applying a patch, but not having the time to try it out himself, to make a
call for developers to try it out. IIRC, I've seen this happen, and indeed
the patch got applied. Sort of a "committer-approved short list".
>
> When I review tickets, the ones with additional comments do get the most
> attention, the ones that stand alone do get the least.
<snip/>
> This is a meritocracy, and hands-on effort
> counts for more than does clicking on a radio button.
<snip/>
> We need to hear from other members of the community that this
> issue is a problem for people <snip/>
Some people might feel that voting for a bug actually "counts" as a stronger
comment, especially since they can leave a limited number of bugs yet leave
comments all over. Also, some might choose not to comment when whatever
comment they might already make has already been said by somebody else.
Maybe there's a way to disable voting for bugs if votes don't count anyway,
or at least let people know that textual comments count more than votes, just
to avoid the misconception. I've seen reports where there were more votes
than comments. If those people knew leaving a comment counted more than
casting their limited votes, it's a good bet that they would've actually left
comments instead.
>
> Here's another reason why: All the committers are very busy guys right now.
I think people sense this, and that's why there were calls sometime ago for
more committers. Personally, I don't feel there's a need for more
committers. I think the current batch of committers are doing a wonderful
job, and I'm glad the bigger changes (such as struts-chain) aren't being
treated as an overnight job. I'm also glad that just submitting a patch
doesn't make a contributor a committer.
I think the fact that there aren't a whole bunch of changes right now reflect
the stability of Struts. Struts already provides so much, and yet remains
very reliable -- only a small percentage of the 262 tickets are really bugs,
most are just enhancement requests. The few bugs I've seen on the tickets
seem to only affect really obscure situations.
> We have very few hours to spend on Apache, and need to take care that we
> spend these hours wisely. Seeing interest in a patch helps us set
> priorities. All the reports do go to the DEV list, and older reports often"
> bubble to the top" that way.
>
> -Ted.
>
> On Mon, 05 Jul 2004 02:00:52 -0700 (PDT), Hubert Rabago wrote:
> >
> > Steve,
> >
> > If I had to guess, I think it's more likely that a person will
> > submit a patch than try someone else's patch and report its
> > effectiveness.
> >
> > A great number of people use Struts, that's a given, but I think
> > it's a much smaller percentage that use the nightly builds (mostly
> > brave and/or trusting souls and those whose hands aren't tied by
> > corporate standards or probably work alone or in a small team). An
> > even smaller percentage use the nightly build by building it
> > themselves. (Maybe some still remember the series of emails
> > before, about the experience of other folks having difficulty
> > setting up to build Struts.) From that group, I'm not sure a whole
> > lot of them would try out a patch on a bug report that the
> > committers aren't noticing. You'd have to find several people from
> > that small group who are also affected enough by an
> > issue/enhancement the patch addresses to be able to spend the time
> > and apply, rebuild, and test, only to end up with a forked version
> > which will be incompatible with the next nightly build/release.
> > Although I can see this happening in an ideal scenario (poor guys
> > with incompatible binaries, though), this just never struck me as
> > realistic.
> >
> > With 262 tickets, or over two dozen with patches, to get "several
> > people" reporting back on the same patch, enough to get the
> > feedback that said patch is "probably good", seems unlikely.
> >
> > I can't recall several people reporting on the same patch so much
> > that it prompted a committer to eventually review and commit it. I
> > think the closest I've seen is add'l feedback to get a bug solved,
> > or an enhancement added, maybe by messages to dev list or add'l
> > votes on the bug report. There were a couple or more times I've
> > seen someone else look at the submitted patch and suggest
> > improvements or alternate solutions. Still, s/he didn't really say
> > "I applied the patch to my local Struts copy and tried it out and I
> > think blah blah blah...".
> >
> > Maybe a more realistic scenario would be a call from a committer
> > for volunteers to specifically review, apply, and test a patch that
> > he's thinking of applying to CVS. I think this has happened at
> > least once during the time I've been lurking, and IIRC it got a few
> > responses and the patch got applied.
> >
> > Also, I hope this isn't the only criteria for determining whether
> > an issue is one that affects many people. I know it's been said
> > here before that "patches are the only votes that count", but
> > still, maybe we can use the bugzilla voting mechanism to encourage
> > users to give feedback on which ones affect them the most.
> >
> > Hubert
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: thoughts on encouraging user development
Posted by Ted Husted <hu...@apache.org>.
I can personally guarantee that if two or three developers post to a ticket and say "works for me", especially if they are names that I've seen before, the patch will be (and has been) applied. [Of course, whether it "sticks" is up to the rest of the committers :)]
When I review tickets, the ones with additional comments do get the most attention, the ones that stand alone do get the least. The ones without patches or comments will probably never be pursued. The squeaky wheels get the oil. Votes are nice, but what I really want to know is if they've tried the patch themselves. This is a meritocracy, and hands-on effort counts for more than does clicking on a radio button.
Here's a big reason why: If the ticket affected the applications I write, or the applications any of the committers write, the problem would already be fixed. We need to hear from other members of the community that this issue is a problem for people, and that this is a solution that they would use. When the problem is one that our application do not share, this is not a judgment we can make on our own.
Here's another reason why: All the committers are very busy guys right now. We have very few hours to spend on Apache, and need to take care that we spend these hours wisely. Seeing interest in a patch helps us set priorities. All the reports do go to the DEV list, and older reports often" bubble to the top" that way.
-Ted.
On Mon, 05 Jul 2004 02:00:52 -0700 (PDT), Hubert Rabago wrote:
>
> Steve,
>
> If I had to guess, I think it's more likely that a person will
> submit a patch than try someone else's patch and report its
> effectiveness.
>
> A great number of people use Struts, that's a given, but I think
> it's a much smaller percentage that use the nightly builds (mostly
> brave and/or trusting souls and those whose hands aren't tied by
> corporate standards or probably work alone or in a small team). An
> even smaller percentage use the nightly build by building it
> themselves. (Maybe some still remember the series of emails
> before, about the experience of other folks having difficulty
> setting up to build Struts.) From that group, I'm not sure a whole
> lot of them would try out a patch on a bug report that the
> committers aren't noticing. You'd have to find several people from
> that small group who are also affected enough by an
> issue/enhancement the patch addresses to be able to spend the time
> and apply, rebuild, and test, only to end up with a forked version
> which will be incompatible with the next nightly build/release.
> Although I can see this happening in an ideal scenario (poor guys
> with incompatible binaries, though), this just never struck me as
> realistic.
>
> With 262 tickets, or over two dozen with patches, to get "several
> people" reporting back on the same patch, enough to get the
> feedback that said patch is "probably good", seems unlikely.
>
> I can't recall several people reporting on the same patch so much
> that it prompted a committer to eventually review and commit it. I
> think the closest I've seen is add'l feedback to get a bug solved,
> or an enhancement added, maybe by messages to dev list or add'l
> votes on the bug report. There were a couple or more times I've
> seen someone else look at the submitted patch and suggest
> improvements or alternate solutions. Still, s/he didn't really say
> "I applied the patch to my local Struts copy and tried it out and I
> think blah blah blah...".
>
> Maybe a more realistic scenario would be a call from a committer
> for volunteers to specifically review, apply, and test a patch that
> he's thinking of applying to CVS. I think this has happened at
> least once during the time I've been lurking, and IIRC it got a few
> responses and the patch got applied.
>
> Also, I hope this isn't the only criteria for determining whether
> an issue is one that affects many people. I know it's been said
> here before that "patches are the only votes that count", but
> still, maybe we can use the bugzilla voting mechanism to encourage
> users to give feedback on which ones affect them the most.
>
> Hubert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: thoughts on encouraging user development
Posted by Hubert Rabago <ja...@yahoo.com>.
Steve,
If I had to guess, I think it's more likely that a person will submit a patch
than try someone else's patch and report its effectiveness.
A great number of people use Struts, that's a given, but I think it's a much
smaller percentage that use the nightly builds (mostly brave and/or trusting
souls and those whose hands aren't tied by corporate standards or probably
work alone or in a small team). An even smaller percentage use the nightly
build by building it themselves. (Maybe some still remember the series of
emails before, about the experience of other folks having difficulty setting
up to build Struts.) From that group, I'm not sure a whole lot of them would
try out a patch on a bug report that the committers aren't noticing. You'd
have to find several people from that small group who are also affected
enough by an issue/enhancement the patch addresses to be able to spend the
time and apply, rebuild, and test, only to end up with a forked version which
will be incompatible with the next nightly build/release. Although I can see
this happening in an ideal scenario (poor guys with incompatible binaries,
though), this just never struck me as realistic.
With 262 tickets, or over two dozen with patches, to get "several people"
reporting back on the same patch, enough to get the feedback that said patch
is "probably good", seems unlikely.
I can't recall several people reporting on the same patch so much that it
prompted a committer to eventually review and commit it. I think the closest
I've seen is add'l feedback to get a bug solved, or an enhancement added,
maybe by messages to dev list or add'l votes on the bug report. There were a
couple or more times I've seen someone else look at the submitted patch and
suggest improvements or alternate solutions. Still, s/he didn't really say
"I applied the patch to my local Struts copy and tried it out and I think
blah blah blah...".
Maybe a more realistic scenario would be a call from a committer for
volunteers to specifically review, apply, and test a patch that he's thinking
of applying to CVS. I think this has happened at least once during the time
I've been lurking, and IIRC it got a few responses and the patch got applied.
Also, I hope this isn't the only criteria for determining whether an issue is
one that affects many people. I know it's been said here before that
"patches are the only votes that count", but still, maybe we can use the
bugzilla voting mechanism to encourage users to give feedback on which ones
affect them the most.
Hubert
--- Steve Raeburn <sr...@apache.org> wrote:
> Michael,
>
> I'd like to follow-up on just one point - reviewing of patches.
>
> Anyone can monitor bugzilla and review patches when they come in. If
> several people send feedback, via bugzilla or via the mailing lists, it
> might speed up the process of getting those patches into CVS.
>
> If there's a patch that you would find useful, try it out and report
> back. If several people are reporting back about the same patch and they
> all say it solves the problem, then we know that a) this is an issue
> that affects many people b) the patch is probably good.
>
> In that case, the chances of a committer spending time looking at the
> problem is greatly increased because they know it's a worthwhile cause
> and that a probable solution exists.
>
> So there is at least one way for more people to contribute AND reduce
> the backlog of requests.
>
> Steve
>
>
> > -----Original Message-----
> > From: Michael McGrady [mailto:mike@michaelmcgrady.com]
> > Sent: July 4, 2004 11:46 AM
> > To: Struts Developers List
> > Subject: Re: thoughts on encouraging user development
> >
> >
> > This was one of the more helpful posts in this regard in a long
> > time. Thanks Ted.
> >
> > From the point of view of someone who regularly adds code to
> > the struts
> > framework on my own site but whom never really offers that
> > code to the
> > community, EXCEPT VIA THE struts WIKI (for reasons explained
> > here before),
> > it might be helpful if someone with perspective on the struts
> > "project"
> > indicated in clear terms what would be helpful. I can tell
> > you that I
> > personally don't have a clue, even though I am daily in
> > contact with all
> > the idea emanating out of struts. I think I have a sufficient
> > understanding of struts to write the platform from scratch.
> > But, I don't
> > have the time to burrow through the administrative details to
> > get involved
> > seriously in the community. This is especially so if
> > contributions are
> > going to just sit without review for an indeterminate period.
> > I think
> > everyone likes to think that there work is going to at least
> > have a chance
> > at making a difference.
> >
> > This is not written in despair. I can tell that struts is doing just
> > fine. Great in fact. Love it. Just some thoughts if anyone
> > cares about
> > this perspective.
> >
> > Michael
> >
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: thoughts on encouraging user development
Posted by Steve Raeburn <sr...@apache.org>.
Michael,
I'd like to follow-up on just one point - reviewing of patches.
Anyone can monitor bugzilla and review patches when they come in. If
several people send feedback, via bugzilla or via the mailing lists, it
might speed up the process of getting those patches into CVS.
If there's a patch that you would find useful, try it out and report
back. If several people are reporting back about the same patch and they
all say it solves the problem, then we know that a) this is an issue
that affects many people b) the patch is probably good.
In that case, the chances of a committer spending time looking at the
problem is greatly increased because they know it's a worthwhile cause
and that a probable solution exists.
So there is at least one way for more people to contribute AND reduce
the backlog of requests.
Steve
> -----Original Message-----
> From: Michael McGrady [mailto:mike@michaelmcgrady.com]
> Sent: July 4, 2004 11:46 AM
> To: Struts Developers List
> Subject: Re: thoughts on encouraging user development
>
>
> This was one of the more helpful posts in this regard in a long
> time. Thanks Ted.
>
> From the point of view of someone who regularly adds code to
> the struts
> framework on my own site but whom never really offers that
> code to the
> community, EXCEPT VIA THE struts WIKI (for reasons explained
> here before),
> it might be helpful if someone with perspective on the struts
> "project"
> indicated in clear terms what would be helpful. I can tell
> you that I
> personally don't have a clue, even though I am daily in
> contact with all
> the idea emanating out of struts. I think I have a sufficient
> understanding of struts to write the platform from scratch.
> But, I don't
> have the time to burrow through the administrative details to
> get involved
> seriously in the community. This is especially so if
> contributions are
> going to just sit without review for an indeterminate period.
> I think
> everyone likes to think that there work is going to at least
> have a chance
> at making a difference.
>
> This is not written in despair. I can tell that struts is doing just
> fine. Great in fact. Love it. Just some thoughts if anyone
> cares about
> this perspective.
>
> Michael
>
> At 11:10 AM 7/4/2004, you wrote:
> >One of the best posts I've read on contributing to open
> source is one that
> >Craig made some time ago to the Tomcat list.
> >
> >* http://jakarta.apache.org/site/contributing.html
> >
> >In this post, Craig describes how committers evolve from
> users. As people
> >use use Struts, and find ways to improve it, they can
> contribute their
> >improvements back to the community. There are several ways to make
> >contibutions. Many people setup their own site, other join
> the SourceForge
> >Struts site (http://struts.sf.net/), and some make
> contributions to the
> >main distribution.
> >
> >Because we consider contributing an extension of using, the "How to
> >contribute" material is part of the Using page.
> >
> >* http://apache.struts.org/using.html
> >
> >If anyone gets the sense that we aren't pushing hard for
> contributions, it
> >might be because we are already backlogged. There are 262
> outstanding
> >enhancement tickets, 29 with patches. So many that I
> despair at ever
> >reviewing them all. I'm sure that many are duplicates,
> overlapping, or
> >obsolete, but what Apache hours I have available need to be spent
> >elsewhere right now. :(
> >
> >-Ted.
> >
> >
> >---------------------------------------------------------------------
> >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: thoughts on encouraging user development
Posted by Hubert Rabago <ja...@yahoo.com>.
--- Michael McGrady <mi...@michaelmcgrady.com> wrote:
<snip/>
> it might be helpful if someone with perspective on the struts "project"
> indicated in clear terms what would be helpful.
<snip/>
> This is especially so if contributions are
> going to just sit without review for an indeterminate period. I think
> everyone likes to think that there work is going to at least have a chance
> at making a difference.
>
> This is not written in despair. I can tell that struts is doing just
> fine. Great in fact. Love it. Just some thoughts if anyone cares about
> this perspective.
>
> Michael
>
I agree on the points Michael made here (including those on the last
paragraph). I think more people would be encouraged to contribute if they
knew which areas they should spend time on. The standard response often
includes "contributing and reviewing patches", but not all submitted or
reviewed patches can be applied. Maybe a patch/code version of
http://struts.apache.org/faqs/newbie.html#undocumented would help.
[Speaking of which, how do contributions to the items listed in
faqs/newbie.html#undocumented get submitted?]
Hubert
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: thoughts on encouraging user development
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
This was one of the more helpful posts in this regard in a long
time. Thanks Ted.
From the point of view of someone who regularly adds code to the struts
framework on my own site but whom never really offers that code to the
community, EXCEPT VIA THE struts WIKI (for reasons explained here before),
it might be helpful if someone with perspective on the struts "project"
indicated in clear terms what would be helpful. I can tell you that I
personally don't have a clue, even though I am daily in contact with all
the idea emanating out of struts. I think I have a sufficient
understanding of struts to write the platform from scratch. But, I don't
have the time to burrow through the administrative details to get involved
seriously in the community. This is especially so if contributions are
going to just sit without review for an indeterminate period. I think
everyone likes to think that there work is going to at least have a chance
at making a difference.
This is not written in despair. I can tell that struts is doing just
fine. Great in fact. Love it. Just some thoughts if anyone cares about
this perspective.
Michael
At 11:10 AM 7/4/2004, you wrote:
>One of the best posts I've read on contributing to open source is one that
>Craig made some time ago to the Tomcat list.
>
>* http://jakarta.apache.org/site/contributing.html
>
>In this post, Craig describes how committers evolve from users. As people
>use use Struts, and find ways to improve it, they can contribute their
>improvements back to the community. There are several ways to make
>contibutions. Many people setup their own site, other join the SourceForge
>Struts site (http://struts.sf.net/), and some make contributions to the
>main distribution.
>
>Because we consider contributing an extension of using, the "How to
>contribute" material is part of the Using page.
>
>* http://apache.struts.org/using.html
>
>If anyone gets the sense that we aren't pushing hard for contributions, it
>might be because we are already backlogged. There are 262 outstanding
>enhancement tickets, 29 with patches. So many that I despair at ever
>reviewing them all. I'm sure that many are duplicates, overlapping, or
>obsolete, but what Apache hours I have available need to be spent
>elsewhere right now. :(
>
>-Ted.
>
>
>---------------------------------------------------------------------
>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: thoughts on encouraging user development
Posted by Ted Husted <hu...@apache.org>.
One of the best posts I've read on contributing to open source is one that Craig made some time ago to the Tomcat list.
* http://jakarta.apache.org/site/contributing.html
In this post, Craig describes how committers evolve from users. As people use use Struts, and find ways to improve it, they can contribute their improvements back to the community. There are several ways to make contibutions. Many people setup their own site, other join the SourceForge Struts site (http://struts.sf.net/), and some make contributions to the main distribution.
Because we consider contributing an extension of using, the "How to contribute" material is part of the Using page.
* http://apache.struts.org/using.html
If anyone gets the sense that we aren't pushing hard for contributions, it might be because we are already backlogged. There are 262 outstanding enhancement tickets, 29 with patches. So many that I despair at ever reviewing them all. I'm sure that many are duplicates, overlapping, or obsolete, but what Apache hours I have available need to be spent elsewhere right now. :(
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org