Free request software for linux

KXML Editor is application for KDE, that display and edit contents of XML file.
Main features:
- Drag and drop editing, clipboard support
- Use DOM level 2 Qt library parser
- KParts technology support
- DCOP technology support
- Editing KOffice compressed files
Enhancements:
- Updated /admin with latest kde-common/admin contents
- Switched the default item insert point to "at bottom" for the "New Element", "New Proc.Instr." and "New CData" dialogs.
- Implemented feature request #1044396 "Reload function".
- Fixed a little usability bug. Tabbing between the widgets work (better) now (all unvisible widgets reject focus on tab).
- Fixed the bug mentioned in feature request #1049159 "Keyboard shortcut for closing the "Edit XML as raw text" win".
- Implemented feature request #1048738 "F2 button for editing text content".
- Added fix_paths script to fix hardcoded paths in files generated by dcopidl2cpp

Tagit allows custom JSP tags to be tested with a container. It is very different than TagUnit; the two libraries complement each other nicely. Tagit is an implementation of the Mock Objects testing pattern.

All custom JSP tags generate HTML, and the HTML can be validated. Often custom tags are reading data from the HTTP request or the HTTP session, Tagit allows data to be stored in the session or the request.

TagIt cannot be used for any custom tags that generate data in the request etc; Tagit is designed to only tags that simplify the creation of HTML.

TagIt is licensed under the LPGL, except for the following packages that are released into public domain:

net.scholnick.net.test.tag
net.scholnick.unittests

Any classes in these packages can be used for any purpose at anytime. They demonstrate how to use TagIt.

PHP Gift Registry is a a Web-enabled database that allows members to keep track of the gifts theyd like to receive and see what items other members would like to receive. Private reservations ensure gifts are not bought twice.
Main features:
- A single unifying view of items on your own list and people whose lists you can view.
- A now-optional request/permit system by which you can control who can see your list.
- A "checkin/checkout" system which allows you to reserve items on someones list.
- An in-system messaging system by which users can be informed of item deletions or custom announcements.
- New users can request accounts. Optionally, administrators will be informed about the request, and they can then approve or reject the request. Either way, the user will be informed by e-mail.
- A site-customizable ranking system for items.
- An events system for users to add significant (read: gift-bearing) events which will show up on others displays when the event nears.

mod_auth_pgsql Apache module allows user authentication (and can log authethication requests) against information stored in a PostgreSQL database. PostgreSQL is a public domain SQL database.

Authentication

One database, and one (or two) tables. One table holds the username and the encryped (or plain) password.
The other table holds the username and the names of the group to which the user belongs.
It is possible to have username, groupname and password in the same table.

Access Logging

Every authentication access is logged in the same database of the authentication table, but in different table.
User name and date of the request are logged.
As option, it can log password, ip address, request line.

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.

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

mod_sesehe SEcure SErver HEader is an Apache module that disguise or remove "Server: " HTTP header.

The ServerTokens directive currently can at best be set to Prod, which will cause apache to return "Apache" as Server header. Some problem still occurs:
First, the level of security by obscurity of this directive is not acceptable by some people that just want to change it to some other value, without re-compiling Apache, or people that even want to simply drop the "Server: " header. Secondly, if apache is configured as a reverse proxy, and a malformed request is received, then it will display its own server token instead of the backend one, so we need to handle error response header.

I developed this tiny module by hijacking normal behavior of (reverse) proxy feature of Apache : i.e. even if a request is not a proxy request, I tag it as if it was, to make Apache core let me do what I want with this header.