rubinius / rubinius.github.io Goto Github PK

Ruby section in the documentation is empty (except for Global Variables section which has broken formatting).

Do you think it would be worth including official Ruby documentation here?

It seem to be under public domain according to Ruby's legal notice.

When I try to get to the website this is what happens:

ERROR

The request could not be satisfied.

Bad request.
Generated by cloudfront (CloudFront)
Request ID: B7nvRSJfTBNWEItUU89sG0vXp5fTTCDiTMYTxYDFInZE7P08Xt7ODg==

Code examples are extremely small on mobile devices, at least on mine.

After adding the German translation I wondered if guides and how-tos can't be merged. In my German translation I used for both categories Anleitungen which is awkward to say the least, I know, but clearest. Also I don't see much of a difference between the two.

"A permanent or temporary ban from some or all Stumptown Syndicate spaces" needs changing. The examples of spaces listed next may also need changing.

Currently the guides on writing specs are really quite basic. One of the most common problems I currently face is dealing with pull-requests that add specs that don't go for the full 100%. In almost all cases this problem can be broken into two categories:

1. Spec descriptions are too short (e.g. it "returns X" vsit "returns X when given an instance of Y"`).
2. Example blocks are far too big instead of only containing the bare minimum needed to test certain behaviour.

The old RubySpec website had a pretty decent guide on writing specs and I think we should re-use that in some shape or form. What it should at least cover:

1. Where certain specs go (this isn't always clear when just searching for similar code)
2. How to write good spec descriptions
3. Some techniques on cutting down the size of example blocks (and why)
4. How to tag specs/remove tags
5. How to deal with complex setup code
6. The importance of all of the above

Pulling in from rubinius/rubinius#3481

A suggestion from rubinius/rubinius#3263