Tarek Ziadé reports on PloneSoftwareCenter progress during the Paris Sprint.

I am amazed to see the progress he and the folks helping him had so far. This is definitely all that I dreamed for when I started with the idea in January 2006. It is great to see that even though ideas take a little longer to get implemented in the Plone community that they do not simply get abandoned, but there’s always people willing to pick up an idea and turn it into reality.

Many thanks for Tarek for all of his work. Once this gets rolled out into the new plone.org it will make the life of us developers so much easier when making releases that we will ask ourselves “how could I live without this for so long”.


Guido van Rossum invites Python developers to try out his Code Review app, inspired by Mondrian but supporting Subversion instead of Perforce.


Google just announced the Google App Engine, and reading through the documentation and all I came up with this idea: it should be possible to get Plone running on the Google App Engine!

How would that be possible you ask? Well, a couple things are required.

The Repoze guys have Plone running as a WSGI app, AFAICT. So the hosting part is pretty much settled. You just deploy an app that sets up a Repoze WSGI App.

Then comes the storage. Plone, being based on Zope, uses the ZODB. But the Google App Engine doesn’t allow writing to the filesystem. The solution? Having a RelStorage backend that uses the DataStore API.

The final step would be getting rid of the C extensions in Zope, and having Zope run in Pure Python. Fortunately, there’s a student application for this year’s Google Summer of Code project that intends to port Zope to Jython! That should help with this last step by providing Pure Python implementations of the C extensions, if it gets approved.

I am really excited by the possibilities that this opens up. And would love to see someone pick up this project and turn it into reality.


If you have been paying attention to Plone checkins, you might have noticed some checkins mentioning CSRF (Cross-Site Request Forgery) flying by. Today Secunia released an advisory about the issue.

As can be seen from the referenced paper, web technologies make some things just way too simple to hack around.

On a unrelated note, call me luddite, but I really think moving our life to the cloud presents way more unforeseen threats than our little brains can imagine.


Found out about the cool comics site Comiqs this morning. It’s very cool, and has features similar to those of Comic Life, which comes pre-installed with new Macs. The nice thing about Comiqs, is that it’s online and free.

Comiqs allows you to create a comic strip, and integrates with Flickr, so you can use your photos from Flickr automatically.

To try it out, I’ve created a fictional story where an unadvised Plonista meets the evil Grokkers, and is rescued by a Sleepy Ninja. Hope you like it. And I hope the actors involved don’t mind me using their images. :)


What is Crick?

15Feb08

The Jabber protocol has this thing called a Resource Names. It’s actually a quite interesting concept.

Some Jabber clients, for example Adium can display the Jabber Resource Name of your contacts. Some Jabber clients use their own name as the Resource Name.

Today while looking at one of my contacts, i saw it had a Resource Name of Crick.v1000xxxxxx. Curious, I’ve tried to search the web for any references to that and only found one meaningful reference, exactly one. And it seems to be from someone at google.com (the person on my contact list was from Google too).

Now, that certainly isn’t from Google Talk, because Google Talk uses a similar but different Resource Name, Talk.v10496B0A851. They are very similar though.

Maybe Crick was Google’s internal codename for Google Talk before launch? Or maybe is the codename for the next version of Google Talk? Who knows…


Jonathan Bowman posted some instructions about how to compile Python-LDAP on Windows, using MingW. His instructions create a shared binary though. I was able to build a static binary in the past, but I have to hunt down my notes about what changes to build a static binary. It is great that someone else was able to do it and document though.


Apparently there was quite some interest in my post from two days ago yesterday about People Management. Unfortunately, the content was all in Portuguese.

Today though, I have more stuff to announce. As part of my research, I’ve interviewed some key people running successful virtual teams, and some of them are known to readers of this blog.

As of today, those interviews are available as podcasts for everyone to download. So if you want to hear what Paul Everitt of Agendaless Consulting, Alan Runyan of Enfold Systems, and Christian Reis of Canonical, Inc and Async Open Source have to say about the subject, please head over to my newly-created podcast at Virtually Working.

I would really like to thank those guys for their support. They provided tons of great insight without which I would not have managed to finish my paper. And I would like to invite anyone who has more great insight about virtual teams to contact me (just comment on this blog post). I would really love to interview more people about this subject.



Follow

Get every new post delivered to your Inbox.