all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matt <matt@excalamus.com>
To: "Ihor Radchenko" <yantar92@posteo.net>
Cc: "emacs-orgmode" <emacs-orgmode@gnu.org>, "Bastien" <bzg@gnu.org>,
	"Timothy" <orgmode@tec.tecosaur.net>
Subject: Re: Maintenance status of individual Org libraries
Date: Sun, 20 Aug 2023 22:56:09 +0200	[thread overview]
Message-ID: <18a14bbd85f.dbd2e492103591.5433509086311815914@excalamus.com> (raw)
In-Reply-To: <87v8ko3zsx.fsf@localhost>

 ---- On Mon, 30 Jan 2023 14:41:18 +0100  Ihor Radchenko  wrote --- 

 > The following libraries have no maintainer or author active on the list:
 
 > ob-comint, ob-core, ...

I'm interested (and technically still maintainer of ob-shell). ob-comint and ob-core are both used by ob-shell, so I've looked at good bits of both.  I'd be willing to work on those.

Unfortunately, my new job has yet to sign the FSF disclaimer, so I'm unable to contribute at the moment (I'm doing what I can to facilitate communication between parties).  Feel free to reach out off-list with advice for how I might help that process.

Until the disclaimer language gets resolved, I may be able to help in other ways.  I have notes explaining the ob- API (https://lists.gnu.org/archive/html/emacs-orgmode/2023-02/msg00531.html).  Maybe if that were completed, it would make being a maintainer more approachable for people?  I'd also be happy to mentor new maintainers.  What other ways might I help?



  parent reply	other threads:[~2023-08-20 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 13:41 Maintenance status of individual Org libraries Ihor Radchenko
2023-08-05  9:46 ` Ihor Radchenko
2023-08-06  5:53 ` Bastien Guerry
2023-08-06  8:42   ` Ihor Radchenko
2023-08-20 20:56 ` Matt [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18a14bbd85f.dbd2e492103591.5433509086311815914@excalamus.com \
    --to=matt@excalamus.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@tec.tecosaur.net \
    --cc=yantar92@posteo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.