From: Phil Estival <pe@7d.nz>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: packages submissions : ob-sql-session and org-blog
Date: Tue, 17 Sep 2024 12:02:49 +0200 [thread overview]
Message-ID: <28da95b9-131a-4fbf-bedc-56219082233d@7d.nz> (raw)
In-Reply-To: <87zfoe64bl.fsf@posteo.net>
* [2024-09-11 09:24] Philip Kaludercic:
> Phil Estival <pe@7d.nz> writes:
>> Hello
on ob-sql-session
>> that I'd like to submit to ELPA, with
>> the advise and approval of emacs-devel.
> Just to be sure, you mean GNU ELPA (not NonGNU ELPA), right?
I think so. The ownership transferred to the FSF and a copyright
assignment. One word about the license notice: I'm in agreement
with Stephan's opinion:
> historically we have accepted both "is part of GNU Emacs" and "is NOT
> part of GNU Emacs". IMO the better choice is to say neither.
on org-blog :
> Hmm, I don't know if we have any literate programs on ELPA yet. If you
> prefer that style of development, that is fair, but what I would suggest
> would be to add a Makefile and extract the elisp at "compile-time", or
> in the case of ELPA when the tarball is being built.
> skimming through the .org file (which most certainly should /not/ be
> the README btw) the code could also use some cleaning
> up, at least if the intention is to publish it as a generic package.
> The functions don't seem to adhere to a specific conventional namespace,
> I have my doubts as to how much sense it would make to try and convert
> this personal code into a proper package, instead of starting over again :/
Understood. I'll be back with something cleaner, reconsider
where it can rely on the existing structures, and seek more advice
on the Org mailing list. Thanks for everything.
Phil
next prev parent reply other threads:[~2024-09-17 10:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 14:50 packages submissions : org-sql-session and org-blog Phil Estival
2024-09-11 3:01 ` Adam Porter
2024-09-17 10:00 ` packages submissions : ob-sql-session " Phil Estival
2024-09-17 22:25 ` Adam Porter
2024-09-18 1:41 ` package submission : ob-sql-session Phil Estival
2024-10-20 12:34 ` Ihor Radchenko
2024-11-04 18:16 ` Phil Estival
2024-11-09 14:43 ` Ihor Radchenko
2024-09-11 7:24 ` packages submissions : org-sql-session and org-blog Philip Kaludercic
2024-09-17 10:02 ` Phil Estival [this message]
2024-09-19 7:47 ` packages submissions : ob-sql-session " Philip Kaludercic
2024-09-22 4:09 ` Richard Stallman
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28da95b9-131a-4fbf-bedc-56219082233d@7d.nz \
--to=pe@7d.nz \
--cc=emacs-devel@gnu.org \
--cc=philipk@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.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).