From: "Rémi Denis-Courmont" <remi@remlab.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v6 0/1] avformat: add Software Defined Radio support Date: Sat, 01 Jul 2023 18:28:03 +0300 Message-ID: <8BAC03EA-D4A2-455C-981C-2C92F4E1B5C8@remlab.net> (raw) In-Reply-To: <20230630180236.GC1093384@pb2> Hi, Le 30 juin 2023 21:02:36 GMT+03:00, Michael Niedermayer <michael@niedermayer.cc> a écrit : >On Fri, Jun 30, 2023 at 07:40:53PM +0200, Michael Niedermayer wrote: >> On Fri, Jun 30, 2023 at 04:38:46PM +0200, Jean-Baptiste Kempf wrote: >> > On Fri, 30 Jun 2023, at 16:08, Michael Niedermayer wrote: >> > > Also as said previously, If there is at least a 2nd developer working >> > > on this then we could & should move this to a seperate libraray (libavradio) >> > >> > Why wait for a 2nd dev? >> >> It is significant work > >And if we could put it in git master then people could work together to >build the libavradio out of it as we all want. You can also achieve that by creating a separate git repo for libavradio on git.ffmpeg.org. Admittedly some people could object to hosting this code by FFmpeg; the point is that I don't see what good putting this inside the FFmpeg master git branch achieves. >Such collaboration is kind of one of the reasons of having a "git master" You're better off collaborating with people interested in this, than with the entirety of FFmpeg-devel, me thinks. That's if this turns into a "Boring Serious Open-Source" project to paraphrase a certain somebody else. If it remains just your hobby project, you're probably better off doing it in your own git repository where you can dictate everything. There you won't have to deal with the FFmpeg TC nor pesky minders of other people's source code such as I. >If i cannot apply the patches but have to do very deep redesigns then >it forces me to do all this work alone. That would affect other things >i would otherwise work on. >IMHO its better if everyone can collaborate on this libavradio project >if everyone wants it. That reasoning only makes sense if a sizable subset of FFmpeg people, and even then it would probably fit better in a separate git repository of the same organisation, than in the same git repository. _______________________________________________ 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-07-01 15:28 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-28 21:25 Michael Niedermayer 2023-06-28 21:25 ` [FFmpeg-devel] [PATCH v6] " Michael Niedermayer 2023-06-29 15:43 ` [FFmpeg-devel] [PATCH v6 0/1] " Paul B Mahol 2023-06-30 14:08 ` Michael Niedermayer 2023-06-30 14:38 ` Jean-Baptiste Kempf 2023-06-30 17:40 ` Michael Niedermayer 2023-06-30 17:57 ` Paul B Mahol 2023-06-30 18:02 ` Michael Niedermayer 2023-07-01 15:28 ` Rémi Denis-Courmont [this message] 2023-07-01 18:56 ` Michael Niedermayer 2023-07-01 19:30 ` Paul B Mahol 2023-07-02 9:40 ` Nicolas George 2023-07-02 10:08 ` Paul B Mahol 2023-07-02 13:47 ` Rémi Denis-Courmont 2023-07-02 16:01 ` Nicolas George 2023-07-02 18:21 ` Rémi Denis-Courmont 2023-07-02 11:00 ` Michael Niedermayer 2023-07-02 16:11 ` Nicolas George 2023-07-02 18:55 ` Lynne 2023-07-02 21:14 ` Michael Niedermayer 2023-07-02 22:03 ` Lynne 2023-07-02 22:46 ` Michael Niedermayer 2023-07-10 6:57 ` Lynne 2023-07-11 21:09 ` Michael Niedermayer 2023-06-30 17:00 ` Kieran Kunhya 2023-07-01 15:20 ` Michael Niedermayer 2023-06-30 21:36 ` Martin Storsjö 2023-07-01 14:44 ` Michael Niedermayer 2023-07-01 19:41 ` Martin Storsjö 2023-07-01 19:56 ` Tomas Härdin 2023-07-01 20:06 ` Michael Niedermayer 2023-07-01 20:42 ` Kieran Kunhya 2023-07-01 21:25 ` Michael Niedermayer 2023-07-01 21:32 ` Kieran Kunhya 2023-07-01 19:08 ` Anton Khirnov 2023-07-01 19:35 ` Michael Niedermayer 2023-07-02 9:58 ` Nicolas George 2023-07-02 10:10 ` Paul B Mahol 2023-07-02 10:43 ` Jean-Baptiste Kempf 2023-07-02 16:07 ` Nicolas George 2023-07-02 18:13 ` Jean-Baptiste Kempf 2023-07-02 18:20 ` Nicolas George 2023-07-02 18:32 ` Michael Niedermayer 2023-07-02 18:52 ` Lynne 2023-07-02 19:52 ` Nicolas George 2023-07-02 20:29 ` Lynne 2023-06-30 22:02 ` Tomas Härdin 2023-07-02 9:28 ` Nicolas George
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=8BAC03EA-D4A2-455C-981C-2C92F4E1B5C8@remlab.net \ --to=remi@remlab.net \ --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