From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: kernelci@groups.io, automated-testing@lists.yoctoproject.org,
kernel-build-reports@lists.linaro.org, workflows@vger.kernel.org
Subject: Re: KernelCI Community Survey
Date: Thu, 9 Jul 2020 23:32:45 +0100 [thread overview]
Message-ID: <c19726e0-0483-c718-2d33-e7ac9c88cb19@collabora.com> (raw)
In-Reply-To: <d03548cc-86ee-4922-7819-9a22acc055ee@collabora.com>
On 11/06/2020 11:11, Guillaume Tucker wrote:
> + workflows
>
> On 02/06/2020 22:22, Guillaume Tucker wrote:
>> As the KernelCI project keeps growing, we need to know a bit
>> better what the Linux kernel community needs in terms of
>> automated testing. We would really appreciate if you could
>> please spare one minute to fill this survey form:
>
> Sending out a big Thank You for all the replies we have received
> already, your input is proving to be highly valuable. We thought
> it would also be relevant to share this on the workflows mailing
> list and reach a slightly broader audience while the survey is
> still open.
>
>> https://forms.gle/Y5iuyLXgQr2y3SrF6
>
> Please feel free to fill the form if you haven't done so already
> and share the link above with others you think might be
> interested.
Thanks again everyone who has responded to the survey. Here's
the detailed report which also includes a spreadsheet with the
full results (minus any personal information):
https://foundation.kernelci.org/blog/2020/07/09/kernelci-community-survey-report/
Please also note that we've decided to re-open the form until the
end of August, in case some of you missed the opportunity to
respond before. The link is the same as in my previous email:
https://forms.gle/Y5iuyLXgQr2y3SrF6
Best wishes,
Guillaume
next prev parent reply other threads:[~2020-07-09 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4e70209b-e637-abdf-d72a-7cb978956f9d@collabora.com>
2020-06-11 10:11 ` KernelCI Community Survey Guillaume Tucker
2020-07-09 22:32 ` Guillaume Tucker [this message]
2020-07-13 17:49 ` Frank Rowand
2020-07-13 18:13 ` Frank Rowand
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=c19726e0-0483-c718-2d33-e7ac9c88cb19@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci@groups.io \
--cc=workflows@vger.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).