all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: emacs-devel@gnu.org
Subject: Re: GNU ELPA package proposal: visual-fill-column
Date: Tue, 26 Oct 2021 10:50:50 -0400	[thread overview]
Message-ID: <jwvlf2fyhew.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87k0i0w39l.fsf@fastmail.fm> (Joost Kremers's message of "Tue, 26 Oct 2021 10:38:23 +0200")

> Philip Kaludercic asked me if I would be interested in adding my package
> `visual-fill-column` to GNU ELPA.[1]

Sounds great!

> While I'm still a bit hazy on the details (though I'm sure it will all
> clear itself up it due time), I do know the process starts with
> a copyright assignment.  I haven't done that yet, so my first question
> is: how do I do that?

Fill the form below and email it as instructed to the FSF so they can
send you the relevant paperwork to sign.

> Another question that occurred to me: the package is currently available on
> Melpa. I know there are packages that exist both on MELPA and on GNU ELPA, but
> for `visual-fill-column`, that doesn't seem to make a lot of sense. If the
> package is added to GNU ELPA and removed from MELPA, would that cause any
> inconvenience for existing users? Would `package.el` be smart enough to update
> existing users to the GNU ELPA version, once a new version is published there?
> Or would it be better to keep the MELPA version to avoid any disruptions?

No, `package.el` is not smart enough.  The reason is that the version
numbers used by MELPA don't match the ones used in GNU ELPA, so the
MELPA versions always seem to be "much higher" than the ones in GNU ELPA
(e.g. 20180223.223 > 5.7.2).  The users can explicitly "downgrade" to
the GNU ELPA version, of course, but it won't happen
automatically/transparently.

The same problem plagues transitions from MELPA to MELPA-Stable,
but not between MELPA-Stable and GNU ELPA ;-)


        Stefan


Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES

[What is the name of the program or package you're contributing to?]
Emacs

[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]


[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your postal address here.]





[Which files have you changed so far, and which new files have you written
so far?]




  parent reply	other threads:[~2021-10-26 14:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  8:38 GNU ELPA package proposal: visual-fill-column Joost Kremers
2021-10-26 13:06 ` Eli Zaretskii
2021-10-26 13:46   ` Michael Heerdegen
2021-10-26 13:47   ` Daniel Martín
2021-10-26 14:17     ` Eli Zaretskii
2021-10-26 17:10       ` Joost Kremers
2021-10-26 14:50 ` Stefan Monnier [this message]
2021-10-26 15:17   ` Stefan Kangas
2021-10-26 15:20     ` Stefan Monnier
2021-10-26 15:29       ` Stefan Kangas
2021-10-26 19:03       ` Philip Kaludercic
2021-11-01 20:27 ` Philip Kaludercic
2021-11-01 21:35   ` Stefan Monnier
2021-11-01 23:39     ` Philip Kaludercic
2021-11-02  2:03       ` Stefan Monnier
2021-11-02 20:52         ` Joost Kremers
2021-11-01 22:23   ` Daniel Martín

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvlf2fyhew.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.