Email or username:

Password:

Forgot your password?
Björkus "No time_t to Die" Dorkus's posts Post Back to profile
Top-level
jannic

@thephd I sincerely hope that there were no bad intentions involved and that it was just a serious case of miscommunication.
In any case, you deserve an explanation and probably an apology from the RustConf organizers.
At the same time, keep in mind that organizing an event like RustConf is a difficult and stressful task. Under stress, people make mistakes. Please try to give them some leeway and do not push them into a defensive position.

27 May 2023 at 6:38 | Wall-to-wall | Open on hachyderm.io
4 comments
Björkus "No time_t to Die" Dorkus

@jannic RustConf was following the direction and lead of the Rust Project, here. The Rust Project has (still) unaired grievances with the direction of compile-time programming, and chose to air those grievances VIA a talk demotion rather than any actionable or explained feedback (or even just a "We hate this, stop doing this").

That's the core problem. Not RustConf having a hard time; everyone behaved exactly as they wanted to, at no point was the sequence of decisions that led to use here rushed or in-error, or so I've been informed repeatedly.

@jannic RustConf was following the direction and lead of the Rust Project, here. The Rust Project has (still) unaired grievances with the direction of compile-time programming, and chose to air those grievances VIA a talk demotion rather than any actionable or explained feedback (or even just a "We hate this, stop doing this").

27 May 2023 at 7:59 | Open on pony.social
jannic

@thephd Is the "Rust Project" something homogeneous enough to have one opinion about topics like compile-time programming? I don't have internal insights, but I imagine it's a relatively heterogeneous group of people.
Obviously somebody acted in a weird way, intentionally or by mistake. But I have no idea how that could have happened, so I'm not going to point to any particular person or group. I'm sorry if my first message could be interpreted as blaming the RustConf organiziers.

27 May 2023 at 8:35 | Open on hachyderm.io
Björkus "No time_t to Die" Dorkus

@jannic Either one person (or multiple people) lied and presented their personal decision as a Rust Project-approved criticism of the talk and the compile-time midterm programming report,

OR

enough of them had misgivings that they could not have the talk or the compile-time midterm programming report, and as a group reached that consensus.

In BOTH cases, they aired that grievance by taking a Rust Project-level decision (through RustConf and not informing me of it themselves) to tell me they don't like the direction. Up until now (literally, as we're talking, as this blog post has gone out!), no Rust Project leadership has explained and/or justified their decision, as either a group or individuals! Using RustConf organizers as a vehicle to initially reveal your disdain for a thing, and not explain that disdain in literally any way after being repeatedly told this is not something we have to do to start with, is extremely sloppy!!

@jannic Either one person (or multiple people) lied and presented their personal decision as a Rust Project-approved criticism of the talk and the compile-time midterm programming report,

OR

enough of them had misgivings that they could not have the talk or the compile-time midterm programming report, and as a group reached that consensus.

27 May 2023 at 13:00 | Open on pony.social
kleines Filmröllchen

@thephd @jannic I have seen that as well with other projects. If you come to me with reasoned complaints, we can discuss. If you shut me down with no explanation, then that's much worse.

27 May 2023 at 19:29 | Open on chaos.social
Go Up