From: Ihor Radchenko <firstname.lastname@example.org>
To: Bastien <email@example.com>
Cc: Daniel Kraus <firstname.lastname@example.org>, email@example.com
Subject: Re: [WORG] Document in more detail about what maintainers do?
Date: Thu, 29 Sep 2022 15:06:57 +0800 [thread overview]
Message-ID: <871qru7j72.fsf@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
Bastien <firstname.lastname@example.org> writes:
> Ihor Radchenko <email@example.com> writes:
>> I think the part about CC is missing in
> Indeed - can you add it?
>> Also, I find it important to take note about worg documentation for
>> built-in babel backends. I did not even know it exist for a long time.
> +1 -- and also suggest adding tests, a part that I missed.
See the attached.
> Also, I'd more comfortable if org-maintenance.org would use stable
> anchors (not #orga0c76fb).
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-maintenance.org-Add-details-about-the-maintainer.patch --]
[-- Type: text/x-patch, Size: 3632 bytes --]
From 23d5ffc8d1bb065cb98dc7f7eb1464575e41c9ad Mon Sep 17 00:00:00 2001
From: Ihor Radchenko <firstname.lastname@example.org>
Date: Thu, 29 Sep 2022 15:03:48 +0800
Subject: [PATCH] org-maintenance.org: Add details about the maintainer duties
* org-maintenance.org (What is the role of a maintainer?): Add details
about CCing from the list, maintaining tests, and updating babel
docs. Rewrite referring to the reader personally in all the places.
org-maintenance.org | 36 ++++++++++++++++++++++++------------
1 file changed, 24 insertions(+), 12 deletions(-)
diff --git a/org-maintenance.org b/org-maintenance.org
index 812cfbce..f5cc70eb 100644
@@ -70,21 +70,33 @@ * What is the role of a maintainer?
If you speak [[https://learnxinyminutes.com/docs/elisp/][Emacs lisp]] and are a regular user of an Org file, please
-consider becoming a maintainer for it: you can simply ask on the list.
+consider becoming a maintainer for it: you can simply ask on the [[https://orgmode.org/worg/org-mailing-list.html][list]].
-The maintainer does not need to be an expert of the functionality in
-the file or to actively improve the file. He or she takes care of bug
-reports and feature requests against this file by participating to the
-discussion on the list.
+You do not need to be an expert of the functionality in the file or to
+actively improve the file. Just take care of bug reports and feature
+requests against this file by participating to the discussion on the
-Org maintainers need to join [[https://savannah.gnu.org/git/?group=emacs][the Emacs group on Savannah]]. When this
-is done, they have access to the [[https://git.savannah.gnu.org/cgit/emacs/org-mode.git/][org-mode.git]] repository and can push
-changes without asking for permission first. If the change is a new
-feature, they should discuss it on the list first.
+You are not strictly required to follow the mailing list closely and
+watch for the relevant emails. When necessary, the relevant messages
+will be directly forwarded to your email.
-In case the change touches files maintained by other maintainers, they
-need to review and validate it first. If Org's maintainer disagrees
-with a change, he can ask a maintainer to revert it.
+As a maintainer, you will need to join [[https://savannah.gnu.org/git/?group=emacs][the Emacs group on Savannah]].
+When this is done, you will have access to the [[https://git.savannah.gnu.org/cgit/emacs/org-mode.git/][org-mode.git]] repository
+and will be able to push changes without asking for permission first.
+If your change is a new feature, discuss it on the [[https://orgmode.org/worg/org-mailing-list.html][list]] first.
+In case the change touches files maintained by other maintainers, ask
+them to review and validate it first. If Org's maintainer disagrees
+with a change, he can ask you to revert it.
+When possible, please accompany bug fixes and new features with tests.
+The Org test infrastructure is detailed in [[https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/testing/README][testing/README]] file in the
+If you are the maintainer of one of the babel language backends,
+please make sure that the [[https://orgmode.org/worg/org-contrib/babel/languages/index.html][language documentation in WORG]] is
See also this steps for [[https://orgmode.org/worg/org-contribute.html#devs][your first commit as a]] maintainer.
[-- Attachment #3: Type: text/plain, Size: 207 bytes --]
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-09-29 7:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 15:28 [PATCH] ob-clojure.el: Add support for babashka and nbb backend Daniel Kraus
2021-11-14 16:25 ` Max Nikulin
2021-11-14 16:30 ` Daniel Kraus
2021-11-15 14:33 ` Max Nikulin
2021-11-15 16:05 ` Daniel Kraus
2021-11-17 16:12 ` Max Nikulin
2021-11-20 10:18 ` Daniel Kraus
2021-12-22 22:34 ` Daniel Kraus
2022-01-31 7:58 ` Daniel Kraus
2022-02-02 15:58 ` Max Nikulin
2022-06-11 7:45 ` Ihor Radchenko
2022-09-25 3:10 ` Bastien
2022-09-25 13:37 ` Christopher M. Miles
2022-09-25 13:43 ` Christopher M. Miles
[not found] ` <email@example.com>
2022-09-25 13:48 ` Bastien
2022-09-26 16:02 ` Daniel Kraus
2022-09-27 2:31 ` Ihor Radchenko
2022-09-27 19:39 ` Bastien
2022-09-28 1:16 ` [WORG] Document in more detail about what maintainers do? (was: [PATCH] ob-clojure.el: Add support for babashka and nbb backend) Ihor Radchenko
2022-09-28 6:56 ` [WORG] Document in more detail about what maintainers do? Bastien
2022-09-29 7:06 ` Ihor Radchenko [this message]
2022-10-29 6:28 ` Ihor Radchenko
2022-10-29 8:06 ` Bastien Guerry
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).