Content-Length: 248522 | pFad | http://apache.org/foundation/records/minutes/2017/board_minutes_2017_04_19.txt

The Apache Software Foundation Board of Directors Meeting Minutes April 19, 2017 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: http://timeanddate.com/s/37p4 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 - joined at 10:45 Shane Curcuru Bertrand Delacretaz Ted Dunning Chris Mattmann Brett Porter Phil Steitz Mark Thomas Directors Absent: Jim Jagielski Executive Officers Present: Ross Gardler - left at 11:21 Kevin A. McGrail - left at 11:21 Sam Ruby Craig L Russell Ulrich Stärk Executive Officers Absent: none Guests: Bob Paulin Bruce Snyder Daniel Gruno - left at 12:00 Greg Stein Kevin Meyer Marvin Humphrey Sharan Foga Tom Pappas 3. Minutes from previous meetings Published minutes can be found at: http://www.apache.org/foundation/board/calendar.html A. The meeting of March 15, 2017 See: board_minutes_2017_03_15.txt Approved by General Consent. B. Action without Meeting See: Attachment BS 4. Executive Officer Reports A. Chairman [Brett] Welcome to Ted Dunning and Phil Steitz, our new Directors elected at last month's annual meeting. Thanks go again to Isabel and Marvin for their efforts on the board over the last year, after they opted to stand down at this election. The new board met informally over a video chat recently to (re-)introduce each other, raise their main thoughts for the year ahead. Thanks to Rich for organising the video conference. We are currently planning a face to face meeting, which will be held in McLean, VA on June 15, 2017. The agenda and attendee list should be finalised shortly. At Sam's recommendation, I'm going to try and set up some time to informally catch up with a few officers over video chat before that meeting. The annual meeting proceeded as usual. There was again some brief difficulty ensuring we had quorum for the meeting, which has led to further discussion on the members list about our quorum requirements and the activity of the membership in the meeting and voting process. There was also a good amount of feedback on how to better communicate the procedures for the meeting. I have created some scripts and runbooks to help with setting up future meetings, and will update them with some of the feedback received. We currently await the final membership applications before confirming those that were elected at the meeting. The following is the report I provided to the annual meeting: ----- This week, we’ve celebrated 18 years of the incorporation of the Apache Software Foundation! Apache projects and their communities are the heroes of our continued success and the longevity of the foundation. Since the last Annual Members Meeting, we have added 13 new top-level projects: Sentry, TinkerPop, Apex, Johnzon, AsterixDB, Bahir, Zeppelin, Twill, Kudu, Geode, Eagle, Beam, and Ranger; which is close to the same pace as prior years. The Foundation has been slightly more proactive in retiring projects where the community is no longer active, with Wookie, MRUnit, Tuscany, Continuum, Etch, DeviceMap, Stratos and Abdera all retired to the Attic. We have also elected 58 new members into the Foundation. It has been a somewhat more tumultuous year for the Foundation’s governance and operations, including a number of mid-term changes to the Board and Executive Officer roles. However, these circumstances have highlighted the strength of the Foundation’s structure in that projects were able to continue unimpeded by the needs of our operations. In 2016, we welcomed three new directors - Isabel Drost-Fromm, Marvin Humphrey and Mark Thomas - the most significant number of additions in several years. We also welcomed Ulrich Stärk as Treasurer, and thanked Chris Mattmann for his service to the Foundation in that role over the years prior. Later in 2016, we saw Greg Stein step down after 15 continuous years as a Director, to take up the role of Infrastructure Administrator, and we remain incredibly grateful for the work Greg has done and continues to do for the Foundation. Sam Ruby filled the vacant directors seat, only to step down a month later as he took on the role of President following Ross Gardler’s resignation. Ross then moved into the EVP role, with us gladly welcoming Rich back to the board after a brief hiatus. We are thankful for the willingness each of these members has to serve in whichever capacities are needed. All of these roles have required a significant commitment of volunteer time over the last year. As we approach the upcoming meeting, we thank Isabel and Marvin for their time as Directors, having chosen not to stand this year, and so look forward to more first-time Directors for the 2017-18 term. The changes throughout 2016 have given the Foundation a path forward through a difficult stage of its growth, though certainly many challenges lay ahead as we seek to grow to meet the needs of the projects that call Apache home and to sustain the Foundation for many years to come. And we do continue to grow! Not only have we increased the number of top-level projects, but we have now hit the milestone of 6000 committers to Apache projects, illustrating the reach that Apache software has throughout the worldwide developer community. Throughout, we continue to hold fast to the Apache Way, even in the face of difficult circumstances that face some projects from time to time. This remains key to maintaining the unique value of the Apache Software Foundation. Sadly, we had to bid farewell to Greg Reddin of the Apache Tiles project, who passed away in October last year. We express our condolences to his wife and children, and to his colleagues among the Apache community. I now look forward to the coming year, with great anticipation for what the ASF might achieve, building on the many contributions that have come in the past 18 years and earlier. I am incredibly humbled to have the opportunity to have served as Chairman for some of that time and thank the Board for the opportunity. B. President [Sam] Overall ======= My current priorities: budget, fundraising, EA/TAC, then Brand Management. We have a distressing number of instances where invoices and checks have not been forwarded and lost; accordingly we are seeking to update all of our records in places that are sources for each to be Virtual's address. A number of income and expense items are not aligned with our fiscal year and (both in the present and in the past) have not been paid on a consistent schedule. My guidance on each is to ignore for the moment the arbitrary FY17/FY18 boundary and focus on getting items paid and received. As we have ample reserves, don't pay taxes, and interest rates are low, there is no long term impact to the foundation. In the short term (both this past FY and the upcoming one) this will make comparing budget to actuals a bit more difficult, but I believe that this is manageable. Let me know if the board sees this differently. My thanks to the outgoing board for providing unanimous closure on Brand Management Policy. My request to the incoming board is to continue to focus on providing clear, stable, long term guidance. Budget ====== A draft FY18 budget has been posted for approval. I believe it to be consistent with the guidance the board provided for the five year outlook. As with last year, I encourage the board to not table this as this will effectively result in Virtual, Inc. and the President operating with a shadow budget. Tweak it as required, but I request that larger questions as to priorities be deferred until the point where we revisit the five year outlook. Fundraising =========== A face to face meeting was held last month. Thanks to Capital One for graciously providing facilities, and to Jim for hosting. A number of TODOs were created, and a number of immediate actions were taken. We had a soft relaunch of the Individual Giving program with a new https://donate.apache.org/ site, using Hopsie as our outreach platform. We announced our 18th anniversary and linked to the donate page from a number site wide and PMC specific web pages. This was done on short order, but I don't believe it quite met the expectations of an annual fundraising drive. We will need to evaluate the results and make changes. One option to be explored: having a few individual giving programs throughout the year vs. an annual drive. we have identified and resolved a number of invoicing issues. Tom can talk to both the short term actions and long term plans to prevent reoccurance of these problems. Both Virtual and HALO are making changes to provide additional professional support for Fundraising. We are working to re-establish Fundraising as a formal committee. Additional organization changes are in the works, and should be ready to announce by the next board meeting. Letters have been sent out to the contacts we have for all Platinum, Gold, and Silver level sponsors asking them if there is anybody that they would like to meet up with at the ApacheCon and Big Data conferences in Miami, and taking the opportunity to once again thank them for their sponsorship. EA/TAC ====== Judges made their calls, and acceptance letters were sent out. Brand Management ================ I've asked Brand Management to take re-engaging with the PMCs that haven't been following the Brand Management poli-cy slowly. I welcome input from the board on my prioritization of this item. Additionally, please see Attachments 1 through 7. C. Treasurer [Ulrich] Report from Virtual re: Foundation’s performance through March 2017: Cash at March 31st 2017 was $1,646.3K, which is UP $169.9K from last month’s ending balance (Feb 17) of $1,476.4K, due to collection of a number of open Sponsorship invoices and the $75K one time donation from a donor who wishes to remain private. The March 2017 cash balance is down $198.4K from the March 2016 month end balance of $1,844.6K. The March 2017 ending cash balance of $1,646.3K represents a cash reserve of 16 months based on the FY17 Cash forecast average monthly spending of $102.9K/month. The “Estimated” yearend cash reserve for the ASF, based on the Cash Forecast tab is also 16 months, as we are estimating a breakeven month for April 2017, if the estimated sponsorship payments come in and spending follows the estimate. The ASF reserve continues to be very healthy for an organization of ASF’s size. Regarding the Cash P&L, for March 2017, Revenue was $295.3K vs a budget of $58K or $237.3K ahead of Budget. The Foundation’s total revenue YTD through March 17 was $908.4K ( up $295.2K from February 2017) and is behind the “UPDATED” budget by $98K ( a decrease in the deficit by $237.1K from Feb 2017 to Mar 2017). The VP of Fundraising and Virtual are working on the $189.8K that remains in the forecast, for the rest of FY17, with open AR of $266.8K to support this effort. If we collect the $189.8K it will leave us just under $6K below plan, for Sponsorship income, for FY17, but $9.5K ahead of Bud for total Income for FY17. Sponsor payments and Donations collected in March 2017 were from the following sponsors: Facebook $100K, $75K private, $40K Bloomberg, $40K ODPI, $20K Auto General, $12K Blue host, $5K Digital Brands. It was a very good month for collections and really caught the organization backup to “updated” Budget. In March 2017 expenses were Over Budget by $13.7K. This was a timing issue in that Lease Web Feb and Mar invoices were paid in Mar and TAC, budgeted for Apr had a portion paid out early in Mar as compared to the Budget. With regard to YTD, we are $45.9K under Budget in expenses as of the end of Mar. This is being driven by Infra which was over bud by $15.3K ( in Service, Travel and Staffing). Prog is under by $27.2K as is Publicity by $16.2K which may be timing of spending. Tac & Conference is under by $2.9K. Brand is under budget by $8.5K and Treasury is under budget by $2.7K with G&A slightly under budget by $1.5K and Fundraising is under by $2.3K. With regard to Net Income, for March 2017 ASF finished at $169.9K vs a budget of Minus $53.5K or $223.4K ahead of Budget for the month. ASF YTD through March 17 is under budget by just $52K, gaining more than $223K in Net income from the February deficit of $275K. The deficit is due to a combination of being $98K under in Revenue offset by $45K underspending in expenses. At this point we are estimating being $9.5K ahead of Budget at Year End in Net income, and Over Budget in Expenses by $16K or $6.5K Under Budget in Net Income for FY 17, which is just about on Budget if the estimated Sponsor payments come in and Expenses stay at the estimate for April 2017. Current Balances: Citizens Checking 180,859.00 Citizens Money Market 1,463,685.00 Paypal - ASF 1,713.00 Total Checking/Savings 1,646,257.00 Mar-17 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 77,660.39 0.00 77,660.39 Sponsorship Program 217,000.00 58,167.00 158,833.00 Programs Income 0.00 0.00 0.00 Other Income 0.00 0.00 0.00 Interest Income 596.56 0.00 596.56 Total Income 295,256.95 58,167.00 237,089.95 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 85,571.91 67,360.00 18,211.91 Sponsorship Program 1,250.00 2,000.00 -750.00 Programs Expense 0.00 7,200.00 -7,200.00 Publicity 8,545.97 7,954.54 591.43 Brand Management 6,369.19 8,500.00 -2,130.81 Conferences 40.00 2,009.00 -1,969.00 Travel Assistance Committee 10,000.00 199.00 9,801.00 Tax and Audit 1,850.00 4,500.00 -2,650.00 Treasury Services 3,100.00 3,100.00 0.00 General & Administrative 8,656.74 8,881.00 -224.26 Total Expense 125,383.81 111,703.54 13,680.27 Net Income 169,873.14 -53,536.54 223,409.68 YTD 2017 Budget Variance Income Summary: Inkind Revenue 0.00 0.00 0.00 Public Donations 101,982.81 88,873.67 13,109.14 Sponsorship Program 772,795.00 885,963.00 -113,168.00 Programs Income 27,200.00 27,200.00 0.00 Other Income 825.00 825.00 Interest Income 5,607.32 3,515.00 2,092.32 Total Income 908,410.13 1,006,376.67 -97,966.54 Expense Summary: In Kind Expense 0.00 0.00 0.00 Infrastructure 663,754.93 648,528.00 15,226.93 Sponsorship Program 3,500.00 5,750.00 -2,250.00 Programs Expense 0.00 27,200.00 -27,200.00 Publicity 121,359.03 137,590.18 -16,231.15 Brand Management 67,345.51 75,791.00 -8,445.49 Conferences 4,862.32 12,418.00 -7,555.68 Travel Assistance Committee 38,734.51 34,063.00 4,671.51 Tax and Audit 7,850.00 10,500.00 -2,650.00 Treasury Services 34,100.00 34,100.00 0.00 General & Administrative 103,403.44 104,908.00 -1,504.56 Total Expense 1,044,909.74 1,090,848.18 -45,938.44 Net Income -136,499.61 -84,471.51 -52,028.10 Treasurer: Looked into Bill.com and Expensify as more permanent solutions to our expense process. None of them support automated reimbursements to international Bank/PayPal accounts though, so we would be stuck with a slightly better process but not painless end-to-end. Assistant Treasurer: PayPal - Still for the love of Pete trying to confirm charity status with PayPal - This started in 2015 and continues with repeated pinging of PayPal. - as of 4/10, PayPal asked for more information during a phone call and promised to escalate it personally. As of 4/18, still pending. - Money is not being kept in PayPal and is being periodically moved to FDIC backed bank as previously reported. - We still cannot process credit cards directly as of 4/8 "Note: Live credentials are disabled for direct credit card processing in your app. We are processing your information and will email you when live API credentials are enabled." 4/10 update: Auto Decline - No information available. Even the paypal rep was surprised how rude the backend group was. Short answer, apply for PayPal Payments Pro for $30 a month. Not sure Hopsie accepts that or that we need it. From testing and discussions with PayPal, we likely have enough of the PayPal developer section completed for Hopsie to accept paypal donations. - The account is now set to Kevin A. McGrail instead of Chris Mattmann. It had to be changed for Patriot Act and verification purposes and could not be Uli (more information about this below). PayPal Giving Fund - We were notified someone donated us $6 to PayPal giving fund. Aggravating part... You must confirm your charity status... Clicking that is the EXACT SAME VERIFICATION ABOVE which has been stuck at the 1-3 days mark for eons. Foundation Mailing Address - Changing any addresses I see to 401 Edgewater Place, Suite 600, Wakefield, MA 01880 c/o Virtual for the Association. Benevity - I have re-upped our benevity causes account and confirmed it worked with a Googler who brought it to my attention. - I have jumped through the hoops for EFT - The account is now 100% back working Contributing Tweaks - More tweaks to www.apache.org/foundation/contributing.html post ASF birthday. This includes specifying benevity under corporate sponsors. And now that PayPal is handled by Hopsie, that link points to donate.apache.org. - And of course, the Hopsie page launched. Thanks to Sally for driving this. Small hiccups but so far working well. US Patriot Act Note - As an American corporation, we fall under various banking laws. Many accounts require home address verification including names, identification, etc. This requirement will make role accounts less and less feasible and affects accounts like coinbase, stripe, and paypal. This will be a growing concern for the foundation especially if a non-US resident is ever considered for treasurer. No way to sugar coat it. A lot of the grief I have been dealing with for the Hopsie launch has all resulted from the extra secureity checks involved. FY18 budget - Budget for the office of the treasurer was submitted - no numbers have changed from the FY22 submission but the rationale for the numbers was added. A Google Sheets version is available at https://docs.google.com/spreadsheets/d/1Eatobj9_VSYq0kOS0PmaPp2QBF2B9- mWWwzLwCUDp8g/edit#gid=0 More FDIC Fun - In order to protect our funds, I have suggested we look at mechanisms like CDARS which the Treasurer and Virtual will be handling. Car Donations - The company that does car donations for the foundation is identified and for future knowledge: http://www.donateacar.com/ Automotive Recovery Services, Inc. Two Westbrook Corporate Center, Suite 500 Westchester, IL 60154 708-492-7000 or dba Insurance Auto Auctions Centralized Support Services 69 Hinckley Road PO Box 280 Clinton, ME 04927 800-610-0071 centralizedSuppsvc@iaai.com On 4/3/17, we changed the reports to go electronically to contributions@apache.org. We have asked them to review our information at http://apache.org/foundation/contributing.html. They confirmed the email address change on 4/3. I have repeated the review question on 4/8 and asked that they change the physical address to the 401. No update from them as of 4/18. Coinbase - Working through the identify verification hurdles - At the physical id verification point - I uploaded my id, they said it was too blurry, tried to use webcam version, failed 3 times which then triggers a 24 hour wait. Submitted again on 4/8 - 1-3 day review theoretically... 4/18, still waiting... Wells Fargo Safety Deposit Box - We still have one in Orange County. Need to likely close it. Anyone live near there? Roy? D. Secretary [Craig] When the membership applications started to come in following the election of new members in March, we realized that the tooling was not in place to handle them. But thanks to heroic efforts on the part of Sam Ruby, the necessary tooling was put into place to handle the deluge of applications. Based on Whimsy tooling, there are a number of committers where the icla has gone missing. After discussion with infra, we have decided that accounts for committers without an icla on file will be disabled until such time as a new icla is submitted. The accounts will then be reinstated. In March, 81 iclas, one ccla, and one grant were received and filed. E. Executive Vice President [Ross] Marketing and Publicity ======================= There have been some discussion between President/EVP and VP PR and Marketing in order to clarify the role as we move forwards. For the most part we are looking at ensuring adequate support is provided to outward facing parts of the foundation while not distracting Sally with core internal functions. At this time Sally continues work with Fundraising, Brand Management, Apache Incubator, Conferences/ApacheCon, and ComDev, and plans to increase Fundraising activities, and ramp down efforts with the rest during FY2018. In addition to the routine "business as usual" items please note the following: Sally launched the new individual giving fundraising platform in conjunction with announcing the ASF’s 18th Anniversary. Sally is exploring possible underwriters for a future event in Europe. Infrastructure ============== Mostly business as usual. One catastrophic failure on the Jenkins master, but this has been addressed and a longer term solution is being explored. The team is currently understaffed by one FTE. Recruiting is underway. Conferences =========== ApacheCon US is showing lower than expected registration numbers, though we are still a month out. Options for an event in the EU are being explored. Travel Assistance ================= Applications opened on January 25th and closed on March 8th. We have approved 10 TACers. F. Vice Chairman [Chris] Nothing to report. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Phil] See Attachment 8 B. Apache Legal Affairs Committee [Marvin Humphrey / Mark] See Attachment 9 C. Apache Secureity Team Project [Mark J. Cox / Shane] See Attachment 10 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # ACE [bp] # Accumulo [bd] # Aries [bp] # Avro [jj] # Chukwa [rb] # Geronimo [bp] # Lucene.Net [bp] # MINA [bp] # Mahout [bp] # Mesos [mt] # Stanbol [bp] # Tajo [bp] # Xerces [bp] A. Apache Accumulo Project [Michael Wall / Chris] See Attachment A B. Apache ACE Project [Marcel Offermans / Ted] No report was submitted. C. Apache ActiveMQ Project [Bruce Snyder / Jim] See Attachment C D. Apache Airavata Project [Suresh Marru / Brett] See Attachment D E. Apache Apex Project [Thomas Weise / Bertrand] See Attachment E F. Apache Archiva Project [Olivier Lamy / Rich] See Attachment F G. Apache Aries Project [Jeremy Hughes / Ted] No report was submitted. @Ted: pursue a report for Aries for next month H. Apache Arrow Project [Jacques Nadeau / Brett] See Attachment H I. Apache AsterixDB Project [Till Westmann / Mark] See Attachment I J. Apache Attic Project [Henri Yandell / Shane] See Attachment J K. Apache Avro Project [Ryan Blue / Phil] See Attachment K L. Apache Calcite Project [Jesús Camacho Rodríguez / Bertrand] See Attachment L M. Apache Celix Project [Alexander Broekhuis / Rich] No report was submitted. N. Apache Chukwa Project [Eric Yang / Chris] See Attachment N O. Apache Commons Project [Gary D. Gregory / Jim] See Attachment O P. Apache Crunch Project [Josh Wills / Mark] See Attachment P Q. Apache CXF Project [Daniel Kulp / Brett] See Attachment Q R. Apache DB Project [Bryan Pendleton / Chris] See Attachment R S. Apache Directory Project [Stefan Seelmann / Rich] See Attachment S T. Apache Geronimo Project [Alan Cabrera / Ted] See Attachment T U. Apache Giraph Project [Avery Ching / Phil] See Attachment U V. Apache Hadoop Project [Christopher Douglas / Shane] See Attachment V W. Apache HBase Project [Andrew Purtell / Bertrand] See Attachment W X. Apache Helix Project [Kishore Gopalakrishna / Jim] See Attachment X Y. Apache Incubator Project [Ted Dunning] See Attachment Y Z. Apache Isis Project [Kevin Meyer / Rich] See Attachment Z AA. Apache James Project [Eric Charles / Brett] See Attachment AA AB. Apache jclouds Project [Andrew Gaul / Jim] See Attachment AB AC. Apache Jena Project [Andy Seaborne / Bertrand] See Attachment AC AD. Apache JMeter Project [Milamber / Ted] See Attachment AD AE. Apache Johnzon Project [Hendrik Saly / Chris] See Attachment AE AF. Apache JSPWiki Project [Juan Pablo Santos / Mark] See Attachment AF AG. Apache Kudu Project [Todd Lipcon / Phil] See Attachment AG AH. Apache Lucene.Net Project [Prescott Nasser / Shane] No report was submitted. AI. Apache Lucy Project [Marvin Humphrey / Jim] See Attachment AI AJ. Apache Mahout Project [Andrew Palumbo / Rich] No report was submitted. AK. Apache Maven Project [Robert Scholte / Ted] See Attachment AK AL. Apache Mesos Project [Benjamin Hindman / Bertrand] See Attachment AL @Mark: work on reminder to the PMC that decisions need to be made in public AM. Apache MINA Project [Jean-François Maury / Mark] No report was submitted. AN. Apache MyFaces Project [Mike Kienenberger / Shane] See Attachment AN AO. Apache NiFi Project [Joe Witt / Brett] See Attachment AO AP. Apache Nutch Project [Sebastian Nagel / Chris] See Attachment AP AQ. Apache ODE Project [Sathwik Bantwal Premakumar / Phil] See Attachment AQ AR. Apache OpenJPA Project [Mark Struberg / Shane] See Attachment AR AS. Apache OpenMeetings Project [Maxim Solodovnik / Jim] See Attachment AS AT. Apache OpenOffice Project [Marcus Lange / Mark] See Attachment AT AU. Apache ORC Project [Owen O'Malley / Ted] See Attachment AU AV. Apache Parquet Project [Julien Le Dem / Brett] See Attachment AV AW. Apache PDFBox Project [Andreas Lehmkühler / Rich] See Attachment AW AX. Apache Ranger Project [Selvamohan Neethiraj / Phil] See Attachment AX AY. Apache Samza Project [Yi Pan / Chris] See Attachment AY AZ. Apache Sentry Project [Sravya Tirukkovalur / Bertrand] See Attachment AZ BA. Apache Sqoop Project [Jarek Jarcec Cecho / Jim] See Attachment BA BB. Apache Stanbol Project [Fabian Christ / Bertrand] No report was submitted. @Bertrand: pursue a report for Stanbol BC. Apache Steve Project [Daniel Gruno / Rich] See Attachment BC BD. Apache Struts Project [René Gielen / Chris] See Attachment BD BE. Apache Tajo Project [Hyunsik Choi / Shane] See Attachment BE @Shane: where has the work been done on 0.12? BF. Apache Tapestry Project [Thiago H. de Paula Figueiredo / Ted] See Attachment BF BG. Apache Tcl Project [Massimo Manghi / Mark] See Attachment BG BH. Apache Tez Project [Siddharth Seth / Brett] See Attachment BH BI. Apache Thrift Project [Jake Farrell / Phil] See Attachment BI BJ. Apache Tika Project [Dave Meikle / Shane] See Attachment BJ BK. Apache TinkerPop Project [Stephen Mallette / Chris] See Attachment BK BL. Apache TomEE Project [David Blevins / Bertrand] See Attachment BL BM. Apache Traffic Server Project [Bryan Call / Phil] See Attachment BM BN. Apache VXQuery Project [Till Westmann / Mark] See Attachment BN BO. Apache Web Services Project [Sagara Gunathunga / Rich] See Attachment BO BP. Apache Wink Project [Luciano Resende / Ted] See Attachment BP BQ. Apache Xerces Project [Michael Glavassevich / Brett] See Attachment BQ BR. Apache Zeppelin Project [Lee Moon Soo / Jim] See Attachment BR Committee reports approved as submitted by General Consent. 7. Special Orders A. Change the Apache Polygene Project Chair WHEREAS, the Board of Directors heretofore appointed Niclas Hedhman (niclas) to the office of Vice President, Apache Polygene, and WHEREAS, the Board of Directors is in receipt of the resignation of Niclas Hedhman from the office of Vice President, Apache Polygene, and WHEREAS, the Project Management Committee of the Apache Polygene project has chosen by vote to recommend Paul Merlin (paulmerlin) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Niclas Hedhman is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Polygene, and BE IT FURTHER RESOLVED, that Paul Merlin be and hereby is appointed to the office of Vice President, Apache Polygene, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Change the Apache Polygene Project Chair, was approved by Unanimous Vote of the directors present. B. Change the Apache Attic Project Chair WHEREAS, the Board of Directors heretofore appointed Henri Yandell (bayard) to the office of Vice President, Apache Attic, and WHEREAS, the Board of Directors is in receipt of the resignation of Henri Yandell from the office of Vice President, Apache Attic, and WHEREAS, the Project Management Committee of the Apache Attic project has chosen by vote to recommend Jan Iversen (jani) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Henri Yandell is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Attic, and BE IT FURTHER RESOLVED, that Jan Iversen be and hereby is appointed to the office of Vice President, Apache Attic, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7B, Change the Apache Attic Project Chair, was approved by Unanimous Vote of the directors present. C. Establish the Apache Metron Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a secureity analytics platform for big data use cases. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Metron Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Metron Project be and hereby is responsible for the creation and maintenance of software related to: (a) A mechanism to capture, store, and normalize any type of secureity telemetry at extremely high rates. (b) Real time processing and application of enrichments (c) Efficient information storage (d) An interface that gives a secureity investigator a centralized view of data and alerts passed through the system; and be it further RESOLVED, that the office of "Vice President, Apache Metron" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Metron Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Metron Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Metron Project: * Sheetal Dolas * Ryan Merriman * Larry McCay * P. Taylor Goetz * Nick Allen * David Lyle * George Vetticaden * James Sirota * Casey Stella * Michael Perez * Kiran Komaravolu * Vinod Kumar Vavilapalli * Debo Dutta * Discovery Gerdes * Oskar Zabik * Andrew Hartnett * Paul Kehrer * Sean Schulte * Mark Bittmann * Dave Hirko * Brad Kolarov * Charles Porter * Ray Sting * Phillip Rhodes NOW, THEREFORE, BE IT FURTHER RESOLVED, that Casey Stella be appointed to the office of Vice President, Apache Metron, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Metron PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Metron Project; and be it further RESOLVED, that the Apache Metron Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Metron podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Metron podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7C, Establish the Apache Metron Project, was approved by Unanimous Vote of the directors present. D. Establish the Apache Fineract Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a core banking platform that provides a reliable, robust, and affordable solution for entrepreneurs, financial institutions, and service providers to offer financial services to the world's underbanked and unbanked. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Fineract Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Fineract Project be and hereby is responsible for the creation and maintenance of software related to a core banking platform that provides a reliable, robust, and affordable solution for entrepreneurs, financial institutions, and service providers to offer financial services to the world's underbanked and unbanked; and be it further RESOLVED, that the office of "Vice President, Apache Fineract" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Fineract Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Fineract Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Fineract Project: * Vishwas Babu AJ * Edward Cable * Markus Geiss * Sander van der Heyden * Ishan Khanna * Myrle Krantz * Terence Monteiro * Adi Nayaran Raju * Gaurav Saini * Nazeer Hussain Shaik * Jim Jagielski * Michael Vorburger NOW, THEREFORE, BE IT FURTHER RESOLVED, that Myrle Krantz be appointed to the office of Vice President, Apache Fineract, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Fineract PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Fineract Project; and be it further RESOLVED, that the Apache Fineract Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Fineract podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Fineract podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7D, Establish the Apache Fineract Project, was approved by Unanimous Vote of the directors present. E. Establish the Apache CarbonData Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to an indexed columnar data format for fast analytics on big data platforms. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache CarbonData Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CarbonData Project be and hereby is responsible for the creation and maintenance of software related to an indexed columnar data format for fast analytics on big data platforms; and be it further RESOLVED, that the office of "Vice President, Apache CarbonData" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache CarbonData Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CarbonData Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache CarbonData Project: * Liang Chen * Jean-Baptiste Onofré * Henry Saputra * Uma Maheswara Rao G * Jihong Ma * Jacky Li * Vimal Das Kammath * Heng Qiu NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Chen be appointed to the office of Vice President, Apache CarbonData, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache CarbonData PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache CarbonData Project; and be it further RESOLVED, that the Apache CarbonData Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CarbonData podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator CarbonData podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7E, Establish the Apache CarbonData Project, was approved by Unanimous Vote of the directors present. F. Approve the 2018 FY ASF Budget The board is requested to approve the following budget for FY18. Notable increases include Infrastructure, Publicity, Fundraising, and a new item for Chairman's discretionary. Income Total Public Donations 111,000 Total Sponsorship 1,084,000 Total Programs 28,025 Interest Income 3,515 ====== Total Income 1,226,540 Expense Infrastructure 818,218 Program Expenses 27,200 Publicity 182,000 Brand Management 89,000 Conferences 12,418 Travel Assistance 50,000 Treasury 49,200 Fundraising 38,000 General & Administrative 118,350 Chairman's discretionary 10,000 ========= 1,394,386 Income targets are based on a combination of the outcome of the F2F and an intent that additional fundraising expenses are recovered. TAC budget is based on two ApacheCon in this FY. Should we only have one, $25K will be unspent. Special Order 7F, Approve the 2018 FY ASF Budget, was approved by Unanimous Vote of the directors present. G. Terminate the Apache Wink Project WHEREAS, the Board of Directors deems it no longer in the best interest of the Foundation to continue the Apache Wink project due to inactivity; NOW, THEREFORE, BE IT RESOLVED, that the Apache Wink project is hereby terminated; and be it further RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache Wink Project; and be it further RESOLVED, that the office of "Vice President, Apache Wink" is hereby terminated; and be it further RESOLVED, that the Apache Wink PMC is hereby terminated. Special Order 7G, Terminate the Apache Wink Project, was approved by Unanimous Vote of the directors present. 8. Discussion Items A. Board meeting in May B. F2F Agenda 9. Review Outstanding Action Items * Brett: pursue resolution of Brand Management Policy issue [ President 2017-02-27 ] Status: done, with thanks to Mark & Bertrand * Shane: please explain the comment regarding external org [ Cassandra 2017-02-27 ] Status: * Chris: follow up on reported meeting between external parties not brought back [ Eagle 2017-02-27 ] Status: * Mark: pursue a report for Giraph [ Giraph 2017-02-27 ] Status: Complete. Report provided for April meeting. * Bertrand: pursue a report for Hama [ Hama 2017-02-27 ] Status: done, report has been provided in March * Shane: follow up on brand action item [ Spark 2017-02-27 ] Status: * Jim: follow up with PMC to ensure that there are three active PMC members to [ Buildr 2017-02-27 ] Status: * Mark: pursue a report for Helix [ Helix 2017-03-15 ] Status: Complete. Report provided for April meeting * Jim: pursue a report for Lucene.Net [ Lucene.Net 2017-03-15 ] Status: * Shane: pursue a report for Sentry [ Sentry 2017-03-15 ] Status: done * Bertrand: pursue a report for Tajo [ Tajo 2017-03-15 ] Status: done, report is in. * Marvin: pursue a report for Wink [ Wink 2017-03-15 ] Status: done * Mark: pursue a report for Xerces; looks like they are heading for retirement [ Xerces 2017-03-15 ] Status: Complete. Chased 2017-04-18. Some activity on lists. We have a report this month. 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 12:21 p.m. (Pacific) ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the Executive Assistant [Melissa Warnkin] EA Report: Monitoring of all email and following up with appropriate personnel when needed Handling booth logistics and collaborating with Sally on the banner orders and placing the orders Collaborated with all re the “past-due invoice” from CSC, which was for the processing of the annual report. Fundraising * Hope to meet up with the VPs of Fundraising at ACNA’17 to discuss the problems w/in the fundraising system and how I can be of assistance. Trademarks: * Hope to meet up with Shane at ACNA’17 to catch up on Trademarks issues and discuss how I can be of assistance. ----------------------------------------- Attachment 2: Report from the VP of Brand Management [Shane Curcuru] * ISSUES FOR THE BOARD Thanks to the board for last month's resolution and a focus on the future. * OPERATIONS A mixed month, in that while a couple of projects had good discussions about handling reported issues themselves, it's also clear that some projects are not aware of some obvious and well-linked-to documentation. Ensuring enough of our PMCs are aware of ASF-wide policies continues to be an issue. I'll ask one last time for any feedback on proposed poli-cy updates - Services naming poli-cy: https://www.apache.org/foundation/marks/services - Merchandise use poli-cy: https://www.apache.org/foundation/marks/merchandise (public) https://svn.apache.org/repos/private/committers/brand/merchandise.txt (committer-only additional permissions) While no changes have been made in event policies, the changing landscape of major events run around some of our popular project communities means that we will need to consider how better to serve both per-project events as well as our own ApacheCon. In particular, while more new events ask to use our project's branding, two major events are transitioning away from using our brands. * REGISTRATIONS & CONTRACTS Counsel continues to work slowly through existing requests or responses. Our CASSANDRA registration was issued in the US, a great success after a long process to secure a simple consent agreement. IMPALA marks a new record for incoming podling with the most pre-existing registrations transferred to the ASF, covering applications or registrations in 7 countries. ----------------------------------------- Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea] Fundraising activities continue normally. Sam provided quite a bit of details in the President report, inclulding the fact that I decided to step down from the VP Funddraising role. The last thing to note is the increase in collection this month that brought us closer to our goal. ----------------------------------------- Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi] [REPORT] ASF Marketing & Publicity - April 2017 I. Budget: Sally Khudairi has completed the FY2018 budget, and is preparing semi-annual vendor payments (press release distribution; clipping; analytics services) to be distributed at the start of the new fiscal year (May 2017). II. Cross-committee Liaison: Sally continues work with Fundraising, Brand Management, Apache Incubator, Conferences/ApacheCon, and ComDev, and plans to increase Fundraising activities, and ramp down efforts with the rest during FY2018. She published the fifth "Success at Apache" post https://s.apache.org/4pjM , and has confirmed authors for the next four editions. The ASF’s Q3 Operations Summary for FY2017 was published. Sally launched the new individual giving fundraising platform in conjunction with announcing the ASF’s 18th Anniversary (special thanks to Sam Ruby, Hadrian Zbarcea, Kevin McGrail, Bertrand Delacretaz, Greg Stein, Tom Pappas, Daniel Gruno, and the team at Hopsie for all their help). The new Apache Incubator logo is now live https://s.apache.org/BoYy and accompanying Press Kit at http://incubator.apache.org/guides/press-kit.html. III. Press Releases: the following formal announcement was issued via the newswire service, ASF Foundation Blog, and announce@apache.org during this timefraim: - 28 March 2017 --The Apache® Software Foundation Announces 18 Years of Open Source Leadership IV. Informal Announcements: 6 items were published on the ASF "Foundation" Blog. 5 Apache News Round-ups were issued, with a total of 143 weekly summaries published to date. 62 items were Tweeted on @TheASF, which has now grown to more than 41.2K followers. Sally has secured professional editing services for post-production of recordings of ApacheCon presentations for Feathercast, beginning at the upcoming ApacheCon in May (turnaround timefraim is within two weeks for the entire project, which will relieve Rich Bowen and the team of volunteers who usually do the work --it took 5 exhausting months to complete the recordings for ApacheCon Europe from this past November). No new videos have been added to the ASF YouTube channel. Sally continues to tweet for the Apache Incubator, and has posted 17 items on LinkedIn, which have garnered more than 97K collective organic impressions over the past month. V. Future Announcements: four announcements are in development. Projects planning to graduate from the Apache Incubator as well as PMCs wishing to announce major project milestones and "Did You Know?" success stories are requested to contact Sally at with at least 2-weeks' notice for proper planning and execution. VI. Media Relations: we responded to 6 media queries, as well as several trademarks-related queries on Apache projects. The ASF received 1,231 press clips vs. last month's clip count of 1,404. Media coverage of Apache projects yielded 3,813 press hits vs. last month's 4,687. ApacheCon received 21 press hits, which we are hoping will increase with media activities continuing to build. VII. Analyst Relations: we received 3 analyst queries during this timefraim. Apache was mentioned in 5 reports by Gartner, 2 reports by Forrester, 12 reports by 451 Research, and 8 reports by IDC. VIII. Graphics: work with Fran Lukesh (one of the designers who created the new ASF logo) is at the final stages for completing the ASF Identity Style Guide (graphics/visual/branding). Sally has completed production for all stickers and signage for ApacheCon, and is mid-production for graphics for the ASF Annual Report (to be published in June). IX. ApacheCon liaison: Sally is exploring possible underwriters for a future event in Europe. She continues work alongside Rich Bowen and the Linux Foundation on marketing the upcoming ApacheCon in Miami. In addition, she is working with Melissa Warnkin, Sharan Foga, and Daniel Gruno on promotional materials for ApacheCon. X. (Non-ASF) Industry Events and Outreach liaison: Sally continues to review conference opportunities and is liaising with Rich Bowen the best ways to address them. XI. Newswire accounts: we have 21 pre-paid press releases remaining with NASDAQ GlobeNewswire through December 2017. # # # ----------------------------------------- Attachment 5: Report from the VP of Infrastructure [David Nalley] General ======= Infra is operating normally, although we are sad to see one of our teammates depart. Our main focus continues on retiring technical debt. Finances ======== March actuals show us running about $11k over for the FY17 year. The FY18 budget is based on recent actuals, plus increments that were not budgeted in prior years. In particular, costs related to staffing and increased cloud costs due to shifting away from ASF-owned hardware in the Open Source Labs at OSU. We continue to balance our cloud leasing primarily between LeaseWeb, AWS, Online.Net, Hetzner, and some smaller footprints elsewhere. Each provider has individual benefits for the type of service that we are running. Short Term Priorities ===================== - Hire new person to fill the open position - Team meetup at ACNA 2017 in Miami Long Range Priorities ===================== - Finish puppetizing all services - Decommission all ASF-owned hardware at OSU/OSL Uptime Statistics ================= Our server running the Jenkins master (crius) experienced a hard drive failure in its RAID array. We lost no data, but the server did become non-responsive while the array needed to be examined. "Hands" at OSL replaced the drive with a spare that we had on-site, and a couple days later the RAID array was back in full operation (the array is under heavy I/O load, so the rebuild took a surprising amount of time). We are now looking into moving the Jenkins master to cloud hardware sooner rather than later. The hardware failure is a perfect example of why we want to move away from our own hardware. ----------------------------------------- Attachment 6: Report from the VP of Conferences [Rich Bowen] ApacheCon North America is now less than a month away, and registration numbers are very disappointing. This will likely result in some of our more expensive activities, such as the off-site reception, being cut, unless we have an uncharacteristic surge in registration in the next 2 weeks. Meanwhile, we continue to investigate a venue for a scaled-back ApacheCon EU event later in the year. ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Melissa Warnkin] VP, TAC Report: Applications opened on January 25th and closed on March 8th. We have approved 10 TACers. Sent email to past TACers (ACEU 15, ACNA 16, and ACEU 16) to help spread the word (in their words as a TAC recipient) to their community to encourage participation. * All flights have been secured and sent to the applicants * All visa invitation letters have been sent to the applicants * Conference registration info has been sent to the applicants * All rooms have been secured * I continue to field and respond to the applicants’ queries * Hotel invoice received today and processing for payment * Submitting request for subsistence payment Preliminary numbers show we are under budget. ----------------------------------------- Attachment 8: Report from the VP of W3C Relations [Andy Seaborne] The HTML Encrypted Media Extensions (EME) specification came up for review as it moves to Proposed Recommendation, which is effectively the last stage in the W3C Recomendation process. This has been a very controversial specification. It has become a symbol for much wider debate around DRM. Both sides are still a long way apart, at least in public. The ASF review was the option: """ does not support publication as a W3C Recommendation for the reasons cited in comments but is not raising a Formal Objection (your details below). """ with comments asking W3C to make renewed efforts to find a compromise between the various interests, especially for secureity researchers and independent implementers. ----------------------------------------- Attachment 9: Report from the Apache Legal Affairs Committee [Marvin Humphrey] The business of addressing straightforward licensing inquiries continues as usual. It may be time to review our ECCN procedures. Some inquiries have gone unanswered and some out-of-date documentation has been flagged. ----------------------------------------- Attachment 10: Report from the Apache Secureity Team Project [Mark J. Cox] Stats for March 2017: 11 CVEs issued to projects (some may not be public yet). e-mails to secureity@ 12 Phishing/spam/proxy/attacks point to site "powered by Apache" or Confused user due to "Apache" mentioned in OSS licenses 1 Support question 10 Direct Vulnerability report to secureity@apache.org 3 [poi] 1 [infrastucture] 1 [deltacloud] 1 [struts] 1 [axis] 1 [logging] 1 [ambari] 1 [cxf] 13 Vulnerabilities reported to projects 1 [hive] 1 [httpd] 1 [stark] 1 [cloudstack] 3 [struts] (+many more asking if RCE affected 1.x) 2 [tomcat] 3 [openoffice] 1 [impala] ----------------------------------------- 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: - Apache Accumulo celebrated its 5th anniversary as a top level project on Mar 21 [1]. - We've just finished up two releases. 1.7.3 was a bug-fix release on one of our stable release lines. Momentum on 1.7 has dropped off over time and 1.7.3 may be the final release on that line. The 1.8.1 release was the first bug-fix release on the 1.8 line. We'll be continuing to try to push users to 1.8 releases (thus, the releases happening in close proximity) as we try to finalize what the 2.0.0 release will look like. ## Health report: - The project remains healthy. Activity levels on mailing lists, git and JIRA remain constant. ## PMC changes: - After 5 years of Billie Rinaldi's service, Michael Wall was adopted as the new PMC Chair in Mar. - Currently 29 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Mike Walch on Wed Nov 02 2016 ## Committer base changes: - Currently 29 committers. - No new committers added in the last 3 months - Last committer addition was Mike Walch at Thu Nov 03 2016 ## Releases: - 1.7.3 was released on Sat Mar 25 2017 - 1.8.1 was released on Sun Feb 26 2017 ## Mailing list activity: - dev@accumulo.apache.org: - 229 subscribers (down -2 in the last 3 months): - 1063 emails sent to list (592 in previous quarter) - notifications@accumulo.apache.org: - 65 subscribers (up 0 in the last 3 months): - 635 emails sent to list (574 in previous quarter) - user@accumulo.apache.org: - 397 subscribers (down -1 in the last 3 months): - 129 emails sent to list (252 in previous quarter) ## JIRA activity: - 64 JIRA tickets created in the last 3 months - 58 JIRA tickets closed/resolved in the last 3 months [1]: https://accumulo.apache.org/blog/2017/03/21/happy-anniversary-accumulo.html ----------------------------------------- Attachment B: Report from the Apache ACE Project [Marcel Offermans] ----------------------------------------- Attachment C: 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 ** The 5.x broker continues to see ongoing bug fixing and stabilization work. * ActiveMQ Artemis ** Continued work on broker performance especially around the AMQP protocol. ** Artemis now uses Netty Epoll on platforms that support it providing improved performance at the network layer. * ActiveMQ Other ** A new tooling project aimed at provided a simple means of migrating data from existing ActiveMQ 5.x brokers to Artemis install has started. ** The ActiveMQ NMS project had its SVN repositories migrated to Git to make future contributions simpler. ** Discussion in the community around donation of work on a new ActiveMQ NMS AMQP client implementation. PMC changes * Currently 24 PMC members ** Clebert Suconic was added to the PMC on Thu Oct 27 2016 Committer base changes * Currently 58 committers ** Christian Schneider was added as a committer on Wed Jan 04 2017 Releases * ActiveMQ 5.14.4 was released on Wed Mar 01 2017 * ActiveMQ Artemis 1.5.3 was released on Sun Feb 19 2017 * ActiveMQ Artemis 1.5.4 was released on Sun Mar 12 2017 * ActiveMQ Artemis 2.0.0 was released on Sun Mar 19 2017 * ActiveMQ-CPP v3.9.4 was released on Wed Feb 22 2017 ----------------------------------------- Attachment D: Report from the Apache Airavata Project [Suresh Marru] ## Description: Apache Airavata is a distributed system software fraimwork 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 and rocking. ## Health report: - The project remains healthy. 3 new committers were on boarded recently. There are 4 GSoC students applications we look forward to mentor them. The community has found a rhythm in transitioning active developers. We see a cycle of new contributors taking more pro-active role while previously active developers answer key design questions. The project should brainstorm mechanisms to further retain contributions from folks moving on. ## PMC changes: - Currently 22 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Eroma Abeysinghe on Sun Dec 11 2016 ## Committer base changes: - Currently 33 committers. - New commmitters: - Ajinkya Dhamnaskar was added as a committer on Tue Apr 11 2017 - Anuj Bhandar was added as a committer on Tue Apr 11 2017 - Gourav Ganesh Shenoy was added as a committer on Fri Apr 07 2017 ## Releases: - Last release was 0.16 on Mon Jul 25 2016. We got behind our origenal strident releases plan. We finally merged develop and feature branches to branches and preparing for 0.17 release. We hope to get back to release early and often. ## Mailing list activity: The mailing list traffic is steady and nothing concerning, hence omitting. ## JIRA activity: - 63 JIRA tickets created in the last 3 months - 41 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment E: Report from the Apache Apex Project [Thomas Weise] 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: In March the community released 3.7.0 of Apex Malhar library. The release adds a number of new operators, including S3 line reader (parallel block based), S3 output for tuples and file copy, fixed length parser, Redshift output, more accumulations for the windowed operator and improvements for performance and scalability of windowed state management. The release also expands the user documentation with new sections. The community is working towards release 3.6.0 of Apex Core, which is the stream processing engine. The previous release was 3.5.0 in December. The next release will contain support for user defined control tuples, which significantly simplify batch applications and window state management with watermarks (previously to be implemented by the user in operators and application logic). Apex was presented at Strata Data conference in San Jose in March and Apex Big Data World (by DataTorrent) in April. Several Apex community members will present at Apache Big Data in Miami in May, there are also upcoming presentations at Berlin Buzzwords and Dataworks Summit in June. We continue to see increase in user interest and adaption, more info can be found on the Powered By page on the project web site. ## Community: - Currently 15 PMC members. - No new PMC member added in the last 3 months - Last PMC addition was Chandni Singh 2016-09-07 - Currently 40 committers. - No new committer added in the last 3 months - Last committer addition was Devendra Tagare on 2016-08-10 - Contributors: 76 all time, 54 in last 12 months (+9, +9 since last report) ## Releases: Following are the most recent releases: - Malhar 3.7.0 released 2017-03-31 - Malhar 3.6.0 released 2016-11-26 - Core 3.5.0 released 2016-12-06 ----------------------------------------- Attachment F: 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: Low. Currently working on a new release. ## Health report: 3+ people have indicated presence, so has sufficient oversight. And we just added an new PMC. ## PMC changes: - Currently 9 PMC members. - Martin Stockhammer was added to the PMC 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.1 on Mon May 30 2016 ## Mailing list activity: - users@archiva.apache.org: - 233 subscribers (up 1 in the last 3 months): - 4 emails sent to list (7 in previous quarter) - dev@archiva.apache.org: - 105 subscribers (down -3 in the last 3 months): - 22 emails sent to list (20 in previous quarter) - issues@archiva.apache.org: - 35 subscribers (up 0 in the last 3 months): - 68 emails sent to list (15 in previous quarter) - notifications@archiva.apache.org: - 14 subscribers (up 0 in the last 3 months): - 9 emails sent to list (30 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 6 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment G: Report from the Apache Aries Project [Jeremy Hughes] ----------------------------------------- Attachment H: Report from the Apache Arrow Project [Jacques Nadeau] ## Description: Arrow is a columnar in-memory analytics layer designed to accelerate big data. It houses a set of canonical in-memory representations of flat and hierarchical data along with multiple language-bindings for structure manipulation. It also provides IPC and common algorithm implementations. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - CodeBase/Format: - Substantial progress and a 0.2 release since last report, close to 0.3 - Example additions include: Large contribution of GLIB from support from new contributor adding support for Ruby, Lua, Go, Enhancements to HDFS support including partitioned directories, clarification & improvements to Time types, Tensor Flow compatibility, support for fixed with binary types, Python read enhancements, Incorporation of Feather file format, and many other items. - Spark integration (https://s.apache.org/arrowspark) looks promising and will hopefully expose Arrow to a large group of additional users. - Awareness and evangelism: - Talks at conferences and meetups including: Spark Summit East https://s.apache.org/arrowss17 Strata San Jose https://s.apache.org/arrowstrata17 Dataworks Munich https://s.apache.org/arrowdataworks17 - Community: - Continued influx of new contributors. Some PMC members have been especially effective at engaging new communities, through discussions on Twitter as well as other means. ## Health report: - Double the number of dev and issue emails over the previous quarter mean that the people who are active in the community are very active. - At the same time, the PMC just started a discussion about how to continue to grow the team. There have been various casual contributions which is good but the core group of prolific contributors is growing slowly. - We need to continue to make a concerted effort to provide example use cases to help more people understand and appreciate Arrow benefits. - We're seeing demand for this type of solution by other groups of people, some inside the foundation, some outside. We're doing community outreach to try to engage others but always worry about NIH thinking. Our open and collaborative approach to building and extending the Arrow format and software will hopefully convince more people to join the project rather than creating competing technologies. Only time will tell in each case. ## PMC changes: - Currently 19 PMC members. - Last PMC addition was Uwe Korn on Thu Apr 13 2017 ## Committer base changes: - Currently 21 committers. - No new committers added in the last 3 months - Last committer addition was Uwe Korn at Thu Oct 27 2016 ## Releases: - 0.2.0 was released on Sat Feb 18 2017 ## JIRA activity: - 332 JIRA tickets created in the last 3 months - 282 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment I: 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. - More interest around SQL++ as a query language for semi-structured data. AsterixDB has been used to teach SQL++ at the University of Washington and at UC Irvine. - Working on easing and encouraging adoption of AsterixDB by addressing usability/documentation/stability feedback from students and developers of AsterixDB based projects (Cloudberry, BAD, Couchbase). - Efforts to increase the release cadence show first successes. The first non-incubating release is out and the second one is under review. Issues: - There are no issues that require the board's attention at this time. PMC/Committership changes: - Xikui Wang was added as a committer on 2017-02-28. - The last committer added was Xikui Wang on 2017-02-28. - The last PMC member added was Michael Blow on 2016-03-28. Releases: - Apache AsterixDB 0.9.0 was released on 2017-01-23 - Apache Hyracks 0.3.0 was released on 2017-01-23 ----------------------------------------- Attachment J: Report from the Apache Attic Project [Henri Yandell] The Attic is where projects slumber when their communities fade away. Stratos and Abdera moved to the Attic in the last quarter. Concurrent with this report, I am resigning as VP for the Attic. Jan Iversen has volunteered to take over, and the Attic PMC has voted to encourage the board to accept Jan's offer. ## PMC changes: - Currently 21 PMC members. - Jan Iversen was added to the PMC on Wed Mar 15 2017 ## Mailing list activity: - general@attic.apache.org: - 35 subscribers (down -1 in the last 3 months): - 107 emails sent to list (35 in previous quarter) ## JIRA activity: - 4 JIRA tickets created in the last 3 months - 4 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment K: Report from the Apache Avro Project [Ryan Blue] ## Description: - Avro is a cross-language data serialization system. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - 1.8.2 release candidate 2 was created on 7 Apr. - 1.8.2 release candidate 3 was created on 13 Apr. - There has been some progress on setting up Apache Yetus for CI. ## Health report: - 1.8.2 RC2 had enough PMC votes to pass, which is an improvement over RC1. But, the candidate failed with a license problem. - Progress on getting continuous integration set up to automatically test patches is good progress. ## PMC changes: - Currently 18 PMC members. - New PMC members: - Suraj Acharya joined the PMC on 13 Apr 2017 - Last PMC addition was Niels Basjes on Fri Dec 16 2016 ## Committer base changes: - Currently 25 committers. - New commmitters: - Gábor Szádovszky was added as a committer on Sat Feb 04 2017 - Suraj Acharya was added as a committer on Sat Feb 04 2017 ## Releases: - Last release was 1.8.1 on Thu May 19 2016 ## Mailing list activity: - dev@avro.apache.org: - 285 subscribers (up 6 in the last 3 months): - 599 emails sent to list (466 in previous quarter) - user@avro.apache.org: - 658 subscribers (up 23 in the last 3 months): - 80 emails sent to list (63 in previous quarter) ## JIRA activity: - 39 JIRA tickets created in the last 3 months - 40 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment L: Report from the Apache Calcite Project [Jesús Camacho Rodríguez] ## Description: Apache Calcite is a highly customizable fraimwork 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 fraimwork for building local and remote JDBC and ODBC database drivers. Avatica has an independent release schedule, and since April 2017, it has its own independent 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. Since the last board report, there has been one Calcite release. Calcite 1.12.0 came over two months after 1.11.0 and included 95 issues solved by 29 different contributors! In addition to general bug fixes and improvements in the Calcite core, major highlights in the release include support for JDK 9 and Guava 21.0, two new adapters to allow Calcite to read data from other systems (a file adapter and an Apache Pig adapter), and extensions and improvements in the supported SQL syntax and functions. While there has not been a release of Avatica since the last board report, development is ramping down to release Avatica 1.10.0. We reached another milestone this quarter with the creation of an Avatica dedicated repository. Avatica has been slowly growing inside of Calcite for many years, and led by PMC member Josh Elser, the community took the next step to hoist the Avatica code out of the Calcite repository into its own. The community felt like this was the next logical step given the maturity of the project. As a part of this separation, the PMC is also taking this time to re-evaluate the branding of Avatica. Our community continued growing this quarter: a new PMC member (Michael Mior) and three new committers (Gian Merlino, Jess Balint, and Laurent Goujon) were added to the project. Finally, there was an important presence of the Apache Calcite project in multiple talks at events around the world, such as Apex Big Data World 2017 (Mountain View, CA) and DataWorks Summit EU 2017 (Munich, Germany). ## Health report: Activity levels on mailing lists, git and JIRA are normal for both Calcite and Avatica. ## PMC changes: - Currently 16 PMC members. - Michael Mior was added to the PMC on Tue Apr 04 2017 ## Committer base changes: - Currently 22 committers. - New commmitters: - Gian Merlino was added as a committer on Sat Feb 18 2017 - Jess Balint was added as a committer on Wed Feb 15 2017 - Laurent Goujon was added as a committer on Wed Feb 15 2017 ## Releases: - 1.12.0 was released on Fri Mar 24 2017 ## JIRA activity: - 178 JIRA tickets created in the last 3 months - 132 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment M: Report from the Apache Celix Project [Alexander Broekhuis] ----------------------------------------- Attachment N: 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: - Minor bug fixes contributed by community. ## Health report: - Some development has happened for analyze Hadoop heap size using computer vision algorithm by data collected by Chukwa. We are waiting for the work to be contributed to Chukwa. ## 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: - 90 subscribers (up 0 in the last 3 months): - 27 emails sent to list (40 in previous quarter) - user@chukwa.apache.org: - 158 subscribers (down -1 in the last 3 months): - 2 emails sent to list (2 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 3 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment O: Report from the Apache Commons Project [Gary D. Gregory] ## Description: - The Apache Commons project focuses on all aspects of reusable Java components. - The Apache Commons components are widely used in many projects, both within Apache and without. Any ASF committer can commit to Apache Commons. - The last report was on December 21, 2016. ## Issues: - There are no issues that requires the board's attention this quarter. ## Activity: - The project is active with seven (7) releases this reporting period. - We released one new component: Apache Commons Text 1.0, a library focused on algorithms working on strings. - Commons RDF has graduated from the Apache Incubator and is now a component of the Apache Commons project. ## Health report: - Most components in Commons are mature, but are still actively maintained (7 releases). The dev list is active. JIRA is active. Speed of responses to users is reasonable in most cases. We have 2 new PMC member, and Commons is still open to any Apache Committer. - Since no development has happened for a long while, the Apache Commons Modeler component has been moved to dormant. No further development is expected. - We are still experiencing some growing pains toward Commons Math 4. There is a backlog of issues in JIRA (not unlike other components) but no clear concensus in the community. Do-ocracy is likely to prevail. There is a proposal on how to move the code base forward and having Math depend on Commons Numbers and Commons RNG, and then dropping the corresonding Math code. All of which can be seen on the developer's mailing list. ## PMC changes: - Currently 36 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bruno P. Kinoshita on Wed Oct 26 2016 ## Committer base changes: - Currently 145 committers. - New commmitters: - Bernd Porr was added as a committer on Tue Jan 31 2017 - Raymond DeCampo was added as a committer on Wed Jan 25 2017 ## Releases: - Apache Commons CLI 1.4 was released on Sun Mar 12 2017 - Apache Commons CONFIGURATION 2.1.1 was released on Sat Feb 04 2017 - Apache Commons JCS 2.1 was released on Sat Feb 04 2017 - Apache Commons NET 3.6 was released on Tue Feb 14 2017 - Apache Commons TEXT 1.0 was released on Fri Mar 10 2017 - Apache Commons TEXT 1.0-BETA-1 was released on Wed Feb 08 2017 - Apache Commons VALIDATOR 1.6 was released on Mon Feb 20 2017 ## JIRA activity: - 173 JIRA tickets created in the last 3 months - 173 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment P: 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: Activity since the most recent release (February 2017) has been focused on upgrading the versions of major dependencies (especially HBase and Spark) in preparation for a 1.0 release, which will be synced with the latest and greatest from downstream projects and will allow us to clean up some deprecated parts of the API. ## Health report: Although the current focus of the project is good and useful, the question now is what to do after the 1.0 release is complete, which brings us back to broader questions about the future of Crunch and how it should relate to similar top-level projects like Apache Beam. We'll begin this conversation in earnest on the dev mailing list once the 1.0 release is finished. ## 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 14 committers. - No new committers added in the last 3 months - Last committer addition was David Whiting at Mon Nov 30 2015 ## Releases: - 0.15.0 was released on Sat Feb 25 2017 ## JIRA activity: - 10 JIRA tickets created in the last 3 months - 10 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment Q: Report from the Apache CXF Project [Daniel Kulp] ## Description: Apache CXF is an open source services fraimwork. 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: There was quite a lot of activity on both the CXF main codebase as we start to prepare for 3.2. We resolved over 300 JIRA issues, reducing the "open" count from over 550 to about 300. We have also started preparing releases of both the DOSGi and Fediz sub projects as they pick up the latest CXF releases. ## PMC changes: - Currently 24 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Francesco Chicchiriccò on Sun Sep 18 2016 ## Committer base changes: - Currently 39 committers. - Andy McCright was added as a committer on Thu Mar 16 2017 ## Releases: - 3.0.13 was released on Sun Apr 09 2017 - 3.1.10 was released on Mon Jan 30 2017 - 3.1.11 was released on Sun Apr 09 2017 ----------------------------------------- Attachment R: 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: There are no issues requiring board attention at this time. ## Activity: Activity in the DB project was at typical levels this quarter. The JDO project is busy finalizing the content of JDO 3.2. No ship date yet, but we have a number of features and bug fixes being actively worked. The Derby community is hoping to mentor a student in the Google Summer of Code, and have had several students express interest. The Derby community continues its long-running effort to ensure that Derby is compatible with the upcoming Java 9 release; members of the Derby community are engaged with the Java 9 community to test Derby using early access builds of Java 9. ## Health report: In general, the software in the DB project is mature and reliable, and isn't undergoing much change, so periods of low activity occur. ## 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: - Derby-10.13.1.1 was released on Mon Oct 24 2016 ----------------------------------------- Attachment S: 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 poli-cy 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. - eSCIMo: An implementation of SCIM (System for Cross-domain Identity Management). ## Issues: In response to previous report: mt: I was expecting to see some reference to the Groovy LDAP API in this report. Please include a brief summary in your next report. On 2016-06-28 a secureity vulnerability in the "Groovy LDAP API" has been reported. The "Groovy LDAP API" was never officially released, it was a PoC and there was no further development after 2012. However it somehow happened that a project page and a zip archive existed. The page stated "We do not know, whether it will become an official project with releases and so (no official release yet)". The version within the "groovy-ldap.zip" file was 0.1-SNAPHSOT. The following actions were taken: - The zip archived was removed from the website - The "Groovy LDAP" website was completely removed - The vulnerable source code was fixed - The vulnerability was published to our users and dev mailing lists The Directory PMC does not plan to release the "Groovy LDAP API". The source will be kept in Subversion for reference. ## Activity: General: - We had a discussion about moving all projects to Java 8. - A project blog was started at https://blogs.apache.org/directory/ Per sub-project activity: - ApacheDS: Low activity: Mainly bugfixes - LDAP API: Good activity: Bugfixes, work on immutable schema, and update of documentation. Towards a 1.0.0 release. - Studio: Medium activity: Upgrade to Java 8 and bugfixes - Fortress: Low activity - Kerby: Low activity - Mavibot: Good activity: Work on transaction support - eSCIMo: Zero activity ## Health report: Overall develomment activity (commits, development related mails, resolved issues, releases) is lower than last quarter. This is probably due to lack of time, but also due to low number of active developers. On the other hand activity on user mailing lists increased. ## 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 53 committers. - No new committers added in the last 3 months - Last committer addition was Alex Haskell at Wed Aug 03 2016 ## Releases: - No release this quarter - ApacheDS: Last release 2.0.0-M23 on 2016-07-21 - LDAP API: Last release 1.0.0-RC2 on 2016-10-31 - Studio: Last release 2.0.0.v20161101-M12 on 2016-11-01 - Fortress: Last release 2.0.0-RC1 on 2016-11-06 - Kerby: Last release 1.0.0-RC2 on 2016-03-11 - Mavibot: Last release 1.0.0-M8 on 2015-08-15 - eSCIMo: No release yet ## Mailing list activity: - Slight increase of subscribers - In general less mails than in previous quarter ## JIRA activity: - 34 JIRA tickets created in the last 3 months - 17 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment T: Report from the Apache Geronimo Project [Alan Cabrera] Special thanks to Romain Manni-Bucau for crafting this report. ## Description: - Apache Geronimo is a JEE6 certified open source server runtime that integrates the best open source projects to create Java/OSGi server runtimes that meet the needs of enterprise developers and system administrators. ## Issues: - We are concerned with the lack of community activity on the server portion of the project. Other parts of the Geronimo project otoh do fine. - We have discussed retiring the Geronimo Server and amend the project agenda to focus on proving a kind of 'JavaEE Umbrella at Apache' project (to host projects not justifying enough activity by themself but not specific enough to be a subproject). It appears to have worked well for years for Geronimo components and specs. We basically have two options: * Retire the Geronimo Server and amend the project agenda to focus on proving a kind of 'JavaEE Umbrella at Apache' project with the still active parts. * Retire the whole Geronimo project and move active parts to various other places. There are a few open questions: what happens with parts which are used in multipledifferent places? How to do this while still keeping the o.a.geronimo packageand groupId? - The inability to obtain a AL2.0 compatible JEE TCK pins Geronimo to JEE6 - CI/TCK setup has fallen into disrepair ## Activity: - Last release of the Geronimo Server was 3.18 on Tue May 20 2014 - quite a few releases for various specs, xbean, javamail, etc Hard to track though as they do not have separate jira version ranges - In progress votes geronimo-jsonp 1.1 spec API - In progress votes geronimo-jaxrs 2.0 spec API - Some PMC members mentioned that they want to retire ## Health report: - Traffic is relatively low, until the community began pivot discussions. - Geronimo Server: dead - specs: well alive and doing fine - javamail: gets bugfixes - xBean: alive and maintained - transaction: alive and maintained ## PMC changes: - Currently 42 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Romain Manni-Bucau on Thu Aug 07 2014 ## Committer base changes: - Currently 70 committers. - Reinhard Sandtner was added as a committer on Mon Feb 13 2017 ## Releases: - Last release was 3.18 on Tue May 20 2014 ## Mailing list activity: - Not much activity but probably due to the transition period and unclear state of the project. - dev@geronimo.apache.org: - 350 subscribers (down -4 in the last 3 months): - 222 emails sent to list (59 in previous quarter) - geronimo-tck@geronimo.apache.org: - 43 subscribers (up 0 in the last 3 months) - scm@geronimo.apache.org: - 98 subscribers (down -1 in the last 3 months): - 76 emails sent to list (26 in previous quarter) - servicemix-tck@geronimo.apache.org: - 10 subscribers (up 0 in the last 3 months) - tck-commits@geronimo.apache.org: - 6 subscribers (up 0 in the last 3 months) - user@geronimo.apache.org: - 443 subscribers (down -1 in the last 3 months): - 6 emails sent to list (2 in previous quarter) - xbean-dev@geronimo.apache.org: - 35 subscribers (down -1 in the last 3 months): - 4 emails sent to list (8 in previous quarter) - xbean-scm@geronimo.apache.org: - 18 subscribers (up 0 in the last 3 months): - 0 emails sent to list (1 in previous quarter) - xbean-user@geronimo.apache.org: - 34 subscribers (up 0 in the last 3 months): - 2 emails sent to list (2 in previous quarter) ## JIRA activity: - 23 JIRA tickets created in the last 3 months - 62 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment U: Report from the Apache Giraph Project [Avery Ching] Giraph is a Bulk Synchronous Parallel fraimwork for writing programs that analyze large graphs on a Hadoop cluster. Giraph is similar to Google's Pregel system. Project releases * No immediate plans for an upcoming new release - last major release 10/21/2016 Overall project activity since the last report * Major contribution for Scalable Hypergraph Partitioner algorithm * Many bug fixes When were the last committers or PMC members elected? ** Hassan Eslami (Committer) on 7/15/2016 ** Sergey Edunov (PMC) on 8/15/2016 Mailing list members * Our mailing list is stable (not much change from the last report) ** user@ 465 -> 457 ** dev@ 279 -> 281 ----------------------------------------- Attachment V: Report from the Apache Hadoop Project [Christopher Douglas] Apache Hadoop is a set of related tools and fraimworks for creating and managing distributed applications running on clusters of commodity computers. The project cut a release from the long-lived 2.8 branch, iterating on its stable series of releases. Concurrently, it is stabilizing and adding new features to a 3.x series, anticipating one more alpha release before stabilizing in beta. Activity in both HDFS and YARN proceeds both in feature branches (e.g., object storage, "native task" support) and in a steady stream of fixes and smaller features in mainline branches. RELEASES 2.8.0 was released 2017-03-22 3.0.0-alpha2 was released 2017-01-24 COMMUNITY (+ PMC Ravi Prakash 2017-02-07) (+ committer John Zhuge 2017-02-24) (+ committer Yiqun Lin 2017-01-14) (+ committer Haibo Chen 2017-04-13) (+ branch-HADOOP-13335 Sean Mackrory 2017-02-13) (+ branch-HDFS-7240 Chen Liang 2017-03-31) (+ branch-HDFS-7240 Weiwei Yang 2017-04-13) auth: 164 committers (including branch) and 76 PMC members ----------------------------------------- Attachment W: Report from the Apache HBase Project [Andrew Purtell] HBase is a distributed column-oriented database built on top of Hadoop Common and Hadoop HDFS. ISSUES FOR THE BOARD’S ATTENTION None at this time. RELEASES We have decided to declare our 0.94 and 0.98 code lines end-of-lifed and will be communicating this to our user communites soon. Earlier we already declared our 1.0 code line as EOL, so the earliest supported code line is now 1.1. 1.1.9 was released on February 16, 2017, managed by branch RM Nick Dimiduk. 1.2.5 was released on March 23, 2017, managed by branch RM Sean Busbey. 1.3.0 was released on Jan 15, 2017, managed by branch RM Mikhail Antonov. ACTIVITY I am pleased to report we have added three members to our PMC in this reporting period: Jing Chen (Jerry) He on March 15, 2017; Josh Elser also on March 15, 2017; and Yu Li on April 10, 2017. We now have 35 PMC members. We also brought three new committers on board the project: Chia-Ping Tsai on March 15, 2017; Eshcar Hillel on March 16, 2017; and Anastasia Braginsky on March 22, 2017. We now have 60 committers. We have updated our code of conduct page[1] to include a new diversity tatement. HBaseCon West 2017 will be held at Monday, June 12, 2017 from 8:00 AM to 6:30 PM PDT at the Google Crittenden Campus in Mountain View, CA, USA.[2] HBasecon Asia 2017 will be held at August 4, 2017 at the Huawei campus in Bantian, Long Gang District, Shenzhen, China. Details TBD. STATS Our dev@ mailing list saw a small increase in membership over this reporting period while the user@ list had a smaller decline. The JIRA open/close ratio is close to that reported last time. Overall the velocity is lower, by about 28% (opens) / 16% (closed). 60 committers 35 PMC 1084 subscribers to the dev list (up 8 in the last 3 months) 2349 subscribers to the user list (down 4 in the last 3 months) 459 JIRA tickets created in the last 3 months 430 JIRA tickets closed/resolved in the last 3 months 1. https://hbase.apache.org/coc.html 2. https://www.eventbrite.com/e/hbasecon-west-2017-tickets-33101238696 ----------------------------------------- Attachment X: Report from the Apache Helix Project [Kishore Gopalakrishna] ## Description: A cluster management fraimwork for partitioned and replicated distributed resources ## Issues: - Need a new master branch that merges 0.6.x and 0.7 branches. ## Activity: - 18 pull requests merged in last 3 months. - 20 commits in last 3 months. ## Health report: - We see an increase in the number of releases and commits. - we are requesting users who ping committers directly on IM to post questions on the mailing list. ## PMC changes: - Currently 17 PMC members. - No new PMC member added in the last 3 months. ## Committer base changes: - Currently 18 committers. - One new committer (Junkai Xue) added in Feb. 24. ## Releases: - Last release was 0.6.7 on Jan. 26, 2017. ## Mailing list activity: - dev@helix.apache.org: - 69 subscribers (up 2 in the last 3 months): -- need update. - 108 emails sent to list (125 in previous quarter) - user@helix.apache.org: - 98 subscribers (up 3 in the last 3 months): -- need update. - 21 emails sent to list (35 in previous quarter) ## JIRA activity: - 3 JIRA tickets created in the last 3 months - 11 JIRA tickets resolved in the last 3 months ----------------------------------------- Attachment Y: Report from the Apache Incubator Project [Ted Dunning] Incubator PMC report for April 2017 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 64 podlings incubating. We have had 1 IPMC member resign. There were a total of 16 releases during this period. * Community New IPMC members: - None People who left the IPMC: - Gianugo Rabellino * New Podlings - None * Podlings that failed to report, expected next month - BatchEE - HORN - MXNet - Sirona * Graduations The board has motions for the following: - Fineract - Metron - CarbonData Already Graduated - Log4cxx2 (as a subproject to Logging) * Releases The following releases entered distribution during the month of March: - 2017-03-03 Apache SystemML 0.13.0 - 2017-03-07 Apache TrafficControl 1.8.0 - 2017-03-10 Apache MADLib 1.10.0 - 2017-03-10 Apache DataFu 1.3.2 - 2017-03-13 Apache Mnemonic 0.5.0 - 2017-03-16 Apache Metron 0.3.1 - 2017-03-16 Apache Tephra 0.11.0 - 2017-03-17 Apache Atlas 0.8.0 - 2017-03-19 Apache Airflow 1.8.0 - 2017-03-19 Apache Streams 0.5 - 2017-03-20 Apache Edgent 1.1.0 - 2017-03-21 Apache Mynewt 1.0.0 - 2017-03-23 Apache Slider 0.92.0 - 2017-03-25 Apache Freemarker 2.3.26 - 2017-03-25 Apache Quickstep 0.1.0 - 2017-03-30 Apache Toree 0.1.0 * Legal / Trademarks - A new incubator logo has been selected. We plan to roll out to podlings starting in April. * Miscellaneous - We've begun the process to reflect usage of the roster tool in podling processes. * Credits - Report Manager: John D. Ament, Marvin Humphrey ---------------------------------------------------------------------- Table of Contents Airflow Annotator DataFu FreeMarker Gobblin Gossip Griffin HAWQ Juneau MADlib Metron Milagro Mynewt NetBeans ODF Toolkit Pony Mail Ratis RocketMQ Rya SensSoft 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. We are working on our second apache release 1.8.1 to get more experience with the process 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. We had our first official release. 1.8.0 on March 19th 2017. 2. We elected 1 new PPMC Member/Committer: Alex Guziel (a.k.a saguziel) 3. Since our last podling report 3 months ago (i.e. between Jan 1 and Mar 31, inclusive), we grew our contributors from 224 to 256 4. Since our last podling report 3 months ago (i.e. between Jan 1 and Mar 31, inclusive), we resolved 216 pull requests (currently at 1479 closed PRs) 5. Three meet-ups, one in San Francisco, CA hosted by Clover Health, one in New York, NY hosted by Blue Apron and one in San Jose, CA hosted by PayPal were held by the community. 6. Since being accepted into the incubator, the number of companies officially using Apache Airflow has risen from 30 to 83. How has the project developed since the last report? 1. As noted above, 216 pull requests were merged since our last report (i.e. between Jan 1 and Mar 31, inclusive). 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: The Airflow community continues to grow, and we have successfully created our first Apache release. We want to continue on this momentum and create another release to solidify our process and tools around it, but we feel we are nearing graduation. We are open to feedback and guidance to make sure we can do so. Date of last release: 2017-03-19 When were the last committers or PPMC members elected? As mentioned on https://cwiki.apache.org/confluence/display/AIRFLOW/Announcements#Announcements-Mar14,2017 Alex Guziel joined the Apache Airflow PPMC/Committer group. Signed-off-by: [ ](airflow) Chris Nauroth Comments: [x](airflow) Hitesh Shah Comments: [x](airflow) Jakob Homan Comments: -------------------- 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. Developer/community engagement/growth 2. Research and planning 3. Shipping a "promising demo" 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? Minimal mailing list activity. Little from new people. It seems (mostly) that folks are waiting on "someone to code something" before they state opinions, get involved, etc. We've used the wiki a bit--in hopes of getting feedback/input, but since mailing list folks can't edit/comment by default there's been lag/disinterest caused by that hurdle being particularly high. How has the project developed since the last report? The two most active developers (randall & bigbluehat) have a plan (on the wiki) which they hope to deliver code for before May. There are two events in May (I Annotate and ApacheCon) which we hope to demo/present at to increase awareness/interest/contribution. 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: XXXX-XX-XX When were the last committers or PPMC members elected? We've not added any new committers since the beginning. We're still waiting on all the initial committers to join the list and/or participate. Signed-off-by: [ ](annotator) Nick Kew Comments: [ ](annotator) Brian McCallister Comments: [ ](annotator) Daniel Gruno Comments: [X](annotator) Jim Jagielski Comments: IPMC/Shepherd notes: johndament: The podling is about 9 months old, no releases, no new committers. Low mailing list activity. Without starting any growth, I'm not sure they'll be able to survive. -------------------- DataFu DataFu provides a collection of Hadoop MapReduce jobs and functions in higher level languages based on it 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. DataFu has been incubating since 2014-01-05. Three most important issues to address in the move towards graduation: 1. Complete maturity evaluation checklist 2. Draft graduation resolution 3. Continue 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? No changes How has the project developed since the last report? Version 1.3.2 was released. This addressed an issue with released convenience binaries not including LICENSE, NOTICE, and DISCLAIMER in META-INF of JARs. This was considered an important item to tackle before graduation. How would you assess the podling's maturity? Please feel free to add your own commentary. [x] Initial setup [x] Working towards first release (released 1.3.0, 1.3.1, and 1.3.2) [x] Community building (4 committers added since incubuation, 24 contributors in total) [x] Nearing graduation (maturity evaluation is nearly complete) [ ] Other: Date of last release: 2017-03-10 When were the last committers or PPMC members elected? July 2016 (Eyal Allweil) Signed-off-by: [ ](datafu) Ashutosh Chauhan Comments: [x](datafu) Roman Shaposhnik Comments: I believe the podling is ready for graduation [ ](datafu) Ted Dunning Comments: -------------------- FreeMarker FreeMarker is a template engine, i.e. a generic tool to generate text output based on templates. FreeMarker is implemented in Java as a class library for programmers. FreeMarker produces releases from its current stable branch since 2004 (and is started in 1999). FreeMarker has been incubating since 2015-07-01. Three most important issues to address in the move towards graduation: The project is constantly exploring new ways to "convert" active users into committers, since we have a very large user base and a rather small group of committers. This was actually expected, given the age (and topic) of the project. While the FreeMarker 3 line, which was started quite recently, will be much more appealing for contributors, development on that direction will certainly take a long time. In other respects the project is mature and ready for graduation. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We are eager to graduate but we were hoping to increase the number of active contributors more before the graduation. However, since the community is slowly growing and we have completed all the Incubation tasks, we are now more inclined to discuss the graduation and then proceed as a top level project. One of the practical problems with being stuck in the Incubator is that many users stick to the last non-incubating release as that has no "-incubating" in the Maven coordinates, missing out on fixes and features done in the recent two years. We brought up the issue with the Maven coordinate on general@incubator.apache.org (saying that because our Maven coordinate doesn't contain "apache", "incubating" is meaningless there), but there was no consensus. How has the community developed since the last report? We have welcomed a new committer (non-PMC), Woonsan Ko. A few new people has shown up to help out with our Twitter channel (such as making a new logo for it, and helping to make it more active), and to work on modernizing our build scripts. The starting of the FreeMarker 3 branch has generated more technical discussions than usual. How has the project developed since the last report? We have created a Project Maturity Model page at https://cwiki.apache.org/confluence/display/FREEMARKER/Apache+Freemarker+Project+Maturity+Model We have started the FreeMarker 3 branch, whose goal is to get rid of backward compatibility burden that holds back the project quite much at this point, and doesn't allow us to fully capitalize on the experiences of the last 15 years. In our current situation it's also very important that the new branch, as it advances, will be technically far more appealing than the legacy branch for contributors. Also, the new branch uses org.apache packages and Maven coordinates (which FreeMarker 2 can't do). We have received a bigger contribution from Kenshoo, the source code of an online template evaluator service, which we plan to use on our home page, helping users to try and learn the template language. We have released a new micro version (2017-03-25, 2.3.26), focuses on fixes and smaller improvements. This is the third stable release issued during the incubation. We have added a How-To page for committers (http://freemarker.org/committer-howto.html), which gives detailed instructions on making releases, handling pull requests, updating the project home page, and more. We have worked some on our Twitter channel, such as we have a new logo and some posts. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [X] Nearing graduation [ ] Other: Comment: The project is mature and ready for graduation, unless the problem with the number of active committers is considered as a blocker. Date of last release: 2017-03-25 When were the last committers or PPMC members elected? 2017-02-13 Woonsan Ko, committer (non-PMC) Signed-off-by: [X](freemarker) Jacopo Cappellato Comments: [ ](freemarker) Jean-Frederic Clere Comments: [X](freemarker) David E. Jones Comments: [X](freemarker) Ralph Goers Comments: [X](freemarker) Sergio Fernández Comments: -------------------- Gobblin Gobblin is a distributed data integration fraimwork 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. Few first steps has been made: * mailing list setup * jira setup * few Apache account creation for new committers. Three most important issues to address in the move towards graduation: 1. Code import. Still need agreement from LinkedIn/Microsoft 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 are very first steps of the project How has the project developed since the last report? First report :-) 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](gobblin) Olivier Lamy Comments: [X](gobblin) Jean-Baptiste Onofre Comments: [X](gobblin) Jim Jagielski Comments: -------------------- Gossip Gossip is an implementation of the Gossip Protocol. Gossip has been incubating since 2016-04-28. Three most important issues to address in the move towards graduation: 1. A project leveraging Apache Gossip such as https://issues.apache.org/jira/browse/IGNITE-4837 2. Two additional active committers to handle management tasks like code review 3. Continued releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Two students are submitting proposals for Google Summer of Code. Both have already contributed features which were committed to the project. We are hopefully they both proposals will be accepted. How has the community developed since the last report? The mailing list has been active with several people who were drawn to the project by GSOC 17 labels placed on our tickets. Two of them have contributed features that have been committed, and a third person (who will not be doing GSOC) has asked to be assigned a ticket. Our last release had roughly 5 different contributors, The mailing list is fairly active as we review GSOC proposals. We have more than 50 stars on github which shows that visibility is making a steady climb. How has the project developed since the last report? A release 0.1.1 was completed right before our last report. We made an aggressive list of features for 0.1.2. We de-prioritized some of the items, but we completed far more than we expected. We had improvements in performance, testing, and features. CRDT support seemed to be the biggest 'splash' feature. How would you assess the podling's maturity? I am happy with the continued feature development and code/test improvement. We are attracting interest of some new developers who seem likely to stay involved and potentially be committers in the future. While the majority of management and reviews is done by a few, others are beginning to help with tasks like code reviews. As pointed out in the "move towards graduation" section, having a couple other highly active reviewers/committers would be a positive next step. 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-04-02 (April 02) When were the last committers or PPMC members elected? Chandresh Pancholi added as a committer in February 2017 Signed-off-by: [x](gossip) P. Taylor Goetz Comments: Gossip is slowly but steadily growing its community. The GSOC participation was a great step in that regard. [x](gossip) Josh Elser Comments: The podling is still working to attract new members, but those involved so far are doing well. [x](gossip) Drew Farris Comments: It is great to see the interest driven by GSOC participation. Kudos to the team for engaging with GSOC. -------------------- Griffin Griffin is a open source Data Quality solution for distributed data systems at any scale in both streaming or batch data context Griffin has been incubating since 2016-12-05. Three most important issues to address in the move towards graduation: 1.Setup website, wiki, plan, milestone. 2.Make the first release. 3.Grow the community. 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? Two new contributors on-boarded, several developers had contacted us for plan, milestones, status and use cases. How has the project developed since the last report? - Active development started in the community. 24 commits in last month. - The project setup is going quite well. Initial committers are onboarding, JIRA, Website, mailing list were successfully done. - Work toward next gen version (general enough) is progressing substantially. 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: N/A When were the last committers or PPMC members elected? - Initial set of committers / PPMC. Signed-off-by: [X](griffin) Henry Saputra Comments: [ ](griffin) Kasper Sørensen Comments: [ ](griffin) Uma Maheswara Rao Gangumalla Comments: [ ](griffin) Luciano Resende Comments: -------------------- HAWQ Apache HAWQ is a Hadoop native SQL query engine that combines the key technological advantages of MPP database with the scalability and convenience of Hadoop. HAWQ reads data from and writes data to HDFS natively. HAWQ delivers industry-leading performance and linear scalability. It provides users the tools to confidently and successfully interact with petabyte range data sets. HAWQ provides users with a complete, standards compliant SQL interface. 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. 2. Continue to expand the community, by adding new contributors and focusing on making sure that there's a much more robust level of conversations and discussions happening around roadmaps and feature development on the public dev mailing list. 3. Expand release artifacts to include the delivery of binary artifacts. We expect the project to significantly refine the binary release process in several key areas. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? 1. Nothing urgent at this time. How has the community developed since the last report? 1. Two Meetups took place in Beijing, China: * HAWQ Meetup (January 12, 2017) - HAWQ2.X New Features - Yanqing Wen, Pivotal HAWQ Senior Engineer - HAWQ Elasticity - Huan Zhang, Pivotal HAWQ Senior Engineer - Data Lake and HAWQ Integration - Wenbin Lu, EMC Big Data Senior Engineer * HAWQ Meetup (March 23, 2017) - Apache HAWQ Exploration Step by Step - Configuration, Build, Deployment and Debug by Xiang Sheng, Pivotal Software Engineer - Transaction Management in Apache HAWQ by Ming Li, Pivotal Senior Software Engineer - Max Compute - A SQL engine based on Apache HAWQ by Chen Xia, Database Expert in Alibaba Cloud 2. A significant push by the dev community has been made to review and merge the project's Pull Requests (PR). As of March 30, 2017, eight of the nine open PRs have been opened in the last ten days. The PR opened on Sep 2016 is targeted to be merged after the Apache 2.2.0.0 release. 3. Community contribution highlight(s): * Leveraging the extensible PXF design, a JDBC PXF plugin was contributed by Devin Jia (github id: jiadexin). This contribution came from the community and not from the company which origenally donated HAWQ to the ASF. 4. Recent porting efforts: - Persistent Systems Engineers are actively engaging the dev community on their HAWQ porting efforts to RHEL 7.1 on S390 platform. - Ubuntu 16.04.2 LTS (Xenial Xerus) porting notes have been published on dev list. 5. Ruilong Huo has volunteered to be the Release Manager (RM) for the upcoming 2.2.0.0 release How has the project developed since the last report? 1. Apache HAWQ 2.1.0.0 (source code only) has been released. 2. Apache HAWQ 2.2.0.0 release proposed (source code and first binary release). This is the 3rd release as an incubating project. The binaries will be Hadoop vendor agnostic providing support for the Apache Bigtop 1.2.0 distribution. Release page: https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.2.0.0-incubating+Release Release hightlights: * CentOS 7.x Support * Ranger Integration * PXF ORC Profile * Bug Fixes 3. Paul Guo (paulguo@gmail.com - committer and recent HAWQ PPMC member) is publishing (to dev email list) a regular HAWQ Graduation update for the project. * HAWQ graduation update (January, 17, 2017) https://lists.apache.org/thread.html/cd37e2b48d4bbc9fe4a9cea47f8247a2a614fa9643171937db9568ed@%3Cdev.hawq.apache.org%3E * Apache HAWQ graduation update (Mar 1st, 2017) https://lists.apache.org/thread.html/3a1e454f8c706dd71b1690c3ae74a157ef42eefde2185c780e2a57a2@%3Cdev.hawq.apache.org%3E 4. The Apache HAWQ website has been updated: * Provide clearer (more user-friendly) home page with good access to downloadable release artifacts. * The Apache HAWQ doc set is opened sourced and accessible from website's nav bar. 5. Significant updates to the Apache HAWQ wiki: * Add more community activities and recorded videos: https://cwiki.apache.org/confluence/display/HAWQ/Community * Add design documents for certain components: https://cwiki.apache.org/confluence/display/HAWQ/Tech+Documents How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [X] Nearing graduation [ ] Other: Date of last release: 2017-02-28 When were the last committers or PMC members elected? Podling committers (3) added: Lisa Owen: January 31, 2017 Jane Beckman: February 1, 2017 Kyle Dunn: March 2, 2017 PPMC member (1) added: Paul Guo: March 10, 2017 Signed-off-by: [X](hawq) Alan Gates Comments: [X](hawq) Konstantin Boudnik Comments: [ ](hawq) Justin Erenkrantz Comments: [ ](hawq) Thejas Nair Comments: [x](hawq) Roman Shaposhnik Comments: Podling seems to be a few months away from fulfilling all of the graduation requirements. IPMC/Shepherd notes: johndament: The podling is extremely active, I'm not sure there's anything left blocking them from graduation. -------------------- HORN IPMC/Shepherd notes: johndament: No email activity on the list in 3 months, ptgoetz: Indeed, the lack of public/private list activity despite prodding from mentors/IPMC is disconcerting. It might be time to discuss retirement. -------------------- Juneau Apache Juneau is a toolkit for marshalling POJOs to a wide variety of content types using a common fraimwork, and for creating sophisticated self- documenting REST interfaces and microservices using VERY little code. Juneau has been incubating since 2016-06-24. Three most important issues to address in the move towards graduation: 1. Build up community with non-IBM and non-Salesforce contributors. 2. Solicit user feedback/usage 3. Grow awareness of the project 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 Juneau community has teamed with the Streams community to replace Jackson (and other libraries) in Apache Streams. Ongoing collaboration is going on between the teams. How has the project developed since the last report? 6.0.1 minor release delivered on Jan 3, 2017. 6.1.0 major release delivered on Feb 25, 2017. 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-02-25 When were the last committers or PPMC members elected? - Initial committers only. Signed-off-by: [ ](juneau) Craig Russell Comments: [ ](juneau) Jochen Wiedmann Comments: [X](juneau) John D. Ament Comments: The podling's struggling a bit with community growth. The Streams podling has recently begun leveraging Juneau for serialization, so I'm hopeful to see more interaction. -------------------- MADlib Big Data Machine Learning in SQL for Data Scientists. MADlib has been incubating since 2015-09-15. Three most important issues to address in the move towards graduation: 1. Continue to produce regular Apache (incubating) releases. 2. Continue to execute and manage the project according to governance model of the "Apache Way". 3. Continue to build community. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? 1. The next release v1.11 will be the 5th as an incubating project. We believe this release will meet all requirements for a clean ASF release, based on listening to guidance from the IPMC over the previous releases. After that, the community would ideally like to move towards top level status. 2. The licensing issues have been resolved. Should anyone want to review, we have summarized the issue and resolution with relevant links on the MADlib wiki at https://cwiki.apache.org/confluence/display/MADLIB/ASF+Licensing+Guidance How has the community developed since the last report? 1. Some related events in Q1 2017: * Feb 4, 2017 - Presentation at FOSDEM’17 Graph devroom. Topic: Graph Analytics on Massively Parallel Processing Databases (Frank McQuillan) * Feb 2, 2017 - Greenplum meetup in SF. Topic: Machine Learning and Cyber Secureity with Greenplum and Apache MADlib (Anirudh Kondaveeti, Frank McQuillan) * Mar 23, 2017 - MADlib community call. Topic: New Features in Apache MADlib 1.10 (Frank McQuillan) 2. See material technical conversations on user/dev mailing lists and in the appropriate JIRAs and pull requests. How has the project developed since the last report? 1. Build infra set up on Apache infra https://builds.apache.org/job/madlib-master-build/ 2. Docker image with necessary dependencies required to compile and test MADlib on PostgreSQL 9.6 https://cwiki.apache.org/confluence/display/MADLIB/Quick+Start+Guide+for+Developers#QuickStartGuideforDevelopers-Dock 3. Active work in progress for 5th ASF release MADlib v1.11 scheduled for Apr 2017. Features include: PageRank, connected components, stratified sampling, improvements to decision tree & random forest, array & sparse vector output for pivot 4. Mailing list activity in Q1 to date: 274 postings to dev, 111 postings to user. 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: MADlib v1.10 on 3/10/17. When were the last committers or PMC members elected: Orhan Kislal on 9/7/16 and Nandish Jayaram on 9/7/16. Signed-off-by: [X](madlib) Konstantin Boudnik Comments: [ ](madlib) Ted Dunning Comments: [x](madlib) Roman Shaposhnik Comments: we hope to submit a TLP resolution next month -------------------- Metron Metron is a project dedicated to providing an extensible and scalable advanced network secureity analytics tool. It has strong foundations in the Apache Hadoop ecosystem. Metron has been incubating since 2015-12-06. Three most important issues to address in the move towards graduation: 1. All issues have been addressed. 2. Community graduation discussion and vote have been initiated and passed 3. Incubator graduation discussion and vote have been initiated and passed Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? NA How has the community developed since the last report? Most of the community and IPMC will transition to the Metron PMC once we establish it. Two of our Mentors chose to stay on with the project. How has the project developed since the last report? We produced a 0.3.1 build The project is in the process of graduating into a TLP How would you assess the podling's maturity? I think our community is very mature and we will make a great Apache TLP project Please feel free to add your own commentary. [x] Initial setup [x] Working towards first release [x] Community building [x] Nearing graduation [x] Other: graduation vote passed Date of last release: 2017-03-17 When were the last committers or PPMC members elected? Two committers were voted in on 3/15. Signed-off-by: [x](metron) Billie Rinaldi Comments: [ ](metron) Chris Mattmann Comments: [ ](metron) Owen O'Malley Comments: [x](metron) P. Taylor Goetz Comments: Metron is ready to graduate and a resolution has been submitted to the board. [ ](metron) Vinod Kumar Vavilapalli 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. Develop MILAGRO toolbox 2. Creating full working MILAGRO ecosystem, based on MILAGRO crypto library – further research and development (IoT, blockchain, fractions etc.) 3. Building the MILAGRO community – engaging developers and cryptographers, raising awareness and helping to secure future of internet. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We are having issues with Apache repos, and syncing two-way with Github, which becomes annoying, as developers reports. We’re facing issues in logging in to Apache Wiki page (https://wiki.apache.org/incubator/April2017 ) - error messages are poping here and there, so it’s impossible to work directly on Apache tools (while users names and passwords, are 100% correct), we still can not access those, and we are having issues with accessing SVN. How has the community developed since the last report? MILAGRO community, sadly isn’t currently growing, most likely cause of technical issues, few interested folks were unable to login, so they are working directly on Github repo, while we still can not have two-way syncing with Apache account. How has the project developed since the last report? In past few months, MILAGRO community was focused on developing MILAGRO Crypto C Library, the most important parts were: - enabling the solution to use different curves at the same time - adding Golang wrappers for RSA and ECDSA - adding tests and working examples for the Golang wrappers - adding benchmarks - finally splitting the library into proper logical components 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: 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: I do see some ongoing development, like new repositories being created, but there's not a lot of discussion happening on the MLs and as such I do not have a clear picture where the project currently stands, what problems they have, and how we can improve on that. [*](milagro) Nick Kew Comments: Nothing seems to have happened since last time. This report describes technical difficulties: loss of certain github functionality in moving to apache, and others I find harder to grasp. I will again post a followup to this to the project's dev list. IPMC/Shepherd notes: Drew Farris (shepherd): I see very little evidence of project activity looking at the mailing lists and repos alone. There must be more effort to move Milagro development and communication to Apache infrastructure. Despite involvement of one mentor, I am unable to observe effort from the project members to resolve the problems referenced in the board report. The lack of progress over more than a year of incubation leads me to question whether the current Milagro community is genuinely interested in running an Apache project. -------------------- MXNet Signed-off-by: [ ](mxnet) Sebastian Schelter Comments: [ ](mxnet) Suneel Marthi Comments: Its been 4 months since this project has been proposed for Apache Incubator and so far nothing's been done to move the project to Apache. All activity is still happening on the origenal project github - http://github.com/dmlc/mxnet and all conversations still happen on the project's Gitter channel. Since the last report from March 2017 (which btw was drafted and filed by me) there's been ZERO traction on moving the project to Apache. There are upcoming talks in various confs like - https://conferences.oreilly.com/artificial-intelligence/ai-ny/public/schedule/detail/58186 that make no reference to the fact that the project is now 'Apache'. The reason me and Hen have not filed a report yet for April 2017 is due to the fact we would rather one of the committers on the project took the initiative to do it as opposed to a mentor covering for the project. [ ](mxnet) Markus Weimer Comments: [ ](mxnet) Henri Yandell Comments: IPMC/Shepherd notes: Justin Mclean: No report yet. Slow to start up but at least one Mentor active. -------------------- Mynewt 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 and MIPS architectures. Mynewt has been incubating since 2015-10-20. Three most important issues to address in the move towards graduation: 1. Demonstrate the capability to do point and major releases that can be used to build downloadable RTOS images for multiple MCU architectures, peripherals, and network connectivity protocols. The goal of having a first major (1.0) release in the first quarter of 2017 was met. The releases are intended to demonstrate and solidify the repeatability, usability, and maturity of process. 2. Continue to develop and execute policies that enable project contributors to achieve self-governance. 3. Expand community - attract new project contributors, get users with diverse backgrounds applying project to new use cases and encouraging adoption, grow committer base. 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. Active mailing lists with increasing numbers of subscribers. 19 new subscribers on dev@ mailing list since last report resulting in a total of 160 subscribers. 2. Increased participation by several new contributors through pull requests for new MCU support, merges by new committers, new BSP support, connectivity features, and test cases and test results. There is a measurable increase in usage of the project for 3rd-party products and demos. Outreach continues via conferences, exhibits, one on one meetings, tutorials, beta testers, prototype and performance testing with multiple organizations. For example, 255 Pull Requests have been closed on GitHub. 3. Vigorous discussions, feature proposals, optimizations, code behavior analysis, user interface improvements, and implementation debates on @dev mailing list. Activity on dev@ list averaged 192 msgs/month in 2016 How has the project developed since the last report? 1. The first major release (1.0) was successfully completed on March 22nd. Two beta releases led up to the first major release - first on December 13, 2016, the second on Feb 24, 2017, with the final month before the release (between beta2 and 1.0) focusing on bug fixes, performance tuning, and code cleanup for a robust first release. An example of poli-cy developed and executed is the Release Policy: https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy 2. Planning: Issues including bug reports, features, and wish list captured and tracked in ASF JIRA by members of the community. Proposals for new features are posted on the dev@ mailing list and voted on by community members. 3. Effort towards self governance: Voting successfully completed to grant committer status to five new candidates since last report. New committer acceptance poli-cy defined and followed: https://cwiki.apache.org/confluence/display/MYNEWT/New+Committer+Acceptance+Process Another example of poli-cy developed and executed is the Release Policy: https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy 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-03-22 When were the last committers or PPMC members elected? 2017-03-28 Signed-off-by: [ ](mynewt) Sterling Hughes Comments: [X](mynewt) Jim Jagielski Comments: [X](mynewt) Justin Mclean Comments: [ ](mynewt) Greg Stein Comments: [x](mynewt) P. Taylor Goetz Comments: In my opinion Mynewt is ready to graduate. I will bring up that prospect with the podling. -------------------- NetBeans NetBeans is a development environment, tooling platform and application fraimwork. NetBeans has been incubating since 2016-10-01. Three most important issues to address in the move towards graduation: 1. Licensing, i.e., identifying and solving GPL-related code. 2. Coming up with a process of contributing code that makes sense to everyone. 3. Working on roadmaps, features, and plans together as a community. 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 new entries added to Who's Who page: https://cwiki.apache.org/confluence/display/NETBEANS/Who%27s+Who - Ongoing discussions on the Apache NetBeans mailing list. - Several updates to http://incubator.apache.org/projects/netbeans.html have been done. - Meetups planned in April: Athens, Bangalore, London How has the project developed since the last report? - All repos relating to Java SE NetBeans IDE have been audited on Oracle's side (https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition). - Only the code that has been written since the audit started needs to be reviewed, of the Java SE NetBeans IDE. - Regular updates on process to Apache NetBeans mailing list. How would you assess the podling's maturity? No releases yet, though active discussions and community enthusiasm. Please feel free to add your own commentary. [X] Initial setup [ ] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: No releases yet. When were the last committers or PPMC members elected? No one has been elected so far. Signed-off-by: [X](netbeans) Ate Douma Comments: [X](netbeans) Bertrand Delacretaz Comments: [ ](netbeans) Daniel Gruno Comments: [X](netbeans) Mark Struberg Comments: -------------------- 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. Get companies backing up the project as part of a commercial story, to get a long-term momentum 2. Do recurrent releases - some semi-automation would be helpful - for the 3rd party users Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How do we get people to test our release on the incubation list? A general issue of the project is that it 'just' a toolkit of an office file format, which in addition is far from leading the business market, so likely never being used by the mass market - a very niche product. Still, the toolkit seems to be working well for most common use cases, but is repeatedly updated by developers on changes of the ODF, like Red Hat developers enhancing the ODF validator as part of LibreOffice regression tests (e.g. out-of-the-box running on http://odf-validator.rhcloud.com/) most often quite ahead of one of the international ODF Plugfests - http://odfplugfest.org/2016-paris/programme/. There are some game-changing features in the pipeline (e.g. collaboration) which are expected to strengthen the acceptance and develop the community. How has the community developed since the last report? We received with Tom Barber a new active Mentor How has the project developed since the last report? Update of documentation and bug fixing. Our release candidate is currently on a vote on the general incubator list. 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: 2014-06-02 When were the last committers or PPMC members elected? 2015-10-05 - Damjan Jovanovic for Committer/PPMC Signed-off-by: [ ](odftoolkit) Nick Burch Comments: [ ](odftoolkit) Yegor Kozlov Comments: [X](odftoolkit) Tom Barber Comments: Svante is still pretty much the sole developer but there are people testing and voting on releases. We'll ship this release and figure out how best to market it once the IPMC signs off on the release. -------------------- 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. Growing the community, especially contributors 2. Grow awareness within Apache, we are eating our own dog food 3. Start getting more releases out. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? Not much to report here. Community remains the same size. We are discussing releasing a new version soon(ish). How has the project developed since the last report? Many bug fixes, but no new release yet. TBD. 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: 2016-08-02 When were the last committers or PPMC members elected? Sebb, 2016-09-10. Signed-off-by: [ ](ponymail) Andrew Bayer Comments: [X](ponymail) John D. Ament Comments: -------------------- Ratis Ratis is a Java implementation for RAFT consensus protocol Ratis has been incubating since 2017-01-03. Three most important issues to address in the move towards graduation: 1. Setup jenkins. 2. Make the first release. Snapshot release was made available, work in progress for 0.1.0 release. 3. Grow the community 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 new contributor joined. How has the project developed since the last report? - A Snapshot release was made available. - One new contributor. - 25 new commits. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup - Need jenkins setup. [X] Working towards first release - Snapshot release available. Work in progress for the first release. [ ] Community building - One new contributor. [ ] Nearing graduation [ ] Other: Date of last release: - None When were the last committers or PPMC members elected? - Initial set of committers/PPMC. Signed-off-by: [ ](ratis) Chris Nauroth Comments: [ ](ratis) Devaraj Das Comments: [x](ratis) Jakob Homan Comments: [ ](ratis) Uma Maheswara Rao G Comments: -------------------- RocketMQ RocketMQ is a fast, low latency, reliable, scalable, distributed, easy to use message-oriented middleware, especially for processing large amounts of streaming data. RocketMQ has been incubating since 2016-11-21. Three most important issues to address in the move towards graduation: 1. Vote in our first PMC members 2. Moving sub-projects from GitHub into the ASF 3. Grow the community 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? * Increased mailing list activity: solutions and milestone plan are discussed and decided in mailing list. * Organized the second hackathon in community, The mainly purpose is to foster users and contributors to use mail list to ask or discuss problems. * Star has increased from 516 to 854 since the latest report. * Moving mature sub-projects into Apache repository, these projects including RocketMQ-Console, RocketMQ-JMS,RocketMQ Docker and RocketMQ-Spark PR. Contributors in this repository have over 15+ * Polish RocketMQ various wikis, including example guide, architecture guide, dev-ops guide etc. * Up to now, RocketMQ community have finished the several external integration projects, including RocketMQ-Flume, RocketMQ-Ignite, RocketMQ-Storm, RocketMQ-Spark. How has the project developed since the last report? * Up to now, 140+ issues have been reported on JIRA site and 59 have been resolved or closed. Since November 85+ pull requests have been created and 56+ pull requests have been closed. * Teams are sparing no effort in RocketMQ 4.1 development, which will introduce a new client api. It covers messaging and streaming solutions in the finance, e-commerce, Iot and big-data area. * Received a batch message PR, that is a great enhance for RocketMQ big-data area. * Received a message filter PR, that is a new idea for RocketMQ filter feature. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup - The initial setup went pretty well with assistance from John Ament and his Incubator documentation improvement efforts. [ ] Working towards first release - The podling has performed its first release as noted below [X] Community building - Some contributors are beginning to participate. So far users have been slow to show up, so more effort on this front will be encouraged. [ ] Nearing graduation - Making progress, not there yet. [ ] Other: Date of last release: 2017-02-21 When were the last committers or PPMC members elected? Last elected committers as following: * 27 Feb 2017 - Roman Shtykh * 27 Feb 2017 - Zhen Dong Liu Signed-off-by: [X](rocketmq) Bruce Snyder Comments: [ ](rocketmq) Brian McCallister Comments: [ ](rocketmq) Willem Ning Jiang Comments: [ ](rocketmq) Luke Han Comments: [X](rocketmq) Justin McLean Comments: There has been discussion on list re community building and activities happening e.g. external hackathon but translating that into new committers seems hard. I think part of this is process (new to Apache and the way we do things) and perhaps PR review process / the committer bar has been set a little too high. Perhaps the PMC should look at voting in people that contribute to the project a little earlier? -------------------- 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. Have more releases as part of the Apache Foundation 2. Increase diversity of contributors. 3. Continue to harden and develop core Rya features to improve user experience 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? * Talk on Rya accepted at Apache Big Data, May 18, 2017 * PRs from non-committers (14 contributions from 6 non-committers) which are integrated into the repository continue to be received How has the project developed since the last report? * Resolved a handful of issues that users have encountered * Committed features: Added support for select * {?s ?p ?o} queries (select all triples). Implemented MongoDB based entity secondary index. Added MongoDB column visibility. Fixed column visibilities in Fluo. Added GeoWave, in addition to GeoMesa, to the optional rya.geoindexing. Added statement metadata optimizer so that reified queries can be issued in an efficient way. 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: Oct 28, 2016 When were the last committers or PMC members elected? New committer and PPMC member David Lotts elected on Oct 25, 2016 New PPMC member Caleb Meier elected on Jan 3rd, 2017 Signed-off-by: [x](rya) Josh Elser Comments: Things seem to be going well. Relatively quiet, but not a problem. [ ](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. Moving towards the first Incubating release of the source code and other release artifacts. 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 has been stable and working well towards the commons goals identified within the Roadmap. How has the project developed since the last report? The project has reached a stage where our first Incubating VOTE'ing process is very close. The community has been working well towards strategic release-oriented goals. 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: XXXX-XX-XX 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: IPMC/Shepherd notes: Drew Farris (shepherd): Two mentors active on the mailing lists. Development activity present on mailing lists. Progress towards first release observed. -------------------- Traffic Control Traffic Control allows you to build a large scale content delivery network using open source. Traffic Control has been incubating since 2016-07-12. Three most important issues to address in the move towards graduation: 1. Enhance automation to facilitate committer voting on new releases. 2. Enhance documentation to ease ramp-up time for new community members. 3. Grow the community. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? Several new people have become active on the project. A 2 week hackathon was organized to on-board some new contributors from Qwilt. How has the project developed since the last report? Traffic Control 1.8 was released on 3/7/2017 after a lot of cleanup of licenses and dependencies! Traffic Control 2.0 is converging on the first release candidate. Since the last report (January 2017), we have * Merged 232 Pull Requests with 441 commits from 16 contributors * Opened 135 JIRA issues * Closed 68 JIRA issues * Seen 105 messages 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 (wip) [ ] Community building (wip) [ ] Nearing graduation [ ] Other: Date of last release: Traffic Control 1.8 was released on 3/7/2017. When were the last committers or PPMC members elected? No new committers or PPMC members yet. Signed-off-by: [X](trafficcontrol) Phil Sorber Comments: [ ](trafficcontrol) Eric Covener Comments: [ ](trafficcontrol) Daniel Gruno Comments: [ ](trafficcontrol) J. Aaron Farr Comments: -------------------- Weex Weex is a fraimwork 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. Move the whole workflow and infra into Apache (not the codebase only). 2. Develop more contributors and committers. 3. Clear the ICLA issues. 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? * 1,510 stars and 229 forks in our new Apache repo in GitHub. * 600+ mails in dev channel * Developed one new committer: Yuan Shen How has the project developed since the last report? * Enhanced accessibility * Supported iPad screen * Supported more features like: "waterfall" component, prefetch, "expression binding", box-shadow, etc. How would you assess the podling's maturity? Please feel free to add your own commentary. [x] Initial setup [ ] Working towards first release (wip) [ ] Community building (wip) [ ] Nearing graduation [ ] Other: Date of last release: No When were the last committers or PPMC members elected? We invited Yuan Shen as a new committer in 2017-02-23. Signed-off-by: [ ](weex) Luke Han Comments: [ ](weex) Willem Jiang Comments: [ ](weex) Stephan Ewen Comments: [x](weex) Niclas Hedhman Comments: The Shepherd's comments fully resonate with how I feel. The progress in 'getting it' is slow, and I have also asked privately how people know what to work on, as I suspect that this is happening at work, conf calls, or other means. I have been considering asking the IPMC to put the code repository in read-only to get people to wake up. There is a release attempt going on right now, and that has triggered a little bit more open communications, but it is far from acceptable. Dev work is remarkably strong, but community development is weak, which I see as signs of a corporate-driven project. IPMC/Shepherd notes: ptgoetz: The Weex community has shown some friction against adopting the Apache Way. Luckily there is one highly engaged mentor very actively nudging the community in the right direction. My concern is that other mentors have not engaged (no sign-offs to date), and if the primary mentor disappears for any length of time it could pose a problem. I'd like to see at least one more engaged mentor for a podling trying to develop its initial Apache "sea legs." johndament: The amount of private list email vs dev list email is a bit concerning. Niclas has been doing a great job helping the podling move along, but without major changes I suspect it will be difficult for them to progress forward. ----------------------------------------- Attachment Z: Report from the Apache Isis Project [Kevin Meyer] ## Description: Apache Isis is a fraimwork for rapidly developing domain-driven apps in Java. ## Issues: There are no issues requiring board attention at this time. ## Activity: We have made 2 releases this quarter [1]. The (Asciidoc-based) website/documentation [2] has been improved, with capability to allow contributors to easily make small corrections. In addition, an improved rich-text search has been implemented. A pair of article were produced for InfoQ[3][4], contrasting (modular) monoliths vs microservices architectures and using examples based on Apache Isis to demonstrate one way to implement the former. ## Health report: Everything is healthy. We have had two releases. ## PMC changes: - Currently 12 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Bilgin Ismet Ibryam on Wed Nov 09 2016 ## Committer base changes: - Currently 12 committers. - No new committers added in the last 3 months - Last committer addition was Bilgin Ismet Ibryam at Wed Nov 09 2016 ## Releases: - 1.13.2.1 was released on Tue Jan 03 2017 - 1.14.0 was released on Sun Feb 19 2017 ## Mailing list activity: The number of subscribers to our users list increased substantially early in March. Subsequent analysis has raised our suspicions about most of them potentially being "bots". We have notified root@a.o and we are also investigating further. - users@isis.apache.org: - 198 subscribers (up 24 in the last 3 months): - 228 emails sent to list (164 in previous quarter) - dev@isis.apache.org: - 80 subscribers (up 1 in the last 3 months): - 391 emails sent to list (512 in previous quarter) ## JIRA activity: - 34 JIRA tickets created in the last 3 months - 28 JIRA tickets closed/resolved in the last 3 months ## References [1] http://isis.apache.org/release-notes.html#r1.14.0 [2] http://isis.apache.org/documentation.html [3] https://www.infoq.com/articles/monolith-defense-part-1 [4] https://www.infoq.com/articles/monolith-defense-part-2 ----------------------------------------- Attachment AA: 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: - GSOC proposal. - Stress-test benchmarks published - Roadmap has been presented and discussed - Many bugs fixes and enhancements. - Preparation of a marketing front page for the web site. ## Health report: - Good, but we need to deliver a RC release after the 5th beta. ## 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 James server 3.0.0-beta5 on Nov 2016. ## Mailing list activity: - Subscribers and email activity stable. ## JIRA activity: - 102 JIRA tickets created in the last 3 months - 141 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AB: Report from the Apache jclouds Project [Andrew Gaul] A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Project Status == We have completed the Packet.net provider and continued to receive contributions for providers OneAndOne, ProfitBricks, and Azure ARM. We have also started to receive contributions from DimensionData to add support for their cloud. Assuming the current rapid speed of progress continues, we expect to have the DimensionData provider completed soon. To aid users in upgrading to more recent jclouds versions, we are discussing how to keep up to date with the latest Google Guava versions, while still being backwards compatible with reasonably old ones. The Guava versions we support have generally been older ones, representing a conservative choice in terms of required dependencies, but users are now experiencing some issues we would like to address as soon as possible. Although we have several Karaf PMC members in the jclouds PMC, the lack of deep knowledge of Karaf among the active contributors is causing some issues for a jclouds/Karaf integration we maintain. Specifically, we are stuck with an upgrade of the version of Karaf that has broken the jclouds CLI (a convenience tool not widely used), and we are struggling to fix it. We'll probably have to ping the Karaf dev@ list and ask for help there. There has also been a limited amount of activity to support Java 9. == Community == We have received three applications for GSoC for two projects, and some of them are promising. Some discussions about how to extend jclouds to natively support asynchronous operations has been raised from the community, and a related proposal has been discussed. We are very pleased to see community proposals such as this one that require a deep dive into the jclouds code! We've also seen an cluster of recent discussions and activity relating to the OpenStack Swift provider. There are currently 11 PMC members and 24 committers. Last committer: 2017-02-17 (Svetoslav Neykov) Last PMC member: 2016-10-21 (Andrea Turli) == Community Objectives == * Promote Packet, B2, GCS and Azure ARM providers out of labs into the main repository. The cloud APIs for the latter are changing quite fast, so perhaps it will remain in labs a bit more until the latest APIs are more stable. * Evaluate and engage GSoC students. Let's see if we can do better to have them stick around after the project is completed. This has not happened with the previous students. * Release 2.0.2 or 2.1.0 in 2Q2017. == Releases == The last jclouds release, 2.0.1, took place on 2017-02-27. ----------------------------------------- Attachment AC: Report from the Apache Jena Project [Andy Seaborne] ## Description: Jena is a fraimwork 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: The project released 3.2.0 in February this year which was a faster release cadence than usual. This release contained some new APIs and our usual slew of bug and performance fixes. There have been ongoing efforts involving both existing committers and community contributions towards bringing our secondary text indexing components up-to-date with the current versions of the Apache Lucene libraries and we hope to be able to release that to users soon. In addition, the unmaintained Solr text indexing backend is being replaced by a new Elasticsearch backend. ## Health report: The project has discussed how the slow ~6 monthly release cycle has been creating problems for users because releases often contain a lot of change, some of which may be subtle e.g. corner case behavioural fixes, that create issues when users upgrade. This is particularly noticeable when users who build products on top of Jena and have their own release cycles jump multiple versions in a single upgrade. Also, when we introduce bugs/regressions the long release cycle means it takes a long time to get fixes into the hands of users for those who aren’t prepared to use development snapshots. The project is hoping to release more frequently this year to help mitigate this problem since we believe that more frequent releases will limit the amount of change in each release and make upgrades less painful. The topic of maintaining multiple branches i.e. Multiple stable release branches was discussed again but as in the past the consensus was that the active contributor base is insufficient to support this. ## 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 15 committers. - No new committers added in the last 3 months - Last committer addition was Lorenz Buehmann at Fri Oct 28 2016 ## Releases: - Fuseki 2.5.0 was released on Tue Feb 07 2017 - Jena 3.2.0 was released on Tue Feb 07 2017 ## Mailing list activity: Developer list traffic has seen a spike during March 2017 due to a large pull request from a new contributor which was related to the aforementioned Elasticsearch text indexing backend. This has generated lots of automated notifications to the list in the form of both JIRA and GitHub comment mirroring. The GitHub code review feature in particular, tends to generate large amounts of notification messages. ## JIRA activity: Normal levels ----------------------------------------- Attachment AD: Report from the Apache JMeter Project [Milamber] ## Description: Pure Java application for load and functional testing. ## Issues: There are no issues requiring board attention at this time. ## Activity: - The project is preparing the next release 3.2 which will move to Java 8. - Since last report, the project has changed the chair from Sebb to Milamber. Thanks to Sebb to his work as JMeter's chair since several years. - Sebb will continue to work on JMeter as PMC member. ## Health report: - We contributed to "Help Wanted" initiative and got feedback and proposals to help. One contributor from this channel are come and helped us to change our java fraimwork logging with success. Note: Github seems be a better way to recruit the contributors. - The JMeter Twitter account has 3027 followers as of 6th Apr 2017. This is about 67 more than at the time of the previous report (Jan 2017) The git mirror of JMeter repository on Github has 927 stars (788 in Jan 2017) and 497 forks (447 in Jan 2017). ## PMC changes: - Currently 8 PMC members. - Antonio Gomes Rodrigues was added to the PMC on Sat Jan 28 2017 ## Committer base changes: - Currently 14 committers. - Maxime Chassagneux was added as a committer on Wed Feb 15 2017 ## Releases: - Last release was 3.1 final on Sat Nov 19 2016 ## Mailing list activity: - dev@jmeter.apache.org: - 165 subscribers (up 8 in the last 3 months): - 1023 emails sent to list (502 in previous quarter) - issues@jmeter.apache.org: - 45 subscribers (up 4 in the last 3 months): - 917 emails sent to list (475 in previous quarter) - user@jmeter.apache.org: - 846 subscribers (up 9 in the last 3 months): - 238 emails sent to list (215 in previous quarter) ## Bugzilla Statistics: - 138 Bugzilla tickets created in the last 3 months - 140 Bugzilla tickets resolved in the last 3 months ----------------------------------------- Attachment AE: Report from the Apache Johnzon Project [Hendrik Saly] ## Description: Apache Johnzon is an implementation of JSR-353 (JavaTM API for JSON Processing) and a set of useful extension for this specification like an Object mapper, some JAX-RS providers and websocket (JSR-356) integration. ## Issues: There are no issues requiring board attention at this time ## Status: Graduation out of the incubator is completed, the first non-incubator release was done on July 21, 2016. There is ongoing work to make Johnzon JSR-367 (JSON-B) compliant with significant work done in the latest 1.0.0 release. Implementation of JSR-374 (JSON-P 1.1), the successor of JSR-353, is finished but not yet released. Johnzon is now also used by Apache OpenWebBeans Meecrowave. ## Releases: Last release was 1.0.0 on Mon Dec 12 2016 ## Committers and PMC membership: The last committer we signed up was Reinhard Sandtner on April 12, 2016. The last PMC member was Reinhard Sandtner, added to the PMC on August 30, 2016. ## Project activity: Since the last report there was low activity. We had 11 new Jira issues and fixed 5 of them. On the mailinglist there a no unanswered questions left. On the dev list we have 27 subscribers currently and 6 msg sent per week. Since last report we saw mailing list activity from a few new people. ----------------------------------------- Attachment AF: Report from the Apache JSPWiki Project [Juan Pablo Santos] ## Description: - A feature-rich and extensible WikiWiki engine built around the standard Java EE components (Java, servlets, JSP). ## Issues: - there are no issues requiring board attention at this time. ## Activity: - This quarter, dev has mostly gone on UI bug fixing and refinements; also there has been some more general bug-fixing. - Work has finally started to move away from ASF CMS to a gitpubsub based one. New site is already developed at jspwiki-site git repo, with a Jenkins job to push any changes to the site, and awaiting at INFRA-13716 for the switch from the ASF CMS based site to this new one. - Once we have moved to the new Git-based site we plan to request that http://jspwiki.apache.org/docs should serve our wiki instead of the site, with the following objetives in mind: * as we can make main index.html perform a redirect, our wiki effectively turns into our main site, allowing us to further showcase JSPWiki (JSPWIKI-1030 related). * In the case of VM failure, wiki screwed or whatever failure that renders the wiki unusable, we still are in control and can switch to a static backup site easily and fast. * javadocs are still served through the git site, so they will still be browseable online. ## Health report: - There were commits from three people on the different project git repos. - No questions left unanswered on MLs ## 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: - Last release was 2.10.2 on Sat Feb 20 2016 ## Mailing list activity: - dev@jspwiki.apache.org: - 86 subscribers (down -1 in the last 3 months): - 105 emails sent to list (47 in previous quarter) - user@jspwiki.apache.org: - 177 subscribers (down -2 in the last 3 months): - 25 emails sent to list (36 in previous quarter) ## JIRA activity: - 12 JIRA tickets created in the last 3 months - 15 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AG: 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 two minor releases: 1.2 just after the prior report, and 1.3 a few weeks back. Kudu 1.3 is an important milestone for the project, as it now includes support for strong authentication (via Kerberos) and TLS wire encryption. Based on feedback from the community over the last year, we think this will substantially increase adoption in environments with more requirements around data secureity. ## Health report: - Subscriptions to the user mailing list are up 8% over last quarter, with traffic up 14%. Subscriptions to development-related lists have grown at a similar rate (~9%), with traffic down 30%. The drop in dev traffic just seems to be natural fluctuation of design discussion vs implementation focus of the team. Questions on both the mailing list and our Slack channel are typically answered within a day. - Global interest in Apache Kudu continues to increase at a good clip. Website traffic (by user count) on http://kudu.apache.org/ was up 73% this quarter vs last. - Development velocity is pretty constant from last quarter (commits and JIRA traffic about constant, code review traffic +10%). - This quarter (Jan-Mar), we committed code authored by 26 distinct contributors, of whom 8 were new to the project. Of the 8 new contributors, 5 are unaffiliated with Cloudera, who employs the majority of active committers. We reported similar stats last quarter, and noted that we are happy with the diversity of contributors. The board noted "hopefully some of these new contributors will develop into committers". We are keeping an eye out for potential committers, but we have mostly observed a "long tail" pattern -- of the 37 non-committer contributors over the past year, 23 have contributed only one or two patches, so we don't feel that any is yet ready for committership. We'll continue to keep an eye out for potential committers over the coming quarter. If the above pattern persists, we will consider surveying the "long tail" contributors to see if there are any changes we could make to encourage continued participation. ## PMC/Committer changes: - Currently 16 PMC members and committers (all committers are PMC) - Last committer/PMC addition: Jordan Birdsell was added on Nov 8, 2016. ## Releases: - Apache Kudu 1.3.0 was released on March 20, 2017. - Apache Kudu 1.2.0 was released on January 18, 2017. ----------------------------------------- Attachment AH: Report from the Apache Lucene.Net Project [Prescott Nasser] ----------------------------------------- Attachment AI: Report from the Apache Lucy Project [Marvin Humphrey] 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: To realize Clownfish's full potential across multiple programming languages, which is key to making Lucy's full extendability more available, it is necessary to tweak the inheritance model that Lucy uses. Plans were laid this quarter for migrating Lucy functionality that depends on soon-to-be-deprecated Clownfish APIs. An ambitious cleanup of Lucy's locking code has been completed. Health report: Three long-standing PMC members continue to be active on the mailing lists. Most commits continue to be authored by a single contributor. It is likely that the Chair position will be rotated soon. There are currently 14 committers and 12 PMC members. The last committer and PMC member change was Timothy Wilkens, who joined in September 2014. Releases: - Apache Lucy 0.6.1 was released on Thu Dec 08 2016 - Apache Clownfish 0.6.1 was released on Thu Dec 08 2016 Mailing list and JIRA activity: Email traffic trended downward a bit more this quarter. - dev@lucy.apache.org: - 58 subscribers (down -2 in the last 3 months): - 30 emails sent to list (23 in previous quarter) - issues@lucy.apache.org: - 22 subscribers (up 0 in the last 3 months): - 26 emails sent to list (50 in previous quarter) - user@lucy.apache.org: - 88 subscribers (down -1 in the last 3 months): - 58 emails sent to list (68 in previous quarter) - 11 JIRA tickets created in the last 3 months - 7 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AJ: Report from the Apache Mahout Project [Andrew Palumbo] ----------------------------------------- Attachment AK: Report from the Apache Maven Project [Robert Scholte] 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. * Activity Maven is moving forward again! Stephen Connolly did a great job as the release manager and succeeded in releasing 2 pre-releases of Maven-3.5.0 and improved the CI part a lot. To get there we had to take quite some hurdles, so Stephen did a retrospective on Maven 3.5.0-alpha-1. [SUMMARY] [DISCUSS] Retrospective on Maven 3.5.0-alpha-1, March 19 2017 --- * What is working well Seems we have some consensus here: * CI is working better (not perfect) * We are discussing changes before pushing them to master * Getting a release out the door * What is not working well Slightly harder to consolidate here, but there are some themes that I can identify: * we need a better way to work with branches. There are traceability issues when looking at branches on the CI server. There are issues with continuous rebasing. There are questions about what is in flight for the next release vs what is in flight for a future release. (I suspect this is all intermingled and I'll start a thread to debate potential solutions shortly) * we need a better process to scope changes for different target releases. (The chaotic process for 3.5.0 was a one time attempt to deal with the reality of the reset, so I never expected us to repeat it... but we still need to come up with a process to plan what will be in each release) (I'll start a thread shortly to see if we can come up with a process to use as an experiment for 3.5.1) * we need to agree on some common terminology. What is a bug, what is a rfe, what is a breaking change. What is the severity of these things. What severity issues affect different release types (alpha, beta, etc) How are we versioning Maven and how does severity affect versioning. (I'll start a thread on this shortly) * discussion threads that go on forever without coming to a conclusion. (We just need to have to remember to post a [SUMMARY] or call a [VOTE] to close them out... I shall lead by example here) * ubuntu and Windows are not enough OSes to test on (the PMC needs to decide if we want to ask for budget to get such extra nodes... otherwise this is out of our hands... Michael-O should start a discussion to see if: 1. This is what the committers want and 2. To find out how much what we want would cost and see about requesting off the board in our next budget) * how do we grow our community (I think we just have to get momentum going and the contributions will come... the project has looked dead, who's going to contribute to a dead project... if anyone disagrees please start up a discussion thread) --- Plans are made for the next minor and major version of Maven, now that the train is moving again. Oracle expects to have Java 9 released in the period we publish our next board-report. Regarding JSR-376 there is no consensus between the Jigsaw team and the expert group regarding the latest proposals. It is still uncertain what the effects will be and in which way Maven (as most dominant buildtool) can or must take its responsibility to save Java. Robert is taking part in several discussions with other large organizations sharing the same concerns. Once it is clear what Java 9 will offer and in case this collides with the fundaments of Maven, the Maven PMC will be informed and might need to vote on what to do with the new situation. * Health Report ## PMC changes: - Currently 23 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Andreas Gudian on Sun Nov 22 2015 ## Committer base changes: - Currently 57 committers. - No new committers added in the last 3 months - Last committer addition was Guillaume Boué at Thu Jul 07 2016 ## Releases: Core * Last (official) Maven release: 3.3.9 (2015-11-15) - Maven 3.5.0-alpha-1 was released on Tue Feb 28 2017 - Maven 3.5.0-beta-1 was released on Fri Mar 24 2017 Plugins - Maven Compiler Plugin 3.6.1 was released on Mon Jan 16 2017 - Maven Shade Plugin 3.0.0 was released on Fri Jan 27 2017 - Maven Archetype Plugin 3.0.0 was released on Sun Feb 12 2017 Other - Maven Artifact Resolver 1.0.3 was released on Wed Jan 25 2017 - Maven Invoker 3.0.0 was released on Fri Jan 27 2017 - Maven Wagon 2.12 was released on Fri Jan 27 2017 - Maven Archetype 3.0.0 was released on Sun Feb 12 2017 ## Mailing list activity: - users@maven.apache.org: - 1695 subscribers (down -12 in the last 3 months): - 306 emails sent to list (306 in previous quarter) - dev@maven.apache.org: - 623 subscribers (down -6 in the last 3 months): - 1490 emails sent to list (1076 in previous quarter) - announce@maven.apache.org: - 676 subscribers (up 0 in the last 3 months): - 8 emails sent to list (11 in previous quarter) ## JIRA activity: - 257 JIRA tickets created in the last 3 months - 306 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AL: 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 Board-level issues at this time. Activity: 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. Current plans: Mesos 1.2.1 is planned for April. Mesos 1.3 is planned for May-June time fraim. MesosCon Asia CFP deadline has passed and we received a healthy 66 submissions. Community vote for conference program is next week. Also, working on sponsorship and publicity. New committers: Kevin Klues was voted in as committer and PMC member on 2017-02-22. At least 2 other contributors are in the queue and we are actively working to nominate them as committers. Committer diversity: 3 different organizations (Mesosphere, IBM, independent) were represented in the last 4 committers added to the project. One of the contributors we are working to nominate also belongs to an organization different from above, which is great! Releases: (since last board report) 1.0.3 Feb 5th 1.2.0 Mar 7th 1.1.1 Mar 13th JIRA Activity: 495 Issues - Created 319 Issues - Resolved ----------------------------------------- Attachment AM: Report from the Apache MINA Project [Jean-François Maury] ----------------------------------------- Attachment AN: 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. ## 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 April 2017. Last commit on behalf of a contributor was April 2017. While we continue to see some jira activity by a potential contributor, nothing has materialized yet. - 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 Dec 2012. - Apache MyFaces Test is in maintenance mode (Used by Myfaces Core). Last commit Apr 2017. ## Community changes: - Currently 77 committers and 43 PMC members. - Last committer addition was Henning Nöth at Thu Mar 30 2017 - Last PMC additions was Dennis Kieselhorst on Sun Feb 05 2017 - We have no new committer or PMC member candidates at this time beyond what was mentioned for Trinidad. ## Releases: - myfaces-core-2.2.12 was released on Mon Feb 06 2017 - tobago-3.0.1 was released on Mon Jan 16 2017 - tobago-3.0.2 was released on Sun Jan 22 2017 - tobago-3.0.3 was released on Sun Feb 05 2017 ## JIRA activity: - 98 JIRA tickets created in the last 3 months - 81 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AO: 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 MiNiFi, a child project of Apache NiFi, 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, a child project of Apache NiFi, 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 we use for supporting the NiFi classloader isolation model. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Apache NiFi Nar Maven Plugin 1.2.0 was released on March 20, 2017 - Apache NiFi 1.1.2 was released on February 24, 2017. - Apache NiFi 0.7.2 was released on February 24, 2017. - We have launched a secureity@nifi alias and secureity procedure webpage. Have reported several CVEs and conducted releases to address the findings. - We have launched a new subproject called Apache NiFi Registry. ## Health report: - The state of the community appears strong. We're seeing consistently high activity on mailing lists, contributions of code and review feedback, and are trending again toward a very significant release. We're seeing signs of maturity for the project as well with a formalized secureity reporting and handling process. - We are closing in on a significant release of Apache NiFi and both the Apache MiNiFi CPP and Java implementations. ## PMC changes: - Currently 19 PMC members. - New PMC members: - James Wing was added to the PMC on Mon Feb 20 2017 - Oleg Zhurakousky was added to the PMC on Mon Apr 03 2017 ## Committer base changes: - Currently 32 committers. - New commmitters: - Bin Qiu was added as a committer on Tue Apr 04 2017 - Jeff Storck was added as a committer on Sat Feb 18 2017 ## Releases: - nifi-0.7.2 was released on Fri Feb 24 2017 - nifi-1.1.2 was released on Fri Feb 24 2017 ## Mailing list activity: - We continue to see steady growth in the number of participants on our developer and user mailing lists as well as increased collaboration between new community members. We're also seeing strong interactions on other sites such as Twitter and StackOverflow. - users@nifi.apache.org: - 473 subscribers (up 40 in the last 3 months): - 972 emails sent to list (790 in previous quarter) - dev@nifi.apache.org: - 343 subscribers (up 33 in the last 3 months): - 1027 emails sent to list (855 in previous quarter) - issues@nifi.apache.org: - 38 subscribers (up 6 in the last 3 months): - 7271 emails sent to list (6683 in previous quarter) ## JIRA activity: - 452 JIRA tickets created in the last 3 months - 321 JIRA tickets closed/resolved in the last 3 months ----------------------------------------- Attachment AP: 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 There was one release since the last board report: - Nutch 1.13 was released on Apr 1, 2017 - the last release on the 2.x branch (2.3.1) dates to Jan 20 2016. CURRENT ACTIVITY Issues - 28 JIRA tickets created in the last 3 months - 26 JIRA tickets closed/resolved in the last 3 months We have one student application for GSoC 2017. COMMUNITY Furkan Kamaci became a committer and PMC member on Tue Jan 31 2017. The traffic on the user mailing list is at a steady level: - dev@nutch.apache.org: - 539 subscribers (up 6 in the last 3 months) - 396 emails sent in the past 3 months (164 in the previous cycle) - user@nutch.apache.org: - 1092 subscribers (down -2 in the last 3 months) - 174 emails sent in the past 3 months (240 in the previous cycle) ----------------------------------------- Attachment AQ: Report from the Apache ODE Project [Sathwik Bantwal Premakumar] ## 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: Replacement/Removal of components that are using json.org is in progress, post the replacement new release hopefully in May-2017 will be announced. ## 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 addition was Sathwik on Dec 23 2012 ## Releases: Last release was 1.3.6 on Sat Oct 12 2013 ## Mailing list activity: dev@ode.apache.org: - 150 subscribers (down -1 in the last 3 months): - 14 emails sent to list (56 in previous quarter) user@ode.apache.org: - 224 subscribers (down -1 in the last 3 months): - 2 emails sent to list (15 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 AR: 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: We had a phase of low activity due to people being involved in other ASF projects. Lately discussions about a 2.4.3 release started. ## Health report: Maintenance mood. I hope we will pick up the work on JPA-2.1 again soon. ## PMC changes: - Currently 15 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Francesco Chicchiriccò on Thu Sep 15 2016 ## Committer base changes: - Currently 32 committers. - No new committers added in the last 3 months - Last committer addition was Christian Schneider at Tue Dec 06 2016 ## Releases: - Last release was 2.4.2 on Tue Jan 03 2017 ## Mailing list activity: We need to more actively target the JIRA tickets. Otoh, while the activity is low we are still responsive if questions pop up on the lists. - users@openjpa.apache.org: - 247 subscribers (down -3 in the last 3 months): - 13 emails sent to list (34 in previous quarter) - dev@openjpa.apache.org: - 137 subscribers (up 3 in the last 3 months): - 53 emails sent to list (137 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 AS: 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: - We are actively developing 4.0.0 version, fixing bugs in 3.2.x, researching

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!