On second thought, just feel free to commit specs. I think the
additional requirement of sending a pull request for each one is just
too onerous. Either one of us or Brian Ford can do bulk merges back
into RubySpec later on.
And I'm fine giving commit access to jruby/rubyspec to anyone who
wants t
I should point out that everyone "jruby-core" has commit rights to
jruby/rubyspec, and as with rubyspec/rubyspec I'm fine opening it up
for commit access if you have access to rubyspec/rubyspec or submit a
"first patch".
Fire away.
- Charlie
On Mon, Dec 5, 2011 at 11:12 PM, Subramanya Sastry wr
Awesome! -Subbu.
On Tue, Dec 6, 2011 at 7:44 AM, Charles Oliver Nutter
wrote:
> In order to make it a bit easier and less daunting to contribute to
> RubySpec, I'm proposing (and have mostly already made) a minor change
> in our process.
>
> * Instead of pulling directly from github.com/rubyspe
very nice, this really helps people like me who have problems finding
the right places all the time ;)
- Kristian
On Tue, Dec 6, 2011 at 7:44 AM, Charles Oliver Nutter
wrote:
> In order to make it a bit easier and less daunting to contribute to
> RubySpec, I'm proposing (and have mostly already
In order to make it a bit easier and less daunting to contribute to
RubySpec, I'm proposing (and have mostly already made) a minor change
in our process.
* Instead of pulling directly from github.com/rubyspec/rubyspec we
will pull from a forked copy at github.com/jruby/rubyspec.
* Developers may
