1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
Patchwork
=========
.. toctree::
:maxdepth: 2
:caption: Contents:
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.
Download
--------
The latest version of Patchwork is available with git. To download:
.. code-block:: shell
$ git clone git://github.com/getpatchwork/patchwork
Patchwork is distributed under the `GNU General Public License (v2)`__.
__ http://www.gnu.org/licenses/gpl-2.0.html
Design
------
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.
Getting Started
---------------
You should check out the `deployment/installation` and
`development/installation` guides for information on how to configure
Patchwork for production and development environments, respectively.
Support
-------
All questions and contributions should be sent to the
`Patchwork mailing list`__
__ https://ozlabs.org/mailman/listinfo/patchwork
|