From: "Ronald S. Bultje" <rsbultje@gmail.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, 13 Dec 2022 08:33:29 -0500 Message-ID: <CAEEMt2nQfTANJAuhipCaeyc_R0dfYZFLSbdfXdk-16Y48k9gZg@mail.gmail.com> (raw) In-Reply-To: <003b01d90eed$852039e0$8f60ada0$@samsung.com> Hi David, On Tue, Dec 13, 2022 at 7:22 AM Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics <d.kozinski@samsung.com> wrote: > Should I leave the following lines: > + libxevd.c Dawid Kozinski > + libxeve.c, Dawid Kozinski > + evc.c, evc.h Dawid Kozinski > + evcdec.c Dawid Kozinski > + evc_parser.c Dawid Kozinski > > or should I remove them? > Here's a question for you, and the answer probably becomes self-evident from that. If you, Dawid, stop working for Samsung, for example because you're starting your own business or Samsung fires you or Google hires you, or if Samsung stops sponsoring this new codec called "EVC" or stops contributing to this new library "libxeve". Will you, Dawid, still maintain these files? If the answer is yes, then you can shorten these lines ("evc*.[ch]: Dawid" & "livxev[ed].c: Dawid") and keep them. If the answer is no, then I think you should remove (or adjust) these lines, since they are (in their current form) inaccurate: you are not maintaining these files, your company is. > We are expecting a clear and consistent standpoint on this matter. This makes no sense: our community is a mish-mash of individuals, each entitled to their own opinion. If we - as a community - can't agree, you can ask for a formal opinion from the technical committee. Ronald _______________________________________________ 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:[~2022-12-13 13:33 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 [this message] 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 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=CAEEMt2nQfTANJAuhipCaeyc_R0dfYZFLSbdfXdk-16Y48k9gZg@mail.gmail.com \ --to=rsbultje@gmail.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