From: Ihor Radchenko <yantar92@posteo.net>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org, Bastien <bzg@gnu.org>
Subject: Re: [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements
Date: Thu, 28 Mar 2024 12:01:28 +0000 [thread overview]
Message-ID: <87frwatvjb.fsf@localhost> (raw)
In-Reply-To: <bdb96c09-66bb-4ce6-9106-34b009994e02@alphapapa.net>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
Adam Porter <adam@alphapapa.net> writes:
> On 3/26/24 09:59, Ihor Radchenko wrote:
>
>> I agree. My concern was not about dropping the previous wording.
>>
>> What about
>>
>> The assignment process does not always go quickly; occasionally it may
>> get stuck or overlooked at the FSF. If there is no response to the
>> contributor from FSF, Org mode maintainers can contact the FSF at
>> =copyright-clerk AT fsf DOT org=. Historically, FSF replies to the
>> maintainer request within a few days.
> ^^^^^^^
>
> Other than changing "request" to, e.g. "arrive," no objection from me.
Actually, what Bastien suggested is slightly different.
See the attached tentative patch.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-maintenance.org-Clarify-how-to-followup-when-no-.patch --]
[-- Type: text/x-patch, Size: 1477 bytes --]
From eff683e8a936edb0e84516daee8d4b8972e3ab8a Mon Sep 17 00:00:00 2001
Message-ID: <eff683e8a936edb0e84516daee8d4b8972e3ab8a.1711627236.git.yantar92@posteo.net>
From: Ihor Radchenko <yantar92@posteo.net>
Date: Thu, 28 Mar 2024 14:59:40 +0300
Subject: [PATCH] org-maintenance.org: Clarify how to followup when no reply
from FSF
* org-maintenance.org (Assignment and verification): Explain that we
allow one month for FSF to reply for the copyright request and then
follow up.
Link: https://orgmode.org/list/87o7b3bye3.fsf@localhost
---
org-maintenance.org | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/org-maintenance.org b/org-maintenance.org
index cfbb55b4..a0393e20 100644
--- a/org-maintenance.org
+++ b/org-maintenance.org
@@ -467,9 +467,12 @@ *** Assignment and verification
#+end_center
The assignment process does not always go quickly; occasionally it may
-get stuck or overlooked at the FSF. The contact at the FSF for this
-is: =copyright-clerk AT fsf DOT org=. In rare cases, an inquiry from an
-Org maintainer gets the process moving again.
+get stuck or overlooked at the FSF. If there is no response to the
+contributor from FSF within a month[fn:: The official response time is
+5 business days, according
+https://www.gnu.org/prep/maintain/maintain.html. We allow a bit
+more.], the maintainers can ask the contributor to follow up with the
+FSF, CCing the Org maintainers.
*** Authorship information
--
2.44.0
[-- Attachment #3: Type: text/plain, Size: 224 bytes --]
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-03-28 12:02 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 [this message]
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
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87frwatvjb.fsf@localhost \
--to=yantar92@posteo.net \
--cc=adam@alphapapa.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).