Here’s information about the Python Unconference in September
The schedule is evolving, but it looks like the focus will be zope/plone and SciPy .
. It’s hosted by the Houston Python Users’- group
Here’s information about the Python Unconference in September
The schedule is evolving, but it looks like the focus will be zope/plone and SciPy .
. It’s hosted by the Houston Python Users’- group
Alexander Limi provides an update about development on Plone 3.0. (here’s a screenshot). My ebook site will be backed by plone 3.0. I’ll probably be jumping the gun a bit, deploying on a release candidate or beta 2 version. (Or maybe, I’ll just test all my 2.5 work against 3.0 and magically change over in May when everything is ready).
It’s always a debateable question about how closely you should match your deployment schedule with the latest release of a piece of software. If I were in the corporate world, I’d play it safer, but now that I’m on my own, I don’t mind the risks involved.
Torrent Freak, a website devoted to coverage of p2p/torrent technology news. Also includes a podcast.
Martin Aspeli on the love-hate relationship people have towards plone:
So following on from that is process. Outsiders always have a tendency to want to add more formalism to Plone’s process, but that kind of misses the point. Some formalism is needed, if it enables people to work on Plone more effectively, for example by avoiding duplication of effort. When it starts restricting them, however, it’s bad. Most people have a day job that gives them plenty of management overheads, and when they go home and want to hack on Plone, they just want to be productive. Surprisingly, this doesn’t actually mean we all pull in different directions. The transparency, friendship and mutual respect that exists in the community means there are incredibly few real disputes, and if they arise, they are normally resolved to mutual satisfaction. We tend to debate until we mostly agree and let pragmatism do the rest. This depends greatly on Plone development being decentralised, which in turn stimulates innovation.
Martin wrote a great guide on creating 3.0 friendly content types. Here’s a video of the same guide.
Interestingly, at the end of his rant, Martin lamented that “Now, if only I’d spent half as much time fixing Plone 3 bugs as writing this, that may have deflected some future criticism from Plone 3. Back to work!” Sometimes getting a rant out of one’s system can be the perfect way to rejuvenate one’s creative energies.
(Martin wrote his dissertation on the plone open source developer’s community PDF ).
It’s official. This weekend, I’m going to do some playing around with Zope 3/Five application development.
I bought Web Application Development with Zope 3, a recently published book about the subject.
Here are some appetizers to follow on the worldcookery site.
I’ll be going through Martin Aspeli’s tutorial on 2.5/zope 3 development.
I’ll be watching Rocky Burt’s video of the talk he gave at Plone conference in Seattle on zope 3. It was way over my head at the time, but I think I’m ready for it. Well, not intellectually ready, but psychologically ready. I’m rarin’ to go.
I have my zope hosting to try it out on a live server (well, zope 2.10 with Five). Also, I have my laptop to try things on.
Making a zope 3 application will be an academic exercise, but very instructive for figuring out the interfaces (also, good for familiarizing myself with python. And getting myself ready for deploying my plone 3 site.
My goal for the weekend is not to get a plone site out (although I think I might end up doing so).
I’m preparing for the upcoming release of Plone 3.0 alpha 2 this weekend. Beta 1 should be out at the end of February (yes, there’s been significant schedule slip, but I can wait).
Although I won’t get around to it, I’d like to get my head around the KSS tutorial (which is plone’s version of Ajax).
I am not a fulltime programmer, but I enjoy getting it into it again. Also, I wanted to try writing some XSLT this weekend. That might be wildly optimistic, but it would be very nice.
Today I figured out why it’s so difficult to find lowcost plone CMS hosting: it uses buttloads more RAM than PHP CMS’s
I also learned why it’s possible for digital cameras to become so cheap: they offer 90 day warranties instead of 1 year warranties! (Btw, warranty information is often missing on the product spec information on the major sites).
I realize that from a marketing point of view it makes sense for a camera company to put photos of teenage girls on their promotional information. But why would they choose to have this photo on their home page?