+1, having sonar would be nice although I've found that having tools
that no one pays attention to is not useful. The best way to combat
that is to integrate it into the build (e.g. hadoop QA bot).
On Mon, Sep 5, 2011 at 1:27 AM, Thomas Koch tho...@koch.ro wrote:
Hi Camille,
We already have a
Hi,
my university labs work has started yesterday. In the next two months I'll
work on ZooKeeper. This work has three major goals
- improve the maintainability of the code base
- migrate ZooKeeper to scala and use actors for reliable concurrency
- find other developers to collaborate on the
Andrew Finnell:
Thomas,
Upfront warning. I am not in charge of ZooKeeper or affiliated with them
except for submitting patches.
While I understand the power of Scala, what is the major benefit of
changing all of the Java code over to Scala? Will this outweigh the
decrease in skill sets
Message-
From: Thomas Koch [mailto:tho...@koch.ro]
Sent: Friday, September 02, 2011 9:16 AM
To: dev@zookeeper.apache.org
Subject: ZooKeeper cleanup / refactoring / scala migration
Hi,
my university labs work has started yesterday. In the next two months I'll
work on ZooKeeper. This work has three
be interesting and maybe something we could
take back as a contribution if you wanted.
C
-Original Message-
From: Thomas Koch [mailto:tho...@koch.ro]
Sent: Friday, September 02, 2011 9:16 AM
To: dev@zookeeper.apache.org
Subject: ZooKeeper cleanup / refactoring / scala migration
Fournier, Camille F.:
We already have a reviewboard set up for zookeeper which you should plan to
Hi Fournier,
I'll use reviewboard for patches targeted for inclusion. However just for
reference and to make you curious, I compare the steps necessary to create a
review in reviewboard and in
Thomas, checkout post-review from https://github.com/reviewboard/rbtools
I haven't used it against Apache rb, however I use it to great effect
inside Cloudera. It will allow you to cut the number of steps
significantly (I have small bash scripts wrapping post-review for the
various projects I
