[30360] trunk/www/contact.php

source_changes at macosforge.org source_changes at macosforge.org
Thu Oct 25 11:28:57 PDT 2007


Revision: 30360
          http://trac.macosforge.org/projects/macports/changeset/30360
Author:   jmpp at macports.org
Date:     2007-10-25 11:28:56 -0700 (Thu, 25 Oct 2007)

Log Message:
-----------
whitespace.

Modified Paths:
--------------
    trunk/www/contact.php

Modified: trunk/www/contact.php
===================================================================
--- trunk/www/contact.php	2007-10-25 18:25:02 UTC (rev 30359)
+++ trunk/www/contact.php	2007-10-25 18:28:56 UTC (rev 30360)
@@ -13,8 +13,8 @@
 
     <h2 class="hdr">Getting in Touch With Us</h2>
 
-    <p>There are a number of ways in which you can get in contact with people involved with the MacPorts project, depending on
-    who you need to contact and the type of support you're looking for:</p>
+    <p>There are a number of ways in which you can get in contact with people involved with the MacPorts project, depending
+    on who you need to contact and the type of support you're looking for:</p>
 
     <ul>
         <li><a href="#Lists">Public Mailing Lists</a></li>
@@ -33,19 +33,20 @@
 
     <ol>
         <li>First and foremost, check the MacPorts <a href="<?php print $guide_url; ?>">Documentation</a>, man pages, <a
-        href="<?php print $trac_url . 'wiki/FAQ'; ?>">FAQ</a> and <a href="<?php print $trac_url . 'wiki/ProblemHotlist'; ?>">
-        problems hotlist</a>.</li>
+        href="<?php print $trac_url . 'wiki/FAQ'; ?>">FAQ</a> and <a href="<?php print $trac_url . 'wiki/ProblemHotlist';
+        ?>">problems hotlist</a>.</li>
         <li>Second, check the archives of the appropriate mailing list you intend to post to (below) to see if your question
         has already been asked and dealt with.</li>
-        <li>Finally, if you still haven't found the answer to your problem, send e-mail to the appropriate mailing list with
-        the following information:
+        <li>Finally, if you still haven't found the answer to your problem, send e-mail to the appropriate mailing list
+        with the following information:
             <ul>
                 <li>output generated by the &ldquo;<kbd>port</kbd>&rdquo; command's <kbd>-v</kbd> (verbose) or <kbd>-d</kbd>
                 (debug) flags;</li>
                 <li>platform details such as operating system version (e.g. 10.4.10) and hardware architecture (e.g. Intel
-                or PowerPC) -- the &ldquo;<kbd>sw_vers</kbd>&rdquo; and &ldquo;<kbd>uname -a</kbd>&rdquo; commands are of great
-                help in this regard;</li>
-                <li>any third party software that may exist in places such as <kbd>/usr/local</kbd> and/or <kbd>/sw</kbd>.</li>
+                or PowerPC) -- the &ldquo;<kbd>sw_vers</kbd>&rdquo; and &ldquo;<kbd>uname -a</kbd>&rdquo; commands are of
+                great help in this regard;</li>
+                <li>any third party software that may exist in places such as <kbd>/usr/local</kbd> and/or <kbd>/sw</kbd>.
+                </li>
             </ul>
         </li>
     </ol>
@@ -62,25 +63,27 @@
         </li>
         <li><a href="http://lists.macosforge.org/mailman/listinfo/macports-dev/">MacPorts Developers</a>
         (<a href="http://lists.macosforge.org/pipermail/macports-dev/">archives</a>):
-            <p>Where project members and contributors discuss the MacPorts &ldquo;base&rdquo; system itself and future development plans,
-            and related &ldquo;Portfile&rdquo; writing best practices. A low volume list.</p>
+            <p>Where project members and contributors discuss the MacPorts &ldquo;base&rdquo; system itself and future
+            development plans, and related &ldquo;Portfile&rdquo; writing best practices. A low volume list.</p>
         </li>
         <li><a href="http://lists.macosforge.org/mailman/listinfo/macports-changes/">MacPorts Changes</a>
         (<a href="http://lists.macosforge.org/pipermail/macports-changes/">archives</a>):
-            <p>Read-only list of changes to our <a href="<?php print $svn_url; ?>">SVN repository</a> for both &rdquo;base&ldquo; code and
-            Portfiles, among others. A low to moderate volume list.</p>
+            <p>Read-only list of changes to our <a href="<?php print $svn_url; ?>">SVN repository</a> for both &rdquo;base&ldquo;
+            code and Portfiles, among others. A low to moderate volume list.</p>
         </li>
         <li><a href="http://lists.macosforge.org/mailman/listinfo/macports-tickets/">MacPorts Tickets</a>
         (<a href="http://lists.macosforge.org/pipermail/macports-tickets/">archives</a>):
-            <p>Ticket activity on our <a href="<?php print $trac_url; ?>">Trac bug tracker</a>. This list is currently disabled, however.</p>
+            <p>Ticket activity on our <a href="<?php print $trac_url; ?>">Trac bug tracker</a>. This list is currently
+            disabled, however.</p>
         </li>
     </ul>
 
-    <p>Note that due to spam control policies you must subscribe in order to post to any of these lists. Members are expected to abide
-    by the very simple <a href="http://www.dtcc.edu/cs/rfc1855.html">Netiquette guidelines</a> that are common to most open forums when
-    posting; of particular relevance is sticking to plain text messages, our language of choice (English), and reducing the number and
-    size of attachments in any way possible (e.g, by using paste bins such as <a href="http://paste.lisp.org/new/macports">lisppaste</a>
-    or <a href="http://pastie.caboo.se">pastie</a> and passing along the paste URL rather than full error messages).</p>
+    <p>Note that due to spam control policies you must subscribe in order to post to any of these lists. Members are
+    expected to abide by the very simple <a href="http://www.dtcc.edu/cs/rfc1855.html">Netiquette guidelines</a> that are
+    common to most open forums when posting; of particular relevance is sticking to plain text messages, our language of
+    choice (English), and reducing the number and size of attachments in any way possible (e.g, by using paste bins such
+    as <a href="http://paste.lisp.org/new/macports">lisppaste</a> or <a href="http://pastie.caboo.se">pastie</a> and
+    passing along the paste URL rather than full error messages).</p>
 
 
     <h3 class="subhdr" id="portmgr">Administrative Contacts</h3>
@@ -92,51 +95,52 @@
     feel is of private nature (like the interaction between MacPorts and NDA'd software).</p>
 
     <p>This is also where you should turn to if you are a developer and/or a contributor interested in joning the MacPorts
-    team with full write access to our SVN repository and Wiki pages, either to work on MacPorts itself or as a ports maintainer.
-    Please read the <a href="<?php print $guide_url . '#project.membership'; ?>">documentation available</a> on joining
-    for more information.</p>
+    team with full write access to our SVN repository and Wiki pages, either to work on MacPorts itself or as a ports
+    maintainer. Please read the <a href="<?php print $guide_url . '#project.membership'; ?>">documentation available</a>
+    on joining for more information.</p>
 
 
     <h3 class="subhdr" id="Bugs">Bug Tracker</h3>
 
     <p>We use the popular <a href="http://trac.edgewall.org/">Trac</a> web-based tool for our <a href="<?php print $trac_url .
     'roadmap'; ?>">bug tracking</a> and <a href="<?php print $trac_url . 'wiki'; ?>">Wiki</a> needs, thus buying ourselves
-    seamless read-only integration with our SVN repository through its <a href="<?php print $trac_url . 'browser'; ?>">source
-    browser</a> and the project <a href="<?php print $trac_url . 'timeline'; ?>">timeline</a> (where ticket activity can also
-    be viewed). Note that in order to interact with Trac for anything other than read only operations, you need to <a
-    href="http://www.macosforge.org/wp-register.php">register</a> with Mac OS Forge for a Wordpress/Trac combined account.</p>
+    seamless read-only integration with our SVN repository through its <a href="<?php print $trac_url . 'browser'; ?>">
+    source browser</a> and the project <a href="<?php print $trac_url . 'timeline'; ?>">timeline</a> (where ticket activity
+    can also be viewed). Note that in order to interact with Trac for anything other than read only operations, you need
+    to <a href="http://www.macosforge.org/wp-register.php">register</a> with Mac OS Forge for a Wordpress/Trac combined
+    account.</p>
 
     <p>If you think you've found a bug either in one of our <a href="ports.php">available ports</a> or in MacPorts itself,
     feel free to <a href="<?php print $trac_url . 'newticket'; ?>">open a ticket</a> to help us look into the problem.
-    Please keep in mind that we usually get a fairly high number of duplicate reports for common problems and therefore appreciate
-    any help we can get in the process of streamlining our ticket dutties. <a href="<?php print $trac_url . 'search'; ?>">
-    Searching</a> the Trac database &amp; mailing list archives (above), and reading our <a href="<?php print $trac_url . 'wiki/FAQ'; ?>">
-    FAQ</a> &amp; <a href="<?php print $trac_url . 'wiki/ProblemHotlist'; ?>">problems hotlist</a> to see if your report has already
-    been filed is recommended, as well as reading the <a href="<?php print $guide_url . '#project.tickets'; ?>"> ticketing guidelines</a>
-    that will help you create a better report.</p>
+    Please keep in mind that we usually get a fairly high number of duplicate reports for common problems and therefore
+    appreciate any help we can get in the process of streamlining our ticket dutties. <a href="<?php print $trac_url .
+    'search'; ?>">Searching</a> the Trac database &amp; mailing list archives (above), and reading our <a href="<?php print
+    $trac_url . 'wiki/FAQ'; ?>">FAQ</a> &amp; <a href="<?php print $trac_url . 'wiki/ProblemHotlist'; ?>">problems hotlist</a>
+    to see if your report has already been filed is recommended, as well as reading the <a href="<?php print $guide_url .
+    '#project.tickets'; ?>"> ticketing guidelines</a>that will help you create a better report.</p>
 
-    <p>Viewing existing tickets through the facilities offered by predefined and custom <a href="<?php print $trac_url . 'report'; ?>">
-    ticket reports</a> that allow for detailed queries is also available.</p>
+    <p>Viewing existing tickets through the facilities offered by predefined and custom <a href="<?php print $trac_url .
+    'report'; ?>">ticket reports</a> that allow for detailed queries is also available.</p>
 
 
     <h3 class="subhdr" id="IRC">IRC</h3>
 
-    <p>For a more real-time discussion of any MacPorts related topic, the <a href="irc://chat.freenode.net/#MacPorts">#MacPorts</a>
-    channel on the <a href="http://freenode.net/">Freenode network</a> is where some of us usually hang out, MacPorts developers
-    and community members alike. Everyone is free and welcomed to join us, even if it is for a random fun conversation or
-    a productive troubleshooting session, but please keep in mind that no one is guaranteed to be around at any particular
-    moment and that channel members are not obligated to answer your questions. If you fail to get any traction at time,
-    do not take it personally and simply direct your questions to the mailing lists instead.</p>
+    <p>For a more real-time discussion of any MacPorts related topic, the <a href="irc://chat.freenode.net/#MacPorts">
+    #MacPorts</a>channel on the <a href="http://freenode.net/">Freenode network</a> is where some of us usually hang out,
+    MacPorts developers and community members alike. Everyone is free and welcomed to join us, even if it is for a random
+    fun conversation or a productive troubleshooting session, but please keep in mind that no one is guaranteed to be
+    around at any particular moment and that channel members are not obligated to answer your questions. If you fail to
+    get any traction at time, do not take it personally and simply direct your questions to the mailing lists instead.</p>
 
-    <p>The language of choice for the IRC channel is also English, for obvious reasons of universality, so sticking to it is
-    appreciated.</p>
+    <p>The language of choice for the IRC channel is also English, for obvious reasons of universality, so sticking to it
+    is appreciated.</p>
 
 
     <h3 class="subhdr" id="Individuals">Individuals</h3>
 
     <p>To find out what specific individuals are doing, visit the <a href="<?php print $trac_url . 'wiki/MacPortsDevelopers'; ?>">
-    team members page</a> on our Wiki and our <a href="http://cia.vc/stats/project/MacPorts">CIA project page</a>, which also shows
-    SVN commit activity and many other project statistics.</p>
+    team members page</a> on our Wiki and our <a href="http://cia.vc/stats/project/MacPorts">CIA project page</a>, which
+    also shows SVN commit activity and many other project statistics.</p>
 
 </div>
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20071025/9ec19255/attachment-0001.html


More information about the macports-changes mailing list