Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2026-01-08 02:08:50 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Copied over Tracks wiki home page

bsag 2011-07-16 05:47:32 -07:00
parent d38fa70a67
commit 449f81de5f
1 changed files with 17 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

39
Home.textile

@ -1,29 +1,24 @@
To clone Tracks:
h1. Welcome to the Tracks Wiki!
<pre>
<code>
mkdir ~/dev/tracks
cd ~/dev/tracks
git clone git://github.com/TracksApp/tracks.git
</code>
</pre>
This wiki is a repository for information about Tracks, partially provided by users. If you'd like to contribute, just ask the TracksApp owners if you can become a contributor (you just need a free GitHub account).
Or you can sign up for a free account on github and fork Tracks using the convenient button.
h2. Overview of Tracks
For help with running the tests, see [[http://www.getontracks.org/wiki/Testing/]]
Tracks is a web application that is specifically designed to implement the Getting Things Done (GTD) methods. That doesn't mean that you can't use it for other kinds of todo tracking. Data is stored in a database (either MySQL, Postgresql or SQLite), and viewed in a web browser via a web server (Apache, Lighttpd or WEBrick among others). This makes it cross-platform as well as being accessible from anywhere that you have web access.
If (when!) you produce a cool new feature or fix a bug, create a patch. If you develop in a branch called 'experiment':
Using the GTD method as a model, there are three main components to Tracks: Next actions, Contexts and Projects.
<pre>
<code>
git diff master..experiment > my_feature.patch
</code>
</pre>
* *Next Actions*: These are the heart of GTD. They are the very next physical action that can be taken on something. It's best to phrase these in an active way e.g. "Call Bob about the committee meeting" or "Search for a reputable garage".
* *Contexts*: Contexts are very flexible, and can be places, states of mind or modes of working in which actions can be taken. Next actions can be assigned to and sorted by context so that you know when you are able to make progress with items. e.g. "Library", "Shops" or "Tired".
* *Projects*: any goal which requires more than one next action to take it to completion is a Project. In Tracks, you can view your next actions by Project.
Then attach my_feature.patch to a ticket.
Find out more:
If you are on github, you can use the button to issue a pull request for your changes to be pulled into the main repository.
If you've found a bug or got a feature to suggest, visit the Tracks "Assembla space":http://www.assembla.com/spaces/tracks-tickets/ and create a ticket. You'll need to create an account on Assembla (see "wiki":http://www.assembla.com/wiki/show/alWI9M0eWr3zoYab7jnrAJ for details of how to do this).
Thanks!
* [[Installation Index]]
* [[Known Issues]]
* [[Development Index]]
* [[Tracks Hosting]]
* [[Recommended Web Hosts]]
* [[Integration]]
* [[Contributors]]
* [[Users Manual]] (especially written for non-Programmers)