Re: [logback-dev] Running the logback project as a commitocracy

2011-02-21 Thread Ceki Gülcü
On 21/02/2011 5:48 PM, Robert Elliot wrote: > We started off with Gradle on my current project, but we've moved > back to Maven because of the lack of IDE support. The ease of sorting > out the classpath in Eclipse and IDEA using Maven plugins makes up a > lot for the pain associated with the re

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-21 Thread Craig P. Motlin
IDE support for SBT is lacking too, so I also tend to use it side by side with Maven. On Mon, Feb 21, 2011 at 11:48 AM, Robert Elliot wrote: > > Gradle's better/more flexible design is rather appealing. One of the > > fetaures I like about the current maven-based build is that IDEA can > > impor

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-21 Thread Robert Elliot
> Gradle's better/more flexible design is rather appealing. One of the > fetaures I like about the current maven-based build is that IDEA can > import it without any problems. Can Gradle projects be imported into > IDEA as easily? We started off with Gradle on my current project, but we've moved b

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-21 Thread Joern Huxhorn
> Gradle's better/more flexible design is rather appealing. One of the fetaures > I like about the current maven-based build is that IDEA can import it without > any problems. Can Gradle projects be imported into IDEA as easily? > Well, there are Gradle plugins to generate Eclipse and IDEA proj

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-21 Thread Ceki Gülcü
On 21/02/2011 3:29 PM, Joern Huxhorn wrote: On 21.02.2011, at 00:27, Craig P. Motlin wrote: Yes, they are both in-language DSLs. Gradle seems like a next-generation ant since it's very configurable. SBT seems like a next-generation maven since projects retain the maven directory layout and h

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-21 Thread Joern Huxhorn
On 21.02.2011, at 00:27, Craig P. Motlin wrote: > Yes, they are both in-language DSLs. Gradle seems like a next-generation ant > since it's very configurable. SBT seems like a next-generation maven since > projects retain the maven directory layout and have standard lifecycle steps > like comp

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-20 Thread Craig P. Motlin
Yes, they are both in-language DSLs. Gradle seems like a next-generation ant since it's very configurable. SBT seems like a next-generation maven since projects retain the maven directory layout and have standard lifecycle steps like compile and test. I prefer Scala because of its type system and

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-20 Thread Craig P. Motlin
Yes, they are both in-language DSLs. Gradle seems like a next-generation ant since it's very configurable. SBT seems like a next-generation maven since projects retain the maven directory layout and have standard lifecycle steps like compile and test. I prefer Scala because of its type system and

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-20 Thread Ceki Gülcü
On 20/02/2011 5:00 PM, Ralph Goers wrote: > Gradle is a build tool, not a language. Joern was asking about it > replacing Maven. I attended a presentation on Gradle at SpringOne and > concluded it wouldn't meet the needs of my organization - it is > somewhere between Ant and Maven. It isn't cle

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-20 Thread Ralph Goers
On Feb 20, 2011, at 5:11 AM, Joern Huxhorn wrote: > > > Other big projects, like Hibernate and Spring, have also chosen to take the > Gradle path. I'm pretty sure that Gradle is "the next big thing"... I very much doubt it. The big selling point for Maven is consistency - when you move from

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-20 Thread Ralph Goers
Gradle is a build tool, not a language. Joern was asking about it replacing Maven. I attended a presentation on Gradle at SpringOne and concluded it wouldn't meet the needs of my organization - it is somewhere between Ant and Maven. It isn't clear to me why one would want to switch from Maven

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-20 Thread Joern Huxhorn
On 19.02.2011, at 22:51, Ceki Gülcü wrote: > On 19/02/2011 10:06 PM, Joern Huxhorn wrote: >> >> On 18.02.2011, at 23:08, Ceki Gülcü wrote: >> >>> Sure. I understand that seeing one's contributions ignored/declined >>> can be frustrating. I am sorry for ignoring/declining the >>> contributions w

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-19 Thread Ceki Gülcü
On 19/02/2011 10:06 PM, Joern Huxhorn wrote: On 18.02.2011, at 23:08, Ceki Gülcü wrote: Sure. I understand that seeing one's contributions ignored/declined can be frustrating. I am sorry for ignoring/declining the contributions which deserved better. > For a more recent example I asked abo

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-19 Thread Joern Huxhorn
On 18.02.2011, at 23:08, Ceki Gülcü wrote: > Sure. I understand that seeing one's contributions ignored/declined > can be frustrating. I am sorry for ignoring/declining the > contributions which deserved better. > For a more recent example I asked about switching to Gradle in http://www.mail-a

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-18 Thread Ceki Gülcü
On 15/02/2011 1:45 AM, Joern Huxhorn wrote: [snip] For git, the dvcs we use in logback, the following command computes the commit-points accumulated by Alice. git log --format='%ad %an' --date=short|uniq|grep Alice|wc -l At present time, the commit-points for the logback project: Ceki Gulcu

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-14 Thread Ralph Goers
Although the details are different, I've also pretty much given up being able to contribute anything to Logback. All my work now is focused on Log4j 2.0 even thought there is no guarantee it will ever be used by anyone. Committing changes to github on a branch no one is ever going to use and I

Re: [logback-dev] Running the logback project as a commitocracy

2011-02-14 Thread Joern Huxhorn
Hi Ceki, On 14.02.2011, at 18:05, Ceki Gülcü wrote: > Hello all, > > I am considering running the logback project as a commitocracy. The idea is > to settle non controversial questions by consensus. However, whenever a > decision cannot be reached by unanimous agreement, a vote is called for.

[logback-dev] Running the logback project as a commitocracy

2011-02-14 Thread Ceki Gülcü
Hello all, I am considering running the logback project as a commitocracy. The idea is to settle non controversial questions by consensus. However, whenever a decision cannot be reached by unanimous agreement, a vote is called for. The commit-point for or against a motion are summed, the total