Kieran Kunhya

So in open source projects...

Sometimes you disagree, right?

And the good thing is because of the license, you're allowed to basically do your own, right?

And this is normal and this has happened all the time, right?

At the point there was GCC at the time of GCC2 and EGCS.

which became then GCC3, right?

There is what we call KHTML with WebKit, with Blink.

It is a same process.

And also, like, when I want to do a new feature today in VLC, I fork, I do my thing on my own, and then I merge back to the community.

So there was a split in the open source community on FFmpeg, which become LibAV and FFmpeg.

And after a few years, well, the community merged back and people moved on.

It's a bit...

drama that is normal in open source community, but forks are even, they're important because they change the status quo of a community.

Not talking about FFmpeg and EBAV here, but the GCC fork made GCC a ton better because some people wanted to change the architecture fundamentally to make it faster.

And of course, it's always a question of people and so on, but in the end, you realize that

FFmpeg today is better than it was before the fork.

And now, well, we're back all together, right?

And I spend a lot of time, and Kieran can say, in the community.

It's not often, to be honest, very well explained because a ton of the reasons are not very public.

But I think that's normal and that's good.