All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Documentation problems
Date: Mon, 28 Nov 2011 10:30:44 +0000	[thread overview]
Message-ID: <1322476245.26081.89.camel@phil-desktop> (raw)
In-Reply-To: <CA+M6bX=PYZ+2vb32ZmT3SirqHdKpCtD90QqtHhQiWSp38f1kVA@mail.gmail.com>

On Sat, 2011-11-26 at 19:40 -0700, Tom Rini wrote:
> As things stand today, the wiki is out of date and a number of folks
> refuse to work on it.  Using things like "It's all text!" for firefox
> only go so far and don't solve problems like people just avoiding
> documentation anyhow.
> 
> Paul Menzel has mentioned that ikiwiki has been mentioned before and
> that lets us have the website in a repository.  Do folks have other
> ideas?

I guess it depends what documentation you are thinking of exactly.

Bitbake and oe-classic both have their own user manuals written in
Docbook.  I think Poky has something similar which might be more or less
directly applicable to oe-core.  If the objective is to create a high
quality user guide then I think that starting from some combination of
these (and continuing in the same format) is probably the right
approach.

It would be fairly straightforward (modulo TSC regulatory requirements)
to set up a git repository on oe.org to hold the documentation and
arrange for interested folks to have write access to it.  

p.




  parent reply	other threads:[~2011-11-28 10:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-27  2:40 Documentation problems Tom Rini
2011-11-27  9:58 ` [RFC] Documentation problems and future plans Paul Menzel
2011-11-27 15:51   ` Chris Larson
2011-11-27 14:29 ` Documentation problems Paul Eggleton
2011-11-27 15:53   ` Chris Larson
2011-11-27 16:58     ` Frans Meulenbroeks
2011-11-27 17:06       ` Paul Eggleton
2011-11-27 18:38         ` Paul Menzel
2011-11-27 18:56           ` Paul Eggleton
2011-11-27 19:06             ` Paul Menzel
2011-11-27 21:49               ` Frans Meulenbroeks
2011-11-27 22:00                 ` Paul Menzel
2011-11-27 15:44 ` Koen Kooi
2011-11-28  5:11   ` Tom Rini
2011-11-28  6:36     ` Chris Verges
2011-11-28  9:23     ` Koen Kooi
2011-11-28 12:19       ` Denis 'GNUtoo' Carikli
2011-11-28 13:40     ` Paul Eggleton
2011-11-28 14:40     ` Samuel Stirtzel
2011-11-28 10:30 ` Phil Blundell [this message]
2011-11-28 11:07   ` Richard Purdie
2011-11-28 11:16     ` Otavio Salvador
2011-11-28 13:33       ` Philip Balister
2011-11-28 13:36         ` Philip Balister
2011-11-28 14:06           ` Koen Kooi
2011-11-28 18:02     ` Bernhard Guillon
2011-11-28 21:13       ` Tom Rini
2011-11-29  8:24       ` Frans Meulenbroeks
2011-11-29 20:17         ` Khem Raj
2011-11-29 21:46           ` Frans Meulenbroeks
2011-11-29 23:37             ` Tom Rini
2011-11-30  7:06               ` Frans Meulenbroeks
2011-11-28 17:44 ` Bernhard Guillon
2011-12-07  5:01   ` Bill Traynor
2011-12-07 22:17     ` Khem Raj
2011-11-30 15:49 ` Rainer Koenig
2011-11-30 17:06   ` Koen Kooi
2011-11-30 17:32   ` McClintock Matthew-B29882
2011-11-30 18:46   ` Paul Menzel
  -- strict thread matches above, loose matches on Subject: below --
2009-09-20 17:58 Bruce Korb
2009-09-20 18:24 ` Matthieu Moy
2009-09-20 18:37   ` Bruce Korb
2009-09-20 18:45     ` Matthieu Moy
2009-09-20 20:52 ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1322476245.26081.89.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.