Misc #9503: Request for a Question and Answer section

• Status: Rejected
• Assignee: -

[sawa (Tsuyoshi Sawada)]

I often come up with a question regarding why Ruby is designed the way it is with respect to a certain specification. Without knowing why it was designed in that way, I usually start to feel that such thing should be in a different way, and I ask that as a feature on this site, but then, sometimes it is responded from the developers with a reason why it has to be the way it is.

When I have such question, I first try to look for answers about the design decision; especially, I am a frequent user of a Question and Answer site called StackOverflow (stackoverflow.com), and whenever I ask that kind of question, it ends up with the consensus being "Ask Matz". Afterall, only Matz (or the core developers) knows.

So, I request a Question and Answer section on this site regarding design decisions about Ruby: Why a certain feature was designed in such way and not in another way. I think this is the right place where such thing should be because only the developers know the reason. Then, people can ask about why a certain design decision was made before posting a feature request, and that will reduce hopeless feature requests that end up being rejected. That would be of a benefit to both the developers and the people wondering about the design.

[normalperson (Eric Wong)]

We have a mailing list (ruby-core) where matz and other core developers
read and discuss. No need to deal with a clunky web browser, either.

[sawa (Tsuyoshi Sawada)]

Eric Wong wrote:

We have a mailing list (ruby-core) where matz and other core developers
read and discuss. No need to deal with a clunky web browser, either.

I am asking for a way to let non-developers (open class set of people) ask to developers, not a discussion among developers.

[zzak (zzak _)]

• Status changed from Open to Rejected

Please feel free to ask any questions on ruby-core or ruby-dev mailing lists.

There is also ruby-talk for general discussion, and stackoverflow for Q&A.

[normalperson (Eric Wong)]

Anybody can join and post to the ruby-core mailing list, not just
core developers.

[sawa (Tsuyoshi Sawada)]

Zachary Scott wrote:

Please feel free to ask any questions on ruby-core or ruby-dev mailing lists.

There is also ruby-talk for general discussion, and stackoverflow for Q&A.

Did you read my question? I wrote explicitly that stackoverflow is useless for this kind of question because the people there are not necessarily developers.

[sawa (Tsuyoshi Sawada)]

Tsuyoshi Sawada wrote:

Zachary Scott wrote:

Please feel free to ask any questions on ruby-core or ruby-dev mailing lists.

There is also ruby-talk for general discussion, and stackoverflow for Q&A.

Did you read my question? I wrote explicitly that stackoverflow is useless for this kind of question because the people there are not necessarily Ruby developers.

[mame (Yusuke Endoh)]

I think it is a good idea, but few committers (including I) will have interest of creating it.
Instend of just requesting it, could you please create a draft by gathering frequent questions that matz has already answered? Or, at least, please create a question list.

Thanks,

--
Yusuke Endoh [e-mail]

[zzak (zzak _)]

We are working on official faq, maybe we can have another that is meant for developers.

I'm afraid a Q&A submission form will just get abused, or neglected.

Why create Yet Anoter Channel for committers have to pay attention to?

On Feb 9, 2014, at 12:07 AM, [e-mail] wrote:

Issue #9503 has been updated by Yusuke Endoh.

I think it is a good idea, but few committers (including I) will have interest of creating it.
Instend of just requesting it, could you please create a draft by gathering frequent questions that matz has already answered? Or, at least, please create a question list.

Thanks,

--
Yusuke Endoh [e-mail]

---

misc #9503: Request for a Question and Answer section
https://bugs.ruby-lang.org/issues/9503#change-45042

• Author: Tsuyoshi Sawada
• Status: Rejected
• Priority: Normal
• Assignee:
• Category:
• Target version:

---

I often come up with a question regarding why Ruby is designed the way it is with respect to a certain specification. Without knowing why it was designed in that way, I usually start to feel that such thing should be in a different way, and I ask that as a feature on this site, but then, sometimes it is responded from the developers with a reason why it has to be the way it is.

When I have such question, I first try to look for answers about the design decision; especially, I am a frequent user of a Question and Answer site called StackOverflow (stackoverflow.com), and whenever I ask that kind of question, it ends up with the consensus being "Ask Matz". Afterall, only Matz (or the core developers) knows.

So, I request a Question and Answer section on this site regarding design decisions about Ruby: Why a certain feature was designed in such way and not in another way. I think this is the right place where such thing should be because only the developers know the reason. Then, people can ask about why a certain design decision was made before posting a feature request, and that will reduce hopeless feature requests that end up being rejected. That would be of a benefit to both the developers and the people wondering about the design.

--
http://bugs.ruby-lang.org/