← Back to branch summary

~james-page/ubuntu/precise/nodejs/0.6.x-merge

« back to all changes in this revision

Viewing changes to doc/community/index.html

  • Committer: James Page
  • Date: 2012-03-30 12:09:16 UTC
  • mfrom: (7.1.23 sid)
  • Revision ID: james.page@canonical.com-20120330120916-40hfu9o00qr5t87b
http://bugs.debian.org/639636
http://bugs.debian.org/650661
http://bugs.debian.org/658441
https://launchpad.net/bugs/892034
* Merge from Debian unstable:
  - New upstream release (LP: #892034).
  - This package is x86/arm only. Update control to match
  - d/patches/2009_increase_test_timeout.patch: Increased default test
    timeout from 60 to 120 seconds to support reliable execution of all
    tests on armhf/armel architectures.
  - d/patches/2005_expected_failing_tests.patch: 
    - Allow racey tests to fail: test-cluster-kill-workers,
      test-child-process-fork2 
    - Allow test-fs-watch to fail as LP buildd's don't support
      inotify.
    - Revert all other Ubuntu changes as no longer required.
* Update Standards-Version to 3.9.3.
* Patch wscript to enable build on mipsel arch, libv8 being available.
  Upstream does not support that arch, failure expected.
* test-cluster-kill-workers is expected to fail on armhf,
  Bug#660802 will be closed when test pass.
* test-buffer is expected to fail on armel,
  Bug#660800 will be closed when test pass.
* Add epoch to dependency on libev >= 1:4.11. Closes: bug#658441.
* Remove tools/doc because node-doc-generator has no license for now.
* Add copyright for doc/sh* files (shjs).
* source.lintian-overrides : source-contains-waf-binary tools/node-waf
  it is simply not the case here.
* test-stream-pipe-multi expected to timeout sometimes on busy builds. 
* New upstream release.
* Remove upstream patches.
* test-dgram-pingpong expected to timeout, the test itself is buggy.
* test-buffer expected to fail on armel, allow building package to make
  it easier to find the cause of the failure.
  Closes: bug#639636.
* Expect tests dgram-multicast and broadcast to fail.
  debian/patches/2005_expected_failing_tests.patch
* Drop dpkg-source local-options: Defaults since dpkg-source 1.16.1.
* New upstream release.
* Depend on libev-dev 4.11, see bug#657080.
* Bump dependency on openssl to 1.0.0g.
* Remove useless uv_loop_refcount from libuv,
  refreshed 2009_fix_shared_ev.patch.
* Apply to upstream patches landed after 0.6.10 release,
  to fix debugger repl and http client.
* New upstream release. Closes:bug#650661
* Repackage to remove non-dfsg font files ./deps/npm/html/*/*.ttf
* Remove unneeded bundled dependencies: lighter tarball,
  debian/copyright is easier to maintain.
* Drop unneeded build-dependency on scons.
* Depend on zlib1g, libc-ares, libev.
  Patches done to support building with those shared libs.
* Fix DEB_UPSTREAM_URL in debian/rules, and debian/watch.
* nodejs.pc file for pkgconfig is no more available.
* Build-depend on procps package, a test is using /bin/ps.
* Refreshed debian/patches/2005_expected_failing_tests.patch,
  only for tests that need networking.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/community/index.html
 
1
<!doctype html>
 
2
<html lang="en">
 
3
  <head>
 
4
    <meta charset="utf-8">
 
5
    <style>
 
6
    ul {
 
7
      padding: 0;
 
8
      margin: 0;
 
9
    }
 
10
    </style>
 
11
    <script src="../sh_main.js"></script>
 
12
    <script src="../sh_javascript.min.js"></script>
 
13
    <link type="image/x-icon" rel="icon" href="../favicon.ico">
 
14
    <link type="image/x-icon" rel="shortcut icon" href="../favicon.ico">
 
15
    <link rel="stylesheet" href="../pipe.css">
 
16
    <link rel="stylesheet" href="../sh_vim-dark.css">
 
17
    <link rel="alternate"
 
18
          type="application/rss+xml"
 
19
          title="node blog"
 
20
          href="http://feeds.feedburner.com/nodejs/123123123">
 
21
    <title>node.js</title>
 
22
  </head>
 
23
  <body class="int" id="community">
 
24
    <div id="intro" class="interior">
 
25
        <a href="/" title="Go back to the home page">
 
26
            <img id="logo" src="http://nodejs.org/images/logo.png" alt="node.js">
 
27
        </a>
 
28
    </div>
 
29
    <div id="content" class="clearfix">
 
30
            <div id="column2" class="interior">
 
31
                <ul>
 
32
                    <li><a href="/" class="home">Home</a></li>
 
33
                    <li><a href="/#download" class="download">Download</a></li>
 
34
                    <li><a href="/about/" class="about">About</a></li>
 
35
                    <li><a href="http://search.npmjs.org/" class="npm">npm Registry</a></li>
 
36
                    <li><a href="http://nodejs.org/docs/latest/api/index.html" class="docs">Docs</a></li>
 
37
                    <li><a href="http://blog.nodejs.org" class="blog">Blog</a></li>
 
38
                    <li><a href="/community/" class="community current">Community</a></li>
 
39
                    <li><a href="/logos/" class="logos">Logos</a></li>
 
40
                    <li><a href="http://jobs.nodejs.org/" class="jobs">Jobs</a></li>
 
41
                </ul>
 
42
                <p class="twitter"><a href="http://twitter.com/nodejs">@nodejs</a></p>
 
43
 
 
44
            </div>
 
45
        
 
46
            <div id="column1" class="interior">
 
47
                <p>Node's most valuable feature is the friendly and <a href="http://blip.tv/jsconf/nodeconf-2011-marak-squires-5729610">colorful community</a> of developers. There are many places where this group congregates on the internet. This page attempts to highlight the best forums.</p>
 
48
        
 
49
              <div class="row clearfix">
 
50
                  <div class="block">
 
51
                      <h2 class="documentation">Documentation</h2>
 
52
 
 
53
                          <p><a href="http://nodejs.org/docs/latest/api">Official API docs</a> detail the node API.</p>
 
54
                          <p><a href="http://docs.nodejitsu.com/">docs.nodejitsu.com</a> answers many of the common problems people come across.</p>
 
55
                          <p><a href="http://howtonode.org/">How To Node</a> has a growing number of useful tutorials.</p> 
 
56
                          <p><a href="http://stackoverflow.com/questions/tagged/node.js">Stack Overflow node.js tag</a> collects new information every day.</p>
 
57
                      </div>
 
58
 
 
59
 
 
60
                      <div class="block">
 
61
                          <h2 class="github">GitHub</h2>
 
62
                          <p>All development takes place at <a
 
63
                                  href="http://github.com/joyent/node">http://github.com/joyent/node</a>.
 
64
                              The comments on commit messages are often source of heated
 
65
                              discussion regarding core development.</p><p>The <a
 
66
                                  href="http://github.com/joyent/node/wiki">GitHub Node
 
67
                                  wiki</a> is full of useful links for newcomers.  Don't
 
68
                              miss <a
 
69
                                  href="https://github.com/joyent/node/wiki/Projects,-Applications,-and-Companies-Using-Node">Projects,
 
70
                                  Applications, and Companies Using Node</a> or the <a
 
71
                                  href="https://github.com/joyent/node/wiki/modules">very
 
72
                                  long list of Node modules</a>, many of which are
 
73
                              published in the <a href="http://search.npmjs.org/">npm
 
74
                                  registry</a>.</p>
 
75
                      </div>
 
76
                  </div>
 
77
 
 
78
        
 
79
              <div class="row clearfix">
 
80
                  <div class="block">
 
81
                      <h2 class="mailing">Mailing Lists</h2>
 
82
 
 
83
                      <p>The <a
 
84
                              href="http://groups.google.com/group/nodejs">user
 
85
                              mailing list</a> is used for announcements, discussion,
 
86
                          and flame wars about Node.  The <a
 
87
                              href="http://groups.google.com/group/nodejs-dev">internal
 
88
                              development mailing list</a> is used for discussion of
 
89
                          internal design and feature proposals.</p>
 
90
                  </div>
 
91
 
 
92
                  <div class="block">
 
93
                      <h2 class="periodicals">Periodicals</h2>
 
94
 
 
95
                      <p> <a
 
96
                              href="http://planetnodejs.com">Planet Node</a> is an
 
97
                          aggregator of Node developer blogs.</p><p><a
 
98
                              href="http://nodeup.com/">NodeUp</a>
 
99
                          is a podcast covering the latest Node news in the
 
100
                          community. </p>
 
101
                  </div>
 
102
              </div>
 
103
 
 
104
              <div class="row clearfix">
 
105
                  <div class="block">
 
106
                      <h2 class="conferences">Conferences</h2>
 
107
 
 
108
                      <p><a href="http://www.nodeconf.com/">NodeConf</a>
 
109
                          conferences are the main event in the United States; they
 
110
                          are organized by <a href="http://www.mikealrogers.com/">Mikeal Rogers</a>.</p>
 
111
                      <p><a href="http://nodefest.jp/">NodeFest (東京Node学園祭)</a>
 
112
                          is organized by the <a href="http://nodejs.jp">Node.js
 
113
                              Japan user group</a>.</p>
 
114
                      <p><a href="http://nodecamp.de/">NodeCamp.de</a> in Cologne,
 
115
                          Germany is organized by <a href="railslove.de">Rails Love</a>.</p>
 
116
                      <p>An <a href="http://nodejsconf.it/">Italian
 
117
                              Node.js Conference</a> exists as well.</p>
 
118
                      <p><a href="http://nodesummit.com/">Node Summit</a> is a
 
119
                          conference in San Francisco focusing on the adoption of
 
120
                          Node in larger companies.</p>
 
121
                      <p><a href="http://jsconf.com/">JSConf</a> organizes the main
 
122
                          JavaScript conferences.</p>
 
123
                  </div>
 
124
 
 
125
                  <div class="block">
 
126
                      <h2 class="localized">Localized Sites</h2>
 
127
 
 
128
                      <p><code>nodejs.org</code> does not maintain any
 
129
                          translations into other languages. However there are
 
130
                          community websites in various languages with mailing lists
 
131
                          and translations of the website.</p>
 
132
 
 
133
                      <p><a href="http://nodejs.ru/">nodejs.ru</a> Russian blog.
 
134
                          <br>
 
135
                          <a href="http://nodejs.ir">nodejs.ir</a> Iran group in Persian
 
136
                          <br>
 
137
                          <a href="http://nodejs.jp/">nodejs.jp</a> Japan user group 
 
138
                          <br>
 
139
                          <a href="http://cnodejs.org">CNodeJS.org</a> Chinese community
 
140
                          <br>
 
141
                          <a href="http://nodejs.co.il">nodejs.co.il</a> Israeli wiki
 
142
                          <br>
 
143
                          <a href="http://nodejs.hk">HKNoJ</a> Hong Kong community
 
144
                          <br>
 
145
                          <a href="http://nodejs.tw">nodejs.tw</a> Taiwan community</p>
 
146
                  </div>
 
147
              </div>
 
148
 
 
149
              <div class="row clearfix">
 
150
                  <div class="block">
 
151
                      <h2 class="irc">IRC</h2>
 
152
 
 
153
                      <p>For real-time chat about Node development go to
 
154
                          <code>irc.freenode.net</code> in the <code>#node.js</code>
 
155
                          channel with an <a href="http://www.mirc.com">IRC</a> <a
 
156
                              href="http://colloquy.info/">client</a> or connect in
 
157
                          your web browser to the channel using <a
 
158
                              href="http://webchat.freenode.net/?channels=node.js">freenode's
 
159
                              WebChat</a>. Felix Geisendörfer keeps <a
 
160
                              href="http://nodejs.debuggable.com/">logs of the
 
161
                              channel</a> for those who miss a day.</p>
 
162
                  </div>
 
163
              </div>
 
164
        
 
165
                  <p><a href="http://notinventedhe.re/on/2011-7-26"><img
 
166
                  src="http://nodejs.org/images/not-invented-here.png" width="100%"></a></p>
 
167
        </div>
 
168
</div>
 
169
    <div id="footer">
 
170
        <ul class="clearfix">
 
171
            <li><a href="/">Node.js</a></li>
 
172
            <li><a href="/#download">Download</a></li>
 
173
            <li><a href="/about/">About</a></li>
 
174
            <li><a href="http://search.npmjs.org/">npm Registry</a></li>
 
175
            <li><a href="http://nodejs.org/docs/latest/api/index.html">Docs</a></li>
 
176
            <li><a href="http://blog.nodejs.org">Blog</a></li>
 
177
            <li><a href="/community/">Community</a></li>
 
178
            <li><a href="/logos/">Logos</a></li>
 
179
            <li><a href="http://jobs.nodejs.org/">Jobs</a></li>
 
180
            <li><a href="http://twitter.com/nodejs" class="twitter">@nodejs</a></li>
 
181
        </ul>
 
182
 
 
183
        <p>Copyright 2010 <a href="http://joyent.com">Joyent, Inc</a>, Node.js is a <a href="/trademark-policy.pdf">trademark</a> of Joyent, Inc. View <a href="https://raw.github.com/joyent/node/v0.6.12/LICENSE">license</a>.</p>
 
184
    </div>
 
185
 
 
186
    <script>
 
187
      var gaJsHost = (("https:" == document.location.protocol) ?
 
188
      "https://ssl." : "http://www.");
 
189
      document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
 
190
    </script>
 
191
    <script>
 
192
      try {
 
193
        var pageTracker = _gat._getTracker("UA-10874194-2");
 
194
        pageTracker._trackPageview();
 
195
      } catch(err) {}
 
196
    </script>
 
197
</body>
 
198
</html>