From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?UTF-8?Q?Cl=c3=a9ment_Pit-Claudel?= 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 11:16:50 -0400 Message-ID: <5ce9a86b-5b06-fa32-d672-c4fdaaf2b63d@gmail.com> 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> 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="69389"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 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: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 13 17:17:53 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 1jYt8q-000Hvf-WF for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 17:17:53 +0200 Original-Received: from localhost ([::1]:40790 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYt8p-0005mC-T3 for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 11:17:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34948) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYt7u-0004Jf-G5 for emacs-devel@gnu.org; Wed, 13 May 2020 11:16:54 -0400 Original-Received: from mail-qt1-x82a.google.com ([2607:f8b0:4864:20::82a]:44197) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jYt7t-0006YL-HP; Wed, 13 May 2020 11:16:54 -0400 Original-Received: by mail-qt1-x82a.google.com with SMTP id r8so60567qtm.11; Wed, 13 May 2020 08:16:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=k8FKzgP18rMYh87CnUi9NHHIr35uNbrGwGhzG9i50Jk=; b=AYQtKpSxMHodVouhrkOXteeYF7Tip6XKFZerRGAphwM2o2wAOPvtPEG25XzUCOD9qn gBGScX/Q8DK8y9z86JHDZjEN9Mup5haWis+Jj9TlyX1CFRSiewJCfGl5mgPSvipPP1ey /OicIQCMC/urVTRTlMPLb0BXi3i4QR/z2ojB1Jnrzym/uNlgAc/SQDVKjW0j5lZa29ij 8thZFw6WgsJLx9+NhjIrxz65g0fC09IzVPFhqzpjf/62wdHYGWWAj4Bdna7vek78pSdJ eWix/aHo5ND28G1Yn9F8Wu1f8MEuzqBbVvfNpYYEuv+oVEcyS4I6RI9b2CVn9bR2nHIz NtXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=k8FKzgP18rMYh87CnUi9NHHIr35uNbrGwGhzG9i50Jk=; b=nIgOdWpy54IvcDCRw474pqOSmlJlkxDuCgm9Bte3VNeStz1nnI25iX0ek/hReS6G7f e/e7BUP+2kTI+a/lqmn+K7VI6IVT1K9sj2cXg2+rY0lk7bwshDs7oFDVwubLBmqArDsl 47FfNWyLpUVyL9xqh8d8W5FN6+Ncja9ddY25vUoVWHq/uj6mHeUQdGI24zfBzaYfupNc 7X2FUjiPiVJ6LcQ/QAPbzb5KYU4lQKmYV/t6i/MrcS/7l6HuDXzcU5w3JzhDw7vIU0eE zM7ZdGN9oxCvC94fsl8qAjbOnLFn8NUUObo9sDv4f/B42lz+SCsw83NwOWmJNoiSNOYw L3Ew== X-Gm-Message-State: AOAM531TcAfbTgLnRJ7qq4JJGNCM6S4gEaCAAFRbpbs4pDM0DpSYdolh CtlB5EWTyGKvMpDmHaEbU4s= X-Google-Smtp-Source: ABdhPJyFTqDilpXwNRjXYcF2S16oklLlpEj9hz0CWXpzJwGuX7jd0ewWYYsdmQTrGXua9j5j6Lf+LA== X-Received: by 2002:ac8:2a55:: with SMTP id l21mr582174qtl.151.1589383012007; Wed, 13 May 2020 08:16:52 -0700 (PDT) Original-Received: from ?IPv6:2601:184:4180:66e7:4d17:b25e:8d9:2188? ([2601:184:4180:66e7:4d17:b25e:8d9:2188]) by smtp.googlemail.com with ESMTPSA id 19sm86867qks.8.2020.05.13.08.16.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 May 2020 08:16:51 -0700 (PDT) In-Reply-To: <83blmr7ucg.fsf@gnu.org> Content-Language: en-GB Received-SPF: pass client-ip=2607:f8b0:4864:20::82a; envelope-from=cpitclaudel@gmail.com; helo=mail-qt1-x82a.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action 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:250138 Archived-At: On 13/05/2020 11.00, Eli Zaretskii wrote: >> 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 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 :) > 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.