Please Note : This is extracted from a list of minutes which have been approved by the Board. The Board typically approves the previous meeting's minutes at the beginning of every Board meeting; therefore, this list below may not contain the minutes of the most recent Board meeting.

2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

Jackrabbit

18 Dec 2013 [Michael Dürig / Doug]

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

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

o Releases

We made the following stable release from Jackrabbit trunk:

 * Apache Jackrabbit 2.6.4 on October 11th

 We made the following unstable release from Jackrabbit trunk:

 * Apache Jackrabbit 2.7.1 on September 16th
 * Apache Jackrabbit 2.7.2 on November 8th
 * Apache Jackrabbit 2.7.3 on December 9th 

 The following patch releases were made from earlier maintenance 
 branches:

 * Apache Jackrabbit 2.4.5 on October 11th
   
 We made the following releases from the Jackrabbit Oak sub project:
 
 * Apache Jackrabbit Oak 0.9 on September 20th 
 * Apache Jackrabbit Oak 0.10 on October 9th
 * Apache Jackrabbit Oak 0.11 on November 21st
 * Apache Jackrabbit Oak 0.12 on November 28th

 We made the following release from the Jackrabbit FileVault sub project:

 * Apache Jackrabbit FileVault 3.0 on October 1st
       
o Community / Development
 * The Jackrabbit project received a donation of Adobe's FileVault. The 
   process was tracked under JCR-3612. IP clearance passed August 10th [1]
   and subsequently lead to a first release as listed above. 

 * No new committers or PMC members joined the Jackrabbit team since
   February 2013.

 [1] http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/201308.mbox/%3CCAB+dfiknHR3gpNzeee3K867jcC1E5Z7XZt3m0d2fqfbuExiByQ@mail.gmail.com%3E

18 Sep 2013 [Michael Dürig / Doug]

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

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

o Releases

 We made the following stable release from the 2.6 branch:

 * Apache Jackrabbit 2.6.3 on August 1st

o Community / Development

 No new committers or PMC members joined the Jackrabbit team since
 February 2013.

19 Jun 2013 [Michael Dürig / Shane]

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

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

o Releases

 We made the following stable release from Jackrabbit trunk:

 * Apache Jackrabbit 2.6.1 on May 13th
 * Apache Jackrabbit 2.6.2 on May 29th

 We made the following unstable release from Jackrabbit trunk:

 * Apache Jackrabbit 2.7.0 on May 13th

 The following patch releases were made from earlier maintenance
 branches:

 * Apache Jackrabbit 2.4.4 on May 13th

 We made a release from the Jackrabbit Oak sub project:

 * Apache Jackrabbit Oak 0.7 on May 20th
 * Apache Jackrabbit Oak 0.8 on May 27th

o Community / Development

 No new committers or PMC members joined the Jackrabbit team since
 February 2013.

o Infrastructure

 Jackrabbit web site migration is done. To make updating easier we
 will probably migrate most of the site's content to the Wiki and
 go with a simpler main page that points to all relevant resources.

20 Mar 2013 [Michael Dürig / Roy]

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

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

o Releases

 We made the following stable release from Jackrabbit trunk:

 * Apache Jackrabbit 2.6 on February 14th

 We made the following unstable 2.5.x release from Jackrabbit trunk:

 * Apache Jackrabbit 2.5.3 on January 13th
   
 We made a release from the Jackrabbit Oak sub project:
 
 * Apache Jackrabbit Oak 0.6 on January 28th
   
o Community / Development

 * Manfred Baedke, Tommaso Teofili and Cédric Damioli joined the Jackrabbit
   team as committers and PMC members.
       
o Infrastructure

 Jackrabbit web site migration is pending for infra, see 
 https://issues.apache.org/jira/browse/INFRA-5919

19 Dec 2012 [Michael Dürig / Jim]

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

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

o Releases

 We made the following unstable 2.5.x release from Jackrabbit trunk:

 * Apache Jackrabbit 2.5.2 on September 23rd
   
 We made a release from the Jackrabbit Oak sub project:
 
 * Apache Jackrabbit Oak 0.5 on September 30th
   
o Community / Development

 * Chetan Mehrotra and Mete Atamel joined the Jackrabbit team as committers 
   and PMC members.

 * Work on Jackrabbit Oak continues strong: At .adaptTo(Berlin) 2012 there 
   was a presentation on Oak and an Oak related hackathon both of which 
   where well attended. A further Hackathon was held at ApacheCon EU.
 
 * There was a discussion on the future of Jackrabbit and Jackrabbit Oak
   on the dev@ list. The emerging consensus seems to be that Oak will be
   kept in Jackrabbit and might eventually become Jackrabbit 3.0
   (See http://markmail.org/message/ga4mn2x2xqsvzwg6).
   
o Infrastructure

 We are still in progress of migrating from Confluence to the new CMS.

19 Sep 2012 [Michael Dürig / Roy]

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

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

o Releases

 We made the following unstable 2.5.x releases from Jackrabbit trunk:

 * Apache Jackrabbit 2.5.1 on August 6th
 
 The following patch releases were made from earlier maintenance 
 branches:

 * Apache Jackrabbit 2.4.3 on September 3rd
 
 This quarter also saw the first releases of the OCM code base in a 
 while:

 * Apache Jackrabbit OCM 2.0 on July 10th

 Finally we made two releases from the Jackrabbit Oak sub project:
 
 * Apache Jackrabbit Oak 0.4 on August 13th
 * Apache Jackrabbit Oak 0.3 on July 5th
   
o Community / Development

 * Randall Hauch joined the Jackrabbit team as committer and PMC member.

 * Work on Jackrabbit Oak is still going strong: there where again two 
 Hackathons in the last quarter during which great progress was made and
 which lead to the release of Oak 0.3. and 0.4. Another Hackathon will 
 take place in September co-located with the .adaptTo(Berlin) 2012 
 conference (http://adaptto.mixxt.de/networks/events/show_event.65841). 
 Being part of .adaptTo() allows us to further broaden the community and 
 spark more interest in Apache Jackrabbit Oak.

 * Jukka Zitting and Michael Dürig submitted a talk about Oak for 
 .adaptTo(Berlin) 2012 (http://adaptto.mixxt.de/).

 * Jukka Zitting and Michael Dürig submitted a talk about Oak for ApacheCon
 Europe 2012.
   
o Infrastructure

 We are still in progress of migrating from Confluence to the new CMS.

20 Jun 2012 [Michael Dürig / Sam]

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

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

o Releases

 We made the following unstable 2.5.x releases from Jackrabbit trunk.

 * Apache Jackrabbit 2.5.0 on June 2nd
 
 The following patch releases were made from earlier maintenance branches:

 * Apache Jackrabbit 2.2.12 on April 23rd    
 * Apache Jackrabbit 2.4.1 on April 3rd
 * Apache Jackrabbit 2.4.2 on June 11th
 
 This quarter also saw the first releases from the Jackrabbit Oak 
 subproject:
 
 * Apache Jackrabbit Oak 0.2.1 on May 7th
 * Apache Jackrabbit Oak 0.1 on April 3rd
 
 Note, there is no Oak 0.2 release since the release vote failed due to a
 license header issue. The issue was quickly resolved and the release re-cut
 into 0.2.1

o Community / Development

 * Unico Hommes and Christian Stocker joined the Jackrabbit team as 
 committers and PMC members.

 * Work on Jackrabbit Oak is gaining momentum: there where two Hackathons 
 in the last quarter during which great progress was made. This eventually 
 lead to the releases 0.1. and 0.2.1 as initially planned. 
 Currently we are discussing whether, how and what we want to contribute to 
 the .adaptTo(Berlin) 2012 conference in September. .adaptTo(Berlin) is a 
 technical meet up focused on the technical stack of Apache Sling including
 Apache Jackrabbit and Apache Felix and is addressed to all developers using 
 this stack or parts of it. Being part of that event would allow us to 
 broaden the community and further spark interest for Apache Jackrabbit Oak.
 
 * Alex Parvulescu has successfully taken up the role of a release manager.

 * There is renewed interest on the OCM codebase, driven by Ard Schrijvers. 
 We expect to be able to cut a new, long overdue OCM release in near future.

 * ModeShape, a JCR implementation from JBoss, is working with us to improve 
 the JCR test suite. To better facilitate this cooperation we may want to 
 split the test suite away from the main Jackrabbit release schedule.  
 
 * Jukka Zitting resigned as chairman of the Jackrabbit PMC due to his new
 role at the Incubator. Michael Dürig was elected and acknowledged as new
 chairman.

o Infrastructure

 We are still in progress of migrating from Confluence to the new CMS.

18 Apr 2012

Change the Apache Jackrabbit Project Chair

 WHEREAS, the Board of Directors heretofore appointed Jukka Zitting
 to the office of Vice President, Apache Jackrabbit, and

 WHEREAS, the Board of Directors is in receipt of the resignation
 of Jukka Zitting from the office of Vice President,
 Apache Jackrabbit, and

 WHEREAS, the Project Management Committee of the Apache Jackrabbit
 project has chosen by vote to recommend Michael Dürig as the
 successor to the post;

 NOW, THEREFORE, BE IT RESOLVED, that Jukka Zitting is relieved and
 discharged from the duties and responsibilities of the office
 of Vice President, Apache Jackrabbit, and

 BE IT FURTHER RESOLVED, that Michael Dürig be and hereby is
 appointed to the office of Vice President, Apache Jackrabbit, to
 serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification, or
 until a successor is appointed.

 Special Order 7A, Change the Apache Jackrabbit Project Chair,
 was approved by Unanimous Vote of the directors present.

21 Mar 2012 [Jukka Zitting / Shane]

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

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

o Releases

 The biggest news this quarter was the first stable Jackrabbit 2.4 release,
 about a year after Jackrabbit 2.2 was branched.

 * Apache Jackrabbit 2.4.0 on February 9th

 In the run-up to 2.4, we cut the following unstable 2.3.x releases:

 * Apache Jackrabbit 2.3.7 on January 24th
 * Apache Jackrabbit 2.3.6 on January 2nd
 * Apache Jackrabbit 2.3.5 on December 16th

 We made one patch release from the earlier 2.2 maintenance branch:

 * Apache Jackrabbit 2.2.11 on February 11th

 We also completed the end-of-life period of the last Jackrabbit 1.x
 maintenance branch, making the stable 2.x branches the only actively
 maintained versions of Jackrabbit.

o Community / Development

 No new committers or PMC members were added in this quarter.

 The work towards Jackrabbit 3 entered a major new phase as we decided
 to promote the effort from prototypes in the Jackrabbit sandbox to
 a new Jackrabbit subproject codenamed "Oak". This is a major rewrite
 of Jackrabbit, which is why we wanted to clearly separate the effort
 from work on the main Jackrabbit codebase. It is yet undecided whether
 the Oak codebase will eventually replace Jackrabbit trunk to become
 Jackrabbit 3.0 or if we want to rebrand the effort and branch it off
 to a separate TLP, possibly through the Incubator. Meanwhile we plan
 to start publishing early access versions of the Oak codebase as a
 series of monthly "Apache Jackrabbit Oak 0.x" releases (as the codename
 "Oak" is not unique enough for use as a standalone "Apache Oak" brand).

 Jukka Zitting wishes to resign as chairman of the Jackrabbit PMC due
 to his new role at the Incubator, so we have started the process of
 electing a new chairman.

o Infrastructure

 We are still in progress of migrating from Confluence to the new CMS.

21 Dec 2011 [Jukka Zitting / Doug]

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

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

o Releases

 We made the following unstable 2.3.x releases from Jackrabbit trunk.

 * Apache Jackrabbit 2.3.4 on November 29th
 * Apache Jackrabbit 2.3.3 on November 15th
 * Apache Jackrabbit 2.3.2 on November 2nd
 * Apache Jackrabbit 2.3.0 on October 3rd

 The following patch releases were made from earlier maintenance branches:

 * Apache Jackrabbit 2.2.10 on November 22nd
 * Apache Jackrabbit 2.2.9 on October 3rd
 * Apache Jackrabbit 2.1.6 on October 3rd
 * Apache Jackrabbit 2.0.5 on October 3rd
 * Apache Jackrabbit 1.6.5 on October 3rd

o Community / Development

 Bart van der Schans and Justin Edelson joined the Jackrabbit team
 as committers and PMC members.

 We adopted an even/odd versioning scheme for stable/unstable releases
 and started cutting unstable 2.3.x releases directly from trunk.
 A stable 2.4.0 release and the accompanying stable 2.4 maintenance
 branch is planned for January 2012.

 The end of life of Jackrabbit 1.x was announced, with 1.6.5 being
 the last 1.x release we plan to make.

 Active work on the new microkernel prototype targeting
 Jackrabbit 3.0 continues.

o Infrastructure

 We started working on migrating from Confluence to the new CMS.

21 Sep 2011 [Jukka Zitting / Doug]

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

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

o Releases

 We made one Jackrabbit 2.2.x patch release in this quarter:

 * Apache Jackrabbit 2.2.8 on August 23rd

o Legal / Branding

 No open issues.

o Community / Development

 No new committers or PMC members were added since our last report.

 Apache Jackrabbit was nominated for the 2011 Swiss Open Source Award
 in the community category. We attended the award ceremony on Tuesday,
 Sep 13th, and gave a short presentation about Jackrabbit, but the
 award went to another project.

 We are planning to cut the Jackrabbit 2.3.0 release from trunk in near
 future. To increase the rate at which latest work in the trunk gets
 released (it is already nine months since Jackrabbit 2.2), we are
 considering an odd/even versioning strategy where all odd releases 
 like 2.3.x are cut directly from trunk, and even-numbered stable
 maintenance branches like 2.4 get created every now and then for
 production-ready releases.

 Meanwhile we will be cutting new patch releases from earlier maintenance
 branches, including the old 1.6 branch whose end of life status will be
 announced along with the last patch release. Also, active work on the
 new microkernel prototype targeting Jackrabbit 3.0 continues.

o Infrastructure

 The planned migration from Confluence to the new CMS soon is still
 pending for action on our part.

Congratulations on being nominated for the 2011 Swiss Open Source award. Both Jackrabbit project and Clerezza podling were nominated.

15 Jun 2011 [Jukka Zitting / Roy]

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

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

o Releases

 We made three Jackrabbit 2.1.x and 2.2.x patch releases in this quarter:

 * Apache Jackrabbit 2.2.7 on June 7th
 * Apache Jackrabbit 2.1.5 on June 7th
 * Apache Jackrabbit 2.2.5 on March 18th

o Legal / Branding

 No open issues.

o Community / Development

 Dave Brosius and Alex Parvulescu joined the Jackrabbit project as
 committers and PMC members.

 A new Jackrabbit 3 prototype has been started based on the proposed
 microkernel concept.

o Infrastructure

 We will be migrating our web site from Confluence to the new CMS soon.

16 Mar 2011 [Jukka Zitting / Noirin]

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

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

o Releases

 We made three Jackrabbit 2.2.x patch releases in this quarter:

 * Apache Jackrabbit 2.2.4 on February 15th
 * Apache Jackrabbit 2.2.2 on January 26th
 * Apache Jackrabbit 2.2.1 on January 11th

o Legal / Branding

 No open issues.

o Community / Development

 Our efforts to better identify key contributors and offer them
 committership are starting to bear fruit. In this quarter
 Berry van Halderen and Thomas Draier joined us as committers and
 PMC members, and we are expecting to welcome more members soon.

 We are happy to see Apache Chemistry reach TLP status, and contributed
 a supporting quote to the press release about their graduation.

o Infrastructure

 We have consensus on moving our web site from Confluence to the new
 CMS, but have yet to start the migration.

15 Dec 2010 [Jukka Zitting / Roy]

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

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

o Releases

 The biggest news this quarter is the release of Jackrabbit 2.2:

 * Apache Jackrabbit 2.2.0 on December 14th

 We also made a number of smaller patch releases:

 * Apache Jackrabbit 2.1.3 on December 7th
 * Apache Jackrabbit 2.1.2 on October 31st
 * Apache Jackrabbit 2.0.3 on October 31st
 * Apache Jackrabbit 1.6.4 on October 12th

o Legal / Branding

 We have updated our project branding to match the new branding guidelines
 except for a few details that still need to be discussed on trademarks@.

o Community / Development

 No new committers were added in this quarter, but a few old committers
 have become active again and we're seeing good levels of activity from
 other contributors.

 Day Software, the employer of many Jackrabbit committers, was recently
 acquired by Adobe. We expect this acquisition to have little impact on
 their contributions to Jackrabbit.

o Infrastructure

 We are currently using a Confluence wiki for managing our project web
 site, but would like to migrate to an alternative system. The most
 promising alternatives are the new CMS or an svnpubsub-based site built
 with Maven.

22 Sep 2010 [Jukka Zitting / Bertrand]

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

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

o Releases

 We released one Jackrabbit 2.1 patch release in August:

 * Apache Jackrabbit 2.1.1 on August 11th

o Legal

 We are aware of the new branding guidelines, but have yet to review
 our web site and other documentation for compliance.

o Community / Development

 No new committers were added in this quarter. There's been some interest
 on the user list about people getting more involved in maintaining some
 less active parts of our codebase. We're trying to encourage and mentor
 such efforts.

 As usual, we saw a temporary dip in mailing list and development activity
 during the summer, but we're already back to normal. The Jackrabbit trunk
 has seen quite a few improvements especially in access control,
 thread-safety and performance, and we plan to ship these improvements
 in a Jackrabbit 2.2 release in near future.

 We received a vulnerability report through security@apache.org, but
 the problem turned out to be a normal bug with no security implications.

o Infrastructure

 The new Hudson master seems to be working better than the previous one.

16 Jun 2010 [Jukka Zitting / Jim]

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

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

o Releases

 Jackrabbit 2.1 was released in April:

   * Apache Jackrabbit 2.1.0 on April 22nd

 We also made maintenance releases from the 1.6 and 1.4 branches:

   * Apache Jackrabbit 1.6.2 on June 7th
   * jackrabbit-core 1.4.12 on June 7th

o Legal

 The question in LEGAL-50 about redistribution of the standard JCR API
 jar has now been officially resolved. Thanks to the legal team for the
 closure on this! With LEGAL-50 resolved, we have no open legal issues.

 We use RAT for automatic license header checks as a part of our normal
 Hudson CI builds, and the accuracy of our LICENSE and NOTICE files is
 manually reviewed before each release.

o Community / Development

 No new committers were added in this quarter. This is our third consecutive
 quarter with no new committers. It looks like we need to pay more attention
 to helping out and mentoring contributors. We have traditionally maintained
 relatively high entry criteria for new committers.

 Community diversity remains an issue we pay attention to, as the bulk of
 Jackrabbit development is still done by one company. In this quarter we've
 had eight people committing to Jackrabbit trunk, six of whom are employees
 of Day Software. We satisfy the criteria of at least three independent
 active committers and the community is healthy. Thus I don't see diversity
 as an immediate problem for Jackrabbit, but it's a topic we are aware of
 especially in light of the few new committers we've recently attracted.

o Infrastructure

 The Confluence upgrade caused some breakage on our web site and required
 manual fixing. We are not too happy with our current Confluence
 auto-export setup, and are considering other options.

 Some of our Hudson builds have been failing due to generic Hudson problems.
 We're hoping that the new master server will solve these issues. We're
 also looking forward to a chance to set up a Sonar instance for Apache
 projects.

Doug to initiate a discussion as to what items the board should periodically request be included in reports (example: diversity) to the mailing list.

17 Mar 2010 [Jukka Zitting / Brian]

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

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

o Releases

 Jackrabbit 2.0 was released in January after all the main issues in
 previous beta releases had been fixed:

   * Apache Jackrabbit 2.0 beta5 on January 11th
   * Apache Jackrabbit 2.0 beta6 on January 18th
   * Apache Jackrabbit 2.0.0 on January 27th

 We also made one maintenance release from the 1.6 branch:

   * Apache Jackrabbit 1.6.1 on January 21st

o Legal

 We have updated our NOTICE files as discussed in LEGAL-62 and LEGAL-59.

o Community / Development

 No new committers were added in this quarter.

 With Jackrabbit 2.0 out, we've started discussing about what we want to
 achieve in Jackrabbit 3, our next major release. These design discussions
 have been pretty lively and it's good to see many voices from outside the
 core development team participating in the email threads. The first bits
 of related prototype code have already hit our sandbox area in svn.

o Infrastructure

 No open issues.

16 Dec 2009 [Jukka Zitting / Justin]

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

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

o Releases

 Jackrabbit 2.0 reached beta status with the following releases:

   * Apache Jackrabbit 2.0 alpha11 on September 23rd
   * Apache Jackrabbit 2.0 beta1 on October 30th
   * Apache Jackrabbit 2.0 beta3 on November 25th
   * Apache Jackrabbit 2.0 beta4 on December 12th

 We also made two releases from the old 1.4 maintenance branch:

   * jackrabbit-core 1.4.10 on September 15th
   * jackrabbit-core 1.4.11 on September 23rd

 We made two releases of the Jackrabbit parent POM:

   * org.apache.jackrabbit:jackrabbit:4 on September 14th
   * org.apache.jackrabbit:jackrabbit:5 on October 4th

o Legal

 We're tracking the LEGAL-50 and LEGAL-62 issues for further comments,
 but currently we have no open legal action items.

 We are interested in figuring out how the new trademark policy affects
 our logo, website and releases, and what steps we need to take to meet
 the policy.

o Community / Development

 Jackrabbit participated in the Content Technology track and the NoSQL
 meetup at ApacheCon US 2009.

 The development branch related to database connection pooling has been
 merged back to Jackrabbit trunk and the results are included in the
 Jackrabbit 2.0 beta4 release.

 We've discussed with Apache Sling about taking over some OSGi bundling
 code they've written for Jackrabbit. On the other hand there is some
 code in Jackrabbit that's only being used by Sling and that might end up
 being adopted by them. We're considering making parts of our svn tree
 writable by members of both projects to simplify such cooperation.

o Infrastructure

 We received some spam through Nabble on our dev@ list, and have asked
 Nabble to disable posts through the web interface.

 We reconfigured the Jackrabbit entry on Ohloh to get code statistics
 from the Git mirror at git.apache.org since the svn history seen by Ohloh
 didn't include the time when Jackrabbit was still incubating.

23 Sep 2009 [Jukka Zitting / Doug]

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

 The big news this quarter is the release of Jackrabbit 1.6.0:

   * Apache Jackrabbit 1.6.0 on August 11th

 The following patch releases were made from earlier maintenance branches:

   * Apache Jackrabbit 1.5.7 on August 3rd
   * jackrabbit-core 1.4.10 on September 15th

 We made two internal releases of the Jackrabbit parent POM:

   * org.apache.jackrabbit:parent:3 on June 26th
   * org.apache.jackrabbit:parent:4 on September 15th

 We also continued releasing Jackrabbit 2.0 alphas:

   * Apache Jackrabbit 2.0 alpha3 on July 3rd
   * Apache Jackrabbit 2.0 alpha4 on July 14th
   * Apache Jackrabbit 2.0 alpha7 on August 10th
   * Apache Jackrabbit 2.0 alpha8 on August 18th
   * Apache Jackrabbit 2.0 alpha9 on August 26th

o Legal

 We have asked (see LEGAL-50) the legal team to review the terms under
 which we are redistributing the JCR API jar. The purpose of this is to
 complete the legal records, and this issue is not a blocker to our
 current releases.

 Recent legal discussions regarding the contents of the NOTICE files
 (see for example LEGAL-62) suggest that we have been including some
 unnecessary information in our NOTICEs. We will review our NOTICE files
 before the 2.0 release to comply with the consensus on legal-discuss@.

o Community / Development

 Sébastien Launay joined the Jackrabbit team as a committer and PMC member.

 With the 1.6 release our JCR 1.0 work has entered maintenance mode and
 we're focusing on releasing Jackrabbit 2.0 shortly after JCR 2.0 becomes
 available. We reached JCR 2.0 feature-completeness with the 2.0 alpha9
 release, and that release was also used for the JCR 2.0 RI and TCK
 candidates. The JSR 283 final approval ballot has just passed, and we
 expect the final JCR 2.0 release to follow soon.

 The main author of the JCROM project that implements an alternative to
 the Jackrabbit OCM (object content mapping) component contacted us about
 bringing the JCROM code to Jackrabbit and possibly merging with our
 existing OCM code.

o Infrastructure

 We are now using the Nexus server at repository.apache.org for staging
 and deploying our releases to the central Maven repository.

 The monthly Google Analytics reports we set up earlier this year don't
 seem to be reaching the dev@ list anymore. To work around this we're now
 sharing the reports via svn and our web site.

17 Jun 2009 [Jukka Zitting / J Aaron]

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 made the following releases from the 1.5 branch:

   * Apache Jackrabbit 1.5.4 on April 7th
   * Apache Jackrabbit 1.5.5 on April 28th
   * Apache Jackrabbit 1.5.6 on June 4th

 We also made the first alpha release of the upcoming Jackrabbit 2.0:

   * Apache Jackrabbit 2.0 alpha1 on June 4th

o Legal

 The current Jackrabbit trunk and the 2.0 alpha1 release have a system
 dependency to an early "for review only" version of the JCR 2.0 API jar
 from JSR 283. No major concerns were raised when this case was discussed
 on the legal-discuss@ mailing list.

o Community / Development

 Jackrabbit was present at the ApacheCon EU where we also organized
 a quite successful JCR meetup.

 The CMIS effort that started in the Jackrabbit sandbox has now become
 the Apache Chemistry project in the Incubator. The other podling with
 Jackrabbit as the sponsoring PMC, Apache Sling, is just about to graduate
 into a standalone TLP.

 The JCR 2.0 specification (JSR 283) is expected to become final in a few
 months, as soon as we've completed the required RI and TCK work in Jackrabbit
 trunk. We're producing source-only alpha releases of the 2.0 codebase to
 give people a chance to review all the new features and to better track our
 progress.

 We are also planning to release Jackrabbit 1.6 as the last minor release
 from the 1.x branch that's still based on the JCR 1.0 API.

o Infrastructure

 We are about to start using the Nexus installation at repository.apache.org
 for staging and deploying our releases to the Maven repository.

Again: any noteworthy regarding the release that the PRC can help with? Jukka to pursue.

18 Mar 2009 [Jukka Zitting / J Aaron]

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 made the following two releases from the 1.5 branch:

  * Apache Jackrabbit 1.5.2 on January 20th
  * Apache Jackrabbit 1.5.3 on February 27th

 The 1.5.2 release contained a fix to the security issue CVE-2009-0026
 (Cross site scripting issues in webapp). This was the first security
 issue we had received through security@, and we had some initial
 confusion on how we should react to such issues. The security team was
 very helpful in guiding us.

 We also made the following component releases from the older 1.4 branch:

  * jackrabbit-core 1.4.7 on January 20th
  * jackrabbit-core 1.4.8 on January 29th
  * jackrabbit-core 1.4.9 on March 3rd

 To get the JCR Commons subproject started we created and released a
 standalone Jackrabbit parent POM:

  * org.apache.jackrabbit:parent:2 on February 6th

o Legal

 No issues at the moment.

o Community / Development

 Michael Duerig joined the Jackrabbit team as a committer and PMC member.

 The JCR Commons subproject was started after related discussion and a
 vote. We are still in the process of setting up this new subproject.
 To respond to earlier feedback from the board: we decided *not* to move
 these components to Apache Commons to avoid splitting the development
 community.

 There is continuous interest in the JCR-based CMIS implementation we
 are developing in our sandbox. Florent Guillaume, who is not (yet) an
 Apache committer, is working on a related codebase in an external
 Mercurial repository under the working name "Chemistry". There are
 concerns over the development being split over different source
 repositories. For now we hope to bring all development into Apache svn
 and plan to manage the effort as organic growth within the Jackrabbit
 project, possibly targetting a subproject once the effort matures.
 Another option is to push the effort to the Incubator as a new podling.

 Starting with the 1.5.3 release our release notes include a section
 that acknowledges everyone who has contributed to that release. The
 contents of this section is based on the contribution report in Jira.

 Work in Jackrabbit trunk continues and I expect us to release
 Jackrabbit 1.6.0 in a few months. After the 1.6 release we'll most
 likely start targeting Jackrabbit 2.0 for release later this year.
 Jackrabbit 2.0 will require Java 5 as the base platform.

o Infrastructure

 We have migrated our Hudson CI builds to the new minerva.apache.org
 slave server.

 The CI builds are now configured to deploy snapshots to the new
 repository.apache.org server. We are planning to start using the
 repository.apache.org server also for staging Maven releases.

 The Jackrabbit zone that we used earlier for CI builds is being
 removed as we no longer need it.

 We have configured monthly Google Analytics reports to be sent to our
 development mailing lists. This is not truly optimal as each report
 needs to be separately approved by a moderator (due to the variable
 sender address), but for now this works well enough as a mechanism of
 sharing site statistics with everyone interested.

17 Dec 2008 [Jukka Zitting / Bertrand]

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 Apache Jackrabbit 1.5.0 on December 8th.

 We also made the following patch releases from the 1.4 branch:
 * jackrabbit-core 1.4.6 on October 7th
 * jackrabbit-classloader 1.4.1 on October 2nd
 * jackrabbit-jcr-server 1.4.1 on September 30th

o Legal

 We use Google Analytics to track usage of our web site. We posted a
 privacy policy that mentions the Analytics use on our web site and
 continue to work with legal-discuss@ to resolve concerns that were
 raised about the use of Google Analytics.

o Community

 Claus Koell joined the Jackrabbit team as a committer and PMC member.

 The slump in community activity over late summer seems to be gone and
 we're back to normal levels of mailing list and commit activity.

 Based on interest to the CMIS implementation effort (see below),
 we have extended write access in our sandbox area in svn to
 all Apache committers.

 We are considering starting a "JCR Commons" subproject for managing
 the development and release of a number of our components that are not
 tightly coupled with the Jackrabbit content repository implementation.
 This subproject would keep using our existing mailing lists but would
 have its own web site (under http://jackrabbit.apache.org/commons/)
 and separate issue trackers and release cycles for each component.
 See http://markmail.org/message/qqlvlwpgi5oauak6 for more details.

o Development

 Development in trunk continues with post-1.5 features, and I expect us
 to release Jackrabbit 1.6 early next year. Jackrabbit 2.0 (and the JSR
 283 reference implementation) will probably be released later next year.

 A new sandbox component was started for an effort to implement the
 proposed Content Management Interoperability Services (CMIS) specification
 on top of a JCR content repository.

o Infrastructure

 We created a new Jira project (JCRCMIS) for the CMIS implementation effort
 and plan to create more assuming the JCR Commons subproject gets started.
 We've enabled wiki markup and the patch-available workflow in the JCRCMIS
 project. If these features work well, we will enable them also in our main
 JCR project in Jira.

No identified concerns over "indemnify and hold harmless" clause.

The board is very happy with the initiative taken to publish a privacy policy.

We noted that Apache Commons is an option available to them, should they wish to explore that alternative.

17 Sep 2008 [Jukka Zitting / Henning]

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

 No releases were made since the last report.

o Legal

 We use Google Analytics to track usage of our web site. We are working
 with site-dev@ and legal-discuss@ to resolve the recent concerns about
 how the site usage data can be made available equally to everyone.

o Community

 No new committers or PMC members were added since the last report.

 There has been a decrease in mailing list and commit activity in the past
 quarter and we've seen some cases of issues or questions being dropped.
 This is partly because of the summer vacations but also due to a number
 of core committers having been otherwise occupied. We'll keep an eye on
 the situation and expect things to normalize soon.

 We will participate and present Apache Jackrabbit in the upcoming
 ApacheCon US.

o Development

 We keep working towards Jackrabbit 1.5 in near future and Jackrabbit 2.0
 (and the JSR 283 reference implementation) later on.

o Infrastructure

 No issues at the moment.

Henning to communicate that every project that uses Google Analytics needs to have a published privacy policy.

25 Jun 2008 [Jukka Zitting / Greg]

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

 Since the last report we made a number of small component releases and
 one older maintenance release. The releases were:

   * March 26, 2008: jackrabbit-core 1.4.2
   * April 2, 2008: jackrabbit-jcr-commons 1.4.2
   * April 9, 2008: jakcrabbit-jcr-rmi 1.4.1
   * May 8, 2008: Apache Jackrabbit 1.3.4
   * May 8, 2008: jackrabbit-core 1.4.3
   * May 9, 2008: jackrabbit-core 1.4.4
   * June 9, 2008: jackrabbit-core 1.4.5

o Legal

 The license issue noted in the previous report (external party using our
 code without proper attribution) has been resolved.

 We have been clarifying our LICENSE and NOTICE files based on recent
 discussions on legal-discuss@ and the incubating sling-dev@ mailing lists.

o Community

 Esteban Franqueiro and Alexander Klimetschek became committers and
 PMC members of Apache Jackrabbit.

 Many members of our community attended ApacheCon EU and we also
 organized a free-for-everyone JCR community gathering along the conference.

o Development

 We are working towards Jackrabbit 1.5 in near future and Jackrabbit 2.0
 (and the JSR 283 reference implementation) later on.

o Infrastructure

 We switched to Hudson for our CI builds.

 We requested and got FishEye indexing for our codebase.

 The svn.eu.apache.org mirror is much appreciated as most of our
 committers are based in Europe.

19 Mar 2008 [Jukka Zitting / Jim]

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

 Apache Jackrabbit 1.4 was released in January.

 We are considering switching to releasing individual components
 in a more frequent and fine-grained manner. So far Jackrabbit releases
 have contained new versions of all Jackrabbit components.

 The first component release, jackrabbit-core 1.4.1, was made in February.

o Legal

 Apache Jackrabbit uses or bundles no cryptographic code, so there is no
 need for export control notifications.

 We have identified a minor license violation by an external party
 bundling Jackrabbit code without meeting all the ALv2 requirements
 (no NOTICE file, etc.). With help from the legal team, we have notified
 the party in question and expect the issue to be resolved soon.

o Community

 The Jackrabbit PMC has voted to invite Esteban Franqueiro to be a Jackrabbit
 committer and PMC member. We are waiting for the CLA to proceed with the
 committer account and other administrative bits.

 We are planning to have a JCR community gathering event right next to the
 ApacheCon EU next month in Amsterdam.

o Development

 The 1.4 release was well received, and with increased usage we've also
 seen many requests to make the default installation and out-of-the-box
 experience smoother for new users. We're working on addressing those needs.

 The ongoing work towards the JCR 2.0 reference implementation continues,
 and with major new features and changes entering the codebase we may see
 some instability of the trunk during the months ahead. On the other hand
 there's recently been much focus on improving test coverage and more test
 automation, which should help us maintain stability of the codebase.

 Some of our users are not yet ready to upgrade from 1.3 to 1.4, so we
 are working on the 1.3 maintenance branch to produce a 1.3.4 release with
 selected bug fixes and improvements from newer releases.

o Infrastructure

 Our web site is now managed using Confluence.

 We have had problems with our private Continuum installation in the
 Jackrabbit zone, and so we are currently migrating our CI builds to the
 Hudson zone.

19 Dec 2007 [Jukka Zitting / Justin]

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

 Apache Jackrabbit 1.3.3 was released in October.

 We are currently working on the 1.4 release. Jackrabbit 2.0, with
 JCR 2.0 support, will likely be released next year.

o Community

 Martijn Hendriks and Ard Schrijvers were added as a committers and
 PMC members.

 The recent decision by the Apache Jakarta PMC to close the Slide project
 has brought a number of people interested in WebDAV to the Jackrabbit
 mailing lists. Most notably there is interest in extending and further
 developing the WebDAV client library in Jackrabbit. We may well end up
 working together with the new Apache HttpComponents project on this
 front.

o Development

 The main development focus at the moment it on the 1.4 release, but
 there's already some work towards implementing the new JCR 2.0 features
 being specified by Jsr 283.

 Once the 1.4 release is out we will need to decide when and how to
 split Jackrabbit into separate JCR 2.0 development and JCR 1.0
 maintenance branches.

 A sandbox project was started for prototyping the Jackrabbit Next
 Generation Persistence proposal that tries to address some long term
 architectural issues in Jackrabbit.

o Infrastructure

 We have acquired a Confluence wiki space for managing our project web
 site but we have yet to migrate the web site contents.

Approved by General Consent.

19 Sep 2007 [Jukka Zitting / Jim]

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

 Apache Jackrabbit 1.3.1 was released in July.

 We are currently working on the 1.4 release, due out later this year.
 Jackrabbit 2.0, with JCR 2.0 support, will likely be released next year.

o Community

 Christoph Kiehl and Thomas Müller were added as a committers and
 PMC members. Brian Moseley resigned to emeritus status.

 The Jackrabbit PMC decided to sponsor the new incubating Sling project.
 There is lots of community overlap and interest in seeing more open
 source tools built on top of the JCR API.

 Our two Google Summer of Code projects ended successfully, even though
 the amount of community interaction related to the projects was lower
 than expected. The resulting JCR example applications will be used as
 a part of Jackrabbit documentation.

 There will be a JCR session in ApacheCon US, and JCR training (assuming
 enough attendance) in both ApacheCon US and OS Summit Asia. The Sling
 project will also be presented.

o Development

 We are seeing lots of development related especially to query features
 and a new storage model for binary content. There has also been
 interest in threads and locking behaviour within Jackrabbit core.

 We are promoting two prominent subprojects, the OCM and SPI
 layers, to release components in Jackrabbit 1.4.

 JSR 283 has released the public draft of the upcoming JCR 2.0
 specification, and we have started working on implementing the new
 new features. The goal is to make Jackrabbit 2.0 (or an early snapshot
 of the release) the reference implementation of JSR 283.

o Infrastructure

 We are considering switching from MoinMoin to Confluence for our wiki
 and using Confluence to manage also our official web site.

Approved by General Consent.

20 Jun 2007 [Jukka Zitting / Justin]

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

 Apache Jackrabbit 1.3 was released in April.

 We are currently working on the 1.3.1 release, and initial planning
 for a 1.4 release later this year and 2.0 next year has begun.

o Community

 Christophe Lombart was added as a committer and PMC member.

 An object-content mapping tool was successfully moved from the
 incubating Graffito project into a Jackrabbit subproject.

 Jackrabbit received lots of attention in ApacheCon EU where we
 had one tutorial and one normal session on Jackrabbit and JCR.
 A Jackrabbit BOF session also took place, although it ended up
 being quite unstructured.

 We have two Google Summer of Code projects in progress this summer.
 Both projects have been relatively quiet so far, but hopefully we'll
 get them up to speed soon.

 Jacco van Weert has announced a nice JCR Controller tool on the user
 mailing list and is interested in bringing it to Jackrabbit through
 the Apache Incubator.

o Development

 Jackrabbit is being actively developed on a number of fronts. Increasing
 numbers of good patches are coming in, and various technical and
 architectural issues are being actively debated on the mailing lists.

 The public draft of the upcoming JCR 2.0 specification will probably
 be soon released by JSR 283. We are planning to use the public draft
 as the main requirements document when implementing the changes and
 new features required to make Jackrabbit 2.0 the reference
 implementation of JSR 283.

It was suggested that, following the Jackrabbit example (which was from the Incubator report guidelines), that all TLP projects provide a small description of what the TLP "does".

Approved by General Consent.

28 Mar 2007 [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 communities.

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 into 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.

Approved by General Consent.

20 Dec 2006 [Jukka Zitting / Cliff]

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

The Apache Jackrabbit project has progressed nicely since the September
status report. We have no board-level issues at this time.

o Releases

 We have released two versions of Apache Jackrabbit: 1.1 in October and
 1.1.1 in December.

 The 1.2 release is scheduled to happen by the end of the year.

o Community

 No new committers have been added since September. One contributor
 was just elected for committership, but the process is still pending
 on us receiving the required CLAs.

 The number of active contributors has grown lately, and I expect
 to see new committers being elected in near future. Most notably we've
 seen a number of contributions from employees of Cognifide, a consulting
 company with JCR expertise. A CCLA has been requested.

 There were two short Apache Jackrabbit presentations during the
 ApacheCon US and some discussion on potential cooperation with other
 related Apache projects.

o Development

 The Jackrabbit build environment was recently upgraded to Maven 2 along
 with a restructuring of the Jackrabbit component projects.

 An initial clustering implementation was added to Jackrabbit core and
 will go out as a beta feature in the 1.2 release.

 The Jackrabbit dependencies to Apache Lucene and Apache Derby were
 upgraded to more recent versions.

 A number of forward-looking design discussions have occurred on the
 mailing list, often based on feedback from outside the core development
 group.

o Infrastructure

 We've requested a Solaris zone for setting up nightly builds and
 automating integration tests and Maven reporting.

Approved by General Consent.

20 Sep 2006 [Jukka Zitting / Greg]

The Apache Jackrabbit project has progressed steadily since our last
status report. We have no board-level issues at this time.

o We voted in Julian Reschke as a new committer and PMC member.

o The Apache Jackrabbit 1.1 release is scheduled to happen at the
 end of September.

o The recent face-lift of our web site received some attention due to
 the "customized" Apache feather logo included in the design. The
 issue was discussed within the PRC and for now we are back to using
 the standard Apache logo to link back to the foundation.

o Day Software has contributed an initial SPI layer for the JCR API
 based on earlier work within the JSR 283 expert group. The ongoing
 SPI effort has potential to clarify and better modularize the
 Jackrabbit core.

o We have discussed with the incubating Apache Graffito project on
 perhaps moving the generic object-content mapping tool they are
 developing into the Apache Jackrabbit project where the tool could
 enjoy a wider community of interested users and developers. The
 feedback within both projects has been positive.

o Our Google Summer of Code project ended successfully with a backup
 tool that implements almost all of the planned features. The missing
 feature (restoring version histories) identified a need for
 structural changes within the Jackrabbit core and we are working
 on solving this issue. The GSoC experience also sparked a good
 discussion on the policies of accepting code changes.

Justin asked if the contribution for SPI recorded as a grant? Jim noted that we had not received a software grant for the code, but that Day Software does have a CCLA on file. Greg was to contact the PMC to get clarification on whether the SPI contribution required a grant.

At this point Justin asked if the ASF should have a policy on moving code between projects? It was noted that the Apache License allows for any PMC to use code in any other PMCs codebase, since it is assigned to the ASF and not to a PMC. Cliff noted that there is ongoing discussion regarding the scope of patents in this case, and what is meant by "the work" when code is copied or moved. Cliff will continue to work this patent angle, but the board agreed that we have no policy in place other than all code is available for reuse by all PMCs, which is implicit and implied in the license.

Approved by General Consent

16 Aug 2006

Change the Chair of the Jackrabbit PMC

  WHEREAS, the Board of Directors heretofore appointed Roy
  T. Fielding to the office of Vice President, Apache Jackrabbit,
  and

  WHEREAS, the Board of Directors is in receipt of the
  resignation of Roy T. Fielding from the office of Vice
  President, Apache Jackrabbit;

  NOW, THEREFORE, BE IT RESOLVED, that Roy T. Fielding is
  relieved and discharged from the duties and responsibilities of
  the office of Vice President, Apache Jackrabbit, and

  BE IT FURTHER RESOLVED, that Jukka Zitting be and hereby is
  appointed to the office of Vice President, Apache Jackrabbit,
  to serve in accordance with and subject to the direction of the
  Board of Directors and the Bylaws of the Foundation until
  death, resignation, retirement, removal or disqualification, or
  until a successor is appointed.

 Special Order 6A, Change the Chair of the Jackrabbit PMC, was
 approved by Unanimous Vote.

19 Jul 2006 [Roy T. Fielding / Dirk]

The Apache Jackrabbit project has had a relatively quiet two months
since our last report.  We have not added any new committers and
we have no board issues at this time.

We successfully released Apache Jackrabbit 1.0.1 on June 2nd
and are currently working on a 1.1 release.  Most of the effort
has been around cleaning up the edge cases as more new developers
send in bug reports related to their own application's use of
the 1.0 release.  We also have one active SoC project working on
a backup system for JCR repositories.  Hopefully, we'll be seeing
more patches soon from developers outside the core committers.
I would be happier if we had some new blood to nominate for the PMC.

At some point over the next two months, I am hoping to turn over
the Jackrabbit PMC chair position to someone else on the project.
Being chair of two different projects is a bit too distracting
and I think more people need to learn how to do it.

27 Jun 2006 [Roy T. Fielding / Dirk]


Tabled due to time constraints.

24 May 2006 [Roy Fielding / Dirk]

The Apache Jackrabbit project has had a relatively quiet month
since our last report.  We have no board issues at this time.

The response to our 1.0 release has been very positive and the
number of active participants on the dev list has increased
substantially. Many of the Jackrabbit developers attended the
JSR 283 face-to-face meeting in Basel, Switzerland, on May 2-3.
The JSR 283 EG agreed that Jukka Zitting could publish a
summary of what was being planned for future JCR API revisions
to the public Apache lists.  Issue items and proposals for
the JCR 1.1 and 2.0 APIs are being tracked at
<https://jsr-283.dev.java.net/>.  All of the Jackrabbit
committers are also members of the JSR 283 expert group.

Approved by General Consent.

26 Apr 2006 [Roy Fielding / Sander]

Over the past month, Apache Jackrabbit completed its graduation from
incubator, moved to its new home at jackrabbit.apache.org, and made
our big 1.0 release using the mirrors.

 http://jackrabbit.apache.org/
 http://www.apache.org/dist/jackrabbit/RELEASE-NOTES.txt

The only thing of board interest is that we have implemented the
file header proposed on legal-discuss last year.

/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements.  The ASF licenses this file to You
* under the Apache License, Version 2.0 (the "License"); you may not
* use this file except in compliance with the License.
* You may obtain a copy of the License at
*
*      http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/

Approved by General Consent.

6. Special Orders

15 Mar 2006

Establish the Apache Jackrabbit Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software related to the Content Repository for Java
 Technology API and its implementation as the Apache Jackrabbit
 content repository, for distribution at no charge to the
 public.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the "Apache Jackrabbit PMC", be
 and hereby is established pursuant to Bylaws of the Foundation;
 and be it further

 RESOLVED, that the Apache Jackrabbit PMC be and hereby is
 responsible for the creation and maintenance of open-source
 software and documentation related to the Content Repository
 for Java Technology API and its implementation as the Apache
 Jackrabbit content repository and tool sets, based on software
 licensed to the Foundation; and be it further

 RESOLVED, that the office of "Vice President, Apache
 Jackrabbit" be and hereby is created, the person holding such
 office to serve at the direction of the Board of Directors as
 the chair of the Apache Jackrabbit PMC, and to have primary
 responsibility for management of the projects within the scope
 of responsibility of the Apache Jackrabbit PMC; and be it
 further

 RESOLVED, that the persons listed immediately below be and
 hereby are appointed to serve as the initial members of the
 Apache Jackrabbit PMC:

   Tobias Bocanegra   <tobias.bocanegra@day.com>
   Roy T. Fielding    <fielding@gbiv.com>
   Stefan Guggisberg  <stefan.guggisberg@gmail.com>
   Serge Huber        <shuber2@jahia.com>
   Felix Meschberger  <Felix.Meschberger@day.com>
   Brian Moseley      <bcm@osafoundation.org>
   David Nuescheler   <david.nuescheler@gmail.com>
   Dominique Pfister  <dominique.pfister@day.com>
   Peeter Piegaze     <peeter.piegaze@day.com>
   Edgar Poce         <edgarpoce@gmail.com>
   Marcel Reutegger   <marcel.reutegger@gmx.net>
   Paul Russell       <prussell@apache.org>
   Angela Schreiber   <anchela@day.com>
   Sylvain Wallez     <sylvain@apache.org>
   Jukka Zitting      <jukka.zitting@gmail.com>

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Roy T. Fielding be
 appointed to the office of Vice President, Jackrabbit, to serve
 in accordance with and subject to the direction of the Board of
 Directors and the Bylaws of the Foundation until death,
 resignation, retirement, removal or disqualification, or until
 a successor is appointed; and be it further

 RESOLVED, that the Apache Jackrabbit PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Jackrabbit Project; and be it further

 RESOLVED, that the Apache Incubator PMC shall, upon deciding
 that the Jackrabbit incubating project has graduated, transfer
 all oversight and responsibility for the Jackrabbit incubating
 project and its artifacts to the Apache Jackrabbit PMC.

 Resolution 6A, Establish the Apache Jackrabbit Project,
 was approved by Unanimous Vote.

15 Mar 2006

Jackrabbit accomplished its first official incubating release with version
0.9 of the Apache Jackrabbit reference implementation and JCR-RMI tools. Day
Software has confirmed that the version 0.9 jars have passed the JCR 1.0 TCK
with the current exclude list.

We are now getting reorganized for graduation from the Incubator to our own
top-level project at the Apache Software Foundation. The Jackrabbit
committers voted on March 11, 2006, to request graduation. In addition, we
made a call to refresh the list of active committers for an accurate
presentation to the board; Stefano Mazzocchi, Gianugo Rabellino, Tim Reilly,
and Andrew Savory have requested emeritus status, meaning that they won't be
listed on the initial project management committee but are welcome to come
back if they choose to rejoin the project at a later time.

18 Jan 2006

 Jackrabbit added four new committers to the project this quarter:

 Serge Huber
 Felix Meschberger
 Brian Moseley
 Angela Schreiber

in recognition of their outstanding and sustained contributions to the
project. Jukka Zitting has volunteered to be the RM for our first set of
incubating releases. We plan to seek graduation from incubator as soon as we
have a track record for a successful release vote.

26 Oct 2005

The Apache Jackrabbit podling is slowly recovering from the impact of
finalizing JSR 170, initializing JSR 283 (the next JCR specification
revision EG), and the summer holiday schedule.  We are in the process
of reconfiguring our source directories for an eventual 1.0 release
and Maven 2 support.  No new committers were added this quarter,
though we expect more to be added soon.

28 Jul 2005

Jackrabbit has attracted public interest from many different
projects, both open source and commercial in nature, and has over
250 people reading the developer list.  During the past quarter
we added one new committer, Edgar Poce, and cleared the minimum
threshold of three independent committers.

The big news is that JCR, the Content Repository for Java
Technology 1.0 API, has been completed by the JSR 170 expert group
and received final approval from the J2SE/EE executive committee
at the end of May.  We are currently working on restructuring the
Jackrabbit project directories in preparation of an eagerly
anticipated first release candidate and passing the official TCK,
at which point we are hoping to graduate from Incubator to
TLP status for the 1.0 release.

27 Apr 2005

http://incubator.apache.org/jackrabbit/
http://incubator.apache.org/projects/jackrabbit.html

Jackrabbit is doing well as a project and is attracting interest
both within other Apache projects (Lenya and Graffito in
particular) as well as from new folks in the Java community.
We added two new committers, Jukka Zitting and Dominique Pfister,
and have received sustained contributions from Serge Huber,
Edgar Poce, Angela Schreiber, Felix Meschberger, and others.

Jackrabbit's only problem right now is continued reliance on
JCP EG private discussions due to the unfinished nature of the
JSR 170 Content Repository for Java Technology API.  JSR 170 is
expected to be submitted for final draft status in early May,
after which all of the discussion can be moved to Apache lists.
We anticipate graduating from Incubator sometime soon after that.

20 Oct 2004

The Jackrabbit project has completed all of the Incubator checklist
items in terms of moving to Apache and getting the IP transfer done.
With the help of Maven, we have a full website set up at

 http://incubator.apache.org/jackrabbit/

with a few link bugs due to the svn/viewcvs integration.  Our big
task from now to graduation is to get the community more involved
in development, planning features, integrating with some of the DB
projects, and scoping out interesting applications to build on top
of the interface.