Re: Showcase your project at ApacheCON at a Podling's Shark Tank

[leerho]

I am a committer on DataSketches, a relatively new Podling and would like
to present at the Shark Tank at ACNA19, if possible.

I tried the above links but none seem to work  :(

Lee Rhodes
lee...@apache.org

On Wed, Aug 14, 2019 at 1:45 PM Roman Shaposhnik  wrote:

> Hi Podlings!
>
> in less than a month we're going to have our first
> ApacheCON this year -- the one in Las Vegas. In
> about two month there will be one more in Berlin.
>
> These are not your regular ApacheCONs -- these are
> 20th Anniversary of ASF ApacehCONs! In other words,
> these are not to be missed!
>
> And even if your talk didn't get accepted -- you still
> get an opportunity to highlight your project to, what's
> likely going to be the biggest audience attending.
>
> Here's how: if you (or any community member who's
> passionate about your project) are going to be at either
> of those ApacheCONs consider signing up for
> Podling's Shark Tank
> events:
> https://www.apachecon.com/acna19/s/#/scheduledEvent/1038
> https://aceu19.apachecon.com/session/podlings-shark-tank
>
> Each project presenting will get ~10 min for the pitch and ~5 min
> of panel grilling them on all sorts of things. Kind of like this ;-)
>  https://www.youtube.com/watch?v=wmenN7NEdBc
>
> You've got nothing to lose (in fact, the opposite: you're likely to get
> a prize!) and you will get a chance to receive feedback that might
> actually help you grow your community and ultimately graduate to the
> TLP status. And! Given our awesome panel of judges:
>  * Myrle Krantz
>  * Justin Mclean
>  * Craig Russel
>  * Shane Curcuru
> We guarantee this to be a fun and useful event for your community!
>
> We will be tracking signups over here:
>  https://wiki.apache.org/apachecon/ACNA19PodlingSharkTank
>  https://wiki.apache.org/apachecon/ACEU19PodlingSharkTank
> but for now:
>
> SIMPLY REPLY TO THIS EMAIL if you're interested.
>
> It is first come, first serve -- so don't delay -- sign up today!
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) v2.0.2

[Joshua Poore]

Hi IPMC—

Just a reminder: please VOTE on Apache Flagon UserALE.js (Incubating) v2.0.2

We need +3 binding VOTE from Incubator having met the VOTE requirements on dev@

Note that we have addressed the omission of the disclaimer files from .bin 
distribution packages Justin discovered, with no commits needed to fix. See 
below.

As this is a security-related patch, attention to this VOTE is much appreciated.

Thanks!

Josh

> On Aug 14, 2019, at 11:10 PM, Joshua Poore  wrote:
> 
> General@
> 
> Following Justin’s comment below—Disclaimer missing from .bin release 
> packages—I have repackaged release candidate #1 to include Disclaimers and 
> pushed to https://dist.apache.org/repos/dist/dev/incubator/flagon/ 
> .
> 
> As this issue was a file omission and did not affect source or build 
> artifacts, the commit reference used for voting in dev@ have not changed, nor 
> have git tags for the release candidate. .bin packages now include our 
> Disclaimer.
> 
> As a matter of good practice I have re-evaluated the repackaged release 
> candidate against the following:
> 
> [ x ] Build and Unit Tests Pass
> [ x ] Integration Tests Pass
> [ x ] "Incubating" in References to Project and Distribution File Names
> [ x ] Signatures and Hashes Match Keys
> [ x ] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release 
> Packages
> [ x ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF and Incubator 
> Policy
> [ x ] CHANGELOG included with release distribution
> [ x ] All Source Files Have Correct ASF Headers
> [ x ] No Unexpected Binary Files in Source Release Packages
> 
> Please feel free to evaluate as you VOTE. See the thread below for the 
> interim summary of VOTEs on dev@
> 
> VOTE details follow:
> 
> Please VOTE on the Apache Flagon (Incubating) 2.0.2 Release Candidate # 1
> 
> This VOTE has passed successfully within the Apache Flagon community. We are 
> now posting the VOTE on general@ as required by Apache Release Management 
> policies. 
> 
> Interim RESULT on dev@ are as follows:
> 
> [+1] 7  
> Joshua Poore
> Rob Foley (`Confused`)
> Laura Mariano
> Furkan Kamaci*
> Arthi Vezhavendan
> Tim Allison*
> Dave Meikle*
> 
> [0] 0
> 
> [-1]
> 
> *Binding IPMC/PPMC Mentor VOTE
> 
> The VOTE thread on dev@ can be found here: 
> https://lists.apache.org/thread.html/1d0efb2a17b1b1a3bb83a6bf882f994000f7d9db316f8b244db54076@%3Cdev.flagon.apache.org%3E
>  
> 
> 
> VOTE details follow:
> 
> About Flagon: http://flagon.incubator.apache.org/ 
>   > 
> 
> This Patch release includes :
> 
>   • Updates to package.json and package-lock.json to resolve downstream 
> Prototype Pollution vulnerabilities in dev dependencies
>   • Updates to package.json and package-lock.json to modernize deprecated 
> npm modules
>   • Minor updates to README documentation for UserALE.js' Example Test 
> Utilities.
> 
> We solved 11 issues: 
> https://issues.apache.org/jira/projects/FLAGON/versions/12345954 
>   >
> 
> Git source tag (43de2fc1e1c5d5e1a83119a91947f7bbe6d313f3): 
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.0.2-RC1-08_06_2019
>  
> 
>  
>   
> >
> 
> Staging repo: https://dist.apache.org/repos/dist/dev/incubator/flagon/ 
> 
> 
> Source Release Artifacts: 
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.0.2-RC1/
>  
> 
>  
> 
> PGP release keys (signed using F937rFAE3FCADF6E): 
> https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS 
> 
> 
> Reference the UserALE.js testing framework to assist in your unit and 
> integration tests: 
> https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Testing+Framework
>  
> 
> 
> Link to Successful Jenkins Build(s): 
> https://builds.apache.org/job/useralejs-ci/91/ 
> 
> 
> Vote will be open for 72 hours. Please VOTE as follows: 
> 
> [ ] +1, let's get it released!!!
> [ ] +/-0, f

Re: [RESULT] [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[David Lim]

Hello,

The resolution to establish Druid as a TLP has been submitted to the Board
for their consideration.

Thank you to everyone for your participation and assistance.

On behalf of the Druid PPMC and community,
David

On Fri, Aug 16, 2019 at 1:42 AM David Lim  wrote:

> The vote to recommend the 'Apache Druid graduation to Top Level project'
> resolution to the board has passed as follows:
>
> 15 binding +1 votes:
>
> Justin Mclean
> Matt Sicker
> Furkan Kamaci
> P. Taylor Goetz
> Dave Fisher
> Ted Dunning
> Andrei Savu
> Julian Hyde
> Julian Feinauer
> Suneel Marthi
> Myrle Krantz
> Ryan Blue
> Sheng Wu
> Paul King
> Jitendra Pandey
>
> 3 non-binding +1 votes:
>
> Hao Chen
> William Guo
> tan zhongyi
>
> Voting thread:
> https://lists.apache.org/thread.html/19b703fdf192ddf8e31bda57264e03113c7e44b5954a56886e05@%3Cgeneral.incubator.apache.org%3E
>
> Thank you all for your vote and for everything you do for the foundation.
>
> Traditionally, would it be a member of the IPMC or the Druid PPMC that
> submits the resolution to the Board? Based on the language used in the
> graduation guide (
> https://incubator.apache.org/guides/graduation.html#submission_of_the_resolution_to_the_board)
> I suspect it is the Druid PPMC, but a confirmation would be appreciated.
>
> Thank you again.
>
> On behalf of the Druid PPMC and community,
> David
>

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[David Lim]

Hello,

The vote is now closed. Voting results are available at:
https://lists.apache.org/thread.html/9fe6ae396aee444d26f2f984903326b6f0974e7e328aee2c81e09e7a@%3Cgeneral.incubator.apache.org%3E

Thank you to everyone who participated.

David

Re: [VOTE] Accept MesaTEE into Apache Incubator

[Byung-Gon Chun]

+1 (binding)

-Gon

On Wed, Aug 14, 2019 at 3:41 PM Zhijie Shen  wrote:

> Hi all,
>
> After gauging the interest of MesaTEE (discussion thread:
>
> https://lists.apache.org/thread.html/323983a2875dd44ef19a3771ec329d5920d4d04bbdde18aab70dbe08@%3Cgeneral.incubator.apache.org%3E
> ),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring MesaTEE into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring MesaTEE into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> Thanks,
> Zhijie
>
> ==
> MesaTEE Apache Incubation Proposal
>
> = Abstract =
>
> MesaTEE is a framework for universal secure computing.
>
> = Proposal =
>
> MesaTEE is the next-gen solution to enable general computing service for
> security-critical scenarios. It will allow even the most sensitive data to
> be
> securely processed to enable offshore businesses without leakage.
>
> The solution combines the advanced Hybrid Memory Safety (HMS) model and the
> power of the Trusted Computing technologies (e.g., TPM) as well as the
> Confidential Computing technologies (e.g., Intel SGX).
>
>   * Code base:
> * https://github.com/mesalock-linux/mesatee
> * https://github.com/baidu/rust-sgx-sdk
>   * Website: https://mesatee.org
>   * Documentation: https://mesatee.org/doc/mesatee_sdk/
>
> = Background =
>
> The emerging technologies of big data analytics, machine learning,
> cloud/edge
> computing, and blockchain are significantly boosting our productivity, but
> at
> the same time they are bringing new confidentiality and integrity concerns.
> On
> public cloud and blockchain, sensitive data like health and financial
> records
> may be consumed at runtime by untrusted computing processes running on
> compromised platforms; during in-house data exchange, confidential
> information
> may cross different clearance boundaries and possibly fall into the wrong
> hands;
> also not to mention the privacy issue arises in offshore data supply
> chains.
>
> Although the consequences of data breaching have been extensively
> elaborated, we
> should also note that proprietary computing algorithms themselves, such as
> AI
> models, also need to be well protected. Once leaked, attackers can steal
> the
> intellectual properties, or launch whitebox attacks and easily exploit the
> weaknesses of the models.
>
> Facing all these risky scenarios, we are in desperate need of a trusted and
> secure mechanism, enabling us to protect both private data and proprietary
> computing models during a migratable execution in potentially unsafe
> environments, yet preserving functionalities, performance, compatibility,
> and
> flexibility. MesaTEE is targeting to be, as we call it, the full "Universal
> Secure Computing" stack, so it can help users resolve these runtime
> security
> risks.
>
> MesaTEE aims to promote the development of universal secure computing
> ecosystem
> through open source and openness, to provide basic support for trust
> protection
> for the productivity revolution brought by big data and AI, to completely
> solve
> the data exchange or multi-party computing between departments/companies,
> to
> enable privacy-crucial services such as financial and medical care using
> blockchain/cloud services, and to convoy businesses that are closely
> related to
> life and safety such as autonomous driving. MesaTEE has been working
> closely
> with mainstream cloud computing/blockchain/chip vendors and
> universities/research institutions to promote hardware TEE, software memory
> safety, and versatile computing services to create an internationally
> protected
> and flexible secure computing framework. MesaTEE’s open-source release will
> greatly accelerate the development of the next generation of big data
> business
> applications, and it is also of great importance to promoting AI in all
> business
> areas.
>
> = Rationale =
>
> MesaTEE stack redefines future AI and big data analytics by providing a
> trusted
> and secure offshore computing environment. The confidentiality and privacy
> of
> data and models can be well protected with MesaTEE, even if data and model
> originate from different parties with no mutual trust. Moreover, the
> computing
> platform itself is not necessarily trusted either. The Trusted Computing
> Base
> (TCB) can thus be largely reduced to MesaTEE framework alone. A detailed
> description of target use-cases can be found at
> https://github.com/mesalock-linux/mesatee/blob/master/docs/case_study.md.
>
> We believe that Apache way of open source community empowers MesaTEE to
> attract
> a diverse set of contributors who can bring new ideas into the project.
>
> = Initial Goals =
>
>   * Move the existing codebase, website, documentation, and mailing lists
> to an
> Apache-hosted infrastructure.
>   * Integrate with the Apache development process.
>   * Ensure all dependencies 

Re: [VOTE] Accept MesaTEE into Apache Incubator

[Wei Mingzhi]

+1

On 2019/08/14 06:40:47, Zhijie Shen  wrote:
> Hi all,>
>
> After gauging the interest of MesaTEE (discussion thread:>
> 
https://lists.apache.org/thread.html/323983a2875dd44ef19a3771ec329d5920d4d04bbdde18aab70dbe08@%3Cgeneral.incubator.apache.org%3E),> 


> I would like to call a VOTE to accept it into the Apache Incubator.>
>
> Please cast your vote:>
>
> [ ] +1, bring MesaTEE into Incubator>
> [ ] +0, I don't care either way>
> [ ] -1, do not bring MesaTEE into Incubator, because...>
>
> The vote will open at least for 72 hours and only votes from the 
Incubator>

> PMC are binding.>
>
> Thanks,>
> Zhijie>
>
> ==>
> MesaTEE Apache Incubation Proposal>
>
> = Abstract =>
>
> MesaTEE is a framework for universal secure computing.>
>
> = Proposal =>
>
> MesaTEE is the next-gen solution to enable general computing service 
for>
> security-critical scenarios. It will allow even the most sensitive 
data to>

> be>
> securely processed to enable offshore businesses without leakage.>
>
> The solution combines the advanced Hybrid Memory Safety (HMS) model 
and the>

> power of the Trusted Computing technologies (e.g., TPM) as well as the>
> Confidential Computing technologies (e.g., Intel SGX).>
>
> * Code base:>
> * https://github.com/mesalock-linux/mesatee>
> * https://github.com/baidu/rust-sgx-sdk>
> * Website: https://mesatee.org>
> * Documentation: https://mesatee.org/doc/mesatee_sdk/>
>
> = Background =>
>
> The emerging technologies of big data analytics, machine learning,>
> cloud/edge>
> computing, and blockchain are significantly boosting our 
productivity, but>

> at>
> the same time they are bringing new confidentiality and integrity 
concerns.>

> On>
> public cloud and blockchain, sensitive data like health and financial>
> records>
> may be consumed at runtime by untrusted computing processes running on>
> compromised platforms; during in-house data exchange, confidential>
> information>
> may cross different clearance boundaries and possibly fall into the 
wrong>

> hands;>
> also not to mention the privacy issue arises in offshore data supply 
chains.>

>
> Although the consequences of data breaching have been extensively>
> elaborated, we>
> should also note that proprietary computing algorithms themselves, 
such as>

> AI>
> models, also need to be well protected. Once leaked, attackers can 
steal the>
> intellectual properties, or launch whitebox attacks and easily 
exploit the>

> weaknesses of the models.>
>
> Facing all these risky scenarios, we are in desperate need of a 
trusted and>
> secure mechanism, enabling us to protect both private data and 
proprietary>

> computing models during a migratable execution in potentially unsafe>
> environments, yet preserving functionalities, performance, 
compatibility,>

> and>
> flexibility. MesaTEE is targeting to be, as we call it, the full 
"Universal>
> Secure Computing" stack, so it can help users resolve these runtime 
security>

> risks.>
>
> MesaTEE aims to promote the development of universal secure computing>
> ecosystem>
> through open source and openness, to provide basic support for trust>
> protection>
> for the productivity revolution brought by big data and AI, to 
completely>

> solve>
> the data exchange or multi-party computing between 
departments/companies, to>
> enable privacy-crucial services such as financial and medical care 
using>

> blockchain/cloud services, and to convoy businesses that are closely>
> related to>
> life and safety such as autonomous driving. MesaTEE has been working 
closely>

> with mainstream cloud computing/blockchain/chip vendors and>
> universities/research institutions to promote hardware TEE, software 
memory>

> safety, and versatile computing services to create an internationally>
> protected>
> and flexible secure computing framework. MesaTEE’s open-source 
release will>

> greatly accelerate the development of the next generation of big data>
> business>
> applications, and it is also of great importance to promoting AI in all>
> business>
> areas.>
>
> = Rationale =>
>
> MesaTEE stack redefines future AI and big data analytics by providing a>
> trusted>
> and secure offshore computing environment. The confidentiality and 
privacy>

> of>
> data and models can be well protected with MesaTEE, even if data and 
model>

> originate from different parties with no mutual trust. Moreover, the>
> computing>
> platform itself is not necessarily trusted either. The Trusted 
Computing>

> Base>
> (TCB) can thus be largely reduced to MesaTEE framework alone. A 
detailed>

> description of target use-cases can be found at>
> 
https://github.com/mesalock-linux/mesatee/blob/master/docs/case_study.md.>

>
> We believe that Apache way of open source community empowers MesaTEE to>
> attract>
> a diverse set of contributors who can bring new ideas into the project.>
>
> = Initial Goals =>
>
> * Move the existing codebase, website, documentation, and mailing lists>
> to an>
> Apache-hosted infrastructu

[RESULT] [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[David Lim]

The vote to recommend the 'Apache Druid graduation to Top Level project'
resolution to the board has passed as follows:

15 binding +1 votes:

Justin Mclean
Matt Sicker
Furkan Kamaci
P. Taylor Goetz
Dave Fisher
Ted Dunning
Andrei Savu
Julian Hyde
Julian Feinauer
Suneel Marthi
Myrle Krantz
Ryan Blue
Sheng Wu
Paul King
Jitendra Pandey

3 non-binding +1 votes:

Hao Chen
William Guo
tan zhongyi

Voting thread:
https://lists.apache.org/thread.html/19b703fdf192ddf8e31bda57264e03113c7e44b5954a56886e05@%3Cgeneral.incubator.apache.org%3E

Thank you all for your vote and for everything you do for the foundation.

Traditionally, would it be a member of the IPMC or the Druid PPMC that
submits the resolution to the Board? Based on the language used in the
graduation guide (
https://incubator.apache.org/guides/graduation.html#submission_of_the_resolution_to_the_board)
I suspect it is the Druid PPMC, but a confirmation would be appreciated.

Thank you again.

On behalf of the Druid PPMC and community,
David