Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]
On 6/25/05, Stephen Colebourne <[EMAIL PROTECTED]> wrote: > Rahul Akolkar wrote: > >>is boils down to the question: does this subproject need it's own > >>sandbox or will neophyte components start in the jakarta commons > >>sandbox? > > > > +1 for sandbox (non-binding) > > > > Its slightly hard to imagine anything otherwise, but maybe I'm just > > used to seeing how commons and taglibs work. If Taglibs join, we have > > a bunch of Taglibs in sandbox, they will need to be housed somewhere, > > and I don't see them migrating to commons sandbox ;-) Right? > > Yes, +1 to a sandbox. Although it can create issues, I think has more > benefits than downsides. +1 -- Martin Cooper > Stephen > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]
Rahul Akolkar wrote: is boils down to the question: does this subproject need it's own sandbox or will neophyte components start in the jakarta commons sandbox? +1 for sandbox (non-binding) Its slightly hard to imagine anything otherwise, but maybe I'm just used to seeing how commons and taglibs work. If Taglibs join, we have a bunch of Taglibs in sandbox, they will need to be housed somewhere, and I don't see them migrating to commons sandbox ;-) Right? Yes, +1 to a sandbox. Although it can create issues, I think has more benefits than downsides. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]
I would love to see a very light weight WebDAV servlet which could be taken from Tomcat. Oliver On 6/24/05, Henri Yandell <[EMAIL PROTECTED]> 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: > >> > >> > >> > >>> 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: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > >> > >> > > > > -- > > Frank W. Zammetti > > Founder and Chief Software Architect > > Omnytex Technologies > > http://www.omnytex.com > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]
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. 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]
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: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]
On 6/23/05, robert burrell donkin <[EMAIL PROTECTED]> wrote: > On Wed, 2005-06-22 at 14:40 -0700, Phil Steitz wrote: > > > > > 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? +1 for sandbox (non-binding) Its slightly hard to imagine anything otherwise, but maybe I'm just used to seeing how commons and taglibs work. If Taglibs join, we have a bunch of Taglibs in sandbox, they will need to be housed somewhere, and I don't see them migrating to commons sandbox ;-) Right? -Rahul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]
On Wed, 2005-06-22 at 14:40 -0700, Phil Steitz wrote: > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
