Patchwork is a patch tracking system for community-based projects. It is intended to make the patch management process easier for both the project's contributors and maintainers, leaving time for the more important (and more interesting) stuff.
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.
Currently, Patchwork is being used for a number of open-source projects, mostly subsystems of the Linux kernel. Although Patchwork has been developed with the kernel workflow in mind, the aim is to be flexible enough to suit the majority of community projects.
Patchwork requires reasonably recent versions of:
- Python 3
- Django REST Framework
- Django Filters
The precise versions supported are listed in the release notes.
Docker is the recommended installation method for a Patchwork development environment. To install Patchwork:
Clone the Patchwork repo:
$ git clone https://github.com/getpatchwork/patchwork.git
.envfile in the root directory of the project and store your
$ cd patchwork && printf "UID=$(id -u)\nGID=$(id -g)\n" > .env
Build the images. This will download a number of packages from the internet, and compile several versions of Python:
$ docker-compose build
Run docker-compose up:
$ docker-compose up
The Patchwork instance will now be deployed at http://localhost:8000/.
For more information, including helpful command line options and alternative installation methods, refer to the documentation.
Talks and Presentations
- Mailing List, Meet CI (slides) - FOSDEM 2017
- Patches carved into stone tablets (slides) - Kernel Recipes Conference 2016
- A New Patchwork (slides) - FOSDEM 2016
- Patchwork: reducing your patch workload (slides) - Linux Plumbers Conference 2011
For further information, refer to the documentation.
For bug reports, patch submissions or other questions, use the mailing list.