[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH v2 1/6] docs: rSTify the "TrivialPatches" wiki

From: Kashyap Chamarthy
Subject: [PATCH v2 1/6] docs: rSTify the "TrivialPatches" wiki
Date: Tue, 19 Oct 2021 11:03:39 +0200

The original wiki is here[1].  I converted by copying the wiki source
into a .wiki file and convert to rST using `pandoc`:

        $ pandoc -f Mediawiki -t rst trivial-patches.wiki -o trivial-patches.rst

Update the active maintainer names to reflect current reality.

[1] https://wiki.qemu.org/Contribute/TrivialPatches

Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
I've only retained Laurent's name as per Philip's review here:
 docs/devel/trivial-patches.rst | 51 ++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 docs/devel/trivial-patches.rst

diff --git a/docs/devel/trivial-patches.rst b/docs/devel/trivial-patches.rst
new file mode 100644
index 0000000000..7df0f901f5
--- /dev/null
+++ b/docs/devel/trivial-patches.rst
@@ -0,0 +1,51 @@
+Trivial Patches
+Trivial patches that change just a few lines of code sometimes languish
+on the mailing list even though they require only a small amount of
+review. This is often the case for patches that do not fall under an
+actively maintained subsystem and therefore fall through the cracks.
+The trivial patches team take on the task of reviewing and building pull
+requests for patches that:
+- Do not fall under an actively maintained subsystem.
+- Are single patches or short series (max 2-4 patches).
+- Only touch a few lines of code.
+**You should hint that your patch is a candidate by CCing
+Since the trivial patch team rotates maintainership there is only one
+active repository at a time:
+- git://git.corpit.ru/qemu.git trivial-patches - `browse 
+- git://github.com/vivier/qemu.git trivial-patches - `browse 
+The trivial patches team rotates the duty of collecting trivial patches
+amongst its members. A team member's job is to:
+1. Identify trivial patches on the development mailing list.
+2. Review trivial patches, merge them into a git tree, and reply to state
+   that the patch is queued.
+3. Send pull requests to the development mailing list once a week.
+A single team member can be on duty as long as they like. The suggested
+time is 1 week before handing off to the next member.
+If you would like to join the trivial patches team, contact Laurent
+Vivier. The current team includes:
+- `Laurent Vivier <mailto:laurent@vivier.eu>`__

reply via email to

[Prev in Thread] Current Thread [Next in Thread]