From: Dmitry Gutov <dgutov@yandex.ru>
To: rms@gnu.org, Ivan Yonchovski <yyoncho@gmail.com>
Cc: bugs@gnu.support, ane@iki.fi, emacs-devel@gnu.org
Subject: Re: NonGNU ELPA and release frequency
Date: Mon, 26 Oct 2020 19:37:00 +0200 [thread overview]
Message-ID: <9cf567ef-caee-5596-b94d-a4ebccd208db@yandex.ru> (raw)
In-Reply-To: <E1kWtq7-0006k5-DZ@fencepost.gnu.org>
On 26.10.2020 06:10, Richard Stallman wrote:
> > So, if someone wants to be in NonGNU elpa should not be using github? If
> > this is the case then why it is fine for ELPA package to be in github
> > but it won't be fine for NonGNU ELPA?
>
> I haven't come to a conclusion about that. I see a few possibilities.
>
> * If the Emacs maintainers who work on this package have Github accounts,
> in principle we could deal with it on GitHub.
All right, then.
> * We could make a repo on Savannah that has a more-or-less copy of the
> GitHub repo, and our maintainers could when necessary make their
> changes there.
>
> It depends on whether the package maintainer is cooperating with us.
> If so, the first option is possible. If not, we would certainly do
> the latter.
Would we have packages where the maintainers don't cooperate, though?
At best, such a package should be a fork, but then it could also be
renamed, and then hosted on Savannah, or wherever.
In the common case, the package maintainer should in contact.
The GNU ELPA experience shows that unilateral changes coming from "us"
and not from maintainers are rare. They should be rarer still in the
case of Non-GNU ELPA.
next prev parent reply other threads:[~2020-10-26 17:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 11:59 NonGNU ELPA and release frequency Antoine Kalmbach
2020-10-23 12:24 ` Stefan Kangas
2020-10-23 18:25 ` Antoine Kalmbach
2020-10-24 3:45 ` Richard Stallman
2020-10-24 13:51 ` Antoine Kalmbach
2020-10-26 9:56 ` Philip K.
2020-10-27 3:41 ` Richard Stallman
2020-10-24 3:50 ` Richard Stallman
2020-10-24 7:08 ` Jean Louis
2020-10-24 8:41 ` Eli Zaretskii
2020-10-24 12:06 ` Jean Louis
2020-10-24 12:54 ` Eli Zaretskii
2020-10-24 14:12 ` Jean Louis
2020-10-24 14:16 ` Eli Zaretskii
2020-10-24 14:21 ` NonGNU ELPA Jean Louis
2020-10-24 14:50 ` Eli Zaretskii
2020-10-24 14:25 ` NonGNU ELPA and release frequency Antoine Kalmbach
2020-10-24 14:29 ` NonGNU ELPA Jean Louis
2020-10-24 14:40 ` Antoine Kalmbach
2020-10-24 16:37 ` Michael Albinus
2020-10-24 17:05 ` Stefan Kangas
2020-10-24 18:00 ` Antoine Kalmbach
2020-10-24 19:12 ` Michael Albinus
2020-10-25 11:40 ` Michael Albinus
2020-10-25 12:20 ` Antoine Kalmbach
2020-10-25 3:48 ` NonGNU ELPA and release frequency Richard Stallman
2020-10-25 10:29 ` Dmitry Gutov
2020-10-25 13:50 ` Stefan Monnier
2020-10-25 14:54 ` Ivan Yonchovski
2020-10-25 15:15 ` Antoine Kalmbach
2020-10-26 4:10 ` Richard Stallman
2020-10-26 10:35 ` NonGNU ELPA Jean Louis
2020-10-27 3:47 ` Richard Stallman
2020-10-26 17:37 ` Dmitry Gutov [this message]
2020-10-27 3:45 ` NonGNU ELPA and release frequency Richard Stallman
2020-10-25 3:48 ` Richard Stallman
2020-10-24 18:47 ` Stefan Monnier
2020-10-26 4:10 ` Richard Stallman
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=9cf567ef-caee-5596-b94d-a4ebccd208db@yandex.ru \
--to=dgutov@yandex.ru \
--cc=ane@iki.fi \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=yyoncho@gmail.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.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).