From: Greg KH <gregkh@linuxfoundation.org>
To: kernelci-members@groups.io
Cc: "kernelci@groups.io" <kernelci@groups.io>,
automated-testing@lists.yoctoproject.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernelci-tsc@groups.io" <kernelci-tsc@groups.io>
Subject: Re: [kernelci-members] KernelCI working group: Web Dashboard
Date: Tue, 27 Jul 2021 17:58:45 +0200 [thread overview]
Message-ID: <YQAtNc4R1K3o6rxb@kroah.com> (raw)
In-Reply-To: <f3874e7d-ccfe-4a2d-d054-9b7bf9e8b44d@collabora.com>
On Tue, Jul 27, 2021 at 04:54:46PM +0100, Guillaume Tucker wrote:
> Last year's KernelCI Community Survey[1] showed the importance of
> having a good web dashboard. About 70% of respondents would use
> one if it provided the information they needed efficiently.
> While other things are arguably even more important, such as
> testing patches from mailing lists, replying to stable reviews
> and sending email reports directly to contributors in a "natural"
> workflow, the web dashboard has been a sticking point for a
> while.
>
> There have been several attempts at solving this problem, using
> Elastic Stack and Grafana among other things, but there isn't a
> single framework able to directly provide an off-the-shelf
> solution to the community's needs. In fact, the first issue is
> the lack of understanding of these needs: who wants to use the
> web dashboard, and how? Then, how does one translate those needs
> into a user interface? Doing this requires skills that engineers
> who regularly contribute to KernelCI typically don't have. As
> such, a dedicated working group is being created in order to fill
> this gap.
>
> The aim is to coordinate efforts and try to follow best practices
> to make steady progress and avoid repeating the same mistakes.
> Most likely, we will need some help from proper web developers
> who aren't part of the usual KernelCI community. This may be
> facilitated by the KernelCI LF project budget if approved by the
> governing board.
>
> In order to get started, we would need to have maybe 3 to 5
> people available to focus on this. It doesn't necessarily mean a
> lot of hours spent but actions to be carried out on a daily or
> weekly basis. So far we have Gustavo Padovan as our new KernelCI
> Project Manager and a few people have expressed interest but we
> still need formal confirmation.
>
>
> Here's a GitHub project dedicated to the new web dashboard:
>
> https://github.com/orgs/kernelci/projects/4
>
> I've created a couple of issues to get started about user
> stories, and some initial milestones as a basic skeleton:
>
> https://github.com/kernelci/kernelci-project/milestones
>
>
> This is ultimately a community-driven effort to address the needs
> of the kernel community. Please share any thoughts you may have
> on this, whether you want to add some user stories, share some
> expertise, be officially in the working group or take part in
> this effort in any other way.
How do we "join" the working group? I'm willing to help out from the
"user who will use this a lot and complain about things that do not
work well" point of view :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-07-27 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 15:54 KernelCI working group: Web Dashboard Guillaume Tucker
2021-07-27 15:58 ` Greg KH [this message]
2022-05-31 19:34 ` [kernelci-members] " Gustavo Padovan
[not found] ` <16F4479F76A8C807.11895@groups.io>
2022-06-07 14:46 ` Gustavo Padovan
[not found] ` <16F65ECD601264EC.15470@groups.io>
2022-07-18 14:17 ` Gustavo Padovan
[not found] ` <1706557437ACCB9C.25939@groups.io>
2022-08-29 15:04 ` Gustavo Padovan
[not found] ` <170FD91B51709B41.16609@groups.io>
2022-09-01 19:32 ` Gustavo Padovan
[not found] ` <1710D385D5C94519.1438@groups.io>
2022-09-05 11:04 ` Gustavo Padovan
2022-09-05 12:13 ` Nikolai Kondrashov
[not found] <1695B2FF4ECA569A.21772@groups.io>
2021-10-05 13:20 ` Gustavo Padovan
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=YQAtNc4R1K3o6rxb@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=kernelci-members@groups.io \
--cc=kernelci-tsc@groups.io \
--cc=kernelci@groups.io \
--cc=linux-kernel@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).