From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Why are so many great packages not trying to get included in GNU Emacs? WAS: Re: Making Emacs more friendly to newcomers Date: Fri, 24 Apr 2020 12:02:27 +0300 Message-ID: <83mu71b6jh.fsf@gnu.org> References: <863691n4xl.wl-me@enzu.ru> <87imhw431x.fsf@yahoo.com> <87mu78huhx.fsf_-_@yahoo.com> <87k12bdgx7.fsf@yahoo.com> <87r1wi7a8o.fsf@yahoo.com> <875zdteybt.fsf@runbox.com> <87368wrvf5.fsf@yahoo.com> <86k126d83n.wl-me@enzu.ru> <83pnbyckvv.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="44070"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Apr 24 11:03:16 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jRuEu-000BMJ-GN for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Apr 2020 11:03:16 +0200 Original-Received: from localhost ([::1]:55982 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jRuEt-0004zP-Kb for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Apr 2020 05:03:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46164) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jRuEN-0004Ra-3W for emacs-devel@gnu.org; Fri, 24 Apr 2020 05:02:43 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39159) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jRuEL-0003eY-LZ; Fri, 24 Apr 2020 05:02:41 -0400 Original-Received: from [176.228.60.248] (port=3965 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jRuEL-0003u7-0M; Fri, 24 Apr 2020 05:02:41 -0400 In-Reply-To: (message from Jean-Christophe Helary on Fri, 24 Apr 2020 08:45:43 +0900) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:247675 Archived-At: > From: Jean-Christophe Helary > Date: Fri, 24 Apr 2020 08:45:43 +0900 > > > - An unwillingness to assign copyright to the FSF, seemingly often more due to > > inertia than any principled opposition. > > It has been mentioned a number of times already. > > I think that the process could be streamlined (and there is a need to check that with the legal team I guess). > > For one, the actually *submission* of the copyright assignment to the FSF could me made to be as easy as a simple code commit, signed with something like a gpg key or something. Commit to what repository? > Once the developer has simply "pushed that button," the contribution should be considered valid, and then eventually the developer receives a PDF signed by the FSF to confirm the assignment. The assignment form requires one to file a couple of personal details that are unlikely to be possible to be gleaned from a commit. In some situations, the assignment needs a disclaimer from the person's employer to go with it, something that again is unlikely to be triggered by any commit anywhere. I believe these aspects of the copyright assignment process are the ones that require a separate communication between humans. Of course, if it can somehow be simplified, I'm all for it.