From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from astoria.ccjclearline.com ([64.235.106.9]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1WkD8P-0002Vg-7J for barebox@lists.infradead.org; Tue, 13 May 2014 13:52:46 +0000 Date: Tue, 13 May 2014 09:50:03 -0400 (EDT) From: "Robert P. J. Day" In-Reply-To: <20140513134228.GQ5858@pengutronix.de> Message-ID: References: <20140513134228.GQ5858@pengutronix.de> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: barebox Documentation To: Sascha Hauer Cc: barebox@lists.infradead.org On Tue, 13 May 2014, Sascha Hauer wrote: > Hi, > > As we all know the barebox documentation sucks. We @Pengutronix will > have our internal techweek next month. One of the goals will be to > improve the documentation situation for barebox. > > What are your opinions in which form the documentation should be? > > We currently have plain text files under Documentation/, a wiki on > http://wiki.barebox.org/doku.php and doxygen. None of the documentation > sets is complete and all are outdated. as i want to introduce barebox into future embedded linux classes of mine, i have a vested interest in making sure the documentation is good. so while others argue about the proper format, i'll be happy to put my editing talents to work and do a lot of proofreading. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox