Free project software for linux

Deep Project is a time entry application for consulting firms. It stores start/end time and sick/vacation time. The project has the beginning of project management and sales cycle features.

USAGI(UniverSAl playGround for Ipv6) Project works to deliver the production quality IPv6 and IPsec(for both IPv4 and IPv6) protocol stack for the Linux system, tightly collaborating with WIDE Project, KAME Project and TAHI Project.
USAGI Project is run by volunteers from various organizations. At this moment, the volunteers are from Japan, however, we are glad to work with volunteers in any country in the world.
We want to contribute to the Linux community and to the IPv6 community via the delivery of IPv6 protocol stack.
Enhancements:
- Unused code was removed.
- Minor bugfixes were made.
- Some of the additional utilities were reorganized.

Project ERP provides an ERP suite written in PHP inside of eGroupware.

Project ERP is a collection of modules for eGroupware, covering acounting, manufacturing, inventory, and sales orders.

It uses the infrastructure of eGroupware and allows customization easily with the eTemplates-Module.

The Arusha Project (ARK) seeks to provide a framework and/or tools for collaborative system administration of multi-platform Unix sites with many dozens of machines.

The core ARK developers are interested in using the Arusha Project as a comprehensive solution for system administration.

It is therefore easy to miss the point that the core ARK engine---which simply provides a ``configuration language to say sysadminish things---can be used in many less-than-comprehensive ways.

Here is a ``laundry list... There are undoubtedly hundreds of other weird-and-wonderful possibilities we havent thought of.

Also note that some of these uses are orthogonal to each other. You could pick one (or none) of the ways to tackle software packages and pick one (or none) of the ways to manage the config files in /etc and pick one (or none) of the ways to manage user accounts, etc. -- this gives you many ARK options, without even breaking a sweat.

1. As a multi-platform package manager for user applications, particularly standard freeware packages.

(We arent pleased to have written Yet Another package manager, but the others [RPM, BSD ports, etc.] just arent up to much when you have several diverse Unix platforms for which you want the ``same packages.)

(Other system administration would be done by other means.)

2. To provide an early-adopter `playpen: [a variant on #1] at a site of any size, you will have a small number of people keen to try out beta- and even alpha-quality software. (It is wise to let them do so---they accumulate much ``intelligence which is helpful when deciding about new software to roll out to the general user population.)

You could use ARK to set up a `playpen where early-adopters could do their trials in a controlled and non-problematic way. (The Sidai version wrapper stuff is one way to get a handle on the multiple-versions-live-at-the-same-time problem.)

3. As a `unifier for diverse package managers: Imagine you have a site of Solaris, Linux, and NetBSD boxes, .and you want to use the native package managers for each. But you want the ``same packages on all hosts, and want a site-at-a-time way to manage them; i.e. ark package install ALL should install all packages on all hosts, each in the appropriate way.

4. As a (binary) package producer: One can imagine having a small number of ARK hosts whose job is to produce (say) binary RPM packages of everything of interest to your site. Your (many?) client/production hosts would then simply use the RPMs.

5. As a front-end for Cfengine or PIKT, or similar: Express what there is to know about the hosts, etc., at your site in the ARK object way (including constraints between them), then push a button to generate a configuration for one of the established sysadmin tools, which will do the heavy lifting for you.

6. As a fancy `rdist: A Unix site has bunches of config files that need to be ``the same across many machines, e.g. /etc/hosts or /etc/resolv.conf. The distributed ARK code (notably from team Sidai) is a good way to do this stuff, and you might use ARK just for that.

7. As an `idea bank: Dont run ARK code at all; simply study others sysadmin solutions as a source of ideas. This is a pathetic choice in our view :-), but entirely legitimate!

8. Toss it for system administration and build chip designs with it, instead! (While this is a mostly-facetious suggestion, it reflects the fact that the earliest ARK ideas emerged alongside some chip-building ideas at Glasgow University in 1999.)

Project Foundry provides a integrated project management tool.
Project Foundry is a tool to create and maintain information used during the development of software projects.
It is oriented towards the high level management of the projects, and aims to better integrate the usual tasks of management.
In particular, one can keep track of:
- Meetings minutes
- Stakeholders
- Requirements
- Models of GUI
- Work breakdown structure (Gantt chart scheduler)
- A glossary so that important words are defined and used correctly all around the project

After decades of war one company, who had gained powerful supplying both sides with weaponary, steps forwards and crushes both warring factions in one swift movement.
Using far superior weaponary and AI craft, the company was completely unstoppable and now no one can stand in their way.
Thousands began to perish under the iron fist of the company. The people cried out for a saviour, for someone to light this dark hour... and someone did.
Main features:
- 26 missions over 4 star systems
- Primary and Secondary Weapons (including a laser cannon and a charge weapon)
- A weapon powerup system
- Wingmates
- Missions with Primary and Secondary Objectives
- A Variety of Missions (Protect, Destroy, etc)
- 13 different music tracks
- Boss battles

Apache XML Projects goals are:
- to provide commercial-quality standards-based XML solutions that are developed in an open and cooperative fashion,
- to provide feedback to standards bodies (such as IETF and W3C) from an implementation perspective, and
- to be a focus for XML-related activities within Apache projects
The Apache XML Project used to be the home for many XML-related subprojects, many of which have moved to top-level project status recently or are currently in migration. The Apache XML Project slowly transforms into an place where you can find pointers to XML-related projects here in the Apache Software Foundation. The remaining subprojects directly under the supervision of the XML PMC are:
- AxKit - XML-based web publishing, in mod_perl
- Crimson - A Java XML parser derived from the Sun Project X Parser.
- Xang - Rapid development of dynamic server pages, in JavaScript
- Xindice - A native XML database.
- XML Commons - focussed on common code and guidelines for XML projects
- XML Security - Java and C++ implementations of the XML signature and encryption standards

project-p project is a simulation in which particles interact with each other based on a simple rule.

In p, a bunch of particles interact with each other according to this simple rule: every particle must move towards, away or watch another particle. When the program starts, each particle chooses a random color, position and the particle it will move towards, away or watch.

As the program runs, some particles join together to form a train and continue their journey together thereafter. There are many such trains too, but how do they form? Imagine 2 particles A and B. If A moves away from B as B moves towards A we get a self propelling train. The rules dont predict when and where these trains will form but they emerge everytime the program runs.

A particle in p moves towards or away from another particle by a definite amount D along the straight line joining the particles. Consequently, a particle cant move towards or away from itself. A particle that watches another particle doesnt move too. It either waits for the watched particle to come close to it or move far away before it decides to move towards, away or watch another particle. But if the watched particle recedes while it hopes it would come closer, it would watch forever.

Now, what happens if there is only 1 particle in the system? Well, it cant move towards or away from itself thats for sure. It could watch itself but what can it do when it stopped watching? Move towards, away or watch itself some more! Therefore, if there is only 1 particle in the system, we can conclude that it will stay put in its initial position.

Now consider a 2 (or more) particle system. Let the particles be A and B. Let A stand still (as if it were a 1-particle system) and let B move towards A. If B is seperated by a multiple M of D ie separated distance = M x D, it will collapse into A in M steps. If B is instead separated by a multiple M of D and by some more distance N ie the separated distance = M x D + N, B will orbit A in M steps.

Apogee and perigee will be N units or N - D units. The same thing happens if A is also moving towards B as B is moving towards A but sooner - in approximately M / 2 steps. Once again, the rules dont predict these phenomena but they always emerge when the program runs.