You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Wendy Smoak <ws...@gmail.com> on 2006/11/21 00:20:51 UTC

Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

On 11/20/06, David H. DeWolf <dd...@apache.org> wrote:
> How about getting an initial tiles release out so that the 2.0.2 tiles
> plugin can rely upon it instead of a snapshot? It would probably only be
> 'alpha' quality at this point, but the same snapshot logic that you
> described below applies to it.
>
> I'll do the release (prior to the weekend), if someone that's done one
> before will help me through it.

Tiles 2 is in the sandbox, and sandbox projects are not allowed to do
releases.  Choosing a particular snapshot for Struts 2 to depend on is
all we can do, unless we change the rules.

If Tiles is ready to graduate, then we need to decide where it's going
to live.  Top level?  Over at Jakarta, or wasn't there some sort of
'web components' project being started?

-- 
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Greg Reddin <gr...@apache.org>.
On Nov 22, 2006, at 12:07 PM, Wendy Smoak wrote:

> Personally, I don't think it's a good idea for either _project_ (for
> Struts to be an umbrella project, or for Tiles 2 to be so closely
> associated with Struts.)  However, it seems to be the best choice
> right now for the people involved.

That's my feeling too.  I'd like to see it promoted on a temporary  
basis so it can get a release out without all the overhead of  
starting a whole new project.  I would consider its promotion  
temporary with the future view being a TLP or Jakarta subproject.

Greg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Wendy Smoak <ws...@gmail.com>.
On 11/22/06, David H. DeWolf <dd...@apache.org> wrote:

> Ok, so what should I do to drive this to a decision?  If we have any
> sort of consensus, I'd like try to get it done before the struts 2.0.2
> release so that we can have the tiles plugin use an alpha release.  That
> may not be doable at this point, but I'd like to at least try.
>
> Let me know if I'm trying to move to fast :)

Put a proposal on the wiki for some discussion and collaborative
editing, then post it to the dev list and call a vote?

Like Greg, I thought the general feeling was that Tiles 2 should not
be a Struts sub-project.

Personally, I don't think it's a good idea for either _project_ (for
Struts to be an umbrella project, or for Tiles 2 to be so closely
associated with Struts.)  However, it seems to be the best choice
right now for the people involved.

-- 
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Greg Reddin <gr...@apache.org>.
On Nov 22, 2006, at 11:55 AM, David H. DeWolf wrote:

> Ok, so what should I do to drive this to a decision?  If we have  
> any sort of consensus, I'd like try to get it done before the  
> struts 2.0.2 release so that we can have the tiles plugin use an  
> alpha release.  That may not be doable at this point, but I'd like  
> to at least try.

I think we just need a proposal and a vote :-)

I'd do it myself, but I just don't have time right at the moment.   
But I'll +1 it.

> Let me know if I'm trying to move to fast :)

Not at all.  The sooner the better.

Greg



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Antonio Petrelli <ap...@apache.org>.
Don Brown ha scritto:
> +0 with the caveat that its temporary nature is very clearly marked on 
> the Struts site.  We just finished fighting off the impression we are 
> a generic umbrella project, and I'd like to not go through that again.

Wiki just edited, it is the last sentence in the page.

Ciao
Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Don Brown <mr...@twdata.org>.
+0 with the caveat that its temporary nature is very clearly marked on 
the Struts site.  We just finished fighting off the impression we are a 
generic umbrella project, and I'd like to not go through that again.

Don

David H. DeWolf wrote:
> Please find the Tiles2 graduation proposal draft below.  I look 
> forward to your feedback . . .
>
> http://cwiki.apache.org/confluence/display/S2WIKI/Tiles2+Graduation+Proposal 
>
>
> David
>
> Martin Cooper wrote:
>>
>> Just write up a brief proposal that we can discuss, maybe on the 
>> wiki, as
>> Wendy suggested. Once we have that, we can bounce the idea around a 
>> bit and
>> then vote on it. IMO, it would be a good idea to include in the 
>> proposal a
>> bit about a Struts sub-project not being the intended final home for 
>> Tiles
>> but rather an intermediate step in the process of growing up. You could
>> mention options for a final home, but I personally don't feel that we 
>> need
>> to decide on that right now.
>>
>
>
> ---------------------------------------------------------------------
> 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: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by "David H. DeWolf" <dd...@apache.org>.
I know I might miss the struts2 release, but I'm going to let this sit 
at least another day or two since some people haven't had a ton of time 
to chime in and because of the US holiday this week. . .


David

David H. DeWolf wrote:
> Please find the Tiles2 graduation proposal draft below.  I look forward 
> to your feedback . . .
> 
> http://cwiki.apache.org/confluence/display/S2WIKI/Tiles2+Graduation+Proposal 
> 
> 
> David
> 
> Martin Cooper wrote:
>>
>> Just write up a brief proposal that we can discuss, maybe on the wiki, as
>> Wendy suggested. Once we have that, we can bounce the idea around a 
>> bit and
>> then vote on it. IMO, it would be a good idea to include in the 
>> proposal a
>> bit about a Struts sub-project not being the intended final home for 
>> Tiles
>> but rather an intermediate step in the process of growing up. You could
>> mention options for a final home, but I personally don't feel that we 
>> need
>> to decide on that right now.
>>
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Greg Reddin <gr...@apache.org>.
No problem.  I just haven't had time to formulate a response yet :-)
Greg

On Nov 27, 2006, at 2:02 PM, Ted Husted wrote:

> Sorry for the rant. I would have just sent the last two paragraphs,
> but the phone rang, and I pressed the wrong button :(
>
> On 11/27/06, Ted Husted <hu...@apache.org> wrote:
>> Here's the thing: If all these other projects depend on Tiles, then
>> why are they not contributing? If other people won't contribute to
>> Tiles in the sandbox, they won't contibute to Tiles as a Struts
>> subproject either. If the Tiles group wants to build community, then
>> cut the apron strings and move on.
>>
>> One approach would be to update the TLP proposal and draw up a
>> corresponding Commons Subproject proposal, and invite people from
>> other communites to sign up as a committer to one or the other. If we
>> want other people to contribute, then we should *invite* them to
>> contribute, and stop casting Tiles as a Struts thing.
>>
>> -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: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Ted Husted <hu...@apache.org>.
Sorry for the rant. I would have just sent the last two paragraphs,
but the phone rang, and I pressed the wrong button :(

On 11/27/06, Ted Husted <hu...@apache.org> wrote:
> Here's the thing: If all these other projects depend on Tiles, then
> why are they not contributing? If other people won't contribute to
> Tiles in the sandbox, they won't contibute to Tiles as a Struts
> subproject either. If the Tiles group wants to build community, then
> cut the apron strings and move on.
>
> One approach would be to update the TLP proposal and draw up a
> corresponding Commons Subproject proposal, and invite people from
> other communites to sign up as a committer to one or the other. If we
> want other people to contribute, then we should *invite* them to
> contribute, and stop casting Tiles as a Struts thing.
>
> -Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Ted Husted <hu...@apache.org>.
On 11/27/06, Greg Reddin <gr...@apache.org> wrote:
> > To create community, a codebase needs to stand on its own or be part
> > of a larger umbrella project, like the Commons or the ASF itself.
>
> I agree.  I don't see this move as building community.  It's just a
> stepping stone on the path to independence.

The sandbox was suppose to be the stepping stone. The original idea
was to separate the Tiles code base so that it could apply for TLP
status.

* http://wiki.apache.org/struts/TilesTopLevel

:) Now, we're asking for a stepping-stone for the stepping-stone. :)

Struts is *not* an incubator. We tried the Shale thing as a courtesy
to the JSF specification, but it was not our original intention to be
a "stepping stone" for Shale, and there's no reason to make that same
blunder with Tiles.

If the Tiles group wants to release, then apply to the Jakarta Commons
as one it's "server-based" components, or to the board for a TLP. In
the alternative, move the o.a.t package to the plugin, and release it
with Struts 2.

People used to lug around the entire Struts JAR just to access Tiles.
Being able to just snag the plugin is huge improvement over what we
have in Struts 1.3. It may not be the final solution, but it is as
good an interim solution as an interim subproject.

>From an infrastructure standpoint, the only and only difference
between a subproject and a plugin is that Tiles would not have its own
release cycle. As a subproject, it still won't have its own lists or
JIRA instance. Anyone interested in Tiles will still have to wade
through all the Struts stuff. As a subproject, all Tiles will have is
a homepage, and a plugin could have a home page too, if we want.

Here's the thing: If all these other projects depend on Tiles, then
why are they not contributing? If other people won't contribute to
Tiles in the sandbox, they won't contibute to Tiles as a Struts
subproject either. If the Tiles group wants to build community, then
cut the apron strings and move on.

One approach would be to update the TLP proposal and draw up a
corresponding Commons Subproject proposal, and invite people from
other communites to sign up as a committer to one or the other. If we
want other people to contribute, then we should *invite* them to
contribute, and stop casting Tiles as a Struts thing.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Greg Reddin <gr...@apache.org>.
On Nov 25, 2006, at 9:32 AM, Ted Husted wrote:

> Could we also document the alternative of moving the org.apache.tiles
> packages *into* the struts2-plugin?
>
> The proposal cites three problems:
>
> 1 Can't release
> 2 Not visible
> 3 Not permanent
>
> As part of the Struts2 Plugin, problems 1 and 2 will be solved.

The problem I'm most concerned about with this proposal is problem  
1.  Our main goal here is to find a point where we stop adding  
revolutionary features and start moving towards a GA release.  To me  
the most urgent "visibility" problem is that people can't download an  
actual Tiles release.  They have to download a snapshot build.  So  
the Struts 2 plugin and the Shale view handler have to depend on a  
snapshot release.  Other projects, like MyFaces, just depend on Tiles  
1.x.  My initial goal is to give people a Tiles 2.0.0 that is an  
Alpha-quality release and I think the other Tiles developers are on  
the same page.

> If all we want to do is separate Tiles from the core, then mission
> accomplished, put the packages back into the plugin.

I disagree.  If we do that Tiles is not standalone anymore and the  
mission is no longer accomplished.  Tiles 2 currently has no  
dependencies on Struts and contains no integration code with any  
other framework.  Integration with another framework is provided by  
the other framework.  That's the whole idea of making it  
"standalone".  If we put the packages into the plugin it now has an  
integration layer with Struts 2.  When we decide where it will  
ultimately live we will have to separate the plugin from the core  
Tiles framework.  That means separating codebase, test cases, doc,  
build files, etc.

I want to keep Tiles standalone, graduate so we can release an alpha,  
then put our focus into knocking out the rest of the issues and  
deciding where the permanent project will live.

> Realistically, making Tiles a subproject is not going to suddenly
> create community interest in the codebase. That didn't happen for the
> other subprojects, that we later merged back into Struts 1, it really
> didn't happen for Shale either, and it's unlikely to happen to Tiles.
>
> To create community, a codebase needs to stand on its own or be part
> of a larger umbrella project, like the Commons or the ASF itself.

I agree.  I don't see this move as building community.  It's just a  
stepping stone on the path to independence.

> As part of the Struts 2 plugin, other projects, like Shale, and
> Spring, and WebWork, would be able to make use of Tiles, which is the
> primary goal. We can make the Tiles plugin as visible as we want it to
> be, and it will be just as easy to promote Tiles to TLP later,  should
> other developers materialize (or remateralize).

Yes, but then the plugin would be part of Tiles.  I personally don't  
want that and I think that goes against the original reason for  
creating the standalone Tiles project.

I'm OK with listing Jakarta Commons as a home for Tiles, as well as a  
new Jakarta Subproject or even TLP for Web Components.  I'm also OK  
with listing the s2 plugin as an option, even though it's not an  
option I'm in favor of.  But our focus here is not trying to find the  
permanent home for Tiles.  We are intentionally leaving that question  
open for the time being and trying to move Tiles to a place where it  
will stabilize.

The reason the subproject appeals to me is that we can simply copy  
the tiles sandbox svn tree out of the sandbox and cut an alpha  
release.  Then we can start trying to answer the bigger questions.   
Any other path either 1) takes us backwards with regard to  
independence (struts2-plugin) or 2) requires a whole lot more  
community-building and red tape before we can move any further  
(jakarta, TLP, etc.).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Ted Husted <hu...@apache.org>.
On 11/24/06, David H. DeWolf <dd...@apache.org> wrote:
> For the sake of documentation, I'll go ahead and take some of these (and
> Ted's) points regarding where to go upon graduation and post them to the
> wiki.
>
> Thanks everyone for your continued input. . .

Could we also document the alternative of moving the org.apache.tiles
packages *into* the struts2-plugin?

The proposal cites three problems:

1 Can't release
2 Not visible
3 Not permanent

As part of the Struts2 Plugin, problems 1 and 2 will be solved.

Problem 3 is *not* solved by making Tiles a subproject. If anything,
it muddies the water, since I don't think anyone believes that a
subproject is an acceptable longterm solution.

If all we want to do is separate Tiles from the core, then mission
accomplished, put the packages back into the plugin. If we want to
attract a larger community, then we have to get Tiles out from under
the shadow of Struts.

Realistically, making Tiles a subproject is not going to suddenly
create community interest in the codebase. That didn't happen for the
other subprojects, that we later merged back into Struts 1, it really
didn't happen for Shale either, and it's unlikely to happen to Tiles.

To create community, a codebase needs to stand on its own or be part
of a larger umbrella project, like the Commons or the ASF itself.
Struts has proven to be a poor umbrella in the past, and there's no
reason to believe that would change.

As part of the Struts 2 plugin, other projects, like Shale, and
Spring, and WebWork, would be able to make use of Tiles, which is the
primary goal. We can make the Tiles plugin as visible as we want it to
be, and it will be just as easy to promote Tiles to TLP later,  should
other developers materialize (or remateralize).

We would just need to make it clear that Struts 2 is not the only
target platform for the Tiles plugin.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Mitchell James <jm...@gmail.com>.
I know I'd like to see Tiles live on its own somewhere other than  
here.  Tiles has forever been associated with Struts, and while the  
code is now independent of Struts, just being here makes it "part of  
Struts" in many people's minds.

I'd be +1 for Tiles going TLP, and if that means first going through  
Jakarta, I also have a binding vote there as well.

--
James Mitchell
678.910.8017




On Nov 24, 2006, at 9:51 PM, David H. DeWolf wrote:

> For the sake of documentation, I'll go ahead and take some of these  
> (and Ted's) points regarding where to go upon graduation and post  
> them to the wiki.
>
> Thanks everyone for your continued input. . .
>
>
> David
>
> Niall Pemberton wrote:
>> If tiles can achieve the critical mass to become a TLP then IMO that
>> would be the best solution - at this point it looks at least a couple
>> of devs short of that. In the meantime its question of "where can it
>> do its growing?". Commons makes less sense to me than staying here
>> since theres definetly already a community here interested in Tiles -
>> in Commons we don't know how interested the community would be and I
>> doubt it would ever match here. Add to that the fact that the 3
>> interested developers are already Struts developers - but not Commons
>> developers and the fact that tiles resources (repository & bugs) are
>> already here staying here for the time being looks like the best
>> option.
>> I can only think of reasons why it would be better for tiles to  
>> remain
>> in Struts rather than Commons. If there is a case for moving tiles to
>> Commons, then its yet to be made for me.
>> Making it a Struts2 sub-project seems like a backward step - what
>> would have been the point of emarking on a "standalone tiles" if the
>> end result is for it to just move from being part of Struts1 to part
>> of Strus2? Again if there are the benefits of doing this then they
>> need to be laid out.
>> I really can't see the point of making alternative suggestions  
>> without
>> making the case for them. I can see benefts for tiles being
>> (temporarily) a Struts sub-project....
>> - theres an interested community here
>> - the active developers are here
>> - the other developers here all know what tiles is about (to  
>> varying degrees)
>> - theres a PMC that knows the software
>> ...and unless someone else makes a better case for an alternative  
>> then
>> thats the best option IMO
>> Niall
>> On 11/24/06, Ted Husted <hu...@apache.org> wrote:
>>> When we invented the Commons, it was not our intention to exclude  
>>> "web
>>> components". If we had even suggested such a thing, I doubt that the
>>> Jakarta PMC would have approved our proposal. At the time, we  
>>> took the
>>> notion that ASF projects were suppose to be tied to HTTPD very
>>> seriously. Of course, since then, we added many top-level projects
>>> that have little to do with HTTPD. But, that shouldn't mean web
>>> components have suddenly become second-class citizens. I believe  
>>> that
>>> the phrase "server-related" in the charter is meant to include web
>>> servers.
>>>
>>> Unless and until the Jakarta Commons PMC rejects a proposal from the
>>> Tiles group, I consider it to be a valid alternative to be explored,
>>> and until it's been fully explored, I will consider the proposal to
>>> create a Struts Tiles subproject premature.
>>>
>>> Others may think differently, but I am entitled (and even  
>>> obliged) to
>>> define what it is required to obtain my vote. (The vote need not be
>>> unanimous, but only a 3/4 majority of the PMC.)
>>>
>>> As it stands, the ASF's preferred unit of release is the TLP. If the
>>> Tiles group is not ready to become a TLP, and unwilling to even try
>>> and join the Commons, then I would suggest that Tiles is not  
>>> ready to
>>> "graduate".
>>>
>>> A third alternative (aside from an independant project) would be to
>>> bring Tiles back into the Struts 2 subproject as part of the Tiles
>>> plugin. If other projects want to use Tiles, they could just grab  
>>> the
>>> tiles-plugin.jar and import the appropriate packages. Rather than  
>>> fuss
>>> with a separate project or subproject, we could document how to use
>>> the Tiles JAR outside of the Struts 2 environment.
>>>
>>> If volunteers from other projects begin to contribute to Tiles, and
>>> want to *build* Tiles without importing the s2 core, then the Tiles
>>> group could then apply for TLP status, either to the board or though
>>> the Incubator. In the meantime, we could continue to handle Tiles
>>> matters on the mailing lists, just as we would for any plugin (or
>>> subproject).
>>>
>>> In any event, if it would be helpful, I see no reason why we can't
>>> create tagged builds of Tiles. A build is not a release,  
>>> regardless of
>>> whether we call it a "nightly", "snapshot", or "test".
>>>
>>> -Ted.
>>>
>>> On 11/23/06, Martin Cooper <ma...@apache.org> wrote:
>>> > On 11/23/06, Ted Husted <hu...@apache.org> wrote:
>>> > >
>>> > > I'd like to see the proposal discuss the alternatives to  
>>> becoming a
>>> > > Struts subproject. A good role for a proposal is to summarize  
>>> various
>>> > > threads. Becoming a subproject seems to be a foregone  
>>> conclusion of
>>> > > the proposal, with no discussion of the alternatives.
>>> >
>>> >
>>> > Well, yeah, that's what is being _proposed_. We did discuss the  
>>> options on
>>> > the mailing list, more than once, and came to the conclusion  
>>> that becoming a
>>> > Struts sub-project was the right interim step. I don't see that  
>>> we need to
>>> > have the discussion all over again just because the proposal  
>>> has been put on
>>> > the wiki.
>>> >
>>> > In previous threads, Jakarta was mentioned, but not so much the
>>> > > Jakarta Commons. Why is it that we are not proposing to move  
>>> Tiles to
>>> > > the Commons, as we did with the Validator, and others?
>>> >
>>> >
>>> > Sigh. We've had this discussion _lots_ of times already, and  
>>> we've had
>>> > similar discussions over in Commons. Jakarta Commons is not  
>>> about web
>>> > components, and people do not want it to be about web  
>>> components, which is
>>> > why the notion of Jakarta Web Components has been bandied about  
>>> so much.
>>> > Validator makes sense in Commons because it's not tied to the  
>>> web; the part
>>> > that does tie to the web is in Struts, not Validator. I, for  
>>> one, would not
>>> > want to propose Tiles as a Commons component, because I'm  
>>> almost certain it
>>> > would be rejected, and because I would vote against that myself.
>>> >
>>> > Also, Tiles might be able to become a TLP by resolution of the  
>>> board.
>>> > > The situation is not much different than Shale. The incubator is
>>> > > charged with "acceptance and oversight of new products  
>>> submitted or
>>> > > proposed to become part of the Foundation". Tiles is already  
>>> part of
>>> > > the foundation.
>>> >
>>> >
>>> > Yes, Tiles might be able to become a TLP, but it is my  
>>> perception that the
>>> > people involved are not ready for that. It behooves us to  
>>> provide better
>>> > options than either staying in the sandbox or going straight to  
>>> TLP. That
>>> > you bring up Shale is interesting; note that we went through  
>>> exactly the
>>> > same process with Shale as we are now proposing for Tiles.  
>>> Shale went from
>>> > the sandbox to a Struts sub-project first. Only later, once it  
>>> found its
>>> > feet as a sub-project, did it go off to TLP land.
>>> >
>>> > Speaking of the Incubator, we might also note that Incubator  
>>> podlings
>>> > > do have releases.
>>> > >
>>> > > Even without quantifying it as a "release", given the usual  
>>> release
>>> > > plan, Tiles could still create a tagged test-build. Before  
>>> deciding
>>> > > whether Tiles should be a subproject or not, I think I'd like  
>>> to see
>>> > > the volunteers create a test-build that could be a release if  
>>> the PMC
>>> > > gave the nod.
>>> >
>>> >
>>> > Why would we introduce a new rule for Tiles that we have never  
>>> imposed on
>>> > other projects coming out of the sandbox?
>>> >
>>> > Moving a code branch out the sandbox is a trivial task. What's not
>>> > > trivial is doing everything that's needed to turn a snapshot  
>>> into a
>>> > > potential release.
>>> >
>>> >
>>> > True. But that has never before been tied to promoting  
>>> something out of the
>>> > sandbox, and I don't think that introducing it in the midst of  
>>> a proposal,
>>> > after most of the discussion has already happened on the lists,  
>>> is a
>>> > productive thing to do.
>>> >
>>> > --
>>> > Martin Cooper
>>> >
>>> >
>>> > -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
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by "David H. DeWolf" <dd...@apache.org>.
For the sake of documentation, I'll go ahead and take some of these (and 
Ted's) points regarding where to go upon graduation and post them to the 
wiki.

Thanks everyone for your continued input. . .


David

Niall Pemberton wrote:
> If tiles can achieve the critical mass to become a TLP then IMO that
> would be the best solution - at this point it looks at least a couple
> of devs short of that. In the meantime its question of "where can it
> do its growing?". Commons makes less sense to me than staying here
> since theres definetly already a community here interested in Tiles -
> in Commons we don't know how interested the community would be and I
> doubt it would ever match here. Add to that the fact that the 3
> interested developers are already Struts developers - but not Commons
> developers and the fact that tiles resources (repository & bugs) are
> already here staying here for the time being looks like the best
> option.
> 
> I can only think of reasons why it would be better for tiles to remain
> in Struts rather than Commons. If there is a case for moving tiles to
> Commons, then its yet to be made for me.
> 
> Making it a Struts2 sub-project seems like a backward step - what
> would have been the point of emarking on a "standalone tiles" if the
> end result is for it to just move from being part of Struts1 to part
> of Strus2? Again if there are the benefits of doing this then they
> need to be laid out.
> 
> I really can't see the point of making alternative suggestions without
> making the case for them. I can see benefts for tiles being
> (temporarily) a Struts sub-project....
> 
> - theres an interested community here
> - the active developers are here
> - the other developers here all know what tiles is about (to varying 
> degrees)
> - theres a PMC that knows the software
> 
> ...and unless someone else makes a better case for an alternative then
> thats the best option IMO
> 
> Niall
> 
> On 11/24/06, Ted Husted <hu...@apache.org> wrote:
>> When we invented the Commons, it was not our intention to exclude "web
>> components". If we had even suggested such a thing, I doubt that the
>> Jakarta PMC would have approved our proposal. At the time, we took the
>> notion that ASF projects were suppose to be tied to HTTPD very
>> seriously. Of course, since then, we added many top-level projects
>> that have little to do with HTTPD. But, that shouldn't mean web
>> components have suddenly become second-class citizens. I believe that
>> the phrase "server-related" in the charter is meant to include web
>> servers.
>>
>> Unless and until the Jakarta Commons PMC rejects a proposal from the
>> Tiles group, I consider it to be a valid alternative to be explored,
>> and until it's been fully explored, I will consider the proposal to
>> create a Struts Tiles subproject premature.
>>
>> Others may think differently, but I am entitled (and even obliged) to
>> define what it is required to obtain my vote. (The vote need not be
>> unanimous, but only a 3/4 majority of the PMC.)
>>
>> As it stands, the ASF's preferred unit of release is the TLP. If the
>> Tiles group is not ready to become a TLP, and unwilling to even try
>> and join the Commons, then I would suggest that Tiles is not ready to
>> "graduate".
>>
>> A third alternative (aside from an independant project) would be to
>> bring Tiles back into the Struts 2 subproject as part of the Tiles
>> plugin. If other projects want to use Tiles, they could just grab the
>> tiles-plugin.jar and import the appropriate packages. Rather than fuss
>> with a separate project or subproject, we could document how to use
>> the Tiles JAR outside of the Struts 2 environment.
>>
>> If volunteers from other projects begin to contribute to Tiles, and
>> want to *build* Tiles without importing the s2 core, then the Tiles
>> group could then apply for TLP status, either to the board or though
>> the Incubator. In the meantime, we could continue to handle Tiles
>> matters on the mailing lists, just as we would for any plugin (or
>> subproject).
>>
>> In any event, if it would be helpful, I see no reason why we can't
>> create tagged builds of Tiles. A build is not a release, regardless of
>> whether we call it a "nightly", "snapshot", or "test".
>>
>> -Ted.
>>
>> On 11/23/06, Martin Cooper <ma...@apache.org> wrote:
>> > On 11/23/06, Ted Husted <hu...@apache.org> wrote:
>> > >
>> > > I'd like to see the proposal discuss the alternatives to becoming a
>> > > Struts subproject. A good role for a proposal is to summarize various
>> > > threads. Becoming a subproject seems to be a foregone conclusion of
>> > > the proposal, with no discussion of the alternatives.
>> >
>> >
>> > Well, yeah, that's what is being _proposed_. We did discuss the 
>> options on
>> > the mailing list, more than once, and came to the conclusion that 
>> becoming a
>> > Struts sub-project was the right interim step. I don't see that we 
>> need to
>> > have the discussion all over again just because the proposal has 
>> been put on
>> > the wiki.
>> >
>> > In previous threads, Jakarta was mentioned, but not so much the
>> > > Jakarta Commons. Why is it that we are not proposing to move Tiles to
>> > > the Commons, as we did with the Validator, and others?
>> >
>> >
>> > Sigh. We've had this discussion _lots_ of times already, and we've had
>> > similar discussions over in Commons. Jakarta Commons is not about web
>> > components, and people do not want it to be about web components, 
>> which is
>> > why the notion of Jakarta Web Components has been bandied about so 
>> much.
>> > Validator makes sense in Commons because it's not tied to the web; 
>> the part
>> > that does tie to the web is in Struts, not Validator. I, for one, 
>> would not
>> > want to propose Tiles as a Commons component, because I'm almost 
>> certain it
>> > would be rejected, and because I would vote against that myself.
>> >
>> > Also, Tiles might be able to become a TLP by resolution of the board.
>> > > The situation is not much different than Shale. The incubator is
>> > > charged with "acceptance and oversight of new products submitted or
>> > > proposed to become part of the Foundation". Tiles is already part of
>> > > the foundation.
>> >
>> >
>> > Yes, Tiles might be able to become a TLP, but it is my perception 
>> that the
>> > people involved are not ready for that. It behooves us to provide 
>> better
>> > options than either staying in the sandbox or going straight to TLP. 
>> That
>> > you bring up Shale is interesting; note that we went through exactly 
>> the
>> > same process with Shale as we are now proposing for Tiles. Shale 
>> went from
>> > the sandbox to a Struts sub-project first. Only later, once it found 
>> its
>> > feet as a sub-project, did it go off to TLP land.
>> >
>> > Speaking of the Incubator, we might also note that Incubator podlings
>> > > do have releases.
>> > >
>> > > Even without quantifying it as a "release", given the usual release
>> > > plan, Tiles could still create a tagged test-build. Before deciding
>> > > whether Tiles should be a subproject or not, I think I'd like to see
>> > > the volunteers create a test-build that could be a release if the PMC
>> > > gave the nod.
>> >
>> >
>> > Why would we introduce a new rule for Tiles that we have never 
>> imposed on
>> > other projects coming out of the sandbox?
>> >
>> > Moving a code branch out the sandbox is a trivial task. What's not
>> > > trivial is doing everything that's needed to turn a snapshot into a
>> > > potential release.
>> >
>> >
>> > True. But that has never before been tied to promoting something out 
>> of the
>> > sandbox, and I don't think that introducing it in the midst of a 
>> proposal,
>> > after most of the discussion has already happened on the lists, is a
>> > productive thing to do.
>> >
>> > --
>> > Martin Cooper
>> >
>> >
>> > -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: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Niall Pemberton <ni...@gmail.com>.
If tiles can achieve the critical mass to become a TLP then IMO that
would be the best solution - at this point it looks at least a couple
of devs short of that. In the meantime its question of "where can it
do its growing?". Commons makes less sense to me than staying here
since theres definetly already a community here interested in Tiles -
in Commons we don't know how interested the community would be and I
doubt it would ever match here. Add to that the fact that the 3
interested developers are already Struts developers - but not Commons
developers and the fact that tiles resources (repository & bugs) are
already here staying here for the time being looks like the best
option.

I can only think of reasons why it would be better for tiles to remain
in Struts rather than Commons. If there is a case for moving tiles to
Commons, then its yet to be made for me.

Making it a Struts2 sub-project seems like a backward step - what
would have been the point of emarking on a "standalone tiles" if the
end result is for it to just move from being part of Struts1 to part
of Strus2? Again if there are the benefits of doing this then they
need to be laid out.

I really can't see the point of making alternative suggestions without
making the case for them. I can see benefts for tiles being
(temporarily) a Struts sub-project....

- theres an interested community here
- the active developers are here
- the other developers here all know what tiles is about (to varying degrees)
- theres a PMC that knows the software

...and unless someone else makes a better case for an alternative then
thats the best option IMO

Niall

On 11/24/06, Ted Husted <hu...@apache.org> wrote:
> When we invented the Commons, it was not our intention to exclude "web
> components". If we had even suggested such a thing, I doubt that the
> Jakarta PMC would have approved our proposal. At the time, we took the
> notion that ASF projects were suppose to be tied to HTTPD very
> seriously. Of course, since then, we added many top-level projects
> that have little to do with HTTPD. But, that shouldn't mean web
> components have suddenly become second-class citizens. I believe that
> the phrase "server-related" in the charter is meant to include web
> servers.
>
> Unless and until the Jakarta Commons PMC rejects a proposal from the
> Tiles group, I consider it to be a valid alternative to be explored,
> and until it's been fully explored, I will consider the proposal to
> create a Struts Tiles subproject premature.
>
> Others may think differently, but I am entitled (and even obliged) to
> define what it is required to obtain my vote. (The vote need not be
> unanimous, but only a 3/4 majority of the PMC.)
>
> As it stands, the ASF's preferred unit of release is the TLP. If the
> Tiles group is not ready to become a TLP, and unwilling to even try
> and join the Commons, then I would suggest that Tiles is not ready to
> "graduate".
>
> A third alternative (aside from an independant project) would be to
> bring Tiles back into the Struts 2 subproject as part of the Tiles
> plugin. If other projects want to use Tiles, they could just grab the
> tiles-plugin.jar and import the appropriate packages. Rather than fuss
> with a separate project or subproject, we could document how to use
> the Tiles JAR outside of the Struts 2 environment.
>
> If volunteers from other projects begin to contribute to Tiles, and
> want to *build* Tiles without importing the s2 core, then the Tiles
> group could then apply for TLP status, either to the board or though
> the Incubator. In the meantime, we could continue to handle Tiles
> matters on the mailing lists, just as we would for any plugin (or
> subproject).
>
> In any event, if it would be helpful, I see no reason why we can't
> create tagged builds of Tiles. A build is not a release, regardless of
> whether we call it a "nightly", "snapshot", or "test".
>
> -Ted.
>
> On 11/23/06, Martin Cooper <ma...@apache.org> wrote:
> > On 11/23/06, Ted Husted <hu...@apache.org> wrote:
> > >
> > > I'd like to see the proposal discuss the alternatives to becoming a
> > > Struts subproject. A good role for a proposal is to summarize various
> > > threads. Becoming a subproject seems to be a foregone conclusion of
> > > the proposal, with no discussion of the alternatives.
> >
> >
> > Well, yeah, that's what is being _proposed_. We did discuss the options on
> > the mailing list, more than once, and came to the conclusion that becoming a
> > Struts sub-project was the right interim step. I don't see that we need to
> > have the discussion all over again just because the proposal has been put on
> > the wiki.
> >
> > In previous threads, Jakarta was mentioned, but not so much the
> > > Jakarta Commons. Why is it that we are not proposing to move Tiles to
> > > the Commons, as we did with the Validator, and others?
> >
> >
> > Sigh. We've had this discussion _lots_ of times already, and we've had
> > similar discussions over in Commons. Jakarta Commons is not about web
> > components, and people do not want it to be about web components, which is
> > why the notion of Jakarta Web Components has been bandied about so much.
> > Validator makes sense in Commons because it's not tied to the web; the part
> > that does tie to the web is in Struts, not Validator. I, for one, would not
> > want to propose Tiles as a Commons component, because I'm almost certain it
> > would be rejected, and because I would vote against that myself.
> >
> > Also, Tiles might be able to become a TLP by resolution of the board.
> > > The situation is not much different than Shale. The incubator is
> > > charged with "acceptance and oversight of new products submitted or
> > > proposed to become part of the Foundation". Tiles is already part of
> > > the foundation.
> >
> >
> > Yes, Tiles might be able to become a TLP, but it is my perception that the
> > people involved are not ready for that. It behooves us to provide better
> > options than either staying in the sandbox or going straight to TLP. That
> > you bring up Shale is interesting; note that we went through exactly the
> > same process with Shale as we are now proposing for Tiles. Shale went from
> > the sandbox to a Struts sub-project first. Only later, once it found its
> > feet as a sub-project, did it go off to TLP land.
> >
> > Speaking of the Incubator, we might also note that Incubator podlings
> > > do have releases.
> > >
> > > Even without quantifying it as a "release", given the usual release
> > > plan, Tiles could still create a tagged test-build. Before deciding
> > > whether Tiles should be a subproject or not, I think I'd like to see
> > > the volunteers create a test-build that could be a release if the PMC
> > > gave the nod.
> >
> >
> > Why would we introduce a new rule for Tiles that we have never imposed on
> > other projects coming out of the sandbox?
> >
> > Moving a code branch out the sandbox is a trivial task. What's not
> > > trivial is doing everything that's needed to turn a snapshot into a
> > > potential release.
> >
> >
> > True. But that has never before been tied to promoting something out of the
> > sandbox, and I don't think that introducing it in the midst of a proposal,
> > after most of the discussion has already happened on the lists, is a
> > productive thing to do.
> >
> > --
> > Martin Cooper
> >
> >
> > -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: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Ted Husted <hu...@apache.org>.
When we invented the Commons, it was not our intention to exclude "web
components". If we had even suggested such a thing, I doubt that the
Jakarta PMC would have approved our proposal. At the time, we took the
notion that ASF projects were suppose to be tied to HTTPD very
seriously. Of course, since then, we added many top-level projects
that have little to do with HTTPD. But, that shouldn't mean web
components have suddenly become second-class citizens. I believe that
the phrase "server-related" in the charter is meant to include web
servers.

Unless and until the Jakarta Commons PMC rejects a proposal from the
Tiles group, I consider it to be a valid alternative to be explored,
and until it's been fully explored, I will consider the proposal to
create a Struts Tiles subproject premature.

Others may think differently, but I am entitled (and even obliged) to
define what it is required to obtain my vote. (The vote need not be
unanimous, but only a 3/4 majority of the PMC.)

As it stands, the ASF's preferred unit of release is the TLP. If the
Tiles group is not ready to become a TLP, and unwilling to even try
and join the Commons, then I would suggest that Tiles is not ready to
"graduate".

A third alternative (aside from an independant project) would be to
bring Tiles back into the Struts 2 subproject as part of the Tiles
plugin. If other projects want to use Tiles, they could just grab the
tiles-plugin.jar and import the appropriate packages. Rather than fuss
with a separate project or subproject, we could document how to use
the Tiles JAR outside of the Struts 2 environment.

If volunteers from other projects begin to contribute to Tiles, and
want to *build* Tiles without importing the s2 core, then the Tiles
group could then apply for TLP status, either to the board or though
the Incubator. In the meantime, we could continue to handle Tiles
matters on the mailing lists, just as we would for any plugin (or
subproject).

In any event, if it would be helpful, I see no reason why we can't
create tagged builds of Tiles. A build is not a release, regardless of
whether we call it a "nightly", "snapshot", or "test".

-Ted.

On 11/23/06, Martin Cooper <ma...@apache.org> wrote:
> On 11/23/06, Ted Husted <hu...@apache.org> wrote:
> >
> > I'd like to see the proposal discuss the alternatives to becoming a
> > Struts subproject. A good role for a proposal is to summarize various
> > threads. Becoming a subproject seems to be a foregone conclusion of
> > the proposal, with no discussion of the alternatives.
>
>
> Well, yeah, that's what is being _proposed_. We did discuss the options on
> the mailing list, more than once, and came to the conclusion that becoming a
> Struts sub-project was the right interim step. I don't see that we need to
> have the discussion all over again just because the proposal has been put on
> the wiki.
>
> In previous threads, Jakarta was mentioned, but not so much the
> > Jakarta Commons. Why is it that we are not proposing to move Tiles to
> > the Commons, as we did with the Validator, and others?
>
>
> Sigh. We've had this discussion _lots_ of times already, and we've had
> similar discussions over in Commons. Jakarta Commons is not about web
> components, and people do not want it to be about web components, which is
> why the notion of Jakarta Web Components has been bandied about so much.
> Validator makes sense in Commons because it's not tied to the web; the part
> that does tie to the web is in Struts, not Validator. I, for one, would not
> want to propose Tiles as a Commons component, because I'm almost certain it
> would be rejected, and because I would vote against that myself.
>
> Also, Tiles might be able to become a TLP by resolution of the board.
> > The situation is not much different than Shale. The incubator is
> > charged with "acceptance and oversight of new products submitted or
> > proposed to become part of the Foundation". Tiles is already part of
> > the foundation.
>
>
> Yes, Tiles might be able to become a TLP, but it is my perception that the
> people involved are not ready for that. It behooves us to provide better
> options than either staying in the sandbox or going straight to TLP. That
> you bring up Shale is interesting; note that we went through exactly the
> same process with Shale as we are now proposing for Tiles. Shale went from
> the sandbox to a Struts sub-project first. Only later, once it found its
> feet as a sub-project, did it go off to TLP land.
>
> Speaking of the Incubator, we might also note that Incubator podlings
> > do have releases.
> >
> > Even without quantifying it as a "release", given the usual release
> > plan, Tiles could still create a tagged test-build. Before deciding
> > whether Tiles should be a subproject or not, I think I'd like to see
> > the volunteers create a test-build that could be a release if the PMC
> > gave the nod.
>
>
> Why would we introduce a new rule for Tiles that we have never imposed on
> other projects coming out of the sandbox?
>
> Moving a code branch out the sandbox is a trivial task. What's not
> > trivial is doing everything that's needed to turn a snapshot into a
> > potential release.
>
>
> True. But that has never before been tied to promoting something out of the
> sandbox, and I don't think that introducing it in the midst of a proposal,
> after most of the discussion has already happened on the lists, is a
> productive thing to do.
>
> --
> Martin Cooper
>
>
> -Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Martin Cooper <ma...@apache.org>.
On 11/23/06, Ted Husted <hu...@apache.org> wrote:
>
> I'd like to see the proposal discuss the alternatives to becoming a
> Struts subproject. A good role for a proposal is to summarize various
> threads. Becoming a subproject seems to be a foregone conclusion of
> the proposal, with no discussion of the alternatives.


Well, yeah, that's what is being _proposed_. We did discuss the options on
the mailing list, more than once, and came to the conclusion that becoming a
Struts sub-project was the right interim step. I don't see that we need to
have the discussion all over again just because the proposal has been put on
the wiki.

In previous threads, Jakarta was mentioned, but not so much the
> Jakarta Commons. Why is it that we are not proposing to move Tiles to
> the Commons, as we did with the Validator, and others?


Sigh. We've had this discussion _lots_ of times already, and we've had
similar discussions over in Commons. Jakarta Commons is not about web
components, and people do not want it to be about web components, which is
why the notion of Jakarta Web Components has been bandied about so much.
Validator makes sense in Commons because it's not tied to the web; the part
that does tie to the web is in Struts, not Validator. I, for one, would not
want to propose Tiles as a Commons component, because I'm almost certain it
would be rejected, and because I would vote against that myself.

Also, Tiles might be able to become a TLP by resolution of the board.
> The situation is not much different than Shale. The incubator is
> charged with "acceptance and oversight of new products submitted or
> proposed to become part of the Foundation". Tiles is already part of
> the foundation.


Yes, Tiles might be able to become a TLP, but it is my perception that the
people involved are not ready for that. It behooves us to provide better
options than either staying in the sandbox or going straight to TLP. That
you bring up Shale is interesting; note that we went through exactly the
same process with Shale as we are now proposing for Tiles. Shale went from
the sandbox to a Struts sub-project first. Only later, once it found its
feet as a sub-project, did it go off to TLP land.

Speaking of the Incubator, we might also note that Incubator podlings
> do have releases.
>
> Even without quantifying it as a "release", given the usual release
> plan, Tiles could still create a tagged test-build. Before deciding
> whether Tiles should be a subproject or not, I think I'd like to see
> the volunteers create a test-build that could be a release if the PMC
> gave the nod.


Why would we introduce a new rule for Tiles that we have never imposed on
other projects coming out of the sandbox?

Moving a code branch out the sandbox is a trivial task. What's not
> trivial is doing everything that's needed to turn a snapshot into a
> potential release.


True. But that has never before been tied to promoting something out of the
sandbox, and I don't think that introducing it in the midst of a proposal,
after most of the discussion has already happened on the lists, is a
productive thing to do.

--
Martin Cooper


-Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Ted Husted <hu...@apache.org>.
I'd like to see the proposal discuss the alternatives to becoming a
Struts subproject. A good role for a proposal is to summarize various
threads. Becoming a subproject seems to be a foregone conclusion of
the proposal, with no discussion of the alternatives.

In previous threads, Jakarta was mentioned, but not so much the
Jakarta Commons. Why is it that we are not proposing to move Tiles to
the Commons, as we did with the Validator, and others?

Also, Tiles might be able to become a TLP by resolution of the board.
The situation is not much different than Shale. The incubator is
charged with "acceptance and oversight of new products submitted or
proposed to become part of the Foundation". Tiles is already part of
the foundation.

Speaking of the Incubator, we might also note that Incubator podlings
do have releases.

Even without quantifying it as a "release", given the usual release
plan, Tiles could still create a tagged test-build. Before deciding
whether Tiles should be a subproject or not, I think I'd like to see
the volunteers create a test-build that could be a release if the PMC
gave the nod.

Moving a code branch out the sandbox is a trivial task. What's not
trivial is doing everything that's needed to turn a snapshot into a
potential release.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Ted Husted <hu...@apache.org>.
There's also a tradition in the Incubator of "co-signing" releases.
If the podling PMC votes on a release, and ithen any three members of
the Incubator PMC can authorize  the release. If Tiles were release
ready, and we had at least three people here who were going to support
it, I'm sure we can wrangle the PMC votes. After all, Greg is already
on the PMC, Antonio has been a committer since July, and David is
already a ASF PMC member, if for another project. So, we have a good
crew here.

-Ted.

On 11/23/06, Antonio Petrelli <ap...@apache.org> wrote:
> David H. DeWolf ha scritto:
> > Please find the Tiles2 graduation proposal draft below.  I look
> > forward to your feedback . . .
>
> +1, but I think that also Wendy should be put as an active participant,
> since she helped us with Maven, gave a lot of useful suggestions and
> made tests.
>
> Ciao
> Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by "David H. DeWolf" <dd...@apache.org>.

Antonio Petrelli wrote:
> David H. DeWolf ha scritto:
>> Please find the Tiles2 graduation proposal draft below.  I look 
>> forward to your feedback . . .

For the record, +1 Myself :)
> 
> +1, but I think that also Wendy should be put as an active participant, 
> since she helped us with Maven, gave a lot of useful suggestions and 
> made tests.

Sure, the original thought was to document the fact that we meet quota, 
not to exclude anyone. . . the more the merrier.

> 
> Ciao
> Antonio
> 
> ---------------------------------------------------------------------
> 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: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Antonio Petrelli <ap...@apache.org>.
David H. DeWolf ha scritto:
> Please find the Tiles2 graduation proposal draft below.  I look 
> forward to your feedback . . .

+1, but I think that also Wendy should be put as an active participant, 
since she helped us with Maven, gave a lot of useful suggestions and 
made tests.

Ciao
Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by Greg Reddin <gr...@apache.org>.
On Nov 22, 2006, at 12:51 PM, David H. DeWolf wrote:

> Please find the Tiles2 graduation proposal draft below.  I look  
> forward to your feedback . . .
>
> http://cwiki.apache.org/confluence/display/S2WIKI/Tiles2+Graduation 
> +Proposal

+1 with one clarification.  I think the Community Involvement section  
should either be rewritten or removed.  Technically, a release  
requires three PMC votes, not just committer votes.  Since that's an  
Apache directive not a Struts directive, I'm not sure if it's  
necessary to even list the requirement.  Maybe it should be changed  
to note the active participants in the project.

Am I correct?

Greg





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


[PROPOSAL] Graduate Tiles2 From the Sandbox (was Re: Releasing Tiles)

Posted by "David H. DeWolf" <dd...@apache.org>.
Please find the Tiles2 graduation proposal draft below.  I look forward 
to your feedback . . .

http://cwiki.apache.org/confluence/display/S2WIKI/Tiles2+Graduation+Proposal

David

Martin Cooper wrote:
> 
> Just write up a brief proposal that we can discuss, maybe on the wiki, as
> Wendy suggested. Once we have that, we can bounce the idea around a bit and
> then vote on it. IMO, it would be a good idea to include in the proposal a
> bit about a Struts sub-project not being the intended final home for Tiles
> but rather an intermediate step in the process of growing up. You could
> mention options for a final home, but I personally don't feel that we need
> to decide on that right now.
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Martin Cooper <ma...@apache.org>.
On 11/22/06, David H. DeWolf <dd...@apache.org> wrote:
>
>
>
> Martin Cooper wrote:
> > On 11/21/06, David H. DeWolf <dd...@apache.org> wrote:
> >>
> >> Is it possible for tiles2 to 'graduate' into a full struts project
> >> (sibling of struts1 and struts2) until it gains a little more momentum?
> >
> >
> > I actually think this would make a great deal of sense as an interim
> step
> > for Tiles. While the long term goal would be for Tiles to move away from
> > home and find its own place to live, letting it spend its adolescence
> here
> > seems appropriate. ;-) It does seem a little drastic to say that the
> choice
> > is to stay in the sandbox or leave entirely.
> >
> > . . .
> >
> > Well, we don't have a process as formal as that of the Incubator, but I
> > suppose along the same general lines. A demonstration of activity and
> > community is sufficient, and I believe Tiles has done that. Really, the
> > sandbox has been used to "contain" projects that might not go anywhere,
> and
> > Tiles is well beyond that now. So, I'd say graduating makes sense.
> >
>
> Ok, so what should I do to drive this to a decision?


Just write up a brief proposal that we can discuss, maybe on the wiki, as
Wendy suggested. Once we have that, we can bounce the idea around a bit and
then vote on it. IMO, it would be a good idea to include in the proposal a
bit about a Struts sub-project not being the intended final home for Tiles
but rather an intermediate step in the process of growing up. You could
mention options for a final home, but I personally don't feel that we need
to decide on that right now.

--
Martin Cooper


  If we have any
> sort of consensus, I'd like try to get it done before the struts 2.0.2
> release so that we can have the tiles plugin use an alpha release.  That
> may not be doable at this point, but I'd like to at least try.
>
> Let me know if I'm trying to move to fast :)
>
> David
>
> > --
> > Martin Cooper
> >
> >
> > Thoughts?
> >>
> >> David
> >>
> >> ---------------------------------------------------------------------
> >> 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: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by "David H. DeWolf" <dd...@apache.org>.

Martin Cooper wrote:
> On 11/21/06, David H. DeWolf <dd...@apache.org> wrote:
>>
>> Is it possible for tiles2 to 'graduate' into a full struts project
>> (sibling of struts1 and struts2) until it gains a little more momentum?
> 
> 
> I actually think this would make a great deal of sense as an interim step
> for Tiles. While the long term goal would be for Tiles to move away from
> home and find its own place to live, letting it spend its adolescence here
> seems appropriate. ;-) It does seem a little drastic to say that the choice
> is to stay in the sandbox or leave entirely.
> 
> . . . 
> 
> Well, we don't have a process as formal as that of the Incubator, but I
> suppose along the same general lines. A demonstration of activity and
> community is sufficient, and I believe Tiles has done that. Really, the
> sandbox has been used to "contain" projects that might not go anywhere, and
> Tiles is well beyond that now. So, I'd say graduating makes sense.
> 

Ok, so what should I do to drive this to a decision?  If we have any 
sort of consensus, I'd like try to get it done before the struts 2.0.2 
release so that we can have the tiles plugin use an alpha release.  That 
may not be doable at this point, but I'd like to at least try.

Let me know if I'm trying to move to fast :)

David

> -- 
> Martin Cooper
> 
> 
> Thoughts?
>>
>> David
>>
>> ---------------------------------------------------------------------
>> 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: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Martin Cooper <ma...@apache.org>.
On 11/21/06, David H. DeWolf <dd...@apache.org> wrote:
>
>
>
> Wendy Smoak wrote:
> > On 11/20/06, David H. DeWolf <dd...@apache.org> wrote:
> >> How about getting an initial tiles release out so that the 2.0.2 tiles
> >> plugin can rely upon it instead of a snapshot? It would probably only
> be
> >> 'alpha' quality at this point, but the same snapshot logic that you
> >> described below applies to it.
> >>
> >> I'll do the release (prior to the weekend), if someone that's done one
> >> before will help me through it.
> >
> > Tiles 2 is in the sandbox, and sandbox projects are not allowed to do
> > releases.  Choosing a particular snapshot for Struts 2 to depend on is
> > all we can do, unless we change the rules.
>
> Ok, thanks for clarifying.
>
> >
> > If Tiles is ready to graduate, then we need to decide where it's going
> > to live.  Top level?  Over at Jakarta, or wasn't there some sort of
> > 'web components' project being started?
> >
>
> Are these the only two options?  My fear with both of them (a top level
> project or the 'seed' project for a new web components project at
> jakarta) would be lack of community due to the fact that there seem to
> be just a few active committers interested in tiles right now.  Jakarta
> would be an option, though their recent trend seems to be graduating
> projects to TLP - not accepting new projects.
>
> Is it possible for tiles2 to 'graduate' into a full struts project
> (sibling of struts1 and struts2) until it gains a little more momentum?
>   The idea would be to allow tiles to leverage the
> participation/oversight   that's allready here?  This seems to make
> sense since I would guess that the vast majority of tiles users are
> using it in conjunction with one version of struts or another.


I actually think this would make a great deal of sense as an interim step
for Tiles. While the long term goal would be for Tiles to move away from
home and find its own place to live, letting it spend its adolescence here
seems appropriate. ;-) It does seem a little drastic to say that the choice
is to stay in the sandbox or leave entirely.

Also, what warrants graduation from the sandbox?  A we assuming the same
> requirements as graduating a project from the incubator?  My assessment
> at this point is that tiles has come a long way and is ready to be
> pushed out to the masses in order to allow them to play.  I'd like to
> 'release early/release often'.


Well, we don't have a process as formal as that of the Incubator, but I
suppose along the same general lines. A demonstration of activity and
community is sufficient, and I believe Tiles has done that. Really, the
sandbox has been used to "contain" projects that might not go anywhere, and
Tiles is well beyond that now. So, I'd say graduating makes sense.

--
Martin Cooper


Thoughts?
>
> David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by "David H. DeWolf" <dd...@apache.org>.
Well said, exactly what I was trying to communicate.

I was just hoping that we weren't "stuck in the sandbox" since that 
seems like it will prevent an alpha release.

David


Greg Reddin wrote:
> 
> On Nov 21, 2006, at 9:15 AM, David H. DeWolf wrote:
> 
>> What I'm more concerned about is the community/oversight.
> 
> I think the scope of the Tiles 2 community remains to be seen.  There 
> are several other templating solutions out there.  How will Tiles 2 be 
> accepted when compared with Sitemesh, etc?  I don't know.  The JSF 
> community has Facelets and Clay, so Tiles support is more of a legacy 
> thing.  The thing we do have going for us is that there's a lot of users 
> who are familiar with Tiles 1.x.  Migration from Tiles 1.x to Tiles 2 
> might be easier than, say, Tiles 1.x to Sitemesh for those who don't 
> want to learn too many new things.  It also helps that the Tiles 
> integration for Struts 2 and Shale is Tiles 2 exclusively.  But the risk 
> is that people who know Tiles 1 and start using Struts 2 or Shale will 
> not be willing to port their Tiles knowledge to Tiles 2 and would rather 
> take on a different framework.
> 
> So, all we can do is work it up, release it, and doc it and see what 
> happens.  I tend to think the earlier we get it out of the sandbox the 
> better.  A snapshot project in the sandbox just doesn't have the same 
> credence as even an alpha that has a real project commitment behind it.
> 
> For me personally, I'll support Tiles whether it's a TLP, part of 
> Jakarta, or part of Struts.  Honestly, I'm not interested in 
> spearheading a TLP right now.  I'm just not yet convinced enough that 
> the community will come along and make the effort worth it.  But if 
> someone else wants to write up the proposals and be the "chair" and 
> whatever else needs to be done, then count me in as a full-time 
> supporter.  It's possible that my situation will change when my day job 
> settles down a bit, but right now I just don't have the bandwidth to 
> kick it off.  I think the Struts community has made it clear that we 
> want Struts to be focused on building an MVC framework and not 
> necessarily all the stuff surrounding that (and I agree with that BTW).  
> So unless that sentiment has changed I think we have to stay in the 
> Struts sandbox until we have enough momentum to either join Jakarta or 
> go TLP.
> 
> Greg
> 
> 
> 
> ---------------------------------------------------------------------
> 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: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Martin Cooper <ma...@apache.org>.
On 11/21/06, Antonio Petrelli <ap...@apache.org> wrote:
>
> Greg Reddin ha scritto:
> >
> > On Nov 21, 2006, at 9:15 AM, David H. DeWolf wrote:
> >
> >> What I'm more concerned about is the community/oversight.
> >
> > How will Tiles 2 be accepted when compared with Sitemesh, etc?  I
> > don't know.  The JSF community has Facelets and Clay, so Tiles support
> > is more of a legacy thing.
>
> It is real until Tiles 2 does not show anything really new. If Tiles 2
> becomes "the IoC engine for the view layer", as I tried to explain some
> time ago, it probably will be an innovative project. But in this case,
> SB-86 needs to be fixed. But probably an alpha version can be released,
> leaving "revolution" for a later change.
> Just to complete the view, what prohibits me to use Tiles 2 together
> with Sitemesh? For example, using the composition capability of Tiles 2
> together with decoration capability of Sitemesh?
>
> In conclusion, after fixing the blocking issues, I think that an alpha
> can be released, but users should be warned that SB-86 will replace a
> feature that Tiles 1.1 had and that currently there is no replacement
> for it.


But the point is that an Alpha *cannot* be released while Tiles is still in
the Struts sandbox. Either we need to graduate Tiles out of the sandbox, or
Tiles needs to find a new home. The latter seems to be going from the frying
pan into the fire, so I'd suggest the former as an interim step.

--
Martin Cooper


Ciao
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Antonio Petrelli <ap...@apache.org>.
Greg Reddin ha scritto:
>
> On Nov 21, 2006, at 9:15 AM, David H. DeWolf wrote:
>
>> What I'm more concerned about is the community/oversight.
>
> How will Tiles 2 be accepted when compared with Sitemesh, etc?  I 
> don't know.  The JSF community has Facelets and Clay, so Tiles support 
> is more of a legacy thing.

It is real until Tiles 2 does not show anything really new. If Tiles 2 
becomes "the IoC engine for the view layer", as I tried to explain some 
time ago, it probably will be an innovative project. But in this case, 
SB-86 needs to be fixed. But probably an alpha version can be released, 
leaving "revolution" for a later change.
Just to complete the view, what prohibits me to use Tiles 2 together 
with Sitemesh? For example, using the composition capability of Tiles 2 
together with decoration capability of Sitemesh?

In conclusion, after fixing the blocking issues, I think that an alpha 
can be released, but users should be warned that SB-86 will replace a 
feature that Tiles 1.1 had and that currently there is no replacement 
for it.

Ciao
Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Greg Reddin <gr...@apache.org>.
On Nov 21, 2006, at 9:15 AM, David H. DeWolf wrote:

> What I'm more concerned about is the community/oversight.

I think the scope of the Tiles 2 community remains to be seen.  There  
are several other templating solutions out there.  How will Tiles 2  
be accepted when compared with Sitemesh, etc?  I don't know.  The JSF  
community has Facelets and Clay, so Tiles support is more of a legacy  
thing.  The thing we do have going for us is that there's a lot of  
users who are familiar with Tiles 1.x.  Migration from Tiles 1.x to  
Tiles 2 might be easier than, say, Tiles 1.x to Sitemesh for those  
who don't want to learn too many new things.  It also helps that the  
Tiles integration for Struts 2 and Shale is Tiles 2 exclusively.  But  
the risk is that people who know Tiles 1 and start using Struts 2 or  
Shale will not be willing to port their Tiles knowledge to Tiles 2  
and would rather take on a different framework.

So, all we can do is work it up, release it, and doc it and see what  
happens.  I tend to think the earlier we get it out of the sandbox  
the better.  A snapshot project in the sandbox just doesn't have the  
same credence as even an alpha that has a real project commitment  
behind it.

For me personally, I'll support Tiles whether it's a TLP, part of  
Jakarta, or part of Struts.  Honestly, I'm not interested in  
spearheading a TLP right now.  I'm just not yet convinced enough that  
the community will come along and make the effort worth it.  But if  
someone else wants to write up the proposals and be the "chair" and  
whatever else needs to be done, then count me in as a full-time  
supporter.  It's possible that my situation will change when my day  
job settles down a bit, but right now I just don't have the bandwidth  
to kick it off.  I think the Struts community has made it clear that  
we want Struts to be focused on building an MVC framework and not  
necessarily all the stuff surrounding that (and I agree with that  
BTW).  So unless that sentiment has changed I think we have to stay  
in the Struts sandbox until we have enough momentum to either join  
Jakarta or go TLP.

Greg



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by "David H. DeWolf" <dd...@apache.org>.

Ted Husted wrote:
> On 11/21/06, David H. DeWolf <dd...@apache.org> wrote:
>> Thoughts?
> 
> The key question is whether there are at least three (3) active
> committers who are using Tiles in their own projects and could vote +1
> for GA release, should the build quality warrant.
> 
> When making the tally, we should keep in mind that a binding +1 on a
> release means: I will help support the release by applying patching
> and answering questions on the user list.
> 
> Regardless of where the code lives, under ASF rules, we need a binding
> quorum of three, but a binding quorum of three is all we need.

It's my impression that we meet this quorom (Antonio, Greg, and myself 
at minimum).  I'm sure they'll correct me if I'm wrong :)

What I'm more concerned about is the community/oversight.  I find it to 
be very beneficial that people like yourself are monitoring tiles mail 
and can chime in on topics such as these.  If Tiles were to graduate to 
a TLP, I'm not yet convinced that we'd have that type of 'vetran' 
oversight.

I also think it's important to make sure that the current activity is 
sustainable.  Tiles2 has been revolutionized and is now at a point where 
it should be pushed out for the community to play with.  That said, I'm 
sure that it's user base is still almost nil, (and will be until an 
initial release) and it would be nice to see how it's accepted and grows 
before having to decide where it belongs.

I guess for those reasons, I'd like to maintain the status quo 
temporarily and find a way to release an initial cut either:

1) as a sandbox project (similar to how incubator poddlings release)

or

2) as a struts project (graduating from the sandbox but not yet from the 
struts umbrella).


> 
> -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: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Antonio Petrelli <ap...@apache.org>.
David H. DeWolf ha scritto:
> 1) Do we need to support EL for an alpha release?

I think this an issue that needs to resolved, since it will be the 
replacement of "beanName" and similar attributes in Tiles configuration 
files. There was a feature in Tiles 1.1 and it has been erased when 
those attributes were removed, so we need to give a replacement.
Probably it should be of "critical" priority.

> 2) Must we flush out all documentation for an alpha release?

I am not sure about it, since tiles-documentation needs to be updated, 
but I think it is not-so-important for the moment, so I agree with you.

> 3) Do we need to extend the putList features (SB-60)

Ok, changed to minor.

Thanks for the feedback :-)

Ciao
Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Greg Reddin <gr...@apache.org>.
On Nov 21, 2006, at 9:30 AM, David H. DeWolf wrote:

> procedural ones which we MUST take care of but are trivial  
> (Copyright notices, and Id Keywords,

I do think this one's critical to get out before alpha.

> retroweaver distributions),

Probably could wait til after alpha.

> 1) Do we need to support EL for an alpha release?
> 2) Must we flush out all documentation for an alpha release?
> 3) Do we need to extend the putList features (SB-60)

I think we could release an alpha without the above.  We know they  
are planned features for a final release, but an alpha would allow  
people to get the stuff in their hands and start playing with it.

Greg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by "David H. DeWolf" <dd...@apache.org>.

Antonio Petrelli wrote:

> For what I can say, surely Tiles 2 cannot be released as GA (neither as 
> alpha I suppose) since there is a blocking issue (just reopened :-) ) 
> and some major issues, not to mention a strange effect that I had last 
> week under Linux (this evening I will check it, I have Linux only at 
> home) that made the Selenium tests fail. I did not open the issue simply 
> because I was not sure about it.

Agreed.  Definitely not GA or Beta, but I do think we're close to alpha.

Take a hard look at the open issues, besides the procedural ones which 
we MUST take care of but are trivial (Copyright notices, and Id 
Keywords, retroweaver distributions), what is outstanding that is truly 
a major issue?

1) Do we need to support EL for an alpha release?
2) Must we flush out all documentation for an alpha release?
3) Do we need to extend the putList features (SB-60)

If not, then there's not much left before alpha.  If there are other 
things pending, please add those to jira so we can drive them to completion.



> 
> Antonio
> 
> ---------------------------------------------------------------------
> 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: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Antonio Petrelli <ap...@apache.org>.
Antonio Petrelli ha scritto:
> ...not to mention a strange effect that I had last week under Linux 
> (this evening I will check it, I have Linux only at home) that made 
> the Selenium tests fail. I did not open the issue simply because I was 
> not sure about it.

Ok false alarm :-) just tested yesterday and everything went fine. 
Probably it was a problem with Servlet-JSP versions.

Ciao
Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Antonio Petrelli <ap...@apache.org>.
Ted Husted ha scritto:
> On 11/21/06, David H. DeWolf <dd...@apache.org> wrote:
>> Thoughts?
>
> The key question is whether there are at least three (3) active
> committers who are using Tiles in their own projects and could vote +1
> for GA release, should the build quality warrant.

For what I can say, surely Tiles 2 cannot be released as GA (neither as 
alpha I suppose) since there is a blocking issue (just reopened :-) ) 
and some major issues, not to mention a strange effect that I had last 
week under Linux (this evening I will check it, I have Linux only at 
home) that made the Selenium tests fail. I did not open the issue simply 
because I was not sure about it.

Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Ted Husted <hu...@apache.org>.
On 11/21/06, David H. DeWolf <dd...@apache.org> wrote:
> Thoughts?

The key question is whether there are at least three (3) active
committers who are using Tiles in their own projects and could vote +1
for GA release, should the build quality warrant.

When making the tally, we should keep in mind that a binding +1 on a
release means: I will help support the release by applying patching
and answering questions on the user list.

Regardless of where the code lives, under ASF rules, we need a binding
quorum of three, but a binding quorum of three is all we need.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by "David H. DeWolf" <dd...@apache.org>.

Wendy Smoak wrote:
> On 11/20/06, David H. DeWolf <dd...@apache.org> wrote:
>> How about getting an initial tiles release out so that the 2.0.2 tiles
>> plugin can rely upon it instead of a snapshot? It would probably only be
>> 'alpha' quality at this point, but the same snapshot logic that you
>> described below applies to it.
>>
>> I'll do the release (prior to the weekend), if someone that's done one
>> before will help me through it.
> 
> Tiles 2 is in the sandbox, and sandbox projects are not allowed to do
> releases.  Choosing a particular snapshot for Struts 2 to depend on is
> all we can do, unless we change the rules.

Ok, thanks for clarifying.

> 
> If Tiles is ready to graduate, then we need to decide where it's going
> to live.  Top level?  Over at Jakarta, or wasn't there some sort of
> 'web components' project being started?
> 

Are these the only two options?  My fear with both of them (a top level 
project or the 'seed' project for a new web components project at 
jakarta) would be lack of community due to the fact that there seem to 
be just a few active committers interested in tiles right now.  Jakarta 
would be an option, though their recent trend seems to be graduating 
projects to TLP - not accepting new projects.

Is it possible for tiles2 to 'graduate' into a full struts project 
(sibling of struts1 and struts2) until it gains a little more momentum? 
  The idea would be to allow tiles to leverage the 
participation/oversight   that's allready here?  This seems to make 
sense since I would guess that the vast majority of tiles users are 
using it in conjunction with one version of struts or another.

Also, what warrants graduation from the sandbox?  A we assuming the same 
requirements as graduating a project from the incubator?  My assessment 
at this point is that tiles has come a long way and is ready to be 
pushed out to the masses in order to allow them to play.  I'd like to 
'release early/release often'.


Thoughts?

David

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Konstantin Priblouda <kp...@yahoo.com>.

--- Martin Cooper <ma...@apache.org> wrote:

> 
> I think you're misunderstanding. The purpose of
> Jakarta Web Components is to
> form a grouping of small web-related projects, along
> the same lines as
> Jakarta Commons but focussed on web related stuff.
> It is specifically not a
> project in and of itself, and it especially is not a
> repository for outside
> projects coming in to the ASF. Those would still
> need to go through
> incubation.

I could donate menu management system if somebody is
interested:
http://www.sourceforge.net/projects/jtec/
( jtec-menu ) 
( J Tec Team it's actually me and only me ) 

regards,

----[ Konstantin Pribluda http://www.pribluda.de ]----------------
Still using XDoclet 1.x?  XDoclet 2 is released and of production quality.
check it out: http://xdoclet.codehaus.org


 
____________________________________________________________________________________
Sponsored Link

Online degrees - find the right program to advance your career. 
www.nextag.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Martin Cooper <ma...@apache.org>.
On 11/20/06, Antonio Petrelli <ap...@apache.org> wrote:
>
> Martin Cooper ha scritto:
> > If so, the next question would be whether
> > or not we have enough people and enough energy to jump-start it.
>
> A good (non Apache yet but with Apache License) candidate for Java Web
> Components could be Java Web Parts (http://javawebparts.sourceforge.net/).
> And I could suggest a pair of projects I am administrator of:
> Scopes (http://scopes.sourceforge.net/);
> Dimensions (http://mutidimensions.sourceforge.net/).
> The only problem with Dimensions is that it probably needs incubation,
> since it is copyrighted by Free2Be LLC (though it seems that this entity
> is dead or changed its name... it needs some investigation :-) ).


I think you're misunderstanding. The purpose of Jakarta Web Components is to
form a grouping of small web-related projects, along the same lines as
Jakarta Commons but focussed on web related stuff. It is specifically not a
project in and of itself, and it especially is not a repository for outside
projects coming in to the ASF. Those would still need to go through
incubation.

--
Martin Cooper


Ciao
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Antonio Petrelli <ap...@apache.org>.
Martin Cooper ha scritto:
> If so, the next question would be whether
> or not we have enough people and enough energy to jump-start it.

A good (non Apache yet but with Apache License) candidate for Java Web 
Components could be Java Web Parts (http://javawebparts.sourceforge.net/).
And I could suggest a pair of projects I am administrator of:
Scopes (http://scopes.sourceforge.net/);
Dimensions (http://mutidimensions.sourceforge.net/).
The only problem with Dimensions is that it probably needs incubation, 
since it is copyrighted by Free2Be LLC (though it seems that this entity 
is dead or changed its name... it needs some investigation :-) ).

Ciao
Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Releasing Tiles (was: Re: [s2] 2.0.2 release this weekend)

Posted by Martin Cooper <ma...@apache.org>.
On 11/20/06, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 11/20/06, David H. DeWolf <dd...@apache.org> wrote:
> > How about getting an initial tiles release out so that the 2.0.2 tiles
> > plugin can rely upon it instead of a snapshot? It would probably only be
> > 'alpha' quality at this point, but the same snapshot logic that you
> > described below applies to it.
> >
> > I'll do the release (prior to the weekend), if someone that's done one
> > before will help me through it.
>
> Tiles 2 is in the sandbox, and sandbox projects are not allowed to do
> releases.  Choosing a particular snapshot for Struts 2 to depend on is
> all we can do, unless we change the rules.
>
> If Tiles is ready to graduate, then we need to decide where it's going
> to live.  Top level?  Over at Jakarta, or wasn't there some sort of
> 'web components' project being started?


You mean Jakarta Web Components? We talked about it a lot, but it hasn't got
off the ground (yet). At one point, I suggested that Tiles might make an
appropriate seed project for it, but Tiles wasn't really in a state to do
that at the time. Maybe it is now. If so, the next question would be whether
or not we have enough people and enough energy to jump-start it.

--
Martin Cooper


--
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>