Re:Sourcehut will blacklist the Go module mirror
by Arnavion on Monday January 09, 2023 @03:50PM
(#34315834)
The offer in [1] was to email the ML to ask for an exclusion, not to continue discussing the general issue which was still being discussed in the GH issue.
And given that they banned him for no reason, he is perfectly in the right to tell them that they should email him instead.
Re:Sourcehut will blacklist the Go module mirror
by ddevault on Monday January 09, 2023 @03:53PM
(#34315866)
Correct: it was made clear to me in no uncertain terms that the only thing I was allowed to say was "yes" or "no" to this offer.
Re:Sourcehut will blacklist the Go module mirror
by tptacek on Monday January 09, 2023 @07:22PM
(#34318533)
The comment above just said that you were banned "for no reason", and you've replied to it "correct". But there is a pretty clear reason you were banned, isn't there?
https://news.ycombinator.com/item?id=34312016
"Correct" isn't the right response here, is it? Like, you don't know the reason you were banned, but it's not as if there is no imaginable reason you would have been.
Hi ddevault, FWIW, in May 2022 on that #44577 issue [0] you had opened, it looks like someone on the core Go team commented there [1] recommending that you email the golang-dev mailing list or email them directly.
Separately, it looks like in July 2022, in one of the issues tracking the new friendlier -reuse flag, there was a mention [2] of the #44577 issue you had opened. In the normal course, that would have triggered an automatic update on your #44577 issue... but I suspect because that #44577 issue had been locked by one of the community gardeners as "too heated", that automatic update didn't happen. (It looks like it was locked due to a series of rapid comments from people unrelated to Sourcehut, including about “scummy behavior”).
Of course, communication on large / sprawling open source projects is never quite perfect, but that's a little extra color...
[0] https://github.com/golang/go/issues/44577
[1] https://github.com/golang/go/issues/44577#issuecomment-11378...
[2] https://github.com/golang/go/issues/53644#issuecomment-11751...