~bzg/worg

6fbe51dee6bf276584c24fa1e7ec673526c9326e — Ihor Radchenko 1 year, 9 months ago 6a5bccb
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.
1 files changed, 24 insertions(+), 12 deletions(-)

M org-maintenance.org
M org-maintenance.org => org-maintenance.org +24 -12
@@ 71,21 71,33 @@ a table with the accounts of the current maintainers:
:END:

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
[[https://orgmode.org/worg/org-mailing-list.html][list]].

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
Org repository.

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
up-to-date.

See also this steps for [[https://orgmode.org/worg/org-contribute.html#devs][your first commit as a]] maintainer.