Patchwork is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project.
Patches that have been sent to a mailing list are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too.
The project's maintainer can then scan through the list of patches, marking each with a certain state, such as Accepted, Rejected or Under Review. Old patches can be sent to the archive or deleted.
The latest version of Patchwork is available with git. To download:
[jk@pingu ~]$ git clone git://ozlabs.org/home/jk/git/patchwork
Patchwork is distributed under the GNU General Public License.
patchwork should supplement mailing lists, not replace them
Patchwork isn't intended to replace a community mailing list; that's why you can't comment on a patch in patchwork. If this were the case, then there would be two forums of discussion on patches, which fragments the patch review process. Developers who don't use patchwork would get left out of the discussion.
However, a future development item for patchwork is to facilitate on-list commenting, by providing a "send a reply to the list" feature for logged-in users.
don't pollute the project's changelogs with patchwork poop
A project's changelogs are valuable - we don't want to add patchwork-specific metadata.
patchwork users shouldn't require a specific version control system
Not everyone uses git for kernel development, and not everyone uses git for patchwork-tracked projects.
It's still possible to hook other programs into patchwork, using the
pwclient command-line client for patchwork, or directly to
the XML RPC interface.
There is now a patchwork mailing list. Sign up for updates to patchwork.
If you'd like to check it out, Patchwork is being used on the Linux-PowerPC Development list. Have a browse here