Thanks Anthony for the initial status. Here are the stats for the month:
## Mailing list activity: - dev@geode.apache.org: - 154 subscribers (down -4 in the last 3 months): - 3117 emails sent to list (1573 in previous quarter) - iss...@geode.apache.org: - 55 subscribers (up 0 in the last 3 months): - 1983 emails sent to list (2807 in previous quarter) - u...@geode.apache.org: - 201 subscribers (up 16 in the last 3 months): - 301 emails sent to list (161 in previous quarter) ## JIRA activity: - 298 JIRA tickets created in the last 3 months - 264 JIRA tickets closed/resolved in the last 3 months --Mark On Mon, Jan 9, 2017 at 9:43 AM, Anthony Baker <aba...@pivotal.io> wrote: > Mark, can you add in the subscriber numbers so we can be ready to submit > the report by Wed Jan 11? > > Thanks, > Anthony > > > On Jan 5, 2017, at 2:08 PM, Anthony Baker <aba...@pivotal.io> wrote: > > > > I volunteered! > > > > Here’s a rough draft, please review and comment: > > > > ## Description: > > - Apache Geode provides a database-like consistency model, reliable > transaction processing and a shared-nothing architecture to maintain very > low latency performance with high concurrency processing. > > > > ## Issues: > > - There are no issues requiring board attention at this time. > > > > ## Activity: > > - New proposal on improving JSON serialization and extending the > serialization framework to allow other libraries to be used. > > - Example code is moving to a new repo to make it easier for end users > to acquire and run the examples. > > - Lots of discussion around product configuration and how it ought to > work > > > > ## Health report: > > - We have received contributions from 10 new community members (more > than 30 code submissions as well as email and JIRA’s). > > - In December we saw the mailing list activity on dev@geode more than > double compared to the previous month. > > - We’re continuing to work on attracting new contributors and making it > easier to participate in the community. > > - We need to nominate a release manager for v1.1.0 and issue our next > release. > > > > ## PMC changes: > > - TBD > > > > ## Committer base changes: > > - TBD > > > > ## Releases: > > - Last release was 1.0.0-incubating issued on October 25, 2016. > > > > ## Mailing list activity: > > - dev@geode.apache.org <mailto:dev@geode.apache.org>: > > - PMC Chair to provide subscriber details > > - 1493 emails sent to list (591 in previous month) > > - iss...@geode.apache.org <mailto:iss...@geode.apache.org>: > > - PMC Chair to provide subscriber details > > - 694 emails sent to list (765 in previous month) > > - u...@geode.apache.org <mailto:u...@geode.apache.org>: > > - PMC Chair to provide subscriber details > > - 146 emails sent to list (52 in previous month) > > > > ## JIRA activity: > > - PMC Chair is able to provide statistics > > > > > > Anthony > > > > > >> On Jan 4, 2017, at 9:31 AM, Anthony Baker <aba...@pivotal.io <mailto: > aba...@pivotal.io>> wrote: > >> > >> Any volunteers to write the Jan report? Given that it needs to be > submitted by 1/11 we need a draft posted for review in the next few days. > >> > >> Anthony > >> > >> > >>> Begin forwarded message: > >>> > >>> From: Brett Porter <br...@apache.org <mailto:br...@apache.org>> > >>> Subject: ASF Board Report for Geode - Initial Reminder for January 2017 > >>> Date: December 27, 2016 at 1:53:30 PM PST > >>> To: Mark Bretl <mbr...@apache.org <mailto:mbr...@apache.org>> > >>> Cc: priv...@geode.apache.org <mailto:priv...@geode.apache.org> > >>> Reply-To: priv...@geode.apache.org <mailto:priv...@geode.apache.org> > >>> > >>> This email was sent on behalf of the ASF Board. It is an initial > reminder to > >>> give you plenty of time to prepare the report. > >>> > >>> According to board records, you are listed as the chair of a committee > that is > >>> due to submit a report this month. [1] [2] > >>> > >>> The meeting is scheduled for Wed, 18 Jan 2017 at 10:30 PST and the > deadline for > >>> submitting your report is 1 full week prior to that (Wed Jan 11th)! > >>> > >>> Meeting times in other time zones: > >>> > >>> http://timeanddate.com/s/34r0 <http://timeanddate.com/s/34r0> > >>> > >>> Please submit your report with sufficient time to allow the board > members > >>> to review and digest. Again, the very latest you should submit your > report > >>> is 1 full week (7days) prior to the board meeting (Wed Jan 11th). > >>> > >>> If you feel that an error has been made, please consult [1] and if > there > >>> is still an issue then contact the board directly. > >>> > >>> As always, PMC chairs are welcome to attend the board meeting. > >>> > >>> Thanks, > >>> The ASF Board > >>> > >>> [1] - https://svn.apache.org/repos/private/committers/board/commit > tee-info.txt <https://svn.apache.org/repos/private/committers/board/commi > ttee-info.txt> > >>> [2] - https://svn.apache.org/repos/private/committers/board/calend > ar.txt <https://svn.apache.org/repos/private/committers/board/calendar.txt > > > >>> [3] - https://svn.apache.org/repos/private/committers/board/templates > <https://svn.apache.org/repos/private/committers/board/templates> > >>> [4] - https://reporter.apache.org/ <https://reporter.apache.org/> > >>> > >>> > >>> Submitting your Report > >>> ---------------------- > >>> > >>> Full details about the process and schedule are in [1]. > >>> > >>> The report should be committed to the meeting agenda in the board > directory > >>> in the foundation repository, trying to keep a similar format to the > others. > >>> This can be found at: > >>> > >>> https://svn.apache.org/repos/private/foundation/board < > https://svn.apache.org/repos/private/foundation/board> > >>> > >>> Reports can also be posted using the online agenda tool: > >>> > >>> https://whimsy.apache.org/board/agenda/2017-01-18/Geode < > https://whimsy.apache.org/board/agenda/2017-01-18/Geode> > >>> > >>> Your report should also be sent in plain-text format to > bo...@apache.org <mailto:bo...@apache.org> > >>> with a Subject line that follows the below format: > >>> > >>> Subject: [REPORT] Geode - January 2017 > >>> > >>> Cutting and pasting directly from a Wiki is not acceptable due to > formatting > >>> issues. Line lengths should be limited to 77 characters. > >>> > >>> Chairs may use the Apache Reporter Service [4] to help them compile and > >>> submit a board report. > >>> > >>> > >>> Resolutions > >>> ----------- > >>> > >>> There are several templates for use for various Board resolutions. > >>> They can be found in [3] and you are encouraged to use them. It is > >>> strongly recommended that if you have a resolution before the board, > >>> you are encouraged to attend that board meeting. > >> > > > >
