From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: New maintainer Date: Sun, 04 Oct 2015 09:26:15 +0300 Message-ID: <838u7j2lq0.fsf@gnu.org> References: <560CCEBA.9080607@online.de> <874miapdhs.fsf@openmailbox.org> <87pp0yktyx.fsf@fencepost.gnu.org> <22029.59130.54156.957525@turnbull.sk.tsukuba.ac.jp> <87io6pnujl.fsf@red-bean.com> <874mi840si.fsf@wanadoo.es> <561034C3.2060101@cumego.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1443939998 8314 80.91.229.3 (4 Oct 2015 06:26:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 4 Oct 2015 06:26:38 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?Przemys=C5=82aw?= Wojnowski Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 04 08:26:29 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zickd-0002Gl-9C for ged-emacs-devel@m.gmane.org; Sun, 04 Oct 2015 08:26:27 +0200 Original-Received: from localhost ([::1]:41387 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zickc-0007Mx-Ht for ged-emacs-devel@m.gmane.org; Sun, 04 Oct 2015 02:26:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59807) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZickZ-0007Mp-Nt for emacs-devel@gnu.org; Sun, 04 Oct 2015 02:26:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZickW-0007GX-IQ for emacs-devel@gnu.org; Sun, 04 Oct 2015 02:26:23 -0400 Original-Received: from mtaout29.012.net.il ([80.179.55.185]:45612) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZickW-0007Fw-AU for emacs-devel@gnu.org; Sun, 04 Oct 2015 02:26:20 -0400 Original-Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0NVO00800MXF3400@mtaout29.012.net.il> for emacs-devel@gnu.org; Sun, 04 Oct 2015 09:27:13 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NVO0020BN9DM180@mtaout29.012.net.il>; Sun, 04 Oct 2015 09:27:13 +0300 (IDT) In-reply-to: <561034C3.2060101@cumego.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.185 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:190844 Archived-At: > From: Przemys=C5=82aw Wojnowski > Date: Sat, 3 Oct 2015 22:04:19 +0200 >=20 > IMHO one problem might be that, due to lack of roadmap and clear > priorities, a lot of different things are developed at the same tim= e, I don't think you can prevent that in a project as multi-faceted and multi-discipline as Emacs, nor do I think you should want to. > which springs even more topics on emacs-devel. Going through this f= lood > and deciding on them must be tiring. Selecting top 10 (X) from the > roadmap would constrain topics range and make it simpler to manage. > Also it would clarify for developers what to focus on. People work on the itches they want to scratch. I think an attempt t= o tell them what to do and what not to will be futile at best, and at worst will make some go away. > Another thing is that a maintainer doesn't have to code review ever= y > single change (search for "the cost of perfectionism"). It's enough= if > some other developer would do that. Assuming those other developers indeed do that. We have too few who do. > A developer that wrote a feature can just write tests and send an e= mail > to emacs-devel "XXX - ready for Code Review". They already do. Then they have to ping us weeks later.