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# >>>> >>>> >>>> >>>> [2] https://github.com/kernelci/kernelci-project/discussions/28 >>>> >>>> >>>> {3} >>>> 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/ >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>> >> >