From: Ihor Radchenko <yantar92@posteo.net>
To: Matt <matt@excalamus.com>
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: Mon, 21 Aug 2023 08:03:24 +0000 [thread overview]
Message-ID: <87zg2k4yb7.fsf@localhost> (raw)
In-Reply-To: <18a14bbd85f.dbd2e492103591.5433509086311815914@excalamus.com>
Matt <matt@excalamus.com> writes:
> ---- 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.
Thanks!
> 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?
You may help by confirming bug reports, discussing new features, and
providing idea about how to fix things.
For example, check out
- Discussion about merging header arguments: https://list.orgmode.org/8735451u20.fsf@gmail.com/
- Discussion about :results header arg: https://list.orgmode.org/orgmode/87sf9x8n38.fsf@localhost/
- Some ob-shell Windows-only bug: https://list.orgmode.org/orgmode/87y1rbeohp.fsf@localhost/
- Some weird edge cases related to comint and command that read key:
https://list.orgmode.org/orgmode/878re5g0ir.fsf@localhost/
You also do not need FSF assignment to contribute to WORG documentation.
Your example babel template may go there.
> I'd also be happy to mentor new maintainers.
It would also be nice to help people who submit patches to
ob-core/ob-comint, by suggesting improvements and answering their
questions. These people are the perspective maintainers - we should
better help them early :)
--
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>
prev parent reply other threads:[~2023-08-21 8:03 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
2023-08-21 8:03 ` Ihor Radchenko [this message]
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=87zg2k4yb7.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=matt@excalamus.com \
--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).