← @shoutplenty Twitter archive
fleegar
@shoutplenty
this retort seemed funny at first but is really sour after walking the walk
the codebase is a mess. i sent a patch to fix a bug that deprecated a bunch of old broken apis that caused it and it was rejected cos the bug could be hacked internally and “we don’t break apis” [1/5]
10/14/2024, 4:46:36 PM
Favs: 1
Retweets: 1
linkfleegar
@shoutplenty
so now the api is still vulnerable to the bug and has an old clone that’s undocumented despite me having done the work to delete both
something like 5 pings and even more unanswered questions, a review process in which my patch was accepted and then rejected by different ppl
10/14/2024, 4:46:36 PM
Favs: 0
Retweets: 0
linkfleegar
@shoutplenty
the hellhole of refreshing and carefully scanning a mailing list to see if u got a reply. it took 12 days to fix my basic-ass bug, and it didn’t make the release despite being merged before it cos it wasn’t backported to the release branch. i’d asked the maintainer if it would be
10/14/2024, 4:46:37 PM
Favs: 0
Retweets: 0
linkfleegar
@shoutplenty
he goes “maybe” and then doesn’t do it
honestly the guy’s reputation precedes him with the split in the project he caused and the email he famously elicited from torvalds telling him to start using git, both about 13 years ago
10/14/2024, 4:46:38 PM
Favs: 0
Retweets: 0
linkfleegar
@shoutplenty
until u see ffmpeg start to use gitlab or similar, my advice for non-seasoned-contributors is to steer well clear of contributing to this project [5/5]
mood: https://twitter.com/shoutplenty/status/1838868056648396965
10/14/2024, 4:46:38 PM
Favs: 0
Retweets: 0
linkfleegar
@shoutplenty
(i did submit my feedback with full details as well here: https://trac.ffmpeg.org/ticket/11194#comment:4)
(many such examples: https://github.com/jellyfin/jellyfin-ffmpeg/issues/395#issuecomment-2363238269)
10/14/2024, 4:46:39 PM
Favs: 0
Retweets: 0
link