KDE Frameworks/Getting Started: Difference between revisions
(→Getting Help: flesh out the getting help section) |
|||
| Line 20: | Line 20: | ||
If you are looking for help in using KDE Plasma or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase]. | If you are looking for help in using KDE Plasma or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase]. | ||
Before you continue with this guide, it is a good idea to get on <abbr title="Internet Relay Chat">IRC</abbr>. This is a realtime text communication system, and the primary "casual" communication tool for KDE developers. | |||
You will need a way to connect to the freenode IRC network. We suggest [https://konversation.kde.org/ Konversation] (see the [https://docs.kde.org/trunk5/en/extragear-network/konversation/index.html handbook] for help in setting it up), although a convenient alternative if you want to get going quickly is freenode's [http://webchat.freenode.net/ online webchat]. You will need to choose a ''nick'' (the name you appear on the network as), [http://freenode.net/using_the_network.shtml connect to freenode] and join [irc://irc.kde.org/kde-devel #kde-devel]. | |||
The other main channel for communication is the KDE mailing lists. To start with, you should subscribe to [https://mail.kde.org/mailman/listinfo/kde-devel the kde-devel list] (you will need to subscribe before you can send emails to the list). | |||
For more information about getting help, see the main [[Special:myLanguage/Development/Getting_Help|Getting Help]] page, and remember that applications often have their own IRC channels and mailing lists that can be better places to ask for help. | |||
Be patient while waiting for a response, and try to work through the problem yourself: we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way. | Be patient while waiting for a response, and try to work through the problem yourself: we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way. | ||
Revision as of 09:00, 29 August 2015
| Under Construction |
|---|
| This is a new page, currently under construction! |
Introduction
There are many different ways to become involved in the KDE Community, starting with simply using our software. This guide is to help you get started on the technical side of developing the software itself.
It is important to note that the version of KDE Software that is provided by your distribution or downloaded via an installer is not the same as the version that is being worked on by software developers. If you are using KDE CoolApp 1.2, the developers are working on the "development" version, usually called "KDE CoolApp master". This is the version that will become KDE CoolApp 1.3, or maybe 2.0. If you want to get involved in developing KDE Software, you will need to get hold of and build the development versions.
This guide will aim to show you how to build, run and help improve the development versions of KDE Software. We will primarily be looking at submitting a patch to change the software, but the information here is also useful if you want to test whether a bug still exists in the software, for example.
If you just want to get started building the code then you can skip to the build instructions, but it is recommended you first understand the background material presented here.
Getting Help
If you are looking for help in using KDE Plasma or KDE Applications then please visit the KDE UserBase.
Before you continue with this guide, it is a good idea to get on IRC. This is a realtime text communication system, and the primary "casual" communication tool for KDE developers.
You will need a way to connect to the freenode IRC network. We suggest Konversation (see the handbook for help in setting it up), although a convenient alternative if you want to get going quickly is freenode's online webchat. You will need to choose a nick (the name you appear on the network as), connect to freenode and join #kde-devel.
The other main channel for communication is the KDE mailing lists. To start with, you should subscribe to the kde-devel list (you will need to subscribe before you can send emails to the list).
For more information about getting help, see the main Getting Help page, and remember that applications often have their own IRC channels and mailing lists that can be better places to ask for help.
Be patient while waiting for a response, and try to work through the problem yourself: we aren't going to do it all for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.
Development Policies
KDE Software is a very large, diverse and complex code base and the KDE Community community has developed many policies and processes to make the KDE Software development process a lot easier. These are documented elsewhere in TechBase and you should try to familiarise yourself with them over time. You should also learn any specific contribution guidelines for the application that you might be working on.
Don't feel you have to read through every single KDE policy before you even send your first patch. Start with the code of conduct, as this is the basis for interacting with the KDE Community in general. When it comes to contributing code, the most important thing to get right is how to send your contribution (see the section about contributing). Maintainers and other contributors will be more familiar with the technical policies, and will help you make your contribution adhere to them while you are still starting out.
- The KDE Community Manifesto that all KDE Projects follow
- The KDE Community Code of Conduct that all KDE Community members must adhere to
- Development Policies and Procedures to follow
- The KDE Software Engineering Framework
- The development lifecycle for a new application
- The KDE Release Schedule
Build And Run
The following sections explain the steps you need to successfully build and run KDE Software from source:
- How the KDE Software source code is structured
- How to Build and Install KDE Software
- Development Tools useful in developing KDE Software
Contributing
Once you have a copy of KDE Software built you can then start contributing code back to the KDE Community. The pages below will help you find out how you can help make KDE Software even better.