[FFmpeg-devel] [PATCH 1/5] avutil/tx_template: extend to 2M

[Thilo Borgmann]

Pls don't top-post.

Am 24.07.23 um 15:04 schrieb Rémi Denis-Courmont:
> Hi,
> 
> That doesn't sound really viable for regular "day-to-day" operations of social network channels, and it's superfluous for stuff that's already been agreed upon.

If you think in patches, I see it would be superfluous. Not that I think that this is the way to look at it - news and patches not necessarily correlate in a 1-1 manner.
About viability, I don't see your argument. Patches, incl their acknowledgement or rejection, already is our day-to-day procedure and the project does not benefit from a faster news-release than this (maybe relaxed for news) scheme would yield. The benefit of doing it the news-patch way, you give yourself:


> The problem is abusing your account privileges to push forward something that was obviously not agreed upon in the first place, such as a controversial feature proposal (as was the case here), or a feature whose implementation is as yet missing or incomplete.
> 
> You shouldn't post this, period. It's not a matter of discussing the post first: if the feature is completed and merged, then you can announce it. If it's not, then you shouldn't make any announcements.

The problem of such controversial posts would completely be solved if a news post goes as patch to the list. No more rules or assumptions needed - ok'd or not. Like we iterate many times a day for code. Would it not? Otherwise we'd be having more controversial posts, yet not as easily to spot as the git log and impossible to correct. I like the overhead of news-patches more.


> Le 24 juillet 2023 15:39:39 GMT+03:00, Thilo Borgmann <thilo.borgmann at mail.de> a écrit :
>> Am 24.07.23 um 13:06 schrieb Leo Izen:
>>>
>>>
>>> On 7/24/23 04:59, Michael Niedermayer wrote:
>>>>
>>>> what ?
>>>> libavradio is part of FFmpeg its just a seperate repository.
>>>> libavradio will also be part of the 6.1 release, it was even officially
>>>> announced. The tweet had over 500 likes IIRC. No sneaking here.
>>>>
>>>
>>> And who made that tweet? Or the decision to tweet it in the first place?
>>
>> That is a good point. Right now, several people just post what they want on several channels, at least Twitter and Linked.in. Without the community involved.
>>
>> We should do a <news post / tweet / whatever you call it> via the means of posting a regular patch for a new news entry to the website - once ok'd on the list, post that as news on the website (push the patch) and trigger all channels to post a similar thing.

-Thilo