forked from rubinius/rubinius
/
community.html
69 lines (50 loc) · 3.53 KB
/
community.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang='en-us' xmlns='http://www.w3.org/1999/xhtml'>
<head>
<title>Rubinius - Community</title>
<link href="screen.css" media="screen" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="container">
<div id="header">
<div id="nav">
<div id="nav-items">
<a href="index.html">Home</a><span class="separator">
| </span><a href="roadmap.html">Roadmap</a><span class="separator">
| </span><a href="bench.html">Benchmarks</a><span class="separator">
| </span><strong>Community</strong><span class="separator">
| </span><a href="contribute.html">Contribute</a><span class="separator">
| </span><a href="documentation.html">Documentation</a><span class="separator">
| </span><a href="download.html">Download</a><span class="separator">
</div>
</div>
<div id="branding">
<div id="site-title">Rubinius</div>
<div id="site-subtitle">Ruby, the Way It Was Meant To Be</div>
<div id="site-download"><a href="http://github.com/evanphx/rubinius/tree/master"><img src="http://74.217.48.135/assets/2/down_24.png" alt="download git" /> Download with git</a></div>
</div>
</div>
<div id="content">
<h1>Community</h1>
<p>Places to be:</p>
<ul>
<li>Tracker: <a href="http://rubinius.lighthouseapp.com/projects/5089-rubinius/overview">On Lighthouse</a></li>
<li>Wiki: See above.</li>
<li><span class="caps">IRC</span>: #rubinius on irc.freenode.net</li>
<li>ML: rubinius-dev at <a href="http://groups.google.com/group/rubinius-dev">Google Groups</a></li>
</ul>
<h2>Communication</h2>
<p>The primary way that Rubinius developers communicate with each other is <span class="caps">IRC</span>. Yes, we know it is the 21st century now–but give it a try. It is even at this late date the best means of communication for a large distributed project. <span class="caps">IRC</span> clients are available for any imaginable OS. If it can access the Internet, it has an <span class="caps">IRC</span> client. More on <span class="caps">IRC</span>, a list of clients and a nick list can be <a href="http://github.com/evanphx/rubinius/blob/master/doc/community.txt">found here</a>. <a href="http://donttreadonme.co.uk/rubinius-irc"><span class="caps">IRC</span> logsare also available</a>.</p>
<p>If you cannot (or prefer not to) use <span class="caps">IRC</span>, feel free to ask questions or submit patches via the mailing list as well. The mailing list <strong>is</strong> relatively quiet currently because of the heavy emphasis on <span class="caps">IRC</span> but rest assured, you will find yourself in a discussion on the ML as well if you send the first e-mail.</p>
<p>If you are just starting with Rubinius feel free to ask for help! We try to make sure that there is documentation available and someone will always be able to answer questions–all we ask in return is that you bring an inquisitive mind and are willing to do proactively poke around the code or research otherwise also.</p>
</div>
<div id="footer">
<ul>
<li>Copyright © 2007-2008 <a href="http://blog.fallingsnow.net/">Evan Phoenix</a>.</li>
<li>Distributed under the <a href="http://en.wikipedia.org/wiki/BSD_license#Terms">BSD license</a>.</li>
<li class="align-right"><a href="http://www.engineyard.com"><img src="assets/4/engineyardproject_logo.png" alt='Engine Yard Project' /></a></li>
</ul>
</div>
</div>
</body>
</html>