From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:203:b4db::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms12 with LMTPS id gHmGKgUrymFILwAAsNZ9tg (envelope-from ) for ; Mon, 27 Dec 2021 21:07:17 +0000 Received: from out0.migadu.com ([2001:41d0:2:267::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id kFetKQUrymFtPQEA9RJhRA (envelope-from ) for ; Mon, 27 Dec 2021 22:07:17 +0100 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1640639237; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=p9In4ZqXhRUEjHtrxtjkGODgMXvpU8sp8KFlCl+wO+c=; b=IGVUsedm2aa4WC1+E/BDXzVrGpPB/6JlV0Q/DjBf+yiQ07cLobxr+GbuvGPc9umtKHVyeW JP+E03SDUl7x2DjIrvQJ64dluC8t6gcV1lcLxxQBtT42YyXCjVI5NiTUcKLPd8P33pj9Z+ 8RRAq++nwnD8YE4G0PU1KMUF23u2bH51Ny7hkz+7dTCDtnPpu4dFE7FcdxBgg6I1B8ha6C yMpMp7ZHYQowXQAH/3NvwsEi3t3sDkUd4OKp5t91xqfm7yeR2/2Fle1giEzSFohbk0m/H3 afVeO5o7xTBs2VskksYf1yXtEcmz4YoM5yYTy93iG2Zc8dhXy9PopdQw5+oGtg== From: Kyle Meyer To: Leo Cc: piem@inbox.kyleam.com Subject: distributing piem via *ELPA In-Reply-To: <87a6gmav5t.fsf@hako.i-did-not-set--mail-host-address--so-tickle-me> References: <878rwjwz52.fsf@kyleam.com> <20211221140212.30248-1-sourcehut@relevant-information.com> <87ee61g8gf.fsf@kyleam.com> <87a6gmav5t.fsf@hako.i-did-not-set--mail-host-address--so-tickle-me> Date: Mon, 27 Dec 2021 16:07:14 -0500 Message-ID: <87bl11lptp.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kyleam.com X-TUID: qkclILQIcdW8 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/