I recently read Plone 3 Theming, a new book by Veda Williams. Although not presently working in Plone, I like to keep up with the Plone ecosystem. Should I find myself working on a new CMS, Plone will be one of my preferred technologies, so I need to nourish what few Plone neurons I’ve got.
I bump into Veda at Seattle Plone Gathering meetings. I wouldn’t say we’re friends, but we are friendly.
BTW, the book has an online errata list.
Buy this book if you’re working on any aspect of developing a Plone-based site. Even if you aren’t doing theming work, its informational goodies will come in handy. It’s written for the newbie-to-intermediate level, but I’ll wager that even advanced Plone site developers will learn a thing or two from this book.
Yesterday’s World Plone Day in Seattle was interesting, and helped me think about a few matters.
Fifteen – 20 people were physically present, with another 10 watching via Brian Gershon‘s ustream.tv wizardry. (It was lower quality than a separate camcorder recording, due to a ustream.tv bug.) After Jon Stahl‘s introduction, Andrew Burkhalter, David Glick, and Cris Ewing previewed new Plone 4 technologies. Their talks rocked.
As I listened, I thought about what Fisher Communications lost when they killed their Internet division, which included shuttering our Plone project. I’m sad about the opportunity that Fisher walked away from, and the effects of inept management.
Idealware has published a report comparing four open-source CMSs. Its title: Comparing Open Source Content Management Systems: WordPress, Joomla, Drupal and Plone. (Is that a straightforward title, or what? Heh.) I read about it in a few blogs I follow.
Idealware's OSS CMS summary
If you’re interested in CMSs, I recommend this report. Here are some quotes to whet your appetite…
If you’re thinking of giving a talk at Open Source Bridge 2009, you’d better hurry up and submit your proposal. Their submissions deadline is March 31!
At last count, they have 33 submissions on topics including Linux kernel development, Drupal, OSS project maintenance, Ruby, and Plone.
I’ve been working on getting the word out at UW’s Computer Science department. Through friends there, I got connected with undergraduate students doing open-source related research, like Scott Shawcroft. Scott put me in touch with Justine Sherry, the UW ACM student chapter’s vice-chair. I’m hoping we’ll some involvement from their CS student population, either for giving talks or attending the conference.
Yesterday was Northwest Python Day. All of the talks were great, and the day was immensely rewarding and enjoyable.
Andrew introduced me to Andy McKay, with whom I’ve traded a bit of e-mail but never met. It’s an oddity of today’s world that you can do business, or strike up a friendship via a few e-mail exchanges, with someone, without ever having actually met them.
Most of the attendees brought some food, and most of them brought breakfast food, and most of the breakfast food were doughnuts. We were swimming in doughnuts! Boy oh boy, there were a lot of doughnuts.
I’m working on my plans for attending PyCon 2009. I don’t know whether to budget for the sprints — I’d stay for them if I could contribute to at least one. But, no sprints are listed yet…
If you’re considering organizing a Plone-related sprint, I’d like to hear from you, even if you’re not yet 100% sure. Or, write about it on your blog, so we can all hear about it. Or, propose a sprint so that it gets listed on the PyCon 2009 sprints page.
There’s just one small hiccup standing between me and my new blog list duties. Today might be the day!
Update @ 1/23: Alex Clark waved his magic wand, and I’m in! I closed three tickets today for new blog listings! Yee haw!
Gerry Kirk asked for volunteers to take over as the maintainer of Planet Plone’s blog list. I raised my hand, and Gerry quickly said, “Huzzah! We have a winner!”
I’m the new zookeeper. It seems like an easy job. And, a way to start contributing (in a teensy-weensy capacity) to the Plone community.
Tonight, I have, alas, a small problem with my ssh keys. Tomorrow, I should launch the “DeRosa era of zookeeping” by processing existing requests for additions to the blog list.
I’m doing some theming work on my team’s first Plone-based site. It’s the first real (i.e., useful, concrete, for-my-job) Plone work I’ve done.
For the first time, just now, I knew how to find a viewlet’s linkages and guts. Without thinking, I went looking for the
common.py files… I’m starting to know what I’m doing!
Most of the technical people in my division (Fisher Interactive) use Apple Macs. They’re all MacBook Pros, except for a Mac Pro used by Andrew.
I sometimes listen to music via iTunes when I work. I’ve rediscovered classical music, so my library has some of that (e.g., a London Symphony performance of Holst’s The Planets, a Boston Symphony performance of Carmina Burana), and more contemporary favorites (e.g., Yes, Traffic, B-52s, Poco, Nektar, and Dave Mason). I shared out my iTunes library — I’m hoping that others bring in their favorite music, and we build a shared library network at work…
Anyway. On a whim, I bought the only two albums (For Beginner Piano and Plock) made by the group Plone, from which the Plone CMS got its name. I plugged in my Bose headphones, cranked up the volume, started the Plone playlist, and began on a CSS task.
I found Plone’s music to be… Different. It was like nothing I expected. It’s… Unusual.
Andrew says it’s good music to code to. Um… Maybe. I don’t think it’ll ever replace Yes, Traffic, or Lou Reed.
Updated 1/10: I replaced the last sentence with one a little less impudent.