From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Please use the wiki
Date: Thu, 05 Feb 2009 16:14:21 +0100 [thread overview]
Message-ID: <gmevod$tbe$1@ger.gmane.org> (raw)
In-Reply-To: <69E6C70090A0A14498CC98FAE5E06B6E3CF632@hiob.intern.dresearch.de>
On 05-02-09 09:07, Sledz, Steffen wrote:
> As a developer working on OE just sometimes it is really hard to find information about all the big and little problems, hacks, tipps, and tricks. Often you have to dig through the archives of the mailing lists and frequently you overlook important things. This leads to problems by breaking unknown rules and much more mails asking the same questions again and again.
>
> With the wiki<http://wiki.openembedded.net/> there is a much better place to pool all these informations. It is easy to write and update the pages, it is possible to discuss the items, there is a version history and a full text search, it is possible to use categories, and much more.
>
> It would be really helpful if all the important information from the mailing lists and other sources could find it's way (directly or with references) to the wiki. I miss pages describing major concepts (e.g. virtual and native packages), the branch policy (e.g. how's the the stable branch made?), pages to all the main distros, machines and major packages, an overview about all the tricky things usable in the recipes, best practises, and so on.
>
> So again my call (especially to the core team): Please share your knowledge in the wiki!
Such information shouldn't be in the wiki, but in the manual:
http://cgit.openembedded.net/cgit.cgi?url=openembedded/log/&h=org.openembedded.documentation
next prev parent reply other threads:[~2009-02-05 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 8:07 Please use the wiki Sledz, Steffen
2009-02-05 15:14 ` Koen Kooi [this message]
2009-02-06 7:17 ` Sledz, Steffen
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='gmevod$tbe$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.