From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: New maintainer Date: Sat, 03 Oct 2015 12:19:57 -0700 Organization: New Artisans LLC Message-ID: References: <5610207A.2000300@harpegolden.net> <83fv1r3gzp.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1443900413 5329 80.91.229.3 (3 Oct 2015 19:26:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 3 Oct 2015 19:26:53 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 03 21:26:48 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 1ZiSSE-0000xa-H7 for ged-emacs-devel@m.gmane.org; Sat, 03 Oct 2015 21:26:46 +0200 Original-Received: from localhost ([::1]:39766 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZiSSD-0002jo-ET for ged-emacs-devel@m.gmane.org; Sat, 03 Oct 2015 15:26:45 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZiSS9-0002jd-8k for emacs-devel@gnu.org; Sat, 03 Oct 2015 15:26:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZiSS4-0005AD-Ag for emacs-devel@gnu.org; Sat, 03 Oct 2015 15:26:41 -0400 Original-Received: from mail-pa0-x22e.google.com ([2607:f8b0:400e:c03::22e]:35485) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZiSS4-0005A9-4K for emacs-devel@gnu.org; Sat, 03 Oct 2015 15:26:36 -0400 Original-Received: by pacfv12 with SMTP id fv12so139368249pac.2 for ; Sat, 03 Oct 2015 12:26:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:subject:in-reply-to:date:organization:message-id :references:user-agent:mail-followup-to:mime-version:content-type; bh=AgAdNCC6jX2wa1QUKaO/45MnH+8+ofss8wrTS+FgZgk=; b=PnXLuM1NGAI3gl7CXJOGGSN2zMpxJ51mGG4lrOxt+k1rm6lsQEmxKMd2nYoOCQZtmW QZMpGkB4lBu8nu8oy62+YlGXO6/hs0LtOF22O1Z0NfSqddYiJ2Ao/0qm7IaPN6eipwVY cwmVh9LmQYLJV6hKDAIWcSn5Ch2oP6u3H5JtZ2qmgXPw3Jxm4EunJGtwcH56nKg/Kyld 0znvVO5XTmAV+uOpI6Iv9PBcWKtEW9Lo3SVdB3367/am2ncyuYHNkUoVOE0wXzUhdzp2 qy8ArZuZKYDPm2TE4lAv6Y+FWHC7KVRkWfeLWa6VPD+CG+vzc6zX0Mq/WeeICmVuN5xn jUTg== X-Received: by 10.68.65.104 with SMTP id w8mr28671305pbs.48.1443900395657; Sat, 03 Oct 2015 12:26:35 -0700 (PDT) Original-Received: from Vulcan.local (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id pq4sm6790897pbc.53.2015.10.03.12.26.34 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 03 Oct 2015 12:26:34 -0700 (PDT) Original-Received: by Vulcan.local (Postfix, from userid 501) id E802AF029AAF; Sat, 3 Oct 2015 12:26:33 -0700 (PDT) In-Reply-To: <83fv1r3gzp.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 03 Oct 2015 22:10:50 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Mail-Followup-To: emacs-devel@gnu.org X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22e 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:190815 Archived-At: >>>>> Eli Zaretskii writes: > How would such an arrangement differ from having just that head as a single > maintainer? What can the co-maintainer do that the rest of us cannot? The co-maintainer is usually given full maintainership over pieces of the puzzle he (or she) has expertise with, until such time that the head maintainer feels a unified direction is no longer being pursued. If there is commonality of thought between them, they typically act in concert and most people wouldn't realize that one of them has final decision. Ensuring that one person sets the tone and vision for progress ensures that things are never paralyzed by in-fighting or disagreement. If the co-maintainer has issues with the maintainer, he resigns; if the maintainer has issues with the co-maintainer, he asks him to step down. John