Podling Report Reminder - May 2018

[johndament]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 16 May 2018, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, May 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/May2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Heron OSS Sync

[Ning Wang]

And here are a brief notes:



* - The first meetup went very well last evening! 60+ attendees. Next
meetup will be in May and could be hackthon format. 200+ followers in the
meetup channel now.- Making an apache release (v0.2.0) is our priority.
Package name changed. Copy right to update. Need to remove binaries. Thrift
0.5.0 is used by Twitter. To remove by Twitter team. Need to sync with
apache infra for the infra part.- Stateful processing in progress. Found
missing functions (stream repartitioning, sink data deduplication).-
Stateful storage layer revisiting- Modeling the traffic evaluation system.-
Integration tests for the Scala streamlet API, as well as the
documentation. Pretty much ready. Scala bazel rule is special and needs to
be doublechecked- New resource config proposal. Could be helpful for some
users.- Container pipeline is in progress.- SQL API in progress too.
Looking into issue with Intellij.*

On Tue, Apr 24, 2018 at 1:55 PM, Ning Wang  wrote:

> Will be happening today at 2.00 pm PST. Please use the following hangou
> link:
> https://hangouts.google.com/hangouts/_/streaml.io/oss-heron-
> sync?authuser=0
>
>
> See you all then.
>

Heron OSS Sync

[Ning Wang]

Will be happening today at 2.00 pm PST. Please use the following hangou
link:
https://hangouts.google.com/hangouts/_/streaml.io/oss-heron-sync?authuser=0


See you all then.

[GitHub] huijunw opened a new issue #2873: [healthmgr] heron-aurora-scheduler.jar is needed in heron-core.tar.gz

[GitBox]

huijunw opened a new issue #2873: [healthmgr] heron-aurora-scheduler.jar is 
needed in heron-core.tar.gz
URL: https://github.com/apache/incubator-heron/issues/2873
 
 
   The present heron-core.tar.gz does not include heron-aurora-scheduler.jar 
file. This jar file is needed in 
https://github.com/apache/incubator-heron/blob/master/heron/healthmgr/src/java/org/apache/heron/healthmgr/HealthManager.java#L394
   
   
![auroraerror](https://user-images.githubusercontent.com/23125934/39208454-e133ea3a-47b7-11e8-88e3-8c1aeb666ee1.PNG)
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services