Index Links: 2018 - All years - Original
                    The Apache Software Foundation

                  Board of Directors Meeting Minutes

                            April 18, 2018


1. Call to order

    The meeting was scheduled for 10:30am Pacific and began at 10:34
    when a sufficient attendance to constitute a quorum was
    recognized by the chairman.

    Other Time Zones: https://timeanddate.com/s/3gbr

    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 - left at 11:22
      Roman Shaposhnik
      Phil Steitz
      Mark Thomas

    Directors Absent:

      Brett Porter

    Executive Officers Present:

      Kevin A. McGrail
      Sam Ruby
      Craig L Russell
      Matt Sicker
      Ulrich Stärk

    Executive Officers Absent:

      Ross Gardler

    Guests:

      Daniel Gruno
      Daniel Ruggeri
      Geoff Macartney
      Greg Stein
      Jim Jagielski
      Pierre Smits
      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 March 21, 2018

       See: board_minutes_2018_03_21.txt

       Approved by General Consent.

    B. The meeting of April 11, 2018

       See: board_minutes_2018_04_11.txt

       Approved by General Consent.

4. Executive Officer Reports

    A. Chairman [Phil]

       This month, we welcome Roman Shaposhnik and Isabel Drost-Fromm as new
       board members (though Isabel has served in the past) and we, once
       again, thank departing members, Jim Jagielski and Chris Mattmann for
       their service.  We had a brief meeting of the new board on April 11,
       where we agreed on officer appointments and had an informal discussion
       of what each of us thought were important topics for the board in the
       coming year. Each board member provided one or more items for
       consideration. We did not make any decisions or discuss any of these
       items in detail. We agreed that substantive discussion and
       decision-making should happen on ASF lists and/or regularly scheduled
       ASF Board meetings.  The full list of items is in the minutes, linked
       in this month's agenda.

       We agreed to ask all current officers to continue in their roles and I
       am happy to report that all have agreed.  To fill the Vice Chair
       vacancy created by Jim's departure, we appointed Shane Curcuru as Vice
       Chair. Thank you, Shane, for agreeing to take on this role.

       This month's reports included some very good ones: Fineract, Hbase and
       Nifi among them.  Each of these provided thoughtful insight into
       project state, problems and plans. Comments on individual reports
       continued to hit the following common themes:

       * Responding to the "long tail" contribution / committer bottleneck by
         making it faster / easier to earn commit
       * Same as above regarding PMC membership
       * Request to provide a more thoughtful project health summary
       * Reminder to follow IP clearance process for substantial
         contributions not developed inside the project
       * Reminder to be careful with synchronous meetings, always summarizing
         on list, etc.
       * Reminder to include date last committer and PMC member were added to
         the project

    B. President [Sam]

       Items requiring Board attention:

       Two resolutions: budget, and sponsor relations.

       - - -

       Overall, we continue to be in a good position financially, running a
       surplus where we had budgeted for a deficit.

       The FY19 budget discussions appear to all have run their course, and
       it is time for a decision and to move on.  Should the budget be
       approved as is, I will request the Fundraising team to develop and
       post a full review by the September board meeting so that the board
       can decide whether to terminate or proceed the SOW at the six month
       mark (which would be the October meeting).

       Also, if the budget is approved, I will be naming Daniel Ruggeri as
       (a?) VP, Fundraising.  As a part of that discussion, we can decide
       what title, if any, Kevin will be retaining/assuming.

       The proposal is to develop a team of individuals doing fundraising,
       and to have each member of that team empowered to "close the deal"
       with sponsors.

       Our project websites are a underutilized resource for bringing
       awareness to visitors of matters such as upcoming ApacheCons, and we
       continue to look to ways to reduce the effort required to add images
       and links across our site.  This hasn't been discussed recently, and
       merits revisiting.  See discussion item 8B.

       Brand Management is operating smoothly.

       Additionally, please see Attachments 1 through 6.


    C. Treasurer [Ulrich]

       Virtual Report:

       Here is a summary of the Foundation’s performance for the first eleven
       months of FY18.

       Operating Cash on Mar 31st, 2018 was $1,955K, which is up $150.4K from
       last month’s ending balance (Feb 18) of $1,804.6K.    Total Cash as of
       Mar 31st, 2018 is $2,847.9K. The Mar 2018 ending Operating cash
       balance of $1,955K represents an Operating cash reserve of 17.7 months
       based on the FY18 conservative Cash forecast average monthly spending
       of $110.3K/month. The ASF reserve continues to be very healthy for an
       organization of ASF’ s size, with a conservative FY18 YE estimate of
       17.5 months of Operating cash reserve.

       Regarding the YTD Cash P&L, we continue to have a very strong and
       favorable showing against our FY18 budget through eleven months of
       FY18, however as I will continue to mention, because we are on a cash
       basis, the timing of Sponsor payments received (including multi-year
       sponsors) and Payables released plays a big part in how well we
       perform financially month to month and year over year.  This month we
       were under the FY 18 budget for Revenue (Timing of estimated sponsor
       payments were over but offset by a large donation that was budgeted to
       be received in Mar 2018 but was received in Feb 18).  The Foundation
       was also over the FY18 budget in Expenses as well for Mar 18 (Infra
       was over in staff and Spare parts as well as timing of paying two
       months of Lease web.  Sponsorship was also budget due to the timing of
       travel vs the budget. YTD all deps are under budget except Infra).  
       The Fundraising team continues to do an excellent job in both areas,
       servicing both new and existing Sponsors.  With total actual Revenue,
       as of Mar 31st, 2018, of $1,574.1K (up $265.5K from the Feb 18 and up
       $560.2K from Mar 2017), we are 154.6% of the way to our Total Revenue
       budget of $1,226.5K for FY18, with a month of FY18 remaining. 
       Regarding Sponsor revenue, we have received in the first 11 months of
       FY18, $1574.1K, (up $263,3K from Feb 18 and up $599.3 from Mar 17)
       which has us at 157.3% for YTD and exceeding the budgeted Sponsor
       revenue goal of $1,084K for FY18.  This is a great accomplishment as
       we still have a month left of FY 18 and we have exceeded our
       Sponsorship goal by $263.3K (and we are estimating another $161K to
       arrive in Apr 18).  As for the remaining revenue categories, we have
       received $167.3K against a total budget of $139.3K or 1.20% of our FY
       18 budget with a month of FY18 left.  I would also like to point out
       that in FY17 to this point we had $135.9K vs the $167.3K we have as of
       Mar 31st which is an increase of $31.4K or basically what we have
       received via the Hopsie platform, which again is fantastic as it is no
       real cost to the foundation but another option for Fundraising.

       YTD expenses, through Mar31st, 2018 are under budget by $103.1K, with
       Infra as the only dept over budget. We will continue to monitor the
       actual vs budget as we move through the remaining month of FY18.  As
       we finish up Apr 2018, I will be in contact with the dept. heads, to
       make sure, as we are on a cash basis, that any FY18 expenses are
       accounted for in FY18 and do not carry over to FY19.

       Regarding Net Income (NI), YTD for FY18 the ASF finished with a
       positive $450.1K NI vs a budgeted negative <$193.6K> NI or $643.7K
       ahead of the FY 18 Budget for Net Income eleven months into the FY,
       which is also 233% ahead of the FY18 budget.  With the current
       conservative forecasted revenue, and expenses for the remainder of FY
       18, we are now estimating, at the Fiscal year end, a positive $413.7K
       NI vs a budgeted NI loss of -$167.8K or about a $581.6K better NI than
       the FY18 budget.  This is attributable to a combination of additional
       revenue and lower than budgeted expenses for FY18 ($511.4K more in
       revenue and $70.4K in lower expenses based on our conservative
       forecast).  I would also like to point out that YTD 18 NI vs YTD 17 NI
       we are $560.2K ahead in Revenue while Expenses were $7.3K higher year
       over year, for a $552.9K increase in NI year over year ($450.1K
       positive NI in FY18 vs <-$102.8K> NI in FY 17, as of Mar 31st, 2018). 
       Again, I want to congratulate the entire Foundation on these very
       positive Operating results now that FY 18 is ending.  It does truly
       take a team effort to achieve these types of results.  Now that we see
       what can be achieved by our efforts, we do need to continue to keep
       these efforts up as we move through the remainder of FY 18, and into
       FY19.  We need to continue to provide Fundraising all the support and
       resources to continue with the traction that has been created with in
       the last year, while keeping an eye on our expenses at the same time. 
       We should also recognize that the Foundation as compared to not only
       its FY18 budget but also to FY 17 actuals, is in “an extremely good
       place” by all measures and we should all be very proud of that fact,
       as we finish out FY 18 and enter FY19.

       Board Summary Financials:

       Current Balances:            
         Boston Private Checking Account   2,250,000.00
         Citizens Money Market               465,463.78
         Citizens Checking                   131,875.51
         Paypal - ASF                            559.24
       Total Checking/Savings              2,847,898.53
                                          
                                           Mar-18       Budget     Variance 
       Income Summary:              
         Inkind Revenue                      0.00         0.00         0.00 
         Public Donations                1,555.16    78,211.81   -76,656.65 
         Sponsorship Program           263,238.09   217,000.00    46,238.09 
         Programs Income                     0.00         0.00         0.00 
         Other Income                      375.89         0.00       375.89 
         Interest Income                   395.52       292.92       102.60 
       Total Income                    265,564.66   295,504.73   -29,940.07 
                                    
       Expense Summary:             
         In Kind Expense                     0.00         0.00         0.00 
         Infrastructure                 77,497.56    62,956.17    14,541.39 
         Sponsorship Program             5,038.19     2,000.00     3,038.19 
         Programs Expense                    0.00         0.00         0.00 
         Publicity                       6,700.00    10,000.00    -3,300.00 
         Brand Management                2,714.72     7,416.67    -4,701.95 
         Conferences                         0.00         0.00         0.00 
         Travel Assistance Committee         0.00         0.00         0.00 
         Tax and Audit                   6,000.00         0.00     6,000.00 
         Treasury Services               3,350.00     3,500.00      -150.00 
         General & Administrative        1,025.51     8,948.00    -7,922.49 
       Total Expense                   102,325.98    94,820.84     7,505.14 
       Net Income                      163,238.68   200,683.89   -37,445.21 

                                         YTD 2018       Budget     Variance
       Income Summary:
         Inkind Revenue                      0.00         0.00         0.00
         Public Donations              128,234.34   108,048.43    20,185.91
         Sponsorship Program         1,406,850.17   894,250.00   512,600.17
         Programs Income                15,100.00    28,025.00   -12,925.00
         Other Income                   16,356.37         0.00    16,356.37
         Interest Income                 7,606.39     3,222.12     4,384.27
       Total Income                  1,574,147.27 1,033,545.55   540,601.72

       Expense Summary:
         In Kind Expense                     0.00         0.00         0.00
         Infrastructure                758,840.34   747,512.87    11,327.47
         Sponsorship Program            28,480.95    32,250.00    -3,769.05
         Programs Expense                    0.00         0.00         0.00
         Publicity                     121,641.61   171,375.00   -49,733.39
         Brand Management               57,494.46    81,583.37   -24,088.91
         Conferences                     5,200.15     8,418.00    -3,217.85
         Travel Assistance Committee     2,191.81    22,500.00   -20,308.19
         Tax and Audit                  10,687.00    10,200.00       487.00
         Treasury Services              36,600.00    37,950.00    -1,350.00
         General & Administrative      102,906.98   115,332.16   -12,425.18
       Total Expense                 1,124,043.30 1,227,121.40  -103,078.10
       Net Income                      450,103.97  -193,575.85   643,679.82


       Asst Treasurer's Report:

       - Things going smoothly with A/R & A/P going well.

       - Guidestar now at the Gold Level

       - Purchased 30 Google Vault licenses for $300 /year.  Likely to be
         needed for ediscovery due to an subpoena for evidence received re:
         Equifax.

       - Have moved 750K additional funds to our CDARS account (Boston Private 
         Checking Account)

    D. Secretary [Craig]
       In March, 62 ICLAs, five CCLAs, 39 member applications, two proxies,
       two emeritus requests, and four grants were received and filed.

    E. Executive Vice President [Ross]

       Infrastructure
       ==============

       Over budget by 0.5%, FY19 budget request reflects this.

       A few outages and a DDOS to address, but nothing too complex.

       Marketing and Publicity
       =======================

       Produced 19th Anniversary blog https://s.apache.org/gK4Q and
       promotional video https://youtu.be/Fqk_rlKiVIs.

       Q3 FY2018 report published https://s.apache.org/UtBD

       Otherwise business as usual.

       Conferences
       ===========

       Apache RoadShow Europe - Berlin, June 11-14 2018 - Scheduled posted:
       http://apachecon.com/euroadshow18/schedule.html

       ApacheCon North America - Montreal, CA, 24-27 Sept - CFP closed, 249
       proposals are being evaluated. Cloudstack Collaboration Conference is
       to be co-located, GeoSpatial community are running a complete track.
       Call for volunteers is open -
       https://docs.google.com/spreadsheets/d/1VWJsUp0HSa2oH6yCbOJJqw5pgdxKt_m0R8yXUcQUA8A/edit#gid=0

       Apache DC RoadShow - DC, October - Date and Venue confirmed, more
       details once website is updated.

       2019 will see the 20th anniversary of ApacheCon. Venue search is
       underway in the SF area.

       Smaller events are being considered on a case by case basis. Please
       join planners@apachecon.com to help.

       TAC
       ===

       Applications are open until May 1st. Everything is under control.

    F. Vice Chairman [needs-to-be-appointed]

       No report was submitted.

    Executive officer reports approved as submitted by General Consent.

5. Additional Officer Reports

    A. VP of W3C Relations [Andy Seaborne / Rich]

       See Attachment 7

    B. Apache Legal Affairs Committee [Chris Mattmann / Bertrand]

       See Attachment 8

    C. Apache Security Team Project [Mark J. Cox / Isabel]

       See Attachment 9

    Additional officer reports approved as submitted by General Consent.

6. Committee Reports

    Summary of Reports

     The following reports required further discussion:

        # CarbonData [rb]
        # Giraph [rs]
        # Isis [rb]
        # James [rs]
        # Metron [mt]
        # MyFaces [rb]

    A. Apache Accumulo Project [Michael Wall / Phil]

       See Attachment A

    B. Apache ActiveMQ Project [Bruce Snyder / Roman]

       See Attachment B

    C. Apache Airavata Project [Suresh Marru / Shane]

       See Attachment C

    D. Apache Apex Project [Thomas Weise / Ted]

       See Attachment D

    E. Apache Archiva Project [Olivier Lamy / Mark]

       See Attachment E

    F. Apache Aries Project [Jeremy Hughes / Brett]

       See Attachment F

    G. Apache Arrow Project [Jacques Nadeau / Mark]

       See Attachment G

    H. Apache AsterixDB Project [Till Westmann / Shane]

       See Attachment H

    I. Apache Attic Project [Jan Iversen / Brett]

       See Attachment I

    J. Apache Avro Project [Thiruvalluvan M. G. / Phil]

       See Attachment J

    L. Apache Bahir Project [Luciano Resende / Rich]

       No report was submitted.

    M. Apache Calcite Project [Michael Mior / Isabel]

       See Attachment M

    N. Apache Camel Project [Christian Mueller / Bertrand]

       No report was submitted.

    O. Apache CarbonData Project [Liang Chen / Roman]

       See Attachment O

    P. Apache Celix Project [Pepijn Noltes / Roman]

       See Attachment P

    Q. Apache Chukwa Project [Eric Yang / Rich]

       See Attachment Q

    R. Apache Crunch Project [Josh Wills / Isabel]

       See Attachment R

    S. Apache CXF Project [Daniel Kulp / Shane]

       See Attachment S

    T. Apache DataFu Project [Matthew Hayes / Bertrand]

       See Attachment T

    U. Apache DB Project [Bryan Pendleton / Mark]

       See Attachment U

    V. Apache Directory Project [Stefan Seelmann / Brett]

       See Attachment V

    W. Apache Fineract Project [Myrle Krantz / Phil]

       See Attachment W

    X. Apache Fluo Project [Keith Turner / Ted]

       See Attachment X

    Y. Apache FreeMarker Project [Dániel Dékány / Bertrand]

       See Attachment Y

    Z. Apache Geronimo Project [Romain Manni-Bucau / Rich]

       See Attachment Z

    AA. Apache Giraph Project [Avery Ching / Mark]

       No report was submitted.

       @Mark: follow up to get a report

    AB. Apache Hadoop Project [Christopher Douglas / Shane]

       See Attachment AB

    AC. Apache Hama Project [Chia-Hung Lin / Isabel]

       See Attachment AC

    AD. Apache HBase Project [Misty Stanley-Jones / Brett]

       See Attachment AD

    AE. Apache Incubator Project [John D. Ament / Ted]

       See Attachment AE

    AF. Apache Isis Project [Kevin Meyer / Phil]

       See Attachment AF

    AG. Apache James Project [Eric Charles / Roman]

       See Attachment AG

       @Roman: any prospects for new committers and PMC members?

    AH. Apache jclouds Project [Andrea Turli / Shane]

       See Attachment AH

    AI. Apache Jena Project [Andy Seaborne / Bertrand]

       See Attachment AI

    AJ. Apache JMeter Project [Bruno Demion / Ted]

       See Attachment AJ

    AK. Apache Johnzon Project [Hendrik Saly / Phil]

       See Attachment AK

    AL. Apache JSPWiki Project [Juan Pablo Santos Rodríguez / Mark]

       See Attachment AL

    AM. Apache Kudu Project [Todd Lipcon / Roman]

       See Attachment AM

    AN. Apache Lucene.Net Project [Prescott Nasser / Brett]

       No report was submitted.

       @Shane: pursue a report again for Lucene.Net

    AO. Apache Lucy Project [Peter Karman / Rich]

       See Attachment AO

    AP. Apache MADlib Project [Aaron Feng / Isabel]

       See Attachment AP

    AQ. Apache Mahout Project [Andrew Palumbo / Phil]

       See Attachment AQ

       @Phil: pursue a report for Mahout for next month

    AR. Apache Maven Project [Robert Scholte / Mark]

       See Attachment AR

    AS. Apache Mesos Project [Benjamin Hindman / Rich]

       See Attachment AS

    AT. Apache Metron Project [Casey Stella / Brett]

       See Attachment AT

       @Rich: follow up to get a better report for next month

    AU. Apache MINA Project [Jeff Maury / Shane]

       See Attachment AU

    AV. Apache MyFaces Project [Mike Kienenberger / Isabel]

       See Attachment AV

       @Rich: follow up re: responses to board comments

    AW. Apache Mynewt Project [Justin Mclean / Roman]

       See Attachment AW

    AX. Apache NiFi Project [Joe Witt / Ted]

       See Attachment AX

    AY. Apache Nutch Project [Sebastian Nagel / Bertrand]

       See Attachment AY

    AZ. Apache ODE Project [Sathwik / Phil]

       See Attachment AZ

    BB. Apache OpenJPA Project [Mark Struberg / Bertrand]

       See Attachment BB

    BC. Apache OpenMeetings Project [Maxim Solodovnik / Roman]

       See Attachment BC

    BD. Apache OpenOffice Project [Peter Kovacs / Brett]

       See Attachment BD

    BE. Apache ORC Project [Owen O'Malley / Shane]

       See Attachment BE

    BF. Apache Parquet Project [Julien Le Dem / Ted]

       See Attachment BF

    BG. Apache PDFBox Project [Andreas Lehmkühler / Mark]

       See Attachment BG

    BH. Apache Ranger Project [Selvamohan Neethiraj / Rich]

       See Attachment BH

    BI. Apache Samza Project [Yi Pan / Brett]

       See Attachment BI

    BJ. Apache Sqoop Project [Venkat Ranganathan / Ted]

       See Attachment BJ

    BK. Apache Stanbol Project [Fabian Christ / Rich]

       See Attachment BK

    BL. Apache Steve Project [Daniel Gruno / Shane]

       See Attachment BL

    BM. Apache Streams Project [Steve Blackmon / Phil]

       See Attachment BM

    BN. Apache Struts Project [René Gielen / Roman]

       See Attachment BN

    BO. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Mark]

       No report was submitted.

       @Mark: pursue a report for Tapestry

    BP. Apache Tcl Project [Georgios Petasis / Isabel]

       See Attachment BP

    BQ. Apache Tez Project [Jonathan Turner Eagles / Bertrand]

       See Attachment BQ

    BR. Apache Thrift Project [Jake Farrell / Phil]

       See Attachment BR

    BS. Apache Tika Project [David Meikle / Brett]

       See Attachment BS

    BT. Apache TinkerPop Project [Stephen Mallette / Mark]

       See Attachment BT

    BU. Apache TomEE Project [David Blevins / Rich]

       See Attachment BU

    BV. Apache Traffic Server Project [Bryan Call / Isabel]

       See Attachment BV

    BW. Apache VXQuery Project [Till Westmann / Ted]

       See Attachment BW

    BX. Apache Web Services Project [Daniel Kulp / Shane]

       See Attachment BX

    BY. Apache Wicket Project [Martijn Dashorst / Roman]

       See Attachment BY

    BZ. Apache Zeppelin Project [Lee Moon Soo / Bertrand]

       See Attachment BZ

    Committee reports approved as submitted by General Consent.

7. Special Orders

    A. Approve the 2019 FY ASF Budget

       Income
         Total Public Donations         140,000
         Total Sponsorship            1,299,000
         Total Programs                  14,400
         Conference Sponsorships        184,000
         Interest Income                 14,400
                                         ====== 
         Total Income                 1,651,800

       Expense
         Infrastructure                 965,540
         Program Expenses                 4,400
         Publicity                      238,300
         Brand Management                98,000
         Conferences                    244,500
         Travel Assistance               65,000
         Treasury                        46,200
         Fundraising                    208,000
         General & Administrative        16,400
         Chairman's discretionary        10,000
                                      =========
                                      1,896,340

       Notes:
         * Infrastructure includes a $150k correction for the Staffing
           expenditure issue raised to the Board in November 2017.

         * Both conferences sponsorships and expenses are now shown as budget
           items, whereas in previous years sponsorship revenue went primarily
           to the producer, keeping expenses low.

         * Marketing and Publicity includes $24K of expenses for Apache Way
           Outreach.

         * Fundraising includes $176K of new expenses for VP, Fundraising and
           for Ambassador services from Virtual and HALO.

         * General and Administrative reduced approximately $100K due to the
           elimination of the EA role.

       Special Order 7A, Approve the 2019 FY ASF Budget, was approved
       by Unanimous Vote of the directors present.

    B. Establish Position of VP, Sponsor Relations

       WHEREAS, the Board of Directors hereby creates the position of Vice
       President, Sponsor Relations to assist the Vice President,
       Fundraising, in maintaining good relations with the sponsors of the
       foundation; and

       NOW, THEREFORE, BE IT RESOLVED, that the number of Vice President,
       Sponsor Relations and their responsibilities shall be initially
       defined and subsequently amended at the direction of the Vice
       President, Fundraising; and

       BE IT FURTHER RESOLVED, that appointments to the office of Vice
       President, Sponsor Relations, shall be at the discretion of the Vice
       President of Fundraising, to serve in accordance with and subject to
       the direction of the Vice President of Fundraising, the ASF President,
       and the ASF Board of Directors and the Bylaws of the Foundation until
       death, resignation, retirement, removal or disqualification, or until
       a successor is appointed.

       Special Order 7B, Establish Position of VP, Sponsor Relations,
       was approved by Unanimous Vote of the directors present.

       @Sam: provide a process for appointing VP, Sponsor Relations
       and defining responsibilities

    C. Change the Apache OODT Project Chair

       WHEREAS, the Board of Directors heretofore appointed Tom Barber
       (magicaltrout) to the office of Vice President, Apache OODT, and

       WHEREAS, the Board of Directors is in receipt of the resignation of Tom
       Barber from the office of Vice President, Apache OODT, and

       WHEREAS, the Project Management Committee of the Apache OODT project
       has chosen by vote to recommend Imesha Sudasingha (imesha) as the
       successor to the post;

       NOW, THEREFORE, BE IT RESOLVED, that Tom Barber is relieved and
       discharged from the duties and responsibilities of the office of Vice
       President, Apache OODT, and

       BE IT FURTHER RESOLVED, that Imesha Sudasingha be and hereby is
       appointed to the office of Vice President, Apache OODT, to serve in
       accordance with and subject to the direction of the Board of Directors
       and the Bylaws of the Foundation until death, resignation, retirement,
       removal or disqualification, or until a successor is appointed.

       Special Order 7C, Change the Apache OODT Project Chair, was
       approved by Unanimous Vote of the directors present.

8. Discussion Items

    A. Publicize board-sanctioned list of services available to projects

       PMCs are sometimes unaware of the various services the ASF provides.  We
       should better publicize this concise and comprehensive list of pointers
       to all the organizational services the ASF has:

       https://www.apache.org/board/services

       @Shane: send note publicizing the list of services to the PMCs;
       precise url TBD

    B. Adopting a well-known COI policy

       As the ASF grows in number of paid positions and is working to
       secure more sponsors, we should adopt a well-known financial
       conflict of interest policy.  This is important to ensure that
       we have clear and consistent disclosures internally of
       financial interests in officer/director roles, as well as to
       show potential donors that we're following best practices for
       fiscal responsibility.

       I suggest the IRS example policy, which many non-profits use:
       https://www.irs.gov/instructions/i1023#en_US_2018_publink100061018
       https://www.irs.gov/charities-non-profits/form-1023-purpose-of-conflict-of-interest-policy

       This also includes an annual review statement, which should be simple to
       automate and is also reported in filing our 990s.

       There are concerns about the necessity for and the overhead involved
       in establishing and reporting on COI policy.

       @Shane: continue to discuss establishing a COI policy on board@

9. Review Outstanding Action Items

    * Ted: Discuss state of development with PMC; encourage on-list development
          [ Tajo 2017-06-21 ]
          Status: Done

    * Ted: pursue a report for Community Development; look at previous examples of
          [ Community Development 2017-08-16 ]
          Status: Moot

    * Jim: work with Greg on resourcing infra resources for OpenOffice
          [ Executive Vice President 2018-02-21 ]
          Status: ongoing

    * Mark: is this project still viable?
          [ Clerezza 2018-02-21 ]
          Status: Closed. 2 active PMC + 2 lurkers for releases, security etc.
                  so just viable.

    * Jim: follow up with PMC on activity
          [ Open Climate Workbench 2018-02-21 ]
          Status: Will follow up and ask that update be in their next report

    * Chris: pursue a report for Perl
          [ Perl 2018-02-21 ]
          Status:

    * Brett: pursue a report or Attic proposal for Xalan
          [ Xalan 2018-02-21 ]
          Status:

    * Shane: pursue a report for Archiva
          [ Archiva 2018-03-21 ]
          Status: Report is submitted.

    * Mark: pursue a report for Bahir
          [ Bahir 2018-03-21 ]
          Status: Ongoing. Chased 201804

    * Brett: pursue a report for Camel
          [ Camel 2018-03-21 ]
          Status:

    * Brett: pursue a report for Giraph
          [ Giraph 2018-03-21 ]
          Status:

    * Phil: pursue a report for Hama
          [ Hama 2018-03-21 ]
          Status: Complete.

    * Shane: pursue a report for Lucene.Net
          [ Lucene.Net 2018-03-21 ]
          Status:

    * Ted: pursue a report for Mynewt
          [ Mynewt 2018-03-21 ]
          Status: Done

    * Mark: get an answer to question on previous report: "..automatic generation
          [ Sentry 2018-03-21 ]
          Status: On-going. Chased 20180415

    * Brett: pursue a report for Stanbol
          [ Stanbol 2018-03-21 ]
          Status:

    * Jim: when will the TM be added to the logo?
          [ Xerces 2018-03-21 ]
          Status: Asks that VP Brand take this on

    * Shane: discuss this proposal on board@ for the next board to take up.
          [ Discussion Items 2018-03-21 ]
          Status: Services half of page added as discussion item. Phil will be
                  taking action item to work on policies half of the board page.

10. Unfinished Business

11. New Business

    Sam Ruby appointed Daniel Ruggeri to the position of VP, Fundraising

12. Announcements

13. Adjournment

    Adjourned at 12:19 p.m. (Pacific)

============
ATTACHMENTS:
============

-----------------------------------------
Attachment 1: Report from the VP of Brand Management  [Mark Thomas]

* ISSUES FOR THE BOARD

None.

* OPERATIONS

The last month saw the first set of paperwork requiring the use of a
Notary Public. I now have a much better handle on the costs, which are
less than $200. Given such paperwork is only expected a few times a
year, I don't plan to put in place any process to enable it to be signed
by someone in the US.

Approval was granted for using Apache owned marks in event names for
KAFKA, NETBEANS, SPARK, HBASE and SERVICECOMB.

Approval was granted for merchandise using various Apache owned marks
including ACCUMULO.

Community members reported problems creating content on Wikipedia for
our projects due to misplaced concerns from some editors regarding
copyright infringement. I reached out to clarify that our license
permits the uses in question.

Confirmed that project documentation (including images) is provided
under the ALv2 unless otherwise stated. (I'm not aware of any exceptions
- just being cautious).

Discussion has started around re-wording the current policy for required
links to be more flexible w.r.t. http vs. https. Currently, a strict
reading of the policy is that all links should be http.

* REGISTRATIONS

We have received a demand for costs amounting to €650 from the existing
owner of a BROOKLYN trademark in the EU relating to their opposition
to our attempt to register BROOKLYN in the EU. I approved this for payment.

More generally, I have noticed a tendency for donated projects to have a
wider range of registrations than the ASF would typically apply for.


* INFRINGEMENTS

There are currently 10 PMCs working on resolving infringements by
external parties. Brand Management is providing support as required.

I have sent a C&D letter on behalf of one of our projects.

Various mailing lists were hit with spam from "Maven - The World's
Largest Micro-Consulting Platform". Concerns regarding the use of Maven
were raised with the Maven PMC who assessed that no action is required
at this time.


-----------------------------------------
Attachment 2: Report from the VP of Fundraising  [Kevin A. McGrail]

Fundraising continues to go well.

In the first 11 months of FY18, *excluding the ~$900K net from the Pineapple
donation*, we have received $1574.1K, (up $263,3K from Feb 18 and up $599.3
from Mar 17) which has the ASF at 157.3% for YTD.  The budgeted Sponsor
revenue goal was $1,084K for FY18.  As such, concerns that we would be
fiscally insolvent in 5 years should be largely put to rest.

BOARD ITEM: I'd like the board to bless "1 - to set aside space on their
website for an automatically embedded and centrally maintained ASF space." as
a requirement for each project by approving adding it to the branding policy
that exists today at https://www.apache.org/foundation/marks/pmcs

Committee meetings continue monthly.

Work on Fundraising for our 2018 events continues well.

On behalf of ASF, I gave an Open Source Governance speech at GMU on 4/11.
https://docs.google.com/presentation/d/1xycSoPFDGlRui_cM-Ji-nS4yoaFc487axStVwmpzdTc/edit?usp=sharing

Attended the CIT/Mach37 United Women in Cyber event on the 29th on behalf of
the ASF as well as the WIT job fair where I met with a number of potential
sponsors.

Paper selected for FOSS Backstage.  Planning to attend BBW & FOSS Backstage
for ASF to speak on How to be an Effective Board Member:
https://foss-backstage.de/session/how-be-effective-board-member

Alexa Donations with Amazon Pay is now live.

If accepted, as of May 1, 2018 PCCC has placed a proposal for a paid role of
VP Fundraising.  Daniel Ruggeri has volunteered to also serve as volunteer VP
Fundraising where I will report to him and he will report to the President.

Work continues on improving our procedures and our playbook website.

Welcome to Ted Liu & Daniel Ruggeri to our Committee

Work continues on our three 2018 Apache events including sponsor agreements
and pitches

A Hopsie security issue was ethically disclosed and resolved.

*Recap of my Goals for the Year*

As I finish this term in Fundraising, this is a look at the goals set at last
year's face to face and their status.

DONE VIA THE AMC PROPOSAL - Look at certification and training content

DONE AND EXPANDED TO ENTIRE COMMITTEE - Setup a standing meeting w/Lynsey

DONE AND HAS BEEN SUCCESSFUL - Pursue Multi-year commitments from more
sponsors.

DECIDED NOT TO DO - Setup Sponsor Soiree before the end of CY'17

IN PLANNING STAGES - Wikipedia-like fundraising drive, with stated goals.  At
end of Year.

DONE - Document all our sponsors and contacts for billing and renewing with
notes about how we got the sponsor

DONE - Setup the Ambassador program

DONE - Contact the sponsors about invoicing, renewal dates, likelihood to
renew, PO Necessity and document their Fiscal Year.

DONE - Formalize Fundraising as a Committee

DONE - Finish the Benefits of Sponsors work that started in March F2F

DONE - Confirm we are invoicing all sponsors properly

STILL UNDER DISCUSSION - Fix the implementation of
sponsor/apachecon/thanks/etc. via something automated like
http://www.apache.org/events/README.txt

DONE - Review Proposal from Virtual to expand their role as discussed at the
F2F for Fundraising in Mar at CapitalOne.

IN PROGRESS - Make a playbook website for fundraising

DONE - Create recommendation to improve what HALO and Virtual do as well as
look at the big picture to improve things.

DONE - EXCEEDED - What is the big picture for fundraising for the next year?
FY18 Goal: $1,074K for sponsorships (vs $968K in FY17)

NOT DONE - Capture foundation/Fundraising/sponsor-contact.yaml

NOT DONE - Get ideas for sponsors that Hadrian was working but not landed.

DONE - Figure out the plan with nofollow links

DONE - Bring Guidestar profile status up to Gold.


-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity  [Sally Khudairi]

[REPORT] ASF Marketing & Publicity - April 2018

I. Budget: we are awaiting approval of our budget submission for the upcoming
fiscal year. We anticipate remaining on budget and on schedule through the
final weeks of the fiscal year.

II. Cross-committee Liaison: We published a press release in celebration of
the ASF’s 19th Anniversary https://s.apache.org/gK4Q and produced a
promotional video to accompany it https://youtu.be/Fqk_rlKiVIs . The quarterly
report for Q3 FY2018 was published slightly later than anticipated
https://s.apache.org/UtBD ; work is underway on the ASF Annual Report. We
published the latest "Success at Apache" post: "Am I there yet? A n00b's
perspective" https://s.apache.org/QyEK . Sally Khudairi continues day-to-day
Sponsor ambassadorial outreach with Fundraising, and is working with
Conferences on promoting ApacheCon and two Apache Roadshow events. She
continues to counsel a Big Data vendor on correcting their promotional
practices to align with established ASF publicity, outreach, and branding
guidelines.

III. Press Releases: the following formal announcement was issued via the
newswire service, ASF Foundation Blog, and announce@apache.org during this
timeframe:

  - 26 March 2018 - The Apache® Software Foundation Celebrates 19 Years of
    Open Source Leadership "The Apache Way"

IV. Informal Announcements: 7 items were published on the ASF "Foundation"
Blog. 4 Apache News Round-ups were issued, with a total of 195 weekly
summaries published to date. We tweeted 39 items, and have 47.3K followers on
Twitter. We posted 9 items on LinkedIn, which garnered more than 82.6K organic
impressions.

V. Future Announcements: two 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 <press@apache.org> with at least 2-weeks' notice
for proper planning and execution.

VI. Media Relations: we responded to 7 media queries. The ASF 2,918 received
press clips vs. last month's clip count of 3,200. Media coverage of Apache
projects yielded 6,293 press hits vs. last month's 7,185. ApacheCon received
86 press hits.

VII. Analyst Relations: we received one analyst query. Apache was mentioned in
29 reports by Gartner; 6 reports by Forrester; 8 reports by 451 Research; and
9 reports by IDC.

VIII. Graphics: Sally has been working on signage for various events that the
ASF will have an official presence at under the ComDev umbrella.

IX. Events liaison: Sally continues work with ASF Conferences and ComDev
regarding upcoming Apache Community events that include ApacheCon and both
Apache Roadshows.

X. Newswire accounts: we have 6 pre-paid press releases remaining with NASDAQ
GlobeNewswire through 2018.

# # #


-----------------------------------------
Attachment 4: Report from the VP of Infrastructure  [David Nalley]

General
=======
No issues to raise to the President or the Board at this time.

Finances
========
Based on "actuals" through March, Infrastructure is slightly over
budget (about 0.5%). These actuals have been used to prepare the FY19
proposed Infra budget attached to the Board's April agenda.

Short Term Priorities
=====================
- One of our third party services provides us with service monitoring
  and reporting. It will be shutting down in a few months, so we have
  begun to look for replacement service(s).
- We are looking standing up a new Jenkins "master" node which should
  improve the responsiveness/throughput of our Jenkins CI cluster.

General Activity
================
It has been a relatively quiet month, though we dealt with a seemingly
email-based DoS, a two hour datacenter downtime, and a couple disk
failures on our remaining hardware (which demonstrates our desire to
continue migrating to cloud-hosted providers).


-----------------------------------------
Attachment 5: Report from the VP of Conferences  [Rich Bowen]

# Events/Conferences

This has been a very busy month in the Events/Conferences world. We have
three events currently in flight, and several more that we're talking
about.

If you wish to be part of this conversation, you need to join the
planners list - planners@apachecon.com.

## Apache RoadShow Europe - Berlin, June 11-14 2018

The schedule has been posted -
http://apachecon.com/euroadshow18/schedule.html

## ApacheCon North America

The CFP has closed, and we are in review mode. We had 249 sessions
submitted. We plan to have a schedule ready by the end of the month.

We have added space for the Cloudstack Collaboration Conference, which
will run in parallel to ApacheCon, and the community is seeking
sponsorship for this additional space.

The GeoSpatial community has put together a one-day track.

A reminder: There is a committer discount. This information was sent to
the committers@apache.org mailing list. If you want your communities to
turn up in force, it's time to make them all committers.

Volunteers are needed for many parts of the show. Please see
https://docs.google.com/spreadsheets/d/1VWJsUp0HSa2oH6yCbOJJqw5pgdxKt_m0R8yXUcQUA8A/edit#gid=0
if you want to help.

## Apache DC RoadShow.

Kevin is putting together an event in DC in October. We have a date and
a venue, and will be promoting additional information as soon as we have
a website up.

## 2019

A venue search has begun for ApacheCon North America 2019. We are
focusing on the San Franciso Bay area, for the 20th anniversary. Once
again, please join planners@apachecon.com to participate in planning
this event.

The goal is to announce ACNA19 at ACNA18. A stretch goal is to also
announce ACEU19 at ACNA18, but nothing has been done towards that end,
yet.

We are also considering several smaller events. These might include
any of the following:

    * ApacheCon Africa
    * ApacheCruise
    * Apache RoadShow North America
    * Apache RoadShow Asia

Any of these events may or may not happen depending on interest,
project involvement, and sponsorship. We are beginning to pitch
entire-year sponsorship packages, rather than per-event sponsorship, as
this tends to be easier for corporate budgets, and ends up being a
better deal for everyone.


-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee  [Gavin McDonald]

TAC is rolling along  quiet but active in the background. Judges are scoring
applications as they come in. We have 13 applications currently, we expect
many more to come in over the final 2 weeks with applications being closed on
1st May.

No other activity currently. A discussion regarding directed sponsorship to
TAC has stalled and needs reviving.


-----------------------------------------
Attachment 7: Report from the VP of W3C Relations  [Andy Seaborne]

Nothing to report this month.


-----------------------------------------
Attachment 8: Report from the Apache Legal Affairs Committee  [Chris Mattmann]

A question arose about the redistribution of OpenJDK in Apache projects. 
Legal committee members and others on the mailing list provided advice
advising that doing so violates Apache legal policy regarding Category-X
dependencies. The project was informed and moved forward and will not be
redistributing OpenJDK.

A handful of questions about the EU’s GDPR initiative arose including one from
our VP, Infra. After discussions, VP Legal and VP Infra agreed that VP, Infra
will draft a short policy document, and then review with VP, Legal and
eventually post that policy on a public Apache web page. Likely we will employ
a similar tactic as we do with DCMA policy by having a “registered agent”
concept.

A discussion surrounding whether a modified version of the Apache license is
still “the Apache license” arose, and guidance was provided that modifications
to the license, along with naming rights for the license, necessitate changing
the license name if modifying it.

Questions surrounding Software Grants and associated materials provided with
them continue to be ongoing with ASF Secretary and ASF projects. VP, Legal has
Referred the matter to the ASF Secretary for resolution.


-----------------------------------------
Attachment 9: Report from the Apache Security Team Project  [Mark J. Cox]

Continued work on incoming security issues and helping projects clean
up the backlog of old issues and outstanding CVE names.

Stats for March 2018:

     5       [license confusion]
     21      [support request/question not security notification]

     Security reports: 47 (last month 40)
     
     4       [activemq]
     3       [nifi]
     3       [httpd]
     2       [cloudstack]
     2       [commons]
     2       [hadoop]
     2       [openoffice]
     2       [zeppelin]
     2       [infrastructure(site)]
     1 each  [airavata],[atlas],[bookkeeper],[couchdb],[fineract],[guacamole],
             [helix],[hive],[incubator/dubbo],[incubator/ripple],[incubator/skywalking],
             [jmeter],[mynewt],[openmeetings],[qpid],[spamassassin],[struts],[syncope]
             [taverna],[tika],[tomcat],[trafficserver],[vcl],[wicket]

-----------------------------------------
Attachment A: Report from the Apache Accumulo Project  [Michael Wall]

## Description:

 - The Apache Accumulo sorted, distributed key/value store is a robust,
   scalable, high performance data storage system that features cell-based
   access control and customizable server-side processing.  It is based on
   Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
   and Thrift.

## Issues:

 - There are no issues requiring board attention at this time.

## Activity:

 - There was 1 new release, Accumulo 1.7.4, since the last report. [1]
 - There were 4 new committers since the last report.  All committers are
   also PMC members.
 - The PMC decided to switch to using github issue for the project and all
   subprojects. [2]
 - The PMC decided to drop support for Hadoop 2 in the Accumulo 2.0.
 - A contributor requested permission to use the Accumulo logo on t-shirts
   and/or stickers to promote projects he uses.  VP Brand Management and the
   PMC had no objections.
 - PMC is working on a 1.9.0 release.

## Health report:

 - The project remains healthy.  Activity levels on mailing lists, git and
   JIRA remain constant.

## PMC changes:

 - Currently 34 PMC members.
 - New PMC members:
    - Adam J. Shook was added to the PMC on Wed Jan 24 2018
    - Mark Owens was added to the PMC on Tue Mar 20 2018
    - Luis Tavarez was added to the PMC on Tue Mar 20 2018
    - Nick Felts was added to the PMC on Thu Mar 22 2018

## Committer base changes:

 - See PMC changes, all committers are PMC members currently.

## Releases:

 - accumulo-1.7.4 was released on Thu Mar 22 2018

## Mailing list activity:

 - Nothing significant in the figures

## JIRA activity:

 - 65 JIRA tickets created in the last 3 months
 - 101 JIRA tickets closed/resolved in the last 3 months

[1]: http://accumulo.apache.org/release/accumulo-1.7.4/
[2]: http://accumulo.apache.org/blog/2018/03/16/moving-to-github-issues.html


-----------------------------------------
Attachment B: Report from the Apache ActiveMQ Project  [Bruce Snyder]

Description

Apache ActiveMQ is a popular and powerful open source message-oriented
middleware. Apache ActiveMQ is fast, supports many cross language clients and
protocols, comes with easy to use enterprise integration patterns and many
advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and
REST.

Activity

* ActiveMQ
** Released 5.15.3
* ActiveMQ Artemis
** The 2.5.0 release contained lots of great new features including support
   for:
*** Exclusive consumers.
*** Equivalent ActiveMQ 5.x Virtual Topic naming abilities.
*** SSL Certificate revocation list.
*** Last-value queues for OpenWire.
*** Masked passwords in bootstrap.xml and login.config
*** Configurable broker plugin implementation for logging various broker events
   (i.e. LoggingActiveMQServerPlugin).
*** Option to use OpenSSL provider for Netty via the sslProvider URL parameter.
*** Splitting of broker.xml into multiple files.
*** Enhanced message count and size metrics for queues.

Releases
* 5.15.3 was released on Wed Jan 31 2018
* Artemis 2.5.0 was released on Wed Mar 21 2018

Committer Changes
* Last PMC addition: Thu Oct 27 2016 (Clebert Suconic)
* Last committer addition: Fri Sep 29 2017 (Michael André Pearce)
* Currently 60 committers and 24 PMC members


-----------------------------------------
Attachment C: Report from the Apache Airavata Project  [Suresh Marru]

## Description:
 - Apache Airavata is a distributed system software framework to manage simple
   to composite applications with complex execution and workflow patterns on
   diverse computational resources.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - The community is active without any major concerns.

## Health report:
 - The community is active. In the past quarter we had a PMC and 3 committers
   on boarded. Airavata continued to attract Google Summer of Code proposals.

## PMC changes:

 - Currently 24 PMC members.
 - Wannipurage Dimuthu Upeksha was added to the PMC on Mon Mar 05 2018

## Committer base changes:

 - Currently 36 committers.
 - New commmitters:
    - Wannipurage Dimuthu Upeksha was added as a committer on Tue Mar 06 2018
    - Sachin Kariyattin was added as a committer on Thu Mar 08 2018
    - Sneha Tilak was added as a committer on Wed Mar 07 2018

## Releases:

 - Last release was 0.16 on Mon Jul 25 2016 We continue to fall behind on the
   release, but we getting close for the next one. With new PMC and Committers
   we hope to cut a release within the next month.

## JIRA activity:

 - 109 JIRA tickets created in the last 3 months
 - 47 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment D: Report from the Apache Apex Project  [Thomas Weise]

## Description:

Apache Apex is a distributed, large-scale, high-throughput, low-latency, fault
tolerant, unified stream and batch processing platform.

## Issues:

There are currently no issues that require the Board's attention.

## Status/Activity:

Activity in the project had declined since mid 2017 and remains very low.

The only feature addition since the last report is the Python operator that
allows native Python execution via JEP (Java Embedded Python). This allows
users to integrate Apex with machine model scoring or other algorithms
implemented in the data science friendly Python ecosystem.

No new releases since the last report. Voting is under way for a new release
candidate for Core 3.7.0.

## Community:

- Currently 16 PMC members.
- No new PMC member added in the last 3 months
- Last PMC addition was Tushar Gosavi on 2017-10-13

- Currently 41 committers.
- No new committer added in the last 3 months
- Last committer addition was Ananth Gundabattula on 2017-11-03

## Releases:

Following are the most recent releases:

- Core 3.6.0 released 2017-05-04
- Malhar 3.8.0 released 2017-11-12


-----------------------------------------
Attachment E: Report from the Apache Archiva Project  [Olivier Lamy]

## Description: 

 Apache Archiva software is an extensible repository management tool that
 helps taking care of your own personal or enterprise-wide build artifact
 repository.
   
## Issues: 

 there are no issues requiring board attention at this time
   
## Activity: 

 Some refactoring are happening now to make Archiva more generic and support
 more repository types.
 We moved our projects to gitbox.
   
## Health report: 

 We have enough PMC to cut release. 
   
## PMC changes: 
   
 - Currently 9 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Martin Stockhammer on Mon Apr 10 2017 
   
## Committer base changes: 
   
 - Currently 21 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Martin Stockhammer at Thu Sep 22 2016 
   
## Releases: 
   
 - Last release was 2.2.3 on Tue May 16 2017 
   
## Mailing list activity: 
   
 - users@archiva.apache.org:  
    - 229 subscribers (down -1 in the last 3 months): 
    - 7 emails sent to list (5 in previous quarter) 
   
 - dev@archiva.apache.org:  
    - 107 subscribers (up 0 in the last 3 months): 
    - 18 emails sent to list (9 in previous quarter) 
   
 - issues@archiva.apache.org:  
    - 34 subscribers (up 1 in the last 3 months): 
    - 4 emails sent to list (55 in previous quarter) 
   
 - notifications@archiva.apache.org:  
    - 16 subscribers (up 1 in the last 3 months): 
    - 15 emails sent to list (33 in previous quarter) 
   
   
## JIRA activity: 
   
 - 1 JIRA tickets created in the last 3 months 
 - 0 JIRA tickets closed/resolved in the last 3 months 



-----------------------------------------
Attachment F: Report from the Apache Aries Project  [Jeremy Hughes]

## Description:
- Apache Aries delivers a set of pluggable Java components enabling an
  enterprise OSGi application programming model.

## Issues:
 - No issues to report.

## Activity:
 - As a community we made 5 releases in the last reporting period around
   updates to Aries Blueprint with a mix of bug fixes and functional
enhancements.
   
## Health report: 
 - Mailing list activity up slightly on the last reporting period. Stable.
   
## PMC changes: 
   
 - Currently 38 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Dominik Przybysz on Tue May 30 2017
   
## Committer base changes: 
   
 - Currently 55 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Tom De Wolf at Wed May 03 2017
   
## Releases: 
   
 - Aries Blueprint Parser (blueprint-parser) 1.5.0 on 2018-02-14
 - Aries Blueprint Core (blueprint-core) 1.9.0 on 2018-02-14
 - Aries Blueprint CM (blueprint-cm) 1.2.0 on 2018-02-14
 - Aries Blueprint Spring (blueprint-spring) 0.6.0 on 2018-02-14
 - Aries Blueprint Spring Extender (blueprint-spring-extender) 0.4.0 on
   2018-02-14
   
## /dist/ errors: 195
 - In progress - all are old releases but some are still the most recent.
   We've requested the signer to extend their key expiration and will
review the list to see which can be archived.

## JIRA activity:

 - 24 JIRA tickets created in the last 3 months
 - 72 JIRA tickets closed/resolved in the last 3 months



-----------------------------------------
Attachment G: Report from the Apache Arrow Project  [Jacques Nadeau]

## Description:

Apache Arrow is a cross-language development platform for in-memory data. It
specifies a standardized language-independent columnar memory format for flat
and hierarchical data, organized for efficient analytic operations on modern
hardware. It also provides computational libraries and zero-copy streaming
messaging and interprocess communication. Languages currently supported include
C, C++, Go, Java, JavaScript, Python, Ruby, and Rust.

## Issues:

There are no issues requiring board attention at this time

## Activity:
 - We received a donation of a Go implementation since the last report
 - New contributors have started developing native Rust bindings. Given its 
   early development, community will likely start by doing regular Rust-only 
   releases at a higher velocity than primary releases (similar to JS)
 - Given the number of different artifacts developed, the build and release 
   complexity has gotten too difficult (too many manual steps). The 
   community is discussing ways to improve the process to simplify development.

## Health report:

Project is very healthy with a growing developer and user community.
Overall development activity has increased since the prior quarter
with the addition of two new programming languages (Go, Rust) to the
project.

## PMC changes:

 - Currently 22 PMC members.
 - New PMC members:
    - Phillip Cloud was added to the PMC on Thu Mar 15 2018
    - Philipp Moritz was added to the PMC on Thu Mar 15 2018

## Committer base changes:

 - Currently 31 committers.
 - New commmitters:
    - Antoine Pitrou was added as a committer on Tue Apr 03 2018
    - Brian Hulette was added as a committer on Mon Feb 12 2018
    - Robert Nishihara was added as a committer on Mon Feb 19 2018

## Releases:

 - 0.9.0 was released on Mon Mar 19 2018
 - JS-0.3.0 was released on Wed Feb 21 2018
 - JS-0.3.1 was released on Fri Mar 16 2018

## JIRA activity:

 - 464 JIRA tickets created in the last 3 months
 - 358 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment H: Report from the Apache AsterixDB Project  [Till Westmann]

Description:

Apache AsterixDB is a scalable big data management system (BDMS) that provides
storage, management, and query capabilities for large collections of
semi-structured data.

Activity:

- Development and discussions are active, the community is healthy and
  engaged.
- We are preparing for the 5th nonincubating release.

Issues:

- There are no issues that require the board's attention at this time.

PMC/Committership changes:

- The last committer added was Dmitry Lychagin on 2017-06-22.
- The last PMC member added was Xikui Wang on 2018-02-02.

Releases:

- Apache AsterixDB 0.9.3 was released on 2018-01-14
- Apache Hyracks 0.3.3 was released on 2018-01-14


-----------------------------------------
Attachment I: Report from the Apache Attic Project  [Jan Iversen]

## Description:
The Attic is where projects slumber when their communities fade away.
## Issues:
No issues
## Activity:
Ace moved to the Attic in the last quarter.
There was a prolonged discussion about cleaning up the dist directory, which
ended with consensus.
## PMC changes:
- Currently 21 PMC members.
- Jan Iversen was added to the PMC on Wed Mar 15 2017
## Committer base changes:
- Currently 25 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Iversen at ‪Thu Mar 16‬ 2017
## Releases:
- No release can be made in attic


-----------------------------------------
Attachment J: Report from the Apache Avro Project  [Thiruvalluvan M. G.]

## Description
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.

## Issues
The project currently has no issues that requires board attention

## Major previous milestones
   * Last release: version 1.8.2 20th May 2017.
   * Last time a new committer elected: 6 November 2017
   * Last time a new PMC elected: 11 November 2016

## Activity in the last quarter

### Committers and PMC
   * No new committer elected. Number of committers remains at 26
   * No new PMC member elected. Number of PMC members remains at 18
### Releases
   * No new release in Jan-Mar 2018. One is planned for April/May 2018
### Infrastructure
   * Moved the project to gitbox in Jan 2018
### Tickets and pull requests:
   * 48 JIRA tickets opened by 37 developers
   * 18 JIRA tickets resolved
   * 30 Pull requests opened in Github by 19 contributors
   * 8 Pull requests merged
   * The main focus of the work are mostly bug fixes and a very few
     feature enhancements. No major extension/enhancement is in the works.

### Mailing lists
   * dev@avro.apache.org
      * 397 messages (previous quarter: 408)
   * user@avro.apache.org
      * 40 messages (previous quarter: 44)

As can be seen from the numbers resolution rate is a small fraction of issue
creation rate. Will nudge the committers to resolve the tickets one way or the
other.


-----------------------------------------
Attachment L: Report from the Apache Bahir Project  [Luciano Resende]


-----------------------------------------
Attachment M: Report from the Apache Calcite Project  [Michael Mior]

## Description:

Apache Calcite is a highly customizable framework for parsing and planning
queries on data in a wide variety of formats. It allows database-like access,
and in particular a SQL interface and advanced query optimization, for data
not residing in a traditional database.

Avatica is a sub-project within Calcite and provides a framework for building
local and remote JDBC and ODBC database drivers. Avatica has an independent
release schedule and its own repository.

## Issues:

- There are no issues requiring board attention at this time.

## Activity:

Development and mailing list activity is steady for both Calcite and its
Avatica sub-project.

Avatica 1.11.0 was released early March, quickly followed by Calcite 1.16.0.
Both of these releases dropped support for JDK 7 and Avatica added support for
JDK 10. Calcite depends on this newest release of Avatica and also adds an
adapter to support Apache Geode along with improvements to the Druid and JDBC
adapters.

A paper, "Apache Calcite: A Foundational Framework for Optimized Query
Processing Over Heterogeneous Data Sources" has been accepted for publication
in SIGMOD 2018. This paper is a result of collaboration between several PMC
members and academic researchers.

We have continued to have a steady string of new committers with solid
contributions.

## Health report:

Activity levels on mailing lists, git and JIRA are normal for both Calcite and
Avatica.

## PMC changes:

 - Currently 16 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Michael Mior on Mon Apr 03 2017

## Committer base changes:

 - Currently 31 committers.
 - New commmitters:
    - Edmon Begoli was added as a committer on Fri Feb 09 2018
    - Nishant Bangarwa was added as a committer on Wed Jan 24 2018
    - Zhen Wang was added as a committer on Thu Mar 08 2018

## Releases:

 - 1.16.0 was released on Sun Mar 18 2018
 - avatica-1.11.0 was released on Thu Mar 08 2018

## JIRA activity:

 - 117 JIRA tickets created in the last 3 months
 - 96 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment N: Report from the Apache Camel Project  [Christian Mueller]


-----------------------------------------
Attachment O: Report from the Apache CarbonData Project  [Liang Chen]

## Description:

- The Apache CarbonData is an indexed columnar store file format for fast
  analytics on Big Data platforms (including Apache Hadoop, Apache Spark,
  among others) to help speed up queries an order of magnitude faster over
  petabytes of data, with the aim of using a unified file format to satisfy
  all kinds of data analysis cases.

## Issues:

- There are no new issues requiring board attention at this time.


## Activity:

- Community is pretty active, contributors who are from 30+ different
  organizations , and now the number of contributors is more than 120+, we are
  receiving around 100-200 pull requests per month.
- We completed two releases(1.3.0 and 1.3.1) in the last 3 months.
- Many users have upgraded to 1.3.1 for better performance, as per the mailing
  list group discussion, we observed that most of them focused on using these
  features: spark 2.2.1 integration , pre-aggregation, partition optimization,
  streaming ingestion.
- We are doing for version 1.4.0 : firstly we are continuing to improve the
  above mentioned features, such as : support partition with pre-aggregation,
  support streaming with pre-aggregation. secondly we are doing CarbonData
  support cloud storage, like AWS S3 or other cloud object storage.
- We organized one meetup in the past 3 months(23th Mar), the meetup focus on
  helping users to upgrade to CarbonData 1.3.1.


## Health Report:

- The project is healthy, community keep active in all the various
  categories(dev mailing list, JIRAs, and pull requests).
- We added 2 new PMC and 1 committer in Jan,2018.


## Releases:

 - 1.3.0 was released on Fri Mar 02 2018
 - 1.3.1 was released on Mon Mar 12 2018


## PMC changes:

 - Currently 11 PMC members.
 - New PMC members:
    - Kumar Vishal was added to the PMC on Tue Jan 09 2018
    - David Cai was added to the PMC on Tue Jan 09 2018


## Committer base changes:

 - Currently 16 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Kunal Kapoor at Sat Jan 06 2018


## Mailing list activity:
- Mailing list activity stays at a high level

- dev@carbondata.apache.org:
    - 178 subscribers (up 8 in the last 3 months):
    - 150 emails sent to list (250 in previous quarter)

 - issues@carbondata.apache.org:
    - 9 subscribers (up 0 in the last 3 months):
    - 10583 emails sent to list (10026 in previous quarter)

 - user@carbondata.apache.org:
    - 65 subscribers (up 5 in the last 3 months):
    - 14 emails sent to list (15 in previous quarter)

## JIRA activity:

- 322 JIRA tickets created in the last 3 months
- 288 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment P: Report from the Apache Celix Project  [Pepijn Noltes]

## Description: 
- Dynamic service framework for C and C++.
   
## Issues: 
 - there are no issues requiring board attention at this time
   
## Activity: 
- Version 2.1.0 of Celix has been released. 
- The usage of CMake is refactored so that target can be exported and used in other projects. This is more inline with modern cmake usage and hopefully makes Apache Celix easier to use.   
   
## Health report: 
 - The mailing list / jira active is normal for Apache Celix. 
   
## PMC changes: 
   
 - Currently 7 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Alexander Broekhuis on Wed Jul 16 2014 
   
## Committer base changes: 
   
 - Currently 10 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Roy Lenferink at Thu Feb 09 2017 
   
## Releases: 
   
 - 2.1.0 was released on Tue Jan 30 2018 
   
## Mailing list activity: 
   
 - dev@celix.apache.org:  
    - 58 subscribers (down -1 in the last 3 months): 
    - 23 emails sent to list (22 in previous quarter) 
   
   
## JIRA activity: 
   
 - 12 JIRA tickets created in the last 3 months 
 - 9 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment Q: Report from the Apache Chukwa Project  [Eric Yang]

## Description:
 - Chukwa is an open source data collection system for monitoring
   large distributed systems.

## Issues:
 - there are no issues requiring board attention at this time.

## Activity:
 - Energy are focused on Hadoop 3.1 release to support running
   container workload.  This will enable Chukwa to run in docker
   container for ease of deployment.

## Health report:
- Chukwa project has little development happening at this time.  There is planned
work for more development after Hadoop 3 release to include docker services.  This
will require new work to monitor Docker services running in Hadoop.

## PMC changes:

 - Currently 12 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Alan Cabrera on Tue Oct 15 2013

## Committer base changes:

 - Currently 16 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Sreepathi Prasanna at Mon Mar 16 2015

## Releases:

 - Last release was 0.8.0 on Fri Jul 15 2016

## Mailing list activity:

 - dev@chukwa.apache.org:
    - 87 subscribers (down 1 in the last 3 months):
    - 6 emails sent to list (10 in previous quarter)

 - user@chukwa.apache.org:
    - 153 subscribers (up 0 in the last 3 months):
    - 6 emails sent to list (5 in previous quarter)

## JIRA activity:

 - 0 JIRA tickets created in the last 3 months
 - 2 JIRA tickets closed/resolved in the last 3 months

-----------------------------------------
Attachment R: Report from the Apache Crunch Project  [Josh Wills]

## Description: 
 - Apache Crunch is a Java library for writing, testing, and running MapReduce
 and Apache Spark pipelines on Apache Hadoop. 
   
## Issues: 
 - There are no issues requiring board attention at this time. 
   
## Activity: 
 - This quarter was relatively quiet and was primarily focused on fixing
 small bugs in the HBase, Kafka, and Hive integrations that Crunch provides.
 A number of these fixes came from Clement Mathieu, who looks like a good
 candidate to be a new committer on the project along with Stephen Durfey,
 who became a committer in February.
  
## Health report: 
 - Crunch continues to move at a steady pace of commits and bug fixes,
 but there has not been a major push from the community to add or update
 the existing functionality beyond the set of things that Crunch does well
 already. The biggest obvious improvement to the project is an upgrade of
 the APIs for the HBase dependency, but that isn't necessarily the
 kind of work that a developer would be interested in doing for fun (as
 opposed to as a result of a specific need for their work and a desire to
 contribute that work back to the community.) 
   
## PMC changes: 
   
 - Currently 12 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Micah Whitacre on Wed Apr 02 2014 
   
## Committer base changes: 
   
 - Currently 15 committers. 
 - Stephen Durfey was added as a committer on Fri Feb 09 2018 
   
## Releases: 
   
 - Last release was 0.15.0 on Sat Feb 25 2017 
   
## JIRA activity: 
   
 - 8 JIRA tickets created in the last 3 months 
 - 7 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment S: Report from the Apache CXF Project  [Daniel Kulp]

## Description: Apache CXF is an open source services framework. CXF helps you
build and develop services using frontend programming APIs, like JAX-WS and
JAX-RS. These services can speak a variety of protocols such as SOAP,
XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as
HTTP, JMS or JBI.

There are also two sub-projects that leverage CXF:

Fediz - Fediz helps you to secure your web applications via the standard
WS-Federation Passive Requestor Profile.

DOSGi - is the reference implementation of the Distribution Provider component
of the OSGi Remote Services Specification

## Issues: There are no issues requiring board attention at this time

## Activity: Activity this quarter centered around a few efforts:
This was a busy quarter, but not really for positive reasons.  Java8 update 161
contained a behavioral change in the included JAXB implementation that broke
some CXF tests and use cases.   We scrambled to get a fix out (in 3.2.2), but
subsequent user testing identified additional cases that were not fixed as
well as cases that then broke with the new fix.  We needed to follow
up with additional releases fairly quickly to address those issues.

One note: April 16th will mark 10 years since CXF graduated from the incubator

## PMC changes:
 - No new PMC members added in the last 3 months
 - Last PMC addition was Dennis Kieselhorst on Thu Nov 02 2017

## Committer base changes:
 - No new committers added in the last 3 months
 - Last committer addition was Alexey Markevich at Fri Dec 29 2017

## Releases:
 - 3.2.2 was released on Tue Feb 06 2018
 - 3.1.15 was released on Mon Mar 12 2018
 - 3.2.3 was released on Sun Mar 18 2018
 - 3.2.4 was released on Sat Mar 24 2018


-----------------------------------------
Attachment T: Report from the Apache DataFu Project  [Matthew Hayes]

## Description:

 - DataFu provides a collection of Hadoop MapReduce jobs and Pig UDFs to
   perform data analysis. It provides functions for common statistics tasks
   (e.g. quantiles, sampling), PageRank, stream sessionization, and set and
    bag operations. DataFu also provides Hadoop jobs for incremental data
    processing in MapReduce.

## Issues:

 - There are no issues requiring board attention at this time.

## Activity:

 - Post-graduation work has been completed.
 - Released 1.4.0, the first release since graduating from incubator.

## PMC changes:

 - Currently 11 PMC members.
 - No new PMC members added in the last 3 months

## Committer base changes:

 - Currently 18 committers.
 - No changes (the PMC was established in the last 3 months)

## Releases:

 - 1.4.0 was released on Wed Mar 22 2018

## JIRA activity:

 - 13 JIRA tickets created in the last 3 months
 - 16 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment U: Report from the Apache DB Project  [Bryan Pendleton]

Report from the Apache DB Project  [Bryan Pendleton]

## Description:

The Apache DB TLP consists of the following subprojects:
 o Derby    : a relational database implemented entirely in Java.
 o JDO      : focused on building the API and the TCK for compatibility
              testing of Java Data Object implementations providing data
              persistence.
 o Torque   : an object-relational mapper for Java.

## Issues:

## Activity:

Derby 10.14.1.0 was released on Oct 13, 2017. Work on Derby 10.14.2.0
is underway and the release is anticipated in the next quarter.

## Health report:

In general, the software in the DB project is mature and reliable,
and isn't undergoing much change. Activity continues to be low, but
stable. Periodic releases occur, primarily containing bug fixes,
and are successfully voted on.

## PMC changes: 
   
 - Currently 43 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Matthew Adams on Sun Jan 19 2014 
   
## Committer base changes: 
   
 - Currently 44 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Brett Bergquist at Tue Aug 30 2016 
   
## Releases: 
   
 - Last release was Derby-10.14.1.0 on Fri Oct 13 2017


-----------------------------------------
Attachment V: Report from the Apache Directory Project  [Stefan Seelmann]

## Description:

The Apache Directory TLP consists of the following sub-projects:
 - ApacheDS: An extensible and embeddable directory server entirely
             written in Java, which has been certified LDAPv3
             compatible by the Open Group. Besides LDAP it supports
             Kerberos 5 and the Change Password Protocol.
 - LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
             replacement for JNDI and the existing LDAP API (jLdap
             and Mozilla LDAP API). This is a "schema aware" API
             with some convenient ways to access all types of LDAP
             servers.
 - Studio:   A complete directory tooling platform intended to be
             used with any LDAP server however it is particularly
             designed for use with ApacheDS. It is an Eclipse RCP
             application, composed of several Eclipse (OSGi) plugins.
 - Fortress: A standards-based access management system that provides
             role-based access control, delegated administration and
             password policy services with an LDAP backend.
 - Kerby:    An implementation of Kerberos v5 protocol and contains
             various tools to access and manage kerberos principals
             and keytabs. It provides a rich, intuitive and
             interoperable implementation, library, KDC and various
             facilities that integrates PKI, OTP and token (OAuth2)
             as desired in modern environments such as cloud, Hadoop
             and mobile.
 - Mavibot:  An embeddable key-value database library with MVCC
             (Multi Version Concurrency Control) support.

## Issues:

 - there are no issues requiring board attention at this time

## Activity:

Per sub-project:

 - ApacheDS: good activity: Transaction support added.
 - LDAP API: good activity: Release preparation started
 - Studio:   good activity: Release to fix Java 9/10 issues planned
 - Fortress: low activity
 - Kerby:    good activity: More work on new "Hadoop Authentication
             Service" and some bugfixes. Discussion about next release.
 - Mavibot:  no activity

## Health report:

  Overall develomment activity (commits, development related mails,
  resolved issues, releases) was similar to previous quarter.

  There are some new contributors which should be considered
  for committership if they stay active.

  The PMC feels the project is still healthy.

## PMC changes:

 - Currently 18 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Chris Pike on Wed Nov 23 2016

## Committer base changes:

 - Currently 57 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Wei Zhou at Fri Sep 29 2017

## Releases:

 - No release in the last 3 months
 - Apache Kerby 1.1.0 was released on Mon Nov 27 2017

## Mailing list activity:

 - Same activiy level then previous quarter

## JIRA activity:

 - 61 JIRA tickets created in the last 3 months
 - 49 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment W: Report from the Apache Fineract Project  [Myrle Krantz]

## Description

Apache Fineract (\’fīn-,ә-,rakt\) is an open source system for core banking as
a platform. Fineract provides a reliable, robust, and affordable solution for
entrepreneurs, financial institutions, and service providers to offer
financial services to the world’s 2 billion underbanked and unbanked.

## Issues

## Activity

We've added committers.

We've started adapting Fineract CN (formerly mifos i/o) to its new home at
Apache. There is still a lot of work to do, and it isn't all captured in
tickets yet.  In particular, Fineract CN is not yet through IP clearance with
the incubator.  Those committers interested in Fineract CN are having trouble
keeping up with the significant interest from contributors.

We've almost released 1.1 containing the following major improvements:

-- Integration of data import tool and enhancements for usability and better
   performance

-- Integration of staff notifications framework including the introduction of
   a topic-subscriber model architecture

-- Support for two-factor authentication with OTP delivery via SMS or email
   and the configuration of remember-me tokens

-- Create and schedule ad-hoc queries to run and generate reports.

-- Support for equal installments with equal amortization of principal and
   interest.

## Health report

We are struggling again with unmerged pull requests. Currently, the oldest
open pull request is from May 2016.The number of open pull requests has
increased from from 16 to 23. Of these, only 9 have received no comment.  The
oldest of those 9 is from November 2017. However it is not that these are
lacking attention as we've tagged several of these pull requests for the next
release, Fineract 1.2, but are still awaiting review of these from committers
who have little time to do so yet.

In an effort to move towards more regular time-driven releases (monthly), we
successfully transferred knowledge about the release process to several
additional committers but have still become bottlenecked in release management
with committers not having time to review the tagged pull requests.

Efforts are also under way to utilize Apache virtual machine infrastructure to
set up a publicly accessible demonstration instance for Fineract CN. Progress
is stalled though as the committers who have volunteered for the effort don't
have the requisite knowledge to complete the task and the volunteers willing
and able to do the work need to be added as committers.

Discussion led by Yannick Awasum has begun around addressing the hibernate
dependency in Fineract CN which needs to be addressed prior to any release;
unfortunately there has been little to no participation from other community
members in this regard.

Functional discussion around features for the Fineract CN roadmap have begun
but are also proceeding more slowly than desired. Discussion related to key
components for migration of users of Fineract 1.x to Fineract CN (i.e. group
lending support, data migration tools, etc.) has been lacking and once again
it relates to low input from our PMC and older committers.

Discussion led by individual product management volunteers around domain areas
such as machine learning and credit analysis, reporting, regulatory
compliance, etc. is ongoing but slow as well.

Documentation for Fineract CN is growing and Isaac Kamga has led a webinar on
customizing a microservice. He is also leading work on live documentation of
APIs via Spring REST Docs which will be made available in the upcoming
quarter. Nonetheless, more documentation is needed and we continue to recruit
volunteers to take on these tasks.

Evaluation of students for Google Summer of Code is taking place with an
emphasis on projects related to Fineract CN including a data import tool,
additional microservices, containerization, enhancements to Fineract CN
mobile, and support for group-based lending operations.

We continue to add committers at a steady clip.  We haven't had any new PMC
members in a while however.

The addition of new committers and ideally the addition of new PMC members is
essential right now as a good proportion of the current base of our PMC
(primarily the original set of PMC members adding during incubation) have been
idle and providing little active contribution. New committers and PMC members
have been taking up additional work loads but are being overwhelmed with
requests to assist.

## PMC changes

- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Avik Ganguly on Sat Oct 14 2017

## Committer base changes

- Currently 25 committers.
- New commmitters:
   - Courage Angeh was added as a committer on Thu Apr 12 2018 
   - Steve Conrad was added as a committer on Wed Mar 28 2018
   - Isaac Kamga was added as a committer on Mon Mar 19 2018
   - Rajan Maurya was added as a committer on Mon Mar 05 2018

## Releases

 - 1.1.0 was released on Wed Apr 18 2018 

## Mailing list activity:
- Subscriber counts to dev, user, and issues have been steadily increasing.
- For the first time in two quarters email counts actually are comparable with
  previous quarters after our mid-September rearrangement of what e-mails are
  sent to which lists.

- dev@fineract.apache.org:
- 243 subscribers (up 39 in the last 3 months):
- 807 emails sent to list (664 in previous quarter)

- issues@fineract.apache.org:
- 17 subscribers (up 5 in the last 3 months):
- 342 emails sent to list (247 in previous quarter)

- user@fineract.apache.org:
- 179 subscribers (up 18 in the last 3 months):
- 59 emails sent to list (146 in previous quarter)


## JIRA activity:
- Jira ticket creation has been down significantly, but the existing JIRA
  tickets are getting more traffic than in the last quarter.

- 19 JIRA tickets created in the last 3 months
- 4 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment X: Report from the Apache Fluo Project  [Keith Turner]

## Description:
 - Apache Fluo is a distributed processing system built on Apache Accumulo.
   Fluo users can easily setup workflows that execute cross node transactions
   when data changes.  These workflows enable users to continuously join new
   data into large existing data sets with low latency while avoiding
   reprocessing all data.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - Voted to merge committers and PMC
 - Made Fluo available at hub.docker.com/r/apache/fluo/
 - Discussed accepting some external Fluo test and example projects
 - Documented how to test/verify a release

## Health report:
 - 60 GitHub PRs opened and 58 closed [1/10-4/11]
 - 15 issues opened and 4 closed [1/10-4/11]
 - 70 commits from 5 committers and 4 contributors [1/10-4/11]
 - 1 new contributor [1/10-4/11]

## PMC changes:

 - Currently 9 PMC members.
 - Kenneth Mcfarland was added to the PMC on Mon Mar 19 2018

## Committer base changes:

 - Currently 9 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Kenneth Mcfarland at Thu Dec 07 2017

## Releases:

 - fluo-1.2.0 was released on Sun Feb 25 2018
 - fluo-recipes-1.2.0 was released on Mon Mar 05 2018
 - fluo-yarn-1.0.0 was released on Mon Mar 05 2018

-----------------------------------------
Attachment Y: Report from the Apache FreeMarker Project  [Dániel Dékány]

## Description:

Apache FreeMarker is a template engine, i.e. a generic tool to generate text
output based on templates. Apache FreeMarker is implemented in Java as a class
library for programmers.

FreeMarker 2 (the current stable line) produces releases since 2002. The
FreeMarker project has joined the ASF in 2015, and graduated from the
Incubator in early 2018.

## Issues:

There are no issues requiring board attention at this time.

## Activity:

We have graduated from the Incubator on 2018-03-21, and have transferred the
resources out of the Incubator.

We have released FreeMarker 2.3.28 on 2018-04-04, which is our first
non-incubating release from Apache.

There was some activity around Eclipse plugin development, as JBoss has
officially stopped maintaining the current plugin (after 12 years). Thus, we
have considered bringing that over to Apache (under the FreeMarker project),
which looks somewhat complicated legally. But as one of our users has started
another plugin, now we are waiting to see if that will reach a state where we
should adopt that instead.

## Health report:

Activity is relatively low but steady, as it's usual for this project. User
questions and new Jira issues are being answered promptly.

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. (Meanwhile, the backward compatible 2.x branch must be
maintained, and produce releases.)

## 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

## Mailing list activity:

 - dev@freemarker.apache.org:
    - 62 subscribers (up 3 in the last 3 months):
    - 241 emails sent to list (188 in previous quarter)
    - This list is used both by developers and users; note that support is
      mostly provided on StackOverflow, not on the mailing list.

 - notifications@freemarker.apache.org:
    - 15 subscribers (up 0 in the last 3 months):
    - 631 emails sent to list (759 in previous quarter)

## JIRA activity:

 - 7 JIRA tickets created in the last 3 months
 - 11 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment Z: Report from the Apache Geronimo Project  [Romain Manni-Bucau]

## Description:
 - Apache Geronimo project is stilll moving from a full EE server activity to
   a JavaEE/EE4J/Microprofile umbrella project and hosts EE utilities as well
   as specification API and implementations.

## Issues:
 - some discussion across Geronimo and TomEE community (which have a huge
   overlap in terms of people) to host jwt-auth can lead to have 2 concurrent
   projects and split a bit the communities, we need to take care of that
   point
 - we still need to put our spec releases in the dist area

## Activity:
 - discussion on revamping the website was relaunched, we are expecting some
   more activity on that in the coming months
 - a simple jcache implementation has been created
 - a microprofile jwt auth module has been created (but not yet provisionned)
 - a new xbean released has been done

## Health report:
 - Microprofile still drives activity but we got some EE activity too
 - XBean has been released too

## PMC changes:

 - Currently 37 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was John D. Ament on Thu Aug 24 2017

## Committer base changes:

 - Currently 67 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Jean-Louis Monteiro at Fri Jul 14 2017

## Releases:

 - XBean was released on Mar 22 2018

## Mailing list activity:

 - Activity is mainly about the website and microprofile-jwt-auth

 - dev@geronimo.apache.org:
    - 329 subscribers (down -4 in the last 3 months):
    - 188 emails sent to list (74 in previous quarter)

 - geronimo-tck@geronimo.apache.org:
    - 43 subscribers (up 0 in the last 3 months)

 - scm@geronimo.apache.org:
    - 93 subscribers (down -2 in the last 3 months):
    - 77 emails sent to list (34 in previous quarter)

 - tck-commits@geronimo.apache.org:
    - 6 subscribers (up 0 in the last 3 months)

 - user@geronimo.apache.org:
    - 432 subscribers (down -5 in the last 3 months):
    - 2 emails sent to list (4 in previous quarter)


## JIRA activity:

 - 9 JIRA tickets created in the last 3 months
 - 13 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AA: Report from the Apache Giraph Project  [Avery Ching]


-----------------------------------------
Attachment AB: Report from the Apache Hadoop Project  [Christopher Douglas]

Apache Hadoop is a set of related tools and frameworks for creating and
managing distributed applications running on clusters of commodity
computers.

Hadoop maintains five to seven active release branches. We hope this will be
the peak. That said, the 3.x releases are a healthy balance of stabilization
in 3.0.1 and new features merged and released in 3.1.0.

RELEASES

3.0.1 was released 2018-03-22
3.1.0 was released 2018-04-05

COMMUNITY

(+ PMC Rakesh Radhakrishnan 2018-01-23)
(+ committer Hanisha Koneru 2018-01-10)
(+ committer Mukul Kumar Singh 2018-02-09)
(+ committer Rushabh Shah 2018-04-06)
(+ committer Bharat Viswanadham 2018-04-06)
(+ branch-HDFS-12090 Bert Verslyppe 2018-03-14)
(+ branch-HDFS-12090 Ewan Higgs 2018-01-19)
(+ branch-HDFS-12943 Chao Sun 2018-01-02)
(+ branch-HDFS-12943 Erik Krogen 2018-01-10)
(+ branch-YARN-7402 Botong Huang 2018-01-31)
(+ branch-YARN-7402 Giovanni Matteo Fumarola 2018-01-31)
auth: 183 committers (including branch) and 92 PMC members

-----------------------------------------
Attachment AC: Report from the Apache Hama Project  [Chia-Hung Lin]

## Description:
 - Apache Hama is a framework for Big Data analytics based on the Bulk
Synchronous Parallel paradigm

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - The project currently focuses on making the system more componentization.

## Health report:
 - Mailing list has little traffic at the moment.

## PMC changes:

 - Currently 10 PMC members.
 - No new PMC members added in the last 4 months
 - Last PMC addition was Behroz Sikander on Mon Feb 01 2016

## Committer base changes:

 - Currently 17 committers.
 - No new committers added in the last 3 months
 - Last committer addition was JongYoon Lim at Tue Sep 13 2016

## Releases:

 - Last release was hama-0.7.1 on Sun Mar 13 2016


-----------------------------------------
Attachment AD: Report from the Apache HBase Project  [Misty Stanley-Jones]

HBase is a distributed column-oriented database built on top of Hadoop Common and Hadoop HDFS.

hbase-thirdparty is a set of internal artifacts used by the project to mitigate the impact of our dependency choices on the wider ecosystem.

ISSUES FOR THE BOARD’S ATTENTION

RELEASES

HBase 1.4.1 was released on Thu Feb 01 2018.

HBase 1.4.2 was released on Tue Feb 27 2018.

HBase 2.0.0-beta-2 was released on Tue Mar 06 2018.

hbase-thirdparty 2.1.0 was released on Sat Mar 23 2018.

HBase 1.3.2 was released on Wed Mar 28 2018.

HBase 1.4.3 was released on Thu Mar 29 2018.

   
ACTIVITY

HBaseCon US has been announced and will take place at Joseph McEnery Convention Center in San Jose, CA, on June 18, 2018. Details can be found at https://hbase.apache.org/hbasecon-2018/, and session proposals are currently being solicited. Thanks to Josh Elser for heading up organization of this event.

In addition, the second annual HBaseCon Asia is being held in Beijing, China, on Aug. 17, 2018. The event will be sponsored by Alibaba, Huawei, and Xiaomi. Admission will be free to attendees. Thanks to Yu Li for coordinating the event. 

Development toward a HBase 2.0.0 release is going well, with the second beta released in early March. Thanks to Michael Stack for driving the 2.0.0 effort. Aside from the code itself, there has been a strong focus on stability and performance improvements, as well as documentation for new features and improvements.

Work on the HBase 1.4.x line is going well, with the releases of 1.4.1, 1.4.2, and 1.4.3 this quarter.

The 1.3.x line is also seeing progress, with the 1.3.2 release.

Three committers agreed to step up as PMC members during this reporting period:

- Ashish Singhi was added to the PMC on Sun Feb 25 2018
- Mike Drob was added to the PMC on Fri Feb 23 2018
- Guanghao Zhang was added to the PMC on Sun Feb 25 2018
 
Two contributors became committers during this reporting period:

- Peter Somogyi was added as a committer on Wed Feb 21 2018
- Zach York was added as a committer on Thu Mar 01 2018

Thanks to the new committers and PMC members for agreeing to take on more responsibilities in the project.

STATS

The dev@ mailing list saw a slight decline in subscribers over the last quarter, and a 4% decrease in traffic.

The user@ mailing list saw a a slight decline in subscribers as well, but a 10% increase in traffic.

73 committers (+3 from last quarter)
41 PMC members (+2 from last quarter)
664 JIRA tickets created (down from 755 last quarter)
651 JIRA tickets closed/resolved (down from 730 last quarter)


-----------------------------------------
Attachment AE: Report from the Apache Incubator Project  [John D. Ament]

Incubator PMC report for April 2018

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 53 podlings incubating. During the month of March,
podlings executed 5 distinct releases, 6 total artifacts.  We added 2 new IPMC
members.  While no podlings are graduating this month, many are heading towards
graduation based on below reports.

* Community

  New IPMC members:

  - Jun Rao
  - Matt Sicker

  People who left the IPMC:

  - None

* New Podlings

  - None

* Podlings that failed to report, expected next month

  - Gossip - No on list activity, likely to retire.

* Graduations

  The board has motions for the following:

  - None

* Releases

  The following releases entered distribution during the month of March:

  - 2018-03-04 Apache Rya 3.2.12
  - 2018-03-05 Apache Pulsar 1.22.0
  - 2018-03-09 Apache SensSoft Useralejs 1.0.0
  - 2018-03-17 Apache HAWQ 2.3.0.0
  - 2018-03-27 Apache ServiceComb Service Center 1.0.0-m1
  - 2018-03-27 Apache ServiceComb Saga 0.1.0

* Infrastructure

  - An issue came up recently between the ECharts podling and Infrastructure
    that was communicated privately to mentors - not posted to any list.  In
    future, such problems should at least be reported to the private@incubator
    list to ensure they are archived.

----------------------------------------------------------------------
                       Table of Contents
Airflow
Amaterasu
Annotator
BatchEE
Druid
Dubbo
ECharts
Gearpump
Gobblin
HAWQ
Hivemall
Livy
Milagro
MXNet
Nemo
NetBeans
ODF Toolkit
PLC4X
Pony Mail
Quickstep
Rya
SensSoft
ServiceComb
SINGA
Traffic Control
Weex

----------------------------------------------------------------------

--------------------

Airflow

Airflow is a workflow automation and scheduling system that can be used to
author and manage data pipelines.

Airflow has been incubating since 2016-03-31.

Three most important issues to address in the move towards graduation:

  1. Once we make a release with the licensing fix we will move forward with
  graduation.
  2.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None


How has the community developed since the last report?
1. Since our last podling report 1.5 months ago (i.e. between Feb 8 & March
   28, inclusive), we grew our contributors from 375 to 427
2. Since our last podling report 1.5 months ago (i.e. between Feb 8 & March
   28, inclusive), we resolved 152 pull requests (currently at 2280 closed
   PRs)
3. Since being accepted into the incubator, the number of companies officially
   using Apache Airflow has risen from 30 to 149, 17 new from the last podling
   report 1.5 months ago.


How has the project developed since the last report?
  See above : 152 PRs resolved, 52 new contributors, & 17 new companies
  officially using it.

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-01-02

When were the last committers or PPMC members elected?

  2017-11-30 joygao a.k.a Joy Gao (committer/PMC)

Signed-off-by:

  [ ](airflow) Chris Nauroth
     Comments:
  [x](airflow) Hitesh Shah
     Comments:
  [x](airflow) Jakob Homan
     Comments: Ready for graduation


IPMC/Shepherd notes:
I checked into the licensing issue and it is resolved, but it seems that a
release will be needed before graduation. Dave Fisher

--------------------

Amaterasu

Apache Amaterasu is a framework providing configuration management and
deployment for Big Data Pipelines.

It provides the following capabilities:

Continuous integration tools to package pipelines and run tests. A repository
to store those packaged applications: the applications repository. A
repository to store the pipelines, and engine configuration (for instance, the
location of the Spark master, etc.): per environment - the configuration
repository. A dashboard to monitor the pipelines. A DSL and integration hooks
allowing third parties to easily integrate.

Amaterasu has been incubating since 2017-09.

Three most important issues to address in the move towards graduation:

1. Prepare the first release
2. Grow up user and contributor communities
3. Prepare documentation

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?

* One conference talks are scheduled in the near future (Voxxed Days
  Melbourne)

How has the project developed since the last report?

* since the last report 12 PRs were opened and 11 are merged
* One additional contributor started contributing to the code base
* One organization we are aware of have started a POC with Amaterasu
* We are in the process of automating the release process as preparation for
  the first release in the incubator.

Date of last release:

N/A

When were the last committers or PMC members elected?

N/A

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [X] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  XXXX-XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

  [X](amaterasu) Jean-Baptiste Onofré
     Comments: Clearly we need to move
   forward on the community grow up and first release.
  [X](amaterasu) Olivier Lamy
     Comments:
  [X](amaterasu) Davor Bonaci
     Comments: low activity, improvements needed to
   get back on track.

--------------------

Annotator

Annotator provides annotation enabling code for browsers, servers, and humans.

Annotator has been incubating since 2016-08-30.

Three most important issues to address in the move towards graduation:

  1. Establishing a release cadence.
  2. Demonstrating utility in the wild.
  3. Increasing community participation.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

None at this time.

How has the community developed since the last report?

  * Two members of the initial committers list have established ASF accounts.
  * The community is scheduling a teleconference for the coming weeks.
  * The community is discussing a face-to-face meeting in the coming months.
  * Several community members have expressed interest in helping with code and
    non-code contributions.

How has the project developed since the last report?

  * Licensing documentation has been updated in preparation for release.
  * Initial test suite automation has been completed.

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:

The initial setup feels complete now. There is work toward a first releases
happening. The community is slowly attracting new voices, but volume of
participation is still low.

Date of last release:

  N/A

When were the last committers or PPMC members elected?

Initial committers having completed setup, the project now has enough
participants to perform elections. At this time, no elections have been
finalized.

Signed-off-by:

  [x](annotator) Nick Kew
     Comments:
  [ ](annotator) Brian McCallister
     Comments:
  [ ](annotator) Daniel Gruno
     Comments:
  [X](annotator) Jim Jagielski
     Comments: As noted, progress is somewhat slow,
   but not to point of any concern at this stage.

--------------------

BatchEE

BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a
set of useful extensions for this specification.

BatchEE has been incubating since 2013-10-03.

Three most important issues to address in the move towards graduation:

None

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?

Community is stable. We still get feedback and have active people around.

How has the project developed since the last report?

We got some enironment related enhancements/bugfixes.

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:

  2017-12-01 batchee-0.5-incubating

When were the last committers or PPMC members elected?

  2015-12-01 Reinhard Sandtner



Signed-off-by:

  [ ](batchee) Jean-Baptiste Onofré
     Comments:
  [ ](batchee) Olivier Lamy
     Comments:
  [X](batchee) Mark Struberg
     Comments:

IPMC/Shepherd notes:
It is time for this podling to graduate. I really think that they should take
the time and JFDI. Dave Fisher.


--------------------

Druid

Druid is a high-performance, column-oriented, distributed data store.

Druid has been incubating since 2018-02-28.

Three most important issues to address in the move towards graduation:

1. Complete SGA for current sources and ICLAs for current committers.
2. Move the source code and website to Apache infrastructure.
3. Plan and execute our first Apache release.

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 moved development discussions to our Apache dev mailing list.
- A healthy, constant flow of bug fixes, quality improvements and new features
  are still ongoing on https://github.com/druid-io/druid.

How has the project developed since the last report?

- Since the last report there have been 36 commits from 18 individuals.
- We have released Druid 0.12.0 (outside the Incubator). We are optimistic
  that our next release will be done as an Apache release.

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:

- Druid 0.12.0 on 2018-03-06 (non-Apache release)
- No official release yet since beginning Apache Incubation

When were the last committers or PPMC members elected?

- Project is still functioning with the initial set of committers.

Signed-off-by:

  [x](druid) Julian Hyde
     Comments: The project still has good momentum getting
   through the initial tasks, and development/community activities continue at
   usual pace.
  [x](druid) P. Taylor Goetz
     Comments: Project seems to be progressing nicely.
  [ ](druid) Jun Rao
     Comments:

--------------------

Dubbo

Dubbo is a high-performance, lightweight, java based RPC framework.

Dubbo has been incubating since 2018-02-16.

Three most important issues to address in the move towards graduation:

  1. First ASF release
  2. Migrate remaining assets to the ASF
  3. Community building

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?

 * Complete ICLA for all PPMC
 * SGA has been filed
 * The community has decided to use Github issue instead of JIRA
 * Discussed feature donation by external users. e.g. circuit breaker, xmlrpc
 * Received 1 GSoc student application (Raghu on Protocol Buffer integration)
 * Currently ~450 mails on the dev@ list
 * 9 new companies reported their using of Dubbo since last report

How has the project developed since the last report?

 * Dubbo 2.6.1 & Dubbo 2.5.10 released (prior to code transition, non-ASF
   release)
 * Move 7 repos (including the core Dubbo repo) to Apache
 * Website (dubbo.incubator.apache.org) has been enabled
 * Website has been updated to be complied with ASF branding policy
 * 37 pull request created, 21 of them are closed
 * 80 Github issues created, 22 of them are closed

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?

N/A

Signed-off-by:

  [X](dubbo) Justin Mclean
     Comments:
  [X](dubbo) John D. Ament
     Comments: Podling is moving forward very well.  An
   on list discussion about splitting up the dev list into multiple lists has
   started.
  [ ](dubbo) Jean-Frederic Clere
     Comments:
  [ ](dubbo) Mark Thomas
     Comments:

IPMC/Shepherd notes:
An excellent start. Dave Fisher


--------------------

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. Get repo moved to https://github.com/apache/incubator-echarts.
  2. Get GitHub ID linked and 2FA enabled.
  3. First pushed to https://github.com/apache/incubator-echarts.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

Currently the setting page of GitHub is not visible to us. There may be a
problem when we need to configure it (e.g.: see if anything goes wrong when
building gh-pages branch) but communication is delayed via email. So we'd like
to ask if it is possible for at least one of us core committers to have the
admin right.

How has the community developed since the last report?

We released the information that ECharts has become a repo of Apache, and
received positive feedback from the community.

How has the project developed since the last report?

None.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [x] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

N/A

When were the last committers or PPMC members elected?

N/A


Signed-off-by:

  [X](echarts) John D. Ament
     Comments: Lots of development activities picking
   up.  Need to encourage more on list discussion.  Its often hard to sift
   through the developer list due to gitbox notifications.
  [ ](echarts) Daniel Gruno
     Comments:
  [ ](echarts) Kevin A. McGrail
     Comments:
  [X](echarts) Dave Fisher
     Comments: They are really just getting started now
   that the repos is transferred. The mentors are going to need to educate the
   podling more, but they have found infra users ML and have asked about how
   to split up the email flows. One thing I have noticed about GitBox projects
   is that it is harder to understand what is happening in those notifications
   vs. JIRAs. (That's just an observation, not sure of the Way yet.

--------------------

Gearpump

  Gearpump is a reactive real-time streaming engine based on the micro-service
  Actor model. Gearpump has been incubating since 2016-03-08.

Three most important issues to address in the move towards graduation:

1. Have frequent release cycles.
2. Continue to evolve community interest and support.
3. Increase user adoption.


- 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?
 Gearpump took part in Google Summer of Code 2017 project and it has been
 succeffully accompolished by student, Buddhi Ayesha, who is interested in
 making more contributions beyond the project.

- How has the project developed since the last report?
 32 issues created and 20 issues resolved. Gearpump Runner has been merged
 into Apache Beam trunk. An experimental SQL support has been added and state
 management is under development.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:
 2017-07-17

When were the last committers or PMC members elected?
 No new committers or PMC members elected yet.

Signed-off-by:

 [X](gearpump) Jean-Baptiste Onofré
     Comments:
 [ ](gearpump) Andrew Purtell
     Comments:
 [ ](gearpump) Jarek Jarcec Cecho
     Comments:
 [ ](gearpump) Reynold Xin
     Comments:
 [ ](gearpump) Todd Lipcon
     Comments:
 [ ](gearpump) Xuefu Zhang
     Comments:

IPMC/Shepherd notes:

  johndament: Report not discussed on list, responded to an email from Sept
  2017 to indicate it was posted by a mentor.  Lots of development activity,
  not much developer discussion.  Seems like they have an unused user list as
  well.

--------------------

Gobblin

Gobblin is a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems.

Gobblin has been incubating since 2017-02-23.

Three most important issues to address in the move towards graduation:

  1. Make frequent releases

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?

* Gobblin community has continued to grow and engage more (on mailing lists
  and Gitter IRC).
* 51% of commits have been from non-committer contributors.
* Email stats since last report:
  user@gobblin.incubator.apache.org : 47 dev@gobblin.incubator.apache.org :
  694
* There have been 121 Commits since last report:
    git log --format='%ci' | grep -cE '(2018-0(1|2|3|4))'
* 62 ie. 51% of those commits were by non-committers:
   git log --format='%ae %ci' | grep -E '(2018-0(1|2|3|4))' | cut -d ' ' -f 1
   | sort | uniq -c | sort -n
* Recurring video conference based meetup has been happening every month with
  healthy attendance.
* Gobblin was presented and well received in various meetups / conferences
  around the world (independently by Apache community members) eg. Strata etc.

How has the project developed since the last report?

* Various new connectors for integration with more systems, and several
  enhancements / feature development.
* Continued development of Gobblin-as-a-Service (PaaS for Gobblin as well as
  non-Gobblin systems). More engagement of community on this front.
* Enhancements to website, and packaging / distribution of Gobblin.
* Release v0.12.0 is being voted on right now.

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:

  v0.12.0 is being voted on right now.

When were the last committers or PPMC members elected?

  Joel Baranick in December, 2017.
  (A few more contributors in the community are ready to be elected.)

Signed-off-by:

  [X](gobblin) Jean-Baptiste Onofré
     Comments:
  [X](gobblin) Olivier Lamy
     Comments:
  [X](gobblin) Jim Jagielski
     Comments: release process being better defined
   the 0.12 RC efforts. NOTICE requirements better understood.

--------------------

HAWQ

HAWQ is an advanced enterprise SQL on Hadoop analytic engine built around a
robust and high-performance massively-parallel processing (MPP) SQL engine
evolved from Greenplum Database.

HAWQ has been incubating since 2015-09-04.

Three most important issues to address in the move towards graduation:

  1. Continue to improve the project's release cadence. To this end we plan on
  expanding automation services to support increased developer participation.
  (HAWQ-127)


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

     Nothing urgent at this time.

How has the community developed since the last report?

1. Conference Talks :

 * HAWQ on Microsoft Azure Cloud. Microsoft Incubator Talk (Speaker: Lei
   Chang, Mar 21, 2018)


2. Two committer candidates passed the voting process:

   1) Shubham SHARMA 2) Lav JAIN


How has the project developed since the last report?


1. HAWQ 2.3 released. It includes the following features.

  1) New Feature: HAWQ Core supports plugable external storage framework. 2)
  New Feature: HAWQ Ranger supports RPS HA. 3) New Feature: HAWQ Ranger
  supports Kerberos authentication. 4) New Feature: HAWQ Core supports HDFS
  TDE (Transparent Data Encryption) through libHdfs3. 5) Licenses: Fix PXF
  license files located in PXF jar files. 6) Licenses: Check Apache HAWQ
  mandatory libraries to match LC20, LC30 license criteria. 7) Build: Release
  build project 8) Bug fixes.

Project page link:
https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.3.0.0-incubating+Release

2. HAWQ 2.4 release plan was proposed.

  1) New Feature: Pluggable Vectorized Execution Engine on HAWQ. 2) New
  Feature: Support Runtime Filter for HAWQ local hash join. 3) New Feature:
  Support accessing Hive table data by the new Pluggable Storage Framework. 4)
  Bug fixes.

Project page link:
https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.4.0.0-incubating+Release


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-03-12, Apache HAWQ 2.3.0.0

When were the last committers or PPMC members elected?

   1) Lav Jain: April 5, 2018 2) Shubham Sharma: April 5, 2018


Signed-off-by:

  [X](hawq) Alan Gates
     Comments:
  [ ](hawq) Justin Erenkrantz
     Comments:
  [ ](hawq) Thejas Nair
     Comments:
  [X](hawq) Roman Shaposhnik
     Comments:

--------------------

Hivemall

Hivemall is a library for machine learning implemented as Hive
UDFs/UDAFs/UDTFs.

Hivemall has been incubating since 2016-09-13.

Three most important issues to address in the move towards graduation:

1. Create the first Apache release
2. Community growth (committers and users)
3. Documentation improvements

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 * Markus Weimer resigned from our Project mentor as he sent a message to IPMC
   private list on March 1.
 * We need to recruit active Mentor(s)
    - Failed March2018 podling report due to missing mentor sign-off

How has the community developed since the last report?

 * Github watchers/stars are gradually increasing:
    131 stars as of April 3 (was 108 on Dec 6)
 * Twitter account @ApacheHivemall followers are gradually increasing:
    123 followers as of April 3 (was 101 on Dec 6)

How has the project developed since the last report?

 * Released the first Apache release (v0.5.0) on March 5.
https://lists.apache.org/thread.html/18e6355   dd06ff065004516eec6ff861777b4ad526714b61667b4904b@%3Cannounce.apache.org%3E

 Since the last report, we have
   * In the last 4 months, we opened 22 JIRA issues and closed 15 JIRA issues
     as seen in https://goo.gl/QFQEF5 (as of April 3) Created   Resolved Dec  
     2017    3           7 Jan   2018    4           3 Feb   2018    5        
     1 March 2018    10          4
   * Created 14 Pull Requests and closed/merged 13 Pull Requests between Dec
     01 and April 01.
https://github.com/apa     che/incubator-hivemall/pulls?q=is%3Apr%20created%3A2017-12-01..2018-04-01
https://github.com/ap     ache/incubator-hivemall/pulls?q=is%3Apr%20closed%3A2017-12-01..2018-04-01

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:

  March 5, 2018.

When were the last committers or PPMC members elected?

 - Elected Jerome Banks as a committer on April 2.
https://lists.apache.org/thread.html/98b28689dcf   fbf3a51a1ff80d9c86be96b46bbb3829bda334a722d89@%3Cdev.hivemall.apache.org%3E

Signed-off-by:

 [ ](hivemall) Reynold Xin
     Comments:
 [ ](hivemall) Xiangrui Meng
     Comments:
 [X](hivemall) Daniel Dai
     Comments:

IPMC/Shepherd notes:

  johndament: The comments with the new committer election are interesting. 
  Don't forget to go through IP Clearance if you are importing an external
  code base.

--------------------

Livy

Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.

Livy has been incubating since 2017-06-05.

Three most important issues to address in the move towards graduation:

  1. Grow the community and continue to involve more users and contributors
  2. Grow more committers to maintain the project
  3. Solidify our release cadence

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

N/A

How has the community developed since the last report?

Activity on the dev and user mailing lists as well as the rate of reported
JIRA issues has stayed steady.

How has the project developed since the last report?

The master branch has been updated to support Spark 2.3 in our next release.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2018-02-05

When were the last committers or PPMC members elected?

  2017-09-18

Signed-off-by:

  [ ](livy) Bikas Saha
     Comments:
  [ ](livy) Brock Noland
     Comments:
  [x](livy) Luciano Resende
     Comments:
  [X](livy) Jean-Baptiste Onofre
     Comments:

-------------------

Milagro

Distributed Cryptography; M-Pin protocol for Identity and Trust

Milagro has been incubating since 2015-12-21.

Three most important issues to address in the move towards graduation:

  1. Sort out infrastructure issues
  2. Enable NTT to handle operational tasks and project management
  3. Build the community

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

There is an ongoing vote for retirement of the Project, votes so far are 6
against and 1 neutral. There is an expressed concern that the development of
the project is happening away from the Apache. This was addressed by the main
contributors (MIRACL and NTT), they pointed out the reason for that were
infrastrucure and procedural issues. They will update the Apache repos and
keep the development there once those issues are resolved.

How has the community developed since the last report?

There were no new commiters added to the project since the last report.

How has the project developed since the last report?

There is an ongoing discussion around dealing with infrastructure issues
obstructing the project development. NTT suggested that they take responsibity
for operational tasks and management of the project.


How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [x] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  n/a

When were the last committers or PPMC members elected?

  n/a

Signed-off-by:

  [ ](milagro) Sterling Hughes
     Comments:

  [ ](milagro) Jan Willem Janssen
     Comments:

  [X](milagro) Nick Kew
     Comments: Retirement vote got a crop of NOs, though
   some of those may have misunderstood its purpose.  I'm proposing those who
   support continuation make concrete progress in time to report (on time) in
   May.  Failing that, I will support retirement.

IPMC/Shepherd notes:

  johndament: In order to survive, the podling needs to move development
  activities to Apache.  Continuing to develop under Miracl's repositories
  means it is not an Apache project.

--------------------

MXNet

A Flexible and Efficient Library for Deep Learning

MXNet has been incubating since 2017-01-23.

Three most important issues to address in the move towards graduation:

1. Establish a predictable release process consistent with Apache Way --
   ONGOING.
2. Grow the community -- ONGOING.
3. Bring website up to Apache standard -- ONGOING
4. Identify remaining ICLAs or SGAs that need signing -- ONGOING

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) Various Slack channels, dev@ mailing lists, and user discussion forums
(http://discuss.mxnet.io) are being used actively. The contributors have been
working on having all discussions on the public dev@ mailing list as much as
possible. This is an ongoing improvement process where the focus will be to
reduce the scope of private discussions to only a few individuals before it is
put on the public dev@ mailing list so that the Apache MXNet community gets a
fair chance in influencing the final outcome/decision of the discussion.

 b) O'Reilly published a series of blogs about MXNet:
https://www.oreilly.com/ideas/anomaly-detection-with-apache-mxnet
https://www.oreilly.com/ideas/logo-detection-using-apache-mxnet
https://www.oreilly.com/ideas/generative-model-using-apache-mxnet
https://www.oreilly.com/ideas/build-a-recurrent-neural-network-using-apache-mxnet

c) A new blog post published on 5-Feb about MXNet Model Server for Apache
MXNet introduces ONNX support and Amazon CloudWatch integration
https://aws.amazon.com/blogs/machine-learning/model-server-for-apache-mxnet-introduces-onnx-support-and-amazon-cloudwatch-integration/

d) A new blog post published on 13-Mar about MXNet - Deploy Gluon Models to
AWS DeepLens using a simple Python API
https://aws.amazon.com/blogs/machine-learning/deploy-gluon-models-to-aws-deeplens-using-a-simple-python-api/

e) Borealis AI (AI lab of Royal Bank of Canada) published a new blog post on
Feb about the comparison between PyTorch and MXNet – Standardizing a machine
learning framework for applied research – PyTorch vs MXNet
http://www.borealisai.com/2018/02/16/standardizing-a-machine-learning-framework-for-applied-research/

f) Microsoft AI research published a new blog post on Mar about the
performance comparison between multiple frameworks including MXNet – Comparing
deep learning frameworks: A Rosetta stone approach
https://blogs.technet.microsoft.com/machinelearning/2018/03/14/comparing-deep-learning-frameworks-a-rosetta-stone-approach/

g) Beeva Labs published a new blog post on Feb about MXNet – Accelerating the
training of deep neural networks with MXNet on AWS P3 instances
https://www.bbva.com/en/accelerate-training-deep-neural-networks-mxnet-aws-p3-instances/

h) Webinars and talks on Apache MXNet on the social media platform:
https://www.youtube.com/watch?v=DSNvm29kIAo
https://www.youtube.com/watch?v=kINQpQiee7g
https://www.youtube.com/watch?v=kWgCbjtsAAM
https://www.youtube.com/watch?v=YjDTL_Kjfww

i) Thomas Delteil spoke at Meetup in Vancouver -
https://www.meetup.com/LearnDataScience/events/248473200/?rv=ea1&_xtd=gatlbWFpbF9jbGlja9oAJDA0ODlhZGJjLWQ0YzYtNDJmOC04MDFiLTZiMWU1OWEwOWEwYw
- and talked about Convolutional Neural Networks for NLP

j) A public meeting is planned for April 24th in Seattle -
https://cwiki.apache.org/confluence/display/MXNET/Seattle

k) MXNet 1.2 release is in preparation and release notes are being reviewed at
https://cwiki.apache.org/confluence/display/MXNET/%5BWIP%5D+Apache+MXNet+%28incubating%29+1.2.0+Release+Notes

l) Community voted and adopted Jira for issue management -
https://issues.apache.org/jira/projects/MXNET/issues/MXNET-267?filter=allopenissues

m) Established MXNet youtube channel -
https://www.youtube.com/channel/UCQua2ZAkbr_Shsgfk1LCy6A. Please subscribe!

n) MXNet 1.1 was released on 19-Feb, 2018 with extensive support and help from
various community members and timely guidance from the Apache MXNet Mentors.

How has the project developed since the last report?

a. The community released MXNet 1.1 that makes MXNet more stable and
production ready: https://blogs.apache.org/mxnet/entry/1-1-0-release-makes

b. From a statistics perspective, based on the Github insights, found here:
https://github.com/apache/incubator-mxnet/pulse/monthly, in Mar 2018, 60
authors pushed 164 commits to master, with updates to 624 files including
23.1K additions and 5.6K deletions. Historically, in Dec 2017, 51 authors
pushed 115 commits to master, with updates to 489 files including 13K
additions and 9K deletions. Historically, in Sep 2017, 62 authors pushed 171
commits to master, with updates to 467 files including 26K additions and 7K
deletions. We are working on finding more contributors to the project.

c. Documentation- Architecture guides, How To's, Tutorials, and APIs continue
to be improved.

d. More advanced features (e.g. ONNX support, mixed precission modeling, Scala
inference API, MKL-DNN integratino etc) and bug-fixes requested by the user
community continue to be added.

How would you assess the podling's maturity?

 Podling is still being established in Apache - hence maturity == Low.


 [ ] Initial setup
 [ ] Working towards first release
 [X] Community building
 [ ] Nearing graduation
 [ ] Other

Date of last release: (latest to oldest releases) A major release Apache
MXNet-incubating 1.1.0 was released on 19-Feb, 2018.
https://github.com/apache/incubator-mxnet/releases/tag/1.1.0

When were the last committers or PPMC members elected?

Jan 18 2018 - Jun Wu and Marco de Abreu elected as committer and PPMC member



Signed-off-by:

  [X](mxnet) Sebastian Schelter
     Comments:
  [ ](mxnet) Suneel Marthi
     Comments:
  [X](mxnet) Henri Yandell
     Comments: I have noted on list that the comment on
   reducing private conversation needs to go much further. The sentiment in
   item (a) does not reach Apache's minimum bar and 'fair chance' is
   insulting.
  [ ](mxnet) Markus Weimer
     Comments:

--------------------

Nemo

Nemo is a data processing system to flexibly control the runtime behaviors of
a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

Three most important issues to address in the move towards graduation:

  1. Grow the community
  2. Create a first Apache release
  3. Donate code to ASF

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?

  * Committers actively involved in mailing lists
  * Committers actively started to send PRs and do code reviews
  * Two committers volunteered for GSoC mentors

How has the project developed since the last report?

  * SonarCloud integrated
  * Community standards and documentation added
  * Scheduler improved by adding a new scheduling policy and making it
    reactive
  * Operator pipelining implemented
  * Experiments performed to demonstrate the benefits of Nemo
  * Blogs posted

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [x] Initial setup
  [x] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  None yet.

When were the last committers or PPMC members elected?

  None yet.

Signed-off-by:

  [X](nemo) Davor Bonaci
     Comments: The project is very active, moving quickly,
   and doing very well.
  [X](nemo) Hyunsik Choi
     Comments:
  [X](nemo) Byung-Gon Chun
     Comments:
  [X](nemo) Jean-Baptiste Onofre
     Comments:
  [ ](nemo) Markus Weimer
     Comments:
  [ ](nemo) Reynold Xin
     Comments:

--------------------

NetBeans

NetBeans is a development environment, tooling platform and application
framework.

NetBeans has been incubating since 2016-10-01.

Three most important issues to address in the move towards graduation:

  1. Granting and integration of 2nd donation (mainly Java EE, JavaScript,
  PHP, Groovy) -- is being wrapped up at Oracle.
  2. Granting and integration of 3rd donation, consisting of tutorials,
  related images, and other documentation for populating netbeans.apache.org.
  3. Rerouting/switching from netbeans.org to netbeans.apache.org, plus new
  home for plugins.netbeans.org.

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?

 - NetCAT (NetBeans Community Acceptance Testing) program has started up,
   preparatory to final release of 9.0.
 - Apache virtual VM has been set up (netbeans-vm.apache.org) and one tool,
   used for NetCAT, is already there: http://netbeans-vm.apache.org/synergy
 - New Apache NetBeans logo has been voted on and accepted.
 - Ongoing discussions re redesign of splash screen.
 - Apache NetBeans Day as a class of event has been approved by Apache
   trademarks: https://netbeans.apache.org/community/events.html
 - First official Apache NetBeans Day accepted via lazy consensus to be held
   April 27, in London, at the University of Greenwich:
https://lists.apache.org/thread.html/328f564ac75   3165b39e7d96e67c929f7996a935ef75437c6c8e239fc@%3Cdev.netbeans.apache.org%3E
 - Currently 557 on Apache NetBeans users mailing list and 406 on Apache
   NetBeans dev mailing list.

How has the project developed since the last report?

 - Apache NetBeans (incubating) 9.0 Beta has been released (02/22/18)
 - Support for running on JDK 8, 9, 10 added, with Java editor support for new
   JDK 10 'var' type (JEP 286: Local-Variable Type Inference).
 - netbeans.apache.org is up and running.
 - Legal issue settled: Apache does not require and does not consider helpful
   list of 3rd party deps in grant:
   https://issues.apache.org/jira/browse/LEGAL-374

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2018-02-22 Apache NetBeans (incubating) 9.0 Beta

When were the last committers or PPMC members elected?

   * PPMC member Antonio Vieiro elected on Feb 18, 2018
   * PPMC member John McDonnell elected on Feb 18, 2018

Signed-off-by:

  [ ](netbeans) Ate Douma
     Comments:
  [ ](netbeans) Bertrand Delacretaz
     Comments:
  [ ](netbeans) Daniel Gruno
     Comments:
  [X](netbeans) Mark Struberg
     Comments: There is really lots of activity in
   the project

IPMC/Shepherd notes:

  johndament: Great progress by the podling.

--------------------

ODF Toolkit

Java modules that allow programmatic creation, scanning and manipulation of
OpenDocument Format (ISO/IEC 26300 == ODF) documents

ODF Toolkit has been incubating since 2011-08-01.

Three most important issues to address in the move towards graduation:

  1. Fulfil the 1.0 version - (collaboration scheduled for the end of March)
  2. Attract more developers
  3. Have frequent releases

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?
        Several bug reports but no new committers.

How has the project developed since the last report?
    Svante Schubert sponsorship by German government's prototypefund.org is
    about to end, the new collaboration feature for the ODF Toolkit not yet on
    GitHub.


Date of the last release:

  2017-04-10

When were the last committers or PMC members elected?

  2017-08-02

Signed-off-by:

  [ ](odftoolkit) Nick Burch
     Comments:
  [ ](odftoolkit) Yegor Kozlov
     Comments:
  [X](odftoolkit) Tom Barber
     Comments:
       Slow going as ever, but I can't fault the effort put in by Svante. I
       also have some interns hopefully looking at the website migration from
       CMS in the near future.

IPMC/Shepherd notes:

  Drew Farris (shepherd): Little overall project activity, but questions are
  being answered on the user list. One mentor active on the mailing lists

--------------------

PLC4X

PLC4X is a set of libraries for communicating with industrial programmable
logic controllers (PLCs) using a variety of protocols but with a shared API.

Most important issues to address while moving towards graduation:

Building the community: The PPMC and committer group has a large percentage of
codecentric employees, we have been recruiting people from other companies,
but will have to continue these efforts for establishing a healthy Apache
community. Onboarding of new committers: With PLC4X several people on the team
are not very familiar with the Apache Way. We have started and will continue
our efforts on this onboarding. Make our first release

Any Issues the Incubator PMC or ASF Board might wish/need to be aware of:

In contrast to previous reports some of the concerns regarding availability
and usability of specifications have been resolved. Especially for using the
Modbus and the OPC-UA specifications Christofer was able to get official
permissions from the corresponding foundations to use the specifications.
These permission Emails have been filed in the private list for documentation.

One of the external foundations (Profinet) doesn’t have a free membership. In
general, the CEO of the European branch of the Profinet Foundation has
signaled that it should be possible for the ASF to become a member and have an
outside company pay the membership fees, but we have to discuss the details
(With them as well as the ASF).

How has the community developed since the last report?

Christofer has invested most of his time in March spreading the word about
PLC4X. A first POC has been created for a company which is currently going
into production An article about Apache Edgent and Apache PLC4X has been
published as a cover-story in the German JavaSPEKTRUM magazines Industrial IoT
special edition (https://www.sigs-datacom.de/digital/javaspektrum/). One PLC4X
talk has been accepted to the Apache EU Roadshow 2018 in Berlin and one will
be at the Silpion Techcamp in Hamburg (https://techcamp.hamburg/) in the first
April week.

The dev-list subscriptions has gone up by one from February, we are hoping to
increase the number in the next few weeks (However quite some emails come in
from un-registered users that have to pass moderation).

We now have a Twitter account: https://twitter.com/ApachePlc4x as another
channel of communicating interesting PLC4X facts.

How has the project developed since the last report?

We have been working hard on making better use of the ASF build
infrastructure. Especially regarding setting up our project VM at
plc4x-vm.apache.org this effort will be continued. After receiving the
permission to use and implement the Modbus protocol, the Driver skeletons have
been setup, but no real implementation of the protocol itself has been done
yet. We are still hoping for volunteers to step up as interest in implementing
the Modbus protocol has been explicitly mentioned by community memebers. The
work on the RawSocket Netty transport which is a requirement to implement
protocols that are IP based, but are not TCP or UDP has continued and we are
currently working on some of the quirks on Linux based operating-systems. We
added Netty support for IO over serial ports and will be using this in the
Beckhoff module as a first protocol. We are still working on the S7 Protocol
fragmentation and hope to be able to finish this in April. Also we discussed
on the list about how the others would think of initiating a first release of
PLC4X.

How does the podling rate their own maturity?

We have a mix of new participants and experienced Apache people involved. So
far, the new participants have shown great willingness and success in adopting
the Apache Way. However, we still need to continue:
the on-boarding increasing the diversity of the team Also, will we need to
decide and establish all the processes involved in releasing software at
Apache



Signed-off-by:

  [X](plc4x) Greg Trasuk
     Comments:
  [X](plc4x) Justin Mclean
     Comments:
  [x](plc4x) Luciano Resende
     Comments:
  [X](plc4x) Stefan Bodewig
     Comments:

IPMC/Shepherd notes:

  Drew Farris (shepherd): Three mentors active on the mailing list. Active
  project.

--------------------

Pony Mail

Pony Mail is a mail-archiving, archive viewing, and interaction service, that
can be integrated with many email platforms.

Pony Mail has been incubating since 2016-05-27.

Three most important issues to address in the move towards graduation:

  1. Grow participation in community
  2. Get releases out properly
  3. Evangelize

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

None that I can think of.

How has the community developed since the last report?

There has been external interest in the project, however this has not yet
formed into a formal relationship.

How has the project developed since the last report?

A release, 0.10, was voted on and approved. Due to time constraints, the
release has not been fully completed yet.


How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [x] Initial setup
  [x] Working towards first release
  [x] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2018-04-04-ish (WIP!)

When were the last committers or PPMC members elected?

Sebastian Bazley, April 2017

Signed-off-by:

  [ ](ponymail) Andrew Bayer
     Comments:
  [X](ponymail) John D. Ament
     Comments: Report not discussed on list,
   extremely low volume and continues to look like a one person project.

--------------------

Quickstep

Quickstep is a high-performance database engine.

Quickstep has been incubating since 2016-03-29.

Three most important issues to address in the move towards graduation:

  1. Adoption of the Quickstep technology.
  2. Grow the Quickstep developer community.
  3. Work towards a second release.

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 paper that describes the Quickstep system was accepted in a premier database
conference Very Large Databases (VLDB). Link to the paper:
http://www.vldb.org/pvldb/vol11/p663-patel.pdf This paper should help the
system and the community to increase its reach further. We are already getting
emails from readers who are finding interest in the system. We are encouraging
the readers to be a part of the community.

We have submitted a keynote proposal ApacheCon. If accepted, the
paper/presentation would help to increase the awareness of Quickstep project
in the Apache community.


How has the project developed since the last report?

We have continued development of the code base. Apart from the routine bug
fixes, there are ongoing efforts for three main development directions
(respective JIRA issues have been opened):
1. Enhancing the type system used by Quickstep
2. Supporting concurrent queries in the system
3. Developing a distributed version of Quickstep

We are planning another release before summer.


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-03-25

When were the last committers or PPMC members elected?

2017-10-03 Robert Claus (committer)

We have seen contributions from some new members (Yuanchen Li, Dylan Bacon and
Yusong Yang). We will soon initiate the process for them to be committers.


Signed-off-by:

  [x](quickstep) Julian Hyde
     Comments: Development remains fairly active but
   the podling's ability to build community outside its core community is a
   major concern.
  [X](quickstep) Roman Shaposhnik
     Comments: big +1 to Julian's comment above.
   This is shaping up to be a vibrant, but a pretty small community. Another
   concern is cadence of releases. A year between releases in a podling is
   concerning.

--------------------

Rya

Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
supports SPARQL queries. Rya is a scalable RDF data management system built on
top of Accumulo. Rya uses novel storage methods, indexing schemes, and query
processing techniques that scale to billions of triples across multiple nodes.
Rya provides fast and easy access to the data through SPARQL, a conventional
query mechanism for RDF data.

Rya has been incubating since 2015-09-18.

Three most important issues to address in the move towards graduation:

  1. Increase diversity of committers

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?

 * Apache Rya 3.2.12 (incubating) released
 * More people expressed interest in contributing to Rya
 * More discussions about graduation

How has the project developed since the last report?
 * Apache Rya 3.2.12 (incubating) released
 * Improved documentation for deploying Rya PCJ Updater
 * Created a Rya Shell for MongoDB
 * Integrated RyaStreams with the Rya Shell
 * Added PCJ indexer support for MongoDB backend
 * Implemented a forward-chaining rules engine that runs as a batch process,
   operates on user-defined SPIN rules, and inserts derived information back
   in Rya
 * Added the ability to use the MongoDB aggregation pipeline to evaluate
   simple SPARQL expressions for MongoDB backend
 * Implemented single node Kafka streams incremental SPARQL processor
 * Plans to improve the SPARQL endpoint to improve standards compliance

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-03-04

When were the last committers or PPMC members elected?

 * PPMC member Caleb Meier elected on Jan 3rd, 2017

Signed-off-by:

  [x](rya) Josh Elser
     Comments: More heavy-handed-ly encouraging the podling
   to graduate
  [ ](rya) Edward J. Yoon
     Comments:
  [ ](rya) Venkatesh Seetharam
     Comments:
  [x](rya) Billie Rinaldi
     Comments:

--------------------

SensSoft

SensSoft is a software tool usability testing platform

SensSoft has been incubating since 2016-07-13.

Three most important issues to address in the move towards graduation:

  1. Extending release process to other parts of the SensSoft software stack.
  2. Grow the Apache SensSoft (Incubating) community.
  3. Complete the issues highlighted at the SensSoft Roadmap
  https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmap

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  No

How has the community developed since the last report?

  The community successfully delivered the first Incubating release for
  UserALE.js. No new community members have come onboard. Several members of
  the community VOTE'd on the UserALE.js 1.0.0 release candidate.

How has the project developed since the last report?

  Development continues at a sustainable level.

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
  [ ] Other:

Date of last release:

  2018-03-14

When were the last committers or PPMC members elected?

  Arthi Vezhavendan was added to PPMC and Committer base on 2017-01-24

Signed-off-by:

  [ ](senssoft) Paul Ramirez
     Comments:
  [X](senssoft) Lewis John McGibbney
     Comments:
  [ ](senssoft) Chris Mattmann
     Comments:

--------------------

ServiceComb

ServiceComb is a microservice framework that provides a set of tools and
components to make development and deployment of cloud applications easier.

ServiceComb has been incubating since 2017-11-22.

Three most important issues to address in the move towards graduation:

  1. Community building
  2. Project visibility
  3. Create release

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 finally get the first release out, service-center 1.0.0-m1,
    java-chassis 1.0.0-m1 and saga 0.1.0
  * The community hold a meetup in Beijing at March 30.

How has the project developed since the last report(March 2018)?
  * Java Chassis merged with 54 PRs by 10 contributors.
  * Service Center merged with 21 PRs by 5 contributors .
  * Saga resolved merged with 24 PRs by 7 contributors.
  * 117 mails sent by 27 people on the dev@ list

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [*] Initial setup
  [*] Working towards first release
  [*] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2018-04-03 Java Chassis 1.0.0-m1 2018-03-26 Service Center 1.0.0-m1
  2018-03-26 Saga 0.1.0

When were the last committers or PPMC members elected?
  2018-03-14 Added ningjiang,liubao,wujimin,asifdxtreme,littlecui as the
  Initial PPMC member


Signed-off-by:

  [X](servicecomb) Roman Shaposhnik
     Comments:
  [X](servicecomb) Jean-Baptiste Onofre
     Comments:
  [X](servicecomb) Timothy Chen
     Comments:

--------------------

SINGA

SINGA is a distributed deep learning platform.

SINGA has been incubating since 2015-03-17.

Three most important issues to address in the move towards graduation:

  1. Finish the existing jira tickets, including autograd (SINGA-342), tensor
  improvement (SINGA-341), backend for Keras (SINGA-340), ONNX (SINGA-333))
  2.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

We are working on the next release with the autograd feature. Another release
is scheduled with improved tensor and Keras backend.


How has the community developed since the last report?

There are 3 new contributors joined.


How has the project developed since the last report?

We fixed some bugs, updated the documentation and are now working on some
major/big updates (new features) including the new front-end APIs and the
autograd feature.


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:

  2017-06-29

When were the last committers or PPMC members elected?

2017-09-01

Signed-off-by:

  [ ](singa) Daniel Dai
     Comments:
  [X](singa) Alan Gates
     Comments: I don't see finishing the existing JIRA
   tickets as the key to graduation.  This podling has added new committers
   and done releases, but they continue to move at a very slow pace.  I am
   concerned about them having enough engagement to have 3 PMC members
   available to vote.  Seeing more consistent engagement is to me the criteria
   for graduation.
  [ ](singa) Ted Dunning
     Comments:
  [ ](singa) Thejas Nair
     Comments:

--------------------

Traffic Control

Traffic Control is a set of components that can be used to build, monitor,
configure, and provision a large scale content delivery network (CDN).

Traffic Control has been incubating since 2016-07-12.

Three most important issues to address in the move towards graduation:

1. A successful graduation vote by project community
2. A successful graduation vote by the IPMC
3. A successful acceptance of our graduation resolution by the apache board

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 (January 2018)?

Since January the Traffic Control community has worked on the following:
* Getting Traffic Control 2.1 released
* Getting Traffic Control 2.2 ready for release candidates
* Supporting new users with installing and configuring traffic control
* Tie up loose ends and prepare ourselves for graduation
* Planning a spring summit to be held April 2018 in Boston, MA

How has the project developed since the last report?

  Since the last report (January 2018), we have

  * Merged 199 Pull Requests with 673 commits from 27 unique contributors
  * Opened 217 Github issues
  * Closed 214 Github issues
  * 301 emails sent by 46 people on the dev@ list
  * 26 emails sent by 10 people on the users@ list

How would you assess the podling's maturity?

We have started the graduation process!  We voted on starting the graduation
process, chose a project chair, and have started the Project vote on the
graduation resolution.

  [ ] Initial setup
  [ ] Working towards first release (wip)
  [ ] Community building (wip)
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  Traffic Control 2.1 was released on January 22, 2017.

  Traffic Control 2.2 is currently on RC 3 and we hope to have 2.2 released by
  the end of April, 2018.


When were the last committers or PPMC members elected?

In October, Traffic Control added 1 new committer: Nir Sopher.

Signed-off-by:

  [X](trafficcontrol) Phil Sorber
     Comments: I think this project is in good
   shape, hopefully we see a graduation resolution in the IPMC for it soon.
  [X](trafficcontrol) Eric Covener
     Comments:
  [X](trafficcontrol) Leif Hedstrom
     Comments:


--------------------

Weex

Weex is a framework for building Mobile cross-platform high performance UI.

Weex has been incubating since 2016-11-30.

Three most important issues to address in the move towards graduation:

  1. Develop more non-Chinese contributors and committers, to bring diversity
  to the community.
  2. Replace Facebook's Yoga(Category X) dependency and release more while in
  Incubator.
  3. Improve the developer's activity in mailing list.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

The community is still learning the Apache Way,  we are making progress and
need more guidance from Mentors. The project has an ongoing problem with lack
of mentor engagement.


How has the community developed since the last report?

* WeexConf 2018 was held in Hangzhou, which brought a lot of new users and
  contributors who is intrested in the project, and Weex meetup in other
  cities will come soon.
* 278(91 new issues since the last report) issues have been reported on JIRA,
  and 145(52 since the last report) of them are resolved or closed.
* More non-Chinese developers are using Weex and contributing to the
  community, including developers from India, Russia, Singapore, etc. The
  first non-Chinese committer will come out soon.
* Our Github repo has growth in contributors 145(10 new since the last
  report), forks 1168(192 new), watchers 451(74 new) and stars 8730(1622 new)
* WebSite Trends Month Active, PV(542124), UV(91873), IP(76598), New Unique
  Visitor(47883) , Session(168065)

How has the project developed since the last report?

* Excluding merges, 11 authors have pushed 16 commits to master and 14 commits
  to all branches.
* Replacing Facebook's Yoga is done and will be released next month.

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-06-08

When were the last committers or PPMC members elected?

  None.

Signed-off-by:

  [ ](weex) Luke Han
     Comments:
  [X](weex) Willem Jiang
     Comments: The development looks good, but it is not
   normal that we don't have any release for 9 months.
  [ ](weex) Stephan Ewen
     Comments:
  [ ](weex) Raphael Bircher
     Comments:


-----------------------------------------
Attachment AF: Report from the Apache Isis Project  [Kevin Meyer]

## Description: 
Apache Isis is a framework for rapidly developing domain-driven applications
in Java.

## Issues:

There are no issues requiring board attention at this time.

## Activity:

We have made 2 release this quarter [1][2], addressing bug reports, 
performance improvements and adding a "replay" module to support
automated end-to-end testing of deployed applications.

Commits on the version 2 branch are continuing to remove deprecated 
and add updated functionality.

We're happy to add ASF links to our website. We are now 100% compliant[3].

The framework will be used to present a hands-on workshop at the 2018 NewCrafts
conference in Paris in May [4].
   
## Health report: 

We consider the project to be healthy with PMC members participating in
votes and both project members and users exchanging questions and answers 
on the mailing lists.
   
## PMC changes: 
   
 - Currently 14 PMC members. 
 - Johan Doornenbal was added to the PMC on Thu Apr 05 2018 
   
## Committer base changes: 
   
 - Currently 14 committers. 
 - Johan Doornenbal was added as a committer on Mon Mar 19 2018 
   
## Releases: 
   
 - 1.16.1 was released on Thu Feb 22 2018 
 - 1.16.2 was released on Mon Mar 05 2018 
   
## Mailing list activity: 
   
There is nothing significant in the mailing list activity.
   
## JIRA activity: 
   
 - 128 JIRA tickets created in the last 3 months 
 - 117 JIRA tickets closed/resolved in the last 3 months 
  
## References

[1] http://isis.apache.org/release-notes/release-notes.html#_release-notes_1.16.1
[2] http://isis.apache.org/release-notes/release-notes.html#_release-notes_1.16.2
[3] https://whimsy.apache.org/site/project/isis
[4] http://ncrafts.io/speaker/dkhaywood


-----------------------------------------
Attachment AG: Report from the Apache James Project  [Eric Charles]

## Description:
   - The Apache James Project delivers a rich set of open source modules and
     libraries, written in Java, related to Internet mail which build into an
     advanced enterprise mail server.

## Issues:
  - There are no issues requiring board attention at this time.

## Activity:
 - Last report has been rescheduled to March, so we only have 1 month
   activity.
 - Issues reported by users on memory usage, db indices... which is good thing
   as we get real end-user experience and can fix the reported issues.

## Health report:
 - Nothing special: JIRA implementation and user support on the mailing lists.
 - Mailing lists subscribers stable.

## PMC changes:

 - Currently 16 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Antoine Duprat on Fri Mar 11 2016

## Committer base changes:

 - Currently 37 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Raphael Ouazana at Thu Jul 07 2016

## Releases:

 - Last release was 3.0.1 on Fri Oct 20 2017

## Mailing list activity:

 - general@james.apache.org:
    - 174 subscribers (down -9 in the last 3 months):
    - 8 emails sent to list (0 in previous quarter)

 - mailet-api@james.apache.org:
    - 93 subscribers (up 0 in the last 3 months):
    - 9 emails sent to list (3 in previous quarter)

 - mime4j-dev@james.apache.org:
    - 80 subscribers (up 1 in the last 3 months):
    - 53 emails sent to list (1 in previous quarter)

 - server-dev@james.apache.org:
    - 184 subscribers (down -5 in the last 3 months):
    - 1348 emails sent to list (1136 in previous quarter)

 - server-user@james.apache.org:
    - 396 subscribers (down -7 in the last 3 months):
    - 22 emails sent to list (32 in previous quarter)

 - site-dev@james.apache.org:
    - 38 subscribers (down -1 in the last 3 months):
    - 3 emails sent to list (0 in previous quarter)


## JIRA activity:

 - 105 JIRA tickets created in the last 3 months
 - 119 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AH: Report from the Apache jclouds Project  [Andrea Turli]

==Description ==

A cloud agnostic library that enables developers to access a variety of cloud
providers using one API.

== Project Status ==

We have released jclouds 2.1.0, which support for OpenStack Keystone v3, a
long-standing issue that prevented jclouds from supporting modern OpenStack
versions. This has been eagerly awaited by the community and we have already
received (although off-list) some positive feedback from users. In this
release, several providers have reached a good level of maturity and have been
promoted out of "labs": Azure ARM, Packet and OpenStack neutron for compute,
and Google Cloud Storage and Backblaze B2 for storage.

Another discussion that is taking place is the need to move to Java 8 as our
officially supported Java version. This presented some compatibility issues
with the Guava library, which is widely used in the project, but we have
finally been able to come to an agreement on the upgrade plan. There has been
valuable feedback from the community regarding this topic and we now feel
comfortable in moving forward with the Java and Guava versions.

== Community ==

The project continues to receive contributions in the form of code and issues
from new developers, indicating that development is healthy and that users are
feeding back their problems and feature suggestions. We're also working to see
if an Aliyun user can contribute work done on a private branch back into the
open-source repository.

It has been great to see a contributor-initiated effort to move the project
forward to Java 8 and a newer Guava version. It is not an easy change given
our codebase and we are happy to see people is not afraid of trying to change
the project core, as one recurrent topic is that the learning curve to
understand the jclouds core is quite high.

Last committer: 2018-01-26 (Jim Spring)

Last PMC member: 2016-10-21 (Andrea Turli)

== Community Objectives ==

- Upgrade to Java 8 to support newer Guava version. This will have a
  significant impact on users but we hope it won't be an issue at this point.
- Continue to monitor our community for potential new committers and PMC
  members

== Releases ==

The last jclouds release, 2.1.0, took place on 2018-02-21.


-----------------------------------------
Attachment AI: Report from the Apache Jena Project  [Andy Seaborne]


## Description:

Jena is a framework for developing Semantic Web and Linked Data applications
in Java. It provides implementation of W3C standards for RDF and SPARQL.

## Issues:

There are no issues requiring board attention at this time.

## Activity:

Activity across mailing lists and github (the project mostly uses a
pull-request workflow) are normal. Pull request are getting reviewed, approved
and merged in a timely fashion.

The project is in the middle of a release with development with a significant
number of features. In addition, the project updated the build to support
running with a Java9 JDK.

## Health report:

The current activity levels are normal.

## PMC changes:

- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Adam Soroka on Mon Jun 06 2016

## Committer base changes:

- Currently 16 committers.
- Chris Tomlinson was added as a committer on Tue Jan 30 2018

## Releases:

- Last release was Jena 3.6.0 on Sun Dec 17 2017

## Mailing list activity:

Normal.

## JIRA activity:

- 57 JIRA tickets created in the last 3 months
- 55 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AJ: Report from the Apache JMeter Project  [Bruno Demion]

## Description:
 Pure Java application for load and functional testing.

## Issues:
 There are no issues requiring board attention at this time.

## Activity:
 - The project has released the version 4.0 with two security issues fixed
   (CVE-2018-1297 and CVE-2018-1287)
 - A topic for the GSoC has been proposed (COMDEV-284). A student made a
   project proposal.

## Health report:

 - The project has a good activity during last quarter with a new release and
   a good number of fixes/enhancements and external patches / PRs.
 - The project adopted the new checksum file Release Distribution Policy. The
   new release will provide only SHA-512 hashes (MD5 hashes has been removed).

## PMC changes:

 - Currently 8 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Antonio Gomes Rodrigues on Sat Jan 28 2017

## Committer base changes:

 - Currently 14 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Maxime Chassagneux at Wed Feb 15 2017

## Releases:

 - 4.0 final was released on Sat Feb 10 2018


-----------------------------------------
Attachment AK: Report from the Apache Johnzon Project  [Hendrik Saly]

## Description:
Apache Johnzon is an implementation of JSR-353 (JSON-P 1.0), JSR-374
(JSON-P 1.1) and JSR-367 (JSON-B 1.0) and a set of useful extension for this
specification like JAX-RS providers and websocket (JSR-356) integration.

## Issues:
There are no issues requiring board attention at this time

## Status:
We recently finished and released the implementation of JSR-374 and JSR-367.
Current focus is now to optimize the performance and stabilize the new
features.

## Releases:
- 1.1.6 was released on Sat Feb 17 2018
- 1.1.7 was released on Thu Mar 01 2018

## Committers and PMC membership:
The last committer we signed up was James W. Carman on July 03, 2017. The last
PMC member was Reinhard Sandtner, added to the PMC on August 30, 2016. We are
currently tracking one person and will likely ask him in the next weeks to
become a committer.

## Project activity:
Since the last report there was low to mid activity. We some some more
external contributions than usually via github.

We had 13 new Jira tickets and closed 15 tickets. On the mailinglist there a
no unanswered questions left. On the dev list we have 32 (+0) subscribers
currently and 12 msg sent per week. Since last report we saw mailing list
activity from a few new people.


-----------------------------------------
Attachment AL: Report from the Apache JSPWiki Project  [Juan Pablo Santos Rodríguez]

## Description: 
 - A feature-rich and extensible WikiWiki engine built around the standard
JEE components (Java, servlets, JSP).
   
## Issues: 
 - There are no issues requiring board attention at this time.
   
## Activity: 
 - Finally, we released 2.10.3 last February. It's been almost 2 years since
   2.10.2, so a lot of features/bugfixes/improvements came through.
 - 2.10.4 is to be expected on May with a few bugfixes.
    
## Health report: 
 
 - No questions unanswered on MLs, with at least 3 people from PMC showing 
   up there.
 
 - Current PMC Chair asked for replacement, not for anything in particular, 
   but because it has been a long time with the same PMC Chair. Nobody has 
   stepped up yet to take the role.
   
## PMC changes: 
   
 - Currently 11 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Dave Koelmeyer on Wed Apr 06 2016 
   
## Committer base changes: 
   
 - Currently 16 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Dave Koelmeyer at Wed Apr 06 2016 
   
## Releases: 
   
 - 2.10.3 was released on Tue Feb 13 2018 
   
## Mailing list activity: 
   
 - Normal quarter regarding ML activity, as shown by the statistics. 
   
 - dev@jspwiki.apache.org:  
    - 83 subscribers (up 0 in the last 3 months): 
    - 85 emails sent to list (38 in previous quarter) 
   
 - user@jspwiki.apache.org:  
    - 175 subscribers (up 0 in the last 3 months): 
    - 19 emails sent to list (59 in previous quarter) 
   
   
## JIRA activity: 
   
 - 4 JIRA tickets created in the last 3 months 
 - 5 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AM: Report from the Apache Kudu Project  [Todd Lipcon]

## Description: 

Apache Kudu is a distributed columnar storage engine built for the Apache
Hadoop ecosystem.
   
## Issues: 

No issues requiring the board's attention at this time.

## Activity: 

Since the last report, we've made one minor release (1.7.0).

The 1.7.0 release included some major improvements to our design for
re-replicating data after machine failure, support for DECIMAL types,
and various other smaller features and improvements based on user and
operator feedback from prior releases.


## Health report: 

- User mailing list growth continues at historical rates (8% this quarter).
  User list traffic is down again after a bump up in the previous quarter.
  Looking historically it seems like "messages sent" is a pretty noisy
  metric with big bursts of activity due to popular threads, followed by
  periods of quietness. We don't believe there is anything to be learned
  from this.

- Website traffic grew again slightly - sessions +2.7%, users +2.3%.

- Development activity grew substantially (measured by code review and
  JIRA traffic): reviews +34%, jira +119%. In the previous report we
  mentioned that it was down due to the holiday season so this is likely
  just the normal activity resuming in the new year.

- This quarter (Jan-Mar), we committed code authored by 22 distinct
  contributors (+5 since last quarter) of whom 8 (+5 since last quarter)
  were new to the project. 

## PMC changes: 
   
 - Currently 19 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Hao Hao on Wed Dec 13 2017 
   
## Committer base changes: 
   
 - Currently 19 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Hao Hao at Wed Dec 13 2017 
   
## Releases: 
   
 - 1.7.0 was released on Tue Mar 20 2018 
   
## JIRA activity: 
   
 - 150 JIRA tickets created in the last 3 months 
 - 96 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AN: Report from the Apache Lucene.Net Project  [Prescott Nasser]


-----------------------------------------
Attachment AO: Report from the Apache Lucy Project  [Peter Karman]

Per Apache Lucy convention, this report was approved by at least 3 PMC members prior to submission.

## Description:
  The Apache Lucy search engine library provides full-text search for
  dynamic programming languages.  The Apache Clownfish "symbiotic" object
  system pairs with "host" programming language environments and facilitates
  the development of high performance language extensions.

## Issues:
  There are no issues requiring board attention at this time.

## Activity:

 - There was one maintenance release (0.6.3) this quarter.
 - There were a few threads on the users@ list this quarter.

## Health report:

 - One maintenance release indicates we have active committers and enough PMC
   voters to create a release.
 - This report was approved by at least 3 PMC members on the lucy-private list.

## PMC changes:

 - Currently 12 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Timothy Wilkens on Sun Sep 14 2014

## Committer base changes:

 - Currently 14 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Tim Wilkens at Fri Sep 26 2014

## Releases:

 - Apache Lucy 0.6.3 and Apache Clownfish 0.6.3 were released on Mon Feb 19 2018

## Mailing list activity:

 - dev@lucy.apache.org:
    - 56 subscribers (down -3 in the last 3 months):
    - 29 emails sent to list (18 in previous quarter)

 - issues@lucy.apache.org:
    - 20 subscribers (down -1 in the last 3 months):
    - 17 emails sent to list (6 in previous quarter)

 - user@lucy.apache.org:
    - 87 subscribers (up 0 in the last 3 months):
    - 5 emails sent to list (15 in previous quarter)


## JIRA activity:

 - 4 JIRA tickets created in the last 3 months
 - 2 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AP: Report from the Apache MADlib Project  [Aaron Feng]

## Description:

- Apache MADlib is a scalable, big data, SQL-driven machine learning framework
  for data scientists.


## Issues:

- There are no issues requiring board attention at this time.


## Activity:

- Community is currently finalizing the 1.14 release which will be third
  release as an Apache TLP project.  We expect voting on release artifacts to
  commence during the week of 2018-April-16.

- A MADlib community call on the topic of the 1.14 release will be scheduled
  towards the end of April.

- There was a MADlib community call on the topic of the 1.13 release on
  2018-January-17.

- Community is working on defining the scope of the 1.15 release in JIRA and
  mailing lists.

- Community has been building and posting data science notebooks as a quick
  start guide to using MADlib.  There are currently more than 25 notebooks
  available at
  https://github.com/apache/madlib-site/tree/asf-site/community-artifacts


## Health report:

The community is relatively small but very engaged with robust mailing list
traffic, interest in doing frequent releases and new functionality being
developed by contributors.

The number of developers actively contributing to the code/documentation is
approximately 9 in the first quarter of the calendar year, which is about the
same as the last report.

We will constantly be on a lookout for new community members to be invited
either as committers or PMC.


## PMC changes:

- No changes in PMC, currently 13 PMC members.


## Committer base changes:

- Currently 13 committers.

- No new committers added in the last 3 months

- Last committer addition was Nandish Jayaram on 2016-09-08


## Releases:

- Next release: v1.14.0 planned for April 2018

- v1.13.0 released on 2017-12-22

- v1.12.0 released on 2017-08-29

- v1.11.0-incubating released on 2017-05-17


## Mailing list activity:

Mailing activity has remained relatively stable with 223 posts to dev@ and 7
posts to user@ during the month of 2018-March.


## JIRA Statistics:

- 13 JIRA tickets created in the last month

- 57 JIRA tickets resolved in the last month


-----------------------------------------
Attachment AQ: Report from the Apache Mahout Project  [Andrew Palumbo]

## Description:

Apache Mahout is an environment for quickly creating scalable performant
machine learning applications.



## Issues:



There are no issues requiring board attention at this time

## Activity:

Activity this quarter has been low. The team hit a larger blocker with a very
ambitious multi-artifact release; while upgrading scala and spark versions
shifting IP restrictions and life for an all volunteer team has made it
difficult to get over this hump.  As well the the team, spread very thin in
the past quarters, took on several other large tasks, leaving all overworked.

The team has been considering plan for a release to become Spark 2.x/scala
2_11.x compliant:

https://lists.apache.org/list.html?dev@mahout.apache.org:2018-3

## PMC changes:



- Currently 14 PMC members.

- No new PMC members added in the last 3 months

- Last PMC addition was Trevor Grant on Sat Feb 04 2017



## Committer base changes:



- Currently 28 committers.

- No new committers added in the last 3 months

- Last committer addition was Holden Karau at Wed Jul 12 2017



## Releases:



- Last release was 0.13.0 on Mon Apr 17 2017



## Mailing list activity:



Mailing list activity has slowed compared to relatively steadily over the last
quarters.  We have established a #mahout channel on https://the-asf.slack.com/
in hopes of reaching more people.



- dev@mahout.apache.org:

   - 902 subscribers (down -7 in the last 3 months):

   - 46 emails sent to list (49 in previous quarter)



- general@mahout.apache.org:

   - 10 subscribers (up 0 in the last 3 months):

   - 3 emails sent to list (0 in previous quarter)



- issues@mahout.apache.org:

   - 15 subscribers (up 0 in the last 3 months):

   - 22 emails sent to list (125 in previous quarter)



- user@mahout.apache.org:

   - 1750 subscribers (down -11 in the last 3 months):

   - 11 emails sent to list (19 in previous quarter)





## JIRA activity:



- 2 JIRA tickets created in the last 3 months

- 2 JIRA tickets closed/resolved in the last 3 months


## Talks and Publications

    “Apache Mahout.” Author: Andrew Musselman. In: Sakr S., Zomaya A. (eds)
     Encyclopedia of Big Data Technologies. Springer, Cham. February 26, 2018.
     https://link.springer.com/referenceworkentry/10.1007/978-3-319-63962-8_144-1

    “Matrix Math at Scale with Apache Mahout and Spark,” Andrew Musselman;
     workshop at ODSC East, Boston, May 2nd 2018.
     https://odsc.com/training/portfolio/matrix-math-scale-apache-mahout-spark

    The Magnificent Modular Mahout:An extensible library for distributed math
    and HPC.

    Trevor Grant, HPC, Big Data, and Data Science track, Fosdem 2018,
    Brussels.


-----------------------------------------
Attachment AR: Report from the Apache Maven Project  [Robert Scholte]

Maven Board Report - April 2018
---------------------------

Apache Maven is a widely-used project build tool, targeting mainly Java
development. Apache Maven promotes the use of dependencies via a standardized
coordinate system, binary plugins, and a standard build lifecycle.

* Issues

  <<There are no issues requiring board attention at this time.>>

* Activity

  With the new release train of Java we can expect a new release every six
  months. This means we need to test early with these versions and where
  possible make the libraries and plugins more robust so there's no release
  required with every new Java version. ASM seems to be a critical library
  which must be updated every time, but as long as the interface stays the
  same new releases are preferred but not required, since it is possible by
  developers to upgrade dependencies of plugins in their poms. Most activities
  were related to make our projects buildable with JDK 10. This is actually a
  risk: every minute we need to spend on making our projects run on a new Java
  version will reduce time to work on the improvements on Maven and its
  plugins. We have good ideas for Maven 4+5 and some are required to better
  support on building with these latest JDKs, but with the current resources
  it will be hard to do both.

  All our gitwip repositories have been migrated to gitbox. We are a bit
  disappointed about this process. We requested the migration a long time ago.
  When we received the message that the migration was planned it took a long
  time before it really happened, even when we asked for status updates. Our
  idea was to do the Maven release from the new gitbox repository, but after a
  while we had to decide to go for a release from gitwip because we had no
  idea when the migration would happen. Moreover, with this migration, all
  commit links in JIRA
  ("Fixed with ${SHA-1}") are broken, because they still point to
    git-wip-us.a.o instead of gitbox.a.o: having a redirection from the old
    canonical repo links to the new would be useful.

  We auto-closed all issues that were inactive for over 3 years. This should
  help us focus on the "real" issues. Only a small number of issues were
  reopened as requested by the reporter or other interested user, because they
  are still valid. The number of unresolved issues used to be between 2000 and
  2100, now it's between 1600 and 1700, see also https://s.apache.org/7tkk

* Health Report

* Community

  * PMC changes
  - Currently 24 PMC members.
  - No new PMC members added in the last 3 months
  - Last PMC addition was Guillaume Boué on Mon Aug 07 2017

  * Committers changes
  - Currently 56 committers.
  - No new committers added in the last 3 months
  - Last committer addition was Guillaume Boué at Thu Jul 07 2016

  * Mailing List activity

  - users@maven.apache.org:
    - 1634 subscribers (down -16 in the last 3 months):
    - 313 emails sent to list (238 in previous quarter)

  - dev@maven.apache.org:
    - 600 subscribers (down -4 in the last 3 months):
    - 883 emails sent to list (732 in previous quarter)

  - announce@maven.apache.org:
    - 663 subscribers (down -7 in the last 3 months):
    - 19 emails sent to list (8 in previous quarter)

  - issues@maven.apache.org:
    - 227 subscribers (up 0 in the last 3 months):
    - 4160 emails sent to list (1902 in previous quarter)

  * JIRA activity:
  - 459 JIRA tickets created in the last 3 months
  - 815 JIRA tickets closed/resolved in the last 3 months

* Releases

  Core
  - Maven 3.5.3 was released on Thu Mar 08 2018

  Plugins
  - Maven Checkstyle Plugin 3.0.0 was released on Sun Jan 07 2018
  - Maven PMD Plugin 3.9.0 was released on Mon Jan 29 2018
  - Maven SCM Publish Plugin 3.0.0 was released on Mon Jan 29 2018
  - Maven JDeps Plugin 3.1.1 was released on Wed Feb 28 2018
  - Maven Help Plugin 3.0.0 was released on Wed Mar 07 2018
  - Maven EAR Plugin 3.0.0 was released on Fri Mar 09 2018
  - Maven Surefire Plugin 2.21.0 was released on Tue Mar 06 2018
  - Maven Help Plugin 3.0.1 was released on Sat Mar 24 2018

  Other
  - Maven Fluido Skin 1.7 was released on Fri Jan 05 2018
  - Maven Dependency Analyzer 1.8 was released on Wed Jan 17 2018
  - Maven Plugin Tools 3.5.1 was released on Mon Jan 22 2018
  - ASF Parent POM 19 was released on Wed Jan 24 2018
  - Maven Parent POMs 31 was released on Mon Feb 05 2018
  - Maven Shared Utils 3.2.1 was released on Sat Feb 10 2018
  - Maven Resolver 1.1.1 was released on Mon Feb 19 2018
  - Maven Dependency Analyzer 1.9 was released on Wed Mar 28 2018


-----------------------------------------
Attachment AS: Report from the Apache Mesos Project  [Benjamin Hindman]

## Description:

- Apache Mesos abstracts CPU, memory, storage, and other compute resources
  away from machines (physical or virtual), enabling fault-tolerant and
  elastic distributed systems to easily be built and run effectively.

## Issues:

- There are no issues requiring board attention at this time.

## Activity:

- Release policy has been updated to reflect reality: quarterly as well as
  supporting 3 release branches for quarterly bug fix releases.

- 'This Month in Mesos' reports were posted to the mailing list for February
   and March. These were started to help users follow along with developments
   in the project, given there's a lot going on.

- The project continues to see new bug reports, bug fixes, features, reviews
  and releases. The mailing lists, slack and IRC channels are also very much
  active with healthy discussions. Multiple active working groups
  (containerization, performance, API, community).

## PMC changes:

- Currently 44 PMC members.
- New PMC members:
    - Chun-Hung Hsiao was added to the PMC on Sun Mar 18 2018
    - Zhitao Li was added to the PMC on Sun Mar 18 2018

## Committer base changes:

- Currently 44 committers.
- New commmitters:
    - Chun-Hung Hsiao was added as a committer on Thu Mar 08 2018
    - Zhitao Li was added as a committer on Mon Mar 12 2018

## Releases:

- 1.3.2 was released on Wed Jan 24 2018
- 1.5.0 was released on Wed Feb 07 2018

## JIRA activity:

- 344 JIRA tickets created in the last 3 months
- 246 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AT: Report from the Apache Metron Project  [Casey Stella]

## Description: 
Metron integrates a variety of open source big data technologies in order
to offer a centralized tool for security monitoring and analysis.  Metron
provides capabilities for log aggregation, full packet capture indexing,
storage, advanced behavioral analytics and data enrichment, while applying
the most current threat-intelligence information to security telemetry
within a single platform.
  
## Issues: 
There are no issues requiring board attention at this time

## Activity: 
 - No new PMC or committers.
   
## Health report: 
Project activity is broadly the same as prior months.

## PMC changes: 
   
 - Currently 27 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Justin Leet on Sun Dec 03 2017 
   
## Committer base changes: 
   
 - Currently 37 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Anand Subramanian at Mon Dec 25 2017 
   
## Releases: 
  
 - Last release was 0.4.2 on Fri Dec 22 2017 

## JIRA activity: 
   
 - 123 JIRA tickets created in the last 3 months 
 - 71 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AU: Report from the Apache MINA Project  [Jeff Maury]

## Description:
Apache MINA is a network application framework which helps users develop high
performance and high scalability network applications easily.

## Issues:
 After a long time due to lack of resources, MINA 2.0.17 was released.

## Activity:
 Although SSHD is still the main area among various MINA projets, the additon
 of a new committer to Core could lead to enhanced activity there.

## Health report:
 MINA 2.0.17 was long waited by MINA users. We expect better community support
 in Core with the recent committer addition. PMC has started discussions about
 moving FtpServer and Vysper to the Attic.

## PMC changes:

 - Currently 12 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Lyor Goldstein on Mon Feb 13 2017
- Jean-François Maury resigned from PMC chair and will be replaced by
  Guillaume Nodet

## Committer base changes:

 - Currently 27 committers.
 - Jonathan Valliere was added as a committer on Thu Feb 15 2018

## Releases:

 - Apache MINA 2.0.17 was released on Thu Mar 15 2018
 - Apache Mina SSHD 1.7.0 was released on Tue Jan 23 2018

## Mailing list activity:

 - users@mina.apache.org:
    - 497 subscribers (down -3 in the last 3 months):
    - 29 emails sent to list (8 in previous quarter)

 - dev@mina.apache.org:
    - 345 subscribers (down -4 in the last 3 months):
    - 473 emails sent to list (474 in previous quarter)

 - ftpserver-users@mina.apache.org:
    - 133 subscribers (up 0 in the last 3 months):
    - 7 emails sent to list (3 in previous quarter)


## JIRA activity:

 - 32 JIRA tickets created in the last 3 months
 - 26 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AV: Report from the Apache MyFaces Project  [Mike Kienenberger]

## Description:
The Apache MyFaces project is an umbrella project of the Apache Software
Foundation for projects relating to the JavaServer Faces
(JSF) technology.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity and health:
- Apache Myfaces Core is healthy, and the community is working on the new JSF
  2.3 specification features.

UI-Component Sets:
- Apache Tobago is healthy and active.
- Apache Trinidad is in maintenance mode.  Last developer commit was Sept
  2017.
- Myfaces Tomahawk is in maintenance mode. Last developer commit was May 2016.
  Last commit on behalf of a contributor was May 2016.

Add-ons and Extensions:
- Apache MyFaces Portlet Bridge is in maintenance mode.  Last developer commit
  was Jan 2014.  Last commit on behalf of a contributor was May 2015.
- Apache MyFaces CODI is in maintenance mode. CODI was replaced by Apache
  DeltaSpike so new development happens there.  Last commit March 2014.
- Apache MyFaces Orchestra is in maintenance mode.  New projects use CDI and
  DeltaSpike instead.  Last commit on behalf of a contributor was August 2016.
- Apache MyFaces ExtVal is in maintenance mode. Last commit June 2014.
- Apache MyFaces Commons is in maintenance mode.  Last commit August 2012.
- Apache MyFaces Ext-Scripting is in maintenance mode.  Last commit Sept 2017.
- Apache MyFaces Test is in maintenance mode (Used by Myfaces Core).  Last
  commit May 2017.

## Community changes:

- Currently 78 committers and 44 PMC members.
- Last committer addition was Eduardo Breijo at Thu Jun 29 2017
- Eduardo Breijo-Baullosa was added to the PMC on Mon Jan 29 2018

## Releases:

 - myfaces-core-2.3.0 was released on Mon Mar 05 2018
 - tobago-2.1.1 was released on Sun Jan 28 2018
 - tobago-4.1.0 was released on Sun Feb 11 2018

## JIRA activity:

 - 87 JIRA tickets created in the last 3 months
 - 94 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AW: Report from the Apache Mynewt Project  [Justin Mclean]

## Description: 
Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M, RISC-V and MIPS
architectures.
   
## Issues: 
None. A minor security issue was raised and resolved.
   
## Activity: 
- Release 1.3 completed on Dec 13, 2017
- Community work in splitting out major components into different repos e.g. 
repo for Bluetooth protocol stack (NimBLE), Newtron Flash File System (NFFS) 
etc.
- Community work in serval areas including working on upcoming 1.4 core 
release, discussions on how to bundle component repos, build tool (Newt) 
enhancements, additional transport protocol support, and sensor support
- Doxygen-based API generation for docs incorporated in the project 
documentation and receiving contributions from community
   
## Health report: 
- PMC and committers are active
- Users questions and contributor's pull requests are quickly dealt with
- Several new committer are currently being voted on
- talk and demos of Apache Mynewt BLE and LoRa at Open IoT Summit, Portland, 
Feb 2017
- participation in LoRa demo table at Mobile World Congress, Feb 2017
- Mynewy talk accepted for upcoming Apache Roadshow in Berlin
   
## PMC changes: 
   
 - Currently 19 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Aditi Hilbert on Wed Jun 21 2017 
   
## Committer base changes: 
   
- Currently 24 committers
- One new committer voted on and added since last report
- Miguel Azevedo on Sun Sep 17 2017
   
## Releases: 
- 1.3 was released on December 13th 2017
- planning on 1.4 release is currently underway 

## Mailing list activity: 
   
- Mailing list activity seeing several new users. 
- Mailing list exchanges are mostly around BLE, BLE mesh, Hardware Abstraction 
Layers, MCU ports, Lora, Newt tool enhancements to make build process easier, 
and new releases
- Mailing list activity up over previous period
- Slack channel activity up significantly and weekly/daily active users up 50% 
from last period
   
## JIRA activity: 
-  JIRAs activity down over previous period
- Issue tracking for each repo moved over to corresponding GitHub Issues after 
discussion on mailing list


-----------------------------------------
Attachment AX: Report from the Apache NiFi Project  [Joe Witt]

## Description:
 - Apache NiFi is an easy to use, powerful, and reliable system to process and
   distribute data.
 - Apache NiFi MiNiFi is an edge data collection agent built to seamlessly
   integrate with and leverage the command and control of NiFi. There are both
   Java and C++ implementations.
 - Apache NiFi Registry is a centralized registry for key configuration items
   including flow versions, assets, and extensions for Apache NiFi and Apache
   MiNiFi.
 - Apache NiFi Nar Maven Plugin is a release artifact used for supporting the
   NiFi classloader isolation model.
 - Apache NiFi Fluid Design System is a theme-able set of high quality UI
   components and utilities for use across the various Apache NiFi web
   applications in order to provide a more consistent user experience.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - Conducted another important feature bearing release of Apache NiFi 1.6.0.
   It includes things like application level resource isolation for things
   like Kerberos credentials and more, better integration to Apache HBase,
   InfluxDB, Druid, MongoDB and a ton of bug fixes and improvements.
 - The community voted to spawn a subproject called the Apache NiFi Fluid
   Design System as called out above. Infra has created the Git repo and code
   has started to land there.  Once this is fully up and running we'll be able
   to build these NiFi web components once and reuse them in NiFi, the NiFi
   Registry and any other web applications that are part of the Apache NiFi
   community.
 - Several members of the community are hosting a meetup for the Maryland, DC,
   Virginia area. It will have talks from large financial institution
   engineering leads using NiFi and NiFi community members.

## Health report:
 - Health of the community remains strong. Mailing list and JIRA activity is
   consistent. ASF Hipchat is serving as an on-ramp for new users to our
   mailing list and JIRA systems.
 - Added a new committer and have noted an uptick in community engagement from
   a developer/contributions/review engagement perspective which is really
   cool.

## PMC changes:

 - Currently 26 PMC members.
 - No new PMC members added in the last 3 months.
 - Last PMC member added Wed Dec 13 2017.

## Committer base changes:

 - Currently 39 committers.
 - New commmitters:
    - Mike Thomsen was added as a committer on Wed Mar 21 2018
 - Last committer added Wed Mar 21 2018.

## Releases:

 - Apache NiFi 1.6.0 was released Apr 8 2018.

## Mailing list activity:

 - Activity on the mailing lists remains high with a mixture of new users,
   contributors, and deeper more experienced users and contributors sparking
   discussion and questions and filing bugs or new features.

 - users@nifi.apache.org:
    - 614 subscribers (up 30 in the last 3 months):
    - 742 emails sent to list (753 in previous quarter)

 - dev@nifi.apache.org:
    - 405 subscribers (up 11 in the last 3 months):
    - 872 emails sent to list (636 in previous quarter)

 - issues@nifi.apache.org:
    - 48 subscribers (up 2 in the last 3 months):
    - 8301 emails sent to list (6307 in previous quarter)


## JIRA activity:

 - 391 JIRA tickets created in the last 3 months
 - 266 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment AY: Report from the Apache Nutch Project  [Sebastian Nagel]

Apache Nutch is a highly extensible and scalable open source web crawler
software project. Stemming from Apache Lucene®, the project has diversified
and now comprises two codebases, based respectively on Apache Hadoop®
data structures and Apache Gora for leveraging NoSQL databases.


ISSUES

There are no issues requiring board attention at this time.


RELEASES

Nutch 1.14 was released on Dec 22 2017.

The last release on the 2.x branch (2.3.1) dates to Jan 20 2016.


CURRENT ACTIVITY

We are working hard to make the Nutch 1.x branch stable after the upgrade
to the new MapReduce API (NUTCH-2375), a huge change over 200 files
which introduced several regressions.

The release of 2.4 is on the agenda.

We still hope to participate again in GSoC but have no student applications
yet.


JIRA ACTIVITY

 - 59 JIRA tickets created in the last 3 months
 - 34 JIRA tickets closed/resolved in the last 3 months


COMMUNITY

No new committers and PMC members in the last 3 months,
last PMC addition was Ralf Kotowski on Wed Jun 14 2017.

The traffic on the user mailing list is at a steady level:

 - dev@nutch.apache.org:
    - 525 subscribers (down -4 in the last 3 months):
    - 571 emails sent to list (872 in previous quarter)
      (mostly machine-generated emails from Jira, Jenkins, Wiki)

 - user@nutch.apache.org:
    - 1050 subscribers (down -10 in the last 3 months):
    - 189 emails sent to list (166 in previous quarter)


-----------------------------------------
Attachment AZ: Report from the Apache ODE Project  [Sathwik]

## Description:
   Apache ODE is a WS-BPEL implementation that supports web services
   orchestration using flexible process definitions.

## Issues:
   There are no issues requiring board attention at this time.

## Activity:

  - Successfully released ODE 1.3.8, comes with major upgrades.
  - Developer activity is low. Might continue to be low.
  - We plan to work towards strengthening the features available in the trunk
    branch.
  - Some new developers have shown interest. We did see some contributions on
    the trunk. Need more involvement in order to make them as committers.
    [http://markmail.org/message/5zkz7vt33urldv7e]

## Health report:
 - ODE is very mature and stable, however the interest in BPEL has decreased
   significantly. Thus ODE's development is currently pretty much in
   maintenance mode.

## PMC changes:
 - Currently 15 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Rafal Rusin on Wed Oct 01 2014

## Committer base changes:
 - Currently 26 committers.
 - No new changes to the committer base since last report.
 - Last committer was Sathwik on Dec 23 2012.

## Releases:
 - Last release was 1.3.8 on Fri Mar 23 2018

## Mailing list activity:
 - dev@ode.apache.org:
    - 147 subscribers (down -2 in the last 3 months):
    - 67 emails sent to list (86 in previous quarter)

 - user@ode.apache.org:
    - 212 subscribers (down -2 in the last 3 months):
    - 23 emails sent to list (21 in previous quarter)

## JIRA activity:
 - 2 JIRA tickets created in the last 3 months
 - 11 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment BB: Report from the Apache OpenJPA Project  [Mark Struberg]

## Description: 
 Apache OpenJPA is a persistent object management kernel for databases,
 relational as well as non-relational. For relational databases, OpenJPA is
 compliant to the Java Persistence Architecture (JPA) version 2.0.
 OpenJPA runs in stand-alone Java SE as well as  containers e.g Java EE,
 Tomcat, Spring or OSGi.
   
## Issues: 
 There are no issues requiring board attention at this time
   
## Activity: 
 Could be more. Much more. Otoh we got a few patches recently.
 Mainly smallish patches, but also some bigger ASM contribution
 and Java9/10/11 stuff.
 We are preparing to ship OpenJPA-2.4.3.
 And after that I hope to finally finish OpenJPA-3.0.0.
   
## Health report: 
 Maintenance going on. And patches get applied.
 Attention could be higher of course.
   
## PMC changes: 
   
 - Currently 16 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Jody Grassel on Tue Aug 15 2017 
   
## Committer base changes: 
   
 - Currently 33 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Will Dazey at Thu Aug 17 2017 
   
## Releases: 
   
 - Last release was 2.4.2 on Tue Jan 03 2017 
   
## Mailing list activity: 
   
 - users@openjpa.apache.org:  
    - 233 subscribers (down -2 in the last 3 months): 
    - 20 emails sent to list (10 in previous quarter) 
   
 - dev@openjpa.apache.org:  
    - 133 subscribers (down -4 in the last 3 months): 
    - 62 emails sent to list (31 in previous quarter) 
   
   
## JIRA activity: 
   
 - 8 JIRA tickets created in the last 3 months 
 - 2 JIRA tickets closed/resolved in the last 3 months 
   

-----------------------------------------
Attachment BC: Report from the Apache OpenMeetings Project  [Maxim Solodovnik]

## Description:
 - Openmeetings provides video conferencing, instant messaging,
white board, collaborative document editing and other groupware
tools using API functions of the Red5 Streaming Server for
Remoting and Streaming.

## Issues:
 - there are no issues requiring board attention at this time

## Activity:
 - 4.0.2 was released (two CVE were addressed)
   4.0.3 is almost ready working on performance improvements
   5.0.0 is being developed

## Health report:
 - We have no new members, I can see no good candidates right now
Will start discussion on private@ list

## PMC changes:

 - Currently 25 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Hemant Sabat on Sat Aug 05 2017

## Committer base changes:

 - Currently 27 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Hemant Sabat at Sat Aug 05 2017

## Releases:

 - 4.0.2 was released on Sat Feb 24 2018

## Mailing list activity:

 - Activity on mailing lists is more or less the same, I believe there will be
more mail traffic as soon as alpha for 5.0.0 will be available.


 - dev@openmeetings.apache.org:
    - 139 subscribers (down -2 in the last 3 months):
    - 241 emails sent to list (344 in previous quarter)

 - user@openmeetings.apache.org:
    - 349 subscribers (up 0 in the last 3 months):
    - 572 emails sent to list (886 in previous quarter)

 - user-espanol@openmeetings.apache.org:
    - 67 subscribers (up 1 in the last 3 months):
    - 12 emails sent to list (19 in previous quarter)

 - user-russian@openmeetings.apache.org:
    - 42 subscribers (up 2 in the last 3 months):
    - 36 emails sent to list (176 in previous quarter)


## JIRA activity:

 - 52 JIRA tickets created in the last 3 months
 - 51 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment BD: 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.

## STATUS

The activity within the project continues to be stable compared with the last
report. In the last quarter the main topics are the further development
towards release 4.2.0, infrastructure topics and activating volunteers. We
expect that we will continue on the taken route and keep our momentum.


## ISSUES FOR BOARD AWARENESS

There are no current topics to be concerned with.

## ISSUES

No topics

## RELEASES

The next major release will be 4.2.0 with a target to publish in 2018. In
opposite to the 4.1.x releases it will include new features and bigger
enhancements but of course also bugfixes.

## Complete Release History

2017-12-30 4.1.5 
2017-10-19 4.1.4 
2016-10-12 4.1.3

## PMC

There are 28 PMC members as of 2018-Apr-11. The recognition and invitation of
new PMC members remains on a stable level.

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. The recognition and invitation of
new committers is also on a stable level.

Last committer addition was on 2017-Jan-28 Kay Schenk (kschenk) Last committer
withdrawal was on 2017-Feb-04 Dennis E. Hamilton (orcmid)

## ACTIVITY

## Organization

No changes

## Development and Release Engineering

Currently the project major goal is the next major 4.2.0 release, ending the
plan from 2016. Dev builds are already built on routine bases. Testing on a
low level is ongoing, more detailed testing will be the next topic. Further
activities focus on the reactivation of the localization team. Documentation,
process and tools are undergoing a complete review. The current activity focus
on:

+ importing the latest work by translators into the OpenOffice code.
+ updating Pootle strings to match trunk (the first Pootle update in years).
+ give translators the possibility to test their translations with dedicated
  builds.
+ add new languages to the next major release if translators manage to
  complete their work in time.

Further activities are:

+ support of gstreamer 0.1.0 and 1.0
+ Migration of Windows 64 bit
+ MSVC 2015
+ Java 9 support
+ continued migration of code modules from dmake to gbuild.

## Downloads

As of 2018-Apr-10 we have more than 247,000,000 downloads and it is at a
consistent rate with ~80,000 downloads in average per day. Windows is the most
famous platform. Then macOS and Linux are following.

Downloads regarding the country over the last 3 months are spread like the
following
(source:
https://sourceforge.net/p rojects/openofficeorg.mirror/files/stats/map?dates=2018-01-17+to+2018-04-10):

14.2 % United States
13.5 % France
11.8 % Germany
 8.4 % Italy
 5.2 % Poland
 4.7 % Spain
 4.1 % United Kingdom
 4.0 % Russia 3,2 % Japan
 2.2 % Canada
 1.8 % India
26.9 % All other countries


## Websites & Infrastructure

In the last Quarter our provider SourceForge a data center migration and
critical technical difficulties. Our Software has been unavailable for several
days. As a reaction some PMC Members have concerns about our lack of Plan B.

The project is taking over one VM from Infra. So far the process is slow,
since we discussing with infra and our community the modernisation of the
software we use. From our site the process is constructive.

## Activity of mailing lists

The following table shows the list activity (monthly average):
(source:
 https://mail-archives.apache.org/mod_mbox/openoffice-<mailing-list-name>/)

                 2016 2017 2018-YTD
           dev@  323  253   177 
         users@  208  154   135 
          l10n@   18   19    39
            qa@   16    2     8 
     marketing@    4    2     5 
           api@    1    0     4
           doc@   13    1     1 
   recruitment@    3   11     7

      users-de@   89   55    46 
        dev-de@   13   17    12


## Fairs and events

OpenOffice, as usual, had a significant presence at FOSDEM, both with a few
talks at the Open Document Editors devroom and with a booth running for the
entire FOSDEM weekend. The AOO Project will work with the ASF organisation
more closely on FOSDEM 2019 in order to ensure that the needs of AOO and ASF
are met. We are looking into different options already.

## BRANDING

We had a long and constructive discussion with brands team on brands topic.
The details have already been reported in the brands report. We have currently
no updates to that report.


-----------------------------------------
Attachment BE: Report from the Apache ORC Project  [Owen O'Malley]

## Description:

- A high-performance columnar file format for Hadoop workloads.

## Issues:

- There are no issues requiring the board's attention.

## Activity: 

- We made two bug fix releases for the 1.4 branch and will make another soon.
 - We also need to finalize the ORC 1.5 release.
 - We decided to create a security list.
 - Expanded the development page on the website to help new committers.
 - Refactored the format specification on the website to make it easier
   to add the new ORCv2 specification as we work on it.
 - The Iceberg project https://github.com/Netflix/iceberg from Netflix added
   ORC support.
 - Presentations got accepted about ORC for Berlin Buzzwords and Dataworks
   Summit San Jose.
   
## Health report: 

- Discovered that our benchmarking code was using a GPL dependency and
   so moved the code to an external github site.
 - The activity level is increasing and drawing from an increasing number
   of contributors. We continue to track the contributions looking for new
   committers and PMC members.
   
## PMC changes: 
   
 - Currently 9 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Eugene Koifman on Tue Sep 05 2017 
   
## Committer base changes: 
   
 - Currently 38 committers. 
 - New commmitters: 
    - Gang Wu was added as a committer on Wed Mar 28 2018 
    - Xiening Dai was added as a committer on Fri Apr 06 2018 
   
## Releases: 
   
 - 1.4.2 was released on Mon Jan 22 2018 
 - 1.4.3 was released on Thu Feb 08 2018

## Mailing list activity: 

The traffic is up this quarter, but in line with expectactions.

 - dev@orc.apache.org:  
    - 55 subscribers (up 5 in the last 3 months)
    - 328 emails sent to list (261 in previous quarter) 
   
 - issues@orc.apache.org:  
    - 20 subscribers (up 0 in the last 3 months)
    - 409 emails sent to list (293 in previous quarter) 
   
 - user@orc.apache.org:  
    - 58 subscribers (up 2 in the last 3 months)
    - 36 emails sent to list (14 in previous quarter) 
   
## JIRA activity: 
   
 - 51 JIRA tickets created in the last 3 months 
 - 38 JIRA tickets closed/resolved in the last 3 months 

-----------------------------------------
Attachment BF: Report from the Apache Parquet Project  [Julien Le Dem]

## Description:
Parquet is a standard and interoperable columnar file format for efficient
analytics. Parquet has 3 sub-projects:
- parquet-format: format reference doc along with thrift based metadata
  definition (used by both sub-projects bellow)
- parquet-mr: java apis and implementation of the format along with
  integrations to various projects (thrift, pig, protobuf, avro, ...)
- parquet-cpp: C++ apis and implementation of the format along with Python
  bindings and arrow integration.

## Issues:
  No issue at this time

## Activity:
 - Statistics bug fixes
 - ongoing votes for parquet-format and parquet-mr release
 - ongoing votes for parquet-rust contribution
 - parquet-proto improvements and new contributors

## Health report:
 The discussion volume on the mailing lists is increasing. Tickets get created
 and closed at a reasonable pace

## PMC changes:
 - Currently 23 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Uwe Korn on Sun Mar 26 2017

## Committer base changes:
 - Currently 28 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Zoltan Ivanfi at Fri Oct 27 2017

## Releases:
 - CPP-1.4.0 was released on Mon Mar 05 2018

## Mailing list activity:
 - mailing list activity up this quarter
 - dev@parquet.apache.org:
    - 202 subscribers (up 5 in the last 3 months):
    - 933 emails sent to list (573 in previous quarter)

## JIRA activity:
 - 77 JIRA tickets created in the last 3 months
 - 54 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment BG: Report from the Apache PDFBox Project  [Andreas Lehmkühler]

## Description:
 - the Apache PDFBox library is an open source Java tool for working with PDF
   documents.

## Issues:
 - there are no issue requiring board attention at this time.

## Activity:
 - we released the first Apache based version of the JBig2 ImageIO plugin last
   month
 - we are working on fixing bugs and adding smaller improvements to 2.0.x
 - we have already resolved quite a number of 2.0.x releated tickets so that
   most likely the next bugfix version 2.0.10 will be released soon
 - we are planning to release a bugfix version of 1.8.x soon
 - we are improving our website

## Health report:
 - there is a steady stream of contributions, bug reports and questions on the
   mailing lists
 - we are pleased to see that the amount of patches compared to other
   contributions is growing. So more and more people are not just using PDFBox
   but dig deeper into it

## PMC changes:

 - Currently 21 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Matthäus Mayer on Mon Oct 16 2017

## Committer base changes:

 - Currently 21 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Joerg O. Henne at Mon Oct 09 2017

## Releases:

 - 2.0.9 was released on Fri Mar 23 2018
 - 3.0.0 JBIG2 was released on Tue Feb 27 2018

## JIRA activity:

 - 127 JIRA tickets created in the last 3 months
 - 127 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment BH: Report from the Apache Ranger Project  [Selvamohan Neethiraj]

## Description:
 - The Ranger project is a framework to enable, monitor and manage comprehensive data security across the Hadoop platform.

## Issues:
 - there are no issues requiring board attention at this time

## Activity:
 - Community has release Apache Ranger 1.0 and working on improve/fix bugs on the releases both 1.0 and 0.7.x
 - Jira: +110(added) -96(resolved) over last 3 months
 - Git (Source): 58 commits over last 3 months
 - SVN (ranger site updates): 15 commits over last 3 months

## Health report:
 - Released Apache Ranger 1.0 with authorization engine to work with Apache Hadoop 3.0+ ecosystem
 - Working on some of the open bugs (branch 0.7 and 1.0 releases) along with new features for next release

## PMC changes:
 - Currently 18 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Abhay Kulkarni on Fri Dec 15 2017

## Committer base changes:
 - Currently 26 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Zsombor Gegesy at Sat Dec 09 2017

## Releases:
 - Apache Ranger 1.0.0 was released on Sun Mar 18 2018

## Mailing list activity:
 - dev@ranger.apache.org:
    - 102 subscribers (up 1 in the last 3 months):
    - 1144 emails sent to list (1356 in previous quarter)

 - user@ranger.apache.org:
    - 170 subscribers (up 1 in the last 3 months):
    - 44 emails sent to list (56 in previous quarter)

## JIRA activity:
 - 110 JIRA tickets created in the last 3 months
 - 96 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment BI: Report from the Apache Samza Project  [Yi Pan]

## Description:
 - Apache Samza is a distributed stream processing engine that are highly
   configurable to process events from various data sources, including
   real-time messaging system (e.g. Kafka) and distributed file systems (e.g.
   HDFS).

## Issues:
 - No issues requires board attention

## Activity:
 - We have another Stream Processing meetup in Mar 2018:
   https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/248309045/

## Health report:
 - Project is in healthy status with a lot of development activities in
   continuation (e.g. SamzaSQL, table API, Samza-on-Azure, Kinesis consumer)
 - Added one new PMC member in last 3 months
 - Added Ntent and Movie in PoweredBy

## PMC changes:
 - Currently 14 PMC members. 
 - Xinyu Liu was added to the PMC on Tue Jan 16 2018 
   
## Committer base changes: 
   
 - Currently 18 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Boris Shkolnik at Mon Oct 02 2017 
   
## Releases: 
   
 - Last release was 0.14.0 on Thu Jan 04 2018 

## Mailing list activity:

 - dev@samza.apache.org:  
    - 287 subscribers (down -6 in the last 3 months): 
    - 227 emails sent to list (253 in previous quarter) 
   
   
## JIRA activity: 
   
 - 91 JIRA tickets created in the last 3 months 
 - 61 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment BJ: Report from the Apache Sqoop Project  [Venkat Ranganathan]

## Description:
Apache Sqoop is a tool designed for efficiently transferring bulk data
between Apache Hadoop and structured datastores such as relational
databases. It can be used to import data from external structured
datastores into Hadoop Distributed File System or related systems like
Hive and HBase. Conversely, Sqoop can be used to extract data from
Hadoop and export it to external structured data stores such as relational
databases and enterprise data warehouses.
## Issues:
There are no issues requiring board attention at this time
## Activity:
Development activity continues on both trunk and sqoop 2 branches -
both our major versions
that we currently support and develop.
## Health report:
Community is healthy, we see a new contributors showing up and
contributing to the project.
## PMC changes:
 - Currently 16 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Abraham Fine on Mon Nov 28 2016
## Committer base changes:
 - Currently 31 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Vasas Szabolcs at Tue Nov 14 2017
## Releases:
 - 1.4.7 was released on Tue Jan 23 2018
## JIRA activity:
 - 38 JIRA tickets created in the last 3 months
 - 18 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment BK: Report from the Apache Stanbol Project  [Fabian Christ]

Apache Stanbol provides a set of reusable components for semantic content
management.

The project is still in sleep mode. No activity on the dev list and no
progress in terms of commits. The last commit was pushed in March 2017
but there is no work happening towards a 1.0.1 release at the moment.

There has been an initiative to place a GSoC project and we have a
student which is interested. Discussions about the scope of the
project are currently made.

Beside the fact that not much is happening there is no issue which
requires board attention at the moment.

Subscribers on the dev list: 219

Last new committer was
  Cristian Petroaca on May 7th, 2015

Last new PMC member were
  Cristian Petroaca on July 28th, 2016
  Rafa Haro on July 28th, 2016
  
Last stack release was:
  Apache Stanbol 1.0.0 on Oct 23rd, 2016

Last component release was:
  Apache Stanbol Partial Security Release RC2 on June 5th, 2014
  org.apache.stanbol.commons.security.reactor-20140602 


-----------------------------------------
Attachment BL: Report from the Apache Steve Project  [Daniel Gruno]

## Description: 
 Apache STeVe is Apache's Python based voting system that the Foundation
 uses to handle things like voting in our new Board of Directors.
   
## Issues: 
 There are no issues requiring board attention at this time.
   
## Activity: 
 The annual members meeting used STeVe for the voting process.
 Things went fairly smoothly, with a minute number of bugs detected,
 among them a unicode bug in the email functions.
 Not much in terms of response this time around, but we did get some
 ideas floating on the dev list[1]. Jim and I (Daniel) have both indicated
 an interest in pursuing these ideas at a later stage, when time permits
    
## Health report: 
 The project is pretty much in chronic hiatus/stand-by mode for the time
 being. We have sufficient PMC oversight (>= 3 active members), but
 little time to devote to the project and not a whole lot of new
 volunteers. If anyone reading this wants to contribute, please let
 us know at dev@steve.apache.org :-). It is probably worth noting, that
 we have sufficient person-power to address bugs and vulnerabilities...
 not that we've had anything serious to address yet.
   
## PMC changes: 
   
 - Currently 5 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Rich Bowen on Mon Apr 20 2015 
   
## Committer base changes: 
   
 - Currently 9 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Pierre Smits at Tue Dec 15 2015 
   
## Releases: 
   
 No releases yet. We have been running members meetings on a trunk
 philosophy for the past few years and it's worked out well enough.
 If we get indications of a desire to use STeVe outside the foundation,
 we will of course consider pushing a release out.
   
## Mailing list activity: 
   
 Very low activity, nothing worth going into details over.
   
## Bug/issue activity: 
   
 - 4 JIRA tickets created in the last 3 months 
 - 0 JIRA tickets closed/resolved in the last 3 months 


[1] https://s.apache.org/8Ejs


-----------------------------------------
Attachment BM: Report from the Apache Streams Project  [Steve Blackmon]

## Description:
- Apache Streams unifies a diverse world of digital profiles and online
  activities into common formats and vocabularies, and makes these datasets
  accessible across a variety of databases, devices, and platforms for
  streaming, browsing, search, sharing, and analytics use-cases.

## Issues:
- There are a lot of changes occurring in the APIs of our supported data
  sources.  Due primarily to the EU's GDPR legislation, a user's ability to
  collect profiles and posts from accounts other than the authenticated
  account is being limited. On the other hand comprehensive data about the
  authenticated account (sometimes via bulk export not via API) is becoming
  richer, presenting an opportunity for the project to assist users in
  awareness of the data collected about them by third-parties, and with data
  portability between systems using bulk export archives.

## Activity:
- We are preparing to release Apache Streams 0.6.0 - the first to include a
  binary artifact allowing users to run Streams classes from their terminal
  without building the project or wrapping it's modules in custom code.
- We ran a comprehensive audit of dependencies (including transitive
  dependencies) and removed all items with undesirable licenses.  The license
  audit now gets published to the website, and the maven plugins involved can
  used to help us maintain our NOTICE file.
- We revamped the way that configuration details are provided to classes
  rather substantially, making it more flexible, powerful, and easier to
  understand.
- The secondary apache/streams-examples repository has been integrated into
  apache/streams.

## Health report:
Streams graduated to TLP on July 19 2017.  New features and platform
improvements are happening at a steady pace.  Adding committers and growing
the PMC needs to be a focus this year.

## PMC changes:
None. There are currently 8 PMC members.

## Committer base changes:
None. There are currently 8 committers.

## Releases:
- Apache Streams 0.5.1 was released on January 09, 2018
- Apache Streams 0.6.0 is targeted for release this month (April 2018)

## Upcoming Project Initiatives:
- Integrate new binary release with Apache Kibble, and with the Apache
  Software Foundation instance of Kibble.
- Add new providers that source streams from export archives of existing data
  sources (twitter, facebook, google).
- More tweets and blog posts of zeppelin notebooks demonstrating data
  pipelines and analyses based on Apache Streams.
- More official examples in source tree demonstrating integration of Apache
  Streams with complementary technologies.
- Drop remaining maven dependencies on java SDKs for accessing third-party
  APIs in favor of HTTP/REST interfaces powered by Apache Juneau Remoteable
  Annotations.
- Improve the interfaces by which components are created, configured,
  activated, and executed via SDK and CLI.- Reduce disparities between
  normalized activities and objects of like type collected from various data
  sources.
- Reduce disparities between the configuration objects that initialize similar
  providers from various data sources.
- Add official support for Schema.org and Activity Streams 2.0 data types.


-----------------------------------------
Attachment BN: Report from the Apache Struts Project  [René Gielen]

The Apache Struts MVC framework is a solution stack for creating elegant
and modern action-based Java web applications. It favors convention over
configuration, is extensible using a plugin architecture, and ships with
plugins to support technologies such as REST, AJAX and JSON.

The Struts team made one GA releases in the last quarter.
* Struts 2.5.16 - full GA release including bug fixes and feature
enhancements (2018-03-16)

Furthermore we released two security announcements
* advise users to upgrade commons-fileupload to version 1.3.3 [1]
* a crafted XML request can be used to perform a DoS attack when using
the Struts REST plugin [2]

In the last quarter we released Struts 2.5.16, with many improvements
feature-wise as well as bug fixes. Community contributions and
development activities were on a constantly decent level.

We had again a few incoming security reports and resulting issues, that
we were able to deal with in a timely manner. The issues were again
mostly related to 3rd party libraries used by the Struts framework.

No committers or PMC members were added in the last quarter.

Last committer addition:
* 2017-11-14 - Yasser Zamani (yasserzamani)
Last PMC addition:
* 2017-11-06 - Stefaan Dutry (sdutry)

We have no issues that require board assistance at this time.

[1] http://struts.apache.org/announce.html#a20180323
[2] http://struts.apache.org/docs/s2-056.html


-----------------------------------------
Attachment BO: Report from the Apache Tapestry Project  [Thiago Henrique De Paula Figueiredo]


-----------------------------------------
Attachment BP: Report from the Apache Tcl Project  [Georgios Petasis]

## Description: 

  - Apache Tcl is home to the Tcl-Apache integration efforts.
    The purpose of our project is to combine the power of the
    Apache web server with the capabilities of the mature,
    robust and flexible Tcl scripting language. Currently
    only the Apache Rivet project is actively maintained
   
## Issues: 
  - The project chair has changed and from now on reports will
   be filed by the new chair George Petasis.
  - A few former members of the PMC (ridruejo,dirkx,mlink) were removed
   from the PMC roster. They had long lost interest in the project
   and had pulled out of the PMC mailing list long ago. 
   We would be glad to see them coming back to the project any time

## Activity: 
  - Rivet released a 3.0.1 version correcting a few bugs that surfaced
   as soon as 3.0.0 was released. 
   
## Health report: 
  - The project activity is limited to Apache Rivet, as usual 
   
## PMC changes: 
   
 - Currently 7 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Brice Hamon De Crevecoer on Tue Nov 25 2014 
   
## Committer base changes: 
   
 - Currently 12 committers. 
 - No new committers added in the last 3 months 
 - Last committer addition was Brice B. Hamon at Tue Nov 25 2014 
   
## Releases: 
   
 - rivet-3.0.0 was released on Wed Jan 17 2018 
 - rivet-3.0.1 was released on Fri Feb 09 2018


-----------------------------------------
Attachment BQ: Report from the Apache Tez Project  [Jonathan Turner Eagles]

## Description:
Apache Tez is an effort to develop a generic application framework which
can be used to process arbitrarily complex directed-acyclic graphs (DAGs) of
data-processing tasks and also a re-usable set of data-processing primitives
which can be used by other projects.

## Issues:
There are no issues requiring board attention at this time.

## Activity:
A 0.9.2 release has been in progress for some time. The a new line 0.10 line is being proposed to better support Apache Hadoop 3.0. Jon Eagles is the new PMC chair for Apache Tez

## Health report:
Development activity continues to be slow, with features and bug fixes
going in as and when requried by projects which use Apache Tez.

## PMC changes:

 - Currently 35 PMC members.
 - Zhiyan Yan was added on Jan 19 2018
 - Kuhu Shukla was add on Mar 26 2018 
 - Last PMC addition was Kuhu Shukla was add on Mar 26 2018

## Committer base changes:

 - Currently 38 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Kuhu Shukla at Wed May 10 2017

## Releases:

 - Tez 0.9.1 was released on Jan 4 2018

## JIRA activity:

 - 27 JIRA tickets created in the last 3 months
 - 19 JIRA tickets closed/resolved in the last 3 months


-----------------------------------------
Attachment BR: Report from the Apache Thrift Project  [Jake Farrell]

Apache Thrift is a framework for providing cross-platform RPC and serialization.

Project Status
---------
The Apache Thrift community recently switched canonical repository location from
Apache git-wip to Github via the ASF Gitbox service and this has caused some
unanticipated pain for our user and dev communities. We are working to address
these client library integration problems as fast as possible and Apache Infra
has been a great help with this when needed. While addressing these issues we
are progressing towards our next release candidate and focusing on improving our
processes arounds test automation and simplifying our workflows.

Community
---
Latest Additions:

* PMC addition:         James King, 11.2.2017
* Committer addition:   Duru Can Celasun, 3.7.2018
                        Allen George, 3.19.2018

Issue backlog status since last report:

* Created:   102
* Resolved:  99

Mailing list activity since last report:

* @dev    1861 messages
* @user   54 messages

Releases
---
Last release: 0.11.0, Release Date: 12.6.2017


-----------------------------------------
Attachment BS: Report from the Apache Tika Project  [David Meikle]

## Description:
Apache Tika is a dynamic toolkit for content detection, analysis, and
extraction. It allows a user to understand, and leverage information from, a
growing a list over 1200 different file types including most of the major
types in existence (MS Office, Adobe, Text, Images, Video, Code, and science
data) as recognised by IANA and other standards bodies.

## Issues:
- There are no issues that require the board's attention at this time.

## Activity:

- The project is currently finalising the contents of a new 1.18 release with
  updated to the Mimetype detection, a new XPS parser, improvements to the OCR
  Parser and updated base libraries.

- Work continues on the new 2.x based master with a significant addition being
  the new composite parser strategy work (TIKA-1509 [0]) added by Nick Burch

## PMC changes:

 - Currently 29 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Madhav Sharan on Thu Aug 31 2017
 - A vote has just finished to add a new PMC member

## Committer base changes:

 - Currently 30 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Madhav Sharan at Thu Aug 31 2017

 ## Releases:

  - 1.17 was released on Wed Dec 13 2017

 ## Mailing list activity:

 - dev@tika.apache.org:
    - 195 subscribers (down -1 in the last 3 months):
    - 776 emails sent to list (575 in previous quarter)

 - user@tika.apache.org:
    - 357 subscribers (up 7 in the last 3 months):
    - 65 emails sent to list (66 in previous quarter)

 ## JIRA activity:

  - 71 JIRA tickets created in the last 3 months
  - 47 JIRA tickets closed/resolved in the last 3 months

[0] https://issues.apache.org/jira/projects/TIKA/issues/TIKA-1509


-----------------------------------------
Attachment BT: Report from the Apache TinkerPop Project  [Stephen Mallette]

## Description:
Apache TinkerPop is a graph computing framework for both graph databases
(OLTP) and graph analytic systems (OLAP).

## Activity:
TinkerPop is currently in the process of releasing 3.2.8 and 3.3.2 which
both generally contain bug fixes and minor new functionality. However, this
release of TinkerPop also includes the first official release of Gremlin
Javascript, which should further open up the TinkerPop world to the
Javascript community. This delivery of Gremlin in Javascript will make for
the fifth official language variation (Gremlin Language Variant or GLV[1]).
The current list of languages officially supported natively for Gremlin by
TinkerPop are:

- Java
- Groovy
- Python
- .NET/C#
- Javascript

While work has not yet truly started, we did open up a new branch of
development for the 3.4.x line of code. It is still up for discussion in the
community to determine what this release will contain.

TinkerPop did invite someone to join the PMC, but that person politely
declined and preferred to continue to contribute as they have been doing.

There were a number of talks on TinkerPop and TinkerPop-enabled technology
in the last several months. Here is a selection of those made by PMC
members:

- "Gremlin's Anatomy" at DataStax NYC Meetup by Stephen Mallette[2]
- "Powers of Ten Redux" at Data Day by Jason Plurad[3]

Finally, we received a nice comment from someone on our user mailing list
who said that our user list was, "One of the most active google groups I
have seen in recent times, kudos for that !!!"[4] It's a simple anecdote,
and we tend to see comments of its like from time to time, but we found this
one to be unique in its wording of "thanks" in that it directly complimented
the attention that our community pays to its users.

## Issues:
There are no issues requiring board attention at this time.

## Releases:
- 3.2.8 (April 2, 2018)
- 3.3.2 (April 2, 2018)

## PMC/Committer:
- Last PMC addition was Robert Dale - April 2017
- Last committer addition was Kelvin Lawrence - December 2017

## Links

[1] https://s.apache.org/F55i
[2] https://www.slideshare.net/StephenMallette/gremlins-anatomy-88713465
[3] https://www.slideshare.net/JasonPlurad/powers-of-ten-redux-86792623
[4] https://s.apache.org/cA8z

-----------------------------------------
Attachment BU: Report from the Apache TomEE Project  [David Blevins]

## Description:

Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.

## Issues

The community had a situation similar to the previously reported June 27th
incident that spawned the "Suffocating development environment" [1] thread.
The subject matter was different, but the dynamics and people involved were
largely the same with a commit that caused immediate harsh feedback and was
immediately reverted.

On February 2nd a discussion was started on potentially implementing
MicroProfile JWT in TomEE, which started some at first healthy discussion on
where this should go.  There was a perspective that this has come up before,
is yet unresolved and should be discussed.  There was also the perspective
that all code that implements the MicroProfile brand should belong to
Geronimo and TomEE can use them, but never create them.  As well that
Geronimo is the proper place for a reusable components under the Java EE
umbrella.

On February 12 a commit came in [2] during this discussion, was perceived as
attempting to circumvent the conversation, infringe on Geronimo's territory,
and generated some immediately harsh responses [3][4].  The committer
reverted his own commit and sent an email largely with the tone "I quit this
project" [5].  A wider discussion was had on the incident [6] and some
apologies were made for jumping to conclusions, however the underlying belief
that Geronimo is the proper owner of the MicroProfile at Apache remains.

In the last 12 months to date, only 3 people have committed to Geronimo, 2 of
them are TomEE committers.  There are no evildoers in any of this, but the
overlap does add to the complexity of the issue and results in most of the
discussion naturally taking place on the TomEE lists.

## Health

Developer mailing list activity spiked up significantly due to the above
discussion.  Activity of any kind is a good thing as the lists have been
generally quiet.  Here are the stats from this reporting period vs the same
period last year:

2017

- Jan, 38 
- Feb, 39
- Mar, 60

2018

- Jan, 42
- Feb, 202
- Feb, 212

While people are no agreeing, they are talking which is a good step forward.
As reported in December, commits had been dominated by largely one person for
the first six months of 2017, but were dramatically transformed in the six
months after the June 27th 2017 triple-commit-and-revert incident.  So while
the incident in this report may sound negative, it's my belief this is
another step in the project regaining balance and growing.  I suspect as
before in six months time we'll see a major improvement that can be traced
back to this event.

## Activity

Implementation of the MicroProfile JWT specification was the major activity.
The code allows for the validation of RSA signed JSon Web Tokens in TomEE
sent over the 'Authorization' header of incoming HTTP requests.  A PR was
created consisting of a handful of integration changes and 19 new java files
that was extensively reviewed by two others, one of whom is a new
contributor.  Due to the unclear stance of this subject in general, a vote
was held on if the code should be merged.  Results were 11 +1s, 1 0 and 1 -1.
6 were binding and 7 came from community members, which is also encouraging
as voter turnout has been low.  After discussion on the list and with the
board, it was determined the -1 issues on the grounds the code should live in
Geronimo is not a binding technical veto.  A separate, non-technical vote,
was held to determine if the project had desire to make the reusable library
that seems to be desired.  That vote concluded with 6 +1s, 1 +0 and 2 -1s.
Both -1s were on the grounds the work should be done in Geronimo.  No further
work has been done yet.

Work on Java 9 and 10 support has started in both the Apache TomEE 1.7.x and
7.0.x branches.  Code dontations of Sheldon and Chatterbox, \ mentioned in
the December report, have completed.  Releases of that code have not yet been
made.

## PMC changes:

- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015

## Committer base changes:

- Currently 30 committers.
- Last two committers added
  - Svetlin Zarev on Tue Oct 24 2017
  - Jonathan S Fisher on Wed Nov 1 2017

## Releases:

- Apache TomEE 1.7.5 on Oct 24, 2017
- Apache TomEE 7.0.4 on Oct 10, 2017


[1] https://lists.apache.org/thread.html/1306bfc0bb78ef47517db6e3866bb750a72458796f9895545dc39cd6@%3Cdev.tomee.apache.org%3E
[2] https://lists.apache.org/thread.html/8fe6bc10edb0ba82da1082fa8a4285d754630efd8980e6f044a8465f@%3Ccommits.tomee.apache.org%3E
[3] https://lists.apache.org/thread.html/b60d0b98b9fc70361e760bba4ba5177d95010aa32409d1f9fe301c40@%3Cdev.tomee.apache.org%3E
[4] https://lists.apache.org/thread.html/70aea236ef6fe414ae243ab1c1887040aff607f8c09704dcf02fb513@%3Cdev.tomee.apache.org%3E
[5] https://lists.apache.org/thread.html/9c316ebb0e652a89c1d7a762e38b8eed887ae6f4f3226ea35ab076b6@%3Cdev.tomee.apache.org%3E
[6] https://lists.apache.org/thread.html/33f9553894f4d192f50e6d9c3bf67c82c3a93795a7b4e1543f6f67b5@%3Cdev.tomee.apache.org%3E

-----------------------------------------
Attachment BV: Report from the Apache Traffic Server Project  [Bryan Call]

## Description: 
Apache Traffic Server is a HTTP and HTTP/2 proxy server and cache.  What makes
ATS unique across the landscape of HTTP proxy caches is a focus on
extensibility (plugins), HTTP and HTTP/2 protocol conformity, and performance.
ATS is driving some of the largest CDNs in the world, delivering a significant
portion of all Internet traffic.

## Issues: 
 - There are no issues requiring board attention at this time.
   
## Activity:
 - There was a QUIC Hackaton in January in Tokyo, Japan.  There were 6 people
   that attended and worked on the design and implementation of IETF QUIC
   inside of ATS.

 - We have an ATS Spring Summit schedule in Cork, Ireland for the week of May
   6th.  18 people have signed up and there are going to be presentations and
   planned events around cleanup of the code and bug reports.
   
## Health report: 
 - We had a successful 7.1.2 release in January and there at least two major
   companies running the release in full production.  The first 7.1.3 release
   candidate came out this week and we are in the middle of voting on it.

## PMC changes: 
   
 - Currently 41 PMC members. 
 - No new PMC members added in the last 3 months 
 - Last PMC addition was Gancho Tenev on Sun Jun 04 2017 
   
## Committer base changes: 
   
 - Currently 56 committers. 
 - New commmitters: 
    - Derek Dagit was added as a committer on Mon Mar 26 2018 
    - Fei Deng was added as a committer on Wed Mar 14 2018 
    - Zizhong Zhang was added as a committer on Wed Mar 28 2018 
   
## Releases: 
   
 - Last release was 7.1.2 on Wed Jan 10 2018 
   
## Mailing list activity: 
   
 - User mailing was higher than normal the previous quarter (Q4 of 20017) and
   now is back to normal levels. The dev email list is up 56% this quarter.
   
 - users@trafficserver.apache.org:  
    - 495 subscribers (down -3 in the last 3 months): 
    - 129 emails sent to list (226 in previous quarter) 
   
 - dev@trafficserver.apache.org:  
    - 329 subscribers (up 0 in the last 3 months): 
    - 156 emails sent to list (100 in previous quarter) 
   
 - announce@trafficserver.apache.org:  
    - 16 subscribers (up 0 in the last 3 months): 
    - 3 emails sent to list (0 in previous quarter) 
   
 - issues@trafficserver.apache.org:  
    - 31 subscribers (down -2 in the last 3 months): 
    - 471 emails sent to list (274 in previous quarter) 
   
 - summits@trafficserver.apache.org:  
    - 17 subscribers (up 2 in the last 3 months)

## GitHub Issue activity:
 - 37 issues created in the last 3 months
 - 40 issues closed in the last 3 months

## Commit activity:
 - 64,512 lines of code changed (down -18%)
 - 502 commits (up 2%)
    - 20 committer email addresses (up 17%)
    - 48 author email addresses (down 12%)

-----------------------------------------
Attachment BW: Report from the Apache VXQuery Project  [Till Westmann]

Description:

Apache VXQuery implements a parallel XML Query processor.

Activity:
- Very low activity.
- Still no new release.
- Started discussion on moving to the attic.

Issues:
- There are no issues that require the board's attention at this time.

PMC/Committership changes:
- Currently 12 committers and 7 PMC members in the project.
- Last PMC addition was Steven Jacobs at Jul 18, 2014.
- Last committer additions were Riyafa Abdul Hameed and Christina Pavlopoulou
  on Aug 22, 2016.

Releases:
- Last release was 0.6 on May 26 2016


-----------------------------------------
Attachment BX: Report from the Apache Web Services Project  [Daniel Kulp]

Apache Web Services is a collection of shared technologies related to
SOAP/XML based Web Services that can be shared by different implementations.
Spring-WS, Axis2, CXF, and others use parts of the technology created within
Apache Web Services.

Community:
WebServices is a mature project based on standards that are also quite
mature.   As such, there is not a significant amount of activity required.
However, user questions are being answered promptly, bugs are being fixed,
and there are at least 3 independent PMC members around making sure
the project can continue to produce releases as needed.   Since
SOAP/XML based Web Services is no longer considered state of the art,
we don't expect a major uptick in new development efforts, new
committers, etc...

At the start of the quarter, we did make an effort to apply some bug
fixes and get some patch releases out.  There have been some fixes
applied to WSS4J since then and we do expect to do some more patch
releases soon.

Last committer addition: Sun Sep 14 2014 (Alessio Soldano)

Last PMC addition: Tue May 17 2016 (Alessio Soldano)

Releases this period:

WSS4J - implementation of WS-Security and related technologies
* 2.1.12 - Jan 2018
* 2.2.1 - Jan 2018

XmlSchema - object model for XML schema
* 2.2.3 - Jan 2018

Neethi - WS-Policy framework
* 3.1.1 - Jan 2018


Last releases for other technologies:
*  Axiom  1.2.20 : Oct 2016 (StAX-based, XML Infoset compliant object model)
*  Woden 1.0M10 : Sept 2015  (WSDL 2.0 implementation)


-----------------------------------------
Attachment BY: Report from the Apache Wicket Project  [Martijn Dashorst]

Report from the Apache Wicket project [Martijn Dashorst]

Apache Wicket is an open source Java component oriented web application
framework.

## Noteworthy items:

 - skipped prior report in the normal schedule, this report follows up on that

 - 2 releases were performed

 - Wicket 8 is technically done, waiting for site adjustments, announcements,
   press release to be written

 - Infoworld published a listicle of 15 Java frameworks to give developers a
   boost [1], and Wicket was one of the reviewed items

## Issues:

 - No issues require board attention.

## Activity:

 - We are on the cusp of releasing Wicket 8, so we still plan on working with
   Sally for the corresponding press coverage.

 - There's some frustration that we haven't pushed Wicket 8 due to not having
   the PR ready.

 - We're also discussing the future plans of Java releases and the impact on
   Wicket releases: how to work with breaking Java changes in our project

 - We (just as the other Java web frameworks at Apache) were interviewed by
   Paul Krill from Infoworld about the future of Java web frameworks in
   general and Wicket specifically.

## Health report:

 - The community is stable as is to be expected from a mature server side Java
   web framework. We don't anticipate a sudden large growth or large decline.

 - Questions to the user list and dev list are answered, resolved and
   discussed.

 - We have joined several other projects on the-asf slack, and created a
   #wicket channel. Not much happening over there, but it is nice to have a
    chat venue available

## PMC changes:

 - Currently 30 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Maxim Solodovnik on Thu Apr 13 2017

## Committer base changes:

 - Currently 31 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Maxim Solodovnik at Thu Apr 13 2017

## Releases:

 - 7.10.0 was released on Thu Feb 15 2018
 - 8.0.0-M9 was released on Sat Feb 17 2018

 [1] https://www.infoworld.com/article/3263767/java/15-java-frameworks-that-give-developers-a-boost.html


-----------------------------------------
Attachment BZ: Report from the Apache Zeppelin Project  [Lee Moon Soo]

## Description: 
 -  Apache Zeppelin is a collaborative data analytics and visualization tool for general-purpose data processing systems.
   
## Issues:
 - No issues
   
## Activity:
 - Preparing 0.8.0 
   
## Health report: 
 - Steady increment of number of code contributors. +11 since last report, 257 total
   
## PMC changes: 
 - Currently 11 PMC members.
 - Last PMC addition was Jeff Zhang on Thu Jan 25 2018
   
## Committer base changes: 
 - Currently 17 committers.
 - Last committer addition was Park Hoon at Jun 22 2017
   
## Releases:
 - 0.7.3 was released on Wed Sep 20 2017
 - 0.7.2 was released on Mon Jun 12 2017
 - 0.7.1 was released on Fri Mar 31 2017
 - 0.7.0 was released on Sun Feb 05 2017
 - 0.6.2 was released on Fri Oct 14 2016
 - 0.6.1 was released on Aug 15 2016
 - 0.6.0 was released on Jul 02 2016
 - 0.5.6-incubating was released on Jan 22 2016
 - 0.5.5-incubating was released on Nov 18 2015
 - 0.5.0-incubating was released on Jul 23 2015

## Mailing list activity: 
 - users@zeppelin.apache.org:  
    - 723 subscribers (up 9 in the last 3 months): 
    - 188 emails sent to list (281 in previous quarter) 
   
 - dev@zeppelin.apache.org:  
    - 327 subscribers (down -3 in the last 3 months): 
    - 1250 emails sent to list (1173 in previous quarter) 

## JIRA activity: 
 - 267 JIRA tickets created in the last 3 months 
 - 154 JIRA tickets closed/resolved in the last 3 months

------------------------------------------------------
End of minutes for the April 18, 2018 board meeting.

Index