KTp/Getting Involved: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
{{:Real-Time_Communication_and_Collaboration/Header}} | {{:Real-Time_Communication_and_Collaboration/Header}} | ||
==Who can be a contributor?== | |||
This project needs people from all skillsets; coders, designers, artists, testers, documentation writers. | |||
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! | |||
==Setting Up== | ==Setting Up== | ||
Revision as of 15:16, 23 July 2012
Who can be a contributor?
This project needs people from all skillsets; coders, designers, artists, testers, documentation writers.
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!
Setting Up
Before you start playing with/hacking on the Telepathy integration stuff, you need to have the latest version compiling and working: Instructions
Contacting Us
IRC
#kde-telepathy channel on irc.freenode.net
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).