Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of jukka.zitting@gmail.com
 designates 66.249.82.236 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=uZZ/7/Duzx7UkJc5RRpnNvK81zdVBIjj70JhQAvi85C7igWnl6k/E1e1DkYCWxC1Mvt/iJFIbDgIrN4Y/4dkSWZR6tPPAZXx7YaTepq9IiDRn6YcioqQlEzLwhV3/JRje7qO3okmI5yHYr8L9a7C9o032uHrXsaxX3mHXs1Afh4=
Message-ID: <510143ac0703120414t48a52f8fl51df3a659a5a97a@mail.gmail.com>
Date: Mon, 12 Mar 2007 13:14:58 +0200
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Jackrabbit board report draft
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

I'm preparing the scheduled Apache Jackrabbit report for the ASF board
meeting this month. See below for the draft report and feel free to
comment on it.

I'd especially like to highlight the "Development" paragraph on
encouraging patch submissions. In some of the recent discussions I've
felt a hint of NIH syndrome, in that alternative design proposals have
been somewhat categorically dismissed without fully discussing the
implications of the proposed changes.

In many cases, even if the proposal sounds downright stupid, it would
be good to gently point out the potential downsides of such proposals
and to encourage people to work out the details in code. This would
both increase the amount of eyes looking at our codebase and give
people a first-hand chance to realize and perhaps fix any potential
downfalls of their proposed changes.

What do you think? Perhaps I'm just overly sensitive.

BR,

Jukka Zitting

----

Apache Jackrabbit is a fully conforming implementation of the Content
Repository for Java Technology API (JCR, specified in JSR 170).

The Apache Jackrabbit project is in good shape. We have no board-level
issues at this time.

o Releases

  We released three versions of Apache Jackrabbit; 1.2.1 in January,
  1.2.2 in February, and 1.2.3 in March.

  The 1.2 release candidate needed to be cancelled and repackaged as
  1.2.1 due to a last-minute issue that was raised during the release
  vote. This prompted a discussion on release candidates and versioning,
  which in turn resulted in some improvements to our release process.

  We are currently working on the 1.3 release.

o Community

  Przemyslaw Pakulski was added as a committer and PMC member.

  The user mailing list that was launched last year has reached the
  activity level of the development list and continues steady growth.
  The total mailing list activity is now higher than ever before.

  One session and one tutorial on JCR/Jackrabbit have been scheduled
  for the upcoming ApacheCon EU. We are also planning to organize a
  Jackrabbit BOF during the conference.

  Based on the experiences from last summer, we are proposing a
  Google Summer of Code 2007 project to build a JCR demo application
  based on Apache Jackrabbit.

  There is interest in starting a new incubating content analysis toolkit
  project named Tika. Hopefully the project will as a side effect build
  more bridges between the Lucene and Jackrabbit projects.

o Development

  The 1.2 releases include a new beta-level clustering feature that is
  attracting much interest. Many corner cases are being ironed out based
  on feedback and bug reports from the user community, and it seems that
  we can soon declare the feature stable.

  The main new feature in the 1.3 release is a set of "bundle persistence
  manager" components contributed by Day. These components bring a major
  performance boost to many Jackrabbit user cases. The contributed IP has
  been cleared and is now being integrated in the Jackrabbit codebase.

  There have been a number of cases where users have suggested some
  internal changes to better handle specific performance and other
  requirements. Unfortunately few of such discussions have resulted in
  proposed patches. We should do better to encourage patch submissions.

o Infrastructure

  The Solaris zone we requested is now up and running. We have a Continuum
  installation doing nightly builds and continuous integration tests for
  all the Jackrabbit release components. So far we've seen zero
  build-breaking commits.