On Fri, 4 Oct 2002, Edgar Dollin wrote:
> Date: Fri, 4 Oct 2002 12:50:43 -0400
> From: Edgar Dollin <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: 'Struts Developers List' <[EMAIL PROTECTED]>
> Subject: RE: Applying patches
>
> Isn't this part of a bigger problem that the whole open source community
> is wrestling with? How do the boys doing Linux do it or is that community
> better funded so the committers can spend full time on it?
>
>From my own personal experience, I can offer Tomcat as an example of open
source softare that is pretty heavily supported by a commercial interest
-- Sun pays the salary of several developers who are devoted to
maintaining and enhancing Tomcat (I was one of those folks until about six
months ago, when I switched roles). This pays off for Sun because we use
Tomcat in a myriad of places, and lets us benefit from the contributions
of others as well (we'd need to build a servlet and JSP container anyway;
this way we get more than we pay for). I'm sure the same kind of thing
happens in the Linux community.
Struts, on the other hand, is quite a lot less commercialized, although
many IDEs and development frameworks are starting to support it directly.
It will be interesting to see if any of the companies choose to fund some
part time developer effort directly on Struts (which has happened in the
past).
> One other issue regarding this issue and struts that I think is worth
> mentioning is that this is the window to ERP and that the issues we are
> all facing are so open ended and we are all pulling this project in
> different ways as well as so many other competing projects. Because of this
> there might be a need for 'sub' projects with committers who only review
> that code.
>
Another way to say this is that it's perfectly reasonable to define
"things that run on top of Struts" type projects, with their own developer
communities. There's already quite a few of those around, and I
anticipate more (as long as we don't screw around with API compatibility
too much :-). Those projects do *not* all have to live here at Jakarta,
though.
For the Struts project itself, I think the only possible case where
sub-committers might make sense is documentation-only folks. If a
committer is competent in Java, why would we (the project) want to
arbitrarily restrict which code they could work on?
> Edgar Dollin
>
Craig
>
>
> Craig R. McClanahan wrote:
>
> >Are you ready to do my job for me (60 hours a week lately), including my
> >travel schedule (such as Tokyo last week for JavaOne Japan), so I can
> >work on Struts? Or, better yet, pay me enough so I can work on it full
> >time? If you're not, then I find your attitude pretty presumptuous.
> >
> >All of Struts was, and is, done by volunteers on their own time. We do
> >this because we enjoy it -- the fact that *you* find it useful as well is
> >icing on the cake. When people have time to analyze the patches and apply
> >them (and take ownership for any problems that the patch causes), they
> >will -- but not until.
> >
> >If you feel strongly about it, start posting alternative nightly builds
> >that contain your patches applied. Who knows, if it's clear you know what
> >you are doing, you might get yourself nominated to be a committer, and
> >then *you* can see what it is like first hand :-).
> >
> >Craig
> >
> >
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
