|
|
| Line 1: |
Line 1: |
| == Status reports for Season of KDE 2024 == | | == Status reports for Season of KDE 2024 == |
| <h1>Testing and development of KEcoLab</h1>
| |
|
| |
| '''Project Type''': Planning and scripting
| |
|
| |
| '''Introduction and Abstract''': Sustainability is a key goal for KDE over the next two years. One aspect of this goal is to measure the energy consumption of KDE softwares. To do this, it is necessary to access lab in KDAB, Berlin, which can be done remotely using KEcoLab.
| |
|
| |
| '''Mentor''': Joseph P. De Veaugh-Geiss, Karanjot Singh
| |
|
| |
| <h3>Weekly Progress</h3>
| |
| '''WEEK 1 - 2''': I've established Selenium on three virtual machines (Kubuntu, Fedora, Ubuntu) for simultaneous testing. I conducted thorough KecoLab testing, identifying and reporting bugs to enhance its quality. Proactive communication was initiated with the Okular team for pipeline integration and with KdeEcoTest contributors regarding Wayland support timelines. Additionally, Also, resolved the dynamic IP issue for Powemeter access, streamlining testing processes.
| |
|
| |
|
| |
|
| |
|
| |
|
| A good status report will include: | | A good status report will include: |
Revision as of 07:36, 6 February 2024
Status reports for Season of KDE 2024
A good status report will include:
- Design documents the student created
- Short video of the work, or screenshots as appropriate
- Link to a list of commits (example)
- Link to blog posts (on KDE Planet)
Students list
Please keep the list sorted.
- TODO
