I think there is a need for a place to discuss beta.rust-lang.org that is not its issue tracker.
Please let us try not to be aggressive and to not assume we know better than the others what their impressions are. Let us also not discuss specific issues, because here is not the right place for it, and we will be able to discuss them again once the issue tracker will be open to discussion again. Let us only discuss facts.
- I discovered the existence of beta.rust-lang.org earlier today. Most of the IRC channel where I heard about it was agreeing that there were big issues with the style of it.
- An alternative design has been put up at issue 468. It has been closed with the point that the overall idea of the design was fixed.
- The overall idea of the design has been fixed without any community consultation. This completely makes sense for when interface designers design a website. However, the current beta.rust-lang.org has several usability issues, despite being a work of art from a pretti-ness side: it’s really hard to read the text from it.
- Seeing this, and reacting to it, I opened issue 478, with two small actionable ideas. @lbolla has been nice enough to provide two other actionable ideas. This issue has been closed ~3 hours after, saying to give small actionable ideas. Well, what can be smaller and more actionable than “increase the font size of the main text”?
- Recently, on another IRC channel, I was pointed to pull request 484. Which made me notice that IRC had been removed from the list of channels without any kind of community consultation. And that a PR sent to re-add it had been closed and discussion on it had been blocked within ~30 minutes. While the choice to make Discord the primary channel may make sense, removing any mention of channels where more than 1000 rustaceans are can easily be felt as betrayal by these 1000 rustaceans.
- As a consequence of points 1-4, it is easy to get the feeling that no style changes will be accepted. As a consequence of point 5, it is easy to get the feeling that no contents changes will be accepted.
- As a consequence of point 6, it is easy to feel that the issues tracker of the beta.rust-lang.org repository is useless, and that community is totally disregarded in this process.
My personal opinion is that this is, at least, a huge public relations issue for Rust, which had managed to more or less avoid them up to now.
I would like to suggest that all operations on beta.rust-lang.org be freezed for long enough to figure out a good path forward that includes the community in at least feeling that they have a voice in the matter. I personally think this would be going through one or many RFCs to decide on matters, as at least the RFC process is tried-and-tested, contrarily to the issues repository of beta.rust-lang.org.
Let us try to have a civilized conversation here, however we internally feel. I have tried to do it myself, and hope my internal feelings didn’t leak here. Feel free to contact me off-band (in PM here or preferably
ekleog on IRC) if you see a point I could tone down some more!