Bug tracker import code/adding a bug tracker (moved): Difference between revisions

Content added Content deleted

Inline

Latest revision as of 18:49, 22 August 2012

This is a page about improving or modifying OpenHatch.

We call that "Hacking OpenHatch," and there is a whole category of pages about that.

We are updating our documentation system. This page is now included in our project package, and is automatically generated by sphinx at openhatch.readthedocs.org Bug tracker import code/Adding a bug tracker

@@ Line 1: / Line 1: @@
+{{Hacking OpenHatch}}
-== About this page ==
+We are updating our documentation system. This page is now included in our project package, and is automatically generated by sphinx at openhatch.readthedocs.org [http://openhatch.readthedocs.org/en/latest/internals/adding_bug_tracker.html Bug tracker import code/Adding a bug tracker]
-There are other pages about our [[bug tracker import code]].
-== Step by step ==
-=== Clone the repository ===
-You will need to have a local copy of our git repository. You can read about that at [[getting started with the OpenHatch code]].
-=== Figure out what kind of bug tracker you're importing ===
-To find the bug tracker import code, do:
-    $ cd mysite/customs/bugtrackers/
-All our code lives inside "mysite". "customs" contains code that handles the ''importing'' of data from other places on the Internet. (Get it? It's a pun.) "bugtrackers" holds one file per type of bug tracker.
-You'll find one file per ''type'' of bug tracker. For example, if you're adding code to cause us to import data from a bug tracker that runs the ''Roundup'' software, you'll need to be editing ''roundup.py''.
-=== Edit the right file ===
-Each file has two parts...
-=== Submit a patch ===