KDE Eco is (AFAIK) a project by the KDE folks to try and push for better optimizations for energy efficiency for software projects in general and to try and push for free software adoption by governments with the main push being the limits of software support by companies and the landfill that limited support creates.
I’m not sure, if you’re involved with the project, but if so: you really need to work on your communication.
You want hardware to last longer by providing software for it. That’s it. Great goal, but you don’t need half a bachelor’s thesis for that, and you also don’t need to tiptoe around the point.
Clearly they can’t get their point across. And I don’t know, why people down vote me for that.
KDE starts a new initiative, and does so by creating a giant wall of text that says very little about the initiative itself. So little in fact, that people here obviously don’t understand what they’re actually trying to do. That is bad communication. Simple as that. And given that this is not a random blog post, but a press statement, I’m pretty sure a bunch of people read it before publishing it.
I mean this subtitle right here gave me a pretty good idea what’s this initiative is all about already, but that’s just me I guess
Also, keep in mind that people from different countries work on KDE, and English is not their first language, I don’t know what are your expectations… on how the writing should be…
But here’s the thing, take a look at Google or MS posts about sustainably and being green, and you’ll realize, truly realize how one could say so much without saying anything… this wall of text that you’re talking about is full of insights
I mean this subtitle right here gave me a pretty good idea what’s this initiative is all about already, but that’s just me I guess
But what does that mean exactly? Fairphones with long support duration? Solar powered software developers?
I get a rough direction from that, but nothing else, but it’s a headline, that’s ok.
What really bugs me is that the body of the text doesn’t really explain it either, but needs hundreds of words for that. It’s just fluff for a press statement that should have fit into a tweet.
Also, keep in mind that people from different countries work on KDE, and English is not their first language, I don’t know what are your expectations… on how the writing should be…
Well, given that I’m from Germany and English is not my first language, and also given that I’m neither very good at it nor do I have a PR team, I would expect writing at least on my level, I guess?
But here’s the thing, take a look at Google or MS posts about sustainably and being green, and you’ll realize, truly realize how one could say so much without saying anything… this wall of text that you’re talking about is full of insights
And these companies are the benchmark? I mean, can’t we expect more from a nonprofit? There are some insights, yes, but they’re drowning in the wall of text.
Just as an insight for you: a news article is supposed to increase in detail level from top to bottom. The headline shows the rough topic, subtitle slightly expands on that, the first paragraphs tell the actual story, the next paragraphs provide more and more context. The idea is, that a reader can stop reading if she feels like there’s been enough context.
Look at the article here and ask yourself if it fits this description.
So… this is going to be a debloated lightweight distro (or just a DE?) with official support for not-so-fresh hardware? I don’t fully understand.
KDE Eco is (AFAIK) a project by the KDE folks to try and push for better optimizations for energy efficiency for software projects in general and to try and push for free software adoption by governments with the main push being the limits of software support by companies and the landfill that limited support creates.
I’m not sure, if you’re involved with the project, but if so: you really need to work on your communication.
You want hardware to last longer by providing software for it. That’s it. Great goal, but you don’t need half a bachelor’s thesis for that, and you also don’t need to tiptoe around the point.
Looking at your username, it makes sense you say something like that
Why would I not say that?
Clearly they can’t get their point across. And I don’t know, why people down vote me for that.
KDE starts a new initiative, and does so by creating a giant wall of text that says very little about the initiative itself. So little in fact, that people here obviously don’t understand what they’re actually trying to do. That is bad communication. Simple as that. And given that this is not a random blog post, but a press statement, I’m pretty sure a bunch of people read it before publishing it.
Sustainable Software For Sustainable Hardware
I mean this subtitle right here gave me a pretty good idea what’s this initiative is all about already, but that’s just me I guess
Also, keep in mind that people from different countries work on KDE, and English is not their first language, I don’t know what are your expectations… on how the writing should be…
But here’s the thing, take a look at Google or MS posts about sustainably and being green, and you’ll realize, truly realize how one could say so much without saying anything… this wall of text that you’re talking about is full of insights
But what does that mean exactly? Fairphones with long support duration? Solar powered software developers?
I get a rough direction from that, but nothing else, but it’s a headline, that’s ok.
What really bugs me is that the body of the text doesn’t really explain it either, but needs hundreds of words for that. It’s just fluff for a press statement that should have fit into a tweet.
Well, given that I’m from Germany and English is not my first language, and also given that I’m neither very good at it nor do I have a PR team, I would expect writing at least on my level, I guess?
And these companies are the benchmark? I mean, can’t we expect more from a nonprofit? There are some insights, yes, but they’re drowning in the wall of text.
Just as an insight for you: a news article is supposed to increase in detail level from top to bottom. The headline shows the rough topic, subtitle slightly expands on that, the first paragraphs tell the actual story, the next paragraphs provide more and more context. The idea is, that a reader can stop reading if she feels like there’s been enough context.
Look at the article here and ask yourself if it fits this description.