From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Thibaut Verron Newsgroups: gmane.emacs.devel Subject: Re: Proposal for an Emacs User Survey Date: Mon, 19 Oct 2020 18:42:48 +0200 Message-ID: References: <4a1188f8-9864-54c0-ae6f-5f32102d9757@gmx.com> <20201011073553.GA6784@odonien.localdomain> <20201011120840.GC2923@protected.rcdrun.com> <20201011125031.GC6784@odonien.localdomain> <20201012050418.GZ2923@protected.rcdrun.com> <20201013052736.GE31408@protected.rcdrun.com> <20201016130235.06218dae@argon> <87eelvplvh.fsf@posteo.net> <10bdf4ea-e365-cc3d-ec03-4348946fadbe@yandex.ru> Reply-To: thibaut.verron@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29382"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "Philip K." , Richard Stallman , Jean Louis , Marcel Ventosa , emacs-devel , Dmitry Gutov To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 19 18:45:47 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 1kUYI6-0007Ue-7t for ged-emacs-devel@m.gmane-mx.org; Mon, 19 Oct 2020 18:45:46 +0200 Original-Received: from localhost ([::1]:59246 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kUYI5-0002f5-1m for ged-emacs-devel@m.gmane-mx.org; Mon, 19 Oct 2020 12:45:45 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35662) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kUYFU-0000W4-3T for emacs-devel@gnu.org; Mon, 19 Oct 2020 12:43:04 -0400 Original-Received: from mail-yb1-xb2a.google.com ([2607:f8b0:4864:20::b2a]:43411) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kUYFR-000738-JM; Mon, 19 Oct 2020 12:43:02 -0400 Original-Received: by mail-yb1-xb2a.google.com with SMTP id d15so62365ybl.10; Mon, 19 Oct 2020 09:43:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=d2RgPqp0XOFfacNrU4Fx1YrhNO8EAzZ9tfLzn+oPlbM=; b=TbtmK1jNC1mKFYjPhaMuEoU37/Wic4/+nWk3IlYdQ5NBcnrRrSkPXf31RXO5KSWijN 0oEVCddLkSl+MNGb1PNFoYsxgGTywJe3gbJskT+02OpEKyPOIF1Zlh6+UGSrSKrees15 xtmcDCPGb/ghGNQs+jE000mSThYh09t+Q6eIokqxb667Pun8OAJfVu5OtlOSOGCO1dvD aAqE5oCbWDUr9sVD4Qj/BhyU9QoMYczYMSn8rrqyqtxefFNhytKkAdJQxDQAAMzwNFeb C7YXwKtPGVNcnGJrxVY8g6KWjW5KCXj3m8Q3ujxiVaA7e6ZRnX4yejLcMoVQ7JF1QSei Qsdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=d2RgPqp0XOFfacNrU4Fx1YrhNO8EAzZ9tfLzn+oPlbM=; b=i0EHA0CmF+QFzeOv6oKxGqv13ga4HElpAlhyVRCMizqJrmptatXqo/MjrHGmIGKUK3 nBaimnKlZiPglMUVHeSExk2QKaL3CJzerB4iOXXcsKuwEr2ReKdsbGQpd7JuYHg5xvzf 8TaAsGZI9wHJHx8RjY7560fU4wtutPPpvBW5JtMe7U6DsfTw6U5LAw+E2FqbmX4ojuAS R/+d4XRyPJ5xtpxF5v3ETdcPwx574OTBv9KeEi4YnfP+u+k6PXsJTaVIyZvx4GbvHsaw P7xunD3rSDxaRJRlA0HJ0eBsVSahd8Ne6nRxiDbBzCrMcmwpqS7hL4Ugx92awrYfOcZ3 637g== X-Gm-Message-State: AOAM532C7y0UifP+NzMEpeq9p2CHnYsAJsu/kucf3KSfTL/A7mb2H5+p fTiv9t28BFKzKGf9ZcdSfDi75DgbQyyayByTwaVY0sJ8 X-Google-Smtp-Source: ABdhPJyiojmnQVXxGQkvndHpVA5UOyxjROd+x6Xx7r9qqMZG0tXGET+lM7GoLfMzX2CKpxhPu9Tahba6EvkQjoCiKv0= X-Received: by 2002:a25:bcc9:: with SMTP id l9mr113935ybm.183.1603125779923; Mon, 19 Oct 2020 09:42:59 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=2607:f8b0:4864:20::b2a; envelope-from=thibaut.verron@gmail.com; helo=mail-yb1-xb2a.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_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no 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:258132 Archived-At: Le lun. 19 oct. 2020 =C3=A0 17:48, Drew Adams a =C3= =A9crit : > > > MELPA to a large part consists of a database of "recipes", one for each > > package that it builds and distributes. This tag can be put inside > > recipes, and thus be controlled by MELPA maintainers, and not by the > > packages authors themselves. > > > > If we provide some well-defined criteria for such tags, and pick a > > neutral-enough name, I don't see why the MELPA maintainers (who are > > quite reasonable people IME) wouldn't go for it. > > Just a minor comment/question about this, which > I think would be the first time such a thing > would be happening: > > Do we really want to set a precedent that > someone other than the code author fiddles with > their code, adding comments or whatever? > > Sure, the maintainers of a repo are, in a way, > administrators. But should such administrators > be changing source code? Adding other code or > whatever, to administer, label, treat, etc. the > code is, at least conceptually, different from > changing the source code itself. > > No, adding a field/tag in a comment is not a big > deal. And yes, GPL code is open to modification. > > Still, is this a good door to open? I'm not sure to understand the question. The recipes are stored in the Melpa repository, so the maintainers of the repo are really the maintainers of the source code (the recipes). The recipes are written by the authors of the package, by forking and filing a request to merge into the Melpa repository. So if the administrators of Melpa agree to it, they are entirely in their prerogative to alter the recipes provided by the users in their code (list of recipes). It's not really different from adding a comment to clarify a bug fix by an external contributor after the code is merged. They would not be modifying the code of the packages themselves, of course.