<?php require("../start_page.php"); start_page("contribute/", "Contribute to OProfile"); ?>
OProfile needs your help ! In your role as a user, we want (good)
<?php rlink("bugs/", "bug reports"); ?>
<?php rlink("mail/", "suggestions"); ?>
. As a developer,
<?php rlink("download/", "patches"); ?>.
If you have a patch to contribute, please make sure to first read and
follow <tt>doc/CodingStyle</tt> and <tt>HACKING</tt>. The script
<tt>check_style.py</tt> in the <tt>oprofile-tests</tt> CVS module can
find some common problems for you, but it has issues with false
negatives as well as false positives. Changes must be against
the most recent CVS tree. Any patches should be in
<tt>diff -prauN</tt> format, and able to be applied with <tt>patch
-p1 <patch.diff</tt> in the top-level directory. If you're using CVS,
you can create such a patch with a command like <tt>cvs -d `cat
oprofile/CVS/Root` diff oprofile/ >patch.diff</tt>.
<p>When you submit a patch, we ask that you include a "Signed-off-by"
line; for example:<br>
<pre> Signed-off-by: Random J Developer <email@example.com></pre><br>
Including this line with your patch implies that you have read and comply with
the "Developer's Certificate of Origin 1.1" (DCO). This is the same process
the kernel community uses to try to ensure the originality of patches. The
DCO can be found in <a href="http://lwn.net/Articles/139918/">
<kernel-source>/Documentation/SubmittingPatches, item 11,
"Sign your work"</a>.
The internal workings are a little under-documented at present: we intend to fix
this. You can find some doxygen-generated source documentation
<?php rlink("srcdoc/", "here"); ?>; there's also an <?php
rlink("doc/internals/index.html", "internals manual"); ?>.
If you have any questions, please ask them on the mailing list. A reasonably
complete TODO list can be found in the source tree.
<?php require("$top/end_page.php"); end_page("contribute/index.php"); ?>