Re: [VOTE] Accept Impala into the Apache Incubator

2015-11-24 Thread Carl Steinbach 
+1 (binding)


On Tue, Nov 24, 2015 at 4:56 PM, Luke Han  wrote:

> +1 (non-binding)
>
>
> Best Regards!
> -
>
> Luke Han
>
> On Wed, Nov 25, 2015 at 8:07 AM, Julien Le Dem  wrote:
>
> > +1 (binding)
> >
> > On Tue, Nov 24, 2015 at 3:49 PM, Mike Percy  wrote:
> >
> > > On Tue, Nov 24, 2015 at 1:03 PM, Henry Robinson 
> > > wrote:
> > >
> > > > I'd like to call a VOTE on that proposal, which is on the wiki at
> > > > https://wiki.apache.org/incubator/ImpalaProposal, and which I've
> > pasted
> > > > below.
> > > >
> > > > During the discussion period, the proposal has been amended to add
> > Brock
> > > > Noland as a new mentor, to add one missed committer from the list and
> > to
> > > > correct some issues with the dependency list.
> > > >
> > > > Please cast your votes as follows:
> > > >
> > >
> > > +1 (non-binding)
> > >
> > > Mike
> > >
> >
> >
> >
> > --
> > Julien
> >
>

Re: [VOTE] Accept Kudu into the Apache Incubator

2015-11-24 Thread Carl Steinbach 
+1 (binding)


On Tue, Nov 24, 2015 at 5:39 PM, John D. Ament 
wrote:

> +1
> On Nov 24, 2015 14:33, "Todd Lipcon"  wrote:
>
> > Hi all,
> >
> > Discussion on the [DISCUSS] thread seems to have wound down, so I'd like
> to
> > call a VOTE on acceptance of Kudu into the ASF Incubator. The proposal is
> > pasted below and also available on the wiki at:
> > https://wiki.apache.org/incubator/KuduProposal
> >
> > The proposal is unchanged since the original version, except for the
> > addition of Carl Steinbach as a Mentor.
> >
> > Please cast your votes:
> >
> > [] +1, accept Kudu into the Incubator
> > [] +/-0, positive/negative non-counted expression of feelings
> > [] -1, do not accept Kudu into the incubator (please state reasoning)
> >
> > Given the US holiday this week, I imagine many folks are traveling or
> > otherwise offline. So, let's run the vote for a full week rather than the
> > traditional 72 hours. Unless the IPMC objects to the extended voting
> > period, the vote will close on Tues, Dec 1st at noon PST.
> >
> > Thanks
> > -Todd
> > -
> >
> > = Kudu Proposal =
> >
> > == Abstract ==
> >
> > Kudu is a distributed columnar storage engine built for the Apache Hadoop
> > ecosystem.
> >
> > == Proposal ==
> >
> > Kudu is an open source storage engine for structured data which supports
> > low-latency random access together with efficient analytical access
> > patterns. Kudu distributes data using horizontal partitioning and
> > replicates each partition using Raft consensus, providing low
> > mean-time-to-recovery and low tail latencies. Kudu is designed within the
> > context of the Apache Hadoop ecosystem and supports many integrations
> with
> > other data analytics projects both inside and outside of the Apache
> > Software Foundation.
> >
> >
> >
> > We propose to incubate Kudu as a project of the Apache Software
> Foundation.
> >
> > == Background ==
> >
> > In recent years, explosive growth in the amount of data being generated
> and
> > captured by enterprises has resulted in the rapid adoption of open source
> > technology which is able to store massive data sets at scale and at low
> > cost. In particular, the Apache Hadoop ecosystem has become a focal point
> > for such “big data” workloads, because many traditional open source
> > database systems have lagged in offering a scalable alternative.
> >
> >
> >
> > Structured storage in the Hadoop ecosystem has typically been achieved in
> > two ways: for static data sets, data is typically stored on Apache HDFS
> > using binary data formats such as Apache Avro or Apache Parquet. However,
> > neither HDFS nor these formats has any provision for updating individual
> > records, or for efficient random access. Mutable data sets are typically
> > stored in semi-structured stores such as Apache HBase or Apache
> Cassandra.
> > These systems allow for low-latency record-level reads and writes, but
> lag
> > far behind the static file formats in terms of sequential read throughput
> > for applications such as SQL-based analytics or machine learning.
> >
> >
> >
> > Kudu is a new storage system designed and implemented from the ground up
> to
> > fill this gap between high-throughput sequential-access storage systems
> > such as HDFS and low-latency random-access systems such as HBase or
> > Cassandra. While these existing systems continue to hold advantages in
> some
> > situations, Kudu offers a “happy medium” alternative that can
> dramatically
> > simplify the architecture of many common workloads. In particular, Kudu
> > offers a simple API for row-level inserts, updates, and deletes, while
> > providing table scans at throughputs similar to Parquet, a commonly-used
> > columnar format for static data.
> >
> >
> >
> > More information on Kudu can be found at the existing open source project
> > website: http://getkudu.io and in particular in the Kudu white-paper
> PDF:
> > http://getkudu.io/kudu.pdf from which the above was excerpted.
> >
> > == Rationale ==
> >
> > As described above, Kudu fills an important gap in the open source
> storage
> > ecosystem. After our initial open source project release in September
> 2015,
> > we have seen a great amount of interest across a diverse set of users and
> > companies. We believe that, as a storage system, it is critical to build
> an
> > equally diverse set of con

Re: [VOTE] Impala 2.7.0 release candidate 3

2016-09-29 Thread Carl Steinbach 
+1


On Thu, Sep 29, 2016 at 8:22 AM, Todd Lipcon  wrote:

> Hey Jim,
>
> Just a quick note: I think several of the mentors (myself included) might
> be busy at Strata/Hadoop World this week, so might be tough to get the
> votes in within 72 hours. If the required 3 votes aren't in by early next
> week, I should have more time to check the release then.
>
> Thanks
> -Todd
>
> On Tue, Sep 27, 2016 at 1:25 PM, Jim Apple  wrote:
>
> > Oh, I forgot to mention - to check the RAT report, you can use the
> > script in bin/check-rat-report.py and the list of files to exclude
> > from bin/rat_exclude_files.txt
> >
> > On Tue, Sep 27, 2016 at 8:33 AM, Jim Apple  wrote:
> > > The Impala PPMC has voted to release 2.7.0 release candidate 3:
> > >
> > > Proposal:
> > >
> > > http://mail-archives.apache.org/mod_mbox/incubator-impala-
> > dev/201609.mbox/%3CCAC-pSX36EbVohLNXdg7pV7i3gkv5_
> > JajZ8ekbZM9OguOi9fH0Q%40mail.gmail.com%3E
> > >
> > > Mirror:
> > >
> > > https://lists.apache.org/thread.html/530925a9689157059d6de31a4e3f97
> > 587154defd13328930112784a4@%3Cdev.impala.apache.org%3E
> > >
> > > The result of the vote:
> > >
> > > https://lists.apache.org/thread.html/477c2e59c44db5c19177b166fc8c28
> > 5d940533963106cdf4c7f2ad6a@%3Cdev.impala.apache.org%3E
> > >
> > > The artifacts for testing (including signatures and checksums):
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/impala/2.7.0/RC3/
> > >
> > > The KEYS:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/impala/KEYS
> > >
> > > The git tag:
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
> > git;a=tag;h=refs/tags/2.7.0-rc3
> > >
> > > This vote will be open for at least 72 hours, or until the necessary
> > > number of votes (3 +1) is reached.
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Don't approve the release (please provide specific comments)
> > >
> > > Thanks,
> > > Jim
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>

Re: [VOTE] Impala 2.7.0 release candidate 3

2016-10-04 Thread Carl Steinbach 
+1 (binding) to the release

On Fri, Sep 30, 2016 at 8:30 AM, Jim Apple  wrote:

> Hi Carl - is this a +1 to the release or to Tom's note about
> Strata/Hadoop World?
>
> On Thu, Sep 29, 2016 at 9:11 AM, Carl Steinbach  wrote:
> > +1
> >
> >
> > On Thu, Sep 29, 2016 at 8:22 AM, Todd Lipcon  wrote:
> >
> >> Hey Jim,
> >>
> >> Just a quick note: I think several of the mentors (myself included)
> might
> >> be busy at Strata/Hadoop World this week, so might be tough to get the
> >> votes in within 72 hours. If the required 3 votes aren't in by early
> next
> >> week, I should have more time to check the release then.
> >>
> >> Thanks
> >> -Todd
> >>
> >> On Tue, Sep 27, 2016 at 1:25 PM, Jim Apple 
> wrote:
> >>
> >> > Oh, I forgot to mention - to check the RAT report, you can use the
> >> > script in bin/check-rat-report.py and the list of files to exclude
> >> > from bin/rat_exclude_files.txt
> >> >
> >> > On Tue, Sep 27, 2016 at 8:33 AM, Jim Apple 
> wrote:
> >> > > The Impala PPMC has voted to release 2.7.0 release candidate 3:
> >> > >
> >> > > Proposal:
> >> > >
> >> > > http://mail-archives.apache.org/mod_mbox/incubator-impala-
> >> > dev/201609.mbox/%3CCAC-pSX36EbVohLNXdg7pV7i3gkv5_
> >> > JajZ8ekbZM9OguOi9fH0Q%40mail.gmail.com%3E
> >> > >
> >> > > Mirror:
> >> > >
> >> > > https://lists.apache.org/thread.html/530925a9689157059d6de31a4e3f97
> >> > 587154defd13328930112784a4@%3Cdev.impala.apache.org%3E
> >> > >
> >> > > The result of the vote:
> >> > >
> >> > > https://lists.apache.org/thread.html/477c2e59c44db5c19177b166fc8c28
> >> > 5d940533963106cdf4c7f2ad6a@%3Cdev.impala.apache.org%3E
> >> > >
> >> > > The artifacts for testing (including signatures and checksums):
> >> > >
> >> > > https://dist.apache.org/repos/dist/dev/incubator/impala/2.7.0/RC3/
> >> > >
> >> > > The KEYS:
> >> > >
> >> > > https://dist.apache.org/repos/dist/dev/incubator/impala/KEYS
> >> > >
> >> > > The git tag:
> >> > >
> >> > > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
> >> > git;a=tag;h=refs/tags/2.7.0-rc3
> >> > >
> >> > > This vote will be open for at least 72 hours, or until the necessary
> >> > > number of votes (3 +1) is reached.
> >> > >
> >> > > [ ] +1 Approve the release
> >> > > [ ] -1 Don't approve the release (please provide specific comments)
> >> > >
> >> > > Thanks,
> >> > > Jim
> >> >
> >> > -
> >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> > For additional commands, e-mail: general-h...@incubator.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Todd Lipcon
> >> Software Engineer, Cloudera
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Gobblin to enter Apache Incubator

2017-02-18 Thread Carl Steinbach 
+1 (binding)

- Carl

On Sat, Feb 18, 2017 at 5:46 PM, Liang Chen  wrote:

> +1 (non-binding)
>
> Regards
> Liang
>
>
>
> --
> View this message in context: http://apache-incubator-
> general.996316.n3.nabble.com/VOTE-Gobblin-to-enter-Apache-
> Incubator-tp53837p53858.html
> Sent from the Apache Incubator - General mailing list archive at
> Nabble.com.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Edit access

2017-05-03 Thread Carl Steinbach 
Can you also give CarlSteinbach edit access?

Thanks.

- Carl

On Wed, May 3, 2017 at 3:17 AM, Nick Burch  wrote:

> On Tue, 2 May 2017, Brock Noland wrote:
>
>> Can you give brocknoland edit access to the wiki?
>>
>
> Done. Note that it looks like you may have an older account BrockNoland
> which already had karma
>
> Nick
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Impala 2.10.0 release candidate 2

2017-09-11 Thread Carl Steinbach 
  [ ] +1 Approve the release


On Sun, Sep 10, 2017 at 10:45 AM, Brock Noland  wrote:

> [x] +1 Approve the release
>
> On Wed, Sep 6, 2017 at 2:27 PM, Bharath Vissapragada <
> bhara...@cloudera.com>
> wrote:
>
> > Impala 2.10.0 release candidate 2 has passed a PPMC vote; this email is a
> > call for an IPMC vote.
> >
> > The PPMC voting thread is at:
> >
> > <
> > https://lists.apache.org/thread.html/788430a3ee2d9599b75ce235e0ab7e
> > 47b6e4d9049c73b56da9352e7f@%3Cdev.impala.apache.org%3E
> > >
> >
> > The vote result thread is at:
> >
> > <
> > https://lists.apache.org/thread.html/208e57e776fa68b0f2adf1daf80f1f
> > 567b77f40433a846669af09626@%3Cdev.impala.apache.org%3E
> > >
> >
> >
> > The artefacts for testing can be downloaded from
> >
> > 
> >
> > The git tag for this release candidate is 2.10.0-rc2 and treehash is
> > visible at
> >
> > <
> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
> git;a=tree;hb=
> > 23d79462da5d0108709e8b1399c97606f4ebdf92
> > >
> >
> > The KEYS are at <
> > https://dist.apache.org/repos/dist/dev/incubator/impala/KEYS>
> >
> > To run RAT, follow the instructions in bin/check-rat-report.py. To build,
> > follow the instructions in bin/bootstrap_build.sh.
> >
> > This vote will be open for at least 72 hours, or until the necessary
> number
> > of votes (3 +1) is reached.
> >
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
>

Re: [VOTE] Resolution to graduate Apache Impala to TLP

2017-11-09 Thread Carl Steinbach 
+1 (binding)

On Thu, Nov 9, 2017 at 10:04 AM, Todd Lipcon  wrote:

> +1 (binding) from me!
>
> Todd
>
> On Nov 8, 2017 8:28 PM, "Jim Apple"  wrote:
>
> > The graduation of Impala to a TLP has been discussed[0] on dev@impala,
> > voted on[1] on dev@impala, and discussed[2] on general@incubator. All
> > threads were open 72 hours or more, and all seem to have quiesced.
> >
> > This is a call for a VOTE to graduate Impala to a TLP. The draft
> resolution
> > is below. Please select from:
> >
> > [ ] +1: Graduate Impala to a TLP
> > [ ] +-0: Neither graduate nor do not graduate Impala to a TLP
> > [ ] -1: Do NOT graduate Impala to a TLP, because ...
> >
> > 
> >
> > [0]: <
> > https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c032
> > 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E
> > >
> >
> > [1]: <
> > https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d6
> > 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E
> > >
> >
> > [2]: <
> > https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc51
> > 0470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E
> > >
> >
> > 
> >
> > Establish the Apache Impala 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 high-performance distributed SQL engine.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Impala Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Impala Project be and hereby is responsible
> > for the creation and maintenance of software related to a
> > high-performance distributed SQL engine; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Impala" 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 Impala
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Impala
> > 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 Impala Project:
> >
> > * Alex Behm 
> > * Bharath Vissapragada 
> > * Brock Noland 
> > * Carl Steinbach 
> > * Casey Ching 
> > * Daniel Hecht 
> > * Dimitris Tsirogiannis 
> > * Henry Robinson 
> > * Ishaan Joshi 
> > * Jim Apple 
> > * John Russell 
> > * Juan Yu 
> > * Lars Volker 
> > * Lenni Kuff 
> > * Marcel Kornacker 
> > * Martin Grund 
> > * Matthew Jacobs 
> > * Michael Brown 
> > * Michael Ho 
> > * Sailesh Mukil 
> > * Skye Wanderman-Milne 
> > * Taras Bobrovytsky 
> > * Tim Armstrong 
> > * Todd Lipcon 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to
> > the office of Vice President, Apache Impala, 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 Impala 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 Impala Project;
> > and be it further
> >
> > RESOLVED, that the Apache Impala Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator Impala
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Impala podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
> >
>

[DISCUSS] Dr. Elephant Incubator Proposal

2018-03-06 Thread Carl Steinbach 
and Apache Airflow (incubating).

= KNOWN RISKS =

== Orphaned products ==

The risk of the Dr. Elephant project being abandoned is minimal. As
noted earlier, there are many organizations that have benefitted from
Dr. Elephant, and which are thus incentivized to continue
development. In addition, the software vendor PepperData has
integrated Dr. Elephant into their Application Profiler product.

== Inexperience with Open Source ==

Dr. Elephant has existed as a healthy open source project since
2016. Any risks that we foresee are ones associated with scaling our
open source communication and operation process rather than with
inherent inexperience in operating as an open source project.

== Homogenous Developers ==

Apart from Linkedin’s developers, Dr. Elephant has developers from
Airbnb, Pepperdata, Flipkart, Hulu, Foursquare, Altiscale, PayPal,
Evariant, Didi, Trivago, and Cardlytics.

A lot of effort has been put for efficient communication between all
the developers. We have set up different forums for communication like
github issues, google groups mailing list, gitter chat, weekly
hangouts, and frequent meetups.

== Reliance on Salaried Developers ==

It is expected that Dr. Elephant development will occur on both
salaried time and on volunteer time, after hours. Many of the initial
committers are paid by their employer 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 to recruiting
additional committers including non-salaried developers.

== A Excessive Fascination with the Apache Brand ==

While we respect the reputation of the Apache brand and have no doubts
that it will attract contributors and users, we believe the ASF is the
right home for Dr. Elephant to foster a great community that will lead
to a better outcome in the long term.

= Documentation =

Dr Elephant's developer wiki: https://github.com/linkedin/dr-elephant/wiki

= Initial Source =

Dr Elephant's initial source contribution will come from
https://github.com/linkedin/dr-elephant

The code is licensed under the Apache License V2.

= Source and Intellectual Property Submission Plan =

The Dr. Elephant codebase is currently hosted on Github. This is the
exact codebase that we would migrate to the Apache Software
Foundation. The Dr. Elephant source code is already licensed under
Apache License Version 2.0. Going forward, we will continue to have
all the contributions licensed directly to the Apache Software
Foundation through our signed Individual Contributor License
Agreements for all of the committers on the project.

= External Dependencies =

To the best of our knowledge all of Dr. Elephant’s dependencies are
distributed under Apache Software Foundation compatible licenses. Upon
acceptance to the incubator, we will begin a thorough analysis of all
transitive dependencies to verify this fact and introduce license
checking into the build and release process.

= Cryptography =

We do not expect Dr. Elephant to be a controlled export item due to
the use of encryption.

= Required Resources =

== Mailing lists ==

 * priv...@drelephant.incubator.apache.org (moderated subscriptions)
 * comm...@drelephant.incubator.apache.org
 * d...@drelephant.incubator.apache.org
 * iss...@drelephant.incubator.apache.org
 * u...@drelephant.incubator.apache.org

== Git Repository ==

Git is the preferred source control system:
git://git.apache.org/dr-elephant

== Issue Tracking ==

JIRA project DOCTOR

== Other Resources ==

The existing code already has unit and integration tests, so we would
like a Jenkins instance to run them whenever a new patch is
submitted. This can be added after project creation.

= Initial Committers =

 * Akshay Rai 
 * Anant Nag 
 * Chetna Chaudhari 
 * Clemens Valiente 
 * Fangshi Li 
 * George Wu 
 * Krishna Puttaswamy 
 * Maxime Kestemont 
 * Noam Shaish 
 * Paul Reed Bramsen 
 * Ragesh K R 
 * Shankar Manian 
 * Shahrukh Khan 
 * Shekhar Gupta 
 * Shida Li 

== Affiliations ==

 * Akshay Rai - Linkedin
 * Anant Nag - Linkedin
 * Chetna Chaudhari - SkyTv New Zealand
 * Clemens Valiente - trivago GmbH
 * Fangshi Li - Linkedin
 * George Wu - Pinterest
 * Krishna Puttaswamy - Airbnb
 * Mark Wagner - Linkedin
 * Maxime Kestemont - Criteo
 * Noam Shaish - Nordea Bank
 * Ragesh K R - Linkedin
 * Shankar Manian - Linkedin
 * Shahrukh Khan - Hortonworks
 * Shekhar Gupta - Pepperdata
 * Shida Li - Dynalist Inc.

= Sponsors =
== Champion ==
 * Carl Steinbach

== Nominated Mentors ==
  * Carl Steinbach (LinkedIn)

== Sponsoring Entity ==
The Apache Incubator

Re: [DISCUSS] Dr. Elephant Incubator Proposal

2018-03-06 Thread Carl Steinbach 
Hi Mike,

Why does Dr. Elephant make sense as a separate project instead of
> contributing to Hadoop directly?
>

Here are a couple reasons why I think Dr. Elephant is more likely to
succeed as a separate project:

* Dr. Elephant supports Hadoop *and* Spark, and may support other
  execution layers in the future. If we make Dr. Elephant a part of
  Hadoop I expect that it will discourage contributions from people
  who are interested mainly in Spark support, and vice versa.

* If Dr. Elephant is added to Hadoop it will be necessary for the
  Hadoop project to declare a dependency on Spark. I doubt this change
  will get approved.

* We don't want to tie Dr. Elephant to a specific version of Hadoop or
  Spark, or tie the Dr. Elephant release cycle to the Hadoop or Spark
  release cycles.

* None of the current Dr. Elephant committers are Hadoop committers,
  and I doubt that the Hadoop PMC is going to give them a commit bit
  just to work on Dr. Elephant. As a result the existing committers
  would be effectively forfeiting their right to continue maintaining
  their own project. I think this is one of the reasons why many
  Hadoop contrib projects are poorly maintained.



> What is the relationship between Dr. Elephant and the (now seemingly
> defunct) Hadoop Vaidya?
>

Vaidya was a command line tool for tuning Hadoop jobs. Dr. Elephant is
an always-on service for tuning Hadoop and Spark jobs. We were unaware
of Vaidya when we started working on Dr. Elephant.

- Carl

Re: IPMC join request

2018-03-06 Thread Carl Steinbach 
Obviously I'm +1 on this!

On Mar 6, 2018 6:39 PM, "Felix Cheung"  wrote:

> Hi all,
>
> I'd like to join IPMC, initially to help mentor Dr Elephant as incubator
> project but also looking forward to help mentor other Apache incubator
> projects.
>
> I am PPMC/PMC of Apache Zeppelin (since incubation to TLP) and PMC of
> Apache Spark, Release Manager for releases.
>
> Thanks!
> Felix
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

2018-03-07 Thread Carl Steinbach 
Hi Roman,

Currently Dr. Elephant only supports YARN, but we are excited at
the prospect of extending it to support other schedulers likes Mesos.

- Carl

On Tue, Mar 6, 2018 at 3:33 PM, Roman Shaposhnik 
wrote:

> On Tue, Mar 6, 2018 at 3:17 PM, Mike Drob  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?
>
> A different way to ask the same question would be: how closely is it tied
> to YARN as a scheduler? Does it support other schedulers (as in running
> Spark on Mesos for example)?
>
> Thanks,
> Roman.
>
> -
> 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

2018-03-07 Thread Carl Steinbach 
I will followup with LinkedIn's legal team regarding getting an SGA. I don't
think this will be a problem since the same team has already reviewed Dr.
Elephant
and approved it for contribution to the Apache incubator.

- Carl

On Wed, Mar 7, 2018 at 11:20 AM, Kevin A. McGrail 
wrote:

> Sorry, I missed the copyright and checked only the LICENSE.  Agree
> completely with you and Craig an SGA is needed.
>
> --
> 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 Wed, Mar 7, 2018 at 2:19 PM, John D. Ament 
> wrote:
>
> > On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail 
> > wrote:
> >
> > > Fair enough but it would be procedural not legal.  Who would sign said
> > > SGA?  LI or representatives of the GH project?
> > >
> >
> > LinkedIn.  And it is a legal need.  Right now, the source files have
> > Copyright LinkedIn on them.  The SGA grants us the ability to remove that
> > copyright header.  The CCLA would allow the individual contributors to
> > submit the code to us with the appropriate header.  Hence why either
> works
> > in this case.
> >
> >
> > >
> > > --
> > > Kevin A. McGrail
> > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > > Chair Emeritus Apache SpamAssassin Project
> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171>
> > >
> > > On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell 
> > > wrote:
> > >
> > > > If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is
> > part
> > > > of the incubation process, although as Bertrand notes, it's good to
> > know
> > > > ahead of time whether all of the current owners of the code are
> willing
> > > to
> > > > grant an explicit license to Apache.
> > > >
> > > > Please see http://www.apache.org/licenses/#provenance for details.
> > > >
> > > > If Dr. Elephant is only *used* as a dependency by an Apache project,
> no
> > > > SGA is needed.
> > > >
> > > > Craig
> > > >
> > > > > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail 
> > > > wrote:
> > > > >
> > > > > I do not believe an SGA is needed as Dr. Elephant is licensed under
> > > ASF.
> > > > > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
> > > > >
> > > > > Regards,
> > > > > KAM
> > > > >
> > > > > --
> > > > > Kevin A. McGrail
> > > > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > > > > Chair Emeritus Apache SpamAssassin Project
> > > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > <(703)%20798-0171>
> > > > >
> > > > > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
> > > > > bdelacre...@codeconsult.ch> wrote:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach 
> > > wrote:
> > > > >>> = Source and Intellectual Property Submission Plan =
> > > > >>> ...The Dr. Elephant source code is already licensed under
> > > > >>> Apache License Version 2.0. Going forward, we will continue to
> have
> > > > >>> all the contributions licensed directly to the Apache Software
> > > > >>> Foundation through our signed Individual Contributor License
> > > > >>> Agreements for all of the committers on the project
> > > > >>
> > > > >> Note that whoever owns the code (LinkedIn IIUC) will have to
> submit
> > a
> > > > >> Software Grant to donate it to the ASF:
> > > > >>
> > > > >> https://www.apache.org/licenses/software-grant.txt
> > > > >>
> > > > >> I think it's prudent to verify that the owners of the code are
> ready
> > > > >> to sign and submit that document, and mention that in the above
> > > > >> section, before entering incubation.
> > > > >>
> > > > >> -Bertrand
> > > > >>
> > > > >> 
> > -
> > > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > >> For additional commands, e-mail: general-help@incubator.apache.
> org
> > > > >>
> > > > >>
> > > >
> > > > Craig L Russell
> > > > Secretary, Apache Software Foundation
> > > > c...@apache.org http://db.apache.org/jdo
> > > >
> > > >
> > > > 
> -
> > > > 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

2018-03-07 Thread Carl Steinbach 
I also wanted to add that we are looking for more mentors.
Please email me if you are interested.

Thanks.

- Carl

On Wed, Mar 7, 2018 at 12:46 PM, Carl Steinbach  wrote:

> I will followup with LinkedIn's legal team regarding getting an SGA. I
> don't
> think this will be a problem since the same team has already reviewed Dr.
> Elephant
> and approved it for contribution to the Apache incubator.
>
> - Carl
>
> On Wed, Mar 7, 2018 at 11:20 AM, Kevin A. McGrail 
> wrote:
>
>> Sorry, I missed the copyright and checked only the LICENSE.  Agree
>> completely with you and Craig an SGA is needed.
>>
>> --
>> 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 Wed, Mar 7, 2018 at 2:19 PM, John D. Ament 
>> wrote:
>>
>> > On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail 
>> > wrote:
>> >
>> > > Fair enough but it would be procedural not legal.  Who would sign said
>> > > SGA?  LI or representatives of the GH project?
>> > >
>> >
>> > LinkedIn.  And it is a legal need.  Right now, the source files have
>> > Copyright LinkedIn on them.  The SGA grants us the ability to remove
>> that
>> > copyright header.  The CCLA would allow the individual contributors to
>> > submit the code to us with the appropriate header.  Hence why either
>> works
>> > in this case.
>> >
>> >
>> > >
>> > > --
>> > > Kevin A. McGrail
>> > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
>> > > Chair Emeritus Apache SpamAssassin Project
>> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>> <(703)%20798-0171>
>> > >
>> > > On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell 
>> > > wrote:
>> > >
>> > > > If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is
>> > part
>> > > > of the incubation process, although as Bertrand notes, it's good to
>> > know
>> > > > ahead of time whether all of the current owners of the code are
>> willing
>> > > to
>> > > > grant an explicit license to Apache.
>> > > >
>> > > > Please see http://www.apache.org/licenses/#provenance for details.
>> > > >
>> > > > If Dr. Elephant is only *used* as a dependency by an Apache
>> project, no
>> > > > SGA is needed.
>> > > >
>> > > > Craig
>> > > >
>> > > > > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail > >
>> > > > wrote:
>> > > > >
>> > > > > I do not believe an SGA is needed as Dr. Elephant is licensed
>> under
>> > > ASF.
>> > > > > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
>> > > > >
>> > > > > Regards,
>> > > > > KAM
>> > > > >
>> > > > > --
>> > > > > Kevin A. McGrail
>> > > > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
>> > > > > Chair Emeritus Apache SpamAssassin Project
>> > > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>> > <(703)%20798-0171>
>> > > > >
>> > > > > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
>> > > > > bdelacre...@codeconsult.ch> wrote:
>> > > > >
>> > > > >> Hi,
>> > > > >>
>> > > > >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach 
>> > > wrote:
>> > > > >>> = Source and Intellectual Property Submission Plan =
>> > > > >>> ...The Dr. Elephant source code is already licensed under
>> > > > >>> Apache License Version 2.0. Going forward, we will continue to
>> have
>> > > > >>> all the contributions licensed directly to the Apache Software
>> > > > >>> Foundation through our signed Individual Contributor License
>> > > > >>> Agreements for all of the committers on the project
>> > > > >>
>> > > > >> Note that whoever owns the code (LinkedIn IIUC) will have to
>> submit
>> > a
>> > > > >> Software Grant to donate it to the ASF:
>> > > > >>
>> > > > >> https://www.apache.org/licenses/software-grant.txt
>> > > > >>
>> > > > >> I think it's prudent to verify that the owners of the code are
>> ready
>> > > > >> to sign and submit that document, and mention that in the above
>> > > > >> section, before entering incubation.
>> > > > >>
>> > > > >> -Bertrand
>> > > > >>
>> > > > >> 
>> > -
>> > > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > > > >> For additional commands, e-mail: general-help@incubator.apache.
>> org
>> > > > >>
>> > > > >>
>> > > >
>> > > > Craig L Russell
>> > > > Secretary, Apache Software Foundation
>> > > > c...@apache.org http://db.apache.org/jdo
>> > > >
>> > > >
>> > > > 
>> -
>> > > > 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

2018-03-07 Thread Carl Steinbach 
Timothy Chen has volunteered to be a mentor. I have updated
the proposal on the wiki to reflect this.

Thanks Timothy!

- Carl

On Wed, Mar 7, 2018 at 12:47 PM, Carl Steinbach  wrote:

> I also wanted to add that we are looking for more mentors.
> Please email me if you are interested.
>
> Thanks.
>
> - Carl
>
> On Wed, Mar 7, 2018 at 12:46 PM, Carl Steinbach  wrote:
>
>> I will followup with LinkedIn's legal team regarding getting an SGA. I
>> don't
>> think this will be a problem since the same team has already reviewed Dr.
>> Elephant
>> and approved it for contribution to the Apache incubator.
>>
>> - Carl
>>
>> On Wed, Mar 7, 2018 at 11:20 AM, Kevin A. McGrail 
>> wrote:
>>
>>> Sorry, I missed the copyright and checked only the LICENSE.  Agree
>>> completely with you and Craig an SGA is needed.
>>>
>>> --
>>> 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 Wed, Mar 7, 2018 at 2:19 PM, John D. Ament 
>>> wrote:
>>>
>>> > On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail 
>>> > wrote:
>>> >
>>> > > Fair enough but it would be procedural not legal.  Who would sign
>>> said
>>> > > SGA?  LI or representatives of the GH project?
>>> > >
>>> >
>>> > LinkedIn.  And it is a legal need.  Right now, the source files have
>>> > Copyright LinkedIn on them.  The SGA grants us the ability to remove
>>> that
>>> > copyright header.  The CCLA would allow the individual contributors to
>>> > submit the code to us with the appropriate header.  Hence why either
>>> works
>>> > in this case.
>>> >
>>> >
>>> > >
>>> > > --
>>> > > Kevin A. McGrail
>>> > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
>>> > > Chair Emeritus Apache SpamAssassin Project
>>> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>> <(703)%20798-0171>
>>> > >
>>> > > On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell 
>>> > > wrote:
>>> > >
>>> > > > If Dr. Elephant *becomes* an Apache project, it needs a SGA. This
>>> is
>>> > part
>>> > > > of the incubation process, although as Bertrand notes, it's good to
>>> > know
>>> > > > ahead of time whether all of the current owners of the code are
>>> willing
>>> > > to
>>> > > > grant an explicit license to Apache.
>>> > > >
>>> > > > Please see http://www.apache.org/licenses/#provenance for details.
>>> > > >
>>> > > > If Dr. Elephant is only *used* as a dependency by an Apache
>>> project, no
>>> > > > SGA is needed.
>>> > > >
>>> > > > Craig
>>> > > >
>>> > > > > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail <
>>> kmcgr...@apache.org>
>>> > > > wrote:
>>> > > > >
>>> > > > > I do not believe an SGA is needed as Dr. Elephant is licensed
>>> under
>>> > > ASF.
>>> > > > > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
>>> > > > >
>>> > > > > Regards,
>>> > > > > KAM
>>> > > > >
>>> > > > > --
>>> > > > > Kevin A. McGrail
>>> > > > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
>>> > > > > Chair Emeritus Apache SpamAssassin Project
>>> > > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>> > <(703)%20798-0171>
>>> > > > >
>>> > > > > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
>>> > > > > bdelacre...@codeconsult.ch> wrote:
>>> > > > >
>>> > > > >> Hi,
>>> > > > >>
>>> > > > >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach >> >
>>> > > wrote:
>>> > > > >>> = Source and Intellectual Property Submission Plan =
>>> > > > >>> ...The Dr. Elephant source code i

Re: [VOTE] Accept Pinot into Apache Incubator

2018-03-09 Thread Carl Steinbach 
+1 (binding)

On Fri, Mar 9, 2018, 7:29 PM kishore g  wrote:

> Added Jim Jagielski to the mentor's list.
>
> On Fri, Mar 9, 2018 at 6:35 PM, Olivier Lamy  wrote:
>
> > +1
> >
> > On 9 March 2018 at 17:11, kishore g  wrote:
> >
> > > Hi all,
> > >
> > > I would like to call a VOTE to accept Pinot into the Apache Incubator.
> > The
> > > full proposal is available on the wiki
> > > 
> > >
> > > Please cast your vote:
> > >
> > >   [ ] +1, bring Pinot into Incubator
> > >   [ ] +0, I don't care either way,
> > >   [ ] -1, do not bring Pinot into Incubator, because...
> > >
> > > The vote will open at least for 72 hours and only votes from the
> > Incubator
> > > PMC are binding.
> > >
> > > Thanks,
> > > Kishore G
> > >
> > > Discussion thread:
> > > https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b
> > > 22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org
> > >
> > >
> > > = 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 exis

Re: [VOTE] Release Apache Iceberg 0.7.0-incubating RC4

2019-10-23 Thread Carl Steinbach 
+1 (binding)

On Tue, Oct 22, 2019, 4:42 PM Julien Le Dem 
wrote:

> +1 (binding)
>
> Downloaded, verified signature, checked licences, ran the build.
>
> On Tue, Oct 22, 2019 at 4:29 PM Jacques Nadeau  wrote:
>
> > +1 (binding)
> >
> > Downloaded, reviewed licenses. Spot check for bad licenses. Built from
> > source + tests.
> >
> > Nice job on the first release guys!
> >
> > On Tue, Oct 22, 2019 at 4:05 PM James Taylor 
> > wrote:
> >
> > > +1 (binding).
> > >
> > > Successfully downloaded, verified license, verified checksum, verified
> > > signature, built from source, and ran unit tests.
> > > Minor nit (ok to fix in next release IMHO): Copyright in NOTICE for
> > Iceberg
> > > should read 2017-2019
> > >
> > >
> > >
> > > On Tue, Oct 22, 2019 at 3:21 PM Ryan Blue  wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > I propose the following RC to be released as official Apache Iceberg
> > > > 0.7.0-incubating release.
> > > >
> > > > This candidate has passed a PPMC vote. The result thread is here:
> > > > *
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/fe76494f9feab454837bc2dc540cd9e59d55dac3f7e0b5b335de7725@
> > > > 
> > > >
> > > > The commit id is 9c81babac65351f7aa21dd878f01c5c81ae304af
> > > > * This corresponds to the tag: apache-iceberg-0.7.0-incubating-rc4
> > > > *
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-iceberg/tree/apache-iceberg-0.7.0-incubating-rc4
> > > > *
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-iceberg/tree/9c81babac65351f7aa21dd878f01c5c81ae304af
> > > >
> > > > The release tarball, signature, and checksums are here:
> > > > *
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/iceberg/apache-iceberg-0.7.0-incubating-rc4/
> > > >
> > > > You can find the KEYS file here:
> > > > * https://dist.apache.org/repos/dist/dev/incubator/iceberg/KEYS
> > > >
> > > > This release includes convenience binary artifacts that are staged in
> > > > Nexus. The Maven repository URL is:
> > > > *
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheiceberg-1004/
> > > >
> > > > The convenience binaries include a Spark runtime Jar with shaded
> > > > dependencies. The LICENSE and NOTICE content for that Jar are
> viewable
> > in
> > > > github as well as in the Jar:
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-iceberg/tree/apache-iceberg-0.7.0-incubating-rc4/runtime
> > > >
> > > > To build and test, run `./gradlew build`. You can also test by adding
> > the
> > > > iceberg-spark-runtime Jar to the jars folder of Spark 2.4.
> > > >
> > > > This is the first Apache Iceberg release.
> > > >
> > > > Please download, verify, and test; then vote in the next 72 hours.
> > > >
> > > > [ ] +1 Release this as Apache Iceberg 0.7.0-incubating
> > > > [ ] +0
> > > > [ ] -1 Do not release this because...
> > > >
> > > > --
> > > > Ryan Blue
> > > >
> > >
> >
>

Re: [VOTE] Recommend Apache Iceberg graduation to top-level project resolution to the board

2020-05-18 Thread Carl Steinbach 
+1 (binding)


On Mon, May 18, 2020 at 6:31 AM Sheng Wu  wrote:

> +1 binding good luck.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Jacques Nadeau  于2020年5月18日周一 上午2:16写道：
>
> > +1 (binding).
> >
> > Congrats
> >
> > On Sat, May 16, 2020 at 2:27 PM Dave Fisher  wrote:
> >
> > > +1 (binding)
> > >
> > > Best Regards,
> > > Dave
> > >
> > > > On May 15, 2020, at 5:39 PM, Ryan Blue  wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > With the support of our mentors (as well as helpful ASF members), the
> > > > Apache Iceberg community has voted to graduate to a top-level
> project.
> > > >
> > > > I propose a vote to recommend graduation for the Iceberg community to
> > the
> > > > board. Here is the proposed resolution:
> > > >
> > > > ```
> > > > Establish the Apache Iceberg 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 managing huge analytic datasets using a standard at-rest
> > > > table format that is designed for high performance and ease of use..
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > (PMC), to be known as the "Apache Iceberg Project", be and hereby is
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache Iceberg Project be and hereby is
> responsible
> > > > for the creation and maintenance of software related to managing huge
> > > > analytic datasets using a standard at-rest table format that is
> > designed
> > > > for high performance and ease of use; and be it further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache Iceberg" 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
> Iceberg
> > > > Project, and to have primary responsibility for management of the
> > > > projects within the scope of responsibility of the Apache Iceberg
> > > > 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 Iceberg
> > Project:
> > > >
> > > > * Anton Okolnychyi 
> > > > * Carl Steinbach   
> > > > * Daniel C. Weeks  
> > > > * James R. Taylor  
> > > > * Julien Le Dem
> > > > * Owen O'Malley
> > > > * Parth Brahmbhatt 
> > > > * Ratandeep Ratti  
> > > > * Ryan Blue
> > > >
> > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ryan Blue be appointed
> to
> > > > the office of Vice President, Apache Iceberg, 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 Apache Iceberg Project be and hereby is tasked
> with
> > > > the migration and rationalization of the Apache Incubator Iceberg
> > > > podling; and be it further
> > > >
> > > > RESOLVED, that all responsibilities pertaining to the Apache
> Incubator
> > > > Iceberg podling encumbered upon the Apache Incubator PMC are
> hereafter
> > > > discharged.
> > > > ```
> > > >
> > > > The community vote passed with 19 +1 votes:
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r9081df0181768f26490f5a85aed7b5a111a82a741764eb3a0e99621d%40%3Cdev.iceberg.apache.org%3E
> > > >
> > > > We also addressed concerns on the IPMC thread, which you can read
> here:
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r3e5795d959feb0a19b233aeaf1121a1d97fd473f5e9b14227de41c54%40%3Cgeneral.incubator.apache.org%3E
> > > >
> > > > Please vote on whether to recommend graduation for the Apache Iceberg
> > > > community to the board.
> > > >
> > > > [ ] +1 Apache Iceberg should graduate
> > > > [ ] +0
> > > > [ ] -1 Apache Iceberg should not graduate because . . .
> > > >
> > > > The vote will be open for at least 72 hours.
> > > >
> > > > --
> > > > Ryan Blue
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [VOTE] Accept Sedona into the Apache Incubator

2020-07-20 Thread Carl Steinbach 
+1 (binding)

- Carl

On Mon, Jul 20, 2020 at 11:41 AM John D. Ament 
wrote:

> While not a vote against Sedona, I think it would be best to fix the mentor
> list to only include IPMC members and allow those not on the IPMC to submit
> proper requests to join the IPMC.
>
> On Wed, Jul 15, 2020 at 11:49 PM Felix Cheung 
> wrote:
>
> > Hi,
> >
> > As we discussed the Sedona proposal [1], I would like to call for a vote
> to
> > accept Sedona into the Apache Incubator.
> >
> > Sedona is a big geospatial data processing engine. The system provides an
> > easy to use Scala, SQL, and Python APIs for spatial data scientists to
> > manage, wrangle, and process geospatial data. The system extends and
> builds
> > upon a popular cluster computing framework (Apache Spark) to provide
> > scalability.
> >
> > The final proposal can be found at
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Sedona+Proposal
> >
> > Please cast your vote:
> >
> >   [ ] +1, yes, bring Sedona into Incubator
> >   [ ] 0, I don't care either way
> >   [ ] -1, no, do not bring Sedona into Incubator, because...
> >
> > The vote will open for at least 72 hours and only votes from the IPMC
> > members are considered binding, but other votes are welcome!
> >
> > Thanks,
> > Felix
> >
> >
> > -
> > [1]
> >
> >
> https://lists.apache.org/thread.html/r72f0b7ddd3143179045653050de9b7de8508d8f8b8194bd73a53e704%40%3Cgeneral.incubator.apache.org%3E
> >
>

Re: [DISCUSS] OneTable proposal

2023-12-13 Thread Carl Steinbach 
Hi Jesús,

This is a great project, and I am eager to see it added to the incubator.

It's great to see that the naming issue is being addressed, but could you
also respond to the other concern Jacques raised about the need to broaden
the list of initial committers to include members of the Iceberg and Delta
communities?

Thanks.

- Carl

On Mon, Dec 11, 2023 at 5:08 PM Jesus Camacho Rodriguez 
wrote:

> Thanks to everyone who expressed support and offered help. It's great to
> see that the project's mission resonates with so many different people.
>
> Jacques, we acknowledge your concern about the project name. We are working
> on selecting a new name for ASF incubation that avoids confusion with any
> specific corporation or product in the space. Currently we are doing some
> due diligence to minimize the risk of having to change it again during
> incubation; we'll update the proposal with the new name soon and share it
> in this thread.
>
> Regarding the name-changing process and your concerns about it, we're
> looking for advice based on past experiences. Specifically, we're
> considering whether it's better to change the project's name before pushing
> the code to the ASF, or if it's more practical to push the code to the ASF
> repository first and then proceed with the name change. Any insights or
> guidance on whether one option is better than the other based on previous
> instances would be appreciated.
>
> Thanks,
> Jesús
>
>
>
> On Mon, Dec 11, 2023 at 5:43 AM Jean-Baptiste Onofré 
> wrote:
>
> > Of course, it's a big +1 one for me.
> >
> > The purpose is interesting, creating "connection" with other Apache
> > projects.
> > Happy to be a mentor on this proposal and contribute to the project :)
> >
> > Thanks !
> > Regards
> > JB
> >
> > On Mon, Dec 4, 2023 at 10:23 PM Jesus Camacho Rodriguez
> >  wrote:
> > >
> > > Hi All,
> > >
> > > I would like to propose a new project to the ASF incubator - OneTable.
> > >
> > > OneTable[1] is an omni-directional converter for table formats that
> > facilitates interoperability across data processing systems and query
> > engines. Currently, OneTable supports widely adopted open-source table
> > formats such as Apache Hudi, Apache Iceberg, and Delta Lake.
> > >
> > > Here is the proposal -
> > >
> https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal
> > >
> > > I would be the Champion of the project. I will mentor and help the
> > project through the incubator with Hitesh Shah [hit...@apache.org],
> > Stamatis Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré [
> > jbono...@apache.org].
> > >
> > > We are looking forward to your feedback!
> > >
> > > Thanks,
> > > Jesús
> > >
> > > [1] https://github.com/onetable-io/onetable
> >
>

Re: [DISCUSS] OneTable proposal

2023-12-14 Thread Carl Steinbach 
Hi Jesus,

Please wait one more day to start the vote.

Thanks.

- Carl

On Thu, Dec 14, 2023 at 3:59 PM Jesus Camacho Rodriguez 
wrote:

> Carl and others, thanks for the feedback. If you have any remaining
> questions or concerns, please let me know. I just want to make sure they
> are all addressed before we start the vote thread --- planning to begin
> later today if possible.
>
> -Jesús
>
> On Wed, Dec 13, 2023 at 8:06 PM Jesus Camacho Rodriguez <
> jcama...@apache.org>
> wrote:
>
> > Carl, thanks for chiming in.
> >
> > Certainly, let me address that part.
> >
> > Concerning the initial list of committers: While the project originated
> > from Onehouse (a company whose offering is powered by Apache Hudi), it's
> > important to highlight that there has been an effort to have an initial
> > list of committers that work for a diverse range of companies invested in
> > different table formats, including Onehouse (4 committers), Microsoft
> (2),
> > Google (1), Walmart (1), Adobe (1), Cloudera (1), and Dremio (1). I
> believe
> > this diversity dispels the notion of a lack of representation or an
> > outsized influence from a single group in the community.
> >
> > Regarding outreach to other communities: As part of the incubation
> > proposal, we extended invitations to participate in this discussion and
> > contribute to the project to members of the communities of the most
> popular
> > OSS table formats [1][2][3][4]. Responses generally fell into four
> > categories (including some private responses): (1) Positive reception,
> > interest in the proposal/vision, and/or thinking about engaging once/if
> the
> > project is in the ASF. (2) Technical/feasibility questions, which we
> > encouraged them to ask on Github since that is our current communication
> > platform in the XTable project. (3) No response received. (4)
> Disagreement,
> > we should all adopt specific format z. It's important to acknowledge the
> > diversity in these communities and recognize that interest on XTable /
> > opinions on XTable's viability vary.
> >
> > Some additional thoughts: I believe everyone involved in XTable is
> > genuinely working towards making the right decisions for the project and
> > they are demonstrating good faith, e.g., hopefully evident in the prompt
> > response to the project's name change when concerns were raised. The goal
> > is to create a vendor-neutral project with a thriving, inclusive
> community.
> > In my view, given the current list of initial committers, there is no
> lack
> > of diversity, and including other committers from table format
> communities
> > does not address the remaining concern about the project, which stems
> from
> > the fact that it actually originated in a company backing one of the
> table
> > format projects, i.e., Apache Hudi.
> > Instead, I'd argue it's more important to focus on establishing XTable as
> > an independent project governed by ASF's meritocracy principles. That
> will
> > naturally serve as an invitation for individuals to contribute, become
> > committers, PPMC/PMC members, etc. While we are still in the very early
> > stages of that journey, I believe that focusing on these principles and
> > building the XTable community around them is ultimately the way to
> mitigate
> > the remaining concern.
> >
> > Thanks,
> > Jesús
> >
> >
> > [1] Apache Paimon (incubating):
> > https://lists.apache.org/thread/t29ghx79cp2rlw20s9p0b8o86c5lzgk7
> > [2] Apache Iceberg:
> > https://lists.apache.org/thread/lwlrscyklkxqmp28pbxpxko9r1vw4s4z
> > [3] Apache Hudi:
> > https://lists.apache.org/thread/3415j1lyp8nkgdv8sk378y8hvvmrt248
> > [4] Delta Lake: https://groups.google.com/g/delta-users/c/8btY3qHydwE
> >
> >
> > On Wed, Dec 13, 2023 at 3:04 PM Carl Steinbach 
> > wrote:
> >
> >> Hi Jesús,
> >>
> >> This is a great project, and I am eager to see it added to the
> incubator.
> >>
> >> It's great to see that the naming issue is being addressed, but could
> you
> >> also respond to the other concern Jacques raised about the need to
> broaden
> >> the list of initial committers to include members of the Iceberg and
> Delta
> >> communities?
> >>
> >> Thanks.
> >>
> >> - Carl
> >>
> >> On Mon, Dec 11, 2023 at 5:08 PM Jesus Camacho Rodriguez <
> >> jcama...@apache.org>
> >> wrote:
> >>
> >> > Thanks to everyone who expressed su

Re: [DISCUSS] OneTable proposal

2023-12-15 Thread Carl Steinbach 
the current list of initial committers, there is no
> > > lack
> > > > of diversity, and including other committers from table format
> > > communities
> > > > does not address the remaining concern about the project, which stems
> > > from
> > > > the fact that it actually originated in a company backing one of the
> > > table
> > > > format projects, i.e., Apache Hudi.
> > > > Instead, I'd argue it's more important to focus on establishing
> XTable
> > as
> > > > an independent project governed by ASF's meritocracy principles. That
> > > will
> > > > naturally serve as an invitation for individuals to contribute,
> become
> > > > committers, PPMC/PMC members, etc. While we are still in the very
> early
> > > > stages of that journey, I believe that focusing on these principles
> and
> > > > building the XTable community around them is ultimately the way to
> > > mitigate
> > > > the remaining concern.
> > > >
> > > > Thanks,
> > > > Jesús
> > > >
> > > >
> > > > [1] Apache Paimon (incubating):
> > > > https://lists.apache.org/thread/t29ghx79cp2rlw20s9p0b8o86c5lzgk7
> > > > [2] Apache Iceberg:
> > > > https://lists.apache.org/thread/lwlrscyklkxqmp28pbxpxko9r1vw4s4z
> > > > [3] Apache Hudi:
> > > > https://lists.apache.org/thread/3415j1lyp8nkgdv8sk378y8hvvmrt248
> > > > [4] Delta Lake:
> https://groups.google.com/g/delta-users/c/8btY3qHydwE
> > > >
> > > >
> > > > On Wed, Dec 13, 2023 at 3:04 PM Carl Steinbach <
> cwsteinb...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Jesús,
> > > > >
> > > > > This is a great project, and I am eager to see it added to the
> > > incubator.
> > > > >
> > > > > It's great to see that the naming issue is being addressed, but
> could
> > > you
> > > > > also respond to the other concern Jacques raised about the need to
> > > broaden
> > > > > the list of initial committers to include members of the Iceberg
> and
> > > Delta
> > > > > communities?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > - Carl
> > > > >
> > > > > On Mon, Dec 11, 2023 at 5:08 PM Jesus Camacho Rodriguez <
> > > > > jcama...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Thanks to everyone who expressed support and offered help. It's
> > > great to
> > > > > > see that the project's mission resonates with so many different
> > > people.
> > > > > >
> > > > > > Jacques, we acknowledge your concern about the project name. We
> are
> > > > > working
> > > > > > on selecting a new name for ASF incubation that avoids confusion
> > > with any
> > > > > > specific corporation or product in the space. Currently we are
> > doing
> > > some
> > > > > > due diligence to minimize the risk of having to change it again
> > > during
> > > > > > incubation; we'll update the proposal with the new name soon and
> > > share it
> > > > > > in this thread.
> > > > > >
> > > > > > Regarding the name-changing process and your concerns about it,
> > we're
> > > > > > looking for advice based on past experiences. Specifically, we're
> > > > > > considering whether it's better to change the project's name
> before
> > > > > pushing
> > > > > > the code to the ASF, or if it's more practical to push the code
> to
> > > the
> > > > > ASF
> > > > > > repository first and then proceed with the name change. Any
> > insights
> > > or
> > > > > > guidance on whether one option is better than the other based on
> > > previous
> > > > > > instances would be appreciated.
> > > > > >
> > > > > > Thanks,
> > > > > > Jesús
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, Dec 11, 2023 at 5:43 AM Jean-Baptiste Onofré <
> > > > > jbono...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Of course, it's a big +1 one for me.
> > > > > > >
> > > > > > > The purpose is interesting, creating "connection" with other
> > Apache
> > > > > > > projects.
> > > > > > > Happy to be a mentor on this proposal and contribute to the
> > > project :)
> > > > > > >
> > > > > > > Thanks !
> > > > > > > Regards
> > > > > > > JB
> > > > > > >
> > > > > > > On Mon, Dec 4, 2023 at 10:23 PM Jesus Camacho Rodriguez
> > > > > > >  wrote:
> > > > > > > >
> > > > > > > > Hi All,
> > > > > > > >
> > > > > > > > I would like to propose a new project to the ASF incubator -
> > > > > OneTable.
> > > > > > > >
> > > > > > > > OneTable[1] is an omni-directional converter for table
> formats
> > > that
> > > > > > > facilitates interoperability across data processing systems and
> > > query
> > > > > > > engines. Currently, OneTable supports widely adopted
> open-source
> > > table
> > > > > > > formats such as Apache Hudi, Apache Iceberg, and Delta Lake.
> > > > > > > >
> > > > > > > > Here is the proposal -
> > > > > > > >
> > > > > >
> > >
> https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal
> > > > > > > >
> > > > > > > > I would be the Champion of the project. I will mentor and
> help
> > > the
> > > > > > > project through the incubator with Hitesh Shah [
> > hit...@apache.org
> > > ],
> > > > > > > Stamatis Zampetakis [zabe...@apache.org], and Jean-Baptiste
> > > Onofré [
> > > > > > > jbono...@apache.org].
> > > > > > > >
> > > > > > > > We are looking forward to your feedback!
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Jesús
> > > > > > > >
> > > > > > > > [1] https://github.com/onetable-io/onetable
> > > > > > >
> > > > > >
> > > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [VOTE] Accept XTable into the ASF Incubator

2023-12-19 Thread Carl Steinbach 
+1 (binding)


On Tue, Dec 19, 2023 at 10:19 AM PJ Fanning  wrote:

> +1 (binding)
>
> On Tue, 19 Dec 2023 at 19:08, Subramaniam Krishnan 
> wrote:
> >
> > +1 (non-binding).
> >
> > Looking forward to this as will be very useful.
> >
> > Thanks,
> > Subru
> >
> > On 2023/12/19 02:15:02 roryqi wrote:
> > > +1
> > >
> > > larry mccay  于2023年12月19日周二 05:30写道：
> > >
> > > > +1 (binding)
> > > >
> > > >
> > > > On Sun, Dec 17, 2023 at 11:32 PM Rakesh Radhakrishnan <
> rake...@apache.org>
> > > > wrote:
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > I'm contributing to the Apache Hadoop project and mentoring Hive
> > > > > contributors in my company. It's a great initiative. The project
> looks
> > > > > interesting to me and can be really useful to the ecosystem.
> > > > >
> > > > > Thanks,
> > > > > Rakesh
> > > > >
> > > > > On Sat, Dec 16, 2023 at 9:48 AM Jesus Camacho Rodriguez <
> > > > > jcama...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > Following the discussion in the incubator mailing list [1], I am
> > > > starting
> > > > > > this official vote for the XTable project.
> > > > > >
> > > > > > Here is the proposal -
> > > > > >
> https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal
> > > > > >
> > > > > > Please cast your vote:
> > > > > >
> > > > > > [ ] +1, bring XTable into the Incubator
> > > > > > [ ] +0, I don't care either way
> > > > > > [ ] -1, do not bring XTable into the Incubator, because...
> > > > > >
> > > > > > This majority vote is open for at least 96 hours (due to the
> weekend).
> > > > > >
> > > > > > Only votes from Incubator PMC members are binding, but other
> votes are
> > > > > > welcome!
> > > > > >
> > > > > > Thanks,
> > > > > > Jesús
> > > > > >
> > > > > > [1]
> https://lists.apache.org/thread/rx9z8ffrf37qjhpkf1vp5rqg5lhht7jm
> > > > > >
> > > > >
> > > >
> > >
> >
> > -
> > 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
>
>

Bylaws != Guidelines

2024-07-03 Thread Carl Steinbach 
In 2018, Justin McLean led an effort to draft a set of project bylaws that
a) apply to projects that don't have bylaws and b) serve as a convenient
starting point for projects that are drafting their own bylaws. This effort
ultimately resulted in the Default Project Guidelines [1] document
located on the Incubator wiki. One change that didn't trigger any
discussion at the time [2] was the decision to use the word "guideline"
instead of "bylaw." This strikes me as odd since there is a major
substantive difference between the meaning of these two words.

Here's how the two words are defined in the Cambridge Dictionary:

- Bylaw: "a rule that GOVERNS the members of an organization." [3]
[emphasis added]

- Guideline: "information intended to advise people on how something SHOULD
BE done or what something SHOULD BE." [4] [emphasis added]

Wikipedia, while not an authoritative source, provides useful context on
how these terms are used in practice:

- "A bylaw ... is a set of rules or law established by an organization or
community so as to regulate itself, as allowed or provided for by some
higher authority." [5]

- "A guideline is similar to a rule, but are legally less binding as
justified deviations are possible." [6]

I am neither a lawyer nor a lexicographer, but it seems clear that a
guideline carries no more weight than an officially approved suggestion,
while a bylaw is a binding rule. While it's up to each PMC to decide
whether they want to adopt a set of non-binding suggestions that SHOULD BE
[7] followed or a set of binding laws that MUST BE followed, I think it's
important for the IPMC to clarify that the former are called guidelines,
the latter are called bylaws, and that PMCs need to be aware of the
difference.

Thanks.

- Carl

[1]
https://cwiki.apache.org/confluence/display/INCUBATOR/Default+Project+Guidelines
[2] https://lists.apache.org/thread/h15qjp35ghg446xr5bnmmlg06p3hdoj9
[3] https://dictionary.cambridge.org/us/dictionary/english/bylaw
[4] https://dictionary.cambridge.org/us/dictionary/english/guideline
[5] https://en.wikipedia.org/w/index.php?title=By-law&oldid=1215430864
[6] https://en.wikipedia.org/w/index.php?title=Guideline&oldid=1185185478
[7] https://datatracker.ietf.org/doc/html/rfc2119

Re: Bylaws != Guidelines

2024-07-03 Thread Carl Steinbach 
Dave, thanks for the historical context.

Taking this into account, I propose making the following changes to the
Default Project Guidelines document:

1) Change the title to Default Project Bylaws
2) Replace all occurrences of "guideline" with "bylaw."
3) Add language to the beginning of the document stating that these bylaws
are subordinate to the ASF's bylaws.

Thoughts?

- Carl

On Wed, Jul 3, 2024 at 1:02 PM Dave Fisher  wrote:

> Top post, but if my memory serves me properly Guidelines was used because
> the ASF’s ByLaws - https://www.apache.org/foundation/bylaws.html - must
> not be overridden by project “bylaws”.
>
> Best,
> Dave
>
> > On Jul 3, 2024, at 12:35 PM, Carl Steinbach  wrote:
> >
> > In 2018, Justin McLean led an effort to draft a set of project bylaws
> that
> > a) apply to projects that don't have bylaws and b) serve as a convenient
> > starting point for projects that are drafting their own bylaws. This
> effort
> > ultimately resulted in the Default Project Guidelines [1] document
> > located on the Incubator wiki. One change that didn't trigger any
> > discussion at the time [2] was the decision to use the word "guideline"
> > instead of "bylaw." This strikes me as odd since there is a major
> > substantive difference between the meaning of these two words.
> >
> > Here's how the two words are defined in the Cambridge Dictionary:
> >
> > - Bylaw: "a rule that GOVERNS the members of an organization." [3]
> > [emphasis added]
> >
> > - Guideline: "information intended to advise people on how something
> SHOULD
> > BE done or what something SHOULD BE." [4] [emphasis added]
> >
> > Wikipedia, while not an authoritative source, provides useful context on
> > how these terms are used in practice:
> >
> > - "A bylaw ... is a set of rules or law established by an organization or
> > community so as to regulate itself, as allowed or provided for by some
> > higher authority." [5]
> >
> > - "A guideline is similar to a rule, but are legally less binding as
> > justified deviations are possible." [6]
> >
> > I am neither a lawyer nor a lexicographer, but it seems clear that a
> > guideline carries no more weight than an officially approved suggestion,
> > while a bylaw is a binding rule. While it's up to each PMC to decide
> > whether they want to adopt a set of non-binding suggestions that SHOULD
> BE
> > [7] followed or a set of binding laws that MUST BE followed, I think it's
> > important for the IPMC to clarify that the former are called guidelines,
> > the latter are called bylaws, and that PMCs need to be aware of the
> > difference.
> >
> > Thanks.
> >
> > - Carl
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Default+Project+Guidelines
> > [2] https://lists.apache.org/thread/h15qjp35ghg446xr5bnmmlg06p3hdoj9
> > [3] https://dictionary.cambridge.org/us/dictionary/english/bylaw
> > [4] https://dictionary.cambridge.org/us/dictionary/english/guideline
> > [5] https://en.wikipedia.org/w/index.php?title=By-law&oldid=1215430864
> > [6]
> https://en.wikipedia.org/w/index.php?title=Guideline&oldid=1185185478
> > [7] https://datatracker.ietf.org/doc/html/rfc2119
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Polaris into the ASF Incubator

2024-08-02 Thread Carl Steinbach 
+1 binding

On Fri, Aug 2, 2024 at 11:40 AM PJ Fanning  wrote:

> +1 binding
>
> On Fri, 2 Aug 2024 at 19:34, Robert Stupp  wrote:
> >
> > +1 (nb)
> >
> > On 02.08.24 19:26, Jean-Baptiste Onofré wrote:
> > > Hi folks,
> > >
> > > Following the discussion about Polaris
> > > (https://lists.apache.org/thread/ymz26dr3bzldbntdgpctbtkb787x311d),
> > > and after updating the proposal based on comments, I would like to
> > > start the formal vote to accept Polaris into the ASF Incubator.
> > >
> > > As reminder, this is the Polaris Proposal:
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/PolarisProposal
> > >
> > > Please cast your vote:
> > > [ ] +1, accept Polaris into the ASF Incubator
> > > [ ] 0, I don't care either way
> > > [ ] -1, do not accept Polaris into the ASF Incubator, because ...
> > >
> > > The vote will run for one week starting from today.
> > >
> > > Thanks !
> > > Regards
> > > JB
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > --
> > Robert Stupp
> > @snazy
> >
> >
> > -
> > 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
>
>