From: Ian Rogers <irogers@google.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users <linux-perf-users@vger.kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
paranlee <p4ranlee@gmail.com>,
Madhu patel <patelmadhu06@gmail.com>,
Anup Sharma <anupnewsmail@gmail.com>,
Lukas Molleman <lukas.molleman@gmail.com>
Subject: Re: Google Summer-of-Code 2023
Date: Mon, 13 Mar 2023 09:38:10 -0700 [thread overview]
Message-ID: <CAP-5=fXWDPzuFrrY+uKnfoa5gO9eEfGUsbCyXB8AS7Tz0ZX=jw@mail.gmail.com> (raw)
In-Reply-To: <CAP-5=fVaH0p4NkKiQSxaxZnT5zR=hbwSArO2n0L7tCNZwBumKQ@mail.gmail.com>
On Wed, Feb 22, 2023 at 7:58 PM Ian Rogers <irogers@google.com> wrote:
>
> The Linux Foundation was selected as a GSoC organization for 2023!
> https://summerofcode.withgoogle.com/programs/2023/organizations/the-linux-foundation
>
> This means we're looking for contributors until March 19th:
> https://developers.google.com/open-source/gsoc/timeline
A reminder of the GSoC timeline. Applications open in a week;
* February 22 - March 19
Potential GSoC contributors discuss application ideas with mentoring
organizations
* March 20 - 18:00 UTC
GSoC contributor application period begins
* April 4 - 18:00 UTC
GSoC contributor application deadline
Thanks,
Ian
> Some project ideas are listed here:
> https://wiki.linuxfoundation.org/gsoc/2023-gsoc-perf
>
> Please help to share!
>
> Thanks,
> Ian
>
> (Resend in plain text because of LKML's HTML filters)
next prev parent reply other threads:[~2023-03-13 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 15:28 Google Summer-of-Code 2023 Ian Rogers
2023-01-09 15:45 ` Arnaldo Carvalho de Melo
2023-01-25 1:01 ` Ian Rogers
2023-02-23 3:58 ` Ian Rogers
2023-03-13 16:38 ` Ian Rogers [this message]
2023-03-27 21:22 ` Ian Rogers
2023-03-27 22:00 ` Ian Rogers
2023-03-28 2:00 ` Namhyung Kim
2023-03-28 2:03 ` Namhyung Kim
2023-04-03 15:56 ` Ian Rogers
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='CAP-5=fXWDPzuFrrY+uKnfoa5gO9eEfGUsbCyXB8AS7Tz0ZX=jw@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=anupnewsmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lukas.molleman@gmail.com \
--cc=namhyung@kernel.org \
--cc=p4ranlee@gmail.com \
--cc=patelmadhu06@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).