[FFmpeg-devel] Next developer meeting

[James Almer]

On 11/11/2020 10:05 AM, Thilo Borgmann wrote:
> Am 11.11.20 um 14:04 schrieb Thilo Borgmann:
>> Am 11.11.20 um 13:01 schrieb Steven Liu:
>>> Thilo Borgmann <thilo.borgmann at mail.de> 于2020年11月11日周三 下午7:20写道：
>>>>
>>>> Hi,
>>>>
>>>> we haven't had a meeting for quite some time and are beyond schedule anyway. So I'd propose having another developer meeting before end of year.
>>>>
>>>> Please give your preferences for a date here:
>>>> https://framadate.org/g1FPmOpfEz9mSLg9
>>>>
>>>> Current agenda proposals, feel free to add to it:
>>>>
>>>> - Tech / Comm committees how-to in practice
>>>> - GSoC adaptations for upcoming years
>>
>>>> - splitting libraries (lavf->lavio)
>>> Need more introduce for this line, libavformat and libavio ?
>>
>> AFAICT i/o operations shall not be separated from lavformat. If I understood it correctly.
> 
> ... shall BE sepearated...

What i know we were discussing was to merge lavd into lavf, since their 
current dependency state is pretty hacky and makes development and 
extension of certain lavf public structs a pain.
It's why i didn't apply my iterate api set just yet.

I don't recall anything about splitting IO, but what does it achieve 
beyond making lavf lighter? Are there users out there that could care 
about linking to an hypothetical lavio while not caring about other lavf 
functionality?

> 
> 
> 
>>>> - writing down development rules
>>>> - switching to a merge request-like system
>>>> - ...
>>
>> -Thilo
>> _______________________________________________
>> ffmpeg-devel mailing list
>> ffmpeg-devel at ffmpeg.org
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>>
> 
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>