From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.devel Subject: Re: Why are so many great packages not trying to get included in GNU Emacs? WAS: Re: Making Emacs more friendly to newcomers Date: Wed, 17 Jun 2020 11:58:37 +0300 Message-ID: <08c69856e75bda767adcdb43bc8d3ceed6849640.camel@yandex.ru> References: <87imhw431x.fsf@yahoo.com> <87mu78huhx.fsf_-_@yahoo.com> <87k12bdgx7.fsf@yahoo.com> <87r1wi7a8o.fsf@yahoo.com> <875zdteybt.fsf@runbox.com> <87368wrvf5.fsf@yahoo.com> <86k126d83n.wl-me@enzu.ru> <83pnbyckvv.fsf@gnu.org> <4923d7e98f5ed816a7569093dbc673153adcea88.camel@yandex.ru> <87mu52tkb3.fsf@elephly.net> 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="34406"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Evolution 3.36.3 Cc: Eli Zaretskii , Stefan Kangas , emacs-devel@gnu.org To: Ricardo Wurmus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jun 17 10:59:22 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 1jlTuk-0008pj-7a for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Jun 2020 10:59:22 +0200 Original-Received: from localhost ([::1]:52172 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jlTuj-0001ap-6G for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Jun 2020 04:59:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33726) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jlTuB-00019I-QK for emacs-devel@gnu.org; Wed, 17 Jun 2020 04:58:47 -0400 Original-Received: from forward100p.mail.yandex.net ([77.88.28.100]:37394) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jlTu8-00013B-8n; Wed, 17 Jun 2020 04:58:47 -0400 Original-Received: from forward101q.mail.yandex.net (forward101q.mail.yandex.net [IPv6:2a02:6b8:c0e:4b:0:640:4012:bb98]) by forward100p.mail.yandex.net (Yandex) with ESMTP id 2B34359827C1; Wed, 17 Jun 2020 11:58:38 +0300 (MSK) Original-Received: from mxback3q.mail.yandex.net (mxback3q.mail.yandex.net [IPv6:2a02:6b8:c0e:39:0:640:4545:437c]) by forward101q.mail.yandex.net (Yandex) with ESMTP id 28378CF4000C; Wed, 17 Jun 2020 11:58:38 +0300 (MSK) Original-Received: from vla5-e763f15c6769.qloud-c.yandex.net (vla5-e763f15c6769.qloud-c.yandex.net [2a02:6b8:c18:340b:0:640:e763:f15c]) by mxback3q.mail.yandex.net (mxback/Yandex) with ESMTP id Q87qb4W9W2-wc6mHba4; Wed, 17 Jun 2020 11:58:38 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1592384318; bh=zkG5uE57FxybbD3277ifqm1/iygMBz40jlNKRsL+n5k=; h=In-Reply-To:Cc:To:From:Subject:References:Date:Message-ID; b=cWrAYE4Ze2QT/r1wakF+O0LHwOkQSW9T89JmsEQ9tUX+5DpbNRtynV/pcVHJ5AIN2 BduXBNcKS+gNNb2X9AiwSJzMnB0WP/hN7gyTbivhhRVU/Khkvl48P0pXkpFGOd/WdO e97LV8XrAtRILCFwRlZm3IK1mCmmh3Wz1GPCiOyM= Authentication-Results: mxback3q.mail.yandex.net; dkim=pass header.i=@yandex.ru Original-Received: by vla5-e763f15c6769.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id 7TNHDtVqqK-wbkOq7YH; Wed, 17 Jun 2020 11:58:37 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) In-Reply-To: <87mu52tkb3.fsf@elephly.net> Received-SPF: pass client-ip=77.88.28.100; envelope-from=hi-angel@yandex.ru; helo=forward100p.mail.yandex.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/17 04:58:38 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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:252285 Archived-At: On Wed, 2020-06-17 at 05:58 +0200, Ricardo Wurmus wrote: > Konstantin Kharlamov writes: > > > 5. As a contributor, when I stumble upon a bug I could fix in > > software, first thing I usually do is go check it is not fixed in > > latest code and that there's no pending merge/pull requests that seem > > to fix that same thing. So, for example, I want to see pending > > patchsets to python-mode, can I do that with Emacs > > "bug-patch-tracker"? No, with debbugs.gnu.org you can either find > > pending patchsets, or you can make a text search, but over everything: > > bugs, patchsets, closed or not… > > For the Guix project I wrote Mumi[1], an alternative web frontend to > Debbugs, which can be seen here: > > https://issues.guix.gnu.org > > The idea was to provide something that’s reminiscent of the Github > experience without abandoning what’s great about the mail-based > workflow. Cool, it looks very nice! > The official Debbugs web interface also allows you to filter by > submissions with patches and by status, though it may not be easily > discoverable how to do that. Oh, right, I stand corrected: the "advanced text search" has also a button called "add attribute", where you can type Bug Title → Includes String → "[PATCH]"