linux-kernel - KernelCI working group: Web Dashboard

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <f3874e7d-ccfe-4a2d-d054-9b7bf9e8b44d@collabora.com>
Date:   Tue, 27 Jul 2021 16:54:46 +0100
From:   Guillaume Tucker <guillaume.tucker@...labora.com>
To:     "kernelci@...ups.io" <kernelci@...ups.io>
Cc:     kernelci-members <kernelci-members@...ups.io>,
        automated-testing@...ts.yoctoproject.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "kernelci-tsc@...ups.io" <kernelci-tsc@...ups.io>
Subject: KernelCI working group: Web Dashboard

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.

Best wishes,
Guillaume

[1] https://foundation.kernelci.org/blog/2020/07/09/kernelci-community-survey-report/