[FFmpeg-devel] GitHub Integration

[FFmpeg-devel] GitHub Integration

[Soft Works]

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.


Kind regards,
softworkz




_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Paul B Mahol]

Topic name is deeply misleading.
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Paul B
> Mahol
> Sent: Thursday, December 23, 2021 8:36 AM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> Topic name is deeply misleading.

What would you say?
Bridge, Interface, Gateway, Connection, Connector..?
I don't know.


The interactive component that "talks" to you for getting
things ready to submit goes by the name "FFmpeg CodeBot"

sw
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Tomas Härdin]

ons 2021-12-22 klockan 23:24 +0000 skrev Soft Works:
> 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.

This sounds like something that will cause problems in the long run.
Github will inevitably be brought into the project's workflow. People
will start submitting tickets on Github rather than our trac. And so
on.

/Tomas

_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Tomas
> Härdin
> Sent: Thursday, December 23, 2021 3:00 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> ons 2021-12-22 klockan 23:24 +0000 skrev Soft Works:
> > 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.
> 
> This sounds like something that will cause problems in the long run.
> Github will inevitably be brought into the project's workflow. People
> will start submitting tickets on Github rather than our trac. And so
> on.

Issues are disabled and hidden.

sw
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Timo Rothenpieler]

[-- Attachment #1.1: Type: text/plain, Size: 349 bytes --]

On 23.12.2021 14:59, Tomas Härdin wrote:
> This sounds like something that will cause problems in the long run.
> Github will inevitably be brought into the project's workflow. People
> will start submitting tickets on Github rather than our trac. And so
> on.

issues are disabled on Github.
Otherwise, they'd be used for that constantly already.

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4494 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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Timo
> Rothenpieler
> Sent: Thursday, December 23, 2021 3:17 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> On 23.12.2021 14:59, Tomas Härdin wrote:
> > This sounds like something that will cause problems in the long run.
> > Github will inevitably be brought into the project's workflow. People
> > will start submitting tickets on Github rather than our trac. And so
> > on.
> 
> issues are disabled on Github.
> Otherwise, they'd be used for that constantly already.

The test setup is located in a separate repository right now.
(anybody just drop me a note and I'll send the link)

What's also important to mention is that the pull request conversations
are looped through the mailing list. There is no side-stepping or 
splitting of conversations: nobody on the ML will miss anything important,
except all the pre-submission validation. There are various checks
performed before a user can even submit, and we can also make it 
mandatory that compilation does not error and FATE tests are being 
passed, so patchsets won't even hit the ML otherwise.

Kind regards,
softworkz


_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: Soft Works
> Sent: Thursday, December 23, 2021 12:25 AM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: GitHub Integration
> 
> 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

I think I should add a quick summary on this subject for all those
who haven't followed the discussion in August.

The Git project (https://git-scm.com/) has a similar problem like 
ffmpeg: There are a number of long-time core developers that are 
strictly rejecting to move away from the ML based approach.
That's how GitGitGadget came to life, intending to bridge that gap.

Adopting that approach for ffmpeg has a number of advantages:

- we can skip the "learning process", i.e. finding out what works
  in practical use and what doesn't
- what has found acceptance at their project - given the similar 
  profile of the developers involved - will likely be acceptable 
  for ffmpeg as well (roughly at least)
- the part that I like most is: even without explicit acceptance -
  this approach doesn't leave much room for objection, because it 
  doesn't impose any changes or drawback to the way people are 
  working with the ML


Here's a rough overview about how it's working:

- User submits a PR to the GitHub repo

- When it's a user's first PR, the ffmpeg-codebot will 
  respond with a very comprehensive message (as PR comment),
  explaining the procedures and providing an overview about
  contributing to ffmpeg with links to the individual topics 
  on the ffmpeg website regarding contributing.

- The message further explains that first-time users are not
  allowed to submit immediately, and that a user needs to
  find and contact another developer who is allowed to make
  submissions and ask that developer to vouch for him.

- Every developer who has been allowed to submit can vouch
  for a first-time submitter
  It is done by adding a comment containing "/allow" to the
  first-time user's PR

- Upon submitting the PR (no matter whether first-time or existing
  submitter), the code bot will likely have posted some other 
  comments, indicating which changes need to be made to the  
  patchset before it can be submitted.

- The user addresses those changes and then force-pushes the branch
  to GitHub, the code bot re-runs all checks and when all 
  requirements are met (and only then), the user will be 
  able to submit.
  This is done by posting a comment to the PR containing "/submit"
  The code bot will automatically create the patch e-mails and 
  send them to the ML.
  (it's also possible to post "/preview" to get the same e-mails
  created but only sent to a user's own e-mail account)

- Comments that are made on the ML are mirrored back to the GitHub
  PR as comments. The other way is not yet implemented, so at this
  point, a user will need to respond through the ML (that's 
  clearly indicated).
  I hope this will be implemented soon, it's not easy though to
  do it in a nice way without repeating all those quoted lines 
  each time

What's really like is the way how you submit new versions of 
a patchset:

- After having applied the changes locally, you just (force-) push
  the branch again, and post another comment with "/submit"
  Everything is done automatically then: the patchset version 
  number is increased, new patches are generated and sent to the ML

Kind regards,
softworkz 









_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Vasily]

Hi,

First off, a great idea bridging that gap! But I agree that the topic is
misleading, maybe rename to smth like "github bridge for PR creation" to be
really explicit?

Second one, why first-comers aren't allowed to submit without pre-approval?
(context: I haven't made my contributions to ffmpeg yet, though posted a
single patch which stalled at review because of lack of my time).

And last point - if comments from github aren't re-posted to the list,
maybe the boy should remove them or edit by removing the message and
telling the commenter to use the ML?

Anyway, good idea!

Thanks, Vasily


пт, 24 дек. 2021 г., 1:30 Soft Works <softworkz@hotmail.com>:

>
>
> > -----Original Message-----
> > From: Soft Works
> > Sent: Thursday, December 23, 2021 12:25 AM
> > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > Subject: GitHub Integration
> >
> > 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
>
> I think I should add a quick summary on this subject for all those
> who haven't followed the discussion in August.
>
> The Git project (https://git-scm.com/) has a similar problem like
> ffmpeg: There are a number of long-time core developers that are
> strictly rejecting to move away from the ML based approach.
> That's how GitGitGadget came to life, intending to bridge that gap.
>
> Adopting that approach for ffmpeg has a number of advantages:
>
> - we can skip the "learning process", i.e. finding out what works
>   in practical use and what doesn't
> - what has found acceptance at their project - given the similar
>   profile of the developers involved - will likely be acceptable
>   for ffmpeg as well (roughly at least)
> - the part that I like most is: even without explicit acceptance -
>   this approach doesn't leave much room for objection, because it
>   doesn't impose any changes or drawback to the way people are
>   working with the ML
>
>
> Here's a rough overview about how it's working:
>
> - User submits a PR to the GitHub repo
>
> - When it's a user's first PR, the ffmpeg-codebot will
>   respond with a very comprehensive message (as PR comment),
>   explaining the procedures and providing an overview about
>   contributing to ffmpeg with links to the individual topics
>   on the ffmpeg website regarding contributing.
>
> - The message further explains that first-time users are not
>   allowed to submit immediately, and that a user needs to
>   find and contact another developer who is allowed to make
>   submissions and ask that developer to vouch for him.
>
> - Every developer who has been allowed to submit can vouch
>   for a first-time submitter
>   It is done by adding a comment containing "/allow" to the
>   first-time user's PR
>
> - Upon submitting the PR (no matter whether first-time or existing
>   submitter), the code bot will likely have posted some other
>   comments, indicating which changes need to be made to the
>   patchset before it can be submitted.
>
> - The user addresses those changes and then force-pushes the branch
>   to GitHub, the code bot re-runs all checks and when all
>   requirements are met (and only then), the user will be
>   able to submit.
>   This is done by posting a comment to the PR containing "/submit"
>   The code bot will automatically create the patch e-mails and
>   send them to the ML.
>   (it's also possible to post "/preview" to get the same e-mails
>   created but only sent to a user's own e-mail account)
>
> - Comments that are made on the ML are mirrored back to the GitHub
>   PR as comments. The other way is not yet implemented, so at this
>   point, a user will need to respond through the ML (that's
>   clearly indicated).
>   I hope this will be implemented soon, it's not easy though to
>   do it in a nice way without repeating all those quoted lines
>   each time
>
> What's really like is the way how you submit new versions of
> a patchset:
>
> - After having applied the changes locally, you just (force-) push
>   the branch again, and post another comment with "/submit"
>   Everything is done automatically then: the patchset version
>   number is increased, new patches are generated and sent to the ML
>
> Kind regards,
> softworkz
>
>
>
>
>
>
>
>
>
> _______________________________________________
> 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".
>
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Vasily]

Typo correction: "the bot should remove", not "the boy" (oh my mobile
tapping...)

сб, 25 дек. 2021 г., 12:31 Vasily <just.one.man@yandex.ru>:

> Hi,
>
> First off, a great idea bridging that gap! But I agree that the topic is
> misleading, maybe rename to smth like "github bridge for PR creation" to be
> really explicit?
>
> Second one, why first-comers aren't allowed to submit without
> pre-approval? (context: I haven't made my contributions to ffmpeg yet,
> though posted a single patch which stalled at review because of lack of my
> time).
>
> And last point - if comments from github aren't re-posted to the list,
> maybe the boy should remove them or edit by removing the message and
> telling the commenter to use the ML?
>
> Anyway, good idea!
>
> Thanks, Vasily
>
>
> пт, 24 дек. 2021 г., 1:30 Soft Works <softworkz@hotmail.com>:
>
>>
>>
>> > -----Original Message-----
>> > From: Soft Works
>> > Sent: Thursday, December 23, 2021 12:25 AM
>> > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org
>> >
>> > Subject: GitHub Integration
>> >
>> > 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
>>
>> I think I should add a quick summary on this subject for all those
>> who haven't followed the discussion in August.
>>
>> The Git project (https://git-scm.com/) has a similar problem like
>> ffmpeg: There are a number of long-time core developers that are
>> strictly rejecting to move away from the ML based approach.
>> That's how GitGitGadget came to life, intending to bridge that gap.
>>
>> Adopting that approach for ffmpeg has a number of advantages:
>>
>> - we can skip the "learning process", i.e. finding out what works
>>   in practical use and what doesn't
>> - what has found acceptance at their project - given the similar
>>   profile of the developers involved - will likely be acceptable
>>   for ffmpeg as well (roughly at least)
>> - the part that I like most is: even without explicit acceptance -
>>   this approach doesn't leave much room for objection, because it
>>   doesn't impose any changes or drawback to the way people are
>>   working with the ML
>>
>>
>> Here's a rough overview about how it's working:
>>
>> - User submits a PR to the GitHub repo
>>
>> - When it's a user's first PR, the ffmpeg-codebot will
>>   respond with a very comprehensive message (as PR comment),
>>   explaining the procedures and providing an overview about
>>   contributing to ffmpeg with links to the individual topics
>>   on the ffmpeg website regarding contributing.
>>
>> - The message further explains that first-time users are not
>>   allowed to submit immediately, and that a user needs to
>>   find and contact another developer who is allowed to make
>>   submissions and ask that developer to vouch for him.
>>
>> - Every developer who has been allowed to submit can vouch
>>   for a first-time submitter
>>   It is done by adding a comment containing "/allow" to the
>>   first-time user's PR
>>
>> - Upon submitting the PR (no matter whether first-time or existing
>>   submitter), the code bot will likely have posted some other
>>   comments, indicating which changes need to be made to the
>>   patchset before it can be submitted.
>>
>> - The user addresses those changes and then force-pushes the branch
>>   to GitHub, the code bot re-runs all checks and when all
>>   requirements are met (and only then), the user will be
>>   able to submit.
>>   This is done by posting a comment to the PR containing "/submit"
>>   The code bot will automatically create the patch e-mails and
>>   send them to the ML.
>>   (it's also possible to post "/preview" to get the same e-mails
>>   created but only sent to a user's own e-mail account)
>>
>> - Comments that are made on the ML are mirrored back to the GitHub
>>   PR as comments. The other way is not yet implemented, so at this
>>   point, a user will need to respond through the ML (that's
>>   clearly indicated).
>>   I hope this will be implemented soon, it's not easy though to
>>   do it in a nice way without repeating all those quoted lines
>>   each time
>>
>> What's really like is the way how you submit new versions of
>> a patchset:
>>
>> - After having applied the changes locally, you just (force-) push
>>   the branch again, and post another comment with "/submit"
>>   Everything is done automatically then: the patchset version
>>   number is increased, new patches are generated and sent to the ML
>>
>> Kind regards,
>> softworkz
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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".
>>
>
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 1018 bytes --]

On Sat, Dec 25, 2021 at 12:31:56PM +0300, Vasily wrote:
> Hi,
> 
> First off, a great idea bridging that gap! But I agree that the topic is
> misleading, maybe rename to smth like "github bridge for PR creation" to be
> really explicit?
> 

> Second one, why first-comers aren't allowed to submit without pre-approval?

Some pull requests on github where "spam" iam not sure how exactly these happen
maybe someoen pressing the wrong buttons, or someone not understanding github
pull requests for random branches like for example our release branch onto
master or something like this has been submitted IIRC. On github its a matter
of closing the request, but if that resulted in a post to the ML it could
produce hundreads of mails. So some sort of pre-approval or some other sort
of double check that a submissing is intended is required

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No snowflake in an avalanche ever feels responsible. -- Voltaire

[-- 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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael
> Niedermayer
> Sent: Saturday, December 25, 2021 12:12 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> On Sat, Dec 25, 2021 at 12:31:56PM +0300, Vasily wrote:
> > Hi,
> >
> > First off, a great idea bridging that gap! But I agree that the topic is
> > misleading, maybe rename to smth like "github bridge for PR creation" to be
> > really explicit?
> >
> 
> > Second one, why first-comers aren't allowed to submit without pre-approval?
> 
> Some pull requests on github where "spam" iam not sure how exactly these
> happen
> maybe someoen pressing the wrong buttons, or someone not understanding github
> pull requests for random branches like for example our release branch onto
> master or something like this has been submitted IIRC. On github its a matter
> of closing the request, but if that resulted in a post to the ML it could
> produce hundreads of mails. So some sort of pre-approval or some other sort
> of double check that a submissing is intended is required

Yea, exactly. Hadn’t seen your reply, just gave the same answer :-)

softworkz
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Vasily
> Sent: Saturday, December 25, 2021 10:32 AM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> Hi,
> 
> First off, a great idea bridging that gap! But I agree that the topic is
> misleading, maybe rename to smth like "github bridge for PR creation" to be
> really explicit?

Agreed. Once I start another conversation for the next step, I'll try to 
choose a better subject.

> Second one, why first-comers aren't allowed to submit without pre-approval?
> (context: I haven't made my contributions to ffmpeg yet, though posted a
> single patch which stalled at review because of lack of my time).

Ah yes, that's a good question. When we had discussed this back in August,
there were concerns that this might cause a certain amount of hoax-, nonsense-
or low-quality patches to hit the mailing list.
And that's what it's about. The "pre-approval" for first-posters is not 
meant to be a review. Reviews are done on the mailing list, just like usual.

This is intended to a rather low bar and all that an "already allowed" user
is expected to do is to take a very quick look at the submitted PR, whether 
it _appears_ to be a reasonable contribution.

> And last point - if comments from github aren't re-posted to the list,
> maybe the boy should remove them or edit by removing the message and
> telling the commenter to use the ML?

Messages from the ML which are shown on GitHub are always including a 
"Reply-To" link with instruction about how to reply.

> Anyway, good idea!

Drop me a note, then I'll send you the link where you can try it out.

Regards,
softworkz
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Lynne]

23 Dec 2021, 00:24 by softworkz@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.
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
> Sent: Saturday, December 25, 2021 5:50 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> 23 Dec 2021, 00:24 by softworkz@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.. ;-)

softworkz


_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[lance.lmwang]

On Sat, Dec 25, 2021 at 05:15:19PM +0000, Soft Works wrote:
> 
> 
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
> > Sent: Saturday, December 25, 2021 5:50 PM
> > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] GitHub Integration
> > 
> > 23 Dec 2021, 00:24 by softworkz@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.

> 
> softworkz
> 
> 
> _______________________________________________
> 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".

-- 
Thanks,
Limin Wang
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Steven Liu]

> 在 2021年12月26日，上午8:55，lance.lmwang@gmail.com 写道：
> 
> On Sat, Dec 25, 2021 at 05:15:19PM +0000, Soft Works wrote:
>> 
>> 
>>> -----Original Message-----
>>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
>>> Sent: Saturday, December 25, 2021 5:50 PM
>>> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
>>> Subject: Re: [FFmpeg-devel] GitHub Integration
>>> 
>>> 23 Dec 2021, 00:24 by softworkz@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

> 
>> 
>> softworkz
>> 
>> 
>> _______________________________________________
>> 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".
> 
> -- 
> Thanks,
> Limin Wang
> _______________________________________________
> 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".



_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Lynne]

26 Dec 2021, 02:03 by lq@chinaffmpeg.org:

>
>
>> 在 2021年12月26日，上午8:55，lance.lmwang@gmail.com 写道：
>>
>> On Sat, Dec 25, 2021 at 05:15:19PM +0000, Soft Works wrote:
>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
>>>> Sent: Saturday, December 25, 2021 5:50 PM
>>>> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
>>>> Subject: Re: [FFmpeg-devel] GitHub Integration
>>>>
>>>> 23 Dec 2021, 00:24 by softworkz@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.
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
> Sent: Sunday, December 26, 2021 5:49 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> 26 Dec 2021, 02:03 by lq@chinaffmpeg.org:
> 
> >
> >
> >> 在 2021年12月26日，上午8:55，lance.lmwang@gmail.com 写道：
> >>
> >> On Sat, Dec 25, 2021 at 05:15:19PM +0000, Soft Works wrote:
> >>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
> >>>> Sent: Saturday, December 25, 2021 5:50 PM
> >>>> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> >>>> Subject: Re: [FFmpeg-devel] GitHub Integration
> >>>>
> >>>> 23 Dec 2021, 00:24 by softworkz@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
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Ronald S. Bultje]

Hi,

On Sun, Dec 26, 2021 at 3:21 PM Soft Works <softworkz@hotmail.com> wrote:

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

No, it's not strictly related to that - they want something that is CLI
accessible. Gitlab has this here: https://glab.readthedocs.io/en/latest/
and github has this here: https://github.com/cli/cli - the next question is
whether the gitlab/hub hosts are blocked by a firewall (no idea) and/or
whether the instances are self-hosted (github: no, gitlab-videolan: yes).

Ronald
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Ronald S.
> Bultje
> Sent: Sunday, December 26, 2021 10:38 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> Hi,
> 
> On Sun, Dec 26, 2021 at 3:21 PM Soft Works <softworkz@hotmail.com> wrote:
> 
> > I'm not sure. My interpretation of Lance' and Steven's comments would
> > be that they'd prefer to stick to the ML.
> >
> 
> No, it's not strictly related to that - they want something that is CLI
> accessible. Gitlab has this here: https://glab.readthedocs.io/en/latest/
> and github has this here: https://github.com/cli/cli - the next question is
> whether the gitlab/hub hosts are blocked by a firewall (no idea) and/or
> whether the instances are self-hosted (github: no, gitlab-videolan: yes).

Agreed. For the submission part, there are CLI options in both cases.
Also true for both cases: the discussion part would change to WWW.

But I'm probably the very last one here to advocate staying with the ML.
Even though I'd prefer GitHub, I would welcome a move to GitLab as well,
and when something like GitGitGadget would have existed for GitLab instead
of GitHub, then I would have adopted that instead.

Looking back at the discussion in August, where I made these suggestions,
a lot of developers had responded, indicating their satisfaction with the
ML approach (some even defending it strongly). Just very few indicated
support for a move to either GitHub or GitLab.

Off-list, I've seen some who were claiming that a majority would exist,
favoring a move to GitLab. That would be great, but I'm not seeing it.
Where is that majority and why do so few of them speak up, then?

After reading the ML for several years, and from what I've learned about
the group interaction dynamics, my assessment is, that a migration
away from the ML is unlikely to happen in a short-term future.
Those who don't want to move are just on standby, waiting for the next
attempt to be made in order to turn it down once again, and those who
would like to move, are sufficiently satisfied by the thought
alone that a move to GitLab would happen "soon". 
Most likely, by the end of 2022, the situation will just be the same.

On the other side, the "GitHub Gateway/Integration" with the 
ffmpeg-codebot is available right now and able to bridge
the gap between ML and more modern and integrated development workflows.
It's not meant to replace, avoid or compete with an actual migration,
and when a migration would happen e.g. to GitLab, it will be still useful
to have a bot on GitHub that either mirrors PRs from GitHub or just 
auto-closes them with an appropriate message.

Somebody said on IRC that the GH integration might only delay a real 
migration away from the ML.
But I'm seeing it somewhat differently: this might rather serve as an 
indication for which approach will be preferred by the majority, maybe
even accelerating a final migration.

Kind regards,
softworkz








_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[lance.lmwang]

On Sun, Dec 26, 2021 at 04:37:54PM -0500, Ronald S. Bultje wrote:
> Hi,
> 
> On Sun, Dec 26, 2021 at 3:21 PM Soft Works <softworkz@hotmail.com> wrote:
> 
> > I'm not sure. My interpretation of Lance' and Steven's comments would
> > be that they'd prefer to stick to the ML.
> >
> 
> No, it's not strictly related to that - they want something that is CLI
> accessible. Gitlab has this here: https://glab.readthedocs.io/en/latest/
> and github has this here: https://github.com/cli/cli - the next question is
> whether the gitlab/hub hosts are blocked by a firewall (no idea) and/or
> whether the instances are self-hosted (github: no, gitlab-videolan: yes).

Yes, self-hosted is more preferable, I recall github has blocked devleopers
in some country by US trade controls. Who knows what's the rules will be
changed someday as it's controlled by company.

> 
> Ronald
> _______________________________________________
> 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".

-- 
Thanks,
Limin Wang
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Zane van Iperen]

On 27/12/21 11:41, lance.lmwang@gmail.com wrote:
> On Sun, Dec 26, 2021 at 04:37:54PM -0500, Ronald S. Bultje wrote:
>> Hi,
>>
>> On Sun, Dec 26, 2021 at 3:21 PM Soft Works <softworkz@hotmail.com> wrote:
>>
>>> I'm not sure. My interpretation of Lance' and Steven's comments would
>>> be that they'd prefer to stick to the ML.
>>>
>>
>> No, it's not strictly related to that - they want something that is CLI
>> accessible. Gitlab has this here: https://glab.readthedocs.io/en/latest/
>> and github has this here: https://github.com/cli/cli - the next question is
>> whether the gitlab/hub hosts are blocked by a firewall (no idea) and/or
>> whether the instances are self-hosted (github: no, gitlab-videolan: yes).
> 
> Yes, self-hosted is more preferable, I recall github has blocked devleopers
> in some country by US trade controls. Who knows what's the rules will be
> changed someday as it's controlled by company.
> 

Something that doesn't require another account would be nice, which is why
I like mailing lists. Although in this case a move to GitHub wouldn't affect me
personally (I use it a lot) - if I didn't, I would seriously reconsider if the mental
overhead of yet another account (and all the baggage that comes with it - passwords, MFA,
data breaches, etc.) is worth contributing to the project.

Ideally, something self-hosted like Gitea or GitLab with a federated approach (i.e. ForgeFed)
would be fantastic for a case such as this. I'm not sure about GitLab, but I know Gitea is
working towards this.


_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Vasily]

Not advocating for github (per this thread it's out of scope), but I think
using a self-hosted gitlab with an option to auth using github account
would help in reducing the "account overhead" at least for those who use
github.

пн, 27 дек. 2021 г., 17:59 Zane van Iperen <zane@zanevaniperen.com>:

>
>
> On 27/12/21 11:41, lance.lmwang@gmail.com wrote:
> > On Sun, Dec 26, 2021 at 04:37:54PM -0500, Ronald S. Bultje wrote:
> >> Hi,
> >>
> >> On Sun, Dec 26, 2021 at 3:21 PM Soft Works <softworkz@hotmail.com>
> wrote:
> >>
> >>> I'm not sure. My interpretation of Lance' and Steven's comments would
> >>> be that they'd prefer to stick to the ML.
> >>>
> >>
> >> No, it's not strictly related to that - they want something that is CLI
> >> accessible. Gitlab has this here:
> https://glab.readthedocs.io/en/latest/
> >> and github has this here: https://github.com/cli/cli - the next
> question is
> >> whether the gitlab/hub hosts are blocked by a firewall (no idea) and/or
> >> whether the instances are self-hosted (github: no, gitlab-videolan:
> yes).
> >
> > Yes, self-hosted is more preferable, I recall github has blocked
> devleopers
> > in some country by US trade controls. Who knows what's the rules will be
> > changed someday as it's controlled by company.
> >
>
> Something that doesn't require another account would be nice, which is why
> I like mailing lists. Although in this case a move to GitHub wouldn't
> affect me
> personally (I use it a lot) - if I didn't, I would seriously reconsider if
> the mental
> overhead of yet another account (and all the baggage that comes with it -
> passwords, MFA,
> data breaches, etc.) is worth contributing to the project.
>
> Ideally, something self-hosted like Gitea or GitLab with a federated
> approach (i.e. ForgeFed)
> would be fantastic for a case such as this. I'm not sure about GitLab, but
> I know Gitea is
> working towards this.
>
>
> _______________________________________________
> 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".
>
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Niklas Haas]

On Tue, 28 Dec 2021 00:59:58 +1000 Zane van Iperen <zane@zanevaniperen.com> wrote:
> 
> 
> On 27/12/21 11:41, lance.lmwang@gmail.com wrote:
> > On Sun, Dec 26, 2021 at 04:37:54PM -0500, Ronald S. Bultje wrote:
> >> Hi,
> >>
> >> On Sun, Dec 26, 2021 at 3:21 PM Soft Works <softworkz@hotmail.com> wrote:
> >>
> >>> I'm not sure. My interpretation of Lance' and Steven's comments would
> >>> be that they'd prefer to stick to the ML.
> >>>
> >>
> >> No, it's not strictly related to that - they want something that is CLI
> >> accessible. Gitlab has this here: https://glab.readthedocs.io/en/latest/
> >> and github has this here: https://github.com/cli/cli - the next question is
> >> whether the gitlab/hub hosts are blocked by a firewall (no idea) and/or
> >> whether the instances are self-hosted (github: no, gitlab-videolan: yes).
> > 
> > Yes, self-hosted is more preferable, I recall github has blocked devleopers
> > in some country by US trade controls. Who knows what's the rules will be
> > changed someday as it's controlled by company.
> > 
> 
> Something that doesn't require another account would be nice, which is why
> I like mailing lists.

I don't understand, isn't this an argument in favor of GitHub? Most
mailing lists (including, notably, FFmpeg's) require registration in
order to submit messages, which is one of the reasons I hate them. It's
not just that registration is annoying in general, it's also that
registration to a mailing list is *more* annoying and cumbersome than
creating an account on any post-90s website.

Conversely on GitHub, everybody already has an account, so the overhead
for first-time contribution is *actually* zero. And on every other
self-hosted GitLab instance I've come across, I could cross-authenticate
with some other account I already have.
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Niklas Haas
> Sent: Tuesday, December 28, 2021 10:22 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> On Tue, 28 Dec 2021 00:59:58 +1000 Zane van Iperen <zane@zanevaniperen.com>
> wrote:
> >
> >
> > On 27/12/21 11:41, lance.lmwang@gmail.com wrote:
> > > On Sun, Dec 26, 2021 at 04:37:54PM -0500, Ronald S. Bultje wrote:
> > >> Hi,
> > >>
> > >> On Sun, Dec 26, 2021 at 3:21 PM Soft Works <softworkz@hotmail.com>
> wrote:
> > >>
> > >>> I'm not sure. My interpretation of Lance' and Steven's comments would
> > >>> be that they'd prefer to stick to the ML.
> > >>>
> > >>
> > >> No, it's not strictly related to that - they want something that is CLI
> > >> accessible. Gitlab has this here: https://glab.readthedocs.io/en/latest/
> > >> and github has this here: https://github.com/cli/cli - the next question
> is
> > >> whether the gitlab/hub hosts are blocked by a firewall (no idea) and/or
> > >> whether the instances are self-hosted (github: no, gitlab-videolan:
> yes).
> > >
> > > Yes, self-hosted is more preferable, I recall github has blocked
> devleopers
> > > in some country by US trade controls. Who knows what's the rules will be
> > > changed someday as it's controlled by company.
> > >
> >
> > Something that doesn't require another account would be nice, which is why
> > I like mailing lists.
> 
> I don't understand, isn't this an argument in favor of GitHub? Most
> mailing lists (including, notably, FFmpeg's) require registration in
> order to submit messages, which is one of the reasons I hate them. It's
> not just that registration is annoying in general, it's also that
> registration to a mailing list is *more* annoying and cumbersome than
> creating an account on any post-90s website.
> 
> Conversely on GitHub, everybody already has an account, so the overhead
> for first-time contribution is *actually* zero. And on every other
> self-hosted GitLab instance I've come across, I could cross-authenticate
> with some other account I already have.

One component of the GitHub "Bridge" is a mirror of the ffmpeg-devel 
mailing list as a Git repository which provides a web interfaces, can be 
cloned via Git and can also be accessed from Atom feed readers.
This allows to follow the mailing list without subscribing. The web UI
might not be everybody's taste, though. It's the same that is used for 
Linux kernel mailing lists (https://lore.kernel.org/git/).
I had to set this up as it's a requirement for the GitHub "Bridge", but
maybe it's useful for someone in other ways:

https://master.gitmailbox.com/ffmpegdev/

Regards,
softworkz





_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Soft Works
> Sent: Tuesday, December 28, 2021 10:58 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> One component of the GitHub "Bridge" is a mirror of the ffmpeg-devel
> mailing list as a Git repository which provides a web interfaces, can be
> cloned via Git and can also be accessed from Atom feed readers.
> This allows to follow the mailing list without subscribing. The web UI
> might not be everybody's taste, though. It's the same that is used for
> Linux kernel mailing lists (https://lore.kernel.org/git/).
> I had to set this up as it's a requirement for the GitHub "Bridge", but
> maybe it's useful for someone in other ways:
> 
> https://master.gitmailbox.com/ffmpegdev/


I have just ACTIVATED patch submission via GitHub and submitted the first 
patch through this method.

Pull requests can be created in this repository (for now):

https://github.com/ffstaging/FFmpeg


What's not nice is that the submitted e-mail shows "ffmpegagent" as sender
and patchwork is showing it under that name as well.

We'll need to see how this can be improved.

Happy new year!

softworkz



_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Lynne]

2 Jan 2022, 04:28 by softworkz@hotmail.com:

>
>
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Soft Works
>> Sent: Tuesday, December 28, 2021 10:58 PM
>> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
>> Subject: Re: [FFmpeg-devel] GitHub Integration
>>
>> One component of the GitHub "Bridge" is a mirror of the ffmpeg-devel
>> mailing list as a Git repository which provides a web interfaces, can be
>> cloned via Git and can also be accessed from Atom feed readers.
>> This allows to follow the mailing list without subscribing. The web UI
>> might not be everybody's taste, though. It's the same that is used for
>> Linux kernel mailing lists (https://lore.kernel.org/git/).
>> I had to set this up as it's a requirement for the GitHub "Bridge", but
>> maybe it's useful for someone in other ways:
>>
>> https://master.gitmailbox.com/ffmpegdev/
>>
>
>
> I have just ACTIVATED patch submission via GitHub and submitted the first 
> patch through this method.
>
> Pull requests can be created in this repository (for now):
>
> https://github.com/ffstaging/FFmpeg
>
>
> What's not nice is that the submitted e-mail shows "ffmpegagent" as sender
> and patchwork is showing it under that name as well.
>
> We'll need to see how this can be improved.
>

I don't like it. Can't it use the author's name for emails?
_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
> Sent: Sunday, January 2, 2022 3:04 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> 2 Jan 2022, 04:28 by softworkz@hotmail.com:
> 
> >
> >
> >> -----Original Message-----
> >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Soft
> Works
> >> Sent: Tuesday, December 28, 2021 10:58 PM
> >> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> >> Subject: Re: [FFmpeg-devel] GitHub Integration
> >>
> >> One component of the GitHub "Bridge" is a mirror of the ffmpeg-devel
> >> mailing list as a Git repository which provides a web interfaces, can be
> >> cloned via Git and can also be accessed from Atom feed readers.
> >> This allows to follow the mailing list without subscribing. The web UI
> >> might not be everybody's taste, though. It's the same that is used for
> >> Linux kernel mailing lists (https://lore.kernel.org/git/).
> >> I had to set this up as it's a requirement for the GitHub "Bridge", but
> >> maybe it's useful for someone in other ways:
> >>
> >> https://master.gitmailbox.com/ffmpegdev/
> >>
> >
> >
> > I have just ACTIVATED patch submission via GitHub and submitted the first
> > patch through this method.
> >
> > Pull requests can be created in this repository (for now):
> >
> > https://github.com/ffstaging/FFmpeg
> >
> >
> > What's not nice is that the submitted e-mail shows "ffmpegagent" as sender
> > and patchwork is showing it under that name as well.
> >
> > We'll need to see how this can be improved.
> >
> 
> I don't like it. Can't it use the author's name for emails?

I don't like this either. I'll try to find a way.

sw 

_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Soft Works
> Sent: Sunday, January 2, 2022 7:16 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> 
> 
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
> > Sent: Sunday, January 2, 2022 3:04 PM
> > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] GitHub Integration
> >
> > 2 Jan 2022, 04:28 by softworkz@hotmail.com:
> >
> > >
> > >
> > >> -----Original Message-----
> > >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Soft
> > Works
> > >> Sent: Tuesday, December 28, 2021 10:58 PM
> > >> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > >> Subject: Re: [FFmpeg-devel] GitHub Integration
> > >>
> > >> One component of the GitHub "Bridge" is a mirror of the ffmpeg-devel
> > >> mailing list as a Git repository which provides a web interfaces, can be
> > >> cloned via Git and can also be accessed from Atom feed readers.
> > >> This allows to follow the mailing list without subscribing. The web UI
> > >> might not be everybody's taste, though. It's the same that is used for
> > >> Linux kernel mailing lists (https://lore.kernel.org/git/).
> > >> I had to set this up as it's a requirement for the GitHub "Bridge", but
> > >> maybe it's useful for someone in other ways:
> > >>
> > >> https://master.gitmailbox.com/ffmpegdev/
> > >>
> > >
> > >
> > > I have just ACTIVATED patch submission via GitHub and submitted the first
> > > patch through this method.
> > >
> > > Pull requests can be created in this repository (for now):
> > >
> > > https://github.com/ffstaging/FFmpeg
> > >
> > >
> > > What's not nice is that the submitted e-mail shows "ffmpegagent" as
> sender
> > > and patchwork is showing it under that name as well.
> > >
> > > We'll need to see how this can be improved.
> > >
> >
> > I don't like it. Can't it use the author's name for emails?
> 
> I don't like this either. I'll try to find a way.


This is fixed now. See my patch from today:

[FFmpeg-devel] libavutil/tests/md5: Avoid warnings

Also, it appears correctly attributed on Patchwork:
(no longer as ffmpegagent)

https://patchwork.ffmpeg.org/project/ffmpeg/patch/pull.20.ffstaging.FFmpeg.1642727870274.ffmpegagent@gmail.com/

Regards,
softworkz



_______________________________________________
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".

Re: [FFmpeg-devel] GitHub Integration

[Anton Khirnov]

Quoting Ronald S. Bultje (2021-12-26 22:37:54)
> Hi,
> 
> On Sun, Dec 26, 2021 at 3:21 PM Soft Works <softworkz@hotmail.com> wrote:
> 
> > I'm not sure. My interpretation of Lance' and Steven's comments would
> > be that they'd prefer to stick to the ML.
> >
> 
> No, it's not strictly related to that - they want something that is CLI
> accessible. Gitlab has this here: https://glab.readthedocs.io/en/latest/
> and github has this here: https://github.com/cli/cli - the next question is

Last I checked, there were two decently developed CLI tools for gitlab
and neither supported enough functionality to fully cover the usual
workflow.

Github's official CLI tools are a lot more advanced, but then github has
other problems.

And for the record - I am not especially in love with our current ML
workflow, but any change that requires me to use a web browser for
common tasks is a MASSIVE step back IMO.

-- 
Anton Khirnov
_______________________________________________
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".