manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Proposed board report, August 2015
Date Mon, 03 Aug 2015 16:04:41 GMT
Here it is:

ManifoldCF PMC Chair: Karl Wright (
Date: August 2015

Project description

ManifoldCF is an effort to provide an open source framework for connecting
source content repositories like Microsoft Sharepoint and EMC Documentum, to
target repositories or indexes, such as Apache Solr, OpenSearchServer or
ElasticSearch. ManifoldCF also defines a security model for target
repositories that permits them to enforce source-repository security


ManifoldCF graduated from the Apache Incubator on May 16, 2012.  Since then,
there have been ten major releases, including a 1.9 and 2.1 release on
May 3 and 4, 2015.  The next pair of major releases is scheduled for August
31, 2015.

ManifoldCF is still in the position of supporting both a legacy set of
(1.x), and a non-backwards-compatible set of releases (2.x).  The 1.10
is planned to be the last major release of the 1.x series of releases.

Committers and PMC membership

The last committer we signed up was Kishore Kumar on April 28, 2015.

Mailing list activity

Mailing list has moderately active.  Most of our connectors now have
significant use
cases and constituencies.  We are participating in Google Summer of Code
this year,
and expect new connectors to come from that.  Dev list comments for this
centered around the ManifoldCF 2.1 and 1.9 releases, and occasional user
I am unaware of any mailing-list question that has gone unanswered.

Outstanding issues

Release upload to the svn repository is quite slow, and
well over an hour for a single ManifoldCF release candidate.  We raised this
issue with Infra originally by posting to the Infra list, but did not
manage to
resolve it.  The problem was originally noted in uploads to
We were told to migrate to svn for release candidate availability, which we
only to find that it was no faster than uploading to  I
finally raised a specific ticket - INFRA-9519 - when it became clear that no
progress had been made.  Infra has responded that this is a known issue that
they need to work on long-term.


We continue to believe we are now compliant with Apache branding guidelines,
with the possible exception of (TM) signs in logos from other Apache
that don't have any such marks.  We submitted ManifoldCF to the trademark
registration service and received word that our trademark application is now

Any comments?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message