From dev-return-19823-archive-asf-public=cust-asf.ponee.io@accumulo.apache.org Tue Jul 10 02:17:14 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 692F818062A for ; Tue, 10 Jul 2018 02:17:13 +0200 (CEST) Received: (qmail 81223 invoked by uid 500); 10 Jul 2018 00:17:12 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 81207 invoked by uid 99); 10 Jul 2018 00:17:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2018 00:17:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6CE701A0375 for ; Tue, 10 Jul 2018 00:17:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.869 X-Spam-Level: * X-Spam-Status: No, score=1.869 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id w5gOYTD0q2QH for ; Tue, 10 Jul 2018 00:17:09 +0000 (UTC) Received: from mail-it0-f52.google.com (mail-it0-f52.google.com [209.85.214.52]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 8FB805F385 for ; Tue, 10 Jul 2018 00:17:09 +0000 (UTC) Received: by mail-it0-f52.google.com with SMTP id j185-v6so28635345ite.1 for ; Mon, 09 Jul 2018 17:17:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Tyc4JP3fKhpFykImSsGLlCd29RbZJG98pDYkhmqof5o=; b=WcOGIOOJxvsvrl9opmG7esxhd7nV3imEQ6Ot3cy9IqE2COwBIjZ4GnI6HeLui+e3xg 18Lsmnkj8/Xy5Y4e94TG474fPGCVnAyQ85VtRvHNTNnGaZuH1mP54PfnuFc1hlqj4K9s zWcJEzX6tzSoAD3DUFMwmLYnvlO9xgGsmbMm27NYbSH4jcIyg2BX+I/Dh0i1ybZefevm S5DggS701rRtF6kiacFaMpwzmIp4UNt4Q6Z1Oxt8/kxp55eU59MnEHYqOWIaY3MPbAxC Qs0qdXCkSrrx+f3bUJhc6+ttpdNNcD2ysU+BeNW4lJIcmWxY8FGQYo9uNgevWnJHhoIm zCEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Tyc4JP3fKhpFykImSsGLlCd29RbZJG98pDYkhmqof5o=; b=aXRged9CFripWp0tozGO4EwspiN6K+uFI39Y1Do+fOOd3/4O/fWnSfZbF6WD5gSoYx mWYRNBmoIo1VlQkiQ+eCVdm0o/BApkcMpMm7sAZkFux1v7QHbRQ8QJbITfUL3euJDBC/ JysuqTzfOjJYJIem9sDzK3jxUmbiUcoK9yFYu981lt3Yo7oCtP8rpSef8rcH4bdeK6z1 Ip5qUdmp91sY2NQpHw/yXaxaN3z2iFdJQAOzyazv3Ec32tA1qyCABVLkBIiN4VJRqO9d MrmObHqjPkZm/8rUTPcsN6XY5Hfu8gRL1qQHPRJ7Zb3p3P7zh7cBc5rOQKXpqUWtdPrw AjKA== X-Gm-Message-State: APt69E3vFjxt9Pd81r/LyYu75CF33h1UXF3jn4FvyJ/eJAiFEfPvAecC nDuwfCzlnR60AgF/d/RcwT+Q5vDcynicXNsw/il6 X-Google-Smtp-Source: AAOMgpdu9MxIdk+R075vw/cr5QG1/UszW3sGcQaTp1xXvZ8CW1559BfvUDP7rL71gOERjmkuABfuiu+i4p+LfmOrw98= X-Received: by 2002:a24:6402:: with SMTP id t2-v6mr16987822itc.131.1531181828658; Mon, 09 Jul 2018 17:17:08 -0700 (PDT) MIME-Version: 1.0 References: <22740319-75ba-8ad9-ba43-939e74083bd0@gmail.com> In-Reply-To: From: Michael Wall Date: Mon, 9 Jul 2018 20:16:57 -0400 Message-ID: Subject: Re: [DRAFT] [REPORT] Apache Accumulo - July 2018 To: dev@accumulo.apache.org Content-Type: multipart/alternative; boundary="000000000000fbdc2905709a0c89" --000000000000fbdc2905709a0c89 Content-Type: text/plain; charset="UTF-8" Report posted, thanks everyone On Mon, Jul 9, 2018 at 5:36 PM Michael Wall wrote: > Mike D, good catch. Our last report was due at the 18 Apr board meeting, > so I made a date range from 18 Apr to 17 Jul, which is the day before the > board meeting this month. Those number may fluctuate between now and the > board meeting time but should stay constant after the 17. To Mike Walch's > point, I summed the open and closed to get the total for created and closed > during the time range for both issues and PRs. > > Josh, added a comment that we will review the contributors before the next > meeting. Always happy to skip middle steps. > > Thanks guys. > > Mike > > -------------- > > [DRAFT] [REPORT] Apache Accumulo - July 2018 > > > The Apache Accumulo PMC decided to draft its quarterly board > reports on the dev list. Here is a draft of our report which is due > by Wednesday, Jul 11, 1 week before the board meeting on > Wednesday, Jul 18. Please let me know if you have any suggestions. > > I am a little earlier with this one since I will be on vacation 5-15 Jul. > My plan is to submit this report sometime on Mon, Jul 9. > > Mike > > ---------- > > ## Description: > > - The Apache Accumulo sorted, distributed key/value > store is a robust, scalable, high performance data storage system that > features cell-based access control and customizable server-side > processing. It is based on Google's BigTable design and is built on > top of Apache Hadoop, Zookeeper, and Thrift. > > ## Issues: > > - There are no issues requiring board attention at this time. > > ## Activity: > > - There were 2 new releases, Accumulo 1.9.0 and Accumulo 1.9.1 since > the last report. The 1.9.0 release [1] had a critical bug in the Write > Ahead Log (WAL) process that is fixed in 1.9.1 [2]. > - The PMC approved the use of the Apache Accumulo trademark for the > 5th annual Accumulo Summit, to be held on October 15, 2018 in Columbia, > MD. > - There were no new committers since the last report. All committers > are also PMC members. We will review contributors during the next 3 > months > to see if anyone should be invited to become a committer. > - The PMC decided to switch to using github issue for the project and all > subprojects [3], which is why the Jira activity dropped off. Github > issues > and pull request statistics are included below. > - Another bug has been found in the WAL process and a 1.9.2 is in the > works. > > ## Health report: > > - The project remains healthy. Activity levels on mailing lists, issues > and pull > requests remain constant. > > ## PMC changes: > > - Currently 34 PMC members. > - No new PMC members added in the last 3 months > - Last PMC addition was Nick Felts on Thu Mar 22 2018 > > ## Committer base changes: > > - See PMC changes, all committers are PMC members currently. > > ## Releases: > > - accumulo-1.9.0 was released on Tue Apr 17 2018 > - accumulo-1.9.1 was released on Sun May 13 2018 > > ## Mailing list activity: > > - Nothing significant in the figures > > ## Issue activity: > > - 49 issued created [4] and 28 closed [5] in the last 3 months > - 75 pull requests created [6] and 67 closed [7] in the last 3 months > > [1]: https://accumulo.apache.org/release/accumulo-1.9.0/ > [2]: https://accumulo.apache.org/release/accumulo-1.9.1/ > [3]: > https://accumulo.apache.org/blog/2018/03/16/moving-to-github-issues.html > [4]: > https://github.com/apache/accumulo/issues?utf8=%E2%9C%93&q=is%3Aissue+created%3A2018-04-18..2018-07-17+ > [5]: > https://github.com/apache/accumulo/issues?utf8=%E2%9C%93&q=is%3Aissue+closed%3A2018-04-18..2018-07-17+ > [6]: > https://github.com/apache/accumulo/pulls?utf8=%E2%9C%93&q=is%3Apr+created%3A2018-04-18..2018-07-17+ > [7]: > https://github.com/apache/accumulo/pulls?q=is%3Apr+closed%3A2018-04-18..2018-07-17+ > > On Mon, Jul 9, 2018 at 5:14 PM Josh Elser wrote: > >> >> >> On 7/9/18 4:54 PM, Michael Wall wrote: >> > Josh, I am not clear on what you are suggesting for another action item. >> > Are you suggesting a pass over contributors to add see if anyone should >> be >> > invited to become a committer or are you suggesting we revisit that >> every >> > committer becomes a PMC member? >> >> If we say that we have no added any new committers/PMC members in a long >> period of time, the board will most assuredly say "Have you looked at >> your contributors to see if you should invite some to be committers?" >> >> I was trying to suggest that we proactively tell them "we know we need >> to see if there are contributors to invite to be committers" in order to >> save that middle step. No need to do this -- just trying to be helpful >> based on what I see over and over again from the board :) >> > --000000000000fbdc2905709a0c89--