From: Michael Malone <michael.j.b.malone@...>
Date: 2010-05-19T17:11:54+09:00
Subject: [ruby-core:30308] New Coder Etiquette & no extension require

--0016e68deb37b952350486ee02b8
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I have been coding in Ruby for a couple of years professionally now, and I
decided I would like to contribute.  I want to add the ability to require a
file that has no extension whatsoever (as a gentle introduction) and I would
start the conversation as to whether it was a good feature or not alongside
the patch implementing it.  When I went to do said change, I thought the
file in question could use a bunch of refactoring, but felt that might be a
little arrogant for my first submission.  So my question is, am I going to
offend people if I start jumping in and changing code structure like there's
no tomorrow?  Or should I learn to like the existing style?  Or am I going
to annoy people more by writing this sort of question to the core mailing
list?

Regards,
Michael

--0016e68deb37b952350486ee02b8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>I have been coding in Ruby for a couple of years professionally =
now, and I decided I would like to contribute.=A0 I want to add the ability=
 to require a file that has no extension whatsoever (as a gentle introducti=
on) and I would start the conversation as to whether it was a good feature =
or not alongside the patch implementing it.=A0 When I went to do said chang=
e, I thought the file in question could use a bunch of refactoring, but fel=
t that might be a little arrogant for my first submission.=A0 So my questio=
n is, am I going to offend people if I start jumping in and changing code s=
tructure like there&#39;s no tomorrow?=A0 Or should I learn to like the exi=
sting style?=A0 Or am I going to annoy people more by writing this sort of =
question to the core mailing list?<br>
<br>Regards,<br>Michael<br>

--0016e68deb37b952350486ee02b8--