<Y
Y>

Snowsprint report:

This year, like last year, will be a year of Grok for me. Grok has given me real hope that Zope technologies can compete, and compete well, with other Python-based web frameworks. In the Zope community, as well as outside it, we are well aware of Zope's flaws, both technology and community-wise. We sometimes think too little about Zope's assets, which are huge. Zope 3 is great technology, years ahead of the competition in the pluggability department, and Zope's community is well established. One of those things in the Zope community is the yearly Snow Sprint. This year was the first time I attended.

[More]

[Comments] (11) On Revolution and Evolution:

Malthe started an interesting discussion on the possibility to rewrite Plone from scratch. I have some thoughts on the topic of rewrites, evolution and revolution. Here are some of my scattered observations.

[More]

[Comments] (6) Allowing Zope 2 applications to contain Zope 3 content:

Five, the system to use Zope 3 within Zope 2, is a pain sometimes. Five is full of hacks to ensure backwards compatibility with Zope 2. This stops developers from using full-fledged Zope 3 strategies in places.

[More]

[Comments] (5) Python 3.0 is incompatible with Python 2.0:

Jesse Noller wrote:

I hate slashdot: Python 3000 is incompatible?!!!
[More]

[Comments] (3) Going to FOSDEM:

This weekend I'm off to FOSDEM, a large free software/open source event in Brussels. For years I intended to go but for years I didn't make it. But this weekend I'll be there, taking the train later today!

[More]

Summer of Code for Zope:

Last year the Zope Foundation participated in the Google Summer of Code. We had four students, all of whom are still active in the Zope community, so we can declare this a success. We hope to participate in 2008 again, and we're looking for mentors and project ideas.

[More]

[Comments] (4) Please don't break library compatibility in Python 3:

Update: Guido appears to share my opinion on this.

[More]

Grokkerdam sprint!:

It was planned for a long time, but at last we are going to hold a Grok sprint in the Netherlands. To be more precise, in Rotterdam. Rotterdam will be "Grokkerdam" for the duration of the sprint!

[More]

Zope Foundation accepted in the Summer of Code:

The Zope Foundation is happy to announce it was accepted in Google's Summer of Code program in 2008!

[More]

Zope Foundation accepting student applications in the Google Summer of Code:

Are you a student and are you interested to hack on Zope, the ZODB or Grok for the summer? Do you want to be helped by an expert mentor? And get money and a t-shirt? The Zope Foundation is participating in the Google Summer of Code for the second time this year, and the time for you to apply is now! The applications just opened yesterday, but deadline for student applications is monday, march 31, so there isn't a lot of time. We're really excited to be part of this program again, and we hope we get many good student applications.

[More]

[Comments] (6) Explicit is better than implicit, and what it means for Grok:

[More]

[Comments] (11) No, you are smart enough for Zope:

This blog entry on picking web frameworks is quite interesting. It doesn't give a lot of detail, and it acknowledges this, but it does show the struggles someone goes through trying to pick the right framework for the job (and one that fits his mind). Wyatt Baldwin considered, among other frameworks, Zope, and had the following to say:

I was having a hard time with the Pylons docs, and so I ended screwing around with Grok (which actually looks fairly interesting) and even took a look at the Zope 3 site. I’m sure Zope is really awesome or whatever, but it might as well suck. Every time I look at that site, I’m just like “WTF! This shit has been around for like five years!” Anyway, I might just not be smart enough for Zope.
[More]

[Comments] (15) SQLAlchemy with Grok:

Grok needs a great relational database integration story. Grok already has a great database story: by default, we use an object database: the ZODB. The ZODB is great as you can just store normal Python objects. You can persist complicated nested structures easily. But this entry isn't about the ZODB. Relational databases are also great. You can query tables every which way very easily. You can manage your data in a RDMS, a familiar system for many, and integrate with existing RDMS that already exist in many places.

[More]

[Comments] (3) Grokkerdam sprint topics:

The Grokkerdam sprint is coming up in a few weeks. I've put some topics people may want to work on during the sprint on the wiki page. Since those topics are just one-liners, I figured I might expand a bit on them here. The sprinters are not required to pick these tasks of course, and can choose something else entirely. If you have ideas, pleases expand the list of tasks!

[More]

[Comments] (15) Local European PyCons and EuroPython:

There is a PyCon UK. There is a PyCon Italy. Just now I saw the announcement of a PyCon France. I understand why these conferences happen - local user communities will want to see conferences where most talks are in their own language and have a bigger selection of talks relevant to the local community.

[More]

[Comments] (12) Porting Zope to different Pythons:

Zope has been under development since 1996. It wasn't called Zope back then yet: it was called bobo, and later pieces were called Principia, and only in 1998 did it become Zope.

[More]

Grok security: more Grokkerdam sprint topics:

In my previous article on the Grokkerdam sprint, I discussed various topics people may want to work on during the sprint. This blog entry is dedicated to some more topics, all security-related.

[Comments] (6) Grok takes Zope 3 the rest of the way:

My friend Lennart's blog entry Zope 3 rocks and rolls is fascinating, not least as it has one of the most misleading titles I've ever seen. Reading that title, you'd be surprised Lennart talks mostly about a series of difficulties encountered with Zope 3 and decision to switch to Plone for a project instead.

[More]

Zope Foundation in the Google Summer of Code:

The Zope Foundation is very happy to announce it has five projects accepted by the Google Summer of Code. Thank you Google! In this article, I will introduce the projects, students and mentors.

[More]

Grok 0.12 released!:

It happened a few days already, but I hadn't mentioned it here yet: Grok 0.12 has been released! Thanks go to Jan-Wijbrand Kolman for again playing the role of release manager, and to all contributors that made this release possible!

[More]

[Comments] (28) In Memoriam Joachim Schmitz:

This is a rather unusual blog entry. I sincerely hope I don't have to write blog entries like this very often. I usually write about technology, and the community surrounding it. This community is, of course, composed of people. Yesterday I heard that Joachim Schmitz, long-standing member of the Zope and Python communities, had died suddenly last weekend. He was a regular presence at Zope-related events, and I have met him often. I feel that his passing should not go without notice for people in our community who knew him and met him.

[More]

[Comments] (4) Grok Status Update Part 1:

Time for a Grok status report. I thought the Grokkerdam sprint was very successful. It is now a few weeks behind us. A fun time was had by the participants and we got a lot of work done. What's more we've had followup on many of the projects started there - people have continued the work started at the sprint.

[More]

Grok Status Update Part 2:

I continue yesterday's status update with some more topics. Lots of stuff is going on in the Grok world!

[More]

[Comments] (3) Grok Status Update part 3:

Lots more is going on in the Grok world, so the Grok Status Update has received a part 3. See also part 1 and part 2.

[More]

[Comments] (5) A misconception about the ZODB:

The ZODB is a powerful object database for Python objects. It's very mature - it's been around for more than a decade. It is transactional, has advanced features like clustering (ZEO), blob support, and yes, it can be used independently from Zope. Zope 2, Zope 3 and Grok all use the ZODB as its default data storage, and it's seen a lot of battle testing.

[More]

[Comments] (5) Grok 0.13 released!:

Grok 0.13 was released yesterday. Grok, of course, is the powerful web application development framework. See the details in the release notes here:

[More]

[Comments] (14) Zope's entry into the commit count pissing match:

Mark Ramm-Christensen of the TurboGears project starts what looks like it will be a great commit count pissing match . I know that wasn't his intent. He just wanted to show the TurboGears project is active. But nevertheless, this kind of thing tends to get rather silly rather quickly, so we certainly can't leave Zope out!

[More]

[Comments] (1) Post-EuroPython Grok sprint report:

This is a report on the Grok sprint that followed EuroPython. Thanks to the EuroPython organizers for giving us the space!

[More]

[Comments] (3) megrok.rdf finally checked in:

Jasper Op de Coul and I worked on megrok.rdf during the post-europython Grok sprint a few weeks ago. We had a few logistical problems concerning access to svn.zope.org, but yesterday Jasper finally managed to check in megrok.rdf:

[More]

[Comments] (16) What Zope can learn from Zope:

So we've had what Django can learn from Zope, what Zope can learn from Mozilla, and a few years ago already we had what Zope can learn from Ruby on Rails. (and www.zope.org still sucks, but grok.zope.org and repoze.org don't)

[More]

[Comments] (3) Grok's release mill:

It already happened last week, but I thought I'd mention our Grok 0.14 release. Grok 0.14 is the first release of Grok that officially works with Python 2.5, though unofficially Grok has worked with Python 2.5 for a while on many platforms. There is already a report of Grok working with Python 2.6!

[More]

[Comments] (1) Happy Second Birthday Grok!:

Grok the codebase is 2 years old this week. Two years ago we had the first Grok sprint in Halle, Germany, at the Gocept offices. A lot has happened since then. For me personally Grok is my development workhorse now and has been since early 2007. It's something I use during development every day.

[More]

[Comments] (6) Why I think Grok can make Plone easier:

Let me start off by saying that I'm not a Plone developer. I've got a lot of experience with Zope 2 development though, and I keep an eye on the Plone community. I hope the Plone developers will not mind a relative outsider's observations and suggestions.

[More]

[Comments] (5) Grok tech in Plone continued:

In my previous blog entry I tried to make the case for Plone adopting Grok technology. I gave some background on Grok and talked about some of the pain points that I think Plone has and that Grok has been trying to tackle. My goal was to explain where Grok is coming from, and why it's a good fit for Plone.

[More]

[Comments] (17) I like doctests:

It seems to be a recent trend to point out things you don't like about doctests. There are two articles by Andrew (? - see update below) and one by Ned Batchelder. There's also one by Marius Gedminas.

[More]

[Comments] (1) The Ghost of Packaging Past and Future:

There has been a recent discussion on how packaging of Python libraries should be done. As frequently happens, the Zope community sometimes encounters problems before many other communities do, and I think we have an example of that here.

[More]

<Y
Y>

[Main]

Unless otherwise noted, all content licensed by Martijn Faassen
under a Creative Commons License.