ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Recruitment; Outreach Programmes
Date: Mon, 3 Aug 2015 21:23:41 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1508032123090.2038@localhost6.localdomain6> (raw)
In-Reply-To: <1438629566.2173.58.camel@HansenPartnership.com>



On Mon, 3 Aug 2015, James Bottomley wrote:

> I think this is part of the broad recruitment topic, but it's worth
> considering in its own right.  We should probably begin by reviewing the
> current outreach programmes and whether they're effective.  The
> currently running one is the Outreach Programme for Women:
> 
> http://www.linuxfoundation.org/news-media/blogs/browse/2013/04/announcing-outreach-program-women-internships-linux-kernel-please
> 
> Which has been running successfully for a while.  The questions for us
> are
> 
>      1. Should the programme be broadened (the current OPW one only
>         reaches women, not everyone who might need outreach)

There are plans to broaden it somewhat, but I don't know the details.

julia

>      2. Assuming we do decide broader is better, what's the next group
>         to reach out to?
>      3. Is this type of outreach better than non group specific
>         outreach?  One can argue the kernel mentors list was non group
>         specific and it didn't seem to get much uptake, so perhaps group
>         specific is better?  Essentially is it better for us to invest
>         our efforts in specific segments rather than generally?
> 
> Just on the premise of 3 we can still improve our overall acceptance
> processes, as we have been discussing, in a general way because outreach
> is what you do to pull people in, not what processes you have in place
> to help them once they are pulled in.
> 
> James
> 
> 
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
> 

  reply	other threads:[~2015-08-03 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 19:19 James Bottomley
2015-08-03 19:23 ` Julia Lawall [this message]
2015-08-04  9:05   ` Mark Brown
2015-08-04 17:05 ` Jerry Snitselaar

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=alpine.DEB.2.02.1508032123090.2038@localhost6.localdomain6 \
    --to=julia.lawall@lip6.fr \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox