FreeBSD’s got a decent setup. Few additions to the list here:
Here are just a few suggestions of mail lists
(Most of these are not original, but come from other
groups I have seen, eg, FreeBSD)
cvs Changes made to the source tree
ruby-advocacy Ruby Evangelism
ruby-announce Important events and project milestones
ruby-arch Architecture and design discussions
ruby-bugs Bug reports
^^^^^^^^^
It’d be nice if this were a subscribable list w/ archives, I’m sure
that’s where I would’ve found a bit about mark/sweep in the past. 
ruby-chat Non-technical items related to the Ruby community
ruby-config Development of Ruby installation and configuration tools
ruby-core Discussion concerning RCR’s and patches for Ruby
ruby-docs Discussion concerning Ruby and library documentation
ruby-jobs Ruby employment and consulting opportunities
ruby-newbies New Ruby users activities and discussions
ruby-questions User questions and technical support
ruby-security Security issues
ruby-test Where to send your test messages instead of one of the actual lists
ruby-www Issues for using Ruby with http servers
Few more to suggest:
ruby-performance
ruby-xml
ruby-database
ruby-gui
ruby-extending
ruby-embedding
Those are good additions. We may however want to consolidate and keep
the list count under 30.
I know this’d spread things thin… but would that necessarily be a
bad thing? I’m sure many people would be on all of the lists, myself
included, but the important thing would be that they could prioritize
their time accordingly. -sc
The thinner the better. That gives me the ability to subscribe
and un-subscribe as my interests change and keep my inbox below
200 emails a day.
PS If in one weeks time I haven’t heard of any objections, I will
wholesale create all of these lists above plus any other suggested
lists and toss them on rubynet.org along with an updated site and
links pointing to all of the lists, descriptions of the lists, and
archives. Searchable archives I’ll be able to have up in a week or so
after that.
Personally, I would be very hesitant to subscribe to a non ruby-lang
authorized list. I would much rather see this driven by ruby-lang.
I feel the longevity would be more certain and searching/archiving would
be more consistent.
···
On Wed, Oct 02, 2002 at 04:29:33AM +0900, Sean Chittenden wrote:
–
Sean Chittenden
–
Jim Freeze
Programming Ruby
def initialize; fun; end
A language with class
Rather than debate lsit splitting, which is already a reality anyway,
someone please focus on (or provide) a one-stop source for subscribing
to all of the lists of one’s choice. One should not have to go all over
the net to find out about and subscribe to (if they choose) the lists
they want or need to be on. 
Regards,
W. Kent Starr
···
On Tue, 2002-10-01 at 15:29, Sean Chittenden wrote:
FreeBSD’s got a decent setup. Few additions to the list here:
Here are just a few suggestions of mail lists
(Most of these are not original, but come from other
groups I have seen, eg, FreeBSD)
cvs Changes made to the source tree
ruby-advocacy Ruby Evangelism
ruby-announce Important events and project milestones
ruby-arch Architecture and design discussions
ruby-bugs Bug reports
^^^^^^^^^
It’d be nice if this were a subscribable list w/ archives, I’m sure
that’s where I would’ve found a bit about mark/sweep in the past.
ruby-chat Non-technical items related to the Ruby community
ruby-config Development of Ruby installation and configuration tools
ruby-core Discussion concerning RCR’s and patches for Ruby
ruby-docs Discussion concerning Ruby and library documentation
ruby-jobs Ruby employment and consulting opportunities
ruby-newbies New Ruby users activities and discussions
ruby-questions User questions and technical support
ruby-security Security issues
ruby-test Where to send your test messages instead of one of the actual lists
ruby-www Issues for using Ruby with http servers
Few more to suggest:
ruby-performance
ruby-xml
ruby-database
ruby-gui
ruby-extending
ruby-embedding
I know this’d spread things thin… but would that necessarily be a
bad thing? I’m sure many people would be on all of the lists, myself
included, but the important thing would be that they could prioritize
their time accordingly. -sc
PS If in one weeks time I haven’t heard of any objections, I will
wholesale create all of these lists above plus any other suggested
lists and toss them on rubynet.org along with an updated site and
links pointing to all of the lists, descriptions of the lists, and
archives. Searchable archives I’ll be able to have up in a week or so
after that.
–
Sean Chittenden
Hi All,
I see a lot of these discussions, and to me personally, they are good
signs of Ruby’s “growing pains”. But really, they are good signs that
more and more people find that Ruby is useful and practical.
On the practical side, are there any official guidelines on what are
acceptable and unacceptable to be posted in this newsgroup?
If there are no, then probably the best (if not just simply the
easiest) way for now is if people can state the title of the thread
clearly. For instance, I don’t do web-related development at all, but
those discussions do not bother me; I just skip them and move on… 
Regards,
Bill
PS If in one weeks time I haven’t heard of any objections, I will
wholesale create all of these lists above plus any other suggested
lists and toss them on rubynet.org along with an updated site and
links pointing to all of the lists, descriptions of the lists, and
archives. Searchable archives I’ll be able to have up in a week
or so after that.
I believe there is already a question of whether such lists should
be hosted by ruby-lang.org. I would suggest that broad-topic lists
remain under the auspices of the ruby-lang.org umbrella, while
independent lists be reserved for application-specific topics (e.g.,
the DRuby or REXML lists).
Having the lists, regardless of where they are, is more important than
not having the lists. Transfering the domains/lists/subscribers is
easy, building the communties and diversifying the traffic is what’s
important. Getting the proof of concenpt done is important since
there seems to be some doubt as to its need. -sc
···
–
Sean Chittenden
Those are good additions. We may however want to consolidate and keep
the list count under 30.
Heh, I’d be inclined to have more, but there’s truth to what you say.
PS If in one weeks time I haven’t heard of any objections, I will
wholesale create all of these lists above plus any other suggested
lists and toss them on rubynet.org along with an updated site and
links pointing to all of the lists, descriptions of the lists, and
archives. Searchable archives I’ll be able to have up in a week
or so after that.
Personally, I would be very hesitant to subscribe to a non ruby-lang
authorized list. I would much rather see this driven by ruby-lang.
I feel the longevity would be more certain and searching/archiving would
be more consistent.
But you wouldn’t to a CPAN.org site if you were a perl user. Like
I said though, having the lists exist is more important than where
they exist. It’s not like this is a community coup or something.
There’s a decided vacuum in the list diversification realm for Ruby
and I’m addressing it. It’s a free market Internet in practice! When
there’s a need/vacuum/void, fill the need/vacuum/void. Deregulation
at a later date is always painful (see California’s former power
situation, the airlines industry, or any price controlled industry for
that matter). -sc
···
–
Sean Chittenden
As I ponder over the list of topics below, I wonder if people would be
interested in distributing the load of RWN? if each mailing list had 1-3
‘correspondents’, a much more detailed RWN could be cooperatively produced
… any thoughts?
-pate
···
On Wed, 2 Oct 2002, Jim Freeze wrote:
On Wed, Oct 02, 2002 at 04:29:33AM +0900, Sean Chittenden wrote:
FreeBSD’s got a decent setup. Few additions to the list here:
Here are just a few suggestions of mail lists
(Most of these are not original, but come from other
groups I have seen, eg, FreeBSD)
cvs Changes made to the source tree
ruby-advocacy Ruby Evangelism
ruby-announce Important events and project milestones
ruby-arch Architecture and design discussions
ruby-bugs Bug reports
^^^^^^^^^
It’d be nice if this were a subscribable list w/ archives, I’m sure
that’s where I would’ve found a bit about mark/sweep in the past.
ruby-chat Non-technical items related to the Ruby community
ruby-config Development of Ruby installation and configuration tools
ruby-core Discussion concerning RCR’s and patches for Ruby
ruby-docs Discussion concerning Ruby and library documentation
ruby-jobs Ruby employment and consulting opportunities
ruby-newbies New Ruby users activities and discussions
ruby-questions User questions and technical support
ruby-security Security issues
ruby-test Where to send your test messages instead of one of the actual lists
ruby-www Issues for using Ruby with http servers
Few more to suggest:
ruby-performance
ruby-xml
ruby-database
ruby-gui
ruby-extending
ruby-embedding
Those are good additions. We may however want to consolidate and keep
the list count under 30.
I know this’d spread things thin… but would that necessarily be a
bad thing? I’m sure many people would be on all of the lists, myself
included, but the important thing would be that they could prioritize
their time accordingly. -sc
The thinner the better. That gives me the ability to subscribe
and un-subscribe as my interests change and keep my inbox below
200 emails a day.
PS If in one weeks time I haven’t heard of any objections, I will
wholesale create all of these lists above plus any other suggested
lists and toss them on rubynet.org along with an updated site and
links pointing to all of the lists, descriptions of the lists, and
archives. Searchable archives I’ll be able to have up in a week or so
after that.
Personally, I would be very hesitant to subscribe to a non ruby-lang
authorized list. I would much rather see this driven by ruby-lang.
I feel the longevity would be more certain and searching/archiving would
be more consistent.
–
Sean Chittenden
–
Jim Freeze
Programming Ruby
def initialize; fun; end
A language with class
As I ponder over the list of topics below, I wonder if people would
be interested in distributing the load of RWN? if each mailing list
had 1-3 ‘correspondents’, a much more detailed RWN could be
cooperatively produced … any thoughts?
I’d be down for doing that on the lists that I had a key interest in.
Would there be any interest in having me toss out a small scheduling
app that’d help ensure that there was someone on duty for each list?
I know there are times that I go dark and would need to pass the hat
to the next person in line. -sc
···
–
Sean Chittenden
[James:]
I believe there is already a question of whether such lists should
be hosted by ruby-lang.org. I would suggest that broad-topic lists
remain under the auspices of the ruby-lang.org umbrella, while
independent lists be reserved for application-specific topics (e.g.,
the DRuby or REXML lists).
Having the lists, regardless of where they are, is more important than
not having the lists. Transfering the domains/lists/subscribers is
easy, building the communties and diversifying the traffic is what’s
important. Getting the proof of concenpt done is important since
there seems to be some doubt as to its need. -sc
–
Sean Chittenden
You are correct, but heed the warning of community fragmentation caused by
disorganised lists. I know you want to “organise” the lists, but if you do it
in haste, as a proof-of-concept-that-becomes-production, then they will in fact
be disorganised.
My kind of organisation:
- all lists under same umbrella (logical; surely bandwidth can be
appropriated without changing names?)
- single web page to manage all subscriptions
- consistent archive/search interface
I personally would like to see many (15? 20?) lists as described in other
posts, subscribe to them all, have them go to separate folders, and then manage
the subscriptions to prevent email overflow.
Being able to do this would achieve a great deal of organisation while
maintaining the stength of community.
Your points about deregulation etc. are well made, but we are talking about a
community here, not a set of competing profit-making organisations. A little
planning (and only a little) will serve us well.
Gavin
···
From: “Sean Chittenden” sean@chittenden.org
I’d be happy to help out with that.
···
On Tuesday, October 1, 2002, at 01:45 PM, Pat Eyler wrote:
As I ponder over the list of topics below, I wonder if people would be
interested in distributing the load of RWN? if each mailing list had
1-3
‘correspondents’, a much more detailed RWN could be cooperatively
produced
… any thoughts?
As I ponder over the list of topics below, I wonder if people would
be interested in distributing the load of RWN? if each mailing list
had 1-3 ‘correspondents’, a much more detailed RWN could be
cooperatively produced … any thoughts?
I’d be down for doing that on the lists that I had a key interest in.
Would there be any interest in having me toss out a small scheduling
app that’d help ensure that there was someone on duty for each list?
I know there are times that I go dark and would need to pass the hat
to the next person in line. -sc
scheduling would be one part. collecting, verifying, collating, and
forwarding the XML to the processor (or processing it locally) would be
the second (and bigger) bit.
Of course, it would all hinge on a) the current RWN crew buying in, and
b) finding enough people to step up to the plate.
-pate
···
On Wed, 2 Oct 2002, Sean Chittenden wrote:
–
Sean Chittenden
As I ponder over the list of topics below, I wonder if people would
be interested in distributing the load of RWN? if each mailing list
had 1-3 ‘correspondents’, a much more detailed RWN could be
cooperatively produced … any thoughts?
I’d be down for doing that on the lists that I had a key interest in.
Would there be any interest in having me toss out a small scheduling
app that’d help ensure that there was someone on duty for each list?
I know there are times that I go dark and would need to pass the hat
to the next person in line. -sc
I think I would just rather have the digest option for each list.
···
On Wed, Oct 02, 2002 at 05:48:25AM +0900, Sean Chittenden wrote:
–
Sean Chittenden
–
Jim Freeze
Programming Ruby
def initialize; fun; end
A language with class
[James:]
I believe there is already a question of whether such lists should
be hosted by ruby-lang.org. I would suggest that broad-topic lists
remain under the auspices of the ruby-lang.org umbrella, while
independent lists be reserved for application-specific topics (e.g.,
the DRuby or REXML lists).
Having the lists, regardless of where they are, is more important
than not having the lists. Transfering the
domains/lists/subscribers is easy, building the communties and
diversifying the traffic is what’s important. Getting the proof
of concenpt done is important since there seems to be some doubt
as to its need. -sc
You are correct, but heed the warning of community fragmentation
caused by disorganised lists. I know you want to “organise” the
lists, but if you do it in haste, as a
proof-of-concept-that-becomes-production, then they will in fact be
disorganised.
Point taken. Offline I’ve gotten very positive feedback for taking
the initiative and championing the topic… the reception hasn’t been
quite as warm on -talk, but still, point is taken.
My kind of organisation:
- all lists under same umbrella (logical; surely bandwidth can be
appropriated without changing names?)
- single web page to manage all subscriptions
- consistent archive/search interface
I personally would like to see many (15? 20?) lists as described in
other posts, subscribe to them all, have them go to separate
folders, and then manage the subscriptions to prevent email
overflow.
Being able to do this would achieve a great deal of organisation
while maintaining the stength of community.
::nods:: Toss me an email in private if you have ideas on how to do
this. I’m thinking mailman/majordomo needs a competitor from the Ruby
arena. I know seattle.rb has something in the works, but I don’t know
what its state is.
Your points about deregulation etc. are well made, but we are
talking about a community here, not a set of competing profit-making
organisations. A little planning (and only a little) will serve us
well.
I was wondering when someone would call a fault in those statements.
-sc
···
–
Sean Chittenden
