Andy McKay's blog

Danae took this in Van Dusen gardens a couple of weeks ago, found a whole bunch of really nice pictures in her iPhoto library, so hopefully a few more to follow.

In a couple of weeks it will be time to head down to Django Con. Looking forward to meeting a whole bunch of Django people. I'll be giving two talks and it would be great to see you there.

The first is entitled "What the Heck went Wrong" and is aimed at more novice developers and focuses on debugging techniques and tools. From how to do a simple print statement to tools like Django Debug Toolbar.

The second is "Fighting Malnutrition with SMS and Django" and covers the great work being done by the RapidSMS team and my brief involvement with it. It's a longer talk that covers an innovative use of Django and some sample code for using Django in a slightly different environment.

Also sad to note tonight that at the moment both djangopluggables and djapp are both offline. Yet djangozen is still chugging along.

Apigee is a new service from Sonoa systems that acts as proxy for API's. That provides:

Analytics and Protection for APIs and Mashups

It does this by creating a proxy that all your requests go through and doing work on those proxies. This is a really interesting idea since API's are the one area of technology that are essentially unmeasured. All other forms of web traffic are easily measured, but rarely API's.

But I'd hate to use a proxy simply because: when the proxy goes down, your API goes down. Everything goes down. There's of course added latency, security is not a huge concern, but SSL isn't an option. Unless of course the proxy get's taken over.

Ideally if I could install that proxy locally, I'd remove this problem - and perhaps this is Apigee's monetization plan. For example, I've pretty much assumed that in Arecibo, our servers can go down and that this will not leave your site in-operable.

A while back I read this post on @mjasay.

It's an interesting post, but made me think about things in a slightly different way. Supposing you are company planning on building support around an open source project. For example Enfold Systems (Plone) or Acquia (Drupal), how do you do that?

The licensing of your project can be a real hinderance since you may or may not be able to code to the project. For example both Drupal and Plone are GPL'd. This puts a limitation on what you can do as a company. If you write a piece of software that includes libraries from the afore mentioned project, your software will (if distributed) have to be GPL'd as well.

This can be a problem if you are trying to monetize on closed source software. I think there are areas of open source projects that can need closed source software. For example, Plone has never done very well at sophisticated reporting. Reporting is boring work that no-one want's to do but enterprises love. Audit logs. Windows integration (what hacker works on windows, c'mon) and so on.

So instead you get to focus on other things. The obvious things: support, training, documentation. But also integration with the project that does not hit the GPL. At Enfold we worked on Windows desktop client, Windows installers, Windows web server integration, for example. Partly because these areas of improvements fell outside of the GPL.

there's already a breed of company that is actively following this advice, and it's the commercial open-source projects like JBoss, MindTouch, Openbravo, Pentaho, etc., as well as foundation-led efforts like Eclipse and Mozilla. Such organizations already know how to add the polish, documentation, and features that an organic community may lack

In Matt's post he points out that companies are working on this, just like Enfold and Acquia. But it's interesting to note, that as a company, your choice can be hampered. It's great to work on and release open source code, but unless that money can come back in via support, consulting or one of your other services, your business might be have a challenge.

It would be interesting to look at companies and see the offerings they provide around their project. For example Acquia seems to be offering hosting and support (primarily). Alfresco seems to be offering hosting and support, but also a paid product. Because Alfresco is dual licensed.

It's good to see companies providing this level of support it's important to make the project a success. But it is curious to see how the license can really impact what a company does around the project.