From: Frank Rowand <firstname.lastname@example.org> To: Guillaume Tucker <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: KernelCI Community Survey Date: Mon, 13 Jul 2020 12:49:30 -0500 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 2020-07-09 17:32, Guillaume Tucker wrote: > 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 > Some feedback from my experience answering the survey today. Question "Would a web-based dashboard fit well within your workflow?" had two answers. The answers to choose from made assumptions about why one would choose "yes" or "no". The second answer is "No thanks, I only want to work with emails and command line tools." The second answer does not allow me say that I have a preference for emails and command line tools, but I find a web based interface to also provide value. It would be better to split the original question into two questions: (1) web-based dashboard useful? (yes/no) (2) emails and command line tools useful? (yes/no) And it would probably be even better to split (2) into (2) emails, and (3) command line tools. I wanted to answer yes to each of them, but if only one was available then I had a preference, which is what my answer was based on. Then the question "Would you want to be able to access an API with raw test data?" again put intent into the "no" answer. The answers should have been (1) yes (2) no If you wanted to explore further, a second question would be: "Do I want to design my own CI tools that access the raw test data via an API?".
next prev parent reply index Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <firstname.lastname@example.org> 2020-06-11 10:11 ` Guillaume Tucker 2020-07-09 22:32 ` Guillaume Tucker 2020-07-13 17:49 ` Frank Rowand [this message] 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Workflows Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/workflows/0 workflows/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 workflows workflows/ https://lore.kernel.org/workflows \ firstname.lastname@example.org public-inbox-index workflows Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.workflows AGPL code for this site: git clone https://public-inbox.org/public-inbox.git