Archive for the ‘OpenSource’ Category

Packt launches fifth annual Open Source Awards

Thursday, September 2nd, 2010

Packt launches fifth annual Open Source Awards

The 2010 Open Source Awards was launched last month by Packt, inviting people to visit www.PacktPub.com and submit nominations for their favorite Open Source project. Now in its fifth year, the Award has been adapted from the established Open Source CMS Award with the wider aim of encouraging, supporting, recognizing and rewarding all Open Source projects.
WordPress won the 2009 Open Source Content Management System (CMS) Award in what was a very close contest with MODx and SilverStripe. While MODx was the first runner up, SilverStripe, a Most Promising CMS Award winner in 2008, made its way to the second runner up position in its first year in the Open Source CMS Award final.
The 2010 Award will feature a prize fund of $24,000 with several new categories introduced. While the Open Source CMS Award category will continue to recognize the best content management system, Packt is introducing categories for the Most Promising Open Source Project, Open Source E-Commerce Applications, Open Source JavaScript Libraries and Open Source Graphics Software. CMSes that won the Overall CMS Award in previous years will continue to compete against one another in the Hall of Fame CMS category.
These new categories will ensure that the Open Source Awards is the ultimate platform to recognise excellence within the community while supporting projects both new and old. “We believe that the adaption of the Award and the new categories will provide a new level of accessibility, with the Award recognizing a wider range of Open Source projects; both previous winners while at the same time, encouraging new projects” said Julian Copes, organizer of this year’s Awards.
Packt has opened up nominations for people to submit their favorite Open Source projects for each category at http://www.PacktPub.com/open-source-awards-home . The top five in each category will go through to the final, which begins in the last week of September. For more information on the categories, please visit Packt’s website http://www.PacktPub.com/blog/packt’s-2010-open-source-awards-announcement

Book Review: jQuery 1.3 with PHP

Sunday, December 13th, 2009

jQuery 1.3 with PHP

jQuery 1.3 with PHP

Before I start this review proper, I need to disclose one nugget of information first: The author, Kae Verens, and I are both currently serving as members of the Irish PHP Users Group Committee and have known each other for quite a few years. If you believe I can remain impartial and objective (as I hope you do – because I am), read on:

This is the first book sent to me from Packt where I wasn’t left dizzy from trying to understand just what it is the author was trying to get across. It looks like their proof-reader was awake for this one – totally awesome.

jQuery, as the vast majority of us already know, is a JavaScript library that simplifies HTML document traversing, event handling, animating, and Ajax interactions for rapid web development. In other words it does all the heavy lifting and takes care of cross-browser compatibility issues so you don’t have to and thus allows you to focus on the work that you need to do without all those distractions.

“jQuery 1.3 with PHP” is aimed “for PHP application developers who want to improve their user interfaces through jQuery’s capabilities and responsiveness”. Over the course of ten chapters Verens starts the off with an introduction, then a series of ‘Quick Tricks’ that almost immediately help you add some measure of “Web 2.0″ functionality to what I’d term a “web 0.2 application” rather sharply.
The book ends with a chapter on Optimization – some of which you are bound to already know and some which are complete gems.

In the middle are chapters with mini-projects on tabs and accordians, forms and form validation, file management, calendars (and how to make your own google-calendar-like application), image manipulation, drag and drop and data tables.
In each case, projects are analysed and the required steps for each are outlined in the simplest terms – no extraneous buzzwords are used or are the projects over-analysed for the sake of pedantry.

I was a little surprised in some places where, for example, the json encoded output was not created via json_encode; but then thought not everyone is going to have PHP 5.2 or greater installed. Thumb forward a few pages and this is mentioned. So all’s o k.

It was good to see Kae suggesting use of the PEAR Validate package (or similar) in the Forms and Forms Validation chapter (chapter 4). I had to wonder if there was a PEAR package for creating and shunting down jQuery validation rules to the client – and found that there isn’t. That’s something to consider for later on, I guess.

The rest of the book is similarly both easy to read and easy to understand – my first port of call for learning how to do something that I’d almost term exotic with jQuery and with PHP in the background is usually Google but that is going to change (actually it already has).

Honestly, I wouldn’t be surprised if this books working title was “JQuery and PHP: The HowTo” – it is that good.
Now, this book is not for learning jQuery – that is not within its remit, but I would heartily recomend “jQuery 1.3 with PHP” by Kae Verens to anyone wanting to utilise jQuery from a PHP background.

Beginning Joomla! (Second Edition); A review

Tuesday, October 27th, 2009

A while ago I was sent a complimentary review copy of “Beginning Joomla! (Second Edition)” by Dan Rahmel and published by Apress.

In a clear non-patronising and concise manner the author explains to the reader just what Joomla is (a content management system), how to install, add content, administer, design templates and write extensions for it. He touches on SEO and covers the aspects of both deploying Joomla on Windows, Linux and Mac.
Done in a gentle manner with graceful explanations along the way, he explains everything in a clear manner: how to troubleshoot not being able to access the web or database servers and even mentioning the password system differs from version 4 to version 5 of mysql, for example.

There are a few points in the book that startled me however; Rahmel informs the reader in chapter three that if XAMPP is used as a means of installing the base requirements then certain security concerns need to be addressed. In chapter two he states PHP 4.3.10 as the lowest version required – I’m surprised that a later version of PHP 4 wasn’t recommended, even though 4.3.10 may be the lowest required version – version 4.4.10 4.4.9 for example which is the very last version of PHP to ever be released. I hope this is just a typo that hadn’t been caught in time.
If it was not, then I’d have to express a certain level of professional disappointment; the security enhancements and bug fixes in PHP 4.4.10 should definitely have been enumerated. While it is true to say that most installs of Joomla are into shared hosting environments where such changes can not be implemented, I also would have expected the author to have mentioned that Apache, and by implication Joomla, performs better when configuration directives are specified in the httpd.conf files rather than .htaccess files which must first be scanned for at a directory-by-directory level.

I had been looking forward to reading the chapter on creating extensions (chapter thirteen) but was rather disappointed. I had expected Rahmel to go into much more depth, especially as the blurb on the back of the book mentions how he has coded other solutions from scratch in PHP and ASP, so surely there would be hard-learned tips and some advice that he could share? Instead he hardly mentions the Joomla API nor does he provide a reference or link to where further information on the subject could be found.

I would like to say that the second edition of “Beginning Joomla!” is well rounded but the lack of detail on creating extensions and the differing levels of detail regarding security and performance tips makes me shy from saying that.

Also, I do wish that there was a list of recommended reading and a glossary in the book too – it is invaluable to have a “cheat sheet” of what different terms mean and also to know what other bodies of work are available to help you learn more.

To summarise – “Beginning Jooma! Secong Edition” is a well-written book aimed at (surprise) people new to using Joomla – it just could be better and the section on developing plugins or components should simply be dropped as it is not adequate and probably could have an entire book devoted to the subject.

OSSBarCamp lightning talk on PEAR: slides now online

Wednesday, September 23rd, 2009

I was the the OSSBarCamp event in Dublin last Saturday and gave a lightning talk on PEAR. It went well (I think). The slides for it are now online at the talks.php.net website.
I’ll write up more thoughts on the event later if I find the time ;-)

OpenStreetMap in the news again

Friday, August 28th, 2009

Spotted two new articles on OpenStreetMap recently – one on the PocketLint site: “OpenStreetMap – Crowd sourced cartography set to re-map the world“; and the other on Wired: “GPS Hackers Blaze Own Trails With Crowdsourced Maps“.
They both mention how OpenStreetMap cartography is more detailed than the alternatives produced by Navteq, Teleatlas et al and the Wired article even goes to include at least four links to various parts of the OSM wiki and mentions some of the devices that our maps can be used on such as iPhones, TomToms and so on.
What with this and more OSM ‘love’ spilling into Episode 83 of Floss Weekly – Steve Coast, founder of OpenStreetMap, was interviewed in Episode 81 it looks like activity is only going to increase.

OpenStreetMap at the Farmleigh Park Geeknic in Dublin, anybody?

Tuesday, July 21st, 2009

There’s a Geeknic (picnic for geeks if you aren’t too sure) on in Farmleigh Park, Dublin in a few weeks time (on Sunday 2nd August @ 1pm). I can’t help but notice that the OpenStreetMap map of Farmleigh could do with a bit of attention – from what I can make out there are unnamed roads on the OSM map along with ones that aren’t there – and as we all know, we can add as much detail as we feel necessary ;-)

So, anybody on for a bit of socialisin’, evangelisin’ and map making?

OpenStreetMapping Nenagh

Tuesday, June 16th, 2009

So yesterday I had a quick interview with a journalist from the Nenagh Guardian – my local paper – about this OpenStreetMap (OSM) mapping malarky.

As most of you will probably know OSM is to printed atlases from AA, Ordnance Survery etc, as wikipedia is to encyclopedias. People can contribute data to the project through a variety of activities: going out and actually mapping an area with a sat nav or gps unit [even a mobile phone with GPS in it such as an iphone, nokia n95 or whatever], tracing data off Yahoo [and other] aerial imagery, filing bugs on the openstreetbugs website or literally drawing in information via the walking papers map making website. And better again, this is about providing free geographic data such as street maps to anyone who wants them.

Anyway…I mentioned how the OpenStreetMap map of Nenagh is more complete than even the latest commercially available maps for Garmin and Google Maps and listed off a few ways how OSM could be used commercially: by real estate agents, courier companies, how being able to pin-point where all the amenities are would be useful for tourists, and so on.

Compare the Open Street Map of Nenagh with the Google Map of the area – as you can see, there’s still quite a bit of work to be done – Millers Brook needs to be marked as such along with the various groves, avenues etc that comprise that estate. Plus all the amenities, shops [perhaps even their opening hours] and the Shannon Development Industrial Centre still need to be added – as I’m sure are some other small portions of the town that I’ve unknowingly neglected.

It’s fair to say that this will never be finished – existing housing estates will be extended, there will always be urban development plans that when implemented would also need to be included on the map.

It would also be cool to have the new “Nenagh Cycling Hub” rendered on the opencyclemap.org website.

I discovered the OpenStreetBrowser site to be a great test of the data that myself and others have entered – it’s also a great way of demonstrating just what can be done with OSM data.

If you happen to spot something that I’ve missed please either drop me a comment or use the openstreetbugs website.

On a related note: it would be good to see a PEAR/PHP based client/component for interfacing with the OpenStreetMap server so that interesting apps utilising that data could be implemented on the LAMP stack – something to go alongside the Services_GeoNames package from pear ;-)

7 things…

Wednesday, January 14th, 2009

I got tagged by Chuck for this “7 Things” meme. So here are 7 things you may not know about me:

  1. I first met my wife at her house warming party seven years ago – it took four years for anything to happen though! I’m so happy it finally did though!
  2. My first computer was a ZX Spectrum 48K that was bought when I was seven years old – I’ve since progressed through BBC computers, Apple Macs and then onto PCs. I also had a accounts on the WRTC vax – VMS and OSF/1.
  3. I’ve similarly gone through a number of differing computer languages: Basic in various incarnations (ZX Basic, BBC Basic, VB), Z80 Assembler, HyperCard (yes, really), C, C++, JavaScript, Perl, PHP, Python, ColdFusion, Java.
  4. I might be Irish but my surname isn’t.
  5. I read a lot of fantasy: Gemmell, Eddings, Tolkien, Pratchett; though I also enjoy Tom Clancy and Dale Brown novels.
  6. I’m long-sighted in one eye and short-sighted in the other: one good reason why I’ve never been that good at sports.
  7. I am an active PEAR developer.

Tagging Others

I’m supposed to tag 7 other people who then repeat the whole process:

  • Proinnsias Breathnach for being such a good friend all this time. And because he doesn’t blog enough.
  • Kae Verens for having a name that sounds the same as his first inital – and for helping out loads at the IPUG stand at last year’s Irish Opensource Technology Conference.
  • Donncha O Caoimh for his trojan work back in the day with the ILUG CMS and for WordPress mu.
  • Jaime Hemmett for her exuberance and energy she’s brought to the Irish PHP scene.
  • AJ McKee for starting the Irish PHP Users Group in the first place!
  • Justin Mason for Spam Assassin, SiteScooper and being an all round nice guy.
  • Fuzzix for his levity and humour. That plus he’s a ZX head like myself.

Rules

  • Link your original tagger(s), and list these rules on your blog.

  • Share seven facts about yourself in the post – some random, some weird.

  • Tag seven people at the end of your post by leaving their names and the links to their blogs.

  • Let them know they’ve been tagged by leaving a comment on their blogs and/or Twitter

PHP 4 – this parrot is deceased!

Friday, August 8th, 2008

I woke this morning with a grin. Nope, nothing to with the Olympics; PHP 4 is dead and by that I mean it is no longer supported – no more official security updates for PHP 4 – or backports from PHP 5 or PHP 6.
The last release of PHP 4.4 occurred yesterday.
Why is this important – and why am I grinning?

PHP 5 has improved support for Object Oriented Programming, PDO, numerous performance and security enhancements that make continuing to maintain or develop PHP4 specific code a mugs game.
The enhancements in PHP 5.3, which is scheduled to be released in October, and those in PHP6 make it all the more compelling to move from PHP4.
If you are a developer and are unaware of this or are clinging on to PHP4 for dear life, you’d do yourself a favour by evaluating all options open to you – including a change of career.

The hosting market may be slow to catch up but remember this: there will be no more security updates for PHP4 and there are security enhancements in PHP5. Compelling reasons to ask your hosting provider if they do PHP5 hosting. Web hosts who are dedicated to supporting PHP 5.2 or later are listed on the gophp5 website.
Blacknight are the only Irish hosting company listed there.

Ivo Jansch, CTO of iBuildings painted a fairly bleak picture a month ago regarding continued PHP4 usage; poising the question “what if there’s an exploit for PHP4 and the bad guys are waiting until after 8/8/8 to make malicious use of it”. This is just scare-mongering but he does make a valid point, after today it will take longer than usual, if at all, for a fix against such expoints to be made available. So if you’re in business it would be wise to consult with your hosting company ASAP.

Impromptu PHP User Group meeting in Dublin tomorrow (7th May)

Tuesday, May 6th, 2008

Jan Lehnardt , he of couchdb fame, and I will be at the Longstone tomorrow from about 19-20:00 onwards. I’ll bring along some elephpants for the taking!

And I think some apache folks may be there too.

Today was Document Freedom Day

Wednesday, March 26th, 2008

Today was Document Freedom Day.

Book Review: SOA Approach to Integration

Wednesday, February 6th, 2008

Book Review: SOA Approach to Integration by Poornachandra Sarang, Frank Jennings, Matjaz Juric, Ramesh Loganathan – (Packt Publishing)

I was recently asked by a representative of Packt Publishing to review this book on Service Oriented Architecture and I looked forward to reading the review copy they sent me.

While I waited for the book to arrive I searched the packt website for the errata for it – and found none. I thought “Either the book is perfect or they haven’t gotten around to publishing a list of corrections yet”. Quite an omen.

The blurb on the back of the book says that it is intended for “architects and senior developers who are responsible for setting up SOA for integration for applications within the enterprise and applications across the enterprise”.

The 360 or so pages are split into six chapters:

  1. Integration Architecture, Principles and Patterns
  2. Service- and Process-Oriented Architectures for Integration
  3. Best Practices for Using XML for Integration
  4. SOA and Web Services Approach for Integration
  5. BPEL and the Process-Oriented Approach to Integration
  6. Service- and Process-Oriented Approach to Integration Using Web Services

Chapter one focuses on integration technologies, approaches and patterns – pretty much laying the groundwork as you would expect an introductory chapter to do.
The second chapter attempts to drill down deep into what SOA is about.
Chapter three details the Best Practices that should be followed when using XML for Integration and seems completely out of place considering the intended audience that this book is written for – it is far to low-level for a book aimed at software architects.
Chapter four focuses on web services and does a very good job of it, advising for example to stick with approved Standards rather than using proprietary extensions of say SOAP and WSDL. Amusingly though, while advising that web services should remain independent of programming languages and application platforms the book soley gives examples in Java and .net.
Chapter five details BPEL (Business Process Execution Language) and the Process-Oriented Approach to Integration in a rather comprehensive manner.
Chapter six, discusses the Enterprise Service Bus (ESB) in depth. Just as with chapter 4 I was amused with this one. There is a subsection to it about how ESB helps avoid vendor lock-ins yet there is no discussion of open source offerings that are available for EBS, BPEL etc etc.

“SOA Approach to Integration” focuses in detail on the WS-* standards and references SOAP very often. There is an anomaly in that there is no mention of REST and while the authors, with their collective experience in Java and .NET, focus on detailing use and interoperability between those platforms I would have expected at least some Open Source technologies and programming languages to be referred to – the ESBs Apache Service Mix, Mule for example; along with perl, PHP and python as some of the programming languages that can be used.
If PHP was to be mentioned I would expect the “WSO2 Web Services Framework for PHP” to be listed as well as, perhaps, the SOAP and UDDI packages from PEAR.

I found myself reading some sections of the book repeatedly – not because the technical content was too complex to understand; but due to it being too verbose, due to bad grammar, spelling mistakes and poor punctuation. I also felt that the diagrams and figures in the book should have been identified better, both in the text and individually. A glossary and a more complete index would have been nice too.

On the whole, although I did enjoy reading portions of the book, it seems to be a lacklustre introduction for software architects and senior developers that are new to Service Oriented Architecture but that’s pretty much all that it is.

There’s some mapping ahead

Sunday, November 18th, 2007

Inside the next seven days two things that I am very excited about* are going to happen:

  • On Thursday (22nd November), Steve Coast from the Open Street Map project will be giving a talk at the HEAnet offices in the IFSC, Dublin.
  • There will be a “Mapping Party” in Dublin on Saturday and Sunday.

*Never said it wouldn’t be something geeky ;-)

Jonathan Kozol Hates Microsoft!

Wednesday, June 7th, 2006

Peter Rock Lacroix, a technology coordinator and teacher at a small international school in west Africa gives the background about the school being told to reverse it’s decision to move to Free Software (which was decided unanimously by the school’s Technology Committee) after “numerous recommendations forthcoming from the US Embassy, the State Department, and technology professionals involved in providing services to international schools worldwide”.

It’s interesting how an unanimous decision by a small school in west Africa gets overturned by the influence of, wait…the US Embassy and State Department – not the school’s director but by some other sovereign state.
[ http://gnuosphere.blogspot.com/2006/06/jonathan-kozol-hates-microsoft.html]

This reminds me of the President of Peru being invited to visit Bill Gates after Peruvian legislators approved a bill sanctioning use of open source software by government and levelling the playing field for start-ups against Microsoft.
[ http://www.wired.com/news/business/0,1367,54141,00.html , http://www.theregister.co.uk/2002/07/16/peru_mulls_free_software_gates/]

The interference of the US and Microsoft [so Microsoft gets to retain a monopoly] in particular with the internal affairs of sovereign states is most vexing.

And to sum it off? Peter was told “you need to refrain from placing undue focus on your personal beliefs concerning the philosophy and practice of Microsoft.”

A personal experience of opensource development

Tuesday, May 30th, 2006

Justin Mason, author of SpamAssassin, describes his personal outlook on OpenSource development.

Notes from “Free Software in Government/Public Administration” talk by Federico Heinz on April 29th.

Wednesday, May 24th, 2006

These are my notes of the talk on Free Software in Government/Public Administration that Federico Heinz gave at the IFSO event hosted on April 29th.

There are three essential requirements of software being used in Government:

  1. Security
  2. Transparency
  3. Persistence

This is only possible using Free Software; using other, proprietary, software to do this just doesn’t work: not using Free Software is immoral as no other type offers these three requirements of security, transparency and persistence.

1. Security

Personal details, and other information needs to be kept secure as it is confidential. Security means:

  • Keeping people out from data
  • Access to change data
  • no unauthorised people should be able to prevent access to this data.

2. Transparency

  • handling data
  • what is done to the data
  • actions of the Public Administration
  • equal access to the information

Software shouldn’t be able to prevent or stop procedures from being fulfilled. To ensure this isn’t possible you need to be able to examine the source-code of that software.
Software should not enforce requirements that aren’t needed by Law and should enforce requirements that are required.
Again the only way to ensure this is by checking the source code of the software.

3. Persistence

There is a very long lifetime of data, especially rearding deeds of ownership of land for example. We need to ensure this information can be accessed in fifty, 100 or 200 years time.
The lifetime of software is much shorter so you can’t depend on specific software that won’t be around.

What is Free Software anyway?

Fedrico explained the four requirements or characteristics of Free Software:

  1. The software can be used for any purpose.
    Some software licences [of propietary software] prohibit benchmarking, reverse engineering to ensure compatibility (also meaning that you can’t report problems that you find by doing this because it might prove that you were doing something that the license doesn’t allow). Fedrico recounted that at one stage you couldn’t use Microsoft Frontpage to create sites that criticise Frontpage!
  2. You are allowed to study how Free Software works and adapt it for your needs.
    An analogy to this refers to the National Budget – it has to be available for people to analyse and understand it, to check that it’s legal and so on. With software you don’t necessarily know what it does, unless you can check the source code of the software and verify that code is what was used to produce the software].
    Microsoft Word documents store a GUID (Globally Unique ID number) that can be used to identify who wrote a certain document. No one asked Microsoft for this, they have been asked to remove this or to even provide a means to disable it. They have not. This is a prime example of something happening that you don’t/aren’t aware of. So you must be able to find out what software does and make it do what we want.
  3. Freedom of solidarity, helping friends, brothers and family by giving them copies of the software should they wish.
    Public Administration should lead by example.
  4. The fourth freedom is that users are allowed modify the software and distribute those changes.

The issue is not of cost but of doing the right thing.

Backdoors

Some software that is now Free has been found with back-doors [ways to secretely gain access]. There are programs that automatically install software during their update process and you don’t know what the new software is for. It might be checking if you are using unlicenced software – what else can they do that we aren’t aware of?
Imagine this in your Foreign Affairs Department: a third party, a private company installing whatever software they want…

Bugs/Errors

The German Government was using Windows NT, which has errors that Microsoft won’t correct. Simply upgrading to another Microsoft operating system won’t work for them as other software was written specifically for Windows NT and won’t work on any other Microsoft operating system.
They are now using Linux and can fix problems when they want, either by themselves or others, and know it is completely secure.
“Trying to build security using proprietary software is like trying to build a prison with Merrangue!”

Persistence is important!

Persistence is possible with proprietary if you are careful to give it a Free Open format – but proprietary software’s versions of Free Open Formats mightn’t be readable without that proprietary software. The odd HTML produced by Microsoft Word is a good example of this.
Also proprietary companies extend these standards to “make it better”.
Proprietary software has an incentive to prevent interoperability.

Transparency Revisited

Proprietary software is by definition opaque. Some companies might allow you to view a portion of source code – but can you be truly certain that code relates to the product?
If you can’t study what a program does then how can you be certain of what that software does?

Other Advantages to Free Software in Public Administration:

  • You can use it as much as you can. For example what happens if you suddenly need to expand a social program that requires more of the [same] software to be installed? With Free Software you don’t need to renegotiate licenses etc.
  • Free Software licenses are very easy to understand and comply with; no ‘per seat’ or per ‘CPU’ issues.

The more important points/advantages are still security, transparency and persistence.

Cultural diversity.

Some governments have obligations to produce documents in more than one language due to legal obligations.
Proprietary software might not have support for the languages in question – adding support for these languages in free software is obviously possible.

Proprietary software cry foul regarding lobbying to have Free Software
used.

They say: “Choose software for its merits and what it does, not whether it is Free or not.”
The licensing mode is the merit what’s the point in having the best program but it can’t let you do what you want it to do. You can add improvements to a Free Software according to your own priorities – with non Free proprietary software it is up to the author/owner of the copyright.

They say: “Public Administration should leave it to software developers to decide the best way to develop software”.

Proprietary software companies claim that Bills are discriminatory – this is not true. Bills say what conditions are acceptable – anyone is free to comply with this.

They say: “Bills are anti-competitive”
Monopolies are anti-competitive!
Free Software enables competition, competition regarding services etc. supporting some program customer can decide best service provider without changing the software, therefore Free Software enables competition.

They say it undermines local economy not allowing locals to sell proprietary software to Public Administration. This means the local software industry is relegated to a secondary role.
With Free Software local industry can provide higher values to customers by fixing problems. This provides a huge opportunity for selling add-on development.
This is money that stays in the local economy.

They say: “Migration costs to Free Software are high”

Even migrating from one version of proprietary software is high, but only because they are kept artificially high just for going from one version of software to the next.
This is an argument for going to Free Software ASAP.
No one is forced to sell to Public Administration.
They say: “This is important data, you can’t just entrust it to volunteers”
Discontinuity problems don’t exist just with Free Software – look at the number of proprietary software that’s not used anymore. FoxPro is a good example of this – it was bought up and discontinued. What happens if there’s a problem?
Informix is another example – IBM bought it and keep telling their users they can upgrade to DB2.
This can’t happen with Free Software – so long as software is used the users (and developers) can support each other. So long as there are users the software is maintained.

How are you to ensure security, transparency and persistence with proprietary
software?

Only with Free Software can you preserve the citizens rights. Only with Free Software can the Public Administration do its job with out betraying its citizens.

OpenIreland ICT Expo Talks.

Wednesday, May 3rd, 2006

Paul O’Malley has listed the OpenIreland ICT Expo Talks on the OpenIreland website – it seems like a very varied and interesting set of talks will take place in the RDS over the next two days.

Irish PHP Users’ Group

Wednesday, May 3rd, 2006

AJ McKee has kickstarted an Irish PHP Users’ Group mailing list. Not a bad idea at all – there’s already a frappr/Google map for members.

Federico Heinz on Education and the Public Administration

Tuesday, April 25th, 2006

Federico Heinz, president of FSF Latin America, will be in Dublin to give two talks in the ICS Building on April 29th. He will be speaking about free software in government /public administration and also about free software in education; starting at 14:00 sharp. There are more details available here.

Notes from Zaheda Bhorat talk at FOSS-Means-Business Conference

Thursday, April 20th, 2006

These are my notes from the Zaheda Bhorat talk at the FOSS Means Business Conference on Thursday 16th March 2006 in Belfast.

Zaheda Bhorat
International Manager, Open Source Programmes, Google.
Zaheda Bhorat has been an Open Source advocate since managing the OpenOffice.org project and community while working for Sun Microsystems Inc. [taken from the FOSS Means Business website]

Why are google using FOSS?

  • It gives them control – they can maintain independence from software companies.
    Special/secret tweaks to the software stack remain with themselves.
  • It also gives Google a great degree of adaptability – they can drill down many
    layers into the software stack to enhance services [reliability, speed,
    etc.]
  • great flexibility – they can do something outside of the ordinary without
    having to disclose this to the software companies.

Google contribute code to:

Google participate with:

Why do they do this?

  • To make software better [They don't have to keep re-applying their private patches of code and others can collaborate].
  • To encourage development.
  • To avoid reinventing the wheel.

Donations and Grants given by Google