On Mon, August 8, 2005 12:42 pm, robert burrell donkin said: > On Mon, 2005-08-08 at 01:54 -0300, Felipe Leme wrote: >> Hello all, >> >> What's the status on the new project proposal? Has the discussion moved >> to another list or has it just staled? > > in a holding pattern: > > IMO the proposal can be finished off pretty quickly but i'm unsure about > the best way to handle the name issue. didn't seem to be any sort of a > consensus. opinions?
Progress on this project seemed to kind of stop, based on posts about it, about two weeks ago. As Robert indicates, there was never any consensus on the name. There were a bunch of options and comments listed on the Wiki page: http://wiki.apache.org/jakarta/CreatingCommonsForWebComponents ...but the discussion seemed to kind of fade away. My personal favorite off that list was Jakarta Web Parts For Java (JWP4J). It has the virtue of sounding like some other Apache/OSS projects (Log4J, SOAP4J, ws-wsrp4j, etc). It has the problem however of being almost identical to my own Java Web Parts project. I still have an interest in donating my work to the foundation, and that would start with the name if so desired, but I still have concerns about such a donation that might make choosing a different name more prudent. >> Anyway, the Jakarta Taglib Project has voted how it would like to take >> part on this new project, and the result was: >> >> 1.The Jakarta Taglibs Project would like to be merged into the project >> 2.The Jakarta Standard Taglib should then be a project of its own >> 3.The remaining taglibs would be gradually migrated to the new project, >> the most actives first >> 4.It's not decided yet if the migrated taglibs would have a newer >> release prior to the migration I'm not sure there was ever a consensus on what the overall structure of the project would be either (someone can correct me if I'm wrong on that point)... It seems like there might be a risk of sub-projects within sub-projects within sub-projects, which I'm not sure would be the best organizational stucture... if you had Jakarta Taglibs as a sub-component of the JWP4J project (assume for the sake of argument that name sticks), and then have Jakarta Standard Taglib as a sub-project of Jakarta Taglibs, is that the best structure to have? How deep of a hierarchy is OK and how deep is too deep? My own JWP project has a taglib package that has individual taglibs within it (AjaxTags, BasicString, etc), so I have the same thing going on... I personally wouldn't go beyond 3-levels like this, and I just wanted to raise the issue now before anything actually moves forward in case others have thoughts on this. Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
