I banned him for responding to it being pointed out that it was an incredibly stupid upload by explaining it wasn't a problem because the slur in question was "just a word" and anyway, he called his black friends that and they didn't mind.
> Mr. Trout, in his self-assumed role of moderator of the then #perl6 channels
I took responsibility for the perl6 IRC infrastructure with Larry's active approval.
Jonathan Worthington was in no way involved in the unbanning process, only Liz being angry at me in private messages on behalf of her 'friend' until I gave up and lifted the ban.
> permaban on the channels as instated by Mr. Trout
The ban was intended to last while he thought about his mistake and considered whether that was the person he wanted to be going forwards.
I still think he would be in a better place today had he had that opportunity then.
> I'm not the only person who left the Perl community because of Mr. Trout's antics.
On a long enough timeline, anybody with an opinion and a spine will get into personality clashes that result in people leaving.
I know of several that were because of me, some of which I regret. I know of several that were because of you, some of which I hope you regret.
So it goes.
TL;DR; - my modules had been up for adoption for *YEARS* already, but nobody was willing to take over maintenance - you can *NOT* just remove modules from CPAN. You can only schedule them for deletion after a week - during that period, no alarm bells started ringing that modules that had downstream dependencies, were being completely removed - I knew that my modules would always be available on BackPAN, and that it would be just a matter of someone re-uploading them and adjusting the master list. Annoying at best, because it would not be breaking anything that was already in production. - And I still had my own copies, so if anybody would have asked to please upload them again, I would have. Nobody did.
What this showed, is that CPAN has a definite vulnerability in this area: - someone (hopefully the owner) can schedule all modules for removal - if these modules have downstream dependencies, then that's too bad: they will stop working
Now, almost two years later, this vulnerability still exists.
As to the reason of me removing my Perl modules: it signalled my leaving the Perl community for good. Before that, I had still hope that some day, I actually would enjoy being part of the Perl community again.
Should I not have removed my modules like that? Well, I don't know how I could further indicate that I did not have any desire to keep maintaining them. The ADOPT-ME status was clearly not enough.
I'm not sure what you tried with ADOPTME, but transferring first-come permissions to ADOPTME would remove your ability to maintain them and allow anyone to adopt the permissions. Permissions for future uploads are a rather separate concern from the currently indexed latest version of the module that dependency chains rely on. The index does not include distributions on BackPAN, so such distributions are only available via manual intervention.
Could you elaborate what these were? I am curious. (I am talking about things other than the commit and the cpan thing)
As far as the Raku CAT is concerned, he is now serving his "sentence" of being banned, until Jan 1st, 2022. We will see what happens after that. I sincerely hope that the Raku CAT will not have to address any reports about him after that date.
Mr. Trout was made aware of the upload by Mr. Spek. An upload that had been superseded within half an hour by another one without the offending (empty) directory. With the original upload marked for removal, but since PAUSE doesn't let you remove modules immediately, it stayed up for a week. And *ANY* module ever uploaded to CPAN, stays on BackPAN for historical purposes. Which I think is a good thing, so we can see what we're talking about.
Mr. Trout, in his self-assumed role of moderator of the then #perl6 channels, kickbanned Mr. Spek without further ado from the #perl6 channels. Even though Mr. Spek was a regular contributor to the Perl 6 project and user of these channels for asking questions and giving answers. In an ironic way very similar to Mr. Trout. Who, by his own admission, has made *MANY* mistakes, yet until then, was *NEVER* banned from anything in the Perl community.
I considered the action of Mr. Spek more as trolling / stupidity / bad habit / young foolishness at the time. And the first offence to my knowledge, by no means grounds for a permaban on the channels as instated by Mr. Trout. I therefore, on behalf of the core team and after conversations with our de-facto BDFL Jonathan Worthington, asked Mr. Trout to raise that ban. Which in the end he reluctantly did. And since then has been interpreted by Mr. Trout as condoning racism.
Sadly, over time, it has become clear to many that Mr. Spek is either too stupid to realize what he's doing with his trolling (saying he is a proponent of free speech and using that), or indeed a racist at some level, or both. The commit in his personal repo (which he makes public as good examples of using dot files) was about using the "master" branch as the default for new git repos, rather than the current git default of "main". With as single comment "Get a job, N*". This was no longer a use of the word as just a word: this was adding context and meaning. For which the Raku CAT team has banned him from public Raku places and revoked all of his commit bits until Jan 1, 2022.
Meanwhile, it looks like Mr. Spek will not change.
As to Mr. Trout: I will no longer interact with Mr. Trout in any way, shape or form. With pain in my heart, I must say that I've given up on the Perl community. And I say this is a recipient of a White Camel award, awarded for services to the Perl *community*.
I'm not the only person who left the Perl community because of Mr. Trout's antics. I guess in the end, only people willing to put up with Mr. Trout, will be left in the Perl community. I sincerely hope they will be happy, as life is too short to be unhappy without good reason.