Difference between revisions of "KTp/Getting Involved"

< KTp
Jump to: navigation, search
(First Steps: corrected junior jobs url)
(Setting Up)
 
(4 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
==Who can be a contributor?==
 
==Who can be a contributor?==
  
This project needs people from all skillsets; coders, designers, artists, testers, documentation writers.
+
This project needs coders, designers, artists, testers, documentation writers. To help out, get in touch, tell us how you're interested in helping.
 
 
For most the above, get in touch, tell us what you're interested in helping with.
 
 
 
If you're interested in contributing programming, read on!
 
  
 
==Contacting Us==
 
==Contacting Us==
Line 16: Line 12:
  
 
===Email===
 
===Email===
[https://mail.kde.org/mailman/listinfo/kde-telepathy mailing list].
+
[https://mail.kde.org/mailman/listinfo/kde-telepathy KDE-Telepathy mail list]
 
 
  
 
==Setting Up==
 
==Setting Up==
Before you start playing with/hacking on the Telepathy integration stuff, you need to have the latest version compiling and working: [[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: [[KTp/Getting_Set_Up|Instructions]]
  
 
==First Steps==
 
==First Steps==
Line 33: Line 28:
 
* [http://telepathy.freedesktop.org/spec/index.html Telepathy Specs]
 
* [http://telepathy.freedesktop.org/spec/index.html Telepathy Specs]
 
* [http://telepathy.freedesktop.org/doc/telepathy-qt/ Telepathy Qt Documentation]
 
* [http://telepathy.freedesktop.org/doc/telepathy-qt/ Telepathy Qt Documentation]
 +
* [http://www.aosabook.org/en/telepathy.html The Architecture of Open Source Applications: Telepathy]
 
* [http://api.kde.org/ KDE API documentation]
 
* [http://api.kde.org/ KDE API documentation]
 +
* [http://try.github.io/ Learn Git]
  
 
==Workflow==
 
==Workflow==
 
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).
 
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).

Latest revision as of 21:48, 20 January 2017

telepathy-kde_med.png

Welcome to the KDE Telepathy Development Wiki

Current Version: 0.9.0
     project_partner_badge.gif
     commits_spark.pngStats at ohloh.net

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 Us

IRC

#kde-telepathy channel on irc.freenode.net

Email

KDE-Telepathy mail list

Setting Up

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

First Steps

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

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, 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).


This page was last edited on 20 January 2017, at 21:48. Content is available under Creative Commons License SA 4.0 unless otherwise noted.