From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id 8CmaLRjjAmYFswAAe85BDQ:P1 (envelope-from ) for ; Tue, 26 Mar 2024 16:00:40 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id 8CmaLRjjAmYFswAAe85BDQ (envelope-from ) for ; Tue, 26 Mar 2024 16:00:40 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=bhO+sNYu; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1711465240; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=S5d2krix8CWusI7LP/bDqY60OlGzfvHK0AWozrEzdpE=; b=r+sb3zkFzamMWzijpD0KbhOJ1OMWOeY6hbCIEgtARe8D9ZiU98rfiTYFiGdGCrh7gRskqU TM/Rl4WjjJ0fp9/7DVh/i7wsqw/dQTjIInYzVCkIdW8JvjzPub/RkLMbjetZPKs98PUkke qTgUXrokgt1eGtgQdOmD3CK/IU7C+U8q1kFUr6blVt646TpToai0KBmBjMvQd3r8NvYWnR ABrD7PRfdiAMxdgQUeLCZmt28DPzfD9jRxdleJB7LQlfKxbvh13sCLZCEjEVUfy9CtdW2G +Upt2SzHqM2tuZDigVjbjWxvWeQHBOzUB9BnkifFM/gUOPLYPnNtc8yqIfk3tQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=bhO+sNYu; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1711465240; a=rsa-sha256; cv=none; b=ZzGFKBc3URs5+RC9S0CT3Vp/8ad3sf1EmZigp6v1f04ofjHPbereZt5avw8I7WjKvlJ9Ym ImeGTIEwqPW5pfEVaztKoDzu9WI+o6OvDphPZFe03SjEIVfA7M1jNS/Hkn2nwd5pQ6VIIY IxSZz7e80R7oUasEkIjeHNYzYf3/kC3uXgXHu7kwpCG6+fcewHs5mlYj72M+Ybc+bgqQeF V1z0URgHjsMvOWqm1nyE8pkK2VuXRQ0WAdqoWc1Jns45t1UTqZd0l5OViwL8Scp/OlhZCH S9NMNrCwqL+Diqb2bIA9SxxHhaoegH295L0xvioB6MAu+3G7MT3T42WtpkUzzg== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 3C66B7585D for ; Tue, 26 Mar 2024 16:00:40 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rp8H3-0001XJ-8X; Tue, 26 Mar 2024 10:59:37 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rp8H1-0001Wv-02 for emacs-orgmode@gnu.org; Tue, 26 Mar 2024 10:59:35 -0400 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rp8Gy-0007Sh-GN for emacs-orgmode@gnu.org; Tue, 26 Mar 2024 10:59:34 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 56098240028 for ; Tue, 26 Mar 2024 15:59:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1711465170; bh=A7MOgxRGvdKtQ7gnrdnXhHwlrEBRQwxL1kxFYn+FOWU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=bhO+sNYuHgCvlnUbCAMWjQKmyICf2/41iAtbWD9tds+u1NonVJ0eCeiK4b/JRhLnu AY9pELmZ+1SOWVA2kAdRvVa1y9pDnL2g4vTvfZkl2cHOwmn+k5JsbmJm9bCO7T2VkV RFnZ6Dauk/6MDOMzbEVvWEXiTHL0wve3SyB5adnWoj5GNd9zHCurizqcwo5CE2llGT QCgYfTIjnmw68jCH7AMG24DueK1TwEooG405BSl0zXZ/eCsqisoZN4QV3P5cddykhd k582V05LQJAtP1rT++tvPpRwDOncJoxVYTKW3NHPFN0+W/tInxklIRuuXXB8QyJRas c9KtTV5gk291w== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4V3tHj2TGkz6tw6; Tue, 26 Mar 2024 15:59:28 +0100 (CET) From: Ihor Radchenko To: Adam Porter Cc: emacs-orgmode@gnu.org, Bastien Subject: Re: [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements In-Reply-To: <04359940-f84f-428a-9e6c-31c16d234439@alphapapa.net> References: <87o7b3bye3.fsf@localhost> <04359940-f84f-428a-9e6c-31c16d234439@alphapapa.net> Date: Tue, 26 Mar 2024 14:59:36 +0000 Message-ID: <87il199gyv.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Queue-Id: 3C66B7585D X-Spam-Score: -8.04 X-Migadu-Spam-Score: -8.04 X-Migadu-Scanner: mx11.migadu.com X-TUID: IsfHjVvURz0x Adam Porter writes: > ... >> According to >> https://www.gnu.org/prep/maintain/maintain.html#Copyright-Papers: >> ... >> We must use a specific form from a specific URL. > > That isn't how the Emacs maintainers handle it. They send a form by=20 > email when asked, or direct users to use the one in the Emacs git repo.=20 > AFAICT, they are equivalent, if not identical. > > Regardless, it would be nice to have a canonical answer to this. The=20 > gnu.org site says one thing, the emacs.git repo says another,=20 > org-mode.git says another, the people on the mailing say another, and=20 > Worg says another--all slightly different for no apparent reason.=20 > (There's also the Emacs manual, which probably mentions it too.) AFAIU, gnu.org is the source of truth for us, as a GNU project. Bastien, any comments? Maybe we should ask gnu-advisory@gnu.org? >> Also, about the changes to the FSF form that Stefan mentioned in >> https://yhetil.org/emacs-devel/jwvh6hne6nv.fsf-monnier+emacs@gnu.org/ >> It does not look like they are official yet. See >> https://lists.gnu.org/archive/html/bug-gnulib/2024-03/msg00060.html > > AFAICT the only change is the line that asks the FSF to send additional=20 > confirmation to some other interested parties. Does that need to be=20 > officially official in order to use it? The alternative is having the=20 > contributor ask by writing in the email message, which seems equivalent.= =20 > IOW, it doesn't change the form, it just adds an extra request. Yes, it has to be, if we stick to what gnu.org says: ... Please don=E2=80=99t use any of the templates except for those listed here, and please don=E2=80=99t cha= nge the wording. (I personally also do prefer the changed wording, but we are not discussing personal preferences here; it is a legal dimension) >>> +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: =3Dcopyright-clerk AT fsf DOT org=3D. In rare cases, an inquiry f= rom an >>> +Org maintainer gets the process moving again. >>=20 >> I may be missing something, but the last sentence now reads like our >> (Org maintainer's) inquiry rarely works. >>=20 >> The previous version is very different, IMHO: >>=20 >>> -Emails from the paper submitter have been ignored in the past, but an >>> -email from the maintainers of Org mode has usually fixed such cases >>> -within a few days. > > I would have preferred to omit all the language about the process=20 > sometimes not going quickly or smoothly; it doesn't seem necessary or=20 > helpful to publish such words, because they seem accusatory toward the=20 > FSF volunteers. 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 =3Dcopyright-clerk AT fsf DOT org=3D. Historically, FSF replies to the maintainer request within a few days. --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at