[FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of Lynne
> Sent: Sunday, December 26, 2021 5:49 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> 26 Dec 2021, 02:03 by lq at chinaffmpeg.org:
> 
> >
> >
> >> 在 2021年12月26日，上午8:55，lance.lmwang at gmail.com 写道：
> >>
> >> On Sat, Dec 25, 2021 at 05:15:19PM +0000, Soft Works wrote:
> >>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of Lynne
> >>>> Sent: Saturday, December 25, 2021 5:50 PM
> >>>> To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org>
> >>>> Subject: Re: [FFmpeg-devel] GitHub Integration
> >>>>
> >>>> 23 Dec 2021, 00:24 by softworkz at hotmail.com:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> holidays are approaching and I got a little present for all of you
> >>>>> even though it won’t be something for everybody.
> >>>>>
> >>>>> A while ago I had committed to prepare a test setup for integrating
> >>>>> GitHub in a similar way as the Git developers are doing.
> >>>>>
> >>>>> For those who missed it or don’t remember the outcome:
> >>>>> https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/msg123329.html
> >>>>> https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/msg123288.html
> >>>>>
> >>>>> Before someone’s temperature might start rising, I want to repeat
> >>>>> some important corner points:
> >>>>>
> >>>>> - it's not a migration nor the start of a migration
> >>>>> - nothing changes, it doesn't affect anybody's way of working
> >>>>> it doesn't replace anything
> >>>>> - it's an add-on that one could use or not
> >>>>>
> >>>>> Basic functionality is that it allows to submit patches to the ML
> >>>>> through GitHub pull requests.
> >>>>>
> >>>>> Right now must features are working, but e-mails are not sent to
> >>>>> the ML yet, just to one's own e-mail address.
> >>>>>
> >>>>>
> >>>>> I don't want to post the repository location publicly at this time,
> >>>>> but for anybody who would be interested in taking a look at this,
> >>>>> please send me an e-mail or PM me on IRC.
> >>>>>
> >>>>
> >>>> I'd rather we move away from ML development altogether.
> >>>> There's general consensus already, and of course one or
> >>>> two who'd rather not.
> >>>>
> >>>
> >>> I'd prefer that as well, but in back in summer there were quite a number
> >>> of developers (> 2) indicating that they are fine with the
> >>> ML approach, so I'm not really sure about whether and when this
> >>> will happen eventually.
> >>>
> >>> This GitHub-PR-Bridge is not meant to be an alternative or replacement
> >>> for an eventual full migration to another platform.
> >>>
> >>> It's just an interim solution until a migration will eventually happen
> >>> (probably like in the 2030ies.. ;-)
> >>>
> >>
> >> My point:
> >> 1, In China network environment, when accessing Github, the network will
> be
> >> blocked or very slow.
> >> 2, For gmail is blocked, so I prefer to use cli, remote ssh to a cloud
> host,
> >> use mutt/vim for ML email, and scp, and git cli tools are professional to
> do
> >> everything for the patchset send, push etc. Yes, I can use socket5 to
> forward,
> >> but I like cli instead of web for I prefer to use keyboard instead of
> mouse.
> >>
> >
> > +1
> >
> 
> We'd never move to Github, that much's for sure. Videolan already
> hosts a Gitlab instance, and I doubt the great firewall would have an
> issue with that.

I'm not sure. My interpretation of Lance' and Steven's comments would
be that they'd prefer to stick to the ML.

sw