tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse Kuhnert <jkuhn...@gmail.com>
Subject Re: [DISCUSS] Tapestry at Top Level Project
Date Tue, 10 Jan 2006 19:30:41 GMT
++1 On moving to a top level project.

Well, ok  I agree on all points. Sounds like the perfect time to have
tapestry show up on the top level project with a brand new look & feel
combined with maven2 build.

I don't want to, nor do I think I've earned the right to be any sort of
chairman of anything, but if no one else thinks they want to do it I will
volunteer my services as a last resort. Can't say how politically/anything
else savvy I would be at it but I'd try..heh I may be able to create some
new icons and such, but it's very very painful to do ;) (I just finished a
new tacos/tapestry icon plus maven theme that I'm itching to push out for
tacos, once the testng part is done)

Does this mean that tacos could move to apache and get subversion finally?
Woo hoo! :)

In summary, I think you've all completely earned your right to a top level
project by sticking to your guns and only designing what you thought was the
best solution, which has also been proven to be a sound path..So, bring it
on !

On 1/10/06, Howard Lewis Ship <hlship@gmail.com> wrote:
> Anyone up for tapestry.apache.org? (I noticed we did have a discussion
> about this back in March.)
> I've been saying for some time that Jakarta is turning into more of a
> second-level incubator; all successful projects (including Ant and
> Struts) have migrated up to top-level projects. It's been made clear
> to me that this is not only possible for Tapestry, it is desirable.
> In organizational terms, this would mean that Tapestry would have its
> own Project Management Comittee. We would have to produce quarterly
> reports to the Apache board. Our home page address and mailing list
> addresses would change.
> The advantage is that we could break Tapestry into smaller pieces
> (projects within the TLP) and each sub-project could have its own set
> of committers.  This, combined with using Maven 2 for builds, would
> give us a lot more flexibility and room to breathe.
> However, it requires a chairman to report to the board and I'm pretty
> desperate for that to ** not ** be me. I say this out of a mix of
> lazyness (I'm already too busy), self awareness (I do terribly at any
> kind of organization stuff) and political savvy (it would some ways
> demonstrate that Tapestry can survive without HLS).
> A TLP move would also be a good time to:
> - Rethink our release numbering strategy
> - Create new project marketting assets (icons, etc.)
> - Ask HiveMind if they would like to move from Jakarta to Tapestry
> On that second point ... does anyone have any ideas about refreshing
> the Tapestry marketting assets?  It might be nice to have someone
> (semi-)professional design new icons and such.  The Circle-T is really
> looking dated!
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
> Professional Tapestry training, mentoring, support
> and project work.  http://howardlewisship.com
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message