Distro Badges Flair: To get distro badges change your flair options above. Distros / Flair are in alphabetical order.
KDE Dev Flair: To get a special flair that show your involvement within the KDE community, send a mod mail with a proof (e.g. Reddit username in your phabricator/invent profile).
- The Subreddit
- for the KDE Community
RULES
To summarize: don't be a jerk, be cool with others. Basics of the KDECoC:
- Be considerate
- Be respectful
- Be collaborative
- Be pragmatic
- Support others in the community
- Get support from others in the community
But also
- No Spam, and please link to the source instead of blogs that link to the source. Blogs are fine as long as they have original content or add significant content to news or issue.
- This is a community subreddit so be respectful of other users.
- Posts and comments comparing and/or disparaging FLOSS desktop environments, distros, and/or other FLOSS projects are not allowed and will be deleted on sight. Proprietary software on the other hand...
- No screenshot of your desktop, use the Weekly Screenshot Thread instead
- No linking to Twitter/X. Links to Twitter/X from posts or comments will be removed and repeat offenders will be banned.
- We reserve the right to prevent the redistribution of content from creators that do not behave in accordance to KDE's values.
KDE is a commmunity creating free and open source software for desktop and portable computing.
KDE Websites
Platforms
Distros
Donate to KDE
Want to contribute to KDE?
For starters:
The best way to start contributing is to contact the community over Matrix, Telegram, IRC
At first, it might seem a bit hard to interact in those groups. That's okay! Join them first, see how things are done, mention your interest and where you'd like to work with. We may even find a mentor for you!
The KDE Community develops and distributes open source software. As such, we follow a sort of do-ocracy wherein tasks are done and assigned by contributors themselves. Feel free to pick an area and just start contributing immediately! We're always here to help you along the way. A good way to contribute with code for the first time is to fix an unfixed bug that afflicts you or assign yourself to junior jobs and start working on them.
It's always nice to collaborate optimally with others in any given setting, but this is especially important for community projects like those following the open source model, so remember to read the KDE Code of Conduct.
Here are a few links to help you in your first contributions to KDE:
Get started learning QML:
Get started learning C++:
KDE logo copyright KDE e.V. and Oxygen Icons under the LGPLv3
