From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jambunathan K Newsgroups: gmane.emacs.devel Subject: Re: Trunk still not open Date: Sat, 15 Mar 2014 14:43:02 +0530 Message-ID: <87ha6z4yg1.fsf@gmail.com> References: <6xwqfxhl88.fsf@fencepost.gnu.org> <83txb1mcsy.fsf@gnu.org> <87siqlku0i.fsf@uwakimon.sk.tsukuba.ac.jp> <20140314114201.GA13025@thyrsus.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1394874801 11207 80.91.229.3 (15 Mar 2014 09:13:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 15 Mar 2014 09:13:21 +0000 (UTC) Cc: "Stephen J. Turnbull" , emacs-devel@gnu.org To: "Eric S. Raymond" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Mar 15 10:13:29 2014 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 1WOkei-0000i6-VO for ged-emacs-devel@m.gmane.org; Sat, 15 Mar 2014 10:13:25 +0100 Original-Received: from localhost ([::1]:49261 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOkei-0006RU-Eb for ged-emacs-devel@m.gmane.org; Sat, 15 Mar 2014 05:13:24 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46278) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOkeZ-0006OM-0i for emacs-devel@gnu.org; Sat, 15 Mar 2014 05:13:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WOkeS-0007s6-Rq for emacs-devel@gnu.org; Sat, 15 Mar 2014 05:13:14 -0400 Original-Received: from mail-pa0-x234.google.com ([2607:f8b0:400e:c03::234]:50362) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOkeS-0007rz-JU for emacs-devel@gnu.org; Sat, 15 Mar 2014 05:13:08 -0400 Original-Received: by mail-pa0-f52.google.com with SMTP id rd3so3654431pab.25 for ; Sat, 15 Mar 2014 02:13:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=9QHRklALcMj6nA+YLx4JqxzGE5HQPuyIKOcOINWq4Bo=; b=YI0XxVRsRnzS/4CxCHzhmGDvyBwf55ypqXeVHsGQDxixnEBIverR7TcWy3LCEb6X6G pEaVoIxpGMJ3SeEx6Wxw+SdKnippBG2QtWes1tfp3pRXvQPOWDm/bCb3XPXAntUCq3bk HSkhHJ3v+Mrl68EgllUSeM35kGuDjeJIyRNPyuIAkVnbrzzztnNJZ6u8HG5SUIIKCF+X 3o57Y5JqM+7D47SpERR4oZ/daneSXRRefmqgiEQon4IPz+SteuuRvOq86BysGLJVfg2U np8CNS49jwQ/863re51U/+kcgEVR5iDMvzdoWMGSjahpAAG7TjVZsghVh7zQCdIaLj8T aiUg== X-Received: by 10.66.155.102 with SMTP id vv6mr13913778pab.89.1394874787259; Sat, 15 Mar 2014 02:13:07 -0700 (PDT) Original-Received: from debian-6.05 ([115.242.195.178]) by mx.google.com with ESMTPSA id pe3sm24096667pbc.23.2014.03.15.02.13.04 for (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Sat, 15 Mar 2014 02:13:06 -0700 (PDT) In-Reply-To: <20140314114201.GA13025@thyrsus.com> (Eric S. Raymond's message of "Fri, 14 Mar 2014 07:42:02 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::234 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:170385 Archived-At: "Eric S. Raymond" writes: > +1 for a no-push without documentation policy. Any policy should cater to the lowest commond denominator. A lowest common denominator would be 1. No release without documentation. 2. The original developer writes the documentation. Trying to "synchornize" documentation and code is a stringent requirement either in terms of the developer's preferred disposition or the specific task at hand. ---------------------------------------------------------------- It is prudent to delay the documentation 1. When some code or feature churn is expected. One the developer of the code intimately what compromises he has made for a particularl commit. 2. To put oneself in the right set of mood or context to surgically approach the task at hand. Speaking from my own experience, the info documentation comes out best when I have sufficiently distanced away from the feature in first place (to the point of even forgetting about it). 3. To make good of what one already has in the plate in terms of showing it to others, encouraging others to comment on it or to test the changes against real-life. 4. To "spread" the effort over a period of time. One cannot overlook (4) particularly when volunteer effort is involved.