Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2017-11-16 00:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

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

Fluo

18 Oct 2017 [Keith Turner / Bertrand]

## Description:

 - Apache Fluo is a distributed processing system built on Apache Accumulo.
   Fluo users can easily setup workflows that execute cross node transactions
   when data changes.  These workflows enable users to continuously join new
   data into large existing data sets with low latency while avoiding
   reprocessing all data.

## Issues:

 - There are no issues requiring board attention at this time.

## Activity:

 - Continued work on supporting Mesos, Kubernetes, and Docker
 - Started work on adding explicit read locks
 - Posted multiple issues to ASF helpwanted and Hacktoberfest.  Worked with
   multiple people who responded.  For each new contributor we tweeted a
   congratulation.
 - Collaborated with Eclipse and formatter-maven-plugin communities to get
   a bug fixed in this plugin we use.

## Health report:

 - Since Sep 12
   - 39 Github pull request were created and 38 were closed
   - 43 commits from 3 committers and 4 non-committers
   - 4 new contributors

## PMC changes:

 - Currently 8 PMC members.
 - No new PMC members added in the last month

## Committer base changes:

 - Currently 8 committers.
 - No new changes to the committer base since last report.

## Releases:

 We released a new parent pom that is used by most Apache Fluo projects.

 - build-resources-2.0.0 was released on Wed Sep 13 2017
 - fluo-parent-2 was released on Wed Sep 13 2017

20 Sep 2017 [Keith Turner / Brett]

## Description:

 - Apache Fluo is a distributed processing system built on Apache Accumulo.
   Fluo users can easily setup workflows that execute cross node transactions
   when data changes.  These workflows enable users to continuously join new
   data into large existing data sets with low latency while avoiding
   reprocessing all data.

## Issues:

 - There are no issues requiring board attention at this time.

## Activity:

 - Work on supporting Mesos and Kubernetes is well underway and nearing
   completion.  Completing this work will likely motivate the next release.
 - Posted an issue on ASF helpwanted site and had a student start working on it.

## Health report:

 - Since Aug 8
    - 11 GitHub issues were opened and 20 closed
    - 16 GitHub pull request were opened and 25 were closed
    - 24 commits were made by 4 authors (all commiters)
    - One new non-committer started working a issue, but did not complete

## PMC changes:

 - Currently 8 PMC members.
 - No new PMC members added in the last month

## Committer base changes:

 - Currently 8 committers.
 - No changes in last month

## Releases:

 - No new releases in last month
 - fluo-1.1.0-incubating was released on Mon Jun 12 2017
 - fluo-recipes-1.1.0-incubating was released on Thu Jun 22 2017

## Answer to question

 - Craig Russell asked : "This PMC is getting very small. What can be done to
   make sure that the project stays viable?"

   - Answer :

     We need to grow the community and that should lead to more PMC members.  To
     do this we plan to continue with a few releases a year and promote them.
     Continue to write up starter issues and promote them.  Continue to speak
     at conferences.  Continue to be a welcoming community.  Continue to engage
     with other communities.

16 Aug 2017 [Keith Turner / Rich]

## Description:

 - Apache Fluo is a distributed processing system built on Apache Accumulo.  Fluo
   users can easily setup workflows that execute cross node transactions when data
   changes.  These workflows enable users to continuously join new data into large
   existing data sets with low latency while avoiding reprocessing all data.

## Issues:

 - There are no issues requiring board attention at this time.

## Activity:

 - Released versions of Fluo are tightly coupled with YARN+Twill for launching
   services on a cluster.  Work is currently under way to break this tight
   coupling inorder to support YARN+Twill, Mesos, and Kubernetes.
 - Fluo implements an immutable byte array wrapper in its API.  Work on moving
   this to its own sub-project is underway.  The goal of this is to create
   something analogous to String for bytes that is suitable for use in other APIs.
   This goal was discussed on an OpenJDK list and there was agreement Java needs a
   library like this until Java defines a bigger story for immutability.
 - Still working through a few gradutation task with INFRA, this is mostly done.

## Health report:

 - Within the past three months
    - 46 GitHub issues were opened and 23 closed
    - 64 GitHub pull request were opened and 56 were closed
    - 69 commits were made by 6 authors, 2 authors were not committers

## PMC changes:

 - Currently 8 PMC members.
 - Chris McTague was added to the PMC on Wed May 31 2017, after our last report to IPMC.
 - PMC and Committers are the same.

## Releases:

 - fluo-1.1.0-incubating was released on Mon Jun 12 2017
 - fluo-recipes-1.1.0-incubating was released on Thu Jun 22 2017

19 Jul 2017

Establish the Apache Fluo 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, for distribution at no charge to
 the public, related to the storage and incremental processing of large
 data sets.

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

 RESOLVED, that the Apache Fluo Project be and hereby is responsible
 for the creation and maintenance of software related to the storage
 and incremental processing of large data sets; and be it further

 RESOLVED, that the office of "Vice President, Apache Fluo" 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 Fluo
 Project, and to have primary responsibility for management of the
 projects within the scope of responsibility of the Apache Fluo
 Project; 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 Fluo Project:

 * Billie Rinaldi <billie@apache.org>
 * Chris McTague <cjmctague@apache.org>
 * Christopher Tubbs <ctubbsii@apache.org>
 * Corey J. Nolet <cjnolet@apache.org>
 * Drew Farris <drew@apache.org>
 * Josh Elser <elserj@apache.org>
 * Keith Turner <kturner@apache.org>
 * Mike Walch <mwalch@apache.org>

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
 to the office of Vice President, Apache Fluo, 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 initial Apache Fluo 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 Fluo Project;
 and be it further

 RESOLVED, that the Apache Fluo Project be and hereby is tasked with
 the migration and rationalization of the Apache Incubator Fluo
 podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache Incubator
 Fluo podling encumbered upon the Apache Incubator PMC are hereafter
 discharged.

 Special Order 7D, Establish the Apache Fluo Project, was
 approved by Unanimous Vote of the directors present.

17 May 2017

Fluo is a distributed system for incrementally processing large data sets
stored in Accumulo.

Fluo has been incubating since 2016-05-17.

Three most important issues to address in the move towards graduation:

  1. Make an additional release of Fluo and Fluo Recipes.
  2. Vote in a new committer.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None.

How has the community developed since the last report?

  A non-committer has made multiple code contributions to the project recently.
  We are discussing a release soon.

How has the project developed since the last report?

  A few exciting new features were added that will be in the next release :

   * Writing Fluo applications is now easier.  Users only need to configure
     a single observer provider class, instead of configuring each observer
     class separately.  This change makes it possible to use Java 8 Lambdas!
   * The scalability of Fluo was greatly improved by changing how it scans for
      notifications.  The work to find notifications was decreased from O(N^2)
      to O(N) where N is the number of nodes.
   * Multiple internal performance improvements were made.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2016-10-28

When were the last committers or PPMC members elected?

 Never


Signed-off-by:

  [x](fluo) Billie Rinaldi
     Comments:
  [x](fluo) Drew Farris
     Comments:
  [x](fluo) Josh Elser

Comments:
     Fluo is comprised of ASF "veterans" -- they operate themselves
     well. That "learn the Apache way" part of incubation was there from day #1
     because they already "got it". However, they continue to struggle to
     attract new talent (it is niche software). There have been some publicity
     efforts from the devs, but growing the podling beyond themselves has not
     yet happened nor is on the horizon, IMO.

27 Feb 2017

Fluo is a distributed system for incrementally processing large data sets
stored in Accumulo.

Fluo has been incubating since 2016-05-17.

Three most important issues to address in the move towards graduation:

 1. Attract new contributors and users
 2. Additional releases
 3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 None

How has the community developed since the last report?

 * Its been quiet.

How has the project developed since the last report?

 * Wrote two blog post to help raise awareness of Fluo.
   - http://fluo.apache.org/blog/2016/12/22/spark-load/
   - http://fluo.apache.org/blog/2016/11/10/immutable-bytes/
 * Made many improvements and bug fixes. Need to start planning for next
   release.
 * Experimented with setting Apache Logo as twitter header.  Shared this
   with members list and a few other Apache projects did something similar.
   https://twitter.com/apachefluo

Date of last release:

 2016-10-28

When were the last committers or PPMC members elected?

 Never

Signed-off-by:

 [x](fluo) Billie Rinaldi
 [x](fluo) Drew Farris
 [x](fluo) Josh Elser

Shepherd/Mentor notes:

 Josh Elser:

   The current podling members are all rather experienced in running
   (other) TLPs and this has been obvious in their actions as a podling.
   They are doing a very good job, but the group still struggles with
   attracting new committers to the project. They are making efforts here,
   but not seeing any result from those actions yet. This is the biggest
   barrier to graduation, IMO.

16 Nov 2016

Fluo is a distributed system for incrementally processing large data sets
stored in Accumulo.

Fluo has been incubating since 2016-05-17.

Three most important issues to address in the move towards graduation:

 1. Attract new contributors and users
 2. Additional releases
 3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 None at this time.

How has the community developed since the last report?

 * Two talks at the Accumulo Summit mentioned Fluo:
   * http://accumulosummit.com/program/talks/tips-for-writing-fluo-applications/
   * http://accumulosummit.com/program/talks/indexing-strategies-for-searching-semantic-networks/
 * Hadoop Weekly Issue #191 mentioned Fluo's release
 * Website traffic is up after the first release according to Google
   Analytics
 * Created Twitter Account : http://twitter.com/apachefluo
 * Recent release of Rya which uses Fluo

How has the project developed since the last report?

 * Successfully made first release and two more releases :
   * https://fluo.apache.org/release/fluo-recipes-1.0.0-incubating/
   * https://fluo.apache.org/release/fluo-1.0.0-incubating/
   * https://lists.apache.org/thread.html/0d02022b544fef972dabcfbbf59381fc811fe3d0843f7052568cd56e@%3Cgeneral.incubator.apache.org%3E
 * Created Fluo Tour (easy, hands on introduction) :
   https://fluo.apache.org/tour/
 * Completed Podling Namesearch :
   https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-109
 * fluo.io now redirects to fluo.apache.org
 * The fluo-io GitHub org was renamed to astralway

Date of last release:

 2016-10-28

When were the last committers or PMC members elected?

 Never

Signed-off-by:

 [x](fluo) Billie Rinaldi
 [x](fluo) Drew Farris
 [x](fluo) Josh Elser

Shepherd/Mentor notes:

 Josh Elser:

   The podling is definitely finding their legs in creating and releasing
   software, but very little progress has been made on growing the community
   (no prospective members).

   I am also happy with the state of trademarks for the podling.

17 Aug 2016

Fluo is a distributed system for incrementally processing large data sets
stored in Accumulo.

Fluo has been incubating since 2016-05-17.

Three most important issues to address in the move towards graduation:

 1. Attract new contributors
 2. Do a release
 3. Conduct a podling name search

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 No

How has the community developed since the last report?

 We have a new contributor to Fluo since the last report.

How has the project developed since the last report?

 We completed refactoring of code to use Apache names.  We attempted our
 first release of a parent pom (for both Fluo projects) and it failed on
 the incubator list.  A parent pom is a way to share build configuration
 among multiple projects.  We plan for Fluo and Fluo Recipes to both
 inherit the same parent pom and obtain common config for code formatting,
 findbugs, checkstyle rules, etc.  For this to work the parent pom needs to
 be released before the projects.

 The reason it failed is because members of the IPMC identified the
 following issues :

* Improper linking to pre-Apache releases of Fluo from website.
* Branding and linking issues with fluo.io domain, fluo-io GitHub org and
  projects.  The domain name and github org were used by the project before
  moving to Apache.

 This was really good feedback.  We want to remedy the issues identified
 and eliminate possible confusion around the Apache Fluo brand.  The
 following link identifies discussion of a possible way forward.

 https://lists.apache.org/thread.html/b478645815bf7b1fee8342a21924162decc173d9
   1c22eaf5f708a435@%3Cdev.fluo.apache.org%3E

Date of last release:

 Never

When were the last committers or PMC members elected?

 Never

Signed-off-by:

 [x](fluo) Billie Rinaldi
 [x](fluo) Drew Farris
 [x](fluo) Josh Elser

Shepherd/Mentor notes:

JE: There was a very heavy discussion on branding spurred from the attempted VOTE
    thread. In the end, I believe this was a very positive discussion and resulted
    in fixing many branding issues. I believe most of them were due to the transition
    from an independent Github community to Apache (which included bringing the website).
    The PPMC has been extremely responsive to incubator feedback and I am very happy
    with the level of response they spearheaded (without mentor prodding/coaxing).

20 Jul 2016

Fluo is a distributed system for incrementally processing large data sets
stored in Accumulo.

Fluo has been incubating since 2016-05-17.

Three most important issues to address in the move towards graduation:

 1. Attract new contributors
 2. Do a release
 3. Conduct a podling name search

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 No

How has the community developed since the last report?

 We have a new contributor to Fluo since the last report.

How has the project developed since the last report?

 We have moved our repos (Fluo, Fluo Recipes, and Fluo Website) to Apache
 infrastructure.  Our website is now hosted by Apache
 (https://fluo.incubator.apache.org) and was updated to reflect our
 incubation status. We are working on refactoring our package names, build
 tooling, and website, to reflect the Apache branding.

Date of last release:

 Never

When were the last committers or PMC members elected?

 Never

Signed-off-by:

 [x](fluo) Billie Rinaldi
 [x](fluo) Drew Farris
 [x](fluo) Josh Elser

Shepherd/Mentor notes:

 Josh Elser:

   The transition to Apache has been slow but steady. In the past week, it
   seems like things are "returning to normal". Interactions with a new
   contributor have been good -- encouraging to community growth.

15 Jun 2016

Fluo is a distributed system for incrementally processing large data sets
stored in Accumulo.

Fluo has been incubating since 2016-05-17.

Three most important issues to address in the move towards graduation:

  1. Attract new contributors.
  2. Establish an Apache website for Fluo that makes it easy for new users
     and contributors to get started.
  3. Do a release.  We should be able to start working on our first release
     as soon as we are fully established on Apache infrastructure

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  No


How has the community developed since the last report?

  The community is the same as when it started incubation a few weeks ago.

How has the project developed since the last report?

  This is the first Fluo report.  We are trying to get established within
  Apache infrastructure.  Mailing lists are setup.  Need to import code.  We
  are working with INFRA to explore using Github for issue tracking.  See
  INFRA-11900.

Date of last release:

  Never

When were the last committers or PMC members elected?

 Never

Signed-off-by:

  [X](fluo) Billie Rinaldi
  [X](fluo) Drew Farris
  [X](fluo) Josh Elser

Shepherd/Mentor notes:

  John Elser:

    Not much to report here. Podling members are working with INFRA to get
    the existing codebase+issue tracker content ported. Still spinning up.