Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

Commit

Permalink
Redirect /for/contributors over to BG
Browse files Browse the repository at this point in the history
  • Loading branch information
@chadwhitacre
chadwhitacre committed May 16, 2014
1 parent f2b3d4a commit b55022c
Show file tree
Hide file tree
Showing 9 changed files with 19 additions and 582 deletions.
7 changes: 3 additions & 4 deletions www/about/index.html.spt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -100,11 +100,10 @@ title = "About"
<div class="clear"></div>

<a name="get-involved"></a>
<h2>Get Involved</h2>
<h2>Help Build Gittip</h2>

<p>Gittip is open-source and funded on Gittip.</p>

<p>Learn about <a href="/for/contributors/">becoming a contributor</a>.</p>
<p>Want to help us with design, code, marketing, and management for Gittip?
Learn how on <a href="http://building.gittip.com/">Building Gittip</a>!</p>

</div>
{% endblock %}
49 changes: 2 additions & 47 deletions www/for/contributors/index.html.spt
View file
Original file line number Diff line number Diff line change
@@ -1,48 +1,3 @@
title = "For Contributors"
[---]
{% extends "templates/for-contributors.html" %}
{% block page %}
<div class="col0">

<h2>Getting Started</h2>

<p>Thanks for wanting to help! This is the place to start. :-)</p>

<p><a href="/about/">Gittip</a> is a new kind of organization called an
&ldquo;<a
href="http://blog.gittip.com/post/26350459746/the-first-open-company">open
company</a>.&rdquo; Anyone can volunteer to help with almost anything at
any time, and <a href="/Gittip/members/">everyone who volunteers</a> gets to
<a href="https://medium.com/building-gittip/eba0a27825b8">take some of the
money</a> that has been given on Gittip to Gittip itself&mdash;Gittip is
funded on Gittip.</p>


<h2>Documentation</h2>

<ol class="upper-roman" style="padding-bottom: 1em;">
<li><a href="mission-statement.html">Mission Statement</a></li>
<li><a href="where-we-work.html">Where We Work</a></li>
<li><a href="ways-to-help/">Ways to Help</a>
<ol class="upper-alpha">
<li><a href="ways-to-help/tell-people-about-gittip.html">Tell People About Gittip</a></li>
<li><a href="ways-to-help/support-users.html">Support Users</a></li>
<li><a href="ways-to-help/build-gittip.html">Build Gittip</a></li>
<li><a href="ways-to-help/train-new-contributors.html">Train New Contributors</a></li>
</ol>
</li>
</ol>


<h2>What next?</h2>

<p>Announce yourself on <a href="where-we-work.html">IRC</a> and say you want
to help, or if you're not sure about IRC or no-one is around when you show up
there, then tweet &ldquo;I want to help!&rdquo; to <a
href="https://twitter.com/Gittip">@Gittip</a>. Someone will respond and
help you get started with your first project.</p>

<p>Woo-hoo! Thanks! :-)</p>

</div>
{% endblock %}
request.redirect('http://building.gittip.com/')
[---]
18 changes: 2 additions & 16 deletions www/for/contributors/mission-statement.html.spt
View file
Original file line number Diff line number Diff line change
@@ -1,17 +1,3 @@
title = "For Contributors"
[---]
{% extends "templates/for-contributors.html" %}
{% block page %}
<div class="col0">

<h2>Mission Statement</h2>

<p>Gittip's mission is to redeem the economy.</p>

<p>We envision a future in which the economy is characterized by trust,
collaboration, cooperation, sharing, openness, transparency, care for one
another, inclusion, inspiration, purpose, generosity, patience, empathy,
optimism, and love.</p>

</div>
{% endblock %}
request.redirect('http://building.gittip.com/big-picture/mission')
[---]
136 changes: 2 additions & 134 deletions www/for/contributors/ways-to-help/build-gittip.html.spt
View file
Original file line number Diff line number Diff line change
@@ -1,136 +1,4 @@
title = "Build Gittip"
[---]
{% extends "templates/for-contributors.html" %}
{% block page %}
<style>
#types-nav li {
margin: 0;
padding: 5px 0;
}
</style>
<div class="col0">

<h2>Build Gittip</h2>

<ol class="decimal">

<li>Find something about Gittip that annoys you. Specifically, don't start
by browsing issues. Start by using Gittip.

<ol class="lower-roman">

<li>When you cognize an annoyance, <a
href="https://github.com/gittip/www.gittip.com/search?state=open&type=Issues">search</a>
for a ticket.</li>

<li>If you don't find a ticket, <a
href="https://github.com/gittip/www.gittip.com/issues/new">make
one</a>.</li>

<li>Pick something interesting and within reach.</li>

<li>Your first contribution should be almost trivial, so you a) get an
early win fast, and b) get comfortable with this process.</li>

<li>Talking with others in <a href="../where-we-work.html">IRC</a> is a
great way to settle on a good next ticket.</li>

</ol>

</li>

<li>If you're a collaborator on our repo, assign yourself to the ticket (if
you're not a collaborator, you will be soon). The rules of assignment are:

<ol class="lower-roman">

<li>Only one assignment per person at a time.</li>

<li>Only you can assign and unassign yourself.</li>

<li>You are the benevolent dictator of your ticket.</li>

</ol>

</li>

<li>Design from the outside in, build from the inside out:

<ol class="lower-roman">

<li><b>Sketch a solution</b> to your problem, using, for example:

<ol class="lower-alpha">

<li>Words. Describe a solution on the ticket.</li>

<li>Paper. Take a picture, possibly with your laptop's webcam, and post
that on the ticket.</li>

<li><a href="http://www.bohemiancoding.com/sketch/">Sketch</a>.
Post a <a href="https://layervault.com/gittip">LayerVault</a> link
on the ticket.</li> </ol>

</li>

<li>Find people to critique your sketch. <a
href="../where-we-work.html">IRC</a> is the best place to actively
look for people.</li>

<li>Iterate on the sketch, molding consensus.</li>

<li><b>Implement the solution</b> and start a pull request.

<ol class="lower-alpha">

<li>If you are a collaborator on our repo, use a topic branch in
the main repo.</li>

<li>If you aren't a collaborator, fork our repo and start the pull
request from there.</li>

<li><a href="http://progrium.com/localtunnel/">Localtunnel</a> is
great for sharing your localhost. This works well when discussing
on IRC.</li>

<li>If you're discussing asynchronously on GitHub, deploy the
branch to a public QA instance if you can. (This is hard right now
and we aim to streamline this.)</li>

<li>If your pull request stays open a long time, periodically merge
master out to the branch.</li>

</ol>

</li>

<li>Find people to critique and possibly contribute commits to your
implementation.</li>

<li>Iterate on the implementation, molding consensus.</li>

<li><b>Call for final review/merge</b> by writing a comment on the pull
request like, "I'm ready for final review/merge here."

<ol class="lower-alpha">

<li>Merge master to the branch first. (Don't rebase.)</li>

<li>No one is allowed to merge their own pull requests.</li>

</ol>

</li>

</ol>

</li>

<li>Your implementation will go out with the next deployment.</li>

<li>Close the ticket once your implementation is deployed.</li>

</ol>
request.redirect('http://building.gittip.com/policies/build-gittip')
[---]

</div>
{% endblock %}
30 changes: 2 additions & 28 deletions www/for/contributors/ways-to-help/index.html.spt
View file
Original file line number Diff line number Diff line change
@@ -1,29 +1,3 @@
title = "Ways to Help"
[---]
{% extends "templates/for-contributors.html" %}
{% block page %}
<style>
#types-nav li {
margin: 0;
padding: 5px 0;
}
</style>
<div class="col0">

<h2>Ways to Help</h2>

<p>If you're a new contributor, tweet &ldquo;I want to help!&rdquo; to <a
href="https://twitter.com/Gittip">@Gittip</a> and someone will help you
get started.</p>

<ol class="upper-alpha">

<li><a href="tell-people-about-gittip.html">Tell People About Gittip</a></li>
<li><a href="support-users.html">Support Users</a></li>
<li><a href="build-gittip.html">Build Gittip</a></li>
<li><a href="train-new-contributors.html">Train New Contributors</a></li>

</ol>

</div>
{% endblock %}
request.redirect('http://building.gittip.com/')
[---]
100 changes: 2 additions & 98 deletions www/for/contributors/ways-to-help/support-users.html.spt
View file
Original file line number Diff line number Diff line change
@@ -1,99 +1,3 @@
title = "Support Users"
[---]
{% extends "templates/for-contributors.html" %}
{% block page %}
<style>
#types-nav li {
margin: 0;
padding: 5px 0;
}
</style>
<div class="col0">

<h2>Support Users</h2>

<p>The process described below assumes Twitter, but this could be adapted for
any other social network or forum.</p>

<ol class="decimal">

<li>Read as much of the <a
href="https://medium.com/building-gittip/latest">collection</a>, the <a
href="http://tinyletter.com/gittip">newsletter</a>, the <a
href="http://blog.gittip.com/">blog</a>, and the <a
href="https://github.com/gittip/www.gittip.com/issues?direction=desc&page=1&sort=comments&state=open">issues</a>
as you can handle.</li>

<li>Search for &ldquo;gittip&rdquo; <a
href="https://twitter.com/search/realtime?q=gittip&src=typd">on
Twitter</a>.</li>

<li>When you notice a tweet about a problem with Gittip:

<ol class="lower-roman">

<li><a
href="https://github.com/gittip/www.gittip.com/search?state=open&type=Issues">Search</a>
for their problem.</li>

<li>If you find it, add a comment using this template:<br><br>

<code>+1 from @blah on [Twitter](tweet-url).</code>

<br><br><code>@blah</code> should be their GitHub username; try hard to
find it. Otherwise link it to their Twitter profile.

<br><br>These cross-linked +1 comments are important to help gauge how
important a given problem is.

</li>

<li>If you don't find a ticket for their problem, <a
href="https://github.com/gittip/www.gittip.com/issues/new">make
one</a>. Mention their GitHub username and link to their tweet.</li>

</li>

<li>Respond on Twitter:

<ol class="lower-alpha">

<li>Use your own personal Twitter account.</li>

<li>Pick "sorry" or "thank you" depending on their tone and level of
apparent frustration.</li>

<li>If there already was a ticket (and they're mad), use this
template:<br><br>

<code>Sorry for the trouble. :( I've added a +1 for you here:
&lt;ticket-url&gt;.</code>

</li>

<li>If you made a new ticket (and they're not mad), use this
template:<br><br>

<code>Thanks for the heads-up! I've ticketed this here:
&lt;ticket-url&gt;. :-)</code>

</li>

<li>If there is a workaround mentioned on the ticket, offer it to
them.</li>

<li>Don't be afraid to have a conversation with them.</li>

<li>Don't be afraid to say &ldquo;we.&rdquo; You're part of Gittip!
:-)</li>

</ol>

</li>

</ol>

</ol>

</div>
{% endblock %}
request.redirect('http://building.gittip.com/policies/run-support')
[---]
Loading

0 comments on commit b55022c

Please sign in to comment.