Author: smoe-guest
Date: 2009-09-04 13:29:27 +0000 (Fri, 04 Sep 2009)
New Revision: 3885
Modified:
trunk/community/website/organisations.xsl
Log:
Adapting template to be shared by multiple pages.
Modified: trunk/community/website/organisations.xsl
===================================================================
--- trunk/community/website/organisations.xsl 2009-09-04 13:09:45 UTC (rev
3884)
+++ trunk/community/website/organisations.xsl 2009-09-04 13:29:27 UTC (rev
3885)
@@ -54,10 +54,13 @@
</td>
<td>
+ <!-- Presentation of organisations -->
+
+ <xsl:for-each select="organisations">
<h1>Organisations sharing aims with Debian Med</h1>
<hr />
<table border="0">
- <xsl:for-each select="organisations/org">
+ <xsl:for-each select="org">
<xsl:variable name="url" select="url" />
<tr>
<td rowspan="2" align="center" valign="top"><a
href="{url}"><xsl:value-of select="@title"/></a></td><td>
@@ -77,7 +80,88 @@
<tr><td colspan="2"><hr /></td></tr>
</xsl:for-each>
</table>
+ </xsl:for-each>
+ <!-- Presentation of sources for support -->
+
+ <xsl:for-each select="support">
+ <h1>Sources for support for packages in Debian Med</h1>
+ <p>
+ With Debian, there are several sources for support. Firstly, there is
the maintainer of the packages, who can be reached with
+ "<tt>reportbug </tt><i>packagename</i>" from the command line. The
maintainer is commonly the Debian Med mailing list, please
+ be aware that your email will be picked up by google and the public
may learn about your activities this way.
+ </p>
+ <p>
+ You may prefer to contact contributors of Debian Med directly or ask
to be contacted on the mailing list. You can find
+ partners for scientific projects, delegate some analyses, ask for
some development or offer internships of various kinds
+ for students. And yes, you'd need to pay for that.
+ </p>
+ <p>
+ Finally, as a commercial entity you should be aware that you are not
alone in your decision for Debian as a distribution. For
+ a general support of Debian you will find contacts in your area on <a
href="http://www.debian.org/consultants/";>www.debian.org/consultants</a>.
+ For support for packages with a rather highly specialised domain
knowledge, the following companies came to our attention:
+ </p>
+ <hr />
+ <table border="0">
+ <xsl:for-each select="entity">
+ <xsl:variable name="url" select="url" />
+ <tr>
+ <td rowspan="2" align="center" valign="top"><a
href="{url}"><xsl:value-of select="@title"/></a></td><td>
+ <xsl:value-of select="longtitle"/><br/>
+ <xsl:value-of select="description"/>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <ul>
+ <li>Outreach: <xsl:value-of select="region"/></li>
+ <li>URL: <a href="{url}"><xsl:value-of select="url"/></a></li>
+ </ul>
+ </td>
+ </tr>
+ <tr><td colspan="2"><hr /></td></tr>
+ </xsl:for-each>
+ </table>
+ </xsl:for-each>
+
+
+ <!-- Presentation of sources for projects -->
+
+
+ <xsl:for-each select="projects">
+ <h1>Projects of Debian Med</h1>
+ <p>
+ With Debian Med collecting tools for various types of data, many such
+ packages can work on the same kind of files. Or the tools depend
+ on each other functionally. For avoiding redundancies and for
orchestrating
+ the individual contributors to biomedical workflows in general,
+ we need some extra level. The following projects emerge as such in
+ the community.
+ </p>
+ <hr />
+ <table border="0">
+ <xsl:for-each select="project">
+ <xsl:variable name="url" select="url" />
+ <tr>
+ <td rowspan="2" align="center" valign="top"><a
href="{url}"><xsl:value-of select="@title"/></a></td><td>
+ <xsl:value-of select="longtitle"/><br/>
+ <xsl:value-of select="description"/>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <ul>
+ <li>Contributors: <xsl:value-of select="members"/></li>
+ <li>URL: <a href="{url}"><xsl:value-of select="url"/></a></li>
+ </ul>
+ </td>
+ </tr>
+ <tr><td colspan="2"><hr /></td></tr>
+ </xsl:for-each>
+ </table>
+ </xsl:for-each>
+
+
</td>
</tr>
</table>
_______________________________________________
debian-med-commit mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/debian-med-commit
