Free keeping track software for linux

Katapult-Fast Track project is a Katapult fork based on the KDE SVN repository. It fixes several outstanding issues of upstream Katapult. Unfortunately, Katapult development stagnated and no progress has been made upstream for half a year. Hopefully someone from the team will actually reply to my e-mails so Katapult development can continue. If not this fork will need a name (Im obviously leaning towards Fast Track) and will be a separate project altogether.
Improvements over last stable Katapult release:
- Support for multiple results (Press up or down keys to see more results)
- Support for multiple actions (Press left or right keys to see more actions)
- Adaptive search
- Threaded architecture
- Non-blocking DCOP calls
Kudos to the team for providing the framework for multiple results, multiple actions, and multithreaded catalogs.
Caveats:
- Currently, only the program and bookmark catalogs actually return more than one result at a time.
- Only the program catalog supports adaptive search.
- Only the amarok catalog has multiple actions.
What this means for YOU:
- The amarok catalog should not slow down Katapult if you have a big collection of songs.
- The amarok catalog can now queue songs and add songs to the current playlist
- The program catalog will adapt to your launching preferences (i.e. no more "Konquest" results when all you want is "Konqueror")
- You no longer have to type more letters (press the down key to choose something else)
What is still lacking:
- Testing. Especially for the amarok catalog. I only have a couple of GB worth of songs so I cant speak for everyone but this should be an improvement over the last release.
- Spell catalog. Ive tried everything to get KSpell to play nice with separate threads (i.e. call KSpell in the main thread, block the worker thread till KSpell is done, then pass the result to the worker thread) but it just wont work.
- Composite support. I havent applied my own real transparency patch. Dont try to apply it here because it was made to specifically work against 0.3.1.4.
Installation:
Extract the files. cd to the created directory. Then ./configure and make and then install as root.
For any problems, either leave something here or post something at the Katapult forums. Ill get back to you as soon as I can. Please include how to reproduce your problems.

b-tektracker is an advanced realtime MIDI step-sequencer with a tracker interface. b-tektracker is a fork of tektracker by Billy Biggs.

ttrk is the product of frustration with bad step editors found on pretty much all MIDI sequencers available today. Im a big fan of trackers, and I wanted to be able to compose MIDI music using a tracker paradigm.

There are five main goals of ttrk:

1. Tracker-style step editor, think ScreamTracker3.
2. Pattern based sequencer.
3. Big, accessable track mute buttons, think Alesis MMT8.
4. Realtime editing, never need to push stop.
5. All functions directly accessable from the keyboard for rapid editing.

ttrk started in the spring of 1999 as a Qt application. I used it to record a bunch of songs (http://mp3.com/bitblit) and some live shows, but it was very much hacked together based on what I needed at the time. Keeping a GUI app up to date is a pain in the ass, and ttrk has been in need of a rewrite ever since.

The urge to create a console version was two-fold:

1. I wanted to use my old computer as a dedicated sequencer, and it doesnt run X.
2. To create a sequencer, you need to run as root. I dont like running big X apps as root.

There are some files to help you use ttrk:

- docs/keys.txt Detailed explanation of all keyboard commands.
- docs/usage.txt Detailed notes on how to use ttrk.

The Bluetail Ticket Tracker (BTT) is a system for creating, storing and keeping track of tickets. A ticket describes an issue of some sort.

It can, for example, be a Trouble Report or a ToDo note. It is available for use (and distribution) under the GNU Public License.

The users of BTT are divided in four different user categories: Staff, Friend, Customer and Anonymous. The access to the data stored in BTT can be tailored for the Friend, Customer and Anonymous groups, while the Staff group has full access rights. This (hopefully) allows BTT to be used both for Open Source Projects as well as in more commercial settings.

In an Open Source Project:

* one or several people (Staff) hosts a site which runs the Ticket handling for a certain application
* a number of people (Staff + Friends) collaborates in the development which also include Ticket handling
* anyone else interested (Customer or Anonymous) may want to check the status of the Tickets (e.g Trouble Reports)

In a commercial setting:

* a company (Staff) runs the Ticket tracker as an aid in their product development.
* the company may be spread geographically or may have development partners (Friends)
* the customers can report problems and track the progression (Customer)

A ticket consists of a number of fields, e.g denoting a release name, component name, responsible person, staus, priority, etc. The actual field values is defined by the Staff when the Bluetail Ticket Tracker is setup. The daily operation of BTT includes creation, editing, searching and viewing of tickets.

The users can also activate the mail alert function which will send a mail to the user when, for example, a new ticket as been assigned to the user.

BTT can also store information about customers which can be useful in a support desk scenario. This makes it possible to connect a ticket with a particular customer. It is also helpful in a support desk scenario where the support engineer quickly need to find information about a customer.

BTT can also store more general information. This Knowledge Base consists of a mail store and a information store.

The mail store makes it possible to retrieve mails (from a POP3 account) and store it locally in a BTT directory. Stored mails can then be searched, viewed and turned into tickets.

The information store is divided in two parts, one external (for users/customers) and one internal (for staff/friends). The external area can for example be used for creating a FAQ (Frequently Asked Question), a HOWTO area. The internal knowledge base is intended for the Staff and/or Friends, and may for example store information such as address lists, how to fill in the expenses form, or contain description of the work process, etc.

Currently BTT supports English, French, German, Spanish and Galician. Adding new languages is easy, one language definition file has to be created with a translation of all text that can be displayed. (If you do this, make sure to send the new language file to the maintainers so that it can be incorporated into the standard release).

Tickets can also be retrieved and stored via a Unix command line interface.

FileTrack is a Web-enabled communication log, keeping track of all your inbound and outbound documents. The project supports multiple logs, auto-archiving of older entries, and generates simple reports based on multiple criteria.

One or more log entries, contacts, or documents can be grouped together into an issue for easier monitoring.

Advanced Stock Tracking System (AST) is a Web-based application for keeping track of stocks.

Advance Stock Tracker features a portfolio with dividend tracking, a worksheet to keep track of prospects, a stock comparison utility, and a search engine for the stock market based heavily on technical analysis.

Plone Click Tracking Tool is a product which aimed for assisting in tracking advertisement campaigns in Plone websites.

Plone Click Tracking Tool (qClickTrackingTool ) is aimed for assisting in tracking advertisement campaigns in Plone websites. It allows to track clicks of visitors. Actual statistics calculation is performed by external AWstats log analysis system.

Each campaign is assigned id and destination URL. Tool is redirecting urls of the form "portal_url/track/campaignId" to actual campaign destination.

External log analysis tool is grouping tracking log entries and provides results as a part of statistical report.

Installation includes AWstats configuration details.