Libporty provides a higher level API for some commonly used library functions such as sockets, date/time, file system access, background processes, and asynchronous DNS resolving. Libporty is configured using scconfig and the API is guaranteed to work the same way on all supported systems. An application that exclusively uses the libporty API will not require autotools/scconfig for porting. Libporty has been tested on Linux, Windows, Mac OS X, multiple BSD variants, Minix, OpenSolaris, and some ancient Unix systems.
libmawk is a fork of mawk 1.3.3 restructured for embedding. It allows you to embed awk interpreters in any application written in C or in a language that can interface C libraries. This allows the application to have plugins, configuration, run control, and AI written in awk. It extends the original feature set of mawk with modularity (C-style include), save/load of compiled bytecode, function calling by name-in-string (substitute for pointers/references), and accounting and limiting of memory and CPU use. While awk as a language does not offer OOP and complex data structures, it is still reasonably powerful. A major advantage is the short learning curve for new users.
PinaCart is a webshop constructor. Use it as a shopping cart engine to create a chain of online stores or build your own SaaS ecommerce platform and allow your clients to create and manage their online stores. Just download and install PinaCart to start getting clients, then you can customize and expand the software, develop and sell your own set of skins and templates, and come up with new features and functionality.
PeerProject is a versatile peer-to-peer filesharing client and file manager. It's intuitive and aesthetic while supporting many networks and features, including BitTorrent, G2, Gnutella, eDonkey, DC++, IRC, HTTP/FTP, and more. It's a mainstream fork of Shareaza p2p, for Windows and WINE.
jWatchdog delivers a simple watchdog to actively monitor your infrastructure and send you notifications in case something goes wrong. It is configured using a simple XML configuration file. This configuration file can be changed on-the-fly without a need to restart the watchdog. jWatchdog does not offer data collection itself. It assumes that you already collected the data on which you want to run jWatchdog. The de facto standard tool Collectd is recommended for data collection. jWatchdog assumes that you use the RRDTool collectd output plugin to store the collected data in RRD files, or use Graphite as a datasource.