From: Ihor Radchenko <yantar92@posteo.net>
To: emacs-orgmode@gnu.org, Bastien <bzg@gnu.org>,
Timothy <orgmode@tec.tecosaur.net>
Subject: Maintenance status of individual Org libraries
Date: Mon, 30 Jan 2023 13:41:18 +0000 [thread overview]
Message-ID: <87v8ko3zsx.fsf@localhost> (raw)
Dear all,
I have gone through the maintainers of individual Org files and,
especially after Nicolas went missing from the list, the situation is
rather dire.
The following libraries have no maintainer or author active on the list:
ob-comint, ob-core, ob-css, ob-ditaa, ob.el, ob-emacs-lisp,
ob-eval, ob-exp, ob-forth, ob-fortran, ob-js, ob-latex, ob-lilypond,
ob-lob, ob-lua, ob-matlab, ob-ocaml, ob-octave, ob-org, ob-per,
ob-plantuml, ob-ref, ob-R, ob-ruby, ob-sass, ob-sed, ob-table,
ob-tangle, oc-basic, oc-biblatex, oc-bibtex, oc.el, oc-natbib, ol-bbdb,
ol-docview, ol-doi, ol.el, ol-eshell, ol-info, ol-irc, ol-mhe, ol-rmail,
org-agenda, org-archive, org-capture, org-clock, org-colview, org-compat
(maintenance would be useful, especially wrt compat.el), org-ctags,
org-datetree, org-duration, org-element (I can), org-entities,
org-faces, org-feed, org-footnote, org-goto, org-id, org-indent,
org-keys, org-lint, org-macro, org-macs, org-mobile, org-mouse, org-num,
org-refile, org-table, org-tempo, org-timer, ox-ascii, ox-beamer, ox.el,
ox-icalendar, ox-man, ox-md, ox-odt, ox-org, ox-publish, ox-texinfo
83/127 (~65%) of the libraries do not have someone familiar with their
code.
Should we try to make a call for maintenance at least for some of these
libraries?
--
Ihor Radchenko // yantar92,
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 reply other threads:[~2023-01-30 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 13:41 Ihor Radchenko [this message]
2023-08-05 9:46 ` Maintenance status of individual Org libraries Ihor Radchenko
2023-08-06 5:53 ` Bastien Guerry
2023-08-06 8:42 ` Ihor Radchenko
2023-08-20 20:56 ` Matt
2023-08-21 8:03 ` Ihor Radchenko
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8ko3zsx.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@tec.tecosaur.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).