You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@jakarta.apache.org by "Frank W. Zammetti" <fz...@omnytex.com> on 2005/06/23 23:46:46 UTC
Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks
reusable in java web applications]
In reading through this all, I have a concern that it will be difficult
for any outside code to come in. Indeed it has proven difficult for
many people I have spoken to to get code into any Commons project
(although I myself had some things accepted, so clearly it is not
impossible).
What is the general feeling in terms of where the code comprising this
package will come from? At least, the largest portion of it? Is the
idea to take parts of other Jakarta and/or Apache projects as the source
material, or is it to put more of an emphasis on outside contributions?
The former sounds much more like the current Jakarta Commons concept,
the later is something else.
As someone who would like to contribute, I wouldn't want to see anything
that makes that more difficult embraced. Just curious what everyone
else is thinking...
Frank
robert burrell donkin wrote:
> On Wed, 2005-06-22 at 14:40 -0700, Phil Steitz wrote:
>
> <snip>
>
>>I guess 18 refers to the sandbox? I do not understand what the intent
>>of this is.
>
>
> is boils down to the question: does this subproject need it's own
> sandbox or will neophyte components start in the jakarta commons
> sandbox?
>
> - robert
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
>
>
>
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]
Posted by Oliver Zeigermann <ol...@gmail.com>.
I would love to see a very light weight WebDAV servlet which could be
taken from Tomcat.
Oliver
On 6/24/05, Henri Yandell <ba...@generationjava.com> wrote:
>
> Just looking within Jakarta, the following all jump out as initial code:
>
> http://svn.apache.org/repos/asf/jakarta/commons/sandbox/servlet/ has a
> couple of classes (as you know :) ).
>
> Taglibs of course, I estimate half a dozen to ten taglibs.
>
> Commons FileUploa.
>
> Commons Http
> (http://svn.apache.org/repos/asf/jakarta/commons/sandbox/http/trunk/src/java/org/apache/commons/http/)
> which contains a browser detector class.
>
> Commons Filters.
>
> Hen
>
> On Thu, 23 Jun 2005, Frank W. Zammetti wrote:
>
> > In reading through this all, I have a concern that it will be difficult for
> > any outside code to come in. Indeed it has proven difficult for many people
> > I have spoken to to get code into any Commons project (although I myself had
> > some things accepted, so clearly it is not impossible).
> >
> > What is the general feeling in terms of where the code comprising this
> > package will come from? At least, the largest portion of it? Is the idea to
> > take parts of other Jakarta and/or Apache projects as the source material, or
> > is it to put more of an emphasis on outside contributions? The former sounds
> > much more like the current Jakarta Commons concept, the later is something
> > else.
> >
> > As someone who would like to contribute, I wouldn't want to see anything that
> > makes that more difficult embraced. Just curious what everyone else is
> > thinking...
> >
> > Frank
> >
> > robert burrell donkin wrote:
> >> On Wed, 2005-06-22 at 14:40 -0700, Phil Steitz wrote:
> >>
> >> <snip>
> >>
> >>> I guess 18 refers to the sandbox? I do not understand what the intent of
> >>> this is.
> >>
> >>
> >> is boils down to the question: does this subproject need it's own
> >> sandbox or will neophyte components start in the jakarta commons
> >> sandbox?
> >>
> >> - robert
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: general-help@jakarta.apache.org
> >>
> >>
> >>
> >>
> >>
> >
> > --
> > Frank W. Zammetti
> > Founder and Chief Software Architect
> > Omnytex Technologies
> > http://www.omnytex.com
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: general-help@jakarta.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks
reusable in java web applications]
Posted by Henri Yandell <ba...@generationjava.com>.
Just looking within Jakarta, the following all jump out as initial code:
http://svn.apache.org/repos/asf/jakarta/commons/sandbox/servlet/ has a
couple of classes (as you know :) ).
Taglibs of course, I estimate half a dozen to ten taglibs.
Commons FileUploa.
Commons Http
(http://svn.apache.org/repos/asf/jakarta/commons/sandbox/http/trunk/src/java/org/apache/commons/http/)
which contains a browser detector class.
Commons Filters.
Hen
On Thu, 23 Jun 2005, Frank W. Zammetti wrote:
> In reading through this all, I have a concern that it will be difficult for
> any outside code to come in. Indeed it has proven difficult for many people
> I have spoken to to get code into any Commons project (although I myself had
> some things accepted, so clearly it is not impossible).
>
> What is the general feeling in terms of where the code comprising this
> package will come from? At least, the largest portion of it? Is the idea to
> take parts of other Jakarta and/or Apache projects as the source material, or
> is it to put more of an emphasis on outside contributions? The former sounds
> much more like the current Jakarta Commons concept, the later is something
> else.
>
> As someone who would like to contribute, I wouldn't want to see anything that
> makes that more difficult embraced. Just curious what everyone else is
> thinking...
>
> Frank
>
> robert burrell donkin wrote:
>> On Wed, 2005-06-22 at 14:40 -0700, Phil Steitz wrote:
>>
>> <snip>
>>
>>> I guess 18 refers to the sandbox? I do not understand what the intent of
>>> this is.
>>
>>
>> is boils down to the question: does this subproject need it's own
>> sandbox or will neophyte components start in the jakarta commons
>> sandbox?
>>
>> - robert
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: general-help@jakarta.apache.org
>>
>>
>>
>>
>>
>
> --
> Frank W. Zammetti
> Founder and Chief Software Architect
> Omnytex Technologies
> http://www.omnytex.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks
reusable in java web applications]
Posted by Phil Steitz <ph...@steitz.com>.
Frank W. Zammetti wrote:
> In reading through this all, I have a concern that it will be difficult
> for any outside code to come in. Indeed it has proven difficult for
> many people I have spoken to to get code into any Commons project
> (although I myself had some things accepted, so clearly it is not
> impossible).
This should be discussed on commons-dev if people really think it is an
issue. Maintaining scope boundaries and quality is a key concern there
(as it should be in the proposed project as well, IMHO), but *many*
patches do get applied.
>
> What is the general feeling in terms of where the code comprising this
> package will come from? At least, the largest portion of it?
The majority of the code should be developed collaboratively by the
community, using the mailing list, Wiki, svn and issue tracker (Bugzilla
or Jira) to discuss ideas and manage patches. Any significant
contribution that is not developed within apache would have to go
through the incubator before being integrated.
<snip/>
>> is boils down to the question: does this subproject need it's own
>> sandbox or will neophyte components start in the jakarta commons
>> sandbox?
I would not recommend reusing the j-c sandbox and I am not sure that I
like the "start components in the sandbox" approach that we use there.
Too many abandoned components that people start to use (and depend on)
despite disclaimers. With the ease of branching in svn, I am not sure
if a sandbox is really needed any more. In any case, I would not
recommend repeating the j-c practice of "incubating" new subprojects in
the sandbox. Just my HO.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org