From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49dbfac4-e730-2eba-e37f-c7395d27b503@collabora.com> Date: Tue, 31 May 2022 15:34:17 -0400 MIME-Version: 1.0 Subject: Re: [kernelci-members] KernelCI working group: Web Dashboard References: From: "Gustavo Padovan" In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable List-ID: To: kernelci-members@groups.io, "kernelci@groups.io" Cc: automated-testing@lists.yoctoproject.org, "linux-kernel@vger.kernel.org" , "kernelci-tsc@groups.io" , Simon Xiao , Carlos Cardenas , KY Srinivasan , Sharath George John , "Alain Gefflaut (HE/HIM)" Hello everyone, ** *From our first meeting back in October[1], we took the action of=20 organizing our user stories that you were spread as a comments in the=20 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=20 discussions to progress on development. The proposed slots are for next=20 week. Please answer the doodle by the end of this week: https://doodle.com/meeting/participate/id/egJ12A9d Best regards, Gustavo [1]=20 https://docs.google.com/document/d/1yp-2L54tnrwkZ--59t2GeXuq1gt5dDnsFy08odi= zl1Y/edit#=20 [2] https://github.com/kernelci/kernelci-project/discussions/28=20 {3}=20 https://docs.google.com/document/d/1_rfMpas4n_gw2GvUTRU63vIXk95VotJuittalX7= trP8/edit=20 * Le 27/07/2021 =C3=A0 11:54, Guillaume Tucker a =C3=A9crit=C2=A0: > 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-sur= vey-report/ > > >=20 > >