Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

## PMC changes:

 
- None. There are currently 8 PMC members.
 
 ## Committer base changes:
  
- None. There are currently 8 committers.

## Releases:

- Apache Streams 0.5.1 was released on January 09, 2017

- We now have four experienced release managers on the PMC

## Mailing list activity:

21 Emails sent during these 92 days, up 0 (0%) compared to previous 92 days.

6 topics started during these 92 days, down 3 (-33%) compared to previous 92 days.

6 Participants during these 92 days, down 5 (-45%) compared to previous 92 days.

https://s.apache.org/GTrn

Image RemovedImage Added

## JIRA Statistics:

36 new, 28 resolved

https://s.apache.org/plwc

Image RemovedImage Added

## Website Traffic (3 month) 

953 1141 sessions, up 5920.90% 11% compared to previous 3 months.

865 1014 users, up 8917.28% 77% compared to previous 3 months.

https://s.apache.org/D0pl

View file
nameStreams Web Site Data January 2018.pdf
pageDraft Board Report - January 2018
spaceSTREAMS
height250

 

 

## Upcoming Project Initiatives:

- Add official support for Schema.org and Activity Streams 2.0 data types.

- Consolide streams-examples into primary streams repository, simplifying deployment and release process. 

- Drop remaining maven dependencies on java SDKs for accessing third-party APIs in favor of HTTP/REST interfaces powered by Apache Juneau Remoteable Annotations.

- More tweets and blog posts of zeppelin notebooks demonstrating data pipelines and analyses based on Apache Streams.

- More official examples in source tree demonstrating integration of Apache Streams with complementary technologies.

- Improve the interfaces by which components are created, configured, activated, and executed via SDK and CLI.

- Official Binaries and Containers that can be integrated with Apache Kibble.

- Reduce disparities between normalized activities and objects of like type collected from various data sources. 

- Reduce disparities between the configuration objects that initialize similar providers from various data sources.