discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Leo <sourcehut@relevant-information.com>
Cc: piem@inbox.kyleam.com
Subject: distributing piem via *ELPA
Date: Mon, 27 Dec 2021 16:07:14 -0500	[thread overview]
Message-ID: <87bl11lptp.fsf@kyleam.com> (raw)
In-Reply-To: <87a6gmav5t.fsf@hako.i-did-not-set--mail-host-address--so-tickle-me>

Leo writes:

> I must thank you for your patience with my sloppy elisp mistakes.  I
> feel like I've learned a lot from submitting these patches thanks to
> you.

Thanks for the kind words, and no worries about mistakes.  I appreciate
the interest and contributions.

> By the way, is there any reason why this package hasn't been submitted
> to elpa or melpa?  It's currently pretty difficult to find this package
> despite its usefulness which seems like a shame to me.

Yeah, that's a valid complaint.

I've come around to the view that in general software maintainers
shouldn't distribute their source code [1].  That feels natural to
someone like me that pulls in most of their packages from Guix (and
nearly everything else from Debian), but it's of course not the norm for
a lot of repositories, particularly language-specific ones.

So, while I don't plan to distribute piem myself, I'd be glad to see
others do so at some point.  Of course that depends on some critical
mass of users gaining interest even though, as you say, piem is pretty
difficult to discover.  I suppose there are other ways I could try to
increase its visibility (e.g., posting demos or info in places that get
more traffic), but that's not something I've done much of---just a few
mentions on Guix lists [2] and a pointer in public-inbox's
Documentation/clients.txt [3].

If you or someone else is interested in submitting piem to an *ELPA
repository, NonGNU ELPA [4] or MELPA would be the primary options, I
think.  ELPA proper is off the table because I don't want to require
copyright assignments from contributors.


[1] I think this post from Drew Default lays out the position well,
    though I can't say whether it's likely to be convincing to someone
    that doesn't already share a similar view:

    https://drewdevault.com/2019/12/09/Developers-shouldnt-distribute.html

[2] https://yhetil.org/guix/?q=nq%3Apiem

[3] https://80x24.org/public-inbox.git/commit/?id=c62ab5b7500bd9e7c584f5972e3c115842598957

[4] https://elpa.nongnu.org/

  reply	other threads:[~2021-12-27 21:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 16:01 Adding support for editing patches before applying them sourcehut
2021-12-08 16:01 ` [PATCH 1/1] piem-notmuch-am-ready-mbox: Add option to edit " sourcehut
2021-12-09  3:43   ` Kyle Meyer
2021-12-09  5:20     ` Kyle Meyer
2021-12-09 10:10     ` Leo
2021-12-09 13:00       ` Leo
2021-12-10  5:08         ` Kyle Meyer
2021-12-10  9:31           ` Leo
2021-12-11 21:44             ` Kyle Meyer
2021-12-16 20:05               ` [PATCH] Add ability " sourcehut
2021-12-17  5:58                 ` Kyle Meyer
2021-12-21 14:02                   ` [PATCH v2] " sourcehut
2021-12-24 18:32                     ` Kyle Meyer
2021-12-27 16:07                       ` Leo
2021-12-27 21:07                         ` Kyle Meyer [this message]
2021-12-27 21:30                           ` distributing piem via *ELPA Kyle Meyer
2021-12-09  3:38 ` Adding support for editing patches before applying them Kyle Meyer

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://git.kyleam.com/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bl11lptp.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --cc=sourcehut@relevant-information.com \
    /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.kyleam.com/piem/

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).