This was extracted (@ 2025-02-19 22: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.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
Report was filed, but display is awaiting the approval of the Board minutes.
No report was submitted.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Project Status: Current project status: At risk Issues for the board: The project does not have sufficient oversight from the PMC. From the number of respondents to the recent roll call, the project probably has sufficient numbers for a vote, particularly one concerning the final disposition of the project, in order to shut it down "gracefully". However, the majority of respondents replied that they either already were inactive, or that they intend to be and do not have an interest in staying active. So, it is unlikely that there will be enough active Fluo PMC members to routinely oversee the project going forward. As a result of that roll call thread's responses, it was proposed to submit an inquiry to the Accumulo PMC to provide the requisite oversight by accepting the Fluo project as a sub-project. The two projects are very closely related, and there is overlap in the PMC, particularly in the remaining active, or semi-active Fluo PMC members, so this might make sense. A discussion thread was started on October 8 to propose the idea to the Accumulo PMC on their private list for their consideration, and it was cross-posted to the Fluo private list. If the Accumulo PMC is willing to accept oversight of the Fluo project, as a sub-project, it is the intention of the remaining active Fluo PMC members to propose that resolution to the board, to resolve the "at risk" status, and then to seek INFRA's assistance in implementing the necessary permissions changes, before the Fluo PMC is dissolved by the board. ## Membership Data: Apache Fluo was founded 2017-07-18 (7 years ago) There are currently 15 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. ## Project Activity: Not much activity this quarter. The main activity this quarter was updates to maintain the project's fluo-uno tool (which exists in its own repository apart from the main Fluo code base). That tool is used by Fluo and Accumulo (one of Fluo's dependencies) for development and testing. Additional trivial updates were also done to fix the GitHub Actions CI builds for several of the project's repositories and to update the build for the project's Jekyll-based website. A comment on the private list indicated that there was also some work being done by one developer to update the main Fluo repository to work with Java 11/17 and Accumulo 2.1, but that work is still in progress and has not yet resulted in a pull request. The only substantial mailing list activity was a roll call thread, from which it became clear that the project is now in an "at risk" status, and the follow-up cross-post to the Accumulo PMC (see earlier "Issues for the board" section). ## Community Health: There were 11 commits from 2 committers and one non committer. While the metrics show a slight uptick in activity, the quality of the activity remains substantially the same as the previous quarter. A roll call was initiated by Rich Bowen and the results were a single +1, 4 +0, and 3 -1 responses. Through the roll call, it was observed that the project is now at risk. There was a proposal on the roll call vote thread to explore offering the Fluo project as a sub-project of Accumulo and see where that goes (see earlier "Issues for the board" section).
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Project Status: Current project status: Dormant Issues for the board: None ## Membership Data: Apache Fluo was founded 2017-07-18 (7 years ago) There are currently 15 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. ## Project Activity: There was very little activity this quarter. An update was made to Fluo uno to update the zookeeper version. The last release was Fluo 2.0.0 in April 2023. ## Community Health: There was only a single update made this quarter from a new non committer. There was no activity on the mailing list.
@Rich: follow up on roll call for Fluo PMC
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache Fluo was founded 2017-07-18 (7 years ago) There are currently 15 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. ## Project Activity: There was very little activity this quarter. An update was made to Fluo uno to support Max OSX. Some dependencies were updated. The last release was Fluo 2.0.0 in April 2023. ## Community Health: There was only a single update made this quarter from a new non committer. There was no activity on the mailing list.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache Fluo was founded 2017-07-18 (6 years ago) There are currently 15 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. ## Project Activity: For the Muchos sub-project the following activity happened. * Updated Ansible core and Azure modules * Added support for a new VM type in Azure * Added support for mixing OS image types in an Azure deployment. * Added support for AlmaLinux 8/9 and Rocky Linux 8 For the Uno sub-project, Mac OSx support was improved. Also changes were made to work around Hadoop not working with Java 17. The last release was Fluo 2.0.0 in April 2023. ## Community Health: Given that there was almost no activity last quarter, the increase in activity for this quarter was huge percentage wise. However the overall amount of activity was light with 15 commits from 2 committers and a new contributor.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache Fluo was founded 2017-07-18 (6 years ago) There are currently 15 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. ## Project Activity: Very minimal project activity, only one minor change from a committer to update dependency versions. ## Community Health: Community activity was almost zero this quarter, with the exception of a single issue that was opened. Since 2.0.0 was released, I am not aware of anyone working on any major changes ATM.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache Fluo was founded 2017-07-18 (6 years ago) There are currently 15 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. This quarter, the following individual stepped down from the PMC and are now considered PMC Emeritus: - Karthick Narendran ## Project Activity: - Fluo 2.0.0 was released on 4/18/23 with 6 +1 votes and no -1 votes - Updated Uno for latest Accumulo versions. - Added an option to run Accumulo jshell to uno ## Community Health: There were 6 commits from 2 people, one being a new contributor. With the low engagement and activity on the project there was discussion of what the project should do, if anything. We decided its ok for now as long as we can get votes for a release. The codebase is fairly stable. If a release is needed in the future and there are not enough votes then that would be cause to panic.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (6 years ago) There are currently 15 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 8:7. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. This quarter, the following individuals stepped down from the PMC and are now considered PMC Emeritus: - Arvind Shyamsundar - Joseph Koshakow ## Project Activity: Minor code changes were made in anticipation of release. A release candidate was generated and put up for a vote that is currently active. ## Community Health: There was very little activity since the last report and less than previous quarters. There were 4 commits from 3 contributors, one of which was not a committer. If the release vote passes it will be the first release in ~5 years. There is a lot of unreleased goodness from many people that has built up in this time.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (6 years ago) There are currently 15 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. ## Project Activity: The following changes were made this quarter. * Scan time authorizations were added, allowing Fluo to filter data based on visibility labels at scan time like Accumulo does. * Remediated many deprecated calls to third party code in the Fluo code base. This work was done in preparation for a Fluo release. * Fixed a serious bug that was causing Fluo to get stuck for an empty column. * Got Fluo building and running with the latest release of Accumulo. This work was done in preparation for a Fluo release. * Fixed insecure usage of a temp file in Fluo test code. ## Community Health: There were 9 commits from 5 people in the past quarter. Four of the commits were from non-committers. The work done in this quarter knocked out some of the prerequisites for a new Fluo release. The work that is left for a release is testing and doing a release candidate and a new release is imminent.
No report was submitted.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (5 years ago) There are currently 15 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. ## Project Activity: There has been extremely little activity in this project in the last quarter. The activity has been limited to only updating a few dependencies. In discussing this board report on the private list, there was agreement that a new release needs to be done, once the next version of Apache Accumulo is released, which is this project's biggest dependency. That implies a new release, version 2.0.0, sometime in the first quarter of 2023. (See explanation of limited activity in the community health section below.) ## Community Health: Despite this project having very limited activity (nearly non-existent this quarter), the community does not have any outstanding health concerns. This project, by design, is a niche project, built upon Apache Accumulo, whose own releases are relatively infrequent. The low level of activity is understandable, given that this project depends on Accumulo releases, and Accumulo itself has had a relatively slow pace of development. Many of the contributors to Fluo are also contributors to Accumulo, and have been prioritizing Accumulo's next LTM (long-term maintenance) release, after which we expect to see more activity in Fluo to accommodate the newer Accumulo version. In addition, some reduced activity can be explained by the fact that one of Fluo's internal developer tools (fluo-muchos) has stabilized from recent additions to support deploying test clusters to Microsoft Azure, when it previously only supported testing in Amazon EC2. In addition, Terraform has become a somewhat popular, and more widely supported, alternative to fluo-muchos, for testing, so we expect to see a continued decline in activity on that tool as Terraform is more frequently used by our developers to test Fluo. We do not think the lack of activity is indicative of an unhealthy community, but of a small, very slowly paced one that depends on other slow paced projects. We anticipate renewed interest in this project, and corresponding activity, once our primary dependency, Apache Accumulo, has released its next version. After that, we expect to release our own Apache Fluo 2.0.0 supporting that Accumulo version. If the inactivity continues past the next quarter, there may be cause for concern, as it would indicate a lack of interest in having new releases of Apache Fluo. However, we anticipate increased activity within the next two quarters, and are not concerned about community health at this time. Prepared by Christopher Tubbs (ctubbsii) on behalf of Keith Turner, who is ill today.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no outstanding issues for the board at this time. ## Membership Data: Apache Fluo was founded 2017-07-18 (5 years ago) There are currently 15 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Brian Frank Loss on 2022-02-01. - No new committers. Last addition was Brian Frank Loss on 2022-02-02. ## Project Activity: Project activity has been low this quarter. This is not necessarily a problem, as this community has always been relatively slow moving, and some members have been on vacation and working on other projects. ## Community Health: The overall community is moderately healthy. Attention has shifted in recent years to tools the project has created more than the main project. However, there remains an interest in supporting the core project. Its biggest dependency, Accumulo, hasn't had a major release in awhile, and that has caused this project to stagnate somewhat. But I imagine that we'll be better able to assess the overall health of this project after Accumulo has its next release, because then we'll be able to see the subsequent changes made by this project to support the newer Accumulo version. This report was prepared by Christopher Tubbs (ctubbsii) in lieu of the PMC Chair, due to their temporary unavailability due to personal matters.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (5 years ago) There are currently 15 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Brian Frank Loss was added to the PMC on 2022-02-01 - Jeffrey Manno was added to the PMC on 2022-01-23 - Brian Frank Loss was added as committer on 2022-02-02 - Jeffrey Manno was added as committer on 2022-01-24 ## Project Activity: * Supported new Accumulo 2.1 features in Muchos * Supported latest version of Fedora in Muchos * Added --test option to Uno to copy Accumulo test jar The last releases were : Fluo 1.2.0 : Feb 26 2018 Fluo Recipes : Mar 06, 2018 ## Community Health: Project activity was lower than last quarter with 4 commits from 3 committers. Since the last quarter we voted in 2 new committers.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (4 years ago) There are currently 13 committers and 13 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Karthick Narendran on 2020-04-16. - No new committers. Last addition was Karthick Narendran on 2020-04-17. ## Project Activity: * Discussions were initiated on which default Linux OS Muchos should move to, it currently uses Centos 7. Consensus has not been reached yet. * Some changes were made in Muchos in reaction to the Log4j exploit * Improvements were made to ELK setup in Muchos * Some issue w/ Centos 7 in Muchos were worked around. * Updates were made in Muchos to support changes in Accumulo 2.1.0-SNAPSHOT The last releases were : Fluo 1.2.0 : Feb 26 2018 Fluo Recipes : Mar 06, 2018 ## Community Health: There were 17 commits from 4 committers and 3 contributors. One of the contributors was a completely new contributor. There was more activity from more people than the last quarter. Discussion was initiated about inviting two contributors that have been active and so far everyone supports this. Will initiate a vote in a few days.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (4 years ago) There are currently 13 committers and 13 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Karthick Narendran on 2020-04-16. - No new committers. Last addition was Karthick Narendran on 2020-04-17. ## Project Activity: Multiple updates for Azure were made to Fluo Muchos including : * Updated Azure deployments to use Centos 7.9 * Support for spot instances * Updated the Anisble Azure version Fluo Uno was updated to work with Accumulo's new cluster config file format. ## Community Health: There was relatively low activity on the project this past quarter. There were 9 commits from 2 committers and 3 contributors. One of the contributors was a first time contributor. Still need to do a release of Fluo 2.0. The last releases for Fluo were : Fluo 1.2.0 on Feb 26, 2018 Fluo Recipes 1.2.0 on Mar 06, 2018
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (4 years ago) There are currently 13 committers and 13 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Karthick Narendran on 2020-04-16. - No new committers. Last addition was Karthick Narendran on 2020-04-17. ## Project Activity: There were multiple improvements for supporting Azure in Muchos including : * Made VM disk caching configurable and data disk names consistent * Supporting multiple VM scale sets in Muchos when creating cluster * Improved configuration validation checks * Added configured ssh keys to the proxy Muchos was also updated to support external compactions in Accumulo and to respect a users configured classpath. Uno was updated to support the new way Accumulo does encryption. ## Community Health: There was relatively low activity on the project this past quarter. There were 12 commits from 4 committers and 2 contributors. One of the contributors was a first time contributor. Still need to do a release of Fluo 2.0. The last releases for Fluo were : Fluo 1.2.0 on Feb 26, 2018 Fluo Recipes 1.2.0 on Mar 06, 2018
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (4 years ago) There are currently 13 committers and 13 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Karthick Narendran on 2020-04-16. - No new committers. Last addition was Karthick Narendran on 2020-04-17. ## Project Activity: * A really nice improvement to how Fluo loads data was made by a new contributor. * Muchos was updated to support the rename of master to manager in Accumulo * Systemd support in Muchos was improved ## Community Health: There was relatively low activity on the project this quarter, similar to the last quarter. There were 12 commits from 3 committers and 2 contributors. The two contributors were first time Fluo contributors. Still need to do a release of Fluo 2.0
## Description:
The mission of Apache Fluo is the creation and maintenance of software related
to the storage and incremental processing of large data sets
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Fluo was founded 2017-07-18 (3 years ago)
There are currently 13 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Karthick Narendran on 2020-04-16.
- No new committers. Last addition was Karthick Narendran on 2020-04-17.
## Project Activity:
* All issues outstanding for a 2.0.0 release were resolved. An assessment
was conducted to determine if Fluo is ready for a release and shared on the
mailing list for discussion. The assessment determined there is more that
could be done before release, but nothing that would block a release. There
was agreement with this finding on the mailing list.
* Nice improvements were made to the way Uno downloads dependencies.
* Uno was updated to support running multiple Accumulo tablet servers.
* Updates were made to Uno and Muchos subproject to work w/ latest Accumulo
and Fluo dependencies.
* Noticed the checksum on an InfluxDB rpm used by Muchos changed. Reached
out to the influxdb team and they were not sure why it changed.
Researched this and found it was resigned.
## Community Health:
Activity on the project was very low this quarter. No large changes were
made, mostly smaller maintenance fixes were made. Any hurdles blocking a
release were cleared and we are ready to do a release. There were 19 commits
from 5 committers and 3 contributors. One of the contributors was completely
new to Fluo.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (3 years ago) There are currently 13 committers and 13 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Karthick Narendran on 2020-04-16. - No new committers. Last addition was Karthick Narendran on 2020-04-17. ## Project Activity: * Added ELK support to Fluo Muchos * Migrated from TravisCI to Github actions * Renamed Github branches from master to main * Reduced the size of Fluo's Docker image * Updated Fluo Recipes to work with Java 11, Hadoop 3, and Accumulo 2 * Updated Fluo Uno to work with Accumulo 1.10 * Updated Fluo Muchos to work with Centos 8 * Simplified HDFS configuration in Fluo Muchos for HA and nameservices ## Community Health: There was a good bit more activity on the project over the previous quarter. There were 68 commits from 5 committers and 5 non-committers with 2 new contributors. Fluo is still long overdue for a release. Some progress was made towards this end in getting Fluo Recipes working with the latest Hadoop, Accumulo, and Java version. This enables work to get Fluo's examples working with the latest snapshot which is a prerequisite for release.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (3 years ago) There are currently 13 committers and 13 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Karthick Narendran was added to the PMC on 2020-04-16 - Karthick Narendran was added as committer on 2020-04-17 ## Project Activity: For Fluo added getAsync() methods, updated build for JDK14, and removed redundant code in the scripts. For Muchos a lot of work was done to automatically format, test, and statically analyze the source code. These steps ensure consistency of, and minimize the chance of syntax-related regressions, in new contributions. Muchos was updated to use the simplified WAL config for cloud storage AND log4j2 in Accumulo 2.1.0-SNAPSHOT. Muchos improved support for working with SNAPSHOT versions of Hadoop, Zookeeper, and Accumulo. Muchos was updated to correctly handle multiple installed java versions. ## Community Health: There was less overall activity this quarter than the last, less commits and PRs. There was more activity on the dev list though, emails from new contributors seeking help. There were 27 commits from 6 committers and 2 non-committers. Both non-committers were first time contributors. Fluo has not done a release in a long time and this is not good. I reported this on the last board report. We have a lot of good unreleased changes. I am going to work on making a release vote happen in the upcoming quarter.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Fluo was founded 2017-07-18 (3 years ago) There are currently 12 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Joseph Koshakow on 2019-11-07. - No new committers. Last addition was Joseph Koshakow on 2019-11-07. ## Project Activity: Fluo added the ability to count running oracles to the Stat command and fixed a race condition with counting workers and oracles. Many general Muchos improvements were made including : Systemd support, Map Reduce Job History support, latest Zookeeper support, multiple standby namenode support, WIP Logstash support, Azure Log Analytics support, Azure ephemeral storage support, and Azure terminate and wipe support. ## Community Health: There was more overall activity this quarter than the last, more commits and PRs. There were 48 commits from 4 committers and 6 non-committers. Three of the non-committers were first time contributors. We are discussing inviting two contributors to join Fluo. Fluo has not done a release in a long time and this is not good. We really need to do a release and will draft a release plan soon.
## Description: The mission of Apache Fluo is the creation and maintenance of software related to the storage and incremental processing of large data sets. ## Issues: ## Membership Data: Apache Fluo was founded 2017-07-18 (2 years ago) There are currently 12 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Arvind Shyamsundar was added to the PMC on 2019-10-31 - Joseph Koshakow was added to the PMC on 2019-11-07 - Mike Miller was added to the PMC on 2019-10-29 - Arvind Shyamsundar was added as committer on 2019-11-01 - Joseph Koshakow was added as committer on 2019-11-07 - Mike Miller was added as committer on 2019-10-30 ## Project Activity: * Worked on making Fluo and Muchos work with Java 11. Had to bump next Fluo version to 2.0.0 because supporting Java 11 required dropping some deprecated APIs. * Parallelized some of Fluo's transaction failure handling code. * Updated Azure Log Analytics integration within Muchos. * Refactored Muchos Configuration code to align with three cluster types (AWS, Azure, Existing) and improved configuration using decorators. This change makes it easier to improve and maintain Muchos. * Updated Fluo's dependencies and docs about them. * Clarified what RTC means for Fluo on our website. ## Community Health: Since the last report, there were 28 commits from 7 committers and 6 non-committers. I need to review the total activity for the 6 non-committers to see if any should be invited. There were less commits this quarter than last, but the total number of people contributing is about the same. There was a lot more discussion on the dev list than the previous quarter. There were discussions about new committers, technical issues, and the path to being a committer. We have not had a release in quite a while, we really need to get Fluo 2.0.0 released. Hoping to see that happen in the current quarter.
@Ted: follow up with info about CoC reporting
## 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 ## Membership Data: Apache Fluo was founded 2017-07-18 (2 years ago) There are currently 9 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Kenneth Mcfarland on 2018-03-19. - No new committers. Last addition was Kenneth Mcfarland on 2017-12-07. ## Project Activity: Fluo has a sub project called Muchos that sets up Accumulo and Fluo in AWS. Recently, external contributors added support for for Azure. There was a large amount of effort that went into this resulting in a lot of code. Also, support for HA Hadoop was added to Muchos. On the AWS front, support for templates were added making composing clusters more expressive. Fluo uses RTC, we discussed relaxing RTC with a 72 hour lazy consensus provision. Work towards the release of Fluo 1.3.0 (which will support Hadoop 3, Accumulo 2, and Java 11) continues. Recent work was testing and resolving integration issues found during testing. ## Community Health: There were 41 commits from 11 non-commiters and 2 commiters. Writing this board report caused me to research inviting new committers, and I have identified a few candidates. A lot of this activity centered around Muchos. We've started the practice of encouraging contributors on GitHub pull requests to subscribe to the mailing list and introduce themselves, as a way of encouraging community growth, and several have accepted the invitation to do so.
## 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: - A good bit of recent activity is focused on making updates that were found as a result of testing with Java 11, Accumulo 2.0, and Hadoop 3.0. Hadoop is does not have a Java 11 ready release so some small workarounds are required to test on a cluster with Java 11 and Hadoop 3.0. ## Health report: - 14 commits from 2 committers and 4 contributors [04/11-06/10] - Issues and pull request : opened 17 and closed 16 [04/11-06/10] ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kenneth Mcfarland on Mon Mar 19 2018 ## Committer base changes: - Currently 9 committers. - No new committers added in the last 3 months - Last committer addition was Kenneth Mcfarland at Thu Dec 07 2017 ## Releases: - Last release was fluo-recipes-1.2.0 on Mon Mar 05 2018
## 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: - A good bit of recent activity is focused on getting Fluo to work well with the upcoming Accumulo 2.0 release and the recent Hadoop 3 release. ## Health report: - 17 commits from 4 committers and 1 contributor [01/09-04/10] - Issues and pull request : opened 27 and closed 23 [01/09-04/10] ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kenneth Mcfarland on Mon Mar 19 2018 ## Committer base changes: - Currently 9 committers. - No new committers added in the last 3 months - Last committer addition was Kenneth Mcfarland at Thu Dec 07 2017 ## Releases: - Last release was fluo-recipes-1.2.0 on Mon Mar 05 2018
## 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: - A good bit of recent activity is focused on getting Fluo to work well with the upcoming Accumulo 2.0 release and the recent Hadoop 3 release. - An Apache Slack channel was created for Fluo. ## Health report: - 38 commits from 5 committers and 1 contributors [10/11-01/08] - Issues and pull request : opened 47 and closed 45 [10/11-01/08] ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kenneth Mcfarland on Mon Mar 19 2018 ## Committer base changes: - Currently 9 committers. - No new committers added in the last 3 months - Last committer addition was Kenneth Mcfarland at Thu Dec 07 2017 ## Releases: - Last release was fluo-recipes-1.2.0 on Mon Mar 05 2018
## 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: - A good bit of recent activity is focused on getting Fluo to work well with the upcoming Accumulo 2.0 release and the recent Hadoop 3 release. ## Health report: - 50 commits from 5 committers and 2 new contributors [6/11-10/10] - Issues and pull request : opened 55 and closed 57 [6/11-10/10] ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kenneth Mcfarland on Mon Mar 19 2018 ## Committer base changes: - Currently 9 committers. - No new committers added in the last 3 months - Last committer addition was Kenneth Mcfarland at Thu Dec 07 2017 ## Releases: - Last release was fluo-recipes-1.2.0 on Mon Mar 05 2018
## 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:
- Accepted external code for running Fluo and Accumulo locally and in EC2.
Also accepted external examples. All of this went through IP Clearance:
https://incubator.apache.org/ip-clearance/fluo-astralway-code-repos.html
## Health report:
- Issues and pull request : opened 35 and closed 41 [4/12-6/10]
- 34 commits from 5 committers [4/12-6/10]
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kenneth Mcfarland on Mon Mar 19 2018
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Kenneth Mcfarland at Thu Dec 07 2017
## Releases:
- Last release was fluo-recipes-1.2.0 on Mon Mar 05 2018
## 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: - Voted to merge committers and PMC - Made Fluo available at hub.docker.com/r/apache/fluo/ - Discussed accepting some external Fluo test and example projects - Documented how to test/verify a release ## Health report: - 60 GitHub PRs opened and 58 closed [1/10-4/11] - 15 issues opened and 4 closed [1/10-4/11] - 70 commits from 5 committers and 4 contributors [1/10-4/11] - 1 new contributor [1/10-4/11] ## PMC changes: - Currently 9 PMC members. - Kenneth Mcfarland was added to the PMC on Mon Mar 19 2018 ## Committer base changes: - Currently 9 committers. - No new committers added in the last 3 months - Last committer addition was Kenneth Mcfarland at Thu Dec 07 2017 ## Releases: - fluo-1.2.0 was released on Sun Feb 25 2018 - fluo-recipes-1.2.0 was released on Mon Mar 05 2018 - fluo-yarn-1.0.0 was released on Mon Mar 05 2018
## 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: - Testing and fixing issues found in preparation for next release. - Updated install docs to include new fluo-yarn and docker projects - Rewrote asynchronous commit code to use new Java 8 Completable Futures - Made many internal Caches with hard coded sizes configurable - Improved Fluo scanner API - Improved automatic formatting of Fluo code - Code cleanup fixed all compiler warnings - Added read locks to Fluo transactions - Fluo talk was given at the Accumulo Summit ## Health report: - Created 57 pull request and closed 59 [10/12/17,1/9/18] - Created 32 issues and closed closed 29 [10/12/17,1/9/18] - 60 commits from 4 committers and 8 contributors [10/12/17,1/9/18] - 6 new contributors ## PMC changes: - Currently 8 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Billie Rinaldi on Tue Jul 18 2017 ## Committer base changes: - Currently 9 committers. - Kenneth Mcfarland was added as a committer on Thu Dec 07 2017 - Invited another committer at beginning of Dec but have not heard back. ## Releases: - fluo-parent-3 was released on Sun Nov 26 2017
## 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
## 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.
## 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
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.
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.
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.
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.
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).
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.
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.