[DISCUSS] Apache Pinot Incubator Proposal

[kishore g]

Hello,

I would like to propose Pinot as an Apache Incubator project. The proposal
is available as a draft at https://wiki.apache.org/incubator/PinotProposal. I
have also included the text of the proposal below.

Any feedback from the community is much appreciated.

Regards,
Kishore G

= Pinot Proposal =

== Abstract ==

Pinot is a distributed columnar storage engine that can ingest data in
real-time and serve analytical queries at low latency. There are two modes
of data ingestion - batch and/or realtime. Batch mode allows users to
generate pinot segments externally using systems such as Hadoop. These
segments can be uploaded into Pinot via simple curl calls. Pinot can ingest
data in near real-time from streaming sources such as Kafka. Data ingested
into Pinot is stored in a columnar format. Pinot provides a SQL like
interface (PQL) that supports filters, aggregations, and group by
operations. It does not support joins by design, in order to guarantee
predictable latency. It leverages other Apache projects such as Zookeeper,
Kafka, and Helix, along with many libraries from the ASF.

== Proposal ==

Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the
development happens at LinkedIn with other contributions from Uber and
Slack. We believe that being a part of Apache Software Foundation will
improve the diversity and help form a strong community around the project.

LinkedIn submits this proposal to donate the code base to Apache Software
Foundation. The code is already under Apache License 2.0.  Code and the
documentation are hosted on Github.
 * Code: http://github.com/linkedin/pinot
 * Documentation: https://github.com/linkedin/pinot/wiki


== Background ==

LinkedIn, similar to other companies, has many applications that provide
rich real-time insights to members and customers (internal and external).
The workload characteristics for these applications vary a lot. Some
internal applications simply need ad-hoc query capabilities with sub-second
to multiple seconds latency. But external site facing applications require
strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple
solutions depending on the workload generated by the application and this
was inefficient. Pinot was developed to be the one single platform that
addresses all classes of applications. Today at LinkedIn, Pinot powers more
than 50 site facing products with workload ranging from few queries per
second to 1000’s of queries per second while maintaining the 99th
percentile latency which can be as low as few milliseconds. All internal
dashboards at LinkedIn are powered by Pinot.

== Rationale ==

We believe that requirement to develop rich real-time analytic applications
is applicable to other organizations. Both Pinot and the interested
communities would benefit from this work being openly available.

== Current Status ==

Pinot is currently open sourced under the Apache License Version 2.0 and
available at github.com/linkedin/pinot. All the development is done using
GitHub Pull Requests. We cut releases on a weekly basis and deploy it at
LinkedIn. mp-0.1.468 is the latest release tag that is deployed in
production.

== Meritocracy ==

Following the Apache meritocracy model, we intend to build an open and
diverse community around Pinot. We will encourage the community to
contribute to discussion and codebase.

== Community ==

Pinot is currently used extensively at LinkedIn and Uber. Several companies
have expressed interest in the project. We hope to extend the contributor
base significantly by bringing Pinot into Apache.

== Core Developers ==

Pinot was started by engineers at LinkedIn, and now has committers from
Uber.

== Alignment ==

Apache is the most natural home for taking Pinot forward. Pinot leverages
several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro.
As Pinot gains adoption, we plan to add support for the ORC and Parquet
formats, as well as adding integration with Yarn and Mesos.

== Known Risks ==

=== Orphaned Products ===

The risk of the Pinot project being abandoned is minimal. The teams at
LinkedIn and Uber are highly incentivized to continue development of Pinot
as it is a critical part of their infrastructure.

=== Inexperience with Open Source ===

Post open sourcing, Pinot was completely developed on GitHub. All the
current developers on Pinot are well aware of the open source development
process. However, most of the developers are new to the Apache process.
Kishore Gopalakrishna, one of the lead developers in Pinot, is VP and
committer of the Apache Helix project.

=== Homogenous Developers ===

The current core developers are all from LinkedIn and Uber. However, we
hope to establish a developer community that includes contributors from
several corporations and we are actively encouraging new contributors via
the mailing lists and public presentations of Pinot.

=== Reliance on Salaried Developers ===

It is expected that Pinot development will occur on

Re: Thoughts on Trademarks / Existing Domains on Podling Proposals / Reports

[Mark Thomas]

On 12/02/18 23:24, Dave Fisher wrote:
> Hi -
> 
> I think that the Incubator should adjust the proposal process when a project 
> comes in that has registered trademarks.
> 
> There are a few impacts to consider some of which may need to be private.
> 
> (1) PODLINGNAMESEARCH may not be needed.

Maybe. I'm not so sure. The view of the ASF as to what is an acceptable
name in terms of potential conflicts with other products may be
different to the entity that registered the mark. For example:

- the registering entity may have considered a narrower geographic area
  whereas the ASF tends to look globally;

- there may have been a conflict that was acceptable to the registering
  entity that would not be acceptable to the ASF.

I think we probably need to keep this.

> (2) The IPMC and trademarks@ should want to understand what will need to be 
> transferred and what the timing of the transfer(s) will be - either during 
> onboarding or at graduation. We should be clear about what happens to the 
> trademark if Incubation fails either with or without a release.

As far as I am aware the standard process is to transfer them prior to
graduation and that this is a required step before graduation. There is
normally a clause in the transfer agreement to the effect that if
graduation fails, the transfer doesn't happen.

> (3) Existing domains are also something that should be on a proposal along 
> with if these need to be continued or should be redirected. We need to be 
> clear about what happens to domains if incubation fails.

My expectation is that these would be treated the same way as
trademarks. Generally, we would redirect but of there are a lot of them
we might opt to let some lapse.

> (4) I think these items would add some additional sections to the podling 
> report.

Do you mean adding a brand section?

What about an additional section on the proposal template? Or would it
make more sense under 'Source and Intellectual Property Submission
Plan'? Maybe call out in the template that this is the place to list
trademarks, domains, etc.

Mark

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

[RESULT][VOTE] Release Apache Hivemall (Incubating) v0.5.0-RC2

[Makoto Yui]

Hi everyone,

The 0.5.0-RC2 vote failed with -1 binding votes.

-1 votes (binding) and reasons:
Justin Mclean - unexpended binary in source release

Vote thread:
https://lists.apache.org/thread.html/33eed30795cc211791ec93a48786ee3f9d8c0961896b9e731476ee9b@%3Cgeneral.incubator.apache.org%3E

We'll prepare another release candidate (RC3) resolving unexpended binary
and Copyright issues.

Best,
Makoto

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

[RESULT] [IP CLEARANCE] Apache RocketMQ - RocketMQ CPP SDK project donation

[yukon]

Hi all,

The IP Clearance vote is now closed and has passed with three +1 binding
votes, and no -1s or 0s.

Binding +1s: Jim Jagielski, Kevin A. McGrail and Justin Mclean.
non-binding +1s: Longda Feng, Xin Wang, Huxing Zhang and Wang Xin.

We will import the donation code to  RocketMQ repo soon.

Regards,
yukon



On Fri, Feb 9, 2018 at 12:49 PM, Wang Xin  wrote:

> +1
> Xin Wang
> lovep...@hotmail.com
>
>
>
> 在 2018年2月9日，上午10:28，Huxing Zhang mailto:huxi
> n...@apache.org>> 写道：
>
> +1
>
> On Thu, Feb 8, 2018 at 9:41 PM, yukon mailto:yukon
> @apache.org>> wrote:
> Hi all,
>
> Apache RocketMQ has received a donation of RocketMQ CPP SDK.
>
> RocketMQ CPP SDK is a stable, widely used C++ client SDK of Apache
> RocketMQ, for Linux and Windows platform. It supports full features of
> RocketMQ Java client and has played an important role in many distributed
> applications of Alibaba Group.
>
> The IP clearance form can be found here:
>
> http://incubator.apache.org/ip-clearance/rocketmq-cpp-sdk.html
>
> Please vote to approve this contribution. Lazy consensus applies: if
> no -1 votes are cast within the next 72 hours, the vote passes.
>
> Regards,
> yukon
>
> --
> Best Regards！
> Huxing
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org general-unsubscr...@incubator.apache.org>
> For additional commands, e-mail: general-h...@incubator.apache.org general-h...@incubator.apache.org>
>
>
>

Re: Thoughts on Trademarks / Existing Domains on Podling Proposals / Reports

[Shane Curcuru]

Thanks for the excellent question and Mark's thoughtful replies.

Mark Thomas wrote on 2/13/18 4:27 AM:
> On 12/02/18 23:24, Dave Fisher wrote:
>> Hi -
>>
>> I think that the Incubator should adjust the proposal process when a project 
>> comes in that has registered trademarks.
>>
>> There are a few impacts to consider some of which may need to be private.
>>
>> (1) PODLINGNAMESEARCH may not be needed.
> 
> Maybe. I'm not so sure. The view of the ASF as to what is an acceptable
> name in terms of potential conflicts with other products may be
> different to the entity that registered the mark. For example:
> 
> - the registering entity may have considered a narrower geographic area
>   whereas the ASF tends to look globally;
> 
> - there may have been a conflict that was acceptable to the registering
>   entity that would not be acceptable to the ASF.
> 
> I think we probably need to keep this.

Yes, we need to keep PODLINGNAMESEARCH.  It's irresponsible to host a
software project without doing our own due diligence to ensure the name
we plan to use isn't stepping on someone's existing name.

> 
>> (2) The IPMC and trademarks@ should want to understand what will need to be 
>> transferred and what the timing of the transfer(s) will be - either during 
>> onboarding or at graduation. We should be clear about what happens to the 
>> trademark if Incubation fails either with or without a release.
> 
> As far as I am aware the standard process is to transfer them prior to
> graduation and that this is a required step before graduation. There is
> normally a clause in the transfer agreement to the effect that if
> graduation fails, the transfer doesn't happen.

The current *requirement* is that trademark rights are legally
transferred before the board votes for creating the new TLP.

That is purposefully under-specified, because different organizations
donating projects in the past have had different expectations.  Also,
the ASF does not need to do the paperwork until the podling's about to
graduate.  However I'm happy to sign paperwork earlier if the donor
wants to. [1]

> 
>> (3) Existing domains are also something that should be on a proposal along 
>> with if these need to be continued or should be redirected. We need to be 
>> clear about what happens to domains if incubation fails.
> 
> My expectation is that these would be treated the same way as
> trademarks. Generally, we would redirect but of there are a lot of them
> we might opt to let some lapse.

Correct.  If there is a major product user-facing portal, or if there
are domains that are baked into URLs within the code, the ASF would take
them on and maintain them for the life of the project.  We'd also expect
to redirect all of them to the proper project.a.o domain.  Any other
domains we would consider taking for a short term transition period
(just a redirect), but we would let lapse.

Domains are easier to manage than trademarks - they merely require the
transfer code, rather than officer's legal signatures.  But yes, we'd
give them back on a failed graduation if they had been transferred.

> 
>> (4) I think these items would add some additional sections to the podling 
>> report.
> 
> Do you mean adding a brand section?
> 
> What about an additional section on the proposal template? Or would it
> make more sense under 'Source and Intellectual Property Submission
> Plan'? Maybe call out in the template that this is the place to list
> trademarks, domains, etc.

Yes, a podling proposal should have an explicit section that lists:

- Registered trademarks and their owner(s)
- Any domain names the project uses
- Any other brand elements - like logos or alternate brand names - that
the project intends to donate (or, that the project is *not* donating).

Separately, I think it would be a good idea for the podling quarterly
report template to have a section or checkbox that shows their progress
to complying with the project branding policy:

  https://www.apache.org/foundation/marks/pmcs

-- 

- Shane
  https://www.apache.org/foundation/marks/resources

[1] This is a factor of our volunteer-led organization, and the strength
of the APACHE brand.

- Since we rely on volunteers to manage this whole process, the
*requirement* is the minimum the ASF needs: trademark rights for TLPs.
While it would be great to have more detailed process - and volunteers
who can *reliably* and *knowledgeably* work on this as soon as a podling
proposal is accepted, we haven't had that in the past.

- Trademark assignment agreements are mostly boilerplate, and thus, easy
for counsel to review.  Trademark assignments with clawback (i.e.
returning the trademark rights if a podling fails to graduate) are...
unique to the ASF, and take more volunteer time and counsel time to
draft and review.

- From a risk management perspective, waiting until graduation nears to
force the matter is not that bad.  Any organization that has spent the
time and thought to donate a codebase and a bra

[IP CLEARANCE] Apache DeltaSpike InterDyn

[Mark Struberg]

Good afternoon!

I want to start IP CLEARANCE for Apache DeltaSpike InterDyn.

I've moved over code I've developed years ago at 
https://github.com/struberg/interdyn
It ever contained the full ASF headers anyway and is ALv2. 
I'm also the sole author of the code.

This is for inclusion in Apache DeltaSpike where I'm accidentially also PMC 
chair ;)

The filled out form is at 
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/deltaspike-interdyn.xml

The IP CLEARANCE check is open for 72h with lazy consensus.


txs and LieGrue,
strub


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

Re: [VOTE] Release Apache NetBeans 9.0 Beta (incubating) rc3

[Mark Struberg]

I think this is reasonably enough for this release. 

We should keep an eye on it and probably someone can upload a fixed release to 
maven.central.

I've also checked the other parts and found no obvious problem

So 

+1 (binding)


txs and LieGrue,
strub



> Am 13.02.2018 um 08:32 schrieb Geertjan Wielenga 
> :
> 
> Proposed solution is in the issue --
> 
> https://issues.apache.org/jira/browse/LEGAL-361
> 
> https://github.com/apache/incubator-netbeans/pull/421
> 
> Gj
> 
> On Sun, Feb 11, 2018 at 8:55 PM, David Jencks  
> wrote:
>> What happened to
>> LEGAL-361 
>> ?
>> 
>> My impression from this issue is that the previous RC included a binary jar 
>> that was mostly EPL 1.0 but had at least one file that no one knew the 
>> origin, contents, or license of.  I don’t see that any progress has been 
>> made on this issue, has the jar been removed from the new RC?  I just 
>> scanned a couple of the links below but didn’t see any mention of this.
>> 
>> david jencks
>> 
>>> On Feb 9, 2018, at 1:36 PM, Geertjan Wielenga 
>>>  wrote:
>>> 
>>> Hi all,
>>> 
>>> The Apache NetBeans community has voted on and approved a proposal to
>>> release Apache NetBeans 9.0 Beta (incubating) rc3.
>>> 
>>> We now kindly request that the Incubator PMC members review and vote
>>> on this incubator release candidate.
>>> 
>>> Apache NetBeans 9.0 Beta (incubating) constitutes all the modules
>>> currently in the Apache NetBeans Git repo, which together provide the
>>> NetBeans Platform (i.e., the underlying application framework), which
>>> was released as Apache NetBeans 9.0 Alpha (incubating), as well as all
>>> the modules that provide the Java SE-related features of Apache
>>> NetBeans. In short, Apache NetBeans 9.0 Beta (incubating) is a full
>>> IDE for Java SE development.
>>> 
>>> Just like the Alpha release, the Beta release is focused specifically
>>> on IP clearance. With Beta, everything in Apache NetBeans Git complies
>>> with Apache IP clearance requirements:
>>> 
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta
>>> 
>>> Changes between rc1 and rc2 -- binaries wrongly included in source zip
>>> have been removed:
>>> 
>>> https://issues.apache.org/jira/browse/NETBEANS-276
>>> 
>>> Changes between rc2 and rc3 -- problems identified by the rc2 IPMC
>>> vote by IPMC members Justin Mclean and John D. Ament have been solved
>>> or issues have been created:
>>> 
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta+rc3
>>> 
>>> https://lists.apache.org/thread.html/8e9520d5e1e365ed2337940fb629c209c63efae24b0a2e44d50412a3@%3Cgeneral.incubator.apache.org%3E
>>> 
>>> How to try out the Beta release:
>>> 
>>> 1. Download the artifact to be voted on and unzip it.
>>> 2. Build it using the README provided by the artifact.
>>> 3. Look in nbbuild/netbeans for the NetBeans installation created by
>>> the build process.
>>> 4. Run the NetBeans executable and (if you're running on JDK 8) you'll
>>> be prompted to install nb-javac, after agreeing to its licensing
>>> terms, and (if you're running on JDK 9), you'll be able to use javac
>>> directly from JDK 9 and, optionally, you'll be prompted to install
>>> nb-javac, after agreeing to its licensing terms.
>>> 
>>> Take note of the Apache Rat exclusions, which are now in a separate file:
>>> 
>>> https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclusions.txt
>>> 
>>> If the above succeeds, i.e., Apache NetBeans installs and starts up,
>>> you will have a Java SE development environment that complies with
>>> Apache IP requirements.
>>> 
>>> Apache NetBeans 9.0 Beta (incubating) rc3 vote thread:
>>> 
>>> https://lists.apache.org/thread.html/f1c5a2a3077690f2c7785ed81c36f1ba1920efa01b26f3e7a5f32f2b@%3Cdev.netbeans.apache.org%3E
>>> 
>>> Apache NetBeans 9.0 Beta (incubating) vote result thread:
>>> 
>>> https://lists.apache.org/thread.html/079f610360463621276d6d8c99979991bded812559a34eff4458a073@%3Cdev.netbeans.apache.org%3E
>>> 
>>> In the above, note there are two IPMC binding votes from Ate Douma and
>>> Bertrand Delacretaz, both Apache NetBeans (incubating) mentors, and 31
>>> non-binding votes, from PPMC members and others in the Apache NetBeans
>>> community.
>>> 
>>> The source tarball, including signatures, digests, etc., as well as a
>>> convenience binary, can be found at:
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta-rc3/
>>> 
>>> The tag to be voted upon is 9.0-beta-rc3:
>>> 
>>> https://github.com/apache/incubator-netbeans/tree/9.0-beta-rc3
>>> 
>>> https://github.com/apache/incubator-netbeans/releases/tag/9.0-beta-rc3
>>> 
>>> Also note, if tag is not identical:
>>> 
>>> https://lists.apache.org/thread.html/66daa753d25a482efecc5b86fdc00dc31250ca1448b533bfba82a51d@%3Cdev.netbeans.apache.org%3E
>>> 
>>> The release hash is:
>>> 
>>> 96974a6c59957fb3d8ff18b9dd8a9323ddb00968
>>> 

Re: [VOTE] Release Apache NetBeans 9.0 Beta (incubating) rc3

[David Jencks]

Since the pull request was made about 8 hours ago, am I correct in thinking 
that the rc3 candidate still includes the jar with unknown contents and 
provenance?

Mark, how could an EPL 1.0 jar with an AL 2 patch applied be uploaded to maven 
central? For one thing, what would the maven coordinates be?

Thanks
David Jencks 

Sent from my iPhone

> On Feb 13, 2018, at 5:23 AM, Mark Struberg  wrote:
> 
> I think this is reasonably enough for this release. 
> 
> We should keep an eye on it and probably someone can upload a fixed release 
> to maven.central.
> 
> I've also checked the other parts and found no obvious problem
> 
> So 
> 
> +1 (binding)
> 
> 
> txs and LieGrue,
> strub
> 
> 
> 
>> Am 13.02.2018 um 08:32 schrieb Geertjan Wielenga 
>> :
>> 
>> Proposed solution is in the issue --
>> 
>> https://issues.apache.org/jira/browse/LEGAL-361
>> 
>> https://github.com/apache/incubator-netbeans/pull/421
>> 
>> Gj
>> 
>>> On Sun, Feb 11, 2018 at 8:55 PM, David Jencks  
>>> wrote:
>>> What happened to
>>> LEGAL-361 
>>> ?
>>> 
>>> My impression from this issue is that the previous RC included a binary jar 
>>> that was mostly EPL 1.0 but had at least one file that no one knew the 
>>> origin, contents, or license of.  I don’t see that any progress has been 
>>> made on this issue, has the jar been removed from the new RC?  I just 
>>> scanned a couple of the links below but didn’t see any mention of this.
>>> 
>>> david jencks
>>> 
 On Feb 9, 2018, at 1:36 PM, Geertjan Wielenga 
  wrote:
 
 Hi all,
 
 The Apache NetBeans community has voted on and approved a proposal to
 release Apache NetBeans 9.0 Beta (incubating) rc3.
 
 We now kindly request that the Incubator PMC members review and vote
 on this incubator release candidate.
 
 Apache NetBeans 9.0 Beta (incubating) constitutes all the modules
 currently in the Apache NetBeans Git repo, which together provide the
 NetBeans Platform (i.e., the underlying application framework), which
 was released as Apache NetBeans 9.0 Alpha (incubating), as well as all
 the modules that provide the Java SE-related features of Apache
 NetBeans. In short, Apache NetBeans 9.0 Beta (incubating) is a full
 IDE for Java SE development.
 
 Just like the Alpha release, the Beta release is focused specifically
 on IP clearance. With Beta, everything in Apache NetBeans Git complies
 with Apache IP clearance requirements:
 
 https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta
 
 Changes between rc1 and rc2 -- binaries wrongly included in source zip
 have been removed:
 
 https://issues.apache.org/jira/browse/NETBEANS-276
 
 Changes between rc2 and rc3 -- problems identified by the rc2 IPMC
 vote by IPMC members Justin Mclean and John D. Ament have been solved
 or issues have been created:
 
 https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta+rc3
 
 https://lists.apache.org/thread.html/8e9520d5e1e365ed2337940fb629c209c63efae24b0a2e44d50412a3@%3Cgeneral.incubator.apache.org%3E
 
 How to try out the Beta release:
 
 1. Download the artifact to be voted on and unzip it.
 2. Build it using the README provided by the artifact.
 3. Look in nbbuild/netbeans for the NetBeans installation created by
 the build process.
 4. Run the NetBeans executable and (if you're running on JDK 8) you'll
 be prompted to install nb-javac, after agreeing to its licensing
 terms, and (if you're running on JDK 9), you'll be able to use javac
 directly from JDK 9 and, optionally, you'll be prompted to install
 nb-javac, after agreeing to its licensing terms.
 
 Take note of the Apache Rat exclusions, which are now in a separate file:
 
 https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclusions.txt
 
 If the above succeeds, i.e., Apache NetBeans installs and starts up,
 you will have a Java SE development environment that complies with
 Apache IP requirements.
 
 Apache NetBeans 9.0 Beta (incubating) rc3 vote thread:
 
 https://lists.apache.org/thread.html/f1c5a2a3077690f2c7785ed81c36f1ba1920efa01b26f3e7a5f32f2b@%3Cdev.netbeans.apache.org%3E
 
 Apache NetBeans 9.0 Beta (incubating) vote result thread:
 
 https://lists.apache.org/thread.html/079f610360463621276d6d8c99979991bded812559a34eff4458a073@%3Cdev.netbeans.apache.org%3E
 
 In the above, note there are two IPMC binding votes from Ate Douma and
 Bertrand Delacretaz, both Apache NetBeans (incubating) mentors, and 31
 non-binding votes, from PPMC members and others in the Apache NetBeans
 community.
 
 The source tarball, including signatures, digests, etc., as well as a
 convenience binary, can be found at:
 
 https://dist.apache.org/repos/dist

Re: [VOTE] Release Apache NetBeans 9.0 Beta (incubating) rc3

[Mark Struberg]

That's a practical issue and not a legal one I'd say.

But yes, finally I'd suggest to use different maven coordinates in the future 
at least.
Otoh we do not even require that this file is on maven.central. 
Just downloadable form a private http page or on github would be perfectly 
enough FROM A LEGAL POV.

We really have to split the legal stuff from the point of providing 
reproducible artifacts. 
In a long term this would not be from the later aspect. 
But look e.g. at OpenJPA and Geronimo. Over there we use privately released 
serp artifacts since a decade. I'm _not_ happy with that neither and would love 
to switch fully over to ASM for example. But legally it's not a problem.
The same was happening in Maven with the various artifacts hosted at Codehaus 
or Eclipse.
Far from perfect from a community perspective. But LEGALLY it's ok.

So I totally agree that NetBeans has to adress this in the future. But it imo 
doesn't block this release, isn't it?

LieGrue,
strub



> Am 13.02.2018 um 16:51 schrieb David Jencks :
> 
> Since the pull request was made about 8 hours ago, am I correct in thinking 
> that the rc3 candidate still includes the jar with unknown contents and 
> provenance?
> 
> Mark, how could an EPL 1.0 jar with an AL 2 patch applied be uploaded to 
> maven central? For one thing, what would the maven coordinates be?
> 
> Thanks
> David Jencks 
> 
> Sent from my iPhone
> 
>> On Feb 13, 2018, at 5:23 AM, Mark Struberg  wrote:
>> 
>> I think this is reasonably enough for this release. 
>> 
>> We should keep an eye on it and probably someone can upload a fixed release 
>> to maven.central.
>> 
>> I've also checked the other parts and found no obvious problem
>> 
>> So 
>> 
>> +1 (binding)
>> 
>> 
>> txs and LieGrue,
>> strub
>> 
>> 
>> 
>>> Am 13.02.2018 um 08:32 schrieb Geertjan Wielenga 
>>> :
>>> 
>>> Proposed solution is in the issue --
>>> 
>>> https://issues.apache.org/jira/browse/LEGAL-361
>>> 
>>> https://github.com/apache/incubator-netbeans/pull/421
>>> 
>>> Gj
>>> 
 On Sun, Feb 11, 2018 at 8:55 PM, David Jencks  
 wrote:
 What happened to
 LEGAL-361 
 ?
 
 My impression from this issue is that the previous RC included a binary 
 jar that was mostly EPL 1.0 but had at least one file that no one knew the 
 origin, contents, or license of.  I don’t see that any progress has been 
 made on this issue, has the jar been removed from the new RC?  I just 
 scanned a couple of the links below but didn’t see any mention of this.
 
 david jencks
 
> On Feb 9, 2018, at 1:36 PM, Geertjan Wielenga 
>  wrote:
> 
> Hi all,
> 
> The Apache NetBeans community has voted on and approved a proposal to
> release Apache NetBeans 9.0 Beta (incubating) rc3.
> 
> We now kindly request that the Incubator PMC members review and vote
> on this incubator release candidate.
> 
> Apache NetBeans 9.0 Beta (incubating) constitutes all the modules
> currently in the Apache NetBeans Git repo, which together provide the
> NetBeans Platform (i.e., the underlying application framework), which
> was released as Apache NetBeans 9.0 Alpha (incubating), as well as all
> the modules that provide the Java SE-related features of Apache
> NetBeans. In short, Apache NetBeans 9.0 Beta (incubating) is a full
> IDE for Java SE development.
> 
> Just like the Alpha release, the Beta release is focused specifically
> on IP clearance. With Beta, everything in Apache NetBeans Git complies
> with Apache IP clearance requirements:
> 
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta
> 
> Changes between rc1 and rc2 -- binaries wrongly included in source zip
> have been removed:
> 
> https://issues.apache.org/jira/browse/NETBEANS-276
> 
> Changes between rc2 and rc3 -- problems identified by the rc2 IPMC
> vote by IPMC members Justin Mclean and John D. Ament have been solved
> or issues have been created:
> 
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta+rc3
> 
> https://lists.apache.org/thread.html/8e9520d5e1e365ed2337940fb629c209c63efae24b0a2e44d50412a3@%3Cgeneral.incubator.apache.org%3E
> 
> How to try out the Beta release:
> 
> 1. Download the artifact to be voted on and unzip it.
> 2. Build it using the README provided by the artifact.
> 3. Look in nbbuild/netbeans for the NetBeans installation created by
> the build process.
> 4. Run the NetBeans executable and (if you're running on JDK 8) you'll
> be prompted to install nb-javac, after agreeing to its licensing
> terms, and (if you're running on JDK 9), you'll be able to use javac
> directly from JDK 9 and, optionally, you'll be prompted to install
> nb-javac, after agreeing to its licensing terms.
> 
> Take note of t

Re: [IP CLEARANCE] Apache Felix Bundle Archive File Installer Extension

[Karl Pauls]

John,

we have an ICLA for Jessica now.

However, Intel is maintaining the position that it shouldn't be
required to identify the software granted in detail but rather stating
the top-level project it is granted to should be sufficient.
Furthermore, they argue that they have done that many times over the
years and only used the project level in Schedule B.

Personally (IANAL), I think we should be good as the size of the
donation isn't that big, Intel claims the copyright and has clearly
green lighted Jessica to contribute in their name to Felix (and we
have an ICLA as well) - hence:

Are you willing to withdraw your veto based on the ICLA and the given CCLA?

Otherwise, I guess I'll go and ask legal to see if they can clear this up.

regards,

Karl


On Thu, Dec 14, 2017 at 2:41 PM, Karl Pauls  wrote:
> John,
>
> yeah, I see that the schedule B is somewhat lacking. Oh well, ok, so
> basically we are fine with a CCLA but in this case we don't think the
> provided one is explicit enough (plus we want an ICLA for Jessica
> Marz).
>
> I'll let them know and get back to this thread when there is either an
> SGA or a new CCLA with the zip name and hash + ICLA for Jessica.
>
> Thank you for looking into this!
>
> regards,
>
> Karl
>
> On Thu, Dec 14, 2017 at 2:06 PM, John D. Ament  wrote:
>> Karl,
>>
>> I just read the CCLA that was filed.  I do not believe it is clear enough
>> in the schedule B that it contains to conclude what is meant to be
>> included.  Since you're a chair, you should have access to it at
>> https://svn.apache.org/repos/private/documents/cclas/intel-corporation-felix.pdf
>>
>> Typically, to use a schedule B (as you're noting) I would expect:
>>
>> - A zip/tar archive with checksum & md5 listed OR
>> - A list of files
>>
>> As well as:
>>
>> - ICLA(s) on file for the individual(s).
>>
>> So you could also do another CCLA but listing out one of those two items
>> above, as well as request an ICLA from Jessica Marz.
>>
>> John
>>
>> On Thu, Dec 14, 2017 at 7:08 AM Karl Pauls  wrote:
>>
>>> John,
>>>
>>> it might typically be an SGA but it does say: "This grant can either
>>> be done by the ASF Corporate CLA (via Schedule B) or the Software
>>> Grant Agreement". Should we change that wording then?
>>>
>>> Anyways, I will follow-up with Intel via Jessica and let them know
>>> that the provided Corporate CLA isn't sufficient and see if they can
>>> provide a Software Grant Agreement instead. Thanks!
>>>
>>> regards,
>>>
>>> Karl
>>>
>>> On Thu, Dec 14, 2017 at 1:01 PM, John D. Ament 
>>> wrote:
>>> > Karl,
>>> >
>>> > If the code is already Apache licensed, then I would check w/ secretary@
>>> or
>>> > legal-discuss@ to confirm what documents need to be in place to remove
>>> the
>>> > Intel copyright claim (typically those would go in to the NOTICE file for
>>> > Apache Felix going forward).  This is typically done as an SGA [1].
>>> >
>>> > John
>>> >
>>> > [1]: https://www.apache.org/licenses/software-grant-template.pdf
>>> >
>>> > On Thu, Dec 14, 2017 at 6:57 AM Karl Pauls  wrote:
>>> >
>>> >> Hi John,
>>> >>
>>> >> the code has been available as AL with the Intel copyright already
>>> >> (the license headers in the files are unchanged). It is mainly an
>>> >> attempt to get it contributed to Apache Felix. I told them we need the
>>> >> following (from the incubator ip-clearance form):
>>> >>
>>> >> "A software grant must be provided to the ASF. This grant can either
>>> >> be done by the ASF Corporate CLA (via Schedule B) or the Software
>>> >> Grant Agreement. The completed and signed grant must be emailed to
>>> >> secret...@apache.org"
>>> >>
>>> >> Consequently, they send (the received) CCLA which was supposed to
>>> >> cover for that.
>>> >>
>>> >> Apologies if I misunderstood the requirement. Could you please help me
>>> >> out here and list what exactly we need from Intel and/or Jessica to
>>> >> get this done?
>>> >>
>>> >> regards,
>>> >>
>>> >> Karl
>>> >>
>>> >>
>>> >>
>>> >> On Thu, Dec 14, 2017 at 12:48 PM, John D. Ament 
>>> >> wrote:
>>> >> > Karl,
>>> >> >
>>> >> > CCLA [1] is just a document indicating that the corporate entity has
>>> >> given
>>> >> > approval for individuals associated to it to contribute to Apache
>>> under
>>> >> > ICLAs.  It really doesn't provide any legal bearing to relicense code
>>> >> > outside of an ICLA/SGA.
>>> >> >
>>> >> > Usually when projects come to us with an IP clearance, its for a
>>> >> > significant amount of code.  In those scenarios, there's an SGA
>>> >> associated
>>> >> > with the contribution (from a corporate entity) indicating that they
>>> are
>>> >> > licensing the ASF to use the code under the Apache license
>>> (irrespective
>>> >> of
>>> >> > the original license).  I'm assuming that at Intel some # of engineers
>>> >> > contributed to this code, and that it was under a proprietary license
>>> >> until
>>> >> > this JIRA ticket was filed.  In that case, SGA is almost always the
>>> right
>>> >> > document to get signed.

Re: [DISCUSS] Apache Pinot Incubator Proposal

[Abhishek Tiwari]

Pinot is already quite popular and I think it will be an awesome addition
under the Apache umbrella.

+1 (non-binding)

On Tue, Feb 13, 2018 at 12:10 AM, kishore g  wrote:

> Hello,
>
> I would like to propose Pinot as an Apache Incubator project. The proposal
> is available as a draft at https://wiki.apache.org/incubator/PinotProposal.
> I
> have also included the text of the proposal below.
>
> Any feedback from the community is much appreciated.
>
> Regards,
> Kishore G
>
> = Pinot Proposal =
>
> == Abstract ==
>
> Pinot is a distributed columnar storage engine that can ingest data in
> real-time and serve analytical queries at low latency. There are two modes
> of data ingestion - batch and/or realtime. Batch mode allows users to
> generate pinot segments externally using systems such as Hadoop. These
> segments can be uploaded into Pinot via simple curl calls. Pinot can ingest
> data in near real-time from streaming sources such as Kafka. Data ingested
> into Pinot is stored in a columnar format. Pinot provides a SQL like
> interface (PQL) that supports filters, aggregations, and group by
> operations. It does not support joins by design, in order to guarantee
> predictable latency. It leverages other Apache projects such as Zookeeper,
> Kafka, and Helix, along with many libraries from the ASF.
>
> == Proposal ==
>
> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the
> development happens at LinkedIn with other contributions from Uber and
> Slack. We believe that being a part of Apache Software Foundation will
> improve the diversity and help form a strong community around the project.
>
> LinkedIn submits this proposal to donate the code base to Apache Software
> Foundation. The code is already under Apache License 2.0.  Code and the
> documentation are hosted on Github.
>  * Code: http://github.com/linkedin/pinot
>  * Documentation: https://github.com/linkedin/pinot/wiki
>
>
> == Background ==
>
> LinkedIn, similar to other companies, has many applications that provide
> rich real-time insights to members and customers (internal and external).
> The workload characteristics for these applications vary a lot. Some
> internal applications simply need ad-hoc query capabilities with sub-second
> to multiple seconds latency. But external site facing applications require
> strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple
> solutions depending on the workload generated by the application and this
> was inefficient. Pinot was developed to be the one single platform that
> addresses all classes of applications. Today at LinkedIn, Pinot powers more
> than 50 site facing products with workload ranging from few queries per
> second to 1000’s of queries per second while maintaining the 99th
> percentile latency which can be as low as few milliseconds. All internal
> dashboards at LinkedIn are powered by Pinot.
>
> == Rationale ==
>
> We believe that requirement to develop rich real-time analytic applications
> is applicable to other organizations. Both Pinot and the interested
> communities would benefit from this work being openly available.
>
> == Current Status ==
>
> Pinot is currently open sourced under the Apache License Version 2.0 and
> available at github.com/linkedin/pinot. All the development is done using
> GitHub Pull Requests. We cut releases on a weekly basis and deploy it at
> LinkedIn. mp-0.1.468 is the latest release tag that is deployed in
> production.
>
> == Meritocracy ==
>
> Following the Apache meritocracy model, we intend to build an open and
> diverse community around Pinot. We will encourage the community to
> contribute to discussion and codebase.
>
> == Community ==
>
> Pinot is currently used extensively at LinkedIn and Uber. Several companies
> have expressed interest in the project. We hope to extend the contributor
> base significantly by bringing Pinot into Apache.
>
> == Core Developers ==
>
> Pinot was started by engineers at LinkedIn, and now has committers from
> Uber.
>
> == Alignment ==
>
> Apache is the most natural home for taking Pinot forward. Pinot leverages
> several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro.
> As Pinot gains adoption, we plan to add support for the ORC and Parquet
> formats, as well as adding integration with Yarn and Mesos.
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> The risk of the Pinot project being abandoned is minimal. The teams at
> LinkedIn and Uber are highly incentivized to continue development of Pinot
> as it is a critical part of their infrastructure.
>
> === Inexperience with Open Source ===
>
> Post open sourcing, Pinot was completely developed on GitHub. All the
> current developers on Pinot are well aware of the open source development
> process. However, most of the developers are new to the Apache process.
> Kishore Gopalakrishna, one of the lead developers in Pinot, is VP and
> committer of the Apache Helix project.
>
> === Homogenous Developers 

Re: [IP CLEARANCE] Apache Felix Bundle Archive File Installer Extension

[John D. Ament]

Yes, an ICLA on file should suffice.

John

On Tue, Feb 13, 2018 at 5:07 PM Karl Pauls  wrote:

> John,
>
> we have an ICLA for Jessica now.
>
> However, Intel is maintaining the position that it shouldn't be
> required to identify the software granted in detail but rather stating
> the top-level project it is granted to should be sufficient.
> Furthermore, they argue that they have done that many times over the
> years and only used the project level in Schedule B.
>
> Personally (IANAL), I think we should be good as the size of the
> donation isn't that big, Intel claims the copyright and has clearly
> green lighted Jessica to contribute in their name to Felix (and we
> have an ICLA as well) - hence:
>
> Are you willing to withdraw your veto based on the ICLA and the given CCLA?
>
> Otherwise, I guess I'll go and ask legal to see if they can clear this up.
>
> regards,
>
> Karl
>
>
> On Thu, Dec 14, 2017 at 2:41 PM, Karl Pauls  wrote:
> > John,
> >
> > yeah, I see that the schedule B is somewhat lacking. Oh well, ok, so
> > basically we are fine with a CCLA but in this case we don't think the
> > provided one is explicit enough (plus we want an ICLA for Jessica
> > Marz).
> >
> > I'll let them know and get back to this thread when there is either an
> > SGA or a new CCLA with the zip name and hash + ICLA for Jessica.
> >
> > Thank you for looking into this!
> >
> > regards,
> >
> > Karl
> >
> > On Thu, Dec 14, 2017 at 2:06 PM, John D. Ament 
> wrote:
> >> Karl,
> >>
> >> I just read the CCLA that was filed.  I do not believe it is clear
> enough
> >> in the schedule B that it contains to conclude what is meant to be
> >> included.  Since you're a chair, you should have access to it at
> >>
> https://svn.apache.org/repos/private/documents/cclas/intel-corporation-felix.pdf
> >>
> >> Typically, to use a schedule B (as you're noting) I would expect:
> >>
> >> - A zip/tar archive with checksum & md5 listed OR
> >> - A list of files
> >>
> >> As well as:
> >>
> >> - ICLA(s) on file for the individual(s).
> >>
> >> So you could also do another CCLA but listing out one of those two items
> >> above, as well as request an ICLA from Jessica Marz.
> >>
> >> John
> >>
> >> On Thu, Dec 14, 2017 at 7:08 AM Karl Pauls  wrote:
> >>
> >>> John,
> >>>
> >>> it might typically be an SGA but it does say: "This grant can either
> >>> be done by the ASF Corporate CLA (via Schedule B) or the Software
> >>> Grant Agreement". Should we change that wording then?
> >>>
> >>> Anyways, I will follow-up with Intel via Jessica and let them know
> >>> that the provided Corporate CLA isn't sufficient and see if they can
> >>> provide a Software Grant Agreement instead. Thanks!
> >>>
> >>> regards,
> >>>
> >>> Karl
> >>>
> >>> On Thu, Dec 14, 2017 at 1:01 PM, John D. Ament 
> >>> wrote:
> >>> > Karl,
> >>> >
> >>> > If the code is already Apache licensed, then I would check w/
> secretary@
> >>> or
> >>> > legal-discuss@ to confirm what documents need to be in place to
> remove
> >>> the
> >>> > Intel copyright claim (typically those would go in to the NOTICE
> file for
> >>> > Apache Felix going forward).  This is typically done as an SGA [1].
> >>> >
> >>> > John
> >>> >
> >>> > [1]: https://www.apache.org/licenses/software-grant-template.pdf
> >>> >
> >>> > On Thu, Dec 14, 2017 at 6:57 AM Karl Pauls 
> wrote:
> >>> >
> >>> >> Hi John,
> >>> >>
> >>> >> the code has been available as AL with the Intel copyright already
> >>> >> (the license headers in the files are unchanged). It is mainly an
> >>> >> attempt to get it contributed to Apache Felix. I told them we need
> the
> >>> >> following (from the incubator ip-clearance form):
> >>> >>
> >>> >> "A software grant must be provided to the ASF. This grant can either
> >>> >> be done by the ASF Corporate CLA (via Schedule B) or the Software
> >>> >> Grant Agreement. The completed and signed grant must be emailed to
> >>> >> secret...@apache.org"
> >>> >>
> >>> >> Consequently, they send (the received) CCLA which was supposed to
> >>> >> cover for that.
> >>> >>
> >>> >> Apologies if I misunderstood the requirement. Could you please help
> me
> >>> >> out here and list what exactly we need from Intel and/or Jessica to
> >>> >> get this done?
> >>> >>
> >>> >> regards,
> >>> >>
> >>> >> Karl
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Thu, Dec 14, 2017 at 12:48 PM, John D. Ament <
> johndam...@apache.org>
> >>> >> wrote:
> >>> >> > Karl,
> >>> >> >
> >>> >> > CCLA [1] is just a document indicating that the corporate entity
> has
> >>> >> given
> >>> >> > approval for individuals associated to it to contribute to Apache
> >>> under
> >>> >> > ICLAs.  It really doesn't provide any legal bearing to relicense
> code
> >>> >> > outside of an ICLA/SGA.
> >>> >> >
> >>> >> > Usually when projects come to us with an IP clearance, its for a
> >>> >> > significant amount of code.  In those scenarios, there's an SGA
> >>> >> associated
> >>> >> > with the contribution (from a corporate entity) indicating

Re: [DISCUSS] Apache Pinot Incubator Proposal

[Dave Fisher]

Noir or Blanc? Gris or Grigio? What’s the vintage?

All kidding aside this looks interesting.

Regards,
Dave

Sent from my iPhone

> On Feb 13, 2018, at 12:10 AM, kishore g  wrote:
> 
> Hello,
> 
> I would like to propose Pinot as an Apache Incubator project. The proposal
> is available as a draft at https://wiki.apache.org/incubator/PinotProposal. I
> have also included the text of the proposal below.
> 
> Any feedback from the community is much appreciated.
> 
> Regards,
> Kishore G
> 
> = Pinot Proposal =
> 
> == Abstract ==
> 
> Pinot is a distributed columnar storage engine that can ingest data in
> real-time and serve analytical queries at low latency. There are two modes
> of data ingestion - batch and/or realtime. Batch mode allows users to
> generate pinot segments externally using systems such as Hadoop. These
> segments can be uploaded into Pinot via simple curl calls. Pinot can ingest
> data in near real-time from streaming sources such as Kafka. Data ingested
> into Pinot is stored in a columnar format. Pinot provides a SQL like
> interface (PQL) that supports filters, aggregations, and group by
> operations. It does not support joins by design, in order to guarantee
> predictable latency. It leverages other Apache projects such as Zookeeper,
> Kafka, and Helix, along with many libraries from the ASF.
> 
> == Proposal ==
> 
> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the
> development happens at LinkedIn with other contributions from Uber and
> Slack. We believe that being a part of Apache Software Foundation will
> improve the diversity and help form a strong community around the project.
> 
> LinkedIn submits this proposal to donate the code base to Apache Software
> Foundation. The code is already under Apache License 2.0.  Code and the
> documentation are hosted on Github.
> * Code: http://github.com/linkedin/pinot
> * Documentation: https://github.com/linkedin/pinot/wiki
> 
> 
> == Background ==
> 
> LinkedIn, similar to other companies, has many applications that provide
> rich real-time insights to members and customers (internal and external).
> The workload characteristics for these applications vary a lot. Some
> internal applications simply need ad-hoc query capabilities with sub-second
> to multiple seconds latency. But external site facing applications require
> strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple
> solutions depending on the workload generated by the application and this
> was inefficient. Pinot was developed to be the one single platform that
> addresses all classes of applications. Today at LinkedIn, Pinot powers more
> than 50 site facing products with workload ranging from few queries per
> second to 1000’s of queries per second while maintaining the 99th
> percentile latency which can be as low as few milliseconds. All internal
> dashboards at LinkedIn are powered by Pinot.
> 
> == Rationale ==
> 
> We believe that requirement to develop rich real-time analytic applications
> is applicable to other organizations. Both Pinot and the interested
> communities would benefit from this work being openly available.
> 
> == Current Status ==
> 
> Pinot is currently open sourced under the Apache License Version 2.0 and
> available at github.com/linkedin/pinot. All the development is done using
> GitHub Pull Requests. We cut releases on a weekly basis and deploy it at
> LinkedIn. mp-0.1.468 is the latest release tag that is deployed in
> production.
> 
> == Meritocracy ==
> 
> Following the Apache meritocracy model, we intend to build an open and
> diverse community around Pinot. We will encourage the community to
> contribute to discussion and codebase.
> 
> == Community ==
> 
> Pinot is currently used extensively at LinkedIn and Uber. Several companies
> have expressed interest in the project. We hope to extend the contributor
> base significantly by bringing Pinot into Apache.
> 
> == Core Developers ==
> 
> Pinot was started by engineers at LinkedIn, and now has committers from
> Uber.
> 
> == Alignment ==
> 
> Apache is the most natural home for taking Pinot forward. Pinot leverages
> several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro.
> As Pinot gains adoption, we plan to add support for the ORC and Parquet
> formats, as well as adding integration with Yarn and Mesos.
> 
> == Known Risks ==
> 
> === Orphaned Products ===
> 
> The risk of the Pinot project being abandoned is minimal. The teams at
> LinkedIn and Uber are highly incentivized to continue development of Pinot
> as it is a critical part of their infrastructure.
> 
> === Inexperience with Open Source ===
> 
> Post open sourcing, Pinot was completely developed on GitHub. All the
> current developers on Pinot are well aware of the open source development
> process. However, most of the developers are new to the Apache process.
> Kishore Gopalakrishna, one of the lead developers in Pinot, is VP and
> committer of the Apache Helix pro

Re: [DISCUSS] Apache Pinot Incubator Proposal

[Kevin A. McGrail]

Agreed.  It could use more mentors from ASF which I'm too overloaded to 
help with but I'd be inclined to +1 this.  Do you have some thoughts on 
getting more community people outside of LI and Uber to help?


On 2/13/2018 7:07 PM, Dave Fisher wrote:

Noir or Blanc? Gris or Grigio? What’s the vintage?

All kidding aside this looks interesting.

Regards,
Dave

Sent from my iPhone


On Feb 13, 2018, at 12:10 AM, kishore g  wrote:

Hello,

I would like to propose Pinot as an Apache Incubator project. The proposal
is available as a draft at https://wiki.apache.org/incubator/PinotProposal. I
have also included the text of the proposal below.

Any feedback from the community is much appreciated.

Regards,
Kishore G

= Pinot Proposal =

== Abstract ==

Pinot is a distributed columnar storage engine that can ingest data in
real-time and serve analytical queries at low latency. There are two modes
of data ingestion - batch and/or realtime. Batch mode allows users to
generate pinot segments externally using systems such as Hadoop. These
segments can be uploaded into Pinot via simple curl calls. Pinot can ingest
data in near real-time from streaming sources such as Kafka. Data ingested
into Pinot is stored in a columnar format. Pinot provides a SQL like
interface (PQL) that supports filters, aggregations, and group by
operations. It does not support joins by design, in order to guarantee
predictable latency. It leverages other Apache projects such as Zookeeper,
Kafka, and Helix, along with many libraries from the ASF.

== Proposal ==

Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the
development happens at LinkedIn with other contributions from Uber and
Slack. We believe that being a part of Apache Software Foundation will
improve the diversity and help form a strong community around the project.

LinkedIn submits this proposal to donate the code base to Apache Software
Foundation. The code is already under Apache License 2.0.  Code and the
documentation are hosted on Github.
* Code: http://github.com/linkedin/pinot
* Documentation: https://github.com/linkedin/pinot/wiki


== Background ==

LinkedIn, similar to other companies, has many applications that provide
rich real-time insights to members and customers (internal and external).
The workload characteristics for these applications vary a lot. Some
internal applications simply need ad-hoc query capabilities with sub-second
to multiple seconds latency. But external site facing applications require
strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple
solutions depending on the workload generated by the application and this
was inefficient. Pinot was developed to be the one single platform that
addresses all classes of applications. Today at LinkedIn, Pinot powers more
than 50 site facing products with workload ranging from few queries per
second to 1000’s of queries per second while maintaining the 99th
percentile latency which can be as low as few milliseconds. All internal
dashboards at LinkedIn are powered by Pinot.

== Rationale ==

We believe that requirement to develop rich real-time analytic applications
is applicable to other organizations. Both Pinot and the interested
communities would benefit from this work being openly available.

== Current Status ==

Pinot is currently open sourced under the Apache License Version 2.0 and
available at github.com/linkedin/pinot. All the development is done using
GitHub Pull Requests. We cut releases on a weekly basis and deploy it at
LinkedIn. mp-0.1.468 is the latest release tag that is deployed in
production.

== Meritocracy ==

Following the Apache meritocracy model, we intend to build an open and
diverse community around Pinot. We will encourage the community to
contribute to discussion and codebase.

== Community ==

Pinot is currently used extensively at LinkedIn and Uber. Several companies
have expressed interest in the project. We hope to extend the contributor
base significantly by bringing Pinot into Apache.

== Core Developers ==

Pinot was started by engineers at LinkedIn, and now has committers from
Uber.

== Alignment ==

Apache is the most natural home for taking Pinot forward. Pinot leverages
several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro.
As Pinot gains adoption, we plan to add support for the ORC and Parquet
formats, as well as adding integration with Yarn and Mesos.

== Known Risks ==

=== Orphaned Products ===

The risk of the Pinot project being abandoned is minimal. The teams at
LinkedIn and Uber are highly incentivized to continue development of Pinot
as it is a critical part of their infrastructure.

=== Inexperience with Open Source ===

Post open sourcing, Pinot was completely developed on GitHub. All the
current developers on Pinot are well aware of the open source development
process. However, most of the developers are new to the Apache process.
Kishore Gopalakrishna, one of the lead developers in Pinot, is VP and
comm

Re: [DISCUSS] Apache Pinot Incubator Proposal

[Timothy Chen]

Love to see this in the incubator as well. +1

Tim

On Tue, Feb 13, 2018 at 4:22 PM, Kevin A. McGrail
 wrote:
> Agreed.  It could use more mentors from ASF which I'm too overloaded to help
> with but I'd be inclined to +1 this.  Do you have some thoughts on getting
> more community people outside of LI and Uber to help?
>
> On 2/13/2018 7:07 PM, Dave Fisher wrote:
>>
>> Noir or Blanc? Gris or Grigio? What’s the vintage?
>>
>> All kidding aside this looks interesting.
>>
>> Regards,
>> Dave
>>
>> Sent from my iPhone
>>
>>> On Feb 13, 2018, at 12:10 AM, kishore g  wrote:
>>>
>>> Hello,
>>>
>>> I would like to propose Pinot as an Apache Incubator project. The
>>> proposal
>>> is available as a draft at
>>> https://wiki.apache.org/incubator/PinotProposal. I
>>> have also included the text of the proposal below.
>>>
>>> Any feedback from the community is much appreciated.
>>>
>>> Regards,
>>> Kishore G
>>>
>>> = Pinot Proposal =
>>>
>>> == Abstract ==
>>>
>>> Pinot is a distributed columnar storage engine that can ingest data in
>>> real-time and serve analytical queries at low latency. There are two
>>> modes
>>> of data ingestion - batch and/or realtime. Batch mode allows users to
>>> generate pinot segments externally using systems such as Hadoop. These
>>> segments can be uploaded into Pinot via simple curl calls. Pinot can
>>> ingest
>>> data in near real-time from streaming sources such as Kafka. Data
>>> ingested
>>> into Pinot is stored in a columnar format. Pinot provides a SQL like
>>> interface (PQL) that supports filters, aggregations, and group by
>>> operations. It does not support joins by design, in order to guarantee
>>> predictable latency. It leverages other Apache projects such as
>>> Zookeeper,
>>> Kafka, and Helix, along with many libraries from the ASF.
>>>
>>> == Proposal ==
>>>
>>> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the
>>> development happens at LinkedIn with other contributions from Uber and
>>> Slack. We believe that being a part of Apache Software Foundation will
>>> improve the diversity and help form a strong community around the
>>> project.
>>>
>>> LinkedIn submits this proposal to donate the code base to Apache Software
>>> Foundation. The code is already under Apache License 2.0.  Code and the
>>> documentation are hosted on Github.
>>> * Code: http://github.com/linkedin/pinot
>>> * Documentation: https://github.com/linkedin/pinot/wiki
>>>
>>>
>>> == Background ==
>>>
>>> LinkedIn, similar to other companies, has many applications that provide
>>> rich real-time insights to members and customers (internal and external).
>>> The workload characteristics for these applications vary a lot. Some
>>> internal applications simply need ad-hoc query capabilities with
>>> sub-second
>>> to multiple seconds latency. But external site facing applications
>>> require
>>> strong SLA even very high workloads. Prior to Pinot, LinkedIn had
>>> multiple
>>> solutions depending on the workload generated by the application and this
>>> was inefficient. Pinot was developed to be the one single platform that
>>> addresses all classes of applications. Today at LinkedIn, Pinot powers
>>> more
>>> than 50 site facing products with workload ranging from few queries per
>>> second to 1000’s of queries per second while maintaining the 99th
>>> percentile latency which can be as low as few milliseconds. All internal
>>> dashboards at LinkedIn are powered by Pinot.
>>>
>>> == Rationale ==
>>>
>>> We believe that requirement to develop rich real-time analytic
>>> applications
>>> is applicable to other organizations. Both Pinot and the interested
>>> communities would benefit from this work being openly available.
>>>
>>> == Current Status ==
>>>
>>> Pinot is currently open sourced under the Apache License Version 2.0 and
>>> available at github.com/linkedin/pinot. All the development is done using
>>> GitHub Pull Requests. We cut releases on a weekly basis and deploy it at
>>> LinkedIn. mp-0.1.468 is the latest release tag that is deployed in
>>> production.
>>>
>>> == Meritocracy ==
>>>
>>> Following the Apache meritocracy model, we intend to build an open and
>>> diverse community around Pinot. We will encourage the community to
>>> contribute to discussion and codebase.
>>>
>>> == Community ==
>>>
>>> Pinot is currently used extensively at LinkedIn and Uber. Several
>>> companies
>>> have expressed interest in the project. We hope to extend the contributor
>>> base significantly by bringing Pinot into Apache.
>>>
>>> == Core Developers ==
>>>
>>> Pinot was started by engineers at LinkedIn, and now has committers from
>>> Uber.
>>>
>>> == Alignment ==
>>>
>>> Apache is the most natural home for taking Pinot forward. Pinot leverages
>>> several existing Apache Projects such as Kafka, Helix, Zookeeper, and
>>> Avro.
>>> As Pinot gains adoption, we plan to add support for the ORC and Parquet
>>> formats, as well as adding integration with Yarn and Mesos.
>>>
>>> == Known R

Re: [DISCUSS] Apache Pinot Incubator Proposal

[kishore g]

Kevin,

Increasing the adoption of Pinot is one thing that can help build a good
diverse community. Few things that come to my mind
- Improve documentation
- Better integration with cloud providers
- Meetup and blog posts.

We would also love to get additional mentors from ASF to help us build the
community around Pinot.




On Tue, Feb 13, 2018 at 4:29 PM, Timothy Chen  wrote:

> Love to see this in the incubator as well. +1
>
> Tim
>
> On Tue, Feb 13, 2018 at 4:22 PM, Kevin A. McGrail
>  wrote:
> > Agreed.  It could use more mentors from ASF which I'm too overloaded to
> help
> > with but I'd be inclined to +1 this.  Do you have some thoughts on
> getting
> > more community people outside of LI and Uber to help?
> >
> > On 2/13/2018 7:07 PM, Dave Fisher wrote:
> >>
> >> Noir or Blanc? Gris or Grigio? What’s the vintage?
> >>
> >> All kidding aside this looks interesting.
> >>
> >> Regards,
> >> Dave
> >>
> >> Sent from my iPhone
> >>
> >>> On Feb 13, 2018, at 12:10 AM, kishore g  wrote:
> >>>
> >>> Hello,
> >>>
> >>> I would like to propose Pinot as an Apache Incubator project. The
> >>> proposal
> >>> is available as a draft at
> >>> https://wiki.apache.org/incubator/PinotProposal. I
> >>> have also included the text of the proposal below.
> >>>
> >>> Any feedback from the community is much appreciated.
> >>>
> >>> Regards,
> >>> Kishore G
> >>>
> >>> = Pinot Proposal =
> >>>
> >>> == Abstract ==
> >>>
> >>> Pinot is a distributed columnar storage engine that can ingest data in
> >>> real-time and serve analytical queries at low latency. There are two
> >>> modes
> >>> of data ingestion - batch and/or realtime. Batch mode allows users to
> >>> generate pinot segments externally using systems such as Hadoop. These
> >>> segments can be uploaded into Pinot via simple curl calls. Pinot can
> >>> ingest
> >>> data in near real-time from streaming sources such as Kafka. Data
> >>> ingested
> >>> into Pinot is stored in a columnar format. Pinot provides a SQL like
> >>> interface (PQL) that supports filters, aggregations, and group by
> >>> operations. It does not support joins by design, in order to guarantee
> >>> predictable latency. It leverages other Apache projects such as
> >>> Zookeeper,
> >>> Kafka, and Helix, along with many libraries from the ASF.
> >>>
> >>> == Proposal ==
> >>>
> >>> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of
> the
> >>> development happens at LinkedIn with other contributions from Uber and
> >>> Slack. We believe that being a part of Apache Software Foundation will
> >>> improve the diversity and help form a strong community around the
> >>> project.
> >>>
> >>> LinkedIn submits this proposal to donate the code base to Apache
> Software
> >>> Foundation. The code is already under Apache License 2.0.  Code and the
> >>> documentation are hosted on Github.
> >>> * Code: http://github.com/linkedin/pinot
> >>> * Documentation: https://github.com/linkedin/pinot/wiki
> >>>
> >>>
> >>> == Background ==
> >>>
> >>> LinkedIn, similar to other companies, has many applications that
> provide
> >>> rich real-time insights to members and customers (internal and
> external).
> >>> The workload characteristics for these applications vary a lot. Some
> >>> internal applications simply need ad-hoc query capabilities with
> >>> sub-second
> >>> to multiple seconds latency. But external site facing applications
> >>> require
> >>> strong SLA even very high workloads. Prior to Pinot, LinkedIn had
> >>> multiple
> >>> solutions depending on the workload generated by the application and
> this
> >>> was inefficient. Pinot was developed to be the one single platform that
> >>> addresses all classes of applications. Today at LinkedIn, Pinot powers
> >>> more
> >>> than 50 site facing products with workload ranging from few queries per
> >>> second to 1000’s of queries per second while maintaining the 99th
> >>> percentile latency which can be as low as few milliseconds. All
> internal
> >>> dashboards at LinkedIn are powered by Pinot.
> >>>
> >>> == Rationale ==
> >>>
> >>> We believe that requirement to develop rich real-time analytic
> >>> applications
> >>> is applicable to other organizations. Both Pinot and the interested
> >>> communities would benefit from this work being openly available.
> >>>
> >>> == Current Status ==
> >>>
> >>> Pinot is currently open sourced under the Apache License Version 2.0
> and
> >>> available at github.com/linkedin/pinot. All the development is done
> using
> >>> GitHub Pull Requests. We cut releases on a weekly basis and deploy it
> at
> >>> LinkedIn. mp-0.1.468 is the latest release tag that is deployed in
> >>> production.
> >>>
> >>> == Meritocracy ==
> >>>
> >>> Following the Apache meritocracy model, we intend to build an open and
> >>> diverse community around Pinot. We will encourage the community to
> >>> contribute to discussion and codebase.
> >>>
> >>> == Community ==
> >>>
> >>> Pinot is currently used extensively at LinkedIn 

Re: [DISCUSS] Apache Pinot Incubator Proposal

[Olivier Lamy]

Hi
Kishore well I think as you are an ASF member you can add yourself as a
mentor :-)


On 14 February 2018 at 01:01, kishore g  wrote:

> Kevin,
>
> Increasing the adoption of Pinot is one thing that can help build a good
> diverse community. Few things that come to my mind
> - Improve documentation
> - Better integration with cloud providers
> - Meetup and blog posts.
>
> We would also love to get additional mentors from ASF to help us build the
> community around Pinot.
>
>
>
>
> On Tue, Feb 13, 2018 at 4:29 PM, Timothy Chen  wrote:
>
> > Love to see this in the incubator as well. +1
> >
> > Tim
> >
> > On Tue, Feb 13, 2018 at 4:22 PM, Kevin A. McGrail
> >  wrote:
> > > Agreed.  It could use more mentors from ASF which I'm too overloaded to
> > help
> > > with but I'd be inclined to +1 this.  Do you have some thoughts on
> > getting
> > > more community people outside of LI and Uber to help?
> > >
> > > On 2/13/2018 7:07 PM, Dave Fisher wrote:
> > >>
> > >> Noir or Blanc? Gris or Grigio? What’s the vintage?
> > >>
> > >> All kidding aside this looks interesting.
> > >>
> > >> Regards,
> > >> Dave
> > >>
> > >> Sent from my iPhone
> > >>
> > >>> On Feb 13, 2018, at 12:10 AM, kishore g  wrote:
> > >>>
> > >>> Hello,
> > >>>
> > >>> I would like to propose Pinot as an Apache Incubator project. The
> > >>> proposal
> > >>> is available as a draft at
> > >>> https://wiki.apache.org/incubator/PinotProposal. I
> > >>> have also included the text of the proposal below.
> > >>>
> > >>> Any feedback from the community is much appreciated.
> > >>>
> > >>> Regards,
> > >>> Kishore G
> > >>>
> > >>> = Pinot Proposal =
> > >>>
> > >>> == Abstract ==
> > >>>
> > >>> Pinot is a distributed columnar storage engine that can ingest data
> in
> > >>> real-time and serve analytical queries at low latency. There are two
> > >>> modes
> > >>> of data ingestion - batch and/or realtime. Batch mode allows users to
> > >>> generate pinot segments externally using systems such as Hadoop.
> These
> > >>> segments can be uploaded into Pinot via simple curl calls. Pinot can
> > >>> ingest
> > >>> data in near real-time from streaming sources such as Kafka. Data
> > >>> ingested
> > >>> into Pinot is stored in a columnar format. Pinot provides a SQL like
> > >>> interface (PQL) that supports filters, aggregations, and group by
> > >>> operations. It does not support joins by design, in order to
> guarantee
> > >>> predictable latency. It leverages other Apache projects such as
> > >>> Zookeeper,
> > >>> Kafka, and Helix, along with many libraries from the ASF.
> > >>>
> > >>> == Proposal ==
> > >>>
> > >>> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of
> > the
> > >>> development happens at LinkedIn with other contributions from Uber
> and
> > >>> Slack. We believe that being a part of Apache Software Foundation
> will
> > >>> improve the diversity and help form a strong community around the
> > >>> project.
> > >>>
> > >>> LinkedIn submits this proposal to donate the code base to Apache
> > Software
> > >>> Foundation. The code is already under Apache License 2.0.  Code and
> the
> > >>> documentation are hosted on Github.
> > >>> * Code: http://github.com/linkedin/pinot
> > >>> * Documentation: https://github.com/linkedin/pinot/wiki
> > >>>
> > >>>
> > >>> == Background ==
> > >>>
> > >>> LinkedIn, similar to other companies, has many applications that
> > provide
> > >>> rich real-time insights to members and customers (internal and
> > external).
> > >>> The workload characteristics for these applications vary a lot. Some
> > >>> internal applications simply need ad-hoc query capabilities with
> > >>> sub-second
> > >>> to multiple seconds latency. But external site facing applications
> > >>> require
> > >>> strong SLA even very high workloads. Prior to Pinot, LinkedIn had
> > >>> multiple
> > >>> solutions depending on the workload generated by the application and
> > this
> > >>> was inefficient. Pinot was developed to be the one single platform
> that
> > >>> addresses all classes of applications. Today at LinkedIn, Pinot
> powers
> > >>> more
> > >>> than 50 site facing products with workload ranging from few queries
> per
> > >>> second to 1000’s of queries per second while maintaining the 99th
> > >>> percentile latency which can be as low as few milliseconds. All
> > internal
> > >>> dashboards at LinkedIn are powered by Pinot.
> > >>>
> > >>> == Rationale ==
> > >>>
> > >>> We believe that requirement to develop rich real-time analytic
> > >>> applications
> > >>> is applicable to other organizations. Both Pinot and the interested
> > >>> communities would benefit from this work being openly available.
> > >>>
> > >>> == Current Status ==
> > >>>
> > >>> Pinot is currently open sourced under the Apache License Version 2.0
> > and
> > >>> available at github.com/linkedin/pinot. All the development is done
> > using
> > >>> GitHub Pull Requests. We cut releases on a weekly basis and deploy it
> > at
> 

[DRAFT] Incubator PMC Board Report - February 2018

[John D. Ament]

All,

Below is the current draft of the IPMC report.  Of note is that the Slider
report still needs mentor sign off.  Hopefully that will come soon.  I'm
going to give it one more day and plan to submit the report on Thursday.

Incubator PMC report for February 2018

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

There are presently 54 podlings incubating.  In the month of January,
podlings executed five releases, we added four additional IPMC members; as
well as one new podling and one retiring podling.

* Community

  New IPMC members:

  - David E. Jones
  - Kevin A. McGrail
  - Mark Thomas
  - Timothy Chen

  People who left the IPMC:

  - None

* New Podlings

  - ECharts

* Podlings that failed to report, expected next month

  - iota: no further reports expected, podling is retiring
  - Milagro: expecting podling to retire
  - Myriad: expecting podling to retire

* Podlings missing sign off

  - Slider

* Graduations

  The board has motions for the following:

  - None

* Releases

  The following releases entered distribution during the month of
  January:

  - 2018-01-02 Apache Airflow 1.9.0
  - 2018-01-16 Apache Aria Tosca 0.2.0
  - 2018-01-17 Apache Taverna Server 3.1.0
  - 2018-01-22 Apache Traffic Control 2.1.0
  - 2018-01-27 Apache DataFu 1.3.3

* IP Clearance

  - Appreciations go out for ensuring that RocketMQ performs proper IP
Clearance.  Similar reminders have gone out to DeltaSpike and TomEE.

* Legal / Trademarks

  - Multiple podlings have open tickets and emails in to legal to review
open questions.  Assistance is requested to guide them, even if the answer
is "work with your mentors to get an answer."

* Infrastructure

  - Work will need to begin to clean up remaining links into the retired
Service Desk instance.

* Miscellaneous


--
   Table of Contents
Airflow
Crail
ECharts
Edgent
Heron
Joshua
Livy
PageSpeed
PLC4X
Ratis
S2Graph
SDAP
ServiceComb
SkyWalking
Slider
Spot
Tamaya
Toree
Unomi

--


Airflow

Airflow is a workflow automation and scheduling system that can be used to
author and manage data pipelines.

Airflow has been incubating since 2016-03-31.

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

  1. We have had 4 releases and are working toward our 5th. We are getting
better at releases.
  2.
  3.

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


How has the community developed since the last report?
1. We had our forth official release 1.9.0 on Jan 2, 2018.
2. Since our last podling report 4 months ago (i.e. between Sept 25 & Feb 8,
   inclusive), we grew our contributors from 315 to 385
3. Since our last podling report 4 months ago (i.e. between Sept 25 & Feb
8,
   inclusive), we resolved 331 pull requests (currently at 2128 closed PRs)
4. Since being accepted into the incubator, the number of companies
officially
   using Apache Airflow has risen from 30 to 132, 18 new from the last
podling
   report.


How has the project developed since the last report?
  See above : 331 PR resolved, 70 new contributors, & 18 new companies
  officially using it.

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

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

Date of last release:

  2018-01-02

When were the last committers or PPMC members elected?

  2017-11-30 joygao a.k.a Joy Gao (committer/PMC)

Signed-off-by:

  [ ](airflow) Chris Nauroth
 Comments:
  [x](airflow) Hitesh Shah
 Comments:
  [ ](airflow) Jakob Homan
 Comments:


Crail

Crail is a storage platform for sharing performance critical data in
distributed data processing jobs at very high speed.

Crail has been incubating since 2017-11-01.

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

  1. Community building
  2. Improve project visibility
  3. Create the first release

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

* No issues require attention at this time.

How has the community developed since the last report?

* We are trying to advertise Crail to attract more people
  to contribute and/or use it. In that respect, we got a
  presentation at this years SF Spark Summit accepted, where
  we will talk about Crail deployment in the Spark context.

How has the project developed since the last report?

 * Code transfer to apache.org complete
 * Project website up, working on improvements and compliance
 * Working on adapting Crail build process to new (Apache)
   environment.

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

  [x] Initial setup
  [x] Working tow

[VOTE] Apache MXNet (incubating) 1.1.0 release RC1

[YiZhi Liu]

Hi all,

As we have updated the LICENSE file which caused the failure vote for
Apache MXNet (incubating) 1.1.0.RC0, this is a call for a releasing
Apache MXNet (incubating) 1.1.0, release candidate 1.

Apache MXNet (incubating) community has voted and approved the release.

Vote thread:
https://lists.apache.org/thread.html/500fb648e8629249b904d9fc56e7737c5312dfe54c17d4d5d06468a8@%3Cdev.mxnet.apache.org%3E

Result thread:
https://lists.apache.org/thread.html/afaf45dda45da60692476c56a268b95dd0663bb193f8c77ac372631a@%3Cdev.mxnet.apache.org%3E

PR which fixes the license:
https://github.com/apache/incubator-mxnet/pull/9701

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.1.0.rc1/

The tag to be voted upon is 1.1.0.rc0:
https://github.com/apache/incubator-mxnet/releases/tag/1.1.0.rc1

The release hash is 07a83a0325a3d782513a04f47d711710972cb144:
https://github.com/apache/incubator-mxnet/commit/07a83a0325a3d782513a04f47d711710972cb144

Release artifacts are signed with the following key:
F42C 1A6E 634C 105E 8D98  5105 CA75 1254 E97B 9FE4

KEYS file available:
https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS

For information about the contents of this release, see:
https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.1.0+Release+Notes

The vote will end at 11:35 pm on Friday, Feb 16th, PST.

[ ] +1 Release this package as 1.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

-- 
Yizhi Liu
DMLC member
Amazon Web Services
Vancouver, Canada

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