htaccess: Add what we currently use, spider-protection
[girocco.git] / mob.html
blob13ea653c5bb906a75ce26b6156addab8f3b5b404
1 <?xml version="1.0" encoding="utf-8"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
5 <head>
6 <title>repo.or.cz :: About the Mob Account</title>
7 <link rel="stylesheet" type="text/css" href="/gitweb.css"/>
8 <link rel="shortcut icon" href="/git-favicon.png" type="image/png"/>
9 </head>
11 <body>
13 <div class="page_header">
14 <a href="http://git.or.cz/" title="Git homepage"><img src="/git-logo.png" width="72" height="27" alt="git" style="float:right; border-width:0px;"/></a>
15 <a href="/">repo.or.cz</a> / site guide / About the Mob Account
16 </div>
19 <p>The <tt>mob</tt> account (the name a tribute to the paper
20 <a href="http://www.dreamsongs.com/MobSoftware.html">Mob Software: The Erotic Life of Code</a>)
21 is.a way to enable <em>anonymous push access</em> for your project.
22 This is largely an experiment and may be scrapped in the future if
23 it will not get widespread use, but I think it's an interesting try.
24 The idea is to provide unmoderated <em>side</em> channel for random
25 contributors to work on a project, coming from the same place as
26 e.g. Wikipedia - that given enough interested people, the quality
27 will grow rapidly and occassional "vandalism" will get fixed quickly.
28 Of course this may not work nearly so well for software, but here
29 we are, to give it a try.</p>
31 <h2>For Repository Admins</h2>
33 <p>How it works? First, you need to add the <tt>mob</tt> user to the
34 list of users allowed to push in your project. <tt>mob</tt> is a
35 keyless, passwordless user that anyone can use to push, without
36 any special setup. <strong>But</strong> this does not mean that
37 your project is now in the hands of raging mindless mob! The <tt>mob</tt>
38 user has a special restriction: it can push only to an existing
39 <tt>mob</tt> branch. This means that the second step you need to take
40 is to create a <tt>mob</tt> branch in the repository (e.g.
41 <code>git checkout -b mob
42 &amp;&amp; git push origin mob</code>). Then the <tt>mob</tt> user
43 will be able to push to that and only that branch, and it won't be
44 able to push whatsoever until you take the second step.</p>
46 <p>To sum it up: Anonymous pushes are allowed <em>only</em> to the <tt>mob</tt>
47 branch and <em>only</em> if you add a <tt>mob</tt> user and do an initial
48 pushout of the <tt>mob</tt> branch.</p>
50 <h2>For Users</h2>
52 <p>After cloning the repository, do <code>git checkout mob</code> to move to the
53 <tt>mob</tt> branch.</p>
55 <p><strong>Note that you are taking a huge security risk on yourself
56 if you just blindly grab the mob branch and run it on your
57 system.</strong></p>
59 <h2>For Developers</h2>
61 <p>Just commit on the <tt>mob</tt> branch you've checked out and <code>git
62 push</code> when the time is ripe. Have fun and enjoy, you are making the
63 history!</p>
65 </body>
66 </html>