[RESULT] [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-09 Thread Jeff Jirsa

With 8 binding +1s (including myself), 3 non-binding +1, and no -1, the vote 
passes, and we'll work to close out this list.

- Jeff

On 2016-11-06 21:11 (-0800), "Jeff Jirsa" wrote: 
> There exists a nearly unused mailing list, client-...@cassandra.apache.org 
> [0]. 
> 
> This is a summary of the email threads over the past 12 months on that list:
> 
> 1) ApacheCon Seville CFP Close notice
> 2) Datastax .NET driver question 
> 3) Datastax Java driver question
> 4) FOSDEM announce
> 5) ApacheCon NA CFP Open noticed
> 
> In order to avoid confusion, and given the lack of relevant and appropriate 
> traffic, I propose we close the client-dev@ list entirely. Any traffic 
> appropriate for the client-dev@ list would likely be better served if it were 
> directed at dev@, which is more active.
> 
> This vote will remain open for 72 hours. 
> 
> 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org
> 
> 
> 


Re: [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-08 Thread Ben Bromhead
+1 (non-binding)

On Tue, 8 Nov 2016 at 10:05 Jake Farrell  wrote:

> +1
>
> -Jake
>
> On Mon, Nov 7, 2016 at 12:11 AM, Jeff Jirsa  wrote:
>
> > There exists a nearly unused mailing list,
> client-...@cassandra.apache.org
> > [0].
> >
> > This is a summary of the email threads over the past 12 months on that
> > list:
> >
> > 1) ApacheCon Seville CFP Close notice
> > 2) Datastax .NET driver question
> > 3) Datastax Java driver question
> > 4) FOSDEM announce
> > 5) ApacheCon NA CFP Open noticed
> >
> > In order to avoid confusion, and given the lack of relevant and
> > appropriate traffic, I propose we close the client-dev@ list entirely.
> > Any traffic appropriate for the client-dev@ list would likely be better
> > served if it were directed at dev@, which is more active.
> >
> > This vote will remain open for 72 hours.
> >
> > 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org
> >
> >
> >
>
-- 
Ben Bromhead
CTO | Instaclustr 
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer


Re: [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-08 Thread Jake Farrell
+1

-Jake

On Mon, Nov 7, 2016 at 12:11 AM, Jeff Jirsa  wrote:

> There exists a nearly unused mailing list, client-...@cassandra.apache.org
> [0].
>
> This is a summary of the email threads over the past 12 months on that
> list:
>
> 1) ApacheCon Seville CFP Close notice
> 2) Datastax .NET driver question
> 3) Datastax Java driver question
> 4) FOSDEM announce
> 5) ApacheCon NA CFP Open noticed
>
> In order to avoid confusion, and given the lack of relevant and
> appropriate traffic, I propose we close the client-dev@ list entirely.
> Any traffic appropriate for the client-dev@ list would likely be better
> served if it were directed at dev@, which is more active.
>
> This vote will remain open for 72 hours.
>
> 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org
>
>
>


Re: [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-07 Thread Dave Lester
+1 (non-binding)

On 2016-11-07 12:52 (-0800), sankalp kohli  wrote: 
> +1
> 
> On Mon, Nov 7, 2016 at 10:19 AM, Brandon Williams  wrote:
> 
> > As the moderator of this list, +1.  It was more helpful in the thrift days
> > (where I built a client, and thus became the moderator) but is practically
> > useless in the cql world.
> >
> > On Sun, Nov 6, 2016 at 11:11 PM, Jeff Jirsa  wrote:
> >
> > > There exists a nearly unused mailing list, client-dev@cassandra.apache.
> > org
> > > [0].
> > >
> > > This is a summary of the email threads over the past 12 months on that
> > > list:
> > >
> > > 1) ApacheCon Seville CFP Close notice
> > > 2) Datastax .NET driver question
> > > 3) Datastax Java driver question
> > > 4) FOSDEM announce
> > > 5) ApacheCon NA CFP Open noticed
> > >
> > > In order to avoid confusion, and given the lack of relevant and
> > > appropriate traffic, I propose we close the client-dev@ list entirely.
> > > Any traffic appropriate for the client-dev@ list would likely be better
> > > served if it were directed at dev@, which is more active.
> > >
> > > This vote will remain open for 72 hours.
> > >
> > > 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org
> > >
> > >
> > >
> >
> 


Re: [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-07 Thread Brandon Williams
As the moderator of this list, +1.  It was more helpful in the thrift days
(where I built a client, and thus became the moderator) but is practically
useless in the cql world.

On Sun, Nov 6, 2016 at 11:11 PM, Jeff Jirsa  wrote:

> There exists a nearly unused mailing list, client-...@cassandra.apache.org
> [0].
>
> This is a summary of the email threads over the past 12 months on that
> list:
>
> 1) ApacheCon Seville CFP Close notice
> 2) Datastax .NET driver question
> 3) Datastax Java driver question
> 4) FOSDEM announce
> 5) ApacheCon NA CFP Open noticed
>
> In order to avoid confusion, and given the lack of relevant and
> appropriate traffic, I propose we close the client-dev@ list entirely.
> Any traffic appropriate for the client-dev@ list would likely be better
> served if it were directed at dev@, which is more active.
>
> This vote will remain open for 72 hours.
>
> 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org
>
>
>


Re: [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-07 Thread Nate McCall
+1

On Mon, Nov 7, 2016 at 6:11 PM, Jeff Jirsa  wrote:
> There exists a nearly unused mailing list, client-...@cassandra.apache.org 
> [0].
>
> This is a summary of the email threads over the past 12 months on that list:
>
> 1) ApacheCon Seville CFP Close notice
> 2) Datastax .NET driver question
> 3) Datastax Java driver question
> 4) FOSDEM announce
> 5) ApacheCon NA CFP Open noticed
>
> In order to avoid confusion, and given the lack of relevant and appropriate 
> traffic, I propose we close the client-dev@ list entirely. Any traffic 
> appropriate for the client-dev@ list would likely be better served if it were 
> directed at dev@, which is more active.
>
> This vote will remain open for 72 hours.
>
> 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org
>
>


Re: [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-07 Thread Licata, Christopher (CONT)
+1

Thanks,
Christopher Licata
Senior Software Engineer
Game Changers 
Card Rewards
718.916.8940



On 11/7/16, 10:29 AM, "Michael Shuler"  wrote:

1) ApacheCon Seville CFP Close notice
2) Datastax .NET driver question 
3) Datastax Java driver question
4) FOSDEM announce
5) ApacheCon NA CFP Open noticed

In order to avoid confusion, and given the lack of relevant and appropriate 
traffic, I propose we close the client-dev@ list entirely. Any traffic 
appropriate for the client-dev@ list would likely be better served if it were 
directed at dev@, which is more active.




The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.


Re: [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-07 Thread Michael Shuler
+1

On 11/06/2016 11:11 PM, Jeff Jirsa wrote:
> There exists a nearly unused mailing list, client-...@cassandra.apache.org 
> [0]. 
> 
> This is a summary of the email threads over the past 12 months on that list:
> 
> 1) ApacheCon Seville CFP Close notice
> 2) Datastax .NET driver question 
> 3) Datastax Java driver question
> 4) FOSDEM announce
> 5) ApacheCon NA CFP Open noticed
> 
> In order to avoid confusion, and given the lack of relevant and appropriate 
> traffic, I propose we close the client-dev@ list entirely. Any traffic 
> appropriate for the client-dev@ list would likely be better served if it were 
> directed at dev@, which is more active.
> 
> This vote will remain open for 72 hours. 
> 
> 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org
> 
> 



Re: [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-06 Thread Gary Dusbabek
+1 let's close it.

Gary.


On Mon, Nov 7, 2016 at 5:11 AM, Jeff Jirsa  wrote:

> There exists a nearly unused mailing list, client-...@cassandra.apache.org
> [0].
>
> This is a summary of the email threads over the past 12 months on that
> list:
>
> 1) ApacheCon Seville CFP Close notice
> 2) Datastax .NET driver question
> 3) Datastax Java driver question
> 4) FOSDEM announce
> 5) ApacheCon NA CFP Open noticed
>
> In order to avoid confusion, and given the lack of relevant and
> appropriate traffic, I propose we close the client-dev@ list entirely.
> Any traffic appropriate for the client-dev@ list would likely be better
> served if it were directed at dev@, which is more active.
>
> This vote will remain open for 72 hours.
>
> 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org
>
>
>


[VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-06 Thread Jeff Jirsa
There exists a nearly unused mailing list, client-...@cassandra.apache.org [0]. 

This is a summary of the email threads over the past 12 months on that list:

1) ApacheCon Seville CFP Close notice
2) Datastax .NET driver question 
3) Datastax Java driver question
4) FOSDEM announce
5) ApacheCon NA CFP Open noticed

In order to avoid confusion, and given the lack of relevant and appropriate 
traffic, I propose we close the client-dev@ list entirely. Any traffic 
appropriate for the client-dev@ list would likely be better served if it were 
directed at dev@, which is more active.

This vote will remain open for 72 hours. 

0: https://lists.apache.org/list.html?client-...@cassandra.apache.org