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: PL support Date: Tue, 12 May 2020 17:44:05 +0300 Message-ID: <83tv0l8b7u.fsf@gnu.org> References: <9mmFgzvrBwjt_n_VJyaJdXINraNi5HsGpwq-0MLeKiJA7kG2BQA4uywrzjyz7lpRS0OZDpjEi8lspOKYUA7P_QsODsDew_8nbH960G55fmY=@protonmail.com> <2e4e8ce9-d857-f3e3-31cf-a40dee67bd25@yandex.ru> <83y2q1dsvh.fsf@gnu.org> <2468efa6-7dbd-8634-44cc-586bb6985f49@yandex.ru> <83pnbddrfd.fsf@gnu.org> <83k11ldpxs.fsf@gnu.org> <83imh5dnun.fsf@gnu.org> <83h7wpdms7.fsf@gnu.org> <88adcf52-7310-6d48-ab31-5d427deaa89d@yandex.ru> <65bfd7bb-34e5-53ca-a7c1-dfd0d22eeb9d@yandex.ru> <2827d7f3-6827-d580-7fe5-f3c24aae0029@yandex.ru> <83mu6ebjb7.fsf@gnu.org> <1b1b1138-82da-d37f-806e-cd478ef12756@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="65839"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca, joaotavora@gmail.com To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 12 16:46:09 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 1jYWAb-000GyW-3X for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 16:46:09 +0200 Original-Received: from localhost ([::1]:60994 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYWAa-0005rq-1x for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 10:46:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58224) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYW94-0003ni-PR for emacs-devel@gnu.org; Tue, 12 May 2020 10:44:34 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42047) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYW93-00045m-Kt; Tue, 12 May 2020 10:44:33 -0400 Original-Received: from [176.228.60.248] (port=3045 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jYW8w-0000Hu-KK; Tue, 12 May 2020 10:44:26 -0400 In-Reply-To: <1b1b1138-82da-d37f-806e-cd478ef12756@yandex.ru> (message from Dmitry Gutov on Tue, 12 May 2020 02:03:58 +0300) 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:249973 Archived-At: > Cc: rms@gnu.org, joaotavora@gmail.com, monnier@iro.umontreal.ca, > emacs-devel@gnu.org > From: Dmitry Gutov > Date: Tue, 12 May 2020 02:03:58 +0300 > > On 11.05.2020 18:08, Eli Zaretskii wrote: > > >> The frequent approach in big projects is "forwarding" bug reports to > >> people responsible for respective piece of code. > > > > Most of the code in Emacs doesn't have an "owner", so this cannot work > > for us. Heck, we don't even have appointed few who'd triage every > > report quickly and efficiently (which would be one way of preventing > > too many people from reading too many email messages). > > These are the main reasons why I'm wary of adding more packages to Emacs > core without solid justification. I don't think adding a few more will cause any tangible changes. We are also regularly retire packages to lisp/obsolete/. > Having more core developers should be a plus for sure, but the extra > cognitive load for everyone else seems unavoidable either way. Of course. But adding packages also tends to add core developers, albeit slowly. > So it seems to me that the logical thing would be to try to slim it down > where feasible rather than simply keep growing. Unless we are going to move a significant fraction, it won't help. To say nothing of the fact that ELPA packages shouldn't be abandoned, they should still be maintained. And moving a package to ELPA doesn't cause someone outside of the core team to take ownership on that package, so the overall burden will not be affected. > > It is not easy to track issues for a large project such as ours, > > that's true. But let's please not represent the situation as a total > > catastrophe: debbugs does have keywords and sub-projects, and we have > > the debbugs package that allows to use those to read only those > > reports in which you are interested. Some of us do use that package. > > I suppose it would help if somebody actually used the > keywords/sub-projects to forward bugs to other people. Indeed. Any volunteers?