-
-
Notifications
You must be signed in to change notification settings - Fork 17
/
contact.php
166 lines (131 loc) · 10.6 KB
/
contact.php
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
<?php
/* -*- 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: */
/* Copyright (c) 2007, The MacPorts Project. */
include_once("includes/common.inc");
print_header('The MacPorts Project -- Contact Us', 'utf-8');
?>
<div id="content">
<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 and/or feedback you're looking for:</p>
<ul>
<li><a href="#Lists">Public Mailing Lists</a></li>
<li><a href="#PortMgr">Administrative Contact</a></li>
<li><a href="#Tracker">Bug Reports & Contributions</a></li>
<li><a href="#IRC">IRC</a></li>
<li><a href="#Individuals">Individuals</a></li>
</ul>
<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), hardware architecture (e.g. Intel
or PowerPC), and the version of Xcode installed -- 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="<?php print $mailman_url . 'macports-users/' ?>">MacPorts Users</a>
(<a href="<?php print $pipermail_url . 'macports-users/' ?>">archives</a>):
<p>General discussion of MacPorts installation and usage. A moderate volume list.</p>
</li>
<li><a href="<?php print $mailman_url . 'macports-dev/' ?>">MacPorts Developers</a>
(<a href="<?php print $pipermail_url . '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="<?php print $mailman_url . 'macports-changes/' ?>">MacPorts Changes</a>
(<a href="<?php print $pipermail_url . 'macports-changes/' ?>">archives</a>):
<p>Read-only, low to moderate volume list of changes to our <a href="<?php print $github_url; ?>">git repository on GitHub</a>
for both “base” code and Portfiles, among others.</p>
</li>
<li><a href="<?php print $mailman_url . 'macports-builds/' ?>">MacPorts Builds</a>
(<a href="<?php print $pipermail_url . 'macports-builds/' ?>">archives</a>):
<p>Read-only, moderate volume list with build notifications from our <a href="<?php print $build_url; ?>">Buildbot
</a>.</p>
</li>
<li><a href="<?php print $mailman_url . 'macports-tickets/' ?>">MacPorts Tickets</a>
(<a href="<?php print $pipermail_url . 'macports-tickets/' ?>">archives</a>):
<p>Read-only, moderate volume list of ticket activity on our <a href="<?php print $trac_url; ?>">Trac bug tracker
</a>.</p>
</li>
<li><a href="<?php print $mailman_url . 'macports-announce/' ?>">MacPorts Announce</a>
(<a href="<?php print $pipermail_url . 'macports-announce/' ?>">archives</a>):
<p>Read-only, low volume list for project related major announcements.</p>
</li>
</ul>
<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.
Members are expected to abide by the very simple <a href="http://tools.ietf.org/html/rfc1855">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="https://gist.github.com/">GitHub Gist</a> and passing along the paste URL rather than full error messages).</p>
<h3 class="subhdr" id="PortMgr">Administrative Contact</h3>
<p>The private and read-only “<?php print obfuscate_email("[email protected]"); ?>” mailing
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
$guide_url . '#project.portmgr'; ?>">management team</a> (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>
<p>This is also where you should turn to if you are a developer and/or a contributor interested in joning The MacPorts
Project with full write access to our git 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="Tracker">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 git 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="<?php print $trac_url . 'auth/register/'; ?>">register</a> with GitHub for an account.</p>
<p>If you think you've found a bug either in one of our <a href="<?php print $portdb_url; ?>">available ports</a> or in MacPorts itself, or
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
. 'newticket'; ?>">open a ticket</a> to help us look into the problem and/or submission. 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 duties. <a href="<?php print $trac_url . 'search'; ?>">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 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://irc.libera.chat/#MacPorts"><code>
#MacPorts</code></a> channel on <a href="https://libera.chat/">Libera Chat</a> is where some of us usually hang out,
MacPorts developers and community members alike. Everyone is free and welcomed to join us, whether 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 traction at any 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. The IRC channel also receives a message for every commit made in the MacPorts project from a user
called <code>mplog</code>. Feel free to ignore those messages.</p>
<p>If you would like a web-based interface to the IRC channel, one option is
<a href="https://kiwiirc.com/nextclient/irc.libera.chat/">KiwiIRC</a>. Note that it is operated by a third party.</p>
<p>An alternative real-time discussion platform is Matrix. MacPorts' channel on the Matrix network is <a
href="https://matrix.to/#/#macports:matrix.org"><code>#macports:matrix.org</code></a>. It preserves chatting
history, so users without an IRC bouncer might prefer this. Matrix is a globally federated protocol, an account on
a Matrix homeserver is required to join. See the Matrix Foundation's <a href="https://matrix.org/try-matrix/">Try
Matrix</a> page for an introduction on how to get one.</p>
<p>We formerly had a <code>#MacPorts</code> channel on the Freenode IRC network. While the channel may still exist there, it is no
longer an official channel for the MacPorts project.</p>
<h3 class="subhdr" id="Individuals">Individuals</h3>
<p>To find out who the people behind MacPorts are and what they are up to, visit the <a href="<?php print $trac_url .
'wiki/MacPortsDevelopers'; ?>">team members page</a> on our Wiki.</p>
</div>
<?php
print_footer();
?>