BlueBream
 |
The topic of this article may not meet Wikipedia's general notability guideline. Please help to establish notability by adding reliable, secondary sources about the topic. If notability cannot be established, the article is likely to be merged, redirected, or deleted. (March 2010) |
BlueBream is a rewrite by the Zope developers of the Zope web application server. It was created under the name "Zope 3", but the existence of two incompatible frameworks with the same name caused much confusion, and Zope 3 was renamed "BlueBream" in January 2010.[1][2] BlueBream is distributed under the terms of the Zope Public License[3] and is thus free software.
Contents |
[edit] History
The Zope 3 project started in February 2001 as an effort to develop a new version of Zope as an almost complete rewrite, with the goal to retain the successful features of Zope 2 while trying to fix some of its shortcomings. The goal was to create a more developer-friendly and flexible platform for programming web applications than Zope 2 is. The project began with the development of a component architecture, which allows the structuring of code into small, composable units with introspectable interfaces. The interfaces are supported by an interface package in order to provide the functionality of explicitly declared interfaces to the Python language. The first production release of the software, Zope X3, was released on November 6, 2004. In January 2010 Zope 3 was renamed BlueBream.[1]
[edit] 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 sprints for open source software development.[4] 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 in active development and is now considered a stable framework, used on production projects worldwide, most notably Launchpad.
[edit] External links
[edit] References
- ^ a b http://bluebream.zope.org/doc/1.0/introduction.html#overview
- ^ http://foundation.zope.org/minutes/zfbod-minutes-20100114
- ^ "FAQ - General 5: What is the license of Zope 3?". http://wiki.zope.org/zope3/FAQGeneral#what-is-the-license-of-zope-3. "Zope 3 is licensed under Zope Public License, Version 2.1 (ZPL)."
- ^ http://wiki.zope.org/zope3/SprintSchedule
