From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Trunk still not open Date: Mon, 17 Mar 2014 13:43:55 +0900 Message-ID: <87bnx5l9is.fsf@uwakimon.sk.tsukuba.ac.jp> References: <6xwqfxhl88.fsf@fencepost.gnu.org> <83txb1mcsy.fsf@gnu.org> <87siqlku0i.fsf@uwakimon.sk.tsukuba.ac.jp> <87wqfxari2.fsf@yandex.ru> <87ha70kyy3.fsf@uwakimon.sk.tsukuba.ac.jp> <5323B66B.5070405@yandex.ru> <837g7vdg70.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1395031585 17444 80.91.229.3 (17 Mar 2014 04:46:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Mar 2014 04:46:25 +0000 (UTC) Cc: Eli Zaretskii , Dmitry Gutov , Emacs developers To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 17 05:46:34 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 1WPPRZ-0003a4-Ey for ged-emacs-devel@m.gmane.org; Mon, 17 Mar 2014 05:46:33 +0100 Original-Received: from localhost ([::1]:55580 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPPRZ-0004Zu-32 for ged-emacs-devel@m.gmane.org; Mon, 17 Mar 2014 00:46:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58395) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPPRP-0004Zi-JT for emacs-devel@gnu.org; Mon, 17 Mar 2014 00:46:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPPRI-0003ep-Ae for emacs-devel@gnu.org; Mon, 17 Mar 2014 00:46:23 -0400 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:46568) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPPRA-0003C5-Fp; Mon, 17 Mar 2014 00:46:08 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 5F104970863; Mon, 17 Mar 2014 13:43:55 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 4D9D51A28DC; Mon, 17 Mar 2014 13:43:55 +0900 (JST) In-Reply-To: X-Mailer: VM undefined under 21.5 (beta34) "kale" 2a0f42961ed4 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 130.158.97.224 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:170430 Archived-At: Juanma Barranquero writes: > That's why I'm unimpressed by the idea of forcing changes to include > docs. Not everyone is able to write Emacs-manual-quality docs, and Many projects have proved that to be false. I can cite Python; Eli has cited gdb. It very rare that a person who can code is incapable of writing docs to an acceptable level of quality. It is of course common that they have had little practice at it. So give them some practice, review their work, and teach them. :-) > specially, not everyone is so fluent in English to write good > English docs; some of us struggle with it. This is certainly true, and those same projects show how to deal with it: if the docs are obviously missing content, reject the patch and iterate; if the docs are uninterpretable, ask questions to help the contributor revise; if the docs are interpretable having reviewed the code part of the patch, fix them and apply.