Re: Short form IP clearance

[Greg Stein]

On Wed, Oct 21, 2015 at 11:10 PM, P. Taylor Goetz  wrote:

> Apologies for potentially coming out of left field on this…
>

hehe... I did too :-)


> But I think that IP clearance is currently a difficult road to travel, and
> I worry that we are graduating podlings that don’t even know when or how to
> go down that road. It’s all too easy to merge a github pull request without
> considering IP clearance.
>
> I’ll admit that I’m unclear on the policy, and try to err on the cautious
> side.
>

I expect anybody unclear to simply ask. That happens all the time. We have
press@ to help people with questions about marketing and outreach. We have
trademarks@ for branding questions. We have legal-internal@ and
legal-discuss@ to ask questions about IP clearance (and other legal-ish
matters).

We have a system of Trust and Independence for our TLPs. The (filed) forms
are there for a TLP to follow, to check off steps, etc. There is a guide
and a description on how to fill out and file the form. And what is needed.

All good.

My concern is the injection of the IPMC into the process, and subjugating
one TLP to its will. IMO, that just is not *possible/allowed* by the
structure we have set up at the ASF. Thus, step 5 needs some modification
and 7/8 need removal to align with the actual structure of the ASF.


> I’ve seen commits to TLP projects that made me think “WTF… how did this
> evade IP clearance?”.
>
> I may be overreacting, but it seems to me IP clearance is REALLY
> important, and I worry that it may be taken for granted.
>

You say it yourself: commits come from out of the blue. Nobody
second-guesses a TLP's series of commits. Nobody second-guesses (say) the
trust network they have set up in a KEYS file for their release artifacts.
The "IP Clearance" process is already *more* controlling than other
policies that TLPs must follow.

I'm not asking to omit the process, but (IMO) the notion that the IPMC has
control over our other projects is simply incorrect, so the doc needs
updating.

Cheers,
-g

Re: Short form IP clearance

[P. Taylor Goetz]

Apologies for potentially coming out of left field on this…

But I think that IP clearance is currently a difficult road to travel, and I 
worry that we are graduating podlings that don’t even know when or how to go 
down that road. It’s all too easy to merge a github pull request without 
considering IP clearance.

I’ll admit that I’m unclear on the policy, and try to err on the cautious side.

I’ve seen commits to TLP projects that made me think “WTF… how did this evade 
IP clearance?”.

I may be overreacting, but it seems to me IP clearance is REALLY important, and 
I worry that it may be taken for granted.

-Taylor

> On Oct 21, 2015, at 10:11 PM, Greg Stein  wrote:
> 
> On Wed, Oct 21, 2015 at 8:45 PM, John D. Ament  >
> wrote:
> 
>> On Wed, Oct 21, 2015 at 9:40 PM Greg Stein  wrote:
>> 
>>> I believe a PMC is capable of performing IP clearance itself. They have a
>>> VP that is an Officer and can take responsibility for the Foundation in
>>> matters of that Project. The forms/recording are valid, so I haven't
>>> suggested changing that (tho I'd like to see them move under /legal/, I'm
>>> not fussed about their location).
>>> 
>>> I would hope that a PMC includes a note in their report to the Board,
>> that
>>> they filed a clearance form. That is just natural reporting. But that is
>>> quite different from one TLP being subject to another TLP's vote (whether
>>> lazy consensus or not).
>>> 
>>> There could certainly be an argument that a PMC needs to be
>> double-checked
>>> by $entity. But that kind of second-guessing means $entity needs to
>>> double-check all commits and all release artifacts. We trust PMCs to get
>>> their IP done correctly, as they work on their project and make releases.
>>> 
>> 
>> What you're saying makes a lot of sense.  I've always questioned the
>> benefit of TLPs submitting IP Clearances to the incubator, but not
>> questioned it because they're so few and far between it's irrelevant.
>> 
> 
> I get a bit crazy-headed when I perceive the ASF encroaches on the
> independence of a TLP. This isn't really a case of the ASF imposing, but
> similar. In my view, the Incubator cannot impede/affect the independence of
> another TLP. Structurally. The Foundation creates each PMC as an
> individual, independent group. Thus, I believe a few of these steps are
> just incorrect. I'd like our documentation to reflect the reality of the
> independence of our TLPs.
> 
> I would however pressure that podlings are not capable of completing this
>> on their own, and that they should continue to follow the processes defined
>> already.  They have knowledgeable mentors, but we should generally note
>> that the IPMC as a whole is responsible for the podlings.
>> 
> 
> Absolutely! The referenced page (and the associated guide) explicitly state
> it is for existing projects only. (the language could be clarified as "TLP,
> not podling", but yeah: definitely not for podlings)
> 
> Cheers,
> -g



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [RESULT] [VOTE] Accept Mynewt into the Apache Incubator

[Greg Stein]

Update: the mailing lists have been created, in case anybody is interested
in following along.


On Mon, Oct 19, 2015 at 12:10 PM, Sterling Hughes 
wrote:

> On Mon, Oct 12, 2015 at 9:04 AM, Sterling Hughes 
> wrote:
> > Hi All,
> >
> > As mentioned in the DISCUSS thread, all feedback has been positive on
> > the Mynewt proposal, so I'd like to call a VOTE to accept Mynewt as a
> > new ASF incubator project.
> >
> > The full text of the proposal is available on the incubator wiki at
> > the following URL:
> >
> > https://wiki.apache.org/incubator/MynewtProposal?action=recall=20
> >
> > I have also included the full text below.
> >
> > Vote is open until Thurs, 16th October 2015, 23:59:00 PST.
> >
> > [   ] +1 to accept Mynewt into the Apache Incubator
> > [   ] +0
> > [   ] -1 because...
> >
>
>
> This vote is now closed and passes with 4 binding +1 votes,
> 3 non-binding +1 votes and no 0 or -1 votes.
>
> Thanks to all who helped with the proposal and cast the vote!
>
> Here's a vote tally:
>
> Non-binding +1s:
>   Jim Jagielski
>   Marvin Humphrey
>   Bertrand Delacretaz
>
> Binding +1s:
>   P. Taylor Goetz
>   Justin Mclean
>   Greg Stein
>   Jean Baptiste Onofré
>
> No 0 or -1 votes.
>
> Thanks,
> Sterling
>
> PS: I didn't realize that I could also vote on the proposal until too
> late, but for the record, I'm also a +1 :-)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Eagle incubator proposal

[Greg Stein]

On Thu, Oct 22, 2015 at 12:09 AM, Owen O'Malley  wrote:

> On Mon, Oct 19, 2015 at 9:00 AM, Ted Dunning 
> wrote:
>
> > I would suggest that Owen O'Malley has not had enough time to be a viable
> > mentor recently and should not be on the list of mentors.
> >
>
> I have been helping Kylin out and it is graduating, so I'm down to just
> Hawq. I'd like to help Eagle out.
>

No need to be on the official list of mentors ... just help out anyways ...
heck, then you don't have to be responsible for signing off reports ;-)

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Owen O'Malley]

+1 (binding)

On Wed, Oct 21, 2015 at 6:43 PM, Luke Han  wrote:

> Just got SGA confirmation from ASF as below.
>
> Please help to double check and change your vote if necessary.
>
> Will update project status and send out vote result later.
>
> Thanks.
>
> -
>
> *This message acknowledges receipt of the following document, which has
> been filed in the Apache Software Foundation records:*
>
> *  Grant from eBay, Inc. for Kylin*
>
> *-- Craig L Russell*
>
> *Secretary, Apache Software Foundation*
>
>
> Best Regards!
> -
>
> Luke Han
>
> On Thu, Oct 22, 2015 at 9:08 AM, Naresh Agarwal  >
> wrote:
>
> > +1 (non-binding)
> >
> > Thanks
> > Naresh
> >
> > On Thu, Oct 22, 2015 at 6:35 AM, Cai, Eddy  wrote:
> >
> > > +1
> > >
> > > -Original Message-
> > > From: Chun, Chad [mailto:wac...@ebay.com]
> > > Sent: Wednesday, October 21, 2015 9:17 AM
> > > To: general@incubator.apache.org
> > > Subject: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
> > >
> > > +1
> > >
> > > Chad Chun
> > > wp_c...@hotmail.com
> > >
> > > On 10/16/15, 4:22 PM, "蒋旭"  wrote:
> > >
> > > >+1
> > > >Jiang Xu
> > > >-- 原始邮件 --
> > > >发件人: "Henry Saputra";;
> > > >发送时间: 2015年10月16日(星期五) 上午9:16
> > > >收件人: "general@incubator.apache.org";
> > > >
> > > >主题: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
> > > >
> > > >
> > > >
> > > >+1 (binding)
> > > >
> > > >On Thursday, October 15, 2015, Luke Han  wrote:
> > > >
> > > >> The Apache Kylin community and project made significant advances
> > > >>during the  incubating (from Nov 2014) and  believes it is ready to
> > > >>graduate as a top-level project.
> > > >>
> > > >> The Apache Kylin is very active. The PPMC doubled in size (added 6
> > > >>committers and 2 mentors) and
> > > >>  increased diversity in the past year. Released 3 version in the
> past
> > > >>6  months. There were presentations about Apache Kylin  at most of
> the
> > > >>big conferences of the world (including Strata+Hadoop World  London,
> > > >>Hadoop Summit San Jose,  ApacheCon EU, Big Data Technology China,
> > > >>Database Technology Conference
> > > >> China) and some meetups (Bay Area,
> > > >> Beijing and one is coming in this weekend in Shanghai), and many
> > > >>talks  around the world.
> > > >> The dev mailing list is growing very month, about 500+ topics per
> > > >>month  now.
> > > >> The community created 1000+ JIRA tickets, many patches from
> > > >>contributors/committers have been merged into code base.
> > > >>
> > > >> A vote passed unanimously on the dev@ list (27 +1 votes). Please
> find
> > > >> below references to the graduation preparation artifacts:
> > > >> * discussion on dev list [1]
> > > >> * vote thread [2]
> > > >> * podling name search [3]
> > > >> * incubation status [4]
> > > >> * proposed resolution below
> > > >>
> > > >> We believe Apache Kylin is ready to become a top-level project and
> if
> > > >>the  IPMC agree we will move to a formal vote.
> > > >> There are a few more items to be updated on the project status page
> > > >>and  others during the next couple of days.
> > > >>
> > > >>
> > > >> Many thanks to the mentors and the IPMC for the support, Luke Han
> (on
> > > >> behalf of the Apache Kylin PPMC)
> > > >>
> > > >> [1] http://s.apache.org/KylinDisGraduate
> > > >> [2] http://s.apache.org/KylinGraduateVote
> > > >> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-86
> > > >> [4] http://incubator.apache.org/projects/kylin.html
> > > >>
> > > >>
> > > >>
> > > >> Apache Kylin top-level project resolution:
> > > >> ===
> > > >>
> > > >>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, relative to distributed and scalable OLAP engine
> > > >>
> > > >>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > >>Committee (PMC), to be known as the "Apache Kylin Project",
> > > >>be and hereby is established pursuant to Bylaws of the
> > > >>Foundation; and be it further
> > > >>
> > > >>RESOLVED, that the Apache Kylin Project be and hereby is
> > > >>responsible for the creation and maintenance of open-source
> > > >>software related to distributed and scalable OLAP engine;
> > > >>and be it further
> > > >>
> > > >>RESOLVED, that the office of "Vice President, Kylin" be and
> > > >>hereby is created, the person holding such office to serve at
> > > >>the direction of the Board 

Re: [DISCUSS] Eagle incubator proposal

[Henry Saputra]

HI Marvin,

You are preaching to the choir with me =)
Totally agree with your comment.

The Eagle team have met with proposed mentors before and have
presented and ask for availability and willingness to help mentor the
project and we got positive response from them.
Now, if the question is whether these mentors will or will not active
in reality it would hard for me to answer.

I know Julian and Taylor have been active and helpful in the Kylin
incubating life.

To be fair, I will circle one more time to existing mentors for Eagle
to confirm their commitment for active participation in the podling.
Would that be acceptable solution?

- Henry

On Wed, Oct 21, 2015 at 9:24 AM, Marvin Humphrey  wrote:
> On Tue, Oct 20, 2015 at 9:16 PM, Henry Saputra  
> wrote:
>> Hi Ted,
>>
>> Thanks for your concern, but we have had discussions with all proposed
>> mentors before to ask for their availability and willingness to
>> actively mentor this project.
>>
>> I think we are good with existing proposed mentors.
>
> Henry,
>
> 4 of the 5 proposed Mentors for Eagle are also Mentors for Kylin.  Kylin's 1.1
> release candidate is still twisting in the wind awaiting IPMC votes.  It was
> was offered up on dev@kylin on October 10th -- 11 days ago.  It got one Mentor
> vote immediately, and another after 9 days.  It is still waiting for a third
> IPMC vote.
>
> I think the IPMC needs to take into consideration whether Eagle will have
> enough active Mentors when voting on this proposal, since at least some of
> the proposed Mentors seem to be having difficulty with their current load.
>
> Mentors who do not actually participate should not be Mentors.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Eagle incubator proposal

[Siddharth Wagle]

Hi Arun,

This proposal looks great. I would like to be an active contributor on this 
project. I bring with me the experience of Apache Ambari and developing the 
Ambari Metrics System.

Best Regards,
Sid

From: Julian Hyde 
Sent: Wednesday, October 21, 2015 9:10 AM
To: general@incubator.apache.org
Subject: Re: [DISCUSS] Eagle incubator proposal

My name is already on the list of mentors. I think this project fills an 
important need. Several of the initial committers were involved with Kylin and 
therefore know the Apache process.

Julian


> On Oct 20, 2015, at 11:58 AM, P. Taylor Goetz  wrote:
>
> I should also have some improved bandwidth both now that Kylin is nearing 
> graduation and for other reasons. I’ve been bogged down recently, but that’s 
> starting to change.
>
> If more mentors are desired, I’d be willing to help in that respect.
>
> -Taylor
>
>> On Oct 20, 2015, at 11:49 AM, Henry Saputra  wrote:
>>
>> Hi Ted,
>>
>> Since Kylin almost ready to graduate, I have more bandwidth to help with 
>> Eagle.
>>
>> But, you are right that current proposed mentors for Eagle seemed to
>> be very busy with other podlings, so 1 or 2 additional mentors would
>> be great.
>>
>> The good news is that the team consist some people from Kylin, for
>> example Luke, which done great job helping Kylin to understand working
>> with Apache way.
>> So we have some help from initial committers who have done the rodeo before.
>>
>> - Henry
>>
>> On Mon, Oct 19, 2015 at 9:00 AM, Ted Dunning  wrote:
>>> I would suggest that Owen O'Malley has not had enough time to be a viable
>>> mentor recently and should not be on the list of mentors.
>>>
>>> Henry and Julian are good if their schedules permit.  Henry, I know has
>>> been mentoring a number of projects lately.
>>>
>>>
>>>
>>> On Mon, Oct 19, 2015 at 8:40 AM, Jean-Baptiste Onofré 
>>> wrote:
>>>
 Hi Arun,

 very interesting proposal. I may see some possible interaction with
 Falcon. In Falcon, we have HDFS files (and Hive/HBase) monitoring (with a
 kind of Change Data Capture), etc.

 So, I see a different perspective in Eagle, but Eagle could also leverage
 Falcon somehow.

 Regards
 JB


 On 10/19/2015 05:33 PM, Manoharan, Arun wrote:

> Hello Everyone,
>
> My name is Arun Manoharan. Currently a product manager in the Analytics
> platform team at eBay Inc.
>
> I would like to start a discussion on Eagle and its joining the ASF as an
> incubation project.
>
> 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 supports a wide variety of policies on HDFS data and 
> Hive.
> Eagle also provides machine learning models for detecting anomalous user
> behavior in Hadoop.
>
> The proposal is available on the wiki here:
> https://wiki.apache.org/incubator/EagleProposal
>
> The text of the proposal is also available at the end of this email.
>
> Thanks for your time and help.
>
> Thanks,
> Arun
>
> 
>
> Eagle
>
> Abstract
> Eagle is an Open Source Monitoring solution for Hadoop to instantly
> identify access to sensitive data, recognize attacks, malicious activities
> in hadoop and take actions.
>
> Proposal
> Eagle audits access to HDFS files, Hive and HBase tables in real time,
> enforces policies defined on sensitive data access and alerts or blocks
> user’s access to that sensitive data in real time. Eagle also creates user
> profiles based on the typical access behaviour for HDFS and Hive and sends
> alerts when anomalous behaviour is detected. Eagle can also import
> sensitive data information classified by external classification engines 
> to
> help define its policies.
>
> Overview of Eagle
> Eagle has 3 main parts.
> 1.Data collection and storage - Eagle collects data from various hadoop
> logs in real time using Kafka/Yarn API and uses HDFS and HBase for 
> storage.
> 2.Data processing and policy engine - Eagle allows users to create
> policies based on various metadata properties on HDFS, Hive and HBase 
> data.
> 3.Eagle services - Eagle services include policy manager, query service
> and the visualization component. Eagle provides intuitive user interface 
> to
> administer Eagle and an alert dashboard to respond to real time alerts.
>
> Data Collection and Storage:
> Eagle provides programming API for extending Eagle to integrate any data
> source into Eagle policy evaluation framework. For example, Eagle hdfs
> audit monitoring collects data from Kafka which is populated from namenode
> 

Re: [DISCUSS] Eagle incubator proposal

[Manoharan, Arun]

Hi Sid,

Thanks for your support.

Actually we have developed an Ambari plugin for Eagle where someone could
use Ambari to deploy Eagle. We have this working on the sandbox. Would
like to have you as a contributor. I will reach out to you.

Thanks,
Arun

On 10/21/15, 9:22 AM, "Siddharth Wagle"  wrote:

>Hi Arun,
>
>This proposal looks great. I would like to be an active contributor on
>this project. I bring with me the experience of Apache Ambari and
>developing the Ambari Metrics System.
>
>Best Regards,
>Sid
>
>From: Julian Hyde 
>Sent: Wednesday, October 21, 2015 9:10 AM
>To: general@incubator.apache.org
>Subject: Re: [DISCUSS] Eagle incubator proposal
>
>My name is already on the list of mentors. I think this project fills an
>important need. Several of the initial committers were involved with
>Kylin and therefore know the Apache process.
>
>Julian
>
>
>> On Oct 20, 2015, at 11:58 AM, P. Taylor Goetz  wrote:
>>
>> I should also have some improved bandwidth both now that Kylin is
>>nearing graduation and for other reasons. I¹ve been bogged down
>>recently, but that¹s starting to change.
>>
>> If more mentors are desired, I¹d be willing to help in that respect.
>>
>> -Taylor
>>
>>> On Oct 20, 2015, at 11:49 AM, Henry Saputra 
>>>wrote:
>>>
>>> Hi Ted,
>>>
>>> Since Kylin almost ready to graduate, I have more bandwidth to help
>>>with Eagle.
>>>
>>> But, you are right that current proposed mentors for Eagle seemed to
>>> be very busy with other podlings, so 1 or 2 additional mentors would
>>> be great.
>>>
>>> The good news is that the team consist some people from Kylin, for
>>> example Luke, which done great job helping Kylin to understand working
>>> with Apache way.
>>> So we have some help from initial committers who have done the rodeo
>>>before.
>>>
>>> - Henry
>>>
>>> On Mon, Oct 19, 2015 at 9:00 AM, Ted Dunning 
>>>wrote:
 I would suggest that Owen O'Malley has not had enough time to be a
viable
 mentor recently and should not be on the list of mentors.

 Henry and Julian are good if their schedules permit.  Henry, I know
has
 been mentoring a number of projects lately.



 On Mon, Oct 19, 2015 at 8:40 AM, Jean-Baptiste Onofré

 wrote:

> Hi Arun,
>
> very interesting proposal. I may see some possible interaction with
> Falcon. In Falcon, we have HDFS files (and Hive/HBase) monitoring
>(with a
> kind of Change Data Capture), etc.
>
> So, I see a different perspective in Eagle, but Eagle could also
>leverage
> Falcon somehow.
>
> Regards
> JB
>
>
> On 10/19/2015 05:33 PM, Manoharan, Arun wrote:
>
>> Hello Everyone,
>>
>> My name is Arun Manoharan. Currently a product manager in the
>>Analytics
>> platform team at eBay Inc.
>>
>> I would like to start a discussion on Eagle and its joining the ASF
>>as an
>> incubation project.
>>
>> 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 supports a wide variety of policies on HDFS data
>>and Hive.
>> Eagle also provides machine learning models for detecting anomalous
>>user
>> behavior in Hadoop.
>>
>> The proposal is available on the wiki here:
>> https://wiki.apache.org/incubator/EagleProposal
>>
>> The text of the proposal is also available at the end of this email.
>>
>> Thanks for your time and help.
>>
>> Thanks,
>> Arun
>>
>> 
>>
>> Eagle
>>
>> Abstract
>> Eagle is an Open Source Monitoring solution for Hadoop to instantly
>> identify access to sensitive data, recognize attacks, malicious
>>activities
>> in hadoop and take actions.
>>
>> Proposal
>> Eagle audits access to HDFS files, Hive and HBase tables in real
>>time,
>> enforces policies defined on sensitive data access and alerts or
>>blocks
>> user¹s access to that sensitive data in real time. Eagle also
>>creates user
>> profiles based on the typical access behaviour for HDFS and Hive
>>and sends
>> alerts when anomalous behaviour is detected. Eagle can also import
>> sensitive data information classified by external classification
>>engines to
>> help define its policies.
>>
>> Overview of Eagle
>> Eagle has 3 main parts.
>> 1.Data collection and storage - Eagle collects data from various
>>hadoop
>> logs in real time using Kafka/Yarn API and uses HDFS and HBase for
>>storage.
>> 2.Data processing and policy engine - Eagle allows users to create
>> policies based on various metadata properties on HDFS, Hive and
>>HBase data.

Re: [DISCUSS] Eagle incubator proposal

[Julian Hyde]

My name is already on the list of mentors. I think this project fills an 
important need. Several of the initial committers were involved with Kylin and 
therefore know the Apache process.

Julian
 

> On Oct 20, 2015, at 11:58 AM, P. Taylor Goetz  wrote:
> 
> I should also have some improved bandwidth both now that Kylin is nearing 
> graduation and for other reasons. I’ve been bogged down recently, but that’s 
> starting to change.
> 
> If more mentors are desired, I’d be willing to help in that respect.
> 
> -Taylor
> 
>> On Oct 20, 2015, at 11:49 AM, Henry Saputra  wrote:
>> 
>> Hi Ted,
>> 
>> Since Kylin almost ready to graduate, I have more bandwidth to help with 
>> Eagle.
>> 
>> But, you are right that current proposed mentors for Eagle seemed to
>> be very busy with other podlings, so 1 or 2 additional mentors would
>> be great.
>> 
>> The good news is that the team consist some people from Kylin, for
>> example Luke, which done great job helping Kylin to understand working
>> with Apache way.
>> So we have some help from initial committers who have done the rodeo before.
>> 
>> - Henry
>> 
>> On Mon, Oct 19, 2015 at 9:00 AM, Ted Dunning  wrote:
>>> I would suggest that Owen O'Malley has not had enough time to be a viable
>>> mentor recently and should not be on the list of mentors.
>>> 
>>> Henry and Julian are good if their schedules permit.  Henry, I know has
>>> been mentoring a number of projects lately.
>>> 
>>> 
>>> 
>>> On Mon, Oct 19, 2015 at 8:40 AM, Jean-Baptiste Onofré 
>>> wrote:
>>> 
 Hi Arun,
 
 very interesting proposal. I may see some possible interaction with
 Falcon. In Falcon, we have HDFS files (and Hive/HBase) monitoring (with a
 kind of Change Data Capture), etc.
 
 So, I see a different perspective in Eagle, but Eagle could also leverage
 Falcon somehow.
 
 Regards
 JB
 
 
 On 10/19/2015 05:33 PM, Manoharan, Arun wrote:
 
> Hello Everyone,
> 
> My name is Arun Manoharan. Currently a product manager in the Analytics
> platform team at eBay Inc.
> 
> I would like to start a discussion on Eagle and its joining the ASF as an
> incubation project.
> 
> 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 supports a wide variety of policies on HDFS data and 
> Hive.
> Eagle also provides machine learning models for detecting anomalous user
> behavior in Hadoop.
> 
> The proposal is available on the wiki here:
> https://wiki.apache.org/incubator/EagleProposal
> 
> The text of the proposal is also available at the end of this email.
> 
> Thanks for your time and help.
> 
> Thanks,
> Arun
> 
> 
> 
> Eagle
> 
> Abstract
> Eagle is an Open Source Monitoring solution for Hadoop to instantly
> identify access to sensitive data, recognize attacks, malicious activities
> in hadoop and take actions.
> 
> Proposal
> Eagle audits access to HDFS files, Hive and HBase tables in real time,
> enforces policies defined on sensitive data access and alerts or blocks
> user’s access to that sensitive data in real time. Eagle also creates user
> profiles based on the typical access behaviour for HDFS and Hive and sends
> alerts when anomalous behaviour is detected. Eagle can also import
> sensitive data information classified by external classification engines 
> to
> help define its policies.
> 
> Overview of Eagle
> Eagle has 3 main parts.
> 1.Data collection and storage - Eagle collects data from various hadoop
> logs in real time using Kafka/Yarn API and uses HDFS and HBase for 
> storage.
> 2.Data processing and policy engine - Eagle allows users to create
> policies based on various metadata properties on HDFS, Hive and HBase 
> data.
> 3.Eagle services - Eagle services include policy manager, query service
> and the visualization component. Eagle provides intuitive user interface 
> to
> administer Eagle and an alert dashboard to respond to real time alerts.
> 
> Data Collection and Storage:
> Eagle provides programming API for extending Eagle to integrate any data
> source into Eagle policy evaluation framework. For example, Eagle hdfs
> audit monitoring collects data from Kafka which is populated from namenode
> log4j appender or from logstash agent. Eagle hive monitoring collects hive
> query logs from running job through YARN API, which is designed to be
> scalable and fault-tolerant. Eagle uses HBase as storage for storing
> metadata and metrics data, and also supports relational database through
> configuration change.
> 
> Data Processing and Policy 

Re: [DISCUSS] Eagle incubator proposal

[Marvin Humphrey]

On Tue, Oct 20, 2015 at 9:16 PM, Henry Saputra  wrote:
> Hi Ted,
>
> Thanks for your concern, but we have had discussions with all proposed
> mentors before to ask for their availability and willingness to
> actively mentor this project.
>
> I think we are good with existing proposed mentors.

Henry,

4 of the 5 proposed Mentors for Eagle are also Mentors for Kylin.  Kylin's 1.1
release candidate is still twisting in the wind awaiting IPMC votes.  It was
was offered up on dev@kylin on October 10th -- 11 days ago.  It got one Mentor
vote immediately, and another after 9 days.  It is still waiting for a third
IPMC vote.

I think the IPMC needs to take into consideration whether Eagle will have
enough active Mentors when voting on this proposal, since at least some of
the proposed Mentors seem to be having difficulty with their current load.

Mentors who do not actually participate should not be Mentors.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Eagle incubator proposal

[Manoharan, Arun]

Thanks Don. Looking forward to work with the Ranger team for meaningful
integrations.

On 10/20/15, 10:19 PM, "Don Bosco Durai"  wrote:

>Hi Arun
>
>This looks really good and fills some obvious gaps in the security
>landscape.
>
>Happy to contribute anyway you want.
>
>All the best!!!
>
>Bosco
>
>
>
>
>
>On 10/20/15, 8:02 AM, "Alex Karasulu" akaras...@apache.org> wrote:
>
>>Hi Arun,
>>
>>Eagle sounds very promising. I just had a discussion with someone about
>>this exact need. I do however agree with Greg on the name. As far as I
>>can
>>see, besides the name, your weakest point is the all eBay employed team.
>>It's not a blocker and can be fixed during incubation. Good luck to you.
>>
>>Alex
>>
>>
>>On Tue, Oct 20, 2015 at 5:51 PM, Manoharan, Arun 
>>wrote:
>>
>>> Hi Greg,
>>>
>>> Thank you for reviewing the proposal.
>>>
>>> Originally we thought Eagle might be trademarked by someone already
>>>but I
>>> went thru eBay legal team to get the clearance for the name to be
>>>used. We
>>> will look into it again to see if there will be potential problems.
>>>
>>> Thanks,
>>> Arun
>>>
>>> On 10/20/15, 1:52 AM, "Greg Stein"  wrote:
>>>
>>> >Hey there, Arun! ... I have no commentary on the proposal itself, as
>>>it
>>> >looks like a great proposal. I would suggest being a bit wary of the
>>>name,
>>> >as "Eagle" is a *very* popular PCB design program.
>>> >
>>> >On Mon, Oct 19, 2015 at 10:33 AM, Manoharan, Arun
>>>
>>> >wrote:
>>> >
>>> >> Hello Everyone,
>>> >>
>>> >> My name is Arun Manoharan. Currently a product manager in the
>>>Analytics
>>> >> platform team at eBay Inc.
>>> >>
>>> >> I would like to start a discussion on Eagle and its joining the ASF
>>>as
>>> >>an
>>> >> incubation project.
>>> >>
>>> >> 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 supports a wide variety of policies on HDFS data
>>>and
>>> >>Hive.
>>> >> Eagle also provides machine learning models for detecting anomalous
>>>user
>>> >> behavior in Hadoop.
>>> >>
>>> >> The proposal is available on the wiki here:
>>> >> https://wiki.apache.org/incubator/EagleProposal
>>> >>
>>> >> The text of the proposal is also available at the end of this email.
>>> >>
>>> >> Thanks for your time and help.
>>> >>
>>> >> Thanks,
>>> >> Arun
>>> >>
>>> >> 
>>> >>
>>> >> Eagle
>>> >>
>>> >> Abstract
>>> >> Eagle is an Open Source Monitoring solution for Hadoop to instantly
>>> >> identify access to sensitive data, recognize attacks, malicious
>>> >>activities
>>> >> in hadoop and take actions.
>>> >>
>>> >> Proposal
>>> >> Eagle audits access to HDFS files, Hive and HBase tables in real
>>>time,
>>> >> enforces policies defined on sensitive data access and alerts or
>>>blocks
>>> >> user¹s access to that sensitive data in real time. Eagle also
>>>creates
>>> >>user
>>> >> profiles based on the typical access behaviour for HDFS and Hive and
>>> >>sends
>>> >> alerts when anomalous behaviour is detected. Eagle can also import
>>> >> sensitive data information classified by external classification
>>> >>engines to
>>> >> help define its policies.
>>> >>
>>> >> Overview of Eagle
>>> >> Eagle has 3 main parts.
>>> >> 1.Data collection and storage - Eagle collects data from various
>>>hadoop
>>> >> logs in real time using Kafka/Yarn API and uses HDFS and HBase for
>>> >>storage.
>>> >> 2.Data processing and policy engine - Eagle allows users to create
>>> >> policies based on various metadata properties on HDFS, Hive and
>>>HBase
>>> >>data.
>>> >> 3.Eagle services - Eagle services include policy manager, query
>>>service
>>> >> and the visualization component. Eagle provides intuitive user
>>> >>interface to
>>> >> administer Eagle and an alert dashboard to respond to real time
>>>alerts.
>>> >>
>>> >> Data Collection and Storage:
>>> >> Eagle provides programming API for extending Eagle to integrate any
>>>data
>>> >> source into Eagle policy evaluation framework. For example, Eagle
>>>hdfs
>>> >> audit monitoring collects data from Kafka which is populated from
>>> >>namenode
>>> >> log4j appender or from logstash agent. Eagle hive monitoring
>>>collects
>>> >>hive
>>> >> query logs from running job through YARN API, which is designed to
>>>be
>>> >> scalable and fault-tolerant. Eagle uses HBase as storage for storing
>>> >> metadata and metrics data, and also supports relational database
>>>through
>>> >> configuration change.
>>> >>
>>> >> Data Processing and Policy Engine:
>>> >> Processing Engine: Eagle provides stream processing API which is an
>>> >> abstraction of Apache Storm. It can also be extended to other
>>>streaming
>>> >> engines. This abstraction allows developers to assemble data
>>> >> transformation, filtering, external data join etc. without
>>>physically
>>> >>bound
>>> >> 

Re: [DISCUSS] Eagle incubator proposal

[Greg Stein]

On Wed, Oct 21, 2015 at 11:53 AM, Henry Saputra 
wrote:
>...

> To be fair, I will circle one more time to existing mentors for Eagle
> to confirm their commitment for active participation in the podling.
> Would that be acceptable solution?
>

Acceptable to whom? I bet you there are enough people who find the list of
mentors to be acceptable, despite Marvin's emails otherwise... :-)

To put it another way: it is unfair to pre-judge people. Even more,
*accepting* a podling should not be subject to a preapproved list of
mentors, since we have juggled mentors many times in the past. *Should* a
mentor be absent in the *future*, then they can be replaced. ... but I
believe it is better to be reactive, than to pre-judge.

Cheers,
-g

Re: [DISCUSS] Eagle incubator proposal

[Owen O'Malley]

On Mon, Oct 19, 2015 at 9:00 AM, Ted Dunning  wrote:

> I would suggest that Owen O'Malley has not had enough time to be a viable
> mentor recently and should not be on the list of mentors.
>

I have been helping Kylin out and it is graduating, so I'm down to just
Hawq. I'd like to help Eagle out.

.. Owen


> Henry and Julian are good if their schedules permit.  Henry, I know has
> been mentoring a number of projects lately.
>
>
>
> On Mon, Oct 19, 2015 at 8:40 AM, Jean-Baptiste Onofré 
> wrote:
>
> > Hi Arun,
> >
> > very interesting proposal. I may see some possible interaction with
> > Falcon. In Falcon, we have HDFS files (and Hive/HBase) monitoring (with a
> > kind of Change Data Capture), etc.
> >
> > So, I see a different perspective in Eagle, but Eagle could also leverage
> > Falcon somehow.
> >
> > Regards
> > JB
> >
> >
> > On 10/19/2015 05:33 PM, Manoharan, Arun wrote:
> >
> >> Hello Everyone,
> >>
> >> My name is Arun Manoharan. Currently a product manager in the Analytics
> >> platform team at eBay Inc.
> >>
> >> I would like to start a discussion on Eagle and its joining the ASF as
> an
> >> incubation project.
> >>
> >> 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 supports a wide variety of policies on HDFS data and
> Hive.
> >> Eagle also provides machine learning models for detecting anomalous user
> >> behavior in Hadoop.
> >>
> >> The proposal is available on the wiki here:
> >> https://wiki.apache.org/incubator/EagleProposal
> >>
> >> The text of the proposal is also available at the end of this email.
> >>
> >> Thanks for your time and help.
> >>
> >> Thanks,
> >> Arun
> >>
> >> 
> >>
> >> Eagle
> >>
> >> Abstract
> >> Eagle is an Open Source Monitoring solution for Hadoop to instantly
> >> identify access to sensitive data, recognize attacks, malicious
> activities
> >> in hadoop and take actions.
> >>
> >> Proposal
> >> Eagle audits access to HDFS files, Hive and HBase tables in real time,
> >> enforces policies defined on sensitive data access and alerts or blocks
> >> user’s access to that sensitive data in real time. Eagle also creates
> user
> >> profiles based on the typical access behaviour for HDFS and Hive and
> sends
> >> alerts when anomalous behaviour is detected. Eagle can also import
> >> sensitive data information classified by external classification
> engines to
> >> help define its policies.
> >>
> >> Overview of Eagle
> >> Eagle has 3 main parts.
> >> 1.Data collection and storage - Eagle collects data from various hadoop
> >> logs in real time using Kafka/Yarn API and uses HDFS and HBase for
> storage.
> >> 2.Data processing and policy engine - Eagle allows users to create
> >> policies based on various metadata properties on HDFS, Hive and HBase
> data.
> >> 3.Eagle services - Eagle services include policy manager, query service
> >> and the visualization component. Eagle provides intuitive user
> interface to
> >> administer Eagle and an alert dashboard to respond to real time alerts.
> >>
> >> Data Collection and Storage:
> >> Eagle provides programming API for extending Eagle to integrate any data
> >> source into Eagle policy evaluation framework. For example, Eagle hdfs
> >> audit monitoring collects data from Kafka which is populated from
> namenode
> >> log4j appender or from logstash agent. Eagle hive monitoring collects
> hive
> >> query logs from running job through YARN API, which is designed to be
> >> scalable and fault-tolerant. Eagle uses HBase as storage for storing
> >> metadata and metrics data, and also supports relational database through
> >> configuration change.
> >>
> >> Data Processing and Policy Engine:
> >> Processing Engine: Eagle provides stream processing API which is an
> >> abstraction of Apache Storm. It can also be extended to other streaming
> >> engines. This abstraction allows developers to assemble data
> >> transformation, filtering, external data join etc. without physically
> bound
> >> to a specific streaming platform. Eagle streaming API allows developers
> to
> >> easily integrate business logic with Eagle policy engine and internally
> >> Eagle framework compiles business logic execution DAG into program
> >> primitives of underlying stream infrastructure e.g. Apache Storm. For
> >> example, Eagle HDFS monitoring transforms audit log from Namenode to
> object
> >> and joins sensitivity metadata, security zone metadata which are
> generated
> >> from external programs or configured by user. Eagle hive monitoring
> filters
> >> running jobs to get hive query string and parses query string into
> object
> >> and then joins sensitivity metadata.
> >> Alerting Framework: Eagle Alert Framework includes stream metadata API,
> >> scalable policy engine framework, extensible policy engine framework.
> >> Stream metadata API allows developers to declare 

Re: [DISCUSS] Eagle incubator proposal

[Henry Saputra]

I think the concern was just kind of a spill-over from other
discussions about rebooting the Incubator so new proposal kind of
being scrutinized more.
Which is OK for me, that is why we have DISCUSS thread right now :)

To just follow up, the concerns that have been raised, the Eagle team
is happy with existing mentors and would like to move forward with
them.
I have strong faith in my fellow IPMCs as mentors for this project to
help the project go through the incubation process.

- Henry

On Wed, Oct 21, 2015 at 12:02 PM, Greg Stein  wrote:
> On Wed, Oct 21, 2015 at 11:53 AM, Henry Saputra 
> wrote:
>>...
>
>> To be fair, I will circle one more time to existing mentors for Eagle
>> to confirm their commitment for active participation in the podling.
>> Would that be acceptable solution?
>>
>
> Acceptable to whom? I bet you there are enough people who find the list of
> mentors to be acceptable, despite Marvin's emails otherwise... :-)
>
> To put it another way: it is unfair to pre-judge people. Even more,
> *accepting* a podling should not be subject to a preapproved list of
> mentors, since we have juggled mentors many times in the past. *Should* a
> mentor be absent in the *future*, then they can be replaced. ... but I
> believe it is better to be reactive, than to pre-judge.
>
> Cheers,
> -g

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Short form IP clearance

[Greg Stein]

Hey all,

On the following page:
  http://incubator.apache.org/ip-clearance/ip-clearance-template.html

The process steps do not align with the intent described in the Preamble,
and some steps are not required. Specifically, steps 5, 7, and 8.

Step 5: the code will be imported *somewhere*; there is no reason for it to
be duplicated into the Incubator repository. The ASF simply requires
paperwork to acknowledge the propriety of that import, wherever it may be.
There isn't even a reason for a checksum.

Step 7: the Incubator has no prerogative over what the VP of an Apache
project does (or other Officers, for that matter). If a TLP wants some
code, then they can do so. And the representative of that TLP (the VP, an
Officer) is the one taking responsibility for their actions. The Incubator
has been a recording area, but that doesn't give it discretion over other
projects.
[ IMO, the recording should go somewhere identified by VP Legal Affairs,
and be entirely disconnected from the Incubator ]

Step 8: moot, once (7) is removed.

I'd like to modify the steps to reflect the above points.

Thoughts?

Cheers,
-g

Re: [VOTE] Release Apache Kylin 1.1-incubating (rc1)

[P. Taylor Goetz]

+1 (binding)

Checked sigs license headers, NOTICE, LICENSE, etc. All look good.

-Taylor 



> On Oct 14, 2015, at 9:42 PM, ShaoFeng Shi  wrote:
> 
> Hi all,
> 
> The Apache Kylin community has voted on and approved a proposal to release
> Apache Kylin 1.1-incubating.
> 
> Proposal:http://s.apache.org/Jzu
> 
> Vote result:
> 7 binding +1 votes
> 6 non-binding +1 votes
> No -1 voteshttp://s.apache.org/kylin-1.1-result_rc1
> 
> 
> The commit to be voted
> upon:https://github.com/apache/incubator-kylin/commit/1955a2f9aea7b7f608f0496c00807715ea4246a5
> 
> Its hash is 1955a2f9aea7b7f608f0496c00807715ea4246a5.
> 
> The artifacts to be voted on are located
> here:https://dist.apache.org/repos/dist/dev/incubator/kylin/apache-kylin-1.1-incubating-rc1/
> 
> The hashes of the artifacts are as follows:
> apache-kylin-1.1-incubating-src.tar.gz.md5 18dfbb012e1eb807b1a5c1b134a537aa
> apache-kylin-1.1-incubating-src.tar.gz.sha1
> 041ee010c67a0b5611d9dd06f7fd6f37388c5374
> 
> A staged Maven repository is available for review
> at:https://repository.apache.org/content/repositories/orgapachekylin-1012/
> 
> Release artifacts are signed with the following
> key:https://people.apache.org/keys/committer/shaofengshi.asc
> 
> Pursuant to the Releases section of the Incubation Policy and with
> the endorsement of our mentors we would now like to request
> the permission of the Incubator PMC to publish the release. The vote
> is open for 72 hours, or until the necessary number of votes (3 +1)
> is reached.
> 
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
> 
> 
> Shaofeng Shi, on behalf of Apache Kylin ppmcshaofeng...@apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Short form IP clearance

[Sam Ruby]

On Wed, Oct 21, 2015 at 3:22 PM, Greg Stein  wrote:
> Hey all,
>
> On the following page:
>   http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> The process steps do not align with the intent described in the Preamble,
> and some steps are not required. Specifically, steps 5, 7, and 8.
>
> Step 5: the code will be imported *somewhere*; there is no reason for it to
> be duplicated into the Incubator repository. The ASF simply requires
> paperwork to acknowledge the propriety of that import, wherever it may be.
> There isn't even a reason for a checksum.
>
> Step 7: the Incubator has no prerogative over what the VP of an Apache
> project does (or other Officers, for that matter). If a TLP wants some
> code, then they can do so. And the representative of that TLP (the VP, an
> Officer) is the one taking responsibility for their actions. The Incubator
> has been a recording area, but that doesn't give it discretion over other
> projects.
> [ IMO, the recording should go somewhere identified by VP Legal Affairs,
> and be entirely disconnected from the Incubator ]

Just some historical perspective (from the previous VP Legal Affairs,
though this predates my having that role), IP clearance is something
that is rarely done on a PMC level so it is something that most
individual PMCs don't have much experience with; at a foundation level
it is done frequently and primarily by the incubator.  Hence the VP of
Legal Affairs (my predecessor and then unchanged by myself) designated
that the Incubator have this role.

> Step 8: moot, once (7) is removed.
>
> I'd like to modify the steps to reflect the above points.
>
> Thoughts?

As far as I can tell, it has been working without issue, where lazy
consensus is key to making it work smoothly.  So I'm -1 on fixing
something that isn't broke.

Of course, as you say, the current VP of Legal Affairs could decide
that to change any of this; but I personally would see that at
variance with statements like "I have no desire to diminish the trust
we provide."

> Cheers,
> -g

- Sam Ruby

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Kylin 1.1-incubating (rc1)

[Justin Mclean]

Hi,

It’s +0 (binding) from me.

I checked:
- release name includes incubating
- signatures and hashes correct
- DISCLAIMER exists
- LICENSE is OK, but probably missing font license
- NOTICE all good
- All source files have apache headers (a few test files and data files don’t)
- A couple of unexpected binary files in release
- Can compile from source

There are two binary font files, whose licensing I’m unsure of in the source 
package:
./webapp/app/fonts/ODelI1aHBYDBqgeIAH2zlPytCVloACqnDHJwh-em2k8.woff2
(may be Source San Pro which is covered by a SIL license so that would also 
need to go into
the LICENSE file or be removed)
./webapp/app/fonts/toadOcfmlt9b38dHJxOBGKUt5Ot5NIMarvNW-hkYWvT3rGVtsTkPsbDajuO5ueQw.woff2
(may be Source Sans Pro Bold?)

This issue was brought up before [1] in a previous release.

Thanks,
Justin

1.http://mail-archives.apache.org/mod_mbox/incubator-general/201505.mbox/%3c09e70cf6-7d79-4bff-9e05-58f9c0897...@classsoftware.com%3E
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Short form IP clearance

[John D. Ament]

Greg,

If I'm reading your email correctly, you're just saying that the Incubator
is not responsible for processing IP Clearances in a lazy way.  Projects
should instead direct their IP clearance emails to <>.

That <> is TBD.

John

On Wed, Oct 21, 2015 at 9:17 PM Greg Stein  wrote:

> [trimmed response right now; in favor of getting a couple other voices]
>
> On Wed, Oct 21, 2015 at 7:01 PM, Sam Ruby  wrote:
> >...
>
> > What is this, randomly propose changes to the incubator month?
> >
>
> Has nothing to do with the Incubator, but with how a PMC records its IP
> clearance. And more importantly, to clarify that a PMC is not beholden to
> the IPMC.
>
>
> > Let me repeat what I just said.  I don't believe I was being obtuse,
> > but then again, you don't appear to have read what I wrote.
> >
>
> I certainly read it, you weren't being obtuse :-)
>
>
> > 1) I hope we can agree that an Officer of the corporation should be
> > subject to the direction of the Legal Affairs committee.
> >
>
> Agreed.
>
> >...
>
> > > My point is to make the document reflect the reality of our
> organization.
> >
> > Reality is what is reflected on this page:
> > http://incubator.apache.org/ip-clearance/
> >
> > Click on any of the clearance documents.
> >
> > I don't know what you are smoking, but those documents are real.
> >
>
> Of course. I didn't say "get rid of IP clearance". Please read my original
> email, if you think otherwise. I just want to alter the published steps to
> reflect that our TLPs are not beholden to the IPMC. We use the Incubator as
> a location to record these things (which I find odd, but is a separate
> discussion).
>
> >...
>
> Cheers,
> -g
>

Re: Short form IP clearance

[Greg Stein]

I believe a PMC is capable of performing IP clearance itself. They have a
VP that is an Officer and can take responsibility for the Foundation in
matters of that Project. The forms/recording are valid, so I haven't
suggested changing that (tho I'd like to see them move under /legal/, I'm
not fussed about their location).

I would hope that a PMC includes a note in their report to the Board, that
they filed a clearance form. That is just natural reporting. But that is
quite different from one TLP being subject to another TLP's vote (whether
lazy consensus or not).

There could certainly be an argument that a PMC needs to be double-checked
by $entity. But that kind of second-guessing means $entity needs to
double-check all commits and all release artifacts. We trust PMCs to get
their IP done correctly, as they work on their project and make releases.

Cheers,
-g

On Wed, Oct 21, 2015 at 8:28 PM, John D. Ament 
wrote:

> Greg,
>
> If I'm reading your email correctly, you're just saying that the Incubator
> is not responsible for processing IP Clearances in a lazy way.  Projects
> should instead direct their IP clearance emails to <>.
>
> That <> is TBD.
>
> John
>
> On Wed, Oct 21, 2015 at 9:17 PM Greg Stein  wrote:
>
> > [trimmed response right now; in favor of getting a couple other voices]
> >
> > On Wed, Oct 21, 2015 at 7:01 PM, Sam Ruby 
> wrote:
> > >...
> >
> > > What is this, randomly propose changes to the incubator month?
> > >
> >
> > Has nothing to do with the Incubator, but with how a PMC records its IP
> > clearance. And more importantly, to clarify that a PMC is not beholden to
> > the IPMC.
> >
> >
> > > Let me repeat what I just said.  I don't believe I was being obtuse,
> > > but then again, you don't appear to have read what I wrote.
> > >
> >
> > I certainly read it, you weren't being obtuse :-)
> >
> >
> > > 1) I hope we can agree that an Officer of the corporation should be
> > > subject to the direction of the Legal Affairs committee.
> > >
> >
> > Agreed.
> >
> > >...
> >
> > > > My point is to make the document reflect the reality of our
> > organization.
> > >
> > > Reality is what is reflected on this page:
> > > http://incubator.apache.org/ip-clearance/
> > >
> > > Click on any of the clearance documents.
> > >
> > > I don't know what you are smoking, but those documents are real.
> > >
> >
> > Of course. I didn't say "get rid of IP clearance". Please read my
> original
> > email, if you think otherwise. I just want to alter the published steps
> to
> > reflect that our TLPs are not beholden to the IPMC. We use the Incubator
> as
> > a location to record these things (which I find odd, but is a separate
> > discussion).
> >
> > >...
> >
> > Cheers,
> > -g
> >
>

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Luke Han]

Just got SGA confirmation from ASF as below.

Please help to double check and change your vote if necessary.

Will update project status and send out vote result later.

Thanks.

-

*This message acknowledges receipt of the following document, which has
been filed in the Apache Software Foundation records:*

*  Grant from eBay, Inc. for Kylin*

*-- Craig L Russell*

*Secretary, Apache Software Foundation*


Best Regards!
-

Luke Han

On Thu, Oct 22, 2015 at 9:08 AM, Naresh Agarwal 
wrote:

> +1 (non-binding)
>
> Thanks
> Naresh
>
> On Thu, Oct 22, 2015 at 6:35 AM, Cai, Eddy  wrote:
>
> > +1
> >
> > -Original Message-
> > From: Chun, Chad [mailto:wac...@ebay.com]
> > Sent: Wednesday, October 21, 2015 9:17 AM
> > To: general@incubator.apache.org
> > Subject: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
> >
> > +1
> >
> > Chad Chun
> > wp_c...@hotmail.com
> >
> > On 10/16/15, 4:22 PM, "蒋旭"  wrote:
> >
> > >+1
> > >Jiang Xu
> > >-- 原始邮件 --
> > >发件人: "Henry Saputra";;
> > >发送时间: 2015年10月16日(星期五) 上午9:16
> > >收件人: "general@incubator.apache.org";
> > >
> > >主题: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
> > >
> > >
> > >
> > >+1 (binding)
> > >
> > >On Thursday, October 15, 2015, Luke Han  wrote:
> > >
> > >> The Apache Kylin community and project made significant advances
> > >>during the  incubating (from Nov 2014) and  believes it is ready to
> > >>graduate as a top-level project.
> > >>
> > >> The Apache Kylin is very active. The PPMC doubled in size (added 6
> > >>committers and 2 mentors) and
> > >>  increased diversity in the past year. Released 3 version in the past
> > >>6  months. There were presentations about Apache Kylin  at most of the
> > >>big conferences of the world (including Strata+Hadoop World  London,
> > >>Hadoop Summit San Jose,  ApacheCon EU, Big Data Technology China,
> > >>Database Technology Conference
> > >> China) and some meetups (Bay Area,
> > >> Beijing and one is coming in this weekend in Shanghai), and many
> > >>talks  around the world.
> > >> The dev mailing list is growing very month, about 500+ topics per
> > >>month  now.
> > >> The community created 1000+ JIRA tickets, many patches from
> > >>contributors/committers have been merged into code base.
> > >>
> > >> A vote passed unanimously on the dev@ list (27 +1 votes). Please find
> > >> below references to the graduation preparation artifacts:
> > >> * discussion on dev list [1]
> > >> * vote thread [2]
> > >> * podling name search [3]
> > >> * incubation status [4]
> > >> * proposed resolution below
> > >>
> > >> We believe Apache Kylin is ready to become a top-level project and if
> > >>the  IPMC agree we will move to a formal vote.
> > >> There are a few more items to be updated on the project status page
> > >>and  others during the next couple of days.
> > >>
> > >>
> > >> Many thanks to the mentors and the IPMC for the support, Luke Han (on
> > >> behalf of the Apache Kylin PPMC)
> > >>
> > >> [1] http://s.apache.org/KylinDisGraduate
> > >> [2] http://s.apache.org/KylinGraduateVote
> > >> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-86
> > >> [4] http://incubator.apache.org/projects/kylin.html
> > >>
> > >>
> > >>
> > >> Apache Kylin top-level project resolution:
> > >> ===
> > >>
> > >>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, relative to distributed and scalable OLAP engine
> > >>
> > >>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >>Committee (PMC), to be known as the "Apache Kylin Project",
> > >>be and hereby is established pursuant to Bylaws of the
> > >>Foundation; and be it further
> > >>
> > >>RESOLVED, that the Apache Kylin Project be and hereby is
> > >>responsible for the creation and maintenance of open-source
> > >>software related to distributed and scalable OLAP engine;
> > >>and be it further
> > >>
> > >>RESOLVED, that the office of "Vice President, Kylin" 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 Kylin Project, and to have primary responsibility for
> > >>management of the projects within the scope of responsibility
> > >>of the Apache Kylin Project; and be it further
> > >>
> > >>RESOLVED, that the persons listed immediately below be and
> > >>hereby 

Re: Short form IP clearance

[John D. Ament]

On Wed, Oct 21, 2015 at 9:40 PM Greg Stein  wrote:

> I believe a PMC is capable of performing IP clearance itself. They have a
> VP that is an Officer and can take responsibility for the Foundation in
> matters of that Project. The forms/recording are valid, so I haven't
> suggested changing that (tho I'd like to see them move under /legal/, I'm
> not fussed about their location).
>
> I would hope that a PMC includes a note in their report to the Board, that
> they filed a clearance form. That is just natural reporting. But that is
> quite different from one TLP being subject to another TLP's vote (whether
> lazy consensus or not).
>
> There could certainly be an argument that a PMC needs to be double-checked
> by $entity. But that kind of second-guessing means $entity needs to
> double-check all commits and all release artifacts. We trust PMCs to get
> their IP done correctly, as they work on their project and make releases.
>

What you're saying makes a lot of sense.  I've always questioned the
benefit of TLPs submitting IP Clearances to the incubator, but not
questioned it because they're so few and far between it's irrelevant.

I would however pressure that podlings are not capable of completing this
on their own, and that they should continue to follow the processes defined
already.  They have knowledgeable mentors, but we should generally note
that the IPMC as a whole is responsible for the podlings.

John


>
> Cheers,
> -g
>
> On Wed, Oct 21, 2015 at 8:28 PM, John D. Ament 
> wrote:
>
> > Greg,
> >
> > If I'm reading your email correctly, you're just saying that the
> Incubator
> > is not responsible for processing IP Clearances in a lazy way.  Projects
> > should instead direct their IP clearance emails to <>.
> >
> > That <> is TBD.
> >
> > John
> >
> > On Wed, Oct 21, 2015 at 9:17 PM Greg Stein  wrote:
> >
> > > [trimmed response right now; in favor of getting a couple other voices]
> > >
> > > On Wed, Oct 21, 2015 at 7:01 PM, Sam Ruby 
> > wrote:
> > > >...
> > >
> > > > What is this, randomly propose changes to the incubator month?
> > > >
> > >
> > > Has nothing to do with the Incubator, but with how a PMC records its IP
> > > clearance. And more importantly, to clarify that a PMC is not beholden
> to
> > > the IPMC.
> > >
> > >
> > > > Let me repeat what I just said.  I don't believe I was being obtuse,
> > > > but then again, you don't appear to have read what I wrote.
> > > >
> > >
> > > I certainly read it, you weren't being obtuse :-)
> > >
> > >
> > > > 1) I hope we can agree that an Officer of the corporation should be
> > > > subject to the direction of the Legal Affairs committee.
> > > >
> > >
> > > Agreed.
> > >
> > > >...
> > >
> > > > > My point is to make the document reflect the reality of our
> > > organization.
> > > >
> > > > Reality is what is reflected on this page:
> > > > http://incubator.apache.org/ip-clearance/
> > > >
> > > > Click on any of the clearance documents.
> > > >
> > > > I don't know what you are smoking, but those documents are real.
> > > >
> > >
> > > Of course. I didn't say "get rid of IP clearance". Please read my
> > original
> > > email, if you think otherwise. I just want to alter the published steps
> > to
> > > reflect that our TLPs are not beholden to the IPMC. We use the
> Incubator
> > as
> > > a location to record these things (which I find odd, but is a separate
> > > discussion).
> > >
> > > >...
> > >
> > > Cheers,
> > > -g
> > >
> >
>

Re: Short form IP clearance

[Greg Stein]

On Wed, Oct 21, 2015 at 8:45 PM, John D. Ament 
wrote:

> On Wed, Oct 21, 2015 at 9:40 PM Greg Stein  wrote:
>
> > I believe a PMC is capable of performing IP clearance itself. They have a
> > VP that is an Officer and can take responsibility for the Foundation in
> > matters of that Project. The forms/recording are valid, so I haven't
> > suggested changing that (tho I'd like to see them move under /legal/, I'm
> > not fussed about their location).
> >
> > I would hope that a PMC includes a note in their report to the Board,
> that
> > they filed a clearance form. That is just natural reporting. But that is
> > quite different from one TLP being subject to another TLP's vote (whether
> > lazy consensus or not).
> >
> > There could certainly be an argument that a PMC needs to be
> double-checked
> > by $entity. But that kind of second-guessing means $entity needs to
> > double-check all commits and all release artifacts. We trust PMCs to get
> > their IP done correctly, as they work on their project and make releases.
> >
>
> What you're saying makes a lot of sense.  I've always questioned the
> benefit of TLPs submitting IP Clearances to the incubator, but not
> questioned it because they're so few and far between it's irrelevant.
>

I get a bit crazy-headed when I perceive the ASF encroaches on the
independence of a TLP. This isn't really a case of the ASF imposing, but
similar. In my view, the Incubator cannot impede/affect the independence of
another TLP. Structurally. The Foundation creates each PMC as an
individual, independent group. Thus, I believe a few of these steps are
just incorrect. I'd like our documentation to reflect the reality of the
independence of our TLPs.

I would however pressure that podlings are not capable of completing this
> on their own, and that they should continue to follow the processes defined
> already.  They have knowledgeable mentors, but we should generally note
> that the IPMC as a whole is responsible for the podlings.
>

Absolutely! The referenced page (and the associated guide) explicitly state
it is for existing projects only. (the language could be clarified as "TLP,
not podling", but yeah: definitely not for podlings)

Cheers,
-g

Re: When podlings don't file a report

[Marvin Humphrey]

On Mon, Oct 19, 2015 at 1:39 PM, Ross Gardler
 wrote:
> This is one aspect that I feel needs fixing. Currently there are too many
> people who "might" be responsible. What we need is someone who *is*
> responsible. It's initially the mentors, but if (as per your original
> question) a podling has failed to file for 4 months then the mentors are
> clearly dropping the ball or they need assistance in impressing upon the
> podling community how important this is. So who next?
>
> My answer is the IPMC, but then we hit the "too many cooks problem".

I don't think it has to be that way.  All any IPMC Member has to do is check
in on the Mentors by sending an email to, say, private@incubator.  That's what
not happening right now.

If there is at least one Mentor willing to continue, all they have to do is
respond "I'm on it" and either persuade the podling to report the next month
or add a comment to the report themselves.

If there are no Mentors willing to continue, then the IPMC has to work with
the podling to arrange for new Mentors or retire.

I don't see a situation there where "too many cooks" end up arguing about the
proper course of action for very long.  Of course someone might stick their
nose in but if there are active Mentors who just needed a nudge, the situation
ought to be resolved quickly.

> To your "shepherd" point below the term here in the IPMC is different to the
> term at the board level. Board shepherds *are* responsible for following up
> after board meetings. That's where the buck stops.

Indeed, the "shepherd" institution is implemented effectively by the Board
level.  We don't have such shepherds in the Incubator... BUT we do have
Mentors.

Mentors are in fact *better* positioned to offer insight than Incubator
shepherds they follow the podling consistently.  We just squander their
insight, because shepherds own primary responsibility for commenting on the
state of the podling.

It's as if the Board had assigned a Director to watch over a TLP then relied
solely on the Board shepherd for their assessment, forgoing all input from the
Director on-the-ground.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Cai, Eddy]

+1

-Original Message-
From: Chun, Chad [mailto:wac...@ebay.com] 
Sent: Wednesday, October 21, 2015 9:17 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

+1

Chad Chun
wp_c...@hotmail.com

On 10/16/15, 4:22 PM, "蒋旭"  wrote:

>+1
>Jiang Xu
>-- 原始邮件 --
>发件人: "Henry Saputra";;
>发送时间: 2015年10月16日(星期五) 上午9:16
>收件人: "general@incubator.apache.org";
>
>主题: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
>
>
>
>+1 (binding)
>
>On Thursday, October 15, 2015, Luke Han  wrote:
>
>> The Apache Kylin community and project made significant advances 
>>during the  incubating (from Nov 2014) and  believes it is ready to 
>>graduate as a top-level project.
>>
>> The Apache Kylin is very active. The PPMC doubled in size (added 6  
>>committers and 2 mentors) and
>>  increased diversity in the past year. Released 3 version in the past 
>>6  months. There were presentations about Apache Kylin  at most of the 
>>big conferences of the world (including Strata+Hadoop World  London, 
>>Hadoop Summit San Jose,  ApacheCon EU, Big Data Technology China, 
>>Database Technology Conference
>> China) and some meetups (Bay Area,
>> Beijing and one is coming in this weekend in Shanghai), and many 
>>talks  around the world.
>> The dev mailing list is growing very month, about 500+ topics per 
>>month  now.
>> The community created 1000+ JIRA tickets, many patches from  
>>contributors/committers have been merged into code base.
>>
>> A vote passed unanimously on the dev@ list (27 +1 votes). Please find 
>> below references to the graduation preparation artifacts:
>> * discussion on dev list [1]
>> * vote thread [2]
>> * podling name search [3]
>> * incubation status [4]
>> * proposed resolution below
>>
>> We believe Apache Kylin is ready to become a top-level project and if 
>>the  IPMC agree we will move to a formal vote.
>> There are a few more items to be updated on the project status page 
>>and  others during the next couple of days.
>>
>>
>> Many thanks to the mentors and the IPMC for the support, Luke Han (on 
>> behalf of the Apache Kylin PPMC)
>>
>> [1] http://s.apache.org/KylinDisGraduate
>> [2] http://s.apache.org/KylinGraduateVote
>> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-86
>> [4] http://incubator.apache.org/projects/kylin.html
>>
>>
>>
>> Apache Kylin top-level project resolution:
>> ===
>>
>>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, relative to distributed and scalable OLAP engine
>>
>>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>Committee (PMC), to be known as the "Apache Kylin Project",
>>be and hereby is established pursuant to Bylaws of the
>>Foundation; and be it further
>>
>>RESOLVED, that the Apache Kylin Project be and hereby is
>>responsible for the creation and maintenance of open-source
>>software related to distributed and scalable OLAP engine;
>>and be it further
>>
>>RESOLVED, that the office of "Vice President, Kylin" 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 Kylin Project, and to have primary responsibility for
>>management of the projects within the scope of responsibility
>>of the Apache Kylin 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 Kylin Project:
>>
>> * Dayue Gao 
>> * Jason Zhong 
>> * Julian Hyde 
>> * Luke Han 
>> * Henry Saputra 
>> * Hongbin Ma 
>> * Hua Huang 
>> * Owen O'Malley 
>> * P. Taylor Goetz 
>> * Qianhao Zhou 
>> * Shaofeng Shi 
>> * Song Yi 
>> * Ted Dunning 
>> * Xu Jiang 
>> * Yang Li 
>> * Yerui Sun < sunyerui at apache dot org>
>>
>>
>>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luke Han
>>be appointed to the office of Vice President,Apache Kylin, 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 Kylin Project be and hereby
>>is tasked with the 

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Naresh Agarwal]

+1 (non-binding)

Thanks
Naresh

On Thu, Oct 22, 2015 at 6:35 AM, Cai, Eddy  wrote:

> +1
>
> -Original Message-
> From: Chun, Chad [mailto:wac...@ebay.com]
> Sent: Wednesday, October 21, 2015 9:17 AM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
>
> +1
>
> Chad Chun
> wp_c...@hotmail.com
>
> On 10/16/15, 4:22 PM, "蒋旭"  wrote:
>
> >+1
> >Jiang Xu
> >-- 原始邮件 --
> >发件人: "Henry Saputra";;
> >发送时间: 2015年10月16日(星期五) 上午9:16
> >收件人: "general@incubator.apache.org";
> >
> >主题: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
> >
> >
> >
> >+1 (binding)
> >
> >On Thursday, October 15, 2015, Luke Han  wrote:
> >
> >> The Apache Kylin community and project made significant advances
> >>during the  incubating (from Nov 2014) and  believes it is ready to
> >>graduate as a top-level project.
> >>
> >> The Apache Kylin is very active. The PPMC doubled in size (added 6
> >>committers and 2 mentors) and
> >>  increased diversity in the past year. Released 3 version in the past
> >>6  months. There were presentations about Apache Kylin  at most of the
> >>big conferences of the world (including Strata+Hadoop World  London,
> >>Hadoop Summit San Jose,  ApacheCon EU, Big Data Technology China,
> >>Database Technology Conference
> >> China) and some meetups (Bay Area,
> >> Beijing and one is coming in this weekend in Shanghai), and many
> >>talks  around the world.
> >> The dev mailing list is growing very month, about 500+ topics per
> >>month  now.
> >> The community created 1000+ JIRA tickets, many patches from
> >>contributors/committers have been merged into code base.
> >>
> >> A vote passed unanimously on the dev@ list (27 +1 votes). Please find
> >> below references to the graduation preparation artifacts:
> >> * discussion on dev list [1]
> >> * vote thread [2]
> >> * podling name search [3]
> >> * incubation status [4]
> >> * proposed resolution below
> >>
> >> We believe Apache Kylin is ready to become a top-level project and if
> >>the  IPMC agree we will move to a formal vote.
> >> There are a few more items to be updated on the project status page
> >>and  others during the next couple of days.
> >>
> >>
> >> Many thanks to the mentors and the IPMC for the support, Luke Han (on
> >> behalf of the Apache Kylin PPMC)
> >>
> >> [1] http://s.apache.org/KylinDisGraduate
> >> [2] http://s.apache.org/KylinGraduateVote
> >> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-86
> >> [4] http://incubator.apache.org/projects/kylin.html
> >>
> >>
> >>
> >> Apache Kylin top-level project resolution:
> >> ===
> >>
> >>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, relative to distributed and scalable OLAP engine
> >>
> >>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >>Committee (PMC), to be known as the "Apache Kylin Project",
> >>be and hereby is established pursuant to Bylaws of the
> >>Foundation; and be it further
> >>
> >>RESOLVED, that the Apache Kylin Project be and hereby is
> >>responsible for the creation and maintenance of open-source
> >>software related to distributed and scalable OLAP engine;
> >>and be it further
> >>
> >>RESOLVED, that the office of "Vice President, Kylin" 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 Kylin Project, and to have primary responsibility for
> >>management of the projects within the scope of responsibility
> >>of the Apache Kylin 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 Kylin Project:
> >>
> >> * Dayue Gao 
> >> * Jason Zhong 
> >> * Julian Hyde 
> >> * Luke Han 
> >> * Henry Saputra 
> >> * Hongbin Ma 
> >> * Hua Huang 
> >> * Owen O'Malley 
> >> * P. Taylor Goetz 
> >> * Qianhao Zhou 
> >> * Shaofeng Shi 
> >> * Song Yi 
> >> * Ted Dunning 
> >> * Xu Jiang 
> >> * Yang Li 
> >> * Yerui Sun < sunyerui at apache dot org>
> >>
> >>
> >>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luke Han
> >>be appointed to the office of Vice President,Apache Kylin, to
> >>serve
> >>in accordance with and subject to the 

Not just yet (was: [VOTE] Graduate Apache Brooklyn from incubator)

[Hadrian Zbarcea]

The resolution to graduate Apache Brooklyn out of the incubator was 
tabled due to a procedural issue. This has nothing to do with the code 
or the community.


The reason was an editorial error on my side, I used the wrong template 
and the last paragraph releasing the incubator from its responsibilities 
was missing from the resolution. It is unfortunate that nobody caught 
that, but the error is completely mine.


We will resubmit in 4 weeks.

Million apologies,
Hadrian

On 10/01/2015 11:06 AM, Hadrian Zbarcea wrote:

Vote passes with:

+1 - 6 binding (ke4qqq, jbonofre, jzb, johndament, olamy, hadrian)
+1 - 2 non-binding
-1 - 0

We will submit the proposal below to the board for approval (including
jbonofre and olamy in the PMC).

Many thanks again to our mentors and the incubator in general for the
guidance.

Hadrian


On 09/28/2015 10:06 AM, Hadrian Zbarcea wrote:

This is the Incubator vote to decide if Apache Brooklyn should graduate
from the Incubator. Please see the proposed resolution below.

See also discuss thread [1]. Mentors were invited to join the future TLP
PMC on request. Invitation is open until this vote is closed.

This vote is open for at least 72 hours.

[ ] +1 Graduate Apache Brooklyn from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...

Thanks,
Hadrian

[1]
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E





X. Establish the Apache Brooklyn 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 tools that help automate various
 administrative tasks or information lookup activities.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the "Apache Brooklyn Project",
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache Brooklyn Project be and hereby is
 responsible for the creation and maintenance of a software
 framework for modeling, monitoring, and managing cloud
 applications through autonomic blueprints; and be it further

 RESOLVED, that the office of "Vice President, Apache Brooklyn"
 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 Brooklyn Project, and to have primary
 responsibility for management of the projects within the scope
 of responsibility of the Apache Brooklyn 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 Brooklyn Project Management Committee:

 * Aled Sage 
 * Alex Heneveld 
 * Andrea Turli 
 * Andrew Kennedy 
 * Ciprian Ciubotariu 
 * Hadrian Zbarcea 
 * Richard Downer 
 * Sam Corbett 
 * Svetoslav Neykov 

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
 appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby
 is tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Brooklyn Project.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Short form IP clearance

[Greg Stein]

[trimmed response right now; in favor of getting a couple other voices]

On Wed, Oct 21, 2015 at 7:01 PM, Sam Ruby  wrote:
>...

> What is this, randomly propose changes to the incubator month?
>

Has nothing to do with the Incubator, but with how a PMC records its IP
clearance. And more importantly, to clarify that a PMC is not beholden to
the IPMC.


> Let me repeat what I just said.  I don't believe I was being obtuse,
> but then again, you don't appear to have read what I wrote.
>

I certainly read it, you weren't being obtuse :-)


> 1) I hope we can agree that an Officer of the corporation should be
> subject to the direction of the Legal Affairs committee.
>

Agreed.

>...

> > My point is to make the document reflect the reality of our organization.
>
> Reality is what is reflected on this page:
> http://incubator.apache.org/ip-clearance/
>
> Click on any of the clearance documents.
>
> I don't know what you are smoking, but those documents are real.
>

Of course. I didn't say "get rid of IP clearance". Please read my original
email, if you think otherwise. I just want to alter the published steps to
reflect that our TLPs are not beholden to the IPMC. We use the Incubator as
a location to record these things (which I find odd, but is a separate
discussion).

>...

Cheers,
-g

Re: Short form IP clearance

[Sam Ruby]

On Wed, Oct 21, 2015 at 7:37 PM, Greg Stein  wrote:
> On Wed, Oct 21, 2015 at 3:37 PM, Sam Ruby  wrote:
>
>> On Wed, Oct 21, 2015 at 3:22 PM, Greg Stein  wrote:
>> > Hey all,
>> >
>> > On the following page:
>> >   http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>> >
>> > The process steps do not align with the intent described in the Preamble,
>> > and some steps are not required. Specifically, steps 5, 7, and 8.
>> >
>> > Step 5: the code will be imported *somewhere*; there is no reason for it
>> to
>> > be duplicated into the Incubator repository. The ASF simply requires
>> > paperwork to acknowledge the propriety of that import, wherever it may
>> be.
>> > There isn't even a reason for a checksum.
>> >
>> > Step 7: the Incubator has no prerogative over what the VP of an Apache
>> > project does (or other Officers, for that matter). If a TLP wants some
>> > code, then they can do so. And the representative of that TLP (the VP, an
>> > Officer) is the one taking responsibility for their actions. The
>> Incubator
>> > has been a recording area, but that doesn't give it discretion over other
>> > projects.
>> > [ IMO, the recording should go somewhere identified by VP Legal Affairs,
>> > and be entirely disconnected from the Incubator ]
>>
>> Just some historical perspective (from the previous VP Legal Affairs,
>> though this predates my having that role), IP clearance is something
>> that is rarely done on a PMC level so it is something that most
>> individual PMCs don't have much experience with; at a foundation level
>> it is done frequently and primarily by the incubator.  Hence the VP of
>> Legal Affairs (my predecessor and then unchanged by myself) designated
>> that the Incubator have this role.
>>
>> > Step 8: moot, once (7) is removed.
>> >
>> > I'd like to modify the steps to reflect the above points.
>> >
>> > Thoughts?
>>
>> As far as I can tell, it has been working without issue, where lazy
>> consensus is key to making it work smoothly.  So I'm -1 on fixing
>> something that isn't broke.
>
> It *is* broken. An Officer of the corporation should not be subject to the
> will of the IPMC.

What is this, randomly propose changes to the incubator month?

Let me repeat what I just said.  I don't believe I was being obtuse,
but then again, you don't appear to have read what I wrote.

1) I hope we can agree that an Officer of the corporation should be
subject to the direction of the Legal Affairs committee.

2) When I first got that particular job, I'll admit that the division
of labor seemed a little... peculiar.  But when I investigated, the
argument made sense, so I went with it.  If you don't like it, perhaps
your beef is with the current VP of Legal.  If you want to make an
argument that it is more efficient to who specialize in IP clearance
to split their time between two committees, go for it.  But the
process isn't broken simply because you don't like the color of the
hat that is being worn by the person or people doing the job.

Recapping: it is quite OK for VP of Legal to set policy.  It is quite
OK for VP of Legal to delegate work.  It is even quite OK for the
current VP of Legal to come to a different conclusion than the two
previous holders of that job.  But what's not OK is...

> Gavin asked me how TLPs can import code, and I noted the IP clearance
> process. I looked at it, and found it to be wrong. Whichever TLP he was
> referring to should not be posting to general@. They should "file the
> paperwork" and call it done.
>
> I will even tell them to ignore those steps. If/when I ever do it with an
> Officer hat on, I'll ignore those steps.

... seriously uncool dude.  What you are saying is that you know
better than both the VP of Legal and those that have been doing this
work without conflict for years.  Not.  Cool.

> My point is to make the document reflect the reality of our organization.

Reality is what is reflected on this page:
http://incubator.apache.org/ip-clearance/

Click on any of the clearance documents.

I don't know what you are smoking, but those documents are real.

As an added bonus, I encourage you to scan the following reports,
searching for the word "Incubator":

https://whimsy.apache.org/board/minutes/Legal_Affairs.html

I don't know whether you remember those reports, but I'll remind you
that you approved of each and every one of them.  I specifically
discussed the division of labor, and followed up subsequently with
mentions of issues being forwarded.

> Cheers,
> -g

- Sam Ruby

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Short form IP clearance

[Greg Stein]

On Wed, Oct 21, 2015 at 3:37 PM, Sam Ruby  wrote:

> On Wed, Oct 21, 2015 at 3:22 PM, Greg Stein  wrote:
> > Hey all,
> >
> > On the following page:
> >   http://incubator.apache.org/ip-clearance/ip-clearance-template.html
> >
> > The process steps do not align with the intent described in the Preamble,
> > and some steps are not required. Specifically, steps 5, 7, and 8.
> >
> > Step 5: the code will be imported *somewhere*; there is no reason for it
> to
> > be duplicated into the Incubator repository. The ASF simply requires
> > paperwork to acknowledge the propriety of that import, wherever it may
> be.
> > There isn't even a reason for a checksum.
> >
> > Step 7: the Incubator has no prerogative over what the VP of an Apache
> > project does (or other Officers, for that matter). If a TLP wants some
> > code, then they can do so. And the representative of that TLP (the VP, an
> > Officer) is the one taking responsibility for their actions. The
> Incubator
> > has been a recording area, but that doesn't give it discretion over other
> > projects.
> > [ IMO, the recording should go somewhere identified by VP Legal Affairs,
> > and be entirely disconnected from the Incubator ]
>
> Just some historical perspective (from the previous VP Legal Affairs,
> though this predates my having that role), IP clearance is something
> that is rarely done on a PMC level so it is something that most
> individual PMCs don't have much experience with; at a foundation level
> it is done frequently and primarily by the incubator.  Hence the VP of
> Legal Affairs (my predecessor and then unchanged by myself) designated
> that the Incubator have this role.
>
> > Step 8: moot, once (7) is removed.
> >
> > I'd like to modify the steps to reflect the above points.
> >
> > Thoughts?
>
> As far as I can tell, it has been working without issue, where lazy
> consensus is key to making it work smoothly.  So I'm -1 on fixing
> something that isn't broke.
>

It *is* broken. An Officer of the corporation should not be subject to the
will of the IPMC.

Gavin asked me how TLPs can import code, and I noted the IP clearance
process. I looked at it, and found it to be wrong. Whichever TLP he was
referring to should not be posting to general@. They should "file the
paperwork" and call it done.

I will even tell them to ignore those steps. If/when I ever do it with an
Officer hat on, I'll ignore those steps.

My point is to make the document reflect the reality of our organization.

Cheers,
-g

Re: [VOTE] Release Apache Kylin 1.1-incubating (rc1)

[Luke Han]

Hi IPMC,
 We would like to have more vote from IPMC members to help on this
release candidate.
 Thank you very much.

Luke



Best Regards!
-

Luke Han

On Tue, Oct 20, 2015 at 12:19 AM, Henry Saputra 
wrote:

> Signature file look good
> Hash files look good
> LICENSE and DISCLAIMER exist
> No 3rd party exes found in source artifacts
>
> +1 (binding)
>
> - Henry
>
> On Wed, Oct 14, 2015 at 6:42 PM, ShaoFeng Shi 
> wrote:
> > Hi all,
> >
> > The Apache Kylin community has voted on and approved a proposal to
> release
> > Apache Kylin 1.1-incubating.
> >
> > Proposal:http://s.apache.org/Jzu
> >
> > Vote result:
> > 7 binding +1 votes
> > 6 non-binding +1 votes
> > No -1 voteshttp://s.apache.org/kylin-1.1-result_rc1
> >
> >
> > The commit to be voted
> > upon:
> https://github.com/apache/incubator-kylin/commit/1955a2f9aea7b7f608f0496c00807715ea4246a5
> >
> > Its hash is 1955a2f9aea7b7f608f0496c00807715ea4246a5.
> >
> > The artifacts to be voted on are located
> > here:
> https://dist.apache.org/repos/dist/dev/incubator/kylin/apache-kylin-1.1-incubating-rc1/
> >
> > The hashes of the artifacts are as follows:
> > apache-kylin-1.1-incubating-src.tar.gz.md5
> 18dfbb012e1eb807b1a5c1b134a537aa
> > apache-kylin-1.1-incubating-src.tar.gz.sha1
> > 041ee010c67a0b5611d9dd06f7fd6f37388c5374
> >
> > A staged Maven repository is available for review
> > at:
> https://repository.apache.org/content/repositories/orgapachekylin-1012/
> >
> > Release artifacts are signed with the following
> > key:https://people.apache.org/keys/committer/shaofengshi.asc
> >
> > Pursuant to the Releases section of the Incubation Policy and with
> > the endorsement of our mentors we would now like to request
> > the permission of the Incubator PMC to publish the release. The vote
> > is open for 72 hours, or until the necessary number of votes (3 +1)
> > is reached.
> >
> > [ ] +1 Release this package
> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> >
> > Shaofeng Shi, on behalf of Apache Kylin ppmcshaofeng...@apache.org
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Not just yet (was: [VOTE] Graduate Apache Brooklyn from incubator)

[John D. Ament]

Any reason you need 4 weeks to add the paragraph back?
On Oct 21, 2015 21:09, "Hadrian Zbarcea"  wrote:

> The resolution to graduate Apache Brooklyn out of the incubator was tabled
> due to a procedural issue. This has nothing to do with the code or the
> community.
>
> The reason was an editorial error on my side, I used the wrong template
> and the last paragraph releasing the incubator from its responsibilities
> was missing from the resolution. It is unfortunate that nobody caught that,
> but the error is completely mine.
>
> We will resubmit in 4 weeks.
>
> Million apologies,
> Hadrian
>
> On 10/01/2015 11:06 AM, Hadrian Zbarcea wrote:
>
>> Vote passes with:
>>
>> +1 - 6 binding (ke4qqq, jbonofre, jzb, johndament, olamy, hadrian)
>> +1 - 2 non-binding
>> -1 - 0
>>
>> We will submit the proposal below to the board for approval (including
>> jbonofre and olamy in the PMC).
>>
>> Many thanks again to our mentors and the incubator in general for the
>> guidance.
>>
>> Hadrian
>>
>>
>> On 09/28/2015 10:06 AM, Hadrian Zbarcea wrote:
>>
>>> This is the Incubator vote to decide if Apache Brooklyn should graduate
>>> from the Incubator. Please see the proposed resolution below.
>>>
>>> See also discuss thread [1]. Mentors were invited to join the future TLP
>>> PMC on request. Invitation is open until this vote is closed.
>>>
>>> This vote is open for at least 72 hours.
>>>
>>> [ ] +1 Graduate Apache Brooklyn from the Incubator.
>>> [ ] +0 Don't care.
>>> [ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...
>>>
>>> Thanks,
>>> Hadrian
>>>
>>> [1]
>>>
>>> http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E
>>>
>>>
>>>
>>>
>>> 
>>> X. Establish the Apache Brooklyn 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 tools that help automate various
>>>  administrative tasks or information lookup activities.
>>>
>>>  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>>  Committee (PMC), to be known as the "Apache Brooklyn Project",
>>>  be and hereby is established pursuant to Bylaws of the
>>>  Foundation; and be it further
>>>
>>>  RESOLVED, that the Apache Brooklyn Project be and hereby is
>>>  responsible for the creation and maintenance of a software
>>>  framework for modeling, monitoring, and managing cloud
>>>  applications through autonomic blueprints; and be it further
>>>
>>>  RESOLVED, that the office of "Vice President, Apache Brooklyn"
>>>  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 Brooklyn Project, and to have primary
>>>  responsibility for management of the projects within the scope
>>>  of responsibility of the Apache Brooklyn 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 Brooklyn Project Management Committee:
>>>
>>>  * Aled Sage 
>>>  * Alex Heneveld 
>>>  * Andrea Turli 
>>>  * Andrew Kennedy 
>>>  * Ciprian Ciubotariu 
>>>  * Hadrian Zbarcea 
>>>  * Richard Downer 
>>>  * Sam Corbett 
>>>  * Svetoslav Neykov 
>>>
>>>  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be
>>>  appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby
>>>  is tasked with the creation of a set of bylaws intended to
>>>  encourage open development and increased participation in the
>>>  Apache Brooklyn Project.
>>>
>>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Not just yet (was: [VOTE] Graduate Apache Brooklyn from incubator)

[Greg Stein]

Several things: the description of the project in para 1 and 3 do not
match. Second, the wording of the (current) last paragraph doesn't refer to
"podling" like other Incubator graduation resolutions. Third, the final
paragraph from the template, releasing the Incubator from responsibility.

See the Calcite resolution in this month's agenda.

Regarding 4 weeks: a new agenda should be posted within a 1-2 weeks, and
the revised resolution can immediately be placed there. The Board will vote
on it during its Nov 18 meeting. (technically, if you can finagle all 9
Directors to +1 the resolution before then, it passes on that 9th vote)

Cheers,
-g

On Wed, Oct 21, 2015 at 9:43 PM, John D. Ament 
wrote:

> Any reason you need 4 weeks to add the paragraph back?
> On Oct 21, 2015 21:09, "Hadrian Zbarcea"  wrote:
>
> > The resolution to graduate Apache Brooklyn out of the incubator was
> tabled
> > due to a procedural issue. This has nothing to do with the code or the
> > community.
> >
> > The reason was an editorial error on my side, I used the wrong template
> > and the last paragraph releasing the incubator from its responsibilities
> > was missing from the resolution. It is unfortunate that nobody caught
> that,
> > but the error is completely mine.
> >
> > We will resubmit in 4 weeks.
> >
> > Million apologies,
> > Hadrian
> >
> > On 10/01/2015 11:06 AM, Hadrian Zbarcea wrote:
> >
> >> Vote passes with:
> >>
> >> +1 - 6 binding (ke4qqq, jbonofre, jzb, johndament, olamy, hadrian)
> >> +1 - 2 non-binding
> >> -1 - 0
> >>
> >> We will submit the proposal below to the board for approval (including
> >> jbonofre and olamy in the PMC).
> >>
> >> Many thanks again to our mentors and the incubator in general for the
> >> guidance.
> >>
> >> Hadrian
> >>
> >>
> >> On 09/28/2015 10:06 AM, Hadrian Zbarcea wrote:
> >>
> >>> This is the Incubator vote to decide if Apache Brooklyn should graduate
> >>> from the Incubator. Please see the proposed resolution below.
> >>>
> >>> See also discuss thread [1]. Mentors were invited to join the future
> TLP
> >>> PMC on request. Invitation is open until this vote is closed.
> >>>
> >>> This vote is open for at least 72 hours.
> >>>
> >>> [ ] +1 Graduate Apache Brooklyn from the Incubator.
> >>> [ ] +0 Don't care.
> >>> [ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...
> >>>
> >>> Thanks,
> >>> Hadrian
> >>>
> >>> [1]
> >>>
> >>>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E
> >>>
> >>>
> >>>
> >>>
> >>> 
> >>> X. Establish the Apache Brooklyn 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 tools that help automate various
> >>>  administrative tasks or information lookup activities.
> >>>
> >>>  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >>>  Committee (PMC), to be known as the "Apache Brooklyn Project",
> >>>  be and hereby is established pursuant to Bylaws of the
> >>>  Foundation; and be it further
> >>>
> >>>  RESOLVED, that the Apache Brooklyn Project be and hereby is
> >>>  responsible for the creation and maintenance of a software
> >>>  framework for modeling, monitoring, and managing cloud
> >>>  applications through autonomic blueprints; and be it further
> >>>
> >>>  RESOLVED, that the office of "Vice President, Apache Brooklyn"
> >>>  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 Brooklyn Project, and to have primary
> >>>  responsibility for management of the projects within the scope
> >>>  of responsibility of the Apache Brooklyn 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 Brooklyn Project Management Committee:
> >>>
> >>>  * Aled Sage 
> >>>  * Alex Heneveld 
> >>>  * Andrea Turli 
> >>>  * Andrew Kennedy 
> >>>  * Ciprian Ciubotariu 
> >>>  * Hadrian Zbarcea 
> >>>  * Richard Downer 
> >>>  * Sam Corbett 
> >>>  * Svetoslav Neykov 
> >>>
> >>>  NOW, THEREFORE, BE IT FURTHER RESOLVED, that 

Re: Not just yet (was: [VOTE] Graduate Apache Brooklyn from incubator)

[John D. Ament]

On Oct 21, 2015 22:48, "Greg Stein"  wrote:
>
> Several things: the description of the project in para 1 and 3 do not
> match. Second, the wording of the (current) last paragraph doesn't refer
to
> "podling" like other Incubator graduation resolutions. Third, the final
> paragraph from the template, releasing the Incubator from responsibility.
>
> See the Calcite resolution in this month's agenda.
>
> Regarding 4 weeks: a new agenda should be posted within a 1-2 weeks, and

I think that's my point.  Those two weeks should be used to get incubator
approval.  If you wait 4 weeks you don't graduate until December.

> the revised resolution can immediately be placed there. The Board will
vote
> on it during its Nov 18 meeting. (technically, if you can finagle all 9
> Directors to +1 the resolution before then, it passes on that 9th vote)
>
> Cheers,
> -g
>
> On Wed, Oct 21, 2015 at 9:43 PM, John D. Ament 
> wrote:
>
> > Any reason you need 4 weeks to add the paragraph back?
> > On Oct 21, 2015 21:09, "Hadrian Zbarcea"  wrote:
> >
> > > The resolution to graduate Apache Brooklyn out of the incubator was
> > tabled
> > > due to a procedural issue. This has nothing to do with the code or the
> > > community.
> > >
> > > The reason was an editorial error on my side, I used the wrong
template
> > > and the last paragraph releasing the incubator from its
responsibilities
> > > was missing from the resolution. It is unfortunate that nobody caught
> > that,
> > > but the error is completely mine.
> > >
> > > We will resubmit in 4 weeks.
> > >
> > > Million apologies,
> > > Hadrian
> > >
> > > On 10/01/2015 11:06 AM, Hadrian Zbarcea wrote:
> > >
> > >> Vote passes with:
> > >>
> > >> +1 - 6 binding (ke4qqq, jbonofre, jzb, johndament, olamy, hadrian)
> > >> +1 - 2 non-binding
> > >> -1 - 0
> > >>
> > >> We will submit the proposal below to the board for approval
(including
> > >> jbonofre and olamy in the PMC).
> > >>
> > >> Many thanks again to our mentors and the incubator in general for the
> > >> guidance.
> > >>
> > >> Hadrian
> > >>
> > >>
> > >> On 09/28/2015 10:06 AM, Hadrian Zbarcea wrote:
> > >>
> > >>> This is the Incubator vote to decide if Apache Brooklyn should
graduate
> > >>> from the Incubator. Please see the proposed resolution below.
> > >>>
> > >>> See also discuss thread [1]. Mentors were invited to join the future
> > TLP
> > >>> PMC on request. Invitation is open until this vote is closed.
> > >>>
> > >>> This vote is open for at least 72 hours.
> > >>>
> > >>> [ ] +1 Graduate Apache Brooklyn from the Incubator.
> > >>> [ ] +0 Don't care.
> > >>> [ ] -1 Don't graduate Apache Brooklyn from the Incubator because ...
> > >>>
> > >>> Thanks,
> > >>> Hadrian
> > >>>
> > >>> [1]
> > >>>
> > >>>
> >
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> 
> > >>> X. Establish the Apache Brooklyn 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 tools that help automate various
> > >>>  administrative tasks or information lookup activities.
> > >>>
> > >>>  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >>>  Committee (PMC), to be known as the "Apache Brooklyn
Project",
> > >>>  be and hereby is established pursuant to Bylaws of the
> > >>>  Foundation; and be it further
> > >>>
> > >>>  RESOLVED, that the Apache Brooklyn Project be and hereby is
> > >>>  responsible for the creation and maintenance of a software
> > >>>  framework for modeling, monitoring, and managing cloud
> > >>>  applications through autonomic blueprints; and be it
further
> > >>>
> > >>>  RESOLVED, that the office of "Vice President, Apache
Brooklyn"
> > >>>  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 Brooklyn Project, and to have primary
> > >>>  responsibility for management of the projects within the
scope
> > >>>  of responsibility of the Apache Brooklyn 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 Brooklyn Project Management Committee:
> > >>>
> > >>>  * Aled Sage 
> > >>>  * Alex Heneveld 
> > >>>

Re: Not just yet (was: [VOTE] Graduate Apache Brooklyn from incubator)

[Marvin Humphrey]

On Wed, Oct 21, 2015 at 7:58 PM, John D. Ament  wrote:

> I think that's my point.  Those two weeks should be used to get incubator
> approval.  If you wait 4 weeks you don't graduate until December.

The Incubator isn't going to vote again.  The text of the graduation
resolution from an Incubator recommendation is advisory and the Board
often modifies it. (The Incubator gets the text wrong embarrassingly
often.)  The Board passing a resolution to establish a TLP is the
crucial step from the standpoint of the Foundation as a corporate
entity.

It's regrettable that the glitch was not caught until there was little
time left during today's meeting, but resolutions are powerful tools
and it's important to get the language right. The Foundation's bylaws
constrain the Board's ability to act -- it's not supposed to be easy.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Kylin 1.1-incubating (rc1)

[Jian Zhong]

Hi all,

about the font license

 Kylin UI is build with AdminLTE[1]

 AdminLTE license here[2]

 AdminLTE use google webfonts, you can see it at first line here[3]

 due to firewall issue,some places like CHINA may not be able to access
this file.so we download it to local file
"webapp/app/fonts/AdminLTE-fonts.css"

 about the google fonts license [4]
 Can I use the Fonts API on any page?

 Yes. All the fonts on Google Fonts  are
licensed under open source licenses that let you use them on any website,
from a private blog to a big commercial site.




 1.https://github.com/almasaeed2010/AdminLTE
 2.https://github.com/almasaeed2010/AdminLTE/blob/master/LICENSE
 3.
https://github.com/almasaeed2010/AdminLTE/blob/master/dist/css/AdminLTE.css
 4.https://developers.google.com/fonts/faq?hl=en


 Thanks

 Jason

On Thu, Oct 22, 2015 at 7:07 AM, Justin Mclean 
wrote:

> Hi,
>
> It’s +0 (binding) from me.
>
> I checked:
> - release name includes incubating
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE is OK, but probably missing font license
> - NOTICE all good
> - All source files have apache headers (a few test files and data files
> don’t)
> - A couple of unexpected binary files in release
> - Can compile from source
>
> There are two binary font files, whose licensing I’m unsure of in the
> source package:
> ./webapp/app/fonts/ODelI1aHBYDBqgeIAH2zlPytCVloACqnDHJwh-em2k8.woff2
> (may be Source San Pro which is covered by a SIL license so that would
> also need to go into
> the LICENSE file or be removed)
>
> ./webapp/app/fonts/toadOcfmlt9b38dHJxOBGKUt5Ot5NIMarvNW-hkYWvT3rGVtsTkPsbDajuO5ueQw.woff2
> (may be Source Sans Pro Bold?)
>
> This issue was brought up before [1] in a previous release.
>
> Thanks,
> Justin
>
> 1.
> http://mail-archives.apache.org/mod_mbox/incubator-general/201505.mbox/%3c09e70cf6-7d79-4bff-9e05-58f9c0897...@classsoftware.com%3E
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Kylin 1.1-incubating (rc1)

[Luke Han]

Thanks Jason to check these.We should add in notice/disclaim files about 
this(AdminLTE already be mentioned there)
But this should not a block issue for release.
Hi Justin, would you mind to check and vote again?
Thank you very much.

Regards!
Luke Han




On Wed, Oct 21, 2015 at 8:29 PM -0700, "Jian Zhong"  
wrote:










Hi all,

about the font license

 Kylin UI is build with AdminLTE[1]

 AdminLTE license here[2]

 AdminLTE use google webfonts, you can see it at first line here[3]

 due to firewall issue,some places like CHINA may not be able to access
this file.so we download it to local file
"webapp/app/fonts/AdminLTE-fonts.css"

 about the google fonts license [4]
 Can I use the Fonts API on any page?

 Yes. All the fonts on Google Fonts  are
licensed under open source licenses that let you use them on any website,
from a private blog to a big commercial site.




 1.https://github.com/almasaeed2010/AdminLTE
 2.https://github.com/almasaeed2010/AdminLTE/blob/master/LICENSE
 3.
https://github.com/almasaeed2010/AdminLTE/blob/master/dist/css/AdminLTE.css
 4.https://developers.google.com/fonts/faq?hl=en


 Thanks

 Jason

On Thu, Oct 22, 2015 at 7:07 AM, Justin Mclean 
wrote:

> Hi,
>
> It’s +0 (binding) from me.
>
> I checked:
> - release name includes incubating
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE is OK, but probably missing font license
> - NOTICE all good
> - All source files have apache headers (a few test files and data files
> don’t)
> - A couple of unexpected binary files in release
> - Can compile from source
>
> There are two binary font files, whose licensing I’m unsure of in the
> source package:
> ./webapp/app/fonts/ODelI1aHBYDBqgeIAH2zlPytCVloACqnDHJwh-em2k8.woff2
> (may be Source San Pro which is covered by a SIL license so that would
> also need to go into
> the LICENSE file or be removed)
>
> ./webapp/app/fonts/toadOcfmlt9b38dHJxOBGKUt5Ot5NIMarvNW-hkYWvT3rGVtsTkPsbDajuO5ueQw.woff2
> (may be Source Sans Pro Bold?)
>
> This issue was brought up before [1] in a previous release.
>
> Thanks,
> Justin
>
> 1.
> http://mail-archives.apache.org/mod_mbox/incubator-general/201505.mbox/%3c09e70cf6-7d79-4bff-9e05-58f9c0897...@classsoftware.com%3E
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Atri Sharma]

+1 (Non Binding)

On Wed, Oct 21, 2015 at 6:47 AM, Chun, Chad  wrote:

> +1
>
> Chad Chun
> wp_c...@hotmail.com
>
> On 10/16/15, 4:22 PM, "蒋旭"  wrote:
>
> >+1
> >Jiang Xu
> >-- 原始邮件 --
> >发件人: "Henry Saputra";;
> >发送时间: 2015年10月16日(星期五) 上午9:16
> >收件人: "general@incubator.apache.org";
> >
> >主题: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
> >
> >
> >
> >+1 (binding)
> >
> >On Thursday, October 15, 2015, Luke Han  wrote:
> >
> >> The Apache Kylin community and project made significant advances during
> >>the
> >> incubating (from Nov 2014) and
> >> believes it is ready to graduate as a top-level project.
> >>
> >> The Apache Kylin is very active. The PPMC doubled in size (added 6
> >> committers and 2 mentors) and
> >>  increased diversity in the past year. Released 3 version in the past 6
> >> months. There were presentations about Apache Kylin
> >> at most of the big conferences of the world (including Strata+Hadoop
> >>World
> >> London, Hadoop Summit San Jose,
> >> ApacheCon EU, Big Data Technology China, Database Technology Conference
> >> China) and some meetups (Bay Area,
> >> Beijing and one is coming in this weekend in Shanghai), and many talks
> >> around the world.
> >> The dev mailing list is growing very month, about 500+ topics per month
> >> now.
> >> The community created 1000+ JIRA tickets, many patches from
> >> contributors/committers have been merged into code base.
> >>
> >> A vote passed unanimously on the dev@ list (27 +1 votes). Please find
> >> below
> >> references to the graduation preparation artifacts:
> >> * discussion on dev list [1]
> >> * vote thread [2]
> >> * podling name search [3]
> >> * incubation status [4]
> >> * proposed resolution below
> >>
> >> We believe Apache Kylin is ready to become a top-level project and if
> >>the
> >> IPMC agree we will move to a formal vote.
> >> There are a few more items to be updated on the project status page and
> >> others during the next couple of days.
> >>
> >>
> >> Many thanks to the mentors and the IPMC for the support,
> >> Luke Han (on behalf of the Apache Kylin PPMC)
> >>
> >> [1] http://s.apache.org/KylinDisGraduate
> >> [2] http://s.apache.org/KylinGraduateVote
> >> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-86
> >> [4] http://incubator.apache.org/projects/kylin.html
> >>
> >>
> >>
> >> Apache Kylin top-level project resolution:
> >> ===
> >>
> >>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, relative to distributed and scalable OLAP engine
> >>
> >>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >>Committee (PMC), to be known as the "Apache Kylin Project",
> >>be and hereby is established pursuant to Bylaws of the
> >>Foundation; and be it further
> >>
> >>RESOLVED, that the Apache Kylin Project be and hereby is
> >>responsible for the creation and maintenance of open-source
> >>software related to distributed and scalable OLAP engine;
> >>and be it further
> >>
> >>RESOLVED, that the office of "Vice President, Kylin" 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 Kylin Project, and to have primary responsibility for
> >>management of the projects within the scope of responsibility
> >>of the Apache Kylin 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 Kylin Project:
> >>
> >> * Dayue Gao 
> >> * Jason Zhong 
> >> * Julian Hyde 
> >> * Luke Han 
> >> * Henry Saputra 
> >> * Hongbin Ma 
> >> * Hua Huang 
> >> * Owen O'Malley 
> >> * P. Taylor Goetz 
> >> * Qianhao Zhou 
> >> * Shaofeng Shi 
> >> * Song Yi 
> >> * Ted Dunning 
> >> * Xu Jiang 
> >> * Yang Li 
> >> * Yerui Sun < sunyerui at apache dot org>
> >>
> >>
> >>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luke Han
> >>be appointed to the office of Vice President,Apache Kylin, 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

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Chun, Chad]

+1

Chad Chun
wp_c...@hotmail.com

On 10/16/15, 4:22 PM, "蒋旭"  wrote:

>+1
>Jiang Xu
>-- 原始邮件 --
>发件人: "Henry Saputra";;
>发送时间: 2015年10月16日(星期五) 上午9:16
>收件人: "general@incubator.apache.org";
>
>主题: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
>
>
>
>+1 (binding)
>
>On Thursday, October 15, 2015, Luke Han  wrote:
>
>> The Apache Kylin community and project made significant advances during
>>the
>> incubating (from Nov 2014) and
>> believes it is ready to graduate as a top-level project.
>>
>> The Apache Kylin is very active. The PPMC doubled in size (added 6
>> committers and 2 mentors) and
>>  increased diversity in the past year. Released 3 version in the past 6
>> months. There were presentations about Apache Kylin
>> at most of the big conferences of the world (including Strata+Hadoop
>>World
>> London, Hadoop Summit San Jose,
>> ApacheCon EU, Big Data Technology China, Database Technology Conference
>> China) and some meetups (Bay Area,
>> Beijing and one is coming in this weekend in Shanghai), and many talks
>> around the world.
>> The dev mailing list is growing very month, about 500+ topics per month
>> now.
>> The community created 1000+ JIRA tickets, many patches from
>> contributors/committers have been merged into code base.
>>
>> A vote passed unanimously on the dev@ list (27 +1 votes). Please find
>> below
>> references to the graduation preparation artifacts:
>> * discussion on dev list [1]
>> * vote thread [2]
>> * podling name search [3]
>> * incubation status [4]
>> * proposed resolution below
>>
>> We believe Apache Kylin is ready to become a top-level project and if
>>the
>> IPMC agree we will move to a formal vote.
>> There are a few more items to be updated on the project status page and
>> others during the next couple of days.
>>
>>
>> Many thanks to the mentors and the IPMC for the support,
>> Luke Han (on behalf of the Apache Kylin PPMC)
>>
>> [1] http://s.apache.org/KylinDisGraduate
>> [2] http://s.apache.org/KylinGraduateVote
>> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-86
>> [4] http://incubator.apache.org/projects/kylin.html
>>
>>
>>
>> Apache Kylin top-level project resolution:
>> ===
>>
>>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, relative to distributed and scalable OLAP engine
>>
>>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>Committee (PMC), to be known as the "Apache Kylin Project",
>>be and hereby is established pursuant to Bylaws of the
>>Foundation; and be it further
>>
>>RESOLVED, that the Apache Kylin Project be and hereby is
>>responsible for the creation and maintenance of open-source
>>software related to distributed and scalable OLAP engine;
>>and be it further
>>
>>RESOLVED, that the office of "Vice President, Kylin" 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 Kylin Project, and to have primary responsibility for
>>management of the projects within the scope of responsibility
>>of the Apache Kylin 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 Kylin Project:
>>
>> * Dayue Gao 
>> * Jason Zhong 
>> * Julian Hyde 
>> * Luke Han 
>> * Henry Saputra 
>> * Hongbin Ma 
>> * Hua Huang 
>> * Owen O'Malley 
>> * P. Taylor Goetz 
>> * Qianhao Zhou 
>> * Shaofeng Shi 
>> * Song Yi 
>> * Ted Dunning 
>> * Xu Jiang 
>> * Yang Li 
>> * Yerui Sun < sunyerui at apache dot org>
>>
>>
>>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luke Han
>>be appointed to the office of Vice President,Apache Kylin, 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 Kylin Project be and hereby
>>is tasked with the creation of a set of bylaws intended to
>>encourage open development and increased participation in the
>>Kylin Project; and be it further
>>
>>RESOLVED, that the initial Apache Kylin Project be and hereby

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Hao Chen]

+1 (Non Binding)

Hao Chen

> On Oct 21, 2015, at 9:17 AM, Chun, Chad  wrote:
> 
> +1
> 
> Chad Chun
> wp_c...@hotmail.com
> 
>> On 10/16/15, 4:22 PM, "½¯Ðñ"  wrote:
>> 
>> +1
>> Jiang Xu
>> -- ԭʼÓʼþ --
>> ·¢¼þÈË: "Henry Saputra";;
>> ·¢ËÍʱ¼ä: 2015Äê10ÔÂ16ÈÕ(ÐÇÆÚÎå) ÉÏÎç9:16
>> ÊÕ¼þÈË: "general@incubator.apache.org";
>> 
>> Ö÷Ìâ: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator
>> 
>> 
>> 
>> +1 (binding)
>> 
>>> On Thursday, October 15, 2015, Luke Han  wrote:
>>> 
>>> The Apache Kylin community and project made significant advances during
>>> the
>>> incubating (from Nov 2014) and
>>> believes it is ready to graduate as a top-level project.
>>> 
>>> The Apache Kylin is very active. The PPMC doubled in size (added 6
>>> committers and 2 mentors) and
>>> increased diversity in the past year. Released 3 version in the past 6
>>> months. There were presentations about Apache Kylin
>>> at most of the big conferences of the world (including Strata+Hadoop
>>> World
>>> London, Hadoop Summit San Jose,
>>> ApacheCon EU, Big Data Technology China, Database Technology Conference
>>> China) and some meetups (Bay Area,
>>> Beijing and one is coming in this weekend in Shanghai), and many talks
>>> around the world.
>>> The dev mailing list is growing very month, about 500+ topics per month
>>> now.
>>> The community created 1000+ JIRA tickets, many patches from
>>> contributors/committers have been merged into code base.
>>> 
>>> A vote passed unanimously on the dev@ list (27 +1 votes). Please find
>>> below
>>> references to the graduation preparation artifacts:
>>> * discussion on dev list [1]
>>> * vote thread [2]
>>> * podling name search [3]
>>> * incubation status [4]
>>> * proposed resolution below
>>> 
>>> We believe Apache Kylin is ready to become a top-level project and if
>>> the
>>> IPMC agree we will move to a formal vote.
>>> There are a few more items to be updated on the project status page and
>>> others during the next couple of days.
>>> 
>>> 
>>> Many thanks to the mentors and the IPMC for the support,
>>> Luke Han (on behalf of the Apache Kylin PPMC)
>>> 
>>> [1] http://s.apache.org/KylinDisGraduate
>>> [2] http://s.apache.org/KylinGraduateVote
>>> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-86
>>> [4] http://incubator.apache.org/projects/kylin.html
>>> 
>>> 
>>> 
>>> Apache Kylin top-level project resolution:
>>> ===
>>> 
>>>   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, relative to distributed and scalable OLAP engine
>>> 
>>>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>>   Committee (PMC), to be known as the "Apache Kylin Project",
>>>   be and hereby is established pursuant to Bylaws of the
>>>   Foundation; and be it further
>>> 
>>>   RESOLVED, that the Apache Kylin Project be and hereby is
>>>   responsible for the creation and maintenance of open-source
>>>   software related to distributed and scalable OLAP engine;
>>>   and be it further
>>> 
>>>   RESOLVED, that the office of "Vice President, Kylin" 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 Kylin Project, and to have primary responsibility for
>>>   management of the projects within the scope of responsibility
>>>   of the Apache Kylin 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 Kylin Project:
>>> 
>>>* Dayue Gao 
>>>* Jason Zhong 
>>>* Julian Hyde 
>>>* Luke Han 
>>>* Henry Saputra 
>>>* Hongbin Ma 
>>>* Hua Huang 
>>>* Owen O'Malley 
>>>* P. Taylor Goetz 
>>>* Qianhao Zhou 
>>>* Shaofeng Shi 
>>>* Song Yi 
>>>* Ted Dunning 
>>>* Xu Jiang 
>>>* Yang Li 
>>>* Yerui Sun < sunyerui at apache dot org>
>>> 
>>> 
>>>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luke Han
>>>   be appointed to the office of Vice President,Apache Kylin, 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 Kylin Project be and hereby
>>> 

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Luke Han]

SGA has confirmed and sent to secretary already.

kylin.xml also updated with correct date.

I think it's ok to announce graduation once ASF confirmed this SGA.

Thanks.

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Bertrand Delacretaz]

On Wed, Oct 21, 2015 at 2:05 PM, Luke Han  wrote:
> ...I think it's ok to announce graduation once ASF confirmed this SGA...

The next step is not announcing graduation, it's sending the
graduation request to the ASF Board for approval.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

[Luke Han]

Thanks Bertrand to kindly remind this:)

I should use send out "vote result" instead of "announce".

Thanks.


Best Regards!
-

Luke Han

On Wed, Oct 21, 2015 at 8:08 PM, Bertrand Delacretaz  wrote:

> On Wed, Oct 21, 2015 at 2:05 PM, Luke Han  wrote:
> > ...I think it's ok to announce graduation once ASF confirmed this SGA...
>
> The next step is not announcing graduation, it's sending the
> graduation request to the ASF Board for approval.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Draft Report October 2015 - please review

[John D. Ament]

I do see one error, possibly not a big deal.  Romain added the BatchEE
podling's report on 10/13, but never updated the other sections to reflect
that the podling did report.  Perhaps this was intentional.

FWIW, Romain is not listed as a mentor at
http://incubator.apache.org/projects/batchee.html but could easily become
one.  He's already an IPMC member.  I'm not sure if we count the report or
not in this case.  In addition, the report is a bit sparse.

On a separate topic, I consider BatchEE to be a mature enough podling.
Mature in the sense that continued incubation isn't going to provide the
podling further value, they understand the ASF.  Their issues seem more
technical than procedural.  It's hard to attract contributors to a JSR
implementation, most people I know cannot distinguish between the
application server and the components that make it up.

John



On Wed, Oct 21, 2015 at 1:46 AM Ted Dunning  wrote:

> filed.
>
> Will sned to mailing list now.
>
>
>
> On Tue, Oct 20, 2015 at 8:56 AM, Ted Dunning 
> wrote:
>
> >
> > I will file shortly.
> >
> > On Tue, Oct 20, 2015 at 5:15 AM, Bertrand Delacretaz <
> > bdelacre...@apache.org> wrote:
> >
> >> On Tue, Oct 20, 2015 at 1:26 PM, Marvin Humphrey <
> mar...@rectangular.com>
> >> wrote:
> >> > ...Ted has certainly earned his money there this month
> >>
> >> Definitely - there was nothing hidden behind my comment, it's just
> >> that it's good to make sure the report is filed in time for the board
> >> meeting (and I'm your shepherd this month, for the board report).
> >>
> >> -Bertrand
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
>