Editing Zope (section)

====Technology====
The goal of the project was to enable programmers to use Zope in order to expose arbitrary Python objects as model objects to the web without the need to make these objects fulfill particular behavior requirements. In Zope 2 there had been many behavior requirements to allow objects to participate in the framework, which resulted in a large amount of [[mixin]] base classes and special attributes. BlueBream uses a model/view architecture, separating the presentation code from the problem domain code. Views and models are linked together by the component architecture.

The libraries underlying BlueBream have been evolving into a collection of useful libraries for web application development rather than a single, monolithic application server. BlueBream includes separate packages for interfaces, component architecture, HTTP server, publisher, Zope Object Database (ZODB), Zope Page Templates, [[I18N]], security policy, and so on. The component architecture is used to glue these together. The component architecture is configured using a ZCML (Zope Configuration Markup Language), an XML based configuration file language.

The Zope 3 project pioneered the practice of [[code sprint|sprints]] for [[open source software]] development.<ref name="sprints">{{cite web|url=http://wiki.zope.org/zope3/SprintSchedule |title=Zope 3 wiki SprintSchedule |access-date=August 17, 2012 |url-status=dead |archive-url=https://web.archive.org/web/20120814030504/http://wiki.zope.org/zope3/SprintSchedule |archive-date=August 14, 2012 }}</ref> Sprints are intensive development sessions when programmers, often from different countries, gather in one room and work together for a couple of days or even several weeks. During the sprints various practices drawn from [[agile software development]] are used, such as [[pair programming]] and [[test-driven development]]. Besides the goal of developing software, sprints are also useful for geographically separated developers to meet in person and attracting new people to the project. They also serve as a way for the participants to learn from each other.

BlueBream is considered a stable framework, used on production projects worldwide, most notably [[Launchpad (website)|Launchpad]].