In reply to @garbas:matrix.org
I was wondering, what would be best way to interact with the rest of the community regarding social media announcements?
eg.Somebody from community did something I would like nixos accounts to retweet/forward/share/...

Another use case is that other teams would like to post something? Where/How do they contact us? Via issue on GitHub sounds a bit of an overkill. Maybe just writing to us here in this channel would be a good start.

And last use case, which I think we should be doing. Looking for content on discourse (https://discourse.nixos.org/c/announcements/8), reddit (https://www.reddit.com/r/NixOS/, https://www.reddit.com/r/Nix), Hackernews (https://news.ycombinator.com/news), lobste.rs (lobste.rs/t/nix), ... and maybe some other channels.

At the end we need to agree on some policy, what should be announced, how often, what should not be announced, etc... some basic rules.

Also at the end of each month, we would gather this announcements and send them via newsletter.

In reply to @matthewcroughan:defenestrate.it
Do we have a problem of too many things to retweet? If we do, that's a nice problem to have.

In reply to @matthewcroughan:defenestrate.it
Yeah, I guess you can look at my twitter for all generic content lol

In reply to @tomberek:matrix.org
raitobezarius: What is the right language here to express the underlying sentiment? I'm noticing that everyone needs to re-invent their own marketing, their own slogans and themes, their own language to describe what is usually enthusiasm. As this occurs, it makes the messaging convoluted. We don't have a unifying theme, or at least it is not clearly described, nor re-usable.

Good question.

I feel like I would try to coin the term 'sustainable enthusiasm' : we are definitely extremely passioned and all advocates of our tooling, ecosystem, project.

But at the same time, we often 'run towards someone' to shill them NixOS and I feel like in this process, we often forget that there are other distributions besides us, collaborating with us, helping us indirectly (whether by fixing upstream before us, etc, etc.)

It's hard to know everything about what's going on somewhere, but also, it is easy to have empathy for other projects' developers when faced with a rant.
We would not love to read a rant on NixOS which could be incomplete or incorrect (I mean, rants are not necessarily about correctness, they are also a great way to vent.). What we don't want for us, we should not want it for the others.

We could probably interact in a nicer way to such posts by also assuming that others distributions have their drawbacks and advantages and acknowledging it in our engagement. We could also phrase things in a way where we offer alternatives but we acknowledge the difficulty of the problem.

But really, I definitely agree your question is probably the important one to answer to move forward regarding this.