From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id C0AF144FBA for ; Tue, 14 Feb 2023 12:10:26 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 2B86568BEAD; Tue, 14 Feb 2023 14:10:23 +0200 (EET) Received: from mailout2.w1.samsung.com (mailout2.w1.samsung.com [210.118.77.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id B98CD68BAEB for ; Tue, 14 Feb 2023 14:10:16 +0200 (EET) Received: from eucas1p1.samsung.com (unknown [182.198.249.206]) by mailout2.w1.samsung.com (KnoxPortal) with ESMTP id 20230214121011euoutp02f915660197c21f9059ed19fe67d1f5eb~Dr6WN8FVL2651026510euoutp02V for ; Tue, 14 Feb 2023 12:10:11 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout2.w1.samsung.com 20230214121011euoutp02f915660197c21f9059ed19fe67d1f5eb~Dr6WN8FVL2651026510euoutp02V DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1676376611; bh=H5HSMymTMTq4+d3OE5/UOA/tCU2tfiLHR/H0OIIx3Vk=; h=From:To:In-Reply-To:Subject:Date:References:From; b=KGV8um66yFokK3szR74rAXbRCmqoCxnLop6c8yJqKTMMnYy/fYuNgXGdlW/QqKxir piUMhfNI/ZzIjrYAlkNG+bzjw6rbgGw1aWQyuyCMfc+rmw4QmfkwLpMrFTqCyemY3Q tHVwx3zVsgHYfOPSj5PlQy3LineTsrcJdYsfrWBg= Received: from eusmges1new.samsung.com (unknown [203.254.199.242]) by eucas1p2.samsung.com (KnoxPortal) with ESMTP id 20230214121011eucas1p241a6b2d5642e320bd6f8921143547177~Dr6V3u53i0675306753eucas1p2T for ; Tue, 14 Feb 2023 12:10:11 +0000 (GMT) Received: from eucas1p1.samsung.com ( [182.198.249.206]) by eusmges1new.samsung.com (EUCPMTA) with SMTP id AD.50.01471.32A7BE36; Tue, 14 Feb 2023 12:10:11 +0000 (GMT) Received: from eusmtrp2.samsung.com (unknown [182.198.249.139]) by eucas1p2.samsung.com (KnoxPortal) with ESMTPA id 20230214121011eucas1p2919ae1f0c133188a51bfcf1345bdd745~Dr6ViQsvT0739707397eucas1p2P for ; Tue, 14 Feb 2023 12:10:11 +0000 (GMT) Received: from eusmgms2.samsung.com (unknown [182.198.249.180]) by eusmtrp2.samsung.com (KnoxPortal) with ESMTP id 20230214121011eusmtrp27d960c0d4c4cd7a3cea78a63d829e4df~Dr6Vho4zR1940219402eusmtrp2V for ; Tue, 14 Feb 2023 12:10:11 +0000 (GMT) X-AuditID: cbfec7f2-2b1ff700000105bf-1d-63eb7a230f93 Received: from eusmtip1.samsung.com ( [203.254.199.221]) by eusmgms2.samsung.com (EUCPMTA) with SMTP id BC.02.00518.32A7BE36; Tue, 14 Feb 2023 12:10:11 +0000 (GMT) Received: from AMDN5164 (unknown [106.210.132.171]) by eusmtip1.samsung.com (KnoxPortal) with ESMTPA id 20230214121010eusmtip16c323bc9b8f4d6a3a25f6d6487a0bcf0~Dr6VNVp1p2651126511eusmtip1F for ; Tue, 14 Feb 2023 12:10:10 +0000 (GMT) From: "Dawid Kozinski/Multimedia \(PLT\) /SRPOL/Staff Engineer/Samsung Electronics" To: "'FFmpeg development discussions and patches'" In-Reply-To: Date: Tue, 14 Feb 2023 13:10:09 +0100 Message-ID: <00ac01d9406d$4932f6f0$db98e4d0$@samsung.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQI7g+IYwVZAkAV+DC9KKbLYwHJMlQLFBuOPAnOBp4IDAdDyeAIUKd8IAKzmdloCKriHLQKANxCvAbSPh38CCgUKsgGt1wKtAks99z6tTuKHYA== Content-Language: pl X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNIsWRmVeSWpSXmKPExsWy7djPc7rKVa+TDe4fEbf49ukMswOjx59F m1kCGKO4bFJSczLLUov07RK4Mu5f2slYsE27om/rIZYGxjlaXYycHBICJhJbfv9n7mLk4hAS WMEocev1WShnEpPEvUm3mCCciUwSZ6/0MsO0THuxgA0isZxR4ltDA1RLG5NE16qLLCBVbAJ5 Eo8/rwXrEBHwkehev54VxOYUUJE4tGQpWFxYIFXiWOdVsHoWAVWJg5e3gsV5BSwlPl9rZ4Sw BSVOznwCVsMsoCfx7NQsKFtbYtnC11AXKUj8fLqMFWJXncT+s3OgakQkbjxqYQQ5TkKgl0Pi zoOtUA0uEg0bDrFD2MISr45vgbJlJP7vnA/0MweQXSxxqN8BwqyROPQjHaLCWuJt43FGCNtR omnnVzaIEj6JG28FIbbySUzaNp0ZIswr0dEmBGGqSPR1ikE0Skk8XTaHeQKj0iwkL85C8uIs JC/OQvLKAkaWVYziqaXFuempxYZ5qeV6xYm5xaV56XrJ+bmbGIHp4fS/4592MM599VHvECMT B+MhRgkOZiURXuGnL5KFeFMSK6tSi/Lji0pzUosPMUpzsCiJ82rbnkwWEkhPLEnNTk0tSC2C yTJxcEo1MAU9Of2l9POO/tIcoRLDyPU/a91rTWJeO/hrysRNOSprb6E/i/3yjSrB2ukK+Ta6 M3q6AvKmi38qLLf711C6xfZ3tdQWjnNsByZ9b/66MGP17bf/vaz101vfHBf+EHagJXMj46Rd YffvhErITj7w+uj/WvP/z7Ln6FmElzrxPb4bszkllOXt5QKX22eE8jwvLnPUf6aclbHiXLq4 TZ7k1r5FEg4h35afXrP556QLotXVH2Zev693k1FWxPbckttPWZwmRXokO5S+5zK3YAxkL8iV Dte5tl2pcuPdXa13HjvuiBeaGLRaX827WjbgxvG5lStdTDPrMxvtWNeear/AmXJQxnju1kqD hS1/vjgmK7EUZyQaajEXFScCAGciovF+AwAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgkeLIzCtJLcpLzFFi42I5/e/4XV3lqtfJBjMPs1p8+3SG2YHR48+i zSwBjFF6NkX5pSWpChn5xSW2StGGFkZ6hpYWekYmlnqGxuaxVkamSvp2NimpOZllqUX6dgl6 GffWb2UuuC1fcXbSN5YGxv+SXYycHBICJhLTXixg62Lk4hASWMoo8f76R1aIhJTE0qWLGCFs YYk/17qgilqYJN7t/8QCkmATyJFYO3siE4gtIuAj0b1+PStE0X9miQWnVoFN4hRQkTi0ZCkz iC0skCzx4NZCsGYWAVWJg5e3gsV5BSwlPl9rZ4SwBSVOznwCVsMsYCCxZOEvJghbW2LZwtfM EBcpSPx8uowVYnGdxP6zc6DqRSRuPGphnMAoNAvJqFlIRs1CMmoWkpYFjCyrGEVSS4tz03OL jfSKE3OLS/PS9ZLzczcxAqNi27GfW3Ywrnz1Ue8QIxMH4yFGCQ5mJRFe4acvkoV4UxIrq1KL 8uOLSnNSiw8xmgL9NpFZSjQ5HxiXeSXxhmYGpoYmZpYGppZmxkrivJ4FHYlCAumJJanZqakF qUUwfUwcnFINTB4VG4K6/+o9yd27avV16WwW9lu+TQrbQj98EF22Zne3ZYvlTHNdi1kfonw1 an0yr3xwCEzSrDxwsNnptR2Dno62e9eMt+W+H49t+Mix6BOf+f0stx0zTc582n1LPEWUn7lz rf/S8nfVD5QUfATtvrpMsTkjz+OwYKfM8vKv0RcuPHvhZvXYUsdKPMBTftWBiZJ7429l370o tpWf64HDI7Xp9+/cvLM5L3N2KKf1pcm9NkvLdt3zyMhz2Xv/jIJgaX8Q69qnoiuST/260DpH 64/OizerF/wU6pbbM5uB7eYEldVaOqfrueYL27v4Ttqq+0Sk81jI3a3x7TynOY7nnrrx11qi 0uzm7JYfPPLCM5RYijMSDbWYi4oTAag6xQMTAwAA X-CMS-MailID: 20230214121011eucas1p2919ae1f0c133188a51bfcf1345bdd745 X-Msg-Generator: CA X-RootMTR: 20230213173227eucas1p1e4f3edf5f68a0de4655ecd20e1784385 X-EPHeader: CA CMS-TYPE: 201P X-CMS-RootMailID: 20230213173227eucas1p1e4f3edf5f68a0de4655ecd20e1784385 References: <003b01d90eed$852039e0$8f60ada0$@samsung.com> <20221214213607.GN3806951@pb2> <00c001d91065$a9d7be10$fd873a30$@samsung.com> <20221215192239.GQ3806951@pb2> <003401d93247$4d542fd0$e7fc8f70$@samsung.com> <20230129095713.GI1949656@pb2> <005601d93f8d$90b5ea40$b221bec0$@samsung.com> Subject: Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in Changelog and MAINTAINERS files X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: -----Original Message----- From: ffmpeg-devel On Behalf Of Lynne Sent: poniedzia=B3ek, 13 lutego 2023 18:32 To: FFmpeg development discussions and patches Subject: Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in Changelog and MAINTAINERS files Feb 13, 2023, 10:29 by d.kozinski@samsung.com: > Lynne, if it concerns us, we will comply with both the current and the = > new maintainership policy once your patchset is pushed. We see that = > your change has not yet been pushed into the main branch, and it = > appears that the discussion on this topic may still be ongoing, = > although both Michael and other maintainers have reviewed and commented on it. > What do you mean both current and new policy? Lynne, you mentioned a new policy change on maintainership in one of the previous emails: "I assign myself to personally review the patchset and push it, if you review my policy change on maintainership. As I said, I have no objection on who gets maintainership, just that it is done explicitly via a separate list in the maintainers file." New Policy =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Your proposal is for a separate list of developers who have write access to the GIT repository [new policy] (https://patchwork.ffmpeg.org/project/ffmpeg/patch/NJIL3BF--3-9@lynne.ee/) Current Policy =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Currently, the MAINTAINERS file has one list of developers who may or may not have write access. The MAINTAINERS file currently contains one list of developers who may or may not have write access to the GIT. Unfortunately, there are significant discrepancies regarding who should be on this list and what rights they should have: Some ffmpeg maintainers argue that those on the list may not necessarily have write access but may qualify for access to publish changes. Being on this list gives them the right to reject (negative acknowledgement - NAK) a set of changes related to the module they are responsible for and (ideally) requires their approval before making any changes to the module. Others, like Lynne, believe that the list should only exist for those who have write access ("... that list is only for those with push access"). Only developers who have contributed to the project and understand that maintaining a repository requires a certain level of dedication should be included on the list. There are also those who believe that developers who care about a piece of code should have write access if they ask for it. Each developer who takes care of a bit of the code base (reviewing patches, approving them, fixing issues, adding features, ...) has the same rights as others. At the moment, it doesn't matter to us whether there are two lists or one. What matters to us is pushing our patchset containing an EVC codec wrapper to ffmpeg. We want to refine and maintain this code and have the information somewhere about who is responsible for it (EVC) and who to contact with questions. We hope that our patchset will eventually be accepted, and we will then apply for write access to Git because we want to take care of the EVC code. We would like to separate these 2 topics, the mainteiners list and the EVC patch. At this point our patch seems to be in line with the current policy. If anyone has any comments regarding a particular MAINTENANCE file related to our patchset, please make comments. Our EVC patch does not change MAINTENANCE policy. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://protect2.fireeye.com/v1/url?k=3D9790493d-f61b5c0e-9791c272-000babff= 9bb 7-cf6035a5089c4d08&q=3D1&e=3D1d26169f-514c-456d-9439-ef58a866852d&u=3Dhttps= %3A%2F% 2Fffmpeg.org%2Fmailman%2Flistinfo%2Fffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".