Re: [PROPOSAL] Tiles as the seed for Jakarta Web Components
On Wed, 2006-04-26 at 11:48 -0400, Henri Yandell wrote: > The Web Components thread is much older than the recent set of threads, it > was back in 2005. So I don't think we've heard your reasons against a JWC > Sub-Project as opposed to the not-community-of-community threads. i have worries about any more formal sub-projects: they are too much like project mini-me's with their own formal structure. IMO the legal and formal structures are best aligned. i do like the idea of a JWC grouping or community within jakarta. with all the trappings that the old sub-projects had (mailing lists, web site and so on) but no separate classes of committers under the same pmc. i think a manifesto would be needed for each grouping (somewhere between guidelines and a charter) which should define the scope. > I can find this on wiki: > > http://wiki.apache.org/jakarta/CreatingCommonsForWebComponents > > which includes a charter - though I think the charter needs changing as > that's a copy of the Commons charter which is 5% charter and 95% > developer guidelines. IIRC the document on the wiki was intended to be the starting point for a charter. > I know we voted on the name, I thought we voted on the creation of the > subproject as part of that but would need to check archives. Will do that > in a bit. i seem to recall a vote but not sure what it was on... > On Wed, 26 Apr 2006, Andrew C. Oliver wrote: > > > No. There isn't a consensus. andrew's right that since he dissents, there isn't an absolute consensus. i do suspect that he's views are in the minority, though. we should push things forward until we have something concrete to vote on. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Tiles as the seed for Jakarta Web Components
On Wed, 2006-04-26 at 14:55 -0500, Greg Reddin wrote: > Sorry to be a latecomer to this thread. I've had some trouble > subscribing for whatever reason. But I just wanted to add that I am > working on Standalone Tiles over at the Struts project and am willing > to support it if it's moved to some Jakarta subproject. cool :) > I'll let you guys hash out how the community is structured :-) I haven't > participated in Jakarta enough lately to have an opinion. i'd hope we're not trying to structure the community, just the formal organisation supporting it. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Tiles as the seed for Jakarta Web Components
On Tue, 2006-04-25 at 22:54 -0700, Martin Cooper wrote: > On 4/25/06, Nathan Bubna <[EMAIL PROTECTED]> wrote: > > > > This sounds great, Martin. But if i may be forgiven a little > > semantic nitpicking, my understanding of previous discussions is that > > JWC would be a "grouping" rather than a "sub-project". So Tiles would > > be directly a Jakarta sub-project, rather than a sub-sub-project (i.e. > > becoming "Jakarta Tiles", not "Jakarta Web Components Tiles"). > > Yes, you are correct, Tiles would be a Jakarta sub-project within the JWC > grouping. I guess I was trying to simplify the proposal for those who > haven't paid as much attention to the whole grouping thing, but in > retrospect, that probably wasn't such a great idea. ;-) i'd prefer to move away from the term sub-project since it has negative formal associations. it can't be a project mini-me with formal structure of it's own. just a Jakarta component: separate product, same project, same formal organisational structure. AIUI (and it might be a good idea to check this out with PR) the naming guidelines mean that it should be Apache Tiles (not Jakarta Tiles or Jakarta Web Components Tiles). the reason for this is to ensure we can use trademark law to protect ourselves (if that's ever needed). IHMO Apache Tiles from the Jakarta Web Components team sounds pretty good anyway - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Tiles as the seed for Jakarta Web Components
Sorry to be a latecomer to this thread. I've had some trouble subscribing for whatever reason. But I just wanted to add that I am working on Standalone Tiles over at the Struts project and am willing to support it if it's moved to some Jakarta subproject.I'll let you guys hash out how the community is structured :-) I haven't participated in Jakarta enough lately to have an opinion. Greg On Apr 26, 2006, at 10:48 AM, Henri Yandell wrote: The Web Components thread is much older than the recent set of threads, it was back in 2005. So I don't think we've heard your reasons against a JWC Sub-Project as opposed to the not-community- of-community threads. I can find this on wiki: http://wiki.apache.org/jakarta/CreatingCommonsForWebComponents which includes a charter - though I think the charter needs changing as that's a copy of the Commons charter which is 5% charter and 95% developer guidelines. I know we voted on the name, I thought we voted on the creation of the subproject as part of that but would need to check archives. Will do that in a bit. Hen On Wed, 26 Apr 2006, Andrew C. Oliver wrote: No. There isn't a consensus. Just you guys REALLY REALLY want it to happen. Do not mistake one for the other. I did pay attention. Yet feel the issue has not been sufficiently addressed thus I'm -1 for all the previously stated reasons in all of the vaguely alluded to threads for all the reasons stated previously that I still feel are not addressed. -Andy Martin Cooper wrote: On 4/25/06, Andrew C. Oliver <[EMAIL PROTECTED]> wrote: I'd be against another commons style sub-community. Unless you can show me a defined scope, "web components" means nothing, then expect my objection. Understood. A formal scope does need to be written down and agreed upon. However, I believe that concensus on the gist of such a scope has already happened, between the lines, in the numerous previous threads on JWC on various lists. -- Martin Cooper -Andy James Mitchell wrote: I believe that this would be a great way to bootstrap this new community. If this were a formal vote, then I, as both a Struts PMC and a Jakarta PMC member, would throw a binding +1 your way. -- James Mitchell On Apr 24, 2006, at 11:56 PM, Martin Cooper wrote: There has been considerable discussion, on this list and others, about the creation of a Jakarta Web Components sub-project (also previously known as Jakarta Silk). I believe the concensus has been in favour of creating it. However, we seemed to get bogged down, several times, in discussions of the name, or of exactly which pieces of Jakarta Commons, Jakarta Taglibs, etc., should move to the new sub-project. Meanwhile, over at Struts, we have had a number of discussions about the future of Tiles[1], currently a Struts sub-project. We have been working hard to make Tiles independent of Struts, and are close to achieving that goal. With Tiles no longer depending on Struts, it makes little sense for it to remain a part of the Struts project. In fact, it is much more likely to flourish outside of Struts. The proposal, then, is to create the Jakarta Web Components sub-project, and make Tiles the first citizen of that sub-project. This simultaneously achieves several objectives: 1) We actually get started with the Jakarta Web Components sub- project. 2) We can defer discussion of which other parts of Jakarta move there. 3) We create a logical home for the now-Struts-independent Tiles. While Tiles is a powerful templating framework, it is actually a fairly small code base, making it a good candidate for an independent web component. It is still being developed, so we would not be seeding Jakarta Web Components with a dormant component. Several of the Struts committers (many of whom are already Jakarta committers) would come here to continue working on Tiles, and to help build the Jakarta Web Components sub-project. Once Jakarta Web Components is up and running, it would, of course, be up to the various communities surrounding Commons and Taglibs components, and potentially other Jakarta sub-projects, as to whether or not they choose to join the new sub-project. The goal of this proposal is simply to seed the sub-project and get the ball rolling. Comments? -- --- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAI
Re: [PROPOSAL] Tiles as the seed for Jakarta Web Components
The Web Components thread is much older than the recent set of threads, it was back in 2005. So I don't think we've heard your reasons against a JWC Sub-Project as opposed to the not-community-of-community threads. I can find this on wiki: http://wiki.apache.org/jakarta/CreatingCommonsForWebComponents which includes a charter - though I think the charter needs changing as that's a copy of the Commons charter which is 5% charter and 95% developer guidelines. I know we voted on the name, I thought we voted on the creation of the subproject as part of that but would need to check archives. Will do that in a bit. Hen On Wed, 26 Apr 2006, Andrew C. Oliver wrote: No. There isn't a consensus. Just you guys REALLY REALLY want it to happen. Do not mistake one for the other. I did pay attention. Yet feel the issue has not been sufficiently addressed thus I'm -1 for all the previously stated reasons in all of the vaguely alluded to threads for all the reasons stated previously that I still feel are not addressed. -Andy Martin Cooper wrote: On 4/25/06, Andrew C. Oliver <[EMAIL PROTECTED]> wrote: I'd be against another commons style sub-community. Unless you can show me a defined scope, "web components" means nothing, then expect my objection. Understood. A formal scope does need to be written down and agreed upon. However, I believe that concensus on the gist of such a scope has already happened, between the lines, in the numerous previous threads on JWC on various lists. -- Martin Cooper -Andy James Mitchell wrote: I believe that this would be a great way to bootstrap this new community. If this were a formal vote, then I, as both a Struts PMC and a Jakarta PMC member, would throw a binding +1 your way. -- James Mitchell On Apr 24, 2006, at 11:56 PM, Martin Cooper wrote: There has been considerable discussion, on this list and others, about the creation of a Jakarta Web Components sub-project (also previously known as Jakarta Silk). I believe the concensus has been in favour of creating it. However, we seemed to get bogged down, several times, in discussions of the name, or of exactly which pieces of Jakarta Commons, Jakarta Taglibs, etc., should move to the new sub-project. Meanwhile, over at Struts, we have had a number of discussions about the future of Tiles[1], currently a Struts sub-project. We have been working hard to make Tiles independent of Struts, and are close to achieving that goal. With Tiles no longer depending on Struts, it makes little sense for it to remain a part of the Struts project. In fact, it is much more likely to flourish outside of Struts. The proposal, then, is to create the Jakarta Web Components sub-project, and make Tiles the first citizen of that sub-project. This simultaneously achieves several objectives: 1) We actually get started with the Jakarta Web Components sub-project. 2) We can defer discussion of which other parts of Jakarta move there. 3) We create a logical home for the now-Struts-independent Tiles. While Tiles is a powerful templating framework, it is actually a fairly small code base, making it a good candidate for an independent web component. It is still being developed, so we would not be seeding Jakarta Web Components with a dormant component. Several of the Struts committers (many of whom are already Jakarta committers) would come here to continue working on Tiles, and to help build the Jakarta Web Components sub-project. Once Jakarta Web Components is up and running, it would, of course, be up to the various communities surrounding Commons and Taglibs components, and potentially other Jakarta sub-projects, as to whether or not they choose to join the new sub-project. The goal of this proposal is simply to seed the sub-project and get the ball rolling. Comments? - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Tiles as the seed for Jakarta Web Components
No. There isn't a consensus. Just you guys REALLY REALLY want it to happen. Do not mistake one for the other. I did pay attention. Yet feel the issue has not been sufficiently addressed thus I'm -1 for all the previously stated reasons in all of the vaguely alluded to threads for all the reasons stated previously that I still feel are not addressed. -Andy Martin Cooper wrote: On 4/25/06, Andrew C. Oliver <[EMAIL PROTECTED]> wrote: I'd be against another commons style sub-community. Unless you can show me a defined scope, "web components" means nothing, then expect my objection. Understood. A formal scope does need to be written down and agreed upon. However, I believe that concensus on the gist of such a scope has already happened, between the lines, in the numerous previous threads on JWC on various lists. -- Martin Cooper -Andy James Mitchell wrote: I believe that this would be a great way to bootstrap this new community. If this were a formal vote, then I, as both a Struts PMC and a Jakarta PMC member, would throw a binding +1 your way. -- James Mitchell On Apr 24, 2006, at 11:56 PM, Martin Cooper wrote: There has been considerable discussion, on this list and others, about the creation of a Jakarta Web Components sub-project (also previously known as Jakarta Silk). I believe the concensus has been in favour of creating it. However, we seemed to get bogged down, several times, in discussions of the name, or of exactly which pieces of Jakarta Commons, Jakarta Taglibs, etc., should move to the new sub-project. Meanwhile, over at Struts, we have had a number of discussions about the future of Tiles[1], currently a Struts sub-project. We have been working hard to make Tiles independent of Struts, and are close to achieving that goal. With Tiles no longer depending on Struts, it makes little sense for it to remain a part of the Struts project. In fact, it is much more likely to flourish outside of Struts. The proposal, then, is to create the Jakarta Web Components sub-project, and make Tiles the first citizen of that sub-project. This simultaneously achieves several objectives: 1) We actually get started with the Jakarta Web Components sub-project. 2) We can defer discussion of which other parts of Jakarta move there. 3) We create a logical home for the now-Struts-independent Tiles. While Tiles is a powerful templating framework, it is actually a fairly small code base, making it a good candidate for an independent web component. It is still being developed, so we would not be seeding Jakarta Web Components with a dormant component. Several of the Struts committers (many of whom are already Jakarta committers) would come here to continue working on Tiles, and to help build the Jakarta Web Components sub-project. Once Jakarta Web Components is up and running, it would, of course, be up to the various communities surrounding Commons and Taglibs components, and potentially other Jakarta sub-projects, as to whether or not they choose to join the new sub-project. The goal of this proposal is simply to seed the sub-project and get the ball rolling. Comments? - 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: [PROPOSAL] Tiles as the seed for Jakarta Web Components
On 4/25/06, Nathan Bubna <[EMAIL PROTECTED]> wrote: > > This sounds great, Martin. But if i may be forgiven a little > semantic nitpicking, my understanding of previous discussions is that > JWC would be a "grouping" rather than a "sub-project". So Tiles would > be directly a Jakarta sub-project, rather than a sub-sub-project (i.e. > becoming "Jakarta Tiles", not "Jakarta Web Components Tiles"). Yes, you are correct, Tiles would be a Jakarta sub-project within the JWC grouping. I guess I was trying to simplify the proposal for those who haven't paid as much attention to the whole grouping thing, but in retrospect, that probably wasn't such a great idea. ;-) I do also like Andrew's term "sub-community" as that describes the > true intent of having these "groupings". > > As far as a formal scope to be attached to the Jakarta Web Components > group goes, i would propose that members of the JWC should be java > components developed primarily for use in the development of web > applications. That's a good start. I'm not sure it's enough, but we could start from there. -- Martin Cooper On 4/24/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > > There has been considerable discussion, on this list and others, about > the > > creation of a Jakarta Web Components sub-project (also previously known > as > > Jakarta Silk). I believe the concensus has been in favour of creating > it. > > However, we seemed to get bogged down, several times, in discussions of > the > > name, or of exactly which pieces of Jakarta Commons, Jakarta Taglibs, > etc., > > should move to the new sub-project. > > > > Meanwhile, over at Struts, we have had a number of discussions about the > > future of Tiles[1], currently a Struts sub-project. We have been working > > hard to make Tiles independent of Struts, and are close to achieving > that > > goal. With Tiles no longer depending on Struts, it makes little sense > for it > > to remain a part of the Struts project. In fact, it is much more likely > to > > flourish outside of Struts. > > > > The proposal, then, is to create the Jakarta Web Components sub-project, > and > > make Tiles the first citizen of that sub-project. This simultaneously > > achieves several objectives: > > > > 1) We actually get started with the Jakarta Web Components sub-project. > > 2) We can defer discussion of which other parts of Jakarta move there. > > 3) We create a logical home for the now-Struts-independent Tiles. > > > > While Tiles is a powerful templating framework, it is actually a fairly > > small code base, making it a good candidate for an independent web > > component. It is still being developed, so we would not be seeding > Jakarta > > Web Components with a dormant component. Several of the Struts > committers > > (many of whom are already Jakarta committers) would come here to > continue > > working on Tiles, and to help build the Jakarta Web Components > sub-project. > > > > Once Jakarta Web Components is up and running, it would, of course, be > up to > > the various communities surrounding Commons and Taglibs components, and > > potentially other Jakarta sub-projects, as to whether or not they choose > to > > join the new sub-project. The goal of this proposal is simply to seed > the > > sub-project and get the ball rolling. > > > > Comments? > > > > -- > > Martin Cooper > > > > [1] http://struts.apache.org/struts-action/struts-tiles/ > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: [PROPOSAL] Tiles as the seed for Jakarta Web Components
On 4/25/06, Andrew C. Oliver <[EMAIL PROTECTED]> wrote: > > I'd be against another commons style sub-community. Unless you can show > me > a defined scope, "web components" means nothing, then expect my objection. Understood. A formal scope does need to be written down and agreed upon. However, I believe that concensus on the gist of such a scope has already happened, between the lines, in the numerous previous threads on JWC on various lists. -- Martin Cooper -Andy > > James Mitchell wrote: > > I believe that this would be a great way to bootstrap this new > community. > > > > If this were a formal vote, then I, as both a Struts PMC and a Jakarta > > PMC member, would throw a binding +1 your way. > > > > -- > > James Mitchell > > > > > > > > > > On Apr 24, 2006, at 11:56 PM, Martin Cooper wrote: > > > >> There has been considerable discussion, on this list and others, about > >> the > >> creation of a Jakarta Web Components sub-project (also previously > >> known as > >> Jakarta Silk). I believe the concensus has been in favour of creating > it. > >> However, we seemed to get bogged down, several times, in discussions > >> of the > >> name, or of exactly which pieces of Jakarta Commons, Jakarta Taglibs, > >> etc., > >> should move to the new sub-project. > >> > >> Meanwhile, over at Struts, we have had a number of discussions about > the > >> future of Tiles[1], currently a Struts sub-project. We have been > working > >> hard to make Tiles independent of Struts, and are close to achieving > that > >> goal. With Tiles no longer depending on Struts, it makes little sense > >> for it > >> to remain a part of the Struts project. In fact, it is much more > >> likely to > >> flourish outside of Struts. > >> > >> The proposal, then, is to create the Jakarta Web Components > >> sub-project, and > >> make Tiles the first citizen of that sub-project. This simultaneously > >> achieves several objectives: > >> > >> 1) We actually get started with the Jakarta Web Components sub-project. > >> 2) We can defer discussion of which other parts of Jakarta move there. > >> 3) We create a logical home for the now-Struts-independent Tiles. > >> > >> While Tiles is a powerful templating framework, it is actually a fairly > >> small code base, making it a good candidate for an independent web > >> component. It is still being developed, so we would not be seeding > >> Jakarta > >> Web Components with a dormant component. Several of the Struts > committers > >> (many of whom are already Jakarta committers) would come here to > continue > >> working on Tiles, and to help build the Jakarta Web Components > >> sub-project. > >> > >> Once Jakarta Web Components is up and running, it would, of course, be > >> up to > >> the various communities surrounding Commons and Taglibs components, and > >> potentially other Jakarta sub-projects, as to whether or not they > >> choose to > >> join the new sub-project. The goal of this proposal is simply to seed > the > >> sub-project and get the ball rolling. > >> > >> Comments? > > > > > > - > > 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: [PROPOSAL] Tiles as the seed for Jakarta Web Components
This sounds great, Martin. But if i may be forgiven a little semantic nitpicking, my understanding of previous discussions is that JWC would be a "grouping" rather than a "sub-project". So Tiles would be directly a Jakarta sub-project, rather than a sub-sub-project (i.e. becoming "Jakarta Tiles", not "Jakarta Web Components Tiles"). I do also like Andrew's term "sub-community" as that describes the true intent of having these "groupings". As far as a formal scope to be attached to the Jakarta Web Components group goes, i would propose that members of the JWC should be java components developed primarily for use in the development of web applications. On 4/24/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > There has been considerable discussion, on this list and others, about the > creation of a Jakarta Web Components sub-project (also previously known as > Jakarta Silk). I believe the concensus has been in favour of creating it. > However, we seemed to get bogged down, several times, in discussions of the > name, or of exactly which pieces of Jakarta Commons, Jakarta Taglibs, etc., > should move to the new sub-project. > > Meanwhile, over at Struts, we have had a number of discussions about the > future of Tiles[1], currently a Struts sub-project. We have been working > hard to make Tiles independent of Struts, and are close to achieving that > goal. With Tiles no longer depending on Struts, it makes little sense for it > to remain a part of the Struts project. In fact, it is much more likely to > flourish outside of Struts. > > The proposal, then, is to create the Jakarta Web Components sub-project, and > make Tiles the first citizen of that sub-project. This simultaneously > achieves several objectives: > > 1) We actually get started with the Jakarta Web Components sub-project. > 2) We can defer discussion of which other parts of Jakarta move there. > 3) We create a logical home for the now-Struts-independent Tiles. > > While Tiles is a powerful templating framework, it is actually a fairly > small code base, making it a good candidate for an independent web > component. It is still being developed, so we would not be seeding Jakarta > Web Components with a dormant component. Several of the Struts committers > (many of whom are already Jakarta committers) would come here to continue > working on Tiles, and to help build the Jakarta Web Components sub-project. > > Once Jakarta Web Components is up and running, it would, of course, be up to > the various communities surrounding Commons and Taglibs components, and > potentially other Jakarta sub-projects, as to whether or not they choose to > join the new sub-project. The goal of this proposal is simply to seed the > sub-project and get the ball rolling. > > Comments? > > -- > Martin Cooper > > [1] http://struts.apache.org/struts-action/struts-tiles/ > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Tiles as the seed for Jakarta Web Components
I'd be against another commons style sub-community. Unless you can show me a defined scope, "web components" means nothing, then expect my objection. -Andy James Mitchell wrote: I believe that this would be a great way to bootstrap this new community. If this were a formal vote, then I, as both a Struts PMC and a Jakarta PMC member, would throw a binding +1 your way. -- James Mitchell On Apr 24, 2006, at 11:56 PM, Martin Cooper wrote: There has been considerable discussion, on this list and others, about the creation of a Jakarta Web Components sub-project (also previously known as Jakarta Silk). I believe the concensus has been in favour of creating it. However, we seemed to get bogged down, several times, in discussions of the name, or of exactly which pieces of Jakarta Commons, Jakarta Taglibs, etc., should move to the new sub-project. Meanwhile, over at Struts, we have had a number of discussions about the future of Tiles[1], currently a Struts sub-project. We have been working hard to make Tiles independent of Struts, and are close to achieving that goal. With Tiles no longer depending on Struts, it makes little sense for it to remain a part of the Struts project. In fact, it is much more likely to flourish outside of Struts. The proposal, then, is to create the Jakarta Web Components sub-project, and make Tiles the first citizen of that sub-project. This simultaneously achieves several objectives: 1) We actually get started with the Jakarta Web Components sub-project. 2) We can defer discussion of which other parts of Jakarta move there. 3) We create a logical home for the now-Struts-independent Tiles. While Tiles is a powerful templating framework, it is actually a fairly small code base, making it a good candidate for an independent web component. It is still being developed, so we would not be seeding Jakarta Web Components with a dormant component. Several of the Struts committers (many of whom are already Jakarta committers) would come here to continue working on Tiles, and to help build the Jakarta Web Components sub-project. Once Jakarta Web Components is up and running, it would, of course, be up to the various communities surrounding Commons and Taglibs components, and potentially other Jakarta sub-projects, as to whether or not they choose to join the new sub-project. The goal of this proposal is simply to seed the sub-project and get the ball rolling. Comments? - 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: [PROPOSAL] Tiles as the seed for Jakarta Web Components
I believe that this would be a great way to bootstrap this new community. If this were a formal vote, then I, as both a Struts PMC and a Jakarta PMC member, would throw a binding +1 your way. -- James Mitchell On Apr 24, 2006, at 11:56 PM, Martin Cooper wrote: There has been considerable discussion, on this list and others, about the creation of a Jakarta Web Components sub-project (also previously known as Jakarta Silk). I believe the concensus has been in favour of creating it. However, we seemed to get bogged down, several times, in discussions of the name, or of exactly which pieces of Jakarta Commons, Jakarta Taglibs, etc., should move to the new sub-project. Meanwhile, over at Struts, we have had a number of discussions about the future of Tiles[1], currently a Struts sub-project. We have been working hard to make Tiles independent of Struts, and are close to achieving that goal. With Tiles no longer depending on Struts, it makes little sense for it to remain a part of the Struts project. In fact, it is much more likely to flourish outside of Struts. The proposal, then, is to create the Jakarta Web Components sub- project, and make Tiles the first citizen of that sub-project. This simultaneously achieves several objectives: 1) We actually get started with the Jakarta Web Components sub- project. 2) We can defer discussion of which other parts of Jakarta move there. 3) We create a logical home for the now-Struts-independent Tiles. While Tiles is a powerful templating framework, it is actually a fairly small code base, making it a good candidate for an independent web component. It is still being developed, so we would not be seeding Jakarta Web Components with a dormant component. Several of the Struts committers (many of whom are already Jakarta committers) would come here to continue working on Tiles, and to help build the Jakarta Web Components sub- project. Once Jakarta Web Components is up and running, it would, of course, be up to the various communities surrounding Commons and Taglibs components, and potentially other Jakarta sub-projects, as to whether or not they choose to join the new sub-project. The goal of this proposal is simply to seed the sub-project and get the ball rolling. Comments? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PROPOSAL] Tiles as the seed for Jakarta Web Components
There has been considerable discussion, on this list and others, about the creation of a Jakarta Web Components sub-project (also previously known as Jakarta Silk). I believe the concensus has been in favour of creating it. However, we seemed to get bogged down, several times, in discussions of the name, or of exactly which pieces of Jakarta Commons, Jakarta Taglibs, etc., should move to the new sub-project. Meanwhile, over at Struts, we have had a number of discussions about the future of Tiles[1], currently a Struts sub-project. We have been working hard to make Tiles independent of Struts, and are close to achieving that goal. With Tiles no longer depending on Struts, it makes little sense for it to remain a part of the Struts project. In fact, it is much more likely to flourish outside of Struts. The proposal, then, is to create the Jakarta Web Components sub-project, and make Tiles the first citizen of that sub-project. This simultaneously achieves several objectives: 1) We actually get started with the Jakarta Web Components sub-project. 2) We can defer discussion of which other parts of Jakarta move there. 3) We create a logical home for the now-Struts-independent Tiles. While Tiles is a powerful templating framework, it is actually a fairly small code base, making it a good candidate for an independent web component. It is still being developed, so we would not be seeding Jakarta Web Components with a dormant component. Several of the Struts committers (many of whom are already Jakarta committers) would come here to continue working on Tiles, and to help build the Jakarta Web Components sub-project. Once Jakarta Web Components is up and running, it would, of course, be up to the various communities surrounding Commons and Taglibs components, and potentially other Jakarta sub-projects, as to whether or not they choose to join the new sub-project. The goal of this proposal is simply to seed the sub-project and get the ball rolling. Comments? -- Martin Cooper [1] http://struts.apache.org/struts-action/struts-tiles/
