Free priority partners software for linux

The Aurora Project is an attempt to create a new generation of Linux distributions. It will try to break free from old patterns and establish Linux as a serious world player.
Currently, Aurora Project consists of the Aurora Desktop Environment which, unlike most other Linux-based desktop environments, dont attempts to accomplish everything but to remove the focus from system configuration and desktop customizing by creating an easy-to-use out-of-the-box intuitive and beutiful desktop experience.
The UI is (for now) somewhat Microsoft Windows-inspired. I am satisfied with the general layout of the panel and start menu, currently I am busy designing the core functionality of the desktop with the panel as my number one priority. Also there is the session manager, the desktop manager and the shared library.
The Aurora Project currently consists of two major components - the panel and the shared library.
Main features:
- Windows-like user interface with a start menu.
- Freedesktop-compliant application menu (compatible with GNOME and KDE).
- Frequently used applications are easy to access.

Support Incident Tracker (or SiT!) is a Web-based application for tracking technical support calls or emails.
Support Incident Tracker project can manage contacts, sites, technical support contracts, and support incidents in one place. You can send and receive email directly from SiT!, attaching files and recording every communication in the incident log.
SiT! is aware of Service Level Agreements, and incidents are flagged if they stray outside of them.
Support Incident Tracker grew out of an application developed by Salford Software since 2000 called Webtrack and is used in-house by Support Engineers to easily track support incidents.
Enhancements:
- Fixed service levels for reopened incidents, service level target opened is now added making the next action initial response
- Fixed regression where mark for closure was ignored and the incident was closed immediately
- Lists number of incidents of each priority a user has on the user listings page.
- Show more accurately who last updated the call on list incidents pages
- Added multiple global signatures, one is choosen at random when email is sent.
- Fixed bug where disabled user accounts would still display as having relevant skills
- Fixed issue where URLs would not be shortened if they contained a % (percent) or $ (dollar) symbol
- Fixed issues with URLs that contain colons
- Incidents page informs you more accuratly who updated the call
- Specified MySQL Engine type to be MyISAM on all table creations
- Call opening notes are shown in tool tip after new incidents logged rather than reassign
- BB Code. Basic set of BB codes supported in incident updates
- Prevent summary and solution from being uncheck from close incident page since these are mandatory
- Fixed bug with not sending closing email
- send_template_email now store emails in the incident log
- Holiday calendar is now functional
- New holiday planner shows when all users are in/out
- Users can now be placed in groups, view users shows just your own group by default
- Users with edit user permission can set users holiday entitlement
- Able to change external escalation details on bulk
- View users now has links to Waiting queues and holiday calendars
- New interface for adding vendors
- Ability to request email notification when a call is reassigned to a user
- Users without valid email address are now prompted on the main page to edit their profile
- Ability for administrators to disable users by editing a profile and setting status to Disabled Account.
- Force username to be unique when adding new users
- Do incident switchover when changing status via edit profie
- New report, average incident duration. Shows the time taken to close incidents over the months.
- When session expires and user logs in again the user is now redirected the the previously accessed page rather than the main page.
- Improved accuracy of SLA calculation
- Added ability to edit/delete software records
- When an inicdent is closed pending-reassignments are remove as necessary
- When an incident is closed any related incidents are notified of the closure.
- Added icons to priority selection dropdown for browsers that support it
- Improved sorting of some tables, you can now click again on the column header to sort in the opposite direction ascending/descending
- Holding queue locks now timeout after $CONFIG[record_lock_delay]
- Ability to delete multiple held emails in one go
- Ability to add resellers
- Escalation can now be configured via a database table, though there is no GUI for this yet
- External escalation partners can be configured via config file
- Edit incident now lets you select an escalation path (assuming paths are configured in the escalationpaths database table)
- Ability to add/edit/view tasks
- Ability to add notes to tasks
- Note owners can now delete their own notes
- Basic incoming email handler now included with SiT, as inboundemail.php
- New report incidents by software shows which software has the most incidents logged
- Tidied more HTML
- Fixed next action field, this is now stored and displayed again
- Interface to configure external escalation partners
- Made holiday booking easier
- Added ability to check which users have been granted each permission

Frottle (Freenet throttle) is a project to control traffic on wireless networks. Such control eliminates the common hidden-node effect even on large scale wireless networks. Frottle is currently only available for Linux wireless gateways using iptables firewalls, with plans to develop a windows client in the future.
Frottle is made to schedule the traffic of each client, using a master node to co-ordinate actions. This eliminates collisions, and prevents clients with stronger signals from receiving bandwidth bias.
Frottle has been developed and tested on the large community wireless network of WaFreeNet. We have found running frottle has given us a significant improvment in the network usability. Testing results will be documented here as time permits.
Frottle currently operates as a userspace application, receiveing outbound packets via the iptables QUEUE functionality. Access to the network is controlled by the frottle master, sending each client a control packet (token) which contains information about how much data can be sent at this time.
Each client receives its token and sends any required data, one at a time. This eliminates collisions, and with a reasonable signal packetloss is virtually zero. Also, since each client gets a limited slice of the bandwidth, everyone can get fair access regardless of their signal strength. Whilst this mechanism does result in increased latency, overall network performance and utilisation can significantly increase.
Main features:
- Traffic queues built in to frottle assign different, dynamic priorities to different traffic. Most traffic has a default priority. Traffic to/from specified ports (and ICMP packets) are made high priority. Traffic for connections that have done more than 2 MB of data and have a rate of more than 5 KB/s are made low priority. When a client is polled, high priority traffic is sent first, then default, then low until the poll quota is used.
-
- Realtime info on each clients performance is available from the master in a html file and optionally at each client in a similar html file. (The names and locations of these files is set in /etc/frottle.conf.)

issPolicy is a free open-source utility for converting an ISS RealSecure Network Sensor and ISS Proventia Inline Appliance Policy to a static HTML file.
Written in Perl, issPolicy allows for granular parsing of ISS RSNS and ISS Proventia policies (also refer to the "support" section), and supports a wide variety of features (see "features" section) allowing the HTML generation to be customized based on different policy parameters.
Main features:
- issPolicy automatically detects whether the policy is a ISS RealSecure Network Sensor or ISS Proventia Inline Appliance policy and generates a static HTML file based on the policy type and its features.
- issPolicy extracts the following information from the ISS RealSecure Network Sensor Policy:
- Signatures Policy (Signature Name, Signature Description, Signature Status, Signature Priority, Configured Responses, Logging Type)
- IP Filters Policy (Filter Name, Filter Description, Filter Status, Protocol, Source Address, Source Port, Destination Address, Destination Port)
- Event Filters Policy (Filter Name, Filter Description, Filter Status, Filtered Event, Source Address, Source Port, Destination Address, Destination Port)
- issPolicy extracts the following information from the ISS Proventia Inline Appliance Policy:
- Signatures Policy (Signature Name, Signature Description, Signature Status, Signature Priority, Configured Responses, Logging Type, Drop Options, DynamicBlock Options)
- IP Filters Policy (Filter Name, Filter Description, Filter Status, Protocol, Source Address, Source Port, Destination Address, Destination Port)
- Event Filters Policy (Filter Name, Filter Description, Filter Status, Filtered Event, Source Address, Source Port, Destination Address, Destination Port)
- issPolicy contains various useful options allowing for a tailored HTML Policy file to be generated, based on one or more of the following criteria:
- Signature Policy Criteria:
- Whether signature is enabled or disabled
- Based on signature priority (High, Medium, or Low)
- Whether drop is enabled [only on ISS Proventia Inline Appliance Policies]
- Based on drop options (ConnectionWithReset, Connection, or Packet) [only on ISS Proventia Inline Appliance Policies]
- Whether dynamicblock is enabled [only on ISS Proventia Inline Appliance Policies]
- Based on dynamicblock options (IsolateTrojan, BlockWorm, BlockIntruder) [only on ISS Proventia Inline Appliance Policies]
- IP Filter Policy Criteria:
- Whether IP filter is enabled or disabled
- Event Filter Policy Criteria:
- Whether Event Filter is enabled or disabled
- issPolicy uses an "API" structured format, pushing the entire policy to hash arrays, allowing the possibility for other output methods to be developed (CSV, XML, etc...)

Audiality is a scalable and portable audio engine for music and sound effects. It is intended to play equally well in studios and inside games, in order to serve as a flexible tool for content creation, and for use in the final product.

Audiality uses MIDI files in combination with scripting and modular synthesis, to minimize file sizes and maximise flexibility. It is very portable, and supports both integer and floating point processing modes.

Scalability has been a major priority from the start. The current version will run on very low end Pentium systems, but can also produce high quality audio on more powerful hardware.
The main goal for the future is to extend the scalability of Audiality well into the range of serious home and professional studio use. The idea is to provide total control, a wide range of features, tools for fast and effective creation of original sounds, and excellent audio quality.

Titration is a multi-user, multi-project tracking system. Titration is simple and is designed to work with other project management and time-tracking projects.
It is designed to show the present work load, priority, and state of (closed/ongoing/queued/active) projects.
This is not a micro-management package, a project management tool, or time-tracking software. It is an extension of tools that do these things.
Enhancements:
- You can now drag and drop the priorities into the desired location.
- The project name in the drop down lists is now sorted by name desc.
- On the "Overview" tab, the user logging in will now have that users project details loaded.
- The overview menu now supports the exporting of data in XML and HTML formats.

Palm::Progect::Converter::CSV is a Perl module to convert between Progect databases and CSV files.

SYNOPSIS

my $converter = Palm::Progect::Converter->new(
format => CSV,
# ... other args ...
);

$converter->load_records();

# ... do stuff with records

$converter->save_records();

This converts between CSV files and Palm::Progect records and preferences.

The CSV format allows for basic import/export with spreadsheet programs. The CSV file does not look like a tree structure; instead, there is a level column, which indicates the indent level for the current row.

The columns in the format are:

level

The indent level of the record.

description

priority

The priority of the record from 1 to 5, or 0 for no priority.

isAction
isProgress
isNumeric
isInfo

Any record can have one (and only one) of the above types.

If you are going to change the type of a record, remember to set all the other types to false:

isAction isProgress isNumeric isInfo
0 0 0 1
completed

Completed has different values depending upon the type of record. For action items, it is either 1 or 0, for complete or not complete.

For Progress items, it is a number between 1 and 100, indicating a percentage.

For Numeric items it is a number between 1 and 100 indicating the the integer percentage of the numericActual value divided by the numericLimit value.

numericActual

The numerator of a numeric record. If the numeric value of a record is 4/5, then the numericActual value is 4.

numericLimit

The denominator of a numeric record. If the numeric value of a record is 4/5, then the numericLimit value is 5.

DateDue

This is a date in the format specified on the command line with the --csv-date-format option
category

opened
description
note