Most of our worflows have moved from mailing lists and patches to merge
requests on gitlab. Until now amending the TU Bylaws formally requires
sending patches via mail which this amendment intends to replace with
merge requests on the gitlab repository.
Signed-off-by: Christian Heusel
---
tu-bylaws.adoc | 19 ++++---------------
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git a/tu-bylaws.adoc b/tu-bylaws.adoc
index 376d909..70a8a27 100644
--- a/tu-bylaws.adoc
+++ b/tu-bylaws.adoc
@@ -170,21 +170,10 @@ These bylaws may be amended at any time.
A TU must motion for an amendment by sending an announcement
to https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general].
-The message must either contain, or have attached, a Git-formatted patch
-against this document which accomplishes the suggested change. The patch should
-be based on the master branch of the official
-https://gitlab.archlinux.org/archlinux/tu-bylaws.git/[tu-bylaws repository] and should
-be sent "inline" (i.e. using `git send-email`) so that other TUs can easily
-comment on specific parts. The strings `[PATCH]` and `[tu-bylaws]` should be
-included in the subject. `git send-email --annotate` can be used to edit a
-patch before sending it to the mailing list.
-
-Sending multiple patches is generally discouraged and should only be done if no
-more than one of the patches are subject for debate (the remaining patches
-might be formatting changes or minor wording changes). If multiple patches are
-sent as part of one proposal, a cover letter describing the changes must be
-included. The `--cover-letter` option of `git send-email` can be used to
-achieve this.
+The message must contain a link to a merge reqest in the official
+https://gitlab.archlinux.org/archlinux/tu-bylaws[tu-bylaws repository] and the
+merge request description should contain a meaningful description and
+motivation for the change.
SVP is commenced at the time of the motion, with a discussion period of 5 days,
a quorum of 75%, and a voting period of 7 days.
--
2.42.0