From: "Dawid Kozinski/Multimedia \(PLT\) /SRPOL/Staff Engineer/Samsung Electronics" <d.kozinski@samsung.com> To: "'FFmpeg development discussions and patches'" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in Changelog and MAINTAINERS files Date: Tue, 14 Feb 2023 13:10:09 +0100 Message-ID: <00ac01d9406d$4932f6f0$db98e4d0$@samsung.com> (raw) In-Reply-To: <NOApMGF--B-9@lynne.ee> -----Original Message----- From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne Sent: poniedziałek, 13 lutego 2023 18:32 To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> 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 ========== 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 ============== 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=9790493d-f61b5c0e-9791c272-000babff9bb 7-cf6035a5089c4d08&q=1&e=1d26169f-514c-456d-9439-ef58a866852d&u=https%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".
next prev parent reply other threads:[~2023-02-14 12:10 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20221024074233eucas1p125b43125cce202641bf48d0f174a39a1@eucas1p1.samsung.com> 2022-10-24 7:42 ` Dawid Kozinski 2022-10-24 15:56 ` Lynne 2022-10-24 16:29 ` James Almer 2022-10-25 11:17 ` Lynne 2022-10-27 16:45 ` Michael Niedermayer 2022-10-28 21:08 ` Lynne 2022-12-13 12:22 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2022-12-13 13:33 ` Ronald S. Bultje 2022-12-14 13:02 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2022-12-14 21:36 ` Michael Niedermayer 2022-12-15 9:14 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2022-12-15 19:22 ` Michael Niedermayer 2023-01-27 12:03 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2023-01-29 9:57 ` Michael Niedermayer 2023-01-29 23:18 ` Lynne 2023-02-06 8:46 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2023-02-13 9:28 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2023-02-13 17:32 ` Lynne 2023-02-14 12:10 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics [this message] 2023-02-14 18:00 ` Lynne 2023-02-15 8:50 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2023-03-06 10:46 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2023-03-18 17:53 ` Lynne 2023-03-21 9:22 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2023-02-14 18:03 ` Kieran Kunhya 2023-02-15 8:49 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2023-02-15 13:05 ` Kieran Kunhya 2023-02-16 8:49 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2023-01-02 13:07 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2022-12-13 18:42 ` Lynne 2022-12-14 12:54 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2022-12-14 21:45 ` Michael Niedermayer 2022-12-15 1:11 ` Lynne 2022-12-15 19:15 ` Michael Niedermayer
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='00ac01d9406d$4932f6f0$db98e4d0$@samsung.com' \ --to=d.kozinski@samsung.com \ --cc=ffmpeg-devel@ffmpeg.org \ /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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git