Harry Fuecks Comments ZZ/OSS Installer

Harry Fuecks took a look at ZZ/OSS Installer and his honest comments clearly describe the status of the application and its potential.

Yes, true, the latest release of the installer is a development release with known and still-to-be-found bugs 😉 We are collecting feedback from the community on new features and hidden bugs, that’s why we did this early release. Meanwhile, development goes on and we are fixing bugs and implementing new features for the next release 1.1.0dev2.

Although the application itself is not yet superstable, I believe it is good enough for experienced PHP devs to start deploying their applications with it. Developing and installing applications that entirely or partly consist of PEAR-like packages, is much easier with ZZ/OSS Installer compared to PEAR Installer, because there is e.g. automatic dependency resolving built in. This tutorial on deploying phpMyAdmin with ZZ/OSS Installer gives you a basic idea how to procede.

Should you encounter any problems, feel free to contact the ZZ/OSS Installer developers via the mailinglist, IRC, etc. as stated on the ZZ/OSS Installer project Website – we’ll do our best to help you. The nice thing is, that once you have a working ZZ/OSS Installer on your system, it is pretty easy to install the latest version with this installer from CVS sources.

ZZ/OSS Installer Client 1.1.0dev1 Released

ZZ/OSS is happy to announce that the ZZ/OSS Installer Client (ZIC) 1.1.0dev1 has been released. ZIC is a PHP-based installation wizard and development tool for professional release management of modular PHP applications.

This is a development release with new features. You can use this version to make your own PHP software installable with ZIC. The schema of the XML files describing your application is solid.

This new tutorial on making phpMyAdmin installable with ZIC is a good start.

If you use Mozilla, please make sure to set the preference ‘network.http.redirection-limit’ to the value ’30’ or higher if you get a “redirection limit” error. Type ‘about:config’ into the address field to access the preferences.

Download ZIC 1.1.0dev1 from the Sourceforge project homepage.

Please report bugs to the bug tracker, mailinglist, or IRC.

More information is available at the installer homepage
http://www.zzoss.com/projects/installer/

An excerpt of most important changes:

  • works on Windows and Linux
  • integrated plugins and packages manager for installed applications
  • development applications can now also be installed
  • default install path of development applications has ‘-dev’ added to app name
  • new default theme ‘kde’ which is more neutral
  • option to automatically remove setup wizard after installation
  • handle different magic quotes settings
  • progress bar shows download process
  • single packages or plugins can be added
  • works with E_ALL error reporting
  • fileroles: default behaviour of installer without having any filerole plugins installed is that the file gets copied to the location specified in filelist/file of package.xml
  • configurable quick installation of development applications allows for faster development
  • detect circular dependencies of packages needing each other
  • process filelists with nested dir elements in package.xml

An Introduction to Radical Constructivism

By chance, I found An Introduction to Radical Constructivism online. This article is part of the excellent book “Die erfundene Wirklichkeit” (edited by Paul Watzlawick) that influenced me a lot during my university studies.

Call constructivism my theoretical mantra 😉 It’s the only theory that does not attempt to explain reality and defines truths, but explains why we explain reality the way we explain it – and why we fight for a certain truth. It also serves as a perfect theoretical basis to understand “knowledge” as a social phenomena.

Scientific Publications: "It is the author's work, it is his or her right"

Want to have a deep look inside of major changes in society? This transscript of a discussion on scientific publications in the UK Science and Technology Committee of the House of Commons indicates that the knowledge society is in full swing and that the scientific community is slowly moving towards a more open and free approach towards scientific research and knowledge transfer in general.

This transscript is also a wonderful manifestation of how knowledge mediaries like publishing houses step by step lose power and impact and how the authors of scientific works, the producers of the knowledge goods traded in the scientific community, gain power.

Open Source Business Models: "Dual Licensing" and "Quid Pro Quo" Explained

For anyone wondering, how the “Dual Licensing” business model of MySQL works, they have briefly explained it in a news posting:

As second-generation open source vendors, MySQL AB, Sleepycat Software and Trolltech AS make the majority of their revenue from selling software licenses. This license-based business model offers higher margins than services-based businesses. Historically, most open source companies have tried to make money by selling services and support.

The guiding principle behind dual licensing is “quid pro quo,” or a fair exchange. Under this model, vendors offer their products under both an open source license and a commercial license. This allows open source projects to use the software at no cost, which contributes to widespread use and testing of the software and the fast growth of a large installed user base. Companies redistributing the software as part of commercial products can also get the benefits of the open source software by purchasing a commercial license, which releases them from requirements to publish their source code. Commercially-licensed customers generate revenue for the open source vendors, which contributes to the rapid development of high-quality software.

I thought about the term “fair exchange” and came to the conclusion that the Dual Licensing business model is based on three crucial factors: knowledge, time, money.

This means: If you’re a FOSS software developer, you might have a basic understanding of which licenses are compatible and which are not. If you’re a software developer in a company that has never dealt with FOSS licensing issues but would like to use MySQL for example, you could either consult one or more lawyers that analyse the situation for you. The other option would be to pay the costs for a commercial MySQL license, which are marginal compared to what the lawyers would charge.

Seen from that perspective, the Dual Licensing model is fair in terms of how much the software user knows about the topic: If you do not have money, but time to investigate and inform yourself about FOSS licensing and you produce FOSS software yourself, you can do your work without any financial burdon. On the other hand, if you have money and you’re short on time analysing the whole issue, simply pay the fee for a commercial license.

The revenue of companies like MySQL is based on the three crucial factors “knowledge”, “time”, “money”. Dual Licensing shows that software companies who in fact produce true knowledge goods, can make money based on these factors and behave fair as well as profitable in a knowledge economy. It is also important to understand that there are two kinds of revenue they make: financial revenue from commercial licenses and revenue in terms of knowledge and lower development costs. The later is what MySQL gets back from a FOSS community that might not buy commercial licenses, but do testing, bug fixing, APIs, etc.

In a knowledge economy, “knowledge” is a good that gains value the more you have of it – other then the industrial economy, where goods usually loose value if the market is saturated. The Dual Licensing business model somehow plays industrial if you want to combine FOSS software with non-FOSS software, i.e. if you do not adhere to the standards of a community of open knowledge transfer. Then you will have to pay for the software aka knowledge good, just as if it were a car. On the other hand, if you are part of the open knowledge transfer aka a free community (“free” as in “freedom of speach”), you can use for example a GPLed software for free (“free” like in “free lunch”).