[#41431] [ruby-trunk - Bug #5694][Open] Proc#arity doesn't take optional arguments into account. — Marc-Andre Lafortune <ruby-core@...>

27 messages 2011/12/01
[#41442] [ruby-trunk - Bug #5694] Proc#arity doesn't take optional arguments into account. — Thomas Sawyer <transfire@...> 2011/12/01

[#41443] Re: [ruby-trunk - Bug #5694] Proc#arity doesn't take optional arguments into account. — Yehuda Katz <wycats@...> 2011/12/01

Maybe we can add a new arity_range method that does this?

[#41496] [ruby-trunk - Bug #5714][Open] Unexpected error of STDIN#read with non-ascii input on Windows XP — Heesob Park <phasis@...>

22 messages 2011/12/06

[#41511] [ruby-trunk - Bug #5719][Open] Hash::[] can't handle 100000+ args — Nick Quaranto <nick@...>

13 messages 2011/12/07

[#41557] [ruby-trunk - Bug #5730][Open] Optinal block parameters assigns wrong — Yukihiro Matsumoto <matz@...>

14 messages 2011/12/08

[#41586] [ruby-trunk - Feature #5741][Open] Secure Erasure of Passwords — Martin Bosslet <Martin.Bosslet@...>

17 messages 2011/12/10

[#41672] [ruby-trunk - Feature #5767][Open] Cache expanded_load_path to reduce startup time — Yura Sokolov <funny.falcon@...>

13 messages 2011/12/15

[#41681] Documentation of the language itself (syntax, meanings, etc) — Rodrigo Rosenfeld Rosas <rr.rosas@...>

Since Ruby is built on top of simple concepts, most of the documentation

23 messages 2011/12/15
[#41683] Re: Documentation of the language itself (syntax, meanings, etc) — Gary Wright <gwtmp01@...> 2011/12/15

[#41686] Re: Documentation of the language itself (syntax, meanings, etc) — Rodrigo Rosenfeld Rosas <rr.rosas@...> 2011/12/16

Em 15-12-2011 19:23, Gary Wright escreveu:

[#41717] Feature : optional argument in File.join — Michel Demazure <michel@...>

In Windows, when using File.join, one often ends with a path containing

13 messages 2011/12/19
[#41719] Re: Feature : optional argument in File.join — Luis Lavena <luislavena@...> 2011/12/19

On Mon, Dec 19, 2011 at 6:09 AM, Michel Demazure <michel@demazure.com> wrote:

[#41720] Re: Feature : optional argument in File.join — Michel Demazure <michel@...> 2011/12/19

Luis Lavena wrote in post #1037331:

[#41728] [ruby-trunk - Feature #5781][Open] Query attributes (attribute methods ending in `?` mark) — Thomas Sawyer <transfire@...>

15 messages 2011/12/19

[#41799] Best way to separate implementation specific code? — Luis Lavena <luislavena@...>

Hello,

15 messages 2011/12/24
[#41800] Re: Best way to separate implementation specific code? — KOSAKI Motohiro <kosaki.motohiro@...> 2011/12/24

2011/12/24 Luis Lavena <luislavena@gmail.com>:

[#41811] Re: Best way to separate implementation specific code? — "U.Nakamura" <usa@...> 2011/12/26

Hello,

[#41817] Re: Best way to separate implementation specific code? — Luis Lavena <luislavena@...> 2011/12/26

On Sun, Dec 25, 2011 at 10:51 PM, U.Nakamura <usa@garbagecollect.jp> wrote:

[#41812] [ruby-trunk - Feature #5809][Open] Benchmark#bm: remove the label_width parameter — Benoit Daloze <redmine@...>

11 messages 2011/12/26

[ruby-core:41691] Ruby IRC Presence Problem

From: Eero Saynatkari <ruby-ml@...>
Date: 2011-12-16 05:35:23 UTC
List: ruby-core #41691
Hi,

As some of you may remember, Ruby's IRC situation is slightly problematic, but recent developments offer a slightly simpler way of resolving the situation.

TL;DR: Matz or a designated representative should assert rights over the #ruby channel.


The Problem
==========

I've tried to condense as much as possible. Please ask if anything's unclear.

As designated on http://ruby-lang.org/en/community/, the official channel is #ruby-lang on Freenode. 

Unfortunately around the same time, a channel named #ruby was also created, and it was/is run mostly by people who had gotten banned from #ruby-lang.

Many new people will automatically go to #ruby, assuming that it is the correct place. This was not a problem until 2008 or so because #ruby was gracious enough to use their /topic to redirect people to #ruby-lang. At some point, however, #ruby removed the redirect and used other questionable means to retain people on their channel (such as telling people that #ruby-lang was for language internals discussion).

The current situation is that both channels have some 300 unique users. I personally find this quite vexing, as it leads to unnecessary fragmentation and duplication of information. I do not have anything against there being two Ruby channels, just that the separation is artificial and based on false premises.

Freenode's policy is that only official channels may use the single hash namespace, but #ruby cannot be reassigned to ##ruby (for example) without authorization because it's been around for some time.


Solutions
=======

There are three possible solutions:

1. Do nothing, and let the fragmentation continue.

2. Designate #ruby as the official channel (incl. on ruby-lang.org), and have everyone move there by default. The problem is that the channel ownership is lost, and in hands of a questionable history.

3. Assert rights on the #ruby namespace. This allows the unofficial #ruby channel to be renamed ##ruby, and then either the name #ruby can be redirected to #ruby-lang, or #ruby-lang can be renamed.

Fortunately Freenode has made obtaining the rights a bit easier than it was previously[1]. It can be done by filling out the group registration form[2], either by Matz or a designated representative (perhaps for example David A. Black or Eric Hodel, who are the registrants for #ruby-lang?).

[1] http://freenode.net/group_registration.shtml
[2] http://freenode.net/group_registration_form.php 


I'd very much like to get opinions on the matter. Thanks!



In This Thread

Prev Next