All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Documentation problems
Date: Sun, 27 Nov 2011 18:56:01 +0000	[thread overview]
Message-ID: <1414964.lPpRFmgCOe@helios> (raw)
In-Reply-To: <1322419119.7998.43.camel@mattotaupa>

On Sunday 27 November 2011 19:38:39 Paul Menzel wrote:
> Only Koen brought up the idea of the pull model. By itself, ikiwiki also
> allows Web edits [1].

Yes but what benefit do we get by changing the system? Only that the backend 
changes to git? Given that MediaWiki is familiar to many (thanks to Wikipedia) 
I would be hesitant to replace it with anything less widely understood.

> Additionally, you have not addressed the point that reality shows, that
> not a lot of people write documentation and use it. The best way to
> “enforce” this is to add documentation with the corresponding change.

I'm not sure I understand what you mean here. If you're suggesting that we 
will be able to force people to write changes for the documentation together 
with their changes to the code, I think there are two problems with this: 
  (1) it assumes that we already have complete documentation for the current 
state of the code;
  (2) given that writing meaningful commit messages is a challenge for many 
contributors, you're going to have a very difficult time getting people to write 
documentation for their changes as well.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-11-27 19:02 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 [this message]
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
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=1414964.lPpRFmgCOe@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.