source: trunk/www/contact.php @ 149535

Last change on this file since 149535 was 108734, checked in by macsforever2000@…, 7 years ago

contacts.php: Fix redirects.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Id
  • Property svn:mime-type set to text/x-php
File size: 9.4 KB
Line 
1<?php
2    /* -*- coding: utf-8; mode: php; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:set fenc=utf-8 filetype=php et sw=4 ts=4 sts=4: */
3    /* $Id: contact.php 108734 2013-07-31 19:33:41Z macsforever2000@macports.org $ */
4    /* Copyright (c) 2007, The MacPorts Project. */
5    include_once("includes/common.inc");
6    print_header('The MacPorts Project -- Contact Us', 'utf-8');
7?>
8
9
10<div id="content">
11
12    <h2 class="hdr">Getting in Touch With Us</h2>
13
14    <p>There are a number of ways in which you can get in contact with people involved with The MacPorts Project, depending
15    on who you need to contact and the type of support and/or feedback you're looking for:</p>
16
17    <ul>
18        <li><a href="#Lists">Public Mailing Lists</a></li>
19        <li><a href="#PortMgr">Administrative Contact</a></li>
20        <li><a href="#Tracker">Bug Reports &amp; Contributions</a></li>
21        <li><a href="#IRC">IRC</a></li>
22        <li><a href="#Individuals">Individuals</a></li>
23    </ul>
24
25
26    <h3>Getting Help</h3>
27
28    <p>If you're looking for help to troubleshoot a particular failure installing or using MacPorts, providing us with as
29    much information about your host platform as you can gather will help us help you in turn to look into the problem.
30    The following simple steps comprise our recommended procedure to obtain support:</p>
31
32    <ol>
33        <li>First and foremost, check the MacPorts <a href="<?php print $guide_url; ?>">Documentation</a>, man pages, <a
34        href="<?php print $trac_url . 'wiki/FAQ'; ?>">FAQ</a> and <a href="<?php print $trac_url . 'wiki/ProblemHotlist';
35        ?>">problems hotlist</a>.</li>
36        <li>Second, check the archives of the appropriate mailing list you intend to post to (below) to see if your question
37        has already been asked and dealt with.</li>
38        <li>Finally, if you still haven't found the answer to your problem, send e-mail to the appropriate mailing list
39        with the following information:
40            <ul>
41                <li>output generated by the &#8220;<kbd>port</kbd>&#8221; command's <kbd>-v</kbd> (verbose) or <kbd>-d</kbd>
42                (debug) flags;</li>
43                <li>platform details such as operating system version (e.g. 10.4.10), hardware architecture (e.g. Intel
44                or PowerPC), and the version of Xcode installed -- the &#8220;<kbd>sw_vers</kbd>&#8221; and &#8220;<kbd>uname -a</kbd>&#8221; commands are of
45                great help in this regard;</li>
46                <li>any third party software that may exist in places such as <kbd>/usr/local</kbd> and/or <kbd>/sw</kbd>.
47                </li>
48            </ul>
49        </li>
50    </ol>
51
52
53    <h3 class="subhdr" id="Lists">Public Mailing Lists</h3>
54
55    <p>The MacPorts Project hosts a number of specialized mailing lists you can freely subscribe to:</p>
56
57    <ul>
58        <li><a href="https://lists.macosforge.org/mailman/listinfo/macports-users/">MacPorts Users</a>
59        (<a href="https://lists.macosforge.org/pipermail/macports-users/">archives</a>):
60            <p>General discussion of MacPorts installation and usage. A moderate volume list.</p>
61        </li>
62        <li><a href="https://lists.macosforge.org/mailman/listinfo/macports-dev/">MacPorts Developers</a>
63        (<a href="https://lists.macosforge.org/pipermail/macports-dev/">archives</a>):
64            <p>Where project members and contributors discuss the MacPorts &#8220;base&#8221; system itself and future
65            development plans, and related &#8220;Portfile&#8221; writing best practices. A low volume list.</p>
66        </li>
67        <li><a href="https://lists.macosforge.org/mailman/listinfo/macports-changes/">MacPorts Changes</a>
68        (<a href="https://lists.macosforge.org/pipermail/macports-changes/">archives</a>):
69            <p>Read-only, low to moderate volume list of changes to our <a href="<?php print $svn_url; ?>">SVN repository</a>
70            for both &#8220;base&#8221; code and Portfiles, among others.</p>
71        </li>
72        <li><a href="https://lists.macosforge.org/mailman/listinfo/macports-tickets/">MacPorts Tickets</a>
73        (<a href="https://lists.macosforge.org/pipermail/macports-tickets/">archives</a>):
74            <p>Read-only, moderate volume list of ticket activity on our <a href="<?php print $trac_url; ?>">Trac bug tracker
75            </a>.</p>
76        </li>
77        <li><a href="https://lists.macosforge.org/mailman/listinfo/macports-announce/">MacPorts Announce</a>
78        (<a href="https://lists.macosforge.org/pipermail/macports-announce/">archives</a>):
79            <p>Read-only, low volume list for project related major announcements.</p>
80        </li>
81    </ul>
82
83    <p>Note that due to spam control policies you must subscribe to our non read-only lists in order to post to any of them.
84    Members are expected to abide by the very simple <a href="http://tools.ietf.org/html/rfc1855">Netiquette guidelines</a>
85    that are common to most open forums when posting; of particular relevance is sticking to plain text messages, our language
86    of choice (English), and reducing the number and size of attachments in any way possible (e.g, by using paste bins such
87    as <a href="http://paste.lisp.org/new/macports">lisppaste</a> or <a href="http://pastie.org">Pastie</a> and
88    passing along the paste URL rather than full error messages).</p>
89
90
91    <h3 class="subhdr" id="PortMgr">Administrative Contact</h3>
92
93    <p>The private and read-only &#8220;<?php print obfuscate_email("macports-mgr@lists.macosforge.org"); ?>&#8221; mailing
94    list is where you should send mail to in case you need to get in touch with the The MacPorts Project's <a href="<?php print
95    $guide_url . '#project.portmgr'; ?>">management team</a> (A.K.A. &#8220;PortMgr&#8221;), in case you have any administrative
96    request or if you wish to discuss anything you might feel is of private nature (like the interaction between MacPorts and
97    NDA'd software).</p>
98
99    <p>This is also where you should turn to if you are a developer and/or a contributor interested in joning The MacPorts
100    Project with full write access to our SVN repository and Wiki pages, either to work on MacPorts itself or as a ports
101    maintainer. Please read the <a href="<?php print $guide_url . '#project.membership'; ?>">documentation available</a>
102    on joining for more information.</p>
103
104
105    <h3 class="subhdr" id="Tracker">Bug Tracker</h3>
106
107    <p>We use the popular <a href="http://trac.edgewall.org/">Trac</a> web-based tool for our <a href="<?php print $trac_url .
108    'roadmap'; ?>">bug tracking</a> and <a href="<?php print $trac_url . 'wiki'; ?>">Wiki</a> needs, thus buying ourselves
109    seamless read-only integration with our SVN repository through its <a href="<?php print $trac_url . 'browser'; ?>">
110    source browser</a> and the project <a href="<?php print $trac_url . 'timeline'; ?>">timeline</a> (where ticket activity
111    can also be viewed). Note that in order to interact with Trac for anything other than read only operations, you need
112    to <a href="<?php print $trac_url . 'auth/register/'; ?>">register</a> with Mac OS Forge for a Wordpress/Trac combined
113    account.</p>
114
115    <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, or
116    on the other hand if you'd like to make a contribution of any kind to the project, feel free to <a href="<?php print $trac_url
117    . 'newticket'; ?>">open a ticket</a> to help us look into the problem and/or submission. Please keep in mind that we
118    usually get a fairly high number of duplicate reports for common problems and therefore appreciate any help we can get in
119    the process of streamlining our ticket duties. <a href="<?php print $trac_url . 'search'; ?>">Searching</a> the Trac database
120    &amp; mailing list archives (above), and reading our <a href="<?php print $trac_url . 'wiki/FAQ'; ?>">FAQ</a> &amp;
121    <a href="<?php print $trac_url . 'wiki/ProblemHotlist'; ?>">problems hotlist</a> to see if your report has already been filed
122    is recommended, as well as reading the <a href="<?php print $guide_url . '#project.tickets'; ?>"> ticketing guidelines</a>
123    that will help you create a better report.</p>
124
125    <p>Viewing existing tickets through the facilities offered by predefined and custom <a href="<?php print $trac_url .
126    'report'; ?>">ticket reports</a> that allow for detailed queries is also available.</p>
127
128
129    <h3 class="subhdr" id="IRC">IRC</h3>
130
131    <p>For a more real-time discussion of any MacPorts related topic, the <a href="irc://chat.freenode.net/#MacPorts">
132    #MacPorts</a> channel on the <a href="http://freenode.net/">Freenode network</a> is where some of us usually hang out,
133    MacPorts developers and community members alike. Everyone is free and welcomed to join us, even if it is for a random
134    fun conversation or a productive troubleshooting session, but please keep in mind that no one is guaranteed to be
135    around at any particular moment and that channel members are not obligated to answer your questions. If you fail to
136    get any traction at time, do not take it personally and simply direct your questions to the mailing lists instead.</p>
137
138    <p>The language of choice for the IRC channel is also English, for obvious reasons of universality, so sticking to it
139    is appreciated.</p>
140
141
142    <h3 class="subhdr" id="Individuals">Individuals</h3>
143
144    <p>To find out who the people behind MacPorts are and what they are up to, visit the <a href="<?php print $trac_url . 
145    'wiki/MacPortsDevelopers'; ?>">team members page</a> on our Wiki.</p>
146
147</div>
148
149
150<?php
151    print_footer();
152?>
Note: See TracBrowser for help on using the repository browser.