Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
Hi On Tue, Mar 12, 2024 at 01:14:45PM -0400, Ronald S. Bultje wrote: > Hello, > > On Sat, Mar 9, 2024 at 8:25 PM Michael Niedermayer > wrote: > > > Some members of the CC want to indefinitely ban Balling > > from trac. And as our doc/community.texi says: > > "Indefinite bans from the community must be confirmed by the General > > Assembly, in a majority vote." > > > > Thus some CC member wishes to involve the public here > > (really theres no other option, the GA cannot discuss/vote on what it > > doesnt know) > > > > Also people have asked for more transparency and i strongly agree with > > transparency. > > > > For reference, Anton and I banned "balling" from IRC in November. We > (FFmpeg's CC) have since then received a request to ban him from trac as > well. > > The ban on IRC was following what happened in #ffmpeg-devel on 11/23/2023 ( > https://libera.irclog.whitequark.org/ffmpeg-devel/2023-11-23) > I've copied the logs from that link between 14:43 and 18:53 below here for > reference. My nick is "BBB", and Anton's nick is "elenril". We also > received help from jess, one of Libera's admins. I think the IRC case and the trac case are different thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Opposition brings concord. Out of discord comes the fairest harmony. -- Heraclitus signature.asc Description: PGP signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On Mon, Mar 11, 2024 at 05:40:25PM -0400, Leo Izen wrote: > > > On 3/9/24 20:25, Michael Niedermayer wrote: > > Hi everyone > > > > Some members of the CC want to indefinitely ban Balling > > from trac. And as our doc/community.texi says: > > "Indefinite bans from the community must be confirmed by the General > > Assembly, in a majority vote." > > > > Thus some CC member wishes to involve the public here > > (really theres no other option, the GA cannot discuss/vote on what it > > doesnt know) > > > > Also people have asked for more transparency and i strongly agree with > > transparency. > > > > As reference, and to make it possible for the community to discuss > > this easily without too much google searching. Ive attached the > > list of all changes in trac done by Balling. > > > > I do not and never did support permanently banning contributors. > > > > In summary: since 2019 > > 842 comment0' changed > > 389 comment1' changed > > 176 comment2' changed > > 87 comment3' changed > > 49 comment4' changed > > 24 comment5' changed > > 12 comment6' changed > >6 comment7' changed > >4 comment8' changed > >3 comment9' changed > > 2194 comment' changed > > 10 component' changed > > 12 description' changed > > 29 keywords' changed > > 37 owner' changed > >8 priority' changed > >7 reproduced' changed > > 291 resolution' changed > > 537 status' changed > > 32 summary' changed > >2 type' changed > > 11 version' changed > > > > > > If these are supposed to be ticket numbers on the left, I checked the first > two and neither have comments from Balling. > > If these are summaries/counts on the left, could you please elaborate on how > you generated this data? I'm not super familiar with the trac user > interface, but iirc you can embed the search in a query string. The data is taken from an admin page of trac that AFAIK lists all activities a user did then email addresses where manually removed to preserve privacy the summary was created using egrep -o '(comment|status|resolution|keyword|version|component|summary|owner|priority|reproduced|type|description).*changed' Balling.txt | sort | uniq -c The numbers on the left are counts not ticket numbers, that is Balling seems to have edited 2194 times a comment field according to grep comment Balling.txt | grep -o 'Ticket [0-9]*' | sort -n | uniq -c | wc grep status Balling.txt | grep -o 'Ticket [0-9]*' | sort -n | uniq -c | wc grep resolution Balling.txt | grep -o 'Ticket [0-9]*' | sort -n | uniq -c | wc he changed the comment fields in 922 distinct tickets he changed the status field in 449 distinct tickets he changed the resolution field in 248 distinct tickets thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Concerning the gods, I have no means of knowing whether they exist or not or of what sort they may be, because of the obscurity of the subject, and the brevity of human life -- Protagoras signature.asc Description: PGP signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On Tue, Mar 12, 2024 at 5:20 PM Marth64 wrote: > I have not interacted with this user and I am just a mediocre contributor. > But from my experience running forums and IRC networks in the past, > this always ends in one process... > >1. toxic user comes along >2. upsets people repeatedly, which also wastes time >3. admins ponder ban, which wastes time >4. they get banned anyway >5. repeat for the next toxic user that comes along > > imo you have the right to /mode +b toxic_user!*@* > looking at the silver lining, at least people get banned on irc -- Vittorio ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
I have not interacted with this user and I am just a mediocre contributor. But from my experience running forums and IRC networks in the past, this always ends in one process... 1. toxic user comes along 2. upsets people repeatedly, which also wastes time 3. admins ponder ban, which wastes time 4. they get banned anyway 5. repeat for the next toxic user that comes along imo you have the right to /mode +b toxic_user!*@* ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On Tue, Mar 12, 2024 at 7:11 PM Kieran Kunhya wrote: > > > > Dear LibAV core developer, thank you for this transcript. > > > > If you feel like trolling, at least get your facts correct. > Dear minor contributor, can you give link to fact checker to use? > > Kieran > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@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-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
> > Dear LibAV core developer, thank you for this transcript. > If you feel like trolling, at least get your facts correct. Kieran ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On Tue, Mar 12, 2024 at 6:15 PM Ronald S. Bultje wrote: > Hello, > > On Sat, Mar 9, 2024 at 8:25 PM Michael Niedermayer > > wrote: > > > Some members of the CC want to indefinitely ban Balling > > from trac. And as our doc/community.texi says: > > "Indefinite bans from the community must be confirmed by the General > > Assembly, in a majority vote." > > > > Thus some CC member wishes to involve the public here > > (really theres no other option, the GA cannot discuss/vote on what it > > doesnt know) > > > > Also people have asked for more transparency and i strongly agree with > > transparency. > > > > For reference, Anton and I banned "balling" from IRC in November. We > (FFmpeg's CC) have since then received a request to ban him from trac as > well. > > The ban on IRC was following what happened in #ffmpeg-devel on 11/23/2023 ( > https://libera.irclog.whitequark.org/ffmpeg-devel/2023-11-23) > I've copied the logs from that link between 14:43 and 18:53 below here for > reference. My nick is "BBB", and Anton's nick is "elenril". We also > received help from jess, one of Libera's admins. > > 14:43 is Valerii Zapodovnikov the same person that was trolling > here earlier? > 14:44 yes > 14:44 valzapod is his other nickname > 14:57 okay so he's active in VLC and placebo too > 14:57 yea > 14:57 and many other projects which haven't banned him yet > 15:56 and you will not be able to ban me > 15:56 You want the Moscow trollfarm? > 15:57 You will get it > 15:57 Just do not forget I own copyright in ffmpeg too. > 15:58 implying someone here asked for it. you're the one behaving > how you are. maybe you feel you're completely OK, but alas that is not a > view shared by many. maybe you're much better IRL, but no-one here has had > the chance of experiencing that. > 15:59 BTW, I really am surprised. I helped you trac progress as > Balling and now that is what I get? LOL, maybe start with trac then, Biden > libtard voters. Is the Russian collusion in the room with right now? > 15:59 *with us > 16:00 courmisch I am active also on wireshark, libtorrent > 16:00 gnuradio (was), rtl-sdr project, all Intel libraries, > clang now too. > 16:01 Are you going and try to ban be there too? You will lose. > Just like Biden lost the election, admit it > 16:03 BTW, banning all VPNs is nice. Are you using same filter > as wikipedia? Cool. But again, github servers do no use VPNs, they are > real. And so are all different virtual machines. > 16:03 Oh, and I web.archived that discussion on github > 16:05 on vlc's gitlab, I mean > 16:06 Biden lost the election, can you LOL??? > 16:06 another maroon > 16:07 JEEB: I am the same in real life, BTW. You just cannot > ban a person in real life, only kill. Like that woman that said All lives > matter in USA. > 16:09 zadedfqul was kicked from #ffmpeg-devel by elenril [zadedfqul] > 16:09 pls do NOT engage the troll > 16:10 I blame TypX this time, but he did not "know" > 16:13 Banning is also engaging, Anton > 16:14 Just like your knowledge in top posting. > 16:14 https://i.imgur.com/3tv4c5x.jpg > 16:15 wsqacadq was kicked from #ffmpeg-devel by elenril [wsqacadq] > 16:19 man that dude is persistent :) > 16:19 does he not have something better to do with his life > 16:19 takes commitment to contract a VPN just for trolling > opensoars > 16:20 or maybe it's provided for official Mordor public service > use > 16:20 :) > 16:20 we'll keep banning the balling > 16:20 every time I saw that, I hear the dwarfs from the hobbit > 16:20 courmisch: to be honest the location from which a person is > does not matter at all > 16:21 s/is/comes/ > 16:21 untrue > 16:21 were he from a civilized country, we could use their law > enforcement services > 16:21 yea, but someone being an asshole or troll is not is a person > problem > 16:21 asdf > 16:21 I was alluding to troll farms. Not every country has > them, especially not on the scale of the Russian federation > 16:21 *is* a person problem > 16:22 obviously some devs over there are reasonable people > 16:26 BTW, Trump just needed 44000 votes to win > 16:27 i thought you said he won? be consistent > 16:27 And so as there are up to a million ballot that were > not observed he really did win. > 16:27 ukrainesucks was banned on #ffmpeg-devel by BBB [*!~ > ukrainesu@195.189.226.40] > 16:27 ukrainesucks was kicked from #ffmpeg-devel by BBB [Your behavior is > not conducive to the desired environment.] > 16:27 psykose: i mean it > 16:27 do NOT engage the troll > 16:28 Also, Clinton was fined for Steele dossier > 16:28 ukrainesuccxxks was banned on #ffmpeg-devel by BBB [*!~ > ukrainesu@91.193.19.147] > 16:28 ukrainesuccxxks was kicked from #ffmpeg-devel by BBB [Your behavior > is not conducive to the desired environment.] > 16:29 +r already > 16:29 nah > 16:29 I'm personally fine with +r > 16:29 but if others object I won't insist on it > 16:30 I don't think it's anywhere bad enough to require +r > 16:30 (yet?) >
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
Hello, On Sat, Mar 9, 2024 at 8:25 PM Michael Niedermayer wrote: > Some members of the CC want to indefinitely ban Balling > from trac. And as our doc/community.texi says: > "Indefinite bans from the community must be confirmed by the General > Assembly, in a majority vote." > > Thus some CC member wishes to involve the public here > (really theres no other option, the GA cannot discuss/vote on what it > doesnt know) > > Also people have asked for more transparency and i strongly agree with > transparency. > For reference, Anton and I banned "balling" from IRC in November. We (FFmpeg's CC) have since then received a request to ban him from trac as well. The ban on IRC was following what happened in #ffmpeg-devel on 11/23/2023 ( https://libera.irclog.whitequark.org/ffmpeg-devel/2023-11-23) I've copied the logs from that link between 14:43 and 18:53 below here for reference. My nick is "BBB", and Anton's nick is "elenril". We also received help from jess, one of Libera's admins. 14:43 is Valerii Zapodovnikov the same person that was trolling here earlier? 14:44 yes 14:44 valzapod is his other nickname 14:57 okay so he's active in VLC and placebo too 14:57 yea 14:57 and many other projects which haven't banned him yet 15:56 and you will not be able to ban me 15:56 You want the Moscow trollfarm? 15:57 You will get it 15:57 Just do not forget I own copyright in ffmpeg too. 15:58 implying someone here asked for it. you're the one behaving how you are. maybe you feel you're completely OK, but alas that is not a view shared by many. maybe you're much better IRL, but no-one here has had the chance of experiencing that. 15:59 BTW, I really am surprised. I helped you trac progress as Balling and now that is what I get? LOL, maybe start with trac then, Biden libtard voters. Is the Russian collusion in the room with right now? 15:59 *with us 16:00 courmisch I am active also on wireshark, libtorrent 16:00 gnuradio (was), rtl-sdr project, all Intel libraries, clang now too. 16:01 Are you going and try to ban be there too? You will lose. Just like Biden lost the election, admit it 16:03 BTW, banning all VPNs is nice. Are you using same filter as wikipedia? Cool. But again, github servers do no use VPNs, they are real. And so are all different virtual machines. 16:03 Oh, and I web.archived that discussion on github 16:05 on vlc's gitlab, I mean 16:06 Biden lost the election, can you LOL??? 16:06 another maroon 16:07 JEEB: I am the same in real life, BTW. You just cannot ban a person in real life, only kill. Like that woman that said All lives matter in USA. 16:09 zadedfqul was kicked from #ffmpeg-devel by elenril [zadedfqul] 16:09 pls do NOT engage the troll 16:10 I blame TypX this time, but he did not "know" 16:13 Banning is also engaging, Anton 16:14 Just like your knowledge in top posting. 16:14 https://i.imgur.com/3tv4c5x.jpg 16:15 wsqacadq was kicked from #ffmpeg-devel by elenril [wsqacadq] 16:19 man that dude is persistent :) 16:19 does he not have something better to do with his life 16:19 takes commitment to contract a VPN just for trolling opensoars 16:20 or maybe it's provided for official Mordor public service use 16:20 :) 16:20 we'll keep banning the balling 16:20 every time I saw that, I hear the dwarfs from the hobbit 16:20 courmisch: to be honest the location from which a person is does not matter at all 16:21 s/is/comes/ 16:21 untrue 16:21 were he from a civilized country, we could use their law enforcement services 16:21 yea, but someone being an asshole or troll is not is a person problem 16:21 asdf 16:21 I was alluding to troll farms. Not every country has them, especially not on the scale of the Russian federation 16:21 *is* a person problem 16:22 obviously some devs over there are reasonable people 16:26 BTW, Trump just needed 44000 votes to win 16:27 i thought you said he won? be consistent 16:27 And so as there are up to a million ballot that were not observed he really did win. 16:27 ukrainesucks was banned on #ffmpeg-devel by BBB [*!~ ukrainesu@195.189.226.40] 16:27 ukrainesucks was kicked from #ffmpeg-devel by BBB [Your behavior is not conducive to the desired environment.] 16:27 psykose: i mean it 16:27 do NOT engage the troll 16:28 Also, Clinton was fined for Steele dossier 16:28 ukrainesuccxxks was banned on #ffmpeg-devel by BBB [*!~ ukrainesu@91.193.19.147] 16:28 ukrainesuccxxks was kicked from #ffmpeg-devel by BBB [Your behavior is not conducive to the desired environment.] 16:29 +r already 16:29 nah 16:29 I'm personally fine with +r 16:29 but if others object I won't insist on it 16:30 I don't think it's anywhere bad enough to require +r 16:30 (yet?) 16:30 Clinton was found to be using gmail 16:30 bsbsvsvsv was banned on #ffmpeg-devel by BBB [*!~ bsbsvsvsv@205.185.127.86] 16:30 bsbsvsvsv was kicked from #ffmpeg-devel by BBB [Your behavior is not conducive to the desired environment.] 16:30 dbbsbsbs was banned on #ffmpeg-devel by
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On 3/9/24 20:25, Michael Niedermayer wrote: Hi everyone Some members of the CC want to indefinitely ban Balling from trac. And as our doc/community.texi says: "Indefinite bans from the community must be confirmed by the General Assembly, in a majority vote." Thus some CC member wishes to involve the public here (really theres no other option, the GA cannot discuss/vote on what it doesnt know) Also people have asked for more transparency and i strongly agree with transparency. As reference, and to make it possible for the community to discuss this easily without too much google searching. Ive attached the list of all changes in trac done by Balling. I do not and never did support permanently banning contributors. In summary: since 2019 842 comment0' changed 389 comment1' changed 176 comment2' changed 87 comment3' changed 49 comment4' changed 24 comment5' changed 12 comment6' changed 6 comment7' changed 4 comment8' changed 3 comment9' changed 2194 comment' changed 10 component' changed 12 description' changed 29 keywords' changed 37 owner' changed 8 priority' changed 7 reproduced' changed 291 resolution' changed 537 status' changed 32 summary' changed 2 type' changed 11 version' changed If these are supposed to be ticket numbers on the left, I checked the first two and neither have comments from Balling. If these are summaries/counts on the left, could you please elaborate on how you generated this data? I'm not super familiar with the trac user interface, but iirc you can embed the search in a query string. - Leo Izen (Traneptora) OpenPGP_signature.asc Description: OpenPGP digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On Sun, Mar 10, 2024 at 10:24 AM Kieran Kunhya wrote: > On Sun, 10 Mar 2024, 01:25 Michael Niedermayer, > wrote: > > > Hi everyone > > > > Some members of the CC want to indefinitely ban Balling > > from trac. And as our doc/community.texi says: > > "Indefinite bans from the community must be confirmed by the General > > Assembly, in a majority vote." > > > > Thus some CC member wishes to involve the public here > > (really theres no other option, the GA cannot discuss/vote on what it > > doesnt know) > > > > Also people have asked for more transparency and i strongly agree with > > transparency. > > > > As reference, and to make it possible for the community to discuss > > this easily without too much google searching. Ive attached the > > list of all changes in trac done by Balling. > > > > I do not and never did support permanently banning contributors. > > > > In summary: since 2019 > > 842 comment0' changed > > 389 comment1' changed > > 176 comment2' changed > > 87 comment3' changed > > 49 comment4' changed > > 24 comment5' changed > > 12 comment6' changed > > 6 comment7' changed > > 4 comment8' changed > > 3 comment9' changed > >2194 comment' changed > > 10 component' changed > > 12 description' changed > > 29 keywords' changed > > 37 owner' changed > > 8 priority' changed > > 7 reproduced' changed > > 291 resolution' changed > > 537 status' changed > > 32 summary' changed > > 2 type' changed > > 11 version' changed > > > > > > On Sat, Mar 02, 2024 at 10:23:32PM +0100, Michael Niedermayer wrote: > > > The CC has no authority for permanent bans > > > "Indefinite bans from the community must be confirmed by the General > > Assembly, in a majority vote." > > > > > > I checked and it seems there are over 4800 events in trac from Balling, > > 3783 match the word "comment" > > > since 2019 > > > > > > By what rules does the CC deal out warnings and bans ? > > > > > > I think this needs to be put in writing in the docs because > > > currently its pretty much arbitrary. Some people get multiple > > > warnings, some people get nothing, some people are suggested to be > > > just banned with no prior warning > > > > > > On Sat, Mar 09, 2024 at 11:06:39AM +0100, Jean-Baptiste Kempf wrote: > > > Hello, > > > > > > On Sat, 9 Mar 2024, at 08:30, Anton Khirnov wrote: > > > > Quoting Michael Niedermayer (2024-03-06 13:56:39) > > > >> Balling does have a quite different style in his language. Not sure > > > >> what is a good term, street style, ghetto style? > > > >> > > > >> He used the same style of language towards me 10 days ago: > > > >> https://trac.ffmpeg.org/ticket/10824#comment:18 > > > > > > > > This is not a "style", he understands perfectly well what he is > doing. > > > > > > Come on, the guy is a troll. > > > We're not talking about a developer from FFmpeg, but an external troll, > > contributing nothing. > > > Kick him out. > > > > Do you have permission to post private CC discussion on the ML? > Yes, As approved by new supreme leader Anton. > > Kieran > > > > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@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-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On Sun, 10 Mar 2024, 01:25 Michael Niedermayer, wrote: > Hi everyone > > Some members of the CC want to indefinitely ban Balling > from trac. And as our doc/community.texi says: > "Indefinite bans from the community must be confirmed by the General > Assembly, in a majority vote." > > Thus some CC member wishes to involve the public here > (really theres no other option, the GA cannot discuss/vote on what it > doesnt know) > > Also people have asked for more transparency and i strongly agree with > transparency. > > As reference, and to make it possible for the community to discuss > this easily without too much google searching. Ive attached the > list of all changes in trac done by Balling. > > I do not and never did support permanently banning contributors. > > In summary: since 2019 > 842 comment0' changed > 389 comment1' changed > 176 comment2' changed > 87 comment3' changed > 49 comment4' changed > 24 comment5' changed > 12 comment6' changed > 6 comment7' changed > 4 comment8' changed > 3 comment9' changed >2194 comment' changed > 10 component' changed > 12 description' changed > 29 keywords' changed > 37 owner' changed > 8 priority' changed > 7 reproduced' changed > 291 resolution' changed > 537 status' changed > 32 summary' changed > 2 type' changed > 11 version' changed > > > On Sat, Mar 02, 2024 at 10:23:32PM +0100, Michael Niedermayer wrote: > > The CC has no authority for permanent bans > > "Indefinite bans from the community must be confirmed by the General > Assembly, in a majority vote." > > > > I checked and it seems there are over 4800 events in trac from Balling, > 3783 match the word "comment" > > since 2019 > > > > By what rules does the CC deal out warnings and bans ? > > > > I think this needs to be put in writing in the docs because > > currently its pretty much arbitrary. Some people get multiple > > warnings, some people get nothing, some people are suggested to be > > just banned with no prior warning > > > On Sat, Mar 09, 2024 at 11:06:39AM +0100, Jean-Baptiste Kempf wrote: > > Hello, > > > > On Sat, 9 Mar 2024, at 08:30, Anton Khirnov wrote: > > > Quoting Michael Niedermayer (2024-03-06 13:56:39) > > >> Balling does have a quite different style in his language. Not sure > > >> what is a good term, street style, ghetto style? > > >> > > >> He used the same style of language towards me 10 days ago: > > >> https://trac.ffmpeg.org/ticket/10824#comment:18 > > > > > > This is not a "style", he understands perfectly well what he is doing. > > > > Come on, the guy is a troll. > > We're not talking about a developer from FFmpeg, but an external troll, > contributing nothing. > > Kick him out. > Do you have permission to post private CC discussion on the ML? Kieran > ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On 10 Mar 2024, at 4:00, Michael Niedermayer wrote: > On Sun, Mar 10, 2024 at 02:36:48AM +0100, epira...@gmail.com wrote: >> On 10 Mar 2024, at 2:25, Michael Niedermayer wrote: >> >>> Hi everyone >>> >>> Some members of the CC want to indefinitely ban Balling >>> from trac. And as our doc/community.texi says: >>> "Indefinite bans from the community must be confirmed by the General >>> Assembly, in a majority vote." >>> >>> Thus some CC member wishes to involve the public here >>> (really theres no other option, the GA cannot discuss/vote on what it >>> doesnt know) >>> >>> Also people have asked for more transparency and i strongly agree with >>> transparency. >>> >>> As reference, and to make it possible for the community to discuss >>> this easily without too much google searching. Ive attached the >>> list of all changes in trac done by Balling. >>> >>> I do not and never did support permanently banning contributors. >>> >>> In summary: since 2019 >>> 842 comment0' changed >>> 389 comment1' changed >>> 176 comment2' changed >>> 87 comment3' changed >>> 49 comment4' changed >>> 24 comment5' changed >>> 12 comment6' changed >>> 6 comment7' changed >>> 4 comment8' changed >>> 3 comment9' changed >>>2194 comment' changed >>> 10 component' changed >>> 12 description' changed >>> 29 keywords' changed >>> 37 owner' changed >>> 8 priority' changed >>> 7 reproduced' changed >>> 291 resolution' changed >>> 537 status' changed >>> 32 summary' changed >>> 2 type' changed >>> 11 version' changed >>> >> >> I already have an opinion about this topic due to various things I read from >> him on various OSS projects communication channels, but I am wondering >> how the attached document is helpful for the GA to get an idea of what >> this is about? >> >> Do you expect us to go through all of this list and visit each Trac ticket >> and look at what they wrote there? >> >> Maybe I am missing something here on the purpose of this document. > > Its unbiased information, its simply the full list of changes done by the > user id on trac > One can read a random subset of the comments/changes or fetch the referred > tickets and run some AI over all and ask for a summary > > If one already has formed an oppinion or does not want to vote then one can > also ignore it. Or maybe the community will decide against a vote. „Or maybe the community will decide against a vote.“ How would that even work? Of course you could propose a vote on having a vote but that seems like unnecessary meta-voting… > > I just tried to provide what i can so people have the information if they want > it. > > To me, every contributor is valuable. I want people to work together as a > team. But if people are asking for others to be banned thats a sign > something is not right. > > thx > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Rewriting code that is poorly written but fully understood is good. > Rewriting code that one doesnt understand is a sign that one is less smart > than the original author, trying to rewrite it will not make it better. > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@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-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On Sun, Mar 10, 2024 at 02:36:48AM +0100, epira...@gmail.com wrote: > On 10 Mar 2024, at 2:25, Michael Niedermayer wrote: > > > Hi everyone > > > > Some members of the CC want to indefinitely ban Balling > > from trac. And as our doc/community.texi says: > > "Indefinite bans from the community must be confirmed by the General > > Assembly, in a majority vote." > > > > Thus some CC member wishes to involve the public here > > (really theres no other option, the GA cannot discuss/vote on what it > > doesnt know) > > > > Also people have asked for more transparency and i strongly agree with > > transparency. > > > > As reference, and to make it possible for the community to discuss > > this easily without too much google searching. Ive attached the > > list of all changes in trac done by Balling. > > > > I do not and never did support permanently banning contributors. > > > > In summary: since 2019 > > 842 comment0' changed > > 389 comment1' changed > > 176 comment2' changed > > 87 comment3' changed > > 49 comment4' changed > > 24 comment5' changed > > 12 comment6' changed > > 6 comment7' changed > > 4 comment8' changed > > 3 comment9' changed > >2194 comment' changed > > 10 component' changed > > 12 description' changed > > 29 keywords' changed > > 37 owner' changed > > 8 priority' changed > > 7 reproduced' changed > > 291 resolution' changed > > 537 status' changed > > 32 summary' changed > > 2 type' changed > > 11 version' changed > > > > I already have an opinion about this topic due to various things I read from > him on various OSS projects communication channels, but I am wondering > how the attached document is helpful for the GA to get an idea of what > this is about? > > Do you expect us to go through all of this list and visit each Trac ticket > and look at what they wrote there? > > Maybe I am missing something here on the purpose of this document. Its unbiased information, its simply the full list of changes done by the user id on trac One can read a random subset of the comments/changes or fetch the referred tickets and run some AI over all and ask for a summary If one already has formed an oppinion or does not want to vote then one can also ignore it. Or maybe the community will decide against a vote. I just tried to provide what i can so people have the information if they want it. To me, every contributor is valuable. I want people to work together as a team. But if people are asking for others to be banned thats a sign something is not right. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Rewriting code that is poorly written but fully understood is good. Rewriting code that one doesnt understand is a sign that one is less smart than the original author, trying to rewrite it will not make it better. signature.asc Description: PGP signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Indefinite ban request [RFC] Was: Re: [FFmpeg-trac] #10882(undetermined:new): swscale wastefully scales luma during yuv420p -> yuv422p
On 10 Mar 2024, at 2:25, Michael Niedermayer wrote: > Hi everyone > > Some members of the CC want to indefinitely ban Balling > from trac. And as our doc/community.texi says: > "Indefinite bans from the community must be confirmed by the General > Assembly, in a majority vote." > > Thus some CC member wishes to involve the public here > (really theres no other option, the GA cannot discuss/vote on what it doesnt > know) > > Also people have asked for more transparency and i strongly agree with > transparency. > > As reference, and to make it possible for the community to discuss > this easily without too much google searching. Ive attached the > list of all changes in trac done by Balling. > > I do not and never did support permanently banning contributors. > > In summary: since 2019 > 842 comment0' changed > 389 comment1' changed > 176 comment2' changed > 87 comment3' changed > 49 comment4' changed > 24 comment5' changed > 12 comment6' changed > 6 comment7' changed > 4 comment8' changed > 3 comment9' changed >2194 comment' changed > 10 component' changed > 12 description' changed > 29 keywords' changed > 37 owner' changed > 8 priority' changed > 7 reproduced' changed > 291 resolution' changed > 537 status' changed > 32 summary' changed > 2 type' changed > 11 version' changed > I already have an opinion about this topic due to various things I read from him on various OSS projects communication channels, but I am wondering how the attached document is helpful for the GA to get an idea of what this is about? Do you expect us to go through all of this list and visit each Trac ticket and look at what they wrote there? Maybe I am missing something here on the purpose of this document. > > On Sat, Mar 02, 2024 at 10:23:32PM +0100, Michael Niedermayer wrote: >> The CC has no authority for permanent bans >> "Indefinite bans from the community must be confirmed by the General >> Assembly, in a majority vote." >> >> I checked and it seems there are over 4800 events in trac from Balling, 3783 >> match the word "comment" >> since 2019 >> >> By what rules does the CC deal out warnings and bans ? >> >> I think this needs to be put in writing in the docs because >> currently its pretty much arbitrary. Some people get multiple >> warnings, some people get nothing, some people are suggested to be >> just banned with no prior warning > > > On Sat, Mar 09, 2024 at 11:06:39AM +0100, Jean-Baptiste Kempf wrote: >> Hello, >> >> On Sat, 9 Mar 2024, at 08:30, Anton Khirnov wrote: >>> Quoting Michael Niedermayer (2024-03-06 13:56:39) Balling does have a quite different style in his language. Not sure what is a good term, street style, ghetto style? He used the same style of language towards me 10 days ago: https://trac.ffmpeg.org/ticket/10824#comment:18 >>> >>> This is not a "style", he understands perfectly well what he is doing. >> >> Come on, the guy is a troll. >> We're not talking about a developer from FFmpeg, but an external troll, >> contributing nothing. >> Kick him out. > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > In fact, the RIAA has been known to suggest that students drop out > of college or go to community college in order to be able to afford > settlements. -- The RIAA > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@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-requ...@ffmpeg.org with subject "unsubscribe".
