[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NonGNU ELPA and release frequency
From: |
Jean Louis |
Subject: |
Re: NonGNU ELPA and release frequency |
Date: |
Sat, 24 Oct 2020 10:08:04 +0300 |
User-agent: |
Mutt/+ (1036f0e) (2020-10-18) |
My proposals for plan of action for ELPA on nongnu.org are following,
and they are not in any order:
- [ ] establish goals purposes for non-GNU ELPA.
My proposal for purpose is to provide useful GNU Emacs packages as
free software meant for inclusion into fully free and FSF endorsed
free system distributions. Guidelines for free software system
distributions on
https://www.gnu.org/distros/free-system-distribution-guidelines.html
should apply for non-GNU ELPA and for GNU ELPA as well.
- [ ] set up the mailing list for non GNU ELPA. My proposal would be:
nongnu-elpa-devel@nongnu.org as maybe it would be good not to mix it
with emacs-devel
- [ ] Find contact information of many developers and invite
developers personally to contribute their packages, they can start
contributing already by using the mailing list and collaborating
with others.
- [ ] discuss the set of policies or principles for non-GNU ELPA. For
example do we really want to see Python packages wrapped inside of
the GNU Emacs package? I don't.
- [ ] obtain server space for hosting of a website
- [ ] decide on sub domain or URL, it could for example
https://elpa.nongnu.org
- [ ] replicate GNU ELPA website in similar fashon on ELPA on
nongnu.org without changing much, keep informing public on the
website of the project's progress
- [ ] provide hosting and shell access to set up git and free code
hosting platform familiar to many developers using Github. Such free
code hosting platform is https://gitea.io/en-us/ or Gitlab.com, I
would prefer first. It looks similar to Github, look here:
https://gitea.com/gitea/gitea-vet and there is problem with one
Javascript, they have to be asked to publish the license properly.
- [ ] install such git hosting, install Gitea or Gitlab or other web based
git whatever be decided as best
- [ ] use already made software for GNU ELPA to develop in same
fashion for elpa.nongnu.org, as not to change drastically well
established workflows
- [ ] propose improvements to workflows both on GNU ELPA and non-GNU
ELPA, and collaborate with emacs-devel
- [ ] start distributing few packages, and keep including other
packages
- [ ] when time seem right, include the package repository
specification in GNU Emacs
- [ ] welcome and invite developers to switch to free hosting at
nongnu.org
- [ ] welcome and invite developers to contribute their packages to
GNU ELPA and transition their package. Futurem may become blended.
- [ ] keep doing all well established actions just as GNU ELPA is
doing to provide more free software for purpose of expansion of
fully free operating systems.
- [ ] add additional scripts or support to help various other
GNU/Linux distributions to easily package both GNU ELPA and non-GNU
ELPA packages
Jean
Re: NonGNU ELPA and release frequency, Richard Stallman, 2020/10/23
- Re: NonGNU ELPA and release frequency,
Jean Louis <=
- Re: NonGNU ELPA and release frequency, Eli Zaretskii, 2020/10/24
- Re: NonGNU ELPA and release frequency, Jean Louis, 2020/10/24
- Re: NonGNU ELPA and release frequency, Eli Zaretskii, 2020/10/24
- Re: NonGNU ELPA and release frequency, Jean Louis, 2020/10/24
- Re: NonGNU ELPA and release frequency, Eli Zaretskii, 2020/10/24
- Re: NonGNU ELPA, Jean Louis, 2020/10/24
- Re: NonGNU ELPA, Eli Zaretskii, 2020/10/24
Re: NonGNU ELPA and release frequency, Antoine Kalmbach, 2020/10/24
Re: NonGNU ELPA, Jean Louis, 2020/10/24
Re: NonGNU ELPA, Antoine Kalmbach, 2020/10/24