we have chosen not to name names or divulge specifics that could implicate anyone. Even so, we felt that we should state our reasons for resigning to avoid people making up their own drama.
An entire team resigned, one of those who is part of the governance structure. Isn’t this enough drama?
I have a feeling that someone wants to take over the whole direction of the Rust Foundation and therefore the way the technology should go. cough cough << Bezos >>.
Maybe it’s gotten cleaned up since you looked, but it seems pretty polite and productive. Then again, it looks like the Reddit moderators locked it and started deleting posts.
Personally I think they dealt with the issue rather well. It would be best at this time to focus on the key foundational issues behind what allowed the core team to disregard the code of conduct as they (allegedly) did and increase accountability for them rather than engage on a witch hunt which would only serve to further increase schisms in the community and incite unrest. We have plenty of examples in FOSS where such behavior has led to failed projects and forks.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !opensource@lemmy.ml
All about open source! Feel free to ask questions, and share news, and interesting stuff!
An entire team resigned, one of those who is part of the governance structure. Isn’t this enough drama?
I have a feeling that someone wants to take over the whole direction of the Rust Foundation and therefore the way the technology should go. cough cough << Bezos >>.
That comment section though. Kind of a free for all rn :S
Maybe it’s gotten cleaned up since you looked, but it seems pretty polite and productive. Then again, it looks like the Reddit moderators locked it and started deleting posts.
deleted by creator
I doubt it. No one wants that to happen, so there will be a lot of people working to heal any rift.
This is one of those vague messages that tells no one what’s actually happening. They should provide some context as to what’s going on.
Personally I think they dealt with the issue rather well. It would be best at this time to focus on the key foundational issues behind what allowed the core team to disregard the code of conduct as they (allegedly) did and increase accountability for them rather than engage on a witch hunt which would only serve to further increase schisms in the community and incite unrest. We have plenty of examples in FOSS where such behavior has led to failed projects and forks.
this kind of makes all the Perl foundation weirdness small in comparison