From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: RW for otavio
Date: Sat, 07 Jun 2008 12:18:21 +0200 [thread overview]
Message-ID: <g2dn9e$bb9$1@ger.gmane.org> (raw)
In-Reply-To: <1212789415.6840.30.camel@dax.rpnet.com>
Hi Richard
Richard Purdie wrote:
> What I'd like to see is some kind of code of conduct for developers,
> particularly new ones
Good point.
In fact, I've been thinking about how to get new devs up to speed more
quickly as well. I thought the new wiki would be a good place to have
this and so I started http://wiki.openembedded.net/index.php/New_Dev
Right now, there is nothing there yet, except a list of things to touch
on. I guess the points you and Koen raised would make good additions.
Regards
Rolf
next prev parent reply other threads:[~2008-06-07 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 22:48 RFC: RW for otavio Rolf Leggewie
2008-06-06 8:41 ` Robert Schuster
2008-06-06 10:40 ` Henning Heinold
2008-06-06 11:06 ` Marcin Juszkiewicz
2008-06-06 13:02 ` Michael 'Mickey' Lauer
2008-06-06 21:56 ` Richard Purdie
2008-06-06 23:32 ` Otavio Salvador
2008-06-07 8:55 ` Koen Kooi
2008-06-07 10:18 ` Rolf Leggewie [this message]
2008-11-11 1:13 ` Weird build failures Otavio Salvador
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='g2dn9e$bb9$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--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.