From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io, dan.rue@linaro.org, kernelci@groups.io,
matthew.hart@linaro.org
Cc: Mark Brown <broonie@kernel.org>
Subject: Re: New meeting time
Date: Fri, 29 Mar 2019 10:20:29 -0700 [thread overview]
Message-ID: <7hy34xwqaq.fsf@baylibre.com> (raw)
In-Reply-To: <20190326003527.jzeviygligmbfkiy@xps.therub.org>
"Dan Rue" <dan.rue@linaro.org> writes:
> On Mon, Mar 25, 2019 at 11:27:52AM +0000, Matt Hart wrote:
>> On Mon, 25 Mar 2019 at 11:23, Mark Brown <broonie@kernel.org> wrote:
>> >
>> > Hi,
>> >
>> > It's been just over a week since I sent out the doodle[1] for the new
>> > meeting time and we've got responses in. The top options we have allow
>> > everyone to attend (at least acording to the survey!):
>> >
>> > 10 - Monday 14:00
>> > - Tuesday 16:00
>> > - Friday 15:00 (I will have a conflict every other week)
>> > 9 - Monday 15:00 (but no Guillaume)
>> >
>> > with a bunch of other options with 8 votes. I don't know what my
>> > schedule is going to be like in a month or so but I'm guessing the other
>> > slots should be fine for me. Given that practically speaking it's
>> > difficult for Kevin to attend the Monday 14:00 slot I propose that we go
>> > with the Tuesday 16:00 slot since that's the latest one and therefore
>> > most friendly to those on PST. Thoughts?
>>
>> Makes sense to me, as long as it definitely works for our PST folks
>
> Is there any objection to making the meeting an open invite, and
> advertising it on the wiki and the weekly minutes?
No objection from me, as long as it's clear that this is a call for
developers working on kernelCI, not a generic support call.
Kevin
next prev parent reply other threads:[~2019-03-29 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 11:22 New meeting time Mark Brown
2019-03-25 11:27 ` Matt Hart
2019-03-26 0:35 ` Dan Rue
2019-03-26 12:42 ` Mark Brown
2019-03-29 17:20 ` Kevin Hilman [this message]
2019-04-01 3:42 ` Mark Brown
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=7hy34xwqaq.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=broonie@kernel.org \
--cc=dan.rue@linaro.org \
--cc=kernelci@groups.io \
--cc=matthew.hart@linaro.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