Re: [VOTE] Graduate Apache Eagle to top level project

[Henry Saputra]

Hi Edward,

Could you tally up the VOTE result in dev@ list?

- Henry

On Mon, Dec 5, 2016 at 9:30 PM, Edward Zhang  wrote:
> Thanks. I have noticed this error and corrected that in formal vote in
> general DL.
>
> Thanks
> Edward
>
> On Mon, Dec 5, 2016 at 9:25 PM, Amareshwari Sriramdasu <
> amareshw...@apache.org> wrote:
>
>> +1
>>
>> Please correct Jijun Tang's link in final vote.
>>
>> On Thu, Dec 1, 2016 at 11:16 AM, Edward Zhang 
>> wrote:
>>
>> > Hi Eagle community,
>> >
>> > After a very positive discussion in Apache Eagle community http://apache
>> .
>> > markmail.org/thread/s2yegpmxf3g7fa34, I'd like to bring the following
>> > resolution for a formal vote in Eagle community and after this we need
>> > another formal vote in IPMC and then we reach a stage close to graduation
>> > :-)
>> >
>> > Please vote on the resolution pasted below to graduate Apache Eagle from
>> > the incubator to top level project.
>> >
>> >
>> > [ ] +1 Graduate Apache Eagle from the Incubator.
>> >
>> > [ ] +0 Don't care.
>> >
>> > [ ] -1 Don't graduate Apache Eagle from the Incubator because...
>> >
>> >
>> > This vote will be open for at least 72 hours.
>> >
>> >
>> > Many thanks to our mentors and everyone else for the support,
>> >
>> > Edward Zhang (on behalf of the Apache Eagle PPMC).
>> >
>> > Resolution:
>> >
>> >   Establish the Apache Eagle Project
>> >
>> >   WHEREAS, the Board of Directors deems it to be in the best
>> >   interests of the Foundation and consistent with the
>> >   Foundation's purpose to establish a Project Management
>> >   Committee charged with the creation and maintenance of
>> >   open-source software, for distribution at no charge to
>> >   the public, related to a distributed monitoring solution for
>> > identifying security and performance issues in real time on big data
>> > platforms, including Hadoop and Spark etc.
>> >
>> >   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> >   Committee (PMC), to be known as the "Apache Eagle Project",
>> >   be and hereby is established pursuant to Bylaws of the
>> >   Foundation; and be it further
>> >
>> >   RESOLVED, that the Apache Eagle Project be and hereby is
>> >   responsible for the creation and maintenance of software
>> >   related to a distributed monitoring solution for identifying
>> security
>> > and performance issues in real time on big data platforms, including
>> Hadoop
>> > and Spark etc.;
>> >   and be it further
>> >
>> >   RESOLVED, that the office of "Vice President, Apache Eagle" be
>> >   and hereby is created, the person holding such office to
>> >   serve at the direction of the Board of Directors as the chair
>> >   of the Apache Eagle Project, and to have primary responsibility
>> >   for management of the projects within the scope of
>> >   responsibility of the Apache Eagle Project; and be it further
>> >
>> >   RESOLVED, that the persons listed immediately below be and
>> >   hereby are appointed to serve as the initial members of the
>> >   Apache Eagle Project:
>> >
>> >
>> > * Edward Zhang yonzhang2...@apache.org
>> >
>> > * Hao Chen h...@apache.org
>> >
>> > * Qingwen Zhao qingwz...@apache.org
>> >
>> > * jilin Jiang ji...@apache.org
>> >
>> > * Ralph Su ralp...@apache.org
>> >
>> > * Jinhu Wu jinh...@apache.org
>> >
>> > * Jijun Tang jjt...@apache.org 
>> >
>> > * Daniel Zhou daz...@apache.org
>> >
>> > * Kumar Senthil senthilec...@apache.org
>> >
>> > * Dendukuri Hemanth hdenduk...@apache.org
>> >
>> > * Wu Michael m...@apache.org
>> >
>> > * Manoharan Arun arunmanoha...@apache.org
>> >
>> > * Gupta Chaitali cgu...@apache.org
>> >
>> > * Libin Sun lib...@apache.org
>> >
>> >
>> >
>> >   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Edward Zhang
>> >   be appointed to the office of Vice President, Apache Eagle, to
>> >   serve in accordance with and subject to the direction of the
>> >   Board of Directors and the Bylaws of the Foundation until
>> >   death, resignation, retirement, removal or disqualification,
>> >   or until a successor is appointed; and be it further
>> >
>> >   RESOLVED, that the initial Apache Eagle PMC be and hereby is
>> >   tasked with the creation of a set of bylaws intended to
>> >   encourage open development and increased participation in the
>> >   Apache Eagle Project; and be it further
>> >
>> >   RESOLVED, that the Apache Eagle Project be and hereby
>> >   is tasked with the migration and rationalization of the Apache
>> >   Incubator Eagle podling; and be it further
>> >
>> >   RESOLVED, that all responsibilities pertaining to the Apache
>> >   Incubator Eagle podling encumbered upon the Apache Incubator
>> >   Project are hereafter discharged.
>> >
>>

Re: [VOTE] Graduate Apache Eagle to top level project

[Henry Saputra]

+1

When we move the board resolution to general@ list please change "
Hadoop and Spark" to "Apache Hadoop and Apache Spark"

- Henry

On Wed, Nov 30, 2016 at 9:46 PM, Edward Zhang  wrote:
> Hi Eagle community,
>
> After a very positive discussion in Apache Eagle community http://apache.
> markmail.org/thread/s2yegpmxf3g7fa34, I'd like to bring the following
> resolution for a formal vote in Eagle community and after this we need
> another formal vote in IPMC and then we reach a stage close to graduation
> :-)
>
> Please vote on the resolution pasted below to graduate Apache Eagle from
> the incubator to top level project.
>
>
> [ ] +1 Graduate Apache Eagle from the Incubator.
>
> [ ] +0 Don't care.
>
> [ ] -1 Don't graduate Apache Eagle from the Incubator because...
>
>
> This vote will be open for at least 72 hours.
>
>
> Many thanks to our mentors and everyone else for the support,
>
> Edward Zhang (on behalf of the Apache Eagle PPMC).
>
> Resolution:
>
>   Establish the Apache Eagle Project
>
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to
>   the public, related to a distributed monitoring solution for
> identifying security and performance issues in real time on big data
> platforms, including Hadoop and Spark etc.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Eagle Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Eagle Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to a distributed monitoring solution for identifying security
> and performance issues in real time on big data platforms, including Hadoop
> and Spark etc.;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Eagle" be
>   and hereby is created, the person holding such office to
>   serve at the direction of the Board of Directors as the chair
>   of the Apache Eagle Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Eagle Project; and be it further
>
>   RESOLVED, that the persons listed immediately below be and
>   hereby are appointed to serve as the initial members of the
>   Apache Eagle Project:
>
>
> * Edward Zhang yonzhang2...@apache.org
>
> * Hao Chen h...@apache.org
>
> * Qingwen Zhao qingwz...@apache.org
>
> * jilin Jiang ji...@apache.org
>
> * Ralph Su ralp...@apache.org
>
> * Jinhu Wu jinh...@apache.org
>
> * Jijun Tang jjt...@apache.org 
>
> * Daniel Zhou daz...@apache.org
>
> * Kumar Senthil senthilec...@apache.org
>
> * Dendukuri Hemanth hdenduk...@apache.org
>
> * Wu Michael m...@apache.org
>
> * Manoharan Arun arunmanoha...@apache.org
>
> * Gupta Chaitali cgu...@apache.org
>
> * Libin Sun lib...@apache.org
>
>
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Edward Zhang
>   be appointed to the office of Vice President, Apache Eagle, to
>   serve in accordance with and subject to the direction of the
>   Board of Directors and the Bylaws of the Foundation until
>   death, resignation, retirement, removal or disqualification,
>   or until a successor is appointed; and be it further
>
>   RESOLVED, that the initial Apache Eagle PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Eagle Project; and be it further
>
>   RESOLVED, that the Apache Eagle Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Eagle podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Eagle podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.

Re: Eagle graduation steps

[Henry Saputra]

Thanks for driving the graduation discussion, Edward,

One thing that we need for graduation is VP or Chair for Eagle as Top Level
project.

I am nominating Edward Zhang as VP for Apache Eagle since he has been very
active to drive Apache Eagle community,

- Henry

On Mon, Nov 7, 2016 at 9:27 PM, Edward Zhang 
wrote:

> Hi Mentors,
>
> Can you please reply this email if you have remaining issues regarding
> Eagle graduation before we call official vote?
>
> According to Apache project graduation guideline, we need make sure mentors
> and IPMC have no remaining issues.
>
>
>- Ensure Mentors
> Responsibilities.html#Mentor>
> and IPMC
> Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29>
> have
>no remaining issues
>
>
>
>
> Thanks
> Edward
>
> On Sun, Nov 6, 2016 at 11:01 AM, Edward Zhang 
> wrote:
>
> > Hi Henry and Eagle Mentors,
> >
> > Seems we have gone through most of check list for graduation, can I start
> > formal community vote on graduation according to http://incubator.apache
> .
> > org/guides/graduation.html#process?
> >
> >
> >
> >- a charter for your project(Draft resolution was
> done)
> >- a positive community graduation VOTE
> >
> >- a positive IPMC recommendation VOTE
> >
> >- the acceptance of the resolution
> >
> by
> >the Board
> >
> > Also, do you have any remaining issues about graduation before we do
> vote?
> >
> >
> >- Ensure Mentors
> > Responsibilities.html#Mentor>
> > and IPMC
> > Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29>
> have
> >no remaining issues
> >
> >
> >
> >
> > Thanks
> > Edward
> >
> > On Sun, Oct 30, 2016 at 8:59 PM, Edward Zhang 
> > wrote:
> >
> >> Hi Eagle community,
> >>
> >> As one step towards graduation, the following is proposed project
> >> destination and resolution and please provide your feedback.
> >>
> >> For destination, according to the guide line
> >> http://incubator.apache.org/guides/graduation.html#subprojec
> >> t-or-top-level, because Apache Eagle is sponsored by IPMC, we should put
> >> it to be top-level project instead of subproject.
> >>
> >> For revision, here is the template, template https://svn.apache.or
> >> g/repos/private/committers/board/templates/podling-tlp-resolution.txt.
> I
> >> put initial committers there and we need a chair for this project.
> >>
> >> Destination: Top-level project
> >>
> >> Revision:
> >>
> >>   Establish the Apache Eagle Project
> >>
> >>   WHEREAS, the Board of Directors deems it to be in the best
> >>   interests of the Foundation and consistent with the
> >>   Foundation's purpose to establish a Project Management
> >>   Committee charged with the creation and maintenance of
> >>   open-source software, for distribution at no charge to
> >>   the public, related to a distributed monitoring solution for
> >> identifying security and performance issues in real time on big data
> >> platforms, including Hadoop and Spark etc.
> >>
> >>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >>   Committee (PMC), to be known as the "Apache Eagle Project",
> >>   be and hereby is established pursuant to Bylaws of the
> >>   Foundation; and be it further
> >>
> >>   RESOLVED, that the Apache Eagle Project be and hereby is
> >>   responsible for the creation and maintenance of software
> >>   related to a distributed monitoring solution for identifying
> >> security and performance issues in real time on big data platforms,
> >> including Hadoop and Spark etc.;
> >>   and be it further
> >>
> >>   RESOLVED, that the office of "Vice President, Apache Eagle" be
> >>   and hereby is created, the person holding such office to
> >>   serve at the direction of the Board of Directors as the chair
> >>   of the Apache Eagle Project, and to have primary responsibility
> >>   for management of the projects within the scope of
> >>   responsibility of the Apache Eagle Project; and be it further
> >>
> >>   RESOLVED, that the persons listed immediately below be and
> >>   hereby are appointed to serve as the initial members of the
> >>   Apache Eagle Project:
> >>
> >>
> >> * yonzhang2...@apache.org
> >>
> >> * h...@apache.org
> >>
> >> * qingwz...@apache.org
> >>
> >> * ji...@apache.org
> >>
> >> * ralp...@apache.org
> >>
> >> * jinh...@apache.

[jira] [Commented] (EAGLE-541) Application policy template framework

[Henry Saputra (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497050#comment-15497050
 ] 

Henry Saputra commented on EAGLE-541:
-

Could you add more information on the Description of what this JIRA for? Thx

> Application policy template framework
> -
>
> Key: EAGLE-541
> URL: https://issues.apache.org/jira/browse/EAGLE-541
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [ANNOUNCE] New Apache Eagle Committer: Jinhu Wu

[Henry Saputra]

Welcome !

On Tuesday, September 6, 2016, Hao Chen  wrote:

> Congrats and welcome Jinhu!
>
> - Hao
>
> On Wed, Sep 7, 2016 at 1:45 PM, Liangfei.Su  > wrote:
>
> > Congrats Jinhu!
> >
> > On Wed, Sep 7, 2016 at 1:33 PM, Jayesh Senjaliya  >
> > wrote:
> >
> > > Congratulations Jinhu !
> > >
> > > On Tue, Sep 6, 2016 at 10:14 PM, Jinhu Wu  >
> > wrote:
> > >
> > > > Thanks, I'm very glad to become a Apache Eagle committer and PPMC
> > member
> > > > and will make more contributions to Eagle and Apache open source
> > > > community.😁
> > > >
> > > > On Wed, Sep 7, 2016 at 11:13 AM, Michael Wu  > wrote:
> > > >
> > > > > Eagle Community,
> > > > >
> > > > > The Project Management Committee (PMC) for Apache Eagle has asked
> > Jinhu
> > > > Wu
> > > > > to become a committer and PPMC member, we are now pleased to
> announce
> > > > that
> > > > > he has accepted.
> > > > >
> > > > > Jinhu has demonstrated a strong commitment to the Apache Eagle
> > > community
> > > > > by carrying out several
> > > > > monitoring features for Map-Reduce Job, Spark Job, Hive Security,
> > etc.
> > > He
> > > > > also participated widely in design discussion, and bug fixing
> > > endeavors.
> > > > >
> > > > > Not only his insight and solid technical skills have brought the
> > > project
> > > > > extra productivity, his enthusiasm in programming and continuous
> > > > > contribution also benefits the community and is believed to guide
> > Eagle
> > > > > project to the next level.
> > > > >
> > > > > @ Jinhu,
> > > > >
> > > > > Welcome to join us! Would you like to make a brief
> self-introduction
> > to
> > > > > the community?
> > > > >
> > > > > Yours,
> > > > > Michael on behalf of Apache Eagle PPMC
> > > > >
> > > >
> > >
> >
>

Re: [HELP] cannot upload eagle jars to maven repository

[Henry Saputra]

Ah looks like it is  there:

https://repository.apache.org/#stagingRepositories

You need to Close the staging repo and then release them.

- Henry

On Fri, Aug 19, 2016 at 11:12 PM, Henry Saputra 
wrote:

> Hi Michael.
>
> I dont see Eagle artifacts in the staging repo https://repository.
> apache.org/content/repositories/staging/org/apache/
>
> And also, could you please document  the steps you did to help the next RE
> do the next Eagel release [1]
>
> - Henry
>
> [1] https://cwiki.apache.org/confluence/display/EAG/How+to+Release
>
> On Wed, Aug 17, 2016 at 9:50 AM, Michael Wu  wrote:
>
>> Henry,
>>
>> I've got the access to upload artifacts to
>> https://repository.apache.org/service/local/staging/deploy/maven2/, and
>> based on the result of latest execution, all .jar, .asc, etc. of eagle
>> 0.4.0-incubating are uploaded to the url successfully. However, I still
>> cannot find them via web-browser from
>> https://repository.apache.org/content/repositories/releases/org/apache/.
>> I
>> went through all documents I had read about the uploading process, but
>> didn't find any instruction for how to verify the visibility of the
>> uploaded jars. Do you have any idea with it, please?
>>
>> BTW, is there any additional operation/request I have to make, or is there
>> any sync process that I have to wait for? Thanks.
>>
>> Michael
>>
>> On Thu, Aug 11, 2016 at 11:21 AM, Michael Wu  wrote:
>>
>> > Tickets created:
>> > https://issues.apache.org/jira/browse/INFRA-12409
>> > https://issues.apache.org/jira/browse/INFRA-12410
>> >
>> > On Thu, Aug 11, 2016 at 10:07 AM, Michael Wu 
>> wrote:
>> >
>> >> Henry,
>> >>
>> >> Thank you very much for guiding me with those details! I'll do it right
>> >> now.
>> >>
>> >> Michael
>> >>
>> >> On Tue, Aug 9, 2016 at 2:39 AM, Henry Saputra > >
>> >> wrote:
>> >>
>> >>> So, we need to file 2 infra tickets:
>> >>> 1. One is to add target in Maven repository for Eagle. You can see
>> sample
>> >>> from here: https://issues.apache.org/jira/browse/INFRA-8026 or
>> >>> https://issues.apache.org/jira/browse/INFRA-7246
>> >>> 2. Create ticket for you to be granted karma to access Apache Nexus
>> repo.
>> >>>
>> >>> -  Henry
>> >>>
>> >>> On Mon, Aug 8, 2016 at 12:56 AM, Michael Wu 
>> wrote:
>> >>>
>> >>> > Hi Henry,
>> >>> >
>> >>> > No, eagle never pushed artifacts to ASF Nexus repository. How can we
>> >>> get
>> >>> > the access, please?
>> >>> >
>> >>> > Michael
>> >>> >
>> >>> > On Mon, Aug 8, 2016 at 2:21 PM, Henry Saputra <
>> henry.sapu...@gmail.com
>> >>> >
>> >>> > wrote:
>> >>> >
>> >>> > > I found Eagle in ASF release dist folder but do not see it in the
>> >>> Nexus
>> >>> > > Maven repo (https://repository.apache.org)
>> >>> > >
>> >>> > > Has Eagle pushed artifacts to ASF Nexus repository for prev
>> releases?
>> >>> > >
>> >>> > > - Henry
>> >>> > >
>> >>> > > On Wed, Aug 3, 2016 at 8:04 PM, Michael Wu 
>> >>> wrote:
>> >>> > >
>> >>> > > > Hi mentors,
>> >>> > > >
>> >>> > > > I was trying to use
>> >>> > > >
>> >>> > > > $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_
>> >>> > > PASSPHRASE}
>> >>> > > > deploy
>> >>> > > >
>> >>> > > > to upload eagle's jars to
>> >>> > > > https://repository.apache.org/service/local/staging/deploy/m
>> aven2,
>> >>> but
>> >>> > > it
>> >>> > > > always return 400 error, as below fragment:
>> >>> > > > 
>> >>> > > > [ERROR] Failed to execute goal
>> >>> > > > org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy
>> >>> > > (default-deploy)
>> >>> > > > on project eagle-parent: Failed to deploy artifacts: Could not
>> >>> transfer
>> >>> > > > artifact org.apache.eagle:eagle-parent:pom:0.4.0-incubating
>> >>> from/to
>> >>> > > > apache.releases.https (
>> >>> > > > https://repository.apache.org/service/local/staging/deploy/m
>> aven2
>> >>> ):
>> >>> > > Failed
>> >>> > > > to transfer file:
>> >>> > > > https://repository.apache.org/service/local/staging/deploy/
>> >>> > > > maven2/org/apache/eagle/eagle-parent/0.4.0-incubating/eagle-
>> >>> > > > parent-0.4.0-incubating.pom.
>> >>> > > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>> >>> > > > 
>> >>> > > >
>> >>> > > > Could you instruct me, whether it's caused by the lack of access
>> >>> to the
>> >>> > > > repository and which mailing list I should get connected with to
>> >>> solve
>> >>> > > this
>> >>> > > > issue, please? Thanks.
>> >>> > > >
>> >>> > > > Michael
>> >>> > > >
>> >>> > >
>> >>> >
>> >>>
>> >>
>> >>
>> >
>>
>
>

Re: [HELP] cannot upload eagle jars to maven repository

[Henry Saputra]

Hi Michael.

I dont see Eagle artifacts in the staging repo
https://repository.apache.org/content/repositories/staging/org/apache/

And also, could you please document  the steps you did to help the next RE
do the next Eagel release [1]

- Henry

[1] https://cwiki.apache.org/confluence/display/EAG/How+to+Release

On Wed, Aug 17, 2016 at 9:50 AM, Michael Wu  wrote:

> Henry,
>
> I've got the access to upload artifacts to
> https://repository.apache.org/service/local/staging/deploy/maven2/, and
> based on the result of latest execution, all .jar, .asc, etc. of eagle
> 0.4.0-incubating are uploaded to the url successfully. However, I still
> cannot find them via web-browser from
> https://repository.apache.org/content/repositories/releases/org/apache/. I
> went through all documents I had read about the uploading process, but
> didn't find any instruction for how to verify the visibility of the
> uploaded jars. Do you have any idea with it, please?
>
> BTW, is there any additional operation/request I have to make, or is there
> any sync process that I have to wait for? Thanks.
>
> Michael
>
> On Thu, Aug 11, 2016 at 11:21 AM, Michael Wu  wrote:
>
> > Tickets created:
> > https://issues.apache.org/jira/browse/INFRA-12409
> > https://issues.apache.org/jira/browse/INFRA-12410
> >
> > On Thu, Aug 11, 2016 at 10:07 AM, Michael Wu  wrote:
> >
> >> Henry,
> >>
> >> Thank you very much for guiding me with those details! I'll do it right
> >> now.
> >>
> >> Michael
> >>
> >> On Tue, Aug 9, 2016 at 2:39 AM, Henry Saputra 
> >> wrote:
> >>
> >>> So, we need to file 2 infra tickets:
> >>> 1. One is to add target in Maven repository for Eagle. You can see
> sample
> >>> from here: https://issues.apache.org/jira/browse/INFRA-8026 or
> >>> https://issues.apache.org/jira/browse/INFRA-7246
> >>> 2. Create ticket for you to be granted karma to access Apache Nexus
> repo.
> >>>
> >>> -  Henry
> >>>
> >>> On Mon, Aug 8, 2016 at 12:56 AM, Michael Wu 
> wrote:
> >>>
> >>> > Hi Henry,
> >>> >
> >>> > No, eagle never pushed artifacts to ASF Nexus repository. How can we
> >>> get
> >>> > the access, please?
> >>> >
> >>> > Michael
> >>> >
> >>> > On Mon, Aug 8, 2016 at 2:21 PM, Henry Saputra <
> henry.sapu...@gmail.com
> >>> >
> >>> > wrote:
> >>> >
> >>> > > I found Eagle in ASF release dist folder but do not see it in the
> >>> Nexus
> >>> > > Maven repo (https://repository.apache.org)
> >>> > >
> >>> > > Has Eagle pushed artifacts to ASF Nexus repository for prev
> releases?
> >>> > >
> >>> > > - Henry
> >>> > >
> >>> > > On Wed, Aug 3, 2016 at 8:04 PM, Michael Wu 
> >>> wrote:
> >>> > >
> >>> > > > Hi mentors,
> >>> > > >
> >>> > > > I was trying to use
> >>> > > >
> >>> > > > $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_
> >>> > > PASSPHRASE}
> >>> > > > deploy
> >>> > > >
> >>> > > > to upload eagle's jars to
> >>> > > > https://repository.apache.org/service/local/staging/deploy/
> maven2,
> >>> but
> >>> > > it
> >>> > > > always return 400 error, as below fragment:
> >>> > > > 
> >>> > > > [ERROR] Failed to execute goal
> >>> > > > org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy
> >>> > > (default-deploy)
> >>> > > > on project eagle-parent: Failed to deploy artifacts: Could not
> >>> transfer
> >>> > > > artifact org.apache.eagle:eagle-parent:pom:0.4.0-incubating
> >>> from/to
> >>> > > > apache.releases.https (
> >>> > > > https://repository.apache.org/service/local/staging/deploy/
> maven2
> >>> ):
> >>> > > Failed
> >>> > > > to transfer file:
> >>> > > > https://repository.apache.org/service/local/staging/deploy/
> >>> > > > maven2/org/apache/eagle/eagle-parent/0.4.0-incubating/eagle-
> >>> > > > parent-0.4.0-incubating.pom.
> >>> > > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> >>> > > > 
> >>> > > >
> >>> > > > Could you instruct me, whether it's caused by the lack of access
> >>> to the
> >>> > > > repository and which mailing list I should get connected with to
> >>> solve
> >>> > > this
> >>> > > > issue, please? Thanks.
> >>> > > >
> >>> > > > Michael
> >>> > > >
> >>> > >
> >>> >
> >>>
> >>
> >>
> >
>

Re: [HELP] cannot upload eagle jars to maven repository

[Henry Saputra]

So, we need to file 2 infra tickets:
1. One is to add target in Maven repository for Eagle. You can see sample
from here: https://issues.apache.org/jira/browse/INFRA-8026 or
https://issues.apache.org/jira/browse/INFRA-7246
2. Create ticket for you to be granted karma to access Apache Nexus repo.

-  Henry

On Mon, Aug 8, 2016 at 12:56 AM, Michael Wu  wrote:

> Hi Henry,
>
> No, eagle never pushed artifacts to ASF Nexus repository. How can we get
> the access, please?
>
> Michael
>
> On Mon, Aug 8, 2016 at 2:21 PM, Henry Saputra 
> wrote:
>
> > I found Eagle in ASF release dist folder but do not see it in the Nexus
> > Maven repo (https://repository.apache.org)
> >
> > Has Eagle pushed artifacts to ASF Nexus repository for prev releases?
> >
> > - Henry
> >
> > On Wed, Aug 3, 2016 at 8:04 PM, Michael Wu  wrote:
> >
> > > Hi mentors,
> > >
> > > I was trying to use
> > >
> > > $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_
> > PASSPHRASE}
> > > deploy
> > >
> > > to upload eagle's jars to
> > > https://repository.apache.org/service/local/staging/deploy/maven2, but
> > it
> > > always return 400 error, as below fragment:
> > > 
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy
> > (default-deploy)
> > > on project eagle-parent: Failed to deploy artifacts: Could not transfer
> > > artifact org.apache.eagle:eagle-parent:pom:0.4.0-incubating from/to
> > > apache.releases.https (
> > > https://repository.apache.org/service/local/staging/deploy/maven2):
> > Failed
> > > to transfer file:
> > > https://repository.apache.org/service/local/staging/deploy/
> > > maven2/org/apache/eagle/eagle-parent/0.4.0-incubating/eagle-
> > > parent-0.4.0-incubating.pom.
> > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > > 
> > >
> > > Could you instruct me, whether it's caused by the lack of access to the
> > > repository and which mailing list I should get connected with to solve
> > this
> > > issue, please? Thanks.
> > >
> > > Michael
> > >
> >
>

Re: [HELP] cannot upload eagle jars to maven repository

[Henry Saputra]

I found Eagle in ASF release dist folder but do not see it in the Nexus
Maven repo (https://repository.apache.org)

Has Eagle pushed artifacts to ASF Nexus repository for prev releases?

- Henry

On Wed, Aug 3, 2016 at 8:04 PM, Michael Wu  wrote:

> Hi mentors,
>
> I was trying to use
>
> $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_PASSPHRASE}
> deploy
>
> to upload eagle's jars to
> https://repository.apache.org/service/local/staging/deploy/maven2, but it
> always return 400 error, as below fragment:
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
> on project eagle-parent: Failed to deploy artifacts: Could not transfer
> artifact org.apache.eagle:eagle-parent:pom:0.4.0-incubating from/to
> apache.releases.https (
> https://repository.apache.org/service/local/staging/deploy/maven2): Failed
> to transfer file:
> https://repository.apache.org/service/local/staging/deploy/
> maven2/org/apache/eagle/eagle-parent/0.4.0-incubating/eagle-
> parent-0.4.0-incubating.pom.
> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> 
>
> Could you instruct me, whether it's caused by the lack of access to the
> repository and which mailing list I should get connected with to solve this
> issue, please? Thanks.
>
> Michael
>

Re: [Discuss] How do you think rename "develop" branch to "trunk"branch so that able to close pull request automatically?

[Henry Saputra]

+1 to move it to master.


On Sun, Aug 7, 2016 at 8:09 PM, Julian Hyde  wrote:

> +1 moving to “trunk” or “master”.
>
> Regarding the name. These days more projects use the name “master” rather
> than “trunk”. (At least, that’s my impression. Hive, for instance, used
> “trunk” when it was primarily svn, and switched to “master” now it’s based
> on git.) But frankly either would be fine.
>
> Julian
>
>
>
> > On Aug 7, 2016, at 7:47 PM, Don Bosco Durai  wrote:
> >
> > I also feel that moving development to “trunk” will be a good thing.
> Right now, synchronizing the final release branch to the “trunk” seems to
> be a redundant activity. In the release notes, we can always ask the users
> to use the release branch and also when we create sub releases, they would
> be off the previous release branch, so it would just work naturally.
> >
> > Bosco
> >
> >
> >
> > On 8/7/16, 7:12 PM, "Michael Wu"  wrote:
> >
> >Sounds good to me, as long as it benefits the project.
> >
> >On Fri, Aug 5, 2016 at 3:22 PM, Hao Chen  wrote:
> >
> >> Currently we are faced a problem that we can't close the pull request
> from
> >> contributors automatically.
> >>
> >> When a pull request is merged in develop branch, github could not close
> the
> >> pull request automatically and committers don't have permission to close
> >> the pull request manually on github page, so that we have to ask the
> >> contributor to close the branch manually otherwise there would be lots
> of
> >> "OPEN" pull requests listed though most are merged.
> >>
> >> Learning from github service:
> >>
> >> "
> >> To close this pull request, make a commit to your *master/trunk *branch
> >> with (at least) the following in the commit message:
> >>
> >>This closes #305
> >> "
> >>
> >> Commits with *"Closes #PULL-REQUEST-ID"* will only work on
> master/trunk, in
> >> fact *trunk* branch should be our *develo *in purpose and would be
> better
> >> for management.
> >>
> >> Any comments are appreciated.
> >>
> >> - Hao
> >>
> >
> >
> >
>
>

Re: Eagle build broken in github

[Henry Saputra]

Edward,

Where do you see this error log from?

- Henry

On Mon, Jul 25, 2016 at 5:40 PM, Don Bosco Durai  wrote:

> I had the same issue with OpenJDK 1.8. But it works with Sun JDK 1.8.
>
> Bosco
>
>
> On 7/25/16, 5:37 PM, "Edward Zhang"  wrote:
>
> Seems it is JDK issue?
>
> [INFO] Compiling 16 source files to
>
> /home/jenkins/jenkins-slave/workspace/incubator-eagle-main/eagle-core/eagle-data-process/eagle-stream-process-base/target/classes
> at 1469439473203[ERROR] error: error while loading CharSequence, class
> file
> '/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/jre/lib/rt.jar(java/lang/CharSequence.class)'
> is broken[INFO] (class java.lang.RuntimeException/bad constant pool
> tag 18 at byte 10)[ERROR] error: error while loading AnnotatedElement,
> class file
> '/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/jre/lib/rt.jar(java/lang/reflect/AnnotatedElement.class)'
> is broken[INFO] (class java.lang.RuntimeException/bad constant pool
> tag 18 at byte 76)[ERROR] error: error while loading ConcurrentMap,
> class file
> '/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/jre/lib/rt.jar(java/util/concurrent/ConcurrentMap.class)'
> is broken[INFO] (class java.lang.RuntimeException/bad constant pool
> tag 18 at byte 61)[ERROR] three errors found
>
>
>
>

Re: Web site branding

[Henry Saputra]

; 2. "acknowledge trademarks", do you mean the trademarks of
> "hadoop".
> > >> If I
> > >> >>> understand right, the "tag line" you mentioned has been modified,
> it
> > >> would
> > >> >>> never mention "Hadoop" again.
> > >> >>>
> > >> >>> [Julian] - In the docs, remove "fork me on github" from the top
> > right
> > >> >>> corner. The call to action is to join the Apache community.
> > >> >>> [Michael] - Not quite clear with this tip. I'm wondering, where is
> > the
> > >> >>> appropriate position for us to place the "forking" element on the
> > >> page? As
> > >> >>> least, people may contribute by firstly forking a git repository.
> Do
> > >> you
> > >> >>> think the top-nav tag bar is good to add forking components?
> > >> >>>
> > >> >>>
> > >> >>> Thanks.
> > >> >>> Michael
> > >> >>>
> > >> >>> On Mon, Jul 18, 2016 at 4:02 PM, Julian Hyde  >
> > wrote:
> > >> >>>
> > >> >>>> I added the following comments to the JIRA case:
> > >> >>>>
> > >> >>>> * Also, make the disclaimer more prominent on the front page. It
> is
> > >> >>>> buried at the bottom of a very long page. I think it should
> appear
> > in
> > >> the
> > >> >>>> first screen-full.
> > >> >>>>
> > >> >>>> * Apply these guidelines throughout the site, in particular to
> the
> > >> docs,
> > >> >>>> https://eagle.incubator.apache.org/docs/.
> > >> >>>>
> > >> >>>> * In the docs, qualify all Apache projects with Apache. I think
> you
> > >> can
> > >> >>>> skip "Apache" in the tag line "Secure Hadoop in real time" but
> you
> > >> must
> > >> >>>> acknowledge trademarks.
> > >> >>>>
> > >> >>>> * In the docs, remove "fork me on github" from the top right
> > corner.
> > >> The
> > >> >>>> call to action is to join the Apache community.
> > >> >>>>
> > >> >>>> Julian
> > >> >>>>
> > >> >>>>> On Jul 17, 2016, at 8:32 PM, Michael Wu  >
> > wrote:
> > >> >>>>>
> > >> >>>>> BTW, here is a jira ticket for trying to fix this issue:
> EAGLE-380
> > >> >>>>> <https://issues.apache.org/jira/browse/EAGLE-380>. It'll be
> > thankful
> > >> >>>> to see
> > >> >>>>> your comments on it. :)
> > >> >>>>>
> > >> >>>>> On Mon, Jul 18, 2016 at 11:29 AM, Michael Wu <
> mchl@gmail.com >
> > >> >>>> wrote:
> > >> >>>>>
> > >> >>>>>> Hi guys,
> > >> >>>>>>
> > >> >>>>>> To my understanding on your suggestions, we could modify our
> > docs in
> > >> >>>> the
> > >> >>>>>> following ways, please help review if they are satisfying the
> > >> request:
> > >> >>>>>> 1. if "eagle" is in doc page title, change it to "Apache Eagle
> > >> >>>>>> (incubating)".
> > >> >>>>>> 2. if there are many "eagle"s appear in the doc page content,
> > change
> > >> >>>> the
> > >> >>>>>> first mention of it to "Apache Eagle (incubating, called Eagle
> in
> > >> the
> > >> >>>>>> following)".
> > >> >>>>>> 3. change logo size or position.
> > >> >>>>>>
> > >> >>>>>> Anything missed, please DO correct me. Thanks.
> > >> >>>>>> Michael
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>>> On Thu, Jun 30, 2016 at 11:05 PM, Henry Saputra <
> > >> >>>> henry.sapu...@

Re: [HELP] could anyone help grant svn write access of directory https://svn.apache.org/repos/asf/incubator/eagle/ to Michael's apache account ?

[Henry Saputra]

Awesome

On Sunday, July 31, 2016, Michael Wu  wrote:

> Henry, it works now for me, thank you very much!
>
> On Sat, Jul 30, 2016 at 12:25 AM, Henry Saputra  >
> wrote:
>
> > Seemed like the change has been merged. Could you give it a spin?
> >
> > - Henry
> >
> > On Thu, Jul 28, 2016 at 10:49 PM, Michael Wu  
> > ');>>
> wrote:
> >
> > > Thank you very much, Henry! Could you please let me know once it's
> done?
> > >
> > > On Fri, Jul 29, 2016 at 1:44 PM, Henry Saputra <
> henry.sapu...@gmail.com 
> > > 
> ');>>
> > > wrote:
> > >
> > > > OK, seemed like your name is not in commit auth for the svn. I will
> > send
> > > PR
> > > > to update it.
> > > >
> > > > - Henry
> > > >
> > > > On Wed, Jul 27, 2016 at 11:50 PM, Michael Wu  
> > > ');>>
> wrote:
> > > >
> > > > > Henry, my apache username is "mw". Thanks.
> > > > >
> > > > > On Thu, Jul 28, 2016 at 2:31 PM, Henry Saputra <
> > > henry.sapu...@gmail.com 
> > > 
> ');>>
> > > > > wrote:
> > > > >
> > > > > > Let me check the /asf-authorization-template.
> > > > > >
> > > > > > Michael, what is your Apache username?
> > > > > >
> > > > > > - Henry
> > > > > >
> > > > > > On Wed, Jul 27, 2016 at 5:05 AM, amareshwarisr . <
> > > > amareshw...@gmail.com 
> > > 
> ');>>
> > > > > > wrote:
> > > > > >
> > > > > > > Not sure if I'm missing any. Henry ?
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Jul 27, 2016 at 2:29 PM, amareshwarisr . <
> > > > > amareshw...@gmail.com 
> > > 
> ');>>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> H Michael,
> > > > > > >>
> > > > > > >> With same commit privileges, you should have access to svn as
> > > well.
> > > > > Can
> > > > > > >>  you write to infrastruct...@apache.org 
> > > ');>
> ?
> > > > > > >>
> > > > > > >> Thanks
> > > > > > >>
> > > > > > >> On Wed, Jul 27, 2016 at 12:55 PM, Michael Wu <
> > mchl@gmail.com 
> > > ');>>
> > > > > > wrote:
> > > > > > >>
> > > > > > >>> Hi guys,
> > > > > > >>>
> > > > > > >>> I'm blocked when I tired to update eagle's doc of website at:
> > > > > > >>> https://svn.apache.org/repos/asf/incubator/eagle/. It seems
> > that
> > > > my
> > > > > > >>> account
> > > > > > >>> "mw" doesn't have the write access. Could anyone help on
> this,
> > > > > please?
> > > > > > >>>
> > > > > > >>> Thanks.
> > > > > > >>> Michael
> > > > > > >>>
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Podling Report Reminder - August 2016

[Henry Saputra]

+1 to mention about graduation discussion.

- Henry

On Mon, Aug 1, 2016 at 12:14 AM, Julian Hyde  wrote:

> I think you should mention that the community is discussing
> graduation, and that is completed the maturity assessment.
>
> Maybe revise the "steps to graduation" in the light of those
> discussions. None of those 3 came up when I asked "What is left to do
> before Eagle graduates?". I think Eagle is close to the end game;
> there is some housekeeping to do, and needs to agree on things like
> bylaws (if any), PMC composition, and the text of the motion to put
> before the Board.
>
> Julian
>
>
> On Sun, Jul 31, 2016 at 12:13 PM, Edward Zhang 
> wrote:
> > I listed some achievement we have made for Eagle in last quarter, it
> should
> > not be sufficient, please review and add back
> >
> >
> > Eagle
> >
> >
> > Eagle is a Monitoring solution for Hadoop to instantly identify access to
> > sensitive data, recognize attacks, malicious activities and take actions
> in
> > real time.
> >
> > Eagle has been incubating since 2015-10-26.
> >
> >
> > Three most important issues to address in the move towards graduation:
> >
> > 1. Release of Apache Eagle 0.4.0
> >
> > 2. Community is growing and contributors built multiple use cases on top
> of
> > Eagle framework
> >
> > 3. Eagle site is modified to have more useful user guide content and to
> be
> > more aligned with Apache Podling policies.
> >
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >
> > aware of?
> >
> > NIL
> >
> >
> > How has the community developed since the last report?
> >
> > . Presented in Apache Con, May 2016
> >
> > . Presented in London Stratus + Hadoop, May 2016
> >
> > . Presented in San Jose Hadoop Summit, June 2016
> >
> > . Presented in China ...
> >
> > Communities showed continuous interest in Apache Eagle project. Some
> > company tried to integrate Eagle as part of whole solution and some
> > contributed different use case to Eagle platform, for example MapR
> support,
> > Oozie monitoring support etc.
> >
> >
> > How has the project developed since the last report?
> >
> > Technically we added more documents for user to easily use Eagle
> >
> > Besides Hadoop security monitoring, we have started working on
> performance
> > monitoring design and development based on the requests from community.
> >
> > As we may have multiple different use cases running on top of Eagle, a
> > design discussion and prototype is conducted to make sure Eagle is a
> > framework to host multiple use cases and user will use Eagle to manage
> > those use cases.
> >
> > Alert engine is going to be decoupled from data processing so that alert
> > engine will be multi-tenant and easy to be used by multiple use cases by
> > incorporating well-designed metadata.
> >
> >
> > Date of last release:
> >
> > 2016-07-19
> >
> >
> > When were the last committers or PMC members elected?
> >
> > Daniel Zhou, 2016-06-15
> >
> > Michael Wu, 2016-06-17
> >
> >
> > Signed-off-by:
> >
> > [ ](eagle) Owen O'Malley
> >
> > [](eagle) Henry Saputra
> >
> > [](eagle) Julian Hyde
> >
> > [](eagle) P. Taylor Goetz
> >
> > [](eagle) Amareshwari Sriramdasu
> >
> > Shepherd/Mentor notes:
> >
> >
> >
> > On Sun, Jul 31, 2016 at 6:15 AM,  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, 17 August 2016, 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, August 03).
> >>
> >> 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.
> >>
> >> Thanks,
> >>
> >> The Apache Incubator PMC
> >>
> &g

[HELP] could anyone help grant svn write access of directory https://svn.apache.org/repos/asf/incubator/eagle/ to Michael's apache account ?

[Henry Saputra]

Seemed like the change has been merged. Could you give it a spin?

- Henry

On Thu, Jul 28, 2016 at 10:49 PM, Michael Wu > wrote:

> Thank you very much, Henry! Could you please let me know once it's done?
>
> On Fri, Jul 29, 2016 at 1:44 PM, Henry Saputra  >
> wrote:
>
> > OK, seemed like your name is not in commit auth for the svn. I will send
> PR
> > to update it.
> >
> > - Henry
> >
> > On Wed, Jul 27, 2016 at 11:50 PM, Michael Wu  > wrote:
> >
> > > Henry, my apache username is "mw". Thanks.
> > >
> > > On Thu, Jul 28, 2016 at 2:31 PM, Henry Saputra <
> henry.sapu...@gmail.com
> >
> > > wrote:
> > >
> > > > Let me check the /asf-authorization-template.
> > > >
> > > > Michael, what is your Apache username?
> > > >
> > > > - Henry
> > > >
> > > > On Wed, Jul 27, 2016 at 5:05 AM, amareshwarisr . <
> > amareshw...@gmail.com
> >
> > > > wrote:
> > > >
> > > > > Not sure if I'm missing any. Henry ?
> > > > >
> > > > >
> > > > > On Wed, Jul 27, 2016 at 2:29 PM, amareshwarisr . <
> > > amareshw...@gmail.com
> >
> > > > > wrote:
> > > > >
> > > > >> H Michael,
> > > > >>
> > > > >> With same commit privileges, you should have access to svn as
> well.
> > > Can
> > > > >>  you write to infrastruct...@apache.org
>  ?
> > > > >>
> > > > >> Thanks
> > > > >>
> > > > >> On Wed, Jul 27, 2016 at 12:55 PM, Michael Wu  >
> > > > wrote:
> > > > >>
> > > > >>> Hi guys,
> > > > >>>
> > > > >>> I'm blocked when I tired to update eagle's doc of website at:
> > > > >>> https://svn.apache.org/repos/asf/incubator/eagle/. It seems that
> > my
> > > > >>> account
> > > > >>> "mw" doesn't have the write access. Could anyone help on this,
> > > please?
> > > > >>>
> > > > >>> Thanks.
> > > > >>> Michael
> > > > >>>
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>

Re: [HELP] could anyone help grant svn write access of directory https://svn.apache.org/repos/asf/incubator/eagle/ to Michael's apache account ?

[Henry Saputra]

OK, seemed like your name is not in commit auth for the svn. I will send PR
to update it.

- Henry

On Wed, Jul 27, 2016 at 11:50 PM, Michael Wu  wrote:

> Henry, my apache username is "mw". Thanks.
>
> On Thu, Jul 28, 2016 at 2:31 PM, Henry Saputra 
> wrote:
>
> > Let me check the /asf-authorization-template.
> >
> > Michael, what is your Apache username?
> >
> > - Henry
> >
> > On Wed, Jul 27, 2016 at 5:05 AM, amareshwarisr . 
> > wrote:
> >
> > > Not sure if I'm missing any. Henry ?
> > >
> > >
> > > On Wed, Jul 27, 2016 at 2:29 PM, amareshwarisr . <
> amareshw...@gmail.com>
> > > wrote:
> > >
> > >> H Michael,
> > >>
> > >> With same commit privileges, you should have access to svn as well.
> Can
> > >>  you write to infrastruct...@apache.org ?
> > >>
> > >> Thanks
> > >>
> > >> On Wed, Jul 27, 2016 at 12:55 PM, Michael Wu 
> > wrote:
> > >>
> > >>> Hi guys,
> > >>>
> > >>> I'm blocked when I tired to update eagle's doc of website at:
> > >>> https://svn.apache.org/repos/asf/incubator/eagle/. It seems that my
> > >>> account
> > >>> "mw" doesn't have the write access. Could anyone help on this,
> please?
> > >>>
> > >>> Thanks.
> > >>> Michael
> > >>>
> > >>
> > >>
> > >
> >
>

Re: [HELP] could anyone help grant svn write access of directory https://svn.apache.org/repos/asf/incubator/eagle/ to Michael's apache account ?

[Henry Saputra]

Let me check the /asf-authorization-template.

Michael, what is your Apache username?

- Henry

On Wed, Jul 27, 2016 at 5:05 AM, amareshwarisr . 
wrote:

> Not sure if I'm missing any. Henry ?
>
>
> On Wed, Jul 27, 2016 at 2:29 PM, amareshwarisr . 
> wrote:
>
>> H Michael,
>>
>> With same commit privileges, you should have access to svn as well. Can
>>  you write to infrastruct...@apache.org ?
>>
>> Thanks
>>
>> On Wed, Jul 27, 2016 at 12:55 PM, Michael Wu  wrote:
>>
>>> Hi guys,
>>>
>>> I'm blocked when I tired to update eagle's doc of website at:
>>> https://svn.apache.org/repos/asf/incubator/eagle/. It seems that my
>>> account
>>> "mw" doesn't have the write access. Could anyone help on this, please?
>>>
>>> Thanks.
>>> Michael
>>>
>>
>>
>

Re: [ANNOUNCE] Apache Eagle 0.4.0-incubating released

[Henry Saputra]

Congratulation guys!

Great job managing the release.

On Wed, Jul 20, 2016 at 8:53 PM, Michael Wu  wrote:

> Hi,
>
> The Apache Eagle (incubating) Community is happy to announce the release of
> version 0.4.0-incubating from the Apache Incubator.
>
> Apache Eagle (incubating) is a monitoring framework to analyze big data
> platforms for security and performance.
>
> The release bits are available at:
>
> http://www.apache.org/dyn/closer.cgi?path=/incubator/eagle/apache-eagle-0.4.0-incubating
>
> The change list is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/tags/v0.4.0-incubating
>
> We would like to thank all contributors who made the release possible.
>
> Disclaimer :
> Apache Eagle is an effort undergoing incubation at The Apache Software
> Foundation
> (ASF), sponsored by the Apache Incubator PMC.
> Incubation is required of all newly accepted projects until a further
> review
> indicates that the infrastructure, communications, and decision making
> process have stabilized in a manner consistent with other successful ASF
> projects.
> While incubation status is not necessarily a reflection of the completeness
> or stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>
> Regards,
> Apache Eagle (incubating) Community
>

Re: [Discuss] what will be the decent way to remove jars from source code for releases

[Henry Saputra]

So what was the solution for this? Could someone points to JIRA or Github
PR to fix this?

Thanks much!

- Henry

On Mon, Jul 11, 2016 at 1:30 AM, Julian Hyde  wrote:

> Can someone explain why these jar files have to be checked into git?
> Many other jar (and other binary) files are retrieved from a maven
> repo when you build; why not these? You can use maven magic to
> extract/filter/copy these files exactly where you need them on the
> first build.
>
> Source files have a sacred role in open source because (a) they can be
> edited (a fundamental right granted by an open source license), (b)
> they can be audited during a release.
>
> And, leaving the open source issues aside and just looking at the
> software engineering, checking non-source files into a source-control
> system, and especially into git, is often a bad idea. For instance,
> projects hotly debate whether to check in java files generated by
> protobuf, because the .proto file is the "source", and the .java files
> are generated. Git doesn't handle binary files particularly well, and
> if the binary is modified a few times the git repo starts to become
> bloated in size.
>
> Julian
>
>
> On Sun, Jul 10, 2016 at 8:28 PM, Zhang, Edward (GDI Hadoop)
>  wrote:
> > In 0.3 release, Hemanth uses a patch to work around this issue. Can we
> use the same approach in 0.4 and in 0.5 we have decided to remove
> dependency on tomcat.
> >
> >
> > Thanks
> >
> > Edward
> >
> > 
> > From: Hao Chen 
> > Sent: Sunday, July 10, 2016 8:17:48 PM
> > To: dev@eagle.incubator.apache.org
> > Subject: Re: [Discuss] what will be the decent way to remove jars from
> source code for releases
> >
> > Yes, the jars are added into the source package intentionally, which is
> > necessary for bootstrapping eagle service. So maybe it possible for us
> the
> > keep the jars following apache way? Otherwise we may need some additional
> > work to refactoring our package method.
> >
> > - Hao
> >
> > On Mon, Jul 11, 2016 at 11:07 AM, Michael Wu  wrote:
> >
> >> Hi guys,
> >>
> >> Further tested and verified, the 3 jar dependencies are NECESSARY for
> the
> >> eagle-service to start up. Without them, we can build the project but
> when
> >> we deploy it, eagle-service fails to start up complaining the lack of
> the
> >> dependencies. So, we cannot simply remove them before packaging the
> source
> >> tar ball.
> >>
> >> @PPMC, so far, we can tell that the 3 remaining jars are intended to be
> >> there for the project's normal functionalities, they are important and
> >> cannot be removed, can we just vote them as passed, please?
> >>
> >> Michael
> >>
> >> On Sat, Jul 9, 2016 at 3:46 PM, Michael Wu  wrote:
> >>
> >> > Hi dev group,
> >> >
> >> > As you may know, we encountered the issue of having depended jars
> within
> >> > the source tar ball of 0.4.0-incubating RC1 and RC2, they are:
> >> > ***
> >> > eagle-assembly/src/main/lib/tomcat/bin/bootstrap.jar
> >> > eagle-assembly/src/main/lib/tomcat/bin/commons-daemon.jar
> >> > eagle-assembly/src/main/lib/tomcat/bin/tomcat-juli.jar
> >> > ***
> >> >
> >> > I've verified, if the 3 jars are removed, maven build can also get
> >> passed.
> >> > But I'm still curious about what's the use of these jars, and will the
> >> > removal of them affects eagle service while the service is deployed
> >> > somewhere?
> >> >
> >> > So could anyone tell some details of the jars and give some advice on
> >> > "shall we also remove the jars in git repository"?
> >> >
> >> > To my understanding, if we just remove the jars from source-RCx, then
> the
> >> > packaged tar ball will contain different files than the view we can
> see
> >> in
> >> > git repository, will this situation violate release policy? Please you
> >> guys
> >> > know well about it DO give instructions. It's highly appreciated!
> >> >
> >> > Michael
> >> >
> >>
>

Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 2)

[Henry Saputra]

Simply reply to the original VOTE  thread prefix the subject with [CANCEL]

In the body of the reply, just add comments that the VOTE is cancelled due
to exe files found as release artifacts.

On Sat, Jul 9, 2016 at 12:48 AM, Liangfei.Su  wrote:

> Mike,
>
> I found a sample cancel vote thread. I think a simple cancel with reason
> stated should be ok, detailed result could be better. You might follow the
> same.
>
> @Julian, comment?
>
>
>  reference ( don't know how to make email as attached directly, simply
> copy here for refernece.)
>
> [CANCEL][VOTE] Release Mynewt 0.9.0-incubating-rc1
>
> Christopher Collins 
> May 28
>
> Hello all,
>
> Voting for the release of 0.9.0-incubating-rc1 has been cancelled due to
> some incorrectly packaged source [*].
>
> Sorry for the confusion, and thank you to everyone who voted.  A second
> release candidate will be put up for a vote on the dev list shortly.
>
> Thanks,
> Chris
>
> [*] For the newt release, a subdirectory was packaged rather than the
> entire repo.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>
>
>
> On Sat, Jul 9, 2016 at 3:10 PM, Michael Wu  wrote:
>
> > Hi Julian,
> >
> > I'd say, it's the quality of the release that is more important than
> > anything else. As you mentioned, I'll bring another discussion for this
> > issue. BTW, could you let me know if I have to send a result email of
> the 2
> > rejected RC to cancel the VOTE? Thanks.
> >
> > Michael
> >
> > On Sat, Jul 9, 2016 at 2:29 AM, Julian Hyde  wrote:
> >
> > > I feel your pain: it's painful to have two RCs shot down. But let's
> > > not have design discussions on a VOTE thread. Let's cancel the vote,
> > > and start a discussion in another thread. If there is an existing JIRA
> > > for this issue, please forward that; it will help us avoid going over
> > > the same old ground.
> > >
> > > On Fri, Jul 8, 2016 at 10:01 AM, Michael Wu 
> wrote:
> > > > @ Hemanth,
> > > >
> > > > Indeed, we could have kept the tar containing only source code,
> without
> > > > packaged non-open-source stuffs, I know it's required by Apache
> policy,
> > > and
> > > > agree with the policy totally.
> > > >
> > > > However, for our project, let's just make an imagination, if we move
> > the
> > > > jars out of the project and create the source tar, so far for voting
> > and
> > > > consequently for releasing in the future, each time customers of the
> > > > project download the source code, they may be unable to build the
> > project
> > > > with merely executing maven build commands, on the contrary, they
> have
> > to
> > > > download and place these depended jars appropriately by themselves,
> > isn't
> > > > it unfriendly and a super boring manner?
> > > >
> > > > Then, that's why I asked you guys who may know the use of the jars
> and
> > > may
> > > > give valuable suggestions for how to deal better with them, on 1 hand
> > not
> > > > blocking future maven builds, on the other hand can make it satisfy
> > > > apache's release policy. Currently, I'm still not sure if it may
> bring
> > > many
> > > > additional efforts, but customer friendly seems very important to a
> > > project.
> > > >
> > > > So, could you give some details on how much the removal of jars will
> > > affect
> > > > the build? Appreciated!
> > > >
> > > > @ all, do you guys have any thought on this issue, please? We seem to
> > > have
> > > > been blocked a bit at it. Thanks.
> > > >
> > > > Michael
> > > >
> > > > Michael
> > > >
> > > > On Sat, Jul 9, 2016 at 12:21 AM, Dendukuri, Hemanth <
> > hdenduk...@ebay.com
> > > >
> > > > wrote:
> > > >
> > > >> Michael, Since this is voting for source only, we need to make sure
> > only
> > > >> eagle source if voted.
> > > >>
> > > >> The artifacts should be uploaded for voting before packaging ("mvn
> > > >> package”), I believe.
> > > >>
> > > >> You can provide the instructions on how to get required tomcat jars
> > for
> > > >> the build, if eagle has dependencies.
> > > >>
> > > >> Regards
> > > >> Hemanth
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> On 7/7/16, 11:30 PM, "Michael Wu"  wrote:
> > > >>
> > > >> >@ Hemanth,
> > > >> >
> > > >> >Did you mean to directly remove the
> > eagle-assembly/src/main/lib/tomcat
> > > >> >directory before packaging the source? I saw the directory removed
> in
> > > >> >0.3.0-incubating release, do you have any idea about the following
> 2:
> > > >> >1. does this removal impact building approach and behavior?
> > > >> >2. if we remove it, after "mvn package" phase, will the final jar
> > > >> assembled
> > > >> >have potential running issue with eagle-service?
> > > >> >
> > > >> >If the jars have dependencies on them, we may have to make more
> > > efforts to
> > > >> >fix it before voting RC3.
> > > >> >
> > > >> >Thanks.
> > > >> >Michael
> > > >> >
> > > >

Re: [Eagle Release Q & A] Do we have to scp KEYS to the links listed?

[Henry Saputra]

As I remember the LDAP sync will automatically update the key group file.

- Henry

On Thu, Jun 30, 2016 at 10:15 PM, Michael Wu  wrote:

> Hi Henry,
>
> My gpg fingerprint has been updated on id.apache.org, how can I add my key
> to keys/groups/eagle.asc, is there any place that automatically sync the
> keys to groups, please? Thanks!
>
> Michael
>
> On Thu, Jun 30, 2016 at 3:56 PM, Henry Saputra 
> wrote:
>
> > Putting the KEYS in dis folder is used to verify the signature of the
> > release artifacts.
> >
> > I think it is more used for convenience since Eagle already have group
> sig
> > file at https://people.apache.org/keys/group/eagle.asc
> >
> > - Henry
> >
> > On Thu, Jun 30, 2016 at 1:55 PM, Michael Wu  wrote:
> >
> > > Hi Hemanth,
> > >
> > > Reading your WIKI of release process, I've merged my gpg-pub-key into
> > KEYS
> > > file, and have committed it to svn, which is visible at
> > > http://www.apache.org/dist/incubator/eagle/.
> > >
> > > However, I got confused on step-14 at below fragment, see:
> > > *
> > > ..
> > > Once this file has been updated, you need to publish it in the
> > appropriate
> > > dist directory for the project on http://www.apache.org/dist. To do
> > this,
> > > you must copy the file as follows:
> > >   $ scp KEYS people.apache.org:/www/
> > > www.apache.org/dist/incubator/eagle/KEYS
> > >   <http://org/www/www.apache.org/dist/incubator/sentry/KEYS>
> > > ..
> > > *
> > >
> > > My question is, now that the KEYS has been committed to svn, what's the
> > use
> > > this fragment? Will it block releasing if I ignore it? Also, what does
> it
> > > mean in the angle bracket pair "<>", do you mean we have to scp the
> KEYS
> > to
> > > the 2 urls, both?
> > >
> > > Thanks.
> > > Michael
> > >
> >
>

Re: Web site branding

[Henry Saputra]

Yeah, thinking moving the link and incubator logo up in the header and keep
the incubator disclaimer as footer.

Also move some content in between to separate page to make visitor scroll
less for homepage.

Thoughts?

- Henry

On Thu, Jun 30, 2016 at 6:31 PM, John D. Ament 
wrote:

>
>
> On 2016-06-29 20:48 (-0400), Henry Saputra 
> wrote:
> > Probably we could move this section to Powered By Eagle page so homepage
> > could be more clear it is part of ASF and also include Incubator
> > description on top of page.
>
> So you're thinking about moving some of the ASF logos up, not buried in
> the footer?
>
> >
> > On Thursday, June 30, 2016, arunkarthick m 
> wrote:
> >
> > > The eBay logo and Paypal logo under who uses Eagle part is taking up
> too
> > > much screen space. Apart from that ebay is mentioned only in one place.
> > >
> > > Thanks,
> > > Arun
> > >
> > > On Wed, Jun 29, 2016 at 2:40 PM, Julian Hyde  > > > wrote:
> > >
> > > > Check what the branding guide says. I think only the first occurrence
> > > > needs to be fully-qualified.
> > > >
> > > > But also ask yourself: Does this page make it look like the project
> is
> > > > controlled by a particular company?
> > > >
> > > > > On Jun 29, 2016, at 1:57 PM, arunkarthick m <
> aruncarth...@gmail.com
> > > >
> > > > wrote:
> > > > >
> > > > > There are lots of places where we mentioned "Eagle". We need to
> change
> > > > them
> > > > > to be Apache Eagle.
> > > > >
> > > > > Thanks,
> > > > > Arun
> > > > >
> > > > > On Wed, Jun 29, 2016 at 11:52 AM, arun karthick manoharan <
> > > > > aruncarth...@gmail.com > wrote:
> > > > >
> > > > >> I'm looking at the branding guide will send what I find.
> > > > >>
> > > > >> Thanks,
> > > > >> Arun
> > > > >>
> > > > >> Sent from my iPhone
> > > > >>
> > > > >>> On Jun 29, 2016, at 11:15 AM, Hao Chen  > > > wrote:
> > > > >>>
> > > > >>> Will continue to verify and update the fix.
> > > > >>>
> > > > >>> - Hao
> > > > >>>
> > > > >>>> On Wed, Jun 29, 2016 at 10:21 AM, Julian Hyde  > > >
> > > > wrote:
> > > > >>>>
> > > > >>>> Did you find any other violations of branding policy?
> > > > >>>>
> > > > >>>>> On Jun 29, 2016, at 10:13 AM, Hao Chen  > > > wrote:
> > > > >>>>>
> > > > >>>>> Updated with (incubating), thanks for advising.
> > > > >>>>>
> > > > >>>>> - Hao
> > > > >>>>>
> > > > >>>>>> On Wed, Jun 29, 2016 at 9:48 AM, Julian Hyde <
> jh...@apache.org
> > > >
> > > > >> wrote:
> > > > >>>>>>
> > > > >>>>>> There is a discussion on general@incubator about podlings’
> web
> > > > sites
> > > > >>>> and
> > > > >>>>>> URLs, and Eagle came in for some criticism. Can someone please
> > > > review
> > > > >>>> the
> > > > >>>>>> site for compliance with Apache’s branding guidelines for
> > > podlings?
> > > > >>>>>>
> > > > >>>>>> For instance, the first mention of Eagle on each page must be
> > > > followed
> > > > >>>> by
> > > > >>>>>> “(incubating)”, and that does not happen. There may be other
> > > > >> violations
> > > > >>>>>> too. During incubation we are looking to see whether the PPMC
> is
> > > > >>>> capable of
> > > > >>>>>> proactively enforcing the Apache brand.
> > > > >>>>>>
> > > > >>>>>> Julian
> > > > >>>>
> > > > >>>>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Arun Karthick
> > > > > 201-850-9399
> > > >
> > > >
> > >
> > >
> > > --
> > > Arun Karthick
> > > 201-850-9399
> > >
> >
>

Re: [Eagle Release Q & A] Do we have to scp KEYS to the links listed?

[Henry Saputra]

Putting the KEYS in dis folder is used to verify the signature of the
release artifacts.

I think it is more used for convenience since Eagle already have group sig
file at https://people.apache.org/keys/group/eagle.asc

- Henry

On Thu, Jun 30, 2016 at 1:55 PM, Michael Wu  wrote:

> Hi Hemanth,
>
> Reading your WIKI of release process, I've merged my gpg-pub-key into KEYS
> file, and have committed it to svn, which is visible at
> http://www.apache.org/dist/incubator/eagle/.
>
> However, I got confused on step-14 at below fragment, see:
> *
> ..
> Once this file has been updated, you need to publish it in the appropriate
> dist directory for the project on http://www.apache.org/dist. To do this,
> you must copy the file as follows:
>   $ scp KEYS people.apache.org:/www/
> www.apache.org/dist/incubator/eagle/KEYS
>   
> ..
> *
>
> My question is, now that the KEYS has been committed to svn, what's the use
> this fragment? Will it block releasing if I ignore it? Also, what does it
> mean in the angle bracket pair "<>", do you mean we have to scp the KEYS to
> the 2 urls, both?
>
> Thanks.
> Michael
>

Re: Web site branding

[Henry Saputra]

Probably we could move this section to Powered By Eagle page so homepage
could be more clear it is part of ASF and also include Incubator
description on top of page.

On Thursday, June 30, 2016, arunkarthick m  wrote:

> The eBay logo and Paypal logo under who uses Eagle part is taking up too
> much screen space. Apart from that ebay is mentioned only in one place.
>
> Thanks,
> Arun
>
> On Wed, Jun 29, 2016 at 2:40 PM, Julian Hyde  > wrote:
>
> > Check what the branding guide says. I think only the first occurrence
> > needs to be fully-qualified.
> >
> > But also ask yourself: Does this page make it look like the project is
> > controlled by a particular company?
> >
> > > On Jun 29, 2016, at 1:57 PM, arunkarthick m  >
> > wrote:
> > >
> > > There are lots of places where we mentioned "Eagle". We need to change
> > them
> > > to be Apache Eagle.
> > >
> > > Thanks,
> > > Arun
> > >
> > > On Wed, Jun 29, 2016 at 11:52 AM, arun karthick manoharan <
> > > aruncarth...@gmail.com > wrote:
> > >
> > >> I'm looking at the branding guide will send what I find.
> > >>
> > >> Thanks,
> > >> Arun
> > >>
> > >> Sent from my iPhone
> > >>
> > >>> On Jun 29, 2016, at 11:15 AM, Hao Chen  > wrote:
> > >>>
> > >>> Will continue to verify and update the fix.
> > >>>
> > >>> - Hao
> > >>>
> >  On Wed, Jun 29, 2016 at 10:21 AM, Julian Hyde  >
> > wrote:
> > 
> >  Did you find any other violations of branding policy?
> > 
> > > On Jun 29, 2016, at 10:13 AM, Hao Chen  > wrote:
> > >
> > > Updated with (incubating), thanks for advising.
> > >
> > > - Hao
> > >
> > >> On Wed, Jun 29, 2016 at 9:48 AM, Julian Hyde  >
> > >> wrote:
> > >>
> > >> There is a discussion on general@incubator about podlings’ web
> > sites
> >  and
> > >> URLs, and Eagle came in for some criticism. Can someone please
> > review
> >  the
> > >> site for compliance with Apache’s branding guidelines for
> podlings?
> > >>
> > >> For instance, the first mention of Eagle on each page must be
> > followed
> >  by
> > >> “(incubating)”, and that does not happen. There may be other
> > >> violations
> > >> too. During incubation we are looking to see whether the PPMC is
> >  capable of
> > >> proactively enforcing the Apache brand.
> > >>
> > >> Julian
> > 
> > 
> > >>
> > >
> > >
> > >
> > > --
> > > Arun Karthick
> > > 201-850-9399
> >
> >
>
>
> --
> Arun Karthick
> 201-850-9399
>

Re: [RESULT][VOTE] Release Eagle Incubating Version 0.3.0(RC3)

[Henry Saputra]

Thanks all, I am coming late for reviewing the release artifacts.

I will run my VOTE in general@ list instead.

Please forward the VOTE to general@ list incubator.

- Henry

On Mon, Mar 28, 2016 at 8:40 AM, Dendukuri, Hemanth 
wrote:

> Voting is now closed and the voting for "Apache Eagle, 0.3.0 Release
> Candidate 3" passed with 7 binding +1 votes from the Incubator PMC members
> and One +1 VOTE from apache contributor. There are no 0 or -1 votes.
>
> Votes:
> +1 Julian Hyde(binding)
> +1 amareshwarisr(binding)
> +1 Hao Chen(binding)
> +1 Zhao Qingwen (binding)
> +1 arun karthick manoharan (binding)
> +1 Michael Wu (binding)
> +1 Edward Zhang (binding)
>
> +1 (Liangfei.Su)
>
>
> Thread:
> https://www.mail-archive.com/dev@eagle.incubator.apache.org/msg02766.html
>
>
> Thanks to all who reviewed and voted.
> I will proceed for Voting on General Incubation.
>
>
> Regards,
> Hemanth
>

Re: Eagle 0.3.0 Incubating Release comments from Julian

[Henry Saputra]

When you said "derived from Apache Amabari", did you mean you copied the
file?

It should have Apache header too in that case.

- Henry

On Wed, Mar 16, 2016 at 1:14 PM, Chen, Hao  wrote:

> The app.js file is derived from Apache Amabri because it’s licensed under
> Apache V2, so don’t need to declare in top-level license file.
>
>
> On 3/17/16, 1:35 AM, "Dendukuri, Hemanth"  wrote:
>
> >@ Hao,
> >
> >Kindly answer below questions.
> >
> >eagle-external/eagle-ambari/lib/EAGLE/package/patches/app.js comes from?
> Although it is a text file, it is 1.7M lines long so I doubt
> >that you can call it "source code". Was it generated? Was it copied from
> another project?
> >
> >
> >
> >Julian,  I will execute below comments without fail.
> >
> >MD5, SHA1 and SHA512 matches. I think we should not keep other .sha file.
> >
> >Next release, I think you only need the .sha1 file; omit the .sha and
> .sha512 files.
> >
> >Also, I'm not sure if you can add and drop files from directory once the
> vote is called out.
> >
> >In future, do not alter the contents of the release candidate being
> >voted on. If there are serious issues you will need to cancel the vote
> >and make a new release candidate; if the issues are not serious you
> >should make sure to fix them in your next release. Either way, each
> >release candidate is immutable.
> >
> >In this case, the sha of the file matched the sha in the vote thread,
> >so everything is fine.
> >
> >This is the second release candidate, but the email has the same
> >subject as the first RC. Next time, I suggest that you include the RC
> >number in the email subject line and the directory name e.g.
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc2/
> >so that it is clear what is being voted on.
> >
> >Also, I don't think I saw a "[CANCEL] [VOTE] Release Eagle Incubating
> >Version 0.3.0" or "[RESULT] [VOTE] Release Eagle Incubating Version
> >0.3.0" message. Remember to terminate each vote thread.
> >
> >
> >Regards
> >Hemanth
>

Re: [DISCUSS] Adding new mailing list to contain JIRA and Github updates

[Henry Saputra]

Ah, we already have issues@ list? Sorry, I missed it.

Yeah, if we have karma to change the notifications that would be great.

- Henry

On Fri, Mar 11, 2016 at 12:33 PM, Edward Zhang 
wrote:

> Understood. I checked we already have issues@ and commits@, but we need
> modify JIRA notifications in the page
>
> https://issues.apache.org/jira/plugins/servlet/project-config/EAGLE/notifications
>
> Looks our mentor Sriramadasu have the permission to modify. We can have
> JIRA ticket created message to be sent to dev@, and have other messages to
> be sent to issues@.
>
> Thanks
>
> Edward
>
> On Fri, Mar 11, 2016 at 12:36 AM, Julian Hyde 
> wrote:
>
> > +1 on keeping the volume on the list manageable. A project with a high
> > volume list is difficult to contribute to if that project is not your
> main
> > job, and we want to encourage a diversity of contributors.
> >
> > A variation on what Henry is suggesting is to have jira send a message to
> > the dev list only when a jira case is created. Subsequent updates go only
> > to the issues list. But the initial email allows anyone interested to
> press
> > "watch" on a case and receive all further updates for that case.
> >
> > Julian
> >
> > > On Mar 10, 2016, at 10:42 PM, Henry Saputra 
> > wrote:
> > >
> > > Hi All,
> > >
> > > With Apache Eagle podling getting more active every day, it seemed like
> > > JIRA updates and Github mirror updates start to become clutter to the
> dev
> > > list.
> > >
> > > I think it is time to introduce new list, typically called issues@ as
> > the
> > > reservoir for the updates.
> > >
> > > We will still need to make JIRA create event to be delivered to dev@
> for
> > > bookeeping but updates could be redirected to issues@
> > >
> > > This is one of the "good" problems to have =)
> > >
> > > Let me know what you guys think.
> > >
> > > Thanks,
> > >
> > > Henry
> >
>

[DISCUSS] Adding new mailing list to contain JIRA and Github updates

[Henry Saputra]

Hi All,

With Apache Eagle podling getting more active every day, it seemed like
JIRA updates and Github mirror updates start to become clutter to the dev
list.

I think it is time to introduce new list, typically called issues@ as the
reservoir for the updates.

We will still need to make JIRA create event to be delivered to dev@ for
bookeeping but updates could be redirected to issues@

This is one of the "good" problems to have =)

Let me know what you guys think.

Thanks,

Henry

Re: Release?

[Henry Saputra]

Friendly reminder that Release manager should come from PPMC since it may
need access to ASF resources.

- Henry

On Fri, Jan 22, 2016 at 12:02 PM, arunkarthick m 
wrote:

> I agree with Julian. Edward is starting to collect the list of features
> that are ready. I'm guessing Michael Wu will be a good release manager and
> start getting educated on the apache process.
>
> Thanks,
> Arun
>
>
>
> On Fri, Jan 22, 2016 at 11:59 AM, Julian Hyde  wrote:
>
> > It’s difficult to describe the “licensing issues”. I suggest that you
> > nominate a release manager and that person subscribes to the
> > general@incubator list [1] and follows the discussions there. Watch the
> > kind of due diligence that people such as Justin McLean apply to the
> > releases, e.g. the Freemarker release [2]. (It seems onerous but is much
> > appreciated by your community, because it means they are getting
> spotlessly
> > clean IP.)
> >
> > You will need to go through the same process: after a vote on this dev
> > list, there is a second vote on the generator@incubator list.
> >
> > I can’t stress this strongly enough: The actual features (and bugs) in
> the
> > first release is very unimportant. It is all about the legal packaging,
> and
> > the process by which you make the release. No reason not to start now.
> >
> > Julian
> >
> > [1] http://mail-archives.apache.org/mod_mbox/incubator-general/
> >
> > [2]
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3CB538B622-B173-4778-97AB-12E66D480FE8%40classsoftware.com%3E
> >
> > > On Jan 22, 2016, at 11:46 AM, Zhang, Edward (GDI Hadoop) <
> > yonzh...@ebay.com> wrote:
> > >
> > > Thanks for initiating this discussion. I also wonder how to do the
> first
> > > release, what it the timing, what is the version number and what
> features
> > > we should include and what is release notes.
> > >
> > > But I am not aware of licensing issues. Does that because that not all
> > our
> > > source files are for apache license so we need explicitly tell that in
> > > public?
> > >
> > > I volunteer to collect the features for the first release. A lot more
> > work
> > > should be identified while we are progressing.
> > >
> > > Thanks
> > > Edward
> > >
> > > On 1/22/16, 8:44, "Julian Hyde"  wrote:
> > >
> > >> Hi eagle community,
> > >>
> > >> How¹s progress on the first Eagle release?
> > >>
> > >> The Eagle project is progressing at an admirable rate in terms of
> > >> features and community engagement. However, you¹ve not yet made a
> > >> release. Making a release is more tricky than you would imagine ‹ and
> > >> it¹s usually due to licensing issues, not due to bugs or other code
> > >> issues ‹ so the first one takes a month or two. But making releases
> is a
> > >> key part of learning the Apache way and demonstrating that you¹re
> ready
> > >> to graduate; and, it helps to build community.
> > >>
> > >> Also remember that the project does not need to be ³perfect². Your
> first
> > >> release will have lots of bugs in it. If it compiles and has a README,
> > >> that is enough.
> > >>
> > >> Julian
> > >>
> > >
> >
> >
>
>
> --
> Arun Karthick
> 201-850-9399
>

Re: [Proposal] Dynamical Topology Manager

[Henry Saputra]

I think we could start with a list of what Apache Eagle needed from
Topology lifecycle management and see if we do cross-post to both dev@ list
of Eagle and Storm to see if enough interest from Storm to work on it or
accept contributions from Eagle.

- Henry

On Fri, Jan 15, 2016 at 4:06 PM, Zhang, Edward (GDI Hadoop) <
yonzh...@ebay.com> wrote:

> I had a short discussion with Henry about this. We probably need discuss a
> more graceful way to tackle the problem of whether eagle does this or
> storm does this.
> Today we know that Storm also provides topology view/statistics features
> but does not have topology lifecycle management UI.
> But can we ask Storm team to build this topology lifecycle UI?
> Right now, can we make our implementation more pluggable and extensible so
> later on if Storm has this feature, we can use that directly (at least
> from API lever)
>
> Do you want to communicate with storm community about this or probably
> Eagle committer can build this feature and contribute back to storm?
>
> What do you think?
>
> Thanks
> Edward
>
>
>
> On 1/11/16, 14:45, "Edward Zhang"  wrote:
>
> >Thanks for the valuable comments, you are right in the high-level
> >observations :-)
> >
> >(I participated some offline discussion on this proposal) I think this
> >proposal is based on the requirements that Eagle not only monitors
> >security
> >events from hadoop but also monitors security events from other data
> >source, for example cassandra and even more requirements are from hadoop
> >native metric monitoring. In last 2 months, when we want to onboard new
> >diverse datasources(for example mongo db metrics, hadoop native metrics
> >etc.), we find it is impossible for user(mostly operations team) to
> >understand storm topology or write code for very simple metrics
> >ingestion/alert rules. For monitoring perspective, user usually wants
> >metric/log onboarding is as simple as turn-key operation.
> >
> >It is possible for Eagle developers to develop applications for each data
> >source, but it might be better for Eagle to support logs/metrics with some
> >general schema. User just needs some configurations to get new data source
> >flow into Eagle and create policy on-the-fly against the streaming data.
> >Maybe I am wrong, but Eagle looks is an application to Storm framework,
> >but
> >Eagle would be a framework to monitoring applications e.g. security or
> >other data activity.
> >
> >The point of Eagle to separate application and framework is very correct.
> >In Eagle source code, the application code and framework code are
> >separated
> >from the beginning. For those features like policy restore after machine
> >fails, DSL, aggregation etc, I think Eagle team should look for
> >contributing back to Storm if people agree that is what stream framework
> >should have.
> >
> >We also found that Eagle monitoring uses streaming framework but streaming
> >framework is not customized for monitoring. The gap between monitoring
> >platform and streaming framework has to be filled to make sure monitoring
> >is reliable. For example compared to real-time streaming analytics,
> >monitoring does not want to have any false alert or missing alert
> >especially for security event, which requires more processing semantics
> >than popular streaming framework provides. We will actively explore help
> >from streaming projects.
> >
> >Thanks
> >
> >Edward
> >
> >On Mon, Jan 11, 2016 at 10:55 AM, Julian Hyde  wrote:
> >
> >> Can I make a high-level observation? (And, although I¹m a mentor of this
> >> project, I¹m not speaking as a mentor, just someone who has built
> >>various
> >> database and streaming systems over the years.)
> >>
> >> I¹ve noticed that Eagle is taking on several problems that ‹
> >> architecturally speaking ‹ should be part of the underlying streaming
> >> system. This topology manager and also, a DSL declarative streaming
> >> queries, and making sure that streaming queries continue where they left
> >> off, even in the presence of failures of individual stream-processing
> >>nodes.
> >>
> >> These are very hard distributed systems problems, and they are
> >>horizontal
> >> problems that have nothing to do with Eagle¹s problem domain
> >>(security). It
> >> would be analogous to an application that is selling concert tickets
> >> deciding to develop HBase as part of the application.
> >>
> >> If the Eagle community wants to solve these problems, that¹s awesome,
> >>and
> >> you should go for it. Apache projects are great at pulling in people
> >>with
> >> diverse skills and when they gather momentum they can build some amazing
> >> technology. But I think Eagle should consider putting more architectural
> >> separation between your stream management technology and your
> >>application.
> >> You could do that by building separate modules (and testing them
> >> independently). Or you could contribute the functionality you need to
> >>the
> >> underlying system (e.g. Storm/Nimbus). Your project 

Re: request an account for the jenkins

[Henry Saputra]

Spark should never use Berkeley Jenkins in the first place.

Either ASF Jenkins or Travis via Github integration the way to go

On Thursday, December 10, 2015, Michael Wu  wrote:

> Hao,
>
> Seems that we cannot make use of the berkeley jenkins, they refused to
> grant access for project other than Spark.
>
> I'll check with other options and keep asking bui...@apache.org
>  for help
> until they respond.
> Michael
>
> -- Forwarded message --
> From: shane knapp >
> Date: Fri, Dec 11, 2015 at 2:41 AM
> Subject: Re: request an account for the jenkins
> To: Michael Wu >
>
>
> hey michael,
>
> the jenkins instance you're pointing to is specifically for spark, and
> not any other apache projects.
>
> sorry!
>
> shane
>
> On Wed, Dec 9, 2015 at 8:46 PM, Michael Wu  > wrote:
> > Hi master,
> >
> > I'm a member of an apache incubator project, and would like to request an
> > account to create jobs to build and improve the process of the project.
> > Could you please assign me an account and grant the access to
> > https://amplab.cs.berkeley.edu/jenkins? Thanks!
> >
> > Best Regards,
> > Michael
>

Re: how to get an account for "Jenkins continuous-integration server"

[Henry Saputra]

What about using Travis service [1] while waiting for ASF Jenkins.

We need to just Travis YAML file like in Flink [2]

Apache has increased Travis capacity for Github mirror.

- Henry

[1] https://travis-ci.org/
[2] https://github.com/hsaputra/flink/blob/master/.travis.yml

On Wed, Dec 9, 2015 at 6:28 PM, Michael Wu  wrote:
> Hao,
>
> Currently, I'm asking builds team to add "github pull request builder"
> plugin to jenkins service, emails have been sent out, but with no response.
>
> Then, I have a thought, if the public apache jenkins can install the plugin
> and be configured to work as expected, we could certainly use it. But what
> if the team refuses to install the plugin or even they install it but we
> don't have the permission to configure it? Additionally, take the fact that
> a huge amount of jobs are running on the jenkins service into account,
> suppose we have our job on that one, when a PR comes up, we cannot
> guarantee that it would be built in time because it may be put in the
> waiting queue to wait for other running jobs to finish.
>
> So, after a brief research, I find, the jenkins service that spark uses is
> not apache's, but setup on berkeley.edu: amplab.cs.berkeley.edu/jenkins.
> Now I'm trying to get access to the service and see if it can fit our needs.
>
> Above is the currently status of the task, i'll keep you updated when any
> step forwards.
>
> BR,
> Michael
>
> On Sun, Dec 6, 2015 at 6:01 PM, Hao Chen  wrote:
>
>> Hi Michael,
>>
>> What's the status of Apache Jenkins CI?
>>
>> Regards,
>> Hao
>>
>> On Fri, Dec 4, 2015 at 4:40 PM, Michael Wu  wrote:
>>
>> > Amareshwarisr,
>> >
>> > It works now! Thank you very much for your great help!
>> >
>> > Best Wishes,
>> > Michael
>> >
>> > On Thu, Dec 3, 2015 at 11:23 PM, amareshwarisr . 
>> > wrote:
>> >
>> > > Hao,
>> > >
>> > > I've added you. Let me know if you are still facing any issue.
>> > >
>> > > Thanks
>> > >
>> > > On Thu, Dec 3, 2015 at 4:50 PM, Hao Chen  wrote:
>> > >
>> > > > Amareshwari,
>> > > >
>> > > > It will be highly appreciated if you could help grant me (apache id:
>> > hao)
>> > > > the permission to configure new Jenkins job and we are setting up CI
>> > for
>> > > > Apache Eagle project.
>> > > >
>> > > > Best Regards,
>> > > > Hao
>> > > >
>> > > > On Thu, Dec 3, 2015 at 7:10 PM, amareshwarisr . <
>> amareshw...@gmail.com
>> > >
>> > > > wrote:
>> > > >
>> > > >> Added Hao.
>> > > >>
>> > > >> Thanks,
>> > > >> Amareshwari
>> > > >>
>> > > >> On Thu, Dec 3, 2015 at 7:21 AM, Michael Wu 
>> > wrote:
>> > > >>
>> > > >>>  Amareshwari,
>> > > >>>
>> > > >>> So glad to hear from you. I do need the access to configure new
>> jobs
>> > > for
>> > > >>> incubator-eagle project. And could you please grant access to
>> apache
>> > id
>> > > >>> "hao"? Thanks.
>> > > >>>
>> > > >>> Michael
>> > > >>>
>> > > >>> On Thu, Dec 3, 2015 at 12:54 AM, amareshwarisr . <
>> > > amareshw...@gmail.com>
>> > > >>> wrote:
>> > > >>>
>> > > >>> > Michael,
>> > > >>> >
>> > > >>> > Have you got access to https://builds.apache.org/ ? All
>> committers
>> > > >>> would
>> > > >>> > already have access to view and start build. If you are looking
>> for
>> > > >>> access
>> > > >>> > to configure new job, please share apache ids for whom access
>> > > configure
>> > > >>> > access is required. I will try to add them.
>> > > >>> >
>> > > >>> > Thanks
>> > > >>> > Amareshwari
>> > > >>> >
>> > > >>> > On Tue, Dec 1, 2015 at 1:05 PM, Michael Wu 
>> > > wrote:
>> > > >>> >
>> > > >>> > > Hi David,
>> > > >>> > >
>> > > >>> > > Thanks for the guidance.
>> > > >>> > >
>> > > >>> > > Michael
>> > > >>> > >
>> > > >>> > > On Mon, Nov 30, 2015 at 11:37 PM, David Nalley 
>> > > >>> wrote:
>> > > >>> > >
>> > > >>> > > > - ComDev
>> > > >>> > > >
>> > > >>> > > > Please see:
>> > > >>> > > >
>> http://wiki.apache.org/general/Jenkins#How_do_I_get_an_account
>> > > >>> > > >
>> > > >>> > > >
>> > > >>> > > >
>> > > >>> > > > On Fri, Nov 27, 2015 at 1:11 AM, Michael Wu <
>> > mchl@gmail.com>
>> > > >>> > wrote:
>> > > >>> > > > > Hi Mentors,
>> > > >>> > > > >
>> > > >>> > > > > I'm a member from Apache Eagle project, and would like to
>> > > >>> subscribe
>> > > >>> > my
>> > > >>> > > > > account to have the permission to login "Jenkins
>> > > >>> > continuous-integration
>> > > >>> > > > > server" at https://builds.apache.org/ and make builds for
>> > > Eagle
>> > > >>> > > project.
>> > > >>> > > > > Could you please guide me what steps I shall go through to
>> > > >>> accomplish
>> > > >>> > > it?
>> > > >>> > > > > Thanks.
>> > > >>> > > > >
>> > > >>> > > > > BTW, with not knowing how to do, I opened a JIRA ticket for
>> > > this
>> > > >>> > > > > requirement: INFRA-10850 <
>> > > >>> > > > https://issues.apache.org/jira/browse/INFRA-10850>
>> > > >>> > > > >
>> > > >>> > > > > Michael
>> > > >>> > > >
>> > > >>> > >
>> > > >>> >
>> > > >>>
>> > > >>
>> > > >>
>> > > >
>> > >
>> >
>>

Re: December 2015 Report

[Henry Saputra]

Thanks to Julian for catching error when I setup Eagle =(

And thanks to Arun to produce the report in such short notice.

Just signed off  the report.

- Henry

On Fri, Dec 4, 2015 at 5:52 PM, Julian Hyde  wrote:
> Thank you, Arun, for putting together the report at short notice.
>
> I have signed off.
>
> I moved your report up the page, into alphabetical order. (The Eagle
> is just before the HAWQ, appropriately! Shame Falcon already
> graduated, otherwise we'd have a threesome.)
>
> I also reformatted to the 70 character line length required by the board.
>
> Don't worry about shepherds -- the mentors keep an eye on the project,
> and the shephers basically keep an eye on the mentors. :)
>
> For next month's report: I think one of the most important issues is
> producing a release. (I know you are working on a release, so you
> probably just forgot to mention it because you were writing the report
> in a hurry.) Ability to make a release (and associated IP hygiene) is
> one of the key skills required for incubation.
>
> Julian
>
>
> On Fri, Dec 4, 2015 at 5:24 PM, arunkarthick m  wrote:
>> Eagle is the last entry in that page. I don't know what's the shepherding
>> means.
>>
>> On Fri, Dec 4, 2015 at 5:06 PM, P. Taylor Goetz  wrote:
>>
>>> I don't see it here: https://wiki.apache.org/incubator/December2015
>>>
>>> Where did you post it?
>>>
>>> -Taylor
>>>
>>> > On Dec 4, 2015, at 7:22 PM, Arun Manoharan 
>>> wrote:
>>> >
>>> > Hi,
>>> >
>>> > I have added the report on Eagle with information from bugs/features and
>>> > community growth. I used HAWQ as an example.
>>> >
>>> > Actually going thru other reports i learned how to make progress and what
>>> > to focus on.
>>> >
>>> > Please let me know your comments.
>>> >
>>> > Thanks,
>>> > Arun
>>> >
>>> >> On Fri, Dec 4, 2015 at 4:04 PM, P. Taylor Goetz 
>>> wrote:
>>> >>
>>> >> And if you have trouble or need more time to put together a meaningful
>>> >> report, I thinks it's okay to slide the reporting schedule a month.
>>> >>
>>> >> I'd rather wait to see a good report than see one that is rushed and
>>> less
>>> >> than complete.
>>> >>
>>> >> -Taylor
>>> >>
>>> >>> On Dec 4, 2015, at 6:57 PM, Julian Hyde  wrote:
>>> >>>
>>> >>> Great. Sorry for the fire drill - you should have received more notice
>>> >> for this.
>>> >>>
>>> >>> Please let the mentors know when you have written the report, so we
>>> >>> can check it over and sign off. (I recommend mailing the mentors
>>> >>> directly -- i.e. on the To: list -- to get their attention for report
>>> >>> sign off, this month and other months. Of course they SHOULD be
>>> >>> reading every message on dev@eagle closely but they are busy people!)
>>> >>>
>>> >>> I have fixed the podlings.xml metadata file, so you should get timely
>>> >>> reminders for subsequent reports in Jan, Feb and May, Aug, etc.
>>> >>>
>>> >>> Julian
>>> >>>
>>> >>>
>>>  On Fri, Dec 4, 2015 at 3:14 PM, Arun Manoharan <
>>> >> arunmanoha...@apache.org> wrote:
>>>  Hi Julian,
>>> 
>>>  I will look at an example and will prepare the first monthly report.
>>> 
>>>  Thanks,
>>>  Arun
>>> 
>>> > On Fri, Dec 4, 2015 at 3:06 PM, Julian Hyde 
>>> wrote:
>>> >
>>> > If I am not mistaken Eagle should be filing its first monthly report.
>>> >> (It
>>> > should report December, January, February and then move to quarterly
>>> > reporting.)
>>> >
>>> > The report should be in
>>> https://wiki.apache.org/incubator/December2015
>>> >> .
>>> >
>>> > Usually a reminder is sent out, like the one below. There was not a
>>> > reminder this time, but that doesn’t get you off the hook! The report
>>> >> was
>>> > due on Wed Dec 2nd but I think there is still time to file.
>>> >
>>> > Can we have a volunteer to write the report?
>>> >
>>> > Marvin, Any idea why there was no reminder sent to Eagle? (It is
>>> >> entirely
>>> > possible that I set up the schedule wrong.)
>>> >
>>> > Julian
>>> >
>>> >
>>> >
>>> >> On Nov 26, 2015, at 12:40 PM, Marvin Humphrey 
>>> >> wrote:
>>> >>
>>> >>
>>> >> Greetings, {podling} developers!
>>> >>
>>> >> This is a reminder that your report is due next Wednesday, December
>>> >> 2nd.  Details below.
>>> >>
>>> >> Best,
>>> >>
>>> >> Marvin Humphrey, Report Manager for December, on behalf of the
>>> >> Incubator PMC
>>> >>
>>> >> ---
>>> >>
>>> >> 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 December 2015, 10:30 am
>>> >> PST.
>>> >> The report for your podling will form a part of the Incubator PMC
>>> >> report. The Incubator PMC requires your report to be submitted 2
>>

Re: Eagle New Release.

[Henry Saputra]

How is it master is not stable enough? Master should be stable and
contains code that should pass all tests.

Could you elaborate more about proposed dev cycle?

- Henry


On Fri, Dec 4, 2015 at 11:49 AM, Dendukuri, Hemanth  wrote:
> Hello Eagle Dev,
>
> I noticed that Master branch is not stable 
> enough for End2End functional testing.
> I see a need to create a new tag to test and 
> release the new stable eagle version, with the changes that went into it , 
> since our last release.
> Reply if anyone need time to merge their new 
> feature or have any other questions regarding this effort.
>
> Regards
> Hemanth
>

Re: Apache Eagle Scrum Board

[Henry Saputra]

Hi Eddy,

Unfortunately only member of Apache Eagle PPMCs could have Administrator role.

- Henry

On Wed, Dec 2, 2015 at 5:28 PM, CaiEddy  wrote:
> Hi Mentors:
> I'm member of Apache Eagle project, and I would like have my account granted 
> with Administrator role on Apache Eagle JIRA project so that I can create 
> sprint.  My Jira account is: wzcyc
> BTW, I have created "Apache Eagle" on board. 
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=103&view=planning.nodetail
>  and we plan to start the first sprint next week.
> RegardsEddy

Re: Eagle wiki is ready

[Henry Saputra]

Awesome news!

On Mon, Nov 23, 2015 at 6:44 PM, sul*fei  wrote:
> Thanks to Daniel's work in
> https://issues.apache.org/jira/browse/INFRA-10793
> https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-10812
>
>
> Eagle wiki is now available at 
> https://cwiki.apache.org/confluence/display/EAG/Eagle. We can start putting 
> design/discussion/faq there.
>
>
> Thanks,
> Ralph
>

Re: apply for checkin privilege for https://github.com/apache/incubator-eagle

[Henry Saputra]

The Github account is just mirror to Apache Git.

You need to use Apache git to commit to the repository instead of via Github

- Henry

On Wed, Nov 18, 2015 at 9:18 PM, Edward Zhang  wrote:
> Hello Eagle Mentors,
>
>
> We developers don’t have privilege to check in code into
> https://github.com/apache/incubator-eagle, what steps should we follow to
> get it approved.
>
>
> Thanks
>
> Edward Zhang

Re: Do all PPMCs get their Apache username created?

[Henry Saputra]

Just another clarification that private@ list is only for PPMCs.

Please only send subscribe request if you are member of Eagle PPMCs.

Thanks,

- Henry

On Tue, Nov 17, 2015 at 8:54 PM, Henry Saputra  wrote:
> Hi,
>
> This is checkpoint to make sure all PPMCs have their Apache username created?
>
> Also please subscribe to priv...@eagle.incubator.apache.org list
>
> - Henry

Re: Do all PPMCs get their Apache username created?

[Henry Saputra]

Thanks for confirming. Just added karma for svn.

Will update eagle incubator page status

On Wednesday, November 18, 2015, P. Taylor Goetz  wrote:

> I’m subscribed to dev and private as well.
>
>
> -Taylor
>
> > On Nov 18, 2015, at 12:30 AM, Henry Saputra  > wrote:
> >
> > By subscribe I meant to send email to :
> >
> >  dev-subscr...@eagle.incubator.apache.org 
> >  private-subscr...@eagle.incubator.apache.org 
> >
> > to subscribe.
> >
> > - Henry
> >
> >
> > On Tue, Nov 17, 2015 at 8:54 PM, Henry Saputra  > wrote:
> >> Hi,
> >>
> >> This is checkpoint to make sure all PPMCs have their Apache username
> created?
> >>
> >> Also please subscribe to priv...@eagle.incubator.apache.org
>  list
> >>
> >> - Henry
>
>

Re: Github and Site

[Henry Saputra]

Alright, has just submiitted the update to grant karma. Wait for few
hours to let LDAP sync and give it a spin.

- Henry

On Wed, Nov 18, 2015 at 11:05 AM, arunkarthick m  wrote:
> Hi Henry,
>
> Did you get to add the SVN karma to Edward ?
>
> We want to push our site from goeagle.io to eagle.apache.incubator.org.
>
> Thanks,
> Arun
>
> On Tue, Nov 17, 2015 at 9:34 PM, Luke Han  wrote:
>
>> Would like to suggest to go through all INFA jira tickets opened by me and
>> Henry for Kylin's one.
>> There are many infrastructure stuff should to be ready including code repo,
>> site, maven, release and so on.
>>
>>
>> Best Regards!
>> -
>>
>> Luke Han
>>
>
>
>
> --
> Arun Karthick
> 201-850-9399

Re: Do all PPMCs get their Apache username created?

[Henry Saputra]

By subscribe I meant to send email to :

  dev-subscr...@eagle.incubator.apache.org
  private-subscr...@eagle.incubator.apache.org

to subscribe.

- Henry


On Tue, Nov 17, 2015 at 8:54 PM, Henry Saputra  wrote:
> Hi,
>
> This is checkpoint to make sure all PPMCs have their Apache username created?
>
> Also please subscribe to priv...@eagle.incubator.apache.org list
>
> - Henry

Re: Github and Site

[Henry Saputra]

I may need to add svn karma to all committers

On Tue, Nov 17, 2015 at 11:45 AM, Julian Hyde  wrote:
> On Tue, Nov 17, 2015 at 11:30 AM, Zhang, Edward (GDI Hadoop)
>  wrote:
>> I tried but failed with authentication issue when I committed changes to
>> incubator/eagle/site. I think Henry is working on enabling checkout for
>> eagle committers.
>>
>> svn: E195023: Changing file
>> '/Users/yonzhang/projects/apacheeagle/eagle/site/index.html' is forbidden
>> by the server
>> svn: E175013: Access to
>> '/repos/asf/!svn/txr/1714854-11mpw/incubator/eagle/site/index.html'
>> forbidden
>
> I'm no expert on svn, but the error message is a bit surprising to me.
> I'd expect the path to be
> https://svn.apache.org/repos/asf/incubator/eagle/site/.
>
> I trust Henry will give us an update when he has one.
>
>
>> Another question is: for source code, do we use git directly or use svn?
>> Now this page is not accessible. https://github.com/apache/incubator-eagle
>
> Use git. As a committer, you should set up your repo as follows:
>
>   git clone https://git-wip-us.apache.org/repos/asf/incubator-eagle.git
>
> That will allow you to push to the definitive git repo in Apache.
> Non-committers can use
>
>   git clone https://github.com/apache/incubator-eagle.git
>
> because a read-only mirror is sufficient. However, when I try it I get
> the following:
>
>   $ git clone https://git-wip-us.apache.org/repos/asf/incubator-eagle.git 
> eagle
>   Cloning into 'eagle'...
>   warning: You appear to have cloned an empty repository.
>   Checking connectivity... done.
>
> So, someone needs to initialize the git repository by checking in a
> file. Shall I do that?
>
> Julian

Do all PPMCs get their Apache username created?

[Henry Saputra]

Hi,

This is checkpoint to make sure all PPMCs have their Apache username created?

Also please subscribe to priv...@eagle.incubator.apache.org list

- Henry

Re: Github and Site

[Henry Saputra]

I will start adding karma to Eagle committers so you could start
checking out svn and Git to add code.

Any specific question about Git?

As for the website, we are using svn pubsub, meaning everything
committed to  https://svn.apache.org/repos/asf/incubator/eagle/site
would be automatically sync and publish to show up at
eagle.incubator.apache.org.
For publishing it, we need to figure out the best way to do it. Some
projects have used Jekyll to translate static doc to HTML and publish
it to website repo.


- Henry

On Tue, Nov 17, 2015 at 7:46 AM, Arun Manoharan
 wrote:
> Hi Mentors,
>
> Can you help with the github project for Eagle ? and regarding the site if
> there is a documentation you can point us to ?
>
> svn for Eagle web site https://svn.apache.org/repos/asf/incubator/eagle and
> submitted svn pub subs request to INFRA and also add entry to
> asf-authorization-template.
>
> Thanks,
>
> Arun

[jira] [Created] (EAGLE-18) Follow up with infra about website creation

[Henry Saputra (JIRA)]

Henry Saputra created EAGLE-18:
--

 Summary: Follow up with infra about website creation
 Key: EAGLE-18
 URL: https://issues.apache.org/jira/browse/EAGLE-18
 Project: Eagle
  Issue Type: Bug
Reporter: Henry Saputra


This is Eagle side for issue filed for INFRA:

  https://issues.apache.org/jira/browse/INFRA-10747



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: About source code migration to apache site

[Henry Saputra]

It needs to be done after software grant has been filed. Which I will
be doing it now.

- Henry

On Mon, Nov 9, 2015 at 2:38 PM, Edward Zhang  wrote:
> Eagle team,
>
> anyone knows when we can migrate source code to apache source control?
> Today Eagle's code is still in https://github.com/eBay/Eagle
>
> Thanks
> Edward Zhang

Re: eagle.incubator.apache.org

[Henry Saputra]

Website need to be hosted on Apache website and following incubator
website guideline: http://incubator.apache.org/guides/sites.html

I have asked infra to set svnpubsub for Eagle website but still 404.

Will follow up with INFRA.


- Henry

On Mon, Nov 9, 2015 at 3:15 PM, Julian Hyde  wrote:
> I’m not sure that that is consistent with Apache’s branding guidelines. I may 
> be wrong, but I believe that the web site needs to be hosted on an Apache 
> domain.
>
> Also, the web site needs the standard disclaimer about Eagle’s incubation 
> status.
>
> Julian
>
>
>
>> On Nov 9, 2015, at 3:10 PM, Adunuthula, Seshu  wrote:
>>
>> Also we should get the website redirected to goeagle.io
>>
>> Regards
>> Seshu
>

[jira] [Commented] (EAGLE-9) In

[Henry Saputra (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996250#comment-14996250
 ] 

Henry Saputra commented on EAGLE-9:
---

This seemed to be created by mistake. Could you close this one?

> In
> --
>
> Key: EAGLE-9
> URL: https://issues.apache.org/jira/browse/EAGLE-9
> Project: Eagle
>  Issue Type: Bug
>Reporter: yuemeng
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [Discuss] New feature request - Whitelist

[Henry Saputra]

Hi Arun,

Please send email to dev-subscr...@eagle.incubator.apache.org to
subscribe to the dev list so I do not have to moderate your messages.

Thanks,

- Henry

On Sun, Nov 8, 2015 at 9:11 AM, Manoharan, Arun  wrote:
> Hi Folks,
>
> There is a need for a whitelist feature in Eagle.
>
> Current Feature:
> Today most of the policies are set based on “If any user access abc.dat data 
> 10 times send an alert”.
>
> UC1:
> In case of a whitelist you can say “Allow user Arun to only access particular 
> data sets like abc.data” If anything else send an alert.
>
> UC2:
> You can white list a user to say this user “Y” can access abc.dat more than 
> 10 times. This should not trigger an alert which was originally put in place 
> based on [current feature].
>
> I would like to start the discussion on this feature.
>
> Thanks,
> Arun

Re: Issues mailing list

[Henry Saputra]

We did it for Flink and Kylin. Need to file ticket against INFRA to
make it happen.

- Henry

On Wed, Nov 4, 2015 at 9:51 PM, amareshwarisr .  wrote:
> Henry,
>
> Is it possible to add such notification scheme on jira ? I'm not aware of
> such scheme. If it already exists and i don't see any issue going there.
>
> Thanks
>
> On Wed, Nov 4, 2015 at 10:45 PM, Adunuthula, Seshu 
> wrote:
>
>> Like that suggestion.
>>
>> On 11/4/15, 7:08 AM, "Henry Saputra"  wrote:
>>
>> >I think we should do mix at this early stage:
>> >-) JIRA created sent to both dev and issues
>> >-) JIRA updates sent to only issues
>> >
>> >On Wednesday, November 4, 2015, amareshwarisr . 
>> >wrote:
>> >
>> >> Hi all,
>> >>
>> >> Eagle has issues@eagle also created. Should we redirect jira updates to
>> >> issues@ instead of dev@ list ?
>> >>
>> >> Thanks
>> >> Amareshwari
>> >>
>>
>>

Re: Issues mailing list

[Henry Saputra]

I think we should do mix at this early stage:
-) JIRA created sent to both dev and issues
-) JIRA updates sent to only issues

On Wednesday, November 4, 2015, amareshwarisr . 
wrote:

> Hi all,
>
> Eagle has issues@eagle also created. Should we redirect jira updates to
> issues@ instead of dev@ list ?
>
> Thanks
> Amareshwari
>

Re: Hello Eagle

[Henry Saputra]

Got the email

On Tuesday, November 3, 2015, Hao Chen  wrote:

> Hello Eagle !
>

Re: hello eagle

[Henry Saputra]

Got it

On Tue, Nov 3, 2015 at 12:11 PM, Zhang, Edward (GDI Hadoop)
 wrote:
> Just test for dev list readiness
>