[ruby-core:54293] Re: Encouraging use of CommonRuby

I have filed an issue with my proposal here:
https://bugs.ruby-lang.org/issues/8271

I am more than happy to discuss and justify my proposal as well as
making changes.

- Charlie

On Mon, Apr 15, 2013 at 7:49 AM, NARUSE, Yui <[e-mail]> wrote:
> (2013/04/15 19:32), "Martin J. D=C3=BCrst" wrote:
>> On 2013/04/13 0:56, Charles Oliver Nutter wrote:
>>> On Fri, Apr 12, 2013 at 8:08 AM, NARUSE, Yui<[e-mail]>  wrote:
>>>> I introduced CommonRuby as where people discuss about a Ruby Standard,
>>>> but I hadn't say anything more than it.
>>>> Matz also hadn't.
>>
>> It would be good to clarify that.
>
> The man who really decide it is matz, not me.
> And matz hadn't say the detail.
> Therefore someone should suggest a proposal.
>
> headius partially proposed it and I objected some parts of it.
>
>>>> Where I should create a ticket is a frequent question on OSS projects.
>>>> You may know sometimes people make CRuby bug report on Customized vers=
ion of Redmine,
>>>> www.ruby-lang.org, and CommonRuby project though there are description=
s.
>>>> This is because Backport trackers is such a cryptic name like Backport=
 193.
>>>>
>>>> I hesitate to add more complexity here.
>>
>> I don't think we need more complexity. But currently, the various pages =
of Redmine that list projects are out of sync and/or otherwise not up to da=
te. Improving the text there will make it much easier for people to contrib=
ute to the right place.
>>
>> As some examples, http://bugs.ruby-lang.org/projects/ruby/wiki/HowtoRepo=
rt does not speak much about features. The top page (http://bugs.ruby-lang.=
org/) does not speak about features at all. http://bugs.ruby-lang.org/proje=
cts could be ordered much better.
>
> Anyone can write it.
>
>> By the way, can an issue be moved from one project to another? If not, t=
hen it may be better to keep features and bugs together so that it's easier=
 to change from one to the other. But then that's a problem in Redmine that=
 could/should be fixed.
>
> Yeah, backporting uses it.
> But its current management is bit troublesome.
>
> --
> NARUSE, Yui  <[e-mail]>
>