samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yi Pan <nickpa...@gmail.com>
Subject [REPORT] Apache Samza - Jan 2018
Date Thu, 11 Jan 2018 08:12:46 GMT
Submitted via Whimsy. Re-posting to dev list as well.

## Description:

 - Apache Samza is a distributed stream processing engine that are highly
   configurable to process events from various data sources, including
   real-time messaging system (e.g. Kafka) and distributed file systems (e.g.
   HDFS).

## Issues:
There were comments from board members requesting answers from PMC in the last
report. I have answered in an email earlier. Just to include the answers again
since it seems to be asked multiple times:

Board questions: jj: I am assuming the LinkedIn meet up occurred?

  rb: I'm very concerned that Mark has asked a question two quarters in a row
  and still received no response. It's not even so much that the question
  itself is urgent, but that you don't appear to be reading board feedback to
  your reports.

  ps: The 9/12 meetup at LinkedIn was announced on the dev list on 8/24 and
  9/12. It appears to have been open to all interested parties. Attendance
  does appear to have required an NDA signed by attendees. It looks more like
  info share than anything actually project dev related. Here is the link from
  the mail to the dev list:

      https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/242656767/?_cookie-check=UErnFE0-NfeCLKWx

My previous answers to the above questions:

A. Yes, LinkedIn meetup was hold on 9/12

B. Yes we do read board's feedbacks and I have already responded with answers
to Marks question in
July:https://mail-search.apache.org/pmc/private-arch/samza-private/201707.mbox/%3CCAFvExu15wywrCpfcxEjUduC2nJs9UgFKCVyti5sFLQ7wi2moog@mail.gmail.com%3E

C. To restate what I have answered in my response to Board's feedback in July,
the meetup was announced via Meetup website, advertised via LinkedIn, tweet,
and Samza dev list. We share the usage information, discuss the features
needed and pain points user has encountered. Once a while, we also share our
development roadmap on big features coming in Samza. Those are all dev
related. Testimony in the exact link listed in the response, you can find the
following description in Redfin's presentation: "Samza is being used at
Redfin, and suggest some features that we'd like to see in Samza". And here is
another meetup where we talk about the roadmap of Samza
development:https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/234454163/.
And new features like async API in Samza in yet another
meetup:https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/237171557/,
and high-level API in
Samza:https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/238303422/.

Hope that I have answered all your questions.


## Activity:
 - We have another Stream Processing meetup in Dec 2017:
   https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/244889719/
 - Samza talk in BigDataSpain'17: Nov 2017 - Unified Stream Processing at
   Scale with Apache Samza

## Health report:
 - Project is in healthy status with a lot of development activities in
   continuation (e.g. SamzaSQL, table API, Samza-on-Azure, Kinesis consumer)
 - Promotion of new PMC member in progress

## PMC changes:

 - Currently 13 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Jagadish Venkatraman on Thu Sep 14 2017

## Committer base changes:

 - Currently 18 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Boris Shkolnik at Mon Oct 02 2017

## Releases:

 - 0.14.0 was released on Thu Jan 04 2018

## Mailing list activity:

 - dev@samza.apache.org:
    - 293 subscribers (up 0 in the last 3 months):
    - 263 emails sent to list (288 in previous quarter)


## JIRA activity:

 - 102 JIRA tickets created in the last 3 months
 - 78 JIRA tickets closed/resolved in the last 3 months

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message