Reverted green-coding-services

green-coding-solutions · Jan 14, 2024 · 1e6ec8f · 1e6ec8f
1 parent 3643a1c
commit 1e6ec8f
Show file tree

Hide file tree

Showing 45 changed files with 117 additions and 117 deletions.
diff --git a/content/about.de.md b/content/about.de.md
@@ -63,7 +63,7 @@ Software kann so schnell sein, dass es nicht wahrnehmbar ist, ob die Nutzung 10m
 
 Um all diese getrennten Bereiche für die EntwicklerInnen sichtbar zu machen, entwickeln wir Open-Source-Tools, die den Energieverbrauch sichtbar machen.
 
-Für nutzerorientierte Anwendungen in der Desktop-, Web- und mobilen Welt entwickeln wir ein Tool zur Messung des gesamten Anwendungslebenszyklus auf der Grundlage eines eines Standardnutzungsszenarios: Das [Green Metrics Tool] (https://github.com/green-coding-services/green-metrics-tool)
+Für nutzerorientierte Anwendungen in der Desktop-, Web- und mobilen Welt entwickeln wir ein Tool zur Messung des gesamten Anwendungslebenszyklus auf der Grundlage eines eines Standardnutzungsszenarios: Das [Green Metrics Tool] (https://github.com/green-coding-berlin/green-metrics-tool)
 
 Durch die Verknüpfung von der Version des Codes und eines Nutzungsszenarios können wir verschiedene Software miteinander vergleichbar machen.
 
@@ -130,7 +130,7 @@ Die Lösung liegt unserer Meinung nach darin, diese Ressource sichtbarer zu mach
 Wir befassen uns derzeit mit diesem Thema, indem wir Entwickler durch [Meetups](/meetups-and-events/) und durch
 Vorträge auf Konferenzen oder Coding Bootcamps wie [WBS Coding School](https://www.wbscodingschool.com/)
 
-Auf der technischen Seite heben wir die Netzwerkemissionen in unserem [Green Metrics Tool](https://github.com/green-coding-services/green-metrics-tool) hervor und zeigen Empfehlungen wie:
+Auf der technischen Seite heben wir die Netzwerkemissionen in unserem [Green Metrics Tool](https://github.com/green-coding-berlin/green-metrics-tool) hervor und zeigen Empfehlungen wie:
 
 - Verlagerung von Mobilfunk- zu Festnetzanschlüssen
 - Demand Shifting, um Netzwerkanfragen zu CO2 freundlichen Zeiten zu erledigen

diff --git a/content/about.md b/content/about.md
@@ -62,7 +62,7 @@ is hard to estimate if scaled up.
 To make all of these separate domains visible to the developer we are creating open source tools to make the energy visible.
 
 For user facing applications in the desktop, web and mobile world we are creating a tool to measure the whole application lifecycle based
-on the concept of a Standard Usage Scenario: The [Green Metrics Tool](https://github.com/green-coding-services/green-metrics-tool)
+on the concept of a Standard Usage Scenario: The [Green Metrics Tool](https://github.com/green-coding-berlin/green-metrics-tool)
 
 By pinning the code version and the usage scenario we can make different softwares comparable to each other.
 
@@ -136,7 +136,7 @@ way of interacting with it.
 We currently address this topic by educating developers through [Meetups](/meetups-and-events/) and through
 talks at conferences or coding bootcamps like [WBS Coding School](https://www.wbscodingschool.com/)
 
-On the technical site we highligh the network emissions in our [Green Metrics Tool](https://github.com/green-coding-services/green-metrics-tool) and show
+On the technical site we highligh the network emissions in our [Green Metrics Tool](https://github.com/green-coding-berlin/green-metrics-tool) and show
 recommendations like
 - Moving connection from mobile to fixed-line
 - Demand Shifting to do network requests in carbon-friendly times

diff --git a/content/blog/adventures-in-dc-measurement.md b/content/blog/adventures-in-dc-measurement.md
@@ -95,7 +95,7 @@ The linux measurement client is a breeze and signals looked directly accurate wi
 
 For inital testing we opted for a simple 0.5 Ohms inline shunt resistor that is measured in the differential measurement mode.
 
-The code for importing the measurements is very simple Python. If you want to have a look at it, you can find it in our [dev branch](https://github.com/green-coding-services/green-metrics-tool/blob/dev/tools/dc_converter.py).
+The code for importing the measurements is very simple Python. If you want to have a look at it, you can find it in our [dev branch](https://github.com/green-coding-berlin/green-metrics-tool/blob/dev/tools/dc_converter.py).
 
 
 ## Judgment of the measurement quality

diff --git a/content/blog/carbon-aware-development.md b/content/blog/carbon-aware-development.md
@@ -25,7 +25,7 @@ The server we are developing should do three simple things:
 
 Like pretty much with any project we start by creating a docker file and specifying what components we need initially. Details can be found in the GitHub repo:
 
-[https://github.com/green-coding-services/SLCA-Code](https://github.com/green-coding-services/SLCA-Code)
+[https://github.com/green-coding-berlin/SLCA-Code](https://github.com/green-coding-berlin/SLCA-Code)
 
 For this example we use a simple setup with a [FastAPI](https://fastapi.tiangolo.com/) and a database in the background. Because I am used to [PostgreSQL](https://www.postgresql.org/) my initial setup includes this but the way we are setting this up we can easily benchmark different backends in the future.
 

diff --git a/content/blog/cloud-energy-usage-data.md b/content/blog/cloud-energy-usage-data.md
@@ -41,7 +41,7 @@ A new project by the Green Software Foundation is also focussing on making this
 ## Using estimation models
 
 If you cannot measure you have to estimate. We have written a prior [blog article](https://www.green-coding.io/blog/specpower-model-with-xgboost-open-sourced/) about how this can be done with an
-easy machine learning model and provided an [extensive documentation on Github](https://github.com/green-coding-services/spec-power-model) how to discover the needed input parameters.
+easy machine learning model and provided an [extensive documentation on Github](https://github.com/green-coding-berlin/spec-power-model) how to discover the needed input parameters.
 
 However sometimes you need auxillary information like more details about the hypervisor and also which machine specific registers (MSRs) are accessible
 on the machine as you might want to leverage some MSRs to provide more information about the machine.

diff --git a/content/blog/eco-ci-activity-checker-released.md b/content/blog/eco-ci-activity-checker-released.md
@@ -12,7 +12,7 @@ author: "Dan Mateas"
 
 One question we've been tinkering around with here at Green Coding Solutions is how can we make CI pipelines around the world a little bit greener.
 
-We have noticed the constantly rising popularity of [Github Actions](https://github.com/features/actions) and its use in various CI jobs such as automated tests. We use it ourselves for this reason in [our open-source repository](https://github.com/green-coding-services/green-metrics-tool/actions). One nice feature of github actions is its marketplace where you can find and use publically published "Actions" in your workflow.
+We have noticed the constantly rising popularity of [Github Actions](https://github.com/features/actions) and its use in various CI jobs such as automated tests. We use it ourselves for this reason in [our open-source repository](https://github.com/green-coding-berlin/green-metrics-tool/actions). One nice feature of github actions is its marketplace where you can find and use publically published "Actions" in your workflow.
 
 So we asked ourselves, what kind of Action should exist that would help make our (and others') automated test runs a bit greener?
 
@@ -32,9 +32,9 @@ jobs:
       recent_dev_commit: ${{ steps.check_dev_commits.outputs.recent_commit }}
     steps:
       - id: check_dev_commits
-        uses: green-coding-services/eco-ci-activity-checker@v1
+        uses: green-coding-berlin/eco-ci-activity-checker@v1
         with:
-         repo: 'green-coding-services/green-metrics-tool'
+         repo: 'green-coding-berlin/green-metrics-tool'
          branch: 'dev'
          time-unit: 'day'
          time-value: '1'

diff --git a/content/blog/eco-ci-energy-estimation.md b/content/blog/eco-ci-energy-estimation.md
@@ -13,23 +13,23 @@ authorlink: "https://www.linkedin.com/in/dan-mateas-693634105/"
 
 As we mentioned in a [previous blog article](https://www.green-coding.io/blog/eco-ci-activity-checker-released/), we've been thinking of ways to make CI pipelines more energy efficient. One idea we had was to give developers a tool which allows them to measure the energy used by their CI runs.
 
-After all, how can people reduce their carbon emissions if they don't know how much energy they're using in the first place? With that in mind we're happy to announce a new Action which we're publishing to the Github Actions marketplace: [Eco CI Energy Estimation](https://github.com/green-coding-services/eco-ci-energy-estimation)
+After all, how can people reduce their carbon emissions if they don't know how much energy they're using in the first place? With that in mind we're happy to announce a new Action which we're publishing to the Github Actions marketplace: [Eco CI Energy Estimation](https://github.com/green-coding-berlin/eco-ci-energy-estimation)
 
 This action measures the CPU used by the machine running your github VM and then uses our [Cloud energy](/projects/cloud-energy) model to estimate the energy used by whichever sections of your workflow file you wish to measure. It is designed to be easily integrated into any workflow file you may already have with just a couple of calls. Let's run through how to set up and use it.
 
 The action has three *tasks* it can be invoked with: `initialize`, `start-measurement`, and `get-measurement`:
 ```
-- uses: green-coding-services/eco-ci-energy-estimation@v1
+- uses: green-coding-berlin/eco-ci-energy-estimation@v1
         with:
           task: initialize
 ```
 ```
-- uses: green-coding-services/eco-ci-energy-estimation@v1
+- uses: green-coding-berlin/eco-ci-energy-estimation@v1
         with:
           task: start-measurement
 ```
 ```
-- uses: green-coding-services/eco-ci-energy-estimation@v1
+- uses: green-coding-berlin/eco-ci-energy-estimation@v1
         with:
           task: get-measurement
 ```

diff --git a/content/blog/eco-ci-gitlab-release.md b/content/blog/eco-ci-gitlab-release.md
@@ -8,10 +8,10 @@ authorlink: "https://www.linkedin.com/in/dan-mateas-693634105/"
 
 We are happy to announce a major update to our Eco-CI tool, a plugin designed to estimate and reduce the energy consumption of continuous integration pipelines. Previously available exclusively for GitHub Actions, we are excited to announce the integration of Eco-CI with GitLab pipelines. We hope this will encourage Gitlab developers to measure their carbon emissions and make informed decisions regarding sustainable software processes.
 
-Link to Release: [Eco-CI Energy Estimation v2](https://github.com/green-coding-services/eco-ci-energy-estimation/releases/tag/v2)
+Link to Release: [Eco-CI Energy Estimation v2](https://github.com/green-coding-berlin/eco-ci-energy-estimation/releases/tag/v2)
 
 To use Eco-CI with Gitlab pipelines, we provide the following template file which can be included in your `gitlab-ci.yml` configuration
-See here an [example configuration](https://github.com/green-coding-services/eco-ci-energy-estimation/blob/main/eco-ci-gitlab.yml)
+See here an [example configuration](https://github.com/green-coding-berlin/eco-ci-energy-estimation/blob/main/eco-ci-gitlab.yml)
 
 You can include the raw file remotely like this:
 
@@ -65,7 +65,7 @@ To see your energy results, you can check the artifacts for each job, or check t
 {{< /rawhtml >}}
 
 \
-We are currently also exploring further methods to output this information to developers. Full instructions on how to use Eco-CI with GitLab pipelines are available in the [ReadMe](https://github.com/green-coding-services/eco-ci-energy-estimation/blob/main/README.md#gitlab).
+We are currently also exploring further methods to output this information to developers. Full instructions on how to use Eco-CI with GitLab pipelines are available in the [ReadMe](https://github.com/green-coding-berlin/eco-ci-energy-estimation/blob/main/README.md#gitlab).
 
 ### Front End
 
@@ -83,7 +83,7 @@ We have improved the front end we provide on [our website](https://metrics.green
 ## Open Source Projects we're monitoring
 As part of our goal to encourage green coding practices, and understand what features / wishes a developer working on real-world projects with a green coding mindset would want, we decided to fork some popular open source repositories and integrate the Eco-CI into their existing workflows. This gives us insight on how easy it is to use, what features are missing, what real-world edge cases don't work, and how valuable the information we provide actually is and what we can do to improve it.
 
-Currently we have forked and integrated three github projects: [Django](https://github.com/green-coding-services/django), [Flask](https://github.com/green-coding-services/flask), and [curl](https://github.com/green-coding-services/curl), as well as one Gitlab project, [OpenMW](https://gitlab.com/green-coding-services/eco-ci/openmw). Our plan is to pretend that we are sustainability engineers for these projects, keep them in sync, track their carbon footprint, and see what we can improve on with this information.
+Currently we have forked and integrated three github projects: [Django](https://github.com/green-coding-berlin/django), [Flask](https://github.com/green-coding-berlin/flask), and [curl](https://github.com/green-coding-berlin/curl), as well as one Gitlab project, [OpenMW](https://gitlab.com/green-coding-berlin/eco-ci/openmw). Our plan is to pretend that we are sustainability engineers for these projects, keep them in sync, track their carbon footprint, and see what we can improve on with this information.
 
 Doing this has already begun to generate some ideas for us, so be on the lookout for new features in the coming weeks!
 

diff --git a/content/blog/energy-measurement-progress.md b/content/blog/energy-measurement-progress.md
@@ -23,7 +23,7 @@ very conscise and scoped functionality, but can be chained through redirecting
 their output.
 
 For the moment we are working on the documentation. If you want to have an early
-look be sure to check out the [development branch](https://github.com/green-coding-services/green-metrics-tool/tree/rapl-and-cgoup-reader)
+look be sure to check out the [development branch](https://github.com/green-coding-berlin/green-metrics-tool/tree/rapl-and-cgoup-reader)
 
 Also we have made progress on getting the prototype for the DC Measurements
 working and are now coding the Linux metrics providers to read directly from

diff --git a/content/blog/firefox-104-energy-measurements.md b/content/blog/firefox-104-energy-measurements.md
@@ -23,7 +23,7 @@ Mozilla released a new [version 104](https://www.mozilla.org/en-US/firefox/104.0
 {{< /rawhtml >}}
 
 This immediately sparked our interest and we wanted to give it some test run against
-a containerized browser in our [Green Metrics Tool](https://github.com/green-coding-services/green-metrics-tool).
+a containerized browser in our [Green Metrics Tool](https://github.com/green-coding-berlin/green-metrics-tool).
 
 According to the information from Mozilla this works only for M1 Macs or on Windows 11.
 

diff --git a/content/blog/github-resources-repo.md b/content/blog/github-resources-repo.md
@@ -24,11 +24,11 @@ categorised content.
 
 The most helpful at this point are probably:
 
-- [Green Software Engineering Web](https://github.com/green-coding-services/links-documents-resources/blob/main/Links/Green-Software-Engineering-Web.md)
+- [Green Software Engineering Web](https://github.com/green-coding-berlin/links-documents-resources/blob/main/Links/Green-Software-Engineering-Web.md)
 
-- [Green Software Engineering Articles / Blogs / Personas](https://github.com/green-coding-services/links-documents-resources/blob/main/Links/Green-Software-Engineering-Personas-Organizations.md)
+- [Green Software Engineering Articles / Blogs / Personas](https://github.com/green-coding-berlin/links-documents-resources/blob/main/Links/Green-Software-Engineering-Personas-Organizations.md)
 
-- [Green Software Engineering Desktop](https://github.com/green-coding-services/links-documents-resources/blob/main/Links/Green-Software-Engineering-Desktop.md)
+- [Green Software Engineering Desktop](https://github.com/green-coding-berlin/links-documents-resources/blob/main/Links/Green-Software-Engineering-Desktop.md)
 
 The most promising link in there is probably the Green Software Foundation and
 their planned [Green Software Projects](https://greensoftware.foundation/projects)

diff --git a/content/blog/green-metrics-measurement-tool.md b/content/blog/green-metrics-measurement-tool.md
@@ -12,7 +12,7 @@ usage.
 The tool is fully open sourced under MIT license and can be used and copied
 by anyone for any purpose.
 
-All code is available on Github: https://github.com/green-coding-services/green-metrics-tool
+All code is available on Github: https://github.com/green-coding-berlin/green-metrics-tool
 
 &nbsp;
 ## About the tool
@@ -45,7 +45,7 @@ repository must contain a usage_scenario.json in a correct format and
 currently only supports command line applications.
 
 To test the flow of the green metric tool we provide a ready made demo software
-that you can test: [https://github.com/green-coding-services/green-metric-demo-software](Github Repository for the Demo software)
+that you can test: [https://github.com/green-coding-berlin/green-metric-demo-software](Github Repository for the Demo software)
 
 After submitting a URL your software will be tested in 5-15 minutes, depeding on
 the current queue. A link to the result page will be sent via e-mail.
@@ -59,7 +59,7 @@ go to: https://metrics.green-coding.io/
 
 ## Documentation
 The current documentation for the available fields in the prototype is found directly
-in the [https://github.com/green-coding-services/green-metric-demo-software](Github Repository for the Demo software)
+in the [https://github.com/green-coding-berlin/green-metric-demo-software](Github Repository for the Demo software)
 
 
 ## Project timeline

diff --git a/content/blog/nop-linux.md b/content/blog/nop-linux.md
@@ -186,7 +186,7 @@ apt remove -y docker docker-engine docker.io containerd runc
 apt install -y ca-certificates curl gnupg lsb-release
 
 su gc << 'EOF'
-git clone https://github.com/green-coding-services/green-metrics-tool ~/green-metrics-tool
+git clone https://github.com/green-coding-berlin/green-metrics-tool ~/green-metrics-tool
 cd ~/green-metrics-tool
 git submodule update --init
 python3 -m pip install -r ~/green-metrics-tool/requirements.txt

diff --git a/content/blog/power-measurement-on-macos.md b/content/blog/power-measurement-on-macos.md
@@ -10,8 +10,8 @@ Last week we have been on the [SDIA event for sustainble software](https://sdial
 a workshop on measuring the energy digital products.
 
 We presented approchaes where you measure the energy either with tool like [Scaphandre](https://github.com/hubblo-org/scaphandre) or
-the [Green Metrics Tool](https://github.com/green-coding-services/green-metrics-tool) as well as approaches for restricted environments like the cloud.
-Here the [SDIA DEF Model](https://knowledge.sdialliance.org/digital-environmental-footprint) and our [SPECPower linear model](https://github.com/green-coding-services/spec-power-model) where presented.
+the [Green Metrics Tool](https://github.com/green-coding-berlin/green-metrics-tool) as well as approaches for restricted environments like the cloud.
+Here the [SDIA DEF Model](https://knowledge.sdialliance.org/digital-environmental-footprint) and our [SPECPower linear model](https://github.com/green-coding-berlin/spec-power-model) where presented.
 
 What the two former tools have in common though is that they are designed to work
 exclusively on Linux.

diff --git a/content/blog/releasing-code-bench.md b/content/blog/releasing-code-bench.md
@@ -25,7 +25,7 @@ Currently we only include a very limited set of python functions that can be opt
 
 Find the code under:
 
-https://github.com/green-coding-services/code-benchmark
+https://github.com/green-coding-berlin/code-benchmark
 
 We have included a Green Metrics Tool `usage_scenario.yml` file so you can benchmark the code with the GMT. Currently the problems are all CPU bound but we will extend this to also have some memory or IO bound problems that can be optimised.