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: Thu, 16 Feb 2023 09:49:18 +0100 Message-ID: <014101d941e3$8ea48ab0$abeda010$@samsung.com> (raw) In-Reply-To: <CAK+ULv5trD6ocj48mYWZQaE-P+JPEv5j9MYkrhiFuOSvS2RX9Q@mail.gmail.com> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Kieran > Kunhya > Sent: środa, 15 lutego 2023 14:05 > 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 > > On Wed, 15 Feb 2023 at 08:49, Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff > Engineer/Samsung Electronics <d.kozinski@samsung.com> wrote: > > > > > Dear Kieran, > > > > While I appreciate your concerns, I must point out that the issues you > > mentioned regarding the maintenance of third-party libraries are not > > limited to corporate contributors. People change jobs and their focus > > may change, but this is not exclusive to those working for > > corporations. Furthermore, it is not necessarily the case that someone > > who has maintained a particular part of code in a project like FFmpeg > > will abruptly cease doing so upon changing jobs. > > > > I believe it's important to consider each individual's level of > > commitment to a project, rather than making assumptions based on > > generalizations. It's also worth noting that while there may have been > > issues with maintaining patches to certain third-party libraries in > > the past, it doesn't mean that it will be each and every time. > > > > Regards > > Dawid > > > > Whilst all of this is true, the community is able to pick up when it's an internal > FFmpeg component. > When it's a third-party library on another person's Github, the community can't > do that. > > Kieran We understand your concern about the fact that the community may not have the same level of control over third-party libraries outside of the internal FFmpeg components. However, our implementation of the EVC codec is available on GitHub (https://github.com/mpeg5/xeve https://github.com/mpeg5/xevd ) under the BSD license, which means that anyone can review and contribute to the code. Are there no other third-party libraries in the FFMpeg? > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://protect2.fireeye.com/v1/url?k=2f1fcb67-7084f26b-2f1e4028- > 000babff3563-4c32b86914b34023&q=1&e=64a9b64e-ef38-4603-9d17- > 6eaf2a80eb0d&u=https%3A%2F%2Fffmpeg.org%2Fmailman%2Flistinfo%2Fffmp > eg-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-16 8:49 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 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 [this message] 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='014101d941e3$8ea48ab0$abeda010$@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