From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Morgan Willcock" <morgan@ice9.digital>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: kixtart-mode
Date: Wed, 09 Nov 2022 18:58:19 -0500 [thread overview]
Message-ID: <jwvleoju1pt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <6061-636c2e00-95-57685e00@208106730> (Morgan Willcock's message of "Wed, 09 Nov 2022 23:48:25 +0100")
Morgan Willcock [2022-11-09 23:48:25] wrote:
> On Wednesday, November 09, 2022 22:04 GMT, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> > Would there be any issues in adding the package?
>>
>> There is one issue, yes: is KiXtart Free Software?
>> According to Wikipedia, the license is "Closed source Careware".
>> And indeed, I can't find any source code on http://www.kixtart.org/.
>> If that's indeed proprietary code, then I think we probably wouldn't
>> want to host `kixtart-mode` on (Non)GNU ELPA.
>
> There is no dependency or inter-op with the interpreter, and the package
> was developed independently - since the source code is not available it
> is also impossible for me to create any link to it.
Yes, I understand this. The question is rather one of policy/strategy
than one of copyright.
> But if this is the final decision I'll live with it.
I can never remember exactly what is the policy in such cases, so I'm
hoping Richard will chime in. AFAIK the general rule is that we don't
want to distribute packages which are only meaningful when you use
proprietary software, but the details matter (e.g. is it likely that
someone will choose to use another editor to edit their KiXtart code, is
it likely that someone will start to use KiXtart because it has a nice
Emacs mode, ...).
>> Find below my sig a suggested patch to fix a few minor issues I found
>> along the way (the main one is arguably the way `kixtart-tempo-tags`
>> is passed to `tempo-define-template`).
> Thanks for taking a look. Are you happy if I take your patch, regardless
> of where the package ends up?
Yes, of course :-)
Stefan
next prev parent reply other threads:[~2022-11-09 23:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 20:55 [ELPA] New package: kixtart-mode morgan
2022-11-09 21:10 ` Philip Kaludercic
2022-11-09 21:24 ` Morgan Willcock
2022-11-09 22:04 ` Stefan Monnier
2022-11-09 22:48 ` Morgan Willcock
2022-11-09 23:58 ` Stefan Monnier [this message]
2022-11-10 0:20 ` Morgan Willcock
2022-11-10 0:40 ` Juanma Barranquero
2022-11-13 4:18 ` Richard Stallman
2022-11-13 7:09 ` Eli Zaretskii
2022-12-11 23:33 ` Richard Stallman
2022-12-12 12:14 ` Eli Zaretskii
2022-12-11 23:50 ` Óscar Fuentes
2022-12-12 6:17 ` North Year
2022-12-12 12:21 ` Eli Zaretskii
2022-12-12 14:00 ` Óscar Fuentes
2022-12-20 23:59 ` Morgan Willcock
2022-11-10 8:16 ` Akib Azmain Turja
2022-11-10 8:25 ` Eli Zaretskii
2022-11-10 9:00 ` Akib Azmain Turja
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=jwvleoju1pt.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=morgan@ice9.digital \
/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).