about.html

   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">
   4
   5 <head>
   6 <title>repo.or.cz :: About the Site</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>
  10
  11 <body>
  12
  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 Site
  16 </div>
  17
  18 <p><strong>repo.or.cz</strong> is a public
  19 <a href="http://git.or.cz">Git</a> hosting site.</p>
  20
  21 <p>
  22 You can <a href="/m/regproj.cgi?mode=push">create a project</a> on this
  23 site to publish your development work, pushing your own changes or
  24 enabling permission for other developers (or even anonymous users) to
  25 push their work.  If you want to work on a project published on another
  26 site, you can <a href="/m/regprog.cgi?mode=mirror">establish a
  27 mirror</a>, and you will gain pull access (Git and HTTP), a gitweb
  28 interface, and low-overhead forking for the project.  Alternatively, you
  29 may need to <a href="/m/regprog.cgi?mode=fork">start a fork</a> of an
  30 existing project, rather than create a completely new project or mirror.
  31 </p>
  32 <p>
  33 The following sections explain the differences between the three mode
  34 of hosting public Git repositories on this site.
  35 </p>
  36 <h3>Depot Mode</h3>
  37 <p>
  38 In depot mode, project developers must
  39 <a href="/m/reguser.cgi">create an account</a> that registers the SSH
  40 key used for pushing changes to the server securely (using git+ssh).
  41 Project administration allows you to manage permissions for developers
  42 to push to your project(s).  In this mode, an optional <tt>mob</tt>
  43 branch may be created to permit <a href="/mob.html">anonymous push
  44 access</a> to the project.
  45 </p>
  46 <h3>Mirror Mode</h3>
  47 <p>
  48 In mirror mode, we will check the remote repository at the URL
  49 you give us every hour and if we spot any changes, we will grab them,
  50 mirror them and show them in our gitweb interface. It's a matter of few
  51 clicks to set up a mirror - don't be shy and feel free to create mirror
  52 for any git project without a decent gitweb interface or with badly
  53 hosted repository; you don't need to be the project maintainer to setup
  54 a mirror.
  55 </p>
  56 <h3>Fork Mode</h3>
  57 <p>
  58 You can <a href="/m/regproj.cgi?mode=fork">create a fork</a> for either
  59 mirror or depot projects.  In fork mode, a project can share its local
  60 parent projects' object stores, so they reduce the bandwidth and storage
  61 requirements significantly for large active projects.  Other than this
  62 magical property, a fork mode project behaves the same as a project
  63 created in depot mode.
  64 </p>
  65 <p>
  66 The gitweb summary page for each project contains a 'fork' link in the
  67 navigation bar at the top of the page.  This provides a shortcut for you
  68 to start a new fork on this server.
  69 </p>
  70
  71 <h2>Terms and Conditions</h2>
  72
  73 <p>There are only two conditions:</p>
  74
  75 <ul>
  76 <li>Your project must be free software and distributing it must not violate laws
  77 of Czech Republic. (The registration process is completely automatic but we will
  78 remove your project if we find out during manual inspection or on request by
  79 someone relevant.)</li>
  80 <li>The repository size should not exceed 100M after repacking (let us know
  81 if you need an exception). If you need more, you are running quite a big
  82 project and should be able to arrange own hosting; but we can and likely will
  83 grant exceptions. Note that e.g. CVS-imported glibc repository with ~15 years
  84 worth of history is just 100M.</li>
  85 </ul>
  86
  87 <p>This site provides NO WARRANTY of any legal kind about whatever you store
  88 here. Someone can crack your account or the site, alter the data, make mayhem
  89 and whatever else; we cannot be held responsible for any damages that may be
  90 caused to you in any way in connection with this site.</p>
  91
  92
  93 <h2>Backup policy</h2>
  94
  95 <p>Your repository is NOT backed up! Why? Because you have backups yourself,
  96 and all your users do, too! The distributed nature of Git means that all the
  97 developers and all the users who ever cloned the repository have the full
  98 history of it, and shall any disaster happen to repo.or.cz, all can be
  99 easily restored by a single simple push. That said, we may set up backups
 100 in the future if the service becomes popular enough.</p>
 101
 102 <p>Actually, the metadata and project information is not backed up either
 103 currently. We'll fix that soon.</p>
 104
 105
 106 <h2>Operation</h2>
 107
 108 <p>repo.or.cz runs on a four-way Xeon 2GHz with 4G RAM and 256G disk array
 109 that also serves as a PoP for the <a href="http://www.xs26.net/">XS26</a>
 110 IPv6 tunnel broker.
 111 The server and connectivity is generously sponsored by <a href="http://www.upc.cz/">UPC Czech Republic</a>.</p>
 112
 113 <p><a href="mailto:pasky@suse.cz">Petr Baudis</a>
 114 runs the site. Virtually all the infrastructure is available in git
 115 repositories <a href="/w/repo.git">repo.git</a> and <a href="/w/git/repo.git">git/repo.git</a>
 116 and is licenced under GPLv2. repo.or.cz development is sponsored by SUSE / Novell Inc.</p>
 117
 118 </body>
 119 </html>