RE: When podlings don't file a report

[Ross Gardler]

Your reply is fine, except that your original question was about what happens 
when “If it turns out that the Mentors have been reminding the podling to file 
but nobody's followed through”

In other words mentors have already said “I’m on it” and have already tried to 
fix the problem. Your reply to my solution is addressing a step before that.



Sent from Mail for Windows 10





From: Marvin Humphrey
Sent: Wednesday, October 21, 2015 5:57 PM
To: general@incubator.apache.org
Subject: Re: When podlings don't file a report


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: Not just yet (was: [VOTE] Graduate Apache Brooklyn from incubator)

[Bertrand Delacretaz]

On Thu, Oct 22, 2015 at 4:43 AM, John D. Ament  wrote:
> Any reason you need 4 weeks to add the paragraph back?..

4 weeks is to get the board to vote on the resolution - our meeting
was yesterday and the next one is on November 18.

As Hadrian says, It is unfortunate that nobody caught that, we noticed
the issue right when we were about to vote on it and there was no time
to properly fix that during the board meeting.

-Bertrand

-
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)

[Henry Saputra]

Jason,

You need to update the LICENSE file for Kylin to include the one for AdminLTE.

I will reopen the JIRA to reflect this.

- Henry

On Thu, Oct 22, 2015 at 3:56 AM, Justin Mclean  wrote:
> Hi,
>
>> But this should not a block issue for release.
>
> My +0 doesn’t block the release, you only need 3 +1 votes.
>
> Normally I would of asked to fix in next release and probably voted +1 as 
> it’s likely they are Apache comparable licences, but this issue has occurred 
> before and there's a vote on graduation so it’s IMO important that this is 
> fixed.
>
> The JIRA with this issue [1] has be marked as “fixed” when the LICENSE file 
> has not been updated.
>
> So for that I will change my vote, it’s  now -1 (binding). You still have 
> enough +1 votes to still make a release but I suggest you actually fix this 
> issue by adding the required bits to LICENSE as described here. [2][3] Assume 
> that is the fonts are actually permissibly  licensed, which is currently 
> unclear.
>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/browse/KYLIN-999
> 2. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> 3. http://www.apache.org/dev/licensing-howto.html#permissive-deps
>

-
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

[Bertrand Delacretaz]

On Thu, Oct 22, 2015 at 3:43 AM, Luke Han  wrote:
> Just got SGA confirmation from ASF as below...

Confirmed, +1 for graduation then.

-Bertrand

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

Re: [DISCUSS] Eagle incubator proposal

[Luke Han]

Thanks Henry, I'm also happy to help Eagle for incubating, the experience
we have
learnt during Kylin's incubating will share to Eagle team and community.

Sign off reports and vote for release is not only things mentors will help,
for the process, setup, policy, infrastructure, guidance, workflow, the
Apache Way and
so on...a lots of things require mentor's efforts, several active mentors
are really important
for new podling committers to learn and practices in their daily work,

We have got help from our mentors very much, hope such experience from
Kylin will also
benefits Eagle even other project.


Thanks.





Best Regards!
-

Luke Han

On Thu, Oct 22, 2015 at 1:16 PM, Greg Stein  wrote:

> 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: Short form IP clearance

[Jim Jagielski]

First and foremost, I have not followed this thread almost at
all. I've been at ATO2015 and then traveling.

What I will say, whether it has been said or not, that
as VP Legal, I will work w/ the Incubator on whatever issues
or questions they may have. If it's time for a conversation
between VP Legal and Incubator re: IP clearance, one that
has not happened for at least a decade, iirc, then I am
fine with that as well and am ready to do so.

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

Re: [DISCUSS] Eagle incubator proposal

[larry mccay]

Arun -

This is a very interesting proposal and I can imagine at least a couple
ways that it and Apache Knox could work together.
I would like to be a contributor to Eagle as well - if you are interested.

I am a committer and PMC member on Knox and Ranger and have contributed to
a number of ecosystem projects on security issues.

Good luck!

--larry

On Thu, Oct 22, 2015 at 4:27 AM, Luke Han  wrote:

> Thanks Henry, I'm also happy to help Eagle for incubating, the experience
> we have
> learnt during Kylin's incubating will share to Eagle team and community.
>
> Sign off reports and vote for release is not only things mentors will help,
> for the process, setup, policy, infrastructure, guidance, workflow, the
> Apache Way and
> so on...a lots of things require mentor's efforts, several active mentors
> are really important
> for new podling committers to learn and practices in their daily work,
>
> We have got help from our mentors very much, hope such experience from
> Kylin will also
> benefits Eagle even other project.
>
>
> Thanks.
>
>
>
>
>
> Best Regards!
> -
>
> Luke Han
>
> On Thu, Oct 22, 2015 at 1:16 PM, Greg Stein  wrote:
>
> > 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: [DISCUSS] Eagle incubator proposal

[Manoharan, Arun]

Thanks Larry. We have some ideas for integration with Ranger and would
love to get your inputs.


On 10/22/15, 4:55 AM, "larry mccay"  wrote:

>Arun -
>
>This is a very interesting proposal and I can imagine at least a couple
>ways that it and Apache Knox could work together.
>I would like to be a contributor to Eagle as well - if you are interested.
>
>I am a committer and PMC member on Knox and Ranger and have contributed to
>a number of ecosystem projects on security issues.
>
>Good luck!
>
>--larry
>
>On Thu, Oct 22, 2015 at 4:27 AM, Luke Han  wrote:
>
>> Thanks Henry, I'm also happy to help Eagle for incubating, the
>>experience
>> we have
>> learnt during Kylin's incubating will share to Eagle team and community.
>>
>> Sign off reports and vote for release is not only things mentors will
>>help,
>> for the process, setup, policy, infrastructure, guidance, workflow, the
>> Apache Way and
>> so on...a lots of things require mentor's efforts, several active
>>mentors
>> are really important
>> for new podling committers to learn and practices in their daily work,
>>
>> We have got help from our mentors very much, hope such experience from
>> Kylin will also
>> benefits Eagle even other project.
>>
>>
>> Thanks.
>>
>>
>>
>>
>>
>> Best Regards!
>> -
>>
>> Luke Han
>>
>> On Thu, Oct 22, 2015 at 1:16 PM, Greg Stein  wrote:
>>
>> > 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
>>;-)
>> >
>>


-
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,

> But this should not a block issue for release.

My +0 doesn’t block the release, you only need 3 +1 votes.

Normally I would of asked to fix in next release and probably voted +1 as it’s 
likely they are Apache comparable licences, but this issue has occurred before 
and there's a vote on graduation so it’s IMO important that this is fixed.

The JIRA with this issue [1] has be marked as “fixed” when the LICENSE file has 
not been updated.

So for that I will change my vote, it’s  now -1 (binding). You still have 
enough +1 votes to still make a release but I suggest you actually fix this 
issue by adding the required bits to LICENSE as described here. [2][3] Assume 
that is the fonts are actually permissibly  licensed, which is currently 
unclear.

Thanks,
Justin

1. https://issues.apache.org/jira/browse/KYLIN-999
2. http://www.apache.org/dev/licensing-howto.html#guiding-principle
3. http://www.apache.org/dev/licensing-howto.html#permissive-deps

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

[John D. Ament]

Ah ha.  It wasn't clear from the original email this happened during the
board meeting.  Now I get it.
On Oct 21, 2015 23:09, "Marvin Humphrey"  wrote:

> 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: Not just yet

[Hadrian Zbarcea]

For the curious and conspiracy theorists :) let me complete the picture.

I did actually attend the board meeting as I usually do and the board 
was gracious enough to give me a couple of minutes to correct the 
resolution. Unfortunately, whimsy wouldn't save the corrected 
resolution, for a reason I don't yet understand. I went a second round 
with svn, but ran out of time.


Looks like I got the graduation gods really angry. This is not what a 
podling should expect from an ASF member.


Hadrian

On 10/22/2015 07:03 AM, John D. Ament wrote:

Ah ha.  It wasn't clear from the original email this happened during the
board meeting.  Now I get it.
On Oct 21, 2015 23:09, "Marvin Humphrey"  wrote:


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






-
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,

> You need to update the LICENSE file for Kylin to include the one for AdminLTE.

The files in question are not part of  AdminLTE [1] that I can see. Even if 
they were they would have different copyright owners and a different LICENCE to 
AdminLTE. An educated guess is that they are the Source San Pro font and that 
is copyright Adobe and license under the SIL Open Font License [2]. It would be 
best to double check the font metadata in the files as that usually includes 
their licensing information.

Thanks,
Justin

1. https://github.com/almasaeed2010/AdminLTE
2. http://www.fontsquirrel.com/license/source-sans-pro
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP Clearance] Alibaba JStorm

[P. Taylor Goetz]

Apache Storm has received a code donation for Alibaba JStorm:

http://incubator.apache.org/ip-clearance/storm-jstorm.html

The source code can be found at https://github.com/alibaba/jstorm with the 
following git commit SHA: e935da91a897797dad56e24c4ffa57860ac91878

Please vote to approve this contribution. Lazy consensus applies. If no -1
votes are cast within the next 72 hours, the vote passes.

Regards,

-Taylor


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Short form IP clearance

[Greg Stein]

On Thu, Oct 22, 2015 at 6:45 AM, Jim Jagielski  wrote:

> First and foremost, I have not followed this thread almost at
> all. I've been at ATO2015 and then traveling.
>
> What I will say, whether it has been said or not, that
> as VP Legal, I will work w/ the Incubator on whatever issues
> or questions they may have. If it's time for a conversation
> between VP Legal and Incubator re: IP clearance, one that
> has not happened for at least a decade, iirc, then I am
> fine with that as well and am ready to do so.


Please read the thread: it contains my part of that conversation that I
think needs to happen.

Thx,
-g

Re: Short form IP clearance

[Sam Ruby]

On Thu, Oct 22, 2015 at 5:37 PM, Greg Stein  wrote:
> On Thu, Oct 22, 2015 at 6:45 AM, Jim Jagielski  wrote:
>
>> First and foremost, I have not followed this thread almost at
>> all. I've been at ATO2015 and then traveling.
>>
>> What I will say, whether it has been said or not, that
>> as VP Legal, I will work w/ the Incubator on whatever issues
>> or questions they may have. If it's time for a conversation
>> between VP Legal and Incubator re: IP clearance, one that
>> has not happened for at least a decade, iirc, then I am
>> fine with that as well and am ready to do so.
>
> Please read the thread: it contains my part of that conversation that I
> think needs to happen.

I'll summarize my position as situations requiring special IP
Clearance procedures (i.e., not a simple patch or even a committer
making a huge change, but events such as bulk importing code that was
previously hosted publicly elsewhere) are infrequent enough events and
important enough risks that having a second set of eyes (from outside
of the receiving PMC) is in order.  I don't have a strong opinion as
to whether IP Clearance for podlings and PMCs should be managed
separately or together.  As long as it continues to be done via lazy
consensus, I also don't see burden.

> Thx,
> -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

[P. Taylor Goetz]

Again my apologies for polluting this thread with tangential thoughts.

Maybe I should start a new thread: "Is IP Clearance Optional?"

My point is that some projects seem to be diligent, while others do not -- to 
the point that at times the IP Clearance process seems optional. I would expect 
the incubator ip clearance list to be a lot longer than it is, and have more 
entries especially from some big data projects that accept some very large 
"patches."

I may be overly cautious, but it seems like there are some important legal 
concerns that are being overlooked.

And I'm not trying to create more work for whatever ASF entity is charged with 
policing the process. ;)

-Taylor

> On Oct 22, 2015, at 12:29 AM, Greg Stein  wrote:
> 
>> 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

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

Re: [DISCUSS] Eagle incubator proposal

[Henry Saputra]

Looks like the discussion has calm down, so unless there is more
comments we will send VOTE thread tomorrow.

Thanks all for the feedback.

- Henry

On Mon, Oct 19, 2015 at 8: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 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 event schema including what 
> attributes constitute an event, what is the type for each attribute, and how 
> to dynamically resolve attribute value in runtime when user configures 
> policy. Scalable policy engine framework allows policies to be executed on 
> different physical nodes in parallel. It is also used to define your own 
> policy partitioner class. Policy engine framework together with streaming 
> partitioning capability provided by all streaming platforms will make sure 
> policies and events can be evaluated in a fully distributed way. Extensible 
> policy engine framework allows developer to plugin a new policy engine with a 
> few lines of codes. WSO2 Siddhi CEP engine is the policy engine which Eagle 
> supports as first-class citizen.
> Machine Learning module: Eagle provides capabilities to define user activity 
> patterns or user profiles for Hadoop users based on the user behaviour in the 
> platform. These user 

Re: [DISCUSS] Eagle incubator proposal

[Henry Saputra]

Looks like the discussion has calm down, so unless there is more
comments we will send VOTE thread tomorrow.

Thanks all for the feedback.

- Henry

On Mon, Oct 19, 2015 at 8: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 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 event schema including what 
> attributes constitute an event, what is the type for each attribute, and how 
> to dynamically resolve attribute value in runtime when user configures 
> policy. Scalable policy engine framework allows policies to be executed on 
> different physical nodes in parallel. It is also used to define your own 
> policy partitioner class. Policy engine framework together with streaming 
> partitioning capability provided by all streaming platforms will make sure 
> policies and events can be evaluated in a fully distributed way. Extensible 
> policy engine framework allows developer to plugin a new policy engine with a 
> few lines of codes. WSO2 Siddhi CEP engine is the policy engine which Eagle 
> supports as first-class citizen.
> Machine Learning module: Eagle provides capabilities to define user activity 
> patterns or user profiles for Hadoop users based on the user behaviour in the 
> platform. These user 

Re: [DISCUSS] Eagle incubator proposal

[P. Taylor Goetz]

+1 for moving forward with a VOTE.

> On Oct 22, 2015, at 7:26 PM, Henry Saputra  wrote:
> 
> Looks like the discussion has calm down, so unless there is more
> comments we will send VOTE thread tomorrow.
> 
> Thanks all for the feedback.
> 
> - Henry
> 
>> On Mon, Oct 19, 2015 at 8: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 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 event schema including what 
>> attributes constitute an event, what is the type for each attribute, and how 
>> to dynamically resolve attribute value in runtime when user configures 
>> policy. Scalable policy engine framework allows policies to be executed on 
>> different physical nodes in parallel. It is also used to define your own 
>> policy partitioner class. Policy engine framework together with streaming 
>> partitioning capability provided by all streaming platforms will make sure 
>> policies and events can be evaluated in a fully distributed way. Extensible 
>> policy engine framework allows developer to plugin a new policy engine with 
>> a few lines of codes. WSO2 Siddhi CEP engine is the policy 

Re: When podlings don't file a report

[Ted Dunning]

On Wed, Oct 21, 2015 at 11:01 PM, Ross Gardler 
wrote:

> Your reply is fine, except that your original question was about what
> happens when “If it turns out that the Mentors have been reminding the
> podling to file but nobody's followed through”
>
> In other words mentors have already said “I’m on it” and have already
> tried to fix the problem. Your reply to my solution is addressing a step
> before that.
>
>
At that point, I think that the IPMC chair or delegate should be stepping
in and evaluating the situation.

These cases are very likely candidates for withdrawal in my book because
either

1) the community has dissipated beyond ability to act

or

2) the community has little or no interest in responding

The exceptional case is that the podling leader needs replacement.

These should be more unusual than they are, but it definitely happens.

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

[Ted Dunning]

Indeed, if Hadrian had succeeded in editing during the meeting, it would
have been fixed right then. Murphy weighed in and we have a 4 week delay.



On Thu, Oct 22, 2015 at 4:03 AM, John D. Ament 
wrote:

> Ah ha.  It wasn't clear from the original email this happened during the
> board meeting.  Now I get it.
> On Oct 21, 2015 23:09, "Marvin Humphrey"  wrote:
>
> > 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: [IP Clearance] Alibaba JStorm

[Luke Han]

Finally JStorm is coming:)

There are many discussion between my friends and local community in China
about JStorm/Storm, people are really would like to have them together.
I think this is great milestone to have more contribution from big giant
from China market (even the biggest in the world;-)

+1 (non-binding)




Best Regards!
-

Luke Han

On Fri, Oct 23, 2015 at 8:19 AM, Amol Kekre  wrote:

> +1 (non-binding)
>
> Amol
>
>
> On Thu, Oct 22, 2015 at 1:13 PM, P. Taylor Goetz 
> wrote:
>
> > Apache Storm has received a code donation for Alibaba JStorm:
> >
> > http://incubator.apache.org/ip-clearance/storm-jstorm.html
> >
> > The source code can be found at https://github.com/alibaba/jstorm with
> > the following git commit SHA: e935da91a897797dad56e24c4ffa57860ac91878
> >
> > Please vote to approve this contribution. Lazy consensus applies. If no
> -1
> > votes are cast within the next 72 hours, the vote passes.
> >
> > Regards,
> >
> > -Taylor
> >
>

Re: Short form IP clearance

[Greg Stein]

It certainly is not optional, and it would be very unfortunate if TLPs
thought so or are unaware. One of the reasons I'd prefer Legal to be the
clear owner. (But to be clear, that is separate from my original post)
On Oct 22, 2015 6:13 PM, "P. Taylor Goetz"  wrote:

> Again my apologies for polluting this thread with tangential thoughts.
>
> Maybe I should start a new thread: "Is IP Clearance Optional?"
>
> My point is that some projects seem to be diligent, while others do not --
> to the point that at times the IP Clearance process seems optional. I would
> expect the incubator ip clearance list to be a lot longer than it is, and
> have more entries especially from some big data projects that accept some
> very large "patches."
>
> I may be overly cautious, but it seems like there are some important legal
> concerns that are being overlooked.
>
> And I'm not trying to create more work for whatever ASF entity is charged
> with policing the process. ;)
>
> -Taylor
>
> > On Oct 22, 2015, at 12:29 AM, Greg Stein  wrote:
> >
> >> 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
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Not just yet

[Ted Dunning]

Indeed, the month delay in consideration is exactly an opportunity to
correct the resolutions technical defects.



On Thu, Oct 22, 2015 at 8:27 AM, Hadrian Zbarcea  wrote:

> Hi John,
>
> I was a reply to your message, but it was not pointed at you. Seriously.
> Maybe the "curious" part a bit, because you asked. We know however from
> experience that there are many other people who are curious what happens
> when unusual events like this take place and even a few, as I called them
> "conspiracy theorists".
>
> Normally I wouldn't write such a reply, but I wanted to take the
> opportunity to also point the positive (because the negatives are so often
> debated at length), which is the fact that board actually was accommodating
> and offered the opportunity for correction. Just to paint a clearer picture
> of the *people* behind board@.
>
> So concerns like the ones you raised are, from my point of view, very
> welcome. Especially as they come in the right tone. They create
> opportunities for learning for lurkers.
>
> Cheers,
> Hadrian
>
>
>
> On 10/22/2015 11:13 AM, John D. Ament wrote:
>
>> On Oct 22, 2015 8:05 AM, "Hadrian Zbarcea"  wrote:
>>
>>>
>>> For the curious and conspiracy theorists :) let me complete the picture.
>>>
>>> I did actually attend the board meeting as I usually do and the board was
>>>
>> gracious enough to give me a couple of minutes to correct the resolution.
>> Unfortunately, whimsy wouldn't save the corrected resolution, for a reason
>> I don't yet understand. I went a second round with svn, but ran out of
>> time.
>>
>>>
>>> Looks like I got the graduation gods really angry. This is not what a
>>>
>> podling should expect from an ASF member.
>>
>> I'll assume that this was pointed to me.  If your email was clearer I
>> wouldn't have been confused about scope.  I apologize for any concerns
>> this
>> raised.
>>
>> Note that I never said you needed a revote.  It wasn't clear that this
>> came
>> out of the board, in the past when we had failed graduations it never made
>> it back to the incubator.
>>
>>
>>> Hadrian
>>>
>>> On 10/22/2015 07:03 AM, John D. Ament wrote:
>>>

 Ah ha.  It wasn't clear from the original email this happened during the
 board meeting.  Now I get it.
 On Oct 21, 2015 23:09, "Marvin Humphrey" 
 wrote:

 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
>
>
>

>>> -
>>> 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: [IP Clearance] Alibaba JStorm

[Amol Kekre]

+1 (non-binding)

Amol


On Thu, Oct 22, 2015 at 1:13 PM, P. Taylor Goetz  wrote:

> Apache Storm has received a code donation for Alibaba JStorm:
>
> http://incubator.apache.org/ip-clearance/storm-jstorm.html
>
> The source code can be found at https://github.com/alibaba/jstorm with
> the following git commit SHA: e935da91a897797dad56e24c4ffa57860ac91878
>
> Please vote to approve this contribution. Lazy consensus applies. If no -1
> votes are cast within the next 72 hours, the vote passes.
>
> Regards,
>
> -Taylor
>

[ANNOUNCE] Apache AsterixDB 0.8.7-incubating released

[Ian Maxon]

The Apache AsterixDB (incubating) Team is happy to announce the first
release of Apache AsterixDB 0.8.7-incubating and its associated
Hyracks release.

Apache AsterixDB is a Big Data Management System (BDMS) that can
store, index, manage, and query semi-structured data at scale on a
cluster. (Hyracks is its underlying dataflow runtime platform.)

More information about the project can be found at

   https://asterixdb.incubator.apache.org/

The release is available at

   https://asterixdb.incubator.apache.org/download.html

The Apache AsterixDB Team would like to hear from you and welcomes
your comments and contributions.

Thanks,
The Apache AsterixDB Team

--
Apache AsterixDB is an effort undergoing incubation at The Apache
Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.

Re: Not just yet

[Sam Ruby]

On Thu, Oct 22, 2015 at 8:05 AM, Hadrian Zbarcea  wrote:
> For the curious and conspiracy theorists :) let me complete the picture.
>
> I did actually attend the board meeting as I usually do and the board was
> gracious enough to give me a couple of minutes to correct the resolution.
> Unfortunately, whimsy wouldn't save the corrected resolution, for a reason I
> don't yet understand. I went a second round with svn, but ran out of time.

I've opened an issue on the whimsy problem:

https://issues.apache.org/jira/browse/WHIMSY-27

I've also opened another issue that I would appreciate feedback on:

https://issues.apache.org/jira/browse/WHIMSY-28

> Looks like I got the graduation gods really angry. This is not what a
> podling should expect from an ASF member.
>
> Hadrian

- Sam Ruby

> On 10/22/2015 07:03 AM, John D. Ament wrote:
>>
>> Ah ha.  It wasn't clear from the original email this happened during the
>> board meeting.  Now I get it.
>> On Oct 21, 2015 23:09, "Marvin Humphrey"  wrote:
>>
>>> 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
>>>
>>>
>>
>
> -
> 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: [VOTE] Release Apache Kylin 1.1-incubating (rc1)

[Han, Luke]

Thanks Justin,
Will raise another thread to continue discuss this.

Would you mind to change your vote to release this candidate?

Thanks.

发自我的 iPhone

> 在 2015年10月23日，12:56，Justin Mclean  写道：
> 
> Hi,
> 
>> So my question is: Which license should to be declare in downstream of
>> Google Fonts?
> 
> INAL you may want to ask for clarification on legal discuss. 
> 
> I would go with what is in the metadata of the font file as it usually 
> contains the copyright holder and the licensing information, but I’d guess 
> any of the options you suggested is a reasonable way to approach the issue.
> 
> Thanks,
> Justin
> -
> 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: When podlings don't file a report

[Ross Gardler]

+1

Sent from my Windows Phone

From: Ted Dunning
Sent: ‎10/‎22/‎2015 6:10 PM
To: general@incubator.apache.org
Cc: Marvin Humphrey
Subject: Re: When podlings don't file a report

On Wed, Oct 21, 2015 at 11:01 PM, Ross Gardler 
wrote:

> Your reply is fine, except that your original question was about what
> happens when “If it turns out that the Mentors have been reminding the
> podling to file but nobody's followed through”
>
> In other words mentors have already said “I’m on it” and have already
> tried to fix the problem. Your reply to my solution is addressing a step
> before that.
>
>
At that point, I think that the IPMC chair or delegate should be stepping
in and evaluating the situation.

These cases are very likely candidates for withdrawal in my book because
either

1) the community has dissipated beyond ability to act

or

2) the community has little or no interest in responding

The exceptional case is that the podling leader needs replacement.

These should be more unusual than they are, but it definitely happens.

Re: Not just yet

[Greg Stein]

On Oct 22, 2015 9:57 AM, "Sam Ruby"  wrote:
>...
> I've also opened another issue that I would appreciate feedback on:
>
> https://issues.apache.org/jira/browse/WHIMSY-28

Cross-check is nice.

I'd suggest another possibility: a web tool to *add* a template-based
resolution in the first place.

Cheers,
-g

[Result][VOTE] Graduate Apache Kylin from the Apache Incubator

[Luke Han]

The vote for Apache Kylin to become a top-level project has passed
with 27 +1 votes and no 0 or -1 votes.

Thank you everyone for taking the time to review and cast your vote.

We will now prepare a resolution for the next Board meeting.

10 binding:
* Henry Saputra
* Andrew Purtell
* Bertrand Delacretaz
* Julian Hyde
* P. Taylor Goetz
* Ted Dunning
* Edward J. Yoon
* Alexander Bezzubov
* John D. Ament
* Owen O'Malley

17 non-binding:
* Luke Han
* Shaofeng Shi
* Jason Zhong
* Qianhao Zhou
* Dong Li
* Droopy Hu
* Xiaoyong Bai (lostitle)
* Qi Liu (Goroutine)
* Yerui Sun
* Xu Jiang
* Debashis Saha
* Yang Li
* Chad Chun
* Atri Sharma
* Hao Chen
* Eddy Cai
* Naresh Agarwal

Luke


-
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,

> So my question is: Which license should to be declare in downstream of
> Google Fonts?

INAL you may want to ask for clarification on legal discuss. 

I would go with what is in the metadata of the font file as it usually contains 
the copyright holder and the licensing information, but I’d guess any of the 
options you suggested is a reasonable way to approach the issue.

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

Re: Not just yet

[John D. Ament]

Agreed, it would likely make more sense for the entire doc to be a
template, with only a few variables and maybe a single check indicating
they want bylaws or not.

On Thu, Oct 22, 2015 at 10:17 PM Greg Stein  wrote:

> On Oct 22, 2015 9:57 AM, "Sam Ruby"  wrote:
> >...
> > I've also opened another issue that I would appreciate feedback on:
> >
> > https://issues.apache.org/jira/browse/WHIMSY-28
>
> Cross-check is nice.
>
> I'd suggest another possibility: a web tool to *add* a template-based
> resolution in the first place.
>
> Cheers,
> -g
>

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

[Luke Han]

Hi Justin,
  JIRA has been reopened and added information about license.
  Also added Google Fonts and Source Sans Pro license information
  in Apache Kylin's LICENSE file.

  It looks like Google Fonts included Source Sans Pro, and has it's
own license agreement, suppose Google has done such legal stuff already.

  So my question is: Which license should to be declare in downstream
of
Google Fonts?  Is it good enough to only add Google Fonts license, or
should
to add all hierarchy dependencies licenses?

  Would love to have your guide and inputs for this.

  Thank you very much.

Luke














Best Regards!
-

Luke Han

On Fri, Oct 23, 2015 at 5:10 AM, Justin Mclean 
wrote:

> HI,
>
> > You need to update the LICENSE file for Kylin to include the one for
> AdminLTE.
>
> The files in question are not part of  AdminLTE [1] that I can see. Even
> if they were they would have different copyright owners and a different
> LICENCE to AdminLTE. An educated guess is that they are the Source San Pro
> font and that is copyright Adobe and license under the SIL Open Font
> License [2]. It would be best to double check the font metadata in the
> files as that usually includes their licensing information.
>
> Thanks,
> Justin
>
> 1. https://github.com/almasaeed2010/AdminLTE
> 2. http://www.fontsquirrel.com/license/source-sans-pro
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Not just yet

[Alex Heneveld]

Hi Hadrian, All,

We have acquired a lot of familiarity with the challenges of the due 
processes and also their importance.  We in the Brooklyn community 
understand completely and we really appreciate all the assistance we are 
getting.


I suggest we still look to release an 0.9.0 around the beginning of 
November, though it will be called 0.9.0-incubating, and keep our 
fingers crossed for the next board meeting and a non-incubating 0.10.0 
at the start of December.


Best
Alex


On 22/10/2015 13:18, Marvin Humphrey wrote:

On Thu, Oct 22, 2015 at 5:05 AM, Hadrian Zbarcea  wrote:

For the curious and conspiracy theorists :) let me complete the picture.

I did actually attend the board meeting as I usually do and the board was
gracious enough to give me a couple of minutes to correct the resolution.
Unfortunately, whimsy wouldn't save the corrected resolution, for a reason I
don't yet understand. I went a second round with svn, but ran out of time.

Looks like I got the graduation gods really angry. This is not what a
podling should expect from an ASF member.

There were other people who who voted for the graduation
recommendation resolution, yet no reviewer raised any concern.  The
missing paragraph would have been subtle and hard to catch, but it's a
bummer that nobody flagged the conflicting mission statements in two
paragraphs.  The drafter does not bear sole responsibility.

Marvin Humphrey

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




--
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP


This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.


Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.


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

Re: Short form IP clearance

[Marvin Humphrey]

On Thu, Oct 22, 2015 at 4:45 AM, Jim Jagielski  wrote:
> First and foremost, I have not followed this thread almost at
> all. I've been at ATO2015 and then traveling.
>
> What I will say, whether it has been said or not, that
> as VP Legal, I will work w/ the Incubator on whatever issues
> or questions they may have. If it's time for a conversation
> between VP Legal and Incubator re: IP clearance, one that
> has not happened for at least a decade, iirc, then I am
> fine with that as well and am ready to do so.

With my Incubator hat on, I wouldn't mind having the Incubator's role in
non-podling IP-clearance removed -- it's a thankless burden, not a perk.
Removal would concentrate the Incubator's focus a bit more, which would be
helpful.

With my Member hat on, it would be good to explore what happens if the
Incubator's role goes away.  I'm not sure how consistently review actually
happens here, though there is clearly some.  But it's good that the people
preparing the IP Clearance documents have to post to a high-profile list like
general@incubator and run the risk of embarrassing themselves if they royally
screw it up.  Take that threat of scrutiny away and quality will drop.

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)

[Justin Mclean]

Hi,

> Would you mind to change your vote to release this candidate?

You can release it without me changing my vote, there are no veto on releases.

But as you asked and it's been dealt with my vote is +1 (binding).

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

Re: Not just yet

[John D. Ament]

On Oct 22, 2015 8:05 AM, "Hadrian Zbarcea"  wrote:
>
> For the curious and conspiracy theorists :) let me complete the picture.
>
> I did actually attend the board meeting as I usually do and the board was
gracious enough to give me a couple of minutes to correct the resolution.
Unfortunately, whimsy wouldn't save the corrected resolution, for a reason
I don't yet understand. I went a second round with svn, but ran out of time.
>
> Looks like I got the graduation gods really angry. This is not what a
podling should expect from an ASF member.

I'll assume that this was pointed to me.  If your email was clearer I
wouldn't have been confused about scope.  I apologize for any concerns this
raised.

Note that I never said you needed a revote.  It wasn't clear that this came
out of the board, in the past when we had failed graduations it never made
it back to the incubator.

>
> Hadrian
>
> On 10/22/2015 07:03 AM, John D. Ament wrote:
>>
>> Ah ha.  It wasn't clear from the original email this happened during the
>> board meeting.  Now I get it.
>> On Oct 21, 2015 23:09, "Marvin Humphrey"  wrote:
>>
>>> 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
>>>
>>>
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: Not just yet

[Hadrian Zbarcea]

Hi John,

I was a reply to your message, but it was not pointed at you. Seriously. 
Maybe the "curious" part a bit, because you asked. We know however from 
experience that there are many other people who are curious what happens 
when unusual events like this take place and even a few, as I called 
them "conspiracy theorists".


Normally I wouldn't write such a reply, but I wanted to take the 
opportunity to also point the positive (because the negatives are so 
often debated at length), which is the fact that board actually was 
accommodating and offered the opportunity for correction. Just to paint 
a clearer picture of the *people* behind board@.


So concerns like the ones you raised are, from my point of view, very 
welcome. Especially as they come in the right tone. They create 
opportunities for learning for lurkers.


Cheers,
Hadrian


On 10/22/2015 11:13 AM, John D. Ament wrote:

On Oct 22, 2015 8:05 AM, "Hadrian Zbarcea"  wrote:


For the curious and conspiracy theorists :) let me complete the picture.

I did actually attend the board meeting as I usually do and the board was

gracious enough to give me a couple of minutes to correct the resolution.
Unfortunately, whimsy wouldn't save the corrected resolution, for a reason
I don't yet understand. I went a second round with svn, but ran out of time.


Looks like I got the graduation gods really angry. This is not what a

podling should expect from an ASF member.

I'll assume that this was pointed to me.  If your email was clearer I
wouldn't have been confused about scope.  I apologize for any concerns this
raised.

Note that I never said you needed a revote.  It wasn't clear that this came
out of the board, in the past when we had failed graduations it never made
it back to the incubator.



Hadrian

On 10/22/2015 07:03 AM, John D. Ament wrote:


Ah ha.  It wasn't clear from the original email this happened during the
board meeting.  Now I get it.
On Oct 21, 2015 23:09, "Marvin Humphrey"  wrote:


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






-
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