helping.fml.svn-base

portal越来越流行了

<?xml version="1.0"?>
<!--
Copyright 1999-2006 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!--
// ======================================================================== 78
-->
<faqs title="Getting Involved">
    <part id="general">

        <faq id="involved">
            <question>Getting Involved</question>
            <answer>

                <p>
                    Every volunteer project obtains its strength
                    from the people involved in it.
                    We invite you to participate as much or as little as you
                    choose.
                    The roles and responsibilities that people can assume in
                    the project
                    are based on merit.
                    Everybody's input matters!
                </p>

                <p>
                    Here is one developer's advice how to get involved.
                    It specifically talks about Tomcat,
                    but the general idea can applied to any of the Apache
                    Projects.
                </p>

                <ul>
                    <li>
                        <a href="http://jakarta.apache.org/site/contributing.html">
                            Contributing</a>
                        -- Craig R. McClanahan
                    </li>
                </ul>

                <p>
                    Here is another comment that was sent to the Jakarta
                    Turbine Mailing
                    List about the open source process and the contrast
                    between how an
                    open source product and a proprietary product improve
                    through the user
                    community.
                </p>

                <ul>
                    <li>
                        <a href="http://jakarta.apache.org/site/understandingopensource.html">
                            Understanding Opensource</a>
                        -- Cameron Riley
                    </li>
                </ul>

                <p>
                    While written for ASF developers,
                    the Rules for Revolutionaries provides insight into how
                    the
                    collaborative process works,
                    and how our process differs from working on a hierarchical
                    team.
                </p>

                <ul>
                    <li>
                        <a href="http://incubator.apache.org/learn/rules-for-revolutionaries.html">
                            Rules for Revolutionaries</a>
                        -- James Duncan Davidson
                    </li>
                </ul>

                <p>
                    Just using the products is a very important role.
                    We need people who will report issues, contribute patches,
                    suggest features, and so forth.
                    Your feedback helps the technology to evolve.
                </p>

            </answer>
        </faq>

        <faq id="mail">
            <question>Joining the Mailing Lists</question>
            <answer>

                <p>
                    There are a variety of ways to participate.
                    Regardless of how you choose to participate,
                    we suggest you join our
                    <a href="mail-lists.html">mailing lists</a>.
                </p>


                <p>
                    Please do be sure to
                    <a href="http://expita.com/nomime.html">turn off
                        HTML</a>
                    in your email client before posting.
                </p>
            </answer>
        </faq>

        <faq id="patches">
            <question>How do I create a patch?</question>
            <answer>
                <p>
                    A patch is a machine-readable script that can
                    automatically
                    recreate a change to a text file, including source code
                    and
                    documentation.
                    The patch format is also human-readable.
                    Developers often pass patches around to discuss a change
                    before
                    applying it to the main repository.
                </p>

                <p>
                    The best way to affect a change to the source code or
                    documentation
                    is to provide a patch.
                    Pluto committers can then review your patch and
                    decide
                    whether to apply it to the main repository.
                </p>

                <p>
                    To create a patch, you first have to
                    <a href="source-repository.html">
                        checkout</a>
                    a copy of the source code or documentation from the main
                    repository.
                    You can then change your copy, and create the patch using
                    a simple
                    <a href="http://subversion.org/">Subversion</a>
                    command, like this:
                </p>

                <p>
                    <code>svn diff Main.java &gt;&gt; patchfile.txt</code>
                </p>

                <p>
                    Then, create a
                    <a href="#issues">JIRA
                        issue</a>
                    about the change, and attach the patch file.
                </p>

                <p>
                    Some Apache projects ask that you to submit your patch to
                    the mailing
                    list.
                    We would prefer that you create a
                    JIRA issue and then attach the patch to the issue.
                    To do this, you must first create the issue,
                    and then modify the report to add your patch.
                    We realize this is a bit clumsy, but it keeps us from
                    losing things,
                    and helps to ensure that your patch will be attended.
                </p>

                <p>
                    The
                    <a href="http://www.netbeans.org/community/contribute/patches.html">
                        NetBeans community</a>
                    also has a helpful section on the
                    subject of creating patches.
                </p>

            </answer>
        </faq>

        <faq id="issues">
            <question>How can I report defects or suggest features?</question>
            <answer>
                <p>
                    Tracking of defect reports and enhancement suggestions for
                    Apache Pluto
                    products is handled
                    through the
                    <a href="http://issues.apache.org/jira/">Apache Pluto
                        JIRA instance.</a>
                    Please select the appropriate Pluto product from
                    the list,
                    and then select the component to which you feel this report
                    relates.
                    You will automatically be notified by email as the status
                    of your defect or
                    enhancement report changes.
                    Please be sure to read
                    <a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">
                        How to
                        Report Bugs Effectively</a>
                    before posting a report.
                </p>

                <p>
                    If you can't write a
                    <a href="#patches">patch</a>
                    to address your issue,
                    a unit test that demonstrates the problem is also welcome.
                    (And, of course, unit tests that prove your patch works
                    are equally welcome.)
                </p>

                <p>
                    If the defect or feature is already being tracked,
                    you can vote for the issue and call more attention to it.
                    Each user can cast up to six votes at a time.
                </p>

                <p>
                    If there is a patch attached to the issue, you can also
                    try applying
                    to your local copy of Pluto, and report whether it worked
                    for you.