The Apache Software Foundation Board of Directors Meeting Minutes February 20, 2019 1. Call to order The meeting was scheduled for 10:30am Pacific and began at 11:31 when a sufficient attendance to constitute a quorum was recognized by the chairman. Other Time Zones: https://timeanddate.com/s/3rte The meeting was held via teleconference, hosted by Doug Cutting and Cloudera. IRC #asfboard on irc.freenode.net was used for backup purposes. 2. Roll Call Directors Present: Rich Bowen Shane Curcuru Bertrand Delacretaz Isabel Drost-Fromm Ted Dunning Brett Porter Roman Shaposhnik Phil Steitz Mark Thomas Directors Absent: none Executive Officers Present: Ross Gardler Tom Pappas Sam Ruby Daniel Ruggeri Craig L Russell Matt Sicker Executive Officers Absent: Ulrich Stärk Guests: Daniel Gruno Geoff Macartney Greg Stein - joined at 10:45 Henri Yandell Jim Jagielski Kevin A. McGrail Sally Khudairi 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of January 16, 2019 See: board_minutes_2019_01_16.txt Approved by General Consent. 4. Executive Officer Reports A. Chairman [Phil] This month, we began preparation for the annual membership meeting to be held next month, March 26, with reconvene on March 28. We are still seeking vote monitors and proxies to help with the meeting. We continued discussion this on how, if at all, the ASF should engage in the external dialog on open source licensing and business models. We do have consensus that any statement we make should confirm our commitment to the Apache License, possibly explaining how it supports and enables our mission. I would like to thank the members who participated for the constructive discussion started this month about how the mission statement might be slightly improved and the connection between the license, the mission and our core principles. B. President [Sam] Items Requiring Board Attention ------------------------------- ApacheCon EU 2019 proposal (agenda item 8A) Overall ------- Finances continue to be in an excellent position, with income exceeding both budget and previous year, and expenditures under budget and previous year. Notable changes from last month (all positive): we now have the number and ApacheCon US made a modest profit; per the advice of the firm preparing our tax returns, the Pineapple fund donation is treated as ordinary income and included in cash on hand; and at this late point in the fiscal year, a number of areas (most notably infrastructure) are running far enough behind that they can't reasonably catch up in expenditures. I'm not sure how to proceed in the five year projections. The only sized estimate that was produced in this past month was the estimate for ApacheCon EU 2019. There clearly is value in having such an event; we could conceivably again make a modest profit on the event, but that's not the point of the event; the remaining question is one of risk. There is a small chance that we could lose a relatively large sum of money, but even worst case, that amount is bounded and one that we could absorb. My input is that it is worth the risk. Brand Management ---------------- Operating normally, providing guidance, registering marks, and resolving potential infringements. No items requiring board attention. Fundraising ----------- Actively reorganizing; transferring that previously was done by Kevin to a mixture of paid staff and volunteers. Thanks go out to Kevin: we are in a much better place than we were two years ago, and wouldn't be where we are today without his hard work. The transition itself is going to take months to work out. While things look promising, there may be occasional bumps that are encountered along the way. My request is that we give the team the space to work things out, keeping intervention to a minimum. Finance ------- Again a month of research and review. I expect Finance to take a larger review in the FY20 budget. Generally, the categories we have date back to Justin's original budget. Tom is already working with groups proposing different categories to align with accounting principles. Additionally, please see Attachments 1 through 7. Shane notes that it is difficult for projects to initiate cross-project proposals. Sam suggests that if there are proposals that might benefit just one project, then the projects could bring them forward. And then other projects might see how it might benefit them. C. Treasurer [Ulrich] Operating Cash on January 31st, 2019 was $2,599.2K, which is up $272.4K from last month’s ending balance (Dec 18) of $2,326.8K. Total Cash as of Jan 31st, 2019 is $3,993.1 ( includes the Pineapple and restricted Donation) as compared to $1,793.4K on Jan 31st 2018 ( an increase of $2,199.7K year over year. If we exclude the Pineapple and Restricted donation that is a year over year increase of $805.8K in net cash). The Jan 2019 ending Operating cash balance of $2,599.2K represents an Operating cash reserve of 19.1 months based on the FY19 conservative Cash forecast average monthly spending of $136.2K/month ( this will most likely change for FY 20 as we continue to work on the budget). The ASF actual Operating reserve of 19.1 months at the end of Jan 2019 is ahead of the budgeted 11.1 month reserve for YTD through Jan 2019. The ASF Operating reserve continues to be very healthy for an organization of the ASF’s size and Operating activity. Reviewing the YTD Cash P&L, total Income, is ahead of FY 18, at this point in the Fiscal year by $436.6K. As compared to the FY 19 Budgeted Income, YTD, we are ahead by $561.7K. ApacheCon NA 2018 has now been reconciled and considered closed. We have added two tabs to this month’s finance package – “Conference P&L” and “Conference P&L Detail.” Total revenue for the Conference came to $226.0K and expenses came to $193.4K. Thus, the net income for the event came to $32.6K versus a budgeted loss of $60.5K, Congrats to the entire team who helped make this event not only a success for the attendees but also a financial success as well. YTD expenses, through Jan 31st, 2019 are under budget by $346.6K. All depts. are under budget, at the end of Jan 2019. There are still a couple items worth mentioning, one being Infra, as noted in the Board summary is $196.3K under budget due to the timing of hiring of staff and not having to pay any Lease web invoices YTD. The other being TAC at $45K under budget YTD for FY19. We have moved most of the dept underspending forward in the Cash forecast and will be reviewing the underspending with the departments as we move forward in FY19 Q4. Regarding Net Income (NI), YTD FY 19 the ASF finished with a positive $539.8K NI vs a budgeted negative <$368.5K> NI or $908.3K ahead of Budget, NI, for FY19 at this point in the Fiscal year. This is attributable to timing of some Sponsor payments offset by more Donations than were budgeted as well as underspending in all depts YTD, vs the FY19 Budget. At this point in the FY we are doing very well, ahead in Revenue and well under budget in Expenses, even taking timing variances into account. We will continue to monitor this as we finish out FY19. With regard to FY18, we are outpacing revenue, by $436.6K as noted above, but we are also out pacing expenses by $166.8K. However, year over year NI for FY19 exceeds FY18 by $269.8K, another good yard stick of the Foundation’s financial health at this point in time. Current Balances: Boston Private CDARS Account 2,250,000.00 Citizens Money Market 1,067,656.88 Citizens Checking 669,173.49 Paypal - ASF 6,291.24 Total Checking/Savings 3,993,121.61 Jan-19 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 4,777.55 5,309.61 -532.06 Sponsorship Program 337,000.00 186,000.00 151,000.00 Programs Income 0.00 0.00 0.00 Conference/Event Income 0.00 0.00 0.00 Other Income 2,674.64 2,916.94 -242.30 Interest Income 453.20 1,652.41 -1,199.21 Total Income 344,905.39 195,878.96 149,026.43 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 49,747.75 78,128.36 -28,380.61 Programs Expense 0.00 0.00 0.00 Publicity 10,689.59 14,146.20 -3,456.61 Brand Management 0.00 8,166.66 -8,166.66 Conferences 0.24 0.00 0.24 Travel Assistance Committee 0.00 0.00 0.00 Fundraising 8,141.09 17,333.32 -9,192.23 Treasury Services 3,350.00 3,475.00 -125.00 General & Administrative 762.87 2,013.59 -1,250.72 Total Expense 72,691.54 123,263.13 -50,571.59 Net Income 272,213.85 72,615.83 199,598.02 YTD FY19 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 126,873.71 38,889.77 87,983.94 Sponsorship Program 1,221,371.47 821,000.00 400,371.47 Programs Income 17,200.00 14,400.00 2,800.00 Conference/Event Income 248,227.95 184,000.00 64,227.95 Other Income 29,557.67 16,535.95 13,021.72 Interest Income 4,949.84 11,616.42 -6,666.58 Total Income 1,648,180.64 1,086,442.14 561,738.50 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 534,808.23 731,154.92 -196,346.69 Programs Expense 0.00 4,400.00 -4,400.00 Publicity 177,621.61 191,361.39 -13,739.78 Brand Management 40,181.99 73,500.02 -33,318.03 Conferences 197,012.10 200,000.00 -2,987.90 Travel Assistance Committee 0.00 45,000.00 -45,000.00 Fundraising 113,953.27 156,000.04 -42,046.77 Treasury Services 32,785.00 33,425.00 -640.00 General & Administrative 11,962.68 20,062.16 -8,099.48 Total Expense 1,108,324.88 1,454,903.53 -346,578.65 Net Income 539,855.76 -368,461.39 908,317.15 D. Secretary [Craig] Processing of submitted documents with digital signatures was deteriorating due to dependence on an oft-overloaded public key repository. After this issue was reported, the Whimsy team stepped up and within a few days, Sebb had committed a change that significantly improved the reliability of the tool. In January, 54 ICLAs, four CCLA, and four grants were received and filed. E. Executive Vice President [Ross] Infrastructure ============= Everything is healthy in Infrastructure. Hiring has reached the offer stage. All projects have been migrated to gitbox. Congrats to the team. Improved On-Call process with "yellow" alerts that don't create unnecessary late night pages. Marketing and Publicity ======================= The role of VP Marketing and Publicity is becoming a central role for many operational activities, including but not limited to, Fundraising and Conferences. Sally has created a "Central Services" sub-group of volunteers to help manage selected cross-foundational projects. This group is intended to help spread the load with respect to ensuring things get done, thereby freeing Sally to concentrate on the more time dependent activities related to the expanded role. Fundraising handover is going well. The current focus is on reviewing, documenting and renewing targeted sponsorships, renewals are, for the most part, proving to be relatively easy to secure. Preparations for the 20th Anniversary are well underway - with lots of work to do, including an apache.org refresh. The central services team are helping drive this forward. The full report includes the usual details of key activities during the month. Conferences =========== DC Roadshow is now only a few weeks out. 12 different projects/communities/topics have claimed a track at ApacheCon North America. A full CFP is expected to open soon. ACEU19 planning is also progressing. See discussion item 8A There was a slight venue hiccup with Chicago roadshow but planning is on track. Travel Assistance Committee =========================== No significant activity. No event currently in planning. F. Vice Chairman [Shane] As we approach the 20th anniversary of the ASF's corporate founding, it's impressive to review the ever-lengthening list of Apache project reports and consider the incredible number of successes that our many communities of volunteers have built for the public good. More importantly from a board perspective, it's heartening to see the continually improving organization and communications coming from our many operations groups. The volunteers and the paid staff working together to keep everything behind the scenes (infra, legal, treasury/fundraising/finances, etc.) and our public face (brand, conferences, publicity!) running smoothly are doing an incredible job. I'm looking forward to the retrospectives on our history as well as the expanded and improved guides to the Apache Way that will be coming out in the next few months to celebrate our anniversary! Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Mark] No report was submitted. B. Apache Legal Affairs Committee [Roman Shaposhnik] See Attachment 9 C. Apache Security Team Project [Mark J. Cox / Bertrand] See Attachment 10 D. VP of Data Privacy [Chris Mattmann / Roman] 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: # Marmotta [rs] # Serf [rb] # Stanbol [rs] # Subversion [rb] # Xalan [rs] A. Apache Airflow Project [Bolke de Bruin / Isabel] See Attachment A B. Apache Ambari Project [Jayush Luniya / Brett] See Attachment B C. Apache Ant Project [Jan Materne / Shane] See Attachment C D. Apache Aurora Project [Jake Farrell / Ted] See Attachment D E. Apache Avro Project [Thiruvalluvan M. G. / Phil] See Attachment E F. Apache Bloodhound Project [Gary Martin / Rich] See Attachment F G. Apache BookKeeper Project [Sijie Guo / Isabel] See Attachment G H. Apache Brooklyn Project [Geoff Macartney / Bertrand] See Attachment H I. Apache Buildr Project [Antoine Toulme / Ted] See Attachment I J. Apache Cassandra Project [Nate McCall / Shane] See Attachment J K. Apache Clerezza Project [Hasan Hasan / Mark] See Attachment K L. Apache Cocoon Project [Cédric Damioli / Phil] See Attachment L M. Apache Community Development Project [Sharan Foga / Rich] See Attachment M N. Apache CouchDB Project [Jan Lehnardt / Brett] See Attachment N O. Apache Creadur Project [Brian E Fox / Roman] See Attachment O P. Apache DeltaSpike Project [Mark Struberg / Isabel] See Attachment P Q. Apache DRAT Project [Tom Barber / Ted] See Attachment Q R. Apache Drill Project [Arina Ielchiieva / Shane] See Attachment R S. Apache Empire-db Project [Rainer Döbele / Brett] See Attachment S T. Apache Flume Project [Mike Percy / Phil] See Attachment T U. Apache Forrest Project [David Crossley / Roman] See Attachment U V. Apache FreeMarker Project [Dániel Dékány / Bertrand] See Attachment V W. Apache Geode Project [Karen Miller / Rich] See Attachment W X. Apache Giraph Project [Dionysios Logothetis / Mark] See Attachment X Y. Apache Gora Project [Kevin Ratnasekera / Bertrand] See Attachment Y Z. Apache Griffin Project [William Guo / Phil] See Attachment Z AA. Apache Groovy Project [Paul King / Mark] See Attachment AA AB. Apache Hama Project [Chia-Hung Lin / Shane] No report was submitted. @Phil: pursue a report for Hama AC. Apache Helix Project [Kishore G / Ted] See Attachment AC AD. Apache HTTP Server Project [Daniel Gruno / Brett] See Attachment AD AE. Apache HttpComponents Project [Asankha Chamath Perera / Roman] See Attachment AE AF. Apache Ignite Project [Denis A. Magda / Isabel] See Attachment AF AG. Apache Impala Project [Jim Apple / Rich] See Attachment AG AH. Apache Incubator Project [Justin Mclean / Roman] See Attachment AH AI. Apache Joshua Project [Tommaso Teofili / Shane] No report was submitted. AJ. Apache jUDDI Project [Alex O'Ree / Phil] See Attachment AJ AK. Apache Juneau Project [James Bognar / Rich] See Attachment AK AL. Apache Kafka Project [Jun Rao / Mark] See Attachment AL AM. Apache Kibble Project [Rich Bowen] See Attachment AM AN. Apache Knox Project [Larry McCay / Bertrand] See Attachment AN AO. Apache Kylin Project [Luke Han / Ted] No report was submitted. @Ted: pursue a report or new chair for Kylin AP. Apache Lens Project [Amareshwari Sriramadasu / Isabel] See Attachment AP AQ. Apache Libcloud Project [Tomaž Muraus / Brett] See Attachment AQ AR. Apache Logging Services Project [Matt Sicker / Brett] See Attachment AR AS. Apache Lucene.Net Project [Shad Storhaug / Phil] See Attachment AS AT. Apache ManifoldCF Project [Karl Wright / Bertrand] See Attachment AT AU. Apache Marmotta Project [Jakob Frank / Roman] See Attachment AU @Roman: ping community about activity AV. Apache Mesos Project [Benjamin Hindman / Isabel] No report was submitted. @Isabel: pursue a report for Mesos AW. Apache MetaModel Project [Kasper Sørensen / Mark] See Attachment AW AX. Apache Oozie Project [Gézapeti / Shane] See Attachment AX AY. Apache Open Climate Workbench Project [Huikyo Lee / Ted] See Attachment AY AZ. Apache OpenOffice Project [Peter Kovacs / Rich] See Attachment AZ BA. Apache Perl Project [Philippe Chiasson / Brett] No report was submitted. BB. Apache Phoenix Project [Josh Elser / Roman] See Attachment BB BC. Apache POI Project [Dominik Stadler / Bertrand] See Attachment BC BD. Apache Qpid Project [Robert Gemmell / Mark] See Attachment BD BE. Apache REEF Project [Byung-Gon Chun / Rich] See Attachment BE BF. Apache River Project [Peter Firmstone / Phil] No report was submitted. @Phil: pursue a report for River BG. Apache RocketMQ Project [Xiaorui Wang / Shane] No report was submitted. @Shane: pursue a report for RocketMQ BH. Apache Roller Project [David M. Johnson / Ted] See Attachment BH BI. Apache Santuario Project [Colm O hEigeartaigh / Isabel] See Attachment BI BJ. Apache Serf Project [Branko Čibej / Phil] See Attachment BJ @Rich: follow up with web issue for mod_pagespeed BK. Apache ServiceComb Project [Willem Ning Jiang / Bertrand] See Attachment BK BL. Apache SIS Project [Martin Desruisseaux / Rich] See Attachment BL BM. Apache Spark Project [Matei Alexandru Zaharia / Roman] See Attachment BM BN. Apache Stanbol Project [Fabian Christ / Ted] No report was submitted. BO. Apache Subversion Project [Stefan Sperling / Mark] See Attachment BO BP. Apache Syncope Project [Francesco Chicchiriccò / Isabel] See Attachment BP BQ. Apache SystemML Project [Jon Deron Eriksson / Shane] See Attachment BQ BR. Apache Thrift Project [Jake Farrell / Brett] See Attachment BR BS. Apache TomEE Project [David Blevins / Isabel] See Attachment BS BT. Apache Traffic Control Project [David Neuman / Phil] See Attachment BT BU. Apache Turbine Project [Georg Kallidis / Roman] See Attachment BU BV. Apache Usergrid Project [Michael Russo / Mark] See Attachment BV BW. Apache Velocity Project [Nathan Bubna / Rich] See Attachment BW BX. Apache Whimsy Project [Sam Ruby / Shane] See Attachment BX BY. Apache Xalan Project [Steven J. Hathaway / Brett] No report was submitted. BZ. Apache Xerces Project [Michael Glavassevich / Ted] No report was submitted. CA. Apache XML Graphics Project [Clay Leeds / Bertrand] See Attachment CA Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache James Project Chair WHEREAS, the Board of Directors heretofore appointed Eric Charles (eric) to the office of Vice President, Apache James, and WHEREAS, the Board of Directors is in receipt of the resignation of Eric Charles from the office of Vice President, Apache James, and WHEREAS, the Project Management Committee of the Apache James project has chosen by vote to recommend Benoit Tellier (btellier) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Eric Charles is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache James, and BE IT FURTHER RESOLVED, that Benoit Tellier be and hereby is appointed to the office of Vice President, Apache James, 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. The vote can be found on https://s.apache.org/RN38 Special Order 7A, Change the Apache James Project Chair, was approved by Unanimous Vote of the directors present. B. Resolution to reboot the Apache Xalan PMC WHEREAS, the Xalan Project Management Committee (PMC) only has less than 3 active members left, which is not enough to operate; and WHEREAS, several ASF members have agreed to form a new PMC to help bring the project back to working status; NOW, THEREFORE, BE IT RESOLVED that the Xalan PMC is re-established, with the persons listed immediately below appointed to serve as its members: * Bill Blough (billblough) * Roger Leigh (rleigh) * Mukul Gandhi (mukulg) * Gary D. Gregory (ggregory) * Michael Glavassevich (mrglavas) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gary D. Gregory be appointed to the office of Vice President, Apache Xalan, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that current members of the Xalan PMC who are not included in the above list of members are discharged from any responsibilities pertaining to the Xalan PMC. Special Order 7B, Resolution to reboot the Apache Xalan PMC, was approved by Unanimous Vote of the directors present. C. Establish the Apache Unomi Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to providing a reference implementation of the OASIS Customer Data Platform specification currently being worked on by the OASIS Context Server Technical Committee. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Unomi Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Unomi Project be and hereby is responsible for the creation and maintenance of software related to providing a reference implementation of the OASIS Customer Data Platform specification currently being worked on by the OASIS Context Server Technical Committee; and be it further RESOLVED, that the office of "Vice President, Apache Unomi" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Unomi Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Unomi Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Unomi Project: * David Griffon * Francois Papon * Jean-Baptiste Onofré * Kevan Jahanshahi * Serge Huber * Thomas Draier NOW, THEREFORE, BE IT FURTHER RESOLVED, that Serge Huber be appointed to the office of Vice President, Apache Unomi, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Unomi PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Unomi Project; and be it further RESOLVED, that the Apache Unomi Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Unomi podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Unomi podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7C, Establish the Apache Unomi Project, was approved by Unanimous Vote of the directors present. D. Change the Apache Thrift Project Chair WHEREAS, the Board of Directors heretofore appointed Jake Farrell (jfarrell) to the office of Vice President, Apache Thrift, and WHEREAS, the Board of Directors is in receipt of the resignation of Jake Farrell from the office of Vice President, Apache Thrift, and WHEREAS, the Project Management Committee of the Apache Thrift project has chosen by vote to recommend Jens Geyer (jensg) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Jake Farrell is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Thrift, and BE IT FURTHER RESOLVED, that Jens Geyer be and hereby is appointed to the office of Vice President, Apache Thrift, 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 7D, Change the Apache Thrift Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Propose ApacheCon EU 2019 for October 22-24 in Berlin produced by NewThinking We'd like to do an ApacheCon in Berlin from the dates October 22 - 24th, produced by NewThinking. Because this is a large budget item, the Conferences committee would like to get the full support of the board. The contract will be provided to the board before the board meeting. We are planning a 4-track event over 3 days for roughly 400 people. The board approves by unanimous consent continuing with the proposal to hold ApacheCon EU in Berlin in October 2019. B. Minor clarification to mission statement It has been proposed that we need a minor change to the Foundations mission statement. It is requested that the board discuss this proposal and make recommendations for making a change should the board agree it is necessary. The current statement is: "The mission of the Apache Software Foundation (ASF) is to provide software for the public good. We do this by providing services and support for many like-minded software project communities of individuals who choose to join the ASF." It has been observed that "join the ASF" gives the impression that there is some thing that one joins, like a membership organization. We don't really have a "joining" of anything. Given our inclusivity and the growing need to literally "join" open source projects outside of the ASF it is proposed that this potential misunderstanding is problematic. In order to resolve this it has been been suggested that we make a minor adjustment to this wording. It is not the intent to change the meaning of the mission statement, only to clarify this single point - that there is no need to "join" the ASF in order to participate in its projects. After discussion on the board@ mailing list the following suggestions have been made and not been objected to: A) "The mission of the Apache Software Foundation (ASF) is to provide software for the public good. We do this by providing services and support for many like-minded software project communities of individuals who choose to contribute to ASF projects." B) "The mission of the Apache Software Foundation (ASF) is to provide software for the public good. We do this by providing services and support for many like-minded software project communities of individuals who choose to participate with the Apache community." C) "The mission of the Apache Software Foundation is to provide software for the public good. We do this by providing services and support for many like-minded software project communities. " D) "The mission of the Apache Software Foundation is to provide software for the public good. We do this by providing services, support, and a common ethos for many software project communities. " @Ross: send message to board to finalize the change to mission statement C. VP Data Privacy Are we ready to appoint someone? The discussion at https://s.apache.org/vpdataprivacyfeb2019 seems to indicate consensus for John Kinsella who volunteered - and Mark's message to members@ got no replies. By unanimous consent, the board appoints John Kinsella to the position of VP, Data Privacy. 9. Review Outstanding Action Items * Rich: pursue a report for Lucene.Net [ Lucene.Net 2018-09-19 ] Status: Done: Prescott replied on private - https://lists.apache.org/thread.html/cd6a78050ef5414a449d00151679414fa4c71ee765d9d6e8e11e8fa8@%3Cprivate.lucenenet.apache.org%3E - and has submitted a report. * Roman: is this project still viable? [ Stanbol 2018-09-19 ] Status: * Roman: help the project with their request to add new pmc/committers [ Xalan 2018-09-19 ] Status: * Brett: follow up with Cocoon to encourage a release [ Cocoon 2018-11-21 ] Status: Update posted this report * Ted: pursue a report for Aurora [ Aurora 2019-01-16 ] Status: Done. Report submitted. * Mark: pursue a report for Avro [ Avro 2019-01-16 ] Status: Complete. We have a report for Feb. * Phil: pursue a report for Bloodhound [ Bloodhound 2019-01-16 ] Status: Complete. Report was submitted. * Isabel: follow up -- are there enough PMC members? [ Hama 2019-01-16 ] Status: * Phil: pursue a report for Helix [ Helix 2019-01-16 ] Status: Complete * Phil: reach out to PPMC to see about improving the governance of the project. [ Incubator 2019-01-16 ] Status: I started work on this, but still have follow-up to complete. Ongoing. * Rich: follow up regarding communications with security team [ Isis 2019-01-16 ] Status: I was confused between this and ODE. Need to go refresh my memory from last month's report. * Rich: pursue a report for Joshua [ Joshua 2019-01-16 ] Status: No response to any of the various messages sent to private@ about reporting. Not sure what's up. No messages at all this year on private@ except from "outsiders". * Rich: is this project headed for the attic? [ Lucene.Net 2019-01-16 ] Status: Done: See report * Mark: is there sufficient activity on the project? [ Streams 2019-01-16 ] Status: Complete. There are 3 PMC members present (and they have identified a way to try an attract more activity). * Isabel: pursue a report for Thrift [ Thrift 2019-01-16 ] Status: * Rich: reach out to the community to validate the plan to move to the attic [ ODE 2019-01-16 ] Status: Done: MThomas indicated on IRC that the Security team had received plenty of notification and didn't need any more. * Phil: discuss on board-chat exact process involving email to secretary@ to [ Process for restoring emeritus members 2019-01-16 ] Status: Dropped the ball on this one this month. Will pick it up. * Mark: prepare description of VP, Data Privacy for members@ [ VP, Data Privacy 2019-01-16 ] Status: Complete * Mark: discuss Jakarta EE proposal on mail list TBD @Phil: discuss potential [ Invitation to join the Jakarta EE Working Group as a Guest Member 2019-01-16 ] Status: Done. 10. Unfinished Business 11. New Business 12. Announcements Bertrand has decided to not run for the board next term. Ted has decided to not run for the board next term. 13. Adjournment Adjourned at 12:09 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] * ISSUES FOR THE BOARD None. * OPERATIONS Updated the guidance for the mandatory links to cover the use of http / https / protocol relative links. Recommendations have been provided but the final choice remains with the PMCs. Responded to the following queries, liaising with projects as required: - Provided guidance on using our logos within an external software product as a means to identify the type of data source - Approved 3 podling names (PINOT, UNOMI, HUDI) - Provided guidance on using Apache project names in titles and abstracts for a conference - Provided a pointer to Sally's excellent guidance for referring to a project's founders. - Provided guidance on using Apache project logos on external websites. * REGISTRATIONS OPENOFFICE is now registered in the US. * INFRINGEMENTS The MXNET podling addressed an issue with product naming in conference session titles and abstracts. The CAMEL PMC gained control of the @ApacheCamel twitter account. The KAFKA PMC addressed some issues with conference session abstracts. Work continues to address a number of potential infringements. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri] As always: we can't do what we do without our sponsors so we are delighted to welcome AWS (Platinum) and Workday (Gold) to the ASF family as sponsors this past month. We also renewed four sponsorships and received $3,414.55 from 42 donors via our individual giving platform. We thank everyone for keeping the family strong! As the Fundraising committee continues the "back office" work, we are pleased to report that outreach to all ASF Sponsors and Targeted Sponsors has been initiated as planned. Through these activities, we have confirmed renewal from most Targeted Sponsors and increases in support for several Targeted Sponsors going forward. These conversations even resulted in a new Apache Incubator project proposal from a Platinum Sponsor! We also continue conversations with top tier sponsors for promotional opportunities such as the recently posted case study from Gold Sponsor, Bloomberg (https://s.apache.org/jKNc). Last but not least, we greatly enjoyed shaking hands and exchanging smiles at FOSDEM with our ASF family members that could make it. The Fundraising committee is also gearing up for 2019 event support under a new model and has engaged with the various event planning teams. Our own Bob Paulin (Sponsor Ambassador) will serve as Event Sponsor Ambassador for the Apache Roadshow Chicago event. Sharan Foga (VP ComDev) will serve as Event Sponsor Ambassador for the ApacheConEU event in 2019 and Daniel Ruggeri (VP Fundraising) will handle ApacheCon NA 2019. Early engagement and clear documentation of roles/responsibilities with the various event planning teams will ensure another round of awesome events for 2019! We continue driving internal efficiencies in the committee to ensure our Sponsors know how much we love them. A few notable activities: - Restructuring of team activities including regular reporting schedule from Sponsor Ambassadors - Formalized process and documentation for ASF Conference (ApacheCon and Roadshows) support - Documentation of roles/responsibilities/workflow for the new Event Sponsor Ambassador role and overall event planning support - Streamlining record keeping processes including reconciliation with Accounting - Continued auditing/cleanup of mailing lists and notification channels The team also thanks Kevin A McGrail for his hard work and dedication (VP and Co-VP Fundraising) over the past two years as he steps away from Fundraising. We have successfully completed transition of notes, ongoing action items and plans as of early Feb and wish Kevin luck in all his future endeavors. ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi] [REPORT] ASF Marketing & Publicity - February 2019 I. Budget: we remain on budget and on schedule. II. Cross-committee Liaison: Sally Khudairi continues restructuring efforts for ASF Fundraising, in collaboration with VP Fundraising Daniel Ruggeri and ASF Fundraising committee members. She has secured the renewal of a Platinum Sponsor and is reviewing contributions from all Targeted Sponsors with 60% responding within first 7 days with confirmed re-commitment for 2019. Sally also established the new Central Services sub-group of ASF Marketing & Publicity to manage various cross-Foundation projects, beginning with creative support, specifically graphics. She has also been working with ASF Conferences across planning, sponsorships, marketing, and related tactics. The latest "Success at Apache" post, "For Love or Money: Volunteer vs Professional Open Source", has been published at https://s.apache.org/ePHl . We published the first ASF Sponsor case study (offered exclusively to Gold and Platinum sponsors), "Apache Software Foundation Gold Sponsor Profile: Bloomberg" https://s.apache.org/jKNc . Planning continues for promotions surrounding the ASF's 20th Anniversary (the community-wide survey on "The Apache Way" closes mid-February https://s.apache.org/oxTr ). III. Press Releases: the following formal announcement was issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timeframe: - 23 January - The Apache Software Foundation Announces Apache® Hadoop® v3.2.0 IV. Informal Announcements: 8 items were published on the ASF "Foundation" Blog. 4 Apache News Round-ups were issued, with a total of 238 weekly summaries published to date. We tweeted 32 items to 51.7K followers on Twitter. We posted 12 items on LinkedIn, which garnered more than 61.9K organic impressions. V. Future Announcements: 2 announcements are in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones and "Did You Know?" success stories are requested to contact Sally at with at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to 6 media queries, and are working on 3 placed articles by invitation. The ASF received 1,053 press clips vs. last month's clip count of 1,189. Media coverage of Apache projects yielded 2,062 press hits vs. last month's 1,697. ApacheCon received 198 press hits. We continue to work with several corporates with strong ties to various Apache projects on branding adherence and publishing internal guidelines to help their employees to properly represent the ASF, the Apache brand/projects/communities in their externally-focused communications. We helped the Apache Camel PMC have the @ApacheCamel handle successfully transferred to their account on Twitter. VII. Analyst Relations: we received two analyst queries during this time. Apache was mentioned in 23 reports by Gartner; 8 reports by Forrester; 4 reports by 451 Research; and 7 reports by IDC. VIII. Graphics: we are continuing to develop promotional materials, create assets, and Website refresh for the ASF's 20th Anniversary. Members of the new Central Services sub-group of ASF Marketing & Publicity are leading the apache.org refresh, reviewing and judging submitted entries for the 20th Anniversary logo, and developing digital advertising assets for the Apache Roadshow Chicago. IX. Events liaison: we continue to work with Virtual regarding sponsorship and marketing/promotional requirements for the Apache Roadshow/Chicago and ApacheCon North America 2019, and are also involved with the initial planning process for ApacheCon Europe 2019. X. Newswire accounts: we have 1 pre-paid press release remaining in our contract with GlobeNewswire, which will auto-renew through December 2019. # # # ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [David Nalley] General ======= Infrastructure is operating as expected, and has no current issues to bring to the attention of the President or the Board. Short Term Priorities ===================== - Finish planning/booking for Infra meetup in New Orleans in April. - Make offers to new system admins. Long Range Priorities ===================== - Complete the hermes-vm transition. Mail and mailing lists appear to be working, yet more testing and edge case features need to be completed before we move a subset of email flow to the new system. General Activity ================ - All projects have been moved to Gitbox, and the old git-wip box has been decommissioned. Related work with git commit emails was completed. - The team has been interviewing our final set of candidates. Offers should go out within the next week or two. - New "yellow alerts" class of warnings on PagerDuty to warn on-call about an issue, without a late night page. - Continued work on hermes-vm, our mail system replacement for the aging hermes box at OSL. - Several systems have been deployed with our new Ubuntu 18.04 support, and using Puppet v6. These rollouts confirm and improve our ongoing work on this platform. We'll begin upgrades of existing puppetized systems to 1804/p6 later this year. - Moved DNS "hidden master" off the again minotaur.a.o box, to a new dns-vm. - Per above, minotaur is mostly deprecated at this point, and general login has been disabled, along with old cronjobs that were running. - CPU rate limiting has been installed on some of our sites that are usually subjected to scrapes/crawls. https://s.apache.org/rate-limit - Bugzilla has been migrated to a beefier server. Along with the new rate-limiting, it should have much better uptime. This will also decommission about four separate VMs that were being used to run BZ. ----------------------------------------- Attachment 5: Report from the VP of Conferences [Rich Bowen] Planning is proceeding well for all of our in-flight events. The DC Roadshow is now just a few weeks out, and we are actively promoting and attempting to fill seats. We encourage you to follow @apachecon on Twitter, and help us amplify that message. We now have 12 different projects/communities/topics who have claimed a track at ApacheCon North America, which we are very excited about. Other aspects of this event planning are progressing. We expect to have a CFP available this week or first thing next week. ACEU19 planning is also progressing. There is a discussion item in today's agenda to get consensus on moving forward with the agreement. One of the venues for the Chicago Roadshow was lost, and has been replaced. Planning for that event is also progressing well. ----------------------------------------- Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald] Nothing to report this month really. Mailing List is quiet, with unfinished (and non-urgent) conversations paused whilst folks work on other things. I'll make a push to get some movement going again for the next report. ----------------------------------------- Attachment 7: Report from the VP of Finance [Tom Pappas] For the Month of January , continued conversations with possible Wealth Management option for foundation's excess funds. Also reviewed a possible CDARS option that has better rates than the current Boston Private option. Will continue to research and review. ----------------------------------------- Attachment 8: Report from the VP of W3C Relations [Andy Seaborne] ----------------------------------------- Attachment 9: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] We've had a lot of discussion on legal-discuss and general@incubator converging the topic of projects publishing software outside of Apache infrastructure. We don't believe this is currently clear. JIRA issues continue to move along (we're down 4, from 28 to 24, open issues this month). Henri has offered up some initial brainstorming on our part of the 5 year plan, the board are very welcome to offer their own thoughts: https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-422 Martin Michlmayr reported that we have not published our IRS filings since the 2015/2016 year. Roman has acquired the PDF for the latest filing and is about to publish it (with ample heads up given to the rest of the board members in the past few weeks). ----------------------------------------- Attachment 10: 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. During January we saw some delays with Mitre updating their site with our CVE submissions to them, they expect this to resolve soon. Stats for January 2019: 15 [license confusion] 9 [support request/question not security notification] Security reports: 38 (last months: 16, 34, 28) 6 [httpd], [site] 3 [ambari] 2 [kafka], [struts], [tomcat] 1 [activemq], [axis], [camel], [cassandra], [couchdb], [fineract], [guacamole], [james], [karaf], [lucene], [mifos], [netbeans], [ofbiz], [openoffice], [qpid], [sling], [zookeeper] In total, as of 1st February 2019, we're tracking 78 (last month: 81) open issues across 39 projects, median age 75 (last month: 109) days. 49 of those issues have CVE names assigned. 8 (last month: 13) of these issues, across 6 projects, are older than 365 days. ----------------------------------------- Attachment 11: Report from the VP of Data Privacy [Chris Mattmann] ----------------------------------------- Attachment A: Report from the Apache Airflow Project [Bolke de Bruin] ## Description: - Apache Airflow (or simply Airflow) is a platform to programmatically author, schedule, and monitor workflows. When workflows are defined as code, they become more maintainable, versionable, testable, and collaborative. Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command line utilities make performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress, and troubleshoot issues when needed. ## Issues: ## Activity: - Most of our assets have been moved to TL. We might have some remnants here and there, which we try to track down - We released a new version (1.10.2) - We are in the process (or have done so) in promoting one of the contributors to committer. - We are, measured by GitHub stars, the most popular project for data orchestration comparing Apache Oozie, Spotify's Luigi, Pinterest's Pinball and LinkedIn's Azkaban - Note: Apologies for not responding to the question by posting comments, it was unclear how this worked ## Health report: - We have grown from 674 to 712 contributors since our last report. We do monitor for potential committers, but we also see a lot of "hit and run" contributors that particularly add to the 'periphery' of our code. - Since the 1.10.2 release 914 commits have been made ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months ## Committer base changes: - Currently 18 committers. - In process of adding one. ## Releases: - 1.10.2 was released on Tue Jan 22 2019 ## Mailing list activity: - dev@airflow.apache.org: - 576 subscribers (up 5 in the last 3 months): - 660 emails sent to list (883 in previous quarter) ## JIRA activity: - 545 JIRA tickets created in the last 3 months - 383 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment B: Report from the Apache Ambari Project [Jayush Luniya] ## Description: - Apache Ambari simplifies provisioning, managing, and monitoring of Apache Hadoop clusters. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Since the last report, the community released Apache Ambari 2.7.3. This maintenance release resolved 117 issues. The community is working on an Apache Ambari 2.7.4 maintenance release. ## Health report: - The development community and engagement remains strong; we have 102 committers and 48 PMC members on the project. ## PMC changes: - Currently 48 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Ishan Bhatt on Thu Oct 25 2018 ## Committer base changes: - Currently 102 committers. - No new committers added in the last 3 months - Last committer addition was Krisztian Kasa at Thu Jun 21 2018 ## Releases: - 2.7.3 was released on Fri Nov 16 2018 ## Mailing list activity: - Apache Ambari has moved from ReviewBoard to GitBox for code reviews and hence there is no activity on reviews@ambari.apache.org - dev@ambari.apache.org: - 301 subscribers (up 2 in the last 3 months): - 21 emails sent to list (52 in previous quarter) - issues@ambari.apache.org: - 49 subscribers (up 2 in the last 3 months): - 1787 emails sent to list (2840 in previous quarter) - reviews@ambari.apache.org: - 61 subscribers (up 1 in the last 3 months): - 0 emails sent to list (2 in previous quarter) - user@ambari.apache.org: - 477 subscribers (down -2 in the last 3 months): - 18 emails sent to list (28 in previous quarter) ## JIRA activity: - 265 JIRA tickets created in the last 3 months - 228 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment C: Report from the Apache Ant Project [Jan Materne] ## Description: Apache Ant is a Java based build tool along with associated tools. 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. ## Activity: - In progress of fixing some issues with Java 11. - Moved from git-wp to gitbox - archived the "antlib-svn" subproject ## Health report: 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. ## PMC changes: - Currently 23 PMC members. - No new PMC members added in the last 3 months - Last PMC (re)addition was Magesh Umasankar on Fri Jul 06 2018 ## Committer base changes: - Currently 29 committers. - No new committers added in the last 3 months - Last committer addition was Jaikiran Pai at Wed Jun 14 2017 ## Releases: - Last release was Ant 1.10.5 on Fri Jul 13 2018 ----------------------------------------- Attachment D: Report from the Apache Aurora Project [Jake Farrell] Apache Aurora is a stateless and fault tolerant service scheduler used to schedule jobs onto Apache Mesos such as long-running services, cron jobs, and one off tasks. Project Status -------------- The Apache Aurora project has seen a significant slowdown of user and contributor activity over the most recent months. This can partially be attributed to the overall stability and maturity of the project, but more importantly this is due to other external projects that managed to win the developer mindshare within the container orchestration field (e.g., general purpose cloud providers, Kubernetes, ...). The project might be heading towards the Apache Attic in the future, unless the community interest increases again. Community --------- * Currently 21 PMC members * Currently 22 committer * No new PMC members added in the last 3 months. Last PMC addition was Jordan Ly on Thu May 03 2018. * No new committers added in the last 3 months. Last committer addition was Renan DelValle at Sat Jan 27 2018 Issue backlog status since last report: * 0 JIRA tickets created in the last 3 months * 1 JIRA tickets closed/resolved in the last 3 months Mailing list activity since last report: * @dev 9 messages (127 in previous quarter) * @user 2 messages (13 in previous quarter) * @reviews 22 messages (181 in previous quarter) * @issues 8 messages (15 in previous quarter) Releases -------- Last release: * 0.21.0 was released on Sun Sep 09 2018 ----------------------------------------- Attachment E: Report from the Apache Avro Project [Thiruvalluvan M. G.] Apache Avro is a data serialization system with a compact binary format. It is used for storing and transporting schema driven serialized data. The unique features of Avro include automatic schema resolution - when the reader's expected schema is different from the actual schema with which the data was serialized the data is automatically adapted to meet reader's requirements. This report is for the four months starting Oct 1 2018 and ending Jan 31 2019 Activity * Moved to gitbox * Automated testing using Travis CI * 75 JIRA tickets opened by 18 developers * 101 Pull requests opened in Github * 147 issues resolved by 23 contributors * 186 Pull requests merged * 33 pull requests pending * 1 new PMC elected (Fokko) * 2 new committers elected (Tim Perkins and Raymie Stata) * Last release: version 1.8.2 20th May 2017. * Last time a new committer elected: 7 December 2018 * Last time a new PMC elected: 7 December 2018 The project has healthy activities except one major problem: no new release since May 2017. We are working towards a release within the next month or so. There is no outstanding issue requiring Board’s help to resolve. ----------------------------------------- Attachment F: Report from the Apache Bloodhound Project [Gary Martin] Project Description =================== Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing Issues ====== As for previous reports, progress continues to be slow. Releases ======== There have been no releases over the last three months. The last release was towards the end of 2014: * apache-bloodhound-0.8 (11th December 2014) PMC/Committer Changes ===================== There are currently 14 PMC members on the project. The last changes were in April 2017. The last new committers were added in May 2014. The last addition to the PMC was in January 2017 (dammina) Ryan Ollos resigned from the PMC in April 2017. Community & Development ======================= After the progress reported in the November report, progress stalled a bit again. A few opportunities to report to the board have also been missed for which the chair of the project apologises on behalf of the PMC. The PMC has been able to confirm to the board that there is oversight of the project from the PMC that exceeds the requirement of three PMC members. Development effort on Bloodhound has focused on the api of the proposed bloodhound core. The mailing lists remain quiet although after a very recent announcement of proposed updates to the api, it was good to see a positive response from someone who wished to remind the project that the ability to host multiple projects from a single bloodhound instance would be good to address early in the api design. As mentioned in the last report, the chair was expecting to arrange some sprint days to bring interested parties together over the same time. These have not yet happened but should be arranged for the coming months. ----------------------------------------- Attachment G: Report from the Apache BookKeeper Project [Sijie Guo] ## Description: BookKeeper is a scalable, fault-tolerant, and low-latency storage service optimized for append-only workloads. It has been used as a fundamental service to build high available and replicated services in companies like Twitter, Yahoo and Salesforce. It is also the log segment store for Apache DistributedLog and message store for Apache Pulsar. Apache DistributedLog is a high-level API and service layer for Apache BookKeeper, providing easier access to the BookKeeper primitives. It is a subproject of Apache BookKeeper. ## Issues: There are no issues requiring board attention at this time. ## Activity: - 4.9.0 was released on Sat, Feb 6, 2019 - The growth of Apache Pulsar community also help grow the adoption of BookKeeper. This helps building the ecosystem around BookKeeper. ## Health report: - Development continues at a steady pace. We are merging multiple PRs per week on average. - Mailing list and slack discussions are brisk, in particularly around the active projects. ## PMC changes: - Currently 15 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Enrico Olivelli on Fri Feb 23 2018 ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Andrey Yegorov at Fri Feb 09 2018 ## Releases: - 4.9.0 was released on Sat, Feb 6, 2019 - 4.7.3 was released on Fri, Dec 7, 2018 - 4.8.1 was released on Fri, Nov 30, 2018 ## Mailing list activity: - Discussions mostly run on dev@ mailing list, distributedlog lists are mostly unused, now that the project as been merged completely with BookKeeper and users started to use the version bundled with BookKeeper releases. - dev@bookkeeper.apache.org: - 105 subscribers (up 2 in the last 3 months): - 119 emails sent to list (121 in previous quarter) - distributedlog-commits@bookkeeper.apache.org: - 12 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - distributedlog-dev@bookkeeper.apache.org: - 41 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - distributedlog-issues@bookkeeper.apache.org: - 9 subscribers (up 0 in the last 3 months): - 2 emails sent to list (4 in previous quarter) - distributedlog-user@bookkeeper.apache.org: - 26 subscribers (up 0 in the last 3 months): - 0 emails sent to list (0 in previous quarter) - issues@bookkeeper.apache.org: - 8 subscribers (up 0 in the last 3 months): - 1994 emails sent to list (2433 in previous quarter) - user@bookkeeper.apache.org: - 118 subscribers (up 3 in the last 3 months): - 14 emails sent to list (17 in previous quarter) ----------------------------------------- Attachment H: Report from the Apache Brooklyn Project [Geoff Macartney] ## Description: - Apache Brooklyn is a software framework for modelling, monitoring and managing cloud applications through autonomic blueprints. ## Issues: - there are no issues requiring board attention at this time ## Activity: - Some significant activity has been done during this quarter to add support for improved authentication within Brooklyn, by adding plugin based support for OAuth [1]. ## Health report: - The project continues with a regular turnover of pull requests and commits, notably the auth changes mentioned above. - We continue to monitor our community for potential new committers and PMC members with the aim of regularly adding individuals (see "PMC Changes"). ## PMC changes: - Currently 16 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Duncan Grant on Thu Aug 30 2018 ## Committer base changes: - Currently 16 committers. - No new committers added in the last 3 months - Last committer addition was Duncan Grant at Wed Jun 13 2018 ## Releases: - Last release was 1.0.0-M1 on Mon Sep 17 2018 ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ## References [1]https://s.apache.org/mI9H ----------------------------------------- Attachment I: 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 onboarded a new committer in December and had a bit of discussion with him on what he would like to contribute. Activity died down over the holidays and has not picked up since. Hopefully it picks up in Q2. ## Health report: - We have a small PMC presence of 3 active members still able to vote releases. We have voted a new committer in in the last quarter. ## 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.6 on May 12th 2018 ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment J: 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 requiring board attention at this time. ## Activity: We have had a very positive response to our blog and should have some more articles posted shortly. We have also requested a day long track for ApacheCon 2019 and are looking forward to participating. ## Health report: We are continue to track and prioritize issues as we approach 4.0: https://cwiki.apache.org/confluence/display/CASSANDRA/4.0%3A+Open+Issues+by+Component We have a number of community members actively testing snapshots of 4.0 with replays of production workloads using audit logging (http://cassandra.apache.org/blog/2018/10/29/audit_logging_cassandra.html). This in combination with recent improvements in property-based testing (http://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html) has led to the discovery of a number of bugs that would have, in previous major releases, been left for users to discover on their own. ## PMC changes: There are currently 31 PMC members. No new PMC members added in the last 3 months. The last PMC addition was Stefania Alborghetti on Thu Sep 27 2018. ## Committer base changes: There are Currently 51 committers. Chris Lohfink was added as a committer on Sat Dec 01 2018 ## Releases: We recently made the following releases across four versions: - 2.1.21 was released on Mon Feb 11 2019 - 2.2.14 was released on Mon Feb 11 2019 - 3.0.18 was released on Mon Feb 11 2019 - 3.11.4 was released on Mon Feb 11 2019 ## Mailing list activity: Mailing list activity is down for both user and dev lists. This may just be a result of nothing new to discuss given the lack of a major release. dev@cassandra.apache.org: - 1597 subscribers (down -27 in the last 3 months): - 361 emails sent to list (460 in previous quarter) pr@cassandra.apache.org: - 14 subscribers (up 1 in the last 3 months): - 141 emails sent to list (585 in previous quarter) user@cassandra.apache.org: - 2996 subscribers (down -23 in the last 3 months): - 481 emails sent to list (791 in previous quarter) ## JIRA activity: - 128 JIRA tickets created in the last 3 months - 128 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment K: 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 Latest release was created on May 13, 2016. A new release is being discussed. ACTIVITY The vote to move Apache Clerezza to the Attic failed due to the addition of a new committer and PMC member who will help in further development of Apache Clerezza. Refactoring of the Apache Clerezza is more or less completed and the new package structure will be available as a new release. COMMUNITY Apache Clerezza PMC accepted Furkan Kamaci as a new committer and PMC member. Latest change was addition of a new committer and PMC member on 27.12.2018 INFRASTRUCTURE The code repository of Apache Clerezza has been moved successfully to gitbox.apache.org with the help of the infra team. Latest update of the Apache Clerezza Website was in February 2018. ----------------------------------------- Attachment L: Report from the Apache Cocoon Project [Cédric Damioli] ## Description: Web development framework: separation of concerns, component-based. ## Issues: there are no issues requiring board attention at this time ## Activity: Thanks Brett for the heads up last month. I (Cédric) have indeed several times thought about making a release, but never found enough time. It happens that I recently found a bug that I want to be fixed, so this will push me to move forward ! The most recent release is 2.1.12 on 2013-03-14 A few JIRA issues opened or resolved since last report. A little activity on both users and dev mailing-lists, even if still at a low level. The project is mainly in maintenance mode. ## PMC changes: None. Most recent addition: 2012-07-06 ## Committer base changes: None. Most recent addition: 2012-07-06 ----------------------------------------- Attachment M: Report from the Apache Community Development Project [Sharan Foga] ## Description: - The Community Development PMC is responsible for helping people become involved with Apache Projects ## Issues: - No issues require board attention at the moment ## Activity: Ideas and Material for Contributor Onboarding - One of the main topics raised this quarter was around the ways to encourage new contributors by lowering barriers to entry [1] and ways that could help onboard them. Some new contributor onboarding material tailored to Apache is currently being developed by the Open Source Strategy team at Google and community feedback has been very positive [2]. A discussion has also been started about how to recognise non technical contributions [3]. This is an area where community development could help develop materials and processes as well as provide guidance to projects. Paris Open Source Summit - In December we again participated at the Paris Open Source Summit, which is the main open source events in France. We had an ASF booth and over the 2 day summit saw lots of attendees who were keen to know more about the ASF. We also participated in a workshop discussing how the administrative sector could help increase their collaboration with open source foundations and communities. Thanks very much to Herve Boutemy and Olivier Heintz for managing the Apache booth and our participation at this event. Apache Roadshows 2019 - Two Apache Roadshows are currently planned for 2019. The DC Roadshow is being run on 25th March and is being co-ordinated by Kevin McGrail. It will feature over twenty presentations in two tracks and will also include career fair. The Chicago Roadshow is being run on 14th and 14th May and is being co-ordinated Trevor Grant. Several tracks are planned incuding Apache in Adtech, Fintech and Startups. New PMC Member - In January we invited Myrle Krantz to become a new member of the PMC. Myrle has been very active in promoting Apache and as well as helping out at many Apache related events. She will be a great addition to our PMC. FOSDEM - Once again we participated at FOSDEM in Brussels. This year we were located on the ground floor and so had a lot more foot traffic. Thanks very much to Daniel Gruno for the great assortment of Apache giveaways (including some nice warm fleece hats) that people were queuing up to talk to us to get. Several projects were represented at the booth includin Beam, Httpd, Tomcat, Fineract, OFBiz, Kibble and Jena. FOSDEM is great for visibility of the Foundation and as a result we have been invited to participate at even more events for 2019. Thanks very much to all the volunteers that helped out. One thing we trialled a little was the idea of getting people to ‘buy the ASF a coffee’ or ‘buy the ASF a beer’ to get people to think about donating 2 – 5 euro especially if any of the ASF projects had helped them in someway. This could potentially be something to look into further for future events. GSOC - The ASF has applied to be a mentoring organisation for GSoC and projects have been asked to start recording their ideas for tasks on the ComDev JIRA or labelling them with the GSoC tag. ## Health report: This is the second quarter where our monthly blog has slipped and although we have an active mailing list, we are perhaps missing out at promoting things to a wider audience. We are looking at being more organised in our event participation and have asked the community for the events [4] that they think we need to be involved in for 2019. ## PMC changes: - Currently 29 PMC members. - Myrle Krantz was added to the PMC on Mon Jan 07 2019 ## Committer base changes: - Currently 30 committers. - Myrle Krantz was added as a committer on Mon Jan 07 2019 ## Mailing list activity: - Mailing list traffic has decreased probably due to the holiday break even though we have had a lot of popular discussions. - dev@community.apache.org: - 886 subscribers (up 19 in the last 3 months): - 443 emails sent to list (491 in previous quarter) ## JIRA activity: - 10 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months [1] https://s.apache.org/WYpU [2] https://s.apache.org/3ss1 [3] https://s.apache.org/p0LS [4] https://s.apache.org/fKKu ----------------------------------------- Attachment N: Report from the Apache CouchDB Project [Jan Lehnardt] ## Description: - Seamless multi-master sync, that scales from Big Data to Mobile, with an Intuitive HTTP/JSON API and designed for Reliability. ## Issues: - there are no issues requiring board attention at this time. ## Activity: - Big News™: The IBM Cloudant team has started a discussion around replacing the bottom ~2/3s of CouchDB (file storage, btree, distributed computing layer) with FoundationDB, keeping most API semantics, but allowing for faster evolution of much needed CouchDB features while building on a reliable, wait for it, foundation. For now this is a discussion, ranging across many threads covering everyting from FDB governance considerations, the detailed tech bits as they pertain to CouchDB, as well as overall project roadmap. This is sparked a huge, and very fruitful discussion, including a transition phase and long-term support for existing users, who for one reason or another couldn’t do the future transition. Tentatively, this would be CouchDB 4.0 while the next major release would be aimed at being “The best version of CouchDB we can make without FoundationDB”, including several long-awaited features that have either recently landed or are nearing completion at the moment. Curiously, discussing a potential 4.0 has sparked activity around getting 3.0 done sooner. We expect the discussion threads to wrap up before long, after which we should have talked through all the relevant details so we can make an informed Vote. - Preparation of versions 2.3.1 (bugfix) and 2.4.0 (major new features). ## Health report: - The aboforementioned discussion has raised dev@ mail traffic to rarely seen heights. ## PMC changes: - Currently 15 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Nick Vatamaniuc on Tue Nov 07 2017 ## Committer base changes: - Currently 64 committers. - Jay Doane was added as a committer on Sat Jan 05 2019 ## Releases: - 2.3.0 was released on Thu Dec 06 2018 ## Mailing list activity: - Just to show the increase in activity on dev@ alone due to the FoundationDB discussion. - dev@couchdb.apache.org: - 538 subscribers (down -12 in the last 3 months): - 254 emails sent to list (34 in previous quarter) ----------------------------------------- Attachment O: Report from the Apache Creadur Project [Brian E Fox] Apache Creadur creates and maintains a suite of open source software related to the auditing and comprehension of software distributions. Any language and build system are welcomed. Status ------ Creadur is primarily used by other Apache projects to help check for conformity to ASF standards. This is why the project team is primarily comprised of members and committers from other ASF projects. The risk of the project foundering is therefore very low despite the ongoing lack of progress. If someone has an itch to scratch, it will no doubt get fixed. Community --------- In September 2016 Karl Heinz Marbaise was elected to join the PMC / Commit. Releases -------- Apache Rat 0.13 was released Nov 5th, 2018 Apache Rat 0.12 was released in June, 2016 Apache Rat 0.11 was released in August, 2014 Apache Rat 0.10 was released in September, 2013. ----------------------------------------- Attachment P: 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. - Quartz integration 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: Our activity was pretty low in the last months. I hope we will get back to some normal level soon. Otoh we keep on fixing bugs if they arise. ## Health report: As explained already, many parts of DeltaSpike made it into proper EE specs. DS still works great as we are still backward compatible and can run 9 years old code. And it has still parts which are really unique and outstanding. The MicroProfile initiative also tackles some parts of that space. ## PMC changes: - Currently 19 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Harald Wellmann on Thu May 19 2016 ## Committer base changes: - Currently 34 committers. - No new committers added in the last 3 months - Last committer addition was Alexander Falb at Wed Aug 01 2018 ## Releases: - Last release was 1.9.0 on Mon Sep 10 2018 ## JIRA activity: - 8 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Q: Report from the Apache DRAT Project [Tom Barber] ## Description: - Apache DRAT is a distributed, parallelized (Map Reduce) wrapper around Apache RAT™ and other code auditing tools to allow it to complete on large code repositories of multiple file types. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The discussion to start an RC was instigated but not actioned upon due to Chris switching his focus. Discussion will restart about an RC shortly, this can also take in new features in the OODT stack being worked on currently. ## Health report: - We are ready for a 1.0 RC1. - We expect some activity to pick up with 1.0 RC1. - In addition we also expect integration of the Avro integration work from Apache OODT (not a blocker to 1.0RC1 for DRAT) will also spurn some interest. - Slow pace of development, but functioning PMC and look to get 1.0 released. ## PMC changes: - Currently 14 PMC members. - Ahmed Ifhaam was added to the PMC on Thu Aug 30 2018 ## Committer base changes: - Currently 14 committers. - Ahmed Ifhaam was added as a committer on Tue Aug 28 2018 ## Releases: - Chris Mattmann will volunteer to be the RM for Apache DRAT 1.0. We slipped a little but are on target for a CY2018/1st Q 2019 release. ## Mailing list activity: - Mailing list activity took a slight dip. Main reason I believe is that we are waiting to test and integrate Apache OODT 1.9-dev with the AvroRPC module in our code base. It's not a blocker to releasing 1.0 for Apache DRAT but I think Imesha is waiting for that to be tested. Mailing list activity will probably spike for a bit in the next quarter as we roll RC1 for 1.0 Apache DRAT. - dev@drat.apache.org: - 17 subscribers (up 1 in the last 3 months) - 4 emails sent in the past 3 months, 56 in the previous cycle - issues@drat.apache.org: - 10 subscribers (up 0 in the last 3 months) ----------------------------------------- Attachment R: Report from the Apache Drill Project [Arina Ielchiieva] ## Description: - Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Since the last board report, Drill has released version 1.15.0, including the following enhancements: - Add capability to do index based planning and execution - CROSS join support - INFORMATION_SCHEMA FILES and FUNCTIONS were added - Support for TIMESTAMPADD and TIMESTAMPDIFF functions - Ability to secure znodes with custom ACLs - Upgrade to SQLLine 1.6 - Parquet filter pushdown for VARCHAR and DECIMAL data types - Support JPPD (Join Predicate Push Down) - Lateral join functionality was enabled by default - Multiple Web UI improvements to simplify the use of options and submit queries - Query performance with the semi-join functionality was improved - Support for aliases in the GROUP BY clause - Option to prevent Drill from returning a result set for DDL statements - Storage plugin names became case-insensitive - Drill Developer Day was held on November 14, 2018: a variety of technical design issues were discussed, including Apache Arrow integration, Metadata and Resource management, Storage plugins, etc. - Drill User Meetup was held on November 14, 2018: use cases of Drill and indexing support were presented. ## Health report: - The project is healthy. Development activity as reflected in the pull requests and JIRAs is good. - Activity on the dev and user mailing lists are stable. - Three committers were added in the last period. ## PMC changes: - Currently 23 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Charles Givre on Mon Sep 03 2018 ## Committer base changes: - Currently 51 committers. - New commmitters: - Hanumath Rao Maduri was added as a committer on Thu Nov 01 2018 - Karthikeyan Manivannan was added as a committer on Fri Dec 07 2018 - Salim Achouche was added as a committer on Mon Dec 17 2018 ## Releases: - 1.15.0 was released on Mon Dec 31 2018 ## Mailing list activity: - dev@drill.apache.org: - 415 subscribers (down -12 in the last 3 months): - 2066 emails sent to list (2653 in previous quarter) - issues@drill.apache.org: - 18 subscribers (up 0 in the last 3 months): - 2480 emails sent to list (3228 in previous quarter) - user@drill.apache.org: - 592 subscribers (down -5 in the last 3 months): - 249 emails sent to list (310 in previous quarter) ## JIRA activity: - 196 JIRA tickets created in the last 3 months - 171 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment S: Report from the Apache Empire-db Project [Rainer Döbele] ## Description: - Apache Empire-db is a relational database access engine that takes an SQL-centric approach in contrast to object-relational-mapping like with JPA It encapsulates the functionality of a RDBMS in a powerful, vendor independent, intuitive and maintenance friendly API providing a maximum of compile-time-safety. ## Issues: - there are no issues requiring board attention at this time. ## Activity: - After having released version 2.4.7 last October we had to deal with issues regarding database compatibility, especially regarding new versions of Microsoft SQL-Server newer than 2016, which have been requested from users over JIRA. Regarding JIRA we have found, that the mailing notifications had been incorrect, which we asked INFRA to correct. Also we had to deal with the mandatory migration of the GIT repository from git-wip-us.apache.org to gitbox.apache.org. ## Health report: - The project remains healthy as activity in JIRA shows. ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Jan Glaubitz on Sun Jul 10 2016 ## Committer base changes: - Currently 9 committers. - No new committers added in the last 3 months - Last committer addition was Jan Glaubitz at Mon Oct 05 2015 ## Releases: - Last release was empire-db-2.4.7 on Wed Oct 31 2018 ## Mailing list activity: - dev@empire-db.apache.org: - 34 subscribers (down -1 in the last 3 months): - 15 emails sent to list (45 in previous quarter) - user@empire-db.apache.org: - 54 subscribers (up 0 in the last 3 months): - 0 emails sent to list (2 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment T: Report from the Apache Flume Project [Mike Percy] ## Description: Apache Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. ## Issues: There are no issues requiring board attention at this time. ## Activity: This quarter we had a release (Flume 1.9.0) and added a PMC member (Ferenc Szabo). ## Health report: - Quite a few bug fixes and improvements made it in for the 1.9.0 release, including improvements to Kafka support. - The pace of activity slowed down a bit after the new year, likely people busy with other things. ## PMC changes: - Currently 24 PMC members. - Ferenc Szabo was added to the PMC on Sun Jan 27 2019 ## Committer base changes: - Currently 31 committers. - No new committers added in the last 3 months - Last committer addition was Attila Simon at Sat Nov 04 2017 ## Releases: - 1.9.0 was released on Tue Jan 01 2019 ## Mailing list activity: There was quite a bit of discussion and pull request traffic on the dev and issues lists leading up to the 1.9.0 release, while the user list has recently been quiet. - dev@flume.apache.org: - 281 subscribers (up 0 in the last 3 months): - 137 emails sent to list (39 in previous quarter) - issues@flume.apache.org: - 9 subscribers (up 0 in the last 3 months): - 377 emails sent to list (144 in previous quarter) - user@flume.apache.org: - 659 subscribers (down -6 in the last 3 months): - 4 emails sent to list (7 in previous quarter) ## JIRA activity: - 34 JIRA tickets created in the last 3 months - 68 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment U: 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 needing board attention: None. Changes in the PMC membership: None. Last modified: 2013-04-08 Most recent addition: 2009-06-09 New committers: None. Most recent addition: 2009-06-09 None on the horizon. General status: The most recent release is 0.9 on 2011-02-07. This quarter there has again been no activity on any Forrest mail list. So that is two sequential quarters of zero activity. At this report, three other PMC members responded to my draft report. This confirms that there are sufficient people hanging around for us to potentially be able to make a decision. Project status: Activity: Idle 4 people indicated presence: potential for sufficient oversight. Project status: Please see the detailed status notes for the June 2018 report. It seems that it is now time for the PMC to raise the topic on the dev list about moving to the Apache Attic. Security issues published: None. Progress of the project: None. ----------------------------------------- Attachment V: Report from the Apache FreeMarker Project [Dániel Dékány] ## Description: Apache FreeMarker is a template engine, i.e. a generic tool to generate text output based on templates. Apache FreeMarker is implemented in Java as a class library for programmers. FreeMarker 2 (the current stable line) produces releases since 2002. The FreeMarker project has joined the ASF in 2015, and graduated from the Incubator in early 2018. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity was very low in the last 3 months. There's slow progress towards the next micro version. ## 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 release the next micro version (2.3.29) in February. 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), instead of being blocked by 15 years of historical baggage. ## PMC changes: - Currently 7 PMC members. - No changes since the graduation on 2018-03-21 ## Committer base changes: - Currently 7 committers. - No changes since the graduation on 2018-03-21 ## Releases: - 2.3.28 was released on Wed Apr 04 2018 ----------------------------------------- Attachment W: Report from the Apache Geode Project [Karen Miller] ## Description: Apache Geode 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 at this time. ## Activity: - We released v1.8.0, containing 124 improvements and new features, resolving 83 bugs and a total of 380 JIRA tickets - The v1.8.0 release includes the first release of the geode-native source, a C++/C# client API for Geode. - Security enhancements include support for Trust and Keystore rotation, endpoint validation during SSL handshake, and dynamic function security. - Karen Miller succeeded Mark Bretl as Apache Geode PMC Chair. - Added benchmarks to baseline performance - Explored the use of micrometer for exposing metrics of cache operations ## Health report: - Mailing lists remain active and productive. - JIRA tickets show that issues continue to be identified and resolved. - We’re continuing to work on attracting new contributors and making it easier to participate in the community. ## PMC changes: - Currently 46 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Dick Cavender on Tue Feb 20 2018 ## Committer base changes: - Currently 98 committers. - No new committers added in the last 3 months, but several invitations in the pipeline - Last committer addition was Robert Houghton at Mon Oct 01 2018 ## Releases: - 1.8.0 was released on Wed Dec 12 2018 ## Mailing list activity: Mailing lists have remained active and have maintained consistent usage levels. - dev@geode.apache.org: - 193 subscribers (up 3 in the last 3 months): - 465 emails sent to list (825 in previous quarter) - issues@geode.apache.org: - 55 subscribers (up 0 in the last 3 months): - 3342 emails sent to list (4259 in previous quarter) - notifications@geode.apache.org: - 7 subscribers (up 0 in the last 3 months): - 2500 emails sent to list (1865 in previous quarter) - user@geode.apache.org: - 250 subscribers (up 0 in the last 3 months): - 94 emails sent to list (212 in previous quarter) ## JIRA activity: - 357 JIRA tickets created in the last 3 months - 314 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment X: Report from the Apache Giraph Project [Dionysios Logothetis] ## Description: - Giraph is a Bulk Synchronous Parallel framework for writing programs that analyze large graphs on a Hadoop cluster. Giraph is similar to Google's Pregel system. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Moved repository to gitbox. - Only a few commits this last quarter, but an important reliability fix was made. ## Health report: - Committee Health score: 0.62 (Mostly Okay) - This last quarter there were only a few commits. We have a number of pull requests that are still pending review due to increased workload for our most experienced/active reviewers. I'm currently trying to pull into the project a new member, but I expect it will take time until they ramp up and are able to review code. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Dionysios Logothetis on Sun Apr 22 2018 ## Committer base changes: - Currently 20 committers. - No new committers added in the last 3 months - Last committer addition was Dionysios Logothetis at Mon Apr 23 2018 ## Releases: - Last release was 1.2.0 on Thu Oct 20 2016 ## Mailing list activity: - Activity in our mailing list was reduced relative to the last quarter, but there were a couple of interactions involving a PMC member that had been inactive for some time. I will be reaching out to see whether there is any opportunity to involve them more. - dev@giraph.apache.org: - 269 subscribers (up 1 in the last 3 months): - 61 emails sent to list (80 in previous quarter) - user@giraph.apache.org: - 441 subscribers (down -1 in the last 3 months): - 5 emails sent to list (19 in previous quarter) ## JIRA activity: - See comments above about activity this quarter. - 6 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Y: Report from the Apache Gora Project [Kevin Ratnasekera] ## Description: The Apache Gora open source framework provides an in-memory data model and persistence for big data. Gora supports persisting to column stores, key value stores, document stores, distributed in-memory key/value stores, in-memory data grids, in-memory caches, distributed multi-model stores, and hybrid in-memory architectures. Gora also enables analysis of data with extensive Apache Hadoop MapReduce and Apache Spark support. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Gora community is currently working towards our next release, there are pull requests sent on three new modules on integration Apache Flink, Apache Pig and Apache Lucene. Hopefully we could get these PR s merged soon once the reviews are addressed. - We are also planning to participate on GSoC 2019, community has already proposed some proposals for this. ## Health report: - The Gora project is in good health. We could observe community participation from actively reviewing PRs. ## PMC changes: - Currently 27 PMC members. - Carlos Muñoz was added to the PMC on Wed Dec 05 2018 ## Committer base changes: - Currently 27 committers. - No new committers added in the last 3 months - Last committer addition was Carlos Muñoz at Tue Nov 13 2018 ## Releases: - Last release was 0.8 on Tue Sep 19 2017 ## Mailing list activity: - There a slight drop of number of email count from previous quarter due to holiday season. - dev@gora.apache.org: - 72 subscribers (up 0 in the last 3 months): - 105 emails sent to list (142 in previous quarter) - user@gora.apache.org: - 75 subscribers (up 0 in the last 3 months): - 1 emails sent to list (1 in previous quarter) ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 month ----------------------------------------- Attachment Z: Report from the Apache Griffin Project [William Guo] ## Description: - Apache Griffin is an open source Data Quality solution for Big Data, which supports both batch and streaming mode. It offers an unified process to measure your data quality from different perspectives, helping you build trusted data assets, therefore boost your confidence for your business. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - There is no specific activity in this month. ## Health report: - The mails and commits activity are as good as usual. ## PMC changes: - Currently 17 PMC members, no change. ## Committer base changes: - Currently 17 committers, no change. ## Releases: - 0.4.0 was released on Fri Jan 05, 2019 ## Mailing list activity: - dev@griffin.apache.org: - 77 subscribes - 284 emails sent by 29 people, divided into 143 topics in September. - 393 emails sent by 44 people, divided into 66 topics in October. - 205 emails sent by 48 people, divided into 43 topics in November. - 221 emails sent by 41 people, divided into 55 topics in December. - 109 emails sent by 27 people, divided into 46 topics in January. ## JIRA activity: - 20 JIRA tickets created in the last 3 months - 12 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AA: Report from the Apache Groovy Project [Paul King] ## Description: - Apache Groovy is a multi-faceted programming language for the Java platform. Groovy is a powerful, optionally typed and dynamic language, with static-typing and static compilation capabilities, aimed at multiplying developers’ productivity thanks to a concise, familiar and easy to learn syntax. It integrates smoothly with any Java program, and immediately delivers to your application powerful features, including scripting capabilities, Domain-Specific Language authoring, first class functional programming support and runtime and compile-time meta-programming. ## Issues: - Outstanding issue: Website: some more progress has been made in the last quarter but this task is not quite finished - work will continue. - New issue: We have had additional requests (e.g. [1]) from Groovy language users to be able to contribute to Groovy's development through crowdfunding. Our understanding is that the ASF doesn't permit "cash for code" so we have suggested that a separate entity be set up for this purpose that can act independently to but in accordance with ASF guidelines. Our users didn't know what might be involved in setting up such an entity and asked us to help. With this in mind I have set up a strawman open collective site[2]. It is not currently active - so please don't distribute the URL publicly at this stage. My goal will be to hand this site over to whoever will take on board running the collective. I don't know whether that will include myself at this stage. My intention of creating the strawman was for feedback purposes. It's often easier to get feedback from a concrete example than to ask for feedback on an abstract idea and, if the wording is close to what we would consider acceptable from an ASF point of view, we can finesse the words. So, we are seeking feedback rather than having a strong feeling that the current wording on that site is fixed in stone. I have requested feedback from a branding/trademark point of view on the trademarks email address but we are keen on feedback on the whole concept from the board. Our take on this is that this initiative will be beneficial to the project, so we would like to help get it off the ground so long as normal Apache procedures aren't compromised. We don't believe this will be the case and are also happy to act as somewhat of a guinea pig project in this regard in case other projects would like to go down this path. [1] https://lists.apache.org/thread.html/3e21470ea5dd59de50401e571c151ad820564ba52481d880f6a46216@%3Cusers.groovy.apache.org%3E ## Activity: - This quarter, 165 commits were contributed from 12 contributors including 8 non-committer contributors (4 new). ## Health report: - Committee Health score: Healthy - Apache Groovy was downloaded 30 million times during the last quarter of 2018. We closed the year 2018 with a record number of downloads (across Maven Central and JFrog Bintray) with over 100 million downloads, up from 23 million in 2017 and 13 million in 2016. - Also, Groovy re-entered the TIOBE top 20 most popular programming languages[3]. While not a super reliable metric for health due to its volatility, it's a good indicator that Groovy remains an active, widely-used and relevant language. [3] https://jaxenter.com/tiobe-index-february-2019-groovy-155403.html ## PMC changes: - Currently 10 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andres Almiray on Thu May 31 2018 ## Committer base changes: - Currently 18 committers. - No new committers added in the last 3 months - Last committer addition was Remko Popma at Sat Jul 07 2018 ## Releases: - 2.4.16 was released on Thu Dec 13 2018 - 2.5.5 was released on Mon Dec 24 2018 - 2.5.6 was released on Mon Feb 04 2019 - 3.0.0-alpha-4 was released on Sun Dec 30 2018 ## Mailing list activity: - Mailing list activity has remained steady. - users@groovy.apache.org: - 417 subscribers (down -4 in the last 3 months): - 117 emails sent to list (92 in previous quarter) - dev@groovy.apache.org: - 235 subscribers (down -1 in the last 3 months): - 227 emails sent to list (460 in previous quarter) ## JIRA activity: - 113 JIRA tickets created in the last 3 months - 102 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AB: Report from the Apache Hama Project [Chia-Hung Lin] ----------------------------------------- Attachment AC: Report from the Apache Helix Project [Kishore G] ## Description: - A cluster management framework for partitioned and replicated distributed resources ## Issues: - There are no issues requiring board attention at this time. ## Health report: - Release 0.8.3 was a bit delayed, but is in preparation, we expect it to be out in end of Feb, 2019. - There is regular level of activities on commits, pull requests and releases. - Dev mail list activities was normal, user email activities dropped. We are in progress of moving the discussion into Slack channels. - Many of current committers are not quite active in terms of daily developments and pull request review, need to look for potential new committers from the community. ## PMC changes: - Currently 18 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Junkai Xue on Mon Jul 03 2017 ## Committer base changes: - Currently 19 committers. - No new committers added in the last 3 months - Last committer addition was Jiajun Wang at Fri Jul 13 2018 ## Releases: - Last release was 0.8.2 on Sat July 25 2018 ## Mailing list activity: - dev@helix.apache.org: - 69 subscribers (down -1 in the last 3 months): - 147 emails sent to list (150 in previous quarter) - user@helix.apache.org: - 104 subscribers (up 0 in the last 3 months): - 4 emails sent to list (53 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 AD: Report from the Apache HTTP Server Project [Daniel Gruno] ## Description: The Apache HTTP Server Project is an effort to develop and maintain an open-source HTTP server for modern operating systems including UNIX and Windows. The goal of this project is to provide a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards. ## Issues: There are no issues requiring board attention at this time ## Activity: - The Apache HTTP Server 2.4.38 was released in January, fixing some bugs, enhancing features, and addressing three CVEs; two at a low severity (CVE-2018-17199, CVE-2018-17189) as well as one with an important severity (CVE-2019-0190), though the latter only applied to specific bleeding-edge configurations of httpd. - Stefan Sperling was added to the PMC. - It was decided to close down some unused mailing lists. - HTTPd was represented at FOSDEM (qua ASF's booth there), and as is often the case, was the baseline for many discussions and questions at the table. - There are plans among committers to represent HTTPd at the HTTP Workshop in Amsterdam, April 2-4 2019. TBD. ## Health report: The project project remains healthy and community oversight is definitely present at all times. Code/commit-wise, we had a slower quarter (down some ~45% in activity compared to previous quarter), with the holidays likely being to blame there. Looking at the bigger picture, it's safe to say that HTTPd is a mature project, with activity having leveled out many years ago - in fact, we are at the same engagement levels now as eight years ago, and holding pretty steady at 30-40 people active on the codebase and 250-300 people on the issue trackers, while email traffic has steadily but slowly declined, leveling out over the past two years. While the shift from one or two major HTTP servers to a multitude of different software projects and cloud-based setups over the past decade has moved some traffic away from HTTPd, another important aspect is aforementioned maturity, in that a lot of questions and answers are much more readily available to users seeking information than they were before, and as such, new queries are less frequent, with services like google, reddit, stackoverflow (et al) covering a lot of ground. A positive take-away from here is that our developer community is now more freed up to focus on enhancing our project and fixing whatever bugs remain. We still maintain a very mature contributor community, with the majority of contributors having had well above 5+ years of experience with the httpd project, and only ~37% with fewer than five years of experience. As we seem very capable of retaining the more experienced contributors, I do not see any concerns here, though reaching out to new people is, of course, always worth exploring. The PMC has more than sufficient oversight, and we have no concerns on that front. ## PMC changes: - Currently 53 PMC members. - Stefan Sperling was added to the PMC on Thu Jan 24 2019 ## Committer base changes: - Currently 122 committers. - No new committers added in the last 3 months - Last committer addition was Sebastian Bazley at Sat Jul 14 2018 ## Releases: - 2.4.38 was released on Mon Jan 21 2019 ## Mailing list activity: Traffic to the big lists (dev+user) were a tad quieter over this past quarter compared to other quarters, with Christmas and New Years taking some of the credit. BugZilla seemed surprisingly busy, but that appears to largely be a cosmetic change to many tickets by one user causing a lot of automated emails. A few lists, which have been receiving little to no traffic over the past few years, have been slated for decommissioning. The top three lists are as follows: - users@httpd.apache.org: - 2495 subscribers (down -22 in the last 3 months): - 297 emails sent to list (483 in previous quarter) - dev@httpd.apache.org: - 825 subscribers (up 0 in the last 3 months): - 227 emails sent to list (663 in previous quarter) - bugs@httpd.apache.org: - 317 subscribers (down -5 in the last 3 months): - 1111 emails sent to list (405 in previous quarter) ## Issue tracker Statistics: As with the mailing list traffic, the large number of tickets closed in this quarter is related to some cleanups, rather than increased continuous effort. - 51 Bugzilla tickets created in the last 3 months - 749 Bugzilla tickets resolved in the last 3 months ----------------------------------------- Attachment AE: Report from the Apache HttpComponents Project [Asankha Chamath Perera] ## Description: - The Apache HttpComponents project is responsible for creating and maintaining a toolset of low-level Java components focused on HTTP and associated protocols ## Issues: - There are no issues requiring board attention at this time. - There are several casual contributors to the project. We are in the process of evaluating one contributor for committership. A formal vote is expected soon ## Activity: - The repos got migrated to GitBox. The team is still working toward completing HttpCore 5.0 and HttpClient 5.0 BETA development phase and reaching GA milestone. ## Health report: - Overall the project remains active. Although established in late 2007 the project remains stable and active as seen by JIRA and Emails. - The number of emails could be seen as low, but it is stable like the state of the project, and we still have interested people contributing. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michael Osipov on Mon Aug 24 2015 ## Committer base changes: - Currently 19 committers. - No new committers added in the last 3 months - Last committer addition was Ryan Schmitt at Wed Nov 14 2018 ## Releases: - HttpClient 4.5.7 GA was released on Thu Jan 24 2019 - HttpClient 5.0-beta3 was released on Mon Dec 17 2018 - HttpCore 4.4.11 GA was released on Mon Jan 21 2019 - HttpCore 5.0-beta6 was released on Thu Dec 06 2018 ----------------------------------------- Attachment AF: Report from the Apache Ignite Project [Denis A. Magda] ## Description: - Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Ignite 2.7 version released in December, 2018. It goes with MVCC and Transactional SQL beta, TensorFlow integration, Node.JS/Python/PHP support, Transparent Data Encryption and other improvements: https://blogs.apache.org/ignite/entry/apache-ignite-2-7-deep - Presently the community is focused on enabling full Java 11 support. ## Health report: - So far so good, we're accepting more committers and PMC members. ## PMC changes: - Currently 27 PMC members. - Nikolay Izhikov was added to the PMC on Mon Nov 19 2018 ## Committer base changes: - Currently 43 committers. - New commmitters: - Alex Plehanov was added as a committer on Fri Nov 16 2018 - Andrey Mashenkov was added as a committer on Fri Feb 08 2019 - Igor Seliverstov was added as a committer on Fri Nov 16 2018 - Ilya Kasnacheev was added as a committer on Mon Nov 26 2018 - Pavel Kovalenko was added as a committer on Tue Nov 20 2018 ## Releases: - 2.7.0 was released on Wed Dec 05 2018 ## Mailing list activity: - dev@ignite.apache.org: - 421 subscribers (up 13 in the last 3 months): - 3128 emails sent to list (3972 in previous quarter) - ci@ignite.apache.org: - 5 subscribers (up 0 in the last 3 months) - issues@ignite.apache.org: - 33 subscribers (up 0 in the last 3 months): - 9724 emails sent to list (9519 in previous quarter) - notifications@ignite.apache.org: - 8 subscribers (up 8 in the last 3 months): - 1456 emails sent to list (0 in previous quarter) - services@ignite.apache.org: - 7 subscribers (up 0 in the last 3 months) - user@ignite.apache.org: - 769 subscribers (up 43 in the last 3 months): - 1898 emails sent to list (1794 in previous quarter) ## JIRA activity: - 1067 JIRA tickets created in the last 3 months - 773 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AG: Report from the Apache Impala Project [Jim Apple] ## Description: Impala is a high-performance distributed SQL engine. ## Activity: The previous three months had 330 patches to the master branch, while this three-month period had 237. This is likely a seasonal dip. Prominent work in the last three months includes: - The revival of the 2.x branch - Modernization of the documentation of the HBase integration - Significant changes to enable Impala to run better in containers - Improvements to the user experience of dealing with changing metadata - Multiple improvements to profile statistics - Numerous build process improvements for performance - Support for reading additional Parquet field types ## Health report: The project remains healthy and metrics (number of commits, bugs filed, and mailing list activity) remain healthy. Three new contributors had patches committed. ## PMC changes: - Currently 28 PMC members. - Zoltán Borók-Nagy was added to the PMC on Thu Jan 03 2019 ## Committer base changes: - Currently 45 committers. - Paul Rogers was added as a committer on Mon Feb 04 2019 - Zoram Thanga was added as a committer on Fri Nov 16 2018 ## Releases: - 3.1.0 was released on Wed Dec 05 2018 ## Mailing list and JIRA activity: Activity dropped, consistent with a seasonal dip during US holidays that Impala sees every year: reviews@, issues@, dev@ traffic decreased by about 30%. ----------------------------------------- Attachment AH: Report from the Apache Incubator Project [Justin Mclean] {{{ Incubator PMC report for February 2019 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are presently 51 podlings incubating. During the month of January, podlings executed 3 distinct releases. We added no new IPMC members and had no IPMC members retire. We have one new podling Hudi. No project graduated last month but several podlings are heading towards graduation in the next few months. BatchEE took a vote to go to Apache Geronimo or TLP and decided on TLP and are back to being stuck in trying to graduate. One podling failed to report this month BRPC and one podling failed to get sign off from it mentors Tamaya. They been asked to report next month. There was one IP clearance. The mentor situation is continuing to improve. One of the mentors for the new Hudi project realised he didn't have the time be be able to give to the project and stood down. Thanks to him for being able to recognising that he wasn't going to be an effective mentor. Other mentors stepped forward to do the job. We have a problem with unapproved releases. A spot check on some (not all) projects reporting this month showed that five projects were making unapproved releases. Hopefully that's a statical aberration, but it seems likely that we probably have more codlings making unapproved releases than this. This has been brought up one the general list and I see a few projects have taken note of it. Three of the projects Doris, Pinot and Sharding Sphere responded quickly and removed the releases. SDAP is addressing the issue. ECharts is a little reluctant to remove the releases due to the high use and popularity of the project and is trying to find another way of resolving the situation. Mentors are working with them to resolve the situation. ECharts was also found to hosting a Chinese version of their incubating site at echarts dot baidu dot com. The PPMC is also dealing with this. A reminder to all incubating projects and mentors that all releases and distributions advertised to the general public need to be approved by the PPMC and IPMC. This includes docker, github, PyPi, npm and any other platform for publishing releases, and also covers release candidates. Nightly builds for project-internal use clearly marked as "snapshot" or "prerelease" (or similar) can be made available to project contributors. If in doubt please ask your mentors or on the incubator general list. Superset has not made an Apache release but is making progress towards one. They accidentally published a release candidate to GitHub but sorting that out. There was also an interesting discussion on binary releases on legal-discuss that could have some impact on the incubator. New new project creating ASF training material may either go to straight to TLP or via the incubator. This did raise a few questions about how initial committers are selected. * Community New IPMC members: - None People who left the IPMC: - None * New Podlings - Hudi * Podlings that failed to report, expected next month - BRPC - Tamaya * Graduations The board has motions for the following: - Unomi? * Releases The following releases entered distribution during the month of January: - Apache Dubbo 2.7.0 - Apache SkyWalking 6.0.0-GA - Apache Dubbo Spring Boot 0.2.1 and 0.1.2 * IP Clearance - Apache Arrow Rust DataFusion * Legal / Trademarks N/A * Infrastructure N/A * Miscellaneous - vote to shut down some old unused incubator lists - discussion on what to do with retired podling repositories ---------------------------------------------------------------------- Table of Contents Doris ECharts Edgent Heron Hudi Iceberg IoTDB PageSpeed Pinot Ratis S2Graph SDAP ShardingSphere Tamaya Toree Unomi ---------------------------------------------------------------------- -------------------- 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 issues to address in the move towards graduation: 1. Resolve IP and Build Issues. 2. Make a Successful First Apache Release. 3. Grow the community encouraging patches and recognizing sustained contributions by adding as Committers and PPMC members. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? A new mentor will add to Doris community. How has the project developed since the last report? Excluding merges, 9 authors have pushed 21 commits to master and 26 commits to all branches. On master, 240 files have changed and there have been 8,984 additions and 2,191 deletions. 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: Still working towards an Apache Release. Made 0.9.0 legacy releases just after entering the Incubator on 2018-07-18 and it failed to approve due to license and build issues. We have fixed all license issues and improved building scripts, also provide a docker environment for building. We Will now focus on making a successful Apache Release. When were the last committers or PPMC members elected? N/A. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes, our mentors have been helpful and responsive. Signed-off-by: [X](doris) Dave Fisher Comments: The podling is making progress towards an Apache Release. There is a candidate and VOTE thread on general@. [ ](doris) Luke Han Comments: [X](doris) Willem Ning Jiang Comments: [ ](doris) Shaofeng Shi Comments: IPMC/Shepherd notes: Justin Mclean: Please addd something about the unapproved releases. Thanks for quickly fixing this, but going through my notes I can see this is the second time this has happened. What can be done to stop a third? -------------------- ECharts ECharts is a charting and data visualization library written in JavaScript. ECharts has been incubating since 2018-01-18. Three most important issues to address in the move towards graduation: 1. Initiating a new release candidate (v4.2.1-rc1) on 2019-01-25. 2. Discussing having a new committer. 3. Discussing develop and release workflow. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? 1. The entrance of Website with Chinese version is under discussion. 2. Currently, the latest version on npm is an rc version. We are working on retagging or deprecating it. 3. Legal problems are under discussion about third party license header. How has the community developed since the last report? More issues are in English now due to our encouragement. How has the project developed since the last report? The project has been improved and we issued a new release candidate on 2019-01-25. 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: 2018-08-04 When were the last committers or PPMC members elected? NA. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes. Signed-off-by: [ ](echarts) John D. Ament Comments: [X](echarts) Kevin A. McGrail Comments:I will continue to work with the podling to improve things especially regarding unofficial releases. [X](echarts) Dave Fisher Comments: We have provided guidance to the podling about pre-Apache releases and unapproved releases. There is a thread which discusses an issue where code was inspired by code another a different license, but this was not a copy. If there is no conclusion on legal-discuss@ then we will need to ask on a LEGAL JIRA. IPMC/Shepherd notes: Justin Mclean: I think this report could have more detail and misses a number of things that are report worthy. Next time carefully go though the mail list and add anything that the IPMC (and board) would want to know about. -------------------- Edgent Apache Edgent is a programming SDK and micro-kernel style runtime that can be embedded in gateways and small footprint edge devices enabling local, real-time, analytics on the continuous streams of data coming from equipment, vehicles, systems, appliances, devices and sensors of all kinds (for example, Raspberry Pis or smart phones). Working in conjunction with centralized analytic systems, Apache Edgent provides efficient and timely analytics across the whole IoT ecosystem: from the center to the edge. Edgent has been incubating since 2016-02-29. Three most important issues to address in the move towards graduation: 1. Re-creating a working community 2. Re-populating the PPMC 3. Replenishing the group of mentors Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? For the past months, there has been very few activity in the project There have been a hand full of Emails from external peoples in the last 3 months but the activity in the project has been solely by me (Julian) and Christofer Dutz writing emails without getting any form of response from the rest of the committers, PPMCs or mentors The main problem we have is that the only active people in the project came in Late and are not that firm with the codebase. Currently, we have a codebase for which we have a detailed understanding of the build, but almost none of the code itself. Furthermore, there has been a lot of activity in other projects and generally edge processing has developed further in the recent years. Thus, there is some discussion going on about the core or the aim of the project to keep its significance and uniqueness. How has the community developed since the last report? * Total, we have 82 subscribers to our mailing list, an increase of 5 since the last report. * There has been one questions asked by users and little discussions about these issues on the list * Julian Feinauer has joined the PPMC on 2018-11-29 * On April, 4th, Julian Feinauer will Talk about Edgent on the building iot 2019 How has the project developed since the last report? * According to JIRA, 0 new issue were added and none were resolved in the last 90 days * The repositories were migrated to gitbox * 2 commits were made in the last 90 days. How would you assess the podling's maturity? After the withdrawal of most of the active committers and PPCM members currently a new committer, PPMC and mentor-base has to be built. Currently we try to re-gain the focus of edgent to Start to rebuild the community and resume development. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-12-14 Apache Edgent 1.2.0 When were the last committers or PPMC members elected? In August 2017, we added Christofer Dutz as a new committer and PPMC member. In November 2018, we added Julian Feinauer as a new committer and PPMC member. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. I just double checked, but it seems our mentors are not existent there had been one or two issues where feedback was explicitly asked for, but both the PPMC as well as all mentors remained silent. Except Justin mentioning the absence of mentors. Christofer Dutz joined as new Mentor and is active in the project. Signed-off-by: [ ](edgent) Luciano Resende Comments: [X](edgent) Justin Mclean Comments: [x](edgent) Christofer Dutz 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 issues to address in the move towards graduation: 1. Making a new release (0.20.1). Formalize the release CI jobs under Apache infra. 2. Making several Releases. 3. Continuing to grow the community. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None at this time. How has the community developed since the last report? The community has been growing. Monthly meetups have been regularly and successfully organized. We have seen new users interested in Heron and community has been discussing and working on different ideas such as Streamlet API, Heron Spouts and Bazel upgration.In November 2018 the first Apache release was done following the Apache process and we are working on the next release with artifacts to make Heron easier for users to access. How has the project developed since the last report? There have been mainly bug fixes and improvements to existing features. Some to note are: * Works towards Apache release with binaries and artifacts. Currently fixing build scripts and jobs. * New functions in Streamlet API * Community initiated a new Heron-Spouts project * Fixes for Helm Charts specific to AWS clusters * Current work in progress to support the newest version of Bazel How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [X] Working towards first release (binaries & artifacts) [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: Dec 2018(0.20.0-incubating, source only release) When were the last committers or PPMC members elected? 3 new committers were elected and invited in Dec 2018. Welcome Ali Ahmed, Boyang Jerry Peng and Ning Wang. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Mentors are responsive and helpful. Signed-off-by: [X](heron) Dave Fisher Comments: The podling needs to discuss more community activity on the dev list. They recently responded to a ping to start mentioning and advertising monthly Meetups on list. [ ](heron) Jake Farrell Comments: [ ](heron) Jacques Nadeau Comments: [ ](heron) Julien Le Dem Comments: [ ](heron) P. Taylor Goetz Comments: IPMC/Shepherd notes: -------------------- Hudi Hudi provides atomic upserts and incremental data streams on Big Data Hudi has been incubating since 2019-01-17. Three most important issues to address in the move towards graduation: 1. Make frequent releases as per Apache guidelines 2. Grow community 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None so far How has the community developed since the last report? Project's still being setup How has the project developed since the last report? 1. Initial set of committers have filed ICLA 2. Jira and Github repo have been setup 3. Mailing lists have been setup How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup [ ] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: Project's still being established When were the last committers or PPMC members elected? Initial set of committers added to the project Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. The mentors have been very helpful in getting this podling established. No open issues. Signed-off-by: [X](hudi) Thomas Weise Comments: [X](hudi) Luciano Resende Comments: [ ](hudi) Kishore Gopalakrishnan Comments: [X](hudi) Suneel Marthi Comments: IPMC/Shepherd notes: -------------------- Iceberg Iceberg is a table format for large, slow-moving tabular data. Iceberg has been incubating since 2018-11-16. Three most important issues to address in the move towards graduation: 1. Update build for Apache release, add LICENSE/NOTICE to Jars. 2. Make the first Apache release. (https://github.com/apache/incubator-iceberg/milestone/1) 3. Grow the Iceberg community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * No issues that require attention. How has the community developed since the last report? * Pull requests from 6 contributors were merged, 7 new contributors How has the project developed since the last report? * Submitted evidence for podling name search: PODLINGNAMESEARCH-163 * Netflix submitted a revised trademark agreement for counter-signing * Abstracted data file locations for community use cases * Reviewing proposed API update for file stream encryption plugins * New contributor highlights: - A new contributor is fixing case sensitivity in expressions - A new contributor opened a PR to add a startsWith predicate - A new contributor reviewed 4 pull requests and opened another How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup (name clearance approval pending) [X] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: None yet When were the last committers or PPMC members elected? None yet Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes. Signed-off-by: [X](iceberg) Ryan Blue Comments: dev list traffic appears to be increasing also [ ](iceberg) Julien Le Dem Comments: [ ](iceberg) Owen O'Malley Comments: [x](iceberg) James Taylor Comments: [X](iceberg) Carl Steinbach Comments: From dev list: "Looks good to me. +1" IPMC/Shepherd notes: -------------------- IoTDB IoTDB is a data store for managing large amounts of time series data such as timestamped data from IoT sensors in industrial applications. IoTDB has been incubating since 2018-11-18. Three most important issues to address in the move towards graduation: 1. Release the first version; 2. Complement the left English documents and supply more design documents to help new developers. 3. Attract more contributors; Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - no. How has the community developed since the last report? - The code repository has been transferred to the ` apache/incubator-iotdb` repository. - The website of `iotdb.apache.org` is updated: (1) Document with English version is available; (2) Other introduction pages, such as `Tools`, `Community` and ` Development` are updated. - Mail list: (1) 490 emails sent by 26 people, divided into 350 topics; (318 mails are from GitBox, for notifying code-review results). (2) a new mail list reviews@iotdb.apache.org is created; (3) two new contributors are involved: Jiaye Wu, Felix Cheung; - The community begin to use JIRA issues and Confluence. How has the project developed since the last report? - All source codes are re-organized: (1) package names are changed to `org.apache.iotdb.*`; (2) All textual files are attached with ASF header; - Apache Jenkins Pipeline was firstly passed at 2019.01.22 - 13 issues are opened on JIRA, 3 of them are closed; - hundreds of vulnerabilities and thousands of code smells are detected by Sonar, 2/3 of them are fixed; - 34 PR are submitted on Github, 24 of them are closed; 10 of them are in code-review process. How would you assess the podling's maturity? - newborn. Please feel free to add your own commentary. [ ] Initial setup [x] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: - N/A When were the last committers or PPMC members elected? - N/A Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. - very Helpful Signed-off-by: [X](iotdb) Justin Mclean Comments: [X](iotdb) Christofer Dutz Comments: [X](iotdb) Willem Ning Jiang Comments: [ ](iotdb) Joe Witt Comments: IPMC/Shepherd notes: -------------------- PageSpeed PageSpeed represents a series of open source technologies to help make the web faster by rewriting web pages to reduce latency and bandwidth. PageSpeed has been incubating since 2017-09-30. Three most important issues to address in the move towards graduation: 1. The project needs more active developers. 2. Create a first release 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The number of active developers is low. It was suggested that a release may help attract community members. This was started, but stalled because of us feeling that we wanted to land a certain bug-fix. This release process will be re-spun and we should have a first incubator release candidate ready for review somewhere in the next couple of weeks. How has the community developed since the last report? One new developer was invited to be added as a committer, but ended up declining. How has the project developed since the last report? There have been significant contributions to the core product, which is an improvement. Frequency is still low. How would you assess the podling's maturity? [ ] Initial setup [X] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: XXXX-XX-XX (First release being prepared, finally) When were the last committers or PPMC members elected? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Mentors have been helpful. Signed-off-by: [ ](pagespeed) Jukka Zitting Comments: [ ](pagespeed) Leif Hedstrom Comments: [*](pagespeed) Nick Kew Comments: As ever, ample git activity, very little discussion on-list. [ ](pagespeed) Phil Sorber 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 issues to address in the move towards graduation: 1.Improving documentation 2.Cutting a release 3.Building community contribution Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? We have had interest from Slack to contribute to https://github.com/apache/incubator-pinot/issues/2798 How has the project developed since the last report? We are preparing for a release in Feb. - Source file headers have been updated to include Apache licenses. - Package names moved from com.linkedin to org.apache. - Additional work related to this effort can be tracked via https://github.com/apache/incubator-pinot/pull/3722 The website (https://pinot.apache.org/) has been updated. Primary changes include updated landing page and documentation now links to updated read-the-docs. All previously released bits have been removed. How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup [ ] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: N/A When were the last committers or PPMC members elected? I believe this was soon after our incubation. @kishoreg may have more information on this. (kishoreg confirmed no new committer) Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes, the mentors have been very helpful and have responded in a timely manner. Signed-off-by: [ ](pinot) Kishore Gopalakrishna Comments: [ ](pinot) Jim Jagielski Comments: [ ](pinot) Roman Shaposhnik Comments: [X](pinot) Olivier Lamy Comments: [X](pinot) Felix Cheung Comments: dev@ discussions are picking up, great job! IPMC/Shepherd notes: Justin Mclean: Please mention the issue of unapproved releases. Thanks for resolving this quickly. -------------------- Ratis Ratis is a java implementation for RAFT consensus protocol Ratis has been incubating since 2017-01-03. Three most important issues to address in the move towards graduation: 1. Have a GA release. 2. Complete graduation template. 3. Need name search. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? 5 new contributors have been added. Total 58 contributors currently. 20 committers. How has the project developed since the last report? 50 new patches committed. Active work on multiple projects. 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 [X] Nearing graduation Date of last release: 2018-08-15: Ratis-0.2.0 2018-12-06: Ratis Thirdparty 0.2.0 2019-01-31: Last snapshot release When were the last committers or PPMC members elected? 2018-12-05: Rajeshbabu Chintaguntla added as a committer. 2018-12-10: Sergey Soldatov added as a committer. 2018-12-26: Vladimir Rodionov added as a committer. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Mentors have been helpful. Signed-off-by: [x](ratis) Jakob Homan Comments: [ ](ratis) Uma Maheswara Rao G Comments: [x](ratis) Devaraj Das Comments: IPMC/Shepherd notes: -------------------- 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 issues to address in the move towards graduation: 1. Make the third release. 2. Attract more users and contributors. 3. Build the developer community in both size and diversity. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? * Adding two committer. * One more mentor has joined. * There were some questions and answers from the community about the deployment of S2Graph. How has the project developed since the last report? * We are overhauling documentation(S2GRAPH-246) - Integrate gitbook into the project. * New HTTP interface integration(S2GRAPH-248) 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? * 2018-12: Jong Wook Kim * 2018-12: Hyunsung Jo Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. * Our mentor is very helpful and responsive. Signed-off-by: [ ](s2graph) Sergio Fernández Comments: [X](s2graph) Woonsan Ko Comments: IPMC/Shepherd notes: -------------------- SDAP SDAP is an integrated data analytic center for Big Science problems. SDAP has been incubating since 2017-10-22. Three most important issues to address in the move towards graduation: 1. Make official SDAP (Incubating) Release 2. Improve/create user guide documentation 3. Grow Community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? A member of the SDAP podling stepped up to the release manager role which is great. It shows the the podling is maturing. Unfortunately, the release candidate which was produced was not in compliance with the ASF release policy, thankfully Justin highlighted this and we are in the process of rolling the RC back. Lewis (SDAP champion) and the release manager are working to resolve this and get the first incubating release candidate finished. How has the community developed since the last report? Two VOTE's have been made over on private@sdap regarding extending PPMC and Committership to two community contributors. This is very positive. How has the project developed since the last report? SDAP is on the verge of it's first release. With some persistence the podling will have a release candidate for community VOTE soon. 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 [X] Other: One the release management process is documented we will be pushing for graduation. Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? Elizabeth Lam was elected on 2019-02-06 Maya DeBellis was elected on 2019-02-06 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes mentors have been responsive providing answers. Signed-off-by: [X](sdap) Jörn Kottmann Comments: [X](sdap) Suneel Marthi Comments: [X](sdap) Lewis John McGibbney Comments: IPMC/Shepherd notes: Dave Fisher: Most of the PPMC listed in Whimsy is not subscribed to private@. The number of developers on the dev list is small. A little too soon to be thinking about graduation if you ask me. Justin Mclean: The IPMC usually likes to see 2 or 3 releases happen before the project consider graduation. -------------------- ShardingSphere Sharding-Sphere is an ecosystem of transparent distributed database middleware, focusing on data sharding, distributed transaction and database orchestration. ShardingSphere has been incubating since 2018-11-10. Three most important issues to address in the move towards graduation: 1. Prepare for the first ASF release. 2. Fix bugs and develop new features. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Remove unapproved legacy release before repo transfer. Add release description of legacy releases. The details of email is [1]. [1] https://lists.apache.org/thread.html/879089eb1dba43f6f159f8c3fde96c2a56d03ed c9804f70dd7b94b6b@%3Cdev.shardingsphere.apache.org%3E How has the community developed since the last report? Good. There are more and more contributors actually participating in project development. How has the project developed since the last report? The github repository has been transferred to Apache. The official website has been deployed to asf-site and add Apache brand. 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: Not finished for the 1st apache release yet. When were the last committers or PPMC members elected? 28 Jan 2019 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [x](shardingsphere) Craig L Russell Comments: [ ](shardingsphere) Benjamin Hindman Comments: [X](shardingsphere) Willem Ning Jiang Comments: [ ](shardingsphere) Von Gosling Comments: IPMC/Shepherd notes: Justin Mclean: Thanks for resolving the unapproved release issue quickly. -------------------- 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 issues to address in the move towards graduation: 1. Grow the PPMC from the existing community. 2. Make another Release 3. Blog about Tamaya Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * We'd like to graduate soon. How has the community developed since the last report? * elected 2 new committers and onboarded them * discussions/we benefited from the Gitbox migration as it makes contribution much easier How has the project developed since the last report? * frequent bugreports and discussions via Jira/mailing list * new external contributions (code improvements, Jira issues, OSGi bugfixes) * homepage overhaul 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: 2017-05-28 0.3-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 or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. * As the project needs a wider audience, maybe mentors with interest in Tamaya would be welcome. Signed-off-by: [ ](tamaya) John D. Ament Comments: [ ](tamaya) David Blevins Comments: IPMC/Shepherd notes: Dave Fisher - sent an email regarding following release distribution policy. https://lists.apache.org/thread.html/91835c4e5b5e7d0cbe8be640e0878d8a3ac95dc f9d2e1d91d13b28fb@%3Cdev.tamaya.apache.org%3E -------------------- 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 issues to address in the move towards graduation: 1.More discussion and engagement on the mailing list as opposed to "gitter" Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * None How has the community developed since the last report? * The community released the 0.3.0-incubating release and after that overall work slowed down. How has the project developed since the last report? * Regular cadence of community activity, with slow down due to 'after-release' and holidays. 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: 2018-11-13 When were the last committers or PPMC members elected? * Ryan Blue was added to the PMC on 2017-04-03 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [x](toree) Luciano Resende Comments: [ ](toree) Julien Le Dem Comments: [x](toree) Ryan Blue Comments: IPMC/Shepherd notes: -------------------- Unomi Unomi is a reference implementation of the OASIS Context Server specification currently being worked on by the OASIS Context Server Technical Committee. It provides a high-performance user profile and event tracking server. Unomi has been incubating since 2015-10-05. Three most important issues to address in the move towards graduation: 1. Conclude IPMC graduation vote 2. Complete Podling Name Search 3. Submit graduation to Apache Board once the IPMC vote and PNS are completed. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? We are seeing more activity on the relatively new user mailing list and continuing to support existing community members finalize some large projects. How has the project developed since the last report? We have now started the graduation process and hope to complete it in the next month. 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-09-10 When were the last committers or PPMC members elected? 2018-09-19 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Our mentor is very helpful and responsive and is doing his best to assist the project when asked. He is alone but the project has now matured and is less dependent on mentors as it is in the graduation process. Signed-off-by: [X](unomi) Jean-Baptiste Onofre Comments: I'm really frustrated to see how long is the graduation process. Some reasons are obviously true, some we wasted time for "mistake" and inaccurate details. IPMC/Shepherd notes: }}} ----------------------------------------- Attachment AI: Report from the Apache Joshua Project [Tommaso Teofili] ----------------------------------------- Attachment AJ: 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. ## Activity: - jUDDI - last release was 04 DEC 2018. Resolved several requisite bugs for updating SCOUT. - 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. - There are enough active PMC members to approve releases and respond to potential security issues. There were no issues raised since the last report. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Alex O'Ree on Sun Mar 17 2013 ## Committer base changes: - Currently 7 committers. - No new changes to the committer base since last report. ## Releases: - 3.3.6 was released on Tue Dec 04 2018 - SCOUT-1.2.8 was released on Mon Dec 10 2018 ## /dist/ errors: 16 - Looks like the checker application does not correctly handle hashes of signature files. The hashes actually match just fine. Additional hash files will be removed shortly. ## Mailing list activity: - dev@juddi.apache.org: - 68 subscribers (down -1 in the last 3 months): - 106 emails sent to list (28 in previous quarter) - user@juddi.apache.org: - 108 subscribers (down -2 in the last 3 months): - 4 emails sent to list (1 in previous quarter) ## JIRA activity: - 8 JIRA tickets created in the last 3 months - 8 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AK: Report from the Apache Juneau Project [James Bognar] ## Description: - Apache Juneau is a single cohesive Java ecosystem for marshalling POJOs and defining POJO-base REST server and client interfaces. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - During this quarter, the Juneau project released a major new version with significant new functionality in the Microservice APIs and integration with Spring Boot. ## Health report: - 3 new PMC members added during the last quarter. - Website traffic increased significantly, especially after the announcement of 8.0.0. ## PMC changes: - Currently 12 PMC members. - New PMC members: - Ayeshmantha Perera was added to the PMC on Wed Jan 02 2019 - Marcelo Vieira was added to the PMC on Thu Dec 20 2018 - Shalitha Suranga was added to the PMC on Thu Nov 29 2018 ## Committer base changes: - Currently 12 committers. - New commmitters: - Ayeshmantha Perera was added as a committer on Wed Jan 02 2019 - Marcelo Vieira was added as a committer on Fri Dec 21 2018 - Shalitha Suranga was added as a committer on Fri Nov 30 2018 ## Releases: - 7.2.2 on Nov 13, 2018 - 8.0.0 on Jan 01, 2019 ## Mailing list activity: - dev@juneau.apache.org: - 29 subscribers (up 4 in the last 3 months): - 427 emails sent to list (203 in previous quarter) ## JIRA activity: - 6 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AL: Report from the Apache Kafka Project [Jun Rao] Apache Kafka is a distributed streaming platform for efficiently storing and processing a large number of records in real time. Development =========== We are preparing the next major release 2.2.0, which plans to include new features such as separate control and data planes, re-authentication in SASL, better fencing with broker epoch, reducing consumer group rebalance, more functionalities in KStreams, etc. We are also preparing a bug fix release 2.1.1, which fixes more than 30 issues. Community =========== Lots of activities in the mailing list. We have 2809 subscribers in the user mailing list, up 37 in the last 3 months. We have 657 emails in the user mailing list in the last 3 months, a bit less than the 811 in the previous cycle (likely due to year end holidays). We have 1310 subscribers in the dev mailing list, up 38 in the last 3 months. We have 2056 emails in the dev mailing list in the last 3 months, a bit less than the 2689 in the previous cycle. We elected two new committers, Vahid Hashemian on Jan 15, 2019 and Bill Bejeck on Feb. 8, 2019. We didn't add any new PMC members. We last elected one new PMC member Dong Lin on Aug. 4, 2018. An EU sponsored Bug Bounty program for Apache Kafka with a focus on security is in progress. Releases =========== 2.1.0 was released on Nov. 21, 2018. 2.0.1 was released on Nov. 9, 2018. ----------------------------------------- Attachment AM: Report from the Apache Kibble Project [Rich Bowen] Apache Kibble is a suite of tools for collecting, aggregating and visualizing activity in software projects. http://kibble.apache.org/ ## Issues: There are no issues requiring board attention at this time. ## Activity and health In February, we had community representation at CHAOSSCon, the annual conference of the CHAOSS workgroups, who do work around community metrics in FLOSS. This was a very positive interaction for everyone concerned, and many new ideas came out of that event. Daniel Gruno presented a lightning talk about what we’re doing. Kibble also was represented at the Apache booth at FOSDEM, and we ran demos for many interested attendees. Discussions at the events have led to a shift away from simply providing metrics reporting, and more towards asking the end-user what kinds of questions they wish to answer, and adapting to those questions. Discussion also began around integration with Slack and Bitbucket for metrics collection purposes. Sharan has provided a more detailed write-up of these events on our dev mailing list, at https://s.apache.org/OEB1 Despite all of the interest and positive interactions, we continue to struggle to find actual participants in the code-part of the project itself. We hope that following up on some of our contacts from FOSDEM will turn the tide on this. There remains adequate (>= 3 PMC members) oversight on the project, and on the more philosophical/design-wise level, we have discussions going and being started. We did have a query from a University student interested in joining the effort, but we have not heard back from them in recent weeks. A suggestion that arose at FOSDEM for future conferences was lowering the bar for contributions by allowing instant subscriptions to mailing lists at the Apache booth. While we have plenty of interest in the project from users, we seem to suffer from "conference amnesia" where in people forget their interactions due to the sheer volume of inputs. ## PMC/Committer changes: - Currently 12 PMC members and 12 committers - Last PMC addition was Rafael Weingärtner on Fri Dec 08 2017 - Last committer addition was Rafael Weingärtner at Sat Dec 09 2017 ## Releases: We have not yet made a release ## Mailing list activity: This quarter was, for us, an uptick in mailing list traffic, largely around our activities at FOSDEM. ----------------------------------------- Attachment AN: Report from the Apache Knox Project [Larry McCay] ## Description: - The Apache Knox Gateway is an HTTP/REST API Gateway for interacting with Apache Hadoop clusters. The Knox Gateway provides a single access point for all REST/HTTP interactions with Apache Hadoop clusters. ## Issues: - there are no issues requiring board attention at this time ## Activity: - In Dec Apache Knox 1.2.0 was released. It consisted of ~160 resolved JIRAs. - This release concentrated on many dependency upgrades, performance improvements, build time improvements and scans - We have recently migrated to gitbox and agreed to start supporting Pull Requests from github - We have begun discussing the planning for the 1.3.0 release with a focus so far on containerization and cloud. ## Health report: - A more proactive approach on dependency upgrade has increased the level of commits and therefore mailing list activity. - New contributors are engaged, providing patches and filing JIRAs. ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kevin Risden on Mon Apr 02 2018 ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Kevin Risden at Tue Apr 03 2018 ## Releases: - 1.2.0 was released on Mon Dec 17 2018 ## Mailing list activity: - dev@knox.apache.org: - 94 subscribers (down -1 in the last 3 months): - 2278 emails sent to list (1829 in previous quarter) - user@knox.apache.org: - 133 subscribers (up 1 in the last 3 months): - 49 emails sent to list (167 in previous quarter) ## JIRA activity: - 174 JIRA tickets created in the last 3 months - 158 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AO: Report from the Apache Kylin Project [Luke Han] ----------------------------------------- Attachment AP: 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 at this time. ## Activity: - Code base migrated to gitbox by Infra. - Code changes done for persisting and recovering lens state in DB and enable HA - Conversation started to move Lens code reviews to pull request. ## PMC changes: - Currently 18 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Puneet Gupta on Tue Sep 20 2016 ## Committer base changes: - Currently 23 committers. - No new committers added in the last 3 months - Last committer addition was Rajitha R at Fri Feb 09 2018 ## Releases: - Last release was 2.7 on Tue Feb 06 2018 ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AQ: 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. ## Activity: Similar to the last report, activity has dropped (mostly on the committer / reviewer side), but we have still received decent amount of contributions from various users. We are trying to recruit more committers / reviewers, but it's not easy due to the nature of the project (driver / plugin model where most people only care about a very small part of a project - e.g. either a single driver or a particular change in the driver they are interested in). ## PMC changes: Quentin Pradet who has joined us as a last PMC member has decided to go emeritus. We have explained to him that it's totally fine to become inactive and there is no need for him to go emeritus because it doesn't affect our project and things such as voting quorum in any negative way. In fact, that's what a lot of people do over a life time of a project - life and priorities change, etc., people move on. We also explained to him that as an inactive PMC members he has no obligations in any form to the project, but he said he would still prefer to go emeritus because it will allow him to more easily move on to different projects. We would also like to thank him for his excellent work and contributions to the project. - Currently 14 PMC members. - Quentin Pradet was added to the PMC on Mon May 14 2018 ## Committer base changes: - Currently 21 committers. - Rick van de Loo was added as a committer on Tue Jun 26 2018 ## Releases: - 2.4.0 was released on Thu Nov 08 2018 - 2.3.0 was released on March 03, 2018 - 2.2.1 was released on September 21, 2017 ----------------------------------------- Attachment AR: Report from the Apache Logging Services Project [Matt Sicker] ## Description: Apache Logging Services creates and maintains open source software related to application logging. ## Issues: There are no issues requiring board attention at this time. ## Activity: - Log4j: we completed our 2.11.2 release and have continuted work, albeit slowly, toward modularizing Log4j Core (and other plugins) along with an updated 3.0 API to better support Java 9 modules and a stable plugin API. - Log4j Audit: Version 1.0.1 was released for audit logging in JVM applications. ## Health report: Logging Services remains an active project. The community is healthy, friendly, and helpful. ## PMC changes: - Currently 14 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Carter Kozak on July 30, 2018 ## Committer base changes: - Currently 34 committers. - Raman Gupta was added as a committer on Mon Dec 17 2018 ## Releases: - LOG4J-2.10.0 was released on Wed Nov 22 2017 - CHAINSAW-2.0 was released on Thu Jan 25 2018 ## /dist/ errors: 6 Expired artifacts were resigned. And SHA-256 and SHA-512 checksums were added to all the artifacts. ## GitHub PRs and issues: 17 PRs created, 13 of which have been closed 17 PRs closed 30 Open PRs total ## Mailing list activity: Mailing list activity has not changed all that much in the past quarter. Most of the lists are fairly quiet. - dev@logging.apache.org: - 325 subscribers (down -7 in the last 3 months): - 197 emails sent to list (177 in previous quarter) - general@logging.apache.org: - 101 subscribers (down -1 in the last 3 months): - 3 emails sent to list (1 in previous quarter) - log4cxx-user@logging.apache.org: - 209 subscribers (down -1 in the last 3 months): - 5 emails sent to list (1 in previous quarter) - log4j-user@logging.apache.org: - 595 subscribers (up 0 in the last 3 months): - 48 emails sent to list (105 in previous quarter) - log4net-user@logging.apache.org: - 289 subscribers (down -2 in the last 3 months): - 0 emails sent to list (1 in previous quarter) - log4php-user@logging.apache.org: - 79 subscribers (up 0 in the last 3 months): - 0 emails sent to list (2 in previous quarter) - notifications@logging.apache.org: - 11 subscribers (down -2 in the last 3 months): - 952 emails sent to list (1335 in previous quarter) ----------------------------------------- Attachment AS: Report from the Apache Lucene.Net Project [Shad Storhaug] Apache Lucene.Net is a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. == Summary == We had stalled in the second half of 2018, with several board members attempting to reach out to figure out status, and several board reports missing, there were several calls and questions regarding moving to the attic. It seems in early January an email to the dev mailing list generated activity, after the private pmc mailing list seemed to have gone radio silent. There has been vocal support on the dev@ mailing list and a flurry of activity. * Several members have stepped up to work on cleaning up JIRA - 1 JIRA ticket fixed - 1 PR opened to improve merge stability * We have a new website design/repo in the works - https://lucenenetsite.azurewebsites.net/ - https://github.com/apache/lucenenet/pull/206 * We're working on bringing our TeamCity CI Servers back online and reporting * We've a community member at MSFT voice their support for the general stability of 4.8.0-beta0005 in their projects, and is investingating their ability to contribute We need to run a roll call at the PMC to see who is still around and possibly add new members and new committers. == Releases == * Last Release 3.0.3 - Oct 2012 * Working toward 4.8.0 - Currently beta0005, which has been out for some time == Board Questions == "Missing Reports" (I'm not sure anyone explicitly asked this). As mentioned above, my time has been extremely limited, and we are looking to rotate our VP, but as of yet have had no takers. Stefan Bodewig suggests we might need to look towards the attic - which I believe would be unfortunate, but may be the reality. == People == * Last PMC Member Added, Paul Irwin, October 2013 * Last committer added Sept 2016, Shad Storhaug (nightowl888) * PMC Chair rotated 20 June 2018 to Shad Storhaug (nightowl888) == Statistics == As of 2019.02.01 Metric are as follows: Release 3.0.3 * Lucene.Net 3.0.3: 1,757,023 (Jan 2018 - 880,370) * Lucene.Net.Contrib 3.0.3: 370229 (Jan 2018 - 202,988) * Lucene.Net Contrib Spatial: 26483 (Jan 2018 - 17,182) * Lucene.Net Contrib Spatial.NTS: 5697 (Jan 2018 - 2,6909) Beta 4.8.0-beta00005 (Published 10/24/2017) * Lucene.Net: 72395 * Lucene.Net.Analysis.Common: 64981 * Lucene.Net.Analysis.Kuromoji: 2240 * Lucene.Net.Analysis.Phonetic: 561 * Lucene.Net.Analysis.SmartCn: 238 * Lucene.Net.Analysis.Stempel: 469 * Lucene.Net.Benchmark: 181 * Lucene.Net.Classification: 361 * Lucene.Net.Codecs: 1205 * Lucene.Net.Expressions: 2770 * Lucene.Net.Facet: 3078 * Lucene.Net.Grouping: 3644 * Lucene.Net.Highlighter: 2156 * Lucene.Net.ICU: 332 * Lucene.Net.Join: 3286 * Lucene.Net.Memory: 3213 * Lucene.Net.Misc: 2580 * Lucene.Net.Queries: 56362 * Lucene.Net.QueryParser: 52534 * Lucene.Net.Replicator: 183 * Lucene.Net.Sandbox: 58878 * Lucene.Net.Spatial: 1080 * Lucene.Net.Suggest: 2067 ----------------------------------------- Attachment AT: 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.12.0 release on December 20, 2018. The next major release is scheduled for April 30, 2019. Committers and PMC membership ============================= We nominated and approved Markus Schuch as a PMC member on 12/29/2017. We did not sign up any new committers this quarter. We continue to be on the lookout for new PMC members and committers. There are several candidates at this time but we have not yet held a vote for committership. Several of our emeritus committers have become active again after a lull of a couple of years. Mailing list activity ===================== Mailing list activity has been very active this quarter. Much of the communication has been related to support and installation debugging, but we're also seeing calls for the development of new connectors, and connectors to replace existing ones where the APIs have become deprecated. Development of a new OpenText connector is underway. Integration with SolrJ had a lengthy discussion in December, but I don't believe that ever was fully resolved, and will need further impetus to be completed. Issues reported have been centered mainly on bugs this quarter. I am unaware of any mailing list question that has gone unanswered. Outstanding issues ================== No outstanding infrastructure issues are known at this time. ----------------------------------------- Attachment AU: Report from the Apache Marmotta Project [Jakob Frank] ## Description: Apache Marmotta, an Open Platform for Linked Data. Apache Marmotta was founded in December 2012, and has graduated from the Incubator in November 2013. ## Issues: There are no major issues requiring board attention at this time. ## Activity: Another quiet quarter to report without significant development activities. The codebase was migrated to gitbox based on a consensus vote in the community. ## Health report: The project was considered feature-complete since 3.3.0 and has recently published version 3.4.0. Currently there are no active development activities. The PMC has an active oversight on the mailing lists, the vote on migrating the codebase to gitbox had timely responses. ## PMC changes: - Currently 11 PMC members. - Last PMC addition was Mark A. Matienzo on Thu Aug 18 2016 ## Committer base changes: - Currently 13 committers. - Xavier Sumba was added as a committer on Mon Mar 27 2017 ## Releases: - Last release was 3.4.0 on Tue Jun 12 2018 ## Mailing list activity: - users@marmotta.apache.org: - 118 subscribers (up 2 since last report): - 2 emails sent to list (1 in previous report) - dev@marmotta.apache.org: - 95 subscribers (down 1 since last report): - 18 emails sent to list (14 in previous report) ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AV: Report from the Apache Mesos Project [Benjamin Hindman] ----------------------------------------- Attachment AW: Report from the Apache MetaModel Project [Kasper Sørensen] ## Description: Providing a common interface for discovery, exploration of metadata and querying of different types of data sources. ## Issues: - There are no issues requiring board attention at this time ## Activity: - Version 5.2.0 was released in early January. ## Health report: - The project is continuing the "slow but steady" modus. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Dennis Du Krøger on Mon Sep 05 2016 ## Committer base changes: - Currently 13 committers. - No new committers added in the last 3 months - Last committer addition was Jörg Unbehauen at Thu May 03 2018 ## Releases: - 5.2.0 was released on Thu Jan 03 2019 ## JIRA activity: - 4 JIRA tickets created in the last 3 months - 3 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AX: Report from the Apache Oozie Project [Gézapeti] ## Description: - Oozie is a workflow scheduler system to manage Apache Hadoop jobs. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Release 5.1.0 was released after a big delay due to CVE-2018-11799 which was reported after the release branch was cut - Migration to gitbox was done without any issues (Thanks Infra for that!) - Active work is being done to make future releases easier (improvements in tests, build and docs) ## PMC changes: - Currently 20 PMC members. - No new PMC members added in the last 3 months - 1 member decided to go Emeritus - Last PMC addition was Andras Piros on Wed Jun 20 2018 ## Committer base changes: - Currently 25 committers. - Kinga Marton was added as a committer on Fri Nov 09 2018 - Andras Salamon was invited, his account is under construction ## Releases: - 5.1.0 was released on Tue Dec 18 2018 ## JIRA activity: - 49 JIRA tickets created in the last 3 months - 37 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AY: 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: - there are no issues requiring board attention at this time ## Activity: - We are refactoring and testing OCW by using xarray and pandas. ## Health report: - The government shutdown affected some of PMC members' activity. ## 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): - 38 emails sent to list (11 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AZ: Report from the Apache OpenOffice Project [Peter Kovacs] ## DESCRIPTION Apache OpenOffice is an open-source office-document productivity suite. There are six productivity applications based around the OpenDocument Format (ODF) that are Writer, Calc, Impress, Draw, Math, Base. With limited support for other file formats, OpenOffice ships for Windows, MacOS, Linux 64-bit, Linux 32-bit and in 41 languages. ## SUMMARY This report has been sent in with a month delay due to full time schedules in January. The Project did a release in November, containing bug fixes and a security fix. The development regained activity concerning the modernization of the code and build environment itself. One result of this development has been that the process for releasing 4.2.0 has built momentum again. ## ISSUES FOR BOARD AWARENESS Issue: CVE-2018-16858 It is a moderate security vulnerability affecting another program. We were notified that it could be impacting OpenOffice in a significantly less dangerous form. We are still investigating. If OpenOffice is actually affected, a fix will be included in the next release. ## RELEASES We are working in parallel on 2 release lines: 1) 4.2.0 is the next minor release, planned to be released into a beta phase. We have missed our goal on going into the beta in 2018. We managed only to solve the biggest blockers. 2) 4.1.x is still in maintenance. We are discussing a parallel 4.1.7 release. The motivation in maintaining the 4.1.x line is not very high. We will shut it down as soon as we have a stable release of 4.2.x, ## Latest Release History 2018-11-18 4.1.6 2017-12-30 4.1.5 2017-10-19 4.1.4 ## PMC There are 28 PMC members as of 2018-Apr-11. Last PMC member addition was on 2017-Dec-20 Keith N. McKenna (knmc) Last PMC member withdrawal was on 2017-Feb-04 Dennis E. Hamilton (orcmid) ## COMMITTERS There are 141 committers as of 2018-Apr-11. Last committer addition was on 2017-Jan-28 Kay Schenk (kschenk) Last committer withdrawal was on 2017-Feb-04 Dennis E. Hamilton (orcmid) ## ORGANIZATIONAL DEVELOPMENT No Changes to report. We have newcomers working on parts of OpenOffice. We hope they will commit something soon. ## WEBSITES & INFRASTRUCTURE We have processed the migration towards new VMs. The Wikis and Forums are now in maintenance by the developer team. We thank infra for their patience and support. We have initiated a new VM payed from the Project Funds in 2018 Q3, for a reviving the OpenGrok Service. We are still in the process of setting the system up. We still use the Apache CMS for our web presence. It seems it is currently unmaintained and unsupported. The recommendation is to migrate to a different setup. Resolution to this issue is unacceptable in a mid term time frame. Only little development has been done in this branch. However, without help from outside the Project it's expected that this problem won't get solved. ## MARKETING The German community is producing new flyers for the Booth team in German and English. We are looking for translators into other languages. We did not get a booth on FOSDEM and at first our application for a documenters room was rejected. On short notice we were notified that the documenters room has not been rejected. Some of our developer community will still meet at FOSDEM, but with smaller engagement then in the last years due to the short notice. The German booth team will attend more conferences in Germany. ----------------------------------------- Attachment BA: Report from the Apache Perl Project [Philippe Chiasson] ----------------------------------------- Attachment BB: Report from the Apache Phoenix Project [Josh Elser] ## Description: - Apache Phoenix enables SQL-based OLTP and operational analytics for Apache Hadoop ## Issues: - There are no issues requiring board attention at this time ## Activity: - 4.14.1 was officially released. This release was in the final steps of release at the time of that last board report (Nov 2018). - We've added a new PMC member and new committers! Karan was added as a PMC member. Four new committers joined our ranks: Akshita, Chinmay, Jaanai, and Gerald. - Regular development continues on the 4.x release line. The 5.x would benefit from a new release in the near future. ## Health report: - Activity remains constant on average. We had an expected tail-off during the Christmas and (calendar) New Year with our predominantly US-based membership. ## PMC changes: - Currently 28 PMC members. - New PMC members: - Karan Mehta (2018/12/23) ## Committer base changes: - Currently 40 committers. - New committers: - Akshita Malhotra (2019/01/21) - Chinmay Kulkarni (2018/12/10) - Jaanai Zhang (2019/01/02) - Gerald Sangudi (2018/12/16) ## Releases: - 4.14.1 was released on 2018/11/14 - 5.0.0 was released on 2018/07/14 ## Mailing list activity: - Activity is largely in-line with history. No significant changes to trends to be identified. ----------------------------------------- Attachment BC: 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 ## Activity: - We released Apache POI 4.0.1 to fix some smaller issues that were found in the major 4.0.0 release. Overall the 4.x releases seem to be of good quality as many changes were made, but we only received few regression bug-reports. Some more work for Java 11 was done, Early testing of JDK 12 and 13 builds was performed. One new Committer/PMC member was voted in and started to apply some patches. ### XMLBeans - Work started on a release XMLBeans 3.0.3, a few issues were discussed in the area of multi threading/concurrency overhead, class-loading and XML parsing. Work is ongoing to refresh the buildsystem to remove some unnecessary complexity and make it easier for developers to build and use modern IDEs for development. Also some work and discussion is ongoing to improve support for Java 9+ ## Health report: - There was some discussion of bug reports/features via bugzilla and a number of requests which indicate that the popularity of Apache POI is still very good. Questions via email or on Stackoverflow usually get answers quickly. Bug influx was moderate this quarter, bug-numbers went down, most likely due to developers could put in some time during the holidays. Bug influx for XMLBeans is very low because it is a stable project in maintenance-mode and was re-activated only a short while ago. ## PMC changes: - Currently 31 PMC members. - Vladislav Galas was added to the PMC on Sun Dec 30 2018 ## Committer base changes: - Currently 38 committers. - Vladislav Galas was added as a committer on Wed Dec 26 2018 ## Releases: - 4.0.1 was released on Fri Nov 30 2018 ## Mailing list activity: - Mostly constant subscriber-base - dev@poi.apache.org: - 223 subscribers (down -1 in the last 3 months): - 598 emails sent to list (643 in previous quarter) - general@poi.apache.org: - 124 subscribers (up 0 in the last 3 months): - 4 emails sent to list (3 in previous quarter) - user@poi.apache.org: - 583 subscribers (up 0 in the last 3 months): - 112 emails sent to list (143 in previous quarter) ## Bugzilla Statistics: ### Apache POI - 49 Bugzilla tickets created in the last 3 months - 60 Bugzilla tickets resolved in the last 3 months - 526 bugs are open overall (-9) - Having 141 enhancements (+2) - Thus having 385 actual bugs (-11) - 99 of these are waiting for feedback (+5) - Thus having 286 actual workable bugs (-16) - 4 of the workable bugs have patches available (-1) - Distribution of workable bugs across components: {HSSF=79, XSSF=73, SS Common=38, HWPF=37, XWPF=19, SXSSF=11, POI Overall=6, XSLF=6, OPC=4, POIFS=4, HPSF=3, HSLF=2, HPBF=1, HSMF=1, SL Common=1, XDDF=1} ### Apache XMLBeans - 175 open issues (-1) - Bug 128 (-2) - Improvement 23 (+1) - New Feature 19 (+-0) - Wish 5 (+-0) ----------------------------------------- Attachment BD: Report from the Apache Qpid Project [Robert 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 JMS 0.38.0 was released on 16th November 2018. - Qpid Proton-J 0.31.0 was released on 27th November 2018. - Qpid JMS 0.39.0 was released on 3rd December 2018. - Qpid JMS 0.40.0 was released on 20th December 2018. - Qpid Broker-J 7.1.0 was released on 4th January 2019. - Qpid Dispatch 1.5.0 was released on 14th January 2019. - Qpid Proton 0.27.0 was released on 9th February 2019. # 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. - Roddie Kieley was added as a committer on 26th Nov 2018. - There were no new PMC additions in this quarter. The most recent new PMC member is Ganesh Murthy, added on 30th Jan 2017. # Development: - The AMQP 1.0 JMS client had its 0.38.0 - 0.40.0 releases with various bug fixes and performance improvements, and work continues on more. - Qpid Dispatch had its 1.5.0 release, and work is under way toward a 1.6.0 with various improvements and bug fixes. - Proton-C and its language bindings had their 0.27.0 and release, incorporating various bug fixes and improvements. More have been made since and work continues toward 0.28.0. - Proton-J had its 0.31.0 release with various fixes and improvements. It continues to get more as appropriate to support various dependent client/broker/etc components using it. - Qpid Broker-J 7.1.0 was released, adding various improvements to the 7.0.x base and refining the test suite following the AMQP 0-x JMS client being made independent. Work continues on more bug fixes and improvements, with backports to the 7.0.x line as appropriate. # Issues: There are no Board-level issues at this time. ----------------------------------------- Attachment BE: Report from the Apache REEF Project [Byung-Gon Chun] ## 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: - .Net elastic group communication - A new PMC chair (Sergiy Matusevych) was elected in Feb. 2019. ## Health report: - The engagement from the community has been declining perhaps because the codebase has been stable. - It’s been long time since we made the last release. We plan to make a release after a new C# API implementation is merged. ## PMC changes: - Currently 22 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Doug Service on Fri Sep 29 2017 ## Committer base changes: - Currently 35 committers. - No new committers added in the last 3 months - Last committer addition was Scott Inglis at Fri Sep 28 2018 ## Releases: - Last release was 0.16 on Thu Aug 10 2017 ## Mailing list activity: - dev@reef.apache.org: - 86 subscribers (up 1 in the last 3 months): - 17 emails sent to list (37 in previous quarter) - user@reef.apache.org: - 20 subscribers (up 2 in the last 3 months): - 0 emails sent to list (0 in previous quarter) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BF: Report from the Apache River Project [Peter Firmstone] ----------------------------------------- Attachment BG: Report from the Apache RocketMQ Project [Xiaorui Wang] ----------------------------------------- Attachment BH: 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. Latest release is 5.2.1 and the ASF blog site at blogs.apache.org runs on Roller 5.1.2 Tomcat and MySQL. ## Issues: - There are no other issues requiring board attention at this time ## Activity: - New release made in January to upgrade Struts 2 due to a vulerability. - Roller web UI modernized and completelyrewritten to use Struts Bootstrap tags. - Hope to release new web UI as Apache Roller 6 this year - Made 6.0.0-SNAPSHOT build available https://s.apache.org/6.0.0-snapshot - Asked for feedback from community, Infra and Sally on new UI - Offered to help create new blog themes for blogs.apache.org ## Health report: Community is made-up of part-time volunteers with limited time to devote to Roller. Currently only one committer is actively working on developing Roller and making release. For the most part other committers only have time to review and test release. ## PMC changes: - Currently 5 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Kohei Nozaki on Sun Dec 06 2015 ## Committer base changes: - Currently 8 committers. - No new committers added in the last 3 months - Last committer addition was Kohei Nozaki at Mon Mar 09 2015 ## Releases: - Last release was 5.2.2 on January 10, 2019 - Release process underway for 5.2.3 ## Mailing list activity: Subscriber counts could be taken to mean there is still some interest in Apache Roller. The low email counts reflec the low level of development and user-support activity. - dev@roller.apache.org: - 150 subscribers (down -3 in the last 3 months): - 23 emails sent to list (4 in previous quarter) - user@roller.apache.org: - 273 subscribers (down -2 in the last 3 months): - 5 emails sent to list (4 in previous quarter) ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BI: Report from the Apache Santuario Project [Colm O hEigeartaigh] ## Description: - Library implementing XML Digital Signature Specification & XML Encryption Specification. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - There were no releases over the last quarter. Some ongoing work is taking place on a new major release for the Java library. We expect to get some releases done over the next quarter. ## Health report: - 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. ## PMC changes: - Currently 7 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Daniel Kulp on Mon Oct 01 2018 ## Committer base changes: - Currently 17 committers. - No new committers added in the last 3 months - Last committer addition was Daniel Kulp at Mon Oct 01 2018 ## Releases: - Last release was Apache Santuario XML-Security C++ 2.0.2 on Fri Nov 02 2018 ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BJ: Report from the Apache Serf Project [Branko Čibej] Report from the Apache Serf Project [Branko Čibej] ## Description: The serf library is a high performance C-based HTTP client library built upon the Apache Portable Runtime (APR) library. Serf is the default client library of Apache Subversion, Apache OpenOffice and mod_pagespeed. ## Issues: Activity on the project seems to have come to a halt since the last report. ## Activity: There has been no move towards getting Serf 1.4.0 released in the last three months. A release candidate for internal testing was produced, but never released. The last Serf release is now 2.5 years old. Since the last report, we asked the AOO developers about their use of Serf. It turns out that they're using version 1.2.x (pre-ASF) and there was some interest but no work done towards updating it. The only active user of Serf seems to be Apache Subversion. mod_pagespeed is still listed as incubating but doesn't even have a podling web site (either that, or the link on the incubator page is wrong). ## Health report: The last commit in the public repository was made on 2nd November. ## PMC & Committer changes: Currently 13 PMC members and 13 committers. - No new committers added in the last 3 months. - Last new committer added in April 2017 (Evgeny Kotkov). - Last new PMC member added in September 2018 (Branko Čibej). ## Releases: Apache Serf 1.3.9 was released on Thu Sep 01 2016 ## Mailing list and Jira activity: The last message on the dev@ mailing list is 3 months old (it started a new thread and got no responses). ----------------------------------------- Attachment BK: Report from the Apache ServiceComb Project [Willem Ning Jiang] ## Description: - 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 at this time. ## Activity: - ServiceComb PMC just finished last around release and plan for a new around release next quarter. ## Health report: - The mails and development activity are as good as usual. ## PMC changes: - Currently 16 PMC members. - No new PMC members added in the last 3 months ## Committer base changes: - Currently 18 committers. ## Releases: - ServiceComb Pack 0.3.0 was released on Wed Jan 02 2019 ## Mailing list activity: This month there are 1024 emails sent to servicecomb.apache.org by 45 people, divided into 784 topics. Top 5 member: GitBox: 580 email(s) ningjiang@apache.org: 95 email(s) liubao@apache.org: 51 email(s) Willem Jiang (JIRA): 47 email(s) Willem Jiang: 38 email(s) - dev@servicecomb.apache.org: - 124 emails sent by 20 people, divided into 23 topics. - 146 subscribers (up 20 in the last 3 months): - 389 emails sent to list (461 in previous quarter) - issues@servicecomb.apache.org: - 8 subscribers (up 0 in the last 3 months): - 1277 emails sent to list (2340 in previous quarter) ## JIRA activity: - 136 JIRA tickets created in the last 3 months - 148 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BL: Report from the Apache SIS Project [Martin Desruisseaux] ## Description: Apache Spatial Information System (SIS) is a Java library for developing geospatial applications. SIS enables better representation of spatial objects for searching, archiving, or other relevant spatial needs. The base of the SIS library is modelled according international standards published jointly by the Open Geospatial Consortium (OGC) and the International Organization for Standardization (ISO). ## Issues: We have difficulty to make a release. See the health report section below. ## Activity About 190 commits by 2 developers in the last 3 months. Extensive work has been done for supporting some raster data in netCDF files from NASA and JAXA space agencies. It caused relatively rapid development of Apache SIS capability to handle remote sensing data. The library now handles some non-trivial problems for positioning 4-dimensional (including time dimension) images on Earth. However we still lack a Graphical User Interface allowing non-developers to visualize their data. The Google Summer of Code work that attempted to address this problem has not yet been integrated. We presented Apache SIS in Paris Open Source Summit 2018 [1]. We did not attended to Open Geospatial Consortium (OGC) meeting in the last 3 months. Activity on the mailing list dropped from 80 emails in the summer to 25 in autumn to 6 in the last 3 months. ## Health report: The last Apache SIS release (0.8) was one year and half ago. In the last two reports, we wrote that Apache SIS 1.0 release would happen soon. But we have been unable to make it happens. The reason is that the developers who made previous releases are trapped in urgent work since many months. Consequently Apache SIS got active development because those new features were essential to the urgent company work, but this is not the development needed for a SIS release. There is some regressions that we didn't had time to fix. Even if we accept those regressions and release SIS almost as-is, preparing a release still require one or two full days (testing, documenting, synchronizing extensions not included in Apache releases for licensing reasons, discover issues, fix them…). Activity on the mailing list dropped because we stopped reporting OGC activities, proposing plan for ongoing work or discussing integration of Google Summer of Code work. It will hopefully resume after the urgent work is completed. The current difficulty to release Apache SIS shows the project bus factor. A proposal to rotate the chair has been posted on the mailing list [2]. ## PMC changes: * Currently 20 PMC members. * No new PMC members added in the last 3 months. * Last PMC addition was Johann Sorel on September 7, 2017. ## Committer base changes: * Currently 21 committers. * No new committers added in the last 3 months. * Last committer addition was Johann Sorel at Thu Mar 31 2016. ## Releases: * 0.8 was released on November 24, 2017. ## Mailing list activity: dev@sis.apache.org: * 71 subscribers (down -1 in the last 3 months) * 6 emails sent to list (25 in previous quarter) user@sis.apache.org: * 47 subscribers (down -1 in the last 3 months) * 0 emails sent to list (1 in previous quarter) ## JIRA activity: * 3 JIRA tickets created in the last 3 months * 4 JIRA tickets closed/resolved in the last 3 months [1] https://www.opensourcesummit.paris/ [2] https://lists.apache.org/thread.html/c2d0a7b93b7f231794349a701cc233213b598fe049f3f57adadf50ef@%3Cdev.sis.apache.org%3E ----------------------------------------- Attachment BM: 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 stream processing, machine learning, and graph analytics. Project status: - We created a security@spark.apache.org mailing list to discuss security reports in their own location (as was also suggested by Mark T in November). - We released Apache Spark 2.2.3 on January 11th to fix bugs in the 2.2 branch. The community is also currently voting on a 2.3.3 release to bring recent fixes to the Spark 2.3 branch. - Discussions are under way about the next feature release, which will likely be Spark 3.0, on our dev and user mailing lists. Some key questions include whether to remove various deprecated APIs, and which minimum versions of Java, Python, Scala, etc to support. There are also a number of new features targeting this release. We encourage everyone in the community to give feedback on these discussions through our mailing lists or issue tracker. Trademarks: - We are continuing engagement with various organizations. Latest releases: - Jan 11th, 2019: Spark 2.2.3 - Nov 2nd, 2018: Spark 2.4.0 - Sept 24th, 2018: Spark 2.3.2 Committers and PMC: - There was a discussion about lack of available review bandwidth for streaming on the dev list in January. The PMC discussed this and added a new committer, Jose Torres, specializing in streaming. We are continuing to look for other contributors who'd make good committers here and in other areas. - The latest committer was added on January 29th, 2019 (Jose Torres). - The latest PMC member was added on January 12th, 2018 (Xiao Li). ----------------------------------------- Attachment BN: Report from the Apache Stanbol Project [Fabian Christ] ----------------------------------------- Attachment BO: Report from the Apache Subversion Project [Stefan Sperling] Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system 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 community is healthy and active. New features are being designed and developed, and bug reports are being handled. Our user support forums (Email and IRC) receive questions and answers regularly. We added Yasuhito Futatsuki (futatuki@), who is working on Subversion's bindings to Python 3, as a committer in January 2019. * Releases Subversion 1.9.10, 1.10.4, and 1.11.1 were released January 11 2019. Subversion 1.12.0 is expected in April 2019, at which point we will stop supporting 1.11 releases. Subversion 1.9 and 1.10 are our current long-term-support (LTS) releases and will receive support until August 2019 and April 2022, respectively. * Delayed patching of known security issues The project has been discussing its approach to security issues. We decided to move parts of related documentation and scripting, which had been kept private, to our public repository. We have two processes for handling security issues, a "public" process where fixes are committed to our public repository before a release is cut, and a "private" process where patches are maintained in the private area of our repository and are included in the release by our release manager. The community is currently debating the merits of each process, and perhaps switching to a single unified process. On January 18, we published a security advisory for CVE-2018-11803. The issue formerly known as CVE-2018-1293 is not fixed yet. It is no longer considered a security issue because its impact is minimal and the workaround is easy (use 'svn rm' on offending path). A fix is being developed in public and status is being tracked in https://issues.apache.org/jira/browse/SVN-4788 ----------------------------------------- Attachment BP: Report from the Apache Syncope Project [Francesco Chicchiriccò] ## Description: Apache Syncope is an Open Source system for managing digital identities in enterprise environments. ## Issues: There are no issues requiring board attention at this time. ## Activity: We are keeping ourselves busy with maintenance work (including feature addition) onto the 2_0_X and 2_1_X branches, which led to the recent 2.1.3 and 2.0.12 releases. The work towards the new 3.0.0 has just started with preliminary discussions in the dev@ mailing list, with supporting wiki pages. ## Health report: Discussions about new features and improvements keep appearing and being followed up in dev@. Users keep asking for basic and advanced features and customizations in user@ and are eventually getting supported by the community. ## PMC changes: - Currently 11 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Matteo Alessandroni on Fri Dec 22 2017 ## Committer base changes: - Currently 23 committers. - No new committers added in the last 3 months - Last committer addition was Dima Ayash at Mon Jul 09 2018 ## Releases: - 2.0.12 was released on Thu Jan 17 2019 - 2.1.3 was released on Thu Jan 17 2019 ----------------------------------------- Attachment BQ: 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: - There are no issues requiring board attention at this time. ## Activity: - The latest release, 1.2.0, was approved on August 24th, 2018. - No new committers were added this quarter. ## Health report: - Code activity is healthy with 25 commits in the last 3 months. - Community growth is healthy with our last new committer approved in August. - Communication on the dev mailing list is down. 6 emails were sent to the dev list this quarter. ## PMC changes: - Currently 23 PMC members. - No new PMC members were added in the last 3 months. ## Committer base changes: - Currently 26 committers. - No new committers added in the last 3 months. - Guobao Li was added as a committer on August 28, 2018. ## Releases: - Version 1.2.0 was released on August 24, 2018. ----------------------------------------- Attachment BR: Report from the Apache Thrift Project [Jake Farrell] ## Description: - Apache Thrift is a high performance cross platform RPC and serialization solution. ## Issues: - The PMC has lost contact with its chair Jake Farrell. A new chair was elected by the PMC to overcome the issue. - Due to the short notice, we do not have access to Whimsy etc. set up, so we are sending this report via mail. ## Activity: - The community continues to dramatically reduce the issue and pull request backlog. James King in particular deserves special mention in this regard, as he has put in a huge amount of hours recently and is almost singularly responsible for our recent 0.12 release. ## Health report: - The project code is healthy and fairly mature. The build system is in transition and while there is work to do there, the community is actively discussing a 1.0 release. That said, we need more active committers and PMC members. Of the 17 PMC members only 3 are active, of the 33 committers, less than half are active. ## PMC changes: - Currently 17 PMC members. - No new PMC members added in the last 4 months - Last PMC addition was James E. King III on Thu Nov 02 2017 - The PMC elected a new Chair, Jens Geyer, per Sun Feb 10 2019 ## Committer base changes: - Currently 33 committers. - No new committers added in the last 4 months - Last committer addition was Allen George at Mon Mar 19 2018 ## Releases: - 0.12.0 was released on Thu Jan 03 2019 ## Mailing list activity: - Mailing list activity is good though not all user inquiries, particularly exotic ones are answered by the community. - dev@thrift.apache.org: Currently: subscribers (down -7 in the last 3 months) () - 257 subscribers (down -7 in the last 3 months): - 1843 emails sent in the past 3 months - 548 in the previous cycle - user@thrift.apache.org: - 680 subscribers (no change in the last 3 months) - 20 emails sent in the past 3 months - 21 in the previous cycle ## JIRA activity: - 134 JIRA tickets created in the last 3 months - 270 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BS: Report from the Apache TomEE Project [David Blevins] This is does not substitute for a board report and we will report next month. There was an ask by the Board for projects to indicate if they would like to use the official Jakarta EE logo once certified. That was discussed and all responses were a yes[1]. Short status of the project is that we've had the best quarter in the project history, shattering previous records on mailing lists communication, commits and new contributors by wide margins. There were over 40 new faces committing their first commit between December and January and we still see a new face weekly. This status is far too amazing to slip in at the last minute, which is why we'll be reporting next month, but we are quite proud of the massive turnaround. [1] https://lists.apache.org/thread.html/93a8d4672c9bcf24c66d863ab7995fa0f0da22f2a7051c74e5da68eb@%3Cdev.tomee.apache.org%3E ----------------------------------------- Attachment BT: Report from the Apache Traffic Control Project [David Neuman] ## Description: - Apache Traffic Control can be used to build, monitor, configure, and provision a large-scale content delivery network (CDN). ## Issues: - There are no issues requiring board attention at this time ## Activity: - Continued to try to get our 3.0 release out. We are up to RC5, hopefully we have all of the issues worked out. - Added a new Commiter, Mike Sandman - Continued to support new users and make our CDN in a box solution better ## Health report: - The Project is healthy but our PMC involvement has seemed to slow down. I think it's time we consider adding new PMC members. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Eric Covener on Tue May 15 2018 ## Committer base changes: - Currently 21 committers. - Mike Sandman was added as a committer on Fri Dec 07 2018 ## Releases: - Last release was apache-trafficcontrol-2.2.0 on Mon Jun 25 2018 - RC5 for 3.0 is available for testing ## Mailing list activity: - users@trafficcontrol.apache.org: - 103 subscribers (down -3 in the last 3 months): - 16 emails sent to list (38 in previous quarter) - dev@trafficcontrol.apache.org: - 94 subscribers (up 1 in the last 3 months): - 200 emails sent to list (184 in previous quarter) ## GitHub activity: - 198 Pull requests submitted in the last quarter - 183 Pull Requests merged/closed in the last quarter - 112 issues created in quarter - 71 issues closed in the last 30 days ----------------------------------------- Attachment BU: Report from the Apache Turbine Project [Georg Kallidis] ## Description: - Apache Turbine is a servlet based framework that allows experienced Java developers to quickly build web applications. Turbine allows you to personalize the web sites and to use user logins to restrict access to parts of your application. - Turbine is a matured and well established framework that is used as the base of many other projects. ## Issues: - No board-level issues at this time. ## Activity: - Quite a couple of component upgrades/releases (Fulcrum) - Resolving some issues with testing in Apache Turbine and Db Torque ORM ## Health report: - The Turbine project has had a well above noise quarter activity with community collaboration in dev mailing list and ongoing code changes across many components. - Need to clean up more builds, site + docu and repo structure. ## PMC changes: - Currently 9 PMC members. - Last PMC addition was Jeffery Painter on Sun Nov 12 2017. ## Committer base changes: - Currently 11 committers. - No new changes to the committer base since last report. - Last committer addition was more than 2 years ago. ## Releases: - Last main project release was Turbine 4.0.1 on Mon Mar 05 2018. - Fulcrum JSON 2.0.0 was released on Fri Feb 01 2019 - Fulcrum TestContainer 1.0.8 was released on Mon Jan 07 2019 - Fulcrum crypto 1.0.8 was released on Tue Feb 05 2019 - Fulcrum factory 1.1.1 was released on Mon Jan 21 2019 - Fulcrum localization 1.0.7 was released on Tue Feb 05 2019 - Fulcrum mimetype 1.0.6 was released on Mon Jan 21 2019 - Fulcrum pool 1.0.5 was released on Wed Jan 23 2019 - Fulcrum xslt 1.1.1 was released on Tue Feb 05 2019 - Fulcrum yaafi 1.0.8 was released on Mon Dec 17 2018 - Fulcrum yaafi-crypto 1.0.7 was released on Wed Nov 28 2018. ----------------------------------------- Attachment BV: 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. ## Activity: - Various Bugfixes around index querying and maintenance. - Improved test stability. - Experimentation with using newer versions(5.x) of Elasticsearch vs. supported older version (1.7). ## Health report: Growth has been flat over the past year or so. Some of historical core contributors have not been active with the project recently. However, there are contributions from a potential new committer. Getting the project to a healthier state will be a focus over the next few months. This includes more discussion on the mailing lists, better use of JIRA, and planning of a new release -- master branch is currently stable and contains many stability fixes over the last release in 2016. ## PMC changes: - Currently 25 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Mike Dunker on Mon Jan 18 2016 ## Committer base changes: - Currently 15 committers. - No new committers added in the last 3 months - Last committer addition was Robert Walsh at Sun Feb 26 2017 ## Releases: - Last release was 2.1.0 on Wed Feb 17 2016 ## /dist/ errors: 1 - This is still outstanding, there is 1 unsigned package. We will either remove it or ensure it gets signed. ## Mailing list activity: - As mentioned in the Health section, growth and activity is flat and the mailing list shows the same. There is less activity in the last 3 months, which may be expected due to the holiday season. - dev@usergrid.apache.org: - 106 subscribers (down -2 in the last 3 months): - 39 emails sent to list (86 in previous quarter) - user@usergrid.apache.org: - 143 subscribers (up 0 in the last 3 months): - 0 emails sent to list (9 in previous quarter) ## JIRA activity: - 5 JIRA tickets created in the last 3 months - 3 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BW: Report from the Apache Velocity Project [Nathan Bubna] ## Description: - Java-based template engine ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Low. No work, just the necessary user support. ## Health report: - Holidays are always a quiet period for us, but the small team is still functioning and responsive. ## PMC changes: - Currently 9 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Michael Osipov on Thu Jul 27 2017 ## Committer base changes: - Currently 14 committers. - No new committers added in the last 3 months - Last committer addition was Michael Osipov at Mon Jan 30 2017 ## Releases: - Last release was velocity-tools-3.0 on Wed Oct 10 2018 ## Mailing list activity: - Things were very quiet through the holidays. Mostly just a bit of user support and bug reports - dev@velocity.apache.org: - 120 subscribers (down -1 in the last 3 months): - 24 emails sent to list (203 in previous quarter) - general@velocity.apache.org: - 72 subscribers (up 0 in the last 3 months): - 2 emails sent to list (2 in previous quarter) - user@velocity.apache.org: - 284 subscribers (up 0 in the last 3 months): - 2 emails sent to list (3 in previous quarter) ## JIRA activity: - 4 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment BX: Report from the Apache Whimsy Project [Sam Ruby] ## Description: Tools that help automate various administrative tasks or information lookup activities ## Issues: None ## Health report: Sebb has been on fire lately, cleaning up a number of mostly or even half completed activities. We continue to have more than adequate oversight, with two to three active committers, and a few occasional committers. ## Development: - A moderators workbench is under development in a branch. - Numerous fixes, in particular to the secretary workbench (including a pull request to the Ruby mail gem), and code cleanup (notably with relation to committees and LDAP). ## PMC and committer base: - Currently 10 committers, all on the PMC. - Last addition: Thu Jun 2017 (John D. Ament) ----------------------------------------- Attachment BY: Report from the Apache Xalan Project [Steven J. Hathaway] ----------------------------------------- Attachment BZ: Report from the Apache Xerces Project [Michael Glavassevich] ----------------------------------------- Attachment CA: 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.11 * Bug Fix for Apache FOP 2.3 to remove Avalon MERGEd to TRUNK (no longer maintained & doesn't compile under Java 9) * Glenn Adams has resigned from XML Graphics PMC but is remaining a Committer 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. Glenn Adams resigned from XML Graphics PMC on 2/10/2019 but remains a Committer. Simon Steiner was added to the PMC on Tue Jan 19 2016 Clay Leeds was approved for XML Graphics PMC Chair position on March 26, 2018. Committers ========== Currently 21 committers. * No new committers added in the last 3 months * Last committer added was Matthias Reischenbacher at Wed May 13 2015 Most Recent Releases ==================== There were no releases in the last quarter. * XMLGraphics Commons 2.3 was released on Mon May 14, 2018 * XMLGraphics FOP 2.3 was released on Mon May 14, 2018 * XMLGraphics Batik 1.11 VOTE for release completed on Mon Feb 11, 2019 and RELEASE is imminent = SUB PROJECTS = ================ XML GRAPHICS COMMONS ==================== Community activity was light, although there were a few bugs resolved. New Release? ------------ There were no releases this quarter. Latest Release -------------- XML Graphics Commons 2.3 was released on Mon May 14, 2018 FOP === A number of patches have been processed into TRUNK and several bugs fixed. New Release? ------------ * There were no releases this quarter. * Bug Fix for FOP 2.3 to remove Avalon committed to TRUNK (no longer maintained & doesn't compile under Java 9) Latest Release -------------- XML Graphics FOP 2.3 was released on Mon May 14, 2018 BATIK ===== Apache Batik 1.11 is ready for imminent RELEASE. A handful of new bugs have been reported by users via JIRA. New Release? ------------ Apache Batik 1.11 VOTE for RELEASE completed on Mon Feb 11, 2019 and RELEASE is imminent. Latest Release -------------- Apache Batik 1.10 was last released on Mon May 14, 2018 ------------------------------------------------------ End of minutes for the February 20, 2019 board meeting.