linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Rogers <irogers@google.com>
To: linux-perf-users <linux-perf-users@vger.kernel.org>
Cc: chu howard <howardchu95@gmail.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	 Namhyung Kim <namhyung@kernel.org>
Subject: Re: GSoC 2024 contributor news - restarting office hours
Date: Tue, 14 May 2024 23:12:29 -0700	[thread overview]
Message-ID: <CAP-5=fV5BxH_VMLbumA76Z4jguMmkc9SgduUfWat3ssf_hTy6A@mail.gmail.com> (raw)
In-Reply-To: <CAP-5=fW2-pbOek68wjrEB+G=kzDmo3oPYuFj7iheouTMiaz5rQ@mail.gmail.com>

On Thu, May 2, 2024 at 9:00 PM Ian Rogers <irogers@google.com> wrote:
>
> Dear all,
>
> We were really excited and grateful for all of the Google
> Summer-of-Code (GSoC) applicants received this year. It was the most
> applicants for GSoC and the most we've ever received for Linux perf
> tools as part of the Linux foundation. Given the number of applicants,
> organizers held proposals to a high bar and we're sorry for all those
> who applied but failed to get a spot - we tried to argue for more
> spots. You are of course welcome to contribute to Linux perf outside
> of GSoC and everyone is here to help with that. Thank you for the
> contributions you've already made!
>
> We are excited to say that Howard Chu's proposal on perf trace and BTF
> for GSoC was accepted. The GSoC program officially starts on May 27th
> and now is a community bonding period [1].
>
> In the past to allow an open interaction with everyone in the project
> we've held weekly office hours/syncs with GSoC contributors. The
> office hours have often had wider discussions on perf event topics. It
> is difficult to pick a time/date for the office hours so if people
> have thoughts on organization then we'd love to know. Perhaps we can
> alternate time slots, or have more than one. I previously did a google
> forms survey and a timezone convenient to Europe was selected, but
> then we had very little attendance from people in that timezone.
> Somewhat selfishly this time I'd like a time slot that is convenient
> to the mentors and Howard.

Reminder that we're just under 2 weeks away from GSoC coding starting
so we need to make a decision on a day/time to hold office hours - or
multiple times if needs be.

Thanks,
Ian

> Thanks,
> Ian
>
> [1] https://developers.google.com/open-source/gsoc/timeline

  reply	other threads:[~2024-05-15  6:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03  4:00 GSoC 2024 contributor news - restarting office hours Ian Rogers
2024-05-15  6:12 ` Ian Rogers [this message]
2024-05-23  4:16   ` 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=fV5BxH_VMLbumA76Z4jguMmkc9SgduUfWat3ssf_hTy6A@mail.gmail.com' \
    --to=irogers@google.com \
    --cc=acme@kernel.org \
    --cc=howardchu95@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).