I did take a look at it earlier. Before I was thinking that it doesn't really change anything because technically any change triggers a lazy consensus vote, but still, it seems a little voting happy. What happens if somebody votes -1 +71 hours after commit? The commit needs to be automatically reverted back? The issue with automated triggering of lazy consensus votes is that there's nobody to gather the results. Of course, most of the time it doesn't matter but then again, what's the point of spelling it out explicitly? The existing Apache rules are minimal but good enough and worked for multiple projects for years. Overall, I'd say I prefer not voting for everything but "just get it done" attitude and explicit voting when needed. However, if community finds these rules are needed that's ok with me, thus still +0 (non-binding).
Kalle On Thu, May 27, 2010 at 4:01 PM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > Take a look at the "When to vote with what voting style" section. I agree > that most of it is just how Apache project work, but there are some parts > that are specific for Tapestry. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
