[Piuparts-commits] [SCM] piuparts git repository branch, bikeshed, updated. 0.52-53-g6217eff

[Holger Levsen]

The following commit has been merged in the bikeshed branch:
commit 6217efff82b106bdee25ac4356478d814020124b
Author: Holger Levsen <holger at layer-acht.org>
Date:   Sat Jun 1 19:42:43 2013 +0200

    htdocs/index.tpl: Further restructure 'about p.d.o' section
    
    Signed-off-by: Holger Levsen <holger at layer-acht.org>

diff --git a/htdocs/index.tpl b/htdocs/index.tpl
index 6188a5d..c8b30df 100644
--- a/htdocs/index.tpl
+++ b/htdocs/index.tpl
@@ -16,21 +16,39 @@
       It does this by  creating a minimal Debian installation in a chroot, and installing,
       upgrading, and removing packages in that environment, and comparing the state of the directory tree before and after.
       piuparts reports any files that have been added, removed, or modified during this process.
-      piuparts is meant as a quality assurance tool for people who create .deb packages to test them before they upload them to the Debian package archive. See the <a href="/doc/README.html" target="_blank">piuparts README</a> for a quick intro and then read the <a href="/doc/piuparts.1.html" target="_blank">piuparts manpage</a> to learn about all the fancy options!
+      piuparts is meant as a quality assurance tool for people who create .deb packages to test them before they upload them to the Debian package archive.
+     </td>
+    </tr>
+    <tr class="normalrow">
+     <td class="contentcell2">
+      See the <a href="/doc/README.html" target="_blank">piuparts README</a> for a quick intro and then read the <a href="/doc/piuparts.1.html" target="_blank">piuparts manpage</a> to learn about all the fancy options!
+     </td>
+    </tr>
+    <tr class="normalrow">
+     <td class="contentcell2">
+      To make sure piuparts is run on all packages in Debian, piuparts.debian.org has set up running piuparts in <a href="/doc/README_server.html" target="_blank">master/slave mode</a>. This setup currently consists of two hosts: <a href="http://db.debian.org/machines.cgi?host=pejacevic" target="_blank">pejacevic.debian.org</a> and <a href="http://db.debian.org/machines.cgi?host=piu-slave-bm-a" target="_blank">piu-slave-bm-a.debian.org</a>:
+     <ul>
+      <li> pejacevic is running as master, which means it is running the piuparts-master, which is scheduling jobs to the slaves to be run. And it is  generating and hosting the reports visible as piuparts.debian.org.</li>
+      <li> piu-slave-bm-a runs four piuparts-slave instances, which then run piuparts itself.</li>
+     </ul>
+      These hosts run as virtualized hardware on <a href="http://bits.debian.org/2013/04/bytemark-donation.html" target="_blank">this nice cluster</a> hosted at <a href="http://www.bytemark.co.uk" target="_blank">Bytemark</a>.
+     </td>
+    </tr>
+    <tr class="normalrow">
+     <td class="contentcell2">
+      To learn more about this setup, follow the <i>"Documentation"</i> links in the navigation menu on the left. The piuparts configuration for all the different suite(-combination)s currently being tested is also linked there.
      </td>
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
-      To make sure piuparts is run on all packages in Debian, piuparts.debian.org has set up running piuparts in <a href="/doc/README_server.html" target="_blank">master/slave mode</a>. This setup currently consists of two hosts: <a href="http://db.debian.org/machines.cgi?host=pejacevic" target="_blank">pejacevic.debian.org</a>, running piuparts-master, generating and hosting the reports and <a href="http://db.debian.org/machines.cgi?host=piu-slave-bm-a" target="_blank">piu-slave-bm-a</a>, which runs four piuparts-slave instances, which then run piuparts itself. These hosts run
- as virtualized hardware on <a href="http://bits.debian.org/2013/04/bytemark-donation.html" target="_blank">this nice cluster</a> hosted at <a href="http://www.bytemark.co.uk" target="_blank">Bytemark</a>.
-     <br>
-      To learn more about this setup, follow the <i>Documentation</i> links in the navigation menu on the left. The piuparts configuration for all the different suite(-combination)s currently being tested is also linked there.
-     <br>
       Besides all the information provided here (which has it's sources in <a href="http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git" target="_blank">GIT</a>) there are also three wiki pages on wiki.debian.org currently: the main one which is mostly about
       <a href="http://wiki.debian.org/piuparts" target="_blank">piuparts development</a>, some
       <a href="http://wiki.debian.org/piuparts/FAQ" target="_blank">frequently asked questions</a> and some
       <a href="http://wiki.debian.org/piuparts/UseCases" target="_blank">use cases</a>.
-     <br>
+     </td>
+    </tr>
+    <tr class="normalrow">
+     <td class="contentcell2">
       Join #debian-qa on irc.debian.org or post on the <a href="http://lists.alioth.debian.org/mailman/listinfo/piuparts-devel" target="_blank">piuparts development mailinglist</a> if you want to help. The best way to help is to provide patches via GIT pull requests.
      </td>
     </tr>

-- 
piuparts git repository