emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org, Bastien <bzg@gnu.org>
Subject: Re: [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements
Date: Sun, 31 Mar 2024 10:46:26 -0500	[thread overview]
Message-ID: <d0671baf-9b14-43f6-aff5-7e0f96647f2d@alphapapa.net> (raw)
In-Reply-To: <87frw80yf5.fsf@localhost>

On 3/30/24 06:08, Ihor Radchenko wrote:

> This is actually not true that Emacs repository has a separate copyright
> assignment form.
> CONTRIBUTE file says
>      In most cases, to start the assignment process you should download
>      https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future
>      and return the completed information to the address at the top.
> This is linking to one of the forms at gnulib, the same with what
> gnu.org suggests.
> In contrast, we, in WORG, link to a _copy_ of the form rather than to
> the original form.
> I've just pushed some clarifications to org-maintenance page, adding the
> correct link, but still leaving our current form - our form has one
> answer pre-filled.
> https://git.sr.ht/~bzg/worg/commit/e5deaca5


>> TODO: Get updated version of form from Emacs maintainers that includes
>> the line asking the secretary to send confirmation to interested
>> parties (i.e. the Org maintainers).
> I am inclined to remove this todo - I already asked gnulib guys and they
> contacted FSF about the latest version of the form. Until we get a
> reply, there is nothing we can act upon. See
> https://lists.gnu.org/archive/html/bug-gnulib/2024-03/msg00060.html

FWIW, I'd be inclined to leave the task for future action, perhaps 
changing it to a WAITING keyword with a state-change note explaining the 
status (that's what I use in my system, anyway).  But if you disagree, I 
won't argue.


  reply	other threads:[~2024-03-31 15:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24 12:35 [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements Ihor Radchenko
2024-03-24 17:55 ` Bastien Guerry
2024-03-24 18:26   ` Ihor Radchenko
2024-03-25  8:17     ` Bastien Guerry
2024-03-25 14:17 ` Adam Porter
2024-03-26 14:59   ` Ihor Radchenko
2024-03-27  3:23     ` Adam Porter
2024-03-28 12:01       ` Ihor Radchenko
2024-03-28 12:49         ` Adam Porter
2024-03-28 13:11           ` Ihor Radchenko
2024-03-29 18:17           ` Bastien Guerry
2024-03-30 11:08   ` Ihor Radchenko
2024-03-31 15:46     ` Adam Porter [this message]
2024-04-02 11:20       ` Ihor Radchenko
2024-04-02 23:01         ` Adam Porter
2024-04-03  0:39           ` Samuel Wales
2024-04-03 12:20             ` Ihor Radchenko
2024-04-03 12:18           ` Ihor Radchenko
2024-05-08 12:12         ` Ihor Radchenko

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=d0671baf-9b14-43f6-aff5-7e0f96647f2d@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \


* 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


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).