From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Re: Volunteering to maintain ob-asymptote.el within Org
Date: Sat, 03 Sep 2022 16:25:49 +0300 [thread overview]
Message-ID: <87k06kwpwi.fsf@iki.fi> (raw)
In-Reply-To: 87y1v3leek.fsf@gnu.org
Greetings Bastien!
Bastien <bzg@gnu.org> writes:
>> I hereby volunteer to maintain ob-asymptote.el. This file has been
>> moved to org-contrib, but I would like it to be brought back into Org
>> itself.
>
> I added Luc (cc'ed) as the maintainer of ob-asymptote.el a while ago:
>
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=27621a5b
>
> Perhaps you can discuss with him to decide whether you both want to
> maintain this file or just one of you?
I do not wish to "steal" ob-asymptote.el from anyone; if Luc is happy
being the maintainer, this is fine by me.
In fact, perhaps it would be best at this point if Luc would maintain
ob-asymptote.el and I would create a good set of examples in Worg:
https://www.orgmode.org/worg/org-contrib/babel/languages/ob-doc-asymptote.html
If ob-asymptote.el is moved out of org-contrib, where whould this page
reside?
> As maintainer(s) or ob-asymptote.el, the first step should probably be
> to package it for GNU ELPA: both you and Luc have signed the FSF
> copyright assignment, so there is no blocker for joining GNU ELPA.
> Then we can move it out of org-contrib, which just serves as a
> transitory repository.
This is an excellent idea. I would certainly want ob-asymptote.el out of
org-contrib, since the advertisement for org-contrib almost guarantees
that the files are not maintained. :-)
> For now, I'd rather be conservative with what is added to Org's core:
> GNU ELPA is reachable enough for "niche" features. If/when Asymptote
> gets more support within Emacs core, we can move ob-asymptote.el in
> Org's core back again.
>
> Would that be okay for you (both)?
This is fine by me. I can start marketing to increase level of interest.
All the best,
Jarmo
next prev parent reply other threads:[~2022-09-03 13:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 5:16 Volunteering to maintain ob-asymptote.el within Org Jarmo Hurri
2022-07-21 10:22 ` Munyoki Kilyungi
2022-07-22 7:28 ` Jarmo Hurri
2022-07-25 21:15 ` Munyoki Kilyungi
2022-07-25 21:15 ` Munyoki Kilyungi
2022-07-26 3:40 ` Greg Minshall
2022-07-26 9:52 ` Jarmo Hurri
2022-07-26 2:05 ` Ihor Radchenko
2022-07-26 10:09 ` Jarmo Hurri
2022-07-27 3:12 ` Ihor Radchenko
2022-07-27 3:13 ` Ihor Radchenko
2022-07-27 0:03 ` Tim Cross
2022-07-27 3:06 ` Ihor Radchenko
2022-07-27 4:09 ` Tim Cross
2022-08-18 16:04 ` Max Nikulin
2022-07-27 4:07 ` Jarmo Hurri
2022-09-01 7:52 ` Bastien
2022-09-03 13:25 ` Jarmo Hurri [this message]
2022-09-27 22:06 ` Bastien
2022-10-08 9:58 ` Jarmo Hurri
2022-11-09 6:21 ` Ihor Radchenko
2022-11-10 12:23 ` Jarmo Hurri
2022-11-13 4:27 ` Ihor Radchenko
2022-11-19 11:15 ` Bastien
2022-11-21 6:59 ` Jarmo Hurri
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=87k06kwpwi.fsf@iki.fi \
--to=jarmo.hurri@iki.fi \
--cc=emacs-orgmode@gnu.org \
/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).