All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster <akuster@mvista.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	Yocto list discussion <yocto@yoctoproject.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: LF Community Bridge Mentorship
Date: Fri, 16 Aug 2019 18:52:03 -0700	[thread overview]
Message-ID: <75297c71-0f45-473c-3a1b-a8ec7a9b6080@mvista.com> (raw)
In-Reply-To: <CAP71WjxRwFni-yjPepwqBkk=77UwN0kaMdxNCz==Y2_28e67VQ@mail.gmail.com>



On 8/16/19 12:37 AM, Nicolas Dechesne wrote:
> hi there.
> just a reminder!
> cheers

Maybe mention this during the BoF in next week's ELC?

- armin
>
> On Tue, Jul 30, 2019 at 4:46 PM Nicolas Dechesne
> <nicolas.dechesne@linaro.org> wrote:
>> Dear all,
>>
>> The Community Bridge platform was launched earlier this year by the
>> Linux Foundation. It’s a set of services available to LF projects to
>> help them build stronger ecosystems, and foster developers
>> relationship within their respective communities. See [1] and [2]. The
>> Yocto Project has joined the Community Bridge Funding and Mentorship
>> programs.
>>
>> If you have any specific questions about these programs, please do not
>> hesitate to reach out to me.
>>
>> Today, we would like to talk more about the mentorship program. We
>> have tried several initiatives in the past about interns and
>> mentorship, and we would like to do that again using the new LF
>> platform. A mentorship program for the Yocto Project is a good
>> opportunity for our overall community to reach out to new developers,
>> improve our developers diversity. It will help increase the pool of
>> available developers with appropriate skills about the Yocto Project
>> and Open Embedded technologies and as a consequence create a more
>> sustainable ecosystem around the Yocto Project. It also offers
>> existing senior developers the chance to become mentors, and share
>> their knowledge!
>>
>> We would like to request feedback about how to best define the Yocto
>> Project Mentorship program.
>>
>> The structure of the mentorship is flexible and we can adjust as
>> needed. Our initial thought is to set 12-week project, which is what
>> the Linux Kernel Mentorship program is using, see [4]. The overall
>> process involves:
>>
>> 1. Finding / defining work items for potential mentees.
>> 2. Get appropriate funding for mentees’ stipends
>> 3. Recruit mentors within our community
>> 4. Review and select mentees’ applications
>>
>> There has already been some work on the potential work items in the
>> form of the newcomer bugs, some of which could be turned into work
>> suitable for a mentorship programme.
>>
>> === Call for ACTION ===
>>
>> * We need your help for any of the items above, and especially #1 to
>> get started. Whether you are a long time contributor to the project or
>> you recently joined our mailing list, your feedback will be greatly
>> appreciated.
>> * If you are interested to participate as a mentor, please let me know!
>> * You don’t need to be a project expert to be a mentor, you need to
>> know how the project works and be willing to help guide someone
>> through their task.
>>
>> There is no specific timeline set yet, it will most likely depend on
>> how much feedback we receive about this initiative, but most likely
>> the internships will have to be tied to the Yocto Project release
>> timeline.
>>
>> If you have any questions or any suggestions, please reach out to me!
>> cheers,
>> Nico
>>
>> [1] https://www.linuxfoundation.org/press-release/2019/03/the-linux-foundation-launches-new-communitybridge-platform-to-help-sustain-open-source-communities/
>> [2] https://communitybridge.org/
>> [3] https://people.communitybridge.org/
>> [4] https://wiki.linuxfoundation.org/lkmp



      reply	other threads:[~2019-08-17  1:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 14:46 LF Community Bridge Mentorship Nicolas Dechesne
2019-08-16  7:37 ` Nicolas Dechesne
2019-08-17  1:52   ` akuster [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=75297c71-0f45-473c-3a1b-a8ec7a9b6080@mvista.com \
    --to=akuster@mvista.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --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.