From: Vittorio Giovara <vittorio.giovara@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Cherry picks vs merges Date: Mon, 2 Jun 2025 00:46:33 -0400 Message-ID: <CABLWnS9bkiULzhRH3rxZaHi0pM2C-B7wm3gKQBWFTB61HT+Fdw@mail.gmail.com> (raw) In-Reply-To: <20250601213149.GX29660@pb2> On Sun, Jun 1, 2025 at 5:32 PM Michael Niedermayer <michael@niedermayer.cc> wrote: > > I'm not against merging his changes, and i apologize if what i said > before > > sounded like an accusation, but the way i want this to go forward is with > > him being ok with it, and not us trying to find a way to workaround what > was > > seemingly his intention to license his changes a certain way. > > If Paul and everyone agrees, of course thats better and I would prefer > that too. > I don't agree. > But also keep in mind he didnt ask us if he can take our LGPL code. > "our" lgpl code? There is no "our" in a copyleft license. There is authorship that grants permission to use and take the code as needed (and defined by the license) regardless of us, them, or you. > > > That said, with open source and free software it is the morally correct > > > thing, if one makes changes to code, to return these changes to the > parent > > > project under the same license as the parent project. > > > This is morally the ONLY correct thing one can do. > Not unless the maintainers of the original project acted in such a way to split the community irreparably. It happened a bunch of times in the history of foss, for example with xfree, libreoffice and so on: the license change prevented "stealing" contributions and the better codebase with a more mature community took over. What is morally incorrect is trying to solve a social problem in a technical way. At any rate, maybe the TC can intervene and decide what to do? Thanks -- Vittorio _______________________________________________ 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:[~2025-06-02 4:46 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-01 15:22 Michael Niedermayer 2025-06-01 17:12 ` Kieran Kunhya via ffmpeg-devel 2025-06-01 17:27 ` James Almer 2025-06-01 19:23 ` Michael Niedermayer 2025-06-01 19:48 ` compn 2025-06-01 20:01 ` James Almer 2025-06-01 21:31 ` Michael Niedermayer 2025-06-02 4:46 ` Vittorio Giovara [this message] 2025-06-02 15:05 ` Michael Niedermayer 2025-06-02 7:41 ` Marton Balint 2025-06-02 8:23 ` softworkz . 2025-06-02 15:28 ` Michael Niedermayer 2025-06-02 15:57 ` Kieran Kunhya via ffmpeg-devel 2025-06-04 15:20 ` compn 2025-06-01 21:55 ` Kieran Kunhya via ffmpeg-devel 2025-06-02 4:36 ` Baptiste Coudurier 2025-06-02 15:38 ` Rémi Denis-Courmont 2025-06-03 13:09 ` Michael Niedermayer 2025-06-03 22:38 ` Kieran Kunhya via ffmpeg-devel 2025-06-04 14:51 ` Michael Niedermayer 2025-06-04 15:00 ` Kieran Kunhya via ffmpeg-devel 2025-06-04 15:35 ` Rémi Denis-Courmont 2025-06-04 18:06 ` Tomas Härdin 2025-06-04 20:42 ` Baptiste Coudurier 2025-06-04 22:41 ` 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=CABLWnS9bkiULzhRH3rxZaHi0pM2C-B7wm3gKQBWFTB61HT+Fdw@mail.gmail.com \ --to=vittorio.giovara@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