4 ms·

Your comment in this thread is the first time I've seen anyone mention that it was being worked on since... June 2021? This despite repeatedly raising the issue

Your comment in this thread is the first time I've seen anyone mention that it was being worked on since... June 2021? This despite repeatedly raising the issue up until I was banned without explanation. I was never told, and still don't know, what disabling the refresh entails, the ban prevents me from discussing the matter further, and I was under the impression that no one was working on it. We have suffered a serious communication failure in this incident. That said, I am looking forward to your follow-up email and seeing this issue resolved in a timely and amicable manner.

typical182 4y ago
> the ban prevents me from discussing the matter further 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. (Edit: 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 https://github.com/golang/go/issues/44577 [1] https://github.com/golang/go/issues/44577#issuecomment-1137822116 https://github.com/golang/go/issues/44577#issuecomment-11378... [2] https://github.com/golang/go/issues/53644#issuecomment-1175117527 https://github.com/golang/go/issues/53644#issuecomment-11751...
- Arnavion 4y ago
  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.
  - ddevault 4y ago
    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.
    - deleted 4y ago
      [deleted]

typical182 4y ago

> the ban prevents me from discussing the matter further 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. (Edit: 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 https://github.com/golang/go/issues/44577 [1] https://github.com/golang/go/issues/44577#issuecomment-1137822116 https://github.com/golang/go/issues/44577#issuecomment-11378... [2] https://github.com/golang/go/issues/53644#issuecomment-1175117527 https://github.com/golang/go/issues/53644#issuecomment-11751...

Arnavion 4y ago
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.
- ddevault 4y ago
  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.
  - deleted 4y ago
    [deleted]