Free to publish software for linux

eZ publish is a popular open source content management system and development framework. eZ publish project is distributed, developed and supported by eZ systems. eZ systems is a commercial company, founded by experienced and open-minded people. The company builds its business by providing services around the eZ publish system. For more information about eZ systems, read the "What is eZ systems?" section.
eZ publish allows the development of highly professional and customized internet solutions and dynamic web applications. It can be used to build anything from a personal homepage to a multinational corporate website with role based multiuser access, online shopping, discussion forums and other advanced functionality. In addition, because of its nature of openness, eZ publish can be easily plugged into, communicate and coexist with existing IT-solutions.
eZ publish comes with a wide range of advanced built-in features, which make it possible to develop professional, complex, secure and reliable solutions within a short amount of time. In addition to the built-in features, the system allows for extensions and custom modifications in almost any direction. Unlike other content management systems, eZ publish delivers a flexible, generic solution with very few limitations. In other words, this is a scalable and dynamic system that companies and organizations can grow with.
eZ publish is platform independent. It can be used on Windows and several UNIX variants such as OS X, Linux, FreeBSD, Solaris, IRIX, etc. In addition, eZ publish is also database independent; if a specific database isnt supported, it is possible to write a driver without modifying any kernel code.
eZ publish is open software, supporting open standards. The software is constructed following strict development processes in order to ensure high technical quality and usability.
eZ publish is dual licensed. There is a GPL (General Public License) and a professional license. Using the GPL license, people can build their own open source applications and thereby contribute to the development of free and open software. The professional license allows companies to make and sell commercial software that is developed using and/or built upon the eZ publish system.
Enhancements:
- Several bugfixes and enhancements.
- The command line package tool ezpm.php has been updated: list, import, and install commands have been changed to match the admin interface functionality.
- The ezinstallscript and ezextension items are supported by the add command. ezpm is allowed to set the vendor.
- Enhancement #010347 (progress output for correctxmltext.php and updatetypedrelation.php) has been implemented.

PhpBibliography allows you to publish your bibliography online (and to edit it via web). PhpBibliography is implemented in Php and uses MySql.
These instructions assume you already have a working web server/php/MySql system.
1. Create a database called bibliography (this is the default but you can choose the name you want, provided you update config.php accordingly, see below; for instance some providers already set up some databases for you, with specific names: you should choose one of these and then update config.php accordingly, see below)
2. (Optional) assign user and password to the created database
3. upload the file bibliography.sql you find in the zip file (this will create the table structures); in order to do this you can either use the following mysql command, where should be replaced with the user you assigned to the database (default: root) and is the name of the database you created (default: bibliography):
mysql -u -p < bibliography.sql
Alternatively you can use your favorite mysql management system, e.g., phpMyAdmin.
Note: phpbibliography relies on InnoDB tables for the database, but it should work even with standard MySql table types (I havent tested this) but you lose referential integrity.
4. Edit the config.php file in the html directory according to your configuration:
$dbhost = "localhost";
This is the address of the MySql server (by default it is the same of your web server - thus, localhost - but it might not always be the case)
$dbuname = "root";
The user owner of the database you created (default: root)
$dbpass = "pippo";
The password of the owner of the database you created (default: pippo, but you should change it as soon as possible!)
$dbname = "bibliography";
The name of the database you created (see above)
$mysite = "http://yoursite/yourphpbibliographypath";
This is the public URL of your phpbibliography site; it depends on where you upload the phpbibliography files (see below)
$filedir = "files";
This directory will store the papers you upload via phpbibliography. You can keep the default value (see below for setting up this directory)
$maintitle = "Bibliography Site";
This will be the title of the html pages generated by phpbibliography
copy all the contents (including the subdirectories) of the html directory to the desired directory in your web server (make sure that the subdirectory files is writable from the web server user - you can make it writable and accessible from anyone. This directory will store the papers you upload via phpbibliography)
If everything was setup correctly you should be able to access to your bibliography site with a browser.
Enhancements:
- Papers can be classified according to several criteria (decided by the users).
- The order of authors in a bib item is respected.
- A paper can be modified using a bibtex.
- An entire bib file can be uploaded to insert or modify the papers.
- An authentication problem with PHP 5 has been fixed.
- Formatting of papers can be customized by passing parameters in the URL.

Top Music allows you to publish music (albums, songs, sound tracks, rankings, artists, etc.) to create an online music portal.

It features: A-Z list of bands; band information (name, photo, genre, biography, etc.); discography; album information (title, year, covers, band, etc.); albums songs lists; song information (title, album, number, lyrics, etc.); the ability to listen to tracks; searching; ranking lists (most visited, most voted, etc.); a voting system; an uploads system; themes; an easy configuration screen; many blocks; multi-language support; easy installation; and a support forum, mailing lists, and Sourceforge.net support (CVS, files, etc.)

Echelon Linux is a distro designed to monitor services on your network. Echelon Linux is based on the DamnSmallLinux project.
I started building echelonlinux last year but I stopped working on it a few month later. Today I have decided to publish a new release of echelonlinux. It is a little bit different than first one; only 3 components are available :
- Nagios Services and local ressources monitoring
- Ntop Network traffic analyser
- Nessus Remote Security Scanner
Main features:
- Apache based system
- Network monitoring with Nagios.
- Vulnerabilities scan with Nessus.

OpenDDS is an open-source C++ implementation of the Object Management Groups Data Distribution Service for Real-time Systems specification (version 1.0). This project implements most of the minimum profile of the Data-Centric Publish-Subscribe (DCPS) layer of the DDS specification.
DDS provides demanding applications with a high-level, object-oriented publish-subscribe model while enabling efficient, direct data transfer between publishers and subscribers. More information about the OMGs DDS specification can be found at the OMG Data Distribution portal.
OpenDDS is built on the ACE (ADAPTIVE Communication Environment) abstraction layer to provide platform portability. OpenDDS also leverages capabilities of TAO (The ACE ORB), such as its IDL compiler and as the basis of the OpenDDS DCPS Information Repository (DCPSInfoRepo). In addition, OpenDDS leverages MPC to ease the maintenance burden of supporting multiple build environments and platforms. For a current list of supported platforms and build environments, see the OpenDDS FAQ.
Enhancements:
- Support for built-in CORBA:: sequences was added.
- DDS entities have changed to local IDL types and now support zero-copy reads.
- User-defined DDS types are now correctly scoped.

LPMtool project is a package management tool. At this time, LPMtool has been developed and tested on Linux. LPMtool could probably be ported to other platforms with a minimum of effort, but at this time no porting effort has been made.
LPMtool is capable of handling all package management chores for an entire Linux system by itself; but it can also play second fiddle alongside the existing system package manager.
LPMtool is not just a basic package manager, that merely keeps track of installed software. LPMtool includes tools for setting up web-based package repositories and publishing packages.
LPMtool publishes an efficient package repository on a web server. The package repository may contain different versions of the same software package built for different Linux distributions, and LPMtool will download the appropriate version, for the Linux distribution LPMtool is running on.
LPMtool aims to simply the task of distributing and installing software packages. Consider a complicated application that uses additional software components from third party sources. LPMtool eliminates the "dependency hell" of pouring through the softwares documentation looking for third party components the software depends on, and figuring out if you already have them installed, and if not where they must be downloaded from.
LPMtool downloads the required software components, automatically, after displaying the third party softwares URL and asking for permission to download the required software from it (of course, the third party components must also be built with LPMtool, in order for this to work).
LPMtool keeps a list of known repositories where software was installed from. A single command checks if newer versions of existing software packages are available, downloads them, and installs them.
Main features:
- A more flexible dependency model. New versions of a package can use a different architecture (such as updating an i686 package to an x86_64 package, or the other way around). Also, it is not necessary to "bump" a packages release after upgrading to a new version of the base Linux distribution. LPMtool knows to update packages built for a different (previous) Linux distribution even if the current distribution carries an older version of the package.
- No configuration files that require manual editing. All configuration settings are adjusted by command options.
- LPMtool includes a lot of documentation. This documentation includes everything needed to use LPMtool, and to set up web-pased package repositories to publish LPMtool packages on the web. This documentation also briefly discusses many internal LPMtool objects and algorithms.
- LPMtool includes a graphical front-end (requires Gnome and Python).

pyctures is a small web gallery written in Python that uses the web.py framework. It does not use any database and stores all the necessary data in the filesystem.
pyctures is published under the BOLA (Public Domain), so you can run the software anywhere, and do whatever you want with it.
Installation:
The installation procedure depends on the HTTP server youre using. What follows is a list of procedures for some common HTTP servers. If you use pyctures with something else, please let me know so I can add it here.
After youve completed the install, read the "Administration" file to learn how to manage your gallery.
Common procedure
1. Copy the "website" directory to a suitable place where you want to install
pyctures. It does not have to be inside your website, but has to be
readable by your webservers user.
2. Create a "config.py" file based on the "config.py.sample" file, and edit it
according to your configuration. A really important setting is the album
path, where all albums will be stored. It can be anywhere you want. Create
an admin user so you can create albums using the web interface.
3. Make sure the album path is writeable by the user who will run the pyctures
application. It usually is your web server user.
4. Install PIL from http://www.pythonware.com/products/pil/. The package name
for most distributions is "python-imaging" or just "imaging".
5. Install cheetah from http://www.cheetahtemplate.org/. The package name for
most distributions is "python-cheetah" or just "cheetah". You need at least
version 2.0-rc5.
No server (stand-alone)
pyctures can be run without any HTTP server by just executing
"./pyctures [PORT]" directly on the website directory. Its useful for
testing and small sites. I recommend that you test everything works this way
before integrating it into a webserver.
lighttpd
First of all, install "flup", from http://www.saddi.com/software/flup/.
Gentoo: Its not in portage, it sucks. Check
http://bugs.gentoo.org/show_bug.cgi?id=100784
Debian: apt-get install python-flup
Now, lets suppose youve installed pyctures in the "/var/www/pyctures"
directory, and want to publish it under the "/pics/" directory.
You need to add the following to /etc/lighttpd/mod_fastcgi.conf (or just
/etc/lighttpd/lighttpd.conf if you dont have the other file):
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
fastcgi.server = (
"/pics" => ((
"socket" => "/tmp/fastcgi-pics.socket",
"max-procs" => 1,
"bin-path" => "/var/www/pyctures/pyctures"
))
)
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
This is enough, but be aware that "http://mysite/pics" (note the missing
"/" at the end) will *not* be redirected to pyctures.
If you want to be able to refer to your pyctures root both as
"http://mysite/pics/" and "http://mysite/pics", you need to add the
following in the same file as before:
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
url.redirect = (
"^/pics$" => "/pics/"
)
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
And then create an empty file in your document root called "gallery",
otherwise lighttpd will think the path does not exist and return 404 before
doing the redirection.
Enhancements:
- This version implemented pagination, IE support, and automatic thumbnail regeneration on config changes.
- It also improved performance considerably, reduced the memory footprint, added Apache installation instructions, and included several other minor improvements.