Re: [DISCUSS] Tapestry slogan

On Thu, Jun 3, 2010 at 9:23 PM, Robin Komiwes wrote: > > D - Code Less, Deliver More > > +1 This is the shortest and most accurately description of Tapestry. -- Best regards, Igor Drobiazko http://tapestry5.de/blog

Re: [DISCUSS] Tapestry slogan

On Thu, 03 Jun 2010 20:38:47 -0300, Christian Riedel wrote: I've got some, too! Tapestry - more than just a wicket hehehe But most people in non-cricket-playing countries could not understand the pun . . . Tapestry - backwards compatible est 2006 ... also major selling points ;) Agr

Re: [DISCUSS] Tapestry slogan

I've got some, too! Tapestry - more than just a wicket Tapestry - backwards compatible est 2006 ... also major selling points ;) Or just: Tapestry - Code Less, Live Longer (but unfortunately we're not selling food here... although...) I don't like slogans ending with 'more'. They remind me too

Re: [DISCUSS] Tapestry slogan

On Jun 3, 2010, at 5:10 PM, Thiago H. de Paula Figueiredo wrote: On Thu, 03 Jun 2010 17:16:19 -0300, Howard Lewis Ship > wrote: D - Code Less, Deliver More +1 +1. That's a major selling point. +1 - you're welcome. ;-) -

Re: [DISCUSS] Tapestry slogan

On Thu, 03 Jun 2010 17:16:19 -0300, Howard Lewis Ship wrote: D - Code Less, Deliver More +1 +1. That's a major selling point. J - When development meet Art +0 but who is this Art fellow? It could be me. IMHO, software development is not just technique, it's an art too. That's why

Re: [DISCUSS] Tapestry slogan

On Thu, Jun 3, 2010 at 12:23 PM, Robin Komiwes wrote: > There was a discussion about that in the Tapestry homepage redesign thread. > > Here are the proposals: > > A - Compose your Web Application > B - Development is Art ! > C - Why build when you can weave? > D - Code Less, Deliver More +1 > E

Re: [VOTE] remove inactive PMC members from the PMC

On Thu, Jun 3, 2010 at 12:57 PM, Andreas Andreou wrote: >> PS. The new bylaws make it even simpler to end up in a situation where >> PMC is unable to act - just something to consider > Can you expand on that? What is the problem / gaps you're seeing? Whoops, I'll withdraw that statement. I really

Re: [VOTE] remove inactive PMC members from the PMC

> PS. The new bylaws make it even simpler to end up in a situation where > PMC is unable to act - just something to consider Can you expand on that? What is the problem / gaps you're seeing? - To unsubscribe, e-mail: dev-unsubscr

Re: [VOTE] remove inactive PMC members from the PMC

The original vote was for 7 days - we can declare this as failed and start a new one (excluding Richard) for just the next 4 days... end result ideally being the same as the original intended On Thu, Jun 3, 2010 at 22:10, Kalle Korhonen wrote: > On Thu, Jun 3, 2010 at 12:01 PM, Thiago H. de Paula

[DISCUSS] Tapestry slogan

There was a discussion about that in the Tapestry homepage redesign thread. Here are the proposals: A - Compose your Web Application B - Development is Art ! C - Why build when you can weave? D - Code Less, Deliver More E - Implement more with less code F - Weave the web! G - Weave your source! H

Re: [VOTE] remove inactive PMC members from the PMC

On Thu, Jun 3, 2010 at 12:01 PM, Thiago H. de Paula Figueiredo wrote: > On Thu, 03 Jun 2010 15:14:56 -0300, Kalle Korhonen > wrote: >> Richard's binding vote btw seems to mean that the whole vote will >> fail (Ulrich cannot change the interpretation of a binding vote with >> "their negative vote

Re: [VOTE] remove inactive PMC members from the PMC

On Thu, 03 Jun 2010 15:14:56 -0300, Kalle Korhonen wrote: Richard's binding vote btw seems to mean that the whole vote will fail (Ulrich cannot change the interpretation of a binding vote with "their negative vote means that they will be excluded from the removal"). That's how Apache works:

Re: [VOTE] remove inactive PMC members from the PMC

Aww. I would have like moving on Github. :D On Thu, Jun 3, 2010 at 7:46 PM, Howard Lewis Ship wrote: > And yes, I'm kidding. I'm just a little frustrated about all this > bureaucratic crap.  We need to have a healthy PMC to vote in new > committers with authority, and I'm impatient to have that r

Re: [VOTE] remove inactive PMC members from the PMC

If you really want to stick to the rules then Richards veto has to be considered as invalid since a veto can't stand without an explanation. On 03.06.2010 20:14, Kalle Korhonen wrote: Ah, take a deep breath, it's just democracy at work. It works but is just a bit slow. Try living in Europe for

Re: [VOTE] remove inactive PMC members from the PMC

Ah, take a deep breath, it's just democracy at work. It works but is just a bit slow. Try living in Europe for a bit and you get used to it :) Richard's binding vote btw seems to mean that the whole vote will fail (Ulrich cannot change the interpretation of a binding vote with "their negative vote

Re: [VOTE] remove inactive PMC members from the PMC

And yes, I'm kidding. I'm just a little frustrated about all this bureaucratic crap. We need to have a healthy PMC to vote in new committers with authority, and I'm impatient to have that resolved. On Thu, Jun 3, 2010 at 8:12 AM, Howard Lewis Ship wrote: > On Thu, Jun 3, 2010 at 6:29 AM, Richard

Re: [VOTE] remove inactive PMC members from the PMC

On Thu, Jun 3, 2010 at 6:29 AM, Richard Lewis-Shell wrote: > Richard Lewis-Shell: -1 (binding) Ok then, it's decided. Let's move Tapestry to GitHub :-) > > On 31 May 2010 23:22, Ulrich Stärk wrote: > >> The vote is to clean up the list of PMC members and remove the members >> >> >> David Solis

Re: [VOTE] remove inactive PMC members from the PMC

Richard Lewis-Shell: -1 (binding) On 31 May 2010 23:22, Ulrich Stärk wrote: > The vote is to clean up the list of PMC members and remove the members > > > David Solis > Kent Tong > Geoffrey Longman > Mind Bridge > Paul Ferraro > Richard Lewis-Shell > Tsvetelin Saykov > > from the PMC. They have

Hudson build is back to normal : tapestry-5.2-freestyle #128

See - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org

Re: Build failed in Hudson: tapestry-5.2-freestyle #127

i've cleanup up the file and now waiting for the build to rerun On Thu, Jun 3, 2010 at 13:10, Apache Hudson Server wrote: > See > > > Changes: > > [hlship] Add a lazy take() method to Flow, and add a method for creati

Build failed in Hudson: tapestry-5.2-freestyle #127

See Changes: [hlship] Add a lazy take() method to Flow, and add a method for creating an infinite series to F [hlship] Make F.lazy() a public method [hlship] Add F.range() to create a lazy Flow between two integers