[nabakin]

1. They didn't submit a talk or intend to give one

2. They were specifically invited to give a keynote and decided to do so at their request

3. Repeatedly confirmed the topic was ok

4. Put a lot of work into the keynote

5. Told last minute they would not be giving a keynote with no reason

I'd be upset. This is not how you treat your community.

[rvz]

That is even worse.

But ever since the Rust Foundation was formed there was no 'community', only corporate interests, so actions like this is typical of them.

Either way, it seems that the 'Rust foundation' is taking everyone involved downhill. Perhaps the Rust core team are realising very late on the way that the structure of the foundation being a big problem as I said before. [0]

Focusing more on 'code' than on the problems with the governance structure which is the reason why they are now finally realising that they have created the same problems which has been seen before in the Linux foundation.

After all, both are 501(c)6 orgs and serve the interests of corporations more than the community and if they were a community then it should have been set up as a 501(c)3 instead.

[0] https://news.ycombinator.com/item?id=35592650

[steveklabnik]

The blog post specifically talks about how the Foundation was very normal and reasonable, but the Project was the one being weird and causing problems.

[DocSavage]

What does "last minute" mean here? Isn't RustConf in mid-September and it's a single track conference so speakers are heard by all participants? It would be a good way to get your work and opinions out to the broader community.

Clearly the process was botched and more effort should've been made to come to a mutually beneficial solution, but going from an invited keynote (great honor) to an invited talk (honor) is not what I would call a deliberate attempt to "disgrace one of the experts in my field."