From: Stefan Kangas <stefankangas@gmail.com>
To: Boruch Baum <boruch_baum@gmx.com>,
Emacs-Devel List <emacs-devel@gnu.org>
Subject: Re: non-gnu elpa issue tracking
Date: Wed, 9 Dec 2020 10:58:01 -0600 [thread overview]
Message-ID: <CADwFkmnJ=00CqGqu6Dx7HaerZucsb27310HA2+U_=OM2hwkJuA@mail.gmail.com> (raw)
In-Reply-To: <20201209125516.lenqswi7fhiscbr2@E15-2016.optimum.net>
Boruch Baum <boruch_baum@gmx.com> writes:
> I've read sumaries of Richard Stallman's presentation about the
> proposed, and in comparing it with Stefan Monnier's in-progress web
> interface, have several suggestions:
>
> 1) License disclosure: The summaries indicate that RMS is open to having
> the repository host packages bearing *any* free license, but there
> may be users who are pickier, so a package's license should be
> disclosed prominently on the listing page and the package detail
> page;
Are there any packages out there that don't use the GPL? Could you
point us to some examples?
> 2) The acceptance or candidacy process for each package should be
> documented in some discrete method. Melpa does this using github's
> pull request feature, which documents the entire conversation related
> to the process of accepting a package.
Could you be more specific? Do you mean that we should document it
somewhere, or do you mean something else?
> 3) After a package is initially accepted to the repository, the
> summaries of Richard Stallman's presentation indicate that subsequent
> commits or releases may be rejected or modified. That record should
> also be documented. Debian does this using its own package tracking
> software.
>
> Here's an example of it in action (for the package 'bash'):
> https://tracker.debian.org/pkg/bash
>
> It's source code is available on its 'salsa' repository (gitlab?):
> https://salsa.debian.org/qa/distro-tracker
>
> Debian's experience and the automation of its infrastructure might be
> useful to adopt in-toto even if its not an absolutely perfect match
> because it's a turnkey solution and is actively maintained (eg. they
> may accept feature requests).
"Debian's infrastructure" is massive and has many moving parts.
Do you suggest that we should adopt all of that wholesale?
> 4) There's no link on the repository page[1] to the software being used
> to generate it, and the forge at which it is being developed. Having
> that would make the infrastructure friendlier for pull-requests, bug
> reports, and other feedback.
I assume that there will be a landing page similar to the one on
elpa.gnu.org.
next prev parent reply other threads:[~2020-12-09 16:58 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 12:55 non-gnu elpa issue tracking Boruch Baum
2020-12-09 16:58 ` Stefan Kangas [this message]
2020-12-09 19:18 ` Jean Louis
2020-12-09 21:48 ` Stefan Kangas
2020-12-09 23:40 ` Jean Louis
2020-12-09 23:58 ` Jean Louis
2020-12-11 6:09 ` Richard Stallman
2020-12-11 6:05 ` Richard Stallman
2020-12-10 4:32 ` Richard Stallman
2020-12-10 6:28 ` Jean Louis
2020-12-09 19:23 ` Jean Louis
2020-12-09 23:22 ` Thibaut Verron
2020-12-10 0:09 ` Jean Louis
2020-12-10 9:14 ` Thibaut Verron
2020-12-10 11:23 ` Stefan Kangas
2020-12-10 14:19 ` Thibaut Verron
2020-12-10 16:37 ` Jean Louis
2020-12-11 6:10 ` Richard Stallman
2020-12-10 11:49 ` Jean Louis
2020-12-10 14:05 ` Stefan Kangas
2020-12-10 15:48 ` Stefan Monnier
2020-12-10 16:05 ` Jean Louis
2020-12-10 17:35 ` Stefan Monnier
2020-12-11 6:09 ` Richard Stallman
2020-12-11 6:04 ` Richard Stallman
2020-12-11 11:10 ` Thibaut Verron
2020-12-12 5:34 ` Richard Stallman
2020-12-12 6:37 ` Tim Cross
2020-12-12 10:08 ` Thibaut Verron
2020-12-12 15:23 ` Tim Cross
2020-12-12 17:07 ` Thibaut Verron
2020-12-13 4:56 ` Richard Stallman
2020-12-13 5:20 ` Tim Cross
2020-12-13 9:54 ` Andrea Corallo via Emacs development discussions.
2020-12-13 22:59 ` Tim Cross
2020-12-14 0:32 ` Stefan Monnier
2020-12-14 0:54 ` Tim Cross
2020-12-14 4:36 ` Stefan Monnier
2020-12-14 5:45 ` Tim Cross
2020-12-15 5:44 ` Richard Stallman
2020-12-14 10:03 ` Alfred M. Szmidt
2020-12-14 14:57 ` Stefan Monnier
2020-12-14 15:01 ` Alfred M. Szmidt
2020-12-14 15:12 ` Stefan Monnier
2020-12-14 15:52 ` Eli Zaretskii
2020-12-14 0:16 ` Stephen Leake
2020-12-13 4:56 ` Richard Stallman
2020-12-13 8:56 ` Vasilij Schneidermann
2020-12-14 5:50 ` Richard Stallman
2020-12-14 6:45 ` Jean Louis
2020-12-12 13:48 ` Michael Albinus
2020-12-12 13:50 ` Stefan Monnier
2020-12-12 15:37 ` Tim Cross
2020-12-12 19:54 ` Jean Louis
2020-12-12 20:46 ` Stephen Leake
2020-12-12 21:24 ` Alfred M. Szmidt
2020-12-12 21:48 ` Christopher Dimech
2020-12-13 0:39 ` Tim Cross
2020-12-13 1:28 ` Christopher Dimech
2020-12-13 5:03 ` Richard Stallman
2020-12-13 4:58 ` Richard Stallman
2020-12-12 21:06 ` Dmitry Gutov
2020-12-13 4:58 ` Richard Stallman
2020-12-13 5:27 ` Christopher Dimech
2020-12-12 19:33 ` Jean Louis
2020-12-12 21:24 ` Alfred M. Szmidt
2020-12-13 4:59 ` Richard Stallman
2020-12-13 5:03 ` Richard Stallman
2020-12-14 17:38 ` Jean Louis
2020-12-14 18:49 ` Vasilij Schneidermann
2020-12-14 22:13 ` Jean Louis
2020-12-14 19:10 ` Boruch Baum
2020-12-14 22:17 ` Jean Louis
2020-12-16 5:32 ` Richard Stallman
2021-01-02 5:25 ` Richard Stallman
2020-12-10 4:35 ` Richard Stallman
2020-12-10 5:03 ` Boruch Baum
2020-12-10 5:55 ` Eli Zaretskii
2020-12-10 6:39 ` "Open records", "good government principles", "corporate culture" Boruch Baum
2020-12-10 7:27 ` Jean Louis
2020-12-10 14:08 ` Eli Zaretskii
2020-12-11 6:16 ` Richard Stallman
2020-12-10 6:54 ` non-gnu elpa issue tracking Jean Louis
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='CADwFkmnJ=00CqGqu6Dx7HaerZucsb27310HA2+U_=OM2hwkJuA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=boruch_baum@gmx.com \
--cc=emacs-devel@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.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).