Re: [VOTE] Release Eagle Version 0.3.0 RC3 (Incubating)

2016-03-28 Thread Zhao Qingwen 
+1 (Binding)


Best Regards,
Qingwen Zhao | 赵晴雯




2016-03-29 13:44 GMT+08:00 Henry Saputra :

> Sig file looks good
> Hash files look good
> NOTICE file exist
> LICENSE file exist
> DISCLAIMER file exist
> No 3rd party exe in source artifact
>
> +1 (binding)
>
> - Henry
>
>
>
> > > On Mar 28, 2016, at 5:05 PM, Dendukuri, Hemanth 
> > wrote:
> > >
> > > Hi all,
> > >
> > >   The Apache Eagle community has voted on and approved the proposal
> > to release "Apache Eagle 0.3.0 Release Candidate 3 (incubating)".
> > >   The voting result is available at
> > https://s.apache.org/eagle-0.3.0-result
> > >
> > >
> > >   The Source file to be voted are located here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/
> > >
> > >   Release Tag  :
> > https://github.com/apache/incubator-eagle/releases/tag/release-0.3.0-rc3
> > >
> > > The commit to be voted upon:
> >
> https://github.com/apache/incubator-eagle/commit/b1d0a87ac0df1cc881427faafc637c152c180872
> > >
> > >   Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/hdendukuri.asc
> > >
> > >   Here’s release notes:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.3.0
> > >
> > >
> > >   Note that this is a source only release and we are voting on the
> > source. The hashes of the source are as follows:
> > >
> > > apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md<
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md5
> >5
> > a211a151d7f66c2516c5e41da1345128
> > >
> > >   apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1<
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1
> >
> > da7b4e60228cf1421dde4342c957aff16de81cbd
> > >
> > >
> > >
> > >The vote is open for a minimum of 72 hours or until the
> necessary
> > number of votes (3 binding +1s) is reached.
> > >
> > >[ ] +1 Release this Eagle 0.3.0 Incubator Release Candidate 3.
> > >
> > >[ ]  0 I don't feel strongly about it, but I'm okay with the
> > release
> > >
> > >[ ] -1 Do not release this package because...
> > >
> > > Please add "(binding)" if your vote is binding.
> > >
> > >
> > > Thanks,
> > >
> > > Hemanth Dendukuri
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Eagle Version 0.3.0 RC3 (Incubating)

2016-03-28 Thread Henry Saputra 
Sig file looks good
Hash files look good
NOTICE file exist
LICENSE file exist
DISCLAIMER file exist
No 3rd party exe in source artifact

+1 (binding)

- Henry



> > On Mar 28, 2016, at 5:05 PM, Dendukuri, Hemanth 
> wrote:
> >
> > Hi all,
> >
> >   The Apache Eagle community has voted on and approved the proposal
> to release "Apache Eagle 0.3.0 Release Candidate 3 (incubating)".
> >   The voting result is available at
> https://s.apache.org/eagle-0.3.0-result
> >
> >
> >   The Source file to be voted are located here:
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/
> >
> >   Release Tag  :
> https://github.com/apache/incubator-eagle/releases/tag/release-0.3.0-rc3
> >
> > The commit to be voted upon:
> https://github.com/apache/incubator-eagle/commit/b1d0a87ac0df1cc881427faafc637c152c180872
> >
> >   Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/hdendukuri.asc
> >
> >   Here’s release notes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.3.0
> >
> >
> >   Note that this is a source only release and we are voting on the
> source. The hashes of the source are as follows:
> >
> > apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md<
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md5>5
> a211a151d7f66c2516c5e41da1345128
> >
> >   apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1<
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1>
> da7b4e60228cf1421dde4342c957aff16de81cbd
> >
> >
> >
> >The vote is open for a minimum of 72 hours or until the necessary
> number of votes (3 binding +1s) is reached.
> >
> >[ ] +1 Release this Eagle 0.3.0 Incubator Release Candidate 3.
> >
> >[ ]  0 I don't feel strongly about it, but I'm okay with the
> release
> >
> >[ ] -1 Do not release this package because...
> >
> > Please add "(binding)" if your vote is binding.
> >
> >
> > Thanks,
> >
> > Hemanth Dendukuri
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Eagle Version 0.3.0 RC3 (Incubating)

2016-03-28 Thread Hao Chen 
Forwarding my vote from dev:

+1 (binding)

- Hao

On Tue, Mar 29, 2016 at 1:23 PM, Amareshwari Sriramdasu <
amareshw...@apache.org> wrote:

> Replaying my vote from dev list :
>
> +1 (Binding)
>
> On Tue, Mar 29, 2016 at 5:35 AM, Dendukuri, Hemanth 
> wrote:
>
> > Hi all,
> >
> >The Apache Eagle community has voted on and approved the proposal
> > to release "Apache Eagle 0.3.0 Release Candidate 3 (incubating)".
> >The voting result is available at
> > https://s.apache.org/eagle-0.3.0-result
> >
> >
> >The Source file to be voted are located here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/
> >
> >Release Tag  :
> > https://github.com/apache/incubator-eagle/releases/tag/release-0.3.0-rc3
> >
> > The commit to be voted upon:
> >
> https://github.com/apache/incubator-eagle/commit/b1d0a87ac0df1cc881427faafc637c152c180872
> >
> >Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/hdendukuri.asc
> >
> >Here’s release notes:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.3.0
> >
> >
> >Note that this is a source only release and we are voting on the
> > source. The hashes of the source are as follows:
> >
> >  apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md<
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md5
> >5
> > a211a151d7f66c2516c5e41da1345128
> >
> >apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1<
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1
> >
> > da7b4e60228cf1421dde4342c957aff16de81cbd
> >
> >
> >
> > The vote is open for a minimum of 72 hours or until the necessary
> > number of votes (3 binding +1s) is reached.
> >
> > [ ] +1 Release this Eagle 0.3.0 Incubator Release Candidate 3.
> >
> > [ ]  0 I don't feel strongly about it, but I'm okay with the
> > release
> >
> > [ ] -1 Do not release this package because...
> >
> > Please add "(binding)" if your vote is binding.
> >
> >
> > Thanks,
> >
> > Hemanth Dendukuri
> >
>

Re: [VOTE] Release Eagle Version 0.3.0 RC3 (Incubating)

2016-03-28 Thread Amareshwari Sriramdasu 
Replaying my vote from dev list :

+1 (Binding)

On Tue, Mar 29, 2016 at 5:35 AM, Dendukuri, Hemanth 
wrote:

> Hi all,
>
>The Apache Eagle community has voted on and approved the proposal
> to release "Apache Eagle 0.3.0 Release Candidate 3 (incubating)".
>The voting result is available at
> https://s.apache.org/eagle-0.3.0-result
>
>
>The Source file to be voted are located here:
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/
>
>Release Tag  :
> https://github.com/apache/incubator-eagle/releases/tag/release-0.3.0-rc3
>
> The commit to be voted upon:
> https://github.com/apache/incubator-eagle/commit/b1d0a87ac0df1cc881427faafc637c152c180872
>
>Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/hdendukuri.asc
>
>Here’s release notes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.3.0
>
>
>Note that this is a source only release and we are voting on the
> source. The hashes of the source are as follows:
>
>  apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md<
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md5>5
> a211a151d7f66c2516c5e41da1345128
>
>apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1<
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1>
> da7b4e60228cf1421dde4342c957aff16de81cbd
>
>
>
> The vote is open for a minimum of 72 hours or until the necessary
> number of votes (3 binding +1s) is reached.
>
> [ ] +1 Release this Eagle 0.3.0 Incubator Release Candidate 3.
>
> [ ]  0 I don't feel strongly about it, but I'm okay with the
> release
>
> [ ] -1 Do not release this package because...
>
> Please add "(binding)" if your vote is binding.
>
>
> Thanks,
>
> Hemanth Dendukuri
>

Re: [VOTE] Graduate Apex from the Incubator

2016-03-28 Thread David Yan 
+1

Thanks,

David

On 2016-03-28 14:46, Pramod Immaneni  wrote:
> Sorry missed including the resolution. Here is the full email again..>
>
> The Apache Apex community has discussed and voted on graduation to top>
> level project.>
> The vote passed with 42  1 votes (12 from the PPMC) and no 0 or -1
votes.>
>
> Maturity Assessment:http://apex.incubator.apache.org/maturity.html>
> Discussion:https://s.apache.org/qrvY>
> Vote:https://s.apache.org/R8MR>
> Result:https://s.apache.org/sJIC>
>
> Please vote on the resolution pasted below to graduate Apache Apex>
> from the incubator to top level project.>
>
> [ ]  1 Graduate Apache Apex from the Incubator.>
> [ ]  0 Don't care.>
> [ ] -1 Don't graduate Apache Apex from the Incubator because%u2026>
>
> This vote will be open for at least 72 hours.>
>
> Many thanks to our mentors and everyone else for the support,>
>
> Pramod Immaneni, for the Apache Apex PPMC>
>
>
>
> Apache Apex top-level project resolution:>
> =>
>
> 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 Hadoop native, distributed,>
> large-scale, high throughput, low-latency, fault tolerant,>
> easily operable, unified stream and batch processing platform.>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management>
> Committee (PMC), to be known as the "Apache Apex Project",>
> be and hereby is established pursuant to Bylaws of the>
> Foundation; and be it further>
>
> RESOLVED, that the Apache Apex Project be and hereby is>
> responsible for the creation and maintenance of software>
> related to Hadoop native, distributed, large-scale,>
> high throughput, low-latency, fault tolerant, easily operable,>
> unified stream and batch processing platform;>
> and be it further>
>
> RESOLVED, that the office of "Vice President, Apache Apex" 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 Apex Project, and to have primary responsibility>
> for management of the projects within the scope of>
> responsibility of the Apache Apex 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 Apex Project:>
>
> * Ilya Ganelin >
> * P. Taylor Goetz >
> * Gaurav Gupta >
> * Pramod Immaneni >
> * Amol Kekre >
> * Justin Mclean >
> * Chetan Narsude >
> * Chris Nauroth >
> * Vlad Rozov >
> * Hitesh Shah >
> * Thomas Weise >
> * David Yan >
> * Brennon York >
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Thomas Weise>
> be appointed to the office of Vice President, Apache Apex, to>
> serve in accordance with and subject to the direction of the>
> Board of Directors and the Bylaws of the Foundation until>
> death, resignation, retirement, removal or disqualification,>
> or until a successor is appointed; and be it further>
>
> RESOLVED, that the initial Apache Apex PMC be and hereby is>
> tasked with the creation of a set of bylaws intended to>
> encourage open development and increased participation in the>
> Apache Apex Project; and be it further>
>
> RESOLVED, that the Apache Apex Project be and hereby>
> is tasked with the migration and rationalization of the Apache>
> Incubator Apex podling; and be it further>
>
> RESOLVED, that all responsibilities pertaining to the Apache>
> Incubator Apex podling encumbered upon the Apache Incubator>
> Project are hereafter discharged.>
>
>
> On Mon, Mar 28, 2016 at 2:24 PM, Ted Dunning 
wrote:>
>
> > There hasn't been a discussion thread here on the general list, but I
am>
> > still prepared to vote in favor of this.>
> >>
> >  1>
> >>
> > See!>
> >>
> > I just did.>
> >>
> >>
> >>
> > On Mon, Mar 28, 2016 at 2:20 PM, Pramod Immaneni >
> > wrote:>
> >>
> > > The Apache Apex community has discussed and voted on graduation to
top>
> > > level project.>
> > > The vote passed with 42  1 votes (12 from the PPMC) and no 0 or -1
votes.>
> > >>
> > > Maturity Assessment:>
> > > http://apex.incubator.apache.org/maturity.html>
> > > Discussion:>
> > > https://s.apache.org/qrvY>
> > > Vote:>
> > > https://s.apache.org/R8MR>
> > > Result:>
> > > https://s.apache.org/sJIC>
> > >>
> > > Please vote on the resolution pasted below to graduate Apache Apex>
> > > from the incubator to top level project.>
> > >>
> > > [ ]  1 Graduate Apache Apex from the Incubator.>
> > > [ ]

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

2016-03-28 Thread Roman Shaposhnik 
On Tue, Mar 22, 2016 at 2:01 PM, Roman Shaposhnik  wrote:
> Hi!
>
> Quickstep proposal was made available for discussion last week
> https://wiki.apache.org/incubator/QuickstepProposal
> and the feedback so far seems to be positive.
>
> Please vote to accept Quickstep into the Apache Incubator.
> The vote will be open until Mon 3/28 noon PST.
>
> [ ] +1 Accept Quickstep into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Don't accept Quickstep into the Apache Incubator because ...

With 8 +1 binding votes, 4 +1 non-binding votes and NO -1 and/or
+-0 votes this VOTE passes. Thanks to everyone who voted. I'll
follow up with the mechanics of establishing the project.

Here's the tally:

+1 binding:
   Jean-Baptiste Onofré
   Chris Nauroth
   Tom Barber
   Chris Douglas
   Julian Hyde
   Konstantin Boudnik
   Roman Shaposhnik
   Julian Hyde

+1 non-binding:
   Alexander Bezzubov
   Uma Gangumalla
   Frank McQuillan
   Rahul Iyer

Thanks,
Roman.

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

Re: [VOTE] Release Eagle Version 0.3.0 RC3 (Incubating)

2016-03-28 Thread Julian Hyde 
Forwarding my vote from dev:

+1 (binding)

Julian

> On Mar 28, 2016, at 5:05 PM, Dendukuri, Hemanth  wrote:
> 
> Hi all,
> 
>   The Apache Eagle community has voted on and approved the proposal to 
> release "Apache Eagle 0.3.0 Release Candidate 3 (incubating)".
>   The voting result is available at 
> https://s.apache.org/eagle-0.3.0-result
> 
> 
>   The Source file to be voted are located here: 
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/
> 
>   Release Tag  :  
> https://github.com/apache/incubator-eagle/releases/tag/release-0.3.0-rc3
> 
> The commit to be voted upon: 
> https://github.com/apache/incubator-eagle/commit/b1d0a87ac0df1cc881427faafc637c152c180872
> 
>   Release artifacts are signed with the following key: 
> https://people.apache.org/keys/committer/hdendukuri.asc
> 
>   Here’s release notes:  
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.3.0
> 
> 
>   Note that this is a source only release and we are voting on the 
> source. The hashes of the source are as follows:
> 
> 
> apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md5
>   a211a151d7f66c2516c5e41da1345128
> 
>   
> apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1
>   da7b4e60228cf1421dde4342c957aff16de81cbd
> 
> 
> 
>The vote is open for a minimum of 72 hours or until the necessary 
> number of votes (3 binding +1s) is reached.
> 
>[ ] +1 Release this Eagle 0.3.0 Incubator Release Candidate 3.
> 
>[ ]  0 I don't feel strongly about it, but I'm okay with the release
> 
>[ ] -1 Do not release this package because...
> 
> Please add "(binding)" if your vote is binding.
> 
> 
> Thanks,
> 
> Hemanth Dendukuri


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

[VOTE] Release Eagle Version 0.3.0 RC3 (Incubating)

2016-03-28 Thread Dendukuri, Hemanth 
Hi all,

   The Apache Eagle community has voted on and approved the proposal to 
release "Apache Eagle 0.3.0 Release Candidate 3 (incubating)".
   The voting result is available at https://s.apache.org/eagle-0.3.0-result


   The Source file to be voted are located here: 
https://dist.apache.org/repos/dist/dev/incubator/eagle/0.3.0-incubating-rc3/

   Release Tag  :  
https://github.com/apache/incubator-eagle/releases/tag/release-0.3.0-rc3

The commit to be voted upon: 
https://github.com/apache/incubator-eagle/commit/b1d0a87ac0df1cc881427faafc637c152c180872

   Release artifacts are signed with the following key: 
https://people.apache.org/keys/committer/hdendukuri.asc

   Here’s release notes:  
https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.3.0


   Note that this is a source only release and we are voting on the source. 
The hashes of the source are as follows:

 
apache-eagle-0.3.0-incubating-src-rc3.tar.gz.md5
  a211a151d7f66c2516c5e41da1345128

   
apache-eagle-0.3.0-incubating-src-rc3.tar.gz.sha1
  da7b4e60228cf1421dde4342c957aff16de81cbd



The vote is open for a minimum of 72 hours or until the necessary 
number of votes (3 binding +1s) is reached.

[ ] +1 Release this Eagle 0.3.0 Incubator Release Candidate 3.

[ ]  0 I don't feel strongly about it, but I'm okay with the release

[ ] -1 Do not release this package because...

Please add "(binding)" if your vote is binding.


Thanks,

Hemanth Dendukuri

Re: [VOTE] Graduate Apex from the Incubator

2016-03-28 Thread Alan Gates 
+1.

Alan.

> On Mar 28, 2016, at 14:46, Pramod Immaneni  wrote:
> 
> Sorry missed including the resolution. Here is the full email again..
> 
> The Apache Apex community has discussed and voted on graduation to top
> level project.
> The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.
> 
> Maturity Assessment:http://apex.incubator.apache.org/maturity.html
> Discussion:https://s.apache.org/qrvY
> Vote:https://s.apache.org/R8MR
> Result:https://s.apache.org/sJIC
> 
> Please vote on the resolution pasted below to graduate Apache Apex
> from the incubator to top level project.
> 
> [ ] +1 Graduate Apache Apex from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Apex from the Incubator because…
> 
> This vote will be open for at least 72 hours.
> 
> Many thanks to our mentors and everyone else for the support,
> 
> Pramod Immaneni, for the Apache Apex PPMC
> 
> 
> 
> Apache Apex top-level project resolution:
> =
> 
> 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 Hadoop native, distributed,
> large-scale, high throughput, low-latency, fault tolerant,
> easily operable, unified stream and batch processing platform.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Apex Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache Apex Project be and hereby is
> responsible for the creation and maintenance of software
> related to Hadoop native, distributed, large-scale,
> high throughput, low-latency, fault tolerant, easily operable,
> unified stream and batch processing platform;
> and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Apex" 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 Apex Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Apex 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 Apex Project:
> 
> * Ilya Ganelin 
> * P. Taylor Goetz 
> * Gaurav Gupta 
> * Pramod Immaneni 
> * Amol Kekre 
> * Justin Mclean 
> * Chetan Narsude 
> * Chris Nauroth 
> * Vlad Rozov 
> * Hitesh Shah 
> * Thomas Weise 
> * David Yan 
> * Brennon York 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Thomas Weise
> be appointed to the office of Vice President, Apache Apex, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
> 
> RESOLVED, that the initial Apache Apex PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Apex Project; and be it further
> 
> RESOLVED, that the Apache Apex Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Apex podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Apex podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> 
> On Mon, Mar 28, 2016 at 2:24 PM, Ted Dunning  wrote:
> 
>> There hasn't been a discussion thread here on the general list, but I am
>> still prepared to vote in favor of this.
>> 
>> +1
>> 
>> See!
>> 
>> I just did.
>> 
>> 
>> 
>> On Mon, Mar 28, 2016 at 2:20 PM, Pramod Immaneni 
>> wrote:
>> 
>>> The Apache Apex community has discussed and voted on graduation to top
>>> level project.
>>> The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.
>>> 
>>> Maturity Assessment:
>>> http://apex.incubator.apache.org/maturity.html
>>> Discussion:
>>> https://s.apache.org/qrvY
>>> Vote:
>>> https://s.apache.org/R8MR
>>> Result:
>>> https://s.apache.org/sJIC
>>> 
>>> Please vote on the resolution pasted below to graduate Apache Apex
>>> from the incubator to top level project.
>>> 
>>> [ ] +1 Graduate Apache Apex from the Incubator.
>>> [ ] +0 Don't care.
>>> [ ] -1 Don't graduate Apache Apex from the Incubator becauseÖ
>>> 
>>> This vote will be open for at

Re: [VOTE] Graduate Apex from the Incubator

2016-03-28 Thread Thomas Weise 
+1

Thanks,
Thomas

On Mon, Mar 28, 2016 at 2:46 PM, Pramod Immaneni 
wrote:

> Sorry missed including the resolution. Here is the full email again..
>
> The Apache Apex community has discussed and voted on graduation to top
> level project.
> The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.
>
> Maturity Assessment:http://apex.incubator.apache.org/maturity.html
> Discussion:https://s.apache.org/qrvY
> Vote:https://s.apache.org/R8MR
> Result:https://s.apache.org/sJIC
>
> Please vote on the resolution pasted below to graduate Apache Apex
> from the incubator to top level project.
>
> [ ] +1 Graduate Apache Apex from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Apex from the Incubator because…
>
> This vote will be open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for the support,
>
> Pramod Immaneni, for the Apache Apex PPMC
>
>
>
> Apache Apex top-level project resolution:
> =
>
> 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 Hadoop native, distributed,
> large-scale, high throughput, low-latency, fault tolerant,
> easily operable, unified stream and batch processing platform.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Apex Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Apex Project be and hereby is
> responsible for the creation and maintenance of software
> related to Hadoop native, distributed, large-scale,
> high throughput, low-latency, fault tolerant, easily operable,
> unified stream and batch processing platform;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache Apex" 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 Apex Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Apex 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 Apex Project:
>
> * Ilya Ganelin 
> * P. Taylor Goetz 
> * Gaurav Gupta 
> * Pramod Immaneni 
> * Amol Kekre 
> * Justin Mclean 
> * Chetan Narsude 
> * Chris Nauroth 
> * Vlad Rozov 
> * Hitesh Shah 
> * Thomas Weise 
> * David Yan 
> * Brennon York 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Thomas Weise
> be appointed to the office of Vice President, Apache Apex, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Apex PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Apex Project; and be it further
>
> RESOLVED, that the Apache Apex Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Apex podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Apex podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
>
> On Mon, Mar 28, 2016 at 2:24 PM, Ted Dunning 
> wrote:
>
> > There hasn't been a discussion thread here on the general list, but I am
> > still prepared to vote in favor of this.
> >
> > +1
> >
> > See!
> >
> > I just did.
> >
> >
> >
> > On Mon, Mar 28, 2016 at 2:20 PM, Pramod Immaneni 
> > wrote:
> >
> > > The Apache Apex community has discussed and voted on graduation to top
> > > level project.
> > > The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1
> votes.
> > >
> > > Maturity Assessment:
> > > http://apex.incubator.apache.org/maturity.html
> > > Discussion:
> > > https://s.apache.org/qrvY
> > > Vote:
> > > https://s.apache.org/R8MR
> > > Result:
> > > https://s.apache.org/sJIC
> > >
> > > Please vote on the resolution pasted below to graduate Apache Apex
> > > from the incubator to top level project.
> > >
> > > [ ] +1 Graduate Apache Apex from the Incubator.
> > > [ ] +0 Don't care.
> > > [ ] -1 Don't graduate Apache Apex from the Incubator becauseÖ
> > >
> >

Re: [VOTE] Graduate Apex from the Incubator

2016-03-28 Thread Pramod Immaneni 
Sorry missed including the resolution. Here is the full email again..

The Apache Apex community has discussed and voted on graduation to top
level project.
The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.

Maturity Assessment:http://apex.incubator.apache.org/maturity.html
Discussion:https://s.apache.org/qrvY
Vote:https://s.apache.org/R8MR
Result:https://s.apache.org/sJIC

Please vote on the resolution pasted below to graduate Apache Apex
from the incubator to top level project.

[ ] +1 Graduate Apache Apex from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Apex from the Incubator because…

This vote will be open for at least 72 hours.

Many thanks to our mentors and everyone else for the support,

Pramod Immaneni, for the Apache Apex PPMC



Apache Apex top-level project resolution:
=

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 Hadoop native, distributed,
large-scale, high throughput, low-latency, fault tolerant,
easily operable, unified stream and batch processing platform.

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

RESOLVED, that the Apache Apex Project be and hereby is
responsible for the creation and maintenance of software
related to Hadoop native, distributed, large-scale,
high throughput, low-latency, fault tolerant, easily operable,
unified stream and batch processing platform;
and be it further

RESOLVED, that the office of "Vice President, Apache Apex" 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 Apex Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Apex 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 Apex Project:

* Ilya Ganelin 
* P. Taylor Goetz 
* Gaurav Gupta 
* Pramod Immaneni 
* Amol Kekre 
* Justin Mclean 
* Chetan Narsude 
* Chris Nauroth 
* Vlad Rozov 
* Hitesh Shah 
* Thomas Weise 
* David Yan 
* Brennon York 

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

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

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

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


On Mon, Mar 28, 2016 at 2:24 PM, Ted Dunning  wrote:

> There hasn't been a discussion thread here on the general list, but I am
> still prepared to vote in favor of this.
>
> +1
>
> See!
>
> I just did.
>
>
>
> On Mon, Mar 28, 2016 at 2:20 PM, Pramod Immaneni 
> wrote:
>
> > The Apache Apex community has discussed and voted on graduation to top
> > level project.
> > The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.
> >
> > Maturity Assessment:
> > http://apex.incubator.apache.org/maturity.html
> > Discussion:
> > https://s.apache.org/qrvY
> > Vote:
> > https://s.apache.org/R8MR
> > Result:
> > https://s.apache.org/sJIC
> >
> > Please vote on the resolution pasted below to graduate Apache Apex
> > from the incubator to top level project.
> >
> > [ ] +1 Graduate Apache Apex from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache Apex from the Incubator becauseÖ
> >
> > This vote will be open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for the support,
> >
> > Pramod Immaneni, for the Apache Apex PPMC
> >
>

Re: [VOTE] Graduate Apex from the Incubator

2016-03-28 Thread Ted Dunning 
There hasn't been a discussion thread here on the general list, but I am
still prepared to vote in favor of this.

+1

See!

I just did.



On Mon, Mar 28, 2016 at 2:20 PM, Pramod Immaneni  wrote:

> The Apache Apex community has discussed and voted on graduation to top
> level project.
> The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.
>
> Maturity Assessment:
> http://apex.incubator.apache.org/maturity.html
> Discussion:
> https://s.apache.org/qrvY
> Vote:
> https://s.apache.org/R8MR
> Result:
> https://s.apache.org/sJIC
>
> Please vote on the resolution pasted below to graduate Apache Apex
> from the incubator to top level project.
>
> [ ] +1 Graduate Apache Apex from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Apex from the Incubator becauseÖ
>
> This vote will be open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for the support,
>
> Pramod Immaneni, for the Apache Apex PPMC
>

[VOTE] Graduate Apex from the Incubator

2016-03-28 Thread Pramod Immaneni 
The Apache Apex community has discussed and voted on graduation to top
level project.
The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.

Maturity Assessment:
http://apex.incubator.apache.org/maturity.html
Discussion:
https://s.apache.org/qrvY
Vote:
https://s.apache.org/R8MR
Result:
https://s.apache.org/sJIC

Please vote on the resolution pasted below to graduate Apache Apex
from the incubator to top level project.

[ ] +1 Graduate Apache Apex from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Apex from the Incubator becauseÖ

This vote will be open for at least 72 hours.

Many thanks to our mentors and everyone else for the support,

Pramod Immaneni, for the Apache Apex PPMC

Re: [VOTE] Accept Quickstep into the Apache Incubator

2016-03-28 Thread Julian Hyde 
+1 (binding)

> On Mar 28, 2016, at 11:50 AM, Rahul Iyer  wrote:
> 
> +1 (non-binding)
> 
> ​
> 
> 
>>> Please vote to accept Quickstep into the Apache Incubator.
>>> The vote will be open until Mon 3/28 noon PST.
>>> 
>>> [ ] +1 Accept Quickstep into the Apache Incubator
>>> [ ] +0 Abstain
>>> [ ] -1 Don't accept Quickstep into the Apache Incubator because ...
>> 
>> ​
>> 
>> 


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

Re: [VOTE] Accept Quickstep into the Apache Incubator

2016-03-28 Thread Rahul Iyer 
+1 (non-binding)

​


> > Please vote to accept Quickstep into the Apache Incubator.
> > The vote will be open until Mon 3/28 noon PST.
> >
> > [ ] +1 Accept Quickstep into the Apache Incubator
> > [ ] +0 Abstain
> > [ ] -1 Don't accept Quickstep into the Apache Incubator because ...
>
> ​
>
>

Re: 54 podlings - too many?

2016-03-28 Thread Roman Shaposhnik 
On Sun, Mar 27, 2016 at 5:44 PM, John D. Ament  wrote:
> All,
>
> We're currently at 54 podlings in the incubator.  I feel like that's a
> lot.  Anyone else have any concerns with so many podlings?

I really encourage everybody to read the feedback on the last year's attempt
at changing the Incubator mechanics thread:  https://s.apache.org/Bxc0

I believe the subject has been beaten to death and then some. I really don't
think there's been any material change between Oct 2015 and now.

Thanks,
Roman.

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

ODF Toolkit Podling (was RE: 54 podlings - too many?)

2016-03-28 Thread Dennis E. Hamilton 
Since I came to OpenOffice and Apache via my work on ODF at OASIS, I have some 
interest in this topic.  

I share Sam Ruby's bafflement.  Sustainability of a single committer curating 
the code base is certainly a concern.  In November 2015, mentor Nick Burch 
challenged the podling with the thread starting at 
.
  The thread died out without any resolution other than to work on JIRA issues 
and their patches.

 - Dennis

OBSERVATIONS (THE TL;DR)

 1. There has been a fork of the significant ODFDOM portion of the ODF Toolkit 
and the fork is unwilling to contribute back to the ODF Toolkit, where new 
feature development seems to be dormant.

 2. There seems some confusion about what going to the attic means.  It does 
not mean that the codebase disappears, the expressed fear.  It does mean that 
the code is frozen.  That would eliminate the maintenance that is the prominent 
current activity.

 3. The ODF Toolkit and the level of SDK support in AOO are fundamentally 
different, despite any similarity of function.  There could be advantageous use 
of ODF Toolkit availability by the Apache OpenOffice project for utility, 
testing, and forensic activities on the project.  That opportunity has not been 
taken and, based on that, I don't foresee it.  

 4. Blending into AOO would doubtless dilute the dedicated attention the ODF 
Toolkit now receives, especially from users and devs, without any benefit of 
AOO developer attention.  (Merging the issue trackers would not be a plus 
either.)

 5. It seems that ODF Toolkit is in a maintenance mode that does not lead to 
releases.  That is evidently adequate for the current community.  Since July 
2014 all commits have been by two developers and since December 2014 only one 
of them.  Many of the recent commits are application of patches provided by 
others on the Apache JIRA ODFTOOLKIT project, and working via JIRA seems to go 
well.  In a brief exploration, I did not find any thrust toward expansion of 
ODF feature coverage.

MORE BACKGROUND

The ODF Toolkit came to the ASF after the Oracle licensing of OpenOffice.org to 
the ASF and the creation of the Apache OpenOffice podling.

The ODF Toolkit is essentially a pure Java project (not a bad thing) and always 
had a small development community when it existed outside of Apache.  It was 
convenient that the original ODF Toolkit project, sponsored by Oracle and IBM 
(whose copyright notices appear on files), was already licensed under ALv2.

The ODF Toolkit shares with Apache POI the provision of APIs and low-level 
functions, in this case for manipulation of ODF-format documents.  The ODF 
Toolkit does not deal with GUI or other types of user-facing functionality.  It 
is mainly a stack for developer usage in ODF processing tools and utilities.

The ODF Validator component of the project is user-operable when deployed.  I 
do not know the state of coverage of the ODF 1.2 format or the quality of 
semantic validation beyond the schema level.  I do not know the extent to which 
the profiles of ODF support by products like Microsoft Office and Apache 
OpenOffice are recognized.  (That also applies with respect to feature coverage 
of the ODF Toolkit generally.)

The ODF Toolkit is very different from SDK provided in Apache OpenOffice 
releases.  The AOO SDK provides APIs into running instances of Apache 
OpenOffice and supports such things as headless operation, injection of 
extensions, etc.  The ODF Toolkit is free-standing and lacks the complexity of 
the AOO SDK and the tight dependency on a full Apache OpenOffice instance.  
This is not a bad thing.  

There are also utility functions within the Apache OpenOffice code base and SDK 
that are usable apart from AOO.  These are the AOO UNO tools, unique to AOO, 
along with additional source to make them operable independently with reliance 
on the AOO UNO library alone.  The ODF Toolkit does not depend on UNO at all, 
providing greater fit into a Java-centric effort.




> -Original Message-
> From: sa3r...@gmail.com [mailto:sa3r...@gmail.com] On Behalf Of Sam Ruby
> Sent: Monday, March 28, 2016 05:48
> To: general@incubator.apache.org
> Subject: Re: 54 podlings - too many?
> 
> On Mon, Mar 28, 2016 at 8:37 AM, Harbs  wrote:
> > What about recommending that it be adopted by OpenOffice?
> >
> > IIUC, ODF Toolkit predates OpenOffice becoming an Apache Project. It
> seems (to an outsider like me) like the OpenOffice community would be a
> good home for a related toolkit.
> 
> It was proposed as a separate project from the beginning by a member
> of the Open Office community.
> 
> - Sam Ruby
> 
> > Harbs
> >
> > On Mar 28, 2016, at 2:33 PM, Sam Ruby  wrote:
> >
> >> On Mon, Mar 28, 2016 at 6:44 AM, John D. Ament
>  wrote:
> >>> Both great ideas.  Thanksfully,

Re: [VOTE] Accept Omid into the Apache Incubator

2016-03-28 Thread Daniel Dai 
With 11 binding +1s (Chris Nauroth, James Taylor, Flavio Junqueira,
Julian Hyde, Chris Douglas, Amol Kekre, Josh Elser, Andrew Purtell, P.
Taylor Goetz, Suresh Marru and Daniel Dai), the vote passes. Thanks
everyone for taking time to vote. I will proceed with next steps.

Thanks,
Daniel

On Fri, Mar 25, 2016 at 5:28 AM, Suresh Marru  wrote:
> + 1 (binding).
>
> Suresh
>
>> On Mar 23, 2016, at 6:31 PM, Daniel Dai  wrote:
>>
>> Following the discussion earlier, I'm calling a vote to accept Omid as
>> a new Incubator project.
>>
>> [ ] +1 Accept Omid into the Incubator
>> [ ] +0 Indifferent to the acceptance of Omid
>> [ ] -1 Do not accept Omid because ...
>>
>> The vote will be open for the next 72 hours.
>>
>> https://wiki.apache.org/incubator/OmidProposal
>>
>> Thanks,
>> Daniel
>>
>> = Omid Proposal =
>>
>> === Abstract ===
>> Omid is a flexible, reliable, high performant and scalable ACID
>> transactional framework that allows client applications to execute
>> transactions on top of MVCC key/value-based NoSQL datastores
>> (currently Apache HBase) providing Snapshot Isolation guarantees on
>> the accessed data.
>>
>> === Proposal ===
>> Omid is a flexible open-source transactional framework that provides
>> ACID transactions with Snapshot Isolation guarantees on top of NoSQL
>> datastores. In particular, the current codebase brings the concept of
>> transactions to the popular Apache HBase datastore. Omid offers great
>> performance, it is highly available, and scalable. Omid's current
>> version is able to scale to thousands of clients triggering concurrent
>> transactions on application data stored in HBase. Omid can scale
>> beyond 100K transactions per second on mid-range hardware while
>> incurring in a minimal impact on the speed of data access in the
>> datastore. We’re currently experimenting with a prototype version that
>> can improve the performance up to ~380K TPS.
>>
>> Omid has been publicly available as an open-source project in Github
>> under Apache License Version 2.0 since 2011 [1]. During these years,
>> it has generated certain interest in the open source community,
>> especially since the public presentation of the first version in
>> Hadoop Summit 2013 [2]. Currently the Github project has 241 Stars and
>> 93 forks. Yahoo Inc. submits this proposal to the Apache Software
>> Foundation with the aim to transfer the Omid project -including its
>> source code and documentation- to Apache in order to start the build
>> of a stable open source community around it.
>>
>> [1] https://github.com/yahoo/omid
>> [2] Omid presentation at Hadoop Summit 2013:
>> https://www.youtube.com/watch?v=Rhdmo9pVGgU=68=PLSAiKuajRe2luyqLU464Nxz4aQe7EPBus
>>
>> === Background ===
>> An Omid prototype was first released as an open-source project back in
>> 2011. Inspired by Google Percolator [1], it offered a lock-free
>> approach to transactions in NoSQL datastores (See [2]). However,
>> during these years, the design of Omid has evolved significantly.
>> Whilst the current open-sourced version maintains many aspects of the
>> original implementation, it is the result of a major redesign of the
>> first prototype released in 2011.
>>
>> Omid has now a more decentralized design that does not sacrifice the
>> consistency and performance of the original version. The current
>> design also enables Omid to scale to thousands of clients executing
>> transactions concurrently on application data stored in HBase.
>> Internally, Omid still utilizes a lock-free approach to support
>> multiple concurrent clients. Its design also relies on a centralized
>> conflict detection component, the TSO, which now resolves in an
>> efficient manner writeset collisions among concurrent transactions
>> without having to piggyback commit information to the clients. Another
>> important benefit of Omid is that it doesn't require any modification
>> of the underlying key-value datastore, HBase in this case. Moreover,
>> the recently added high availability algorithm allows to eliminate the
>> single point of failure represented by the TSO in those system
>> deployments requiring a higher degree of dependability. Last but not
>> least, the provided user API is very simple, mimicking transaction
>> managers in the relational world: begin, commit, rollback.
>>
>> Omid is used internally at Yahoo. Sieve, Yahoo’s web-scale content
>> management platform powering some of next-generation search and
>> personalization products is using Omid as a transaction manager in its
>> processing pipeline. Sieve essentially acts as a huge processing hub
>> between content feeds and serving systems. It provides an environment
>> for highly customizable, real-time, streamed information processing,
>> with typical discovery-to-service latencies of just a few seconds. In
>> terms of scale and availability, Omid’s new design was largely driven
>> by Sieve’s requirements.
>>
>> At Yahoo, we are also making an effort to

Re: [VOTE] Accept Quickstep into the Apache Incubator

2016-03-28 Thread Roman Shaposhnik 
On Tue, Mar 22, 2016 at 2:01 PM, Roman Shaposhnik  wrote:
> Hi!
>
> Quickstep proposal was made available for discussion last week
> https://wiki.apache.org/incubator/QuickstepProposal
> and the feedback so far seems to be positive.
>
> Please vote to accept Quickstep into the Apache Incubator.
> The vote will be open until Mon 3/28 noon PST.
>
> [ ] +1 Accept Quickstep into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Don't accept Quickstep into the Apache Incubator because ...

+1 (binding)

Thanks,
Roman.

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

Re: [VOTE] Accept Quickstep into the Apache Incubator

2016-03-28 Thread Konstantin Boudnik 
+1 [binding]

On Tue, Mar 22, 2016 at 02:01PM, Roman Shaposhnik wrote:
> Hi!
> 
> Quickstep proposal was made available for discussion last week
> https://wiki.apache.org/incubator/QuickstepProposal
> and the feedback so far seems to be positive.
> 
> Please vote to accept Quickstep into the Apache Incubator.
> The vote will be open until Mon 3/28 noon PST.
> 
> [ ] +1 Accept Quickstep into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Don't accept Quickstep into the Apache Incubator because ...
> 
> == Abstract ==
> 
> Quickstep is a high-performance database engine. It is designed to (1)
> convert data to insights at bare-metal speed, (2) support multiple
> query surfaces including SQL (the first (and current) version only
> supports SQL, and (3) deliver bare-metal performance on any hardware
> (including running on a laptop, running on a high-end (single node)
> server, and running on a distributed cluster). Since its inception,
> the project has been planned to deliver a high-performance single node
> system first, followed by a distributed system.
> 
> Quickstep is composed of several different modules that handle
> different concerns of a database system. The main modules are:
>   * Utility - Reusable general-purpose code that is used by many other 
> modules.
>   * Threading - Provides a cross-platform abstraction for threads and
> synchronization primitives that abstract the underlying OS threading
> features.
>   * Types - The core type system used across all of Quickstep. Handles
> details of how SQL types are stored, parsed, serialized &
> deserialized, and converted. Also includes basic containers for typed
> values (tuples and column-vectors) and low-level operations that apply
> to typed values (e.g. basic arithmetic and comparisons).
>   * Catalog - Tracks database schema as well as physical storage
> information for relations (e.g. which physical blocks store a
> relation's data, and any physical partitioning and placement
> information).
>   * Storage - Physically stores relational data in self-contained,
> self-describing blocks, both in-memory and on persistent storage (disk
> or a distributed filesystem). Also includes some heavyweight run-time
> data structures used in query processing (e.g. hash tables for join
> and aggregation). Includes a buffer manager component for managing
> memory use and a file manager component that handles data persistence.
>   * Compression - Implements ordered dictionary compression. Several
> storage formats in the Storage module are capable of storing
> compressed column data and evaluating some expressions directly on
> compressed data without decompressing. The common code supporting
> compression is in this module.
>   * Expressions - Builds on the simple operations provided by the
> Types module to support arbitrarily complex expressions over data,
> including scalar expressions, predicates, and aggregate functions with
> and without grouping.
>   * Relational Operators - This module provides the building blocks
> for queries in Quickstep. A query is represented as a directed acyclic
> graph of relational operators, each of which is responsible for
> applying some relational-algebraic operation(s) to transform its
> input. Operators generate individual self-contained "work orders" that
> can be executed independently. Most operators are parallelism-friendly
> and generate one work-order per storage block of input.
>   * Query Execution - Handles the actual scheduling and execution of
> work from a query at runtime. The central class is the Foreman, an
> independent thread with a global view of the query plan and progress.
> The Foreman dispatches work-orders to stateless Worker threads and
> monitors their progress, and also coordinates streaming of partial
> results between producers and consumers in a query plan DAG to
> maximize parallelism. This module also includes the QueryContext
> class, which holds global shared state for an individual query and is
> designed to support easy serialization/deserialization for distributed
> execution.
>   * Parser - A simple SQL lexer and parser that parses SQL syntax into
> an abstract syntax tree for consumption by the Query Optimizer.
>   * Query Optimizer - Takes the abstract syntax tree generated by the
> parser and transforms it into a runable query-plan DAG for the Query
> Execution module. The Query Optimizer is responsible for resolving
> references to relations and attributes in the query, checking it for
> semantic correctness, and applying optimizations (e.g. filter
> pushdown, column pruning, join ordering) as part of the transformation
> process.
>   * Command-Line Interface - An interactive SQL shell interface to Quickstep.
> 
> Quickstep is implemented in C++ and does not require many external
> libraries to run. Quickstep is currently an open source project
> licensed under the Apache License Version 2.0 and governed by a group
> of engineers at Pivotal.
> 
> Quickstep began in 2011 as a

Re: 54 podlings - too many?

2016-03-28 Thread Mattmann, Chris A (3980) 
There was also some discussion of maybe bringing the code into Apache
Tika - we would be happy to have a discussion on dev@tika if it made
sense RE: ODF Toolkit.

++
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/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++





-Original Message-
From:  on behalf of Sam Ruby 
Reply-To: "general@incubator.apache.org" 
Date: Monday, March 28, 2016 at 5:47 AM
To: "general@incubator.apache.org" 
Subject: Re: 54 podlings - too many?

>On Mon, Mar 28, 2016 at 8:37 AM, Harbs  wrote:
>> What about recommending that it be adopted by OpenOffice?
>>
>> IIUC, ODF Toolkit predates OpenOffice becoming an Apache Project. It
>>seems (to an outsider like me) like the OpenOffice community would be a
>>good home for a related toolkit.
>
>It was proposed as a separate project from the beginning by a member
>of the Open Office community.
>
>- Sam Ruby
>
>> Harbs
>>
>> On Mar 28, 2016, at 2:33 PM, Sam Ruby  wrote:
>>
>>> On Mon, Mar 28, 2016 at 6:44 AM, John D. Ament 
>>>wrote:
 Both great ideas.  Thanksfully, Whimsy helps a bit on the age part

 https://whimsy.apache.org/incubator/podlings/by-age

 It also gives a clean dashboard to display who the mentors are, etc.
Is it
 possible we can have the mentors of each project give this feedback
in an
 objective manner?
>>>
>>> Hmmm, that pie chart looks wonky.
>>>
>>> Second on the list is ODF Toolkit, with my name.  Relevant links:
>>>
>>> http://mail-archives.apache.org/mod_mbox/incubator-odf-commits/
>>> https://whimsy.apache.org/board/minutes/ODF_Toolkit.html
>>>
>>> Short summary: development continues in a slow, sometimes bursty, but
>>> steady manner; hasn't had a release in nearly two years; hasn't added
>>> any committers or PMC members in over three years; has an
>>> understanding of what they need to do to graduate.
>>>
>>> Periodically I peek in expecting to make a recommendation one way or
>>> another, but not seeing anything worth adding.  I honestly don't know
>>> what to recommend.
>>>
>>> - Sam Ruby
>>>
 John

 On Mon, Mar 28, 2016 at 2:00 AM Jean-Baptiste Onofré 
 wrote:

> Hi,
>
> I agree with Justin.
>
> Maybe, we should do kind of audit:
> - are the podlings actually active (commits, messages on the mailing
> list, releases, etc) ?
> - for how long are they in the incubator ?
> - how far are they from graduation ?
>
> We can spread this work with "buckets" assigned to volunteer
>Incubator
> PMC members. I would be happy to help there.
>
> Regards
> JB
>
> On 03/28/2016 03:42 AM, Justin Mclean wrote:
>> Hi,
>>
>>> We're currently at 54 podlings in the incubator.
>>
>> A more use stat would perhaps to see:
>> a) How long they have been in incubation?
>> b) How many releases have they made?
>>
>> May be easier to then target one that should graduate or perhaps
>>retire?
>>
>> Thanks,
>> Justin
>>
>> 
>>-
>> 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
>>
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: 54 podlings - too many?

2016-03-28 Thread Sam Ruby 
On Mon, Mar 28, 2016 at 8:37 AM, Harbs  wrote:
> What about recommending that it be adopted by OpenOffice?
>
> IIUC, ODF Toolkit predates OpenOffice becoming an Apache Project. It seems 
> (to an outsider like me) like the OpenOffice community would be a good home 
> for a related toolkit.

It was proposed as a separate project from the beginning by a member
of the Open Office community.

- Sam Ruby

> Harbs
>
> On Mar 28, 2016, at 2:33 PM, Sam Ruby  wrote:
>
>> On Mon, Mar 28, 2016 at 6:44 AM, John D. Ament  wrote:
>>> Both great ideas.  Thanksfully, Whimsy helps a bit on the age part
>>>
>>> https://whimsy.apache.org/incubator/podlings/by-age
>>>
>>> It also gives a clean dashboard to display who the mentors are, etc.  Is it
>>> possible we can have the mentors of each project give this feedback in an
>>> objective manner?
>>
>> Hmmm, that pie chart looks wonky.
>>
>> Second on the list is ODF Toolkit, with my name.  Relevant links:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-odf-commits/
>> https://whimsy.apache.org/board/minutes/ODF_Toolkit.html
>>
>> Short summary: development continues in a slow, sometimes bursty, but
>> steady manner; hasn't had a release in nearly two years; hasn't added
>> any committers or PMC members in over three years; has an
>> understanding of what they need to do to graduate.
>>
>> Periodically I peek in expecting to make a recommendation one way or
>> another, but not seeing anything worth adding.  I honestly don't know
>> what to recommend.
>>
>> - Sam Ruby
>>
>>> John
>>>
>>> On Mon, Mar 28, 2016 at 2:00 AM Jean-Baptiste Onofré 
>>> wrote:
>>>
 Hi,

 I agree with Justin.

 Maybe, we should do kind of audit:
 - are the podlings actually active (commits, messages on the mailing
 list, releases, etc) ?
 - for how long are they in the incubator ?
 - how far are they from graduation ?

 We can spread this work with "buckets" assigned to volunteer Incubator
 PMC members. I would be happy to help there.

 Regards
 JB

 On 03/28/2016 03:42 AM, Justin Mclean wrote:
> Hi,
>
>> We're currently at 54 podlings in the incubator.
>
> A more use stat would perhaps to see:
> a) How long they have been in incubation?
> b) How many releases have they made?
>
> May be easier to then target one that should graduate or perhaps retire?
>
> Thanks,
> Justin
>
> -
> 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
>

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

Re: 54 podlings - too many?

2016-03-28 Thread Harbs 
What about recommending that it be adopted by OpenOffice?

IIUC, ODF Toolkit predates OpenOffice becoming an Apache Project. It seems (to 
an outsider like me) like the OpenOffice community would be a good home for a 
related toolkit.

Harbs

On Mar 28, 2016, at 2:33 PM, Sam Ruby  wrote:

> On Mon, Mar 28, 2016 at 6:44 AM, John D. Ament  wrote:
>> Both great ideas.  Thanksfully, Whimsy helps a bit on the age part
>> 
>> https://whimsy.apache.org/incubator/podlings/by-age
>> 
>> It also gives a clean dashboard to display who the mentors are, etc.  Is it
>> possible we can have the mentors of each project give this feedback in an
>> objective manner?
> 
> Hmmm, that pie chart looks wonky.
> 
> Second on the list is ODF Toolkit, with my name.  Relevant links:
> 
> http://mail-archives.apache.org/mod_mbox/incubator-odf-commits/
> https://whimsy.apache.org/board/minutes/ODF_Toolkit.html
> 
> Short summary: development continues in a slow, sometimes bursty, but
> steady manner; hasn't had a release in nearly two years; hasn't added
> any committers or PMC members in over three years; has an
> understanding of what they need to do to graduate.
> 
> Periodically I peek in expecting to make a recommendation one way or
> another, but not seeing anything worth adding.  I honestly don't know
> what to recommend.
> 
> - Sam Ruby
> 
>> John
>> 
>> On Mon, Mar 28, 2016 at 2:00 AM Jean-Baptiste Onofré 
>> wrote:
>> 
>>> Hi,
>>> 
>>> I agree with Justin.
>>> 
>>> Maybe, we should do kind of audit:
>>> - are the podlings actually active (commits, messages on the mailing
>>> list, releases, etc) ?
>>> - for how long are they in the incubator ?
>>> - how far are they from graduation ?
>>> 
>>> We can spread this work with "buckets" assigned to volunteer Incubator
>>> PMC members. I would be happy to help there.
>>> 
>>> Regards
>>> JB
>>> 
>>> On 03/28/2016 03:42 AM, Justin Mclean wrote:
 Hi,
 
> We're currently at 54 podlings in the incubator.
 
 A more use stat would perhaps to see:
 a) How long they have been in incubation?
 b) How many releases have they made?
 
 May be easier to then target one that should graduate or perhaps retire?
 
 Thanks,
 Justin
 
 -
 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

Re: 54 podlings - too many?

2016-03-28 Thread Sam Ruby 
On Mon, Mar 28, 2016 at 7:36 AM, John D. Ament  wrote:
> On Mon, Mar 28, 2016 at 7:33 AM Sam Ruby  wrote:
>
>> On Mon, Mar 28, 2016 at 6:44 AM, John D. Ament 
>> wrote:
>> > Both great ideas.  Thanksfully, Whimsy helps a bit on the age part
>> >
>> > https://whimsy.apache.org/incubator/podlings/by-age
>> >
>> > It also gives a clean dashboard to display who the mentors are, etc.  Is
>> it
>> > possible we can have the mentors of each project give this feedback in an
>> > objective manner?
>>
>> Hmmm, that pie chart looks wonky.
>
> What does the pie chart even mean?

Try hovering your cursor over it :-)

- Sam Ruby

>> Second on the list is ODF Toolkit, with my name.  Relevant links:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-odf-commits/
>> https://whimsy.apache.org/board/minutes/ODF_Toolkit.html
>>
>> Short summary: development continues in a slow, sometimes bursty, but
>> steady manner; hasn't had a release in nearly two years; hasn't added
>> any committers or PMC members in over three years; has an
>> understanding of what they need to do to graduate.
>>
>> Periodically I peek in expecting to make a recommendation one way or
>> another, but not seeing anything worth adding.  I honestly don't know
>> what to recommend.
>>
>> - Sam Ruby
>>
>> > John
>> >
>> > On Mon, Mar 28, 2016 at 2:00 AM Jean-Baptiste Onofré 
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> I agree with Justin.
>> >>
>> >> Maybe, we should do kind of audit:
>> >> - are the podlings actually active (commits, messages on the mailing
>> >> list, releases, etc) ?
>> >> - for how long are they in the incubator ?
>> >> - how far are they from graduation ?
>> >>
>> >> We can spread this work with "buckets" assigned to volunteer Incubator
>> >> PMC members. I would be happy to help there.
>> >>
>> >> Regards
>> >> JB
>> >>
>> >> On 03/28/2016 03:42 AM, Justin Mclean wrote:
>> >> > Hi,
>> >> >
>> >> >> We're currently at 54 podlings in the incubator.
>> >> >
>> >> > A more use stat would perhaps to see:
>> >> > a) How long they have been in incubation?
>> >> > b) How many releases have they made?
>> >> >
>> >> > May be easier to then target one that should graduate or perhaps
>> retire?
>> >> >
>> >> > Thanks,
>> >> > Justin
>> >> >
>> >> > -
>> >> > 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
>>
>>

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

Re: 54 podlings - too many?

2016-03-28 Thread John D. Ament 
On Mon, Mar 28, 2016 at 7:33 AM Sam Ruby  wrote:

> On Mon, Mar 28, 2016 at 6:44 AM, John D. Ament 
> wrote:
> > Both great ideas.  Thanksfully, Whimsy helps a bit on the age part
> >
> > https://whimsy.apache.org/incubator/podlings/by-age
> >
> > It also gives a clean dashboard to display who the mentors are, etc.  Is
> it
> > possible we can have the mentors of each project give this feedback in an
> > objective manner?
>
> Hmmm, that pie chart looks wonky.
>

What does the pie chart even mean?


>
> Second on the list is ODF Toolkit, with my name.  Relevant links:
>
> http://mail-archives.apache.org/mod_mbox/incubator-odf-commits/
> https://whimsy.apache.org/board/minutes/ODF_Toolkit.html
>
> Short summary: development continues in a slow, sometimes bursty, but
> steady manner; hasn't had a release in nearly two years; hasn't added
> any committers or PMC members in over three years; has an
> understanding of what they need to do to graduate.
>
> Periodically I peek in expecting to make a recommendation one way or
> another, but not seeing anything worth adding.  I honestly don't know
> what to recommend.
>
> - Sam Ruby
>
> > John
> >
> > On Mon, Mar 28, 2016 at 2:00 AM Jean-Baptiste Onofré 
> > wrote:
> >
> >> Hi,
> >>
> >> I agree with Justin.
> >>
> >> Maybe, we should do kind of audit:
> >> - are the podlings actually active (commits, messages on the mailing
> >> list, releases, etc) ?
> >> - for how long are they in the incubator ?
> >> - how far are they from graduation ?
> >>
> >> We can spread this work with "buckets" assigned to volunteer Incubator
> >> PMC members. I would be happy to help there.
> >>
> >> Regards
> >> JB
> >>
> >> On 03/28/2016 03:42 AM, Justin Mclean wrote:
> >> > Hi,
> >> >
> >> >> We're currently at 54 podlings in the incubator.
> >> >
> >> > A more use stat would perhaps to see:
> >> > a) How long they have been in incubation?
> >> > b) How many releases have they made?
> >> >
> >> > May be easier to then target one that should graduate or perhaps
> retire?
> >> >
> >> > Thanks,
> >> > Justin
> >> >
> >> > -
> >> > 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
>
>

Re: 54 podlings - too many?

2016-03-28 Thread Marvin Humphrey 
On Sun, Mar 27, 2016 at 6:42 PM, Justin Mclean  wrote:
> Hi,
>
>> We're currently at 54 podlings in the incubator.
>
> A more use stat would perhaps to see:
> a) How long they have been in incubation?
> b) How many releases have they made?
>
> May be easier to then target one that should graduate or perhaps retire?

The "Clutch Report" provides this sort of analysis.

  http://incubator.apache.org/clutch.html

Column B is "number of days in incubation", helpfully color coded.

Column S is "has release".

Plus lots of other data.

Marvin Humphrey

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

Re: 54 podlings - too many?

2016-03-28 Thread Sam Ruby 
On Mon, Mar 28, 2016 at 6:44 AM, John D. Ament  wrote:
> Both great ideas.  Thanksfully, Whimsy helps a bit on the age part
>
> https://whimsy.apache.org/incubator/podlings/by-age
>
> It also gives a clean dashboard to display who the mentors are, etc.  Is it
> possible we can have the mentors of each project give this feedback in an
> objective manner?

Hmmm, that pie chart looks wonky.

Second on the list is ODF Toolkit, with my name.  Relevant links:

http://mail-archives.apache.org/mod_mbox/incubator-odf-commits/
https://whimsy.apache.org/board/minutes/ODF_Toolkit.html

Short summary: development continues in a slow, sometimes bursty, but
steady manner; hasn't had a release in nearly two years; hasn't added
any committers or PMC members in over three years; has an
understanding of what they need to do to graduate.

Periodically I peek in expecting to make a recommendation one way or
another, but not seeing anything worth adding.  I honestly don't know
what to recommend.

- Sam Ruby

> John
>
> On Mon, Mar 28, 2016 at 2:00 AM Jean-Baptiste Onofré 
> wrote:
>
>> Hi,
>>
>> I agree with Justin.
>>
>> Maybe, we should do kind of audit:
>> - are the podlings actually active (commits, messages on the mailing
>> list, releases, etc) ?
>> - for how long are they in the incubator ?
>> - how far are they from graduation ?
>>
>> We can spread this work with "buckets" assigned to volunteer Incubator
>> PMC members. I would be happy to help there.
>>
>> Regards
>> JB
>>
>> On 03/28/2016 03:42 AM, Justin Mclean wrote:
>> > Hi,
>> >
>> >> We're currently at 54 podlings in the incubator.
>> >
>> > A more use stat would perhaps to see:
>> > a) How long they have been in incubation?
>> > b) How many releases have they made?
>> >
>> > May be easier to then target one that should graduate or perhaps retire?
>> >
>> > Thanks,
>> > Justin
>> >
>> > -
>> > 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

Re: 54 podlings - too many?

2016-03-28 Thread John D. Ament 
Both great ideas.  Thanksfully, Whimsy helps a bit on the age part

https://whimsy.apache.org/incubator/podlings/by-age

It also gives a clean dashboard to display who the mentors are, etc.  Is it
possible we can have the mentors of each project give this feedback in an
objective manner?

John

On Mon, Mar 28, 2016 at 2:00 AM Jean-Baptiste Onofré 
wrote:

> Hi,
>
> I agree with Justin.
>
> Maybe, we should do kind of audit:
> - are the podlings actually active (commits, messages on the mailing
> list, releases, etc) ?
> - for how long are they in the incubator ?
> - how far are they from graduation ?
>
> We can spread this work with "buckets" assigned to volunteer Incubator
> PMC members. I would be happy to help there.
>
> Regards
> JB
>
> On 03/28/2016 03:42 AM, Justin Mclean wrote:
> > Hi,
> >
> >> We're currently at 54 podlings in the incubator.
> >
> > A more use stat would perhaps to see:
> > a) How long they have been in incubation?
> > b) How many releases have they made?
> >
> > May be easier to then target one that should graduate or perhaps retire?
> >
> > Thanks,
> > Justin
> >
> > -
> > 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: 54 podlings - too many?

2016-03-28 Thread Michael Fitzner 


> Am 28.03.2016 um 07:59 schrieb Jean-Baptiste
Add
> Onofré :
> 
> Hi,
> 
> I agree with Justin.
> 
> Maybe, we should do kind of audit:
> - are the podlings actually active (commits, messages on the mailing list, 
> releases, etc) ?
> - for how long are they in the incubator ?
> - how far are they from graduation ?
> 
> We can spread this work with "buckets" assigned to volunteer Incubator PMC 
> members. I would be happy to help there.
> 
> Regards
> JB
> 
>> On 03/28/2016 03:42 AM, Justin Mclean wrote:
>> Hi,
>> 
>>> We're currently at 54 podlings in the incubator.
>> 
>> A more use stat would perhaps to see:
>> a) How long they have been in incubation?
>> b) How many releases have they made?
>> 
>> May be easier to then target one that should graduate or perhaps retire?
>> 
>> Thanks,
>> Justin
>> 
>> -
>> 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

Re: 54 podlings - too many?

2016-03-28 Thread Jean-Baptiste Onofré 

Hi,

I agree with Justin.

Maybe, we should do kind of audit:
- are the podlings actually active (commits, messages on the mailing 
list, releases, etc) ?

- for how long are they in the incubator ?
- how far are they from graduation ?

We can spread this work with "buckets" assigned to volunteer Incubator 
PMC members. I would be happy to help there.


Regards
JB

On 03/28/2016 03:42 AM, Justin Mclean wrote:

Hi,


We're currently at 54 podlings in the incubator.


A more use stat would perhaps to see:
a) How long they have been in incubation?
b) How many releases have they made?

May be easier to then target one that should graduate or perhaps retire?

Thanks,
Justin

-
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