From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Documentation problems
Date: Mon, 28 Nov 2011 13:40:31 +0000 [thread overview]
Message-ID: <1724253.zzXo0bHLbE@helios> (raw)
In-Reply-To: <CA+M6bXnQN9Q62w22sjiVaqkdipaXPgujR_FTWPE8N24z=MAW4A@mail.gmail.com>
On Sunday 27 November 2011 22:11:00 Tom Rini wrote:
> The number one thing we lack today is people willing to document.
> Everyone, myself included, who has said we need X done to the public
> documentation today, has generally found a point at which they stop
> wanting to keep things up to date. Why? What would change that?
> Does anyone reading this know people that _like_ editing wikis? Can
> we ask them what keeps them engaged in the process?
FWIW I do like editing wikis - certainly more than I like editing things
written in DocBook at least.
It's true our wiki contains a *lot* of outdated or incomplete information. We
could do a lot just by marking pages as out-of-date or irrelevant (via
categories?) and then updating or deleting them assuming people agree. I'm
happy to start working on this assuming we aren't going to throw the whole
thing out.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-28 13:47 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 [this message]
2011-11-28 14:40 ` Samuel Stirtzel
2011-11-28 10:30 ` Phil Blundell
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=1724253.zzXo0bHLbE@helios \
--to=paul.eggleton@linux.intel.com \
--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.