@@ -70,31 +70,6 @@ Minero AOKI for letting us translate his work.
7070You can get further information about this project from
7171"the archives of rhg-discussion mailing list":http://rubyforge.org/pipermail/rhg-discussion/
7272
73-
74- h2. Help us!
75-
76- People who are good at Ruby, C and Japanese or English are
77- needed. Those good at Japanese (native Japanese speakers are of course
78- welcome) can help translate and those good at English (preferably
79- native speakers) can help correct mistakes, and rewrite badly written
80- parts... Knowing Ruby and C well is really a requirement because it
81- helps avoiding many mistranslations and misinterpretations.
82-
83- People good at making diagrams would also be helpful because there is
84- quite a lot to redo and translators would rather spend their time
85- translating instead of making diagrams.
86-
87- There have been multiple efforts to translate this book, and we want to see if
88- we can renew efforts by creating an organisation on github. Interested parties
89- can join in by starting a pull request on this repo
90- https://github.com/ruby-hacking-guide/ruby-hacking-guide.github.com
91- There is a mostly derelict mailing list at
92- "rhg-discussion mailing list":http://rubyforge.org/mailman/listinfo/rhg-discussion
93- feel free to introduce yourself (who you are, your skills, how much free time you
94- have), but we think the best way to propose or send corrections/improvements
95- is to send a pull request. If you start a feature branch along with a pull
96- request at the start of your work then people can comment as you work.
97-
9873There is an old SVN repo, that is hosted at
9974The RubyForge project page is http://rubyforge.org/projects/rhg.
10075It has been imported here, and I will attempt to give credit and re-write the
0 commit comments