-
Notifications
You must be signed in to change notification settings - Fork 1
Development Guide
wowus edited this page Sep 14, 2010
·
12 revisions
This page is targeted towards people who wish to write code with the core GoGo team. Hopefully, we can fast-track you to direct commit access to the repository in no time! If you’re just looking to use GoGo, as opposed to writing code for it, you’re looking for Using GoGo, not this page.
- If you don’t already know how to use Git, our source control system, you can learn by going to Being Effective with Git.
- Now that you’re familiar with Git (and hopefully github), instructions for getting the code and building GoGo can be found at Setting Up Your Build Environment.
- If you plan on testing GoGo by running the executable (as opposed to just using the automated test suite), you’re going to need to set up your database. Instructions for this can be found at either [Windows] Setting up The Database or [Linux] Setting up the Database.
- Now that you’re in a position to write code, you need to learn how we do that around here. For that, we have our monolithic Coding Standards.
- Now you’re ready to get hacking! If you’d like to learn more, we have Library Overview which should help you get your bearings. There are a whole bunch of internal docs spread through this wiki, some of which aren’t ever linked to. You can usually find them by scanning the page list to your right for things that interest you.
- If you’re looking for something to help out with, have a look at our bugtracker. I’m sure there’s something in there you can help close!
- For information on where this project is headed (and when), we document that on our Roadmap.
We primarily communicate over IRC, so feel free to ask for help (or just chat!) if you want:
irc.fyrechat.net #gogo