From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Documentation problems
Date: Sun, 27 Nov 2011 17:06:16 +0000 [thread overview]
Message-ID: <15202278.8Gdc2a6et6@helios> (raw)
In-Reply-To: <CACW_hTay+0OU8PcgSJnELiDpDWTT_CeP-ahKf6HCxwtgydG97Q@mail.gmail.com>
On Sunday 27 November 2011 17:58:00 Frans Meulenbroeks wrote:
> What is the problem with being it a wiki (probably with authorized users to
> avoid spam).
>
> I'd say let everyone who wants to contribute.
> If someone makes a mistake it can easily be corrected and/or reverted, and
> if someone messes things up on purpose and/or creates more bad than good
> such a (non)contributor can be banned.
>
> Disadvantage of a pull model is:
> - more difficult to make changes (e.g. if I see a typo in a wiki and I have
> write permission, I'll fix it; however if it invokes checking out a file,
> make the edit, commit it, mail a pull request, most likely I'll decide it
> is not worth the effort
> - more administrative workload (that is probably better spent on actually
> doing things).
> - It sends out a message of distrust. Not really a good way to create
> involvement.
>
> One might feel that it improves quality; then again also in a wiki one can
> review and improve (or revert) changes.
>
> As far as I see it we are all adults (at least I think so) all interested
> in improving OE so no unnecessary barriers should be raised.
>
> Frans.
>
> PS: it is quite possible to backup a wiki (and I hope this is done at
> regular intervals with our wiki). Also all edits are recorded so they can
> always be tracked back and (if needed) undone.
I agree with all of this. We shouldn't be putting more barriers up to
contributing to the documentation - there are already enough.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-27 17:12 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 [this message]
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
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=15202278.8Gdc2a6et6@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.