index.html

m4_include(/mcs/m4/worksp.lib.m4)
_NIMBUS_HEADER(2.6 Developer Resources)
_NIMBUS_HEADER2(n,n,y,n,n,n,n)

_NIMBUS_LEFT2_COLUMN

_NIMBUS_LEFT2_DEV1_SIDEBAR(y,n,n,n,n,n,n,n,n)

_NIMBUS_LEFT2_COLUMN_END
_NIMBUS_CENTER2_COLUMN
_NIMBUS_IS_DEPRECATED


<h2>Developer Resources (2.6)</h2>
<p>
    To learn how to make Nimbus components behave differently (beyond
    configuration), see the <a href="../plugins/index.html">Extensibility
    Guide</a>.
</p>

<p>
    To learn about source control, including where to view the source online,
    see <a href="sccs.html">Source control</a>.
</p>

<p>
    This section also contains information on making
    <a href="docs.html">documentation changes</a> and
    <a href="releases.html">new releases</a>.
</p>

<p>
    You <b>can contribute</b> without a vote to bring you in as a full committer and many
    do.  All that is necessary is that you sign a
    <a href="http://dev.globus.org/wiki/Licensing_and_Contribution_Guidance#Legal_Requirements_for_Contributions">contributor's license</a>
    which allows us to freely distribute your contributions.  Your git
    author information is preserved in the repository, you just don't
    have free reign in this situation.
</p>

<p>
    You will get access to the Nimbus contributor chatroom and any amount
    of praise and encouragement you can handle :-)
</p>

<p>
    The best place to "dive in" to working with Nimbus (whether it be to
    contribute something or to customize something for your own purpose) is
    by learning to run the <a href="testing.html">test suites</a>.
    Run some of the unit suites.  Change
    some behavior and run them again and see what happens.  Try it with the
    debugger and step through how some of the code flows.  Make a quick
    contribution by writing a new test!
</p>

_NIMBUS_CENTER2_COLUMN_END
_NIMBUS_FOOTER1
_NIMBUS_FOOTER2
_NIMBUS_FOOTER3