You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by co...@apache.org on 2014/01/27 15:41:03 UTC

svn commit: r895553 - in /websites/production/santuario/content: cache/main.pageCache contributing.html cprogramming.html download.html faq.html

Author: coheigea
Date: Mon Jan 27 14:41:02 2014
New Revision: 895553

Log:
Fixing website

Modified:
    websites/production/santuario/content/cache/main.pageCache
    websites/production/santuario/content/contributing.html
    websites/production/santuario/content/cprogramming.html
    websites/production/santuario/content/download.html
    websites/production/santuario/content/faq.html

Modified: websites/production/santuario/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/santuario/content/contributing.html
==============================================================================
--- websites/production/santuario/content/contributing.html (original)
+++ websites/production/santuario/content/contributing.html Mon Jan 27 14:41:02 2014
@@ -165,7 +165,7 @@ Apache Santuario -- contributing
 
 <p>This is a collection of tips for contributing to the project in a manner that is productive for all parties.</p>
 
-<ul><li>Every contribution is worthwhile. Even if the ensuing discussion proves it to be off-beam, then it may jog ideas for other people.</li><li>Use sensible and concise email subject headings. Search engines, and humans trying to browse a voluminous list, will respond favourably to a descriptive title.</li><li>Start new threads with a new Subject for new topics, rather than reusing the previous Subject line.</li><li>Keep each topic focused. If some new topic arises then start a new discussion. This leaves the original topic to continue uncluttered.</li><li>Whenever you decide to start a new topic, then start with a fresh new email message window. Do not use the "Reply to" button, because threaded mail-readers get confused (they utilise the In-reply-to header). If so, then your new topic will get lost in the previous thread and go unanswered.</li><li>Prepend your email subject line with a marker when that is appropriate, e.g. <a shape="rect" class="unresolved" href="#">Patch</a>, 
 <a shape="rect" class="unresolved" href="#">Proposal</a>, <a shape="rect" class="unresolved" href="#">RT</a> (Random Thought which quickly blossom into research topics <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)">, <a shape="rect" class="unresolved" href="#">STATUS</a> (development status of a certain facility).</li><li>When making changes to XML documentation, or any XML document for that matter, use a <a shape="rect" class="external-link" href="http://www.oasis-open.org/cover/" rel="nofollow">validating parser</a> (one that is tried and true is <a shape="rect" class="external-link" href="http://openjade.sourceforge.net/" rel="nofollow">OpenSP/onsgmls</a>). This procedure will detect errors without having to go through the whole build docs process to find them. Do not expect Forrest or the build system to de
 tect the validation errors for you - they can do it, but that is not their purpose. (Anyway, nsgmls validation error messages are more informative.)</li><li>Remember that most people are participating in development on a volunteer basis and in their "spare time". These enthusiasts will attempt to respond to issues. It may take a little while to get your answers.</li><li>Research your topic thoroughly before beginning to discuss a new development issue. Search and browse through the email archives - your issue may have been discussed before. Do not just perceive a problem and then rush out with a question - instead, delve.</li><li>Try to at least offer a partial solution and not just a problem statement.</li><li>Take the time to clearly explain your issue and write a concise email message. Less confusion facilitates fast and complete resolution.</li><li>Do not bother to send an email reply that simply says "thanks". When the issue is resolved, that is the finish - end of thread. Redu
 ce clutter.</li><li>You would usually do any development work against the HEAD branch of CVS.</li><li>When sending a patch, you usually do not need to worry about which CVS branch it should be applied to. The maintainers of the repository will decide.</li><li>If an issue starts to get bogged down in list discussion, then it may be appropriate to go into private off-list discussion with a few interested other people. Spare the list from the gory details. Report a summary back to the list to finalise the thread.</li><li>Become familiar with the mailing lists. As you browse and search, you will see the way other people do things. Follow the leading examples.</li></ul>
+<ul><li>Every contribution is worthwhile. Even if the ensuing discussion proves it to be off-beam, then it may jog ideas for other people.</li><li>Use sensible and concise email subject headings. Search engines, and humans trying to browse a voluminous list, will respond favourably to a descriptive title.</li><li>Start new threads with a new Subject for new topics, rather than reusing the previous Subject line.</li><li>Keep each topic focused. If some new topic arises then start a new discussion. This leaves the original topic to continue uncluttered.</li><li>Whenever you decide to start a new topic, then start with a fresh new email message window. Do not use the "Reply to" button, because threaded mail-readers get confused (they utilise the In-reply-to header). If so, then your new topic will get lost in the previous thread and go unanswered.</li><li>Prepend your email subject line with a marker when that is appropriate, e.g. <a shape="rect" class="createlink" href="https://cwiki.
 apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&amp;title=Patch&amp;linkCreation=true&amp;fromPageId=24193313">Patch</a>, <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&amp;title=Proposal&amp;linkCreation=true&amp;fromPageId=24193313">Proposal</a>, <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&amp;title=RT&amp;linkCreation=true&amp;fromPageId=24193313">RT</a> (Random Thought which quickly blossom into research topics <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)">, <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&amp;title=STATUS&amp;linkCreation=true&amp;fromPageId=24193313">STAT
 US</a> (development status of a certain facility).</li><li>When making changes to XML documentation, or any XML document for that matter, use a <a shape="rect" class="external-link" href="http://www.oasis-open.org/cover/" rel="nofollow">validating parser</a> (one that is tried and true is <a shape="rect" class="external-link" href="http://openjade.sourceforge.net/" rel="nofollow">OpenSP/onsgmls</a>). This procedure will detect errors without having to go through the whole build docs process to find them. Do not expect Forrest or the build system to detect the validation errors for you - they can do it, but that is not their purpose. (Anyway, nsgmls validation error messages are more informative.)</li><li>Remember that most people are participating in development on a volunteer basis and in their "spare time". These enthusiasts will attempt to respond to issues. It may take a little while to get your answers.</li><li>Research your topic thoroughly before beginning to discuss a new de
 velopment issue. Search and browse through the email archives - your issue may have been discussed before. Do not just perceive a problem and then rush out with a question - instead, delve.</li><li>Try to at least offer a partial solution and not just a problem statement.</li><li>Take the time to clearly explain your issue and write a concise email message. Less confusion facilitates fast and complete resolution.</li><li>Do not bother to send an email reply that simply says "thanks". When the issue is resolved, that is the finish - end of thread. Reduce clutter.</li><li>You would usually do any development work against the HEAD branch of CVS.</li><li>When sending a patch, you usually do not need to worry about which CVS branch it should be applied to. The maintainers of the repository will decide.</li><li>If an issue starts to get bogged down in list discussion, then it may be appropriate to go into private off-list discussion with a few interested other people. Spare the list from 
 the gory details. Report a summary back to the list to finalise the thread.</li><li>Become familiar with the mailing lists. As you browse and search, you will see the way other people do things. Follow the leading examples.</li></ul>
 </div>
            </div>
            <!-- Content -->

Modified: websites/production/santuario/content/cprogramming.html
==============================================================================
--- websites/production/santuario/content/cprogramming.html (original)
+++ websites/production/santuario/content/cprogramming.html Mon Jan 27 14:41:02 2014
@@ -31,6 +31,7 @@ rce">
   <link href='http://cxf.apache.org/resources/highlighter/styles/shThemeCXF.css' rel='stylesheet' type='text/css' />
   <script src='http://cxf.apache.org/resources/highlighter/scripts/shCore.js' type='text/javascript'></script>
   <script src='http://cxf.apache.org/resources/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
+  <script src='http://cxf.apache.org/resources/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
   
   <script type="text/javascript">
   SyntaxHighlighter.defaults['toolbar'] = false;

Modified: websites/production/santuario/content/download.html
==============================================================================
--- websites/production/santuario/content/download.html (original)
+++ websites/production/santuario/content/download.html Mon Jan 27 14:41:02 2014
@@ -30,7 +30,7 @@ rce">
   <link href='http://cxf.apache.org/resources/highlighter/styles/shCoreCXF.css' rel='stylesheet' type='text/css' />
   <link href='http://cxf.apache.org/resources/highlighter/styles/shThemeCXF.css' rel='stylesheet' type='text/css' />
   <script src='http://cxf.apache.org/resources/highlighter/scripts/shCore.js' type='text/javascript'></script>
-  <script src='http://cxf.apache.org/resources/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
+  <script src='http://cxf.apache.org/resources/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
   
   <script type="text/javascript">
   SyntaxHighlighter.defaults['toolbar'] = false;

Modified: websites/production/santuario/content/faq.html
==============================================================================
--- websites/production/santuario/content/faq.html (original)
+++ websites/production/santuario/content/faq.html Mon Jan 27 14:41:02 2014
@@ -30,7 +30,7 @@ rce">
   <link href='http://cxf.apache.org/resources/highlighter/styles/shCoreCXF.css' rel='stylesheet' type='text/css' />
   <link href='http://cxf.apache.org/resources/highlighter/styles/shThemeCXF.css' rel='stylesheet' type='text/css' />
   <script src='http://cxf.apache.org/resources/highlighter/scripts/shCore.js' type='text/javascript'></script>
-  <script src='http://cxf.apache.org/resources/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
+  <script src='http://cxf.apache.org/resources/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
   
   <script type="text/javascript">
   SyntaxHighlighter.defaults['toolbar'] = false;