As mentioned in our conversation, I think we all agree that a good URL for the project would be eco.kde.org, yes?

I think eco.kde.org is great.

I have added Lyda, Cornelius, and Aleix as subscribers. We will need to coordinate regarding external support for website design as part of the project's funding.

There are a few regulations to keep in mind for any external publications such as the website:

• everything must be approved by UBA,
• the funding notice (Förderhinweis) must be displayed in a clearly visible position, and
• the Barrier-Free Information Technology Ordinance (Barrierefreien Informationstechnik Verordnung or BITV) and gender neutrality/sensitivity must be observed.

Information about the regulations from: https://www.umweltbundesamt.de/sites/default/files/medien/376/dokumente/regelung-veroeffentlichungen.pdf

This sounds good. I will request the URL from sysadmin and try and get a skeleton web page up pronto.

As for the rules and regulations, maybe you, @joseph, can guide us as we go along and help us bash the material into compliance as we make it?

Sysadmin request created for the repo at T14789

Suggested sections

• Call to action 1
• Intro
• What are we doing
• How you can help
• Resources
• Call to action 2
• Official stuff

Suggested intro draft

What is BE4F0SS?
Blauer Engel for Free Open Source Software (BE4FOSS) is program set up by the German Federal Government that helps Free Open Source Software Communities (like KDE) produce more environ­mentally friendly software. The project provides communities with guidelines and funding to optimize software so it uses less energy when running, for example, or so that it can run on older and less powerful hardware (thus generating less waste).

I like the intro!

Something to keep in mind: there are two related projects which should be part of eco.kde.org.

(1) Free & open source Energy Efficiency Project (FEEP): https://invent.kde.org/cschumac/feep
(2) Blauer Engel for Free & Open Source Software (BE4FOSS): https://invent.kde.org/joseph/be4foss

FEEP has the general goal of improving the energy efficiency of free and open source software, whereas BE4FOSS is more focused on promoting FEEP as well as eco-certification with Blauer Engel. This should be reflected in the structure of the site.

Created new shared folder in Collaborate at

Promo Team Resources/Projects/Eco

Shared with @joseph .

Moved @joseph's text to

Promo Team Resources/Projects/Eco/Website/

@paulb Thanks!

I have updated a few things in the first draft. Please let me know if there are any further suggestions. If not, I will send the first iteration of the website content to UBA for approval so we can get the website online as soon as it is possible.

@aniqakhokhar and @joseph: Figured out how to invite you to edit the page. Added you as developers-

Thanks @paulb

I have updated the content of the website template for KDE Eco and have pushed to the GitLab repository. @paulb I went ahead and merged the branch to master, I hope that is ok.

FYI I am new to Hugo and am not 100% certain I am doing everything correctly. However, I was able to preview the website using the command

hugo server

and then opening http://localhost:1313/.

It is still a work in progress, but I like the template and can envision what it will look like soon (I hope) :)

Good stuff!

I tried to be clever and run the website on my local server. After a bunch of tinkering, managed to run it and connect, but no styling.

I must be missing some link or something. Gonna pull yours, see if it works better.

By the way, do we have a Matrix room for this project?

KDE Eco
For a resource efficient, free software future.

is a bit of a mouthful. What about "Greener Free Software"?

Or, if you want to say what you want people to do: "Build greener Free Software". Or, if you want to specify that you are doing something: "Building greener Free Software".

I agree it is a mouthful, and thanks for the suggestions! I feel "green" has become too much of a buzz word and may lack specificity. What do you think about "Building efficient Free Software"? This also has a nice parechesis to it in the repetition of the /f/ sound.

In T14786#262713, @joseph wrote:

I agree it is a mouthful, and thanks for the suggestions! I feel "green" has become too much of a buzz word

Well, no: Buzzword (no space) is a voguish word, usually used by pedants to distance themselves from laypeople. Green has been used at least since the 70s (yeah, I was alive then and remember) in popular culture to describe eco-friendliness and environmentalism, making it the complete opposite of a buzzword.

and may lack specificity.

That is true. But how specific do you intend to get in a blurb? Surely the main function of a blurb is to give readers a very general gist of what they are about to read and then give them the details in the body.

What do you think about "Building efficient Free Software"?

I don't think this solves your specificity gripe. "Efficient" can refer to so many things!

This also has a nice parechesis to it in the repetition of the /f/ sound.

I wouldn't include that as a favourable factor.

Thanks for the critical feedback and valuable input, Paul! Regarding the last point, it is not clear to me what is not favorable to you, and I can think of many examples of sound repetition being used in ads, such as "Maybe it's Maybelline", "Beans Means Heinz", "Leggo My Eggo" ... although maybe we do not want to promote KDE Eco in a way similar to frozen waffles :-)

I am not tied to any particular wording at this point. One idea I think we may want consider is using phrasing similar to that in the Blauer Engel award criteria [1], which is the basis for both the FEEP and BE4FOSS projects, in order to underscore the connection with KDE Eco.

Regardless, it probably makes sense to continue the discussion once the external support for the website has been settled on, which I hope will be soon now that we may have a new Project Lead.

[1] https://www.blauer-engel.de/en/products/electric-devices/resources-and-energy-efficient-software-products

In T14786#263057, @joseph wrote:

Thanks for the critical feedback and valuable input, Paul! Regarding the last point, it is not clear to me what is not favorable to you, and I can think of many examples of sound repetition being used in ads, such as "Maybe it's Maybelline", "Beans Means Heinz", "Leggo My Eggo" ... although maybe we do not want to promote KDE Eco in a way similar to frozen waffles :-)

I am so sorry. I did not want to come over as dismissive.

The reason that I say I don't think it is a factor is because for every slogan you can think of that rhymes or has alliteration, or whatever, you can probably think of one that is catchier and more famous that has none of those things: "Just Do it", "Diamonds are forever", "Break fast of Champions", etc. So what I was trying to say is that I don't think it hurts, but word play doesn't seem to be a criterion when judging the effectiveness of a slogan.

I am not tied to any particular wording at this point. One idea I think we may want consider is using phrasing similar to that in the Blauer Engel award criteria [1], which is the basis for both the FEEP and BE4FOSS projects, in order to underscore the connection with KDE Eco.

Regardless, it probably makes sense to continue the discussion once the external support for the website has been settled on, which I hope will be soon now that we may have a new Project Lead.

Ok. I am trying to get my head around their headline "Resources and Energy-Efficient Software Products". Do they mean "Resources _for_ Energy-Efficient Software Products", meaning they provide resources to create energy-efficient software products, or that they want to help produce software that is efficient both in its use of resources and of energy? If it is the latter, the grammar may be slightly incorrect as it should be "Resource- and Energy-Efficient Software Products" (or "Resource-Effcient and Energy-Efficient Software Products", but that is a very clumsy sentence). I think something has been lost in the translation. Does it make sense in German?

Either way, using "energy-efficient" in the sentence "Building Energy-Efficient Free Software" solves the specificity problem and it is not terribly clunky!

Hi all,
we found external support to set up the website with Hugo because we have only a few days left until Joseph will have his talk on SFSCON (12th of November)
Since he will promote the project and the 1st sprint there we need to have at least a minimal version of the website online where people can go to and join the project or the sprint. UBA will also have to approve it so it would be great if we have a first version for them to take a look around 5th of November.
@paulb Joseph mentioned you might know what we need to do to get the website online once it is implemented in the repository? Could you help us out there?
This is a dummy Arwin (our external support) already has built: https://arwinneil-kde-eco.netlify.app/

@lana @paulb Thank you for your work on this!

@paulb I am happy to merge any MRs from Arwin in the GitLab repository, if you want. Just let me know! I am still relatively new to GitLab/Git, so bear with me if I make a mistake. I will try to be careful.