Announce@ == less email (FAQ item?)

ZenTest and ZenWeb were just released. I announced these to several
lists including this one. I’m sure many of you got multiple copies. I
admit that is annoying. These releases announce my LAST announcements
to ruby-talk@. I’ll be announcing only to announce@rubynet.org. I urge
every developer releasing ruby scripts, modules, or anyone having
ruby-related events to use this as your primary means of announcing
your information. It will cut down on volumes of email that we get and
make it easier to focus on the work at hand.

http://lists.rubynet.net/lists/listinfo/rubynet-announce

ALSO:

1) Can we get this link added to www.ruby-lang.org?
2) Can we get this link added to the FAQ(s)?

I’ll add it to the comp.lang.ruby FAQ if
you wish. I’ll list it as a possibility
for people who wish to make announcements.
But these will be read only by the people
reading that list, not on the main Ruby
mailing list or the newsgroup.

I, for one, will continue announcing to
ruby-talk (not that I have ever made many
announcements); and I hope that everyone
else will also. I don’t want to subscribe
to yet another mailing list, and I don’t
want to miss announcements either.

My personal opinion is that the announcements
are some of the most interesting and relevant
material on the list.

What I do wish we could get rid of are the
posts by people who think they can improve
Ruby by dragging it in a direction other
than what Matz has in mind, i.e., by making
it more like Java or COBOL or whatever.
These are what really make me tired. Even
more so than the occasional spam email we get.

Hal

···

----- Original Message -----
From: “Ryan Davis” ryand-ruby@zenspider.com
To: “ruby-talk ML” ruby-talk@ruby-lang.org
Sent: Sunday, September 29, 2002 1:30 AM
Subject: announce@ == less email (FAQ item?)

ZenTest and ZenWeb were just released. I announced these to several
lists including this one. I’m sure many of you got multiple copies. I
admit that is annoying. These releases announce my LAST announcements
to ruby-talk@. I’ll be announcing only to announce@rubynet.org. I urge
every developer releasing ruby scripts, modules, or anyone having
ruby-related events to use this as your primary means of announcing
your information. It will cut down on volumes of email that we get and
make it easier to focus on the work at hand.

  1. Can we get this link added to the FAQ(s)?

Ryan Davis wrote:

ZenTest and ZenWeb were just released. I announced these to several
lists including this one. I’m sure many of you got multiple copies. I
admit that is annoying. These releases announce my LAST announcements to
ruby-talk@. I’ll be announcing only to announce@rubynet.org. I urge
every developer releasing ruby scripts, modules, or anyone having
ruby-related events to use this as your primary means of announcing your
information. It will cut down on volumes of email that we get and make
it easier to focus on the work at hand.

http://lists.rubynet.net/lists/listinfo/rubynet-announce

ALSO:

1) Can we get this link added to www.ruby-lang.org?
2) Can we get this link added to the FAQ(s)?

I appreciate the effort, Ryan.

Unfortunately, subscribing to it will only increase the volume for those
of us who are staying on ruby-talk. And it will double the effort
required to search archives. And it will make it harder for newbies to
understand how the community works.

Personally, I think ruby-talk is enough and don’t think list
proliferation is good for the community. I understand why some might not
want to deal with the volume. Have you considered just using a procmail
filter to trash everything but /^[ANN/ ?

In any case, I would like to see the announcements. Is it possible to
automatically forward from rubynet-announce to ruby-talk? Then people
could choose whether to subscribe to one or the other, without missing
anything, and without getting duplicates.

Also, about the name: some people might get the impression that the
rubynet-announce list is for announcements related to the rubynet
project. Why not call it ruby-announce?

People reading ruby-talk are interested also in announcements, so I
for one will keep posting them here. I’ll be happy, though, to cross
post them to announce@ for those who are interested only in
announcements (if it’s allowed to post without having to subscribe).

But I begin to wonder whether it should a bot’s task to forward the
[ANN]'s it sees on ruby-talk to a ruby-ann. Oh well, just a
thought…

Massimiliano (bard on IRC)

···

On Sun, Sep 29, 2002 at 03:30:20PM +0900, Ryan Davis wrote:

I urge every developer releasing ruby scripts, modules, or anyone
having ruby-related events to use this as your primary means of
announcing your information.

From: “Ryan Davis” ryand-ruby@zenspider.com

ZenTest and ZenWeb were just released. I announced these to several
lists including this one. I’m sure many of you got multiple copies. I
admit that is annoying. These releases announce my LAST announcements
to ruby-talk@. I’ll be announcing only to announce@rubynet.org. I urge
every developer releasing ruby scripts, modules, or anyone having
ruby-related events to use this as your primary means of announcing
your information. It will cut down on volumes of email that we get and
make it easier to focus on the work at hand.

  1. Can we get this link added to the FAQ(s)?

I’ll add it to the comp.lang.ruby FAQ if
you wish. I’ll list it as a possibility
for people who wish to make announcements.
But these will be read only by the people
reading that list, not on the main Ruby
mailing list or the newsgroup.

I, for one, will continue announcing to
ruby-talk (not that I have ever made many
announcements); and I hope that everyone
else will also. I don’t want to subscribe
to yet another mailing list, and I don’t
want to miss announcements either.

I too question the value of a separate list. Announcements don’t take up much
room in this list. There’s no need for duplicate emails: just send them all to
ruby-talk. I can’t conceive of anybody wanting to read announcements only. If
they’re not subscribed here, they’re probably not into mailing lists. Also,
what happens to follow-up discussion of announcements?

I don’t mind the announcements disappearing, per se. As long as they get
reported in the Weekly News.

My personal opinion is that the announcements
are some of the most interesting and relevant
material on the list.

What I do wish we could get rid of are the
posts by people who think they can improve
Ruby by dragging it in a direction other
than what Matz has in mind, i.e., by making
it more like Java or COBOL or whatever.
These are what really make me tired. Even
more so than the occasional spam email we get.

That’s a bit harsh. I agree it’s a bit irritating, but only a bit, and it’s
natural. If we had some good documents (FAQ? Wiki?) summarising the
discussions, they could be used to stop repeating them … again. They’d be
interesting documents too.

Hal

Gavin

···

From: “Hal E. Fulton” hal9000@hypermetrics.com

Hal E. Fulton wrote:

I, for one, will continue announcing to
ruby-talk (not that I have ever made many
announcements); and I hope that everyone
else will also. I don’t want to subscribe
to yet another mailing list, and I don’t
want to miss announcements either.

My personal opinion is that the announcements
are some of the most interesting and relevant
material on the list.

I agree. An announcements-only list is a nice service for those who want
to follow Ruby without getting 50 emails a day. But it would be an
annoyance for us ruby-talk subscribers to have yet another list to keep
track of.

/Anders

···

A n d e r s B e n g t s s o n | ndrsbngtssn@yahoo.se
Stockholm, Sweden |


Följ VM på nära håll på Yahoo!s officielle VM-sajt www.yahoo.se/vm2002
Håll dig ajour med nyheter och resultat, med vinnare och förlorare…

> What I do wish we could get rid of are the > posts by people who think they can improve > Ruby by dragging it in a direction other > than what Matz has in mind, i.e., by making > it more like Java or COBOL or whatever. > These are what really make me tired. Even > more so than the occasional spam email we get.

I completely agree. Those post always keep me in a state of dread concerning
the Ruby I know and love. I was glad when someone decided that it would be a
good thing to have a list of gotchas for people coming from other languages;
then instead of having to constantly explain the rationale of Ruby over and
over to each one, we could just say: read item number x in the FAQ, and be
done with it.

Albert

···

On Sunday 29 September 2002 02:03 am, Hal E. Fulton wrote:

Hal

Seeing [ANN] in the subject is nice. I used to use a script to try and collect
the announcements automatically for me so I could put them in the RWN.
However I noticed that it missed the occassional announcement so now I don’t
bother and parse all mail manually. It takes longer to compose the RWN now,
but I think it is more complete, that is, unless everyone would [ANN] their
announcements :slight_smile:


Signed,
Holden Glova

···

On Mon, 30 Sep 2002 10:13, Massimiliano Mirra wrote:

On Sun, Sep 29, 2002 at 03:30:20PM +0900, Ryan Davis wrote:

I urge every developer releasing ruby scripts, modules, or anyone
having ruby-related events to use this as your primary means of
announcing your information.

People reading ruby-talk are interested also in announcements, so I
for one will keep posting them here. I’ll be happy, though, to cross
post them to announce@ for those who are interested only in
announcements (if it’s allowed to post without having to subscribe).

But I begin to wonder whether it should a bot’s task to forward the
[ANN]'s it sees on ruby-talk to a ruby-ann. Oh well, just a
thought…

Massimiliano (bard on IRC)

ZenTest and ZenWeb were just released. I announced these to several
lists including this one. I’m sure many of you got multiple
copies. I admit that is annoying. These releases announce my LAST
announcements to ruby-talk@. I’ll be announcing only to
announce@rubynet.org. I urge every developer releasing ruby
scripts, modules, or anyone having ruby-related events to use this
as your primary means of announcing your information. It will cut
down on volumes of email that we get and make it easier to focus on
the work at hand.

http://lists.rubynet.net/lists/listinfo/rubynet-announce

Hey Joel, sorry for picking on your email but you phrased everything
just perfectly in the right quantities.

I read this thread out of curiosity because I’m hosting the
announcement list, and the sentiments of the nay-sayers finally got to
me after a few hours of thinking about it. Immediately after I’d
finished reading my -talk mail, I archived my read or non-flagged
messages from ruby-talk and moved them into old-ruby-talk. To reply
to this message, I had to open up a mail spool with some 35K messages,
ALL of them -talk. I’m running a count of my mail spool at the
moment, I’ll post the # of messages I’ve received in the last year and
a half… it’s staggering and really sick, but, that frames my retort.
FWIW, 570979 msgs and in 18mo, that’s about 1043 emails a day. I
digress…

Unfortunately, subscribing to it will only increase the volume for
those of us who are staying on ruby-talk.

Honestly? I don’t really care. -talk is close to -chat. Most of the
35K emails to ruby I’ve scanned over because they don’t interest me.
Not to say that what people are saying isn’t interesting, just that
what they’re talking about has little relevance or bearing on my use
of Ruby.

And it will double the effort required to search archives. And it
will make it harder for newbies to understand how the community
works.

There’s truth to this however it hasn’t stopped PostgreSQL, FreeBSD,
Cyrus/sasl, MIT Kerberos, or any of the other zillions of other open
source projects. Google’s everyone’s friend, let’s just hope
archivers have sane robots.txt files and we’re all set. If this is a
big enough issue for folks, I’ll archive the relevant ruby lists that
folks have interest in and will write a search engine for them. This
shouldn’t be a prohibitive reason for branching out the number of ruby
related mailing lists.

Personally, I think ruby-talk is enough and don’t think list
proliferation is good for the community.

To the contrary, the lack of proliferation is bad for the community.
There is no notion of ‘on topic’ for -talk. If I’ve got a busy day,
which most seem to be, then I want to prioritize what it is that I’m
reading, listening to, or watching. I like FreeBSD’s structure for
mailing lists because it lets me tune out the mailing lists I don’t
have an interest in until I’ve got the time to read them. As is, the
only TV I watch is Law & Order (original), I listen to NPR while I’m
in the shower in the mornings, and that’s about the extent of media
exposure that I receive. Every now and then I’ll get a community news
paper in the mail, but I only glance at it as I’m walking to the
recycle bin. I like that I can filter and prioritize out all of the
discussion and bits in my world that I don’t care about. I know I’m
not alone.

With my developer hat on, I only use Ruby and C/Ruby. With my DBA hat
on, I only use PostgreSQL and BDB. As a sysadmin, it’s FreeBSD. I
work hard to be good at what I do and enjoy staying informed of what’s
going on in each of those communities. When I read my email, I read
it in the order of ‘inbox’, ‘cvs commit lists for projects I
maintain’, ‘cvs commit lists for the products I use’, ‘-announce
lists’, ‘-bug lists’, ‘-security lists’, ‘-bug lists’, ‘-hacker
lists’, ‘-admin lists’, ‘-audit’, ‘-arch’, and generic user lists some
where down at the bottom of the pile. -talk, however, doesn’t fit
nicely into that stratification. -talk is the bug list, is the
security list, is the -hacker list, is the -admin list, is -arch list,
and up until recently, used to be the -core list.

Honestly folks, I don’t care about what Larry Wall driveled out in an
attempt to promote Perl6 (and as a result stepped on Ruby) and I don’t
care about overloading methods or even private variables, sure they’d
both be nice to have, but the amount of time that I spend thinking
about ways of enhancing Ruby is close to 30sec out of every month.
Matz, Nobu, Guuy, and other folks have got a pretty good handle on
things and I just assume let them continue to work on the core ruby
interpreter and not fielding obtuse questions that, while interesting
to talk about and discuss and spawn some very interesting discussions,
really only fill up my -talk box and take time for me to mark as read
while skimming the subjects.

I think that there are other people in the world who use ruby
commercially and aren’t on -talk (probably because of its volume and
they are time constrained). For the people who are are actively using
ruby in the work place, I bet dime to dollar they would have a HUGE
interest in a thread about a bug that shows up in tight iterations
wherein the GC that leaks 4bytes every GC sweep and corrupts memory in
adjacent memory addresses. Just yesterday I did well over a million
dynamic page views using mod_ruby and inserted some 30M rows of
data… having this bug squashed is VERY valuable and interesting to
me and getting this in front of the people who are busy/using ruby
commercially would aid me and other ruby core developers in solving
the problem. As it stands, I think this bug has gone unreported
because no one who is pushing ruby to its limits wants to deal with
the volume of -talk.

In any case, I would like to see the announcements. Is it possible
to automatically forward from rubynet-announce to ruby-talk? Then
people could choose whether to subscribe to one or the other,
without missing anything, and without getting duplicates.

Absolutely… the duplicates issue is a tad tough to manage though.

Also, about the name: some people might get the impression that the
rubynet-announce list is for announcements related to the rubynet
project. Why not call it ruby-announce?

rubynet’s getting bigger in its scope. rubynet is just a network of
ruby services, it’s not limited to just the rubynet
module/package/CPAN project. That said, I will gladly setup new
mailing lists for any interested ruby users. I will set the lists up
under any one of the following domains (this is not limited to English
speaking lists!!! fr, ru, jp, mx, es, etc. are all very very
welcome!):

rubynet.(net|org)
rubydoc.(net|org)
rubydev.org
ruby-support.org

I’d like to second zenspider’s plea to have developers use the
announcement list for announcing modules, etc. Here are the two lists
that I imagine are of use to people at the moment:

List: announce@rubynet.org
Subscribe: http://lists.rubynet.org/lists/listinfo/rubynet-announce
Archives: http://lists.rubynet.org/lists/listinfo/rubynet-announce

List: developers@ruby-support.org
Subscribe: http://lists.ruby-support.com/lists/listinfo/ruby-developers
Archives: http://lists.ruby-support.com/pipermail/ruby-developers

I’d like to startup a lists dealing with, but not limited to XML, XSL,
network programming, and database usage. Please let me know
(privately) if you have an interest in said topics and mailing lists
on each.

-sc

PS Again, this isn’t to say that -talk doesn’t host wonderful
discussions about development, programming, or other obtuse
discussions.

···


Sean Chittenden

What I do wish we could get rid of are the
posts by people who think they can improve
Ruby by dragging it in a direction other
than what Matz has in mind, i.e., by making
it more like Java or COBOL or whatever.
These are what really make me tired. Even
more so than the occasional spam email we get.

That’s a bit harsh. I agree it’s a bit irritating, but only a bit, and
it’s
natural. If we had some good documents (FAQ? Wiki?) summarising the
discussions, they could be used to stop repeating them … again. They’d
be
interesting documents too.

Yes, probably a bit harsh. Sorry if anyone was
offended, as I was not referring to any specific
individual.

I have had a bad week, and I was very tired when
I wrote this. And as for wanting to make changes
to Ruby, I have done the same thing.

I do like to keep the discussion of changing
Ruby down to less than 50% of the message traffic.
Ruby is very powerful as-is. I prefer to spend
time using tools to build, as opposed to worrying
about the exact color and texture of the hand-grip
on the hammer. But that is a bad analogy, as I am
very interested in theory and in language design.
I’ve pulled a muscle or something and my shoulder
hurts like the devil. I should just be quiet now.

Hal

···

----- Original Message -----
From: “Gavin Sinclair” gsinclair@soyabean.com.au
To: “ruby-talk ML” ruby-talk@ruby-lang.org
Sent: Sunday, September 29, 2002 4:55 AM
Subject: Re: announce@ == less email (FAQ item?)

From: “Hal E. Fulton” hal9000@hypermetrics.com

From: “Ryan Davis” ryand-ruby@zenspider.com

ZenTest and ZenWeb were just released. I announced these to several
lists including this one. I’m sure many of you got multiple copies. I
admit that is annoying. These releases announce my LAST announcements
to ruby-talk@. I’ll be announcing only to announce@rubynet.org. I urge
every developer releasing ruby scripts, modules, or anyone having
ruby-related events to use this as your primary means of announcing
your information. It will cut down on volumes of email that we get and
make it easier to focus on the work at hand.

[elision]

I, for one, will continue announcing to
ruby-talk (not that I have ever made many
announcements); and I hope that everyone
else will also. I don’t want to subscribe
to yet another mailing list, and I don’t
want to miss announcements either.

I too question the value of a separate list. Announcements don’t take up much
room in this list. There’s no need for duplicate emails: just send them all to
ruby-talk. I can’t conceive of anybody wanting to read announcements only. If
they’re not subscribed here, they’re probably not into mailing lists. Also,
what happens to follow-up discussion of announcements?

I don’t mind the announcements disappearing, per se. As long as they get
reported in the Weekly News.

Okay, here’s the rub. Announcements not made to this list are much less
likely to make it into RWN (at this point). I’d love to bring in
announcements, interesting threads, etc. from other sources, but 1) my
time to read other lists is limited and b) those other sources aren’t
always convenient (e.g…, they have no web archive).

I’d rather see announcements made here. (I’d also encourage people to
make annuoncements here, whether they be for group meetings, articles,
new software, or whatnot.)

-pate

···

On Sun, 29 Sep 2002, Gavin Sinclair wrote:

My personal opinion is that the announcements
are some of the most interesting and relevant
material on the list.

Hal

Gavin

Sean Chittenden wrote:
[…]

With my developer hat on, I only use Ruby and C/Ruby. With my DBA hat
on, I only use PostgreSQL and BDB. As a sysadmin, it’s FreeBSD. I
work hard to be good at what I do and enjoy staying informed of what’s
going on in each of those communities. When I read my email, I read
it in the order of ‘inbox’, ‘cvs commit lists for projects I
maintain’, ‘cvs commit lists for the products I use’, ‘-announce
lists’, ‘-bug lists’, ‘-security lists’, ‘-bug lists’, ‘-hacker
lists’, ‘-admin lists’, ‘-audit’, ‘-arch’, and generic user lists some
where down at the bottom of the pile. -talk, however, doesn’t fit
nicely into that stratification. -talk is the bug list, is the
security list, is the -hacker list, is the -admin list, is -arch list,
and up until recently, used to be the -core list.
[…]

I have to totally agree. When I first started using ruby I subscribed
to -talk and was blown away by the volume of mail. I even use different
email addresses to subscribe to most lists so it’s all broken up into
folders for me already, but even then there’s too much information for
me to parse. I just can’t make myself even skim all the subjects - I
get too bored about half way through and just mark all as read. My
solution at the moment is to filter this mailing list and only allow
messages through with certain keywords like “web”, “XML”, etc. But this
sucks because sometimes partial threads come through, plus I get, for
example, all of David’s messages since he has “web” in his sig :smiley:

It’s very easy for someone who wants to read every single message about
ruby to subscribe to multiple lists… it takes maybe a few minutes of
their life, once. For the 95% of people who have more limited
interests, it is difficult or even impossible to select only messages
that are related to certain topics unless the lists are split up.

Having one mailing list is like having lossy storage. The user who
sends the message knows what their email is about, but as soon as they
send that to the One Big Mailing List, that information is lost in a
form that computers can understand. I can now no longer use a computer
to categorize the mail for me. If it’s split into separate lists, I can
merge all the lists into one folder and there is no difference, but I
now have the option of using that meta-information (what list the mail
was in) to make some decisions. Always hold on to potentially-useful
information until the last possible moment.

Julian

···


julian@beta4.com
Beta4 Productions (http://www.beta4.com)

[…]
-talk is close to -chat. Most of the
35K emails to ruby I’ve scanned over because they don’t interest me.
[…]
To the contrary, the lack of proliferation is bad for the community.
There is no notion of ‘on topic’ for -talk.
[…]
Honestly folks, I don’t care about what Larry Wall driveled out in an
attempt to promote Perl6 (and as a result stepped on Ruby) and [more],
but the amount of time that I spend thinking
about ways of enhancing Ruby is close to 30sec out of every month.
[…]
I think that there are other people in the world who use ruby
commercially and aren’t on -talk (probably because of its volume and
they are time constrained).
[…]
Absolutely… the duplicates issue is a tad tough to manage though.
[…]
I’d like to second zenspider’s plea to have developers use the
announcement list for announcing modules, etc. Here are the two lists
that I imagine are of use to people at the moment:

WOW! I was going to go through all of the replies and give a piece of
my mind to one and all of them, but I really truly couldn’t have said
it better than you have. You clearly iterated every point I thought up
today and quite a few more.

Quite simply, the list is growing well beyond it’s means of management
(reader’s perspective):

Post # YYYY-MM Span
00,001 1998-12
10,000 2001-01 25 mo
20,000 2001-08 7 mo
30,000 2002-02 6 mo
40,000 2002-05 3 mo
50,000 2002-09 4 mo

50k was early THIS MONTH, and we are already 1/5th through to 60k! The
list needs to be split up so that people can pick and choose what they
want to subscribe to. It won’t increase the amount of email that people
get, and even if it did, I guarantee you that it’s less than .01% of
the current traffic in -talk!

Personally, I too don’t give a hoot about extending ruby for the sake
of extending ruby. A brief glance at the archives tell me that a vast
MINORITY of the list DO care about extending ruby. Why should all of us
have to wade through what the minority want to talk about in volume?
Because we don’t have a choice. announce@ is the first step in giving
people a choice.

I’d love to have the list moved over to ruby-lang.org and be a
sanctioned list. Matz was the first person to subscribe to announce@
after it was announced, so I doubt he’d mind all that much. I’d also
love it if we could do that in such a way that Sean can donate some of
his bandwidth into helping out (maybe lists.ruby-lang.org?).

···

On Monday, September 30, 2002, at 05:21 PM, Sean Chittenden wrote:

List: announce@rubynet.org
Subscribe: http://lists.rubynet.org/lists/listinfo/rubynet-announce
Archives: http://lists.rubynet.org/lists/listinfo/rubynet-announce

List: developers@ruby-support.org
Subscribe: http://lists.ruby-support.com/lists/listinfo/ruby-developers
Archives: http://lists.ruby-support.com/pipermail/ruby-developers

Hi Hal,

As this newsgroup is not moderated, I guess it is rather difficult to
completely prevent certain types of topics. I see several options that
can be taken:

  1. We just create a new rule, we put it in the FAQ, that these topics are
    not welcomed.

  2. We summarize all the ever existing discussions regarding those topics,
    and any new mention of these topics can simply be redirected to the FAQ.

  3. The title of the thread should be clear. People not interested in
    these topics can simply skip them. I myself do not read every post, if
    the title is not relevant.

  4. Probably Matz can more clearly state his opinion, whether a discussion
    topic is futile or not. If Matz is positive that a topic is not relavant
    to Ruby, then the affected people should find a new channel beside
    comp.lang.ruby.

I am sorry if some of the topics bothered you.

Regards,

Bill

···

===========================================================================
Hal E. Fulton hal9000@hypermetrics.com wrote:

I do like to keep the discussion of changing
Ruby down to less than 50% of the message traffic.
Ruby is very powerful as-is. I prefer to spend
time using tools to build, as opposed to worrying
about the exact color and texture of the hand-grip
on the hammer. But that is a bad analogy, as I am
very interested in theory and in language design.
I’ve pulled a muscle or something and my shoulder
hurts like the devil. I should just be quiet now.

OK, these arguments have persuaded me. It’s reasonable to have some new lists.
I just plead for sanity in their creation. They should be kept together (at
ruby-lan.org) and created in an organized way. The ultimate documentation for
what gets posted where will end up in the FAQ. This information should be
concise, coherent and sensible.

An announcement list is sensible, but it should have the appearance of official
sanction, not just be created on an arbitrary site. If the future FAQ entry
about mailing lists looks inconsistent, it reflects poorly on the maturity of
the community and ultimately the language.

Another benefit of lists being grouped is that subscriptions can be managed
more easily.

Just as it takes a few minutes to subscribe to multi[ple lists, it takes a few
minutes to create those lists sensibly.

Just my AU$0.04

Gavin

···

----- Original Message -----
From: “Julian Fitzell” julian@beta4.com

Sean Chittenden wrote:
[…]

With my developer hat on, I only use Ruby and C/Ruby. With my DBA hat
on, I only use PostgreSQL and BDB. As a sysadmin, it’s FreeBSD. I
work hard to be good at what I do and enjoy staying informed of what’s
going on in each of those communities. When I read my email, I read
it in the order of ‘inbox’, ‘cvs commit lists for projects I
maintain’, ‘cvs commit lists for the products I use’, ‘-announce
lists’, ‘-bug lists’, ‘-security lists’, ‘-bug lists’, ‘-hacker
lists’, ‘-admin lists’, ‘-audit’, ‘-arch’, and generic user lists some
where down at the bottom of the pile. -talk, however, doesn’t fit
nicely into that stratification. -talk is the bug list, is the
security list, is the -hacker list, is the -admin list, is -arch list,
and up until recently, used to be the -core list.
[…]

It’s very easy for someone who wants to read every single message about
ruby to subscribe to multiple lists… it takes maybe a few minutes of
their life, once. For the 95% of people who have more limited
interests, it is difficult or even impossible to select only messages
that are related to certain topics unless the lists are split up.

[…]

Julian

OOPS! Bad editing on my part. Sorry, I was trying to post before
midnight. See correct edit below:

···

On Monday, September 30, 2002, at 11:48 PM, Ryan Davis wrote:

50k was early THIS MONTH, and we are already 1/5th through to 60k! The
list needs to be split up so that people can pick and choose what they
want to subscribe to. [[announce@]] won’t increase the amount of email
that people get, and even if it did, I guarantee you that it’s less
than .01% of the current traffic in -talk!

Hi Julian,

This is the exact reason the Ruby Weekly News was started at Phil Tomson’s
suggestion almost a year ago. Sure we don’t meet everyone interest in a
topic, but we try and catch all the announcements, and we try and write about
things that we find interesting (which doesn’t include Larry Wall :slight_smile:


Signed,
Holden Glova

···

On Tue, 01 Oct 2002 13:04, Julian Fitzell wrote:

Sean Chittenden wrote:
[…]

With my developer hat on, I only use Ruby and C/Ruby. With my DBA hat
on, I only use PostgreSQL and BDB. As a sysadmin, it’s FreeBSD. I
work hard to be good at what I do and enjoy staying informed of what’s
going on in each of those communities. When I read my email, I read
it in the order of ‘inbox’, ‘cvs commit lists for projects I
maintain’, ‘cvs commit lists for the products I use’, ‘-announce
lists’, ‘-bug lists’, ‘-security lists’, ‘-bug lists’, ‘-hacker
lists’, ‘-admin lists’, ‘-audit’, ‘-arch’, and generic user lists some
where down at the bottom of the pile. -talk, however, doesn’t fit
nicely into that stratification. -talk is the bug list, is the
security list, is the -hacker list, is the -admin list, is -arch list,
and up until recently, used to be the -core list.

[…]

I have to totally agree. When I first started using ruby I subscribed
to -talk and was blown away by the volume of mail.

Hi,

Actually I am thinking that if this “off-Ruby” topics traffic volume does
not decrease, should we create another group such as
“comp.lang.ruby.internals”, or “comp.lang.ruby.misc”, or
“comp.lang.ruby.beyond”? Here we can discuss possible Ruby enhancements,
Ruby’s C world, and/or anything that is beyond the current standard
“Ruby” (that is, beyond its current syntax and beyond its current object
model).

Regards,

Bill

···

===========================================================================
William Djaja Tjokroaminata billtj@z.glue.umd.edu wrote:

As this newsgroup is not moderated, I guess it is rather difficult to
completely prevent certain types of topics. I see several options that
can be taken:

  1. We just create a new rule, we put it in the FAQ, that these topics are
    not welcomed.
  1. We summarize all the ever existing discussions regarding those topics,
    and any new mention of these topics can simply be redirected to the FAQ.
  1. The title of the thread should be clear. People not interested in
    these topics can simply skip them. I myself do not read every post, if
    the title is not relevant.
  1. Probably Matz can more clearly state his opinion, whether a discussion
    topic is futile or not. If Matz is positive that a topic is not relavant
    to Ruby, then the affected people should find a new channel beside
    comp.lang.ruby.

Gavin Sinclair wrote:
[…]

An announcement list is sensible, but it should have the appearance of official
sanction, not just be created on an arbitrary site. If the future FAQ entry
about mailing lists looks inconsistent, it reflects poorly on the maturity of
the community and ultimately the language.

Another benefit of lists being grouped is that subscriptions can be managed
more easily.
[…]

Agreed.

I realized just as I hit send that I hadn’t added my opinion that all
the mailing lists should be hosted in one place with a consistent naming
scheme. I wouldn’t want to see mailing lists scattered all over the
place so you can’t find them.

Julian

···


julian@beta4.com
Beta4 Productions (http://www.beta4.com)

[…]

With my developer hat on, I only use Ruby and C/Ruby. With my DBA hat
on, I only use PostgreSQL and BDB. As a sysadmin, it’s FreeBSD. I
work hard to be good at what I do and enjoy staying informed of what’s
going on in each of those communities. When I read my email, I read
it in the order of ‘inbox’, ‘cvs commit lists for projects I
maintain’, ‘cvs commit lists for the products I use’, ‘-announce
lists’, ‘-bug lists’, ‘-security lists’, ‘-bug lists’, ‘-hacker
lists’, ‘-admin lists’, ‘-audit’, ‘-arch’, and generic user lists some
where down at the bottom of the pile. -talk, however, doesn’t fit
nicely into that stratification. -talk is the bug list, is the
security list, is the -hacker list, is the -admin list, is -arch list,
and up until recently, used to be the -core list.
[…]

It’s very easy for someone who wants to read every single message
about ruby to subscribe to multiple lists… it takes maybe a few
minutes of their life, once. For the 95% of people who have more
limited interests, it is difficult or even impossible to select
only messages that are related to certain topics unless the lists
are split up.

[…]

OK, these arguments have persuaded me. It’s reasonable to have some
new lists. I just plead for sanity in their creation. They should
be kept together (at ruby-lan.org) and created in an organized way.
The ultimate documentation for what gets posted where will end up in
the FAQ. This information should be concise, coherent and sensible.

I’m inclined to agree myself and need to take fault for not talking
with Matz or anyone else at Netlab for seeing if this was possible.
I’m very willing and able to transfer subscriber lists to
ruby-lang.org if that is setup (maybe just a mail alias for
listname@ruby-lang.org and setup the appropriate mx records to point
to my list servers. Just a thought since I’ve got bandwidth and
resources I’m willing to donate to ruby). The flip side of the topic
is, there’s something to be said for having a non-official list
because that lowers the bar for what can be considered an announcement
or makes it easier to fire up a discussion list about various topics.
Announcements coming from ruby-lang.org carry some weight in terms of
their officialness and the consequences of the announcement.
Rhetorical question: would you guys like ruby-lang.org to be a hub of
social and community events? If so, that’s additional resources and
burdens that would be placed on Matz and other folk who help
administer the netlab servers. I, for one, would like to see their
time spent on Ruby and not on mailing lists or worrying about
community events… but then again, I’m biased and have an interest in
time being spent on Rite. ::grin::

An announcement list is sensible, but it should have the appearance
of official sanction, not just be created on an arbitrary site. If
the future FAQ entry about mailing lists looks inconsistent, it
reflects poorly on the maturity of the community and ultimately the
language.

There’s definitely truth to that and I won’t argue with it one bit.

Another benefit of lists being grouped is that subscriptions can be
managed more easily.

Agreed… but, the flip side being that rubynet could be a general
community site that handles the off topic, non-interpreter lists.

Just as it takes a few minutes to subscribe to multi[ple lists, it
takes a few minutes to create those lists sensibly.

Not disagreeing there. -sc

···


Sean Chittenden