Free request for proposal software for linux

Request Tracker (RT) is an enterprise-grade ticketing system which enables a group of people to intelligently and efficiently manage tasks, issues, and requests submitted by a community of users.
The RT platform has been under development since 1996, and is used by systems administrators, customer support staffs, IT managers, developers and marketing departments at thousands of sites around the world.
Written in object-oriented Perl, RT is a high-level, portable, platform independent system that eases collaboration within organizations and makes it easy for them to take care of their customers.
RT manages key tasks such as the identification, prioritization, assignment, resolution and notification required by enterprise-critical applications including project management, help desk, NOC ticketing, CRM and software development.
RT is used by Fortune 100 companies, government agencies, educational institutions, and development organizations worldwide.
Main features:
- RT is your organizations focal point for tracking tasks, issues, knowledge, and collaboration.
- Its easy to submit, assign, prioritize, search, escalate, and report on issues.
- RT keeps track of each tickets full history and metadata to help your organization better retain knowledge and analyze trends.
- RT can track multiple projects for multiple teams within a single installation.
- RT tracks critical system metadata, including time spent per action, due dates, and estimated time to completion.
- Its easy to record private comments that are not available to end-users.
- RTs web interface comes complete with an intuitive "iterative" search interface that allows end users to construct complex queries by pointing and clicking within their web browsers.
- Users can save and edit queries later, using their browsers "bookmarks" feature.
- Users dont need to do anything special -- they can just send email to RT. RT will take care of thanking them for their message, automatically routing it to the appropriate staff, and making sure all future correspondence gets to the right place.
- RT provides a simple, self-service interface that allows end users to view their own active and resolved tickets online.
- RTs web interface is designed to be easy to use from any browser. Just working in Internet Explorer and Netscape isnt enough. Your staff need to be able to get work done anytime, anywhere.
- Whether you use Windows, MacOS or Unix, your staff already have everything they need to access RT.
- RT works great from a handheld or screen-reader (for the blind.) Best Practical is working with users to ensure that a future release is fully compliant with Section 508 accessibility requirements.
- A powerful new command-line interface that allows power users to quickly and easily work with RT, even if theyre out of the office is currently available for testing by the public.
- Youve got customers around the world. RT lets you interact with them in their own language. Internally, RT converts all data to UnicodeTM, so you can respond to users in their native tongue, but work in yours.
- Youve got staff around the globe. RTs web interface has been fully internationalized. Right now, RT speaks English, German, French, Dutch, Portuguese, Russian, Czech, Japanese, Traditional Chinese, and Simplified Chinese. Adding new languages is a breeze, if you need something RT doesnt support yet. On login, RT automatically detects which language each user prefers, so staff members can collaborate even if they speak different languages.
- Unlike costly proprietary issue tracking systems, an administrator can have a basic RT system up and running in an afternoon.
- RT is built to be useful right out of the box. You dont need expensive consultants
- Theres no client software to manage or keep up to date. Your existing web browser and email clients are all you need.
- RT is written in object-oriented perl. Not only do you get the complete source code to the product with every download, but your staff can begin customizing RT to meet your needs within hours.
- RTs web interface and mail gateway are built on top of the same API we publish for you to write your own tools on top of. The interface is documented and there are numerous third party tools to use as examples and templates.
- Every organization needs to track specialized data. RT lets you define list-based and freeform custom fields to help track your tickets. Once you create custom fields, its easy to search on them, just like RTs predefined fields.
- All of RTs mailing rules are based around a powerful custom business logic system called "Scrips." Scrips make it easy for a local administrator to make RT do ANYTHING whenever a ticket is created or updated, without making it hard to upgrade.
- RTs entire web interface is built on a flexible templating system that lets you build your own web-based tools or alter RTs look and feel to better fit your organization.
- If you dont want to radically change RTs interface, you can add your own components to RTs pages. A web callback system lets you drop miniature templates into RTs web pages.
- If you need even more power, "Code overlays" let you customize RTs internal behaviour without touching RTs core libraries.
Enhancements:
- This release includes numerous small cleanups and improvements.
- It fixes the dreaded "infinite relogin" bug.

CGI::Request is a parse client request via a CGI interface.

SYNOPSIS

use CGI::Request;

# Simple interface: (combines SendHeaders, new and import_names)

$req = GetRequest($pkg);

print FmtRequest(); # same as: print $req->as_string


# Full Interface:

$req = new CGI::Request; # fetch and parse request

$field_value = $req->param(FieldName);
@selected = $req->param(SelectMultiField);
@keywords = $req->keywords; # from ISINDEX

print $req->as_string; # format Form and CGI variables

# import form fields into a package as perl variables!
$req->import_names(R);
print "$R::FieldName";
print "@R::SelectMultiField";

@value = $req->param_or($fieldname, $default_return_value);

# Access to CGI interface (see CGI::Base)

$cgi_obj = $req->cgi;
$cgi_var = $req->cgi->var("REMOTE_ADDR");


# Other Functions:

CGI::Request::Interface($cgi); # specify alternative CGI

CGI::Request::Debug($level); # log to STDERR (see CGI::Base)


# Cgi-lib compatibility functions
# use CGI::Request qw(:DEFAULT :cgi-lib); to import them

&ReadParse(*input);
&MethGet;
&PrintHeader;
&PrintVariables(%input);

This module implements the CGI::Request object. This object represents a single query / request / submission from a WWW user. The CGI::Request class understands the concept of HTML forms and fields, specifically how to parse a CGI QUERY_STRING.

Jifty::Request is a canonical internal representation of an incoming Jifty request.

This document discusses the ins and outs of getting data from the web browser (or any other source) and figuring out what it means. Most of the time, you wont need to worry about the details, but they are provided below if youre curious.

This class parses the submission and makes it available as a protocol-independent Jifty::Request object.

Each request contains several types of information:

actions

A request may contain one or more actions; these are represented as Jifty::Request::Action objects. Each action request has a moniker, a set of submitted arguments, and an implementation class. By default, all actions that are submitted are run; it is possible to only mark a subset of the submitted actions as "active", and only the active actions will be run. These will eventually become full-fledge Jifty::Action objects.

state variables

State variables are used to pass around bits of information which are needed more than once but not often enough to be stored in the session. Additionally, they are per-browser window, unlike session information.

continuations

Continuations can be called or created during the course of a request, though each request has at most one "current" continuation. See Jifty::Continuation.

(optional) fragments

Fragments are standalone bits of reusable code. They are most commonly used in the context of AJAX, where fragments are the building blocks that can be updated independently. A request is either for a full page, or for multiple independent fragments. See Jifty::Web::PageRegion.

Change Control Request Manager is an online system for managing change requests for businesses. Change Control Request Manager project can be customized to fit the needs of a particular business.
Main features:
- Abillity to customize data entry fields. Field type include test, dropdown list, boolean, date, and integer.
- Search for existing CCR records.
- Custom logo. You can place your companys logo at the top.
- Custom Disclaimer message.
- User administration.
- Install script.
Enhancements:
- A reporting system was added.
- Similar to the browse order screen, you can customize the report and display a date range to print.

Yet Another Object Request Broker is an implementation of the CORBA ORB.
YaOrb advanced installation
YaOrb uses the GNU tools (Autoconf, Automake, ...).
See the GNU documentation for complete instructions, in file $/INSTALL.GNU.
Optional features
The configure script also supports package specific options :
-enable-yoconf=DEV : build in "Development" configuration
-enable-yoconf=TCOV : build in "Coverage" configuration
-enable-yoconf=GPROF : build in "Profiling" configuration
These options are private for the maintainer of this package, and will only work in a specific environment (since assumptions are made about which compiler is used, ...). You may try them, but dont need them to make a build.
The "DEV" (Development) configuration is used to perform a build with all the possible warning options turned on, and warnings are considered errors (using gcc with -Wall -Werror). This configuration is used to enforce that the code is as clean as possible.
The "TCOV" (Coverage) configuration is used to collect code coverage statistics, and also depend on gcc. After running tests, use make profiling to collect code coverage, and read the resulting files :
- $/.SCORE
- $/.MISSING
The "GPROF" (Profiling) configuration is used to collect performance data, and relies on specific gcc options and gprof. After running tests, use make profiling to collect statistics generated.
Enhancements:
- First public release of Yet Another Object Request Broker. Pre alpha, release 0.2

ScraperPOD is a framework for scraping results from search engines.

SYNOPSIS

use WWW::Scraper;

# Name your Scraper module / search engine as the first parameter,
use WWW::Scraper(eBay);
# or in the new() method
$scraper = new WWW::Scraper(eBay);

Classic WWW::Search mode

# Use a Scraper engine just as you would a WWW::Search engine.
$scraper = new WWW::Scraper(carsforsale, Honda, { lbxModel => Accord, lbxVehicleYearFrom => 1998 });
while ( $response = $scraper->next_result() ) {
# harvest results via hash-table reference.
print $scraper->{sellerPhoneNumber};
}

Canonical Request/Response mode (not yet implemented)

$scraper = new WWW::Scraper(carsforsale, Request => Autos, Response => Autos);
# or, since carsforsale.pm defaults to the Request and Response classes of Autos
$scraper = new WWW::Scraper(carsforsale);
#
# Set field values via field-named canonical access methods.
$scraper->scraperRequest->make(Honda);
$scraper->scraperRequest->model(Accord);
$scraper->scraperRequest->minYear(1998);
#
# Note: this is *not* next_result().
while ( $response = $scraper->next_response() ) {
#
# harvest results via field-named access methods.
print $response->sellerPhoneNumber();
}

Variant Requests to a single search engine

$scraper = new WWW::Scraper(carsforsale);
$scraper->scraperRequest->make(Honda);
$scraper->scraperRequest->minYear(1998);
#
for ( $model = (Accord Civic) ) {
$scraper->scraperRequest->model($model);
$response = $scraper->next_response() ) {
# all response fields are returned as a reference to the value.
print ${$response->sellerPhoneNumber()};
}

Single Request to variant search engines

# Set the request parameters in a Request object (sub-class Autos).
$request = new WWW::Scraper::Request(Autos);
$request->make(Honda);
$request->model(Accord);
$request->minYear(1998);
#
for ( $searchEngine = (carsforsale 1001cars) ) {
$scraper = new WWW::Scraper($searchEngine, Request => $request);
for ( $response = $scraper->next_response() ) {
# all response fields are returned as a reference to the value.
print ${$response->sellerPhoneNumber()};

WebScarab for Eclipse is an extensible framework for analyzing applications that communicate using the HTTP protocol.
It includes an HTTP monitor and an HTTP proxy for recording all messages between your machine and remote servers.
It is a port to Eclipse of the WebScarab application from OWASP.
It consists of the following components:
Proxy: HTTP proxy that monitors HTTP communication.
Triggers: Eclipse extensions and user scripts that are executed on specific message patterns.
HTTP Summary View: Eclipse view that shows all recorded messages with the ability to save and edit the message content.
Main features:
- Tight integration with the Eclipse platform
- Easily create custom trigger scripts or trigger extensions
- Save and edit HTTP message content within the Eclipse environment
- View request and response message details
- Edit messages on the fly with manual triggers