Re: [kernelci-members] KernelCI working group: Web Dashboard

From: Gustavo Padovan
Date: Thu Sep 01 2022 - 15:32:18 EST

Next message: Guenter Roeck: "Re: [PATCH v2] string: Introduce strtomem() and strtomem_pad()"
Previous message: kernel test robot: "Re: [PATCH 2/3] mm, page_owner: Add page_owner_stacks file to print out only stacks and their counter"
Next in thread: Gustavo Padovan: "Re: [kernelci-members] KernelCI working group: Web Dashboard"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello,

The next meeting is next Monday September 5th at 12:00pm EDT. Invite sent to those who answered the poll and the the members and tsc mailing list. In any invite ics is attached.

Best regards,

Gustavo

Le 29/08/2022 à 11:04, Gustavo Padovan a écrit :

Hello,

The previous tentative below didn't work due to vacation season. Here's a new pool with dates from 1st to 8th of September. Please answer it until this Wednesday August 31th.

https://doodle.com/meeting/participate/id/dG5v423a

See the email below for meetings notes and current User Stories document.

Regards,

Gustavo

On 7/18/22 10:17, Gustavo Padovan wrote:

Hi everyone,

In our last Web Dashboard meeting[1] where we reviewed the User Stories document[2]. Then, after that we worked offline to incorporate the feedback on doc, so it is time for our next meeting to further discuss. Please answer the poll with your time availability on the link below. I added dates from 21th to 28th of July.

https://doodle.com/meeting/participate/id/eX6vyY5b

Thank you,

Gus
—
[1]https://docs.google.com/document/d/1yp-2L54tnrwkZ--59t2GeXuq1gt5dDnsFy08odizl1Y/edit#bookmark=id.6ok0ufne9shj
[2]https://docs.google.com/document/d/1_rfMpas4n_gw2GvUTRU63vIXk95VotJuittalX7trP8/edit#heading=h.wjoxi4s5pxzl

On 6/7/22 10:46, Gustavo Padovan wrote:

Hello,

Our next meeting has been scheduled for this Thursday at 3pm UTC. Invite was sent to the kernelci-members list, but here goes the instructions to join as well:

This event has a video call.
Join: https://meet.google.com/yyz-jzjy-yfu
(US) +1 254-227-6870 PIN: 188509910#
View more phone numbers: https://tel.meet/yyz-jzjy-yfu?pin=5882595078642&hs=7

Regards,

Gustavo

Le 31/05/2022 à 15:34, Gustavo Padovan a écrit :

Hello everyone,

**

*From our first meeting back in October[1], we took the action of organizing our user stories that you were spread as a comments in the the github issue{2} and, converting them into User Stories document[3].*

*

In the next meeting, we want to study the current User Stories and start discussions to progress on development. The proposed slots are for next week. Please answer the doodle by the end of this week:

https://doodle.com/meeting/participate/id/egJ12A9d

Best regards,

Gustavo

[1] https://docs.google.com/document/d/1yp-2L54tnrwkZ--59t2GeXuq1gt5dDnsFy08odizl1Y/edit# <https://docs.google.com/document/d/1yp-2L54tnrwkZ--59t2GeXuq1gt5dDnsFy08odizl1Y/edit#>

[2] https://github.com/kernelci/kernelci-project/discussions/28 <https://github.com/kernelci/kernelci-project/discussions/28>

{3} https://docs.google.com/document/d/1_rfMpas4n_gw2GvUTRU63vIXk95VotJuittalX7trP8/edit <https://docs.google.com/document/d/1_rfMpas4n_gw2GvUTRU63vIXk95VotJuittalX7trP8/edit>*
Le 27/07/2021 à 11:54, Guillaume Tucker a écrit :

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/

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20220905T160000Z
DTEND:20220905T170000Z
DTSTAMP:20220901T192904Z
ORGANIZER;CN=kernel bot:mailto:bot@xxxxxxxxxxxx
UID:59e134a5v811tplqpr1j8c2gcn@xxxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=guillaume.tucker@xxxxxxxxxxxxx;X-NUM-GUESTS=0:mailto:guillaume.tuck
er@xxxxxxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=kernel bot;X-NUM-GUESTS=0:mailto:bot@xxxxxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=khilman@xxxxxxxxxxxx;X-NUM-GUESTS=0:mailto:khilman@xxxxxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=nikolai.kondrashov@xxxxxxxxxx;X-NUM-GUESTS=0:mailto:nikolai.kondras
hov@xxxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=kernelci-tsc@xxxxxxxxx;X-NUM-GUESTS=0:mailto:kernelci-tsc@xxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=kernelci-members@xxxxxxxxx;X-NUM-GUESTS=0:mailto:kernelci-members@g
roups.io
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=johnson.george@xxxxxxxxxxxxx;X-NUM-GUESTS=0:mailto:johnson.george@m
icrosoft.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=denys.f@xxxxxxxxxxxxx;X-NUM-GUESTS=0:mailto:denys.f@xxxxxxxxxxxxx
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=gustavo.padovan@xxxxxxxxxxxxx;X-NUM-GUESTS=0:mailto:gustavo.padovan
@collabora.com
X-GOOGLE-CONFERENCE:https://meet.google.com/ajg-qxsz-uje
X-MICROSOFT-CDO-OWNERAPPTID:-1184272718
CREATED:20220901T192903Z
DESCRIPTION:<br>In our last Web Dashboard meeting[1] where we reviewed the
User Stories document[2]. Then\, after that we worked offline to incorporat
e the feedback on doc\, so it is time for our next meeting to further discu
ss the next steps<br>—<br>[1] meeting notes:&nbsp\;<a href="https://docs.go
ogle.com/document/d/1yp-2L54tnrwkZ--59t2GeXuq1gt5dDnsFy08odizl1Y/edit#bookm
ark=id.6ok0ufne9shj" class="pastedDriveLink-0" id="ow698" __is_owner="true"
>https://docs.google.com/document/d/1yp-2L54tnrwkZ--59t2GeXuq1gt5dDnsFy08od
izl1Y/edit#bookmark=id.6ok0ufne9shj</a> <br>[2] User stories&nbsp\;<a href=
"https://docs.google.com/document/d/1_rfMpas4n_gw2GvUTRU63vIXk95VotJuittalX
7trP8/edit#heading=h.wjoxi4s5pxzl" class="pastedDriveLink-1" id="ow705" __i
s_owner="true">https://docs.google.com/document/d/1_rfMpas4n_gw2GvUTRU63vIX
k95VotJuittalX7trP8/edit#heading=h.wjoxi4s5pxzl</a>\n\n-::~:~::~:~:~:~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nThis e
vent has a video call.\nJoin: https://meet.google.com/ajg-qxsz-uje\n(US) +1
314-325-2325 PIN: 560694566#\nView more phone numbers: https://tel.meet/aj
g-qxsz-uje?pin=8415062680492&hs=7\n\nView your event at https://calendar.go
ogle.com/calendar/event?action=VIEW&eid=NTllMTM0YTV2ODExdHBscXByMWo4YzJnY24
ga2VybmVsY2ktbWVtYmVyc0Bncm91cHMuaW8&tok=MTYjYm90QGtlcm5lbGNpLm9yZzE4NGNhMG
QzODZjYTNkNWYyOGZiMjU5NmVhYjU4NTFiOWRmMWM4OTM&ctz=America%2FLos_Angeles&hl=
en&es=1.\n\nDo not edit this section of the description.\n-::~:~::~:~:~:~:~
:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20220901T192903Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:KernelCI Web Dashboard WG
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

Next message: Guenter Roeck: "Re: [PATCH v2] string: Introduce strtomem() and strtomem_pad()"
Previous message: kernel test robot: "Re: [PATCH 2/3] mm, page_owner: Add page_owner_stacks file to print out only stacks and their counter"
Next in thread: Gustavo Padovan: "Re: [kernelci-members] KernelCI working group: Web Dashboard"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]