Hey Hans and Mauro, I remember also on a very little point regarding hardware for testing. But we didn't go in detail again during the summit. How do we can go ahead here? Are there some test systems up and running somewhere centralized or how it is organized right now? BR Martin ________________________________________ Von: Sebastian Fricke <sebastian.fricke@xxxxxxxxxxxxx> Gesendet: Mittwoch, 18. September 2024 11:30 An: Mauro Carvalho Chehab Cc: Hans Verkuil; Linux Media Mailing List; Sakari Ailus; Daniel Almeida; Mauro Carvalho Chehab; Hecht, Martin (Avnet Silica); Tommaso Merciai; Jacopo Mondi; Benjamin Mugnier; Laurent Pinchart; Ricardo Ribalda; Michael Tretter; Alain Volmat; Sean Young; Steve Cho; Tomasz Figa; Hidenori Kobayashi; Hu, Jerry W; Suresh Vankadara; Devarsh Thakkar; r-donadkar@xxxxxx; Dave Stevenson; Mehdi Djait; Nicolas Dufresne; Salahaldeen Altous Betreff: [External]Re: [ANN] Media Summit September 16th: Final Agenda (v7) Hey Hans & Mauro, On 18.09.2024 09:24, Mauro Carvalho Chehab wrote: >Em Tue, 17 Sep 2024 14:52:19 +0200 >Hans Verkuil <hverkuil@xxxxxxxxx> escreveu: > >> Hi Sebastian, >> >> On 9/17/24 11:17 AM, Sebastian Fricke wrote: >> > Greetings, >> > >> > I remember that we wanted to still define a couple of processes for the >> > multi-committer model for which we hadn't have the time on the media >> > summit. Just would like to gather who would be interested to meet for >> > that, where we meet (probably LPC venue) and when (Laurent just told me >> > that Friday is probably a good slot for that). >> >> Can you refresh my memory which processes need more work? Well I basically remember that we had a bunch of topics in our meetings that we wanted to skip in order to talk about them here. We looked at the documentation from DRM and wanted to think about equivalent policies for media. https://drm.pages.freedesktop.org/maintainer-tools/committer/committer-drm-misc.html#where-do-i-apply-my-patch Also there were topics like how to handle backports. > >I have the same doubt. As discussed during the summit, Hans and I had some >discussions yesterday, to address a few details. For both of us the process >sounds well defined. I know that we scraped a lot of topics in the meeting at the media summit and I am not sure about the scope you discussed with Ricardo yesterday. So, we don't have to meet if you feel like we covered everything, just wanted to use the opportunity as long as we are all in the same place. Regards, Sebastian > >From my personal notes, this will be the new process: > >- committers will merge patches at media-committers.git tree at fdo, > provided that they'll follow the rules defined on a committers agreement > and (partially?) enforced by media-ci checks; >- core committers follow the same rules, with a broader privilege of > changing kernel API/ABI; >- committers will ensure that patchwork will reflect the review process of > the patches; >- maintainers will double-check if everything is ok and, if ok, merge the > changes at linuxtv.org. We intend to rename the tree there to "media.git", > being the main tree to be used for development; >- pull requests will keep using the same process as currently. The only > change is that the media-stage.git tree will be renamed to "media.git"; >- maintainers will periodically send patches upstream. > >The media-commiters.git tree at fdo might be rebased if needed; the >media.git tree at linuxtv.org is stable. A large effort will be taken to >avoid rebasing it. > >We may need some helper scripts and/or use pwclient to keep patchwork >updated after committers reviews. > >Such process will start after -rc1. > >We intend to rename media-state to media at linuxtv after -rc1. > >It is up to maintainers to invite and decide who will be a committer. > >All committers/core-committers need to explicitly accept a committers >agreement. We may end starting without it at the beginning, but as soon >as a final version of such agreement is written, everyone with access to >the media-committers tree have to explicitly accept to keep their >commit rights on such tree. > >The only part that still require some work is the committers >agreement. I'm working on it together with Hans. As soon as we have >a version, we'll submit a patch to the kernel, to add it to the >media developer's profile[1]. > >[1] Documentation/driver-api/media/maintainer-entry-profile.rst > >> >> For me I think Friday afternoon (probably after 14:00) is the only >> option, or perhaps Thursday after the Camera MC. > >I can't meet on Friday afternoon. I probably will be on another >event on Thursday (Openeuler MC). > >> >> Regards, >> >> Hans >> >> > >> > Regards, >> > Sebastian >> > >> > On 11.09.2024 11:03, Hans Verkuil wrote: >> >> Hi all, >> >> >> >> Here is my seventh and final version of the agenda for the media >> >> summit. As always, >> >> all times (except lunch time) are guesstimates! >> >> >> >> The media summit will be held on Monday September 16th. Avnet Silica >> >> has very >> >> kindly offered to host this summit at their Vienna office, which is >> >> about 35 >> >> minutes by public transport from the Open Source Summit Europe venue >> >> (https://events.linuxfoundation.org/open-source-summit-europe/OSSE). >> >> >> >> Avnet Silica Office Location: >> >> >> >> Schönbrunner Str. 297/307, 1120 Vienna, Austria >> >> >> >> https://www.google.com/maps/place/Avnet+EMG+Elektronische+Bauteile+GmbH+(Silica)/@48.183203,16.3100937,15z/data=!4m6!3m5!1s0x476da80e20b26d5b:0x2c5d2a77bbd43334!8m2!3d48.1832035!4d16.320372!16s%2Fg%2F1tcy32vt?entry=ttu >> >> >> >> Refreshments are available during the day. >> >> >> >> Lunch is held at Schönbrunner Stöckl >> >> (https://www.schoenbrunnerstoeckl.com/), close >> >> to the Avnet Silica office. The lunch is sponsored by Ideas on Board >> >> and Cisco Systems >> >> Norway. >> >> >> >> Regarding the face mask policy: we will follow the same guidance that the >> >> Linux Foundation gives for the EOSS conference: >> >> >> >> https://events.linuxfoundation.org/open-source-summit-europe/attend/health-and-safety/#onsite-health-and-safety >> >> >> >> >> >> In-Person Attendees: >> >> >> >> Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx> (Intel) >> >> Daniel Almeida <daniel.almeida@xxxxxxxxxxxxx> (Collabora) >> >> Salahaldeen Altous <salahaldeen.altous@xxxxxxxxxxxxxxxx> (Leica Camera >> >> AG) >> >> Mauro Carvalho Chehab <mchehab@xxxxxxxxxx> (Huawei, Media Kernel >> >> Maintainer) >> >> Steve Cho <stevecho@xxxxxxxxxxxx> (Google) >> >> Sebastian Fricke <sebastian.fricke@xxxxxxxxxxxxx> (Collabora) >> >> Martin Hecht <martin.hecht@xxxxxxxx> (Avnet) >> >> Tommaso Merciai <tomm.merciai@xxxxxxxxx> (Avnet) >> >> Jacopo Mondi <jacopo.mondi@xxxxxxxxxxxxxxxx> (Ideas On Board) >> >> Benjamin Mugnier <benjamin.mugnier@xxxxxxxxxxx> (ST Electronics) >> >> Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> (Ideas On Board) >> >> Ricardo Ribalda <ribalda@xxxxxxxxxxxx> (Google) >> >> Michael Tretter <m.tretter@xxxxxxxxxxxxxx> (Pengutronix) >> >> Suresh Vankadara <svankada@xxxxxxxxxxxxxxxx> (Qualcomm) >> >> Hans Verkuil <hverkuil-cisco@xxxxxxxxx> (Cisco Systems Norway) >> >> Alain Volmat <alain.volmat@xxxxxxxxxxx> (ST Electronics) >> >> Sean Young <sean@xxxxxxxx> >> >> Jerry W Hu <jerry.w.hu@xxxxxxxxx> (Intel) >> >> >> >> Remote Attendees (using MS Teams): >> >> >> >> Mehdi Djait <mehdi.djait@xxxxxxxxxxxxxxx> (Intel) >> >> Rishikesh Donadkar <r-donadkar@xxxxxx> (TI) >> >> Nicolas Dufresne <nicolas@xxxxxxxxxxxx> (Collabora) >> >> Tomasz Figa <tfiga@xxxxxxxxxxxx> (Google) >> >> Hidenori Kobayashi <hidenorik@xxxxxxxxxxxx> (Google) >> >> Dave Stevenson <dave.stevenson@xxxxxxxxxxxxxxx> (Raspberry Pi) >> >> Devarsh Thakkar <devarsht@xxxxxx> (TI) >> >> >> >> All remote participants listed above should have received an invite >> >> with connection details. >> >> If not, please contact Martin Hecht <martin.hecht@xxxxxxxx> asap. >> >> >> >> If any information above is incorrect, or if I missed someone, then >> >> please let me know. >> >> >> >> We have 18 confirmed in-person participants, so we're full. >> >> If you want to join remotely, then contact me and I'll add you to that >> >> list. >> >> >> >> Draft agenda: >> >> >> >> 8:45-9:15: Get settled :-) >> >> >> >> 9:15-9:25: Hans: Quick introduction >> >> >> >> 9:25-11:00: Ricardo: multi-committer model using gitlab >> >> >> >> 11:00-11:15: break >> >> >> >> 11:15-12:15: Jacopo: Multi-context support in V4L2 >> >> >> >> 12:15-13:30: Lunch at Schönbrunner Stöckl >> >> >> >> 13:30-14:00: Tomasz: Current state of videobuf2, its limitations and >> >> the paths forward. >> >> >> >> 14:00-14:45: Laurent: subdevs, state, and usage of the media >> >> controller device to submit requests. >> >> >> >> 14:45-15:00: break >> >> >> >> 15:00-15:30: Sean: new tooling for infrared: >> >> >> >> - What it is and what it can do (love to hear any feedback of course) >> >> - Where it should be hosted? (I hope gitlab fdo, who do I ask) >> >> - What needs to be in place for a release? >> >> - This tool replaces ir-ctl and ir-keytable. How we phase them out? >> >> >> >> 15:30-16:00: Daniel: Rust in the media subsystem >> >> >> >> 16:00-16:15: break >> >> >> >> 16:15-16:30: Hans: UVC maintenance >> >> >> >> 16:30-17:00: Steve Cho: >> >> >> >> - V4L2 testing on Chromium using virtual video decode driver (visl) >> >> - V4L2 video decoding testing with KernelCI >> >> >> >> 17:00-17:30: Laurent: Should media drivers depend on CONFIG_PM? >> >> See here for more info: >> >> https://lore.kernel.org/linux-media/20240825222455.GA24390@xxxxxxxxxxxxxxxxxxxxxxxxxx/ >> >> >> >> 17:30-18:00: Any other topics and feedback on what can be improved >> >> next media summit. >> >> >> >> Hope to see you all on Monday! >> >> >> >> Regards, >> >> >> >> Hans >> >> >> >> >> >> >> > Sebastian Fricke >> > Consultant Software Engineer >> > >> > Collabora Ltd >> > Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK >> > Registered in England & Wales no 5513718. > Sebastian Fricke Consultant Software Engineer Collabora Ltd Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK Registered in England & Wales no 5513718. We continuously commit to comply with the applicable data protection laws and ensure fair and transparent processing of your personal data. Please read our privacy statement including an information notice and data protection policy for detailed information on our website.
