The Apache Software Foundation Board of Directors Meeting Minutes February 19, 2020 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 10:32 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: https://timeanddate.com/s/41zj The meeting was held via teleconference, hosted by the Secretary via Zoom. IRC #asfboard on irc.freenode.net was used for backup purposes. 2. Roll Call Directors Present: Danny Angus Rich Bowen Shane Curcuru Ted Dunning Myrle Krantz Daniel Ruggeri Craig L Russell Roman Shaposhnik Directors Absent: Dave Fisher Executive Officers Present: Sally Khudairi David Nalley Tom Pappas Sam Ruby Matt Sicker Executive Officers Absent: none Guests: Daniel Gruno Furkan Kamaci Gavin McDonald Greg Stein Justin Mclean Kenneth Knowles Patricia Shanahan Sander Striker 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of January 15, 2020 See: board_minutes_2020_01_15.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Craig] The Foundation continues to operate financially conservatively. A new budget proposal is being developed for the next fiscal year. We understand that Sam Ruby intends to step down as President, and is working with David Nalley on a transition plan. The coronavirus has significantly affected all Chinese people, and we hope that they can resolve the issue quickly and resume normal activity. We are working on developing a policy for Conflict of Interest. While we have no current issues, it is expected that foundations like the ASF will enforce a CoI policy. B. President [Sam] We continue to be on track to be on budget, modulo some timing issues of sponsor payments. No officers in operations are reporting issues requiring board attention. I'm continuing to transition responsibilities to the EVP in preparation for my stepping down. I'm open to discussion as to when it would be best to step down - should it be the current board or the next board that names my replacement? My recommendation for my replacement continues to be David Nalley. Should the current board wish to defer this transition to the next board, my plans are to have David effectively acting as the President by the next board meeting, with me supporting him. Additionally, please see Attachments 1 through 9. @David: determine top ten CI issues affecting projects C. Treasurer [Myrle] Operating Cash on January 31st, 2020 was $2,137.8K, which is down $1K from last month’s ending balance (Dec 19) of $1,738.8K. Total Cash as of Jan 31st, 2020 is $3,531.7K (includes the Pineapple, Restricted Donation as well as the Tides Restricted Donations) as compared to $3,3,993.1K on January 31st, 2019, (a decrease of $461.4K year over year). The January 31st 2020 ending Operating cash balance of $2,137.8K represents an Operating cash reserve of 10.1 months based on the “Estimated” FY20 Cash forecast average monthly spending of $249.9K/month. The ASF actual Operating reserve of 10.1 months at the end of January 2020 is a bit ahead the budgeted 8.7 months of reserve for YTD through January 31st 2020. The estimated YE Operating reserve of 10.6 months is ahead of the Budgeted YE reserve of 7.6 months. The ASF Operating reserve is above the ASAE standard average of 6 months of reserve for Non Profits. Reviewing the YTD Cash P&L, total Revenue is behind budget at this point in the Fiscal year by $288.9K (this is partly due to timing of sponsor payments) The open Accounts Receivable is very healthy at $593K, which as of the Jan 20 Fin Close is enough, if it comes in before 4.30.20, to achieve the FY20 Foundation Sponsorship Budget. As compared to FY19, FY20 YTD revenue is ahead by $133.6K primarily due to FY20 Events exceeding Revenue as compared to FY19, YTD. YTD expenses through January 31st, 2020 are under budget by $254.8K, spread across all depts except Conferences. Which we expect to continue as the FY20 comes to an end. Regarding Net Income (NI), YTD FY20 the ASF finished with a negative <$258.6K> NI vs a budgeted negative <$224.5K> NI or $34.1K behind the Budgeted NI for FY20 at this point in the Fiscal year. After being behind Budgeted NI by $117K, last month, with the timing of Sponsor payments, and expenses under budget, we are getting closer to being back on track for FY20 as compared to budget. The cash forecast has been updated, with the information we have at hand, and at this point with about 3 months left in the Fiscal year, we are still on pace to, if everything goes according to the Forecast, possibly exceed our FY20 budgeted NI. We have one slight change to the Monthly Financial Pkg. We have added a tab for each department, that has their Cash basis GL activity for the month, compared to the combined Cash Basis GL detail that had previously been included. We hope that this provides a more efficient view for department budget holders to review the details of their monthly spending. That said, as I have done in previous months, I urge all dept heads to review their depts in the Cash forecast, for the last 3 months of the Fiscal year, and let us know if there is anything that they are aware of that could change the estimates for the remaining 3 months of FY20. This effort will make the Cashforecast a much more accurate management tool for the Foundation. With regard to FY19, we are ahead in revenue, by $133.6K as noted above, but we are also ahead on expenses by $901.1K (due to ACNA19, ACEU19, the Lease web payment which should have taken place in FY19, but did not etc); thus, year over year NI FY20 is behind FY19 by $767.5K. It is estimated that this will even out, to a degree, as the FY20 progresses. Current Balances: Boston Private CDARS Account 2,266,757.51 Citizens Money Market 714,205.22 Citizens Checking 550,057.58 Paypal - ASF 666.57 Total Checking/Savings 3,531,686.88 Jan-20 Budget Variance Income Summary: Public Donations 11,153.89 7,452.19 3,701.70 Sponsorship Program 87,000.00 337,000.00 -250,000.00 Programs Income 0.00 0.00 0.00 Conference/Event Income 70,018.15 0.00 70,018.15 Other Income 0.00 Interest Income 1,667.08 400.00 1,267.08 Total Income 169,839.12 344,852.19 -175,013.07 Expense Summary Infrastructure 127,667.10 85,733.08 41,934.02 Programs Expense 5,012.78 3,333.33 1,679.45 Publicity 20,689.32 21,233.34 -544.02 Brand Management 0.00 8,166.67 -8,166.67 Conferences 0.00 17,250.00 -17,250.00 Travel Assistance Committee 0.00 10,000.00 -10,000.00 Fundraising 11,420.01 16,080.00 -4,659.99 Treasury Services 3,350.00 3,350.00 0.00 General & Administrative 2,639.97 1,915.00 724.97 Diversity and Inclusion 0.00 5,833.33 -5,833.33 Total Expense 170,779.18 172,894.75 -2,115.57 Net Income -940.06 171,957.44 -172,897.50 YTD FY20 Budget Variance Income Summary: Public Donations 91,865.37 124,856.06 -32,990.69 Sponsorship Program 1,056,600.00 1,228,000.00 -171,400.00 Programs Income 14,900.00 14,000.00 900.00 Conference/Event Income 610,161.06 700,000.00 -89,838.94 Other Income 0.00 0.00 Interest Income 8,287.98 3,850.00 4,437.98 Total Income 1,781,814.41 2,070,706.06 -288,891.65 Expense Summary Infrastructure 812,412.73 826,097.75 -13,685.02 Programs Expense 12,420.31 30,000.00 -17,579.69 Publicity 276,066.08 331,180.00 -55,113.92 Brand Management 35,958.09 73,500.00 -37,541.91 Conferences 651,816.47 633,250.00 18,566.47 Travel Assistance Committee 46,058.81 145,000.00 -98,941.19 Fundraising 111,875.59 144,720.00 -32,844.41 Treasury Services 30,150.00 30,150.00 0.00 General & Administrative 33,614.16 28,755.00 4,859.16 Diversity and Inclusion 30,000.00 52,500.00 -22,500.00 Total Expense 2,040,372.24 2,295,152.75 -254,780.51 Net Income -258,557.83 -224,446.69 -34,111.14 D. Secretary [Matt] In January, the secretary received 67 ICLAs, 3 CCLAs, and 4 software grants. E. Executive Vice President [David] Things are largely working as intended. One new thing to the lineup this past month is that we held an operations call. The call went well. Budget ====== Budget process is underway with most operational functions having submitted a proposed budget. In the process,​ we've identified some problems and misallocation of some expenses that may change things. We've additionally begun discussions around treating Conferences and Fundraising as their own distinct lines of business from an accounting perspective so that we have a more clear picture of the efficacy of money spent in those areas. Conferences =========== Conferences currently has 5 events in process and things appear to be well managed. Most exciting though is the Event Playbook - which should help mitigate Single Points of Failure as well as making it easier for folks to participate and help. Travel Assistance ================= TAC successfully concluded a small committer-focused travel sponsorship at FOSDEM. Additionally, they are working on a calendar for future event support as part of the FY21 budget planning process. Infrastructure ============== Infrastructure suffered an outage to a critical service (LDAP) but quickly resolved it. Data Privacy ============ Privacy seems to have reached critical mass to make progress. There are several requests pending that are being worked. Diversity ========= Diversity has made good progress on a number of fronts. The most interesting bit is that our first Outreachy participant has been adding info into the friction log. I hope that in the coming months this is something that we can take time to review and learn from. Survey is in analysis mode and is on track for publication in coming months. F. Vice Chairman [Shane] Assisted Chairman with preparing records and emails relating to our upcoming Annual Member's meeting, where the Membership will elect a new board and potentially new individual Members. Created an automated overview page and other tooling to simplify the meeting process. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Dave] See Attachment 10 B. Apache Legal Affairs Committee [Roman Shaposhnik] See Attachment 11 C. Apache Security Team Project [Mark J. Cox / Ted] See Attachment 12 D. VP of Jakarta EE Relations [Mark Struberg / Myrle] No report was submitted. Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # Cocoon [myrle] # CouchDB [da] # DRAT [myrle] # Giraph [druggeri] # HTTP Server [myrle] # Infrastructure [druggeri] # Logging Services [druggeri] # Open Climate Workbench [da] # SIS [da, druggeri] A. Apache Ambari Project [Jayush Luniya / Shane] No report was submitted. B. Apache Ant Project [Jan Materne / Danny] See Attachment B C. Apache BookKeeper Project [Sijie Guo / Craig] See Attachment C D. Apache Brooklyn Project [Geoff Macartney / Rich] See Attachment D E. Apache Buildr Project [Antoine Toulme / Daniel] See Attachment E F. Apache Cassandra Project [Nate McCall / Roman] See Attachment F G. Apache Clerezza Project [Hasan Hasan / Danny] See Attachment G H. Apache Cocoon Project [Cédric Damioli / Rich] See Attachment H @Rich: pursue report for next month I. Apache Community Development Project [Sharan Foga / Daniel] See Attachment I J. Apache CouchDB Project [Jan Lehnardt / Ted] See Attachment J David mentions that the project can file an issue with INFRA to enable HTML emails per-list. K. Apache Creadur Project [Philipp Ottlinger / Shane] See Attachment K L. Apache DeltaSpike Project [Mark Struberg / Craig] See Attachment L M. Apache DRAT Project [Tom Barber / Myrle] No report was submitted. @Myrle: pursue a report for DRAT N. Apache Drill Project [Charles Givre / Roman] See Attachment N O. Apache Druid Project [Gian Merlino / Dave] See Attachment O P. Apache Empire-db Project [Rainer Döbele / Ted] See Attachment P Q. Apache Flume Project [Ferenc Szabo / Roman] No report was submitted. @Roman: pursue a report for Flume R. Apache Forrest Project [David Crossley / Danny] See Attachment R S. Apache FreeMarker Project [Dániel Dékány / Shane] See Attachment S T. Apache Geode Project [Karen Miller / Rich] See Attachment T U. Apache Giraph Project [Dionysios Logothetis / Myrle] See Attachment U V. Apache Gora Project [Kevin Ratnasekera / Daniel] No report was submitted. @Daniel: pursue a report for Gora W. Apache Groovy Project [Paul King / Dave] See Attachment W X. Apache Hama Project [Chia-Hung Lin / Craig] No report was submitted. @Ted: begin Attic process with Hama Y. Apache Helix Project [Kishore G / Craig] No report was submitted. @Craig: pursue a report for Helix Z. Apache HTTP Server Project [Daniel Gruno / Danny] See Attachment Z AA. Apache HttpComponents Project [Asankha Chamath Perera / Daniel] See Attachment AA AB. Apache Ignite Project [Dmitry Pavlov / Dave] See Attachment AB AC. Apache Impala Project [Jim Apple / Roman] See Attachment AC AD. Apache Incubator Project [Justin Mclean / Shane] See Attachment AD AE. Apache Joshua Project [Tommaso Teofili / Ted] No report was submitted. @Ted: pursue a report for Joshua AF. Apache jUDDI Project [Alex O'Ree / Rich] See Attachment AF AG. Apache Juneau Project [James Bognar / Myrle] See Attachment AG AH. Apache Kafka Project [Jun Rao / Roman] See Attachment AH AI. Apache Kibble Project [Rich Bowen] See Attachment AI AJ. Apache Knox Project [Larry McCay / Myrle] See Attachment AJ AK. Apache Kylin Project [Shao Feng Shi / Danny] See Attachment AK AL. Apache Lens Project [Amareshwari Sriramadasu / Craig] See Attachment AL AM. Apache Libcloud Project [Tomaž Muraus / Ted] See Attachment AM AN. Apache Logging Services Project [Matt Sicker / Daniel] See Attachment AN @Daniel: follow up about log4net security fix AO. Apache ManifoldCF Project [Karl Wright / Rich] See Attachment AO AP. Apache Marmotta Project [Jakob Frank / Shane] No report was submitted. @Shane: pursue a report for Marmotta AQ. Apache MetaModel Project [Kasper Sørensen / Dave] See Attachment AQ AR. Apache Oozie Project [Gézapeti / Roman] See Attachment AR AS. Apache Open Climate Workbench Project [Huikyo Lee / Daniel] See Attachment AS @Danny: find out about fork details AT. Apache OpenNLP Project [Jeffrey T. Zemerick / Dave] See Attachment AT AU. Apache OpenWhisk Project [Dave Grove / Shane] See Attachment AU AV. Apache Perl Project [Philippe Chiasson / Rich] No report was submitted. AW. Apache Petri Project [Dave Fisher] See Attachment AW AX. Apache Phoenix Project [Josh Elser / Myrle] See Attachment AX AY. Apache POI Project [Dominik Stadler / Ted] See Attachment AY AZ. Apache Qpid Project [Robbie Gemmell / Craig] See Attachment AZ BA. Apache REEF Project [Sergiy Matusevych / Danny] See Attachment BA BB. Apache River Project [Peter Firmstone / Ted] No report was submitted. @Ted: pursue a report for River BC. Apache RocketMQ Project [Xiaorui Wang / Rich] See Attachment BC BD. Apache Roller Project [David M. Johnson / Daniel] See Attachment BD BE. Apache Santuario Project [Colm O hEigeartaigh / Myrle] See Attachment BE BF. Apache Serf Project [Branko Čibej / Danny] No report was submitted. @Danny: pursue a report for Serf BG. Apache ServiceComb Project [Willem Ning Jiang / Shane] See Attachment BG BH. Apache SIS Project [Martin Desruisseaux / Roman] See Attachment BH @Daniel: follow up with questions from comments BI. Apache Spark Project [Matei Alexandru Zaharia / Dave] See Attachment BI BJ. Apache Stanbol Project [Rafa Haro / Craig] No report was submitted. BK. Apache Streams Project [Steve Blackmon / Roman] See Attachment BK BL. Apache Subversion Project [Stefan Sperling / Myrle] See Attachment BL BM. Apache Syncope Project [Francesco Chicchiriccò / Craig] See Attachment BM BN. Apache SystemML Project [Jon Deron Eriksson / Ted] See Attachment BN BO. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Daniel] See Attachment BO BP. Apache TomEE Project [David Blevins / Danny] See Attachment BP BQ. Apache Traffic Control Project [David Neuman / Rich] See Attachment BQ BR. Apache Turbine Project [Georg Kallidis / Shane] See Attachment BR BS. Apache Usergrid Project [Michael Russo / Dave] See Attachment BS BT. Apache Velocity Project [Nathan Bubna / Shane] See Attachment BT BU. Apache Whimsy Project [Sam Ruby / Dave] See Attachment BU BV. Apache Xalan Project [Gary D. Gregory / Myrle] See Attachment BV BW. Apache Xerces Project [Michael Glavassevich / Danny] No report was submitted. BX. Apache XML Graphics Project [Clay Leeds / Craig] See Attachment BX Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Bigtop Project Chair WHEREAS, the Board of Directors heretofore appointed Youngwoo Kim (ywkim) to the office of Vice President, Apache Bigtop, and WHEREAS, the Board of Directors is in receipt of the resignation of Youngwoo Kim from the office of Vice President, Apache Bigtop, and WHEREAS, the Project Management Committee of the Apache Bigtop project has chosen by vote to recommend Jun He (junhe) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Youngwoo Kim is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Bigtop, and BE IT FURTHER RESOLVED, that Jun He be and hereby is appointed to the office of Vice President, Apache Bigtop, 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 Bigtop Project Chair, was approved by Unanimous Vote of the directors present. B. IPMC members removal WHEREAS, the Board of Directors requires Project Management Committee Members subscribe to their Project’s Private Mailing List, and WHEREAS, the Board of Directors is in receipt of a list of Incubator PMC Members who are not subscribed to said mailing list, and WHEREAS, the Project Management Committee of the Apache Incubator project has chosen by consensus to remove not subscribed members from the PMC. NOW, THEREFORE, BE IT RESOLVED, that the following people are removed from the Apache Incubator Project Management Committee. Adam Estrada Afkham Azeez Aleksander Slominski Andrew Hart Andrus Adamchik Anne Kathrine Petteroe Arun Murthy Arvind Prabhakar Ashutosh Chauhan Ben Laurie Benjamin Hindman Berin Loritsch Bill Stoddard Brock Noland Bruce Snyder Carl Johan Erik Edstrom Chris Mattmann Chris Nauroth Christopher Douglas Craig McClanahan Curt Arnold Daniel John Debrunner Daniel Takamori Dave Johnson Dirk-Willem van Gulik Eran Chinthaka Florian Müller Garrett Rooney Ioannis Canellos Jacques Le Roux James Strachan Jan Piotrowski Jarek Gawor Jean-Louis Monteiro Justin Erenkrantz Kanchana Pradeepika Welagedara Karl Wright Kasper Sørensen Kathey Marsden Kim Whitehall Larry McCay Marcel Offermans Marlon Pierce Michael James Joyce Mladen Turk Morgan Delegrange Niklas Gustavsson Norman Maurer Patrick Wendell Paul Hammant Paul Ramirez Phil Sorber Philip M. Gollucci Reinhard Pötz Richard Hirsch Rick Hillegas Robert Burrell Donkin Romain Manni-Bucau Sanjiva Weerawarana Senaka Fernando Srinath Perera Stephen D Blackmon Suresh Srinivas Susan Wu Sylvain Wallez Thomas Dudziak Tomaž Muraus Tony Stevenson Vincent Siveton Xiangrui Meng Yegor Kozlov Zhaohui Feng Special Order 7B, IPMC members removal, was approved by Unanimous Vote of the directors present. C. Terminate the Apache Aurora Project WHEREAS, the Project Management Committee of the Apache Aurora project has chosen by vote to recommend moving the project to the Attic; and WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache Aurora project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Aurora project is hereby terminated; and be it further RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache Aurora Project; and be it further RESOLVED, that the office of "Vice President, Apache Aurora" is hereby terminated; and be it further RESOLVED, that the Apache Aurora PMC is hereby terminated. Special Order 7C, Terminate the Apache Aurora Project, was approved by Unanimous Vote of the directors present. D. Terminate the Apache Forrest Project WHEREAS, the Project Management Committee of the Apache Forrest project has chosen by vote to recommend moving the project to the Attic; and WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache Forrest project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Forrest project is hereby terminated; and be it further RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache Forrest Project; and be it further RESOLVED, that the office of "Vice President, Apache Forrest" is hereby terminated; and be it further RESOLVED, that the Apache Forrest PMC is hereby terminated. Special Order 7D, Terminate the Apache Forrest Project, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Adopting a well-known COI policy As the ASF grows in number of paid positions and is working to secure more sponsors, we should adopt a well-known financial conflict of interest policy. This is important to ensure that we have clear and consistent disclosures internally of financial interests in officer/director roles, as well as to show potential donors that we're following best practices for fiscal responsibility. I suggest the IRS example policy, which many non-profits use: https://www.irs.gov/instructions/i1023#en_US_2018_publink100061018 https://www.irs.gov/charities-non-profits/form-1023-purpose-of-conflict-of-interest-policy This also includes an annual review statement, which should be simple to automate and is also reported in filing our 990s. By general consent, this discussion will continue on the lists. B. Long Running Topics of Board Interest I'd like to briefly touch on the subject of long running topics that are of interest to the board. Could we consider using "unfinished business" to track on-going items such as "distribution of binaries", "CI", and "CoI Policy" and assign a board shepherd and reporting date? I am concerned that the current set-up is optimised to deal with committee reports and time-boxed actions and doesn't really incorporate the board keeping an eye on slow burning topics. @Craig: fill in unfinished business section for next board meeting 9. Review Outstanding Action Items * Roman: Update docs around legal FAQ [ President 2019-09-18 ] Status: DONE * David: close the loop with Arrow and other communities with needs for CI [ Arrow 2019-10-16 ] Status: * Danny: work with Sally on info about the Attic process [ Tajo 2019-10-16 ] Status: * Roman: find out about bandwidth [ Jakarta EE Relations 2019-11-20 ] Status: DONE * Roman: reach out to members@ for any interest in volunteering [ Jakarta EE Relations 2019-12-18 ] Status: DONE * Rich: pursue a roll call for PredictionIO [ PredictionIO 2019-12-18 ] Status: * Sally: talk to Tajo about Attic [ Tajo 2019-12-18 ] Status: done. Tajo is moving to the Attic. * Dave: find a volunteer for this position [ Jakarta EE Relations 2020-01-15 ] Status: Wanted email sent to members@ and board@ on Jan 29 and repeated on Feb 10. One person may be interested but they want to know the current state I cc'd Roman on that discussion. * Myrle: follow up on security issue [ Aries 2020-01-15 ] Status: * Daniel: follow up on outstanding questions to PMC [ AsterixDB 2020-01-15 ] Status: Pinged on 2020-01-26. Awaiting response. * Ted: follow up with info about CoC reporting [ Fluo 2020-01-15 ] Status: done. It was a random thing, not an Apache thing * Danny: pursue a roll call [ Helix 2020-01-15 ] Status: * DanielGruno: start graduation talks with Pony Mail [ Incubator 2020-01-15 ] Status: * Matt: ensure new PMC Chair knows to report next month [ OpenNLP 2020-01-15 ] Status: Done! * Dave: ensure foreign language dev@ discussions are mirrored in English [ OpenOffice 2020-01-15 ] Status: Done: I've reminded the PMC gently that this is important. I'll need to revisit the dev-de@ list from time to time. Myrle: please check to see if the folks on dev-de@ have got the message correctly. * Dave: push for Attic discussion with PMC and community [ Stanbol 2020-01-15 ] Status: Pushing on private@ for the PMC to start. No response to the push in one week. Sent a warning message to dev@ on Jan 30 I had a response only from the PMC chair on dev@ on Jan 31. Force the issue? * Ted: pursue a report for Streams [ Streams 2020-01-15 ] Status: Done. They reported * Shane: pursue a report for Tapestry [ Tapestry 2020-01-15 ] Status: Done! 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 12:10 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] * ISSUES FOR THE BOARD None. * OPERATIONS Covering the period January 2020 Responded to the following queries, liaising with projects as required: - Updated event policy regarding date conflicts at request of VP, Conferences - Continued to work on a draft policy for how we allow providers of services - Continued to work on a draft policy for downstream distribution of Apache projects - Provided input to FY21 budget (8% reduction to FY20) - Signed an agreement with Alibaba to transfer dubbo.io to the ASF to reference our use of those services in their marketing material - Signed a co-existence agreement for DRUID. - Approved two uses of our logos to identify use of our products - Provided advice to a podling regarding trademark assignment - Provided advice to a podling regarding the trademark registration process - Approved use of a project logo on a t-shirt for personal use - Provided advice to a project regarding a name change - Provided advice regarding allocating speaking slots to sponsors at an external event using our marks - Approved the use of our marks in a book - Providing advice to a project on including links to external support services on the project website - Provided advice to CASSANDRA regarding the development of guidelines for the use of the project name in a managed service offering - Approved one podling name search - Approved one external event * REGISTRATIONS - Started the process to register FLINK in China and the EU * INFRINGEMENTS KAFKA is taking the lead on a couple of issues related to external product naming. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri] We continue operating nominally with regular renewals. Of note is that one Gold and one Silver sponsor have been acquired and are sorting out their future strategy. We have been seeking a new point-of-contact for one of our Bronze sponsors. We have three sponsors that are in arrears. We welcomed one new Bronze Sponsor, Xplenty, this month. Our outreach to our Targeted Sponsors to confirm their commitment for the 2020 year continues. The majority of existing Targeted Sponsors have confirmed to renew donated products and services. We have also reached out to all Sponsors regarding their renewals, per their usual sponsorship cycle. We have also pre-pitched sponsorship opportunities for ASF Conferences in 2020. We're continuing to engage with ASF Conferences team to provide support and process documentation. With 3 Roadshows in North America and 1 in Europe, as well as ApacheCon North America, we want to be sure the procedures we work up are commonly understood and useful for all teams involved. Of note, we've finalized our process for sponsorship sales and documented the procedure for future events. Individual Donations and Corporate Giving: we have earned $1,950 over the past month. Some sponsors are also using the donation interface to pay for their sponsorship renewals using a credit card; we received a Silver Sponsorship renewal payment this month. We experienced a high volume of repeat fraudulent donation attempts, and are working with Hopsie and ASF Infrastructure to resolve the issue. We are also working to socialize and improve understanding of the link policy modification communicated in November. The sponsorship page has been updated to indicate that all links are rel="sponsored" and we're planning an email communication for all existing sponsors to let them know about the upcoming change upon their renewal. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi] [REPORT] ASF Marketing & Publicity — February 2020 I. Budget: we remain on budget as planned. A few additional vendor invoices have been forwarded for payment processing; we are also examining our spend on the "Trillions" documentary: a portion of this budget may need to be carried into the FY2021 budget as the work continues. II. Cross-committee Liaison: Sally Khudairi supports ASF Fundraising by securing ASF Sponsor renewals, pursuing outstanding sponsor payments, and confirming commitments from ASF Targeted Sponsors. We have pre-pitched ASF 2020 Conferences to our Sponsors, and will liaise with the sales support team as our work continues. We are promoting the CFPs for Apache Roadshow/DC and ApacheCon, and have been assisting the Apache Roadshow/Seattle with any questions. We supported ASF Diversity & Inclusion by inviting Apache PMCs to submit proposals for internships through Outreachy. We published "Apache in 2019 - By The Digits" https://s.apache.org/Apache2019Digits , the "Apache Software Foundation Security Report: 2019" https://s.apache.org/tbyxg ; and the latest “Success at Apache” post, "Literally", https://s.apache.org/xjcrj . The ASF documentary, "Trillions and Trillions Served", is in post-production and on schedule, and released its first teaser https://s.apache.org/ASF-Trillions III. Press Releases: no formal announcements were issued via the newswire service, ASF Foundation Blog, or announce@apache.org during this timeframe. IV. Informal Announcements: we published 6 items on the ASF "Foundation" Blog. 5 Apache News Round-ups were issued, with a total of 292 weekly summaries published to date. We tweeted 27 items to 56K followers on Twitter, and posted 23 items on LinkedIn that garnered more than 78.8K organic impressions. We have also begun to tweet again for the Apache Incubator after a 2-year hiatus. V. Future Announcements: 3 announcements are in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones, "Did You Know?" success stories, "Have You Met?" highlights, and "Project Perspectives" profiles are requested to contact Sally at with at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to two media queries. The ASF received 1,213 press clips vs. last month's clip count of 1,150. Media coverage of Apache projects yielded 1,180 press hits vs. last month's 1,550. ApacheCon received 1 press hit. VII. Analyst Relations: we received no briefing requests for at this time. Apache was mentioned in 1 report by Gartner; 6 reports by Forrester; 4 reports by 451 Research; and 5 reports by IDC. VIII. Central Services: the Creative team has finalized tweaks to the ApacheCon site https://www.apachecon.com/ . They have also relaunched the ASF Fundraising landing page http://apache.org/foundation/contributing.html , and are continuing work on refining the Apache PLC4X theme, as well as updating the Apache project logo page. Our work on a new home page for Central Services that will enable both Creative and Editorial teams to standardize the process to request assistance and track progress. We are rolling out new editorial projects, but have scheduling gaps to accommodate volunteers' limited availability. IX. Events liaison: we continue to support ComDev-coordinated events, such as FOSDEM and DevNexus, as well as ASF Conferences, including Apache Roadshows and ApacheCon. X. Newswire and press clip accounts: all accounts are auto-renewing through 2020 to ensure we have constant access without interruption. # # # ----------------------------------------- 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 ========== - Added Jekyll as a standard website builder. This is the default for GitHub Pages, so many people are familiar with it, and have been asking for it. This is provided via our ".asf.yaml" system. - The certificate on our LDAP servers expired, causing havoc. We quickly generated a new cert and propagated that to the servers and clients needing it (including our vendor who operates the lists.a.o archive). - Chris Thistlethwaite wrote a blog post for the "Success at Apache" series being produced by Marketing & Public Relations. https://s.apache.org/xjcrj Finances ======== - The FY21 Infra budget has been developed and submitted to operations@ for inclusion into the overall budget. Short Term Priorities ===================== - Expand our agenda, for the team meetup. - Get downloads.a.o running (see below) Long Range Priorities ===================== - Turn off hermes, and get our mail infrastructure on modern systems. - Rackspace may be ending their Open Source support program, likely at the end of 2021. We have no critical services operating there. General Activity ================ - JMX monitoring has been added for deeper insights into our Java-heavy services (Jira and Confluence). - Decided on time/location for Infra F2F: March 29 to April 3rd, in Nashville, TN, USA. - Infra documentionat improvements are in-progress for three primary areas: www.a.o/dev, infra.a.o, and the INFRA cwiki. - Project-specific Jenkins Masters are getting set up and tested, using CloudBees Operation Center for managing them. - Several Infra people attended FOSDEM, and had good chats with community members and a couple of our vendors. - The Apache Roller instance for blogs.a.o has been updated. - Looking at "rundeck" to improve our tooling. - The TLP servers have been failing. We are going to move the downloads off of www.a.o/dist/ to a new downloads.a.o server, as a way to stabilize the *.a.o websites. - Two projects were identified as improperly using our primary servers to download distribution artifacts, contrary to our published policy (ie. use the mirror system). Given the problems that we've been seeing on the TLP servers (above), we notified the projects to fix their distribution points. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] Conferences We currently have 6 events “in flight”, with two of them happening in the next 3 months. Apache Roadshow, Washington DC. March 25-26 http://apachecon.com/usroadshowdc20 Apache Roadshow Chicago. May 18-20 https://www.apachecon.com/chiroadshow20/ The ARS Chicago launched CFP, targeted to close 3/20. At the moment is finalizing booking venues (will probably be done by board meeting), generating prospectus, and devising /executing on Meetup/University/tech incubator out reach strategy. There is no link on the top page of apachecon.com to the roadshow at this time, by design. We want to finish site build, which is waiting on registration plumbing, finalizing venue bookings, etc. Though we haven't finished prospectus yet, there has been some interest expressed in sponsorship. Budget has been approved. Apache Roadshow Seattle. June 23-26 https://www.apachecon.com/searoadshow20/ Seattle Roadshow is in sponsorship and agenda mode, and we will be inviting speakers starting this month. We have venue and amenities secured, and are planning a BarCamp in the spring to promote the main event. ApacheCon North America 2020, New Orleans, September 28 - October 3 http://apachecon.com/acna2020 The Call for Presentations is now open and we have received 35 submissions so far. Registration is open (as of meeting time). Apache Roadshow Europe is in planning. No details are available yet, although a June timeframe has been suggested. We are working on detailed Event Playbook documentation, at https://cwiki.apache.org/confluence/display/CONFERENCES/Event+Playbook , with the hopes that our 2021 events schedule will be 1) planned further in advance, 2) have more consistency between events, and 3) be easier for our event leads, who will not feel that they are making everything up from scratch every time. Apache Roadshow China, October 24-26 Potentially in Beijing. No details are yet available. ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] Current Events ============== Fosdem completed at the start of the month, and three TAC attendees had a busy and good 2 days. Going around talking to other attendees - about what they are doing in their Apache projects, how they got in via the Incubator etc. And also what other attendees were involved in. They also spent some time on the ASF Booth, talking with attendees there and handing out swag etc - this allowed for the main person(s) on the booth to present and to attend talks. Our TAC folks also got to attend many talks that they were interested in. Informal conversations after the event showed that all our TAC folks had a great time and learned much from the weekend. Also enjoying talking with long time ASF people, current and ex board members, infra staff etc. More formal feedback in the form of a survey will be sent out soon. Future Events ============= TAC has an events Calendar that it shares with other Committees for the purposes of cross-committee planning and collaboration. Currently filled our up until October we are looking at possibly supporting :- Chicago Roadshow, Berlin Buzzwords, Seattle Roadshow, ApacheCon New Orleans. Any ASF Project putting on a Hackathon and/or Meetup should also talk to TAC about supporting them getting folks there (Committers and Non Committers) Mailing List Activity ===================== No list activity since the previous report. Membership ========== No changes to the TAC membership since the last report. ----------------------------------------- Attachment 7: Report from the VP of Finance [Tom Pappas] * Continued work with Fundraising committee * Working on Roadshows operations, including Insurance * Working with the President, EVP and Dept heads on FY21 Budget creation ----------------------------------------- Attachment 8: Report from the VP of Diversity and Inclusion [Gris Cuevas] Contributors Gris Cuevas Katia Rojas Georg Link ## 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: Survey revamp*** The survey application was wrapped up with 622 completed responses and we are moving into survey analysis. We are focusing on moving the next sections of the project along, these are: contributor experience interviews and community metrics analysis. *** Project: User Experience Research on new contributors *** No status change here, so same information as previous report applies: We have reviewed preliminary answers from the survey to draft interview questions. The main focus for now is to write follow up questions to validate early hypothesis, main topics gravitate around type of contributions, demographic background specially spoken language, and challenges experienced by newer members. We need to find at least 20 people we can interview with the questions from this User Experience research. See the operations section below to see how we're planning to do this. *** Project: Internships for underrepresented groups (Outreachy) *** First-round Outreachy program dec-march: Mentors and Outreachy intern are getting assignments. The feedback provided is positive. The next steps for the training toolkit are open to discussion in the mailing list dev@. See page [1] We change the date of our weekly meeting to Mondays at 20h (UTC). [2] Second round Outreachy program: Apache has been successfully accepted to participate in the next round of the Outreachy program May-August 2020. [3] Sponsors: we got fundings for 8 interns approximately. We started "calling for mentors" with the help of PR, Sally. We also set up a reminder for this message. We discussed alternative channels to promote the program and attract mentors/interns such as meetups and talks in local universities. We made the first contact. [4] We updated the blog. One page for the message "calling for mentors" and a second page to update the instructions to become a mentor and submit a project. [5] We are monitoring PMC mailing lists to see if projects are getting developed. There are some potential mentors showing their interest and asking for guidance. We are contacting mentors to see if they would like to continue in the second round. *** Operations *** 2021 Budget request was originally going to be $0, now we are considering request a small amount around ~$15k for survey and community data analysis next year to compare improvements. ## Health report: The dev@ and diversity@ mailing lists continue to be slow, not too much activity outside the work done for each ongoing project. The discussions have been focused on topics that pertain to the projects we are running. ## Committee members changes: None. ## References [1]https://cwiki.apache.org/confluence/display/EDI/Getting+Started+At+Apache [2]https://cwiki.apache.org/confluence/display/EDI/2020-01-13+Outreachy+Meeting+notes [3]https://www.outreachy.org/december-2019-to-march-2020-internship-round/communities/apache/ [4]https://cwiki.apache.org/confluence/display/EDI/2020-01-27+Outreachy+Meeting+notes [5]https://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=EDI ----------------------------------------- Attachment 9: Report from the VP of Data Privacy [Dirk-Willem van Gulik] My personal take is that there are now enough people on the list (-and- the 12 `sample' cases discussed sofar seem to all have headed for sufficient consensus) that it is fair to now draft what should be our GDPR stance from which we can derive a guideline and policy. And with that concept not coming as a surprise. We have about 6 more legal/complex points for expects sofar (such as to what extent can you push things back for `self service' to the complainant). These may require legal attention at some point. Actual GDPR and similar requests: two in flight; neither contentious. Tracked in JIRA. ----------------------------------------- Attachment 10: Report from the VP of W3C Relations [Andy Seaborne] Andy Seaborne (andy@) and Steve Blackmon (sblackmon@) have joined the W3C Bridging GraphQL and RDF Community Group. ASF has signed the W3C Community Contributor License Agreement for this Community Group. ----------------------------------------- Attachment 11: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] For the past months we've had a regular amount of usual requests flowing through LEGAL JIRA and legal-discuss. Hen and the rest of the volunteers took a good care of resolving most of these in time. We're up 1 (to 22), unresolved issues this month. John D. Ament has indicated that he may want to step in to replace Mark Struberg as VP Jakarta EE Relations. With renewed involvement, hopefully we can finalize discussions with the Eclipse Foundation We were contacted by Technology Enforcement Division (Bureau of Competition) from the Federal Trade Commission of the United States Government and offered to participate in a study of "market participants" in the cloud services industry. We had to decline on account that we are not, in fact, a market participant. I started collecting background information on various binary distribution channels that ASF controls in preparation for a more comprehensive discussion on the subject. ----------------------------------------- Attachment 12: 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. This month we published a look at Security for 2019 https://s.apache.org/security2019 Stats for Jan 2020: 16 [license confusion] 12 [support request/question not security notification] Security reports: 40 (last months: 23, 31, 29, 28) 3 [httpd], [nifi], [tomcat] 2 [hadoop], [spamassassin], [trafficserver] 1 [activemq], [ant], [aries], [beam], [brooklyn], [cayenne], [cloudstack], [commons], [hc], [hive], [infrastructure], [jackrabbit], [jspwiki], [kafka], [kylin], [manifoldcf], [nuttx], [ofbiz], [olingo], [openoffice], [portals], [shardingsphere], [shiro], [superset], [zookeeper] In total, as of 3 February 2020, we're tracking 53 (last month: 49) open issues across 32 projects, median age 69 (last month: 116) days. 36 of those issues have CVE names assigned. 4 (last month: 4) of these issues, across 3 projects, are older than 365 days. None require escalation. ----------------------------------------- Attachment 13: Report from the VP of Jakarta EE Relations [Mark Struberg] ----------------------------------------- Attachment A: Report from the Apache Ambari Project [Jayush Luniya] ----------------------------------------- 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 (17 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: Ivy 2.5.0 was released on 2019-10-24. Ant 1.10.7 was released on 2019-09-05. Ant 1.10.6 was released on 2019-05-08. ## 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 BookKeeper Project [Sijie Guo] ## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Issues: There are no blocker issues requiring board attention at this time. ## Membership Data: Apache BookKeeper was founded 2014-11-18 (5 years ago) There are currently 21 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Charan Reddy G on 2019-07-23. - No new committers. Last addition was Andrey Yegorov on 2018-02-09. ## Project Activity: Recent releases: 4.10.0 was released on 2019-11-06. 4.9.2 was released on 2019-05-16. 4.9.1 was released on 2019-04-06. ## Community Health: ### Community We are leveraging Pulsar for growing BookKeeper community. Pulsar Summit has a dedicated `bookkeeper` track for the community to present bookkeeper related talks. This will drive more participation from both communities. ### Committers We did not add any new committer within last year. We have a good amount of small contributions but no one is yet ready to be invited as committer. We are trying to engage more with current contributors. Most of current contributions come from other downstream Open Source projects that are using BookKeeper as building block. We got recent feedback of usage of BookKeeper and DistributeLog by new non open source projects. ### Activities dev@bookkeeper.apache.org had a 80% increase in traffic in the past quarter (123 emails compared to 68) user@bookkeeper.apache.org had a 271% increase in traffic in the past quarter (52 emails compared to 14) 32 commits in the past quarter (-40% decrease) 12 code contributors in the past quarter (-29% decrease) 32 PRs opened on GitHub, past quarter (-31% decrease) 25 PRs closed on GitHub, past quarter (-13% decrease) 25 issues opened on GitHub, past quarter (66% increase) 8 issues closed on GitHub, past quarter (100% increase) ----------------------------------------- Attachment D: 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 (4 years ago) There are currently 16 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Duncan Grant on 2018-08-30. - No new committers. Last addition was Duncan Grant on 2018-06-13. ## Project Activity: I am very pleased to report that there has been considerable activity recently to prepare the 1.0.0 release of Apache Brooklyn, with many pull requests to fix outstanding issues and concerns. A candidate release was made, but some issues were found with it which we want to take a little more time to address. However, I am confident that Brooklyn 1.0.0 is imminent. ## Community Health: - The project continues with a recently high turnover of pull requests and commits. - We continue to monitor our community for potential new committers and PMC members with the aim of regularly adding individuals. ----------------------------------------- Attachment E: 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. We haven't had any activity since. ## 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 F: Report from the Apache Cassandra Project [Nate McCall] ## Description: The Apache Cassandra database is the right choice when you need scalability and high availability without compromising performance. Linear scalability and proven fault-tolerance on commodity hardware or cloud infrastructure make it the perfect platform for mission-critical data. Cassandra's support for replicating across multiple datacenters is best-in-class, providing lower latency for your users and the peace of mind of knowing that you can survive regional outages. ## Issues: There are no issues to report at this time. ## Membership Data: Apache Cassandra was founded 2010-02-17 (10 years ago) There are currently 54 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Chris Lohfink on 2019-10-01. - No new committers. Last addition was Dinesh Joshi on 2019-03-05. ## Project Activity: We released 4.0-alpha3 on 2020-02-06 to gather community feedback and get more folks actively involved in testing. We have started a detailed tracking board on JIRA and have been sending out regular updates on status. An example email can be found here: https://s.apache.org/r56u3 Other releases: - 2.2.15 was released on 2019-10-29. - 3.0.19 was released on 2019-10-29. Note: new releases of each 3.11, 3.0, and 2.2 branches are currently under vote. ## Community Health: We've had a substantial uptick in traffic over the past quarter as a result of folks getting back involved in the release of 4.0 after the holidays. The following stats are pertinent: - 79 issues closed in JIRA, past quarter (21% increase) - 115 commits in the past quarter (57% increase) - 35 code contributors in the past quarter (40% increase) - 63 PRs opened on GitHub, past quarter (36% increase) We continue to see an increase in user participation in both #cassandra and #cassandra-dev Slack channels. This is now our most popular avenue for helping new users. We are looking forward to our Apache Cassandra track at this years ApacheConNA and have again requested three days. CFP announcements for such have been sent to the dev and users mail lists. ----------------------------------------- Attachment G: 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 FOR THE BOARD There are no issues requiring board attention at this time. RELEASE The latest release was created on February 10, 2020. ACTIVITY Two releases were made in this reporting period: 1. API version 2.0.0 2. API Implementation and Ontologies version 2.0.0 They are the result of the refactoring effort done last year. A dependency diagram provided by Hasan is used to plan the releases of other modules. COMMUNITY Latest change was addition of a new committer and PMC member on 27.12.2018 INFRASTRUCTURE Latest update of the Apache Clerezza Website was in February 2018. ----------------------------------------- Attachment H: 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 (17 years ago) There are currently 80 committers and 32 PMC members in this project. The Committer-to-PMC ratio is 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: The most recent release is 2.1.12 on 2013-03-14 The project is mainly in maintenance mode. ## Community Health: Still very few activity on the project. Still active PMC members around here. There was some activity on users list showing that the branch 2.2 is still in use, while all activity was previously mainly on branch 2.1 ----------------------------------------- Attachment I: Report from the Apache Community Development Project [Sharan Foga] ## 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 needing Board feedback at this time. ## Membership Data: Apache Community Development was founded 2009-11-01 (10 years ago) There are currently 34 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 9:8. Community changes, past quarter: - Swapnil Mane was added to the PMC on 2020-01-02 - Swapnil Mane was added as committer on 2020-01-02 ## Project Activity: We have had a very active quarter with discussions on a wide range of topics. Apache Local Community (ALC) ComDev has been actively worked on Apache Local Community (ALC) initiative. Swapnil Mane has been a key co-ordinator responding to all community feedback. The ALC comprises local groups of Apache (Open Source) enthusiasts, called an 'ALC Chapter'.[1] Following various discussions we have agreed the following steps to help ComDev establish solid oversight of the ALC initiative -- Process to establish ALC Chapter and requirement for it (like it is mandatory to have at least 1 ASF member plus 2 PMC members in the ALC Chapter team)[2] -- ALC Roles and Responsibilities -- Code of conduct, rules, and regulations for ALC Chapter [3] -- Process to dissolve the ALC Chapter [4] -- Guidelines to organize ALC Event[5] -- How we make sure that we are not having people use the Apache name to promote messages that are not *our* message. The guidelines to organize an event, qualifications to establish ALC and code of conduct will help us in spreading the right messaging.[6][7][8] We have received the requests from the following places to establish the ALC Chapters. ComDev PMC is analyzing these requests. -- Beijing, China -- Warsaw, Poland -- Budapest, Hungary It is likely that our second ALC to be approved and formed, will be ALC Beijing. The ALC Indore Chapter executed the following event in this quarter: - Session on 'Open Source and ASF Awareness' for school students And their reports can be found at http://s.apache.org/alc-indore-reports FOSDEM Once again we had an ASF booth at FOSDEM. Volunteers from several projects were present or spent time on the booth talking to attendees about their projects or the ASF in general. We gave away stickers, ballons, hats, pens and coffee cups and encouraged people to buy the ASF a coffee by donating the cost of a cup of coffee to the ASF. We received invitations to participate at other open source events so will be promoting this on the mailing lists. GSOC We have applied on behalf of the ASF to be a GSoC mentoring organisation for 2020. Maxim Solodovnik from the ComDev PMC will be s the main administrator with Kevin McGrail helping co-admOuin. A wiki page has been created to collect GSoC ideas.[9] [1] https://s.apache.org/alc [2] https://s.apache.org/establish-alc-chapter [3] https://s.apache.org/alc-code-of-conduct [4] https://s.apache.org/dissolve-alc-chapter [5] https://s.apache.org/alc-guidelines [6] https://s.apache.org/tb177 [7] https://s.apache.org/qxdby [8] https://s.apache.org/zte2s [9] https://s.apache.org/iugko ----------------------------------------- Attachment J: 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 (11 years ago) There are currently 65 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 9:2. Community changes, past quarter: - Jonathan Hall was added to the PMC on 2020-02-12 - Juanjo Rodriguez was added as committer on 2020-02-07 ## Project Activity: - The release process for CouchDB 3.0.0 has started. We expect a release shortly. See board reports from last year about the exact nature of this release, including a discussion on features and backwards compatibility. - a blog post campaign to accompany the campaign is in the works as well. - a rogue source that provided binary builds off of CouchDB master has been shut down. Unbeknownst to the project, a good number of critical fixes for the 3.0.0 release were found by users of this unauthorized binary provider. We are happy to continue to make sure the project complies with ASF policy, but we also want to highlight that we benefited from something that was technically forbidden, so maybe it is worth reconsidering some of this. Due to the release process, we are currently not in the position to bring this up in the form of a regular policy change request, we just wanted to flag this, in case someone wants to take up this cause. - a large corporate contributor to CouchDB has an infrastructure policy of only allowing outbound HTML emails, while the ASF mail servers allow absolutely no HTML. This has lead to friction in getting individuals from that corporation to participate in the official channels of the project. We’ve made due for the moment, but this is hurting our official activity as people will go the route of least friction and start discussions outside of official channels. While those discussions are not of a nature that make decisions for the project, we are careful about keeping those on dev@, it leads to folks missing out on discussions, if they don’t happen to be part of a discussion channel that’s more accessible than the plaintext mailing list. Again, we are not in a position to pick up the mantle for this surely larger discussion, we just bring up another data point on the issue. ## Community Health: Community activity is in line with our expectations. We are seeing an uptick of new contributions around in the lead up of 3.0.0, which people are genuinely excited about. ----------------------------------------- Attachment K: 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: There are no issues requiring board attention. ## Membership Data: Apache Creadur was founded 2012-04-18 (8 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: Minor bugs have been fixed in the current 0.14-SNAPSHOT. The RAT part of Creadur is used most often. After ApacheCon2019 in Berlin some discussions and feature requests were reported. Apache Rat 0.13 was released on 2018-10-13. ## Community Health: The project benefits from the Github integration as it seems easier to integrate/file issues/start discussions. Apart from that we successfully changed the chair of the project. ----------------------------------------- Attachment L: 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 fixed some security related issues in our JSF module. Apart from that we've seen punctual fixes with no new features this time around. But this is fine for such a mature project. DS still has a really good reputation in the industry. We've been serving as a blueprint and idea supply for other projects like Microprofile. And many of our features even made it back to the CDI specification itself. ## Health report: We recently added a new committer. And we are always obsesrving the community for more active people. I think community is fine for a project of our age. ## Releases: - 1.9.3 was released on 2020-02-05. - 1.9.2 was released on 2019-12-16. - 1.9.1 was released on 2019-08-19. ## 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 M: Report from the Apache DRAT Project [Tom Barber] ----------------------------------------- Attachment N: 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: Nothing significant to report. ## Membership Data: Apache Drill was founded 2014-11-18 (5 years ago) There are currently 56 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - Bohdan Kazydub was added to the PMC on 2020-01-28 - Igor Guzenko was added to the PMC on 2019-12-12 - Denys Ordynskiy was added as committer on 2019-12-26 ## Project Activity: Drill 1.17 was released on 2019-12-26 which contains a significant number of bugfixes and improvements. (https://drill.apache.org/docs/apache-drill-1-17-0-release-notes/). The Drill Community had a Hangout meeting and will be working towards a number of strategic goals: 1. Increase the size of community 2. Reduce obstacles to use, such as improving documentation and website. 3. Work on publicity We have averaged about two releases per year. Going forward, we will try for smaller releases more frequently. Our next release is targeted for early Q2. Interesting work underway: - Storage plugins for Apache Druid, Apache Cassandra, Elasticsearch, and general HTTP/REST. - Significant code improvements to facilitate storage and format plugin development. - Integrations with Docker and K8s. - Documentation improvements to include website re-work. ## Community Health: - dev@drill.apache.org had a 35% increase in traffic in the past quarter (2169 emails compared to 1606) - user@drill.apache.org had a 97% increase in traffic in the past quarter (231 emails compared to 117) - 129 issues opened in JIRA, past quarter (28% increase) - 99 issues closed in JIRA, past quarter (15% increase) - 100 commits in the past quarter (78% increase) - 16 code contributors in the past quarter (6% increase) - 74 PRs opened on GitHub, past quarter (29% increase) - 75 PRs closed on GitHub, past quarter (15% increase) ----------------------------------------- Attachment O: Report from the Apache Druid Project [Gian Merlino] ## Description Apache Druid is a high performance real-time analytics database. It is designed for workflows where low-latency query and ingest are the main requirements. It implements ingestion, storage, and querying subsystems. Users interface with Druid through built-in SQL and JSON APIs, as well as third-party applications. Druid has an extensive web of connections with other Apache projects: Calcite for SQL planning, Curator and ZooKeeper for coordination, Kafka and Hadoop as data sources, Avro, ORC, or Parquet as supported data input formats, and DataSketches for scalable approximate algorithms. Druid can also be used as a data source by Superset. ## Issues There are no issues requiring board attention at this time. ## Activity We have done our first post-graduation release, Druid 0.17.0, containing over 250 new features, performance enhancements, bug fixes, and major documentation improvements from 52 contributors. Major improvements include improved native batch indexing, performance improvements, LDAP support, improved compliance with SQL standards, and much more. Work on the upcoming 0.18.0 release is underway and on track for a likely end of March release date. Community activity continues to be strong, with a healthy rate of commits, issues filed on GitHub, user mailing list posts, and ever increasing activity in our ASF Slack channel #druid, which now has over 600 members. Keeping boots on the ground to improve adoption, over the last month we have had Druid meetups in New Delhi, London, Athens, and Tel Aviv, with an additional meetup in Sydney scheduled in March. Planning for the Druid Summit event is progressing with over 80 proposed talks currently being evaluated, and half of the 40 scheduled speaking slots filled with a diverse set of both PMC members and passionate users. The event will take place April 13 - 15 in the San Francisco Bay Area. ## Recent PMC changes - Currently 27 PMC members. - No recent changes to PMC. ## Recent committer changes - Currently 35 committers. - New commmitters since last board report (Jan 15 2019): - Chi Cao Minh (Jan 21 2020) ## Recent releases - 0.17.0, our first release post graduation was released on Jan 26 2020 ## Development activity by the numbers In the last month: - 79 pull requests opened - 78 pull requests merged/closed - 55 issues opened - 25 issues closed - 476 comments on pull requests - 231 comments on issues ----------------------------------------- Attachment P: Report from the Apache Empire-db Project [Rainer Döbele] ## Description: Empire-db aims to provide a sophisticated approach to access SQL based relational database systems and to make the full power of the RDBMS available in 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 board attention at this time ## Membership Data: Apache Empire-db was founded 2012-01-24 (8 years ago) There are currently 9 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 9:10. 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: We have now just completed the work on our upcoming release and started a vote to begin with the build and publication process. If no objections arise, we will proceed and publish the release in the coming weeks. ## Community Health: Our existing community is still alive and active, although as we have mentioned before, for a small but mature project which is not about a hot new topic, it is not easy to attract new committers. ----------------------------------------- Attachment Q: Report from the Apache Flume Project [Ferenc Szabo] ----------------------------------------- Attachment R: Report from the Apache Forrest Project [David Crossley] Apache Forrest mission is software for generation of aggregated multi-channel documentation maintaining a separation of content and presentation. Issues: After discussion on both the dev and user mailing lists, a successful vote agreed to move the project to the Apache Attic. The resolution has been added to the board agenda as "Item 7D". The vote thread: https://lists.apache.org/thread.html/c49f6223e82bf32b559dc4bf0a061a75369856e11cf05cf654e51036@%3Cdev.forrest.apache.org%3E The vote summary thread: https://lists.apache.org/thread.html/42754945934baa9636ddb3894a57cd46217ed698a100fc6e6e0cae58%40%3Cdev.forrest.apache.org%3E ----------------------------------------- Attachment S: 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: We have released a new version mid August, with some major features. We are very close releasing 2.3.30, addressing feature requests from the users. freemarker-generator sub-product has received significant amount of code, and hopefully will yield releases in the foreseeable future. ## Health report: Activity is low but steady, as it's 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 (2.3.30). 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.29 was released on 2019-08-17 ----------------------------------------- Attachment T: Report from the Apache Geode Project [Karen Miller] ## Description: Apache Geode is a data management platform that provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high concurrency processing. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Geode was founded 2016-11-15 (3 years ago) There are currently 107 committers and 52 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 Bill Burcham on 2019-09-08. - Aaron Lindsey was added as committer on 2019-12-16 - Benjamin Ross was added as committer on 2019-12-06 - Donal Evans was added as committer on 2019-11-22 ## Project Activity: 1.11.0 was released on 2019-12-31. We are well on our way to a 1.12.0 release. Two areas of focus on our code base have been toward fixing tests marked as flaky, and introducing the ability to specify (authorize) access to data when querying a dataset (see https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security). ## Community Health: The community is actively contributing to the Apache Geode code base. In the past quarter: - 393 emails sent to dev@geode.apache.org - 315 issues opened in JIRA - 288 issues closed in JIRA - 379 PRs opened on GitHub - 396 PRs closed on GitHub - 563 commits by 57 code contributors ----------------------------------------- Attachment U: 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 (7 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: - Improve handling of network connection failure, overall improving reliability. - Performance improvements in the counter collection mechanism. ## Community Health: - Decreased activity for this last quarter. ----------------------------------------- Attachment V: Report from the Apache Gora Project [Kevin Ratnasekera] ----------------------------------------- Attachment W: Report from the Apache Groovy Project [Paul King] ## Description: Apache Groovy is responsible for the evolution and maintenance of the Groovy programming language. Groovy is a multi-faceted JVM programming language. ## Issues: No issues requiring board attention at this time. ## Membership Data: Apache Groovy was founded 2015-11-18 (4 years ago) There are currently 18 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 9:5. Community changes, past quarter: - No new PMC members. Last addition was Daniel Sun on 2019-05-06. - No new committers. Last addition was Eric Milles on 2019-08-21. ## Project Activity: The main recent focus recently has been on preparing for the 3.0.0 release expected in February. Recent releases: - 3.0.0-rc-3 was released on 2020-01-15. - 2.4.18 was released on 2020-01-14. - 2.5.9 was released on 2020-01-14. - 3.0.0-rc-2 was released on 2019-12-08. Downloads: - For Nov/Dec/Jan quarter: over 61 million - For 2019: approx 200M ## Community Health: Last quarter stats: - 75/72 PRs opened/closed on GitHub. - 77/86 issues opened/closed in JIRA. Master/all branch commits: - 424/821 commits were contributed from 15/17 contributors including 9 non-committer contributors (6 new). ----------------------------------------- Attachment X: Report from the Apache Hama Project [Chia-Hung Lin] ----------------------------------------- Attachment Y: Report from the Apache Helix Project [Kishore G] ----------------------------------------- Attachment Z: Report from the Apache HTTP Server Project [Daniel Gruno] ## Description: The mission of HTTP Server is the creation and maintenance of software related to Apache Web Server (httpd). The project is celebrating its 25th anniversary this month. ## Issues: There are no issues requiring board attention at present. ## Membership Data: Apache HTTP Server was founded 1995-02-27 (25 years ago) There are currently 124 committers and 53 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 Stefan Sperling on 2019-01-24. - Dennis Clarke was welcomed as a new committer on 2020-02-07. - Giovanni Bechis was welcomed as a new committer on 2020-02-16. ## Project Activity: - There were no new releases this quarter, which isn't surprising. We are on version 41 of the 2.4.x release branch, and with our habit of burning version numbers for botched release processes, we have had around 27 actual releases over the past 8 years, or roughly one every 4 months. The last release was 2.4.41 in August 2019, and we are slowly looking at whether a new release makes sense[1]. As with many projects, we are not dictated by a release schedule, but rather work with the mantra "does rolling a new release at present add more value than it costs releasing?". - We are having better luck with our CI testing this quarter, though there are still some issues with the more esoteric platforms that we need to iron out[2]. It is our hope that the new CI efforts can not only help us find bugs in patches quicker, but also have us work towards more reliable testing of specifications by utilizing a standardized framework of systems. - Work is ongoing for better support for systemd on the various Linux variants that make use of this, with a mod_systemd making it to the 2.4.x branch of our software, and future features like systemd socket activation and journald support sitting in the pipeline. - Our documentation build tool-chain may need an upgrade or automation, to remove issues when building with different java versions (as I understand it, we have - among other issues - problems with line endings and Unicode). Perhaps we can utilize the new ASF BuildBot 2.x service for this in the near future. [1] https://s.apache.org/y31qm [2] https://s.apache.org/1aa19 ## Community Health: The project experienced a very standard Christmas season, with commits and email traffic being down for the usual three weeks around Christmas, leading to an overall slower quarter (roughly 40% less activity as opposed to the previous busier quarter). Activity on our GitHub mirror picked up a bit, which may again nudge the question of moving to git. A simple tally of the PMC activity this past quarter shows excellent oversight in the project, and we have no concerns about community health. Likewise, the number of active contributors to our code-base has remained steady at 16 people this quarter (same as last quarter). Furthermore, we welcomed two new committers this quarter, and I would like to heartily welcome them to the httpd family. ----------------------------------------- Attachment AA: Report from the Apache HttpComponents Project [Asankha Chamath Perera] ## Description: The mission of HttpComponents is the creation and maintenance of software related to Java toolset of low level HTTP components ## Issues: There are no issues requiring attention of the Board at this point. ## Membership Data: Apache HttpComponents was founded 2007-11-14 (12 years ago) There are currently 19 committers and 10 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 Ryan Schmitt on 2019-08-28. - No new committers. Last addition was Ryan Schmitt on 2018-11-13. ## Project Activity: The project team is preparing the first GA release of HttpCore 5.0 and HttpClient 5.0 component libraries. This marks the end of a 5 year long development cycle and is a major milestone for the project. Recent releases: * HttpClient 5.0-beta7 was released on 2020-01-27. * HttpClient 4.5.11 GA was released on 2020-01-20. * HttpCore 4.4.13 GA was released on 2020-01-14. * HttpCore 5.0-beta11 was released on 2020-01-08. ## Community Health: Overall the project remains active. With 5.0 development phase completed we expect the main focus of the project to shift from development to maintenance and user support for some while. We planning to start a discussion on the development list about the 5.1 development project, its main objectives, scope and timeline. ----------------------------------------- Attachment AB: Report from the Apache Ignite Project [Dmitry Pavlov] ## Description: The mission of Ignite is the creation and maintenance of software related to High-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Ignite was founded 2015-08-19 (4 years ago) There are currently 49 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - Ivan Pavlukhin was added to the PMC on 2019-12-12 - Igor Sapego was added to the PMC on 2020-01-26 - Saikat Maitra was added to the PMC on 2020-01-08 - Alexey Zinoviev was added to the PMC on 2019-12-11 - Alexey Scherbakov was added as committer on 2019-12-12 ## Project Activity: - The community is focused on releasing a new major version of Apache Ignite, 2.8 (previous version 2.7.6 was released on 2019-09-19). - A new initiative to move Apache Ignite extensions to the separate Git repository is in progress. Meetups and Conferences: - PMC members and community members gave a number of talks in NY, Bay Area, Chicago, Silicon Valley, London. - Apache Ignite Meetups were held in Moscow and Saint-Petersburg. - Several webinars and meetups are scheduled, see also https://ignite.apache.org/events.html ## Community Health: - Overall community health is good. - PMC continues to discuss and vote for new committers and new PMC members. - Apache Ignite keeps attracting new contributors. - Dev. list activity remains stable. User list traffic increased by 15% compared to the previous quarter, commits increased by 30%. ----------------------------------------- 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: There are no issues requiring board attention. ## Membership Data: Apache Impala was founded 2017-11-14 (2 years ago) There are currently 50 committers and 32 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 Fredy Wijaya on 2019-07-27. - No new committers. Last addition was Laszlo Gaal on 2019-06-19. ## Project Activity: - Discussions on a release of 3.4 have begun - Planner and executor improvements for multi-threaded execution - Improvements to tests on ACID tables - Continued iterations on local catalog mode - The enablement of primary/foreign key hints during table creation - A number of improvements to test reproducability - A correctness fix for negative zero - Numerous improvements to ORC file handling - Several Apache Ranger related improvements, including support for column masking - Ten tickets with activity on aarch64 support; Impala has traditionally only supported x86-64 ## Community Health: Activity on many metrics decreased last quarter. This is typical for the project, and it corresponds to the US holiday season. The most prominent decrease was in the number of commits, which was down to 164. The November-December-January quarter has, in years past, seen 238, 258, 310, 199, and 183 commits (reverse chronological order). ----------------------------------------- Attachment AD: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for February 2020 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. This monthly report is in markdown so that it's easier to read. If you are not viewing this in that format, it can be seen here: https://cwiki.apache.org/confluence/display/INCUBATOR/February2020 There are presently 46 podlings incubating. In January, podlings executed 11 distinct releases. We added three new IPMC members and sixteen IPMC members retired. There was two requested IP clearance, one had an issue and the problem with last months IP clearance has been resolved. We have one new podling this month YuniKorn; another is under discussion AgensGraph. No projects graduated last month. Myriad has retired, and both Tamaya and Taverna are considering leaving the Incubator. At least one podling is heading towards graduation in the next few months. Two podlings did not report and will be asked to report again next month; they include PageSpeed and Taverna. This is the second time Taverna has failed to report and looking on their list they are discussing retiring from the Incubator. PageSpeed reached out to say they will report next month. It was noticed that a dozen of so podlings were missing multiple PPMC members signed up to their private mailing lists. Each podling was contacted, and just about all of them have corrected this. Three podlings MXNet, SDAP and Spot are still working on it. Several IPMC members are not signed up to the IPMC private list and may not be providing the oversight needed by their role. A board proposal has been put forward to remove them from the IPMC. These IPMC members have been emailed twice in the last month asking them to sign up. About 30% of the people identified have responded, and have signed up or asked to no longer be IPMC members. Most of them are ASF members, so even if they were removed, they could ask to join again. A dozen inactive mentors were contacted offlist and asked if they want to continue in the role, several have responded they wish to step down, and a couple have done so. The IPMC roster was also cleaned up with the removal of several people who had previously stood down or passed away. TubeMQ is no longer having issues bootstrapping, but needed guidance with their report. We were contacted by a researcher from the University of California to sign a letter of support for a project to study incubating projects. While the Incubator is supportive of research like this, some concerns were raised about the scope of the letter, and it was not signed. ## Community ### New IPMC members: - Holden Karau - Jason Darrell - Trevor Grant ### People who left the IPMC: - Benson Margulies - Branko Čibej - Brett Porter - Brian Fitzpatrick - Carsten Ziegeler - Colm O hEigeartaigh - Doug Cutting - Felix Meschberger - Glen Daniels - Gregory D. Reddin - Isabel Drost-Fromm - Marvin Humphrey - Michael Stack - Rob Vesse - Ross Gardler - Till Westmann ## New Podlings - YuniKorn ## Podlings that failed to report, expected next month - PageSpeed - Taverna ## Graduations - none The board has motions for the following: - none ## Releases The following releases entered distribution during the month of January: - APISIX 1.0 - Crail 1.2 - Daffodil 2.5.0 - DataSketches Java 1.2.0 - DolphinScheduler 1.2.0 - ECharts 4.6.0 - Hudi 0.5.1 - IoTDB 0.9.1 - Milagro Crypto C 2.0.1 - ShardingSphere 4.0.0 - Superset 0.35.2 ## IP Clearance - airflow-on-k8s-operator - Maven Wrapper ## Legal / Trademarks none ## Infrastructure none ## Miscellaneous The font size on the incubator web site was increased. ## Credits |---------------------------------------------------------------------- Table of Contents [Annotator](#Annotator) [DataSketches](#datasketches) [DolphinScheduler](#DolphinScheduler) [Doris](#Doris) [ECharts](#ECharts) [Heron](#Heron) [Milagro](#Milagro) [Myriad](#Myriad) [NuttX](#NuttX) [Pinot](#Pinot) [Ratis](#Ratis) [S2Graph](#S2Graph) [SDAP](#SDAP) [StreamPipes](#StreamPipes) [Tamaya](#tamaya) [Toree](#Toree) [Training](#Training) [TubeMQ](#TubeMQ) [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. Grow contributions outside the PPMC. 2. Establish release cadence. 3. Improve documentation, and in particular articulate a roadmap. ### Are there any issues that the IPMC or ASF Board need to be aware of? The podling missed reporting in January due to holiday disruptions and has been slow to make its first ASF release. The release machinery is all in place as of this month, and voting for the first release candidate should begin within the week. ### How has the community developed since the last report? The PPMC has been more actively communicating and plans to open up a weekly call to more directly engage early users. ### How has the project developed since the last report? The release machinery is in place, with Apache Rat being used to verify that licenses are in order. The PPMC is resolved to release the current state of the project and generate momentum from there. ### 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: Should begin voting within the week. ### When were the last committers or PPMC members elected? No new committers nor PPMC members have been added since the last report. ### Have your mentors been helpful and responsive? Mentors have been very helpful so far. They will be engaged around the initial release, to help ensure that everything is in order. ### Is the PPMC managing the podling's brand / trademarks? All the proper incubation disclaimers should be in the repository and on the website. The project is aware of no incidents of misuse of brand or trademark. ### Signed-off-by: - [X] (annotator) Nick Kew Comments: - [ ] (annotator) Steve Blackmon Comments: - [ ] (annotator) Tommaso Teofili Comments: ### IPMC/Shepherd notes: Dave Fisher - It looks like the report will be done a day late. Mentors did push for them and the project is active. -------------------- ## DataSketches DataSketches is an open source, high-performance library of stochastic 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. DataSketches has been incubating since 2019-03-30. ### Three most important unfinished issues to address before graduating: 1. Be more communicative and document our code changes more clearly. 2. We need to have more substantive discussions on dev@ especially about our growing TODO list and how we plan to address them -- create a roadmap as a guide for others to contribute. 3. Find / Attract new code committers outside Yahoo! ### 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? We are presenting at more conferences which has attracted some interest. We are definitely getting more traffic on our forum, GitHub issues and email lists. We recently added two channels on the-asf@slack: #datasketches and #datasketches-dev. The traffic has been fairly low on Slack as well as the forum. We could do more to publicize the slack channels. I could be optimistic and believe the low traffic is due to the holidays -- or that the code just works :) Nonetheless, the download traffic measured by repository.a.o has grown exponentially since our first Apache release on Sep 23. We are over 1000 unique IPs/ month and had a recent high of 22K downloads/ month. Bear in mind that this is all traffic that has migrated from the older, pre-Apache artifacts at com.yahoo.datasketches and is already higher than our peak downloads prior to Apache. These numbers also do not reflect any downloads of our Zip artifacts from a.o./dist (which includes our C++ artifacts) or other external download repositories (for example, specific to PostgreSQL). ### How has the project developed since the last report? Our releases are becoming easier, more polished and routine. Nonetheless, our website needs a lot of work (as mentioned above) and this will become our focus for the next month or so. ### 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: These are the major components and their last release dates: * DataSketches-Java 2020-01-26 * DataSketches-Memory 2019-11-21 * DataSketches-CPP 2019-09-17 * DataSketches-Hive 2019-10-11 * DataSketches-Pig 2019-10-18 * DataSketches-Postgresql 2019-10-29 ### When were the last committers or PPMC members elected? No new committers since April, 2019. ### Have your mentors been helpful and responsive? Yes. No open issues. ### Is the PPMC managing the podling's brand / trademarks? To the best of our knowledge, yes. * Are 3rd parties respecting and correctly using the podlings name and brand? As far as we know, yes. * If not what actions has the PPMC taken to correct this? We have not had to face this issue yet. * Has the VP, Brand approved the project name? Yes, and it is clearly stated as such on http://incubator.apache.org/projects/datasketches.html ### Signed-off-by: - [X] (datasketches) Liang Chen Comments: - [X] (datasketches) Kenneth Knowles Comments: - [X] (datasketches) Furkan Kamaci Comments: - [X] (datasketches) Dave Fisher Comments: - [X] (datasketches) Evans Ye Comments: ### IPMC/Shepherd notes: -------------------- ## DolphinScheduler Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow scheduling system dedicated to solving the complex dependencies in data processing, making the scheduling system out of the box for data processing. Dolphin Scheduler has been incubating since 2019-8-29. ### Three most important unfinished issues to address before graduating: 1. Make first no-WIP Apache releases. (in progress) 2. Make development document more easily to read 3. Develop more committers and 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? 1. Developed 7 more committers, commiters grew from 15 to 22. 2. More than 10 experienced users grew to be active contributors. 3. E-mail is popular between developers on serious topic discussion. ### How has the project developed since the last report? 1. Apache 1.2.0 with WIP has been released while non-WIP 1.2.1 version was ready to vote. 2. Substantially reduced config file and options to make the project easy to install 3. Modified CSS JS code to follow Apache license ### 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-1-2 ### When were the last committers or PPMC members elected? 2020-1-24 ### Have your mentors been helpful and responsive? Yes, our mentors help a lot on our firtst Apache Release. ### Is the PPMC managing the podling's brand / trademarks? Yes, We keep tracking podling's brand / trademarks. ### Signed-off-by: - [X] (dolphinscheduler) Sheng Wu Comments: - [X] (dolphinscheduler) ShaoFeng Shi Comments: - [X] (dolphinscheduler) Liang Chen Comments: - [X] (dolphinscheduler) Furkan KAMACI Comments: - [x] (dolphinscheduler) Kevin Ratnasekera Comments: ### IPMC/Shepherd notes: Justin Mclean: For an active project there is very list email on the devlist. Can you provide some insight to why this might be? Is conversation and planning happening off list? -------------------- ## 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. Continue to build our community. It is glad to see that more developers joined us and became contributors. But we still need more leading developers to join the community who can participate in the discussion of Doris' road map, not just start-up members. 2. Improve the documents and website as well. Currently, most of documents are in Chinese and most of English docs are translated by machine. We are working on it. 3. The discussion on dev mail list is still very few. Most of discussion and decisions are still make in private or in GitHub issues. We should improve the utilization of mailing lists and discuss more public. ### 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? Since the last report, we have added 21 contributors and 1 committer. There are currently 79 contributors and 15 committers. More and more companies are considering choosing Doris as their solution, and more people are contributing to Doris. In the past three months, the number of contributors has increased from 58 to the current 79. ### How has the project developed since the last report? The community is working hard to improve the usability and functionality of the product so that more people can use Doris more easily to solve their problems. During this time, a total of 336 commits were merged and 333 issues were created. Our new storage engine refactoring is almost coming to an end. After this work, some exciting features can be added, such as secondary index, etc. ### 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: 2019-10-29: Apache Doris (incubating) 0.11.0 ### When were the last committers or PPMC members elected? Hangyuan Liu: New Committer 2020-01-17 ### Have your mentors been helpful and responsive? All mentors are helpful. ### Is the PPMC managing the podling's brand / trademarks? To the best of our knowledge, yes. * Are 3rd parties respecting and correctly using the podlings name and brand? As far as we know, yes. * If not what actions has the PPMC taken to correct this? Nothing to do. * Has the VP, Brand approved the project name? Name is approved ### Signed-off-by: - [X] (doris) Dave Fisher Comments: Need to engage with podling to work on dev@ more along with convert more contributors into committership. - [X] (doris) Willem Ning Jiang Comments: Put some efforts on the documentation and website can lower the bar for the new contributors to join. - [ ] (doris) Shao Feng Shi Comments: ### IPMC/Shepherd notes: -------------------- ## ECharts ECharts is a charting and data visualization library written in JavaScript. ECharts has been incubating since 2018-01-18. ### Three most important unfinished issues to address before graduating: 1. Status page ( https://incubator.apache.org/projects/echarts.html ) has not been updated and we are going to do this within a month. 2. Official Website: We have redirected echarts.baidu.com to echartsjs.com and put a banner in echartsjs.com stating that the official Website is echarts.apache.org but we still need to come to a conclusion about whether CDN still has a problem with the access in China. If so, we should probably make echartsjs.com as a mirror site with a clear specification about the main site. If not, we should redirect echartsjs.com to echarts.apache.org. 3. Currently the collaborator of [echarts npm package](https://www.npmjs.com/package/echarts) is ecomfe and we should move it to echarts. ### 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? More people from the community become contributors, either in the form of answering questions in the issues, fixing the document or making pull requests with the code. We did more public introduction about the community and welcome others to contribute and it did show some positive effects recently. ### How has the project developed since the last report? The monthly release became quite on time recently and in each release, we have several pull requests from 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: 2019-12-29 ### When were the last committers or PPMC members elected? 2020.01.15 ### Have your mentors been helpful and responsive? Yes, mentors are very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [X] (echarts) Kevin A. McGrail Comments: Looking forward to a graduation readiness review/exercise - [X] (echarts) Dave Fisher Comments: Definitely nearing graduation - [ ] (echarts) Ted Liu Comments: - [X] (echarts) Sheng Wu 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. Fixing issues with licensing in the repo. [mostly done] 2. Improving the amount of community discussion on the dev@ mailing list. 3. n/a ### 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 is gradually growing. - Monthly meetups have been regularly and successfully organized. ### How has the project developed since the last report? There have been bug fixes and feature improvements - Creation of the website publishing scripts and jenkins job - Python3 upgrade - Library updates - UI improvements - License fixes ### 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 - [X] Nearing graduation - [ ] Other: ### Date of last release: 2019-11-14 ### When were the last committers or PPMC members elected? - Two new committers were added: - Dmitry Rusakov: Nov 25, 2019 - Nick Nezis: Jan 29, 2020 - Three new PPMC members were elected and invited on Nov 14, 2019 - Ning Wang - Josh Fischer - Sree Vaddi ### Have your mentors been helpful and responsive? - Our mentor has been helpful and responsive ### 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: The project's new PPMC members are engaged and helping move towards graduation. ### 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? None. ### How has the community developed since the last report? A vote by the Milagro community to accept Kirk Baird as a new committer is in progress. Once complete, the formal process to add him will be undertaken. ### How has the project developed since the last report? The first release (0.1.0) of the Decentralized Trust Authority (D-TA) server was successful and the Milagro website updated with D-TA documentation and official download links. A second release of the Crypto-C library (2.0.1) has just been voted on successfully by the IPMC. The Apache Way for this release is still to be completed (update website, formal [ANNOUNCE] email etc.) A proposal for Qredo do submit a new "Multi Party Computation" library to the Milagro project has been accepted by the Milagro community. A software grant has been submitted to Apache and the formal process to add the repo to Apache's GitHub is underway. ### 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-10-04 ### When were the last committers or PPMC members elected? June 2019 ### Have your mentors been helpful and responsive? The community received helpful feedback from our mentors on our releases and the feedback is being actioned. ### Is the PPMC managing the podling's brand / trademarks? No known issues, but further investigation required by the Milagro community. ### Signed-off-by: - [X] (milagro) Nick Kew Comments: Too late to amend, but I just noticed the last release date is nonsense. I (and likely the report) at first confused it with the current release, announced Feb.10. - [X] (milagro) Jean-Frederic Clere Comments: ### IPMC/Shepherd notes: -------------------- ## Myriad Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together on the same cluster and allows dynamic resource allocations across both Hadoop and other applications running on the same physical data center infrastructure. Myriad has been incubating since 2015-03-01. ### Are there any issues that the IPMC or ASF Board need to be aware of? The Myriad community, included the active PPMC have decided the retirement of Myriad from Incubator. The vote was ratified by IPMC members: https://lists.apache.org/thread.html/ra5e731389018b6a398362b34142ea5a2f9c0 19f4b8802376b080a9ec%40%3Cgeneral.incubator.apache.org%3E ### How has the community developed since the last report? Only activity for the retirement. ### How has the project developed since the last report? No development activity. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [X] Other: Retirement process. ### Date of last release: 2019-03-25 ### Have your mentors been helpful and responsive? No answer. ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [ ] (myriad) Benjamin Hindman Comments: - [x] (myriad) Ted Dunning Comments: ### IPMC/Shepherd notes: -------------------- ## NuttX NuttX is a mature, real-time embedded operating system (RTOS) with emphasis on standards compliance and small footprint. NuttX has been incubating since 2019-12-09. ### Three most important unfinished issues to address before graduating: 1. Clear any potential infringing use of the NuttX trademark 2. Determine the form and location of NuttX releases 3. Make the first release under Apache ### 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? * Most communications have moved from old venues to dev@nuttx.apache.org. Some users are still accustomed to the google group but they are getting redirected to the dev list. * Last year, the first International NuttX Workshop (NuttX 2019) was held in Gouda, Netherlands. The second NuttX workshop (NuttX 2020) is in preparation and will be hosted by Sony in Tokyo, Japan. * The PPMC has seen a new addition. The roster now contains 14 members. ### How has the project developed since the last report? * Contributions are flowing regularly as PRs in GitHub and as patches in the dev list. These are handled by committers through an "unofficial" workflow. Our official workflow document is nearing completion where details about contributions, reviews and criteria of acceptance are explained. * A new repository has been created, nuttx-testing, that contains the necessary scripts for automated testing. * The website is now accessible at: https://nuttx.apache.org/ ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [X] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: There is yet to be a release for Apache NuttX. However with the help of our mentor Justin, we are working towards accomplishing this. ### When were the last committers or PPMC members elected? Last elected PPMC: * Brennan Ashton: 2020-01-10 ### Have your mentors been helpful and responsive? Mentors are helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? As noted in the last report the name is registered in the US by Gregory Nutt, and no new issue regarding the trademark usage was noted. A podling name search is yet to be done to get the Brand Management VP approval. ### Signed-off-by: - [ ] (nuttx) Junping Du Comments: - [X] (nuttx) Justin Mclean Comments: - [X] (nuttx) Mohammad Asif Siddiqui Comments: - [X] (nuttx) Flavio Paiva Junqueira Comments: ### IPMC/Shepherd notes: -------------------- ## Pinot Pinot is a distributed columnar storage engine that can ingest data in real- time and serve analytical queries at low latency. Pinot has been incubating since 2018-10-17. ### Three most important unfinished issues to address before graduating: 1. Activity on the mailing list. Most of the discussion happens on pinot slack channel 2. Pinot has close to 200 members on the slack channel. We asked users to join the mailing list but very few did. 3. We are planning to write slack hooks to post discussion summary in the slack channel to the mailing list. ### Are there any issues that the IPMC or ASF Board need to be aware of? 1. Most Apache projects have slack channels, is there any effort from IPMC to formally recognize project slack channel as a first-class citizen. 2. If there is any interest, the Pinot Podling can volunteer to drive this effort. ### How has the community developed since the last report? 1. The usage of Pinot is growing and we have close to 200 users on slack 2. Voted Sidd as a new committer. 3. Pinot has close to 100 contributors ### How has the project developed since the last report? 1. 100+ commits in the last 3 months. 2. Lots of new features were added and working towards 1.0 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 - [x] Nearing graduation - [ ] Other: ### Date of last release: 2019-11-22 ### When were the last committers or PPMC members elected? 2020-01-08 ### Have your mentors been helpful and responsive? No answer. ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [X] (pinot) Kishore Gopalakrishna Comments: - [X] (pinot) Jim Jagielski Comments: - [X] (pinot) Olivier Lamy Comments: what about moving the slack channel to ASF slack? - [X] (pinot) Felix Cheung Comments: ### IPMC/Shepherd notes: Justin Mclean: While Slack its a useful tool it should not replace asynchronous communication. If the project wants to try an experiment please discuss with the incubator to work out the details. Justin Mclean: This report is a bit minimal, and you failed to answer some questions can you please include more detail next time. -------------------- ## Ratis Ratis is a java implementation for RAFT consensus protocol Ratis has been incubating since 2017-01-03. ### Three most important unfinished issues to address before graduating: 1. Graduation template needs more work. 2. Podling name search needs to be completed. 3. Expand the community, committers and PPMC. ### 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? 4 new contributors. 69 contributors in total. ### How has the project developed since the last report? 40 new commits. Discussion for 0.5.0 release started. ### 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 - [X] Nearing graduation - [ ] Other: ### Date of last release: 2019-09-19 ### When were the last committers or PPMC members elected? - 09/11/2019 - Ankit Singhal as Committer - 09/13/2019 - Shashikant Banerjee as PPMC member ### Have your mentors been helpful and responsive? No answer ### Is the PPMC managing the podling's brand / trademarks? No answer ### Signed-off-by: - [X] (ratis) Jakob Homan Comments: Community is ready for graduation; still needs to do some Incubator paperwork, would be good to see progress on that. - [X] (ratis) Uma Maheswara Rao G Comments: - [ ] (ratis) Devaraj Das Comments: ### IPMC/Shepherd notes: Justin Mclean: This report is a lacking in detail, and you failed to answer some questions can you please include more detail next time. -------------------- ## S2Graph S2Graph is a distributed and scalable OLTP graph database built on Apache HBase to support fast traversal of extremely large graphs. S2Graph has been incubating since 2015-11-29. ### Three most important unfinished issues to address before graduating: 1. Make the third release. 2. Attract more users and contributors. 3. Build the developer community in both size and diversity. ### 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? 1. Not much activities 2. One new contributor joined in community by submitting the PR(S2GRAPH-255). ### How has the project developed since the last report? 1. S2GRAPH-15(merged): S2Lambda, speed and batch layers of the lambda architecture 2. S2GRAPH-255(under review): Enable incremental processing of s2jobs ### 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-08-26 ### When were the last committers or PPMC members elected? 2019-02-05 ### Have your mentors been helpful and responsive? Our mentor is very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [ ] (s2graph) Sergio Fernández Comments: - [X] (s2graph) Woonsan Ko Comments: most active committers have been busy with their daily jobs; but reviewing and accepting PRs from community. ### IPMC/Shepherd notes: Justin Mclean: Please make sure to answer all questions. -------------------- ## 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? No. ### How has the community developed since the last report? We are continuing to attract new committers. A NASA-sponsored project to build a cloud workflow for sea ice and ocean circulation data, in development at JPL, is adapting SDAP for its analytics platform. Reference: T. Huang, M. DeBellis, I. Fenty, P. Heimbach, J. C. Jacob, O. Wang, E. Yam, "Analytics Center Framework for Estimating the Circulation and Climate of the Ocean," 39th IEEE Geoscience and Remote Sensing Symposium, Jul-Aug 2019, doi: 10.1109/IGARSS.2019.8897904. ### How has the project developed since the last report? Development of a helm chart for use when deploying to kubernetes has been opened as a PR. Further development work has continued and existing installations are being maintained. ### 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: XXXX-XX-XX ### When were the last committers or PPMC members elected? Maya Debellis was elected as a committer on 2019-02-08 ### Have your mentors been helpful and responsive? Mentors are helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? PPMC is not managing the podling's brand or trademarks. ### Signed-off-by: - [ ] (sdap) Jörn Rottmann Comments: - [X] (sdap) Trevor Grant Comments: Need to start working towards release. Let me know if I can help- I may have some cycles in upcoming months. ### IPMC/Shepherd notes: -------------------- ## StreamPipes StreamPipes is a self-service (Industrial) IoT toolbox to enable non- technical users to connect, analyze and explore (Industrial) IoT data streams. StreamPipes has been incubating since 2019-11-11. ### Three most important unfinished issues to address before graduating: 1. Finish license review of third-party dependencies 2. Make a first Apache release 3. Grow the community ### Are there any issues that the IPMC or ASF Board need to be aware of? There are no issues right now. ### How has the community developed since the last report? In the last month, our focus was on setting up some structures that help growing the community: * Further people appeared on the mailing list expressing their interest to develop StreamPipes components * We added issues in Jira that are targeted at new developers (marked with a newbie tag) * We migrated the previously internal Wiki to Confluence and added developer information to lower the entry barrier to contribute * Blog post on how to run StreamPipes on a Raspberry Pi, we now plan to publish blog posts at regular intervals * Contact to sensor producer, and first integrations with their sensors, which should help growing the ecosystem * Meeting with a manufacturing company to present StreamPipes and talk about cooperation possibilities * We started to plan ApacheCon talks (also a joint talk together with Apache PLC4X) * The number of Twitter followers has increased (currently at 103) * The number of Github stars has increased (currently at 109) ### How has the project developed since the last report? * Successfully migrated complete development cycle to new GitHub and Docker Hub repositories * Optimized containers to run on ARM architectures * Implemented further algorithms to merge data streams and pre-process data for machine learning tasks * Checking licences of the UI and adding checklist to Wiki * Checking licenses of the backend and populated the LICENSE-binary file * Currently, we are finishing a license review to properly create LICENSE and NOTICE files In the next month, we plan to continue our work towards the first Apache release. ### 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? No new committers were elected beyond the initial committers. Two people mentioned on the mailing list that they might be willing to contribute to StreamPipes. ### Have your mentors been helpful and responsive? Our mentors are very responsive and provide good feedback. We discovered an issue that some mentors are not subscribed to the private mailing list and got in contact with them to fix this issue. ### Is the PPMC managing the podling's brand / trademarks? * We are currently preparing a new logo * Currently, no issues are known related to brand misuse, but there are still some open issues concerning the transition to the ASF infrastructure (e.g., shutting down the old streampipes organization on Github to avoid confusion) * We've started to research best-practices related to brand management (other ASF projects) and intend to add a section in the Confluence Wiki on brand management. ### Signed-off-by: - [X] (streampipes) Christofer Dutz Comments: - [ ] (streampipes) Jean-Baptiste Onofré Comments: - [X] (streampipes) Julian Feinauer Comments: - [X] (streampipes) Justin Mclean Comments: - [ ] (streampipes) Kenneth Knowles Comments: ### IPMC/Shepherd notes: -------------------- ## Tamaya Tamaya is a highly flexible configuration solution based on an modular, extensible and injectable key/value based design, which should provide a minimal but extendible modern and functional API leveraging SE, ME and EE environments. Tamaya has been incubating since 2014-11-14. ### Three most important unfinished issues to address before graduating: 1. Gain more active contributors and committers 2. Decide how to ensure future development of Tamaya 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? Since we lack a lot of committers and contributors we started a discussion on the mailing list about the future of the project. One way might be to let the code return to Github instead of becoming a TLP - it's an ongoing discussion with no decision yet. ### How has the community developed since the last report? No changes in the project. ### How has the project developed since the last report? We released version 0.4-incubating and continue working on changes in upcoming 0.5. ### 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: 2019-11-11 0.4-incubating ### When were the last committers or PPMC members elected? * 2018-12: Aaron Coburn * 2018-12: William Lieurance ### Have your mentors been helpful and responsive? Julian took part in the discussion about the Tamaya's future. ### Is the PPMC managing the podling's brand / trademarks? No answer ### Signed-off-by: - [x] (tamaya) John D. Ament Comments: Tamaya is currently discussing its next steps. We may need to prod that conversation along a bit to ensure that it can be resolved in a way that allows the podling to move past their current blockers. - [ ] (tamaya) David Blevins Comments: - [ ] (tamaya) Kanchana Pradeepika Welagedara Comments: - [X] (tamaya) Julian Feinauer Comments: I wrote an email to incubator private to inform about the discussion, some weeks ago. Lets see how the discussion ends. ### IPMC/Shepherd notes: Justin Mclean: Please make sure to answer all questions. -------------------- ## 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 2. 3. ### 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? The community is preparing for the 0.4.0 release and a few contributors have provided pull requests with additions to the release. ### How has the project developed since the last report? The release preparation has provided slightly increased level of community contributions. ### 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: 2018-11-13 ### 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? There was nothing requiring mentor intervention on the last quarter. ### Is the PPMC managing the podling's brand / trademarks? No Trademark issues ### Signed-off-by: - [X] (toree) Luciano Resende Comments: - [ ] (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. Promote the information about Apache Training Project with increased participation from community 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? - There currently is a lack of involvement by the PPMC in the project which caused stagnation in mailing list participation and overall project progress. The PPMC is currently taking steps to address this by focusing on promoting new committers and being more involved again. - The current review and release process seems to be overly complex and scary and hampers contributions. Discussions around relaxing this are ongoing. ### How has the community developed since the last report? Activity on the dev list has declined since the last report, total number of posts was November 37, December 13, January (to be updated) 84. ### How has the project developed since the last report? - We have refactored the Maven structure to make adding new projects much easier by using an archetype, this should help make the project more accessible to a lot of people. - ApacheCon themed templates are under development that will be available for speakers at future conferences - An introductory Hadoop slide deck was contributed and is currently undergoing review. ### 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: ### Date of last release: No new releases as ongoing discussions around the Pixabay license in LEGAL-479 have been blocking releases for months now. ### When were the last committers or PPMC members elected? Voting is currently ongoing to add a new committer to the projects roster. ### 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: - [ ] (training) Craig Russell Comments: - [X] (training) Christofer Dutz Comments: - [X] (training) Justin Mclean Comments: - [X] (training) Lars Francke Comments: ### IPMC/Shepherd notes: -------------------- ## TubeMQ TubeMQ is a distributed messaging queue (MQ) system. TubeMQ has been incubating since 2019-11-03. ### Three most important unfinished issues to address before graduating: 1. Launch the first Apache release. 2. Make development document more easily to read 3. Grow the community to involve more contributors and increase the diversity. ### 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? Currently the project is still on migrating, a few contributions in the bug reports and pull requests are offered on the repository. We hosted 1 below-the-line meetups to promote this project. ### How has the project developed since the last report? Towards migrating to Apache incubator, we submitted SGA, builded home pages, all PPMC’s apache id, icla, roster are ready. Some things are being worked on, such as ensuring that all PPMCs join private mailing lists, adjusting project packages, etc. We are leading everyone to communicate via email, Jira(not just IM). ### 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: None ### When were the last committers or PPMC members elected? None ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? Still on migrating. ### Signed-off-by: - [X] (tubemq) Junping Du Comments: Overall looks good. Next time if there is community meetup, we'd better to notice everyone on dev mail list. - [X] (tubemq) Justin Mclean Comments: Needed a little help of getting the report together. Try to keep offlist communication to a minimum and bring things back to the mailing list. - [ ] (tubemq) Sijie Guo Comments: - [ ] (tubemq) Zhijie Shen Comments: - [ ] (tubemq) Jean-Baptiste Onofre 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. Finish export notice for cryptographic elements 2. Build a diverse community 3. Ship a few items on the roadmap (see below) ### Are there any issues that the IPMC or ASF Board need to be aware of? No issues to report at this time. ### How has the community developed since the last report? We are seeing a few contributions in the bug reports and pull requests offered on the repository. The project is starting to gain good traction. ### How has the project developed since the last report? The project has released a new maintenance release (0.10.0). It is now working now on its next major release, moving to support Java 11+. Releasing is less and less of a daunting task now - with some automation and documentation, one can issue a release without fear of missing bits anymore. ### 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: The podling is building its community. As part of this board report, we moved to using Confluence to draft the report together before submitting it. We also drafted a set of stories and use cases as a roadmap with the goal of using this to also build the community: https://cwiki.apache.org/confluence/display/TUWENI/Roadmap ### Date of last release: 2019-11-30 ### When were the last committers or PPMC members elected? Gordon Martin as committer on 2019-08-01. ### Have your mentors been helpful and responsive? No problem to report. ### Is the PPMC managing the podling's brand / trademarks? Yes. At present, there are no issues nor concerns with the Tuweni mark. We do not anticipate any issues with the mark regarding graduation. ### Signed-off-by: - [X] (tuweni) Jim Jagielski Comments: - [ ] (tuweni) Jean-Baptiste Onofré Comments: - [X] (tuweni) Michael Wall Comments: Maybe we should review https://incubator.apache.org/guides/community.html for some ideas on community building. - [X] (tuweni) Furkan Kamaci Comments: ### IPMC/Shepherd notes: ----------------------------------------- Attachment AE: Report from the Apache Joshua Project [Tommaso Teofili] ----------------------------------------- Attachment AF: 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 (9 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 Jan 11, 2020, primarily bug fixes. Next released planned for next no later than March to resolve additional bugs fixes and dependency updates. - 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. However there has been a recent uptick due to user feedback and problem reporting. - There has been some new feature development recently related to enhanced security and access control mechanisms. - There are enough active PMC members to approve releases and respond to potential security issues. ## Releases: - 3.3.7 was released on Jan 11 2020 - SCOUT-1.2.8 was released on Mon Dec 10 2018 ## JIRA activity: - 6 issues opened in JIRA, past quarter (600% increase) - 12 issues closed in JIRA, past quarter (1200% increase) ## Commit activity: - 21 commits in the past quarter (2100% increase) - 1 code contributor in the past quarter (100% increase) ----------------------------------------- Attachment AG: 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: No issues to report at this time. ## Membership Data: Apache Juneau was founded 2017-10-17 (2 years ago) There are currently 12 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - 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: - 8.1.2 was released on 2019-12-01 - 8.1.3 was released on 2020-01-20 - Currently have an Outreachy intern working on the project. ## Community Health: Activity has been about average for the project. - 18 issues opened in JIRA, past quarter (-48% decrease) - 16 issues closed in JIRA, past quarter (-38% decrease) - 115 commits in the past quarter (43% increase) - 3 code contributors in the past quarter (-25% decrease) ----------------------------------------- Attachment AH: Report from the Apache Kafka Project [Jun Rao] Apache Kafka is a distributed event streaming platform for efficiently storing and processing a large number of records in real time. Development =========== We released 2.4.0, which includes the following new features: - Allow consumers to fetch from closest replica - Support for incremental cooperative rebalancing to the consumer rebalance protocol - MirrorMaker 2.0 (MM2), a new multi-cluster, cross-datacenter replication engine - New Java authorizer Interface - Support for non-key joining in KTable - Administrative API for replica reassignment - Securing Internal connect REST endpoints - API to delete consumer offsets and expose it via the AdminClient. We also released 2.2.2, which fixes more than 30 issues. Community =========== Lots of activities in the mailing list. We had 2,203 emails in the dev mailing list, 15% less than the last 3 months, likely due to the holiday season. We had 814 emails in the in the user mailing list, 18% more than the last 3 months. We had 2,963 JIRA activities, 7% less than the last 3 months. We added 3 new PMC members, Colin McCabe, Manikumar Reddy and Vahid Hashemian in January, 2020. We didn't add any new committers in the last 3 months. We last added a new committer on Nov. 11, 2019. We plan to have 2 Kafka Summits in 2020, London on Apr. 27/28 and Austin on Aug. 24/25. Releases =========== 2.4.0 was released on Dec. 16, 2019. 2.2.2 was released on Dec. 1, 2019. ----------------------------------------- Attachment AI: Report from the Apache Kibble Project [Rich Bowen] ## 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. ## Membership Data: Apache Kibble was founded 2017-10-17 (2 years ago) There are currently 12 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Rafael Weingärtner on 2017-12-08. - No new committers. Last addition was Rafael Weingärtner on 2017-12-09. ## Project Activity: Sharan gave a 20 minute talk[1] at chaosscon[2] (one of the events in the FOSDEM Fringe - events surrounding FOSDEM in Brussels) featuring kibble. We got lots of interest especially around the sentient analysis. Chaoss are keen to include kibble but we need to do the work to highlight how we align (or not) to the Chaoss definitions. ## Community Health: The community is healthy, although still small, and struggling to add new members. We continue to have a great deal of interest at events, but that doesn't often result in actual new contributors. Meanwhile, the project has sufficient oversight and continues steady forward progress. [1] https://chaoss.github.io/website/CHAOSScon/2020EU/slides/Measuring-Culture.pdf [2] https://chaoss.community/chaosscon-2020-eu/ ----------------------------------------- Attachment AJ: Report from the Apache Knox Project [Larry McCay] ## Description: The mission of Knox is the creation and maintenance of software related to Simplify and normalize the deployment and implementation of secure Hadoop clusters ## Issues: There are no issues requiring board attention ## Membership Data: Apache Knox was founded 2014-02-18 (6 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: - Sandor Molnar was added to the PMC on 2019-11-20 - Sandor Molnar was added as committer on 2019-11-21 ## Project Activity: - Planning for the Apache Knox 1.4.0 release has begun and continues with the approach of using KIPs to communicate larger design and feature changes and goals. - This release has been in the works for longer than anticipated but will land within a matter of weeks. - We plan to concentrate on the client library and shell for interacting with remote Knox instances/Hadoop clusters and Cloudera Manager based service discovery. - 1.3.0 was released on 2019-07-23. - 1.2.0 was released on 2018-12-18. ## Community Health: There does seem to be an uptick in use of Apache Knox in Hadoop and other big data deployments across the industry. We have received contributions from new contributors with varying sizes and level of impact. Pull requests are a relatively new mechanism for the Knox community which explains the large increase over previous quarters. The large increase in email traffic on the dev list is likely a result of additional traffic from github PR activity and commits. - dev@knox.apache.org had a 21% increase in traffic in the past quarter (2194 emails compared to 1813): - user@knox.apache.org had a 32% decrease in traffic in the past quarter (24 emails compared to 35): - 102 issues opened in JIRA, past quarter (-28% decrease) - 105 issues closed in JIRA, past quarter (-27% decrease) - 97 commits in the past quarter (-37% decrease) - 13 code contributors in the past quarter (-38% decrease) - 63 PRs opened on GitHub, past quarter (-5% decrease) - 62 PRs closed on GitHub, past quarter (-4% decrease) ----------------------------------------- Attachment AK: 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: No issue need board's attention; ## Membership Data: Apache Kylin was founded 2015-11-18 (4 years ago) There are currently 39 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - Chunen Ni was added to the PMC on 2019-11-26 - Xiaoxiang Yu was added as committer on 2019-12-27 - Temple Zhou was added as committer on 2019-11-14 ## Project Activity: Recent releases: 3.0.0 was released on 2019-12-18. 3.0.0-beta was released on 2019-10-24. 2.6.4 was released on 2019-10-12. As across the year-end and beginning, there is no Meetup event in the past 3 months; But we have several online webinars to share the Kylin tutorial and user scenarios, which attracts more than 100 audiences each time. ## Community Health: - dev@kylin.apache.org had a 7% increase in traffic in the past quarter (316 emails compared to 294) - issues@kylin.apache.org had a 33% increase in traffic in the past quarter (2686 emails compared to 2011) - 120 issues opened in JIRA, past quarter (no change) - 96 issues closed in JIRA, past quarter (-33% decrease) - 343 commits in the past quarter (76% increase) - 51 code contributors in the past quarter (34% increase) - 161 PRs opened on GitHub, past quarter (12% increase) - 174 PRs closed on GitHub, past quarter (41% increase) The community is still actively growing; In Dec. of 2019 we just released the new Kylin 3.0 version, we're looking forward to attracting more users to Kylin! ----------------------------------------- Attachment AL: Report from the Apache Lens Project [Amareshwari Sriramadasu] ## Description: Lens provides an Unified Analytics interface. Lens aims to cut the Data Analytics silos by providing a single view of data across multiple tiered data stores and optimal execution environment for the analytical query. It seamlessly integrates Hadoop with traditional data warehouses to appear like one. ## Issues: There are no issues requiring board attention ## Membership Data: Apache Lens was founded 2015-08-19 (4 years ago) There are currently 23 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 Puneet Gupta on 2016-09-20. - No new committers. Last addition was Rajitha R on 2018-02-09. ## Project Activity: No changes done during last quarter. We are awaiting changes for the project, as proposed in roadmap discussion last quarter. ## Community Health: There is no change in contributors and overall activity is low, as seen in earlier quarter. ----------------------------------------- Attachment AM: 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. ## Project Activity Since the last report, we had two releases with major new changes and improvements. If no major issues are reported with v3.0.0-rc1 release, we will release stable v3.0.0 version in the near future (first version which drops support for Python 2). ## Community Health Community state is similar to the one in the last report - we received a decent amount of activity on Github. We also received a good amount of downloads / installations on PyPi (primary method of installing the library) - https://pypistats.org/packages/apache-libcloud. ## Membership Data - Currently 13 PMC members. - No new PMC members added in the last 3 months - Currently 22 committers. - Clemens Wolff was added as committer on 2019-07-15 ## Releases - 3.0.0-rc1 was released on January 29, 2020 - 2.8.0 was released on January 2, 2020 ----------------------------------------- Attachment AN: 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 (16 years ago) There are currently 35 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 5:2. Community changes, past quarter: - No new PMC members. Last addition was Carter Kozak on 2018-07-29. - No new committers. Last addition was Andrei Ivanov on 2019-04-18. ## Project Activity: - In November, we received increased interest and contributions to log4php and log4net. - In November, we continued discussions around the plugin dependency injection overhaul and learned some lessons from various CDI implementations. - In December, we released Log4j 2.13.0 which is the first Log4j 2 release that requires Java 8. Other notable features in this release include backward compatibility with Log4j 1 properties and XML configuration files, new configuration integrations with Kubernetes and Spring Boot, a new logger builder API, additional message sub-layout configuration for GELF layouts, and numerous bug fixes and pull requests. - In December, we announced CVE-2019-17571 for Log4j 1.x as a deserialization of untrusted data vulnerability in the log socket server. This is announced without a fix as the 1.x release line was EOLed in August 2015. A similar vulnerability was announced a couple years ago in Log4j 2.x in CVE-2017-5645. - In December, we turned back to discussing what else is necessary for Log4j 3.0. Some main changes considered include improved compatibility with the Java module system in Java 9+ along with trimming down the size of the core jar due to finer grained modules, an overhauled plugin system making plugin development more comparable to common dependency injection frameworks, backward-compatible API housekeeping, and a consideration around what level of backward compatibility is expected for this release line which concluded with a desire to continue backward compatibility with the 2.x API. - In January, we received contributions from a couple new people for log4cxx including a build system simplification toward using CMake. - In January, we began conversations with a contributor who is working on merging their highly customizable Logstash/JSON layout project into Log4j. - In January, we received a contribution fixing our Travis build. This has led to discussions around the possibility of trying out GitHub Actions as a PR tester replacement in the future. ## Community Health: - Renewed interest in log4php in improving its website and other rough edges. - Doubling of dev@ mailing list traffic thanks to increased interest in all of Log4j, log4cxx, and log4php. - Large increases in email, commit, and PR traffic this quarter (all at least doubled from last quarter). This was partially to be expected due to a decrease in traffic last quarter. ----------------------------------------- Attachment AO: Report from the Apache ManifoldCF Project [Karl Wright] Project description ============== ManifoldCF is an effort to provide an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr, OpenSearchServer or ElasticSearch. ManifoldCF also defines a security model for target repositories that permits them to enforce source repository security policies. Releases ======== ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then, there have been numerous major releases, including a 2.15 release on December 25, 2019. The next major release is due on April 30, 2020. Committers and PMC membership ============================= 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. There are two prospects who we may ask in the near future. We are still not 100% done with the newest OpenText replacement connector; some installations aren't able to connect and we're trying to diagnose why. It's a long process because of the lack of local installations for these repositories available directly to our team. Other connectors that will be requiring this level of work in the near future include the SharePoint connector, which suffers from the same issue. We continue to rely on early adopters to co-develop these connectors with us. Mailing list activity ===================== Mailing list activity has been fairly active this quarter. Requests for connector development continue to be significant. I am unaware of any mailing list question that has gone unanswered. ----------------------------------------- Attachment AP: Report from the Apache Marmotta Project [Jakob Frank] ----------------------------------------- Attachment AQ: 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-18 (5 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-28. - No new committers. Last addition was Jörg Unbehauen on 2018-05-03. ## Project Activity: Low activity in general. New releases have been managed by Arjan Seijkens, not by the PMC chair, which is a nice change and good to get more involvement. ## Community Health: The community isn't very active and we're mostly just adding maintenance updates or smaller improvements. Whether this is a problem or not is not quite sure - the project may not evolve a whole lot more, but still offers value to it's users. ----------------------------------------- Attachment AR: 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 (7 years ago) There are currently 25 committers and 22 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - Andras Salamon was added to the PMC on 2020-01-07 - No new committers. Last addition was Andras Salamon on 2019-02-14. ## Project Activity: - 5.2.0 release is out with Java11 support. - Development is slow, mostly updates in dependencies, bugs and minor improvements - There are plans to upgrade some major dependencies soon (Pig, Hadoop, Hive) ## Community Health: There are some new contributors showing up and we're prioritizing reviews for them to keep them motivated. We had contributions from 11 people, most of them were first commits. dev@oozie.apache.org had a 12% increase in traffic in the past quarter (605 emails compared to 537) user@oozie.apache.org had a big increase in traffic in the past quarter (6 emails compared to 0) 27 issues opened in JIRA, past quarter (28% increase) 17 issues closed in JIRA, past quarter (no change) 17 commits in the past quarter (-29% decrease) ----------------------------------------- Attachment AS: Report from the Apache Open Climate Workbench Project [Huikyo Lee] ## Description: - The OCW includes a Python open-source library for common climate model evaluation tasks as well as a set of user-friendly interfaces for quickly configuring a model evaluation task. OCW also allows users to build their own climate data analysis tools, such as the statistical downscaling toolkit. ## Issues: - We could not make any new release last year. Community Health Score (Chi) is -2.65. ## Activity: - We almost completed refactoring and testing OCW by using Xarray and pandas. The refactored code has been released in the main developer’s personal Github repository. ## Health report: - The main developer of the refactored OCW had hard time getting approval to release his development with Apache License. We are also cleaning up some old JIRA issues. We are confident that our Chi will become healthy in coming months. ## PMC changes: - Currently 30 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ibrahim Jarif on Mon Apr 25 2016 ## Committer base changes: - Currently 30 committers. - No new committers added in the last 3 months - Last committer addition was Christopher Douglas at Tue Apr 26 2016 ## Releases: - Last release was 1.3.0 on Mon Apr 23 2018 - dev@climate.apache.org: - 63 subscribers (up 2 in the last 3 months): - 23 emails sent to list (36 in previous quarter) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AT: Report from the Apache OpenNLP Project [Jeffrey T. Zemerick] ## Description: The mission of OpenNLP is the creation and maintenance of software related to Machine learning based toolkit for the processing of natural language text ## Issues: There are no issues requiring board attention. ## Membership Data: Apache OpenNLP was founded 2012-02-14 (8 years ago) There are currently 22 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Koji Sekiguchi on 2017-10-09. - Tim Allison was added as committer on 2020-01-28 ## Project Activity: Recent releases: - 1.9.2 was released on 2019-12-30. New features recently merged include improvements to the language detector, documentation, and general clean up of code. As chair I would like to see OpenNLP have more frequent releases and we will work toward that. ## Community Health: The OpenNLP community remains healthy even though it is not extremely active. The project added a new committer, Tim Allison, who provided valuable contributions to OpenNLP last year. We have quite a few pending pull requests that we are working on merging or asking the authors to update. These short conversations will likely mostly take place directly the on GitHub pull requests and will not be reflected in the OpenNLP mailing list statistics. ----------------------------------------- Attachment AU: 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 (7 months ago) There are currently 48 committers and 20 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 Rob Allen on 2019-07-16. - Shawn Black was added as committer on 2019-11-26 - Cosmin Stanciu was added as committer on 2019-12-06 - PengCheng Jiang was added as committer on 2019-12-02 - Dan McWeeney was added as committer on 2020-01-15 - Duy Nguyen was added as committer on 2020-01-15 - Neeraj Mangal was added as committer on 2020-02-03 ## Project Activity: We are actively working towards a long-awaited next release of the core OpenWhisk system (the last release of the core system was 0.9.0-incubating in 2018-10-31). This will be the first release of our new "standalone" configuration which enables a very simple single machine deployment of OpenWhisk. It will also be the first time the project has released a coherent set of all its releasable software components (currently 22 separate packages). This effort is driving a wave of component releases detailed below. Recent releases: - openwhisk-runtime-docker-1.14.0: 2020-02-11 - openwhisk-runtime-java-1.14.0: 2020-02-11 - openwhisk-runtime-php-1.14.0: 2020-02-11 - openwhisk-runtime-ruby-1.14.0: 2020-02-11 - openwhisk-runtime-swift-1.14.0: 2020-02-11 - openwhisk-client-js-3.21.1: 2020-02-08 - openwhisk-client-js-3.21.0: 2020-02-06 - openwhisk-composer-0.12.0: 2020-01-22 - openwhisk-runtime-go-1.15.0: 2020-01-17 - openwhisk-catalog-0.11.0: 2020-01-07 - openwhisk-runtime-dotnet-1.14.0: 2020-01-07 ## Community Health: Community health is good with plenty of activity on dev list and slack. Statistical metrics (PRs, commits, list traffic, etc.) are stable. The community is working on developing a light-weight process for Proposing Openwhisk EnhanceMents (POEM) to facilitate discussion of proposed architectural changes to the core system. There is a sense that by having a documented series of steps for managing such changes we could increase community involvement and project velocity. ----------------------------------------- Attachment AV: Report from the Apache Perl Project [Philippe Chiasson] --- mod_perl -- mod_perl 2.0.11 was released on October 5th 2019 Since that successfull release, activity has quieted down a bit, as is usually the case. CVE-2011-2767 can be put to rest thanks to that release. -- Activity -- The activity levels went down a little, after a noticeable uptick leading up to the final release. -- Users -- The mod_perl users list is seeing little activity, as usual. Patches and bug reports are few, but keep on coming. -- Commiters -- Currently 22 committers. No new changes to the committer base since last report. Last Commiter addition was Jan Kaluza in April 2013 -- PMC -- Currently 11 PMC members. No new PMC members added in the last 3 months Last PMC addition was Steve Hay on Wed Feb 29 2012 ----------------------------------------- Attachment AW: Report from the Apache Petri Project [Dave Fisher] ## Description: The mission of Apache Petri is the creation and maintenance of software related to assessment of, education in, and adoption of the Foundation's policies and procedures for collaborative development and the pros and cons of joining the Foundation ## Issues: Nothing to report to the Board. ## Membership Data: Apache Petri was founded 2019-11-19 (3 months ago) There are currently 6 committers and 6 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members (project established recently). - No new committers were added. ## Project Activity: Slow to start. The OSS-Bot project has gone quiet due to Lunar New Year and Coronavirus. Will attempt to rekindle discussion next week. Rumblings of a possible project coming soon. ## Community Health: We need to spend some more time on the website. I think we are all mostly distracted by other things occurring in the Foundation. ----------------------------------------- Attachment AX: Report from the Apache Phoenix Project [Josh Elser] ## 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-20 (6 years ago) There are currently 51 committers and 31 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 Chinmay Kulkarni on 2019-09-09. - Andreas Neumann was added as committer on 2019-12-03 - Terence Yim was added as committer on 2019-12-03 - Gokcen Iskender was added as committer on 2020-02-07 - Gokul Gunasekaran was added as committer on 2019-12-03 - Istvan Toth was added as committer on 2019-12-02 - Xinyi Yan was added as committer on 2019-12-26 - Yoni Gottesman was added as committer on 2019-12-03 ## Project Activity: Following up from the previous report, I'm happy to report that both the former podlings Omid and Tephra have been successfully "adopted" under the Apache Phoenix PMC. The PMC voted to grant committership to all PPMC who desired it, transitioned all infrastructure (e.g. Jira projects, Git repositories) under the Phoenix role, and did some basic updates to our public facing user-documentation to make sure our users can be aware of how these (now) sub-projects will continue to exist at the ASF. I'm also happy to report that Phoenix 4.15.0 was released in December. As is normal, we are also approaching a 4.15.1 bug-fix release in that release line. Activity on the 4.x release line continues at the usual cadence thanks to the dedicated work of the committers. On the 5.x release line, we were largely blocked because upstream Apache HBase changes caused us some API and runtime compatibility issues. Thankfully, after some more discussion on the matter, we got traction by a developer to chase down the problem and implement a solution. At this point, we are largely unblocked to work towards a long-overdue 5.1.0 release. ## Community Health: We've added 7 new committers since our last report which is fantastic. We have not, however, added any new committers. We should take this as an action item as a project. I find the mailing list traffic largely status quo; user lists have a drop year-over-year but the dev and issues list have an increase of a similar percentage magnitude year-over-year. In general, I observe a steady stream of user questions and developers created and resolving Jira issues. ----------------------------------------- Attachment AY: 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 (13 years ago) - There are currently 39 committers and 32 PMC members in this project. - The Committer-to-PMC ratio is roughly 5:4. - Community changes, past quarter: - Axel Howind was added to the PMC on 2019-11-11 - Axel Howind was added as committer on 2019-11-12 ## Project Activity: - Some feature development in the area of HSLF/XSLF, mostly rendering of slides and support for more image formats. Also some charting enhancements. Otherwise mostly bugfixes, file-leaks fixed, Sonar issues resolved, ... Release 4.1.2 is currently finalized and should be available soon. Some testing of JDK 14 was performed to ensure newer JDK versions work as well. ## Community Health: - There are some ongoing discussions with users about features/behavior which indicates that the popularity of Apache POI is still high. Questions via email or on Stackoverflow usually get answers quickly. There is steady activity from multiple committers, 4.1.2 will contain commits from at least 6 different developers. We still should broaden the developer base but not many potential committers show up on the mailing lists currently. This time the holidays helped to resolve some bugs, however in general bug-numbers unfortunately increase steadily, some bug influx and some could be fixed, but overall the rate of creation is higher than resolving, also due to some invalid bugs being entered which need lots of time to be analyzed/triaged as well. ### XMLBeans - Nearly no changes for XMLBeans this quarter, the project is in maintenance mode. Bug influx for XMLBeans is very low because it is a stable project in maintenance-mode. ## Bugzilla Statistics: ### Apache POI - 564 bugs are open overall (+-0) - Having 158 enhancements (+4) - Thus having 406 actual bugs (-4) - 96 of these are waiting for feedback (+7) - Thus having 310 actual workable bugs (-11) - 4 of the workable bugs have patches available (-1) - Distribution of workable bugs across components: {XSSF=86, HSSF=83, SS Common=41, HWPF=35, XWPF=20, SXSSF=11, POI Overall=10, XSLF=7, POIFS=4, HPSF=3, HSMF=3, OPC=3, HPBF=1, HSLF=1, SL Common=1, XDDF=1} ### Apache XMLBeans - 177 open issues (+1) - Bug 131 (+1) - Improvement 22 (+-0) - New Feature 19 (+-0) - Wish 4 (+-0) ----------------------------------------- Attachment AZ: 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 Broker-J 7.1.6 was released on 5th December 2019. - Qpid Proton-J 0.33.3 was released on 6th December 2019. - Qpid JMS 0.48.0 was released on 10th December 2019. - Qpid Proton 0.30.0 was released on 13th December 2019. - Qpid Dispatch 1.10.0 was released on 20th December 2019. - Qpid Broker-J 7.1.7 was released on 14th January 2020. # 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 committer additions in this quarter. The most recent new committer is Ben Hardesty, added on 20th Sept 2019. - There were no new PMC additions in this quarter. The most recent new PMC member is Ganesh Murthy, added on 30th Jan 2017. # Development: - Dispatch router had a 1.10.0 release including various bug fixes and improvements, some in concert with Proton changes below. Work on more continues toward a 1.11.0 release. - Proton-C and its language bindings had their 0.30.0 release, incorporating various bug fixes and improvements around reducing memory usage. Work on more updates toward a 0.31.0 release continues. - Broker-J had its 7.1.6 and 7.1.7 releases, including various bug fixes and improvements. Work continues on more toward an 8.0.0 release, with backports to the 7.1.x line as appropriate. A candidate for a 7.1.8 release is currently under vote. - The AMQP 1.0 JMS client had its 0.48.0 release containing a few bug fixes and work continues on more. - Proton-J had a 0.33.3 bug fix release, with more fixes and improvements occurring as needed for its various dependent components. # Issues: There are no Board-level issues at this time. ----------------------------------------- Attachment BA: Report from the Apache REEF Project [Sergiy Matusevych] ## Description: - Apache REEF (Retainable Evaluator Execution Framework) is a library for developing portable applications for cluster resource managers such as Apache Hadoop YARN or Apache Mesos. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Reviewed and updated the dependencies for the entire project, removed duplicate/shadowed imports and fixed the code to match the new APIs. - Will issue a minor release once we finish testing the new updates. - Finishing work on .Net elastic broadcast. Planning a new major release this year. ## Health report: - The engagement from the community has been declining perhaps because the codebase has been stable. - There's new activity towards an upcoming minor release (PRs pending review). - Work continues in the elastic broadcast pull request (600+ comments/fixes). There was a delay in this effort due to the principal committer's paternity leave; We will resume that work after publishing a minor release of REEF. - We plan to issue a new major release as soon as we merge the elastic group communication into master. ## PMC changes: - Currently 22 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Doug Service on Thu Sep 28 2017 ## Committer base changes: - Currently 35 committers. - No new committers added in the last 3 months - Last committer addition was Scott Inglis at Thu Sep 27 2018 ## Releases: - Last release was 0.16 on Wed Aug 09 2017. - Release 0.16.1 planned for February 2019. - Release 0.17 planned before July 2020. ## Mailing list activity: - dev@reef.apache.org: - 86 subscribers (up 0 in the last 3 months) - 1150% increase in traffic in the past quarter (25 emails compared to 2) - user@reef.apache.org: - 20 subscribers (up 0 in the last 3 months) - 0 emails sent to list (0 in previous quarter) ## JIRA activity: - 4 issues opened in JIRA, past quarter (300% increase) - 2 issues closed in JIRA, past quarter (200% increase) ## Commit activity: - 0 commits in the past quarter (0 last quarter) - 0 code contributors in the past quarter (0 last quarter) ## GitHub PR activity: - 1 PRs opened on GitHub, past quarter (6 last quarter) - 5 PR closed on GitHub, past quarter (1 last quarter) ----------------------------------------- Attachment BB: Report from the Apache River Project [Peter Firmstone] ----------------------------------------- Attachment BC: Report from the Apache RocketMQ Project [Xiaorui Wang] ## Description: The mission of Apache RocketMQ is the creation and maintenance of software related to a fast, low latency, reliable, scalable, distributed, easy to use message-oriented middleware, especially for processing large amounts of streaming data ## Issues: There are no issues requiring board attention. ## Membership Data: Apache RocketMQ was founded 2017-09-20 (2 years ago) There are currently 26 committers and 13 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Qipeng Li on 2019-08-12. - Chen Guangsheng was added as committer on 2019-12-20 - Fang Jian was added as committer on 2019-12-20 - Rongtong Jin was added as committer on 2019-12-20 ## Project Activity: Recent releases: ROCKETMQ-4.6.0 was released on 2019-11-25. ROCKETMQ-CLIENT-GO-1.2.4 was released on 2019-11-25. ROCKETMQ-CLIENT-CPP-1.2.4 was released on 2019-11-15. ## Community Health: Overall community health is good.Community Health Score (Chi): 8.37 (Healthy). We have been performing extensive outreach to related projects, in order to attract new contributors, and are seeing a steady influx of new people wishing to join and contribute, both programming and documentation-wise. RocketMQ community activity decreased slightly compared with last quarter, but the speed of processing issues saw a moderate increase compared with last quarter. Next we hope that more international contributors can join through GSOC or other projects. Moreover, some discussions about new features have already taken place on the mailing list. We'd like to take this opportunity to ask the board or others reading this report for guidance on reaching a wider group of international messaging platform student developers. ----------------------------------------- Attachment BD: 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 latest release is 6.0.0 and the ASF blog site at blogs.apache.org runs on Roller 5.2.4 Tomcat and MySQL. ## Issues: No issues require the attention of the board. ## Membership Data: Apache Roller was founded 2007-02-20 (13 years ago) There are currently 10 committers and 6 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Aditya Sharma on 2019-08-03. - No new committers. Last addition was Swapnil Mane on 2019-09-15. ## Project Activity: - Roller 6 was released at the end of 2019 - A new logo is being designed by some new contributors - blogs.apache.org will be upgraded to Roller 6 soon ## Community Health: Overall community health is good and new contributors have been helping out with development, logo design and documentation. ----------------------------------------- Attachment BE: 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 (14 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 were no releases over the last quarter. A new contributor has raised several issues and submitted pull requests, so we anticipate geting a new minor Java release out within a month for these fixes. Work continued on a new major Java release. We also anticipate this over the next quarter. We discussed again the possibility of moving to GIT - there were no objections, so we anticipate doing this over the next quarter. Recent releases: Apache Santuario - XML Security for Java 2.1.4 was released on 2019-07-20. Apache Santuario - XML Security for Java 2.1.3 was released on 2019-03-29. Apache Santuario XML-Security C++ 2.0.2 was released on 2018-11-02. ## 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 BF: Report from the Apache Serf Project [Branko Čibej] ----------------------------------------- Attachment BG: 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 (a year ago) There are currently 23 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 MabinGo on 2019-10-09. - Lisen Sun was added as committer on 2019-12-27 ## Project Activity: We are planning to do a new round release at the end of this quarter. Recent releases: ServiceComb toolkit 0.2.0 was released on 2020-01-05 ServiceComb Service-Center 1.3.0 was released on 2019-11-07. ServiceComb Java Chassis 1.3.0 was released on 2019-10-31. ## Community Health: Overall community health is good. We started to work with some Apache project to address the multiple data center sync since issue last month. Although there is a litter drop of the code contributors (-13%) as some developers just switch the job, the developer activities are increase (PR and code commits have 30% increase). ----------------------------------------- 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 the Open Geospatial Consortium (OGC) and the International Organization for Standardization (ISO) standards. Apache SIS also develops project-specific API for functionalities not covered by OGC/ISO standards. ## Issues: No issue to report this month. ## Membership Data: Apache SIS was founded 2012-09-19 (7 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: All activities is happening on a branch (we develop on a branch anticipating what may be future standards, and keep master aligned with currently released standards). The last merge on master was on October 24, 2019. We usually merge on master more often, but the merge is currently hold because of large contributions committed on the development branch and not yet reorganized in a way to minimize merge conflicts. The new functionalities include: * Use of PostGIS spatial database, spatial filters, GeoJSON (cited in last report). * JavaFX application is progressing well. * Base class for portrayal (i.e. rendering of maps). * Base class for reproducing some of the functionalities of Java Advanced Imaging (JAI) library. The JAI library was developed ~25 years ago by Sun Microsystems, NASA and others. It was a powerful library for processing large images, with advanced features for defining and manipulating chains of image operations, lazy computing and multi-threading on a tile-by-tile basis, handling interpolations problems, etc. It was suitable to classical photos, medical imagery or remote sensing data. Unfortunately JAI is not maintained anymore for about 15 years. Nevertheless at least some of JAI functionalities are critical to Apache SIS. In the last three months we started to reproduce in Apache SIS some functionalities of JAI. An Open Geospatial Consortium (OGC) meeting was done in November 2019. A report has been posted on the Apache geospatial mailing list: https://s.apache.org/m0itz The Open Geospatial Consortium (OGC) does every year a "test bed" where new standards are experimented. The test bed for 2020 includes an aspect in which Apache SIS is particularly well suited. In short, the main trend of the last 20 years has been in the development of Web APIs for the discovery and download of data. However the amount of Earth Observation data is so huge (terabytes of new data every day) that space agencies want to change the paradigm, and transfer algorithms close to the machine where data are located instead than downloading the data. This may require the standardization of programming languages APIs (as opposed to Web APIs). I will give more details in next report if we get involved (indirectly) in this experiment. ## Community Health: Traffic on user mailing list has increased thanks to new users in the process of evaluating Apache SIS. They have not yet made their choice, so we do not know yet if they will stay around. Traffic on developer mailing list is probably too low compared to the amount of commits. Since the 3 currently active developers are from the same company, and all of them in a rush for getting projects done, we have difficulty to spend the required amount of time for communicating better on the list. ----------------------------------------- Attachment BI: Report from the Apache Spark Project [Matei Alexandru Zaharia] Apache Spark is a fast and general engine for large-scale data processing. It offers high-level APIs in Java, Scala, Python and R as well as a rich set of libraries including SQL, streaming, machine learning, and graph analytics. Project status: - We have cut a release branch for Apache Spark 3.0, which is now undergoing testing and bug fixes before the final release. In December, we also published a new preview release for the 3.0 branch that the community can use to test and give feedback: https://spark.apache.org/news/spark-3.0.0-preview2.html. Spark 3.0 includes a range of new features and dependency upgrades (e.g. Java 11) but remains largely compatible with Spark’s current API. - We published Apache Spark 2.4.5 on Feb 8th with bug fixes for the 2.4 branch of Spark. Trademarks: - Nothing new to report in the past 3 months. Latest releases: - Spark 2.4.5 was released on Feb 8th, 2020. - Spark 3.0.0-preview2 was released on Dec 23rd, 2019. - Spark 3.0.0-preview was released on Nov 6th, 2019. - Spark 2.3.4 was released on Sept 9th, 2019. Committers and PMC: - The latest PMC member was added on Sept 4th, 2019 (Dongjoon Hyun). - The latest committer was added on Sept 9th, 2019 (Weichen Xu). We also added Ryan Blue, L.C. Hsieh, Gengliang Wang, Yuming Wang and Ruifeng Zheng as committers in the past three months. ----------------------------------------- Attachment BJ: Report from the Apache Stanbol Project [Rafa Haro] ----------------------------------------- Attachment BK: Report from the Apache Streams Project [Steve Blackmon] ## Description: Apache Streams unifies a diverse world of digital profiles and online activities into common formats and vocabularies, and makes these datasets accessible across a variety of databases, devices, and platforms for streaming, browsing, search, sharing, and analytics use-cases. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Streams was founded 2017-07-18 (3 years ago) There are currently 8 committers and 8 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Ate Douma on 2017-07-18. - No new committers were added. ## Project Activity: - Three modules are new or materially improved this quarter. - One module was submitted (and several reviewed) by a new project participant bhodge. ## Community Health: - Mailing list and commit participation was low again. Adding committers and growing the PMC needs to be a focus. - Streams is over-due for a release to incorporate new ActivityStreams 2.0 support and updates to several of our core dependencies. ----------------------------------------- Attachment BL: Report from the Apache Subversion Project [Stefan Sperling] 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. * Board Issues There are no Board-level issues of concern. * Community The Subversion development community is fairly quiet these days. A small trickle of development is ongoing. The community usually responds to bug reports and is willing to help the reporter or any other volunteer to develop a fix. However, in many cases there is no such volunteer, and those bug reports are filed but often remain unresolved. Our user support forums (Email and IRC) receive questions and answers regularly. We have added no new committers/PMC members since the last report. Most recently added PMC members are Nathan Hartman (hartmannathan@) and Yasuhito Futatsuki (futatuki@). * Releases The currently supported releases are Subversion 1.13.0 and 1.10.6. We are currently preparing for the 1.14 release which is expected in April: https://subversion.apache.org/roadmap.html#release-planning Discussions about the frequency of minor releases are still taking place on our dev@ list. Because funding for a developer who managed our time-based releases is no longer available the community is reconsidering the viability of time-based releases. One particular question is whether we should move towards a release model which is focused on maintenance in the long term, as opposed to development of new features. ----------------------------------------- Attachment BM: 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 (7 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: Several fixes, improvements and small new features are being introduced for upcoming maintenance release 2.1.6. Also, work on master branch for next major release 3.0.0 is regaining strength. Contributions via pull requests from GitHub remain quite high and seem to be seen as a mean to double-check changes before getting into actual commits, especially for new features. This not only for newcomers but also by committers. Latest releases: - 2.0.14 was released on 2019-09-12 - 2.1.5 was released on 2019-09-12 ## Community Health: Besides Misagh Moayyed recently welcomed as new committer, we have been glad to report an additional contributor to our team list page, Dmitriy Brashevets. ----------------------------------------- Attachment BN: Report from the Apache SystemML Project [Jon Deron Eriksson] ## Description: SystemML provides declarative large-scale machine learning (ML) that aims at flexible specification of ML algorithms and automatic generation of hybrid runtime plans ranging from single node, in-memory computations, to distributed computations such as Apache Hadoop MapReduce and Apache Spark. ## Issues: Little development has happened in the main project in the last year. On the private list, there is discussion about merging an active fork of SystemML back into the main project. This fork is SystemDS, led by Matthias Boehm, the largest contributor to SystemML. Matthias has proposed nominating the 4 most active SystemDS team members to be committers. He has stated that he would require that the project name is changed to SystemDS. He has discussed this name change process with Mark Thomas. The responses on the private list regarding merging of the active fork have been positive. ## Membership Data: Apache SystemML was founded 2017-05-16 (3 years ago) There are currently 26 committers and 23 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 Arvind Surve on 2017-05-16. - No new committers. Last addition was Guobao Li on 2018-08-28. ## Project Activity: There was one commit to the project this quarter. One pull request was opened and closed this quarter. The most recent release was 1.2.0 on Aug 24, 2018. ## Community Health: The community is currently unhealthy. There is little email activity. Community health should significantly improve if SystemDS is merged into the main project. ## Answers to Board Questions: myrle: Thank you for your clear and frank assessment of the state of the project community. Is it time to retire SystemML? Henry Saputra initiated a discussion about possibly retiring SystemML to the attic. In this discussion, the possibility of merging the active SystemDS fork into the main Apache project was discussed. All responses on the private list to the proposal to merge SystemDS into SystemML have been positive. ----------------------------------------- Attachment BO: Report from the Apache Tapestry Project [Thiago Henrique De Paula Figueiredo] ## Description: The mission of Tapestry is the creation and maintenance of software related to Component-based Java Web Application Framework ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Tapestry was founded 2006-02-14 (14 years ago) There are currently 27 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 9:4. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Gusev on 2019-09-02. - No new committers. Last addition was Balázs Palcsó on 2019-01-17. ## Project Activity: This was a pretty slow quarter for the project. Unfortunately, we weren't able to release Tapestry 5.5 in the last quarter as we planned, but we definitely are going to do that in this month or in the next. We expect a little increase in community activity after the release. ## Community Health: dev@tapestry.apache.org had a 87% decrease in traffic in the past quarter (11 emails compared to 82) 3 issues opened in JIRA, past quarter (-50% decrease) 0 issues closed in JIRA, past quarter (-100% decrease) 1 commit in the past quarter (-92% decrease) 1 code contributor in the past quarter (-66% decrease) 1 PR opened on GitHub, past quarter (-66% decrease) 0 PRs closed on GitHub, past quarter (-100% decrease) ----------------------------------------- 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 Our mailing lists are quieter this quarter than the previous quarter. We do, however, anticipate this as the project tends to see an increase in November/December time as contributors enjoy spending some free time over the holiday period contributing to the project, and the volume drops once the holiday period is over. We are seeing greater participation from the PMC in creating board reports, in particular Jonathan Gallimore who created the majority of this report. We hope to see continued collaboration here. There was a slight delay getting enough binding votes on our last round of releases, which is a sign we should put some attention to expanding the PMC. Additionally we've more than doubled contributors in the last 14 months, from around 40 to now 98, however have only added one committer in that same timeframe, which is a sign we should consider being more aggressive granting commit. ## Activity The community has recently released TomEE 8.0.1 in January, along with parallel releases of TomEE 7.1.2 and TomEE 7.0.7. The latest 8.0.1 release fixes compliance issues around JAX-RS, provides some fixes for running with Java 11, removes some outdated and unused dependencies (Xalan and Serializer), and upgrades other dependencies (Tomcat and CXF) to mitigate the latest CVE vulnerabilities in those components, including: CVE-2019-12419: Apache CXF OpenId Connect token service does not properly validate the clientId CVE-2019-12406: Apache CXF does not restrict the number of message attachments CVE-2019-17563: Apache Tomcat Session fixation CVE-2019-12418: Apache Tomcat Local Privilege Escalation TomEE is not yet Jakarta EE 8 compliant, but work continues in this area. The release of Jakarta EE 9 is in progress and set to deliver in the June-August timeframe 2020. This will involve a namespace break from javax to jakarta that will impact not just TomEE but all Apache java projects that implement former-Java EE specifications. We expect a great deal of project-to-project communication on this and it is likely something we should ask projects to report on over the next year. All projects will need to know each other's status and the board should be aware of overall progress and potential project or community impacts. We have seen new activity in the community, particularly in the area of maintaining Docker images, and re-working the website. We're particularly grateful for David Jencks' work on the website, and welcome the collaboration between new contributors Rod Jenkins and Carl Mosca on the mailing list. We continue to support their efforts, and strive to be as welcoming as possible to new contributors. Our community speaks a number of different languages, which has enabled translations of our documentation, particularly around the large library of examples we include with the project. We have seen translations to Portuguese and Spanish, and have a new contributor translating documentation into Russian. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015 ## Committer base changes: - Currently 31 committers. - Last committer added was Cesar Hernandez on July 1st 2019. ## Releases: - Apache TomEE 8.0.1 on January 22, 2020 - Apache TomEE 7.1.2 on January 22, 2020 - Apache TomEE 7.0.7 on January 22, 2020 ----------------------------------------- Attachment BQ: Report from the Apache Traffic Control Project [David Neuman] ## 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 board attention ## Membership Data: Apache Traffic Control was founded 2018-05-15 (2 years ago) There are currently 24 committers and 15 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. Last addition was Derek Gelinas on 2019-03-17. - No new committers. Last addition was Brennan Fieck on 2019-07-27. ## Project Activity: ATC 4.0 release candidate is out for vote. We are up to RC4 and have been getting good feedback on our releases. Our ATC Robots working group - designed to discuss ATC automation - had it's first meeting. The Traffic Control working group has been working on defining our 3.0 API which will be implemented in a future release. The working groups are doing a good job of following up on list after their meetings. ## Community Health: The communinity health is good. We seem to be getting a lot of good participations from new users which is encouraging even though it seems like most of them are just users and are not necessarily contributing code. We recognize that providing good feedback is valuable and we are happy to see more people active in our community. ----------------------------------------- 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. Turbine is a matured and well established framework that is used as the base of many other projects. It allows experienced Java developers to quickly build web applications. ## Issues: No board-level issues currently. ## Membership Data: Apache Turbine was founded 2007-05-16 (13 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. ## Project Activity: - Code changes in components are on low/medium level. - Continuing last quarter efforts the main focus has been on preparing the upstream related project Apache Torque 4.1 (version label may be changed to 5.0) before the next Turbine/Fulcrum 5.1 releases. - Last quarters backlog / discussion are still in follow-up work/work in process. - No releases were done this quarter. - Last main project was Turbine 5.0 Core release on Tue May 28 2019. ## Community Health: - Some PMC members are currently more active in related project Db/Torque, this slows down the development process in this project. - Turbine is at its core a user/group/role-based web application - it is very well-defined and definitely should not be considered as outdated. Moving Turbine core to Git (rw) may be one step, but to signal more recentness this may be also achieved by improving the front page (more responsive, text and design updates). ----------------------------------------- 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 (4 years ago). There are currently 28 committers and 25 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. 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: - CI setup with ASF Jenkins still in progress. Daily builds are in place but configuration needs to be investigated as builds are not green. - Experimentation with using newer versions(5.x) of Elasticsearch vs. supported older version (1.7). 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 and use of Usergrid has been stable with no issues reported recently. There is a new committer and additional interest for modernizing Usergrid -- upgrading Cassandra/Elasticsearch to the latest version and containerizing Usergrid. However, there has not been any significant contributions for this yet. Getting the project to a healthier state will continue to be a focus. This includes planning of a new release -- master branch is currently stable and contains many stability fixes over the last release in 2016. ----------------------------------------- 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 (13+ years ago) There are currently 14 committers and 9 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 Michael Osipov on 2017-07-27. - No new committers. Last addition was Michael Osipov on 2017-01-30. ## Project Activity: Velocity Engine 2.2 was released on 2020-02-02. This release has improvements to logging, custom parsing support, and a big effort toward improved backward compatibility with 1.x versions. ## Community Health: The active community is small but very capable. Coding continues to be handled by a single PMC member, with others contributing to votes and discussion. The dormant PMC members did a great job coming out of dormancy to vet and support the 2.2 Engine release. Stability continues to be both intentional and appropriate, but the more active PMC members are planning to reach out to a few very active contributors, hoping to talk them into taking committer and, eventually, PMC roles. ----------------------------------------- Attachment BU: Report from the Apache Whimsy Project [Sam Ruby] ## 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: I (Sam) remain concerned that there are not enough developers on the board agenda tool. ## Membership Data: Apache Whimsy was founded 2015-05-19 (5 years ago) There are currently 10 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was John D. Ament on 2017-06-11. - No new committers. Last addition was John D. Ament on 2017-06-08. ## Project Activity: - setupmymac and docker scripts provided to make it easier for new developers - whimsy now will download file lists rather than file contents for large repositories (e.g., documents/iclas) - prep for puppet 6 / ubuntu 18.04 (whimsy-vm5) - ICLAs will be OCR parsed to reduce data entry for the secretary - mirror download checker improvements - proxy form and other membership meeting tools improvements, including a new members meeting information page - email reminders for action items - general code cleanup (example: removal of unused variables) ## Community Health: More than enough oversight, no new committers for over two years. One tool (as noted above) has a bus factor isssue. ----------------------------------------- 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 at this time. ## Membership Data: Apache Xalan was founded 2004-09-30 (15 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: - Research on resuscitating builds has paused; we cannot find folks with historical build knowledge. ## Community Health: The community is not very active. I reject almost all email list posts as Spam. ----------------------------------------- Attachment BW: Report from the Apache Xerces Project [Michael Glavassevich] ----------------------------------------- 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.12 * Apache FOP 2.4 * Apache XML Graphics Commons 2.4 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 * Clay Leeds became XML Graphics PMC Chair/VP 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 ==================== * XMLGraphics Commons 2.4 was released on Sat October 31, 2019 * XMLGraphics FOP 2.4 was released on Sat October 31, 2019 * XMLGraphics Batik 1.12 was released on Sat October 31, 2019 = SUB PROJECTS = ================ XML GRAPHICS COMMONS ==================== Community activity was light, although there were a few bugs resolved. New Release? ------------ XMLGraphics Commons 2.4 was released on Sat October 31, 2019 Latest Release -------------- XML Graphics Commons 2.4 was released on Sat October 31, 2019 FOP === A number of patches have been processed into TRUNK and several bugs fixed. New Release? ------------ XML Graphics FOP 2.4 was released on Sat October 31, 2019 Latest Release -------------- XML Graphics FOP 2.4 was released on Sat October 31, 2019 BATIK ===== Apache Batik 1.12 was released on Sat October 31, 2019 New Release? ------------ Apache Batik 1.12 was released on Sat October 31, 2019 Latest Release -------------- Apache Batik 1.12 was released on Sat October 31, 2019 ------------------------------------------------------ End of minutes for the February 19, 2020 board meeting.