The Apache Software Foundation Board of Directors Meeting Minutes May 19, 2021 1. Call to order The meeting was scheduled for 22:00 UTC and began at 22:02 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://timeanddate.com/s/42ba The meeting was held via teleconference, hosted by the Secretary via Zoom. The #asfboard channel on the-asf.slack.com was used for backup. 2. Roll Call Directors Present: Bertrand Delacretaz Roy T. Fielding Sharan Foga Justin Mclean Craig L Russell Roman Shaposhnik Sander Striker Sheng Wu Directors Absent: Sam Ruby Executive Officers Present: David Nalley Matt Sicker Ruth Suehle Executive Officers Absent: Myrle Krantz Guests: Balázs Donát Bessenyei Daniel Gruno Daniel Ruggeri Dave Fisher Gavin McDonald Greg Stein Sally Khudairi 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of April 21, 2021 See: board_minutes_2021_04_21.txt Approved by General Consent. 4. Executive Officer Reports A. Board Chair [Sander] I have little to report outside of the agenda. My interest in making further tweaks to the board meeting process remains. I will continue to push for timely reports, giving us more time to review and ask questions. I am aiming to have some tweaks to the agenda tool to assist with this by next meeting. B. President [David] It's been a relatively quiet month. The only material item of note is that I received a CoC complaint; though it seems the project is resolving the issue on their own. I continue to be happy with the work from the Treasurer's Office to provide us with a greater measure of controls while dramatically increasing visibility and flexibility. The latest addition of Ramp provides even greater insight to what each card is spending as well as making it a lot easier for virtual or physical cards to be issued. Update from verbal report during the board meeting: Gris Cuevas has resigned as VP D&I. After two years, Gris has done a ton of work to help us better understand the scope of diversity issues at the ASF, and I appreciate all the work and believe she has left us in a better place due to that work. I’ve appointed Katia Rojas as VP, Diversity & Inclusion. Katia has been involved in a lot of the D&I work and is picking up additional responsibilities as part of this transition. Expect more in next month’s board report. Additionally, please see Attachments 1 through 8. C. Treasurer [Myrle] Summary: Collaboration with IgniteSpot on accounting continues to work smoothly. IgniteSpot is now supporting Conferences Fundraising in addition to their normal Fundraising support. We’ve hit a hitch on the transition from the Citizens’ bank account to TDBank, but we are resolving it. We have shifted from cash-based to accrual-based accounting with the beginning of the new fiscal year on May 1st. We discovered that Charity Navigator rates us lower than warranted because they have inaccurate information about us. Craig Russell is helping us rectify the situation by pointing them to our most recent audit and our CoI policy. In the process we have also updated records with GuideStar.org. We have ended acceptance of BitCoin donations to The Foundation. We have also finished the recovery of our PayPal account. We believe that now all treasury-related accounts are in the hands of the treasurer, or accounting. We have also updated treasurer.apache.org to contain current external information and moved internal information about invoice approval processes and similar to the ASF internal confluence page. Thank you Dave Fisher for moving the Treasurer website to Pelican/Github to make this process much easier. Going forward we plan to move finance-related externally-visible corporate documents such as 990s and audit reports to the treasurer website. Transition to TDBank We discovered that TDBank did not have exceptions in ACH blocking for bill.com. Because of that, we continue to pay vendors via Citizen’s while we wait for TDBank to workaround the bug in their ACH blocking. We have moved PEO (ADP Total Source) to TDBank, and that has gone smoothly. As of April 16th, all outgoing sponsorship invoices have contained the new bank account number. A number of sponsors have requested that we provide extra proof of the new bank account, and IgniteSpot has taken on the extra work. We’ll continue to monitor the Citizen’s account in preparation for closing it completely. There may still be a few sponsors’ PO systems that need updating. We’ll synchronize with fundraising before taking the last step. Introduction of virtual credit cards Greg Stein’s tests of virtual and physical credit cards issued from Ramp.com have been successful. As a result we are proceeding with the full roll out to the officers. All officers have been invited to the platform. We may need to fine-tune expense policies and approval rights over the next couple of months, but the platform is fully ready for go-live. The resonance among those who have tried it has been overwhelmingly positive. As a result, we plan to cancel our Citizen’s credit cards as soon as the last bill has been paid. D. Secretary [Matt] In April, the secretary received 53 ICLAs, 2 CCLAs, 4 software grants, 5 membership applications, and 15 CoI affirmations. We made a small adjustment to our ICLA form to specify an optional GitHub id for help with communities who tend to refer to each other by those usernames in vote threads. E. Executive Vice President [Ruth] ApacheCon(s) planning still proceeding well, including sponsorships. Four companies have taken advantage of the option to sponsor both events. ApacheCon Asia --------------- Strategic (1) Platinum (5) Gold (1) ApacheCon NA+Europe ------------------- Strategic (1) Platinum (4) Gold (5) Silver (1) Bronze (1) Other details in Fundraising and Conferences reports. F. Vice Chair [Shane] No particular activities to report. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Craig] See Attachment 9 B. Apache Legal Affairs Committee [Roman Shaposhnik] See Attachment 10 C. Apache Security Team Project [Mark J. Cox / Roy] See Attachment 11 D. VP of Jakarta EE Relations [Rob Tompkins / Sam] See Attachment 12 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Diversity and Inclusion [striker] # Sqoop [clr] A. Apache Ambari Project [Jayush Luniya / Roman] See Attachment A B. Apache Ant Project [Jan Materne / Sheng] See Attachment B C. Apache Bloodhound Project [Gary Martin / Sharan] See Attachment C D. Apache BookKeeper Project [Sijie Guo / Justin] No report was submitted. E. Apache Brooklyn Project [Geoff Macartney / Sander] See Attachment E F. Apache Buildr Project [Antoine Toulme / Bertrand] See Attachment F G. Apache Cassandra Project [Nate McCall / Roy] See Attachment G H. Apache Clerezza Project [Hasan Hasan / Sharan] See Attachment H I. Apache Cocoon Project [Cédric Damioli / Roman] See Attachment I J. Apache Community Development Project [Swapnil Mane / Sam] See Attachment J K. Apache CouchDB Project [Jan Lehnardt / Sander] See Attachment K L. Apache Creadur Project [Philipp Ottlinger / Sheng] See Attachment L M. Apache Daffodil Project [Mike Beckerle / Justin] See Attachment M N. Apache DataSketches Project [Lee Rhodes / Craig] See Attachment N O. Apache DeltaSpike Project [Mark Struberg / Bertrand] See Attachment O P. Apache DolphinScheduler Project [Lidong Dai / Craig] See Attachment P Q. Apache Drill Project [Charles Givre / Sheng] See Attachment Q R. Apache Empire-db Project [Rainer Döbele / Bertrand] See Attachment R S. Apache Flume Project [Balázs Donát Bessenyei / Sander] See Attachment S T. Apache FreeMarker Project [Dániel Dékány / Sam] See Attachment T U. Apache Geode Project [Karen Miller / Sharan] See Attachment U V. Apache Giraph Project [Dionysios Logothetis / Roman] See Attachment V W. Apache Gora Project [Kevin Ratnasekera / Roy] See Attachment W X. Apache Griffin Project [William Guo / Justin] See Attachment X Y. Apache Groovy Project [Paul King / Craig] See Attachment Y Z. Apache HTTP Server Project [Joe Orton / Sam] See Attachment Z AA. Apache HttpComponents Project [Michael Osipov / Roman] See Attachment AA AB. Apache Ignite Project [Dmitry Pavlov / Sheng] See Attachment AB AC. Apache Impala Project [Jim Apple / Justin] See Attachment AC AD. Apache Incubator Project [Justin Mclean] See Attachment AD AE. Apache jUDDI Project [Alex O'Ree / Roy] See Attachment AE AF. Apache Juneau Project [James Bognar / Sander] See Attachment AF AG. Apache Kafka Project [Jun Rao / Sharan] See Attachment AG AH. Apache Kibble Project [Sharan Foga] See Attachment AH AI. Apache Knox Project [Larry McCay / Bertrand] See Attachment AI AJ. Apache Kylin Project [Shao Feng Shi / Sheng] See Attachment AJ AK. Apache Libcloud Project [Tomaž Muraus / Roman] See Attachment AK AL. Apache Logging Services Project [Matt Sicker / Sharan] See Attachment AL AM. Apache ManifoldCF Project [Karl Wright / Bertrand] See Attachment AM AN. Apache Mesos Project [Qian Zhang / Roy] See Attachment AN AO. Apache MetaModel Project [Kasper Sørensen / Sam] See Attachment AO AP. Apache Mnemonic Project [Yanhui Zhao / Justin] See Attachment AP AQ. Apache Oozie Project [Gézapeti / Sander] See Attachment AQ AR. Apache OpenWhisk Project [Dave Grove / Craig] See Attachment AR AS. Apache Ozone Project [Sammi Chen / Justin] See Attachment AS AT. Apache Perl Project [Steve Hay / Sander] See Attachment AT AU. Apache Phoenix Project [Ankit Singhal / Sheng] See Attachment AU AV. Apache POI Project [Dominik Stadler / Craig] See Attachment AV AW. Apache Qpid Project [Robbie Gemmell / Roy] See Attachment AW AX. Apache Ranger Project [Selvamohan Neethiraj / Sam] See Attachment AX AY. Apache Ratis Project [Tsz-wo Sze / Sander] See Attachment AY AZ. Apache REEF Project [Sergiy Matusevych / Bertrand] See Attachment AZ BA. Apache River Project [Roy T. Fielding] See Attachment BA BB. Apache RocketMQ Project [Xiaorui Wang / Roman] No report was submitted. BC. Apache Roller Project [David M. Johnson / Sharan] See Attachment BC BD. Apache Santuario Project [Colm O hEigeartaigh / Justin] See Attachment BD BE. Apache Serf Project [Justin Erenkrantz / Sander] See Attachment BE BF. Apache ServiceComb Project [Willem Ning Jiang / Sharan] See Attachment BF BG. Apache ShardingSphere Project [Liang Zhang / Sheng] See Attachment BG BH. Apache SIS Project [Martin Desruisseaux / Roy] See Attachment BH BI. Apache Solr Project [Jan Høydahl / Craig] See Attachment BI BJ. Apache Spark Project [Matei Alexandru Zaharia / Sam] See Attachment BJ BK. Apache Sqoop Project [Venkat Ranganathan / Bertrand] See Attachment BK @Bertrand: follow up with another report for next month BL. Apache Subversion Project [Nathan Hartman / Roman] See Attachment BL BM. Apache Superset Project [Maxime Beauchemin / Craig] See Attachment BM BN. Apache Syncope Project [Francesco Chicchiriccò / Sander] See Attachment BN BO. Apache SystemDS Project [Matthias Boehm / Roman] See Attachment BO BP. Apache TomEE Project [David Blevins / Sharan] See Attachment BP BQ. Apache Traffic Control Project [Eric Friedrich / Justin] See Attachment BQ BR. Apache Turbine Project [Georg Kallidis / Sheng] See Attachment BR BS. Apache Usergrid Project [Michael Russo / Roy] See Attachment BS BT. Apache Velocity Project [Nathan Bubna / Sam] See Attachment BT BU. Apache Whimsy Project [Shane Curcuru / Bertrand] See Attachment BU BV. Apache Xalan Project [Gary D. Gregory / Sheng] See Attachment BV BW. Apache Xerces Project [Michael Glavassevich / Bertrand] See Attachment BW BX. Apache XML Graphics Project [Clay Leeds / Sharan] See Attachment BX BY. Apache Zeppelin Project [Lee Moon Soo / Justin] See Attachment BY Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Parquet Project Chair WHEREAS, the Board of Directors heretofore appointed Julien Le Dem (julien) to the office of Vice President, Apache Parquet, and WHEREAS, the Board of Directors is in receipt of the resignation of Julien Le Dem from the office of Vice President, Apache Parquet, and WHEREAS, the Project Management Committee of the Apache Parquet project has chosen by vote to recommend Xinli Shang (shangxinli) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Julien Le Dem is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Parquet, and BE IT FURTHER RESOLVED, that Xinli Shang be and hereby is appointed to the office of Vice President, Apache Parquet, 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 Parquet Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Geode Project Chair WHEREAS, the Board of Directors heretofore appointed Karen Miller (kmiller) to the office of Vice President, Apache Geode, and WHEREAS, the Board of Directors is in receipt of the resignation of Karen Miller from the office of Vice President, Apache Geode, and WHEREAS, the Project Management Committee of the Apache Geode project has chosen by vote to recommend Dan Smith (upthewaterspout) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Karen Miller is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Geode, and BE IT FURTHER RESOLVED, that Dan Smith be and hereby is appointed to the office of Vice President, Apache Geode, 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 7B, Change the Apache Geode Project Chair, was approved by Unanimous Vote of the directors present. C. Change the Apache DataFu Project Chair WHEREAS, the Board of Directors heretofore appointed Matthew Hayes (mhayes) to the office of Vice President, Apache DataFu, and WHEREAS, the Board of Directors is in receipt of the resignation of Matthew Hayes from the office of Vice President, Apache DataFu, and WHEREAS, the Project Management Committee of the Apache DataFu project has chosen by vote to recommend Eyal Allweil (eyal) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Matthew Hayes is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache DataFu, and BE IT FURTHER RESOLVED, that Eyal Allweil be and hereby is appointed to the office of Vice President, Apache DataFu, 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 7C, Change the Apache DataFu Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items 9. Review Outstanding Action Items * Roy: work on binary release policy [ Unfinished Business 2020-05-20 ] Status: Stalled. * David Nalley: ensure CoI filed for everyone [ Conflict of Interest Policy Ratification 2021-03-17 ] Status: Temporarily obviated by the resignation of VP D&I. I will chase new VP D&I later this week. * Roy: Follow up with board issues [ Arrow 2021-04-21 ] Status: Not done yet (due to higher priority issues in River). 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 22:17 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period April 2021 * ISSUES FOR THE BOARD * OPERATIONS Responded to the following queries, liaising with projects as required: - Approved name search for HOP - Approved use of STORM project logo for a blog post - Provided feedback on proposed marketing material for two training courses. - Responded to two queries regarding potential infringement - Reviewed mail from EUIPO regarding potential conflict with new registration - One request to sell swag for a project - One query regarding a proposed corporate renaming that potentially conflicted with ASF marks * REGISTRATIONS Worked with counsel to progress our national application for APACHE (this is a backup to our WIPO application). Continued to progress paperwork necessary to record the ASF's change of address for our existing registrations. The US registrations for APISIX and BROOKLYN are progressing. * INFRINGEMENTS It has been good to see projects, particularly CASSANDRA and KAFKA proactively protecting their marks this month. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri] 1) ASF Sponsors: we are happy to close out FY2021 having exceeded our revenue goals. We are renewing a Platinum Sponsor and are pursuing 7 Sponsor renewals (2 Silver and 5 Bronze). We are awaiting payment from 6 Sponsors (1 Platinum, 2 Gold, 2 Silver, and 1 Bronze). We are discussing Sponsorship with two candidate organizations. 2) Targeted Sponsors: we onboarded a new Targeted Sponsor at the Platinum level and are awaiting input to onboard a second new Targeted Sponsor, also at the Platinum level. 3) Sponsor Relations: standing Sponsor outreach continues. We are working with a small handful of organizations with promotional opportunities included with their sponsorship. We published the first “Sponsor Success at Apache” post with Leaseweb (Targeted Platinum Sponsor). 4) Event Sponsorship: sponsorships for ApacheCon Asia and ApacheCon@Home are underway. A small handful of agreements for ApacheCon Asia were delayed in execution, which has been rectified. We are awaiting payments from three event sponsors as of the end of April. 5) Individual Donations and Corporate Giving: we earned $2.5K in April over 50 donations. 6) Administrivia: day-to-day operations are running smoothly, and we are enjoying additional participation from some members of the Fundraising team. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi] [REPORT] ASF Marketing & Publicity — May 2021 I. Budget: we wrapped FY2021 under budget and all outstanding vendor payments processed. We are beginning to implement additional processes to support the ASF's migration to accrual accounting. II. Cross-committee Liaison: Sally Khudairi continues to support ASF Fundraising, and is working with a small handful of Platinum Sponsors on promotional opportunities. We published the first Sponsor Success at Apache post, "The Fork" https://s.apache.org/snobd , submitted by Platinum Targeted Sponsor Leaseweb. We have begun work on the FY2021 Annual Report. We announced the newly-elected ASF Members https://s.apache.org/2021NewMembers as well as the March Month-in-Review https://s.apache.org/Mar2021 and video highlights https://s.apache.org/exppv. We assisted the Apache Attic with a media query regarding the influx of retired projects. We are supporting Apache project events, including their corporate producers, and are supporting ASF Brand Management and ASF Security teams with various requests. We continue to promote the CFP, registration, and sponsorship opportunities for ApacheCon Asia and ApacheCon@Home. We are also working with Infra regarding the migration to the new CMS for apache.org. III. Press Releases: the following formal announcement was issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 4 May - Media Alert: Apache OpenOffice Recommends upgrade to v4.1.10 to mitigate legacy vulnerability IV. Informal Announcements: we published 9 items on the ASF "Foundation" Blog, including 4 Apache News Round-ups and 1 monthly overview, totalling 382 news summaries published to date. We tweeted 18 items to 59.8K followers on Twitter, and posted 17 items to 48.5K followers on LinkedIn. The ASF's YouTube channel had 13.8K views this month. V. Future Announcements: 2 announcements are in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones are requested to contact Sally at with at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to 4 media queries, and are in the midst of working with a reporter from a top-tier international publication, who is reviewing 12 potential spokespeople/communities for possible inclusion in a feature article. We are also working with a security-focused outlet who is interviewing a couple members of the Board and ASF Security. We received a total of 3,575 press hits vs. last month's 2,959, inclusive of coverage on the ASF, Apache Projects, and ApacheCon. VII. Analyst Relations: we received 2 analyst queries and are working with a PMC on briefings for a BI report with a European analyst team as well as an analyst report on Cloud computing. We received an analyst query on a Big Data project that was seemingly dormant. Apache was mentioned in a total of 28 reports by Gartner, Forrester, 451 Research, GigaOm, and IDC. VIII. Central Services: activity with Kenneth Paskett (Creative team) continues on best practices for use of https:// to implement on apache.org; researching ADA/Accessibility compliance; adding markdown code to the CLA-FAQ page; creating high-def ASF Sponsor badge SVGs; site review to implement statistics using a master variable file; and working on local GitHub template-site repo to prepare for new CMS (Pelican) and its impact on Bootstrap styles. The FY2021 Annual Report template has been completed. Swapnil Mane (Editorial team) continues his efforts in producing and publishing the ASF Weekly News Round-ups and Months-in-Review reports, and has expanded that to include recording video highlights of them and other newsworthy items as well. He has also been updating and optimizing the ASF’s YouTube profile page and playlists, and is preparing to produce a Feathercast series of interviews to help promote ApacheCon. IX. Events liaison: we are promoting both ApacheCon Asia and ApacheCon@Home, and continue to counsel a handful of commercially-produced Apache project events in flight. Queries include promotions, press releases, Website copy, and overall messaging. We are supporting the ASF's virtual presence at a developer conference. Where needed, we are coordinating with ASF Brand Management. X. Newswire and press clip accounts: services are active and continue without interruption. XI. Miscellany: we continue to monitor discussions regarding the "Apache" name. We are assisting a new ASF Sponsor rep across several areas of activity for the past several weeks. We reviewed a third-party press release promoting an Apache Project event, and advised four PMCs regarding their Project events. We advised an organization seeking to make a submission to the Apache Incubator. We also advised a vendor (whose primary solution integrates an Apache Project) on how to work with the analyst community. We created a presentation for a PMC's participation in an industry event, as well as one for a Board member preparing for a presentation on the ASF's trajectory from its inception to current day. We advised a consulting group regarding commercial solutions using Apache Projects. We received requests for promotional materials (stickers, signage, and swag) for an in-person community event, but are unable to provide any (none remaining after ApacheCon Berlin/2019; no budget or production due to all ASF events being held virtually due to the pandemic). We are fielding ~3 telephone calls per week on a variety of topics, ranging from solutions sales, conference sponsorship, employment verification, outsourcing infrastructure support and software development, to non-ASF business, with the primary grievance involving mobile apps. # # # ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [David Nalley] General ======= Infrastructure is operating as expected, and has no current issues requiring escalation to the President or the Board. Highlights ========== - www.a.o has been fully-ported from the CMS over to our new Pelican/GFM service, and is undergoing acceptance testing. There are about eight more CMS-based websites to finish moving per the work contract. Short Term Priorities ===================== - Critical blocker was figured out in the LDAP migration mentioned last month, so this will be continuing. - Switch to R53 so that we have an API to perform DNS-based challenges from LetsEnecrypt for wildcard certificates such as *.staged.a.o Long Range Priorities ===================== - Gitbox v2 is progressing, with steps identified for migration of individual components instead of all-or-nothing. We will perform testing with Infrastruture repositories first. General Activity ================ - Planning for Infra's "presence" at ApacheCon 2021. Looks like one or two sessions will be proposed. - Infra is working with a potential future service provider, evaluating their service for our needs. We are also providing feedback to their teams for future feature work. - Atlassian meetings continue for moving to their cloud offering. - Artifactory has been spun up, and bintray turned off. Thank you JFrog for the service (past and future). - All Infra services billed via Citizen's Bank credit cards have now been moved, and we're monitoring this new workflow. So far: it is very awesome. - InfraAdmin/Greg finally brain-dumped to Andrew a long discussion of the job duties, should another need to take over. - Continued migration from Puppet v3, up to v6. - New system for keep svn authz ACLs synchronized is now completed and running in production. ("svnauthz") - Improved our Pelican/GFM build system to better-support our contractor for the CMS migrations. This also includes providing some "assists" with coding to more closely fit Infra systems. - Jenkins work around testing ElasticSearch metrics (decided against) and some issues around the GitHub PR Builder. - Brand new system for managing and displaying fingerprints for all machines managed by Infra. Lots of stale machines were cleaned out, along with somewhat-related DNS entries. - Some assistance to Sam for the Agenda Tool on agenda.a.o. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] The Call for Presentations for both of our events - ApacheCon @Home and ApacheCon Asia - have closed, and we are in the process of selecting our schedules. We hope to have a schedule announced by early June, although we will likely trickle out some of the track schedules as they are ready. Sponsors for the two events are going up onto the website this week, and should be up by the time of this meeting: https://apachecon.com/acah2021/sponsors.html and https://apachecon.com/acasia2021/sponsorship.html respectively. Platinum sponsorships are sold out, but other levels are available. The events will once again feature more than 20 project/topic content tracks, and span three days of content each. The events will be online, and registration will once again be free. Registration for ApacheCon @Home is now open, and registration for ApacheCon Asia is expected to open in the next week or two. Last month we ran an event for Cassandra - "Apache Cassandra 4.0 World Party", which had 1115 registrations. In June we will be hosting "Pulsar Summit North America 2021" - https://pulsar-summit.org/ - with a Europe and Asia event to follow later in the year. Kafka summit - https://www.kafka-summit.org/ - was held May 11-12, and there will be two more Kafka events in July and September. Projects who are interested in hosting events on our conference platform are encouraged to get in touch with the planners mailing list - planners@apachecon.com - for details of requirements and process. ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] Current Events ============== No current events Future Events ============= None Currently Short/Medium Term Priorities ===================== Install and test the webapp. The webapp is complete and delivered to us. The source code has been placed into a private Github repository, mirrored to Gitbox. Due to the occasional nature of the need for the webapp, offsite web hosting offered to us by the software writers was declined. We have a new VM ready to use and will be installing and testing the software over the coming week or so. Budget ====== TAC has not requested any budget for the FY22. No in person events are expected for ApacheCon nor any of the other supported events. Should an in person event appear and is one we would normally support, TAC will request a budget for that event at the time. Mailing List Activity ===================== No activity this month Membership ========== No changes to the membership this month. ----------------------------------------- Attachment 7: Report from the VP of Diversity and Inclusion [Gris Cuevas] D&I Board Report 17 May 2021 ## Description: - The Diversity and Inclusion VP works in collaboration with a team who contributes towards generating a current description of the D&I landscape in the industry and for the foundation. The team also focuses on developing resources the projects can leverage to increase diversity and inclusion in their communities. ## Issues: None ## Activity: *** Project: Internships for underrepresented groups (Outreachy) *** The "December 2020 - March 2021" round has concluded successfully with 6 interns in total, on 6 different projects. We submitted our application for round "May 2021 - August 2021" and got accepted to participate in the program. We used the same communication channels as before, multiple emails via mailing list and blog post [4] We got confirmation of funds for one intern. The new intern will work on the project: Implement distributed tracing for Qpid Proton C++ [1][2] The internship period is from May 24, 2021, to August 24, 2021. [3] *** Project: website We are calling for webmasters to help us developing or maintaining the technical or design parts of the website. We are looking for someone who can help us get the site in a state where content writers can help contribute. [6] *** Topic: criteria for inclusive words During May, the community has been discussing criteria for inclusive words [5]. This could be a potential project we could follow up but we don't have resources (people) to work on it. *** Operations FY2021: no information available on this topic. Bitergia: no information available on this project. *** Project: User Experience Research on new contributors *** no information available on this project. ## Committee members changes: None. ## References [1] https://www.outreachy.org/outreachy-may-2021-internship-round/communities/apache/implement-distributed-tracing-for-qpid-proton-c/cfp/ [2] https://www.outreachy.org/alums/2021-05/ [3] https://www.outreachy.org/outreachy-may-2021-internship-round/ [4] https://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=EDI [5] https://lists.apache.org/list.html?diversity@apache.org [6] https://lists.apache.org/list.html?dev@diversity.apache.org ----------------------------------------- Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier] There were no issues requiring board attention so far. Changes: VP Privacy will maintain this directory for now: https://svn.apache.org/repos/private/foundation/dataprivacy/ It will contain recent requests, TODOs, DPAs and general discussions. "User requests" should be privacy-committee only. A basic website was created here which will contain FAQ and policies: https://privacy.apache.org/ Interesting items: - one data removal request (Jira) was done without problems - one data removal requests was denied since the request did not look legit - discussion about ICLA and how to store it took place, no conclusion so far Next action items: - collect more DPAs - discourage Google Analytics - Update privacy terms on the main website ----------------------------------------- Attachment 9: Report from the VP of W3C Relations [Andy Seaborne] Nothing to report this month. ----------------------------------------- Attachment 10: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] It's been a little busier this month with several discussions on a wide range of topics, including a couple that come up frequently. Committee members took good care of resolving these in time. We're resolved several outstanding issues and currently down to 24 unresolved issues. There has been discussions on gradle jars in source releases (LEGAL-570), changes in elastic search licensing, the LGPL dependency chardet (LEGAL-572), and clarifying the naming of 3rd party licenses that add additional incompatible clauses to the Apache license. Release and distribution policies has been updated and made more explicit, clarifying the use of Category B licensed items and jars containing compiled code in source releases. (In both cases, they cannot be included in source releases.) ----------------------------------------- Attachment 11: Report from the Apache Security Team Project [Mark J. Cox] Continued work on incoming security issues, keeping projects reminded of outstanding issues, and general oversight and advice. Stats for Apr 2021: 28 [license confusion] 21 [support request/question not security notification] Security reports: 41 (last months: 27, 46, 46) 12 [site] 5 [httpd] 3 [pdfbox] 2 [tomcat], [trafficserver] 1 [apisix], [cxf], [druid], [dubbo], [hadoop], [hive], [ignite], [juddi], [kylin], [ofbiz], [openoffice], [shiro], [solr], [tapestry], [tvm], [xerces] In total, as of 1st May 2021, we're tracking 76 (last month: 80) open issues across 37 projects, median age 83 (last month: 56) days. 51 of those issues have CVE names assigned. 9 (last month: 9) of these issues, across 8 projects, are older than 365 days. ----------------------------------------- Attachment 12: Report from the VP of Jakarta EE Relations [Rob Tompkins] I've signed us up to the Eclipse Foundation and the Jakarta EE working group. Further we have made announcement to the PMCs (and not publicly from the ASF) regarding our involvement. Regarding any messaging that I do about our relationship with the Eclipse Foundation, I have found prudent to run by Sally Khudairi, and I plan to continue to use her as a sounding board for any of my messaging strategies as she has much more experience in this area than I do. I am still working out all of the details of what the engagement requirements are, but they seem not to be too overwhelming. Cheers, -Rob ----------------------------------------- Attachment A: Report from the Apache Ambari Project [Jayush Luniya] ## Description: The mission of Apache Ambari is the creation and maintenance of software related to Hadoop cluster management ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Ambari was founded 2013-11-20 (7 years ago) There are currently 109 committers and 51 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Szabolcs Béki on 2020-03-27. - No new committers. Last addition was Tamas Payer on 2020-03-28. ## Project Activity: Team is working on the new Ambari 2.7.6 release that will be independent of Cloudera HDP repositories [(see)|https://www.cloudera.com/downloads/paywall-expansion.html]. The velocity of development is quite indeterministic and largely influenced by other external activities, but still the new release is expected in 2-3 months, which will probably be the last one, unless the new Big Top based Ambari doesn't attract new contributors. ## Community Health: There is no major change in community health, still seems to be hard to get a momentum. 5-10 commits monthly. The goal is to have one final release that is breaks off the dependency from Hortonworks Data Platform. That could give a fresh new start for those who would still like to contribute to Ambari while using Big Top as big data stack. ----------------------------------------- Attachment B: Report from the Apache Ant Project [Jan Materne] ## Description: The mission of Apache Ant is the creation and maintenance of the Ant build system and related software components. It consists of 3 main projects: - Ant - core and libraries (AntLibs) - Ivy - Ant based dependency manager - IvyDE - Eclipse plugin to integrate Ivy into Eclipse Additionally Ant provides several extensions to Ant (antlibs). ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Ant was founded 2002-11-18 (18 years ago) There are currently 29 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 4:3. Community changes, past quarter: - No new PMC members. Last addition was Magesh Umasankar on 2018-07-06. - No new committers. Last addition was Jaikiran Pai on 2017-06-14. ## Project Activity: Recent releases: Ant 1.10.10 was released on 2021-04-17. Ant 1.10.9 was released on 2020-09-30. Ant 1.10.8 was released on 2020-05-13. Ivy 2.5.0 was released on 2019-10-24. Tests with early version of JDK 17 worked. ## Community Health: For Ant we feel healthy enough to apply patches, and get a release done. But basically we are in "maintenance mode". There isn't much development. For IvyDE we lack the knowledge of building Eclipse plugins on actual Eclipse versions. We hope to get the build running again so we could update that. ----------------------------------------- Attachment C: Report from the Apache Bloodhound Project [Gary Martin] Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== There are no issues to raise to the Board at this time. Releases ======== There have been no releases since the last report. The last release was towards the end of 2014: * apache-bloodhound-0.8 (11th December 2014) PMC/Committer Changes ===================== There are currently 14 PMC members on the project. The last changes were in April 2017. The last new committers were added in May 2014. The last addition to the PMC was in January 2017 (dammina) Community & Development ======================= Progress remains slow but in the background there has been some progress including ironing out issues with the setup of live.bloodhound.a.o. Some plans to describe the ideas behind the ongoing development of Apache Bloodhound have begun to be drawn up with the intention of encouraging some engagement from the dev community to contribute to these. With the current plan describing the ability to migrate from the legacy Trac-based database schema, we can anticipate initial progress on modelling to be fairly swift, ready for further experimentation. While the new architecture for Apache Bloodhound will hopefully be fairly straight forward, it is recognized that there may need to be some kind of introduction to Django for those who have not used it before. As such a new document has been added to the wiki to give some hints around how to set up a development environment appropriate for following the official Django tutorial. ----------------------------------------- Attachment D: Report from the Apache BookKeeper Project [Sijie Guo] ----------------------------------------- Attachment E: Report from the Apache Brooklyn Project [Geoff Macartney] ## Description: The mission of Apache Brooklyn is the creation and maintenance of software related to a software framework for modeling, monitoring and managing cloud applications through autonomic blueprints. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Brooklyn was founded 2015-11-18 (5 years ago) There are currently 19 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Duncan Grant on 2018-08-30. - No new committers. Last addition was Iuliana Cosmina on 2020-07-03. ## Project Activity: - This has been a busy quarter, with a relatively high frequency of commits. - We have been pleased to welcome changes to the project from a number of new contributors. ## Community Health: - We continue to monitor our community for potential new committers and PMC members with the aim of regularly adding individuals. ----------------------------------------- Attachment F: Report from the Apache Buildr Project [Antoine Toulme] ## Description: Apache Buildr is a build system for Java-based applications, including support for Scala, Groovy and a growing number of JVM languages and tools. We wanted something that’s simple and intuitive to use, so we only need to tell it what to do, and it takes care of the rest. But also something we can easily extend for those one-off tasks, with a language that’s a joy to use. And of course, we wanted it to be fast, reliable and have outstanding dependency management. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We have released 1.5.8 in July 2019. We haven't had any activity since. This report is essentially the same as what we filed for a while now. ## Health report: - We still have a small PMC presence of 3 active members still able to vote releases. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Peter Donald on Tue Oct 15 2013 ## Committer base changes: - Currently 10 committers. - Olle Jonsson was added as a committer on Wed Dec 12 2018 ## Releases: - Last release was 1.5.8 on July 14th 2019 ----------------------------------------- Attachment G: Report from the Apache Cassandra Project [Nate McCall] ## Description: Apache Cassandra software is a highly scalable second-generation distributed database. ## Issues: The project is waiting on clear documentation on the policy of the permitted composition of releases. The project is following the same release procedure it has for the past 11 years, as it was developed in the incubator. This procedure adheres to all current documentation of the ASF's release policy. The project was recently told this was not the case. The project requests this policy documentation be clarified. The project has applied what it presumes to be an accurate and efficient fix to trunk, but not on our older release branches: 2.2, 3.0 and 3.11. Addressing the issue involved significant effort over a number of codebases, and distracted many from fixing critical technical issues in the 4.0 code. This was the project's first 4.0 RC release after many years of feature freeze (on the whole project) as it focuses on stabilisation efforts. At a critical point in time for the project, with a number of community events coordinated, it was unfortunate timing for the issue to be raised and demanded to be immediately fixed. The project is interested in improving how communication happens across the ASF. Recent interjections have disrupted the health of the community. Despite best intentions to be constructive the issues were raised in an authoritative manner over the project, and with only a little homework were quickly proven as factually wrong. While these issues could have been easily raised by a contributor without controversy, they also demonstrate the challenges of good communication. ## Membership Data: Apache Cassandra was founded 2010-02-17 (11 years ago) There are currently 61 committers and 35 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - Paulo Motta was added to the PMC on 2021-02-09 - Berenguer Blasi was added as committer on 2021-04-01 - Štefan Miklošovič was added as committer on 2021-05-02 The PMC currently consists of 35 members. 38% work at Apple, 22% at DataStax. The remaining 40% do not share the any same employer. The project considers this a healthy ratio. ## Project Activity: Recent releases: 4.0-rc1 was released on 2021-04-25. After a previous failed attempt. 3.0.24 was released on 2021-02-01. 3.11.10 was released on 2021-02-01. A newly designed website was launched for Apache Cassandra. With a heavy focus on the community and the extent of Cassandra deployments. Work is ongoing with contributions to the documentation and providing versioned documentation for each release. The community is collecting its own website traffic stats using a self-hosted Plausible server. The project recommends ASF Infra considers evaluating hosting this for all projects. https://plausible.cassandra.apache.org/cassandra.apache.org The community organised the Apache Cassandra World Party, hosting presentations and lightning talks in three timezones (APAC, EMEA, AMER), attracting over a thousand participants. https://hopin.com/events/apache-cassandra-4-0-world-party Trademark issue with Aiven remain in discussion. ## Community Health: All MLs have seen a significant increase in traffic, attributed to the RC release of 4.0, the feature freeze on trunk ending, and ongoing efforts to build community momentum. The PMC takes regular discussions on how to improve community growth and encouraging contributors. The last thread on it received a lot of engagement, especially as new contributors are appearing now that the feature freeze on trunk is lifted. This thread started before a Board member interjected about not enough being done. Focus is currently on reviewer bandwidth and Jira ticket hygiene. https://lists.apache.org/thread.html/ra364097c4dafeeac52934bbf08687b3b54445c5758824c53bcb901b0%40%3Cdev.cassandra.apache.org%3E ----------------------------------------- Attachment H: Report from the Apache Clerezza Project [Hasan Hasan] ## Description: Apache Clerezza models the RDF abstract syntax in Java and provides supports for serializing, parsing, managing and querying triple collections (graphs). Apache Clerezza modules aim at supporting the development of Semantic Web applications and services. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Clerezza was founded 2013-02-20 (8 years ago) There are currently 16 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Furkan Kamaci on 2018-12-27. - No new committers. Last addition was Furkan Kamaci on 2018-12-27. ## Project Activity: Furkan Kamaci and Hasan will mentor a student within GSoC 2021 to work on a project using Apache Clerezza for data management layer. And currently, we are working on upgrading Apache Clerezza to use JUnit 5. The latest release was created on October 22, 2020. ## Community Health: At the moment, there is no improvement with respect to community health. We hope this will change after GSoC 2021 participation. ----------------------------------------- Attachment I: Report from the Apache Cocoon Project [Cédric Damioli] ## Description: The mission of Cocoon is the creation and maintenance of software related to Web development framework: separation of concerns, component-based ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Cocoon was founded 2003-01-22 (18 years ago) There are currently 79 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Javier Puerto on 2012-07-06. - No new committers were added. ## Project Activity: 2.1.13 was released on 2020-07-29. Since then, only really low activity. ## Community Health: Even if the project is in maintenance mode with low activity on both dev and users lists, we still see active users on the project. ----------------------------------------- Attachment J: Report from the Apache Community Development Project [Swapnil Mane] ## Description: The mission of Community Development is the creation and maintenance of software related to Resources to help people become involved with Apache projects ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Community Development was founded 2009-11-01 (12 years ago) There are currently 39 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members. Last addition was Roy Lenferink on 2020-05-04. - No new committers. Last addition was Priya Sharma on 2020-10-27. ## Project Activity: ALC In the previous quarter, we had a request to create an ALC in Lagos, Nigeria and were looking for volunteers from the community to help establish the new chapter. We are happy to report that the minimum requirements to establish an ALC is achieved for ALC Lagos (Nigeria) [1]. We are now working on starting a formal vote to establish the ALC Lagos. ALC Beijing celebrated its first anniversary.[2] ApacheCon The CFP for the Community track at ApacheCon@Home has been successful, and we are now reviewing submissions. GSoC The ASF has once again been accepted as a GSoC mentoring organisation and we are now currently ranking the various project proposals. Other We have received some feedback on the tools we have provided[3][4]. The Nearby Apache people service was stopped due to lack of interest, so we will continue to monitor for volunteers willing to help revive it if necessary. ## Community Health: We have had lots of active discussions this quarter with one of the most popular being about the possible introduction of digital merit badges.[5] The thread received lots of feedback both for and against the idea. A new discussion on bringing together ASF projects that are related to Healthcare [6] has been discussed. ComDev has been suggested as being responsible to oversee and manage this initiative. Traffic on our dev mailing list and especially JIRA is up significantly this quarter probably due to the GSoC activity as well as general discussions. [1] https://s.apache.org/2lttu [2] https://s.apache.org/m2q2l [3] https://s.apache.org/znpff [4] https://s.apache.org/6vov2 [5] https://s.apache.org/j9cod [6] https://s.apache.org/tgh0l ----------------------------------------- Attachment K: Report from the Apache CouchDB Project [Jan Lehnardt] ## Description: Apache CouchDB software is a document-oriented database that can be queried and indexed in a MapReduce fashion using JavaScript. CouchDB also offers incremental replication with bi-directional conflict detection and resolution. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache CouchDB was founded 2008-11-19 (12 years ago) There are currently 68 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 9:2. Community changes, past quarter: - No new PMC members. Last addition was Jonathan Hall on 2020-02-12. - No new committers. Last addition was Balázs Donát Bessenyei on 2021-01-14. ## Project Activity: - spent significant amounts of time dealing with the bintray/artifactory migration - preparing a 3.2 release, including some new-contributor submitted features and bugfixes - continued progress on the next major release (4.x, details in reports from last year) ## Community Health: - activity across the board is picking up, including new contributors getting patches in ----------------------------------------- Attachment L: Report from the Apache Creadur Project [Philipp Ottlinger] ## Description: The mission of Creadur is the creation and maintenance of software related to Comprehension and auditing of software distributions ## Issues: No issues that require board attention. ## Membership Data: Apache Creadur was founded 2012-04-18 (9 years ago) There are currently 11 committers and 10 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 Karl Heinz Marbaise on 2016-08-30. - No new committers. Last addition was Karl Heinz Marbaise on 2016-08-30. ## Project Activity: Although the Whimsy report shows no Jira issues closed for the last quarter, there has been some activity and issues were resolved. Mainly CVE-related dependency updates and questions concerning the use of RAT. ## Community Health: Not many changes or requests at the moment. Hopefully I will be able to carve out a new release of RAT. ----------------------------------------- Attachment M: Report from the Apache Daffodil Project [Mike Beckerle] ## Description: Implementation of Data Format Description Language (DFDL) used to convert data from native formats into more easily processed forms such as XML, JSON, or the structures carried by data-processing fabrics. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Daffodil was founded 2021-02-16 (4 months ago) There are currently 13 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: This is our third board report since graduation to a TLP. The project continues to move towards its first TLP release which will be 3.1.0. The major features needed are in place including * the first version of the C-code generator - a new lightweight, small-footprint C-code generator that we hope will attract new contributors * raw validation output * command-line debugger improvements ## Community Health: We have 3 new contributors who have expressed interest and started work. Our hope is of course that they will stay engaged and become committers. Our stats look healthier this month across the board. ----------------------------------------- Attachment N: Report from the Apache DataSketches Project [Lee Rhodes] ## Description: The mission of Apache DataSketches is the creation and maintenance of software related to an open source, high-performance library of streaming algorithms commonly called "sketches" in the data sciences. Sketches are small, stateful programs that process massive data as a stream and can provide approximate answers, with mathematical guarantees, to computationally difficult queries orders-of-magnitude faster than traditional, exact methods ## Issues: There are no issues requiring board attention. ## Membership Data: Apache DataSketches was founded 2020-12-15 (5 months 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 Alexander Saydakov on 2020-12-15. - No new committers. Last addition was Charlie Dickens on 2020-12-18. ## Project Activity: Internal work on Java library for JDK 9+ and new C++ Memory model. ## Community Health: Good Health. LinkedIn adopted our library via Apache Pinot (uses DataSketches).. ----------------------------------------- Attachment O: Report from the Apache DeltaSpike Project [Mark Struberg] ## Description: Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency Injection) extensions intended to make application development easier when working with CDI and Java EE. Some of its key features include: - A core runtime that supports component configuration, type safe messaging and internationalization, and exception handling. - A suite of utilities to make programmatic bean lookup easier. - A plugin for Java SE to bootstrap both JBoss Weld and Apache OpenWebBeans outside of a container. - JSF integration, including backporting of JSF 2.2 features for Java EE 6. - JPA integration and transaction support. - A Data module, to create an easy to use repository pattern on top of JPA. Testing support is also provided, to allow you to do low level unit testing of your CDI enabled projects. ## Issues: There are no issues requiring board attention at this time. ## Activity: We shipped a release in March and are mostly in maintenance mode. Sometimes new feature requests pop up which we look at, but nothing fancy. Statistics say we had a much improved last quarter in terms of activity. But it doesn't feel like it. It's just if there is some work to do, then we do it. ## Health report: Stable and okish. Enough people around to vote and roll releases for sure. ## Releases - 1.9.5 was released on 2021-03-10. - 1.9.4 was released on 2020-06-12. - 1.9.3 was released on 2020-02-05. ## Project Composition: - There are currently 35 committers and 19 PMC members in this project. - The Committer-to-PMC ratio is roughly 9:5. ## Community changes, past quarter: - No new PMC members. Last addition was Harald Wellmann on 2016-05-19. - No new committers. Last addition was Christian Beikov on 2019-10-21. ----------------------------------------- Attachment P: Report from the Apache DolphinScheduler Project [Lidong Dai] ## Description: Apache DolphinScheduler is a distributed, extensible visual Big Data workflow scheduler system. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache DolphinScheduler was founded 2021-03-17 (2 months ago) There are currently 32 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - Calvin Kirs was added to the PMC on 2021-05-07 - Shiwen Cheng was added as committer on 2021-04-01 - Chong Zhuang was added as committer on 2021-04-09 ## Project Activity: DolphinScheduler 1.3.6 was released on 2021-04-28. Contributors are working on an architecture refactoring for DolphinScheduler - version 2.0 ## Community Health: We will hold a global online co-meetup outside of China for the first time on May 15 with the Apache ShardingSphere community. We are working hard to build a global community, we created slack workspace and some instant talks move to slack channel, and we also create tag as apache-dolphinscheduler on stackoverflow. 434 PRs opened on GitHub, past quarter (no change) 436 PRs closed on GitHub, past quarter (no change) 307 issues opened on GitHub, past quarter (-14% change) 352 issues closed on GitHub, past quarter (-8% change) dev@dolphinscheduler.apache.org had a 48% decrease in traffic in the past quarter (138 emails compared to 261) ----------------------------------------- Attachment Q: Report from the Apache Drill Project [Charles Givre] ## Description: The mission of Drill is the creation and maintenance of software related to Schema-free SQL Query Engine for Apache Hadoop, NoSQL and Cloud Storage ## Issues: One minor issue. We requested some config changes to the Drill github repository (https://issues.apache.org/jira/browse/INFRA-218050) and have not received any response on this. ## Membership Data: Apache Drill was founded 2014-11-18 (6 years ago) There are currently 59 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Bohdan Kazydub on 2020-01-28. - No new committers. Last addition was Cong Luo on 2021-01-19. ## Project Activity: The Drill community is gearing up for the release of Drill 1.19 which will be a a very large improvement over Drill 1.18. We project a release date of mid June. Drill 1.19 will include: * New connectors for Cassandra/Scylla and ElasticSearch * Streaming REST API * Improvements to the Kafka, Kudu, and Mongo connectors * Updates to the parquet reader * A format reader for XML data, as well as integration with the REST plugin * Integration of a streaming Excel reader so Drill can read Excel files of arbitrary size * Security improvements to incorporate a password vault * Access controls around storage plugins * Resolution of numerous CVEs * Much more... The Drill community has been requesting more frequent (but smaller) releases, so after Drill 1.19 is released, we will make every effort to move to quarterly releases rather than biannual releases. Recent releases: * 1.18.0 was released on 2020-09-04. * 1.17.0 was released on 2019-12-26. * 1.16.0 was released on 2019-05-02. ## Community Health: The Drill community is healthy with actiivty comparable to last quarter. One metric not reflected here, is that our Slack channel has grown considerably over the last quarter. More dev and user interaction is happening there than via the email lists. Slack doesn't seem to have quarterly metrics, but I will attempt to gather some metrics for the next report. * dev@drill.apache.org had a 21% increase in traffic in the past quarter (622 emails compared to 514) * user@drill.apache.org had a 295% increase in traffic in the past quarter (83 emails compared to 21) * 62 issues opened in JIRA, past quarter (14% increase) * 44 issues closed in JIRA, past quarter (-18% change) * 78 commits in the past quarter (-16% change) * 17 code contributors in the past quarter (13% increase) * 48 PRs opened on GitHub, past quarter (-20% change) * 52 PRs closed on GitHub, past quarter (-8% change) ----------------------------------------- Attachment R: Report from the Apache Empire-db Project [Rainer Döbele] ## Description: Empire-db is an object orientated API for dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems. With an SQL centric, no-compromise approach Emprie-db attempts to makes the full power of the database system available to applications. In contrast to object-relational-mapping it provides a easy, intuitive and string-free way to create SQL-statements of any complexity in order to query or manipulate data. ## Issues: There are no issues requiring the boards attention at this time. ## Membership Data: Apache Empire-db was founded 2012-01-24 (9 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 Jan Glaubitz on 2016-07-10. - No new committers. Last addition was Jan Glaubitz on 2015-10-05. ## Project Activity: There has been a considerable amount of development activity in the previous quarter with many existing issues resolved and new tickets for improvements created. This raises the possibility for an upcoming new release later this year. ## Community Health: Community is still active. The last release was in May, 2020. 14 issues opened in JIRA 6 issues closed in JIRA ----------------------------------------- Attachment S: Report from the Apache Flume Project [Balázs Donát Bessenyei] ## Description: The mission of Flume is the creation and maintenance of software related to A reliable service for efficiently collecting, aggregating, and moving large amounts of log data ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Flume was founded 2012-06-20 (9 years ago) There are currently 32 committers and 24 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Ferenc Szabo on 2019-01-28. - No new committers. Last addition was Tristan Stevens on 2020-01-07. ## Project Activity: The last quarter had low activity, likely due to people busy with other things. The last release was on January 8, 2019, more than two years ago. ## Community Health: The community shows low activity, but we still seem to have the necessary number of people around. A release is probably due sometime now; a PR was recently merged that also bumped a few outdated dependencies. ----------------------------------------- Attachment T: Report from the Apache FreeMarker Project [Dániel Dékány] ## Description: Apache FreeMarker is a template engine, i.e. a generic tool to generate text output based on templates. Apache FreeMarker is implemented in Java as a class library for programmers. FreeMarker 2 (the current stable line) produces releases since 2002. The FreeMarker project has joined the ASF in 2015, and graduated from the Incubator in early 2018. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity was low in recent months. Voting on 2.3.31 was finished and it was released. ## Health report: Activity is low but steady, as is usual for this project. User questions (mostly on StackOverflow) and new Jira issues are being answered promptly. The short term goal is to develop the next micro version. The long term goal is continuing the ongoing development on the 3.0 branch, so that the project can innovate and the code base can become much cleaner and more attractive for new committers. ## PMC changes: - Currently 7 PMC members. - No changes since the graduation on 2018-03-21 ## Committer base changes: - Currently 8 committers. - Last added: Siegfried Goeschl on 2020-01-07 ## Releases: - 2.3.31 was released on 2021-02-16 ----------------------------------------- Attachment U: Report from the Apache Geode Project [Karen Miller] ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. ## Issues: Karen Miller notified the PMC on 7-April-2021 of her intent to resign from the position of PMC Chair. Karen has held the position since Dec 2018. The community solicited nominations and conducted an election. A resolution has been submitted separately from this report naming Dan Smith (upthewaterspout) as the new Apache Geode PMC Chair. ## Membership Data: Apache Geode was founded 2016-11-15 (over 4 years ago) There are currently 114 committers and 54 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Donal Evans was added to the PMC on 2021-03-22 - Alberto Gomez was added as committer on 2021-02-17 - Kamilla Aslami was added as committer on 2021-04-19 - Matthew Reddington was added as committer on 2021-03-24 - Ray Ingles was added as committer on 2021-03-18 - Bruce Schuchardt resigned from the PMC on 2021-04-28; he remains a committer on the project. ## Project Activity: Three releases of Apache Geode were issued during this reporting period. Work areas included: - Improvements to existing tests and addition of new ones - Improvements to WAN replication - Several bug fixes and improvements in the area of disaster recovery and restart Recent releases: - 1.13.2 was released on 2021-03-29. - 1.12.1 was released on 2021-02-26. - 1.12.2 was released on 2021-04-22. ## Community Health: Initiatives during this period include: - Implementation of CODEOWNERS and CODEWATCHERS lists to facilitate PR reviews - For the geode-native client, ongoing discussions regarding C++ version support and coding standards These initiatives and the releases listed above are reflected in Apache Geode repository activity: - 308 issues opened in JIRA, past quarter (30% increase) - 236 issues closed in JIRA, past quarter (6% increase) - 691 commits in the past quarter (50% increase) - 62 code contributors in the past quarter (10% increase) - 488 PRs opened on GitHub, past quarter (29% increase) - 478 PRs closed on GitHub, past quarter (28% increase) PMC member Barry Ogelesby published [Transmitting Deltas Between Different Apache Geode Distributed Systems](https://medium.com/@boglesby_2508/transmitting-deltas-between-different-apache-geode-distributed-systems-e46a3eae931) on 23-March-2021. ----------------------------------------- Attachment V: Report from the Apache Giraph Project [Dionysios Logothetis] ## Description: The mission of Giraph is the creation and maintenance of software related to Iterative graph processing system built for high scalability ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Giraph was founded 2012-05-15 (9 years ago) There are currently 20 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Dionysios Logothetis on 2018-04-22. - No new committers. Last addition was Dionysios Logothetis on 2018-04-23. ## Project Activity: - No new commits - Security related feature currently under review ## Community Health: - Even though there was not much activity this quarter, we're adding a fairly important feature around authorization/authentication and data encryption. ----------------------------------------- Attachment W: Report from the Apache Gora Project [Kevin Ratnasekera] ## Description: The mission of Gora is the creation and maintenance of software related to ORM framework for column stores such as Apache HBase and Apache Cassandra with a specific focus on Hadoop ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Gora was founded 2012-01-24 (9 years ago) There are currently 31 committers and 31 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Lahiru Jayasekara on 2020-04-30. - No new committers. Last addition was Lahiru Jayasekara on 2020-04-28. ## Project Activity: - 0.9 was released on 2019-08-15 and we are currently working on our development drive for next release. We have made some good progress from last quarterly report, now we have initiated pull request Hackathon to review and clear the existing PR s queue. There were many PMC members volunteered in driving these efforts and there were many solid contributions received from PMC members. - We have received a solid proposal for GSoC and we are planning to participate this year GSoC if we are able to allocate a slot. ## Community Health: - Compared to previous quarter, there is a considerable increase in level of activity in both mailings lists as well as on Github. These activity reflects the mainly the development work carried out from PMC members. Hopefully once the development work is completed, we are looking forward to proceed with our major release which is pending from us for while. ----------------------------------------- Attachment X: Report from the Apache Griffin Project [William Guo] ## Description: - Apache Griffin is an open source Data Quality solution for Big Data, which supports both batch and streaming mode. It offers an unified process to measure your data quality from different perspectives, helping you build trusted data assets, therefore boost your confidence for your business. ## Issues: - So far, there's no particular issue requiring the board's attention. ## Membership Data: - There are currently 21 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, the past quarter: - Keep stable. ## Project Activity: - New Feature adding, 1.Rewrite the Rule/Measure implementations - Enhancement including, 1. Notifying by email 2. Improve merge_pr.py script 3. Support cross-version compilation for Scala and other dependencies 4. Standardize Batch Data Connectors. - Bug identifying and fixing, 1. Oracle connection for Apache Griffin 2. DirectKafkaInputDStream has not been initialized 3. GET jobs API not working after publishing DQ ## Community Health: - dev@griffin.apache.org had 27 threads in the past quarter - 3 issues were opened in JIRA in the past quarter - 5 tasks were opened in JIRA including 4 improvements, 1 feature in the past quarter - 1 commits in the past quarter - 2 PRs opened on GitHub in the past quarter - 1 PRs closed on GitHub in the past quarter ----------------------------------------- Attachment Y: Report from the Apache Groovy Project [Paul King] ## Description: Apache Groovy is responsible for the evolution and maintenance of the Groovy programming language ## Issues: No issues requiring board attention at this time. ## Membership Data: Apache Groovy was founded 2015-11-18 (5 years ago) There are currently 20 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Eric Milles on 2020-11-20. - No new committers. Last addition was Mikko Värri on 2020-06-03. ## Project Activity: We continue to work on bug fixes for 2.5.x and 3.0.x and continue to assist other non-Apache projects within the Groovy ecosystem move to Groovy 3. We are also continuing on our roadmap for Groovy 4 and recently released another alpha version. We expect to move to beta/RC versions shortly with GA release expected later this year. We have also had some activity related to the bintray sunset: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ Bintray was still the path to Maven Central for older "org.codehaus" Groovy artifacts but now that is no longer the case. Recent releases: - 3.0.8 was released on 2021-04-19. - 4.0.0-alpha-3 was released on 2021-04-16. Our most comprehensive historical download statistics are from Maven Central and Bintray. With Bintray's sunset, as mentioned earlier, we haven't found a good exact replacement for those statistics. Our anticipation is that downloads will pick up from Maven Central and ASF mirrors (where we don't have similar statistic reporting capabilities). This seems to be the case so far. Downloads from Maven Central for Mar 2021 were 34.2 million compared to 16.6 million for the same month in 2020. We also have a track in the upcoming Apachecon @Home conference where we are currently reviewing the CFP submissions. ## Community Health: This quarter, 278 commits (538 across all branches) were contributed from 25 contributors including 51 commits from 20 non-committer contributors (18 new). In recent times, Groovy has benefited from contributions from hacker events, student projects and bug bashes. This has been beneficial for the project but it seems difficult to attract such contributors to hang around longer term. We will continue to work on making it easy for newcomers to find a foothold within the project. Activity across mailing lists, issues and pull requests remained healthy: - 139/177 issues were opened/closed in JIRA during the quarter. - 85/86 PRs were opened/closed on GitHub during the quarter. ----------------------------------------- Attachment Z: Report from the Apache HTTP Server Project [Joe Orton] ## Description: The mission of HTTP Server is the creation and maintenance of software related to Apache Web Server (httpd) ## Issues: There are no issues requiring board attention. ## Membership Data: Apache HTTP Server was founded 1995-02-27 (26 years ago) There are currently 127 committers and 54 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Mario Brandt on 2020-04-27. - Ivan Zhakov was added as committer on 2021-04-12 ## Project Activity: Apache httpd 2.4.46 was released on 2020-08-05, which is our latest release. The project came close to a new release (2.4.47) in the last month, but failed at the last hurdle as a regression was discovered just hours before the release announcement. Having determined how to address the new issue, the Release Manager has proposed to tag and roll a new release in the coming weekend (May 16th). Huge thanks should go to to first-time release manager Christophe Jaillet for taking on the duties and mastering the process. Other than discussion around the releases, mailing list activity was relatively quiet in this quarter, primarily covering reviews of proposed backports from trunk to the 2.4.x branch. ## Community Health: Mailing list activity was up slightly this quarter on the previous quarter. GitHub activity continues to be a source of new contributions to the project as well as a testbed for backports and exercising the CI by committers; activity here was at a lower level than in the previous quarter (16% fewer PRs opened). Similarly, direct commit activity was down on the previous quarter. ASF member Ivan Zhakov accepted an invitation to become an HTTP Project committer, and was added to the committer list in April. ----------------------------------------- Attachment AA: Report from the Apache HttpComponents Project [Michael Osipov] ## Description: - The Apache HttpComponents project is responsible for creating and maintaining a toolset of low-level Java components focused on HTTP and associated protocols. ## Issues: - There are no issues requiring board attention at this time. ## Project Activity: - Minimal changes have occured for 4.x branches - Work for both Core and Client on 5.x has been done by external contributors. - More and more tickets arrive for the 5.x line - The 5.1 branches are of GA quality - 5.1 branches will be the last to support Java 7 - Active feature developments happens on master (5.2.x) ## Community Health: - Overall the project remains active. Issues and dicussions are resolved in time. ## Membership Data - No changes ## Releases: - HttpComponents Core 5.1.1 GA was released on 2021-05-06 - HttpComponents Core 5.0.4 GA was released on 2021-05-06 - HttpComponents Core 5.1 GA was released on 2021-03-15 - HttpComponents Client 5.1 beta 1 was released on 2021-02-11 ----------------------------------------- Attachment AB: Report from the Apache Ignite Project [Dmitry Pavlov] ## Description: The mission of Ignite project is the creation and maintenance of software related to high-performance distributed database engine providing in-memory and persistent data caching, partitioning, processing, and querying components. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Ignite was founded 2015-08-19 (6 years ago) There are currently 58 committers and 35 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Alex Plehanov on 2020-11-18. - Ivan Daschinsky was added as committer on 2021-04-09 - Mauricio Stekl was added as committer on 2021-03-01 ## Project Activity: Development: - 2.10.0 was released on 2021-03-15 (latest stable), it is next major release contatining a number of features. - (extensions) pyignite-0.4.0-rc1 was released on 2021-04-21. - Community discussed possible future major releases (verisioning is grand.major.fix), migth contain uncompatible changes instead of next grand release only. Events - Ignite summit CFP has been closed. Event comittee decided which talks are to be accepted to the final program. ## Community Health: - Ignite summit caused interest from speakers, event schedule was extended. - Mailing lists activity is the same with the past quarter. - User list activity decrease most likely caused by statistic calculation issue. - PRs activity has ~ 20% decrease - quite minor, but commits count decreased markably ~ -40%. ----------------------------------------- Attachment AC: Report from the Apache Impala Project [Jim Apple] ## Description: The mission of Apache Impala is the creation and maintenance of software related to a high-performance distributed SQL engine ## Issues: ## Membership Data: Apache Impala was founded 2017-11-14 (3 years ago) There are currently 56 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Csaba Ringhofer on 2020-02-18. - No new committers. Last addition was Abhishek Rawat on 2020-12-08. ## Project Activity: During February, March, and April, the Impala community: * Upgrad dependencies: DataSketches, thrift, Impyla, Bzip2, LZ4, Snappy, Zlib, ZStd, urllib3, python requests, Paramiko, springframework, JacksonDatabing, and slf4j * Added improvements to compatibility with ABFS, RHEL 8, Iceberg, S3, Ubuntu 20.04, Ranger, Kudu, Calcite, Google Cloud Storage, UTF-8, Hive, ORC, and docker hub * Addressed reliability for failed nodes and teardowns * Added result spooling * De-flaked many tests * Added most components needed for supporting external frontends * Added support for spilling to S3 ## Community Health: The community is overall healthy. This quarter has a common amount of variability in some previous metrics. It is not infrequent that this variability has no plainly obvious cause. * 157 patches were committed this quarter, vs. 153 the previous quarter * 212 tickets were opened, up 24%, and 152 tickets were closed, down 67% * reviews@ traffic was up 33% to 3288 emails ----------------------------------------- Attachment AD: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for May 2021 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are presently 37 podlings incubating. In April, podlings executed 4 distinct releases. We added 5 new IPMC members, and none retired. There was two IP clearances in April, and there was one new podling ShenYu, and another is under active discussion. No podlings graduated last month. This month we were missing reports from Livy, Pinot, and Weex. Livy has missed five reports in a row, a roll call was taken for Livy, and two PMC members responded. The IPMC will discuss retiring the project. A vote is in progress to retire Weex. MXNet has new outstanding trademark and branding issues. In a review of a release of Doris, the IPMC found several serious trademark and branding issues. The PMC is working on them, but it looks like the current trademark owner wants to continue using the name, which means they're likely to confuse users and risk Doris graduating. In a review of a Liminal release, a dependency on an LGPL library chardet was found. It turns out this is a common dependency and will impact several TLPs, including Apache Airflow. The community is working out the best way to get this dependency relicensed (which seems unlikely), replaced with something else or making it optional. Good progress has been made, working with 3rd parties. An external project interviewed several IPMC members as part of a study to see what makes projects successful. The Incubator track for ApacheCon is being organised. Further cleanup was done in removing old releases from current podlings. Still to sort out their releases areas are Crail, Livy, MXNet, Nemo and Pinot. Some old outstanding JIRAs were cleaned up, and there was a discussion on fixing up retired podling websites. As usual, most discussions on the mailing list were around releases, new project proposals and selecting good names for podlings and finding new mentors. ## Community ### New IPMC members: - Atri Sharma - Jincheng Sun - Lidong Dai - Yu Li - Zhenxu Ke ### People who left the IPMC: - None ## New Podlings - ShenYu ## Podlings that failed to report, expected next month - Livy - Pinot - Weex ## Graduations - None The board has motions for the following: - None ## Releases The following releases entered distribution during the month of April: - Flagon Useralejs 2.1.1 - Hop 0.70 - Pinot 0.7.1 - Yunikorn 0.10.0 ## IP Clearance - tika-helm - Ballista ## Legal / Trademarks Note that legal policy has been clarified and made clear that: - Jars containing compiled code cannot be include in source releases - Category b code in any form cannot be include in source releases ## Infrastructure - None ## Miscellaneous - None ## Table of Contents [Annotator](#annotator) [Doris](#doris) [Heron](#heron) [Milagro](#milagro) [NLPCraft](#nlpcraft) [PageSpeed](#pagespeed) [SDAP](#sdap) [Sedona](#sedona) [Spot](#spot) [Toree](#toree) [Training](#training) [Tuweni](#tuweni) -------------------- ## Annotator Annotator provides annotation enabling code for browsers, servers, and humans. Annotator has been incubating since 2016-08-30. ### Three most important unfinished issues to address before graduating: 1. Add active contributors 2. Stabilize a release cadence 3. Continue to demonstrate good governance ### Are there any issues that the IPMC or ASF Board need to be aware of? Community building has been very slow and it has been a long time since the project added new committers or PPMC members. After a period of relative inactivity and a conversion of the codebase to TypeScript, the project is long overdue for a second release. The IPMC should expect to see the project vote on a second release before the next board report to demonstrate forward momentum. ### How has the community developed since the last report? There have been some one-off contributions to project documentation and questions raised by people evaluating the project for use, but there have not been sustained contributions or involvement from new folks yet. ### How has the project developed since the last report? The project is now making continuous development packages to make it easier for developers to test upcoming releases. There is now tooling in place for generating API documentation, with plans to integrate the generated documentation into the website. The existing interfaces have all been documented. These efforts are all focused around the current goal of building community by making it easier for developers to become familiar with the project. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2020-07-11 ### When were the last committers or PPMC members elected? 2018-09-04 ### Have your mentors been helpful and responsive? Yes. Mentors have been as available when needed, but the project will reach out to get advice on what else could be done to make the project more accessible to new contributors and to grow the community. ### Is the PPMC managing the podling's brand / trademarks? There are no branding issues that the PPM is aware of. ### Signed-off-by: - [X] (annotator) Nick Kew Comments: - [X] (annotator) Tommaso Teofili Comments: - [X] (annotator) Benjamin Young Comments: Apologies for the lack of sign-off last month! ### IPMC/Shepherd notes: -------------------- ## Doris Doris is a MPP-based interactive SQL data warehousing for reporting and analysis. Doris has been incubating since 2018-07-18. ### Three most important unfinished issues to address before graduating: 1. More releases and rich product features. 2. Attract more users and contributors to make the community more prosperous. 3. There are some branding issues need to be addressed ### Are there any issues that the IPMC or ASF Board need to be aware of? There are some branding issues need to be addressed, which has been discussed in [1] And we are working on it. [1] https://lists.apache.org/thread.html/rf51fad9228bf38f9fdf8ee0f691550e69853c7b1a31a8d23381a52ce%40%3Cprivate.doris.apache.org%3E ### How has the community developed since the last report? Since the last report, we have added 8 contributors. There are currently 156 contributors and 21 committers. We have also conducted some online and offline meetup with the main developers of the community, and designated a Doris roadmap for 2021. ### How has the project developed since the last report? 1. We are still working on releasing Doris 0.14, but we met some NOTICE file problems. The new release vote will be issued soon. ### 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: 2021-01-22 ### When were the last committers or PPMC members elected? 1. We are voting to invite a Committer(Zhengguo Yang) to join PPMC[1]. [1] https://lists.apache.org/thread.html/ra594f03122283ce963de5bc57b372152ea607e58e156b9418cb114e9%40%3Cprivate.doris.apache.org%3E ### Have your mentors been helpful and responsive? All mentors are helpful, especially on the issue of branding, they helped us a lot. ### Is the PPMC managing the podling's brand / trademarks? Yes, we have encountered some problems, but they are being resolved. These problems include unreasonable use of domain names, product names, and the migration of official docker images. ### Signed-off-by: - [X] (doris) Willem Ning Jiang Comments: We need to updated the latest status of the branding issue. - [ ] (doris) Shao Feng Shi Comments: - [X] (doris) Ming Wen Comments: ### IPMC/Shepherd notes: -------------------- ## Heron A real-time, distributed, fault-tolerant stream processing engine. Heron has been incubating since 2017-06-23. ### Three most important unfinished issues to address before graduating: 1. Building the community 2. Making releases 3. Make Heron easier to adopt ### Are there any issues that the IPMC or ASF Board need to be aware of? N/A ### How has the community developed since the last report? The community has remained consistent. New presentations in the monthly meetups. Increasing the community should be one of the major goals for the project. ### How has the project developed since the last report? - Bug/issue fixes - Feature and documentation improvements - Tried to Build the first convenience docker image ### 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: 2021-1-14: 0.20.3-incubating ### When were the last committers or PPMC members elected? The last two new committers voted in: Oliver Bristow (July 22, 2020) Windham Wong (July 3, 2020) ### Have your mentors been helpful and responsive? Mentors have been helpful for the new release and answering questions. ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (heron) Jake Farrell Comments: - [ ] (heron) Julien Le Dem Comments: - [ ] (heron) P. Taylor Goetz Comments: - [X] (heron) Dave Fisher Comments: - [ ] (heron) Ming Wen Comments: - [X] (heron) Kevin Ratnasekera Comments: ### IPMC/Shepherd notes: -------------------- ## Milagro Milagro is core security infrastructure and crypto libraries for decentralized networks and distributed systems. Milagro has been incubating since 2015-12-21. ### Three most important unfinished issues to address before graduating: 1. Continue to build relevant and useful crypto libraries and applications for decentralized networks in order to grow the ecosystem of users and contributors to the project. 2. Continue to improve compliance with the Apache Way. In particular to update the Milagro website and other project sites (e.g. Whimsy) in accordance with Apache policies. 3. Further releases to increase the scope of the Milagro project, extend the capability of existing releases and to demonstrate improved compliance with the Apache Way. ### Are there any issues that the IPMC or ASF Board need to be aware of? No significant issues, however some administrative tasks around the project are still outstanding largely due to the pandemic but are now being addressed. In particular, a PPMC meeting to discuss the project roadmap needs to be arranged, old releases need to be deleted, confirmation that the project's Whimsy, Clutch, SVN, Confluence & Committers pages are all current, and the code signing keys needs countersigning. ### How has the community developed since the last report? No change. ### How has the project developed since the last report? Works is progressing preparing the MPC library for its first official Apache release. ### 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: 2020-02-10 ### When were the last committers or PPMC members elected? February 2020 ### Have your mentors been helpful and responsive? No issues ### Is the PPMC managing the podling's brand / trademarks? No known issues, but further investigation is still required by the Milagro community. ### Signed-off-by: - [X] (Milagro) Nick Kew Comments: There appears to be a cut and paste error. Will raise the subject on list. - [X] (Milagro) Jean-Frederic Clere Comments: ### IPMC/Shepherd notes: Justin Mclean: Can you please remove your old releases from the list release area. -------------------- ## NLPCraft Apache NLPCraft is an open source library for adding natural language Interface to modern applications. Apache NLPCraft has been incubating since 2020-02-13. ### Three most important unfinished issues to address before graduating: 1. Community growth & outreach. 2. Get to the point with multiple release managers. 3. Presenting the project at ApacheCon/ApacheAsia 2021. ### Are there any issues that the IPMC or ASF Board need to be aware of? Project have several new contributors that we are expecting to formally join the project/ASF in the future. These are individuals outside of the original NLPCraft community. We are also getting number of offline contributions when it comes to ideas, documentation and website. We are working on promoting these contributions and inviting these individuals to be more active. We need, however, to get much better at the general project outreach via meetups, conferences, etc. Some of the conversations happen on Gitter. Project has 8 forks on the Github. ### How has the community developed since the last report? Project produced 2 releases. Both releases were an interim, bug fix releases. So far, they were produced by the same release manager (Aaron Radzinski). The community is working on the major release 0.7.5 right now that should go GA in the April 2021 with significant changes and improvements (all of which are reflected in JIRA tickets for 0.7.5 version). At this point, the community does not have a formalized roadmap with many internal discussions happening on Slack channels. We are generally expecting to formalize the long-term roadmap towards 1.0.0 release with hopefully a larger community around the project. Community is actively working on 0.7.5 release that should be sent for a vote in the coming days. ### How has the project developed since the last report? ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: NLPCraft 0.7.4 released on Jan 31, 2021. ### When were the last committers or PPMC members elected? Aug, 2020 - Gleb Zernov (ifropc), committer. ### Have your mentors been helpful and responsive? We have had some problems with getting attention from mentors - however this has been largely resolved as of now. We've also identified some of the communication inefficiencies that would help us to engage mentors better going forward. ### Is the PPMC managing the podling's brand / trademarks? Yes, no issues to report. ### Signed-off-by: - [ ] (nlpcraft) Roman Shaposhnik Comments: - [X] (nlpcraft) Furkan Kamaci Comments: - [ ] (nlpcraft) Evans Ye Comments: - [ ] (nlpcraft) Paul King Comments: - [ ] (nlpcraft) Konstantin I Boudnik Comments: - [X] (nlpcraft) Dave Fisher Comments: ### IPMC/Shepherd notes: Justin Mclean: Can you please remove your old releases from the list release area. -------------------- ## PageSpeed PageSpeed represents a series of open source technologies to help make the web faster by rewriting web pages to reduce latency and bandwidth. PageSpeed has been incubating since 2017-09-30. ### Three most important unfinished issues to address before graduating: 1. Grow the number of active developers 2. Enhance the release process: switch to github tagged release to simplify. ### Are there any issues that the IPMC or ASF Board need to be aware of? While there is a healthy user base, the number of active developers remains persistently low. This seems to be a hard to address challenge. ### How has the community developed since the last report? Mailing lists and git issues are active. The number of active developers is unchanged. ### How has the project developed since the last report? Minor activity, updating deps on the 2.0-alpha. ### 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: We'll be blogging about the 2.0 Envoy PoC, hopefully that will get some developer interest as we pivot into the service mesh world ### Date of last release: The week of May 11th, 2020 ### When were the last committers or PPMC members elected? May 27 2019 (Longinos Ferrando, elected as both committer and PMC member) ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? As far as we know the brand is respected by third parties. ### Signed-off-by: - [ ] (pagespeed) Jukka Zitting Comments: - [ ] (pagespeed) Leif Hedstrom Comments: - [X] (pagespeed) Nick Kew Comments: ### IPMC/Shepherd notes: -------------------- ## SDAP SDAP is an integrated data analytic center for Big Science problems. SDAP has been incubating since 2017-10-22. ### Three most important unfinished issues to address before graduating: 1. Make official SDAP (Incubating) Release 2. Improve committer participation 3. Improve/create user guide documentation ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? New Committers and PPMC members elected ### How has the project developed since the last report? Completed: - Migrated SDAP to Python 3. New efforts and features: - Working on Elasticsearch integration. - Adding Apache Parquet support for in situ data - Integration with AWS Athena - Enhancements to support multispectral data ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: XXXX-XX-XX ### When were the last committers or PPMC members elected? Two new committers were elected in March 2021. ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. Have not heard from Jörn in a while. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? Not aware of any issues ### Signed-off-by: - [ ] (sdap) Jörn Rottmann Comments: - [X] (sdap) Trevor Grant Comments: ### IPMC/Shepherd notes: -------------------- ## Sedona Sedona is a big geospatial data processing engine. It provides an easy to use APIs for spatial data scientists to manage, wrangle, and process geospatial data. Sedona has been incubating since 2020-07-19. ### Three most important unfinished issues to address before graduating: 1. Need several release managers. 2. Currently, Jia is the release manager Complete IP clearance is not done yet. 3. Website may not be fully compliant with Apache guidelines ### Are there any issues that the IPMC or ASF Board need to be aware of? N/A ### How has the community developed since the last report? All good here. We are interacting with our users through dev@s.a.o and Gitter ### How has the project developed since the last report? 1. We published our first release Sedona 1.0.0. 2. We added several patches after the first release according to the community feedback ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ X] Initial setup - [ X] Working towards first release - [ X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2021-02-06 ### When were the last committers or PPMC members elected? ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. All good here ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? All good here ### Signed-off-by: - [x] (sedona) Felix Cheung Comments: - [ ] (sedona) Jean-Baptiste Onofré Comments: - [ ] (sedona) George Percivall Comments: - [ ] (sedona) Von Gosling Comments: ### IPMC/Shepherd notes: -------------------- ## Spot Apache Spot is a platform for network telemetry built on an open data model and Apache Hadoop. Spot has been incubating since 2016-09-23. ### Three most important unfinished issues to address before graduating: 1. Revive community activity (Discussion in mailing lists, increase frequency of commits) 2. Create a new roadmap and release plan that will improve adoption 3. Make it easier to contribute to the project (e.g. documentation, framework). ### Are there any issues that the IPMC or ASF Board need to be aware of? Not at this time ### How has the community developed since the last report? We're continuing to solidify a short term and long term on a roadmap with the community that will allow more contributors to focus and work on different levels of the project (i.e. data modeling and schema design, use-cases, ingestion, ml, ui, dev ops, docs, etc). These discussions have been delayed this quarter due to COVID and getting schedules aligned relative to other workloads. ### How has the project developed since the last report? The master branch of Apache Spot was largely developed on commercial but freely available Hadoop software (i.e. Cloudera, Hortonworks) that now have been either End of Life’d (or will be in 2022) in favor of the newer Cloudera Data Platform (CDP), or have been put behind a paywall to get updates. The cloud provider landscape has also changed drastically in the last few years and it's time that we start looking at better support for Quickstart options in each major cloud providers so we can further develop the project for the community with wider platform support, and give committers better options for creating development environments to more efficiently contribute to the project. The following topics are planned for the next set of discussions with the community to determine what we focus on for the next several quarters: - Add more native support on cloud infrastructure and software (i.e. AWS, Azure, GCP) - In the short-term we can focus on AWS EMR on standing up Spot and fixing any issues related to getting the software installed and working. - In the long term we will want to support several cloud providers and on-premise options depending on the interest of the community. - Add an infrastructure module to Spot to automate creating clusters in each providers we plan to support. - Initially we can focus on Cloudformation support with AWS EMR. - Our goal will be to generalize further in the long term with Terraform across each provider. - Investigate and explore alternative replacement for Spot UI (i.e. Apache Supersets) - In the short-term Apache Supersets may give us a basic authentication and visualization layer into the data landed and processed by Spot. - In the long-term we will need to develop a more comprehensive security and use-case roadmap for the UI and determine if it makes sense to develop something from scratch. The next step will be to create Jira Epic’s and tasks for these items so we can start to distribute the work across the community. ### 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: 2017-09-08 ### When were the last committers or PPMC members elected? 2019-09-02 ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. Yes our mentors have been helpful. We will be engaging them more soon for guidance on on-boarding new committers, as well as a few other items related to the Whimsy and Clutch reports and also updating the Apache Spot Podling website as this is missing a number of updates. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? Yes. ### Signed-off-by: - [X] (spot) Uma Maheswara Rao G Comments: Need few more mentors. Very less IPMC involvement currently. Need more efforts from IPMC in building community. IPMC roll call was going on. ### IPMC/Shepherd notes: -------------------- ## Toree Toree provides applications with a mechanism to interactively and remotely access Apache Spark. Toree has been incubating since 2015-12-02. ### Three most important unfinished issues to address before graduating: 1.Increase active contributors ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? It has been a quiet few months, with a few bug reported related to Apache Spark 3.x. The community also needs to update the latest RC to conform to the changes on release requirements for python packages. ### How has the project developed since the last report? Quiet few months with work needed to be done on the failed RC. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2020-07-31 ### When were the last committers or PPMC members elected? Kevin Bates was added to the PPMC on 2019-08-14 ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. There was nothing requiring mentor intervention on the last quarter. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? No Trademark issues ### Signed-off-by: - [X] (toree) Luciano Resende Comments: In case people ask about the contents of the report, the podling has reported last month, and not much changed since then. - [ ] (toree) Julien Le Dem Comments: - [ ] (toree) Ryan Blue Comments: ### IPMC/Shepherd notes: -------------------- ## Training The Training project aims to develop resources which can be used for training purposes in various media formats, languages and for various Apache and non-Apache target projects. Training has been incubating since 2019-02-21. ### Three most important unfinished issues to address before graduating: 1. Improve the participation from community for Apache Training Project 2. Create a tutorial on how the tools provided by this project can be used to create own content 3. Review current policies around contribution review and releases to find a pragmatic compromise ### Are there any issues that the IPMC or ASF Board need to be aware of? The Training Project needs more contribution from other Apache Projects. It also needs feedback from other Apache Projects on the presentations and trainings developed till now. ### How has the community developed since the last report? Activity has remained low since the last report. There were 8 posts in last 3 months. We have to work on strategies to increase the queries for contributions from individual contributors. ### How has the project developed since the last report? New training slides were added on following topics: * Apache Airflow PR activity is less since the last report. ### How would you assess the podling's maturity? There are currently some issues with this podling that we are working to address, we believe that the issues are not yet critical and can be turned around from within the community but want to make the board aware of this early on. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### When were the last committers or PPMC members elected? November 2020 ### Have your mentors been helpful and responsive? Mentors have been responsive and helpful when reached out to. ### Is the PPMC managing the podling's brand / trademarks? The name search process has not yet been started, as there is still time to do that if and when graduation draws nearer. The PPMC is actively monitoring usage of the Podlings current name on other sites. The Podling is not directly affiliating with any sponsors donating content and presenting an independent image on the webpage. ### Signed-off-by: - [X] (training) Craig Russell Comments: We may need more outreach to PMCs to ask them to add material. - [X] (training) Christofer Dutz Comments: - [X] (training) Justin Mclean Comments: - [X] (training) Lars Francke Comments: ### IPMC/Shepherd notes: -------------------- ## Tuweni Tuweni is a set of libraries and other tools to aid development of blockchain and other decentralized software in Java and other JVM languages. Tuweni has been incubating since 2019-03-25. ### Three most important unfinished issues to address before graduating: 1. More contributors! 2. Getting started, docs, videos 3. Finishing the Ethereum client ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? Community is increasing in size a bit, just with a bit more interest. The dev list increased to 29 subscribers. ### How has the project developed since the last report? The project is under active development. We have added crucial features to the project such as an Ethereum Virtual Machine, a proxy subprotocol and a network crawler. We need to cut another release but keep pushing it back, too much work. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2020-11-27 ### When were the last committers or PPMC members elected? Nicolas Melendez as committer on 2021-04-29. ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. All good, need a release out. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? No problems reported. ### Signed-off-by: - [ ] (tuweni) Jean-Baptiste Onofré Comments: - [X] (tuweni) Furkan Kamaci Comments: ### IPMC/Shepherd notes: ----------------------------------------- Attachment AE: Report from the Apache jUDDI Project [Alex O'Ree] ## Description: - jUDDI (pronounced "Judy") is an open source Java implementation of the Universal Description, Discovery, and Integration (UDDI v3) specification for (Web) Services. The jUDDI project includes Scout. Scout is an implementation of the JSR 93 - Java API for XML Registries 1.0 (JAXR). ## Issues: - There are no issues that require the board's attention at this time. ## Membership Data: Apache jUDDI was founded 2010-08-21 (11 years ago) There are currently 7 committers and 7 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Alex O'Ree on 2013-03-17. - No new committers were added. ## Activity: - jUDDI - last release was Aug 18, 2020, primarily bug fixes but includes some feature requests and support for additional database vendors. - SCOUT - last release 10 DEC 2018. Resolved several bugs and dependencies. ## Health report: - Low development activity is a factor for low mailing list volume, but in all likelihood, it's from a general lack of interest in the protocol. - No JIRA activity or mailing list activity (aside from spam) is also a factor for low development. - There are enough active PMC members to approve releases and respond to potential security issues. ## Releases: - 3.3.9 was released on 2020-08-18. - SCOUT-1.2.8 was released on Mon Dec 10 2018 ----------------------------------------- Attachment AF: Report from the Apache Juneau Project [James Bognar] ## Description: The mission of Apache Juneau is the creation and maintenance of software related to a toolkit for marshalling POJOs to a wide variety of content types using a common framework, and for creating sophisticated self-documenting REST interfaces and microservices using VERY little code ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Juneau was founded 2017-10-17 (4 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 Ayeshmantha Perera on 2019-01-02. - No new committers. Last addition was Ayeshmantha Perera on 2019-01-02. ## Project Activity: Recent releases: - 8.2.0: 2020-10-14 - 8.1.3: 2020-01-20 Community is currently working on version 9.0 with significant integration improvements with Apache HttpClient and injection-based environments such as Spring. This release is likely still months away from being ready. ## Community Health: The primary developers were unable to contribute as frequently as in the past due to other commitments which lead to a decrease in metrics: 46% decrease in traffic in the past quarter (13 emails compared to 24) 76 commits in the past quarter (-42% change) 2 code contributors in the past quarter (-33% change) We expect these dips in activity to be transient. ----------------------------------------- Attachment AG: Report from the Apache Kafka Project [Jun Rao] ## Description: Apache Kafka is a distributed event streaming platform for efficiently storing and processing a large number of records in real time. ## Project Activity: We released 2.8.0, which includes the following key features. - Early access of replace ZooKeeper with a self-managed quorum - Add Describe Cluster API - Support mutual TLS authentication on SASL_SSL listeners - JSON request/response debug logs - Limit broker connection creation rate - Topic identifiers - Expose task configurations in Connect REST API - Update Streams FSM to clarify ERROR state meaning - Extend StreamJoined to allow more store configs - More convenient TopologyTestDriver constructors - Introduce Kafka-Streams-specific uncaught exception handler - API to start and shut down Streams threads - Improve TimeWindowedDeserializer and TimeWindowedSerde to handle window size - Improve timeouts and retries in Kafka Streams We released 2.7.1, which fixes 41 critical issues. We released 2.6.2, which fixes 35 critical issues. We’ve continued steady progress toward the task of replacing ZooKeeper in Kafka. The early access in 2.8.0 demonstrated a 10X improvement in the amount of metadata supported. Tiered Storage work continues and unlocks infinite scaling and faster rebalance times via KIP-405. The KIP proposal has been accepted and the implementation is in progress. ## Community Dev mailing list had a 18% decrease in traffic in the past quarter (2572 emails compared to 3102). User mailing list had a 38% increase in traffic in the past quarter (510 emails compared to 367). We added 3 new PMC members, Chia-Ping Tsai on Mar. 11, Bill Bejeck on Apr. 7, and Randall Hauch on Apr. 15, respectively. We added 2 new committers, Tom Bentley on Mar. 12, and Bruno Cadonna on Apr. 12. Kafka Summit Europe 2021 is happening on May 11 and May 12, virtually. ## Releases 2.8.0 was released on Apr. 19, 2021. 2.7.1 was released on May 10, 2021. 2.6.2 was released on Apr. 21, 2021. ## Issues: There are no issues requiring board attention. ----------------------------------------- Attachment AH: Report from the Apache Kibble Project [Sharan Foga] ## Description: The mission of Apache Kibble is the creation and maintenance of software related to an interactive project activity analyzer and aggregator ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Kibble was founded 2017-10-18 (4 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: - Michał Słowikowski was added to the PMC on 2021-05-03 - Tomasz Urbaszek was added to the PMC on 2021-05-03 - Kaxil Naik was added as committer on 2021-02-21 ## Project Activity: Since the last report we have welcomed a new committer, a new PMC Chair and two new PMC members. A new git Kibble repo has been created for the code rewrite and the existing repo has been renamed Kibble-1. Current users are being re-directed to Kibble-1 as this is the code source for the Kibble demo. Progress has been slow but we hope to kick off activity again by working on a roadmap that will help focus the work. We have had some discussions on some potential features of vendor neutrality [3] that could be interesting. Also confirmed was the importance of Kibble as crucial part of the ASF reporter.apache.org tool [4] We have received a potential bug report [1] which we are looking into. A Kibble talk [2] has also been submitted for ApacheCon@Home as a basic introduction for projects looking for information about their community. ## Community Health: While development activity has been slow, discussions have been more active this quarter as we were waiting on the new repo to be created. Now that it is - we need to focus on having a clear roadmap that can be communicated within the community. It's good to see that our mailing list activity has increased this quarter mainly due to the discussions around planning the re-write. [1] https://s.apache.org/vgnbe [2] https://s.apache.org/rbx97 [3] https://s.apache.org/a5iux [4] https://s.apache.org/9tr8h ----------------------------------------- Attachment AI: Report from the Apache Knox Project [Larry McCay] ## Description: The mission of Apache Knox is the creation and maintenance of software related to simplifying and normalizing the deployment and implementation of secure Hadoop clusters. Knox accomplishes this through a combination of an HTTP gateway for proxying Hadoop and its ecosystem resources, SSO capabilities for UI access and support for token exchange patterns for integration usecases. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Knox was founded 2014-02-18 (7 years ago) There are currently 22 committers and 18 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 Sandor Molnar on 2019-11-20. - No new committers. Last addition was Sandor Molnar on 2019-11-21. ## Project Activity: 1.5.0 was released 2020-12-06 It is likely that a 1.5.1 release for a regression in OpenID Connect support will be spun soon, if not a 1.6.0. Community reporting of both the regression and the solution was contributed via JIRA. A large portion of the focus in the project over the last quarter has been on the creation of a UI for acquiring tokens for integration usecases with both JWT and new access tokens called Passcode tokens. ## Community Health: dev@knox.apache.org had a 17% increase in traffic in the past quarter (805 emails compared to 687) user@knox.apache.org had a 62% decrease in traffic in the past quarter (7 emails compared to 18) 27 issues opened in JIRA, past quarter (metrics report incorrect) 24 issues closed in JIRA, past quarter (metrics report incorrect) 42 commits in the past quarter (-27% change) 9 code contributors in the past quarter (no change) 46 PRs opened on GitHub, past quarter (170% increase) 44 PRs closed on GitHub, past quarter (144% increase) While Apache Knox seems to be reaching a level of maturity, it is still healthy in terms of community contribution and feature improvements. ----------------------------------------- Attachment AJ: Report from the Apache Kylin Project [Shao Feng Shi] Description: The mission of Apache Kylin is the creation and maintenance of software related to a distributed and scalable OLAP engine Issues: There is no issue requiring board attention. Membership Data: - Apache Kylin was founded 2015-11-18 (5 years ago) - There are currently 46 committers and 24 PMC members in this project. - The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. The last addition was Xiaoxiang Yu on 2020-10-08. - Zhichao Zhang was added as a committer on 2021-03-09 Project Activity: Recent releases: - 3.1.2 was released on 2021-04-26. - 4.0.0-beta was released on 2021-02-07. - 3.1.1 was released on 2020-10-18. Community Health: In the past quarter, most of our efforts are on Kylin 4.0 development and bugfix. Besides, we are taking care of some vulnerabilities and bugs for Kylin 3. - dev@kylin.apache.org had a 33% increase in traffic in the past quarter (180 emails compared to 135) - user@kylin.apache.org had a 34% decrease in traffic in the past quarter (59 emails compared to 89) - 87 issues opened in JIRA, past quarter (-5.6% change) - 52 issues closed in JIRA, past quarter (-2% change) ----------------------------------------- Attachment AK: Report from the Apache Libcloud Project [Tomaž Muraus] ## Description: Libcloud is a Python library that abstracts away the differences among multiple cloud provider APIs. ## Issues: There are no issues which require board attention at this time. ## Membership Data: Apache Libcloud was founded 2011-05-19 (10 years ago) There are currently 24 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - Clemens Wolff was added to the PMC on 2021-04-26 - Dimitris Moraitis was added to the PMC on 2021-05-07 - Dimitris Moraitis was added as committer on 2021-05-02 ## Project Activity: Since the last report we had no release, but we still had a good amount of activity across the board. We migrated our CI from Travis CI to Github Actions. This also included adding various new checks and new integration / end to end tests which exercise real provider APIs. We also added 1 new committer + 2 PMC members. ## Community Health: Community health continues to be OK. Most of the activity and contributions happens on Github. ----------------------------------------- Attachment AL: Report from the Apache Logging Services Project [Matt Sicker] ## Description: The mission of the Apache Logging Services project is to create and maintain of software for managing the logging of application behavior, and for related software components. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Logging Services was founded 2003-12-16 (17 years ago) There are currently 39 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - Robert Middleton was added to the PMC on 2021-03-21 - No new committers. Last addition was Stephen Webb on 2020-08-08. ## Project Activity: - In March, we released Log4j 2.14.1 which is primarily composed of bugfixes, dependency updates, and a few small feature updates. - In March, we decided to EOL support for Java 6 and Java 7. While the old releases of Log4j (2.3 and 2.12.1) are still available in the archives and Maven Central, we will no longer be linking to them on the website or in future release announcements. - In March, we welcomed Robert Middleton to the PMC. - In Log4j, we added improved Java module support for our upcoming 3.x branch. This allowed us to simplify our build requirements to use Java 11 without additional compiler versions. - In Log4j, we collaborated with the Spring project to work on improvements to allow them to migrate to Log4j as their default logging backend. - In log4cxx, we started efforts toward ABI compatibility automation. - In April, we began release preparations for log4cxx 0.12.0, to occur in the next quarter (i.e., next month). - In Chainsaw, we bumped the minimum Java version to 9 to repair and improve the macOS UI integration. ## Community Health: - Mailing list traffic and code activity increased back to more normal levels after the holidays. ----------------------------------------- Attachment AM: Report from the Apache ManifoldCF Project [Karl Wright] ## Description: The mission of ManifoldCF is the creation and maintenance of software related to Framework for connecting source content repositories to target repositories or indexes. ## Issues: No issues to report at this time. ## Membership Data: Apache ManifoldCF was founded 2012-05-15 (9 years ago) There are currently 25 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Markus Schuch on 2018-01-04. - No new committers. Last addition was Cihad Guzel on 2019-08-17. ## Project Activity: ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then, there have been numerous major releases, including a 2.18 release on December 28, 2020. The next major release, 2.19, is undergoing voting at this time. This quarter's activities centered mainly about bringing the Elastic Search connector up to date with changes to that platform. ## Community Health: We nominated and approved Cihad Guzel as committer on 8/16/2019. We nominated and approved Markus Schuch as a PMC member on 12/29/2017. We did not sign up any new PMC members or committers this quarter. We continue to be on the lookout for new PMC members and committers. As was true for last quarter, the light level of activity this quarter has limited our pool of new developers considerably. All developers we have have extensive outside commitments and the pandemic has, if anything, made that situation worse. However, existing committers have continued to contribute, and use the product. ----------------------------------------- Attachment AN: Report from the Apache Mesos Project [Qian Zhang] ## Description: The mission of Mesos is the creation and maintenance of software related to a cluster manager that provides efficient resource isolation and sharing across distributed applications ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Mesos was founded 2013-06-19 (8 years ago) There are currently 49 committers and 49 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Andrei Sekretenko on 2020-01-21. - No new committers. Last addition was Andrei Sekretenko on 2020-01-22. ## Project Activity: We have not made a release since 2020-11-24 (Mesos 1.11.0). The plan is to collect new feature requests from community and try to setup a roadmap for the next release. ## Community Health: Overall the community is not active, we have some GitHub PRs ongoing/complete, but not much in the review board. The plan is to call for new contributors and some existing committers for reviewing patches so that we could have enough people for the potential roadmap release. ----------------------------------------- Attachment AO: Report from the Apache MetaModel Project [Kasper Sørensen] ## Description: The mission of MetaModel is the creation and maintenance of software related to common interface for discovery, exploration of metadata and querying of different types of data sources ## Issues: There are no issues requiring board attention. ## Membership Data: Apache MetaModel was founded 2014-11-19 (6 years ago) There are currently 13 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members. Last addition was Arjan Seijkens on 2019-08-29. - No new committers. Last addition was Jörg Unbehauen on 2018-05-03. ## Project Activity: - 5.3.3 was released on 2021-02-23. - Not very much activity. ## Community Health: The community is maintaining the code and responding to issues, but otherwise it's fairly quiet. ----------------------------------------- Attachment AP: Report from the Apache Mnemonic Project [Yanhui Zhao] ## Description: Apache Mnemonic is an open-source Java library for durable object-oriented programming on hybrid storage-class memory(e.g. NVM) space. It comes up with durable object model (DOM) and durable computing model(DCM) and takes full advantages of storage-class memory to simplify the code complexity, avoid SerDe/(Un)Marshal, mitigate caching for constructing next generation computing platforms. Mnemonic makes the storing and transmitting of massive linked objects graphs simpler and more efficient. The performance tuning could also be mostly converged to a single point of tuning place if based on Mnemonic to process and analyze linked objects. The programmer is able to focus on the durable object oriented business logic instead of worrying about how to normalize/join, SerDe(un)marshal, cache and store their linked business objects with arbitrary complexity. ## Issues: None at this this time ## Membership Data: There are currently 20 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. ## Project Activity: Our 0.14.0 release was done on 03/28/2021. Since our last release of version 0.14.0, we have 8 new JIRA tickets majorly targeting JDK 14 upgrade, 8 JIRA tickets closed, 4PR merged. We are working toward our 0.15.0 release targeting early June, focusing on 1. Solve the resgc dependency 2. JDK 14 upgrade 3. Fix the issue that some test cases are causing errors 4. Review current test cases, remove duplicate test cases that test on the same features, improving test case running efficiency. Support test cases running with gradle. 5. Keep improving the website with updated information and webpage layout. ## Community Health: Our community has held regular meetings on biweekly basis, and we have covered the following topics on the project meeting - Project related training - Release target discussion and planning - New feature support discussion - Blocker issue discussion and possible solution - Encourage community engagement and looking to grow our developer communities Through our biweekly meetings, current committers and active developers are actively contributing and participating in the project. We plan to grow our community by recruiting other active developers. ----------------------------------------- Attachment AQ: Report from the Apache Oozie Project [Gézapeti] ## Description: The mission of Oozie is the creation and maintenance of software related to A workflow scheduler system to manage Apache Hadoop jobs. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Oozie was founded 2012-08-28 (9 years ago) There are currently 27 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - Dénes Bodó was added to the PMC on 2021-04-08 - No new committers. Last addition was Mate Juhasz on 2020-03-28. ## Project Activity: - Oozie 5.2.1 was released on 2021-02-26 to address CVE-2020-35451. - We've added Denes to the PMC who was the Release Manager for 5.2.1 ## Community Health: Community activity is low, but there are enough active people on the project to provide oversight. Community metrics were up for two reasons: 1) the baseline is very low 2) the CVE fix and the release release-related generated mails and commits dev@oozie.apache.org had a 27% increase in traffic in the past quarter (148 emails compared to 116) user@oozie.apache.org had a 133% increase in traffic in the past quarter (7 emails compared to 3) 1 issue opened in JIRA, past quarter (-66% change) 1 issue closed in JIRA, past quarter (100% increase) 7 commits in the past quarter (700% increase) 5 code contributors in the past quarter (500% increase) ----------------------------------------- Attachment AR: Report from the Apache OpenWhisk Project [Dave Grove] ## Description: The mission of Apache OpenWhisk is the creation and maintenance of software related to a platform for building serverless applications with functions ## Issues: There are no issues requiring board attention. ## Membership Data: Apache OpenWhisk was founded 2019-07-16 (2 years ago) There are currently 53 committers and 20 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - No new PMC members. Last addition was Rob Allen on 2019-07-16. - No new committers. Last addition was Ning You Gang on 2021-01-19. ## Project Activity: The project released new versions of the OpenWhisk CLI and of our go-based "actionloop" runtimes for Go, PHP, Rust, Ruby, Python, and Java. This was mainly driven by updating these components to be based on Go 1.15 and thus continuing to receive security updates from the upstream GoLang project. Active development in the core repository continued to be focused on the new scheduler implementation. We also added a new runtime for JavaScript based on Deno to complement our existing Node.js based runtime for JavaScript. We have begun discussion of making our second unified release that bundles together compatible versions of all 22 separately released OpenWhisk components. We would like to establish a 6 month cadence for making these unified releases (May & November of each year). The first unified release, 20.11 was made at the end of November 2020. Recent releases: + openwhisk-runtime-java-1.16.0 was released on 2021-04-16. + openwhisk-runtime-python-1.16.0 was released on 2021-04-16. + openwhisk-runtime-ruby-1.16.0 was released on 2021-04-16. + openwhisk-runtime-rust-1.2.0 was released on 2021-04-16. + openwhisk-cli-1.2.0 was released on 2021-04-01. + openwhisk-wskdeploy-1.2.0 was released on 2021-03-24. + openwhisk-client-go-1.2.0 was released on 2021-03-15. + openwhisk-runtime-php-1.16.0 was released on 2021-02-25. + openwhisk-runtime-go-1.17.0 was released on 2021-02-12. ## Community Health: Overall the community was active this quarter; development and discussion picked up in mid-January after a very quiet December and has continued at a healthy pace since then. There continues to be active technical discussion via GitHub issues. The bulk of user support happens via our Slack, but also spills into GitHub issues and Stackoverflow. ----------------------------------------- Attachment AS: Report from the Apache Ozone Project [Sammi Chen] ## Description Apache Ozone is a scalable, redundant, and distributed object and file store, designed to scale to billions of objects/files and run on clusters of thousands of nodes. Ozone supports S3 compatible object APIs as well as a Hadoop Compatible File System implementation. ## Issues None. ## Membership Data - Apache Ozone was founded 2020-10-21. - There are currently 50 comitters and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. - In the last quarter, Matthew Sharp was added as PMC and committer on 2021-04-06. Rui Wang was added as committer on 2021-02-12. Glen Geng was added as committer on 2021-02-12. ## Project Activity: - FS Namesystem optimization is under development, close to ready. - SCM HA has finished Phase 3.0 development and started the Phase 4.0 tasks, including snapshot and dynamic membership change. SCH HA branch is merged back to master. - S3 ACL feature development is finished. Native ACL is improved. - Recon stability is improved. - Security is enhanced. - Non-rolling upgrade design and development are smoothly ongoing. - New feature Multi-Tenant support design draft is under review and POC is ongoing. - New feature Container Balancer design document is ready and passed the community review. Development is ongoing. - Community kicked off new feature Erasure-Coding support design discussion. - A lot of bugs are fixed to improve Ozone's whole stability and performance. - 1.1.0 is released. ## Releases: - 1.0.0 was released on 2020-09-02. - 1.1.0 was released on 2021-04-20. ## Community Health: Last board report was sent on Feb 9th. In the past quarter, - dev@ozone.apache.org had 235 emails (+72% change). - issues@ozone.apache.org had 5549 emails(-19% change). - 328 issues resolved in JIRA in the past quarter (-9% change). - 392 issues opened in JIRA in the past quarter (+1% change). - 11 new contributors joined the community in the past quarter. Now it's totally 115 contributors(Last report is 104). ----------------------------------------- Attachment AT: Report from the Apache Perl Project [Steve Hay] ## Description: The mission of Perl is the creation and maintenance of software related to Dynamic websites using Perl ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Perl was founded 2000-03-10 (21 years ago) There are currently 21 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Steve Hay on 2012-03-01. - No new committers were added. Last addition was Jan Kaluza in April 2013. ## Project Activity: The last release was mod_perl-2.0.11 on 2019-10-05. There was some activity surrounding a build breakage in the upcoming perl-5.34.0, for which we now have a fix, to be released in mod_perl-2.0.12 soon. There was further activity discussing the future of mod_perl, following a PMC roll call with a low response. ## Community Health: The mod_perl users list also joined the discussion on the future of mod_perl, with questions about mod_perl alternatives. It is clear that whilst there are many more modern alternatives available, none quite match the power and flexibility of mod_perl. Several users stepped up to express a willingness to serve on the PMC if necessary to keep the project alive, but none are yet committers. It is good to hear from people who are enthusiastic about the project and its survival, and we hope to encourage more code contributions in order to identify possible future committers and ultimately PMC members. Only 4 of the 11 PMC members responded positively to the roll call in March [1] (myself, Adam Prime, Fred Moyer and Philippe Chiasson). In an earlier roll in February [2], Philip M. Gollucci and Perrin Harkins both responded to say that they can no longer provide oversight. [1] https://s.apache.org/ua3cg [2] https://s.apache.org/v76rf However, given that https://www.apache.org/dev/pmc.html#membersleave says, "It is not a problem to retain members of the PMC who have become inactive, and it can make it easier for them to stay in touch with the project if they choose to become active again," I do not feel that it is necessary or useful to remove those that didn't respond from the PMC roster. ----------------------------------------- Attachment AU: Report from the Apache Phoenix Project [Ankit Singhal] ## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (7 years ago) There are currently 54 committers and 34 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - Xinyi Yan was added to the PMC on 2021-03-31 - No new committers. Last addition was Viraj Jasani on 2021-02-06. ## Project Activity: * Apache Phoenix had its last release 5.1.1 on 2021-03-25, And two other key releases 5.1.0 (on 2021-02-10) and 4.16.0(on 2021-02-24) in the last quarter * There is a growing consensus on dropping support for EOL HBase 1.x runtime which will save some developer's efforts on backporting features to multiple branches that are based on different HBase and Java runtime. * Discussion on splitting our core module into server and client module to avoid conflicting with the libraries in runtimes that are not consistent at server and client. * Working on patch release to fix some nitty bugs of 4.16.0. * Total of 3 Phoenix Tech Talk events were held in the last quarter, we extend our thanks to all who have sincerely arranged the event and actively participated in the talks. ## Community Health: * Community activities got cool down after the enormous work done initially for the two major releases. * There is an increase in traffic on the user mailing list(+225%) owing some to tech talk discussions but traffic on the dev/issues mailing list(-50%) and the number of PRs/commit(-50%) has declined in this quarter as compared to our previous busy quarter * we closed/reviewed almost all the PRs opened(96/102) ----------------------------------------- Attachment AV: Report from the Apache POI Project [Dominik Stadler] Report from the Apache POI committee [Dominik Stadler] ## Description: - Apache POI is a Java library for reading and writing Microsoft Office file formats The Apache POI PMC also handles bugfixes for the XMLBeans project: XMLBeans is a tool that allows you to map XML files to generated Java classes via XML Schema definitions. ## Issues: - There are no issues requiring board attention at this time ## Membership Data: Apache POI was founded 2007-05-16 (14 years ago) There are currently 41 committers and 34 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 Marius Volkhart on 2020-12-27. - No new committers. Last addition was Marius Volkhart on 2020-12-19. ## Project Activity: - The work on some fixes after Apache POI 5.0.0 was followed by working on switching the buildsystem from Apache Ant to Gradle in order to remove the need for Ant and Maven (for SonarQube runs) in the future. - Also logging was reworked from a self-built implementation to using Log4j. Some smaller adjustments to various log-lines may still be needed to not cause many log-lines with the default setup. - A release is planned soon to provide all these and a number of smaller fixes that popped up after the 5.0.0 release. - XMLBeans 5.0.0 was released with some follow-up work after 4.0.0, again marked as major release because the structure of produced code was changed some more after feedback from other users based on the 4.0.0 release. ## Project Release Activity: XMLBeans-5.0.0 was released on 2021-03-14. 5.0.0 was released on 2021-01-19. XMLBeans-4.0.0 was released on 2020-10-15. ## Community Health: - Some Discussion about changes related to Apache POI 5.0.0 and XMLBeans 4.0.0, fortunately mostly caused by mixed up jars which can be fixed by the reporters themselves. - There are questions about features/behaviour which indicates that Apache POI is used by a considerable number of people. Questions via email or on Stackoverflow usually get answers quickly. - We have a fairly constant small number of active committers currently. However we are always looking at ways to broaden the developer base as the code-base is large and so some areas are currently not maintained much at all. - Number of bugs increased but not drastically, there is a constant stream of reports/bugs/patches, but it seems the committers could not spend too much time on those this time. ### XMLBeans - A few bugs were reported by people using XMLBeans directly after they upgraded to 4.0.0, it seems there are a core set of users of it besides Apache POI itself. - Bug influx for XMLBeans is very low in general because it is a stable project in maintenance-mode. ## Bugzilla Statistics: ### Apache POI - 584 bugs are open overall (+9) - Having 158 enhancements (+-0) - Thus having 426 actual bugs (+9) - 103 of these are waiting for feedback (+4) - Thus having 323 actual workable bugs (+5) - 4 of the workable bugs have patches available (+1) - Distribution of workable bugs across components: {XSSF=90, HSSF=82, SS Common=42, HWPF=36, XWPF=21, POI Overall=11, SXSSF=11, XSLF=11, POIFS=5, HSMF=4, OPC=4, HPSF=3, HPBF=1, HSLF=1, SL Common=1} ### Apache XMLBeans - 175 open issues (-1) - Bug 134 (+3) - Improvement 22 (-1) - New Feature 17 (-2) - Wish 2 (-1) ----------------------------------------- Attachment AW: Report from the Apache Qpid Project [Robbie Gemmell] Apache Qpid is a project focused on creating software based on the Advanced Message Queuing Protocol (AMQP), currently providing a protocol engine library, message brokers written in C++ and Java, a message router, and client libraries for C, C++, Go, Java/JMS, Python, and Ruby. # Releases: - Qpid Dispatch 1.15.0 was released on 11th February 2021. - Qpid Broker-J 8.0.4 was released on 18th February 2021. - Qpid Broker-J 7.1.12 was released on 18th February 2021. - Qpid JMS 0.57.0 was released on 22nd March 2021. - Qpid Proton 0.34.0 was released on 12th April 2021. - Qpid JMS 0.58.0 was released on 13th April 2021. - Qpid ProtonJ2 1.0.0-M1 was released on 11th May 2021. # Community: - The main user and developer mailing lists continue to be active and JIRAs are being raised and addressed in line with prior activity levels. - There were no new PMC member additions in this quarter. The most recent new PMC member is Jiri Danek, added on 11th May 2020. - There were no new committer additions in this quarter. The most recent new committer is Ben Hardesty, added on 20th Sept 2019. # Development: - Work on changes for Proton 0.35.0 are getting under way after 0.34.0 having been released. As well as typical bug fixes and improvements, the expected changes include removing Python 2 support and C++ 03 support. - An Outreachy project was submitted for adding distributed tracing support for Protons C++ binding. Several students showed initial interest, with one going on to contribute some fixes and improvements for other areas of the binding to gain experience and then applying for the internship itself. - A student participating in the Red Hat Open Source Contest is working on updating the Proton Python binding to use CFFI instead of SWIG for its Proton-C integration code, aiming for various usability etc improvements. - Work progressed on a new ProtonJ2 protocol engine with an imperative API client built upon it. An initial milestone release was made to allow for initial usage and feedback toward additional changes. - Work on a Dispatch router 1.16.0 release is nearing completion, with an initial candidate now under vote. The release contains many bug fixes and improvements to the routers new protocol adapters, and also many changes around improved test stability. - The AMQP 1.0 JMS client had 0.57.0 and 0.58.0 bug fix releases. Work continues on more fixes and improvements as encountered. Discussing was also held on doing a 1.0.0 release requiring Java 11+ in the near future. - Qpid Broker-J had 7.1.12 and 8.0.4 releases containing various bug fixes and improvements, with work continuing on more 7.1.x and 8.0.x releases as items arise. - We transitioned our git repositories to use 'main' as their default branch name, liaising with Infra to make use of the GitHub rename tooling to do so and achieving a slightly nicer result versus pushing a new branch. # Issues: There are no Board-level issues at this time. ----------------------------------------- Attachment AX: Report from the Apache Ranger Project [Selvamohan Neethiraj] ## Description: - Apache Ranger is a framework to enable, monitor and manage comprehensive data security across the Hadoop platform ## Issues: - There are no issues requiring board attention at this time ## Activity: - Community is working on a minor release of 2.2.0 with some of the bugfixes - Community is focused on enhancements and fixes for 3.0.0 release - Dynamic Config of Solr audit based on number of solr nodes - Ranger UI Improvements on Audit Filter Feature - Improve Docker based setup ## Health report: - The community is overall healthy. - Community is working on many library upgrades (Apache Tomcat, Netty, libthrift, lib4j-core, api-i18n) for upcoming 2.2.0 release. ## PMC changes: - Currently 20 PMC members - No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18. ## Committer base changes: - Currently 30 committers - Dhaval Shah was added as committer on 2021-01-20 ## Releases: - Apache Ranger 2.1.0 was released on 2020-09-03. - Apache Ranger 2.0.0 was released on 2019-08-07. - Apache Ranger 1.2.0 was released on 2018-10-04. ## Mailing list activity: - Regular activity continues. - dev@ranger.apache.org: - 833 emails sent to list in the last 3 months (+15%) - user@ranger.apache.org: - 6 emails sent to list in the last 3 months (-87%) ## JIRA activity: - 15 JIRA tickets created in the last 3 months (-85%) - 15 JIRA tickets closed/resolved in the last 3 months (-73%) ## Commit activity: - 145 commits in the last 3 months (-4%) - 16 active code contributors in the last 3 months (-15%) ----------------------------------------- Attachment AY: Report from the Apache Ratis Project [Tsz-wo Sze] ## Description: Apache Ratis is a highly customizable Java library implementing the RAFT consensus protocol. It supports pluggable state machines, a pluggable transport layer and a pluggable RAFT log. Ratis also improves the original RAFT protocol to support data intensive applications. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Ratis was founded 2021-02-17 (3 months ago) There are currently 27 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members (project graduated recently). - Attila Doroszlai was added as committer on 2021-04-26 ## Project Activity: We currently focus on bug fix and performance improvement. The previous 2.0.0 release was released on 2021-03-25. ## Community Health: The project is healthy. There is not much activity in this quarter compared with the last quarter. We worked 2.0.0 release in the last quarter. We focus on bug fix and performance improvement in this quarter. ----------------------------------------- Attachment AZ: Report from the Apache REEF Project [Sergiy Matusevych] ## Description: Apache REEF, or Retainable Evaluator Execution Framework, is a library for developing portable applications for cluster resource managers such as Apache Hadoop YARN or Apache Mesos. For example, Microsoft Azure Stream Analytics is built on REEF and Hadoop. ## Issues: We've just started the discussion about the future of the project. After finishing the long-term release 0.16.1, we will hold a vote to elect a new PMC Chair, and/or start the process of graceful retirement of the project and moving it to the attic. ## Membership Data: We have not had new PMC members or committers since 2018. Our community currently has 35 committers and 22 PMC members. Last PMC member joined was Doug Service on 2017-09-28. Last committer joined was Scott Inglis on 2018-09-27. ## Project Activity: Last quarter have been quite slow for REEF; we've got only two issues opened and received only one PR. We are in the process of signing and issuing the long-term stable release 0.16.1. Following the release, we will hold a vote and make a decision about the future of the project. If we have enough volunteers to lead the effort, we will start a large experimental release of REEF 0.17 that will include a new elastic group communication functionality (currently in a pull request, approved for merge immediately after the 0.16.1 release). Otherwise, we'll consider retiring the project and moving it to the attic. Other than that, we don't plan any major changes in the API or the functionality and will focus on maintaining the 0.16.1 branch. ## Community Health: The project is stable, but the user and developer engagement has been quite low lately. There was only one new PR and two issues opened or closed this quarter. We've just started the discussion about the project's future on the mailing list. Either way, we are finishing our work on publishing the long-term stable release 0.16.1 and will vote on the new release in May 2021. ----------------------------------------- Attachment BA: Report from the Apache River Project [Roy T. Fielding] ## Description: Apache River creates and maintains software related to the Jini service-oriented architecture. ## Issues: There are no new issues requiring board attention. Roy will continue as chair pro tem until the PMC nominates a new chair. ## Membership Data: Apache River was founded 2011-01-18 (10 years ago). There are currently 9 committers and 5 PMC members in this project. The Committer-to-PMC ratio is 9:5. Community changes, past quarter: - The old PMC, consisting mostly of pre-Apache contributors and mentors from the incubator podling, has been replaced with the active committers willing to continue oversight. - Patricia Shanahan, Bryan Thompson, and Dan Rollo continue as PMC members. - Roy T. Fielding was added to the PMC during the April board meeting. - Dennis Reedy was added to the PMC on 2021-04-30 - Phillip Rhodes, Jeremy R. Easton-Marks, Norman Kabir, and Michael Sobolewski were added as committers on 2021-05-10 ## Project Activity: Activity is waiting upon the project reboot being complete, which should be within the next week (before the board meeting). - River-3.0.0 was released on 2016-10-06. - river-jtsk-2.2.3 was released on 2016-02-21. - river-examples-1.0 was released on 2015-08-10. ## Community Health: Nothing to report on this month, but it should be the highlight of next month's report. ----------------------------------------- Attachment BB: Report from the Apache RocketMQ Project [Xiaorui Wang] ----------------------------------------- Attachment BC: Report from the Apache Roller Project [David M. Johnson] ## Description: Apache Roller is a full-featured, Java-based blog server that works well on Tomcat and MySQL, and is known to run on other Java servers and relational databases. The ASF blog site at blogs.apache.org runs on Roller 6.0.0 Tomcat and MySQL. ## Issues: No issues require board attention at this time. ## Membership Data: Apache Roller was founded 2007-02-21 (14 years ago) There are currently 11 committers and 6 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Swapnil Mane on 2020-05-24. - No new committers. Last addition was Michael Bien on 2020-08-04. ## Project Activity: The community worked on upgrades to maven dependencies, fixing integration tests and fixing issues identified by sonarqube. ## Community Health: The Roller community is small and relatively inactive but healthy and continuing to add new features, enhancements and bug fixes to Roller. ----------------------------------------- Attachment BD: Report from the Apache Santuario Project [Colm O hEigeartaigh] ## Description: The mission of Santuario is the creation and maintenance of software related to XML Security in Java and C++ ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Santuario was founded 2006-06-27 (15 years ago) There are currently 17 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - No new PMC members. Last addition was Daniel Kulp on 2018-10-01. - No new committers. Last addition was Daniel Kulp on 2018-10-01. ## Project Activity: There was one new release over the last quarter - Apache Santuario - XML Security for Java 2.2.2. This was a bug-fix release. Apart from this it was a quiet quarter. ## Community Health: Apache Santuario is a mature and stable project that has reached a point where not too many fixes are required, as it is a set of implementations of some specifications that are quite old now. It is actively managed by the PMC. ----------------------------------------- Attachment BE: Report from the Apache Serf Project [Justin Erenkrantz] ## Description: The mission of the Apache Serf project is creating and maintaining of software related to HTTP and associated protocols. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Serf was founded 2015-08-18 (6 years ago) There are currently 13 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members. Last addition was Branko Čibej on 2018-09-12. - No new committers. Last addition was Evgeny Kotkov on 2017-04-13. ## Project Activity: All quiet this quarter with no meaningful activity on the mailing lists. (There was a slew of JIRAs that were created that were spam and deleted by contributors in a timely manner.) ## Community Health: In the prior quarter, we had discussed whether we should cut a 1.4.x release, but the timing didn't work out given downstream release cadences (Debian and FreeBSD) and the ability of those folks to integrate new versions into their respective release cycles after they entered code freezes. Those distributions incorporated patches that are in our tree, but are unreleased in a formal version. So, there wasn't a huge drive to cut a formal release. Repeating from my earlier report: while relatively quiet, I do believe that there exists enough of a community where we could cut a new Serf release with a quorum of PMC/committers. If a quorum isn't reached and a release can't be cut, we will then need to have a conversation then about the community. However, I remain optimistic. ----------------------------------------- Attachment BF: Report from the Apache ServiceComb Project [Willem Ning Jiang] ## Description: The mission of Apache ServiceComb is the creation and maintenance of software related to a microservice framework that provides a set of tools and components to make development and deployment of cloud applications easier. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache ServiceComb was founded 2018-10-17 (3 years ago) There are currently 26 committers and 20 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was MabinGo on 2019-10-09. - Jianwen Luo was added as committer on 2021-03-03 ## Project Activity: There are some new release of Java Chassis. ServiceComb Java Chassis 2.2.0 was released on 2021-03-02. ServiceComb-Kie was released on 2021-02-23. ServiceComb Java Chassis 2.1.5 was released on 2021-01-20. ## Community Health: Current ServiceComb Java-Chassis is in active development states, but some other sub-projects are in maintenance states. The email of dev traffic has 25% increase. The code contributors in the past quarter has 11% increase. There are some decrease (11%,15%) on the commits, PRs and issues. ----------------------------------------- Attachment BG: Report from the Apache ShardingSphere Project [Liang Zhang] ## Description: The mission of Apache ShardingSphere is the creation and maintenance of software related to a database clustering system providing data sharding, distributed transactions, and distributed database management ## Issues: No ## Membership Data: Apache ShardingSphere was founded 2020-04-15 (a year ago) There are currently 32 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Kimm King on 2020-06-26. - No new committers. Last addition was Lu Qiu on 2021-01-02. ## Project Activity: Software development activity: - We prepared to release 5.0.0-beta version. - We worked with the OpenGauss community to help them adopt the 5.0.0-alpha version version. Meetups and Conferences: - One PMC member attended DataFun Summit 2021, giving one talks on Apache ShardingSphere. - One PMC member had an interview with OpenTecr which talking about how to grow open source community. - Two committers submmit CFP for ApacheCon Asia 2021 about Apache ShardingSphere. ## Community Health: Overall community health is good. The version of 5.x is more and more stable. We are prepare to release soon after the API minor changes. ----------------------------------------- Attachment BH: Report from the Apache SIS Project [Martin Desruisseaux] ## Description: The mission of Apache SIS is the creation and maintenance of software providing data structures for developing geospatial applications compliant with the model of OGC/ISO international standards. ## Issues: See "Community health". ## Membership Data: Apache SIS was founded 2012-09-19 (9 years ago) There are currently 22 committers and 20 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 Johann Sorel on 2017-09-07. - No new committers. Last addition was Alexís Manin on 2019-07-05. ## Project Activity: A join ASF - OSGeo - OGC (Open Geospatial Consortium) code sprint was held in February 17th to 19th. The code sprint results have been summarized in an engineering report [1]. Our main activity has not been on Apache SIS directly, but rather in interoperability with the UCAR (University Corporation for Atmospheric Research) library via the GeoAPI interfaces [2]. Web site migration to a new Content Management System (CMS) is in progress [3], thanks to Bruno P. Kinoshita help. Last release was 1.5 years ago. Release was blocked by a large code review, which is finally in progress [4]. I have good hope that we can finally merge to master and make a release in the next few months. OGC is supervising sponsored developments with various participants this summer. Contributors to SIS (Geomatys) got contract for two areas: Cloud Optimized GeoTIFF reader in Apache SIS (for testing the OGC specification with an implementation different than the current one), and Moving Features. More details are in the mailing list [5]. [1] https://docs.ogc.org/per/21-008.html [2] https://github.com/Unidata/geoapi-netcdf-java [3] https://github.com/apache/sis-site [4] https://github.com/Geomatys/sis/compare/geoapi-4.0...refactor/filters [5] https://s.apache.org/2kvs0 ## Community Health: There is a slight increase in contribution diversity with activity spread in different branches, but this activity does not show up on master branch yet. While the PMC contains 20 PMC members, most of them are quiet for a few years. I saw that the River project recently had a roll call for moving inactive PCM members to emeritus status. Should SIS do the same? ----------------------------------------- Attachment BI: Report from the Apache Solr Project [Jan Høydahl] ## Description: Solr is a highly scalable search server based on Apache Lucene. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Solr TLP was founded 2021-02-17. However Solr has existed since 2006-01-17 as a Lucene subproject. There are currently 87 committers and 61 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past month: - (no changes) ## Project Activity: Work is ongoing on the solr build system to consume Lucene as a library in a better way than relying on nightly SNAPSHOT. Also other blockers that must be done before a 9.0 release is being discussed and worked on. The Solr and Lucene projects plan to do a joint v8.9 release before 9.0. Releases (since April report): - solr-operator-0.3.0 was released on 2021-04-29 ## Community Health: It's still hard to compare various community metrics to the joint history with Lucene. Mail traffic on dev@solr is around 40-50 per week, a slight increase since April. Mails from JIRA and GitHub PRs are around 250 per week, same as last month. The users list is steady going at around 60 per week. While we in our April report had 75 GitHub PRs registered for solr, there are now 120, an increase of 45 last month. Note that PR and commit activity related to 8.x backports still ends up in Lucene lists and statistics. ----------------------------------------- Attachment BJ: Report from the Apache Spark Project [Matei Alexandru Zaharia] Description: Apache Spark is a fast and general engine for large-scale data processing. It offers high-level APIs in Java, Scala, Python, R and SQL as well as a rich set of libraries including stream processing, machine learning, and graph analytics. Issues for the board: - None Project status: - We released Apache Spark 3.1.1, a major update release for the 3.x branch, on March 2nd. This release includes updates to improve Python usability and error messages, ANSI SQL support, the streaming UI, and support for running Apache Spark on Kubernetes, which is now marked GA. Overall, the release includes about 1500 patches. - We are voting on an Apache Spark 2.4.8 bug fix release with for the Spark 2.x line. This may be the last release on 2.x. - We added six new committers in the past three months: Atilla Zsolt Piros, Gabor Somogyi, Kent Yao, Maciej Szymkiewicz, Max Gekk, and Yi Wu. - Several SPIPs (major project improvement proposals) were voted on and accepted, including adding a Function Catalog in Spark SQL and adding a Pandas API layer for PySpark based on the Koalas project. We've also started an effort to standardize error message reporting in Apache Spark (https://spark.apache.org/error-message-guidelines.html) so that messages are easier to understand and users can quickly figure out how to fix them. Trademarks: - The PMC is investigating a potential trademark issue with another open source project. Latest releases: - Spark 3.1.1 was released on March 2nd, 2021. - Spark 3.0.2 was released on February 19th, 2021. - Spark 2.4.7 was released on September 12th, 2020. Committers and PMC: - The latest committers were added on March 18th, 2021 (Atilla Zsolt Piros, Gabor Somogyi, Kent Yao, Maciej Szymkiewicz, Max Gekk, and Yi Wu). - The latest PMC member was added on Sept 4th, 2019 (Dongjoon Hyun). The PMC has been discussing some new PMC candidates. ----------------------------------------- Attachment BK: Report from the Apache Sqoop Project [Venkat Ranganathan] ## Description: The mission of Sqoop is the creation and maintenance of software related to Bulk Data Transfer for Apache Hadoop and Structured Datastores ## Issues: There are no issues requiring board attention at this time ## Membership Data: Apache Sqoop was founded 2012-03-20 (9 years ago) There are currently 32 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Vasas Szabolcs on 2018-11-05. - No new committers. Last addition was Fero Szabo on 2018-11-08. ## Project Activity: Recent releases: 1.4.7 was released on 2018-01-24. 1.99.7 was released on 2016-08-08. 1.99.6 was released on 2015-05-04. ## Community Health: ev@sqoop.apache.org had a 533% increase in traffic in the past quarter (38 emails compared to 6) 1 issue opened in JIRA, past quarter (-66% change) 0 issues closed in JIRA, past quarter (-100% change) 0 commits in the past quarter (no change) 0 code contributors in the past quarter (no change) 3 PRs opened on GitHub, past quarter (200% increase) 3 PRs closed on GitHub, past quarter (300% increase) ----------------------------------------- Attachment BL: Report from the Apache Subversion Project [Nathan Hartman] ## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (21 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (11 years ago). There are currently 88 committers and 49 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. No new committers have been added since the last report. Our most recently added committer, Daniel Sahlberg (dsahlberg@) received a commit bit in December 2020. No new PMC members have been added since the last report. Our most recently added PMC member, Jun Omae (jun66j5@) joined the PMC in May 2020. ## Project Activity: This quarter, two exciting client-side performance improvements landed in trunk. The first speeds up 'svn checkout' and 'svn update' operations when fetching large directories from the server while simultaneously solving an annoying issue with server-side timeouts. This is achieved by combining what were previously separate steps that at times held the server connection open without reading from it, leading to the timeouts. The new process, which could be called "streamy checkouts," results in a noticeably snappier user experience. The second is a new "thread pool" API to leverage modern multi-core systems. The challenge is order of operations: certain steps must run in a deterministic sequence, contrary to the asynchronous nature of thread pools. The new APIs address this by running part of the work in multiple threads, after which a follow-up runs in the same order as sequential code. Currently only 'svn status' uses the new APIs, but other features could be made to take advantage of them in the future. These new features are expected to eventually ship in a future 1.15 release line, which has not been scheduled yet. Other improvements and bug fixes developed during this quarter include improved Python 2 and Python 3 compatibility, a workaround for Python issue #40312, bug fixes for SWIG bindings, contributed scripts, string encoding handling, i18n regressions, out-of-tree builds, building Subversion on Windows, improved handling of foreign repository merges, new regression tests, and other minor improvements. ## Community Health: Activity seems to come in waves, as our volunteers desire and are able to invest their time and effort into Subversion. Our last quarter of 2020 was our quietest ever, but it was followed by an action-packed first quarter of 2021. In comparison to it, this second quarter of 2021 felt slower, but was nevertheless quite eventful. It began with the releases of 1.10.7 and 1.14.1, the culmination of the previous quarter's work, and was soon followed by the new feature development and other improvements and bug fixes mentioned earlier. Recently we had a discussion about our community health. It began when one of our volunteers noticed that an easy-to-make but serious C programming mistake was committed and went unnoticed for 11 days. This error affected only a new regression test that was added in the same commit; it has never been included in a release and was quickly fixed once it was pointed out, but it did prompt the discussion. Various aspects of community health were discussed and ideas proposed. It does not escape us that we have difficulty enticing volunteers to take on demanding tasks such as release management. The final word seems to be that to ensure long-term longevity, we need to attract new developers to the project. Notwithstanding the above discussion and the challenges that we do face, it is this chair's feeling that our project is more active and our community health is better than it may at times feel. It may look dismal when compared to the heyday of our early years, but considering that this quarter, we had 100 commits, more than one for each day, with the vast majority of these being quite substantive, not "easy" things like typo fixes; 100% of questions posted to our users@ mailing list received responses; new features were developed; bugs were fixed; when compared to other volunteer-driven projects of similar age and maturity, some of which go weeks or months without a commit, our community health looks far more encouraging. ----------------------------------------- Attachment BM: Report from the Apache Superset Project [Maxime Beauchemin] ## Description: The mission of Apache Superset is the creation and maintenance of software related to data exploration, analysis, visualization, and dashboarding ## Issues: Nothing to report, things are going well ## Membership Data: Apache Superset was founded 2020-11-17 (6 months ago) There are currently 44 committers and 27 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Amit Miran was added to the PMC on 2021-02-23 - Junlin Chen was added to the PMC on 2021-03-25 - Amit Miran was added as committer on 2021-02-11 - Kamil Gabryjelski was added as committer on 2021-03-31 - Phillip Kelley-Dotson was added as committer on 2021-02-19 ## Project Activity: 1.1 was released, see the notes [here](https://github.com/apache/superset/tree/master/RELEASING/release-notes-1-1) Superset was voted #3 most popular data open source project [here](https://petesoder.medium.com/what-are-the-most-popular-oss-data-projects-of-2021-84ef021bb5a2) Also worth mentioning. Two Sigma Ventures created an Open Source Index using a unique methodology to rank projects. Superset came through as #29 of most "popular and fast growing" projects out there. [Find more details here](https://twosigmaventures.com/open-source-index/) There was a issue-cleaning bash that was well attended. Goal was to to a bit of a spring cleanup and improve labeling / triage for more sustainable collaboration. We're looking to organize a cosmetic/bug bash in the next few weeks. ## Community Health: Great increased attention on the project bringing many newcomers as reflected per GitHub stars bumps. Committers/contributors meetups seem to be growing to be less important as we increase the collaboration async on GitHub discussions and issues. - 38.4k stars on GitHub, nice bumps from the DataCouncil blog post mentioned above - 1234 commits in the past quarter (-8% change) - 100 code contributors in the past quarter (26% increase) - 846 PRs opened on GitHub, past quarter (6% increase) - 799 PRs closed on GitHub, past quarter (1% increase) - 567 issues opened on GitHub, past quarter (1% increase) - 501 issues closed on GitHub, past quarter (63% increase) ----------------------------------------- Attachment BN: Report from the Apache Syncope Project [Francesco Chicchiriccò] ## Description: The mission of Syncope is the creation and maintenance of software related to Managing digital identities in enterprise environments ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Syncope was founded 2012-11-21 (8 years ago) There are currently 24 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Matteo Alessandroni on 2017-12-22. - No new committers. Last addition was Misagh Moayyed on 2019-10-04. ## Project Activity: We finalized 2.1.9 (with bugfixes, minor improvements and features). There are still a few steps to be performed before being able to cut 3.0.0-M1, but work is still progressing. We remark that the work towards Syncope 3.0.0 is leading to cooperation with Open Source projects external to the ASF as Apereo CAS and Pac4j. Some work to integrate Travis CI with GitHub Actions was performed, to cover all possible unit and integration tests within all supported environments. Recent releases: * 2.1.9 was released on 2021-04-17. ## Community Health: Discussions about new features and improvements keep appearing and being followed up in dev@. Newcomers approach user@ and are getting supported by the community. GitHub's Pull Requests are now the main contribution mean, from both first-time contributors and committers: this consideration was driving the effort to improve CI integration. ----------------------------------------- Attachment BO: Report from the Apache SystemDS Project [Matthias Boehm] ## Description: Apache SystemDS is a machine learning (ML) system for the end-to-end data science lifecycle from data preparation and cleaning, over efficient ML model training, to scoring and debugging. ML algorithms or pipelines are specified in a high-level language with R-like syntax, or related Python and Java APIs, and the system automatically generates hybrid runtime plans of local, in-memory operations and distributed operations on Apache Spark. ## Project Status: - We are working towards the SystemDS 2.1 release (planned for June), which will be the last release on Spark 2.x, Hadoop 2.x, and Java 8 (before switching to Spark 3, Hadoop 3, and Java 11). ## Membership Data: - Apache SystemDS was founded 2017-05-16 (incubator process entered 2015-11-02) - Last PMC members added 2020-10-07 (Arnab Phani, Sebastian Baunsgaard) - Last committer added 2021-04-10 (Olga Ovcharenko) - There are currently 33 committers and 24 PMC members in the project. ## Activity and Health: - Code activity is healthy with 190 commits (+44%) in the last 3 months. - Community growth is healthy with 1 new committer and 26 active contributors (+30%) in the last 3 months - Communication is healthy, mailing list activity is improving, additional work better documentation. ## Releases: - Apache SystemDS 2.0.0 was released on 2020-10-14. - Apache SystemML 1.2.0 was released on 2018-08-24. ----------------------------------------- Attachment BP: Report from the Apache TomEE Project [David Blevins] ## Description: Apache TomEE delivers enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. ## Health The project is very happy with the progress reported in the last report. Initiatives to release more frequently and add more committers and pmc members have all gone well. Our last release received 7 binding PMC votes and 11 votes overall, which is very good for us as some votes in the past struggled to get 3 binding votes. ## Activity The project flipped priorities on pursing Jakarta EE 8 and Jakarta EE 9 certification and made Jakarta EE 9 the primary focus. The Jakarta EE 9.1 release is completing Monday May 17th on the Eclipse side of the fence and the project very much wanted to be part of the announcements. On this note we'd like to thank Rob Tompkins and the board for accepting Guest membership in the Eclipse Foundation so that we can be listed in on the jakarta.ee website once certified. Other projects at Apache are not restricted and can be listed without Apache being a member of the Working Group. Implementations of the Jakarta EE Platform and Web Profile are treated differently and do need to be members of the Working Group to be on the certification page at jakarta.ee, so we are very grateful to everyone who made that possible. After a considerable amount work, the project was able to pass all test required to claim Jakarta EE 9.1 Web Profile certification. This is a historic milestone as the last certification we were able to achieve was Java EE 6 in 2011, 10 years ago. Apache's Java EE TCK license expired about 2 months before Java EE 7 was released. After access was restored through Jakarta EE, it's been a very long road working through all the tests after not having access for so many years. As of this week there are 16 certified implementations of Jakarta EE and Apache TomEE is the only one to ship the Apache implementations of various Jakarta specifications such as Tomcat, ActiveMQ, OpenJPA, OpenEJB, Johnzon, OpenWebBeans, BVal, Geronimo JavaMail, Geronimo Transactions, Geronimo Connectors, etc. All 15 other implementations use and share more or less the same, usually Eclipse, implementations. This means we have to match the resources of all other Jakarta EE implementations combined. We are very proud we were able to do this and that Apache and Apache TomEE offers true diversity to the ecosystem where it would not otherwise exist. In pursuit of certification there were some backwards incompatible changes made to the released TomEE 8.0.7, which is bytecode transformed into TomEE 9 and the basis of TomEE 9.0.0-M7, which is the officially certified release. Both versions went up for a release vote simultaneously as there is interdependence between them. However, due to the regressions in 8.0.7 the project has opted to not put 8.0.7 on the website and will only be leaving it on the mirror system briefly. The community plans to address all regressions and build failures and release a TomEE 8.0.8 as soon as possible. Other areas of focus likely to surface are improving the website to host the TCK results for each releases and take advantage of the Jakarta EE logo and of course discuss what criteria we think must be met for a TomEE 9.0.0 final release. ## PMC changes: - Currently 12 PMC members. - Last PMC addition Cesar Hernandez on February 10th 2021 ## Committer base changes: - Currently 33 committers. - Last committer added was Richard Zowalla on January 6th 2021 ## Releases: - Apache TomEE 8.0.7 on May 10, 2021 - Apache TomEE 9.0.0-M7 on May 10, 2021 ----------------------------------------- Attachment BQ: Report from the Apache Traffic Control Project [Eric Friedrich] ## Description: The mission of Apache Traffic Control is the creation and maintenance of software related to building, monitoring, configuring, and provisioning a large scale content delivery network (CDN) ## Issues: There are no issues requiring the board's attention. ## Membership Data: Apache Traffic Control was founded 2018-05-15 (3 years ago) There are currently 26 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 1.5:1. Community changes, past quarter: - One new PMC member. Last addition was Brennan Fieck on 2021-02-17. - No new committers. Last addition was Zach Hoffman on 2020-09-03. ## Project Activity: The community completed a minor 5.1 release (March 11, 2021) and a bug fix 5.1.1 release (April 1, 2021). Development is well underway for the 6.0 major release currently targeted to begin release candidates in July. The next release will include the replacement of an unmaintained dependency (Riak NoSQL DB) by Postgres, already a heavily used component of the project. The community also completed the long in-progress conversion of our perl based configuration application into a much more extensible and performant Go based application. In the last 3 months, we registered just under 200 new commits from 25 different contributors, many of which are not yet committers. ## Community Health: In the last 3 months, we added one new PMC member. The community is healthy. Overall the community remains healthy even though the majority of contributions are primarily coming from one company with a small number of contributions coming from others. We continue to see new users join our community and set up Traffic Control, however we still struggle to turn them into contributors. Finally, this is my first board report as PMC Chair. The community sends gratitude to Dave Neuman for guiding Traffic Control through its first three years. ----------------------------------------- Attachment BR: Report from the Apache Turbine Project [Georg Kallidis] ## Description: The mission of Turbine is the creation and maintenance of software related to A Java Servlet Web Application Framework and associated component library ## Issues: The Turbine project has no board-level issues at this time. ## Membership Data: Apache Turbine was founded 2007-05-16 (14 years ago) There are currently 11 committers and 9 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 Jeffery Painter on 2017-11-12. - No new committers were added. The last change to the committer base was the addition of Georg Kallidis (2012-09-19). ## Project Activity: Last released component: - Turbine Parent 8 was released on 2021-04-28. - Last main release was Turbine 5.0 Core on 2019-05-28. - Fulcrum components has seen code activity in bugfixes, tests, security checks, code alignments and dependency updates. ## Community Health: - Turbine project has seen below average levels of activity in the last quarter in dev mailing list and commits. - Activity is primarily in preparation of the upcoming Turbine 5.1 (feature) release, which is expected to be in the next or the following quarter. - Turbine project community shows good readiness in answering questions and fixing any issues. ----------------------------------------- Attachment BS: Report from the Apache Usergrid Project [Michael Russo] ## Description: Usergrid is Backend-as-a-Service (BaaS) composed of an integrated database (Cassandra), a query engine (ElasticSearch), and application layer and client tier with SDKs for developers. ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache Usergrid was founded 2015-08-18 (6 years ago) There are currently 27 committers and 24 PMC members in this project. The Committer-to-PMC ratio is 9:8. Community changes, past quarter: - No new PMC members. Last addition was Mike Dunker on 2016-01-18. - No new committers. Last addition was Keyur Karnik on 2019-03-18. ## Project Activity: - Elasticsearch licensing issues discussed with LEGAL in https://issues.apache.org/jira/browse/LEGAL-571. Recent releases: - 2.1.0 was released on 2016-02-18. - 1.0.2 was released on 2015-07-20. ## Community Health: Growth is flat with no issues reported or fixed in a very long time. A discussion has been started in the dev mailing list about moving Usergrid to the Attic due to lack of contributions and outdated support for Usergrid's dependencies. ----------------------------------------- Attachment BT: Report from the Apache Velocity Project [Nathan Bubna] ## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Velocity was founded 2006-10-24 (15 years ago) There are currently 15 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Michael Osipov on 2017-07-27. - No new committers. Last addition was Thomas Mortagne on 2020-03-09. ## Project Activity: Velocity Engine 2.3 was released on Feb 27. Velocity Tools 3.1 was released on Feb 27. Minimal activity since that time. ## Community Health: The project is highly stable with no notable problems. The ongoing mild problem is low interest in additional investment of energy from existing developers or entice new developers to get involved. ----------------------------------------- Attachment BU: Report from the Apache Whimsy Project [Shane Curcuru] ## Description: The mission of Apache Whimsy is the creation and maintenance of software related to tools that help automate various administrative tasks or information lookup activities ## Issues: None - although in happy news, the PMC and Infra are having productive discussions about turning the Board Agenda tool into an infra-supported resource. ## Membership Data: Apache Whimsy was founded 2015-05-19 (6 years ago) There are currently 12 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 6:5. Community changes, past quarter: - No new PMC members. Last addition was Matt Sicker on 2020-04-11. - No new committers. Last addition was Test Sam Ruby on 2020-06-11. ## Project Activity: sebb continues to ensure services are updated and bugs are fixed. Sam, Greg, Sander and others are making clearly documented progress on a new Board Agenda tool and plans to make it formally supported by Apache Infra, while still allowing PMC volunteers to assist where able. The apache.org website CMS update is being coordinated to ensure that various bits of data used by Whimsy are still accessible/writable. ## Community Health: While overall email and ticket traffic is up, and we are seeing more people ask questions about whimsy, we still have the same few PMC members doing most of the work. ----------------------------------------- Attachment BV: Report from the Apache Xalan Project [Gary D. Gregory] ## Description: Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible Stylesheet Language Transformations) as a compelling paradigm that transforms XML documents, thereby facilitating the exchange, transformation, and presentation of knowledge. The ability to transform XML documents into usable information has great potential to improve the functionality and use of information systems. We intend to build freely available XSLT processing components in order to engender such improvements. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Xalan was founded 2004-09-30 (17 years ago) There are currently 57 committers and 5 PMC members in this project. The Committer-to-PMC ratio is roughly 8:1. Community changes, past quarter: - No new PMC members. Last addition was Bill Blough on 2019-02-19. - No new committers. Last addition was Bill Blough on 2019-03-20. ## Project Activity: Activity is low. We receive a fair amount of spam on the mailing lists which I moderate out. There are some Jiras and need attention. There have been no releases in this reporting period. The C side of Xalan is slightly more active than the inactive Java side this period. There is still interest a large it appears for Xalan, it's just that our side has little availability. ## Community Health: Health is low. While there is some low level activity in Jira, community engagement is low, better on the C side than the Java side it seems. ----------------------------------------- Attachment BW: Report from the Apache Xerces Project [Michael Glavassevich] Xerces-J Some functional and performance testing was done on the XML Schema 1.1 implementation. Results were shared on the mailing list. There was no other development activity over the reporting period. In April, there was another potential security issue that was reported through security@ that requires investigation. We're trying to verify whether this is an issue with an Apache Xerces release or only the JDK fork that the reporter mentioned in their testing. Mailing list traffic has been very low; roughly 15+ posts on the j-dev and j-users lists since the beginning of March 2021. No new releases since the previous report. The latest release is Xerces-J 2.12.1 (January 11th, 2020). Xerces-C Aside from a couple mailing list posts, there's been no activity since the previous report. Mailing list traffic has been very low; roughly 2+ posts on the c-dev and c-users lists since the beginning of March 2021. No new releases since the previous report. The latest release is Xerces-C 3.2.3 (April 10th, 2020). Xerces-P Nothing in particular to report. There was no development activity over the reporting period. XML Commons No activity over the reporting period. Committer / PMC Changes The most recent committers were added in April 2017 (Xerces-C) and May 2017 (Xerces-J). No new PMC members since the last report. The most recent addition to the PMC was in June 2016. No committers have committed changes to SVN or Git since March 2021. ----------------------------------------- Attachment BX: Report from the Apache XML Graphics Project [Clay Leeds] Apache XML Graphics Project Board Report ================================== The Apache XML Graphics Project is responsible for software intended for the creation & maintenance of the conversion of XML formats to graphical output & related software components. ISSUES FOR THE BOARD ===================== No issues at present. ACTIVITY ======== * Apache Batik 1.14 released 2021-01-21 * Apache FOP 2.6 released 2021-01-21 * Apache XML Graphics Commons 2.6 released 2021-01-21 PROJECT HEALTH REPORT ======================= The level of community and developer activity remains at a consistent, moderate, level with respect to the previous reporting period. RECENT PMC CHANGES ================== Currently 11 PMC members. * Simon Steiner was added to the PMC on Tue Jan 19 2016 * Simon ABSOLUTELY ROCKS IT! * Clay Leeds was approved for XML Graphics PMC Chair position on March 26, 2018. Committers ========== Currently 21 committers. * No new committers added in the last 3 months * Last committer added was Matthias Reischenbacher at Wed May 13 2015 Most Recent Releases ==================== * Apache Batik 1.14 was released January 21, 2021 * Apache FOP 2.6 was released January 21, 2021 * Apache XML Graphics Commons 2.6 was released January 21, 2021 = SUB PROJECTS = ================ XML GRAPHICS COMMONS ==================== Community activity was light, although there were a few bugs resolved. New Release? ------------ * Apache XML Graphics Commons 2.6 was released January 21, 2021 Latest Release -------------- XML Graphics Commons 2.6 was released on January 21, 2021 FOP === * Apache FOP 2.6 was released January 21, 2021 Newest Release? --------------- * Support OTF/TTF SVG fonts * Allow overpaint of PDF border * Bug fixes Latest Release -------------- Apache XML Graphics FOP 2.6 was released on January 21, 2021 BATIK ===== * Apache Batik 1.14 was released January 21, 2021 New Release? ------------ Apache XML Graphics Apache Batik 1.14 was released on January 21, 2021 * BATIK-1292: Useless console message "About to transcoder source of type: ..." * BATIK-1297: Dependency Convergence issue with xml-apis Latest Release -------------- Apache XML Graphics Apache Batik 1.14 was released on January 21, 2021 ----------------------------------------- Attachment BY: Report from the Apache Zeppelin Project [Lee Moon Soo] ## Description: - Apache Zeppelin is a collaborative data analytics and visualization tool for general-purpose data processing systems. ## Issues: ## Membership Data: Apache Zeppelin was founded 2016-05-18 (5 years ago) There are currently 22 committers and 11 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Jeff Zhang on 2018-01-25. - No new committers. Last addition was Philipp Dallig on 2020-06-24. ## Project Activity: - We have the first online community meeting in March, 4 people join this meeting and discuss various of things, which is a very successful and excited thing for the zeppelin community, we plan to continue this kind of community meeting in each quarter. ## Community Health: +1 new code contributors since last report. 344 total. Releases: - 0.9.0 was released on Dec 24, 2020 - 0.9.0-preview2 was released on July 27, 2020 - 0.9.0-preview1 was released on March 26, 2020 - 0.8.2 was released on Wed Sep 29 2019 - 0.8.1 was released on Wed Jan 23 2019 - 0.8.0 was released on Wed Jul 18 2018 Mailing list activity: - users@zeppelin.apache.org: - 104 emails sent to list ( 35 in previous quarter) - dev@zeppelin.apache.org: - 688 emails sent to list ( 623 in previous quarter) ------------------------------------------------------ End of minutes for the May 19, 2021 board meeting.