From: Darren Hart <dvhart@linux.intel.com>
To: Yury Bushmelev <jay4mail@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: RFC: newbies and janitors
Date: Wed, 30 Mar 2011 09:08:21 -0700 [thread overview]
Message-ID: <4D935575.1050501@linux.intel.com> (raw)
In-Reply-To: <BANLkTi=Nc31v4K3AcL54X4aFYLmcCMeBvw@mail.gmail.com>
On 03/28/2011 04:29 PM, Yury Bushmelev wrote:
> 2011/3/28 Darren Hart<dvhart@linux.intel.com>:
>> The Yocto Project is a complex thing, and people eager to get involved can
>> have a difficult time sorting out where to start. The Linux kernel community
>> put together kernelnewbies and kerneljanitors to help people get up to speed
>> and provide them with manageable tasks to get them started.
>>
>> I think we have (or should have) the "newbies" side of things covered with
>> #yocto #poky and the website and the various manuals and documentation
>> projects, but I think something like "janitors" would be valuable. This
>> could be something as simple as a tag for bugzilla bugs appropriate for
>> newcomers go after.
>>
>> I imagine this is something we could share with OE - or perhaps OE already
>> has something that serves this purpose - or could be extended to do so.
>
> We (OE) have wiki page (slightly outdated) with some janitor tasks:
> http://openembedded.org/index.php/OpenEmbeddedJanitors
Great, this is the idea. It's a pretty sparse list, and could do with
some fleshing out.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
prev parent reply other threads:[~2011-03-30 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 16:51 RFC: newbies and janitors Darren Hart
2011-03-28 21:41 ` Rifenbark, Scott M
2011-03-28 23:29 ` Yury Bushmelev
2011-03-29 1:37 ` Jeff Osier-Mixon
2011-03-30 16:08 ` Darren Hart [this message]
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=4D935575.1050501@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=jay4mail@gmail.com \
--cc=yocto@yoctoproject.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.