From: David Vernet <void@manifault.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com, bsegall@google.com, bristot@redhat.com,
vschneid@redhat.com, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@kernel.org, joshdon@google.com, brho@google.com,
pjt@google.com, derkling@google.com, haoluo@google.com,
youssefesmat@google.com, greg.marsden@oracle.com,
willy@infradead.org, andrea.righi@canonical.com,
andrealmeid@igalia.com, changwoo@igalia.com, gpiccoli@igalia.com,
tj@kernel.org, colin.i.king@gmail.com, ast@kernel.org,
julia.lawall@inria.fr, himadrispandya@gmail.com,
redha.gouicem@rwth-aachen.de, admin@ptr1337.dev,
lucjan.lucjanov@gmail.com
Subject: Re: Sched Ext slack channel / office hours
Date: Mon, 23 Oct 2023 12:53:26 -0500 [thread overview]
Message-ID: <20231023175326.GA4055@maniforge> (raw)
In-Reply-To: <20231019093109.4c4406b2@gandalf.local.home>
On Thu, Oct 19, 2023 at 09:31:09AM -0400, Steven Rostedt wrote:
> On Wed, 18 Oct 2023 15:54:31 -0500
> David Vernet <void@manifault.com> wrote:
>
> > Hello everyone,
> >
> > The first RFC patch set [0] for sched_ext was sent to the upstream list
> > almost one year ago, with three more revisions of the series having been
> > sent upstream since. In that time, a number of individuals, companies,
> > and organizations have begun to use and experiment with sched_ext. We
> > want to make it easier to collaborate, so we’ve decided to set up a
> > weekly office hours call, and create a Slack channel [1] that folks can
> > join to ask questions, discuss features, etc.
> >
> > [0]: https://lore.kernel.org/lkml/20221130082313.3241517-1-tj@kernel.org/
> > [1]: https://join.slack.com/t/schedextworkspace/shared_invite/zt-24c4on3sk-sHlozdLfCZBODfwU6t6dbw
> >
> > The Slack channel can be joined via the link in [1]. For office hours,
> > we’ll start with 10:00 PDT / 17:00 UTC on Mondays (likely starting the
> > week of 10/30), but we can change the time if it’s inconvenient for too
> > many folks. The calls will likely take place through Slack, so you’ll
> > have to join the Slack channel if you want to participate in the office
> > hours calls. As a friendly reminder, you can access the sched_ext
> > repository at [2].
> >
> > [2]: https://github.com/sched-ext/sched_ext
>
> I just have to state that there's a significant amount of people on this
> list (myself included) that will not use slack (I don't have it installed
> on any of my machines, and will not install it). Perhaps an open source
> platform (matrix) or simply an IRC channel would work for us. Although that
> still would not guarantee that anyone would show up.
>
> That said, I do host a Linux schedule monthly meeting on Google meets if
> you would like to join that.
Hi Steven,
Yes, it could be beneficial to attend your meeting as well. Please feel
free to send us an invitation to any instance of your meeting that is
related to sched_ext.
Thanks,
David
next prev parent reply other threads:[~2023-10-23 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 20:54 Sched Ext slack channel / office hours David Vernet
2023-10-19 13:31 ` Steven Rostedt
2023-10-23 17:53 ` David Vernet [this message]
2023-10-23 18:46 ` Steven Rostedt
2023-10-23 21:43 ` David Vernet
2023-10-29 7:09 ` Julia Lawall
2023-10-30 14:06 ` David Vernet
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=20231023175326.GA4055@maniforge \
--to=void@manifault.com \
--cc=admin@ptr1337.dev \
--cc=andrea.righi@canonical.com \
--cc=andrealmeid@igalia.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=brho@google.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=colin.i.king@gmail.com \
--cc=daniel@iogearbox.net \
--cc=derkling@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gpiccoli@igalia.com \
--cc=greg.marsden@oracle.com \
--cc=haoluo@google.com \
--cc=himadrispandya@gmail.com \
--cc=joshdon@google.com \
--cc=julia.lawall@inria.fr \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucjan.lucjanov@gmail.com \
--cc=martin.lau@kernel.org \
--cc=pjt@google.com \
--cc=redha.gouicem@rwth-aachen.de \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=willy@infradead.org \
--cc=youssefesmat@google.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