source: trunk/www/help.php @ 28303

Last change on this file since 28303 was 28303, checked in by jmpp@…, 13 years ago

Major but minor commit to the www svn space: reorder the sources a bit to have a cleaner
layout while bringing the content up to speed with current practices and reality, otherwise
sticking to the same website we had back in OpenDarwin days.

The one big thing about this commit, though, is that the old ports.php page is again operational,
as shown in my local server: http://apollo.homeunix.net/macports/ports.php. Woot!

Further discussion of what to do with these sources is needed, however, so I'm not gonna push to
host them anywhere for the time being until we have a clearer map of how we should move forward
wrt our web presence.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Id
File size: 3.7 KB
Line 
1  <?php
2    $DOCUMENT_ROOT = $_SERVER['DOCUMENT_ROOT'];
3    include_once("$DOCUMENT_ROOT/macports/includes/common.inc");
4    print_header('Get Help', 'utf-8');
5  ?>
6
7        <div id="content">
8                <h2 class="hdr">Get Help</h2>
9
10                <p>If you get stuck while using MacPorts and have a problem you
11                can't figure out, we have a lot of resources to help you.</p>
12         
13                <h5 class="subhdr">Documentation</h5>
14
15                <p>The <a href="http://geeklair.net/new_macports_guide/">MacPorts Guide</a> has a section dedicated to MacPorts
16                installation issues, <a href="http://geeklair.net/new_macports_guide/#installing">Chapter 2. Installing MacPorts</a>
17                and another one for general usage, <a href="http://geeklair.net/new_macports_guide/#using">Chapter 3: Using MacPorts</a>.</p>
18
19                <p>The <a href="http://trac.macports.org/projects/macports/wiki/FAQ">MacPorts FAQ</a>
20                is now an ongoing, user driven effort part of our <a href="http://trac.macports.org/projects/macports/wiki">Wiki</a>,
21                where anyone with a <a href="http://www.macports.org/wp-register.php">Trac account</a>
22                and MacPorts knowledge can contribute with information to help others.</p>
23
24                <p>All of our documentation is a work in progress, so if you spot an error or have a quesiton about some part of the document,
25                let us know!  This will help us </p>
26       
27                <h5 class="subhdr">Mailing Lists</h5>
28
29                <p>The <a href="http://lists.macosforge.org/mailman/listinfo/macports-users">General MacPorts mailing list</a> is open to all
30                for supscription. It is the best place for existing and new users alike to ask questions about MacPorts and MacPorts
31                installed software. Please note that due to spam problems the mailing list will reject posts from non-subscribers.</p>
32
33                <p>It is recommended to check the <a href="http://lists.macosforge.org/pipermail/macports-users/">list archive</a> before posting
34                a question, as some issues are aired fairly regularly and dealt with many times in a row. We try to be as helpful as possible,
35                but if it's a common question our answers may be fairly short.</p>
36
37                <p>When posting a question to the mailing list, please included any information you think might be relevent to the problem,
38                such as  operating system and version you're using, Mac OS X 10.4.10 for example, whether you have any other third party
39                software installed, in <kbd>/usr/local</kbd> for instance, and any error messages that MacPorts might give you (use the
40                <kbd>-v</kbd> or <kbd>-d port(1)</kbd>'s flags to turn on verbose or debugging information, it's a lot easier for us to
41                help you once these are used).</p>
42
43                <p>If you are a developer and need help with any part of the MacPorts internals, the <a href="http://lists.macosforge.org/mailman/listinfo/macports-dev">
44                development list</a> is where you should direct your posts to, as this is where all discussion about MacPorts itself takes place.
45                <a href="http://lists.macosforge.org/pipermail/macports-dev/">Archives</a> for this mailing list are also available.</p>
46
47                <h5 class="subhdr">IRC</h5>
48
49                <p>For more real-time discussion, the #MacPorts channel on the <a href="http://freenode.net/">Freenode IRC network</a> is generally
50                where we hang out. Though it is generally helpful, please keep in mind that no one is obligated to help or even answer your question
51                if you join IRC. Do not take it personally, simply ask your question on the <a href="http://lists.macosforge.org/mailman/listinfo/macports-users">
52                users</a> or <a href="http://lists.macosforge.org/mailman/listinfo/macports-dev">development</a> mailing lists instead.</p>
53
54        </div>
55</div>
56
57<?php
58  print_footer();
59?>
Note: See TracBrowser for help on using the repository browser.