Licences, project governance, free software in public administration and in business.
Notes after a day spent discussing open source in public administration: the problem is not how much a licence costs, but who holds the data formats, the code, and the continuity of the service.
Read moreThe Open Source Definition sets ten criteria a licence must satisfy for OSI certification. The approved licences sit along one axis: strong copyleft, weak copyleft, permissive.
Read moreAn application server with an object database and a content management framework keep content, presentation and workflow separate. Technical notes on Zope and the CMF, and on why the Open Source approach holds up against enterprise products.
Read moreThe dual-licence model of MySQL, Qt and Berkeley DB rests on the GPL's reciprocity. A technical anatomy of a 2002 mechanism.
Read moreThe questions put to the Pisa panel already have a measurable answer in 2002: filed licences, foundation governance and third-party market share, not opinion.
Read moreTechnical notes on using Linux, Apache and GPL licensing inside a technology park near Pisa, in the spring of 2002.
Read moreBetween 2000 and 2001 the rights to Python changed hands three times. The founding of the Python Software Foundation closes a season of fragmented licences and shows why a project's governance weighs as much as its code.
Read moreFree software is defined by the permissions it grants over source code, not by its price. What the four freedoms guarantee and why copyleft makes them inherited.
Read moreWhat actually changes when a small company builds its infrastructure on open-source software: licences, copyleft, supplier dependence.
Read more
