List Split


#1

I’m honestly sure that nobody cares, but this list needs to split, I
can’t
handle the volume of junk that is completely irrelevant because I am
subscribed looking for to keep up to date with cucumber wisdom; I’m
going to
see how this message is received, and unsubscribe myself later today.
The SNR ratio is absurd, and the list users should really consider a
split.

Thanks for the things I’ve learned, and the tips and tricks that I have
been
fortunate enough to pick up.

  • Lee

#2

On Mon, May 18, 2009 at 10:13 AM, Lee H. removed_email_address@domain.invalid
wrote:

I’m honestly sure that nobody cares, but this list needs to split, I can’t
handle the volume of junk that is completely irrelevant because I am
subscribed looking for to keep up to date with cucumber wisdom; I’m going to
see how this message is received, and unsubscribe myself later today.

The SNR ratio is absurd, and the list users should really consider a split.
Thanks for the things I’ve learned, and the tips and tricks that I have been
fortunate enough to pick up.

Over the entire weekend I received a little over 30 messages on this
list. I wouldn’t exactly consider that high-volume or absurd.

I use both RSpec and Cucumber and I don’t personally mind them being
on the same list as it allows me participate in discussions that
pertain to the full cycle of outside-in development. I can see where
you are coming from though since you only seem to care about the
Cucumber aspect of things. If the lists are split I will simply
subscribe to both.

A nice thing about having the two ML’s combined at this point is that
discussions and questions which span the entire BDD process can be
asked and answered. The down-side of this is that not all folks who
use Cucumber use RSpec (or even Ruby).

I don’t encourage the split, but I think it is becoming inevitable.
Cucumber itself is becoming large and wide. I can’t think of a good
reason for Java programmers who want to use Cucumber to join the RSpec
ML.

  • Lee

rspec-users mailing list
removed_email_address@domain.invalid
http://rubyforge.org/mailman/listinfo/rspec-users


Zach D.
http://www.continuousthinking.com (personal)
http://www.mutuallyhuman.com (hire me)
@zachdennis (twitter)


#3

Zach,
You hit the nail on the head exactly, the problem was compounded by my
being
on vacation for a week, and coming back to a flood of emails,
regrettably my
gmail filters can’t even take the strain, I can’t restrict it accurately
enough, as there isn’t enough standardization in subject tagging
([rspec-users] [cucumber]) to filter accurately.

It was a general moan on my part, and not really fair to air it to the
list,
but looking at the archives, this comes up from time to time, and I
agree
completely for anyone using the whole package, it is an invaluable
resource… I’m not sure what the solution is, or how my participation
will
continue (not that the list will feel my absence!)

I do however want the best for the list, and to voice my distress with
the
volume of traffic that could very well be largely irrelevant to the
typical user… as it happens we are using the rspec+cucumber stack
with
MRI ruby, and a rails project, it doesn’t get more mainstream for rspec
and
cucumber than that, but even so I find most of the rspec centric
conversations on the list to be distracting and confusing.

Considerately,

  • Lee

2009/5/18 Zach D. removed_email_address@domain.invalid


#4

makes no difference to me, if the list were to split, i’d subscribe
to both so I’d see the same signal and noise.

–linoj


#5

On Mon, May 18, 2009 at 11:46 AM, Zach D. removed_email_address@domain.invalid
wrote:

On Mon, May 18, 2009 at 10:13 AM, Lee H. removed_email_address@domain.invalid wrote:

I’m honestly sure that nobody cares, but this list needs to split, I can’t
handle the volume of junk that is completely irrelevant because I am
subscribed looking for to keep up to date with cucumber wisdom; I’m going to
see how this message is received, and unsubscribe myself later today.

The SNR ratio is absurd, and the list users should really consider a split.
Thanks for the things I’ve learned, and the tips and tricks that I have been
fortunate enough to pick up.

use Cucumber use RSpec (or even Ruby).

I don’t encourage the split, but I think it is becoming inevitable.
Cucumber itself is becoming large and wide. I can’t think of a good
reason for Java programmers who want to use Cucumber to join the RSpec
ML.

As a long-time RSpec, and now Cucumber user, to me the Java stuff is
the noise .


Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale


#6

Rick,
To me too, maybe we could get some mileage by just having a convention
of
tagging subjects properly [rspec-users][cucumber][java] etc… and people
could filter out what they just don’t care about

Actually, looking at today’s mail, its the Java thread that broke the
proverbial camel’s back and prompted me to post this thread

  • Lee

2009/5/18 Jonathan L. removed_email_address@domain.invalid


#7

On Mon, May 18, 2009 at 9:51 AM, Lee H. removed_email_address@domain.invalid
wrote:

To me too, maybe we could get some mileage by just having a convention of
tagging subjects properly [rspec-users][cucumber][java] etc… and people
could filter out what they just don’t care about

Been there, mandated that - it didn’t work.

I think a mailing list should be about one subject (defined broadly or
narrowly). For example, “rspec-users” should be for users of RSpec.

///ark