From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 2C93AAF3 for ; Mon, 13 Jul 2015 19:18:41 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A5C997C for ; Mon, 13 Jul 2015 19:18:39 +0000 (UTC) From: Peter =?utf-8?q?H=C3=BCwe?= To: Alexey Dobriyan Date: Mon, 13 Jul 2015 21:20:32 +0200 References: <201507130038.01474.PeterHuewe@gmx.de> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201507132120.33180.PeterHuewe@gmx.de> Cc: Dan Carpenter , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [CORE-TOPIC] Documentation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Am Montag, 13. Juli 2015, 11:47:23 schrieb Alexey Dobriyan: > On Mon, Jul 13, 2015 at 1:38 AM, Peter H=C3=BCwe wrot= e: > > as we talked about recruiting in the other thread I realized that one > > thing that might reduce the entrance barrier a bit (apart from tooling > > and flow) would be proper documentation. >=20 > Newbies should not write documentation because they, by definition, > have little knowledge of the code. It will lead to many, many useless > and redundant comments like below whose only purpose is stealing > vertical whitespace: While I agree with your 'stupid documentation is stupid' argument, I tend t= o=20 somewhat disagree about that newbies should not write documentation. By newbies I do not mean someone new to programming - that of course makes = no=20 sense - but why shouldn't a experienced c-programmer who is currently figur= ing=20 out how the kernel works not document stuff along the way? I think that's much better than fixing whitespaces and long lines. Peter