|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| Choosing what you want to work on is more important to the contribution process than it might look like at first, and sometimes a difficult choice to do.
| | See https://develop.kde.org/docs/getting-started/building/help-choosing |
| | |
| If you don't know which project to start working on, there are multiple ways to go about it, but the sole principle behind all of them is this: '''your motivation'''. It is, after all, a contribution to open source software where you'll be spending your time and energy: whether it will be done will depend on you.
| |
| | |
| For that reason, a good place to start is with a small bug or feature in an existing piece of software that personally affects you (something commonly known as "scratching your own itch" in open source land). This can be many things:
| |
| | |
| * A missing feature
| |
| * Broken functionality
| |
| * Unexpected behavior
| |
| * Non-descriptive text
| |
| * Bad application layout
| |
| * etc.
| |
| | |
| By having the issue affect you personally, you will be more inclined to start, go through, and finish your contribution to KDE. This is not a requirement, but it is a strong indicator that you will be able to finish your tasks as a brand new KDE contributor.
| |
| | |
| Below you will see multiple lists of tasks that might inspire you to fix them.
| |
| | |
| Once you have established or have a general idea about what you want to work on, you can [[Get_Involved/development#Where_to_find_the_development_team| get in touch with the existing developers]] and they can help you out by pointing you to the right place in the code and giving advice about how to tackle the problem.
| |
Latest revision as of 22:53, 6 December 2024
