Re: Podling Report Reminder - May 2018

[Karthik Ramasamy]

Josh - Looks good to me.

> On May 1, 2018, at 2:44 PM, Josh Fischer  wrote:
> 
> Hi All,
> 
> Please see below and feel free to make any suggestions.  I have updated the
> status report based on Bill's feedback.
> 
> -
> 
> Heron
> 
> A real-time, distributed, fault-tolerant stream processing engine.
> 
> Heron has been incubating since 2017-06-23.
> 
> Three most important issues to address in the move towards graduation:
> 
>  1. Finish bootstrapping project, IP clearance, initial website
>  2. Expanding the community and adding new committers
>  3. 1st ASF release
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> 
> Extracting all binaries out of code base is still in progress.  There is
> only one binary left.
> Internal developers from Twitter are working on this process.
> 
> How has the community developed since the last report?
> 
>  * The number of contributors to the project has increased from 82 to 87
> since the last report.
>  * A meetup was hosted at Twitter HQ in Sunnyvale, CA with approximately
> 80 in attendance
> 
> 
> How has the project developed since the last report?
> 
>  * Development has been very active.
>  * Twitter has submitted a signed SGA, granting ownership of Heron to
> Apache
>  * The repository has been moved from Twitter's github account to Apache
> git
>  * The appropriate work has been completed for package renaming.
> com.twitter has now been changed to org.apache
>  * All of the binaries have been removed from the code base with the
> exception of Scribe.  Twitter developers are to finish this task.
> 
> 
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
> 
>  [ ] Initial setup
>  [x] Working towards first release
>  [ ] Community building
>  [ ] Nearing graduation
>  [ ] Other:
> 
> Date of last release:
> 
>  No Apache releases as of yet. The first Apache release will happen soon
> once all binaries are removed from the codebase.
> 
> When were the last committers or PPMC members elected?
> 
>  N/A, still bootstrapping the project.
> 
> Signed-off-by:
> 
>  [ ](heron) Jake Farrell
> Comments:
>  [ ](heron) Jacques Nadeau
> Comments:
>  [ ](heron) Julien Le Dem
> Comments:
>  [](heron) P. Taylor Goetz
> Comments:
> 
> On Tue, May 1, 2018 at 3:35 PM, Josh Fischer  wrote:
> 
>> Will add tonight.  Thank you for the guidance.
>> 
>> 
>> On Tue, May 1, 2018 at 3:33 PM Bill Graham  wrote:
>> 
>>> Thanks again Josh for taking on the updates. In terms of project
>>> development, it would be good to include specifics, like:
>>> 
>>> 1. Twitter submitted a signed SGA granting the code to Apache.
>>> 2. The repository moved from Twitter's github to Apache git
>>> 
>>> You could also give an update on the package naming change to org.apache
>>> if
>>> there is any progress to report on that  If there was progress on removing
>>> the binaries from the source repo we could include that too. Both of those
>>> are work required towards the first apache release.
>>> 
>>> For community development you can discuss the meetup hosted at Twitter
>>> last
>>> week.
>>> 
>>> 
>>> 
>>> On Tue, May 1, 2018 at 1:02 PM, Josh Fischer  wrote:
>>> 
 Hello All,
 
 Please review the status report for May for review.  It is to be added
>>> to
 https://wiki.apache.org/incubator/May2018 by tomorrow.  Please review
>>> and
 comment.
 
 -
 
 Heron
 
 A real-time, distributed, fault-tolerant stream processing engine.
 
 Heron has been incubating since 2017-06-23.
 
 Three most important issues to address in the move towards graduation:
 
  1. Finish bootstrapping project, IP clearance, initial website
  2. Expanding the community and adding new committers
  3. 1st ASF release
 
 Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
 aware of?
 
 Extracting all binaries out of code base is still in progress.
 Work is in progress to complete this task.
 
 How has the community developed since the last report?
 
  * The number of contributors to the project has increased from 82 to
>>> 87
 since the last report.
 
 How has the project developed since the last report?
 
  * Development has been very active
 
 How would you assess the podling's maturity?
 Please feel free to add your own commentary.
 
  [ ] Initial setup
  [x] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:
 
 Date of last release:
 
  No Apache releases as of yet. The first Apache release will happen
>>> soon
 once all binaries are removed from the codebase.
 
 When were the last committers or PPMC members elected?
 
  N/A, still bootstrapping the project.
 
 Signed-off-by:
 

Re: Copyright Violations

[Ning Wang]

Thanks for bringing it up!

Too many things going on and we haven't got time to update the license text
yet. We will work on it.

This is the first update on the NOTICE file. Does it look ok this way?
https://github.com/apache/incubator-heron/pull/2878

Thanks in advance.



On Tue, May 1, 2018 at 6:53 PM, Dave Fisher  wrote:

> See https://www.apache.org/legal/src-headers.html#faq-moveothercopyright
>
> Copyrights go in the NOTICE and not the source.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On May 1, 2018, at 6:47 PM, Karthik Ramasamy  wrote:
> >
> > Taylor -
> >
> > As Ali pointed out these are pending task items. One of the major task
> that
> > we finished is converting the namespace from com.twitter.heron to
> > org.apache.heron.
> >
> > Sree is working on converting the copyrights to use Apache copyrights.
> One
> > of the question he had is whether the copyright can use one line or it
> > should be multi line.
> >
> > It will be great if you could provide advice on this - so that we can
> > change the copyright accordingly.
> >
> > cheers
> > /karthik
> >
> >
> >> On Tue, May 1, 2018 at 5:42 PM, Ali Ahmed  wrote:
> >>
> >> Hi Taylor ,
> >>
> >> There are some tasks pending in this regard , the goal is to remove all
> >> twitter copyright headers soon , some of the commits are in and some are
> >> remaining .
> >>
> >> -Ali
> >>
> >>> On May 1, 2018, at 5:37 PM, P. Taylor Goetz  wrote:
> >>>
> >>> Heron PPMC,
> >>>
> >>> I’ve mentioned this before, but IMO, this practice needs to stop.
> >>>
> >>> The community default seems to be to apply the Apache license header
> >> with a twitter copyright assertion on all files, even ones copied from
> >> other ALv2-licensed projects.
> >>>
> >>> Twitter can’t assert copyright on code their employees didn’t create,
> >> though, at least in this project, they continue to do so. I find this
> >> practice unacceptable.
> >>>
> >>> Please reconsider even including “Copyright Twitter $date” at all in
> >> license headers. That’s more suitable for the NOTICE file, and removed
> from
> >> the source header.
> >>>
> >>> Aside from having a twitter account, I have no affiliation with
> twitter.
> >> As a mentor I was surprised and disappointed to see a Twitter copyright
> >> applied to my own (implicitly copyrighted) work. That’s not cool, nor
> >> really (IANAL) legal.
> >>>
> >>> I would appreciate if this could be corrected. This kind of thing is
> >> something podlings need to know how to address proactively.
> >>>
> >>> -Taylor
> >>
> >>
>

[GitHub] nwangtw opened a new pull request #2878: Update NOTICE file

[GitBox]

nwangtw opened a new pull request #2878: Update NOTICE file
URL: https://github.com/apache/incubator-heron/pull/2878
 
 
   


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

Re: Heron github emails

[FatJ Love]

+1

On Tue, May 1, 2018 at 7:00 PM, Chris Kellogg  wrote:

> +1
>
> On Tue, May 1, 2018 at 4:45 PM, Karthik Ramasamy 
> wrote:
>
> > +1 as well.
> >
> > On Tue, May 1, 2018 at 3:53 PM Josh Fischer  wrote:
> >
> > > I’m on board with sending git commits to commits@.
> > >
> > > +1
> > >
> > > On Tue, May 1, 2018 at 5:20 PM Bill Graham 
> wrote:
> > >
> > > > Hi,
> > > >
> > > > Ever since migrating to Apache's gitbox, the dev list has been
> > dominated
> > > by
> > > > gitbox comment emails. See
> > > > https://lists.apache.org/list.html?d...@heron.apache.org
> > > >
> > > > It seems a bit heavy handed (i.e. spammy) to have every comment
> emailed
> > > to
> > > > the dev lis, especially when git has features to let people control
> > their
> > > > notifications. What do people think about disabling the git comments
> to
> > > the
> > > > dev list? Or we could have the git comments sent to commits@
> instead.
> > > >
> > > > Thoughts?
> > > >
> > > > Bill
> > > >
> > > --
> > > Sent from A Mobile Device
> > >
> >
>

Re: Heron github emails

[Chris Kellogg]

+1

On Tue, May 1, 2018 at 4:45 PM, Karthik Ramasamy  wrote:

> +1 as well.
>
> On Tue, May 1, 2018 at 3:53 PM Josh Fischer  wrote:
>
> > I’m on board with sending git commits to commits@.
> >
> > +1
> >
> > On Tue, May 1, 2018 at 5:20 PM Bill Graham  wrote:
> >
> > > Hi,
> > >
> > > Ever since migrating to Apache's gitbox, the dev list has been
> dominated
> > by
> > > gitbox comment emails. See
> > > https://lists.apache.org/list.html?d...@heron.apache.org
> > >
> > > It seems a bit heavy handed (i.e. spammy) to have every comment emailed
> > to
> > > the dev lis, especially when git has features to let people control
> their
> > > notifications. What do people think about disabling the git comments to
> > the
> > > dev list? Or we could have the git comments sent to commits@ instead.
> > >
> > > Thoughts?
> > >
> > > Bill
> > >
> > --
> > Sent from A Mobile Device
> >
>

Re: Copyright Violations

[Dave Fisher]

See https://www.apache.org/legal/src-headers.html#faq-moveothercopyright

Copyrights go in the NOTICE and not the source.

Regards,
Dave

Sent from my iPhone

> On May 1, 2018, at 6:47 PM, Karthik Ramasamy  wrote:
> 
> Taylor -
> 
> As Ali pointed out these are pending task items. One of the major task that
> we finished is converting the namespace from com.twitter.heron to
> org.apache.heron.
> 
> Sree is working on converting the copyrights to use Apache copyrights. One
> of the question he had is whether the copyright can use one line or it
> should be multi line.
> 
> It will be great if you could provide advice on this - so that we can
> change the copyright accordingly.
> 
> cheers
> /karthik
> 
> 
>> On Tue, May 1, 2018 at 5:42 PM, Ali Ahmed  wrote:
>> 
>> Hi Taylor ,
>> 
>> There are some tasks pending in this regard , the goal is to remove all
>> twitter copyright headers soon , some of the commits are in and some are
>> remaining .
>> 
>> -Ali
>> 
>>> On May 1, 2018, at 5:37 PM, P. Taylor Goetz  wrote:
>>> 
>>> Heron PPMC,
>>> 
>>> I’ve mentioned this before, but IMO, this practice needs to stop.
>>> 
>>> The community default seems to be to apply the Apache license header
>> with a twitter copyright assertion on all files, even ones copied from
>> other ALv2-licensed projects.
>>> 
>>> Twitter can’t assert copyright on code their employees didn’t create,
>> though, at least in this project, they continue to do so. I find this
>> practice unacceptable.
>>> 
>>> Please reconsider even including “Copyright Twitter $date” at all in
>> license headers. That’s more suitable for the NOTICE file, and removed from
>> the source header.
>>> 
>>> Aside from having a twitter account, I have no affiliation with twitter.
>> As a mentor I was surprised and disappointed to see a Twitter copyright
>> applied to my own (implicitly copyrighted) work. That’s not cool, nor
>> really (IANAL) legal.
>>> 
>>> I would appreciate if this could be corrected. This kind of thing is
>> something podlings need to know how to address proactively.
>>> 
>>> -Taylor
>> 
>> 

Re: Copyright Violations

[Dave Fisher]

Hi Ali,

Where are pending tasks and plans discussed and recorded so that folks can find 
out and participate.

What I am saying is you are having sync ups and not publishing minutes. You 
also announce the sync up 5 minutes beforehand. Decisions need to come to this 
mailing list.

How was the Meetup last week?

Apache projects are global which actually means that asynchronous communication 
and letting the world turn for three days is a common rule to the Apache Way.

Regards,
Dave

Sent from my iPhone

> On May 1, 2018, at 5:42 PM, Ali Ahmed  wrote:
> 
> Hi Taylor , 
> 
> There are some tasks pending in this regard , the goal is to remove all 
> twitter copyright headers soon , some of the commits are in and some are 
> remaining .
> 
> -Ali
> 
>> On May 1, 2018, at 5:37 PM, P. Taylor Goetz  wrote:
>> 
>> Heron PPMC,
>> 
>> I’ve mentioned this before, but IMO, this practice needs to stop.
>> 
>> The community default seems to be to apply the Apache license header with a 
>> twitter copyright assertion on all files, even ones copied from other 
>> ALv2-licensed projects.
>> 
>> Twitter can’t assert copyright on code their employees didn’t create, 
>> though, at least in this project, they continue to do so. I find this 
>> practice unacceptable.
>> 
>> Please reconsider even including “Copyright Twitter $date” at all in license 
>> headers. That’s more suitable for the NOTICE file, and removed from the 
>> source header.
>> 
>> Aside from having a twitter account, I have no affiliation with twitter. As 
>> a mentor I was surprised and disappointed to see a Twitter copyright applied 
>> to my own (implicitly copyrighted) work. That’s not cool, nor really (IANAL) 
>> legal.
>> 
>> I would appreciate if this could be corrected. This kind of thing is 
>> something podlings need to know how to address proactively.
>> 
>> -Taylor
> 

Re: Copyright Violations

[Karthik Ramasamy]

Taylor -

As Ali pointed out these are pending task items. One of the major task that
we finished is converting the namespace from com.twitter.heron to
org.apache.heron.

Sree is working on converting the copyrights to use Apache copyrights. One
of the question he had is whether the copyright can use one line or it
should be multi line.

It will be great if you could provide advice on this - so that we can
change the copyright accordingly.

cheers
/karthik


On Tue, May 1, 2018 at 5:42 PM, Ali Ahmed  wrote:

> Hi Taylor ,
>
> There are some tasks pending in this regard , the goal is to remove all
> twitter copyright headers soon , some of the commits are in and some are
> remaining .
>
> -Ali
>
> > On May 1, 2018, at 5:37 PM, P. Taylor Goetz  wrote:
> >
> > Heron PPMC,
> >
> > I’ve mentioned this before, but IMO, this practice needs to stop.
> >
> > The community default seems to be to apply the Apache license header
> with a twitter copyright assertion on all files, even ones copied from
> other ALv2-licensed projects.
> >
> > Twitter can’t assert copyright on code their employees didn’t create,
> though, at least in this project, they continue to do so. I find this
> practice unacceptable.
> >
> > Please reconsider even including “Copyright Twitter $date” at all in
> license headers. That’s more suitable for the NOTICE file, and removed from
> the source header.
> >
> > Aside from having a twitter account, I have no affiliation with twitter.
> As a mentor I was surprised and disappointed to see a Twitter copyright
> applied to my own (implicitly copyrighted) work. That’s not cool, nor
> really (IANAL) legal.
> >
> > I would appreciate if this could be corrected. This kind of thing is
> something podlings need to know how to address proactively.
> >
> > -Taylor
>
>

Copyright Violations

[P. Taylor Goetz]

Heron PPMC,

I’ve mentioned this before, but IMO, this practice needs to stop.

The community default seems to be to apply the Apache license header with a 
twitter copyright assertion on all files, even ones copied from other 
ALv2-licensed projects.

Twitter can’t assert copyright on code their employees didn’t create, though, 
at least in this project, they continue to do so. I find this practice 
unacceptable.

Please reconsider even including “Copyright Twitter $date” at all in license 
headers. That’s more suitable for the NOTICE file, and removed from the source 
header.

Aside from having a twitter account, I have no affiliation with twitter. As a 
mentor I was surprised and disappointed to see a Twitter copyright applied to 
my own (implicitly copyrighted) work. That’s not cool, nor really (IANAL) legal.

I would appreciate if this could be corrected. This kind of thing is something 
podlings need to know how to address proactively.

-Taylor


signature.asc
Description: Message signed with OpenPGP

Re: Heron github emails

[Josh Fischer]

I’m on board with sending git commits to commits@.

+1

On Tue, May 1, 2018 at 5:20 PM Bill Graham  wrote:

> Hi,
>
> Ever since migrating to Apache's gitbox, the dev list has been dominated by
> gitbox comment emails. See
> https://lists.apache.org/list.html?d...@heron.apache.org
>
> It seems a bit heavy handed (i.e. spammy) to have every comment emailed to
> the dev lis, especially when git has features to let people control their
> notifications. What do people think about disabling the git comments to the
> dev list? Or we could have the git comments sent to commits@ instead.
>
> Thoughts?
>
> Bill
>
-- 
Sent from A Mobile Device

Heron github emails

[Bill Graham]

Hi,

Ever since migrating to Apache's gitbox, the dev list has been dominated by
gitbox comment emails. See
https://lists.apache.org/list.html?d...@heron.apache.org

It seems a bit heavy handed (i.e. spammy) to have every comment emailed to
the dev lis, especially when git has features to let people control their
notifications. What do people think about disabling the git comments to the
dev list? Or we could have the git comments sent to commits@ instead.

Thoughts?

Bill

Re: Podling Report Reminder - May 2018

[Josh Fischer]

Hi All,

Please see below and feel free to make any suggestions.  I have updated the
status report based on Bill's feedback.

-

Heron

A real-time, distributed, fault-tolerant stream processing engine.

Heron has been incubating since 2017-06-23.

Three most important issues to address in the move towards graduation:

  1. Finish bootstrapping project, IP clearance, initial website
  2. Expanding the community and adding new committers
  3. 1st ASF release

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

Extracting all binaries out of code base is still in progress.  There is
only one binary left.
Internal developers from Twitter are working on this process.

How has the community developed since the last report?

  * The number of contributors to the project has increased from 82 to 87
since the last report.
  * A meetup was hosted at Twitter HQ in Sunnyvale, CA with approximately
80 in attendance


How has the project developed since the last report?

  * Development has been very active.
  * Twitter has submitted a signed SGA, granting ownership of Heron to
Apache
  * The repository has been moved from Twitter's github account to Apache
git
  * The appropriate work has been completed for package renaming.
com.twitter has now been changed to org.apache
  * All of the binaries have been removed from the code base with the
exception of Scribe.  Twitter developers are to finish this task.


How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [x] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  No Apache releases as of yet. The first Apache release will happen soon
once all binaries are removed from the codebase.

When were the last committers or PPMC members elected?

  N/A, still bootstrapping the project.

Signed-off-by:

  [ ](heron) Jake Farrell
 Comments:
  [ ](heron) Jacques Nadeau
 Comments:
  [ ](heron) Julien Le Dem
 Comments:
  [](heron) P. Taylor Goetz
 Comments:

On Tue, May 1, 2018 at 3:35 PM, Josh Fischer  wrote:

> Will add tonight.  Thank you for the guidance.
>
>
> On Tue, May 1, 2018 at 3:33 PM Bill Graham  wrote:
>
>> Thanks again Josh for taking on the updates. In terms of project
>> development, it would be good to include specifics, like:
>>
>> 1. Twitter submitted a signed SGA granting the code to Apache.
>> 2. The repository moved from Twitter's github to Apache git
>>
>> You could also give an update on the package naming change to org.apache
>> if
>> there is any progress to report on that  If there was progress on removing
>> the binaries from the source repo we could include that too. Both of those
>> are work required towards the first apache release.
>>
>> For community development you can discuss the meetup hosted at Twitter
>> last
>> week.
>>
>>
>>
>> On Tue, May 1, 2018 at 1:02 PM, Josh Fischer  wrote:
>>
>> > Hello All,
>> >
>> > Please review the status report for May for review.  It is to be added
>> to
>> > https://wiki.apache.org/incubator/May2018 by tomorrow.  Please review
>> and
>> > comment.
>> >
>> > -
>> >
>> > Heron
>> >
>> > A real-time, distributed, fault-tolerant stream processing engine.
>> >
>> > Heron has been incubating since 2017-06-23.
>> >
>> > Three most important issues to address in the move towards graduation:
>> >
>> >   1. Finish bootstrapping project, IP clearance, initial website
>> >   2. Expanding the community and adding new committers
>> >   3. 1st ASF release
>> >
>> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> > aware of?
>> >
>> > Extracting all binaries out of code base is still in progress.
>> > Work is in progress to complete this task.
>> >
>> > How has the community developed since the last report?
>> >
>> >   * The number of contributors to the project has increased from 82 to
>> 87
>> > since the last report.
>> >
>> > How has the project developed since the last report?
>> >
>> >   * Development has been very active
>> >
>> > How would you assess the podling's maturity?
>> > Please feel free to add your own commentary.
>> >
>> >   [ ] Initial setup
>> >   [x] Working towards first release
>> >   [ ] Community building
>> >   [ ] Nearing graduation
>> >   [ ] Other:
>> >
>> > Date of last release:
>> >
>> >   No Apache releases as of yet. The first Apache release will happen
>> soon
>> > once all binaries are removed from the codebase.
>> >
>> > When were the last committers or PPMC members elected?
>> >
>> >   N/A, still bootstrapping the project.
>> >
>> > Signed-off-by:
>> >
>> >   [ ](heron) Jake Farrell
>> >  Comments:
>> >   [ ](heron) Jacques Nadeau
>> >  Comments:
>> >   [ ](heron) Julien Le Dem
>> >  Comments:
>> >   [](heron) P. Taylor Goetz
>> >  Comments:
>> >
>> >
>> >
>> > On Tue, May 1, 2018 at 7:03 AM, Josh Fischer 

[GitHub] tomncooper commented on issue #2877: Compilation error in a container

[GitBox]

tomncooper commented on issue #2877: Compilation error in a container
URL: 
https://github.com/apache/incubator-heron/issues/2877#issuecomment-385782955
 
 
   I would recommend using the dockerfiles in the `docker/compile` directory 
they are used routinely for compilation so should work. Can you give the 
instructions in the `docker/Readme.md` a try?


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

[GitHub] tomncooper commented on issue #2877: Compilation error in a container

[GitBox]

tomncooper commented on issue #2877: Compilation error in a container
URL: 
https://github.com/apache/incubator-heron/issues/2877#issuecomment-385782955
 
 
   I would recommend using the dockerfiles in the docker/compile directory they 
are used routinely for compilation so should work. Can you give the 
instructions in the docker/compose/ReadMe.md a try?


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

Re: Podling Report Reminder - May 2018

[Josh Fischer]

Will add tonight.  Thank you for the guidance.


On Tue, May 1, 2018 at 3:33 PM Bill Graham  wrote:

> Thanks again Josh for taking on the updates. In terms of project
> development, it would be good to include specifics, like:
>
> 1. Twitter submitted a signed SGA granting the code to Apache.
> 2. The repository moved from Twitter's github to Apache git
>
> You could also give an update on the package naming change to org.apache if
> there is any progress to report on that  If there was progress on removing
> the binaries from the source repo we could include that too. Both of those
> are work required towards the first apache release.
>
> For community development you can discuss the meetup hosted at Twitter last
> week.
>
>
>
> On Tue, May 1, 2018 at 1:02 PM, Josh Fischer  wrote:
>
> > Hello All,
> >
> > Please review the status report for May for review.  It is to be added to
> > https://wiki.apache.org/incubator/May2018 by tomorrow.  Please review
> and
> > comment.
> >
> > -
> >
> > Heron
> >
> > A real-time, distributed, fault-tolerant stream processing engine.
> >
> > Heron has been incubating since 2017-06-23.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Finish bootstrapping project, IP clearance, initial website
> >   2. Expanding the community and adding new committers
> >   3. 1st ASF release
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> > Extracting all binaries out of code base is still in progress.
> > Work is in progress to complete this task.
> >
> > How has the community developed since the last report?
> >
> >   * The number of contributors to the project has increased from 82 to 87
> > since the last report.
> >
> > How has the project developed since the last report?
> >
> >   * Development has been very active
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [x] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   No Apache releases as of yet. The first Apache release will happen soon
> > once all binaries are removed from the codebase.
> >
> > When were the last committers or PPMC members elected?
> >
> >   N/A, still bootstrapping the project.
> >
> > Signed-off-by:
> >
> >   [ ](heron) Jake Farrell
> >  Comments:
> >   [ ](heron) Jacques Nadeau
> >  Comments:
> >   [ ](heron) Julien Le Dem
> >  Comments:
> >   [](heron) P. Taylor Goetz
> >  Comments:
> >
> >
> >
> > On Tue, May 1, 2018 at 7:03 AM, Josh Fischer 
> wrote:
> >
> > > Thanks Karthik.  I should have it done as a first pass tonight.
> > >
> > > On Mon, Apr 30, 2018 at 9:13 PM Karthik Ramasamy 
> > > wrote:
> > >
> > >> Thanks Josh for helping out. Have been swamped with work - let me know
> > if
> > >> you need anything as well.
> > >>
> > >> On Mon, Apr 30, 2018 at 5:45 PM, Josh Fischer 
> > >> wrote:
> > >>
> > >> > Ok, I will check out the past reports first.  Thanks Bill.
> > >> >
> > >> > On Mon, Apr 30, 2018 at 7:40 PM Bill Graham 
> > >> wrote:
> > >> >
> > >> > > Awesome, thanks Josh. You can reach out to me directly if you have
> > any
> > >> > > questions. A search for previous reports might also help.
> > >> > >
> > >> > > On Mon, Apr 30, 2018 at 5:37 PM Josh Fischer  >
> > >> > wrote:
> > >> > >
> > >> > >>  I’ll give it a try .
> > >> > >>
> > >> > >> Josh
> > >> > >>
> > >> > >> On Mon, Apr 30, 2018 at 7:35 PM Bill Graham <
> billgra...@gmail.com>
> > >> > wrote:
> > >> > >>
> > >> > >>> Hi folks,
> > >> > >>>
> > >> > >>> Does anyone else want to take a stab at submitting the report
> this
> > >> time
> > >> > >>> around? I haven’t been as directly involved in recent months so
> it
> > >> > would
> > >> > >>> be
> > >> > >>> good to have someone closer to the action handle the report.
> > >> > >>>
> > >> > >>> Thanks,
> > >> > >>> Bill
> > >> > >>>
> > >> > >>> On Mon, Apr 30, 2018 at 5:27 PM  wrote:
> > >> > >>>
> > >> > >>> > 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 

Re: Podling Report Reminder - May 2018

[Bill Graham]

Thanks again Josh for taking on the updates. In terms of project
development, it would be good to include specifics, like:

1. Twitter submitted a signed SGA granting the code to Apache.
2. The repository moved from Twitter's github to Apache git

You could also give an update on the package naming change to org.apache if
there is any progress to report on that  If there was progress on removing
the binaries from the source repo we could include that too. Both of those
are work required towards the first apache release.

For community development you can discuss the meetup hosted at Twitter last
week.



On Tue, May 1, 2018 at 1:02 PM, Josh Fischer  wrote:

> Hello All,
>
> Please review the status report for May for review.  It is to be added to
> https://wiki.apache.org/incubator/May2018 by tomorrow.  Please review and
> comment.
>
> -
>
> Heron
>
> A real-time, distributed, fault-tolerant stream processing engine.
>
> Heron has been incubating since 2017-06-23.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Finish bootstrapping project, IP clearance, initial website
>   2. Expanding the community and adding new committers
>   3. 1st ASF release
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> Extracting all binaries out of code base is still in progress.
> Work is in progress to complete this task.
>
> How has the community developed since the last report?
>
>   * The number of contributors to the project has increased from 82 to 87
> since the last report.
>
> How has the project developed since the last report?
>
>   * Development has been very active
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [ ] Initial setup
>   [x] Working towards first release
>   [ ] Community building
>   [ ] Nearing graduation
>   [ ] Other:
>
> Date of last release:
>
>   No Apache releases as of yet. The first Apache release will happen soon
> once all binaries are removed from the codebase.
>
> When were the last committers or PPMC members elected?
>
>   N/A, still bootstrapping the project.
>
> Signed-off-by:
>
>   [ ](heron) Jake Farrell
>  Comments:
>   [ ](heron) Jacques Nadeau
>  Comments:
>   [ ](heron) Julien Le Dem
>  Comments:
>   [](heron) P. Taylor Goetz
>  Comments:
>
>
>
> On Tue, May 1, 2018 at 7:03 AM, Josh Fischer  wrote:
>
> > Thanks Karthik.  I should have it done as a first pass tonight.
> >
> > On Mon, Apr 30, 2018 at 9:13 PM Karthik Ramasamy 
> > wrote:
> >
> >> Thanks Josh for helping out. Have been swamped with work - let me know
> if
> >> you need anything as well.
> >>
> >> On Mon, Apr 30, 2018 at 5:45 PM, Josh Fischer 
> >> wrote:
> >>
> >> > Ok, I will check out the past reports first.  Thanks Bill.
> >> >
> >> > On Mon, Apr 30, 2018 at 7:40 PM Bill Graham 
> >> wrote:
> >> >
> >> > > Awesome, thanks Josh. You can reach out to me directly if you have
> any
> >> > > questions. A search for previous reports might also help.
> >> > >
> >> > > On Mon, Apr 30, 2018 at 5:37 PM Josh Fischer 
> >> > wrote:
> >> > >
> >> > >>  I’ll give it a try .
> >> > >>
> >> > >> Josh
> >> > >>
> >> > >> On Mon, Apr 30, 2018 at 7:35 PM Bill Graham 
> >> > wrote:
> >> > >>
> >> > >>> Hi folks,
> >> > >>>
> >> > >>> Does anyone else want to take a stab at submitting the report this
> >> time
> >> > >>> around? I haven’t been as directly involved in recent months so it
> >> > would
> >> > >>> be
> >> > >>> good to have someone closer to the action handle the report.
> >> > >>>
> >> > >>> Thanks,
> >> > >>> Bill
> >> > >>>
> >> > >>> On Mon, Apr 30, 2018 at 5:27 PM  wrote:
> >> > >>>
> >> > >>> > 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
> >> 

[GitHub] tomncooper commented on issue #2877: Compilation error in a container

[GitBox]

tomncooper commented on issue #2877: Compilation error in a container
URL: 
https://github.com/apache/incubator-heron/issues/2877#issuecomment-385780178
 
 
   Can you clarify if you are using the Docker containers defined in the Heron 
repo (docker/compile) or you are constructing your own?


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

[GitHub] comes5 commented on issue #2877: Compilation error in a container

[GitBox]

comes5 commented on issue #2877: Compilation error in a container
URL: 
https://github.com/apache/incubator-heron/issues/2877#issuecomment-385774462
 
 
   The error I am mentioning is in the log file I posted:
   
   `ERROR: /incubator-heron/heron/tools/admin/src/python/BUILD:22:1: PexPython 
heron/tools/admin/src/python/heron-admin.pex failed (Exit 1)
    Failed to install netifaces-0.10.6 (caused by: NonZeroExit("received 
exit code 1 during execution of `['/usr/bin/python2.7', '-', 'bdist_wheel', 
'--dist-dir=/tmp/tmpwn7Syj']` while trying to execute `['/usr/bin/python2.7', 
'-', 'bdist_wheel', '--dist-dir=/tmp/tmpwn7Syj']`",)
   ):`
   
   The problem is that I want to use Dhalion to implement new policies for 
Heron so I need to modify the source code and doing some tests with it.


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

Re: Podling Report Reminder - May 2018

[Josh Fischer]

Hello All,

Please review the status report for May for review.  It is to be added to
https://wiki.apache.org/incubator/May2018 by tomorrow.  Please review and
comment.

-

Heron

A real-time, distributed, fault-tolerant stream processing engine.

Heron has been incubating since 2017-06-23.

Three most important issues to address in the move towards graduation:

  1. Finish bootstrapping project, IP clearance, initial website
  2. Expanding the community and adding new committers
  3. 1st ASF release

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

Extracting all binaries out of code base is still in progress.
Work is in progress to complete this task.

How has the community developed since the last report?

  * The number of contributors to the project has increased from 82 to 87
since the last report.

How has the project developed since the last report?

  * Development has been very active

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [x] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  No Apache releases as of yet. The first Apache release will happen soon
once all binaries are removed from the codebase.

When were the last committers or PPMC members elected?

  N/A, still bootstrapping the project.

Signed-off-by:

  [ ](heron) Jake Farrell
 Comments:
  [ ](heron) Jacques Nadeau
 Comments:
  [ ](heron) Julien Le Dem
 Comments:
  [](heron) P. Taylor Goetz
 Comments:



On Tue, May 1, 2018 at 7:03 AM, Josh Fischer  wrote:

> Thanks Karthik.  I should have it done as a first pass tonight.
>
> On Mon, Apr 30, 2018 at 9:13 PM Karthik Ramasamy 
> wrote:
>
>> Thanks Josh for helping out. Have been swamped with work - let me know if
>> you need anything as well.
>>
>> On Mon, Apr 30, 2018 at 5:45 PM, Josh Fischer 
>> wrote:
>>
>> > Ok, I will check out the past reports first.  Thanks Bill.
>> >
>> > On Mon, Apr 30, 2018 at 7:40 PM Bill Graham 
>> wrote:
>> >
>> > > Awesome, thanks Josh. You can reach out to me directly if you have any
>> > > questions. A search for previous reports might also help.
>> > >
>> > > On Mon, Apr 30, 2018 at 5:37 PM Josh Fischer 
>> > wrote:
>> > >
>> > >>  I’ll give it a try .
>> > >>
>> > >> Josh
>> > >>
>> > >> On Mon, Apr 30, 2018 at 7:35 PM Bill Graham 
>> > wrote:
>> > >>
>> > >>> Hi folks,
>> > >>>
>> > >>> Does anyone else want to take a stab at submitting the report this
>> time
>> > >>> around? I haven’t been as directly involved in recent months so it
>> > would
>> > >>> be
>> > >>> good to have someone closer to the action handle the report.
>> > >>>
>> > >>> Thanks,
>> > >>> Bill
>> > >>>
>> > >>> On Mon, Apr 30, 2018 at 5:27 PM  wrote:
>> > >>>
>> > >>> > 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 

[GitHub] kramasamy commented on issue #2877: Compilation error in a container

[GitBox]

kramasamy commented on issue #2877: Compilation error in a container
URL: 
https://github.com/apache/incubator-heron/issues/2877#issuecomment-385708454
 
 
   Alternatively you could use the docker image at
   ```
   streamlio/build-ubuntu14.0:latest 
   ```
   it has everything installed already.
   
   


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

[GitHub] kramasamy commented on issue #2877: Compilation error in a container

[GitBox]

kramasamy commented on issue #2877: Compilation error in a container
URL: 
https://github.com/apache/incubator-heron/issues/2877#issuecomment-385708454
 
 
   Alternatively you could use the docker - streamlio/build-ubuntu14.0:latest - 
it has everything installed already.
   
   


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

[GitHub] kramasamy commented on issue #2877: Compilation error in a container

[GitBox]

kramasamy commented on issue #2877: Compilation error in a container
URL: 
https://github.com/apache/incubator-heron/issues/2877#issuecomment-385707765
 
 
   @comes5 - can you include what error you are getting?


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

[GitHub] comes5 opened a new issue #2877: Compilation error in a container

[GitBox]

comes5 opened a new issue #2877: Compilation error in a container
URL: https://github.com/apache/incubator-heron/issues/2877
 
 
   I am trying to build incubator-heron master in a container with Ubuntu, I 
managed to install everything but bazel when building the heron folder gives me 
an error, probably related to Python.
   Can someone help me? I have attached all the output from the build comand, 
specifically `bazel build --config=ubuntu heron/...`
   
   
[output.log](https://github.com/apache/incubator-heron/files/1963750/output.log)
   


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

Re: Podling Report Reminder - May 2018

[Josh Fischer]

Thanks Karthik.  I should have it done as a first pass tonight.

On Mon, Apr 30, 2018 at 9:13 PM Karthik Ramasamy  wrote:

> Thanks Josh for helping out. Have been swamped with work - let me know if
> you need anything as well.
>
> On Mon, Apr 30, 2018 at 5:45 PM, Josh Fischer  wrote:
>
> > Ok, I will check out the past reports first.  Thanks Bill.
> >
> > On Mon, Apr 30, 2018 at 7:40 PM Bill Graham 
> wrote:
> >
> > > Awesome, thanks Josh. You can reach out to me directly if you have any
> > > questions. A search for previous reports might also help.
> > >
> > > On Mon, Apr 30, 2018 at 5:37 PM Josh Fischer 
> > wrote:
> > >
> > >>  I’ll give it a try .
> > >>
> > >> Josh
> > >>
> > >> On Mon, Apr 30, 2018 at 7:35 PM Bill Graham 
> > wrote:
> > >>
> > >>> Hi folks,
> > >>>
> > >>> Does anyone else want to take a stab at submitting the report this
> time
> > >>> around? I haven’t been as directly involved in recent months so it
> > would
> > >>> be
> > >>> good to have someone closer to the action handle the report.
> > >>>
> > >>> Thanks,
> > >>> Bill
> > >>>
> > >>> On Mon, Apr 30, 2018 at 5:27 PM  wrote:
> > >>>
> > >>> > 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
> > >>> >
> > >>> --
> > >>> Sent from Gmail Mobile
> > >>>
> > >> --
> > >> Sent from A Mobile Device
> > >>
> > > --
> > > Sent from Gmail Mobile
> > >
> > --
> > Sent from A Mobile Device
> >
>
-- 
Sent from A Mobile Device