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? Date: Wed, 13 May 2020 18:00:47 +0300 Message-ID: <83blmr7ucg.fsf@gnu.org> References: <9mmFgzvrBwjt_n_VJyaJdXINraNi5HsGpwq-0MLeKiJA7kG2BQA4uywrzjyz7lpRS0OZDpjEi8lspOKYUA7P_QsODsDew_8nbH960G55fmY=@protonmail.com> <87d07xamrg.fsf@ericabrahamsen.net> <878silajdl.fsf@ericabrahamsen.net> <87tv18pyh4.fsf@russet.org.uk> <83blmu9u57.fsf@gnu.org> <7c61a272-f4ba-fdfd-755b-1a720e8cc2df@gmail.com> <838shy9srs.fsf@gnu.org> <7f820b59-ebbc-18c7-9f08-104a7ba88dd2@gmail.com> <834kslao2y.fsf@gnu.org> <052569f9-0571-6471-7a27-f3d7b36497a0@gmail.com> <83sgg58ari.fsf@gnu.org> <837dxh847w.fsf@gnu.org> <834ksl833q.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="7484"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, rms@gnu.org, eric@ericabrahamsen.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca, phillip.lord@russet.org.uk, ndame@protonmail.com To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 13 17:04:23 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 1jYsvn-0001rE-6o for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 17:04:23 +0200 Original-Received: from localhost ([::1]:38908 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYsvm-0008NT-77 for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 11:04:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60700) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYsst-0005c8-JG for emacs-devel@gnu.org; Wed, 13 May 2020 11:01:24 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38891) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYssr-0002eO-JB; Wed, 13 May 2020 11:01:21 -0400 Original-Received: from [176.228.60.248] (port=4420 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jYssb-0000AN-Co; Wed, 13 May 2020 11:01:06 -0400 In-Reply-To: (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Wed, 13 May 2020 00:22:56 -0400) 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:250135 Archived-At: > Cc: eliz@gnu.org, casouri@gmail.com, eric@ericabrahamsen.net, > emacs-devel@gnu.org, monnier@iro.umontreal.ca, ndame@protonmail.com, > phillip.lord@russet.org.uk > From: Clément Pit-Claudel > Date: Wed, 13 May 2020 00:22:56 -0400 > > Maybe we can publicize a part of the list which would not violate privacy? When I signed my copyright papers, I answered yes to a question that said "Would it be acceptable for us to publicize your contribution by microblogging that you are contributing, and listing your name in our monthly newsletter?". I think it is safe to assume that those who answered yes to this question do not object to appearing on a public list; correct? If you suggest making public a part of the entries in the list, then this would be worse than not publishing it at all, I think. If you suggest publishing part of the _data_ in each entry, then this should work in principle, but (a) "Someone" needs to do the work of setting this up, and (b) even in this case there might be issues which need to be resolved. For example, some people need to submit disclaimers from their employers, in addition to their personal assignment, but publishing that part discloses their employment, which may be invading their privacy. Others have other private arrangements mentioned, or are minors who need their parents' permissions, etc. Deciding which of this is necessary to make sure a person's assignment is in order, while at the same time avoiding disclosure of private information is the hard part of the job. At least AFAIU, that is.