[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU ELPA package discoverability
From: |
Richard Stallman |
Subject: |
Re: GNU ELPA package discoverability |
Date: |
Sat, 23 May 2020 23:53:00 -0400 |
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> You mention 'within the limits of our basic goals'. I don't think this has
> been clearly defined
The goal of the GNU Project is to develop the entirely-free operating
system GNU and rid the world of nonfree software. It is a very
ambitious goal, but we will push as far as we can, and we will not
give up.
> Something which will need to
> be considered at this point is available maintenance resources. For
> example, at a high level, having a stable and reliable archive of elisp
> packages which are guaranteed to be GPL compliant and do not reference,
> link-to or encourage the use of non-free software, but does not require
> assignment of copyright to the FSF may be a worthy goal. However, if the
> resources are not available to maintain such an archive and or
> adding/updating code in the archive becomes a slow process because
> approvals take too long (because there are insufficient resources), it
> simply won't work.
Since we will put less effort into checking and maintaining these
packages than into GNU ELPA packages, we can surely handle more
packages in it.
How many more? It isn't useful to worry about. If this is the
right approach, we will try it and see how many.
> Document process workflow, the steps a developer needs to follow in order
> to get their code into the appropriate place and how to manage bugs,
Our usual approach is to try things, develop a practice that works,
then write it down. Too much advance planning is a pain, and often it
turns out not to be useful. Once we have real experience we can make
a better plan.
What we do need to write down are the criteria that would make a package
acceptable for each repositor. We need that stated clearly so that
we make consistent decisions.
> developer should be confident [perse] now know[s] what is the appropriate
> location for [per] code
When would that question arise? In what scenario?
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
- RE: GNU ELPA package discoverability, (continued)
- RE: GNU ELPA package discoverability, Drew Adams, 2020/05/20
- Re: GNU ELPA package discoverability, Richard Stallman, 2020/05/20
- Re: GNU ELPA package discoverability, Tim Cross, 2020/05/21
- Re: GNU ELPA package discoverability, Richard Stallman, 2020/05/21
- Re: GNU ELPA package discoverability, Vasilij Schneidermann, 2020/05/22
- Re: GNU ELPA package discoverability, Richard Stallman, 2020/05/23
- Re: GNU ELPA package discoverability, Vasilij Schneidermann, 2020/05/24
- Re: GNU ELPA package discoverability, Richard Stallman, 2020/05/25
- Re: GNU ELPA package discoverability, Vasilij Schneidermann, 2020/05/25
- Re: GNU ELPA package discoverability, Tim Cross, 2020/05/22
- Re: GNU ELPA package discoverability,
Richard Stallman <=
- Re: GNU ELPA package discoverability, Tim Cross, 2020/05/24
- Re: GNU ELPA package discoverability, Eli Zaretskii, 2020/05/24
- Re: GNU ELPA package discoverability, Tim Cross, 2020/05/24
- Re: GNU ELPA package discoverability, Eli Zaretskii, 2020/05/25
- Re: GNU ELPA package discoverability, Tim Cross, 2020/05/25
- Re: GNU ELPA package discoverability, Eli Zaretskii, 2020/05/26
- Re: GNU ELPA package discoverability, Tim Cross, 2020/05/26
- Re: GNU ELPA package discoverability, Eli Zaretskii, 2020/05/26
- Re: GNU ELPA package discoverability, Tim Cross, 2020/05/27
- Re: GNU ELPA package discoverability, Eli Zaretskii, 2020/05/27