[open-ils-commits] r1339 - evergreen-ils.org (bshum)
svn at svn.open-ils.org
svn at svn.open-ils.org
Tue Apr 12 23:02:08 EDT 2011
Author: bshum
Date: 2011-04-12 23:02:05 -0400 (Tue, 12 Apr 2011)
New Revision: 1339
Modified:
evergreen-ils.org/communicate.php
evergreen-ils.org/documentation.php
evergreen-ils.org/downloads.php
evergreen-ils.org/irc.php
evergreen-ils.org/opensrf.php
Log:
Applying p and li class="content" for consistency on some pages.
Modified: evergreen-ils.org/communicate.php
===================================================================
--- evergreen-ils.org/communicate.php 2011-04-13 02:24:15 UTC (rev 1338)
+++ evergreen-ils.org/communicate.php 2011-04-13 03:02:05 UTC (rev 1339)
@@ -23,10 +23,10 @@
<p class="content">
Once it's out there, it's public.</p>
<ul class="bullet">
- <li>
+ <li class="content">
Technically, administrators can delete things, but the content may be mirrored, has feeds and is in the Google cache & other search engines indexes, so deleting something doesn't make it go away.
</li>
- <li>
+ <li class="content">
<span style="font-weight: bold;">Our policy</span> is to leave the archives alone except in exceptional cases.<br /> Please send a request promptly to <a href="mailto:feedback at evergreen-ils.org" class="mail JSnocheck" title="Posting Deletion">feedback at evergreen-ils.org</a> if you believe you are the exception.
</li>
</ul>
Modified: evergreen-ils.org/documentation.php
===================================================================
--- evergreen-ils.org/documentation.php 2011-04-13 02:24:15 UTC (rev 1338)
+++ evergreen-ils.org/documentation.php 2011-04-13 03:02:05 UTC (rev 1339)
@@ -14,24 +14,24 @@
<!--end side-->
<div id="pagebody">
<h1>Documentation</h1>
-<p>This is the documentation section of the Evergreen project.</p>
+<p class="content">This is the documentation section of the Evergreen project.</p>
<a name="official"></a>
<h2>Official documentation</h2>
<ul class="bullet">
-<li><a href="http://docs.evergreen-ils.org/">Official documentation for Evergreen 1.6 (draft)</a>: written and maintained by the <a href="http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig">Documentation Interest Group</a> (DIG).</li>
+<li class="content"><a href="http://docs.evergreen-ils.org/">Official documentation for Evergreen 1.6 (draft)</a>: written and maintained by the <a href="http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig">Documentation Interest Group</a> (DIG).</li>
</ul>
<a name="process"></a>
<h2>Development process documentation</h2>
<ul class="bullet">
-<li> <a href="/dokuwiki/doku.php?id=faqs:evergreen_roadmap">Evergreen Roadmap</a>: Current development milestones</li>
-<li> <a href="/dokuwiki/doku.php?id=contributing">How to participate in development</a>: procedures and conventions for contributing code to the Evergreen project</li>
-<li> <a href="/dokuwiki/doku.php?id=faqs:evergreen_feature_request_procedures">Feature Request Procedure</a>: Have an idea for a feature for Evergreen? This is how to submit it!</li>
-<li> <a href="http://svn.open-ils.org/trac/ILS/timeline">Watch us work</a>: the running change log for the Evergreen code repository</li>
+<li class="content"> <a href="/dokuwiki/doku.php?id=faqs:evergreen_roadmap">Evergreen Roadmap</a>: Current development milestones</li>
+<li class="content"> <a href="/dokuwiki/doku.php?id=contributing">How to participate in development</a>: procedures and conventions for contributing code to the Evergreen project</li>
+<li class="content"> <a href="/dokuwiki/doku.php?id=faqs:evergreen_feature_request_procedures">Feature Request Procedure</a>: Have an idea for a feature for Evergreen? This is how to submit it!</li>
+<li class="content"> <a href="http://svn.open-ils.org/trac/ILS/timeline">Watch us work</a>: the running change log for the Evergreen code repository</li>
</ul>
<a name="dokuwiki"></a>
<h2>Wiki documentation</h2>
<ul class="bullet">
-<li> <a href="/dokuwiki/doku.php">Evergreen wiki</a>: End-user, system administrator, and software developer materials.<br /> The wiki serves as an incubator for much of the material that ends up in the official documentation.</li>
+<li class="content"> <a href="/dokuwiki/doku.php">Evergreen wiki</a>: End-user, system administrator, and software developer materials.<br /> The wiki serves as an incubator for much of the material that ends up in the official documentation.</li>
</ul>
</div>
<!--end pagebody-->
Modified: evergreen-ils.org/downloads.php
===================================================================
--- evergreen-ils.org/downloads.php 2011-04-13 02:24:15 UTC (rev 1338)
+++ evergreen-ils.org/downloads.php 2011-04-13 03:02:05 UTC (rev 1339)
@@ -110,14 +110,14 @@
</p>
<p class="content">The <a href="/%7Edenials/Evergreen_2_0_3_Squeeze.zip">2.0.3, Debian Squeeze</a> (754 MB) virtual image (<a href="/%7Edenials/Evergreen_2_0_3_Squeeze/README">README</a>) and the <a href="/%7Edenials/Evergreen_1_6_1_4_Lenny.zip">Evergreen 1.6.1.4, Debian 5.0 (Lenny)</a> virtual image should run under recent versions of VirtualBox or VMWare.</p>
<h3><a name="pos">Bug Reports</a></h3>
-<p><a name="bugs">Please report any Evergreen bugs/wishlist on <a href="https://bugs.launchpad.net/evergreen">Launchpad</a>.</p>
+<p class="content"><a name="bugs">Please report any Evergreen bugs/wishlist on <a href="https://bugs.launchpad.net/evergreen">Launchpad</a>.</p>
<p class="content">To submit a vulnerability please email your report to <a href="mailto:open-ils-security at esilibrary.com">open-ils-security at esilibrary.com</a>.</p>
<h3><a name="code_museum">Evergreen Code Museum<br />
</a></h3>
-<p><a name="code_museum">Older versions of Evergreen software are available from the </a><a href="code_museum.php">Evergreen Code Museum</a>.</p>
+<p class="content"><a name="code_museum">Older versions of Evergreen software are available from the </a><a href="code_museum.php">Evergreen Code Museum</a>.</p>
<a name="repos" /><h3><a name="repos">Source Code Repository</a></h3>
<p class="content"><a name="repos">A Trac instance sits atop the Subversion repositories for Evergreen and OpenSRF. You can find both repositories at </a><a href="http://svn.open-ils.org/">svn.open-ils.org</a>. Here is the running change log for the Evergreen code repository: <a href="http://svn.open-ils.org/trac/ILS/timeline">watch us work</a>.</p>
-<p>Trac sends code commits to two public Evergreen mailing lists:</p>
+<p class="content">Trac sends code commits to two public Evergreen mailing lists:</p>
<ul class="bullet"><li> For Evergreen commits, subscribe to <a href="http://list.georgialibraries.org/mailman/listinfo/open-ils-commits">open-ils-commits</a></li><li> For OpenSRF commits, subscribe to <a href="http://list.georgialibraries.org/mailman/listinfo/opensrf-commits">opensrf-commits</a></li></ul>
</div>
<!--end pagebody-->
Modified: evergreen-ils.org/irc.php
===================================================================
--- evergreen-ils.org/irc.php 2011-04-13 02:24:15 UTC (rev 1338)
+++ evergreen-ils.org/irc.php 2011-04-13 03:02:05 UTC (rev 1339)
@@ -20,12 +20,12 @@
<p class="content">Technically, administrators can delete things, but the content may be mirrored, has feeds and is in the Google cache & other search engines indexes, so deleting something doesn't make it go away. Our policy is to leave the archives alone except in exceptional cases. Please send a request promptly to <a href="mailto:feedback at evergreen-ils.org" class="mail JSnocheck" title="Posting Deletion">feedback at evergreen-ils.org</a> if you believe you are the exception.</p>
<h3>Links</h3>
<ul class="bullet">
-<li><a href="/irc_logs/">Browse the logs for #Evergreen</a></li>
-<li><a href="http://evergreen-ils.org/dokuwiki/doku.php?id=community:irc_channel">Who's who on the #evergreen channel</a></li>
-<li><a href="http://www.livinginternet.com/r/ru_chatq.htm">IRC
+<li class="content"><a href="/irc_logs/">Browse the logs for #Evergreen</a></li>
+<li class="content"><a href="http://evergreen-ils.org/dokuwiki/doku.php?id=community:irc_channel">Who's who on the #evergreen channel</a></li>
+<li class="content"><a href="http://www.livinginternet.com/r/ru_chatq.htm">IRC
Etiquette</a></li>
-<li><a href="http://paste.lisp.org/new/evergreen">"Paste-bot" for IRC channel</a> (use this for sharing large error messages, etc.)</li>
-<li><a target="_blank"
+<li class="content"><a href="http://paste.lisp.org/new/evergreen">"Paste-bot" for IRC channel</a> (use this for sharing large error messages, etc.)</li>
+<li class="content"><a target="_blank"
href="http://webchat.freenode.net/?channels=evergreen">Join
#Evergreen through a web gateway</a> courtesy of Freenode.
</li>
Modified: evergreen-ils.org/opensrf.php
===================================================================
--- evergreen-ils.org/opensrf.php 2011-04-13 02:24:15 UTC (rev 1338)
+++ evergreen-ils.org/opensrf.php 2011-04-13 03:02:05 UTC (rev 1339)
@@ -86,11 +86,11 @@
<p class="content"><a name="opensrf_development">Dan Scott has written a two part article which is a detailed introduction to OpenSRF. "This article introduces OpenSRF, how to build OpenSRF services through code examples, explains the technical foundations on which OpenSRF is built, and evaluates OpenSRF’s value in the context of Evergreen" - "</a><a href="http://journal.code4lib.org/articles/3365">Easing gently into OpenSRF, Part 1</a>" and "<a href="http://journal.code4lib.org/articles/3284">Easing gently into OpenSRF, Part 2</a>".</p>
<p class="content"><a name="opensrf_development">He also has an introductory workshop available along with some Perl/JavaScript examples - "</a><a href="/%7Edenials/workshop.html">Evergreen development</a>".</p>
<h3><a name="pos">OpenSRF Bug Reports</a></h3>
-<p><a name="bugs">Please report any OpenSRF bugs on <a href="https://bugs.launchpad.net/opensrf">Launchpad</a>.</p>
+<p class="content"><a name="bugs">Please report any OpenSRF bugs on <a href="https://bugs.launchpad.net/opensrf">Launchpad</a>.</p>
<p class="content">To report a vulnerability please email your report to <a href="mailto:open-ils-security at esilibrary.com">open-ils-security at esilibrary.com</a>.</p>
<a name="repos" /><h3><a name="repos">Source Code Repository</a></h3>
<p class="content"><a name="repos">A Trac instance sits atop the Subversion repository for OpenSRF and is available at </a><a href="http://svn.open-ils.org/trac/OpenSRF">svn.open-ils.org/trac/OpenSRF</a>. Here is the running change log for the OpenSRF code repository: <a href="http://svn.open-ils.org/trac/OpenSRF/timeline">watch us work</a>.</p>
-<p>Trac sends code commits to public OpenSRF commits mailing lists:</p>
+<p class="content">Trac sends code commits to public OpenSRF commits mailing lists:</p>
<ul class="bullet"><li> For OpenSRF commits, subscribe to <a href="http://list.georgialibraries.org/mailman/listinfo/opensrf-commits">opensrf-commits</a></li></ul>
</div>
<!--end pagebody-->
More information about the open-ils-commits
mailing list