The board asked for a report this month to check on the progress of the Fluo migration to Accumulo that they approved last month. I volunteered to help draft it for Ed. It is due at the end of today, so please don't delay if you have suggested edits. Here is my draft of that report for peer review (copied from the reporter wizard tool, so this might not reflect the final formatting):
*** saved as 1747201956-ctubbsii.draft *** ## Description: The mission of Apache Accumulo is the creation and maintenance of software related to a robust, scalable, distributed key/value store with cell-based access control and customizable server-side processing. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Accumulo was founded 2012-03-20 (13 years ago) There are currently 43 committers and 39 PMC members in this project. The Committer-to-PMC ratio is roughly 6:5. Community changes, past quarter: - No new PMC members. Last addition was Kevin Rathbun on 2024-07-24. - No new committers. Last addition was Kevin Rathbun on 2024-07-25. ## Project Activity: The primary Accumulo project activity remains focused on work towards 2.1.4, 3.1, and 4.0 releases, as reported in our normal quarterly report last month. Some draft release notes were added to the accumulo.apache.org website to prepare for publishing for when those releases are performed. In addition, the PMC was asked to provide a report this month to communicate our progress migrating the Apache Fluo TLP to be a subproject of Accumulo, as per the resolution from the April board meeting. We are making progress in this regard. To date, we have: 1) sent an email notification to relevant list subscribers of dev@fluo, dev@accumulo, user@accumulo, and also a courtesy copy to dev@rya, since we were aware that Apache Rya has an optional dependency on Fluo. The email sent was https://lists.apache.org/thread/g809tdpfrbry8vpploogksgrj93607rl 2) restored the functionality of the fluo.apache.org website; it had been non-functional due to the use of 3rd party JavaScript and CSS web assets that no longer work on apache.org sites, due to policy changes, and 3) created a ticket for INFRA to perform the necessary disposition tasks of the Fluo PMC permissions/groups/memberships and assign permissions to the Accumulo PMC (https://issues.apache.org/jira/browse/INFRA-26799). We identified at least one possible issue that we will need to work with INFRA to determine the best path forward. Specifically, we encountered a rule that prevents setting a notification or commits email address in a git repo's ".asf.yaml" file to a domain other than the inferred TLP domain based on the git repo's name. INFRA may suggest a different solution, but the two obvious solutions appear to be to either keep the current mailing lists (at least as an alias for their corresponding @accumulo lists), or rename the git repos to match the conventions currently enforced. We will likely rely on INFRA's advice for the best path forward for that. We are currently awaiting INFRA to make the changes in the ticket. However, this is not a blocker. While we wait on INFRA, we will continue to focus on the main Accumulo project work, and continue to make updates to the Fluo website, as needed. ## Community Health: Overall community health is good and GitHub and mailing list activity remains consistent (no substantial change to report from our regular quarterly report provided last month).
