From d04ee197c95d184ea462d9aa6b13a1acfd93e527 Mon Sep 17 00:00:00 2001
From: m <3440586+maiska@users.noreply.github.com>
Date: Sat, 1 Jun 2024 14:32:45 +0200
Subject: [PATCH] add newlines for better rst conversion

---
 introduction/issue-tracking.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/introduction/issue-tracking.md b/introduction/issue-tracking.md
index 3296210e..13ebb449 100644
--- a/introduction/issue-tracking.md
+++ b/introduction/issue-tracking.md
@@ -95,10 +95,12 @@ Meta-issues must abide by the following rules:
 
 - Only members of the core team may create meta-issues (or convert existing issues into meta-issues).
 
+
   Rationale: The purpose of meta-issues is to track the development of certain features that fit into the overall goals of the Qubes OS Project, which requires making informed project-management decisions with the approval of the project lead.
 
 - Meta-issues must be [locked](https://docs.github.com/en/communities/moderating-comments-and-conversations/locking-conversations).
 
+
   Rationale: One of the historical problems we've experienced with meta-issues (and one of the reasons they were discouraged for a long time) is that each meta-issue tends to turn into a discussion thread that becomes hopelessly long to the point where the person who is supposed to work on it has no idea what is supposed to be done or where to start, and it eventually just gets closed. Locking is intended to prevent that from happening again.
 
 - Meta-issues must have informative descriptions, not just lists of issues. In particular, each meta-issue should explain its goal, what is in scope, and what the relevant categories and priorities are.