The Definitive Guide to Plone

MAY 2004-I'm on a flight to Las Vegas, Nevada, to announce at CA World 2004 the formation of the nonprofit Plone Foundation. Whilst on the plane, I'm also writing this foreword for the book-something I'm excited to see released as open source. Both are pieces in the bigger jigsaw puzzle of Plone, and I'm thrilled to see the holes in the puzzle being filled. Over the past two weeks, the focus of the Plone community has moved from purely technical to much more unfamiliar territory: marketing. The Las Vegas trip will end with Computer Associates announcing that it's sponsoring the Plone Foundation. Allofthis will happen about three years after Alexander Limi and I first released what would become Plone. As Bill Hicks once said, "e;Who woulda thunk it?"e; In May 2001, the startup company that I was the second employee at grew from 3 people to 160 people and then submerged under top heaviness, in both the development cyde (J2EE on every project) and the increasingly large management. I saw the handwriting on the wall. During the death throes, I practiced Python. I had been using Zope on our intranet and was fascinated by the software for several years (since International Python Conference 8). I thought Python was the onlyway I could accomplish the projects I was going to take on in my new life as a consultant.