OpenVeda Playbook: KDE

Your guide to contributing to one of the world's largest and oldest open-source software communities.

1. The "Why": Mission & Impact

• The Mission: KDE is a global team dedicated to creating a free and user-friendly computing experience, offering an advanced graphical desktop, and a wide variety of applications for communication, work, education, and entertainment. They create the Plasma Desktop, a popular alternative to Windows and macOS.
• Your Impact: You can work on anything from the core desktop shell to a simple calculator or a powerful video editor. Your code will be used by millions of Linux users around the world.
• Why it's great for your career: Contributing to KDE demonstrates a mastery of C++ and the powerful Qt framework. It shows you can work in a massive, decades-old codebase and a highly structured, international community.

2. The "What": Tech Stack

• Core Language: C++. The vast majority of KDE software is written in C++.
• Core Framework: Qt. A deep understanding of the Qt framework is essential.
• Scripting/UI: QML and JavaScript are used for creating modern, dynamic user interfaces.
• Key Tools: GitLab (at invent.kde.org) for code, Bugzilla for bug tracking, Matrix and Mailing Lists for communication.

3. The "How": Your Onboarding Journey

3.1: Join the Community

• Primary Channel (Matrix): The KDE community is migrating to Matrix for real-time chat.
  • Link: Join the KDE Matrix Space
  • Your First Action: Join the #kde-welcome channel and introduce yourself.
• Secondary Channel (Mailing Lists): Different teams have their own mailing lists for deeper discussions.

3.2: The Setup Guide

• Official Guide: KDE has a dedicated "Get Involved" portal with excellent guides.
  • Link: Getting Involved with KDE Development
• OpenVeda Pro-Tip: Follow the guide for setting up KDE neon Unstable edition in a virtual machine or on a spare computer. This provides you with the perfect, pre-configured environment for development and testing.

3.3: The Contribution Workflow

• Official Guide: The process involves finding a bug on Bugzilla and submitting a "merge request" on GitLab.
  • Link: The KDE Contribution Workflow

4. GSoC History & Focus Areas

• Historical Focus: KDE has participated in GSoC every year since its inception. Projects are incredibly diverse, from writing new applications (like a new music player), to improving core components of the Plasma desktop, to enhancing their educational software suite.
• What Mentors Look For: Initiative and a willingness to learn C++/Qt. The best way to get noticed is to fix a small bug before the GSoC period. The community is very large, so you need to be proactive in communicating with your potential mentor.

5. Key Repositories to Know

• KDE Invent (GitLab): invent.kde.org - Explore the hundreds of projects here. Start with an application you use, like kcalc (the calculator) or kdenlive (the video editor).

6. Find Your First Task Right Now

• The Golden Link: The community curates a list of simple bugs for newcomers on their Bugzilla tracker.
  • Link: Junior Jobs on Bugzilla

7. The Unwritten Rules (Mentor Insights)

• Pick One Thing: The KDE ecosystem is massive. Don't try to learn everything. Pick one application that you find interesting and focus all your energy on becoming an expert in that small part of the universe.
• Build from Source: Just like with other complex projects, your first task is always to successfully compile the application yourself.
• Be a Good Community Member: The KDE community values its culture. Be respectful, be helpful in the chat channels, and follow their Code of Conduct.