KTp/Getting Involved: Difference between revisions

From KDE Community Wiki
< KTp
(Update page content (somewhat) and make transcludable for insertion on the main KTp page)
 
(12 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==Setting Up==
<noinclude>{{:KTp/Header}}</noinclude>
Before you start playing with/hacking on the Telepathy integration stuff, you need to have the latest version compiling and working: [[Real-Time_Communication_and_Collaboration/Getting_Set_Up|Instructions]]


==Contacting Us==
=== Who can be a contributor? ===
===IRC===
This project needs coders, designers, artists, testers, documentation writers. To help out, get in touch, tell us how you're interested in helping.
<nowiki>
#kde-telepathy channel on irc.freenode.net
</nowiki>


===Email===
=== Contacting the developers ===
[https://mail.kde.org/mailman/listinfo/kde-telepathy mailing list].
==== IRC ====
* The [https://web.libera.chat/#ircs://irc.libera.chat:+6697/#kde-telepathy '''#kde-telepathy''' IRC channel] on Libera.Chat (web client)


==First Steps==
==== Email ====
The best way to get involved is to start on some "junior jobs". These are small bugs or features that exist in our applications that are a good way to get to learn the code, and learn our workflow process
* The [https://mail.kde.org/mailman/listinfo/kde-telepathy KDE Telepathy mailing list]


A list of junior jobs can be found [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=telepathy&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=junior-jobs&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= here].  
=== Setup ===
:'''''Main page:''''' [[KTp/Getting Set Up|Instructions]]
 
Before you start playing with/hacking on the Telepathy integration stuff, you need to have the latest version compiled and working.
 
=== First steps ===
The best way to get involved is to start working on some "junior jobs". These are small bugs or features that exist in our applications that are a good way to get to learn the code, and learn our workflow process.
 
A list of junior jobs can be found [https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&keywords=junior-jobs&keywords_type=allwords&order=Last%20Changed&product=telepathy here].  


If you want to work on any of those, get in touch!
If you want to work on any of those, get in touch!


==Recommended Reading==
=== Recommended Reading ===
http://telepathy.freedesktop.org/doc/telepathy-qt/classes.html
* [https://telepathy.freedesktop.org/wiki/ Telepathy Wiki]
* [https://telepathy.freedesktop.org/spec/index.html Telepathy Specifications]
* [https://telepathy.freedesktop.org/doc/telepathy-qt/ Telepathy Qt Documentation]
* [https://aosabook.org/en/v1/telepathy.html The Architecture of Open Source Applications: Telepathy]
* [https://api.kde.org/ KDE API documentation]
* [https://docs.github.com/en/get-started/getting-started-with-git GitHub Docs: Getting Started with Git]
 
=== Workflow ===
If you want to work on a feature, start by cloning the git repository from the KDE Invent server. Then create a new branch in the cloned directory and start working there. Try to keep your commits atomic (small and meaningful). Once you are finished working on a single bug or feature, push the branch in your cloned repository back to the KDE Invent server (under your own account) and then use the [https://invent.kde.org/ web interface] to create a Merge Request back to the official repository before asking someone on the developer team to review it. Once it is reviewed, you may be asked to make further changes, but once all concerns are addressed it will be merged into the codebase.


==Workflow==
=== External links ===
If you want to work on a feature, clone the git repository on the server side and then clone your personal clone on your local machine. Make a new git branch and start working there. Try to keep commits small and meaningful. Once you are finished, push the branch on your server-side clone and ask someone of the team to review it. Once it is reviewed, you can merge it on the master repository (or ask someone else to merge it).
* [https://telepathy.freedesktop.org Telepathy home page] (FreeDesktop.org)

Latest revision as of 07:48, 26 February 2024

Project logo Welcome to the
KDE Telepathy Development Wiki
Current Version: 23.07.70

Open Hub project report for KDE Telepathy

KDE Telepathy

Commit Activity Timeline:

more at 

Updated Feb 22, 2024

Who can be a contributor?

This project needs coders, designers, artists, testers, documentation writers. To help out, get in touch, tell us how you're interested in helping.

Contacting the developers

IRC

Email

Setup

Main page: Instructions

Before you start playing with/hacking on the Telepathy integration stuff, you need to have the latest version compiled and working.

First steps

The best way to get involved is to start working on some "junior jobs". These are small bugs or features that exist in our applications that are a good way to get to learn the code, and learn our workflow process.

A list of junior jobs can be found here.

If you want to work on any of those, get in touch!

Recommended Reading

Workflow

If you want to work on a feature, start by cloning the git repository from the KDE Invent server. Then create a new branch in the cloned directory and start working there. Try to keep your commits atomic (small and meaningful). Once you are finished working on a single bug or feature, push the branch in your cloned repository back to the KDE Invent server (under your own account) and then use the web interface to create a Merge Request back to the official repository before asking someone on the developer team to review it. Once it is reviewed, you may be asked to make further changes, but once all concerns are addressed it will be merged into the codebase.

External links

Retrieved from "https://community.kde.org/index.php?title=KTp/Getting_Involved&oldid=100158"