From: Gustavo Padovan <gustavo.padovan@collabora.com>
To: kernelci-members@groups.io, "kernelci@groups.io" <kernelci@groups.io>
Cc: automated-testing@lists.yoctoproject.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernelci-tsc@groups.io" <kernelci-tsc@groups.io>,
Simon Xiao <sixiao@microsoft.com>,
Carlos Cardenas <Carlos.Cardenas@microsoft.com>,
KY Srinivasan <kys@microsoft.com>,
Sharath George John <sgeorgejohn@microsoft.com>,
"Alain Gefflaut (HE/HIM)" <agefflaut@microsoft.com>,
Johnson George <Johnson.George@microsoft.com>
Subject: Re: [kernelci-members] KernelCI working group: Web Dashboard
Date: Mon, 29 Aug 2022 11:04:26 -0400 [thread overview]
Message-ID: <ce17e20b-b60d-baaf-15af-1e3c8157df7b@collabora.com> (raw)
In-Reply-To: <1706557437ACCB9C.25939@groups.io>
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/
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>
--
Gustavo Padovan
Collabora Ltd.
Platinum Building, St John's Innovation Park
Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718
next prev parent reply other threads:[~2022-08-29 15:04 UTC|newest]
Thread overview: 9+ 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 ` [kernelci-members] " Greg KH
2021-07-27 16:34 ` Gustavo Padovan
[not found] ` <16F4479F76A8C807.11895@groups.io>
[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 [this message]
[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=ce17e20b-b60d-baaf-15af-1e3c8157df7b@collabora.com \
--to=gustavo.padovan@collabora.com \
--cc=Carlos.Cardenas@microsoft.com \
--cc=Johnson.George@microsoft.com \
--cc=agefflaut@microsoft.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=kernelci-members@groups.io \
--cc=kernelci-tsc@groups.io \
--cc=kernelci@groups.io \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sgeorgejohn@microsoft.com \
--cc=sixiao@microsoft.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
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).