Pure Data External Repository

+ + +

Bug reporting

+ +

+Bug reporting is done via the tracker system on sourceforge. Click on +Submit Bug to submit a bug against one of the subprojects. +

+It is important that you assign the bug to the correct subproject. This +is done by selecting the appropriate Category from the category tab. Before +submitting a bug report, you might check if the bug you encountered hasn't been +reported already by looking at the open bug reports page. +

+ +

Patches

+ +

+There is another tracker which is used to submit patches against Pd and the +subprojects. +This tracker is a collection of up to date patches (patches that apply +cleanly against the latest version of Pd in CVS). Patches that don't apply +cleanly will be removed from the list (after notification, so the author has +time to fix the problem). +

+
+

+All patches need to have a detailed description. This can later be used +to decide if the patch can go into the main Pd distribution or not, and +should also minimize the work that has to be done in order to adapt new +ideas. Click to Submit a patch. +

+
+

+If you submit a patch, take care that you only send the parts that have to +be changed. Formatting changes and changes in whitespace will only make the +patch less readable. Send the patch in unified diff format.
+
+e.g. from a CVS directory: +
+
+cvs diff -uBw > cool_feature.patch +
+ +

Feature Requests

+ +

+There is also a tracker for feature requests. A feature request can be sent if +you are missing a functionality, but you don't know how to code it. This could +be and additional external, or functionality of the Pd core. +

+Click Add Feature Request to add a new feature request. + +
+
+ + + +
+ + +