Free july holidays software for linux

Missile of Holiday Cheer is a winter holiday vertically oriented flying finesse game.

Missile of Holiday Cheer is a game that revolves around piloting missiles bearing presents from elves workshops up to Santas low-orbiting mothership.

There are five elf groups and a number of powerups, and can be played alone or splitscreen with others.

LibHdate is a small C,C++ library for Hebrew calendar and dates, holidays, and reading sequence (parasha).

LibHdate is using the sorce code from Amos Shapirs hdate package fixed and patched by Nadav HarEl.

The Torah reading sequence is from tables by Zvi HarEl.

Installation:

From source:

Untar:

tar -xvzf libhdate-XXX.tar.gz

Configure:

cd libhdate-XXX

configure --prefix=/usr [--enable-examples --enable-python --enable-perl --enable-pascal]
--enable-examples - build and install examples
--enable-python - build and install the python bindings
--enable-perl - build and install the perl bindings
--enable-pascal - build and install the pascal bindings

You will need swig and perl/python devel files.

Build:

make

Install:

make install (as root)

The Daily Journal project is a PIM program that is written using the Fast Light Tool Kit.
It manages daily notes, appointments, holidays, contact and to-do lists, and issues alerts before scheduled appointments.
Enhancements:
- Multiple spurious appointment alerts! Traced to wrong starting index in for loop.
- Appt indices should start from 1, instead of zero. Fixed.

Solunas Hotel Management helps the user manage small to medium-sized hotels, holiday flats, guest houses, or car rentals.

The Solunas Booking Engine Software is aimed at Hotels and Holiday Homes of between 1 to 150 units who are seeking to market their accomodation over the internet.

Because the trend in online bookings has remained constant/continues to grow, experience shows this system to be well liked by customers with growth in orders extending into the double digits. It is also noteworthy that private landlords providing from 1 to 50 units have a lot of catching up to do when it comes to the latest technology.

The Solunas.org central portal tasks itself, through a worldwide volunteer effort, to create an alternative Booking-Platform to rival commercial product offerings.

The end user has two methods to reserve his accomodation. Firstly, a visual reservations calendar displaying room availability, offers the customer direct booking online by mouse-click.

The second method, offering a manual selecction of the booking period and number of persons, involves a list of available units or groups can, likewise, be booked directly online. Details of the total price and last minute bargains are generated straight from the system.

The booking path, known internally as Bookflow, can be modified for very individual requirements.

Hackystat is a framework for the automated collection and analysis of software engineering product and process data.
Hackystat uses sensors to unobtrusively collect data from development environment tools; there is no chronic overhead on developers to collect product and process data. Hackystat does not tie you to a particular tool, environment, process, or application.
Hackystat project is intended to provide in-process project management support.
Hackystat is in its sixth major architectural release family. The first architectural release family, called the "Spike Solution", was used to explore the feasibility of the approach and to evaluate various component technologies (including JATO, XSL, Ant, JUnit/HttpUnit, Tomcat, Cocoon, and SOAP). Work on this Spike Solution architecture lasted eight months, from May to December, 2001.
In December 2001, we began a major re-implementation of the system in order to provide architectural support for design discoveries made with the Spike Solution. This second architectural release family is called the "Framework Architecture", because it implements package and class-level patterns that facilitate extension of the system via inheritance and composition of existing classes. Unfortunately, the Framework architecture required modification of the hackystat source code to implement new sensors and analysis, and only a single configuration of analyses and sensors can be supported in this architecture.
In November, 2002, we began work on the "SDK" (or "kernelized") architecture release family. This third architectural family decomposes the system into two layers. The first layer is a kernel system which implements the core facilities for data definition, storage, transmission and user interface.
Developers build an actual Hackystat installation by combining the framework with a second layer: a set of plug-in extension modules that define the specific sensor data types, tool sensors, and analyses required to support their development procedures. In the SDK architecture, developers can implement new sensors and analyses without modifying the underlying kernel code, and multiple Hackystat installations can be built with different configurations of analyses and sensors.
In June, 2003, we performed a package restructuring that facilitates the development of third layer, or "application" layer systems. This is the fourth architectural release family, called the "Three Layer" architecture.
After only a month of application layer development, we realized that the build process we developed for the second release family would be woefully inadequate to support the three layer architecture, in which multiple components would be combined into a configuration for release.
So, in August, 2003, we released the fifth architectural release family, called the "Component Architecture", along with extensive new build support including the hackydev web site with daily integration builds.
In July, 2004, we released the sixth architectural family, which provides services to support a "telemetry" based approach to software project monitoring and control. This includes various caching mechanisms, as well as the hackyTelemetry package that includes a telemetry specification language and associated APIs. In this architecture, telemetry support becomes a "low level" feature of the system.
Enhancements:
- A new sensor for IntelliJ Idea, enhancements to the Visual Studio sensor, improved support for test driven development inference, and many bugfixes.

PyCalendarGen generates customizable calendar pages in PDF format for use in things like photo calendars.

PyCalendarGen supports custom holidays, birthdays, and other special days and has decent internationalization.

Installation:

Just unpack the archive somewhere useful, and run PyCalendarGen.py from the installation directory (so it will find the fonts).

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

oz2remind is a tool to convert OpenZaurus Opie calendar XML files to Remind format.
Its a small but useful Perl script to convert the datebook.xml file used by the calendar app in OpenZaurus Opie to Remind format.
About Remind:
Remind is a sophisticated calendar and alarm program. It includes the following features:
- A sophisticated scripting language and intelligent handling of exceptions and holidays.
- Plain-text, PostScript and HTML output.
- Timed reminders and pop-up alarms.
- A friendly graphical front-end for people who dont want to learn the scripting language.
- Facilities for both the Gregorian and Hebrew calendars.
- Support for 12 different languages.
About OpenZaurus:
The OpenZaurus project was created as an alternative Operating System for the Sharp Zaurus Personal Mobile Tool. The original purpose behind the project was to create a system (kernel + root filesystem) which was a bit closer to what the developer community specifically desired. The method by which this was accomplished was simply to use the Sharp ROM as a base and make alterations, bugfixes, additions and even removals, where necessary, to make the package more open.
Shortly after this, it was revamped completely. OpenZaurus was then a Debian based embedded distribution built from source, from the ground up. Given its debian roots, it is quite similar to other embedded Debian-based distributions, such as Familiar for the Ipaq. This means of doing things also facilitates an easy method for users to build their own custom system images.
Current Versions of OpenZaurus are built from the OpenEmbedded Build system, this was again a complete rebuild of the entire distribution from scratch.