From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] STF SoWs Date: Wed, 7 Feb 2024 13:58:20 +0100 Message-ID: <20240207125820.GF6420@pb2> (raw) In-Reply-To: <CAEEMt2nVFjQRr+jGSyOcJtiV9OR1ysu3E=ORAczT7Y26-EQJKg@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2376 bytes --] On Tue, Feb 06, 2024 at 08:38:13PM -0500, Ronald S. Bultje wrote: > Hi, > > On Tue, Feb 6, 2024 at 6:04 PM Michael Niedermayer <michael@niedermayer.cc> > wrote: > > > I think you should sign a SoW that has "Merged in git master" as a > > Deliverable > > > > I already did. It was fine. of course its fine 9 out of 10 times but 1 out of 10 times the customer is unhappy and you are unhappy. I like being transparent and explain this possibility to the customer/buisness partner. because no matter whats written in a contract, sometimes some patches cannot be merged in git master. > > > > PS: do you have a single person willing to sign this Deliverable you > > want ? > > If not, how will the STF thing work ? > > > > You're asking for community input for your proposal, I gave comments as > requested. It's OK to disagree on things, happens all the time. yes, but i was hoping we could find something we both agree on > You can A) > ignore my suggestions and submit the proposal to STF anyway, > B) submit a > proposal to STF as yourself rather than as FFmpeg (but for the same tasks, > on FFmpeg), > C) submit a proposal using another company/non-profit (e.g. > fflabs), > D) not submit a proposal to STF, > or E) something else ??? Its more complex Theres the person writing a SoW for work he wants to do. Theres the person who accepts the SoW in FFmpeg Theres the person who passes accepted SoW on to SPI/STF Iam sadly involved in more than one role here. If everyone including you agree on whats written in the SoW, i think its ok but if you disagree I cannot override or bypass that. That said, we from the point of view of FFmpeg should not promise STF that we can merge code in git master before its written. It could fail and would make the project look bad STF is about maintainance, analyzing bugs, fixing bugs, submitting patches reviewing patches maybe. Promising them that the whole community will accept every change. Which is what "merge to git master" is. Is not needed In fact it might even be counter productive. STF probabyl does not want things to be merged that people do not agree on. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Nations do behave wisely once they have exhausted all other alternatives. -- Abba Eban [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2024-02-07 12:58 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-06 2:06 Michael Niedermayer 2024-02-06 14:18 ` Ronald S. Bultje 2024-02-06 15:04 ` Vittorio Giovara 2024-02-06 15:14 ` Michael Niedermayer 2024-02-06 15:21 ` Ronald S. Bultje 2024-02-06 15:26 ` Michael Niedermayer 2024-02-06 15:41 ` Michael Niedermayer 2024-02-06 16:04 ` Niklas Haas 2024-02-06 17:02 ` Ronald S. Bultje 2024-02-06 18:17 ` Michael Niedermayer 2024-02-06 18:48 ` Paul B Mahol 2024-02-07 12:16 ` Nicolas George 2024-02-07 13:11 ` Rémi Denis-Courmont 2024-02-06 20:53 ` Ronald S. Bultje 2024-02-06 21:23 ` Michael Niedermayer 2024-02-06 21:39 ` Ronald S. Bultje 2024-02-06 23:04 ` Michael Niedermayer 2024-02-07 1:38 ` Ronald S. Bultje 2024-02-07 12:58 ` Michael Niedermayer [this message] 2024-02-07 13:08 ` Ronald S. Bultje 2024-02-07 14:44 ` Michael Niedermayer 2024-02-07 17:31 ` Ronald S. Bultje 2024-02-08 4:08 ` Michael Niedermayer 2024-02-07 19:01 ` Leo Izen 2024-02-07 19:53 ` Michael Niedermayer 2024-02-08 12:32 ` Nicolas George 2024-02-08 12:42 ` epirat07 [not found] ` <1C84A3B8-51FD-4E46-8A61-B0A047606152@cosmin.at> 2024-02-07 2:28 ` Cosmin Stejerean via ffmpeg-devel 2024-02-06 18:48 ` Niklas Haas 2024-02-06 15:59 ` Niklas Haas 2024-02-06 14:57 ` Vittorio Giovara 2024-02-06 15:25 ` 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=20240207125820.GF6420@pb2 \ --to=michael@niedermayer.cc \ --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