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".
