Project & Governance

:grinning: If that’s the case, I can “do things” but you have to know what those things are and how to do them. For example, I could keep a roadmap for Leap and Tumbleweed and other associated projects and make sure they are clearly communicated if I have some easy way to know what that readmap is other than subscribing to a dozen mailing lists so that the one that goes to spam is the one that includes what you should publish.
And you need to have a place to publish it and it’s accessible to all interested people, and general communication channels to publicize it etc.

Most things are not a problem of who does it, but rather who decides to do it. For example, it’s discouraging to make a communication for YaST (wiki, social networks) and then be told “ah, YaST, yes, we’re going to remove that soon”. But if we decide “let’s go with Agama” then we do it with Agama, what’s the problem? And so on.

I agree. And it’s true that

And someone in the “direction” must take care about that Central Communication Hub (it have the resources, the people,…)

first news, as we say here.