> Like I said in a comment further down below, I think my initial reaction and post were way too harsh (i.e., not constructive and cynical), sorry for that. It's great that you're taking the initiative and trying to build something, and I wish you all the best with it.
Thank you for being understanding, I appreciate it.
> To be more constructive: I personally feel that such efforts have an easier way of getting of the ground if you first build consensus with a smaller group in private. Ideally this would include some of the influential people in this sphere, (devs of larger projects in the space, cloud providers, famous rustaceans, ...). Otherwise the initiative does not have a lot of credibility (because it hinges on the words of someone most people will not have heard of).
In hindsight, having the folks I've spoken to in private be part of the "launch" and PR reviews could have prevented some confusion.
That being said, I did not want to compose a large core group without giving the opportunity for new people to join.
It was a trade-off to launch small with the intent to start public partnerships with well-known people in the future.
I've spoken to some of these folks in the past, and we intend on collaborating/cooperating if the community's desires warrant it (e.g. a new channel in the official Discord).
> 1) It gives the impression that this is an already established organization, when in fact it is merely a call to action.
I would argue that it's an established organization, but we need to be clear that one of its first goals is to gather community feedback on determining where it should go next.
I did not want ideation happen behind closed doors,
It's established with the intent to be...
1. transformed
2. de-scoped to purely maintaining the website and itself
Regardless, this should be updated with your feedback in mind, and there's a new issue tracking it: https://github.com/rust-cloud-native/core/issues/8
> 2) You never actually say what you are trying to do. Even after all of this, I'm still not sure what you want to create. A community? A main code repository? A specific technical solution? You say you want to "enable the usage of Rust in the cloud". But that's super vague. I can use Rust in the cloud today already, so what are you _really_ after? And _how_ are you going to achieve that?
This is a good point.
I've touched on this above, but it exists to facilitate community ideation and to maintain a website to connect people interested in cloud native Rust.
I believe the issue here is that I've mistakenly blended the mission with the goal(s).
The mission tackles the "why", which is the enablement piece.
That doesn't lean into the "real action".
The goal(s) are what we are trying to do.
Currently, that includes maintaining the existing repos, and gathering community feedback via issue/discussion filing.
There's an issue tracking splitting the "mission" from the "goal(s)", and I think it'll make the answer to this much more clear: https://github.com/rust-cloud-native/core/issues/7