Junior Jobs for all projects within KDE.
Details
Mar 14 2023
Jan 13 2023
Sorry of the late reply. By unknown state I mean the case in which we return "camera.metering.unknown". in Battery.swift. There's probably a case in which it is truly needed, but currently it's hard to reason when that's the case.
Nov 10 2022
Hi @apollozhu, I'm currently working on this feature as well as the "unknown states" issues you mentioned. It would be great if you can give me more details about those unknown states.
Oct 27 2022
Oct 4 2022
Sorry for not getting to this earlier, looks good to me!
Aug 24 2022
I'd want to work on this issue. Can someone direct me to the appropriate resources? I'm pretty new to C++ coding.
Aug 16 2022
I would like to propose this mapping for the percentage symbols:
Apr 24 2022
Merged
Mar 28 2022
Created an MR with these changes :)
Mar 25 2022
Merged.
Hi, I opened a PR with this change here: https://invent.kde.org/network/kdeconnect-ios/-/merge_requests/59
Mar 24 2022
Hi, I just opened an MR with this change :)
Mar 6 2022
Beautiful!
Feb 28 2022
Feb 24 2022
The redesign has finished. Let's close this.
Jan 2 2022
Note: currently Backend.swift contains a large number of unrelated functionalities, it might be a better idea to create a new file for each functionality (starting from the new changes, and gradually expanding to existing code)
Dec 31 2021
Mar 29 2021
Mar 1 2021
Feb 28 2021
I believe it's coming along nicely. However, I did notice that colors, themes and styles are all over the place in the project. Perhaps something I can work on after this is done :)
Feb 23 2021
Sorry that I have given such a limited context, as @vibhav said, this task is about updating the look of the icons so they appear modern, the gradient is pretty dated.
Anyone interested can take on this task since artistic development falls off of my expertise/interest.
Considering no updates on this, can I take this over?
Feb 16 2021
Jan 25 2021
There is some ongoing work in https://invent.kde.org/network/kdeconnect-android/-/merge_requests/219
Hello,
Is someone working on this? I'd like to work on this as my first task, if it's available.
Jan 21 2021
Jan 20 2021
The logic should be done inside the main memory activity, but also each of the memory not-against-tux should have its own ActivityConfig.qml.
also the player will choose the game mode, right?
to make sure, this will be done in "memory" folder, right?
or it will be done in each memory folder?
The former (add an optional extra mode played by 2 children)
I want to make sure if I understand correctly, in all memory activities (not with against Tux) must have 2 modes, the first mode which is played by 1 child and this is already done, the second mode will be an extra mode and will be played by 2 children, right?
or it will always by played by 2 children?
Jan 4 2021
Dec 19 2020
PLOT TWIST