The ImpactXchange hackathon is an event where the students co-design a green coding hackathon for Malaysian students in one week and test it themselves in the second week.

• Objective: Design a two-week hackathon/course (Green Coding) to be held for Malaysian students in August 2024, with the following parts.
  • Defining the hackathon challenge
  • Designing the solution for the given challenge
  • Tools for developing the solution
  • Measuring the footprint of the solution
  • Assessing the impact of the solution
• Participation onsite in the Linux classroom during the hackathon time or teamwise in zoom (952 720 9283).
• Schedule: First-week Mon-Fri planning of the Hackathon, Second-week Mon-Tue testing of the hackathon concept.
• Grading will be: Pass/Fail
• Evaluation (for the winners):
  • Teams will be evaluated based on each part (Defining, Designing, Developing, Measuring, Assessing, and actually testing the Hack concept).

While defining the hackathon challenge, one should consider how to start the Green Coding Hack in Malaysia and instruct the students to start thinking of the challenge they want to solve using software solutions (Remember Elina's words in KTH that not all challenges are solvable by software).

Requirements for the hackathon setup

• Topic needs to be linked with sustainability and software development
• Hackathon setup can be a high-level challenge (e.g., select an SDG and design and develop a solution for that), a predefined topic (e.g., Focus on SDG4 and education solutions in a developing countries), or a detailed level (e.g., each team should design and implement a dashboard for the given CSRD data visualization). In this task, you provide a proposal for all three approaches.

You should consider the following when giving instructions

• What is the group size you allow/prefer
• Do you have any specific requirement for the topic a team selects
• What do the students have/present when they have selected their topic

The outcome of this phase:

• Presentation of all 3 approaches: high-level to detailed (what you select in each of those is up to the team) presented as you would present them to the students of your hackathon.
• Each team has 15 minutes to present their Hackathon setups.

ImpactXchange material

• Material for setting up the hackathon

For the ImpactXchange hackathon in Finland, we use “Waste management” as an application domain to help identify the necessary technologies.

In designing the solution, the technologies are divided into three parts (one per team)

• Backend - some cloud environment behind your solution (e.g., Google Cloud), data management activities, …)
• Mobile frontend - selection of technologies that enable the development of mobile frontend for multiple environments
• Web frontend - selection of technologies enabling whatever actions you plan for the web interface (e.g., management of the solution)

Teams are supposed to

• select technologies for the development of the intended features in each part of the implementation
• find material/guidelines that help approach each part of the implementation
• create guidelines for the hackathon participants to start developing different parts.

Outcome:

• Guidelines for backend development
• Guidelines for mobile frontend development
• Guidelines for web frontend development

The work on this phase is divided in two parts

• Search for suitable tools for the development of green code (analysis, development, guidelines)
• Application of those tools on various parts of the solution architecture (backend, mobile frontend, web frontend)

What do we need to measure in green solution

• e.g. data transferred between the backend and frontend
• …

Tools and frameworks for green code development

• e.g. Vincit planet centric toolkit - (short explanation here, more behind the link)
• Aalto University - Green Page Analyzer -
• Green Frame - open-source solution that allows developers to decarbonize their websites by detecting carbon leaks
• Digital Beacon - compares first and return visit to the websit
• Globemallow - a browser add-on that generates a report on the environmental sustainability of the website and gives advice on how to optimize it
• Website Carbon - estimates the carbon emissions attributed to a website.
• Google Cloud Carbon Footprint - Measures, reports, and reduces your cloud carbon emissions
• EcoGrader - Gives extremely comprehensive analysis of your website
• Simapro - Gives science-based sustainability insights,and helps you become informed
• Sonar Source - Helps detect and inform developers of unsustainable coding practices
• Green Software Foundation - Helps with keeping sustainability in mind during the development process
• Green Algorithms - Metrics on algorithm footprint
• Blacklight - discovers trackers on a website
• Green Spector - measure & analyse environmental impact of Apps
• Emission Impact Dashboard - estimate your carbon emissions
• Joular JX - Java-based agent for software power monitoring
• Power API - set of tools for green computing
• Cloud Carbon Footprint - measure & monitor carbon emissions
• Sonar Qube - tool to ensure good code quality
• Containerization - Containerization promotes sustainability by enhancing resource utilization
• Eco2AI - python library for CO2 emission tracking
• Carbon Aware SDK - toolset to measure carbon emission
• Lighthouse - dev tools tab that offers most of above mentioned analyses
• WebPack - Code and media minifaction tool

Phase 4 aims to answer the question of how to evaluate (in hackathon) that your part (backend, mobile, web) is efficient (green) and how to follow these aspects on the development project (both team itself and the evaluators of the hackathon).

In order to answer the questions …

Add more table lines if those are needed for additional teams!