On 11/24/06, David H. DeWolf <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
