unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: rms@gnu.org, stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: magit copyright assignments
Date: Fri, 19 Jul 2024 20:32:11 +0300	[thread overview]
Message-ID: <8634o5fftw.fsf@gnu.org> (raw)
In-Reply-To: <87ed7qbfp6.fsf@jeremybryant.net> (message from Jeremy Bryant on Thu, 18 Jul 2024 21:36:21 +0100)

> From: Jeremy Bryant <jb@jeremybryant.net>
> Cc: rms@gnu.org,  stefankangas@gmail.com,  emacs-devel@gnu.org
> Date: Thu, 18 Jul 2024 21:36:21 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Jeremy Bryant <jb@jeremybryant.net>
> >> Cc: rms@gnu.org,  stefankangas@gmail.com,  emacs-devel@gnu.org
> >> Date: Thu, 18 Jul 2024 17:53:31 +0100
> >> 
> >> It appears I didn't explain my idea clearly enough, I'll attempt to clarify.
> >> 
> >> I am proposing a *separate*, much smaller, form, modelled on the main
> >> form.  A sort of 'package form'. The advantages are
> >> 
> >> 1. The wording can be agreed in advance to be the most appropriate.
> >> 
> >> 2. This 'package form' can be distributed by the Emacs maintainers to
> >> those volunteers willing to follow-up on package assignments, and
> >> everybody uses the best wording as per 1.
> >
> > If this is for us, then how is it different from just asking whether
> > they contribute the package?  The assignment form is a form because the
> > FSF assignment clerk needs to collect specific information, but here
> > no specific information is needed, just an informal agreement.
> >
> 
> 
> > IOW, why codify and formalize something that is informal to begin
> > with, and a simple question to ask?
> 
> Because, at least from my own interpretation of the thread, that by
> asking the question in an imprecise manner it may not satisfy the
> conditions set by the advice from the lawyer.  Hence the suggestion to
> formalize the question itself, even if short.
> 
> But perhaps this is an abundance of caution on my part, I have so far limited
> experience of following up contributor's assignments.

IME, the exact words to reach out depend on the package and its
developers, so I think it is best not to have any standard wording,
but leave it to the Emacs maintainer to come up with it.




  reply	other threads:[~2024-07-19 17:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13 15:50 magit copyright assignments Jeremy Bryant
2024-07-13 16:25 ` Eli Zaretskii
2024-07-13 21:39   ` Jeremy Bryant
2024-07-14  4:50     ` Eli Zaretskii
2024-07-15 20:10       ` Jeremy Bryant
2024-07-15 20:49         ` Stefan Kangas
2024-07-16  2:17   ` Richard Stallman
2024-07-16  5:53     ` Lele Gaifax
2024-07-16 10:29       ` Eli Zaretskii
2024-07-16 17:23         ` Lele Gaifax
2024-07-16 18:25           ` Eli Zaretskii
2024-07-16 19:09             ` Lele Gaifax
2024-07-18  3:21             ` Richard Stallman
2024-07-18  5:15               ` Eli Zaretskii
2024-07-21  3:00                 ` Richard Stallman
2024-07-16  2:18   ` Richard Stallman
2024-07-16 21:27     ` Jeremy Bryant
2024-07-17 11:23       ` Eli Zaretskii
2024-07-17 13:53         ` Jeremy Bryant
2024-07-18  3:21       ` Richard Stallman
2024-07-18 14:02         ` Jeremy Bryant
2024-07-18 15:31           ` Eli Zaretskii
2024-07-18 16:53             ` Jeremy Bryant
2024-07-18 17:40               ` Eli Zaretskii
2024-07-18 20:36                 ` Jeremy Bryant
2024-07-19 17:32                   ` Eli Zaretskii [this message]
2024-07-21  3:02                 ` 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=8634o5fftw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=rms@gnu.org \
    --cc=stefankangas@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).