I’m happy to serve as the initial VP if that is the consensus.

I like the idea that the post comes up annually, and that triggers a “state of 
the project” discussion. And it would be great if I can rotate the role to 
someone else. I share Ted’s concerns about diversity - not just in the VP, but 
also in release managers and committers (i.e. people taking third-party 
contributions and committing them to master branch).

To improve diversity, I think it would help if we start counting and reporting 
who is doing third-party commits. There’s too much of me right now. 

Also, it doesn’t need to be in the bylaws, but after graduation, let’s agree a 
“start date” so that the appointment is exactly a year. (Analogous to Jan 20 
for US presidents.)

Julian


> On Sep 3, 2015, at 10:55 PM, Nick Dimiduk <[email protected]> wrote:
> 
> +1 on Julian as initial VP, if he's interested in holding the
> responsibility. I like Jacques's suggestion of a "renewal consideration" on
> some interval. I'm not sure this is necessary to include as bylaws, more
> like a healthy practice for a democratically organized endeavor.
> 
> -n
> 
> On Wed, Sep 2, 2015 at 10:03 PM, Jacques Nadeau <[email protected]> wrote:
> 
>> My thoughts on this are a little different. I like the concept as it simply
>> causes a discussion to happen once a year. The community can always choose
>> to have the same person. This just helps us lazy people to remember to
>> discuss this on occasion. Momentum is great and time flies. I like having a
>> reminder once in a while...
>> On Sep 2, 2015 9:49 PM, "Ted Dunning" <[email protected]> wrote:
>> 
>>> 
>>> Hmmm.  Rotating often is really good for spreading knowledge.
>>> 
>>> If calcite has any defect it is the tendency to depend on Julian's high
>>> throughput.  Hard to argue with in the moment but the project will do
>>> better from spreading the load and experience.  Having Jacques run the
>> last
>>> release was a great step in that direction.
>>> 
>>> 
>>> Sent from my iPhone
>>> 
>>>> On Sep 2, 2015, at 21:10, James Taylor <[email protected]> wrote:
>>>> 
>>>> +1 to Julian as VP. If folks are willing to step up for taking the
>> reins,
>>>> that's a good idea, but a yearly rotation may be too frequent
>> (especially
>>>> initially) IMHO.
>>>> 
>>>>> On Wed, Sep 2, 2015 at 8:48 PM, Jacques Nadeau <[email protected]>
>>> wrote:
>>>>> 
>>>>> I appreciate the humility but I think it is a no-brainer that Julian
>>> should
>>>>> be the VP.  The one thought I suggest is having a rotating chair each
>>> year.
>>>>> Thoughts on that?
>>>>> 
>>>>> 
>>>>>> On Tue, Sep 1, 2015 at 5:48 PM, Julian Hyde <[email protected]>
>> wrote:
>>>>>> 
>>>>>> Let’s agree on the text of the motion before we start a vote. I
>> propose
>>>>>> the following text (see below).
>>>>>> 
>>>>>> If you are a committer, please:
>>>>>> 
>>>>>> 1. Review the text.
>>>>>> 
>>>>>> 2. Remove your name from the list, if you do NOT wish to remain a
>>>>>> committer after graduation. (You can email me privately if you
>> prefer.)
>>>>>> 
>>>>>> 3. Send nominations for an initial Vice President. (This will replace
>>> the
>>>>>> placeholder, "<TBD>”, in the text below.)
>>>>>> 
>>>>>> At Ted’s suggestion, I started a thread on the Incubator list asking
>> a
>>>>>> shepherd to review.
>>>>>> 
>>>>>> Julian
>>>>>> 
>>>>>> 
>>>>>> - - - - snip
>>>>>> 
>>>>>> 
>>>>>> 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 parsing and planning queries on data in a wide variety of formats.
>>>>>> 
>>>>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>>>> (PMC),
>>>>>> to be known as the "Apache Calcite Project", be and hereby is
>>> established
>>>>>> pursuant to Bylaws of the Foundation; and be it further
>>>>>> 
>>>>>> RESOLVED, that the Apache Calcite Project be and hereby is
>> responsible
>>>>> for
>>>>>> the creation and maintenance of software related to interactive
>>> analysis
>>>>> of
>>>>>> large-scale datasets; and be it further RESOLVED, that the office of
>>>>> "Vice
>>>>>> President, Apache Calcite" 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 Calcite Project, and to have primary
>> responsibility
>>>>> for
>>>>>> management of the projects within the scope of responsibility of the
>>>>> Apache
>>>>>> Calcite 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 Calcite Project:
>>>>>> 
>>>>>> * Alan Gates <gates at apache dot org>
>>>>>> * Aman Sinha <amansinha at apache dot org>
>>>>>> * Ashutosh Chauhan <hashutosh at apache dot org>
>>>>>> * Chris Wensel <cwensel at apache dot org>
>>>>>> * James R. Taylor <jamestaylor at apache dot org>
>>>>>> * Jacques Nadeau <jacques at apache dot org>
>>>>>> * Jesús Camacho Rodríguez <jcamacho at apache dot org>
>>>>>> * Jinfeng Ni <jni at apache dot org>
>>>>>> * John Pullokkaran <jpullokk at apache dot org>
>>>>>> * Julian Hyde <jhyde at apache dot org>
>>>>>> * Nick Dimiduk <ndimiduk at apache dot org>
>>>>>> * Steven Noels <stevenn at apache dot org>
>>>>>> * Ted Dunning <tdunning at apache dot org>
>>>>>> * Vladimir Sitnikov <vladimirsitnikov at apache dot org>
>>>>>> 
>>>>>> 
>>>>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that <TBD> be appointed to
>> the
>>>>>> office of Vice President, Apache Calcite, 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 Calcite Project be and hereby is tasked
>> with
>>>>> the
>>>>>> migration and rationalization of the Apache Incubator Calcite
>> podling;
>>>>> and
>>>>>> be it further
>>>>>> 
>>>>>> RESOLVED, that all responsibilities pertaining to the Apache
>> Incubator
>>>>>> Calcite podling encumbered upon the Apache Incubator Project are
>>>>> hereafter
>>>>>> discharged.
>>>>>> 
>>>>>> - - - -
>>>>> 
>>> 
>> 

Reply via email to