Re: [VOTE] Graduate Calcite from the Apache Incubator

[Steven Noels]

On Tue, Sep 15, 2015, at 03:56 AM, Julian Hyde wrote:

> This is a vote for Calcite to become a top-level project.
> 
> Since joining the Incubator in May, 2014, the Calcite
> community has:
> * Produced eight IPMC-approved releases under two release
>   managers;
> * Added five new committers and one new PPMC member;
> * Collaborated successfully with several other Apache
> projects (Drill, Hive, Kylin, Phoenix, Samza);
> * Grown into an active community (typical monthly activity
>   is 100 emails, 30 commits and 20 issues fixed);
> * Conducted a successful community vote to graduate with
>   20 +1 votes, of which 2 were from our mentors, 12 were
>   from committers, and 6 were from IPMC members.
> 
> Further information: the discussion on the dev list [1],
> vote thread [2] and result [3]. Also relevant are the
> incubation status page [4] and a thread on this list
> requesting review of whether Calcite met the criteria to
> graduate [5].
> 
> Below is our proposed resolution for the Board.
> 
> Please vote:
> 
> [ ] +1 Graduate Apache Calcite as a top-level project
> [ ] +0
> [ ] -1 Do not graduate Apache Calcite because…

Enthusiastic +1

Great job!

Steven.


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

Re: [VOTE] Release Apache Brooklyn 0.8.0-incubating [rc2]

[Justin Mclean]

Hi,

> Your files [2]-[5] are covered as part of distributions of packages we 
> already credit.

You may want to double check, but these are relatively minor issues as 
everything is permissive here.

While both data tables and data tables extensions are MIT licensed they are 
different products and may have different copyright owners. [1] You also notice 
the years are different in the MIT licenses [2][3]. I don’t know for instance 
how IP is handled by Spry Media with the plug ins, (for instance) do they get 
plug in contributors to sign ICLAs?

Query wiggle has this header:
 /*
jQuery Wiggle
Author: WonderGroup, Jordan Thomas
URL: http://labs.wondergroup.com/demos/mini-ui/index.html
License: MIT (http://en.wikipedia.org/wiki/MIT_License)
*/

Only Swagger UI is mentioned in the LICENSE file. I can see it's a separate 
project here [4].

Similar issue with text the LICENSE has require.js (some owners as text) but 
iit’s a separate project here [5]. You licence includes the URLs so may be good 
to add that.

> As for the structure of our LICENSE we wanted it to be it clear from the 
> start that there are multiple parts to the file.

No issue with it and up to you if you want to change it or not. Just that it's 
different format to other Apache projects so took more time to review.

Thanks,
Justin

1. http://www.datatables.net/plug-ins/api/fnStandingRedraw
2. https://github.com/DataTables/DataTables/blob/master/license.txt
3. https://github.com/DataTables/Plugins/blob/master/License.txt
4. https://github.com/jordanthomas/jquery-wiggle
5. https://github.com/requirejs/text
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Release Sentry incubating version 1.6.0 (rc0)

[Sun, Dapeng]

Hi Sravya,

Good suggestion, I will resend the voting email.

Regards
Dapeng

-Original Message-
From: Sravya Tirukkovalur [mailto:sra...@cloudera.com] 
Sent: Wednesday, September 16, 2015 2:07 AM
To: dev
Cc: general@incubator.apache.org
Subject: Re: [VOTE] Release Sentry incubating version 1.6.0 (rc0)

Hi Dapeng,

As recommended on the dev list[1] can you resend the voting email on general 
with updated PPMC votes?

Thanks

[1]:
http://mail-archives.apache.org/mod_mbox/sentry-dev/201509.mbox/%3CB957EE1AFDEBFD4B934BCF11804A23DC032933E5%40shsmsx102.ccr.corp.intel.com%3E


On Tue, Sep 15, 2015 at 12:08 AM, Sun, Dapeng  wrote:

> Hi Dear Mentors,
>
> This is the incubator release of Apache Sentry, version 1.6.0-incubating.
>
>
>
> The list of fixed issues, added features and improvements can be found
> here:
>
> http://s.apache.org/w5
>
>
>
>
>
> Source files :
> https://dist.apache.org/repos/dist/dev/incubator/sentry/1.6.0-incubati
> ng-rc0/
>
>
>
>
>
> Tag to be voted on (release-1.6.0-rc0/SHA:
> 3c122b76483531db5f0de82cd80d9ce5967f6e00):
>
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=commi
> t;h=3c122b76483531db5f0de82cd80d9ce5967f6e00
>
>
>
>
>
> Sentry's KEYS containing the PGP key we used to sign the release:
>
> http://www.apache.org/dist/incubator/sentry/KEYS
>
>
>
>
>
> Note that this is a source only release and we are voting on the source:
>
> tag=release-1.6.0-rc0, SHA=3c122b76483531db5f0de82cd80d9ce5967f6e00
>
> A vote on releasing this package has already passed in Apache Sentry 
> PPMC[1] including +1 votes from our PPMC (Sravya Tirukkovalur, Lenni 
> Kuff, Prasad Mujumdar, Anne Yu).
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Regards
> Dapeng
>
>
> [1] -
> http://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20v
> ote%20release%20order%3Adate-backward+page:1+mid:5rp3ibtacb3xjryk+stat
> e:results
>
>


--
Sravya Tirukkovalur

Re: [VOTE] Graduate Calcite from the Apache Incubator

[Amol Kekre]

+1 (non-binding)

Thks
Amol

On Tue, Sep 15, 2015 at 2:22 PM, Seetharam Venkatesh <
venkat...@innerzeal.com> wrote:

> +1.
>
> Thanks,
> Venkatesh
>
> On Tue, Sep 15, 2015 at 2:16 PM Henry Saputra 
> wrote:
>
> > +1
> >
> > Good job guys
> >
> > On Mon, Sep 14, 2015 at 6:56 PM, Julian Hyde  wrote:
> > > This is a vote for Calcite to become a top-level project.
> > >
> > > Since joining the Incubator in May, 2014, the Calcite
> > > community has:
> > > * Produced eight IPMC-approved releases under two release
> > >   managers;
> > > * Added five new committers and one new PPMC member;
> > > * Collaborated successfully with several other Apache
> > > projects (Drill, Hive, Kylin, Phoenix, Samza);
> > > * Grown into an active community (typical monthly activity
> > >   is 100 emails, 30 commits and 20 issues fixed);
> > > * Conducted a successful community vote to graduate with
> > >   20 +1 votes, of which 2 were from our mentors, 12 were
> > >   from committers, and 6 were from IPMC members.
> > >
> > > Further information: the discussion on the dev list [1],
> > > vote thread [2] and result [3]. Also relevant are the
> > > incubation status page [4] and a thread on this list
> > > requesting review of whether Calcite met the criteria to
> > > graduate [5].
> > >
> > > Below is our proposed resolution for the Board.
> > >
> > > Please vote:
> > >
> > > [ ] +1 Graduate Apache Calcite as a top-level project
> > > [ ] +0
> > > [ ] -1 Do not graduate Apache Calcite because…
> > >
> > > Here is my vote:
> > > +1 (binding)
> > >
> > > Voting will last 72 hours, ending at 19:00 Pacific on
> > > September 17th.
> > >
> > > Julian Hyde, on behalf of Calcite PPMC
> > >
> > > [1] http://s.apache.org/ZPC
> > > [2] http://s.apache.org/rvB
> > > [3] http://s.apache.org/sv
> > > [4] http://incubator.apache.org/projects/calcite.html
> > > [5] http://s.apache.org/itP
> > >
> > > - - - 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 parsing and planning queries on data in a wide
> > > variety of formats; 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 
> > > * Aman Sinha 
> > > * Ashutosh Chauhan 
> > > * James R. Taylor 
> > > * Jacques Nadeau 
> > > * Jesús Camacho Rodríguez 
> > > * Jinfeng Ni 
> > > * John Pullokkaran 
> > > * Julian Hyde 
> > > * Nick Dimiduk 
> > > * Steven Noels 
> > > * Ted Dunning 
> > > * Vladimir Sitnikov 
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.
> > >
> > > - - - end - - -
> > >
> > >
> > > -
> > > 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 Calcite from the Apache Incubator

[Nick Dimiduk]

+1 (non-binding)

On Monday, September 14, 2015, Julian Hyde  wrote:

> This is a vote for Calcite to become a top-level project.
>
> Since joining the Incubator in May, 2014, the Calcite
> community has:
> * Produced eight IPMC-approved releases under two release
>   managers;
> * Added five new committers and one new PPMC member;
> * Collaborated successfully with several other Apache
> projects (Drill, Hive, Kylin, Phoenix, Samza);
> * Grown into an active community (typical monthly activity
>   is 100 emails, 30 commits and 20 issues fixed);
> * Conducted a successful community vote to graduate with
>   20 +1 votes, of which 2 were from our mentors, 12 were
>   from committers, and 6 were from IPMC members.
>
> Further information: the discussion on the dev list [1],
> vote thread [2] and result [3]. Also relevant are the
> incubation status page [4] and a thread on this list
> requesting review of whether Calcite met the criteria to
> graduate [5].
>
> Below is our proposed resolution for the Board.
>
> Please vote:
>
> [ ] +1 Graduate Apache Calcite as a top-level project
> [ ] +0
> [ ] -1 Do not graduate Apache Calcite because…
>
> Here is my vote:
> +1 (binding)
>
> Voting will last 72 hours, ending at 19:00 Pacific on
> September 17th.
>
> Julian Hyde, on behalf of Calcite PPMC
>
> [1] http://s.apache.org/ZPC
> [2] http://s.apache.org/rvB
> [3] http://s.apache.org/sv
> [4] http://incubator.apache.org/projects/calcite.html
> [5] http://s.apache.org/itP
>
> - - - 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 parsing and planning queries on data in a wide
> variety of formats; 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 
> * Aman Sinha 
> * Ashutosh Chauhan 
> * James R. Taylor 
> * Jacques Nadeau 
> * Jesús Camacho Rodríguez 
> * Jinfeng Ni 
> * John Pullokkaran 
> * Julian Hyde 
> * Nick Dimiduk 
> * Steven Noels 
> * Ted Dunning 
> * Vladimir Sitnikov 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.
>
> - - - end - - -
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
>
>

Re: [VOTE] Graduate Calcite from the Apache Incubator

[Li Yang]

+1 (non-binding)  :-)

On Wed, Sep 16, 2015 at 10:45 AM, Nick Dimiduk  wrote:

> +1 (non-binding)
>
> On Monday, September 14, 2015, Julian Hyde  wrote:
>
> > This is a vote for Calcite to become a top-level project.
> >
> > Since joining the Incubator in May, 2014, the Calcite
> > community has:
> > * Produced eight IPMC-approved releases under two release
> >   managers;
> > * Added five new committers and one new PPMC member;
> > * Collaborated successfully with several other Apache
> > projects (Drill, Hive, Kylin, Phoenix, Samza);
> > * Grown into an active community (typical monthly activity
> >   is 100 emails, 30 commits and 20 issues fixed);
> > * Conducted a successful community vote to graduate with
> >   20 +1 votes, of which 2 were from our mentors, 12 were
> >   from committers, and 6 were from IPMC members.
> >
> > Further information: the discussion on the dev list [1],
> > vote thread [2] and result [3]. Also relevant are the
> > incubation status page [4] and a thread on this list
> > requesting review of whether Calcite met the criteria to
> > graduate [5].
> >
> > Below is our proposed resolution for the Board.
> >
> > Please vote:
> >
> > [ ] +1 Graduate Apache Calcite as a top-level project
> > [ ] +0
> > [ ] -1 Do not graduate Apache Calcite because…
> >
> > Here is my vote:
> > +1 (binding)
> >
> > Voting will last 72 hours, ending at 19:00 Pacific on
> > September 17th.
> >
> > Julian Hyde, on behalf of Calcite PPMC
> >
> > [1] http://s.apache.org/ZPC
> > [2] http://s.apache.org/rvB
> > [3] http://s.apache.org/sv
> > [4] http://incubator.apache.org/projects/calcite.html
> > [5] http://s.apache.org/itP
> >
> > - - - 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 parsing and planning queries on data in a wide
> > variety of formats; 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 
> > * Aman Sinha 
> > * Ashutosh Chauhan 
> > * James R. Taylor 
> > * Jacques Nadeau 
> > * Jesús Camacho Rodríguez 
> > * Jinfeng Ni 
> > * John Pullokkaran 
> > * Julian Hyde 
> > * Nick Dimiduk 
> > * Steven Noels 
> > * Ted Dunning 
> > * Vladimir Sitnikov 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.
> >
> > - - - end - - -
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > 
> > For additional commands, e-mail: general-h...@incubator.apache.org
> > 
> >
> >
>

Re: [RESULT][VOTE] TinkerPop 3.0.1-incubating Release

[John D. Ament]

Apologies, I looked at the last email not the first
On Sep 15, 2015 17:31, "Stephen Mallette"  wrote:

> Hi John, the vote has been open since September 8th - here's where it
> started:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3CCAA-H438vLKoQiJ%3Dcn6CXPYOvueHrvzbBQ_LhKgmxjVkeMceAMQ%40mail.gmail.com%3E
>
> On Tue, Sep 15, 2015 at 5:13 PM, John D. Ament 
> wrote:
>
> > Ideally we leave votes open for 72 hrs in case anyone has a -1 after 3
> +1s
> > cast.
> > On Sep 15, 2015 15:55, "Stephen Mallette"  wrote:
> >
> > > The vote for releasing Apache TinkerPop passed with 3 binding +1s, 0
> > > non-binding +1s, and no 0 or -1.
> > >
> > > Binding +1s:
> > > Daniel Gruno
> > > Justin Mclean
> > > Rich Bowen
> > >
> > > Thanks to those who gave us a hand and added a vote.
> > >
> > > Separately, Justin, I'll try to get LICENSE/NOTICE right for the next
> > run.
> > > I suspect I'll be pinging this list separately for a bit more guidance
> > > before then.  Thanks.
> > >
> > > Stephen
> > >
> > > On Tue, Sep 15, 2015 at 5:39 AM, Justin Mclean <
> jus...@classsoftware.com
> > >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > > I suppose I still could have missed something, but I thought i'd
> > gotten
> > > > the bulk of it right - could you please
> > > > > tell me what you noticed that I missed or misunderstood from your
> > last
> > > > > post?
> > > >
> > > > Only things in the release need to be in LICENSE or NOTICE [1]. I’d
> > check
> > > > that first. Permissive licensed software (i.e. MIT/BSD) don't need to
> > go
> > > in
> > > > NOTICE [5], I can see there a few of those there.
> > > >
> > > > > Does that simply mean that I should remove all apache licensed
> > > > dependencies
> > > > > from the binary NOTICE and all is good?
> > > >
> > > > Generally when adding Apache licenced software there's no need to
> > modify
> > > > LICENSE or NOTICE unless it has a NOTICE file [2]. That means you
> > > generally
> > > > don’t have to add much when bundling other ASF projects especially
> when
> > > > they have a boilerplate NOTICE file. [3] The no need to add Apache
> > > licensed
> > > > software to LICENSE but it not an licensing error to do so. I
> generally
> > > > don’t mind that as it makes checking releases a little easier when
> > > > reviewing.
> > > >
> > > > Not that dependancies of dependancies matter [4]. Rather than go down
> > > that
> > > > rabbit hole just look inside all the jars in the release with
> something
> > > > like this:
> > > > find . -name "*.jar" -exec tar ft {} \; | sort -u > paths.txt
> > > >
> > > > Look at all of the classes contained to see what’s included. For
> > example
> > > > with TinkerPop I see that it includes "com/carrotsearch/hppc” and
> > looking
> > > > at its license (Apache) I can see it has a NOTICE file (which looks
> > > > incorrect but that’s another story), so that would need to be
> > considered
> > > > and possibly something added to TinkerPop’s NOTICE. In this case I’d
> > > > probably assume a standard NOTICE and add a copyright line to the
> > NOTICE
> > > > file - but that’s not the only valid solution. It's may not be always
> > > clear
> > > > cut what needs to be done and you may have to consider each on a case
> > by
> > > > case basis.
> > > >
> > > > If any questions come up ask you mentors, ask this list or on legal
> > > > discuss.
> > > >
> > > > Thanks,
> > > > Justin
> > > >
> > > > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> > > > 2.. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> > > > 3. http://www.apache.org/dev/licensing-howto.html#bundle-asf-product
> > > > 4. http://www.apache.org/dev/licensing-howto.html#deps-of-deps
> > > > 5. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

[VOTE] Release Sentry incubating version 1.6.0 (rc0)

[Sun, Dapeng]

Hi Dear Mentors,

This is the incubator release of Apache Sentry, version 1.6.0-incubating.



The list of fixed issues, added features and improvements can be found here:

http://s.apache.org/w5





Source files : 
https://dist.apache.org/repos/dist/dev/incubator/sentry/1.6.0-incubating-rc0/





Tag to be voted on (release-1.6.0-rc0/SHA: 
3c122b76483531db5f0de82cd80d9ce5967f6e00):

https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=commit;h=3c122b76483531db5f0de82cd80d9ce5967f6e00





Sentry's KEYS containing the PGP key we used to sign the release:

http://www.apache.org/dist/incubator/sentry/KEYS





Note that this is a source only release and we are voting on the source:

tag=release-1.6.0-rc0, SHA=3c122b76483531db5f0de82cd80d9ce5967f6e00

A vote on releasing this package has already passed in Apache Sentry
PPMC[1] including +1 votes from our PPMC (Sravya Tirukkovalur, Lenni Kuff, 
Prasad Mujumdar, Anne Yu).

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Regards
Dapeng


[1] - 
http://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20vote%20release%20order%3Adate-backward+page:1+mid:5rp3ibtacb3xjryk+state:results

Re: Wiki Access for project proposal

[Nick Burch]

On Tue, 15 Sep 2015, Kris Popat wrote:
Can someone give me write access to the wiki so I can put up the ORDs 
project proposal. I’ve registered an account and my username is 
krispopat


Karma granted


Also, assuming you're based in Oxford too, while I don't have the cycles 
to help mentor ORDS at the moment, I could probably manage an hour over 
lunch / a pint one evening, to offer some incubation advice


Nick

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

Re: [VOTE] Graduate Calcite from the Apache Incubator

[Owen O'Malley]

+1 (binding)

On Tue, Sep 15, 2015 at 9:48 AM, Ted Dunning  wrote:

>
> +1 (binding)
>
> Sent from my iPhone
>
> > On Sep 14, 2015, at 22:56, Balaji Ganesan  wrote:
> >
> > +1
> >
> > On Mon, Sep 14, 2015 at 8:47 PM, Chris Nauroth  >
> > wrote:
> >
> >> +1 (binding)
> >>
> >> --Chris Nauroth
> >>
> >>
> >>
> >>
> >>> On 9/14/15, 6:56 PM, "Julian Hyde"  wrote:
> >>>
> >>> This is a vote for Calcite to become a top-level project.
> >>>
> >>> Since joining the Incubator in May, 2014, the Calcite
> >>> community has:
> >>> * Produced eight IPMC-approved releases under two release
> >>> managers;
> >>> * Added five new committers and one new PPMC member;
> >>> * Collaborated successfully with several other Apache
> >>> projects (Drill, Hive, Kylin, Phoenix, Samza);
> >>> * Grown into an active community (typical monthly activity
> >>> is 100 emails, 30 commits and 20 issues fixed);
> >>> * Conducted a successful community vote to graduate with
> >>> 20 +1 votes, of which 2 were from our mentors, 12 were
> >>> from committers, and 6 were from IPMC members.
> >>>
> >>> Further information: the discussion on the dev list [1],
> >>> vote thread [2] and result [3]. Also relevant are the
> >>> incubation status page [4] and a thread on this list
> >>> requesting review of whether Calcite met the criteria to
> >>> graduate [5].
> >>>
> >>> Below is our proposed resolution for the Board.
> >>>
> >>> Please vote:
> >>>
> >>> [ ] +1 Graduate Apache Calcite as a top-level project
> >>> [ ] +0
> >>> [ ] -1 Do not graduate Apache Calcite becauseŠ
> >>>
> >>> Here is my vote:
> >>> +1 (binding)
> >>>
> >>> Voting will last 72 hours, ending at 19:00 Pacific on
> >>> September 17th.
> >>>
> >>> Julian Hyde, on behalf of Calcite PPMC
> >>>
> >>> [1] http://s.apache.org/ZPC
> >>> [2] http://s.apache.org/rvB
> >>> [3] http://s.apache.org/sv
> >>> [4] http://incubator.apache.org/projects/calcite.html
> >>> [5] http://s.apache.org/itP
> >>>
> >>> - - - 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 parsing and planning queries on data in a wide
> >>> variety of formats; 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 
> >>> * Aman Sinha 
> >>> * Ashutosh Chauhan 
> >>> * James R. Taylor 
> >>> * Jacques Nadeau 
> >>> * Jesús Camacho Rodríguez 
> >>> * Jinfeng Ni 
> >>> * John Pullokkaran 
> >>> * Julian Hyde 
> >>> * Nick Dimiduk 
> >>> * Steven Noels 
> >>> * Ted Dunning 
> >>> * Vladimir Sitnikov 
> >>>
> >>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.
> >>>
> >>> - - - end - - -
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: 

Re: [VOTE] Release Apache Brooklyn 0.8.0-incubating [rc2]

[Alex Heneveld]

Hi Justin,

// cross posting to dev@brooklyn

Thanks for the detailed review.

Good spot on the other items included in r.js.  We had missed those.  
All look to be MIT or BSD and so are fine but we do need to call them 
out; I will do this.


Your files [2]-[5] are covered as part of distributions of packages we 
already credit.  I agree we should call out in the LICENSE all files we 
include which come from a given distribution; I'll do this also.  (These 
files are all already listed in [1] so it is an easy addition to have 
this info included in the auto-generated LICENSE.)


As for the structure of our LICENSE we wanted it to be it clear from the 
start that there are multiple parts to the file.  This is because it is 
otherwise so easy to overlook embedded licenses; you do a `less` and 
assume it's all one license (as we did with r.js).  Is our structure 
okay given this?  Or is there a better way we can accomplish this?


Cheers
Alex

[1] 
https://github.com/apache/incubator-brooklyn/blob/master/usage/dist/licensing/overrides.yaml



 Forwarded Message 
Subject:Re: [VOTE] Release Apache Brooklyn 0.8.0-incubating [rc2]
Date:   Sat, 12 Sep 2015 09:49:50 +1000
From:   Justin Mclean 
Reply-To:   general@incubator.apache.org
To: general@incubator.apache.org



Hi,

+1 binding

For the source release I checked:
- release files contain incubating
- signatures and hashes correct
- DISCLAIMER exists
- LICENSE has some issues (see below)
- NOTICE is OK  
- No unexpected binary files
- Source files have headers (a few test resources / sample files including java 
files don’t however)

Some issues:
- The LICENSE files is structured a little strangely you might want to make it 
more like other projects.
- In r.js [2] there a number of copyright owners/licenses (most look to BSD 
licenses) that are missing from LICENSE. e.g. uglifyjs, parsejs and base64 code.
- LICENSE is missing sections for dataTables.extensions.js [2], 
jquery.slideto.min.js [3], jquery.wiggle.min.js [4] and possible text.js [5].

Thanks,
Justin

1. ./usage/jsgui/src/build/requirejs-maven-plugin/r.js
2. ./usage/jsgui/src/main/webapp/assets/js/libs/dataTables.extensions.js
3. 
./apache-brooklyn-0.8.0-incubating-src/usage/jsgui/src/main/webapp/assets/js/libs/jquery.slideto.min.js
4. ./usage/jsgui/src/main/webapp/assets/js/libs/jquery.wiggle.min.js
5. ./usage/jsgui/src/main/webapp/assets/js/libs/text.js
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




--
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP


This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.


Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.

Re: [VOTE] Release Sentry incubating version 1.6.0 (rc0)

[Sravya Tirukkovalur]

Hi Dapeng,

As recommended on the dev list[1] can you resend the voting email on
general with updated PPMC votes?

Thanks

[1]:
http://mail-archives.apache.org/mod_mbox/sentry-dev/201509.mbox/%3CB957EE1AFDEBFD4B934BCF11804A23DC032933E5%40shsmsx102.ccr.corp.intel.com%3E


On Tue, Sep 15, 2015 at 12:08 AM, Sun, Dapeng  wrote:

> Hi Dear Mentors,
>
> This is the incubator release of Apache Sentry, version 1.6.0-incubating.
>
>
>
> The list of fixed issues, added features and improvements can be found
> here:
>
> http://s.apache.org/w5
>
>
>
>
>
> Source files :
> https://dist.apache.org/repos/dist/dev/incubator/sentry/1.6.0-incubating-rc0/
>
>
>
>
>
> Tag to be voted on (release-1.6.0-rc0/SHA:
> 3c122b76483531db5f0de82cd80d9ce5967f6e00):
>
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=commit;h=3c122b76483531db5f0de82cd80d9ce5967f6e00
>
>
>
>
>
> Sentry's KEYS containing the PGP key we used to sign the release:
>
> http://www.apache.org/dist/incubator/sentry/KEYS
>
>
>
>
>
> Note that this is a source only release and we are voting on the source:
>
> tag=release-1.6.0-rc0, SHA=3c122b76483531db5f0de82cd80d9ce5967f6e00
>
> A vote on releasing this package has already passed in Apache Sentry
> PPMC[1] including +1 votes from our PPMC (Sravya Tirukkovalur, Lenni Kuff,
> Prasad Mujumdar, Anne Yu).
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Regards
> Dapeng
>
>
> [1] -
> http://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20vote%20release%20order%3Adate-backward+page:1+mid:5rp3ibtacb3xjryk+state:results
>
>


-- 
Sravya Tirukkovalur

Re: [VOTE] TinkerPop 3.0.1-incubating Release

[Justin Mclean]

Hi,

> I suppose I still could have missed something, but I thought i'd gotten the 
> bulk of it right - could you please
> tell me what you noticed that I missed or misunderstood from your last
> post? 

Only things in the release need to be in LICENSE or NOTICE [1]. I’d check that 
first. Permissive licensed software (i.e. MIT/BSD) don't need to go in NOTICE 
[5], I can see there a few of those there.

> Does that simply mean that I should remove all apache licensed dependencies
> from the binary NOTICE and all is good?

Generally when adding Apache licenced software there's no need to modify 
LICENSE or NOTICE unless it has a NOTICE file [2]. That means you generally 
don’t have to add much when bundling other ASF projects especially when they 
have a boilerplate NOTICE file. [3] The no need to add Apache licensed software 
to LICENSE but it not an licensing error to do so. I generally don’t mind that 
as it makes checking releases a little easier when reviewing.

Not that dependancies of dependancies matter [4]. Rather than go down that 
rabbit hole just look inside all the jars in the release with something like 
this:
find . -name "*.jar" -exec tar ft {} \; | sort -u > paths.txt

Look at all of the classes contained to see what’s included. For example with 
TinkerPop I see that it includes "com/carrotsearch/hppc” and looking at its 
license (Apache) I can see it has a NOTICE file (which looks incorrect but 
that’s another story), so that would need to be considered and possibly 
something added to TinkerPop’s NOTICE. In this case I’d probably assume a 
standard NOTICE and add a copyright line to the NOTICE file - but that’s not 
the only valid solution. It's may not be always clear cut what needs to be done 
and you may have to consider each on a case by case basis.

If any questions come up ask you mentors, ask this list or on legal discuss.

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
2.. http://www.apache.org/dev/licensing-howto.html#alv2-dep
3. http://www.apache.org/dev/licensing-howto.html#bundle-asf-product
4. http://www.apache.org/dev/licensing-howto.html#deps-of-deps
5. http://www.apache.org/dev/licensing-howto.html#permissive-deps
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Should Apache VOTEs be in a first-come, first-serve queue?

[Rob Vesse]

Various comments inline:

On 15/09/2015 03:41, "Marko Rodriguez"  wrote:

>Hi,
>
>> Thanks for making a clear statement because it lets me focus on the
>> question that may be central to this discussion: can you tell us why
>> did you guys decided to join ASF in the first place? This is not a
>>baited
>> question: I'm genuinely curious about what kind of expectations did
>> you have when joining and what did you want to achieve?
>> 
>> Because, you see, a project that's part of the foundation can't simply
>> be just 'using' the foundation, it actually has to become part of the
>> foundation, in my mind.
>
>For me personally, I wanted TinkerPop to be apart of Apache because no
>one has won a lawsuit against Apache and I wanted that protecting me and
>my code as an open source software developer.
>---

Well AFAIK no-one has actually gone so far as to prosecute a lawsuit
against Apache so this may have been a poor motivator

I'll assume that what you actually meant that you wanted the legal
protection of the foundation (or more specifically if memory serves some
of your larger corporate users wanted this and pointed you towards the ASF)

>
>
>>> I don't expect the users of TinkerPop to have to write my code, they
>>>are
>>> there to use it.
>> 
>> Well, that a bit black-n-white. Certainly folks who don't want to write
>> TinkerPop code can't be forcefully compelled to do so. Yet, somehow,
>> the way you phrased it makes me suspect that you see it as a firewall
>> between the two communities of users vs. developers. Am I reading
>> this wrong?
>
>99.% of people using TinkerPop are not submitting bug reports,
>pull requests, ideas, community "votes" on directions, @Deprecation
>decisions, etc. I do not have any fantasies that these people should
>participate in a bi-directional engagement with TinkerPop. Why should
>they, they are using the software to solve their particular problems and
>could care less about the "TinkerPop community" as long as those releases
>(bug fixes/optimizations/features) keep coming.

The community is not defined purely as those who actively participate in
what you might call development activities.  It is also the people who ask
questions on your user list, StackOverflow etc, the people who build other
projects on top of your project and create an ecosystem, evangelists who
talk about Tinkerpop or the cool stuff they've done with it at meet-ups,
conferences etc.  Many of these people will never write a drop of code for
Tinkerpop itself but it doesn't stop them being part of your community.
Whether they care about the wider community is also irrelevant, if they
participate in the ecosystem they are part of your community which the
Tinkerpop PMC exists to promote and serve.

IMO If you are defining community as only developers then you've kinda
missed the point of community

>---
>
>
>> 
>>> If I'm not delivering software in a timely manner,
>> 
>> *you* (as in Marko Rodriguez) are not delivering software. Your entire
>> development community does. It is a subtle but important distinction
>> that goes to heart of the Apache Governance model: we don't allow
>> BDFLs. Anyone who's part of your community can propose a release
>> at any time.
>
>No, I deliver software. Likewise, other committers on TinkerPop are
>delivering software. Every piece of code written TinkerPop is not an
>exercise in pair programming. Its "I'm going to knock X, Y, Z out… give
>me 24 hours before touching that module on master/." To which people
>typically reply: "Sweet. Good luck and thanks for taking the reigns on
>that one." So, I go about delivering -- and I do it on time, documented,
>and tested. Why, cause I wear the TinkerPop hat and if I'm say I'm
>TinkerPop, guess what --- you are going to witness me Tinker that Pop.
>There is no "Marko, you said would work on that…can you please get it
>done? Please… Comon… At least respond to my emails."  And I don't use the
>"I volunteer" excuse as a way of getting out of having to do things I
>implicitly promise to do. If I wear that hat, I do the job the hat
>entails. And guess what, I'm not "busy" either.

Implying that other people are not busy is not helpful and is simply
insulting other volunteers time.  You are fortunate enough to get paid by
your employer to work pretty much full time on Tinkerpop judging by your
activity on the project.  Most people here (including myself) have day
jobs where contributing to Apache projects is only a tiny part of their
paid time (if they get any at all)

If all you are doing is writing code then you aren't building a
sustainable community, believe me I've spent years delivering code only to
result in completely non-viable communities.  There is a reason that the
Apache matra is "community over code".  In projects I participate in most
of the PMC don't actively write code and spend far more time guiding the
community and 

Re: Should Apache VOTEs be in a first-come, first-serve queue?

[Justin Mclean]

Hi,

> Implying that other people are not busy is not helpful and is simply
> insulting other volunteers time.  You are fortunate enough to get paid by
> your employer to work pretty much full time on Tinkerpop judging by your
> activity on the project.  Most people here (including myself) have day
> jobs where contributing to Apache projects is only a tiny part of their
> paid time (if they get any at all)

And many (like me) are not paid to work on Apache projects and can’t do so 
during normal working hours, but hopefully someday for me that will change :-)

Thanks,
Justin

Re: Should Apache VOTEs be in a first-come, first-serve queue?

[Bertrand Delacretaz]

On Mon, Sep 14, 2015 at 6:26 PM, Marko Rodriguez  wrote:
> ...the project committee is left "hoping" that someone will care --- pinging 
> around
> to their mentors (no reply)...

This is your actual problem - a podling needs active mentors to operate.

-Bertrand

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

Re: [VOTE] Graduate Calcite from the Apache Incubator

[Alan Gates]

+1.

Alan.


Julian Hyde 
September 14, 2015 at 18:56
This is a vote for Calcite to become a top-level project.

Since joining the Incubator in May, 2014, the Calcite
community has:
* Produced eight IPMC-approved releases under two release
managers;
* Added five new committers and one new PPMC member;
* Collaborated successfully with several other Apache
projects (Drill, Hive, Kylin, Phoenix, Samza);
* Grown into an active community (typical monthly activity
is 100 emails, 30 commits and 20 issues fixed);
* Conducted a successful community vote to graduate with
20 +1 votes, of which 2 were from our mentors, 12 were
from committers, and 6 were from IPMC members.

Further information: the discussion on the dev list [1],
vote thread [2] and result [3]. Also relevant are the
incubation status page [4] and a thread on this list
requesting review of whether Calcite met the criteria to
graduate [5].

Below is our proposed resolution for the Board.

Please vote:

[ ] +1 Graduate Apache Calcite as a top-level project
[ ] +0
[ ] -1 Do not graduate Apache Calcite because…

Here is my vote:
+1 (binding)

Voting will last 72 hours, ending at 19:00 Pacific on
September 17th.

Julian Hyde, on behalf of Calcite PPMC

[1] http://s.apache.org/ZPC
[2] http://s.apache.org/rvB
[3] http://s.apache.org/sv
[4] http://incubator.apache.org/projects/calcite.html
[5] http://s.apache.org/itP

- - - 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 parsing and planning queries on data in a wide
variety of formats; 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 
* Aman Sinha 
* Ashutosh Chauhan 
* James R. Taylor 
* Jacques Nadeau 
* Jesús Camacho Rodríguez 
* Jinfeng Ni 
* John Pullokkaran 
* Julian Hyde 
* Nick Dimiduk 
* Steven Noels 
* Ted Dunning 
* Vladimir Sitnikov 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.

- - - end - - -


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

Re: [VOTE] Graduate Calcite from the Apache Incubator

[Ted Dunning]

+1 (binding)

Sent from my iPhone

> On Sep 14, 2015, at 22:56, Balaji Ganesan  wrote:
> 
> +1
> 
> On Mon, Sep 14, 2015 at 8:47 PM, Chris Nauroth 
> wrote:
> 
>> +1 (binding)
>> 
>> --Chris Nauroth
>> 
>> 
>> 
>> 
>>> On 9/14/15, 6:56 PM, "Julian Hyde"  wrote:
>>> 
>>> This is a vote for Calcite to become a top-level project.
>>> 
>>> Since joining the Incubator in May, 2014, the Calcite
>>> community has:
>>> * Produced eight IPMC-approved releases under two release
>>> managers;
>>> * Added five new committers and one new PPMC member;
>>> * Collaborated successfully with several other Apache
>>> projects (Drill, Hive, Kylin, Phoenix, Samza);
>>> * Grown into an active community (typical monthly activity
>>> is 100 emails, 30 commits and 20 issues fixed);
>>> * Conducted a successful community vote to graduate with
>>> 20 +1 votes, of which 2 were from our mentors, 12 were
>>> from committers, and 6 were from IPMC members.
>>> 
>>> Further information: the discussion on the dev list [1],
>>> vote thread [2] and result [3]. Also relevant are the
>>> incubation status page [4] and a thread on this list
>>> requesting review of whether Calcite met the criteria to
>>> graduate [5].
>>> 
>>> Below is our proposed resolution for the Board.
>>> 
>>> Please vote:
>>> 
>>> [ ] +1 Graduate Apache Calcite as a top-level project
>>> [ ] +0
>>> [ ] -1 Do not graduate Apache Calcite becauseŠ
>>> 
>>> Here is my vote:
>>> +1 (binding)
>>> 
>>> Voting will last 72 hours, ending at 19:00 Pacific on
>>> September 17th.
>>> 
>>> Julian Hyde, on behalf of Calcite PPMC
>>> 
>>> [1] http://s.apache.org/ZPC
>>> [2] http://s.apache.org/rvB
>>> [3] http://s.apache.org/sv
>>> [4] http://incubator.apache.org/projects/calcite.html
>>> [5] http://s.apache.org/itP
>>> 
>>> - - - 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 parsing and planning queries on data in a wide
>>> variety of formats; 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 
>>> * Aman Sinha 
>>> * Ashutosh Chauhan 
>>> * James R. Taylor 
>>> * Jacques Nadeau 
>>> * Jesús Camacho Rodríguez 
>>> * Jinfeng Ni 
>>> * John Pullokkaran 
>>> * Julian Hyde 
>>> * Nick Dimiduk 
>>> * Steven Noels 
>>> * Ted Dunning 
>>> * Vladimir Sitnikov 
>>> 
>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.
>>> 
>>> - - - end - - -
>>> 
>>> 
>>> -
>>> 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
>> 
>> 

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

Re: Looking for a Champion for ORDs

[Mattmann, Chris A (3980)]

Dear Kris, please feel free to post the full proposal to the
Incubator wiki, here:
http://wiki.apache.org/incubator/, e.g., at:
http://wiki.apache.org/incubator/ORDSProposal


You will need permissions to do so, so let someone on this list
know when you register for your wiki account.

Sounds very interesting.

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++





-Original Message-
From: Kris Popat 
Reply-To: "general@incubator.apache.org" 
Date: Tuesday, September 15, 2015 at 6:08 AM
To: "general@incubator.apache.org" 
Subject: Looking for a Champion for ORDs

>Hello All,
>
>A while back I started a brief discussion about inclubating ORDS (Oxford
>Research Database System). However, we had a pause in this process over
>the summer whilst some potential IP issues were sorted out, these have
>been resolved. 
>
>I would like to start looking for a Champion for the project again.
>
>Here is the first section of the proposal which has some adjustments from
>the previous post.
>
>--
>ORDS is a user and project centered, web-based  database-as-a-service
>(DbaaS) system with data publishing.
>
>ORDS imports data from recognized sources such as csv files,
>spreadsheets, and relational database files into structured online
>databases to provide DbaaS functionality. The databases are stored in an
>RDBMS (PostgreSQL with ORM access). It has a full set of high-level tools
>for managing and editing these databases, including tools that give users
>the ability to create versioned snapshots of data and share specific
>datasets. New databases can also be created using these tools.  Databases
>are housed in projects and associated with users with given roles. The
>data can be exported in common formats.
>-
>
>We believe strongly that the ASF would be good place for this project to
>grow because of it’s tradition of upholding good open source practice.
>
>In brief it is in use by researchers at Oxford and there is a lot of
>interest in the sector for using it in other institutions.  Promotion of
>the system is already happening and this should give us a route for
>getting users, documenters, testers and developers involved.
>It is written in Java and uses Tomcat, PostgreSQL though the database can
>be switched as we use JPA for all db access.
>
>I have worked on the full proposal and can post it on this list if
>required or will put it on the wiki as and when is appropriate.  I just
>didn’t want to clog this email with a whole proposal at this stage.
>
>Please let me know if you are interested in Championing this project or
>know of any member who might be.
>
>Many thanks
>
>Kris Popat
>
>———
>Developer | Consultant Researcher
>
>
>
>
>-
>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

[RESULT] [VOTE] Accept MADlib into the Apache Incubator

[Roman Shaposhnik]

On Wed, Sep 9, 2015 at 7:37 PM, Roman Shaposhnik  wrote:
> Following the discussion earlier:
>http://s.apache.org/TE6
>
> I would like to call a VOTE for accepting
> MADlib community as a new ASF incubator
> project.
>
> The proposal is available at:
> https://wiki.apache.org/incubator/MADlibProposal
> and is also included at the bottom of this email.
>
> Vote is open until at least Mon, 14 September 2015, 23:59:00 PST
>
>  [ ] +1 accept MADlib into the Apache Incubator
>  [ ] ±0
>  [ ] -1 because...

This vote is now closed and passes with 4 binding +1 votes,
15 non-binding +1 votes and no 0 or -1 votes.

Thanks to all who helped with the proposal and cast the vote!

Here's a vote tally:

Non-binding +1s:
  Atri Sharma
  Christian Tzolov
  Rahul Iyer
  Caleb Welton
  Frank McQuillan
  Srivatsan Ramanujam
  Chris Rawles
  Gregory Chase
  Gautam Muralidhar
  Don Bosco Durai
  dpop...@uvic.ca
  Kee Siong Ng
  Sarah Aerni
  Michael West
  AJ Welch

Binding +1s:
   Konstantin Boudnik
   Roman Shaposhnik
   Julian Hyde
   Ted Dunning

Thanks,
Roman.

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

Re: [VOTE] Accept Rya into the Apache Incubator

[Josh Elser]

+1

Adam Fuchs wrote:

Thanks again for the healthy discussion on Rya. With that, I would like to
call a VOTE for accepting Rya as a new incubator project.

The proposal text is included below, and is posted on the wiki here:
https://wiki.apache.org/incubator/RyaProposal

The discussion thread on Rya starts here:
http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3CCALt5_xJKtRcUr3WGjfrY77DYWF0-8DWi%3DzyS7hrMFTg%2BYAORjQ%40mail.gmail.com%3E

The vote will be open until Thu Sep 17 15:15:00 UTC 2015.

[ ] +1 accept Rya in the Incubator
[ ] ±0
[ ] -1 because...

Thanks,
Adam


= Rya Proposal =
== Abstract ==
Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
supports SPARQL queries.

== Proposal ==
Rya is a scalable RDF data management system built on top of Accumulo. Rya
uses novel storage methods, indexing schemes, and query processing
techniques that scale to billions of triples across multiple nodes. Rya
provides fast and easy access to the data through SPARQL, a conventional
query mechanism for RDF data.

== Background ==
RDF is a World Wide Web Consortium (W3C) standard used in describing
resources on the Web. The smallest data unit is a triple consisting of
subject, predicate, and object. Using this framework, it is very easy to
describe any resource, not just Web related. For example, if you want to
say that Alice is a professor, you can represent this as an RDF triple like
(Alice, rdf:type, Professor). In general, RDF is an open world framework
that allows anyone to make any statement about any resource, which makes it
  a popular choice for expressing a large variety of data.

RDF is used in conjunction with the Web Ontology Language (OWL). OWL is a
framework for describing models or ontologies for RDF. It defines concepts,
relationships, and/or structure of RDF documents. These models can be used
to 'reason/infer' information about entities within a given domain. For
example, you can express that a Professor is a sub class of Faculty,
(Professor, rdfs:subClassOf, Faculty) and knowing that (Alice, rdf:type,
Professor), it can be inferred that (Alice, rdf:type, Faculty).

SPARQL is an RDF query language. Similar with SQL, SPARQL has SELECT and
WHERE clauses; however, it is based on querying and retrieving RDF triples.

Work on Rya, a large scale distributed system for  storing and querying RDF
data, started in 2010.

== Rationale ==
With the increase in data size, there is a need for scalable systems for
storing and retrieving RDF data in a cluster of nodes. We believe that Rya
can fulfill that role. We expect that communities within government, health
care, finance, and others who generate large amounts of RDF data will be
most interested in this project.

 From its inception, the project operated with an Apache-style license, but
it was open to mostly US government-related projects only. We believe that
having the project and the development open for all will benefit both the
project and the interested communities.

== Current Status ==
The project source code and documentation are currently hosted in a private
repository on Github. New users are added to the repository upon request.

=== Meritocracy ===
Meritocracy is the model that we currently follow, and we want to build a
larger and more diverse developer community by becoming an Apache project.

=== Community ===
Rya has being building a community of users and developers for the past 3
years. There is currently an active workgroup with monthly meetings and the
number of participants in the meeting is increasing.

=== Core Developers ===
The core developers are a diverse group of people who are either government
employees or former / current government contractors from different
companies.

=== Alignment ===
Rya is built on top of Accumulo, an Apache project.

== Known Risks ==
=== Orphaned Products ===
There is a very small risk of becoming orphaned. The current contributors
are strongly committed to the project, there is a large enough number of
developers interested in contributing to the project, and we believe that
the support for the project will continue to grow from the interested
communities.

=== Inexperience with Open Source ===
The initial committers have various degrees of experience with open source
projects - from very new to experienced. This project was open source
within government from the beginning. We are aware that it will be
different and more difficult functioning in a real open source environment.
We are enthusiastic and committed to learning the Apache way and being
successful in operating under Apache's development process.

=== Homogenous Developers ===
The current list of developers form a heterogeneous group, with people for
academia, government, and industry, collaborating from distributed
geographic locations. We aim to expand the list of contributors with the
help of the Apache incubation process.

=== Reliance on Salaried Developers ===
Many but not all of the 

Re: [VOTE] Accept Rya into the Apache Incubator

[Chris Nauroth]

+1 (binding)

--Chris Nauroth




On 9/14/15, 8:17 AM, "Adam Fuchs"  wrote:

>Thanks again for the healthy discussion on Rya. With that, I would like to
>call a VOTE for accepting Rya as a new incubator project.
>
>The proposal text is included below, and is posted on the wiki here:
>https://wiki.apache.org/incubator/RyaProposal
>
>The discussion thread on Rya starts here:
>http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C
>CALt5_xJKtRcUr3WGjfrY77DYWF0-8DWi%3DzyS7hrMFTg%2BYAORjQ%40mail.gmail.com%3
>E
>
>The vote will be open until Thu Sep 17 15:15:00 UTC 2015.
>
>[ ] +1 accept Rya in the Incubator
>[ ] ±0
>[ ] -1 because...
>
>Thanks,
>Adam
>
>
>= Rya Proposal =
>== Abstract ==
>Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
>supports SPARQL queries.
>
>== Proposal ==
>Rya is a scalable RDF data management system built on top of Accumulo. Rya
>uses novel storage methods, indexing schemes, and query processing
>techniques that scale to billions of triples across multiple nodes. Rya
>provides fast and easy access to the data through SPARQL, a conventional
>query mechanism for RDF data.
>
>== Background ==
>RDF is a World Wide Web Consortium (W3C) standard used in describing
>resources on the Web. The smallest data unit is a triple consisting of
>subject, predicate, and object. Using this framework, it is very easy to
>describe any resource, not just Web related. For example, if you want to
>say that Alice is a professor, you can represent this as an RDF triple
>like
>(Alice, rdf:type, Professor). In general, RDF is an open world framework
>that allows anyone to make any statement about any resource, which makes
>it
> a popular choice for expressing a large variety of data.
>
>RDF is used in conjunction with the Web Ontology Language (OWL). OWL is a
>framework for describing models or ontologies for RDF. It defines
>concepts,
>relationships, and/or structure of RDF documents. These models can be used
>to 'reason/infer' information about entities within a given domain. For
>example, you can express that a Professor is a sub class of Faculty,
>(Professor, rdfs:subClassOf, Faculty) and knowing that (Alice, rdf:type,
>Professor), it can be inferred that (Alice, rdf:type, Faculty).
>
>SPARQL is an RDF query language. Similar with SQL, SPARQL has SELECT and
>WHERE clauses; however, it is based on querying and retrieving RDF
>triples.
>
>Work on Rya, a large scale distributed system for  storing and querying
>RDF
>data, started in 2010.
>
>== Rationale ==
>With the increase in data size, there is a need for scalable systems for
>storing and retrieving RDF data in a cluster of nodes. We believe that Rya
>can fulfill that role. We expect that communities within government,
>health
>care, finance, and others who generate large amounts of RDF data will be
>most interested in this project.
>
>From its inception, the project operated with an Apache-style license, but
>it was open to mostly US government-related projects only. We believe that
>having the project and the development open for all will benefit both the
>project and the interested communities.
>
>== Current Status ==
>The project source code and documentation are currently hosted in a
>private
>repository on Github. New users are added to the repository upon request.
>
>=== Meritocracy ===
>Meritocracy is the model that we currently follow, and we want to build a
>larger and more diverse developer community by becoming an Apache project.
>
>=== Community ===
>Rya has being building a community of users and developers for the past 3
>years. There is currently an active workgroup with monthly meetings and
>the
>number of participants in the meeting is increasing.
>
>=== Core Developers ===
>The core developers are a diverse group of people who are either
>government
>employees or former / current government contractors from different
>companies.
>
>=== Alignment ===
>Rya is built on top of Accumulo, an Apache project.
>
>== Known Risks ==
>=== Orphaned Products ===
>There is a very small risk of becoming orphaned. The current contributors
>are strongly committed to the project, there is a large enough number of
>developers interested in contributing to the project, and we believe that
>the support for the project will continue to grow from the interested
>communities.
>
>=== Inexperience with Open Source ===
>The initial committers have various degrees of experience with open source
>projects - from very new to experienced. This project was open source
>within government from the beginning. We are aware that it will be
>different and more difficult functioning in a real open source
>environment.
>We are enthusiastic and committed to learning the Apache way and being
>successful in operating under Apache's development process.
>
>=== Homogenous Developers ===
>The current list of developers form a heterogeneous group, with people for
>academia, government, and industry, collaborating from 

Wiki Access for project proposal

[Kris Popat]

Hi,

Can someone give me write access to the wiki so I can put up the ORDs project 
proposal.

I’ve registered an account and my username is krispopat

Thanks

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

[IP CLEARANCE] Apache POI - Visio XDGF

[Nick Burch]

Hi All

We think we've now done everything for the IP Clearance of the Visio XDGF 
contribution to Apache POI. The completed template can be found at:

http://incubator.apache.org/ip-clearance/poi-visio.html

Please do let us know if we've missed anything / done anything wrong! 
Otherwise, we'll start the count for the 72 hour timer for a lazy 
consensus from now.


Thanks
Nick

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

Wiki Access for Project Proposal

[Kris Popat]

Hi,

Can someone give me write access to the wiki so I can put up the ORDs project 
proposal please?

I’ve registered an account and my username is krispopat

Thanks

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

Re: Should Apache VOTEs be in a first-come, first-serve queue?

[Marvin Humphrey]

That was a tour de force, Rob.  Very well said.  I'm glad that
contributors from other podlings seem to be reading along.

On Tue, Sep 15, 2015 at 2:17 AM, Rob Vesse  wrote:

> On 15/09/2015 03:41, "Marko Rodriguez"  wrote:

>>I did my part for TinkerPop today. Again, I don't care about
>>social/software infrastructure -- *yawn*. I'm tired from battle and must
>>rest up for the next release -- sharpen my weapons and strengthen my
>>armor. Freedom from Incubation!
>
> If this thread genuinely reflects your attitude to the ASF then I expect
> you may find yourself in for a somewhat contentious graduation vote.

There are surely other people who get by within Apache with a more
transactional attitude, but they generally keep their heads down and
you only notice when their spittle flies at Infra or something like
that.  It's unusual to be confronted so forthrightly.

And what's especially striking is that if the predictability of
incubating release votes were really the problem, a solution exists
and was given upthread. Why not just say "thanks, we'll do that next
time -- the extra work is no problem" or "thanks but it might be
overkill since pinging worked" and move on?  Why instead plant a flag
in the ground asserting a "social contract" which is inappropriately
narrow for a volunteer-driven Apache project?

With expectations having been set, to what extent should the
Foundation anticipate an ongoing dispute over that "social contract"
after TinkerPop graduates?  Are the emails on this thread
representative of the wider TinkerPop community?  If not, are there
others within that community who have sufficient political capital to
speak out in contradiction of a strong core developer and assert
control of their project?

Marvin Humphrey

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

RE: Should Apache VOTEs be in a first-come, first-serve queue?

[Ross Gardler]

+1 and given further comments from Tinkerpop community representatives I would 
say the mentors need to step up and explain what Apache is all about.

Ross

-Original Message-
From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] 
Sent: Tuesday, September 15, 2015 8:49 AM
To: Incubator General 
Subject: Re: Should Apache VOTEs be in a first-come, first-serve queue?

On Mon, Sep 14, 2015 at 6:26 PM, Marko Rodriguez  wrote:
> ...the project committee is left "hoping" that someone will care --- 
> pinging around to their mentors (no reply)...

This is your actual problem - a podling needs active mentors to operate.

-Bertrand

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

RE: Should Apache VOTEs be in a first-come, first-serve queue?

[Ross Gardler]

If you want the legal protection of the foundation then you need to learn to 
respect and understand why we work the way we do. That's what gives you legal 
protection.

Voting +1 on a release is an indication that best effort due diligence has been 
conducted on the release. It takes time and effort. I hope everyone who ever 
votes +1 on any release does so after doing the required IP audit.

Anything less is doing you and Tinkerpop a disservice despite your lack of 
respect for the community approach to developing software that we advocate 
alongside strong IP management policies.

Ross

-Original Message-
From: Marko Rodriguez [mailto:okramma...@gmail.com] 
Sent: Monday, September 14, 2015 7:41 PM
To: general@incubator.apache.org
Subject: Re: Should Apache VOTEs be in a first-come, first-serve queue?

Hi,

> Thanks for making a clear statement because it lets me focus on the 
> question that may be central to this discussion: can you tell us why 
> did you guys decided to join ASF in the first place? This is not a 
> baited
> question: I'm genuinely curious about what kind of expectations did 
> you have when joining and what did you want to achieve?
> 
> Because, you see, a project that's part of the foundation can't simply 
> be just 'using' the foundation, it actually has to become part of the 
> foundation, in my mind.

For me personally, I wanted TinkerPop to be apart of Apache because no one has 
won a lawsuit against Apache and I wanted that protecting me and my code as an 
open source software developer.
---


>> I don't expect the users of TinkerPop to have to write my code, they 
>> are there to use it.
> 
> Well, that a bit black-n-white. Certainly folks who don't want to 
> write TinkerPop code can't be forcefully compelled to do so. Yet, 
> somehow, the way you phrased it makes me suspect that you see it as a 
> firewall between the two communities of users vs. developers. Am I 
> reading this wrong?

99.% of people using TinkerPop are not submitting bug reports, pull 
requests, ideas, community "votes" on directions, @Deprecation decisions, etc. 
I do not have any fantasies that these people should participate in a 
bi-directional engagement with TinkerPop. Why should they, they are using the 
software to solve their particular problems and could care less about the 
"TinkerPop community" as long as those releases (bug 
fixes/optimizations/features) keep coming.
---


> 
>> If I'm not delivering software in a timely manner,
> 
> *you* (as in Marko Rodriguez) are not delivering software. Your entire 
> development community does. It is a subtle but important distinction 
> that goes to heart of the Apache Governance model: we don't allow 
> BDFLs. Anyone who's part of your community can propose a release at 
> any time.

No, I deliver software. Likewise, other committers on TinkerPop are delivering 
software. Every piece of code written TinkerPop is not an exercise in pair 
programming. Its "I'm going to knock X, Y, Z out... give me 24 hours before 
touching that module on master/." To which people typically reply: "Sweet. Good 
luck and thanks for taking the reigns on that one." So, I go about delivering 
-- and I do it on time, documented, and tested. Why, cause I wear the TinkerPop 
hat and if I'm say I'm TinkerPop, guess what --- you are going to witness me 
Tinker that Pop. There is no "Marko, you said would work on that...can you 
please get it done? Please... Comon... At least respond to my emails."  And 
I don't use the "I volunteer" excuse as a way of getting out of having to do 
things I implicitly promise to do. If I wear that hat, I do the job the hat 
entails. And guess what, I'm not "busy" either.

---

>> Likewise for Apache Incubation (though perhaps I'm naive in my 
>> assumptions) -- if you are a mentor, move the artifacts through in a 
>> timely manner and don't wait for the project leaders to ping "Hey, can we 
>> get a VOTE?...please...pretty pleasehello?"
> 
> That's a very legitimate point. As Ross mentioned a couple of times if 
> there's one actionable AI from this thread this would be feedback to your 
> mentors.
> Your mentors are your first line of defense on things like release VOTES.
> That said, they are not the only line of defense. Any IPMC member can 
> vote on your release. But the trick is -- you've got to incentivize 
> them somehow.
> And no -- $20 won't cut it and is morally wrong. What will cut it is 
> paying it forward perhaps along the lines that Marvin suggested.

Through my emails here, TinkerPop got the VOTE so my incentivizing-technique 
worked --- troll the list and get people fired up. I suspect a few people 
giggled and thought: "Ha. That guy is funny if anything. -- +1 binding." To the 
quiet gigglers out there, curtsy bow. And unfortunately, if our next release 
doesn't get VOTEs in a timely manner, another 

Re: [DISCUSS] Unomi incubation proposal

[Jean-Baptiste Onofré]

Hi Serge,

what's your username on the wiki ?

Thanks,
Regards
JB

On 09/14/2015 11:45 AM, Serge Huber wrote:

I don’t have write access to the wiki, would you mind making that change ?

cheers,
   Serge…


On 14 sept. 2015, at 11:28, Bertrand Delacretaz  wrote:

Hi,

The proposal at https://wiki.apache.org/incubator/UnomiProposal
requests a u...@unomi.incubator.apache.org, does Unomi really need
that?

My preference is to start with just a dev list, and only split if this
becomes too busy.

-Bertrand

-
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



--
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] Unomi incubation proposal

[Serge Huber]

Actually Bertrand already did it thanks !

Cheers,
  Serge

> Le 15 sept. 2015 à 21:25, Jean-Baptiste Onofré  a écrit :
> 
> Hi Serge,
> 
> what's your username on the wiki ?
> 
> Thanks,
> Regards
> JB
> 
>> On 09/14/2015 11:45 AM, Serge Huber wrote:
>> I don’t have write access to the wiki, would you mind making that change ?
>> 
>> cheers,
>>   Serge…
>> 
>>> On 14 sept. 2015, at 11:28, Bertrand Delacretaz  
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> The proposal at https://wiki.apache.org/incubator/UnomiProposal
>>> requests a u...@unomi.incubator.apache.org, does Unomi really need
>>> that?
>>> 
>>> My preference is to start with just a dev list, and only split if this
>>> becomes too busy.
>>> 
>>> -Bertrand
>>> 
>>> -
>>> 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
> 
> -- 
> 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

[RESULT][VOTE] TinkerPop 3.0.1-incubating Release

[Stephen Mallette]

The vote for releasing Apache TinkerPop passed with 3 binding +1s, 0
non-binding +1s, and no 0 or -1.

Binding +1s:
Daniel Gruno
Justin Mclean
Rich Bowen

Thanks to those who gave us a hand and added a vote.

Separately, Justin, I'll try to get LICENSE/NOTICE right for the next run.
I suspect I'll be pinging this list separately for a bit more guidance
before then.  Thanks.

Stephen

On Tue, Sep 15, 2015 at 5:39 AM, Justin Mclean 
wrote:

> Hi,
>
> > I suppose I still could have missed something, but I thought i'd gotten
> the bulk of it right - could you please
> > tell me what you noticed that I missed or misunderstood from your last
> > post?
>
> Only things in the release need to be in LICENSE or NOTICE [1]. I’d check
> that first. Permissive licensed software (i.e. MIT/BSD) don't need to go in
> NOTICE [5], I can see there a few of those there.
>
> > Does that simply mean that I should remove all apache licensed
> dependencies
> > from the binary NOTICE and all is good?
>
> Generally when adding Apache licenced software there's no need to modify
> LICENSE or NOTICE unless it has a NOTICE file [2]. That means you generally
> don’t have to add much when bundling other ASF projects especially when
> they have a boilerplate NOTICE file. [3] The no need to add Apache licensed
> software to LICENSE but it not an licensing error to do so. I generally
> don’t mind that as it makes checking releases a little easier when
> reviewing.
>
> Not that dependancies of dependancies matter [4]. Rather than go down that
> rabbit hole just look inside all the jars in the release with something
> like this:
> find . -name "*.jar" -exec tar ft {} \; | sort -u > paths.txt
>
> Look at all of the classes contained to see what’s included. For example
> with TinkerPop I see that it includes "com/carrotsearch/hppc” and looking
> at its license (Apache) I can see it has a NOTICE file (which looks
> incorrect but that’s another story), so that would need to be considered
> and possibly something added to TinkerPop’s NOTICE. In this case I’d
> probably assume a standard NOTICE and add a copyright line to the NOTICE
> file - but that’s not the only valid solution. It's may not be always clear
> cut what needs to be done and you may have to consider each on a case by
> case basis.
>
> If any questions come up ask you mentors, ask this list or on legal
> discuss.
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> 2.. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> 3. http://www.apache.org/dev/licensing-howto.html#bundle-asf-product
> 4. http://www.apache.org/dev/licensing-howto.html#deps-of-deps
> 5. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Unomi incubation proposal

[Jean-Baptiste Onofré]

Ah cool, thanks. I was busy with a customer.

Regards
JB

On 09/15/2015 09:34 PM, Serge Huber wrote:

Actually Bertrand already did it thanks !

Cheers,
   Serge


Le 15 sept. 2015 à 21:25, Jean-Baptiste Onofré  a écrit :

Hi Serge,

what's your username on the wiki ?

Thanks,
Regards
JB


On 09/14/2015 11:45 AM, Serge Huber wrote:
I don’t have write access to the wiki, would you mind making that change ?

cheers,
   Serge…


On 14 sept. 2015, at 11:28, Bertrand Delacretaz  wrote:

Hi,

The proposal at https://wiki.apache.org/incubator/UnomiProposal
requests a u...@unomi.incubator.apache.org, does Unomi really need
that?

My preference is to start with just a dev list, and only split if this
becomes too busy.

-Bertrand

-
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


--
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



--
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: [RESULT][VOTE] TinkerPop 3.0.1-incubating Release

[John D. Ament]

Ideally we leave votes open for 72 hrs in case anyone has a -1 after 3 +1s
cast.
On Sep 15, 2015 15:55, "Stephen Mallette"  wrote:

> The vote for releasing Apache TinkerPop passed with 3 binding +1s, 0
> non-binding +1s, and no 0 or -1.
>
> Binding +1s:
> Daniel Gruno
> Justin Mclean
> Rich Bowen
>
> Thanks to those who gave us a hand and added a vote.
>
> Separately, Justin, I'll try to get LICENSE/NOTICE right for the next run.
> I suspect I'll be pinging this list separately for a bit more guidance
> before then.  Thanks.
>
> Stephen
>
> On Tue, Sep 15, 2015 at 5:39 AM, Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > I suppose I still could have missed something, but I thought i'd gotten
> > the bulk of it right - could you please
> > > tell me what you noticed that I missed or misunderstood from your last
> > > post?
> >
> > Only things in the release need to be in LICENSE or NOTICE [1]. I’d check
> > that first. Permissive licensed software (i.e. MIT/BSD) don't need to go
> in
> > NOTICE [5], I can see there a few of those there.
> >
> > > Does that simply mean that I should remove all apache licensed
> > dependencies
> > > from the binary NOTICE and all is good?
> >
> > Generally when adding Apache licenced software there's no need to modify
> > LICENSE or NOTICE unless it has a NOTICE file [2]. That means you
> generally
> > don’t have to add much when bundling other ASF projects especially when
> > they have a boilerplate NOTICE file. [3] The no need to add Apache
> licensed
> > software to LICENSE but it not an licensing error to do so. I generally
> > don’t mind that as it makes checking releases a little easier when
> > reviewing.
> >
> > Not that dependancies of dependancies matter [4]. Rather than go down
> that
> > rabbit hole just look inside all the jars in the release with something
> > like this:
> > find . -name "*.jar" -exec tar ft {} \; | sort -u > paths.txt
> >
> > Look at all of the classes contained to see what’s included. For example
> > with TinkerPop I see that it includes "com/carrotsearch/hppc” and looking
> > at its license (Apache) I can see it has a NOTICE file (which looks
> > incorrect but that’s another story), so that would need to be considered
> > and possibly something added to TinkerPop’s NOTICE. In this case I’d
> > probably assume a standard NOTICE and add a copyright line to the NOTICE
> > file - but that’s not the only valid solution. It's may not be always
> clear
> > cut what needs to be done and you may have to consider each on a case by
> > case basis.
> >
> > If any questions come up ask you mentors, ask this list or on legal
> > discuss.
> >
> > Thanks,
> > Justin
> >
> > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> > 2.. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> > 3. http://www.apache.org/dev/licensing-howto.html#bundle-asf-product
> > 4. http://www.apache.org/dev/licensing-howto.html#deps-of-deps
> > 5. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Graduate Calcite from the Apache Incubator

[Henry Saputra]

+1

Good job guys

On Mon, Sep 14, 2015 at 6:56 PM, Julian Hyde  wrote:
> This is a vote for Calcite to become a top-level project.
>
> Since joining the Incubator in May, 2014, the Calcite
> community has:
> * Produced eight IPMC-approved releases under two release
>   managers;
> * Added five new committers and one new PPMC member;
> * Collaborated successfully with several other Apache
> projects (Drill, Hive, Kylin, Phoenix, Samza);
> * Grown into an active community (typical monthly activity
>   is 100 emails, 30 commits and 20 issues fixed);
> * Conducted a successful community vote to graduate with
>   20 +1 votes, of which 2 were from our mentors, 12 were
>   from committers, and 6 were from IPMC members.
>
> Further information: the discussion on the dev list [1],
> vote thread [2] and result [3]. Also relevant are the
> incubation status page [4] and a thread on this list
> requesting review of whether Calcite met the criteria to
> graduate [5].
>
> Below is our proposed resolution for the Board.
>
> Please vote:
>
> [ ] +1 Graduate Apache Calcite as a top-level project
> [ ] +0
> [ ] -1 Do not graduate Apache Calcite because…
>
> Here is my vote:
> +1 (binding)
>
> Voting will last 72 hours, ending at 19:00 Pacific on
> September 17th.
>
> Julian Hyde, on behalf of Calcite PPMC
>
> [1] http://s.apache.org/ZPC
> [2] http://s.apache.org/rvB
> [3] http://s.apache.org/sv
> [4] http://incubator.apache.org/projects/calcite.html
> [5] http://s.apache.org/itP
>
> - - - 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 parsing and planning queries on data in a wide
> variety of formats; 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 
> * Aman Sinha 
> * Ashutosh Chauhan 
> * James R. Taylor 
> * Jacques Nadeau 
> * Jesús Camacho Rodríguez 
> * Jinfeng Ni 
> * John Pullokkaran 
> * Julian Hyde 
> * Nick Dimiduk 
> * Steven Noels 
> * Ted Dunning 
> * Vladimir Sitnikov 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.
>
> - - - end - - -
>
>
> -
> 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 Calcite from the Apache Incubator

[Seetharam Venkatesh]

+1.

Thanks,
Venkatesh

On Tue, Sep 15, 2015 at 2:16 PM Henry Saputra 
wrote:

> +1
>
> Good job guys
>
> On Mon, Sep 14, 2015 at 6:56 PM, Julian Hyde  wrote:
> > This is a vote for Calcite to become a top-level project.
> >
> > Since joining the Incubator in May, 2014, the Calcite
> > community has:
> > * Produced eight IPMC-approved releases under two release
> >   managers;
> > * Added five new committers and one new PPMC member;
> > * Collaborated successfully with several other Apache
> > projects (Drill, Hive, Kylin, Phoenix, Samza);
> > * Grown into an active community (typical monthly activity
> >   is 100 emails, 30 commits and 20 issues fixed);
> > * Conducted a successful community vote to graduate with
> >   20 +1 votes, of which 2 were from our mentors, 12 were
> >   from committers, and 6 were from IPMC members.
> >
> > Further information: the discussion on the dev list [1],
> > vote thread [2] and result [3]. Also relevant are the
> > incubation status page [4] and a thread on this list
> > requesting review of whether Calcite met the criteria to
> > graduate [5].
> >
> > Below is our proposed resolution for the Board.
> >
> > Please vote:
> >
> > [ ] +1 Graduate Apache Calcite as a top-level project
> > [ ] +0
> > [ ] -1 Do not graduate Apache Calcite because…
> >
> > Here is my vote:
> > +1 (binding)
> >
> > Voting will last 72 hours, ending at 19:00 Pacific on
> > September 17th.
> >
> > Julian Hyde, on behalf of Calcite PPMC
> >
> > [1] http://s.apache.org/ZPC
> > [2] http://s.apache.org/rvB
> > [3] http://s.apache.org/sv
> > [4] http://incubator.apache.org/projects/calcite.html
> > [5] http://s.apache.org/itP
> >
> > - - - 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 parsing and planning queries on data in a wide
> > variety of formats; 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 
> > * Aman Sinha 
> > * Ashutosh Chauhan 
> > * James R. Taylor 
> > * Jacques Nadeau 
> > * Jesús Camacho Rodríguez 
> > * Jinfeng Ni 
> > * John Pullokkaran 
> > * Julian Hyde 
> > * Nick Dimiduk 
> > * Steven Noels 
> > * Ted Dunning 
> > * Vladimir Sitnikov 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.
> >
> > - - - end - - -
> >
> >
> > -
> > 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: [RESULT][VOTE] TinkerPop 3.0.1-incubating Release

[Stephen Mallette]

Hi John, the vote has been open since September 8th - here's where it
started:

http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3CCAA-H438vLKoQiJ%3Dcn6CXPYOvueHrvzbBQ_LhKgmxjVkeMceAMQ%40mail.gmail.com%3E

On Tue, Sep 15, 2015 at 5:13 PM, John D. Ament 
wrote:

> Ideally we leave votes open for 72 hrs in case anyone has a -1 after 3 +1s
> cast.
> On Sep 15, 2015 15:55, "Stephen Mallette"  wrote:
>
> > The vote for releasing Apache TinkerPop passed with 3 binding +1s, 0
> > non-binding +1s, and no 0 or -1.
> >
> > Binding +1s:
> > Daniel Gruno
> > Justin Mclean
> > Rich Bowen
> >
> > Thanks to those who gave us a hand and added a vote.
> >
> > Separately, Justin, I'll try to get LICENSE/NOTICE right for the next
> run.
> > I suspect I'll be pinging this list separately for a bit more guidance
> > before then.  Thanks.
> >
> > Stephen
> >
> > On Tue, Sep 15, 2015 at 5:39 AM, Justin Mclean  >
> > wrote:
> >
> > > Hi,
> > >
> > > > I suppose I still could have missed something, but I thought i'd
> gotten
> > > the bulk of it right - could you please
> > > > tell me what you noticed that I missed or misunderstood from your
> last
> > > > post?
> > >
> > > Only things in the release need to be in LICENSE or NOTICE [1]. I’d
> check
> > > that first. Permissive licensed software (i.e. MIT/BSD) don't need to
> go
> > in
> > > NOTICE [5], I can see there a few of those there.
> > >
> > > > Does that simply mean that I should remove all apache licensed
> > > dependencies
> > > > from the binary NOTICE and all is good?
> > >
> > > Generally when adding Apache licenced software there's no need to
> modify
> > > LICENSE or NOTICE unless it has a NOTICE file [2]. That means you
> > generally
> > > don’t have to add much when bundling other ASF projects especially when
> > > they have a boilerplate NOTICE file. [3] The no need to add Apache
> > licensed
> > > software to LICENSE but it not an licensing error to do so. I generally
> > > don’t mind that as it makes checking releases a little easier when
> > > reviewing.
> > >
> > > Not that dependancies of dependancies matter [4]. Rather than go down
> > that
> > > rabbit hole just look inside all the jars in the release with something
> > > like this:
> > > find . -name "*.jar" -exec tar ft {} \; | sort -u > paths.txt
> > >
> > > Look at all of the classes contained to see what’s included. For
> example
> > > with TinkerPop I see that it includes "com/carrotsearch/hppc” and
> looking
> > > at its license (Apache) I can see it has a NOTICE file (which looks
> > > incorrect but that’s another story), so that would need to be
> considered
> > > and possibly something added to TinkerPop’s NOTICE. In this case I’d
> > > probably assume a standard NOTICE and add a copyright line to the
> NOTICE
> > > file - but that’s not the only valid solution. It's may not be always
> > clear
> > > cut what needs to be done and you may have to consider each on a case
> by
> > > case basis.
> > >
> > > If any questions come up ask you mentors, ask this list or on legal
> > > discuss.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> > > 2.. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> > > 3. http://www.apache.org/dev/licensing-howto.html#bundle-asf-product
> > > 4. http://www.apache.org/dev/licensing-howto.html#deps-of-deps
> > > 5. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [VOTE] Graduate Calcite from the Apache Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Sep 15, 2015, at 1:02 PM, Owen O'Malley  wrote:
> 
> +1 (binding)
> 
>> On Tue, Sep 15, 2015 at 9:48 AM, Ted Dunning  wrote:
>> 
>> 
>> +1 (binding)
>> 
>> Sent from my iPhone
>> 
>>> On Sep 14, 2015, at 22:56, Balaji Ganesan  wrote:
>>> 
>>> +1
>>> 
>>> On Mon, Sep 14, 2015 at 8:47 PM, Chris Nauroth >> 
>>> wrote:
>>> 
 +1 (binding)
 
 --Chris Nauroth
 
 
 
 
> On 9/14/15, 6:56 PM, "Julian Hyde"  wrote:
> 
> This is a vote for Calcite to become a top-level project.
> 
> Since joining the Incubator in May, 2014, the Calcite
> community has:
> * Produced eight IPMC-approved releases under two release
> managers;
> * Added five new committers and one new PPMC member;
> * Collaborated successfully with several other Apache
> projects (Drill, Hive, Kylin, Phoenix, Samza);
> * Grown into an active community (typical monthly activity
> is 100 emails, 30 commits and 20 issues fixed);
> * Conducted a successful community vote to graduate with
> 20 +1 votes, of which 2 were from our mentors, 12 were
> from committers, and 6 were from IPMC members.
> 
> Further information: the discussion on the dev list [1],
> vote thread [2] and result [3]. Also relevant are the
> incubation status page [4] and a thread on this list
> requesting review of whether Calcite met the criteria to
> graduate [5].
> 
> Below is our proposed resolution for the Board.
> 
> Please vote:
> 
> [ ] +1 Graduate Apache Calcite as a top-level project
> [ ] +0
> [ ] -1 Do not graduate Apache Calcite becauseŠ
> 
> Here is my vote:
> +1 (binding)
> 
> Voting will last 72 hours, ending at 19:00 Pacific on
> September 17th.
> 
> Julian Hyde, on behalf of Calcite PPMC
> 
> [1] http://s.apache.org/ZPC
> [2] http://s.apache.org/rvB
> [3] http://s.apache.org/sv
> [4] http://incubator.apache.org/projects/calcite.html
> [5] http://s.apache.org/itP
> 
> - - - 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 parsing and planning queries on data in a wide
> variety of formats; 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 
> * Aman Sinha 
> * Ashutosh Chauhan 
> * James R. Taylor 
> * Jacques Nadeau 
> * Jesús Camacho Rodríguez 
> * Jinfeng Ni 
> * John Pullokkaran 
> * Julian Hyde 
> * Nick Dimiduk 
> * Steven Noels 
> * Ted Dunning 
> * Vladimir Sitnikov 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.
> 
> - - - end - - -
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: 

Re: [VOTE] Graduate Calcite from the Apache Incubator

[John D. Ament]

+1
Good luck!

On Mon, Sep 14, 2015 at 9:54 PM Julian Hyde  wrote:

> This is a vote for Calcite to become a top-level project.
>
> Since joining the Incubator in May, 2014, the Calcite
> community has:
> * Produced eight IPMC-approved releases under two release
>   managers;
> * Added five new committers and one new PPMC member;
> * Collaborated successfully with several other Apache
> projects (Drill, Hive, Kylin, Phoenix, Samza);
> * Grown into an active community (typical monthly activity
>   is 100 emails, 30 commits and 20 issues fixed);
> * Conducted a successful community vote to graduate with
>   20 +1 votes, of which 2 were from our mentors, 12 were
>   from committers, and 6 were from IPMC members.
>
> Further information: the discussion on the dev list [1],
> vote thread [2] and result [3]. Also relevant are the
> incubation status page [4] and a thread on this list
> requesting review of whether Calcite met the criteria to
> graduate [5].
>
> Below is our proposed resolution for the Board.
>
> Please vote:
>
> [ ] +1 Graduate Apache Calcite as a top-level project
> [ ] +0
> [ ] -1 Do not graduate Apache Calcite because…
>
> Here is my vote:
> +1 (binding)
>
> Voting will last 72 hours, ending at 19:00 Pacific on
> September 17th.
>
> Julian Hyde, on behalf of Calcite PPMC
>
> [1] http://s.apache.org/ZPC
> [2] http://s.apache.org/rvB
> [3] http://s.apache.org/sv
> [4] http://incubator.apache.org/projects/calcite.html
> [5] http://s.apache.org/itP
>
> - - - 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 parsing and planning queries on data in a wide
> variety of formats; 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 
> * Aman Sinha 
> * Ashutosh Chauhan 
> * James R. Taylor 
> * Jacques Nadeau 
> * Jesús Camacho Rodríguez 
> * Jinfeng Ni 
> * John Pullokkaran 
> * Julian Hyde 
> * Nick Dimiduk 
> * Steven Noels 
> * Ted Dunning 
> * Vladimir Sitnikov 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde 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.
>
> - - - end - - -
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Looking for a Champion for ORDs

[Kris Popat]

Hello All,

A while back I started a brief discussion about inclubating ORDS (Oxford 
Research Database System). However, we had a pause in this process over the 
summer whilst some potential IP issues were sorted out, these have been 
resolved. 

I would like to start looking for a Champion for the project again. 

Here is the first section of the proposal which has some adjustments from the 
previous post.

--
ORDS is a user and project centered, web-based  database-as-a-service (DbaaS) 
system with data publishing.

ORDS imports data from recognized sources such as csv files, spreadsheets, and 
relational database files into structured online databases to provide DbaaS 
functionality. The databases are stored in an RDBMS (PostgreSQL with ORM 
access). It has a full set of high-level tools for managing and editing these 
databases, including tools that give users the ability to create versioned 
snapshots of data and share specific datasets. New databases can also be 
created using these tools.  Databases are housed in projects and associated 
with users with given roles. The data can be exported in common formats.
-

We believe strongly that the ASF would be good place for this project to grow 
because of it’s tradition of upholding good open source practice.

In brief it is in use by researchers at Oxford and there is a lot of interest 
in the sector for using it in other institutions.  Promotion of the system is 
already happening and this should give us a route for getting users, 
documenters, testers and developers involved.
It is written in Java and uses Tomcat, PostgreSQL though the database can be 
switched as we use JPA for all db access. 

I have worked on the full proposal and can post it on this list if required or 
will put it on the wiki as and when is appropriate.  I just didn’t want to clog 
this email with a whole proposal at this stage.

Please let me know if you are interested in Championing this project or know of 
any member who might be.

Many thanks

Kris Popat

———
Developer | Consultant Researcher 




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