This message was deleted.
# community-support
s
This message was deleted.
πŸ‘ 1
βž• 2
a
Hello Jonathan! I don't think we have met. I am the Developer Advocate for Gradle Build Tool. I am going to follow up with the parties you mentioned and get back to you. Often times a direct call of C-level people in a community slack is actually not seen because their slack feeds are really noisy with sometimes thousands of messages a day. This is an important question and I don't want it to get lost but they will probably not see it to respond. Just wanted to make sure you knew it will be followed up on.
πŸ™‚ 2
j
Awesome, thank you so much! πŸ™‚
a
It seems like Cloudflare made the decision to not support kiwifarms. That is the website seems down. I am not sure on the situation other that what you have shared so if you know more it would be nice to help me relay this to the others.
j
Cloudflare is still fronting their traffic. People have been attacking Kiwi Farms infrastructure through alternative mechanisms. Cloudflare has not made a decision to drop them as a customer
Just because the Kiwi Farms site is currently offline, doesn't mean Cloudflare has chosen to drop them as a customer
a
I was hoping... I am trying to get up to speed on this and found times when things they decided the correct path https://blog.cloudflare.com/why-we-terminated-daily-stormer/
j
Correct, but that was only after their customers started threatening to leave
Will Gradle be joining the rest of the industry in dropping Cloudflare and moving to a different CDN given Cloudflare's refusal to stop supporting hate groups? https://twitter.com/gossithedog/status/1565355108283478016?s=21&t=SUR9i-QGGXP320hMctI7aA
βž• 1
a
we’re having internal conversations, but please keep the slack channel on topic. This is a channel for #CAHSN3LDN
j
Which channel would be more appropriate?
a
I think the description "Post links about interesting articles related to Gradle" is most fitting probably for this which is what the #CNHSSRWNL is for.
j
It's not really an article related to Gradle. This is a call from a former Gradler, and current member of the community asking Gradle the organization to stand against the hate and toxicity Cloudflare supports. This is a community support call, just an unusual one.
a
@Jonathan Leitschuh I'm speaking (obviously anonymously) on behalf of a bunch of us here in the community that have been discussing this privately. We don't feel like this was the correct forum to raise this issue, and we don't appreciate that this was posed as a question to the "singular" Gradle community. No one here should be speaking for anyone else, especially on such polarizing topics. #CAHSN3LDN is certainly not the right place for this discussion/ultimatum, and neither is #CNHSSRWNL Quite frankly, no public channel in this slack is an appropriate place for this. This could have easily been communicated over Twitter, or private channels. This community is a place where we come to help each other with Gradle related support, and not a place for political or social issues. Furthermore, we don't appreciate the position you placed Gradle in. They shouldn't have to be dealing with this issue. We've decided to post this anonymously because none of us are willing to risk the undue blowback we would receive personally and professionally. However, we don't want to remain silent. Not everyone agrees with you and the position you put forward.
❀️ 1
m
I would like this entire thread deleted. It is am embarrassment to the Gradle community.
j
Hi! Thank you for reaching out and sharing your perspective. However, I believe that this request aligns with Gradle's publicly stated code of conduct policy. I also believe that the stance that Cloudflare has taken is in direct contrast to the culture that Gradle is expecting from its community. https://gradle.org/conduct/
a
No one in this slack community, or the Gradle community, or Gradle, has taken any action or stated any belief that runs contrary to Gradle's CoC. Reading through it, nothing indicates that Cloudflare would be governed by it. We respect your opinion on the matter, but we do not respect your attempt to drag unrelated entities (Gradle and the community) into an issue that doesn't concern them, through a medium that is inappropriate for that (this slack).
πŸ™Œ 1
j
No one in this slack community, or the Gradle community, or Gradle, has taken any action or stated any belief that runs contrary to Gradle's CoC.
I agree. I'm sorry if that was in any way implied
a
Then considering your agreement, wouldn't you agree that invoking the CoC is inappropriate considering it pertains to the behavior of Gradle and community members within the context of the community?
m
The nature of this entire thread is seems against the CoC as feels like personal attacks to the heads of gradle and nears on public harassment to them.
a
In addition, please consider the risk of harm you've caused to the Gradle community. If you had not posted your original message in this slack, there would be no effect on the Gradle community. Now having posted it, you run the risk of alienating members of this community who don't want to be involved in issues like this from participating in the community. Your message would have been better suited for a medium like Twitter, or by reaching out to Gradle privately.
πŸ‘ 1
m
If he is a former Gradle worker than why not reach out to those people directly rather than call out here? If you worked there you should have the emails? That makes this thread not useful as you know the people you listed. They aren't even here.
a
To Gradle: we request that measures be taken to prevent things like this from happening in the future.
πŸ‘ 1