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 19:01:29 +0300 Message-ID: <8336837rja.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> <83blmr7ucg.fsf@gnu.org> <5ce9a86b-5b06-fa32-d672-c4fdaaf2b63d@gmail.com> 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="23174"; 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 18:05:13 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 1jYtsf-0005uj-G0 for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 18:05:13 +0200 Original-Received: from localhost ([::1]:52776 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYtse-0001qn-GK for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 12:05:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43388) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYtpb-0004Mr-Lg for emacs-devel@gnu.org; Wed, 13 May 2020 12:02:04 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:40232) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYtpa-000160-C6; Wed, 13 May 2020 12:02:02 -0400 Original-Received: from [176.228.60.248] (port=4185 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jYtpM-0004bD-Qq; Wed, 13 May 2020 12:01:54 -0400 In-Reply-To: <5ce9a86b-5b06-fa32-d672-c4fdaaf2b63d@gmail.com> (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Wed, 13 May 2020 11:16:50 -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:250144 Archived-At: > Cc: rms@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 11:16:50 -0400 > > > 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 > > I've sent an implementation ^^ I'm happy to write the code if code is needed, it's the specs that I don't know :) I meant to set this up on gnu.org machines. The hard part is to extract the data that can be published, I think (and maybe even to decide which part is that). > > 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. > > I think an API could say "yes", "no", or "check with maintainer". > We can put all tricky cases in the "check with maintainer" category. Anything's possible, but a volunteer who'd do all that is still needed. As always with Emacs (and GNU in general).