From: Bastien Guerry <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>,
Daniel Fleischer <danflscr@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: [ANN] Looking for new maintainers for ox-html.el
Date: Thu, 23 Mar 2023 18:47:30 +0100 [thread overview]
Message-ID: <87edpfxsul.fsf@bzg.fr> (raw)
In-Reply-To: <87y1plea08.fsf@localhost> (Ihor Radchenko's message of "Sun, 29 Jan 2023 13:38:31 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> "Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
>
>> Ihor Radchenko <yantar92@posteo.net> writes:
>>
>>> I have been informed that our current ox-html maintainer will no longer
>>> able to perform his duties in full extent.
>
> [ This was actually not accurate - TEC, the current ox-html maintainer,
> is still around. However, he was recently focusing on developing new
> features for ox-html and other parts of Org. So, we can still use help
> from another maintainer with bug fixes. ]
Yes, it's always good to have more than one maintainer.
>>> We thus need volunteers to help maintaining Org HTML export library -
>>> lisp/ox-html.el
>>
>> I depend on ox-html for my personal website. I would be glad to help.
>
> Thanks for volunteering!
> Upon Bastien's confirmation, you can follow
> https://orgmode.org/worg/org-maintenance.html#maintainer-role and create
> an account with write access to Org git sources.
I confirm Arne's FSF records are in order.
Thanks for your help!
--
Bastien Guerry
next prev parent reply other threads:[~2023-03-23 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 13:32 [ANN] Looking for new maintainers for ox-html.el Ihor Radchenko
2023-01-27 14:41 ` Dr. Arne Babenhauserheide
2023-01-29 13:38 ` Ihor Radchenko
2023-03-23 17:47 ` Bastien Guerry [this message]
2023-08-05 9:20 ` 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=87edpfxsul.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=arne_bab@web.de \
--cc=danflscr@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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 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).