3. About gnome-music
GNOME’s own built-in Music Application.
Written in Python3 using GTK+
Released in August 2013.
Current release version 3.10.2
4.
5. Music’s source code
Source Code is the collection of the files containing the instructions for the
application.
Source code contains more than Thousands of lines of code, and are
divided according to the functions it carries out in the application.
We use version control system for software development.
6.
7. Which project to select ?
Complete beginners: Established projects like Mozilla Firefox, KDE.
Intermediate/ Experienced Programmers: New projects like GNOME-Music
and Linux kernel (Skilled coders).
Non-programmers: Wikimedia and other project’s
documentation, designing, etc.
8. Building the Source Code
Developers use jhbuild, it creates a separate environment inside your OS
and builds the latest repositories directly from source.
Some projects like Mozilla use mach build.
Smaller projects can be directly compiled and tested.
9.
10. Selecting your first bug
Bugs are divided as
•
•
•
•
•
low-hanging fruits (github), in general trivial or easy bugs.
Enhancements.
Major bugs.
Critical.
Blocker.
Each bug has STR (Steps to reproduce) and description about it.
Select a bug which interests you and one that you understand.
Contact mentors and start trying out methods to fix the bug.
11.
12. Communicating with other
Developers
IRC, Xchat, IRCcloud.com, Mibbit
IRC Channel: #gnome-music on irc.gnome.org / GIMPNet (irc.gimp.org)
#gnome-love, #gnome-hackers, #gtk+
13. Create and Test Patch
Changes made in the local codebase that are ready to be pushed to the git
repo.
Steps to Create patch:
Make appropriate changes to the code.
Test the code for regressions.
Commit the changes.
Push it to forked repo.
Pull Request.