From: Kyle Meyer <kyle@kyleam.com>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: List of ob-* maintainers
Date: Mon, 19 Apr 2021 23:07:31 -0400 [thread overview]
Message-ID: <87eef5y7po.fsf@kyleam.com> (raw)
In-Reply-To: <87pmyr4b7x.fsf@tsdye.online>
Thomas S. Dye writes:
> Aloha all,
>
> Is there a list of current ob-* maintainers?
Bastien updated the "Maintainer" field of the source files:
$ git grep -i maintainer lisp/ob-* | cut -d'<' -f1
lisp/ob-C.el:;; Maintainer: Thierry Banel
lisp/ob-J.el:;; Maintainer: Joseph Novakovich
lisp/ob-R.el:;; Maintainer: Jeremie Juste
lisp/ob-abc.el:;; Maintainer: William Waites
lisp/ob-clojure.el:;; Maintainer: Bastien Guerry
lisp/ob-dot.el:;; Maintainer: Justin Abrahms
lisp/ob-eshell.el:;; Maintainer: stardiviner
lisp/ob-groovy.el:;; Maintainer: Palak Mathur
lisp/ob-haskell.el:;; Maintainer: Lawrence Bottorff
lisp/ob-java.el:;; Maintainer: Ian Martins
lisp/ob-mscgen.el:;; Maintainer: Justin Abrahms
lisp/ob-perl.el:;; Maintainer: Corwin Brust
lisp/ob-python.el:;; Maintainer: Jack Kamm
lisp/ob-screen.el:;; Maintainer: Ken Mankoff
$ git describe
release_9.4.5-317-g3d5284326
The oldest addition is from September 2020, so that should be a fairly
current list.
> Perhaps it would be useful to add and populate a Maintainer column to
> the language table on Worg (org-contrib/babel/languages/index.html)?
Hmm, I suppose it's nice to have just one spot to avoid information
becoming out of sync, but that's a minor issue, so no objections from me
if you or others think it'd be helpful to have the information on Worg.
next prev parent reply other threads:[~2021-04-20 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 19:57 List of ob-* maintainers Thomas S. Dye
2021-04-20 3:07 ` Kyle Meyer [this message]
2021-04-20 4:15 ` Thomas S. Dye
2021-04-21 2:47 ` Kyle Meyer
2021-04-22 2:06 ` Thomas S. Dye
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=87eef5y7po.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.online \
/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).