[30284] trunk/www
source_changes at macosforge.org
source_changes at macosforge.org
Tue Oct 23 13:37:18 PDT 2007
Revision: 30284
http://trac.macosforge.org/projects/macports/changeset/30284
Author: jmpp at macports.org
Date: 2007-10-23 13:37:17 -0700 (Tue, 23 Oct 2007)
Log Message:
-----------
Various improvements & fixes to the contact.php page, partly based on very helpful feedback from Ernie. Thanks!
Modified Paths:
--------------
trunk/www/contact.php
trunk/www/macports.css
Modified: trunk/www/contact.php
===================================================================
--- trunk/www/contact.php 2007-10-23 19:59:15 UTC (rev 30283)
+++ trunk/www/contact.php 2007-10-23 20:37:17 UTC (rev 30284)
@@ -13,89 +13,125 @@
<h2 class="hdr">Getting in Touch With Us</h2>
- <p>There are a number of ways in which you can get in contact with the MacPorts project, either the core developers
- and ports maintainers behind it and/or members of its broad user base.</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>
+ <li><a href="#portmgr">Administrative Contacts</a></li>
+ <li><a href="#Bugs">Bug Reports</a></li>
+ <li><a href="#IRC">IRC</a></li>
+ <li><a href="#Individuals">Individuals</a></li>
+ </ul>
- <h3 class="subhdr" id="lists">Mailing Lists</h3>
- <p>The MacPorts project hosts a number of purpose specific mailing lists you can freely subscribe to:</p>
+ <h3>Getting Help</h3>
+ <p>If you're looking for help to troubleshoot a particular failure installing or using MacPorts, providing us with as
+ much information about your host platform as you can gather will help us help you in turn to look into the problem.
+ The following simple steps comprise our recommended procedure to obtain support:</p>
+
+ <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>
+ <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:
+ <ul>
+ <li>output generated by the “<kbd>port</kbd>” 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 “<kbd>sw_vers</kbd>” and “<kbd>uname -a</kbd>” 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>
+
+
+ <h3 class="subhdr" id="Lists">Public Mailing Lists</h3>
+
+ <p>The MacPorts project hosts a number of specialized mailing lists you can freely subscribe to:</p>
+
<ul>
- <li><a href="http://lists.macosforge.org/mailman/listinfo/macports-users/">MacPorts Users</a> mailing list,
- our main support forum for MacPorts usage and general discussion of MacPorts installed software. A moderate
- volume list with archives located <a href="http://lists.macosforge.org/pipermail/macports-users/">here</a>.</li>
- <li><a href="http://lists.macosforge.org/mailman/listinfo/macports-dev/">MacPorts Developers</a> mailing list,
- an open forum meant for the development of MacPorts itself and its “Portfiles”. This is where all
- discussion pertaining to our development roadmap and Portfile writing best practices are held. A low volume list
- with archives located <a href="http://lists.macosforge.org/pipermail/macports-dev/">here</a>.</li>
- <li><a href="http://lists.macosforge.org/mailman/listinfo/macports-changes/">MacPorts Changes</a> mailing list,
- where the logs of commits to our <a href="<?php print $svn_url; ?>">SVN repository</a> get posted to (including
- commits to both the ”base“ code and ports tree, among others). A low to moderate volume list with
- archives located <a href="http://lists.macosforge.org/pipermail/macports-changes/">here</a>.</li>
- <li><a href="http://lists.macosforge.org/mailman/listinfo/macports-tickets/">MacPorts Tickets</a> mailing list,
- where ticket activity on our <a href="<?php print $trac_url; ?>">Trac bug tracker</a> is posted to. This list
- is currently disabled, however.</li>
+ <li><a href="http://lists.macosforge.org/mailman/listinfo/macports-users/">MacPorts Users</a>
+ (<a href="http://lists.macosforge.org/pipermail/macports-users/">archives</a>):
+ <p>General discussion of how to install and use MacPorts. A moderate volume list.</p>
+ </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 “base” system itself and future development plans,
+ and related “Portfile” 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 ”base“ 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>
+ </li>
</ul>
- <p>Even though everyone is free to subscribe to any of our mailing lists, they are closed to non-subscribers due to
- basic spam control policies. 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), reducing the number and size of attachments in any way possible and,
- last but not least, searching the archives before raising a question.</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>
- <p>Needless to say, providing us with as much information as you can gather will help us help you in turn diagnosing any
- problems you may be experiencing, so always remember to use <kbd>port(1)</kbd>'s <kbd>-v</kbd> or <kbd>-d</kbd> flags for
- verbose and debugging output if you want to post an error message MacPorts is giving you, for example. Platform information
- such as operating system (e.g. 10.4.10) and any third party software that may exist in <kbd>/usr/local</kbd> is also very
- useful information.</p>
+ <h3 class="subhdr" id="portmgr">Administrative Contacts</h3>
+
+ <!-- we need a link down here pointing to some page detailing the portmgr team - guide authors? ;-) -->
<p>The private and read-only “<?php print obfuscate_email("macports-mgr at lists.macosforge.org"); ?>” mailing
-<!-- we need a link down here pointing to some page detailing the portmgr team - guide authors? ;-) -->
list is where you should send mail to in case you need to get in touch with the <a href="">MacPorts management team</a>
- (A.K.A. “portmgr”), in case you have any administrative request or if you wish to discuss anything you mightd
+ (A.K.A. “portmgr”), in case you have any administrative request or if you wish to discuss anything you might
feel is of private nature (like the interaction between MacPorts and NDA'd software).</p>
- <h3 class="subhdr">Bug Tracker</h3>
+ <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 viewing only operations, you need to <a
+ 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 database and reading our <a href="<?php print $trac_url . 'wiki/FAQ'; ?>">FAQ</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>
+ Searching</a> the Trac database & mailing list archives (above), and reading our <a href="<?php print $trac_url . 'wiki/FAQ'; ?>">
+ FAQ</a> & <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 of predefined and custom <a href="<?php print $trac_url . 'report'; ?>">
- reports</a> that allow you to customize 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">IRC</h3>
+ <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 any time,
+ 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>
- <h3 class="subhdr">Other</h3>
+ <h3 class="subhdr" id="Individuals">Individuals</h3>
- <p>Other miscellaneous venues you can use to learn about the MacPorts project and its activities are the <a href="<?php print
- $trac_url . 'wiki/MacPortsDevelopers'; ?>">team members page</a> in our Wiki and our CIA <a href="http://cia.vc/stats/project/MacPorts">
- project page</a>, where you can also view our SVN commit activity and many other types of project statistics.</p>
+ <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>
</div>
Modified: trunk/www/macports.css
===================================================================
--- trunk/www/macports.css 2007-10-23 19:59:15 UTC (rev 30283)
+++ trunk/www/macports.css 2007-10-23 20:37:17 UTC (rev 30284)
@@ -142,6 +142,19 @@
max-width: 700px;
}
+#content li {
+ margin: 0 0 7px 0;
+}
+
+#content li p {
+ margin: 5px 0 15px 0;
+ padding: 0 0 0 20px;
+}
+
+#content li ul {
+ margin: 7px 0 0 0;
+}
+
.warning {
background: #FCC;
border: 2px solid #F66;
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20071023/ddd7d48f/attachment.html
More information about the macports-changes
mailing list