Skip to content

Instantly share code, notes, and snippets.

@waldyrious
Last active August 29, 2015 14:07
Show Gist options
  • Save waldyrious/fb74b870ddd5ba0bc45e to your computer and use it in GitHub Desktop.
Save waldyrious/fb74b870ddd5ba0bc45e to your computer and use it in GitHub Desktop.
Mini-guide for Elementary OS development, inspired by https://www.mediawiki.org/wiki/Gerrit/Getting_started

Initial setup

Picking a bug to fix

  1. Bugs that you have experienced yourself (i.e. "scratch your own itch")
  2. Bugs that are targeted to the next milestone (any way to make this link future-proof? https://launchpad.net/elementary/+milestones provides no sorting methods...)
  3. Bugs that have bounties attached bounties
  4. If you're getting started, pick from the bugs marked as "bitesize"

Actually doing the fix

  • Many projects have README and HACKING files in their root directory. And "grep -rl" is a powerful ally.
  • You could also try asking in a comment on the bug report itself.
  • If the bug is reported against the right page, you can just click the link that says "code" up top there and the very first branch is "trunk" (what you'd call "master" if you're familiar with git).

Getting help


Sources / links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment