Re: [VOTE] Graduate Apache TVM as TLP

[Timothy Chen]

+1 binding as well

Tim

Sent via Superhuman iOS <https://sprh.mn/?vip=tnac...@apache.org>


On Wed, Oct 21 2020 at 08:18, Sebastian Schelter  wrote:

>
> +1
>
> On 2020/10/19 17:29:23, Tianqi Chen  wrote:
>
> Dear Incubator:
>
> A month ago we brought up the discussion about graduating TVM as TLP.
> After great discussions in the apache way [2],
> we get good support from the incubator and also get helpful feedback about
> producing another release.
> The TVM PPMC always focused on getting consensus, and is fully committed
> to building a better community,
> as a result, we decided to withdraw the graduation until there has been
> another release.
>
> Now that the community has produced another release by two new release
> managers from different organizations
> and a after new round of discussion[1], we propose to formally vote on
> TVM's graduation.
>
> Please also see the community discussion thread[3], voting thread[4].
>
> This is a formal voting thread about Apache TVM's graduation, please Vote:
> [ ] +1 - Recommend graduation of Apache TVM as a TLP
> [ ] 0 - I don't feel strongly about it, but don't object
> [ ] -1 - Do not recommend graduation of Apache TVM because...
>
> The VOTE will open for at least 72 hours.
>
> --
> Summary of community status:
>
> Compliance
>
> Compliance is what every project is required to do. These policies are set
> to protect Apache’s brand,
> encourage community over code and set a common foundation for the
> projects. Usually compliance is well documented (as per-apache way, what is
> not documented did not happen).
> The TVM PPMC has been diligently upholding compliances, including, but not
> limited to
>
> - T0 Project website hosted at ASF https://tvm.apache.org/.
> - T1 Produce apache release, no cat-X code.
> - T2 No advertising non-release items as Apache release.
> - T3 Protect Apache brand, working with trademark to resolve branding
> concerns.
> - T4 Clearly marks third party artifacts and makes sure they comply with
> trademark policies.
> - T5 Open development: everyone happens (also) happens on dev@
> - T6 Consider all forms of contributions for committer nomination.
> - T7 Make sure release processes are clearly documented, reproducible by
> any committers.
>
> Community
>
> The “community over code” is one of the most important factors of the
> Apache way.
> The TVM PPMC has been working very hard to foster a healthy, diverse and
> independent community,
> and will continue to do so.
>
> - C0: Consider all forms of contributions as merit.
> - C1: Encourage community diversity by only nominating people from
> different organizations.
> - C2: Actively discusses, and brings in new committers from diverse
> backgrounds.
> The community grows healthily and is quite vibrant.
>
> -
>
> Establish the Apache TVM Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish a
> Project Management Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the public, related
> to compilation of machine learning models to run on a wide range of
> hardware platforms...
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache TVM Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache TVM Project be and hereby is responsible for the
> creation and maintenance of software related to compilation of machine
> learning models to run on a wide range of hardware platforms; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache TVM" be and hereby is
> created, the person holding such office to serve at the direction of the
> Board of Directors as the chair of the Apache TVM Project, and to have
> primary responsibility for management of the projects within the scope of
> responsibility of the Apache TVM Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache TVM Project:
>
> * Tianqi Chen 
> * Timothy Chen 
> * Zhi Chen 
> * Byung-Gon Chun 
> * Ziheng Jiang 
> * Furkan Kamaci 
> * YiZhi Liu 
> * Masahiro Masuda 
> * Thierry Moreau 
> * Jared Roesch 
> * Henry Saputra 
> * Haichen Shen 
> * Markus Weimer 
> * Eddie Yan 
> * Lianmin Zheng 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tianqi Chen be appointed to
> the office of Vice President, Apache TVM, to serv

Re: [VOTE] Accept Apache TVM into the incubator

[Timothy Chen]

+1 (binding).

Tim

On Thu, Feb 28, 2019 at 12:23 AM Cihad Guzel  wrote:
>
> +1 (non-binding)
>
> 28 Şub 2019 Per 11:08 tarihinde Felix Cheung  şunu
> yazdı:
>
> > +1 (binding)
> >
> > On Wed, Feb 27, 2019 at 10:17 PM kellen sunderland <
> > kellen.sunderl...@gmail.com> wrote:
> >
> > > +1 (non-binding)
> > >
> > > On Wed, Feb 27, 2019, 10:15 PM Furkan KAMACI 
> > > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > 28 Şub 2019 Per, saat 08:40 tarihinde Henry Saputra <
> > > > henry.sapu...@gmail.com>
> > > > şunu yazdı:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > On Wed, Feb 27, 2019 at 8:44 PM Markus Weimer 
> > > wrote:
> > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > we've discussed the proposal for the TVM project in [1]. The
> > proposal
> > > > > > itself can
> > > > > > be found on the wiki [2].
> > > > > >
> > > > > > According to the Incubator rules[3] I'd like to call a vote to
> > accept
> > > > the
> > > > > > new
> > > > > > TVM project as a podling in the Apache Incubator.
> > > > > >
> > > > > > A vote for accepting a new Apache Incubator podling is a majority
> > > vote.
> > > > > > Everyone
> > > > > > is welcome to vote, only Incubator PMC member votes are binding. It
> > > > would
> > > > > > be
> > > > > > helpful (but not required) if you could add a comment stating
> > whether
> > > > > your
> > > > > > vote
> > > > > > is binding or non-binding.
> > > > > >
> > > > > > This vote will run for at least 72 hours (but I expect to keep it
> > > open
> > > > > for
> > > > > > longer). Please VOTE as follows:
> > > > > >
> > > > > > [ ] +1 Accept TVM into the Apache Incubator
> > > > > > [ ] +0 Abstain
> > > > > > [ ] -1 Do not accept TVM into the Apache Incubator because ...
> > > > > >
> > > > > > Thank you for everyone who decided to join in in the past
> > > discussions!
> > > > > >
> > > > > > Markus
> > > > > >
> > > > > > [1]:
> > > > > >
> > > > >
> > > >
> > >
> > https://lists.apache.org/thread.html/e2b1fe9ca76422ec80b146a6b120091f2419e2f1c27d57080f39cf6f@%3Cgeneral.incubator.apache.org%3E
> > > > > >
> > > > > > [2]: https://wiki.apache.org/incubator/TVMProposal
> > > > > >
> > > > > > [3]: https://incubator.apache.org/guides/proposal.html#the_vote
> > > > > >
> > > > > >
> > -
> > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >

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

Re: [Proposal] Apache TVM

[Timothy Chen]

Very excited to see this proposed as well.

I’d also like to volunteer mentoring if the community is open too.

Tim

On Fri, Feb 15, 2019 at 10:48 Henry Saputra  wrote:

> HI Markus,
>
> I have been using TVM as part of ML platform work as consumer of the
> project, this is great news!
>
> Would love to come in and help as a Mentor of this project if it is Ok with
> the community.
>
>
> Thanks,
>
> - Henry
>
> On Fri, Feb 15, 2019 at 10:42 AM Markus Weimer  wrote:
>
> > Hi,
> >
> > we'd like to start the discussion of accepting TVM into the incubator.
> > Please see the proposal below. I'd like to highlight a few things for
> > our discussion:
> >
> > (1) The project already follows many Apache ways like meritocracy,
> > open development and such.
> >
> > (2) The project recognizes an in-between state of "reviewer" that it
> > nominates people for between contributor and committer status. We'd
> > like to learn if and how to maintain that in the future.
> >
> > (3) The project contains hardware as a software artifact. We are not
> > aware of another ASF project like that and wonder if and how it
> > affects its acceptance into the incubator.
> >
> > Thanks!
> >
> > Markus
> >
> > === Proposal ===
> >
> > We propose to incubate the TVM project the Apache Software Foundation.
> TVM
> > is a
> > full stack open deep learning compiler stack for CPUs, GPUs, and
> > specialized
> > accelerators. It aims to close the gap between the productivity-focused
> > deep
> > learning frameworks, and the performance- or efficiency-oriented hardware
> > backends.
> >
> > === Background ===
> >
> > There is an increasing need to bring machine learning to a wide diversity
> > of
> > hardware devices. Current frameworks rely on vendor-specific operator
> > libraries
> > and optimize for a narrow range of server-class GPUs. Deploying workloads
> > to new
> > platforms -- such as mobile phones, embedded devices, and accelerators
> > (e.g.,
> > FPGAs, ASICs) -- requires significant manual effort. TVM is an end to end
> > deep
> > learning a compiler that exposes graph-level and operator-level
> > optimizations to
> > provide performance portability to deep learning workloads across diverse
> > hardware back-ends. TVM solves optimization challenges specific to deep
> > learning, such as high-level operator fusion, mapping to arbitrary
> hardware
> > primitives, and memory latency hiding. It also automates optimization of
> > low-level programs to hardware characteristics by employing a novel,
> > learning-based cost modeling method for rapid exploration of program
> > optimizations.
> >
> > Moreover, there is increasing interest in designing specialized hardware
> > which
> > accelerates machine learning. Towards this goal, TVM introduces VTA, an
> > open
> > source deep learning accelerator as part of its stack. The open source
> VTA
> > driver and hardware design is a crucial step toward building software
> > support
> > for future ASICs. The TVM-VTA flow acts as a is the great frontier for
> > researchers and practitioners to explore specialized hardware designs.
> >
> >
> > === Rationale ===
> >
> > Deep learning compilation will be the next frontier of machine learning
> > systems.
> > TVM is already one of the leading open source projects pursuing this
> > direction.
> >
> > Specifically, TVM provides infrastructure to use machine learning to
> > automatically optimize deployment of deep learning programs on diverse
> > hardware
> > backends.
> >
> >
> > === VTA: Open Source Hardware Design ===
> >
> > TVM also contains open source hardware as part of its stack. The VTA
> > hardware
> > design is a fully open sourced deep learning accelerator that allows us
> to
> > experiment with compiler, driver, runtime, and execute the code on FPGA.
> > VTA
> > provides a path to target future ASICs, and build software-driven
> > solutions to
> > co-design future deep learning accelerators.
> >
> > Having an open source hardware design in an ASF project is rare and
> perhaps
> > unprecedented. We put some of our rationale on why it is necessary for
> the
> > community.
> >
> > Deep learning specialized ASICs are going to be at the center of the AI
> > revolution. However, given its early shape, there is no open standard, or
> > even
> > any available information hardware interface that allows an open source
> > software
> > to target to. VTA provides such open source hardware abstraction layer
> and
> > allows us to build in abstractions that can be effectively used to target
> > other
> > deep learning accelerators.
> >
> > Moreover, there is an increasing need for co-designing future of machine
> > learning systems with the hardware abstraction. Having a co-designed open
> > source
> > hardware stack along with the software creates a path for this route. In
> > short,
> > we need open-source hardware to build the best open source software.
> >
> > Finally, we can still view VTA design as “software”, as its source code
> is
> > 

Re: [VOTE] Graduate Apache ServiceComb (incubating)

[Timothy Chen]

+1 (binding)

Tim
On Wed, Sep 26, 2018 at 10:22 AM Matt Sicker  wrote:
>
> +1 (binding)
>
> On Wed, 26 Sep 2018 at 06:02, Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
> > On Wed, Sep 26, 2018 at 12:06 AM Roman Shaposhnik  wrote:
> > > ...Please vote on the resolution pasted below to graduate
> > > Apache ServiceComb from the incubator to the top level project...
> >
> > +1
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> --
> Matt Sicker 

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

Re: [VOTE] Release Apache ServiceComb Java-Chassis (Incubating) version 1.0.0

[Timothy Chen]

+1 binding.

Tim
On Mon, Jul 30, 2018 at 9:58 PM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Casting my vote here.
>
> Regards
> JB
>
> On 28/07/2018 19:41, Mohammad Asif Siddiqui wrote:
> > Hello All,
> >
> > This is a call for vote to release Apache ServiceComb Java-Chassis
> (Incubating) version 1.0.0
> >
> > Apache ServiceComb (Incubating) Community has voted and approved the
> release.
> >
> > Vote Thread :
> https://lists.apache.org/thread.html/cce5f584cf644e62381440813bda26a1d87a84cb0b5304ae1ebeedd8@%3Cdev.servicecomb.apache.org%3E
>
> >
> > Result Thread :
> https://lists.apache.org/thread.html/8c61031d9c81592440c124b6d6f70fc1e9bb194e465018ea2deeb1a4@%3Cdev.servicecomb.apache.org%3E
>
> >
> > Release Notes :
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12342426
>
> >
> > Release Candidate :
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/1.0.0/rc-01/
>
> >
> > Staging Repo :
> https://repository.apache.org/content/repositories/orgapacheservicecomb-1326/
>
> >
> > Release Tag :
> https://github.com/apache/incubator-servicecomb-java-chassis/releases/tag/1.0.0
>
> >
> > Release CommitID : 2d8645355febc215b33818770ae18468aba6146a
> >
> > Keys to verify the Release Candidate :
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
> >
> > Voting will start now ( Saturday, 28th July, 2018) and will remain open
> for atleast 72 hours, Request all IPMC members to give their vote.
> >
> > [ ] +1 Release this package as 1.0.0
> > [ ] +0 No Opinion
> > [ ] -1 Do not release this package because
> >
> > On the behalf of ServiceComb Team
> > Mohammad Asif Siddiqui
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0

[Timothy Chen]

+1 binding as well.

Tim
On Mon, Jul 30, 2018 at 9:58 PM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Casting my vote here.
>
> Regards
> JB
>
> On 28/07/2018 19:50, Mohammad Asif Siddiqui wrote:
> > Hello All,
> >
> > This is a call for vote to release Apache ServiceComb Service-Center
> (Incubating) version 1.0.0
> >
> > Apache ServiceComb (Incubating) Community has voted and approved the
> release.
> >
> > Vote Thread :
> https://lists.apache.org/thread.html/f17a41eb20f36ca4eea7ed1624ebaf66bc8488ebce819e9207017ae1@%3Cdev.servicecomb.apache.org%3E
>
> >
> > Result Thread :
> https://lists.apache.org/thread.html/43474f7082c63abbfa4a102a30704531d127a810e9c1dc6072b5f4c5@%3Cdev.servicecomb.apache.org%3E
>
> >
> > Release Notes :
> https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes-1.0.0.md
>
> >
> > Release Candidate :
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0/rc-03/
>
> >
> > Release Tag :
> https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0
>
> >
> > Release CommitID : fc38b272a288cf322fa309402a98a89dc6b591f4
> >
> > Keys to verify the Release Candidate :
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
> >
> > Guide to build the release from source :
> https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
>
> >
> > Voting will start now(Saturday, 28th July, 2018) and will remain open
> for at-least 72 hours, Request all IPMC members to give their vote.
> >
> > [ ] +1 Release this package as 1.0.0
> > [ ] +0 No Opinion
> > [ ] -1 Do not release this package because...
> >
> > On the behalf of ServiceComb Team
> > Mohammad Asif Siddiqui
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Doris into the Apache Incubator

[Timothy Chen]

+1 (binding)

Been following the discussions and knowing the mentors I believe the team
can continue to improve and learn how the Apache way works.

Tim
On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG)  wrote:
> > ...None of them are affiliated with Baidu Inc., just initial committers
> are...
>
> Ok, thanks for clarifying!
>
> Here's my +1
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Warble into the Apache Incubator

[Timothy Chen]

+1

Tim

On Sat, Jun 9, 2018 at 10:15 AM Daniel Takamori  wrote:

> +1
>
> On 2018/06/08 14:43:53, Chris Thistlethwaite  wrote:
> > Hi All (again),
> >
> > I'd like to start a vote on accepting Warble into the Apache Incubator.
> >
> > https://lists.apache.org/thread.html/1d62a2948d047cea38e6f01f92d5f138f8
> > 3acd2c9d86349023fb28e4@%3Cgeneral.incubator.apache.org%3E
> >
> > The ASF voting rules are described:
> >
> > https://www.apache.org/foundation/voting.html
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote
> > for which only Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as follows
> > [ ] +1 Accept Warble into the Apache Incubator
> > [ ] +0 Abstain.
> > [ ] -1 Do not accept Warble into the Incubator
> >
> > The proposal is listed below, but you can also access it on the wiki:
> > https://wiki.apache.org/incubator/WarbleProposal
> >
> >
> > Thank you,
> > Chris T.
> >
> >
> >
> > = Apache Warble Proposal =
> >
> > == Abstract ==
> >
> > Apache Warble is a distributed endpoint monitoring solution where
> > the agent is hosted on your own hardware. The aim of Warble is to
> > produce a more balanced and less binary view of services and
> > systems, lowering the rates of false positives while also providing
> > greater insight into possible peering issues and proactive trend
> > analysis.
> >
> > ==Proposal ==
> >
> > The goal of Warble will be to bring internal control of
> > distributed monitoring back to the end user. Warble can be used as
> > an independent service running on your own infrastructure
> > monitoring other services in your infrastructure.
> >
> > == Background and Rationale ==
> >
> > The beginning of this project was prompted by the service
> > pingmybox.com (PMB) going end of life. This brought up
> > conversation about FOSS services that can monitor internal and
> > external services. PMB offered a unique code base to build this
> > service upon a known infrastructure.
> >
> > ===Initial Goals ===
> >
> > Bring PMB code into the ASF, refactor the client/server into
> > a more reusable structure. Further reuse of code gives us the a
> > great starting point to build a starting point.
> >
> > ==Current Status ==
> >
> > The software exists as a proprietary service. We wish to convert
> > this to a FLOSS solution.
> >
> > ==Meritocracy ==
> >
> > The initial PMC list covers new folks coming into the ASF.
> >
> > ==Community ==
> >
> > There exists a large user-base of software like Warble, as well
> > as existing users of the old propietary service. It is our hope
> > that we can convert a great deal of these to contributors and
> > testers for the new open source product.
> >
> > ==Core Developers ==
> >
> > The initial set of developers are a lot of newcomers:
> >
> > * Daniel Gruno 
> > * Chris Thistlethwaite 
> > * Haig Didizian 
> > * Andrew Karetas 
> > * Chandler Claxton 
> > * Luke Stevens 
> > * Mike Andescavage 
> > * Chris Lambertus 
> >
> > ==Known Risks ==
> >
> > There are many existing services that provide external
> > monitoring. They are well established and have large user bases.
> >
> > ===Orphaned Products ===
> >
> > The initial PMC has great interest in open source projects, though
> > no formal projects have been run.
> >
> >
> > ===Inexperience with Open Source ===
> >
> > Most of the initial PPMC members are new to the ASF and some are
> > new to open source projects. However, all are very interested in
> > giving back to the community and projects.  Having said that, there
> > are several people involved with extensive experience in the
> > Apache Way and our procedures and processes.
> >
> > ===Homogenous Developers ===
> >
> > The initial set of developers are employed by a variety of
> > companies, located across the world, and used to working on a
> > variety of distributed projects.
> >
> > ===Reliance on Salaried Developers ===
> >
> > We do not expect the interest of the proposed initial PMC to be
> > directly tied to current employment, but will actively seek to
> > grow our volunteer base regardless.
> >
> > ===Relationships with Other Apache Products ===
> >
> > Not much to say here. Many ASF projects make use of the proprietary
> > offering, we wish to open source it and have people engage in the
> > development of the project. There are, at present, indirect
> > relationships in that some dependencies are built on Apache
> > software, but these are generally by proxy and does not merit
> > considering Warble as a sub-project of an existing TLP.
> >
> >
> > ==Initial Source ==
> >
> > The initial task of the PMC will be assessing what we wish the
> > project to contain. The proprietary 

Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.1.0

[Timothy Chen]

+1 binding

Compiled from source and ran all the unit tests.
LICENSE, NOTICE, ASF headers looks good to me.

Tim

On Fri, Mar 23, 2018 at 5:15 PM, Justin Mclean  wrote:
> Hi,
>
> +1 binding
>
> I checked:
> - name includes incubating
> - DISCLAIMER exists
> - LICENSE and NOTICE all good
> - No unexpected binary files
> - All source files have ASF headers
> - Can compile form source
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Timothy Chen]

+1 as well, I think the work Dr. Elephant is doing can also be
potentially applied to more than Spark and Hadoop.

Tim

On Tue, Mar 6, 2018 at 8:38 PM, Kevin A. McGrail  wrote:
> I'm intrigued by the proposal and the product. I'm a 0.5+.
>
> I'd love to know more about why LI put it on GitHub and what problems it's
> having that are leading to a foundation.
>
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
> On Tue, Mar 6, 2018 at 8:27 PM, Gangumalla, Uma 
> wrote:
>
>> I would +1 to have as a separate project instead of pushing under Hadoop.
>> When a project can sustain by having potential to build community on its
>> own and can run logically as independent module, I feel that’s good enough
>> to start as separate project.
>>
>> I could not recall the discussions on removal of Vaidya package from
>> Hadoop. If someone remembers, it would be great to know the reasons for
>> removal of that package from Hadoop base. [ probably at the time of
>> mavenization ? ]
>>
>> Regards,
>> Uma
>>
>> On 3/6/18, 3:17 PM, "md...@cloudera.com on behalf of Mike Drob" <
>> md...@cloudera.com on behalf of md...@apache.org> wrote:
>>
>> Why does Dr. Elephant make sense as a separate project instead of
>> contributing to Hadoop directly?
>>
>> What is the relationship between Dr. Elephant and the (now seemingly
>> defunct) Hadoop Vaidya?
>>
>> On Tue, Mar 6, 2018 at 5:08 PM, Carl Steinbach  wrote:
>>
>> > Hi,
>> >
>> > I would like to propose Dr. Elephant as an Apache Incubator
>> > project. The proposal is available as a draft at
>> > https://wiki.apache.org/incubator/DrElephantProposal. I have also
>> > included the text of the proposal below.
>> >
>> > Any feedback from the community is much appreciated.
>> >
>> > Thanks.
>> >
>> > - Carl
>> >
>> >
>> > = ABSTRACT =
>> >
>> > Dr. Elephant is a performance monitoring and tuning service for
>> Apache
>> > Hadoop and Apache Spark jobs and workflows. While the system is
>> > primarily aimed at developers, we have discovered that it is also
>> > popular with cluster operators who use it to monitor the health of
>> > workloads running on their clusters.
>> >
>> > = PROPOSAL =
>> >
>> > Dr. Elephant was open sourced by LinkedIn in 2016 and is currently
>> > hosted on GitHub. We believe that being a part of the 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 the Apache
>> > Software Foundation. The code is already under Apache License 2.0.
>> > Both the source code and documentation are hosted on Github.
>> >
>> >  * Code: http://github.com/linkedin/dr-elephant
>> >  * Documentation: https://github.com/linkedin/dr-elephant/wiki
>> >
>> > = Background =
>> >
>> > Dr. Elephant is a service that helps users of Apache Hadoop and
>> Apache
>> > Spark understand, analyze, and improve the performance of jobs and
>> > workflows running on their clusters. It automatically gathers
>> metrics,
>> > performs analysis, and presents the results along with actionable
>> > advice. The goal of the project is to improve developer productivity
>> > and increase cluster efficiency by reducing the time and domain
>> > expertise required to diagnose and treat sick jobs. It analyzes
>> Hadoop
>> > and Spark jobs using a set of configurable, extensible, rule-based
>> > heuristics that provide insights on job performance, and then uses
>> > this information to provide recommendations about how to tune jobs to
>> > make them run more efficiently.
>> >
>> > Dr. Elephant was open sourced in 2016 after two years of
>> > successful production use at Linkedin. In the time since many new
>> > features have been added including support for the Oozie and Airflow
>> > workflow schedulers, improved metrics, and enhancements to the Spark
>> > history fetcher and Spark heuristics. It is also important to note
>> > that many of these contributions came from developers outside of
>> > LinkedIn. We have also been happy to see that many people have been
>> > able to benefit from running Dr. Elephant including companies like
>> > Airbnb, Foursquare, Hulu, and Pinterest.
>> >
>> > = RATIONALE =
>> >
>> > Dr. Elephant's entry to the ASF will be beneficial to both the
>> > Dr. Elephant and Apache communities. Dr. Elephant has greatly
>> > benefited from its open source roots. Its community and adoption has
>> > grown greatly as a result. More importantly, the feedback from the
>> > community, whether 

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Timothy Chen]

+1 binding

Reviewed license and release artifacts / signatures.

Tim

On Fri, Mar 2, 2018 at 12:05 AM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Reviewed:
> * build from src
> * ASF headers
> * checksum and signatures
> * DISCLAIMER
> * License is OK
> * We can do a minor improvement on the NOTICE formating
>
> Thanks !
> Regards
> JB
>
> On 02/28/2018 02:25 PM, Mohammad Asif Siddiqui wrote:
> > Hello All,
> >
> > This is a call for vote to release Apache ServiceComb Service-Center
> (Incubating) version 1.0.0-m1.
> >
> > Apache ServiceComb (Incubating) Community has voted and approved the
> release.
> >
> > Vote Thread:
> https://lists.apache.org/thread.html/b2d87628d019c069f478c56cadaf794112add210c504e3ac4c3056e5@%3Cdev.servicecomb.apache.org%3E
> >
> > Result Thread:
> https://lists.apache.org/thread.html/527a77d1467880602a7d679bd21d281b58fb365fa29b18a96a2a3676@%3Cdev.servicecomb.apache.org%3E
> >
> > Release Notes:
> https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes.md
> >
> > Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0-m1/
> >
> > Release Tag:
> https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0-m1
> >
> > Release CommitID:  8d40fc3b10e99c9084a7b62504226007660ad6de
> >
> > Keys to Verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
> >
> > Guide to build the release from Source:
> https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
> >
> > Voting will start now(Wednesday, February 28, 2018) and will remain open
> for next 72 hours, Request all IPMC members to give their vote.
> >
> > [ ] +1 Release this package as 1.0.0-m1.
> > [ ] +0 No Opinion.
> > [ ] -1 Do not release this package because...
> >
> > Regards
> > Asif
> >
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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 

IPMC join request

[Timothy Chen]

Hi all,

I'd like to request joining IPMC, initially to help mentor ServiceComb
incubator project but also looking forward to help mentor other Apache
incubator projects. I'm not yet an Apache member.

I've been PPMC for Apache Drill (saw incubation to TLP) and Mesos.

Let me know if there is any more info needed.

Thanks!

Tim

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

Re: [VOTE] Accept ServiceComb into the Apache Incubator

[Timothy Chen]

/bradfitz/gomemcache
>>   * google.golang.org/genproto
>>   * github.com/astaxie/beego
>>   * gopkg.in/yaml.v2
>>   * github.com/cockroachdb/cmux
>>   * github.com/casbin/casbin
>>   * github.com/coreos/etcd
>>   * github.com/coreos/go-semver
>>   * github.com/coreos/go-systemd
>>   * github.com/jonboulle/clockwork
>>   * github.com/prometheus/client_golang
>>   * github.com/prometheus/client_model
>>   * github.com/prometheus/common
>>   * github.com/prometheus/procfs
>>   * github.com/hsluoyz/casbin
>>   * github.com/coreos/pkg
>>   * github.com/garyburd/redigo
>>   * github.com/spf13/cobra
>>   * github.com/google/btree
>>   * github.com/matttproud/golang_protobuf_extensions
>>
>> Copyright (c) 2013, The GoGo Authors.
>>   * github.com/gogo/protobuf
>>
>> Copyright 2010 The Go Authors.
>>   * github.com/golang/protobuf
>>
>> Service-Center Frontend depends on
>> Open-Source Projects(Organized by License)
>> MIT:
>>   * angular
>>   * angular-animate
>>   * angular-aria
>>   * angular-material-data-table
>>   * angular-material
>>   * angular-messages
>>   * angular-mocks
>>   * angular-resource
>>   * angular-route
>>   * angular-sanitize
>>   * angular-swagger-ui
>>   * angular-translate-loader-static-files
>>   * angular-translate
>>   * angular-ui-bootstrap
>>   * angular-ui-router
>>   * bootstrap-less-only
>>   * bootstrap-sass-official
>>   * chart.js
>>   * Components-font-awesome
>>   * mmumshad/angular-yamljs
>>   * jeremyfa/yaml.js
>>
>> Apache-2.0:
>>   * Json-formatter
>>
>> BSD
>>   * Angular-charts.js
>>   * JS Foundation
>>   * jQuery
>>
>> == Required Resources ==
>> === Mailing Lists ===
>>   * priv...@servicecomb.incubator.apache.org (moderated subscriptions)
>>   * comm...@servicecomb.incubator.apache.org
>>   * d...@servicecomb.incubator.apache.org
>>   * iss...@servicecomb.incubator.apache.org
>>
>> === Source Control ===
>>   *
>>
>> https://git-wip-us.apache.org/repos/asf/incubator-servicecomb-java-chassis.git
>>   *
>>
>> https://git-wip-us.apache.org/repos/asf/incubator-servicecomb-service-center.git
>>   * https://git-wip-us.apache.org/repos/asf/incubator-servicecomb-saga.git
>>   *
>> https://git-wip-us.apache.org/repos/asf/incubator-servicecomb-website.git
>>
>> === Issue Tracking ===
>> JIRA Project ServiceComb
>>
>> === Initial Committers ===
>>   * Ning Jiang
>>   * Qi Zhang
>>   * Xiang Yin
>>   * JiMin Wu
>>   * Bao Liu
>>   * Mohammad Asif Siddiqui
>>   * Sukesh A C
>>   * Yihua Cui
>>   * Roman Shaposhnik
>>   * Jean-Baptiste Onofre
>>   * Timothy Chen
>>
>> === Additional Interested Contributors ===
>>   * Jian Zhang cos...@gmail.com
>>   * Bing Wang wangbb0...@gmail.com
>>   * Ven Jiang venji...@gmail.com
>>   * GeekTJS josephy...@gmail.com
>>   * Li Zhou eacdy0...@126.com
>>   * Haiwei Zhang haiwei...@foxmail.com
>>   * Yetiea yet...@gmail.com
>>
>> === Affiliations ===
>>   * Huawei: Ning Jiang, Qi Zhang, Xiang Yin, JiMin Wu, Bao Liu, Sukesh A
>> C,
>> Mohammad Asif Siddiqui, Yihua Cui
>>   * Stealth: Roman Shaposhnik
>>   * Talend: Jean-Baptiste Onofré
>>   * Hyperpilot: Timothy Chen
>>
>> === Sponsors ===
>> Champion
>>   * Roman Shaposhnik[r...@apache.org]
>> Nominated Mentors
>>   * Roman Shaposhnik[r...@apache.org]
>>   * Jean-Baptiste Onofre [jbono...@apache.org]
>>   * Timothy Chen[tnac...@apache.org]
>>
>> === Sponsoring Entity ===
>>   * We are requesting the Incubator to sponsor this project.
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Graduate Apache CarbonData Project from the Incubator

[Timothy Chen]

+1

Tim

> On Mar 15, 2017, at 9:50 AM, Julian Hyde  wrote:
> 
> +1 (binding)
> 
> Well done, and good luck.
> 
> Julian
> 
> 
>> On Mar 15, 2017, at 8:32 AM, Pierre Smits  wrote:
>> 
>> +1 (non binding).
>> 
>> Best regards,
>> 
>> Pierre Smits
>> 
>> ORRTIZ.COM 
>> OFBiz based solutions & services
>> 
>> OFBiz Extensions Marketplace
>> http://oem.ofbizci.net/oci-2/
>> 
>>> On Wed, Mar 15, 2017 at 3:40 PM, Niclas Hedhman  wrote:
>>> 
>>> +1 (binding)
>>> 
>>> On Wed, Mar 15, 2017 at 8:39 PM, Jean-Baptiste Onofré 
>>> wrote:
>>> 
 Hi IPMC,
 
 Following the previous discussion, please vote on the draft resolution
 proposed by the Apache CarbonData PPMC below, which establishes Apache
 CarbonData as a new top-level project at the Apache Software Foundation,
>>> as
 follows:
 
 [ ] +1, Graduate Apache CarbonData from the Incubator.
 [ ] +0, Don't care.
 [ ] -1, Don't graduate Apache CarbonData from the Incubator (provide
 details)
 
 The full text of the resolution is bellow.
 
 If approved by the Apache Incubator PMC members, the proposed resolution
 will be submitted to the Board of Directors for their consideration.
 
 Thanks !
 
 Regards
 JB
 
 The full-text of the draft resolution proposed by the Apache CarbonData
 PPMC:
 
 X. Establish the Apache CarbonData Project
 
  WHEREAS, the Board of Directors deems it to be in the best
  interests of the Foundation and consistent with the
  Foundation's purpose to establish a Project Management
  Committee charged with the creation and maintenance of
  open-source software, for distribution at no charge to
  the public, related to an indexed columnar data format
  for fast analytics on big data platform.
 
  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the "Apache CarbonData Project",
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further
 
  RESOLVED, that the Apache CarbonData Project be and hereby is
  responsible for the creation and maintenance of software
  related to a unified programming model for both batch and
  streaming data processing, enabling efficient execution across
  diverse distributed execution engines and providing extensibility
  points for connecting to different technologies and user
  communities; and be it further
 
  RESOLVED, that the office of "Vice President, Apache CarbonData"be
  and hereby is created, the person holding such office to
  serve at the direction of the Board of Directors as the chair
  of the Apache CarbonData Project, and to have primary responsibility
  for management of the projects within the scope of
  responsibility of the Apache CarbonData Project; and be it further
 
  RESOLVED, that the persons listed immediately below be and
  hereby are appointed to serve as the initial members of the
  Apache CarbonData Project:
 
   * Liang Chen 
   * Jean-Baptiste Onofré 
   * Henry Saputra 
   * Uma Maheswara Rao G 
   * Jenny MA 
   * Jacky Li 
   * Vimal Das Kammath 
   * Jarray Qiu 
 
  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Chen be
  appointed to the office of Vice President, Apache CarbonData, to
  serve in accordance with and subject to the direction of the
  Board of Directors and the Bylaws of the Foundation until
  death, resignation, retirement, removal or disqualification,
  or until a successor is appointed; and be it further
 
  RESOLVED, that the initial Apache CarbonData PMC be and hereby is
  tasked with the creation of a set of bylaws intended to
  encourage open development and increased participation in the
  Apache CarbonData Project; and be it further
 
  RESOLVED, that the Apache CarbonData Project be and hereby
  is tasked with the migration and rationalization of the Apache
  Incubator CarbonData podling; and be it further
 
  RESOLVED, that all responsibilities pertaining to the Apache
  Incubator CarbonData podling encumbered upon the Apache Incubator
  Project are hereafter discharged.
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>>> 
>>> 
>>> --
>>> Niclas Hedhman, Software Developer
>>> http://polygene.apache.org  - New Energy for Java
>>> 
> 
> 
> 

Re: [VOTE] Accept Airflow into the Incubator

[Timothy Chen]

+1 (non-binding)

Tim

On Fri, Mar 25, 2016 at 9:37 AM, Arthur Wiedmer
 wrote:
> +1 (non-binding)
>
> Regards,
> Arthur
> On Mar 25, 2016 9:27 AM, "Chris Nauroth"  wrote:
>
>> +1 (binding)
>>
>> --Chris Nauroth
>>
>>
>>
>>
>> On 3/24/16, 8:00 PM, "Siddharth Anand"  wrote:
>>
>> >Following the discussion earlier:
>> >https://s.apache.org/AirflowDiscussion
>> >
>> >I would like to call a VOTE for accepting Airflow as a new incubator
>> >project.
>> >
>> >The proposal is available at:
>> >https://wiki.apache.org/incubator/AirflowProposal
>> >
>> >The proposal is also included at the bottom of this email.
>> >
>> >Vote is open until at least Tues, 29 March 2016, 23:59:00 PDT
>> >[ ] +1 accept Airflow into the Apache Incubator
>> >[ ] ±0
>> >[ ] -1 because...
>> >
>> >+1 (non-binding)
>> >
>> >Thanks,
>> >-s (Sid)
>> >
>> >
>> >== Abstract ==
>> >
>> >Airflow is a workflow automation and scheduling system that can be
>> >used to author and manage data pipelines.
>> >
>> >== Proposal ==
>> >
>> >Airflow provides a system for authoring and managing workflows a.k.a.
>> >data pipelines a.k.a. DAGs (Directed Acyclic Graphs). The developer
>> >authors DAGs in Python using an Airflow-provided framework. He/She
>> >then executes the DAG using Airflow¹s scheduler or registers the DAG
>> >for event-based execution. A web-based UI provides the developer with
>> >a range of options for managing and viewing his/her data pipelines.
>> >Background
>> >
>> >Airflow was developed at Airbnb to enable easier authorship and
>> >management of DAGs than were possible with existing solutions such as
>> >Oozie and Azkaban. For starters, both Oozie and Azkaban rely on one or
>> >more XML or property files to be bundled together to define a
>> >workflow. This separation of code and config can present a challenge
>> >to understanding the DAG - in Azkaban, a DAG¹s structure is reflected
>> >by its file system tree and one can find himself/herself traversing
>> >the file system when inspecting or changing the structure of the DAG.
>> >Airflow workflows, on the other hand, are simply and elegantly defined
>> >in Python code, often a single file. Airflow merges the powerful
>> >Web-based management aspects of projects like Azkaban and Oozie with
>> >the simplicity and elegance of defining workflows in Python. Airflow,
>> >less than a year old in terms of its Open Source launch, is currently
>> >used in production environments in more than 30 companies and boasts
>> >an active contributor list of more than 100 developers, the vast
>> >majority of which (>95%) are outside of Airbnb.
>> >
>> >We would like to share it with the ASF and begin developing a
>> >community of developers and users within Apache.
>> >
>> >== Rationale ==
>> >
>> >Many organizations (>30) already benefit from running Airflow to
>> >manage data pipelines. Our 100+ contributors continue to provide
>> >integrations with 3rd party systems through the implementation of new
>> >hooks and operators, both of which are used in defining the tasks that
>> >compose workflows.
>> >
>> >== Current Status ==
>> >
>> >=== Meritocracy ===
>> >
>> >Our intent with this incubator proposal is to start building a diverse
>> >developer community around Airflow following the Apache meritocracy
>> >model. Since Airflow was open-sourced in mid-2015, we have had fast
>> >adoption and contributions by multiple organizations the world over.
>> >We plan to continue to support new contributors and we will work to
>> >actively promote those who contribute significantly to the project to
>> >committers.
>> >
>> >=== Community ===
>> >
>> >Airflow is currently being used in over 30 companies. We hope to
>> >extend our contributor base significantly and invite all those who are
>> >interested in building large-scale distributed systems to participate.
>> >
>> >=== Core Developers ===
>> >
>> >Airflow is currently being developed by four engineers: Maxime
>> >Beauchemin, Siddharth Anand, Bolke de Bruin, and Chris Riccomini.
>> >Chris is a member of the Apache Samza PMC and a contributor to various
>> >Apache projects, including Apache Kafka and Apache YARN. Maxime,
>> >Siddharth, and Bolke have contributed to Airflow.
>> >
>> >=== Alignment ===
>> >The ASF is the natural choice to host the Airflow project as its goal
>> >of encouraging community-driven open-source projects fits with our
>> >vision for Airflow.
>> >
>> >== Known Risks ==
>> >
>> >=== Orphaned Products ===
>> >
>> >The core developers plan to work part time on the project. There is
>> >very little risk of Airflow being abandoned as all of our companies
>> >rely on it.
>> >
>> >=== Inexperience with Open Source ===
>> >
>> >All of the core developers have experience with open source
>> >development. Chris is a member of the Apache Samza PMC and a
>> >contributor to various Apache projects, including Apache Kafka and
>> >Apache YARN. Bolke is 

Re: [VOTE] Accept Concerted into the Apache Incubator

[Timothy Chen]

+1 non binding 

Tim


> On Oct 11, 2015, at 4:59 PM, Luke Han  wrote:
> 
> +1 (non-binding)
> 
> 
> Best Regards!
> -
> 
> Luke Han
> 
> On Mon, Oct 12, 2015 at 4:33 AM, Alan D. Cabrera 
> wrote:
> 
>> +1 - binding
>> 
>> 
>> Regards,
>> Alan
>> 
>>> On Oct 9, 2015, at 8:55 AM, Atri Sharma  wrote:
>>> 
>>> Hi all,
>>> 
>>> Following the discussion about Concerted I would like to call a vote for
>>> accepting Concerted as a new incubator project.
>>> 
>>> The proposal text is included below, and available on the wiki:
>>> 
>>> https://wiki.apache.org/incubator/ConcertedProposal
>>> 
>>> The vote is open for 72 hours:
>>> 
>>> [ ] +1 accept Concerted in the Incubator
>>> [ ] ±0
>>> [ ] -1 (please give reason)
>>> 
>>> Regards,
>>> 
>>> Atri
>>> 
>>> = Abstract =
>>> 
>>> Concerted is an in memory write less read more engine aimed to provide
>>> extreme read performance with very high degree of concurrency and
>>> scalability and focus on minimizing own resource footprint.
>>> 
>>> = Proposal =
>>> Concerted is built on the principal that a new type of workload is
>>> dominating the scene and is now needed to be supported. These are the
>> large
>>> data set analytical workloads being analyzed or used on large clusters or
>>> high power machines. Large analytical workloads depend on the ability to
>>> query large data sets efficiently and in high concurrency while
>> maintaining
>>> semantics such as immediate consistency. An in memory engine designed to
>>> support extreme read queries while providing support for aggregation
>>> through various features (such as multidimensional representation of
>>> tuples) will accelerate many usecases around large scale analytics.
>>> 
>>> Concerted believes that best understanding of user application lies with
>>> user application developer. The need for massive read scaling should be
>> on
>>> demand and should be flexible to the level that user can decide as to
>> which
>>> representation and access of data suits his/her current requirements.
>>> Hence, Concerted is not built in a traditional client/server model.
>>> Concerted provides users with an API which can be used to load, read,
>>> update and delete data. User chooses which data structure has to be used
>>> for his current requirements. All API access is covered by Concerted's
>>> internal systems like lock manager, transaction manager and cache manager
>>> which ensure that reads scale to high level in every API call.
>>> 
>>> Concerted is a Do It Yourself in memory platform for making in memory
>>> supporting engines. The use case we think of is supporting big data
>>> warehouses like Hive, but there are endless use cases for a custom,
>> highly
>>> scalable in memory platform.
>>> 
>>> The goal of this proposal is to leverage an existing code base available
>> on
>>> Github and licensed under the Apache License 2.0 to build a community
>>> around the project. Currently the community consists of existing hackers
>> of
>>> Concerted as well as people who have been following and associated with
>> the
>>> project since a while as well as database experts who are excited about
>>> building a project like this. We are hoping that entering into Apache
>> would
>>> help us attract more contributors as well as connect with existing big
>> data
>>> projects like Apache Hive, Apache HAWQ, Apache Storm, Apache Tajo, Apache
>>> Spark, Apache Geode to leverage their community base while assisting in
>>> their use cases with Concerted. We had a discussion with founders of
>> Apache
>>> Tajo and they showed interest in using Concerted for some of their use
>>> cases.
>>> = Background =
>>> Relational databases were built with the cost of physical memory in mind.
>>> The cost is no longer very relevant and physical memory is now available
>> on
>>> demand. Another driving factor behind Concerted is that there is a
>> paradigm
>>> shift with big data coming into picture. Disk IO speeds are more of a
>>> bottleneck than ever before. Combining the read dominance of analytical
>>> workload with the speed of in memory structures, Concerted fits the
>> current
>>> scene. Also, supporting OLAP workloads with in memory support for faster
>>> read constant queries and joins will be useful.
>>> 
>>> = Rationale =
>>> As explained above, large analytical workloads need an in memory
>>> lightweight engine which supports massive read concurrency, ground level
>>> support for aggregations and analytics, extreme scalability and high read
>>> performance, along with the engine being very light itself. Concerted
>> aims
>>> to solve these needs. Concerted is designed and built with three goals as
>>> objectives:
>>> 
>>> 
>>> Performance
>>>   To provide high performance access to data from a large number of
>> rows,
>>> Concerted uses efficient representation and in memory indexing of data
>>> coupled with high performance transactions, custom transactions and

Re: [VOTE] Accept Mysos into the Apache Incubator

[Timothy Chen]

+1

Tim

On Thu, May 28, 2015 at 9:26 AM, Chris Aniszczyk z...@twitter.com.invalid 
wrote:
 +1

 On Thu, May 28, 2015 at 11:14 AM, Jake Farrell jfarr...@apache.org wrote:

 Based on the earlier discussion in thread [1], I would like to call a VOTE
 to accept Mysos, an Apache Mesos framework for running MySQL instances, as
 a new Apache Incubator project.

 The proposal is available on the wiki at [2] and is also attached below

 The VOTE is open for at least the next 72 hours:

   [ ] +1 Accept Mysos into the Apache Incubator
   [ ] ±0
   [ ] -1 Do not accept Mysos into the Apache Incubator because...

 I would like to get the voting started with my own +1

 Thank you
 -Jake

 [1]: http://s.apache.org/2vm
 [2]: https://wiki.apache.org/incubator/MysosProposal



 Mysos Proposal

 Abstract

 Mysos is an Apache Mesos framework for running MySQL instances.

 Proposal

 Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the
 management of MySQL instances. It is designed to offer:

 Efficient hardware utilization through multi-tenancy (in
 performance-isolated containers)
 High reliability through preserving the MySQL state during failure and
 automatic backing up to/restoring from HDFS
 An automated self-service option for bringing up new MySQL clusters
 High availability through automatic MySQL master failover
 An elastic solution that allows users to easily scale up and down a MySQL
 cluster by changing the number of slave instances
 Background

 Initial development of Mysos was done at Twitter, and its codebase was
 recently open sourced. This proposal is for Mysos to join the Apache
 Incubator.

 Rationale

 Mysos is built to be used by anyone who desires to run MySQL on Apache
 Mesos, and in the near-future it will take advantage of state primitives
 that are being added to the Mesos core:
 https://issues.apache.org/jira/browse/MESOS-1554

 Furthermore, the rapid growth of Mysos community is empowered by open
 source. We believe the Apache Foundation is a great fit as the long-term
 home for Mysos, as it provides an established process for community-driven
 development and decision making by consensus.

 Initial Goals

 Move the existing codebase to Apache
 Integrate with the Apache development process
 Ensure all dependencies are compliant with Apache License version 2.0
 Strengthen and grow the Mysos community
 Incremental development and releases per Apache guidelines
 Current Status

 Mysos was originally born out of a project within Twitter. The original
 committers (Twitter) are working with Mesosphere and Percona to fully open
 source the code and make it ready for incubation at Apache.

 The Mysos source is currently hosted at GitHub, which will be used to seed
 the Apache git repository.

 Meritocracy

 We plan to invest in supporting a meritocracy. We will discuss the
 requirements in an open forum. Several companies have already expressed
 interest in this project, and we intend to invite additional developers to
 participate. We will encourage and monitor community participation so that
 privileges can be extended to those that contribute.

 Community

 By bringing Mysos into Apache, we believe that the community will grow even
 bigger.

 Core Developers

 Mysos was initially developed as a collaboration between Twitter and
 Mesosphere.

 Alignment

 We believe that having Mysos at Apache will help further the growth of the
 big-data community, as it will encourage cooperation within the greater
 ecosystem of projects spawned by Apache Mesos.

 Known Risks

 Orphaned Products

 Mysos is being used and developed by companies we work for so the companies
 have an interest in its continued vitality.

 Given strong interest we've had since open sourcing Mysos, we anticipate
 we'll grow a sustainable community that will expand contributors and keep
 it active as the Mesos core evolves.

 Inexperience with Open Source

 Most of the committers have experience at Apache, whether it's through
 Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were
 both shepherded through the ASF incubator process and have graduated to
 become successful and diverse open source projects. We also have Jake
 Farrell as an ASF Champion to help us through incubation.

 Homogenous Developers

 Initial committers come from a number of companies. Our intention is
 increase the diversity of contributing developers and their affiliations,
 and we'll recognize contributions and contributors as the community grows
 at Apache. We encouraged by interest in the project thus far.

 Reliance on Salaried Developers

 It is expected that Mysos development will occur on both salaried time and
 on volunteer time, after hours. The majority of initial committers are paid
 by their employers to contribute to this project. However, they are all
 passionate about the project, and we are confident that the project will
 continue even if no salaried developers contribute to the project. We are
 committed 

Re: [VOTE] Graduate Apache Parquet from the Incubator

[Timothy Chen]

+1 as well

Tim

On Mon, Apr 13, 2015 at 9:44 AM, Henry Saputra henry.sapu...@gmail.com wrote:
 +1

 Awesome job guys

 On Monday, April 13, 2015, Jake Farrell jfarr...@apache.org wrote:

 This thread is to start a vote on the graduation resolution Apache Parquet
 has approved on the dev list with 14 positive votes (11 PPMC (4 from IPMC
 members), 3 community)

 Status page: http://incubator.apache.org/projects/parquet.html
 Graduation discussion: http://s.apache.org/8qU
 Graduation resolution: http://s.apache.org/w7

 Apache Parquet has been apart of the Incubator since May 2014 and in that
 time has

 * Had successful IPMC approved releases
 * Expanded the PPMC with new members
 * Worked and submitted fixes in other Apache projects to improve Parquet
 support
 * A successful community vote to graduate with 14 positive votes

 I would like to get the voting started with my own +1

 Please vote

 [ ] +1 Graduate Apache Parquet as a TLP
 [ ] +0
 [ ] -1 Don't graduate Apache Parquet as a TLP because…

 Voting will end in 72 hours, i.e. 12:00 UTC on 2015-04-16
 http://www.timeanddate.com/countdown/to?iso=20150416T12

 -Jake



 === Board Resolution ==

 Establish the Apache Parquet Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to the
 public, related to a columnar storage format for Hadoop.

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

 RESOLVED, that the Apache Parquet Project be and hereby is
 responsible for the creation and maintenance of software
 related to a columnar storage format for Hadoop; and be it further

 RESOLVED, that the office of Vice President, Apache Parquet be
 and hereby is created, the person holding such office to
 serve at the direction of the Board of Directors as the chair
 of the Apache Parquet Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache Parquet Project; and be it further

 RESOLVED, that the persons listed immediately below be and
 hereby are appointed to serve as the initial members of the
 Apache Parquet Project:

* Chris Aniszczyk caniszc...@apache.org javascript:;
* Ryan Blue b...@apache.org javascript:;
* Jonathan Coveney jcove...@apache.org javascript:;
* Tianshuo Deng tians...@apache.org javascript:;
* Jake Farrell jfarr...@apache.org javascript:;
* Marcel Kornacker mar...@apache.org javascript:;
* Mickael Lacour mlac...@apache.org javascript:;
* Julien Le Dem jul...@apache.org javascript:;
* Alex Levenson alexleven...@apache.org javascript:;
* Nong Li n...@apache.org javascript:;
* Todd Lipcon t...@apache.org javascript:;
* Chris Mattmann mattm...@apache.org javascript:;
* Aniket Mokashi aniket...@apache.org javascript:;
* Lukas Nalezenec lu...@apache.org javascript:;
* Brock Noland br...@apache.org javascript:;
* Wesley Graham Peck wesleyp...@apache.org javascript:;
* Remy Pecqueur rpecqu...@apache.org javascript:;
* Dmitriy Ryaboy dvrya...@apache.org javascript:;
* Roman Shaposhnik r...@apache.org javascript:;
* Daniel Weeks dwe...@apache.org javascript:;
* Tom White tomwh...@apache.org javascript:;

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julien Le Dem
 be appointed to the office of Vice President, Apache Parquet, to
 serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification,
 or until a successor is appointed; and be it further

 RESOLVED, that the initial Apache Parquet PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Parquet Project; and be it further

 RESOLVED, that the Apache Parquet Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator Parquet podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Parquet podling encumbered upon the Apache Incubator
 Project are hereafter discharged.


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

Re: [VOTE] Accept Apache AsterixDB in to the Incubator

[Timothy Chen]

+1 (non-binding)

Tim

 On Feb 22, 2015, at 10:59 AM, Alan D. Cabrera l...@toolazydogs.com wrote:
 
 +1 binding
 
 
 Regards,
 Alan
 
 On Feb 19, 2015, at 9:38 PM, Mattmann, Chris A (3980) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
 That said, I would like to propose Apache AsterixDB as an
 Incubator project. I am now calling a VOTE to accept AsterixDB
 into the Apache Incubator. This VOTE will run for at least 72 hours.
 
 [ ] +1 Accept Apache AsterixDB into the Incubator
 [ ] +0 Don’t care.
 [ ] -1 Don’t accept Apache AsterixDB into the Incubator because..
 

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

Re: [VOTE] Accept Myriad into the Apache Incubator

[Timothy Chen]

+1!

Tim

On Sat, Feb 21, 2015 at 10:10 PM, Naresh Agarwal
naresh.agar...@inmobi.com wrote:
 +1

 Thanks
 Naresh
 On 22 Feb 2015 11:14, Mohit Soni mohitsoni1...@gmail.com wrote:

 Definitely a +1




 Thanks

 Mohit



 —
 Sent from Mailbox

 On Sat, Feb 21, 2015 at 9:34 PM, Adam Bordelon a...@mesosphere.io wrote:

  Hello friends,
  After receiving a positive response on the discussion thread, and even a
  new Mentor (Luciano), I would like to call a VOTE to accept Myriad into
 the
  Apache Incubator. I will end the vote after 7 days.
  https://wiki.apache.org/incubator/MyriadProposal?action=recallrev=7
  [ ] +1 Accept Myriad into the Incubator
  [ ] +0 Don’t care.
  [ ] -1 Don’t accept Myriad into the Incubator because..
  I am clearly a +1.
  Thanks,
  -Adam-
  me@apache

 --
 _
 The information contained in this communication is intended solely for the
 use of the individual or entity to whom it is addressed and others
 authorized to receive it. It may contain confidential or legally privileged
 information. If you are not the intended recipient you are hereby notified
 that any disclosure, copying, distribution or taking any action in reliance
 on the contents of this information is strictly prohibited and may be
 unlawful. If you have received this communication in error, please notify
 us immediately by responding to this email and then delete it from your
 system. The firm is neither liable for the proper and complete transmission
 of the information contained in this communication nor for any delay in its
 receipt.

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

Re: Final draft of IPMC report for January 2015

[Timothy Chen]

Hi Roman,

I just added my shepherd notes last night and I don't think it appeared.

Not sure it's a big deal but if you can please pull the latest change.

Thanks,

Tim

On Wed, Jan 14, 2015 at 8:42 AM, Roman Shaposhnik r...@apache.org wrote:
 The following will be submitted to the board at midnight:

 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 currently 36 podlings undergoing incubation.  One podling
 joined us this month (Corinthia). One member joined and two members
 left the IPMC.

 IPMC has recognized the need for tightening up mentorship requirements
 and overall structure of the incubation process. Active discussions
 on how to this in the best possible way are on going and the recommendation
 is expected to be available in a few weeks.

 * Community

   New IPMC members:

 Hyunsik Choi


   People who left the IPMC:

 Sean Owen
 Marvin Humphrey

   Mentors who didn't sign off on the reports:

 Alan Gates
 Alex Karasulu
 Andrei Savu
 Andrew Purtell
 Arun Murthy
 Ashutosh Chauhan
 Benjamin Hindman
 Daniel Gruno
 David Blevins
 Devaraj Das
 Drew Farris
 Enis Soztutar
 Gerhard Petracek
 Henri Gomez
 Henry Saputra
 Lewis John Mcgibbney
 Luciano Resende
 Marcel Offermans
 Matt Hogstrom
 Nick Burch
 Olivier Lamy
 Sam Ruby
 Sergio Fernandez
 Suresh Marru
 Suresh Srinivas
 Todd Lipcon
 Tom White
 Yegor Kozlov

 * New Podlings

 Corinthia

 * Graduations

   The board has motions for the following:

 Samza



 * Releases

   The following releases were made since the last Incubator report:

 Dec 05 2014   Apache Falcon 0.6-incubating
 Dec 08 2014   Apache Samza 0.8.0-incubating
 Dec 22 2014   Apache Brooklyn 0.7.0-M2-incubating

 * IP Clearance

   * Corinthia initial source grant

 * Legal / Trademarks



 * Infrastructure



 * Miscellaneous

   * NPanday community seems to be in agreement that retirement is the best
 option at this point. The only outstanding issue before formally
 recommending graduation VOTE is to decide whether there's enough cycles
 available for one last release before retirement.

  Summary of podling reports 

 * Still getting started at the Incubator

 SAMOA
 Corinthia
 Kylin
 NiFi
 Taverna (delayed software grant)
 Zeppelin

 * Not yet ready to graduate

   No release:

 DataFu
 HTrace
 Ignite
 Kalumet
 Lens
 Tamaya

   Community growth:

 Aurora
 Brooklyn
 Calcite
 MRQL
 ODF Toolkit
 Parquet
 Ranger
 Usergrid

 * Ready to graduate

   The Board has motions for the following:

 Samza

 * Did not report, expected next month

 NPanday
 Ripple

 --
Table of Contents
 Aurora
 Brooklyn
 Calcite
 Corinthia
 DataFu
 HTrace
 Ignite
 Kalumet
 Kylin
 Lens
 MRQL
 NiFi
 NPanday
 ODF Toolkit
 Parquet
 Ranger
 SAMOA
 Samza
 Tamaya
 Taverna
 Usergrid
 Zeppelin

 --

 
 Aurora

 Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

 Aurora has been incubating since 2013-10-01.

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

   1. Expanding the community's diversity and adding new committers.
   2. Third Apache release, progress being tracked in ticket AURORA-872
   3.

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

   * None at this time.

 How has the community developed since the last report?

   Latest Additions:

   * PMC addition:
 * David McLaughlin, 2014-08-20
   * Contributor additions: No additional contributors had code committed
 since the last report, however three new contributors currently have
 code under review that was submitted within the past 6 weeks. At least
 one of these contributions is a large feature addition, which is
 promising.

   Issue backlog status since last report (Oct 1, 2014):

   * Created:   212
   * Resolved:  177

   Mailing list activity since last report:

   * @dev  480 messages
   * @issues   1085 messages
   * @reviews  2235 messages

 How has the project developed since the last report?

   * Increased participation from new contributors within the Aurora core and
 ecosystem, for example a Chef cookbook and Docker support under
 development.
   * Continued to hold weekly IRC meetings, digests sent to dev@ list
   * Large improvements to project documentation and website.

 Date of last release:

   * Apache Aurora 0.6.0 (incubating) - 2014-11-21

 When were the last committers or PMC members elected?

   * David McLaughlin, 2014-08-20

 Signed-off-by:

   [X](aurora) Jake Farrell
 

Re: Report Timeline Report Manager for December

[Timothy Chen]

Thanks Marvin!

Tim

On Sat, Dec 6, 2014 at 10:43 PM, Marvin Humphrey mar...@rectangular.com wrote:
 On Sat, Dec 6, 2014 at 9:49 PM, Timothy Chen tnac...@gmail.com wrote:

 I just found out I can't edit the wiki, can you give me edit permissions?

 My wiki username is TimothyChen

 Done.

 Marvin Humphrey

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


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

Re: Report Timeline Report Manager for December

[Timothy Chen]

Hi John,

I just found out I can't edit the wiki, can you give me edit permissions?

My wiki username is TimothyChen

Thanks!

Tim

On Fri, Dec 5, 2014 at 5:30 PM, John D. Ament john.d.am...@gmail.com wrote:
 Hi Tim,

 Thanks for the update.  Typically the way we handle this is by sending an
 email to the general@ mailing list, and making a note in the shepherd's
 notes within the report.

 John


 On Fri Dec 05 2014 at 7:23:07 PM Timothy Chen tnac...@apache.org wrote:

 Hi John,

 I'm doing incubator shepherd the first time, and notice that Incubator
 Ripple hasn't fill in the report yet. I emailed the dev list but I
 wonder if I there is anything that should be done since it's already
 past due.

 Thanks!

 Tim

 On Sat, Nov 22, 2014 at 7:16 PM, John D. Ament john.d.am...@gmail.com
 wrote:
  All,
 
  I've published the December 2014 report to the wiki.  Here's the
  timeline and shepherd assignment:
 
  December 2014 Incubator report timeline:
  http://wiki.apache.org/incubator/December2014
 
  Wed December 03 -- Podling reports due by end of day
  Sun December 07 -- Shepherd reviews due by end of day
  Sun December 07 -- Summary due by end of day
  Tue December 09 -- Mentor signoff due by end of day
  Wed December 10 -- Report submitted to Board
  Wed December 17 -- Board meeting
 
  Alan D. Cabrera - Ignite
  Andrei Savu - Drill
  Andrei Savu - Johnzon
  Dave Fisher - NPanday
  John Ament - MRQL
  John Ament - log4cxx2
  Justin Mclean - Tamaya
  Konstantin Boudnik - Argus
  Matthew Franklin - Brooklyn
  Raphael Bircher - Kalumet
  Raphael Bircher - Streams
  Roman Shaposhnik - Sentry
  Ross Gardler - Wave
  Suresh Marru - Falcon
  Suresh Marru - Lens
  Timothy Chen - Ripple
  Timothy Chen - Taverna
 
  I know this is a few days early, but considering we have a few
  holidays popping up I wanted to send it earlier than later.  If we get
  any new podlings in the next few days we can add them to the report.
 
  I'm wondering if anyone's willing to help with some of the report
  manager responsibilities this month?  To see some of the required
  steps, run this in the incubator site svn repo:
 
  ./report_runbook.py --apache-id  your apache id  --month 12
 
  John
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 

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

Re: [DISCUSS] Rolling shepherds?

[Timothy Chen]

I just signed up few weeks ago and looking to help out when assigned.

Tim

 On Nov 22, 2014, at 4:56 PM, John D. Ament john.d.am...@gmail.com wrote:
 
 Hi all,
 
 I was wondering what everyone thought about the current shepherd program?
 
 It seems like we have some idle shepherds, who maybe don't have the
 bandwidth to help out all the time.  What would everyone thing if we marked
 idle shepherds w/ max_podlings = 0 so that they don't get assigned?
 
 With that said, are there any folks out in the community who might be
 interested in taking a shot at being shepherds?  It's a great way to get
 some exposure to the incubator and its processes.
 
 John

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

Re: [DISCUSS] Rolling shepherds?

[Timothy Chen]

I'm still looking to my first podling report :) how does the limit usually get 
decided?

Tim

 On Nov 22, 2014, at 5:32 PM, John D. Ament john.d.am...@gmail.com wrote:
 
 Nevermind, appears I'm blind.  You're there already. :-)
 
 On Sat, Nov 22, 2014 at 8:23 PM, John D. Ament john.d.am...@gmail.com
 wrote:
 
 Tim,
 
 Thanks!  Looks like you were never added to shepherds.json.  Are you in
 the incubator group already or not yet?
 If not yet, can you tell me your apache id and if you have any prefer to a
 podling limit?
 
 John
 
 On Sat, Nov 22, 2014 at 8:18 PM, Timothy Chen tnac...@gmail.com wrote:
 
 I just signed up few weeks ago and looking to help out when assigned.
 
 Tim
 
 On Nov 22, 2014, at 4:56 PM, John D. Ament john.d.am...@gmail.com
 wrote:
 
 Hi all,
 
 I was wondering what everyone thought about the current shepherd
 program?
 
 It seems like we have some idle shepherds, who maybe don't have the
 bandwidth to help out all the time.  What would everyone thing if we
 marked
 idle shepherds w/ max_podlings = 0 so that they don't get assigned?
 
 With that said, are there any folks out in the community who might be
 interested in taking a shot at being shepherds?  It's a great way to get
 some exposure to the incubator and its processes.
 
 John
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

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

Incubator Shepherd

[Timothy Chen]

Hi all,

I am interested in helping out incubator projects as a shepherd, and saw from 
the wiki the instructions is to simply drop a line here.

I wonder what else I need to do to apply?

Thanks!

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

Re: [RESULT][VOTE] Graduation of Apache Drill from the Incubator

[Timothy Chen]

Just want to chime in around diversity in Drill.

I've been involved in Drill since the beginning of incubation as a non
MapR employee, and from the beginning of the project Drill opened up
the design and contributions to the community, and was obvious from
the design google docs early on with collaborations and feedback from
the community as a whole, to the Google hangouts that are conducted
weekly with all the community members which consistently have multiple
companies show up to chime in discussions.

Being also involved with other top level Apache projects, I view Drill
as already working nicely with the community and very least very
active discussing and improving around allowing diversity.

Tim







On Sat, Oct 25, 2014 at 11:02 PM, Ted Dunning ted.dunn...@gmail.com wrote:
 On Sat, Oct 25, 2014 at 9:11 AM, Sean Owen sro...@gmail.com wrote:

 I think projects, realistically, get
 driven by companies, and necessarily often start around one company. A
 bit more diversity here would be good but hey. I take the message that
 being an Apache project doesn't signify as much as is advertised (see
 link above) about the 'community support' or diversity. Maybe just how
 it is now and no big deal, but thought I would ask. Thanks for
 indulging.


 Drill is working hard on diversifying.  Large contributions are coming in
 as we speak from new contributors and if followed up, these should lead to
 committership before long.

 But we really should look at other projects like Knox and Ambari which have
 graduated without even much lip service paid to diversity to judge the
 standards.  Even now, Knox has one emeritus non-Horton committer and one
 ex-mentor from elsewhere.  That is diversity there.

 With Drill you have a project whose ethos involves very strongly welcoming
 newcomers and welcoming their contributions.  A very different kettle of
 fish.

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

Re: [VOTE] Accept Parquet into the incubator

[Timothy Chen]

+1 non-binding.

Tim


 On May 18, 2014, at 6:14 PM, Jake Farrell jfarr...@apache.org wrote:
 
 +1 (binding)
 
 -Jake
 
 
 
 On Sun, May 18, 2014 at 5:15 PM, Chris Aniszczyk caniszc...@gmail.comwrote:
 
 Based on the results of the discussion thread:
 
 http://mail-archives.apache.org/mod_mbox/incubator-general/201405.mbox/%3CCAJg1wMRGhLu4P7LeVQB%2B5K0C-fr-pw2448uj%3D6-3zHag4F1EbA%40mail.gmail.com%3E
 
 I would like to call a vote on accepting Parquet into the incubator.
 https://wiki.apache.org/incubator/ParquetProposal
 
 [ ] +1 Accept Parquet into the Incubator
 [ ] +0 Indifferent to the acceptance of Parquet
 [ ] -1 Do not accept Parquet because ...
 
 The vote will be open until Thursday May 22nd 18:00 UTC.
 
 = Parquet Proposal =
 
 == Abstract ==
 Parquet is a columnar storage format for Hadoop.
 
 == Proposal ==
 
 We created Parquet to make the advantages of compressed, efficient columnar
 data representation available to any project in the Hadoop ecosystem,
 regardless of the choice of data processing framework, data model, or
 programming language.
 
 == Background ==
 
 Parquet is built from the ground up with complex nested data structures in
 mind, and uses the repetition/definition level approach to encoding such
 data structures, as popularized by Google Dremel (
 https://blog.twitter.com/2013/dremel-made-simple-with-parquet). We believe
 this approach is superior to simple flattening of nested name spaces.
 
 Parquet is built to support very efficient compression and encoding
 schemes. Parquet allows compression schemes to be specified on a per-column
 level, and is future-proofed to allow adding more encodings as they are
 invented and implemented. We separate the concepts of encoding and
 compression, allowing parquet consumers to implement operators that work
 directly on encoded data without paying decompression and decoding penalty
 when possible.
 
 == Rationale ==
 
 Parquet is built to be used by anyone. We believe that an efficient,
 well-implemented columnar storage substrate should be useful to all
 frameworks without the cost of extensive and difficult to set up
 dependencies.
 
 Furthermore, the rapid growth of Parquet community is empowered by open
 source. We believe the Apache foundation is a great fit as the long-term
 home for Parquet, as it provides an established process for
 community-driven development and decision making by consensus. This is
 exactly the model we want for future Parquet development.
 
 == Initial Goals ==
 
 * Move the existing codebase to Apache
 * Integrate with the Apache development process
 * Ensure all dependencies are compliant with Apache License version 2.0
 * Incremental development and releases per Apache guidelines
 
 == Current Status ==
 
 Parquet has undergone 2 major releases:
 https://github.com/Parquet/parquet-format/releases of the core format and
 22 releases: https://github.com/Parquet/parquet-mr/releases of the
 supporting set of Java libraries.
 
 The Parquet source is currently hosted at GitHub, which will seed the
 Apache git repository.
 
 === Meritocracy ===
 
 We plan to invest in supporting a meritocracy. We will discuss the
 requirements in an open forum. Several companies have already expressed
 interest in this project, and we intend to invite additional developers to
 participate. We will encourage and monitor community participation so that
 privileges can be extended to those that contribute.
 
 === Community ===
 
 There is a large need for an advanced columnar storage format for Hadoop.
 Parquet is being used in production by many organizations (see
 https://github.com/Parquet/parquet-mr/blob/master/PoweredBy.md)
 
 * Cloudera: https://twitter.com/HenryR/statuses/324222874011451392
 * Criteo: https://twitter.com/julsimon/statuses/312114074911666177
 * Salesforce: https://twitter.com/TwitterOSS/statuses/392734610116726784
 * Stripe: https://twitter.com/avibryant/statuses/391339949250715648
 * Twitter: https://twitter.com/J_/statuses/315844725611581441
 
 By bringing Parquet into Apache, we believe that the community will grow
 even bigger.
 
 === Core Developers ===
 
 Parquet was initially developed as a collaboration between Twitter,
 Cloudera and Criteo.
 
 See
 
 https://blog.twitter.com/2013/announcing-parquet-10-columnar-storage-for-hadoop
 
 === Alignment ===
 
 We believe that having Parquet at Apache will help further the growth of
 the big-data community, as it will encourage cooperation within the greater
 ecosystem of projects spawned by Apache Hadoop. The alignment is also
 beneficial to other Apache communities (such as Hadoop, Hive, Avro).
 
 == Known Risks ==
 
 === Orphaned Products ===
 
 The risk of the Parquet project being abandoned is minimal. There are many
 organizations using Parquet in production, including Twitter, Cloudera,
 Stripe, and Salesforce (
 http://blog.cloudera.com/blog/2013/10/parquet-at-salesforce-com/).
 
 === Inexperience with Open Source ===
 
 Parquet has existed as a 

Request perms to edit incubator report wiki

[Timothy Chen]

Hi,

I'm a new committer for Drill and wanted to update quarterly report for Drill 
but don't have permissions to do so.

I wonder if I can get added to edit the wiki?

Thanks,

Tim


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