Contributing

OProfile needs your help ! In your role as a user, we want (good) bug reports and suggestions. As a developer, patches.

If you have a patch to contribute, please make sure to first read and follow doc/CodingStyle and HACKING. The script check_style.py in the oprofile-tests git 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 git tree. Any patches should be in diff -prauN format, and able to be applied with patch -p1 <patch.diff in the top-level directory. If you're using git, you can create such a patch with a command like ' git diff >patch.diff'.

When you submit a patch, we ask that you include a "Signed-off-by" line; for example:

        Signed-off-by: Random J Developer <random@developer.example.org>

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 <kernel-source>/Documentation/SubmittingPatches, item 11, "Sign your work".

The internal workings are a little under-documented at present: we intend to fix this. You can find some doxygen-generated source documentation here; there's also an 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.