背景说明：

O'Reilly Network

知名IT出版和媒体商，大家应该都读过他们出的计算机书吧...

COMDEX

美国最大的IT展览盛会，每年(或者每两年)举办一次

采访原因

Plone如选O'Reilly Network在去年COMDEX会议上举办的开源产品宣讲, 并且超过其他著名的开源项目，如Eclipse, OpenOffice, KDE and Gnome，获得第一名

采访文章

在这里

采访内容：

为什么要启动plone项目？

(概要，Zope和CMF都是非常cool的东西，但是界面不好，疏远了用户；Plone项目启动，就是要亲近最终用户的)

Limi: Zope was lacking a good-looking, functional piece of UI software - the technology was very good, but no consistent, approachable products existed (IMHO, of course). People were struggling with very basic concepts when they started with Zope, something they shouldn't have to do.

The itch was customer projects that required content management and we were tired of doing the same things over and over again. Classic tale, really.

Runyan: Zope's CMF (Content Management Framework) was a pretty interesting piece of software, like most Zope software, but it lacked a functional interface. It was made for people to customize, but most opensource developers don't care about looks only about functionality. So we started off making a skin on top of the CMF. Shortly after doing work we realized that we would need to add lots of functionality to CMF because it had many short-comings; after all it is a framework not a product. Basically, Plone and the CMF attempts to address some issues Zope has had for years.

Limi: It provides workflow, Dublin Core metadata, etc.

Runyan: ...How to re-use and customize services.

Limi: ...Component architecture.

Runyan: So, until CMF there was no structure/policy for products to communicate with each other.

OSDir: So, Plone works on top of Zope's CMF and makes Zope easier to work with?

Runyan: Exactly - by providing higher level services to developers. So, we sort of started out making a customization of the CMF - but realized for usability's sake that it lacked quite a few things. Zope was the Wild West of Object Persistence and Publishing before the CMF.

内容管理Content Management，这个词被赋予了太多的含义，是应该比较含糊的词，在Plone中，你怎么看内容管理的

(内容管理是在计算机系统中对内容整个生命周期的管理、创建的过程，使用一组工具完成，其中一个工具是网站的内容管理（CMS），这一块是Plone完成。)

Runyan: Great question. I see CM as the process of managing, creating, and lifecycling content throughout a computer system. Managing is composed of tools. One of those tools that's inherent with a Web Content Management System (CMS) is the web interface. This is where Plone started.

（Plone最初是想用来做内部应用的，但是很快就扩展导网站发布和门户服务了。）

Limi: The initial use case that drove Plone was intranet applications - but it quickly extended to web publishing and portal services too. Steve: So, Plone is used by normal people managing web content and by developers to get at the inner workings of Zope and the Zope CMF.

Limi: We do all the boring stuff you hate doing.

Plone位于投票的首位，而不是PHP-Nuke，或者Cocoon，人们为什么要选择基于zope的plone系统，你能说一下原因吗？

(Plone面向最终用户;Coccon着力一个开发框架;PHP-Nuke则是开发人员关心的，他使得人们能够插入很多模块，建立一个混合的PHP－Nuke网站。对我们的来说，Cocoon太底层，而PHP-Nuke则太不底层。)

Runyan: Plone has focused a lot of attention towards end-user experience. Cocoon (the last time I looked) was focusing on framework concerns. PHP-Nuke (the last time I looked) was focusing on developer concerns; enabling people to plug-in a few modules together to get a hybrid PHP-Nuke site. Cocoon is too generic and PHP-Nuke is not generic enough for our needs.

（Plone同时也试图建立一个通用的web用户界面，就像大名鼎鼎的wxWindows或者QT一样。这样使得能够使得一直的、可用的界面。大多数开发人员希望我们能够有现成的很好的UI策略，这样他们就不必太担心了）

Limi: Plone also tries to create a generic web UI (kind of like wxWindows or QT) that makes it easy to generate consistent, usable UI in browser format. Most developers are very happy that we have good UI policies in place, so they don't have to worry about that.

（我们社区中开发人员，大多数是从Java迁移过来，他们希望获得一个通往成功的快速路径。Plone着眼于开发人员所关心的哪些东西。大多数人不希望在去写一个注册和登录的系统。到目前为止，我们很少有从PHP世界中迁移过来的开发人员，可能因为他们的目标不同吧）

Runyan: Almost all developers (immigrants) we get are Java developers who are wanting a quick path to victory. Plone addresses quite a bit of the concerns that most developers have. When I say Plone I mean Plone and its technology stack (CMF/Zope/Python). Most people don't want to write "yet another registration system". Up until now, we've have very few immigrants from the PHP world, mostly because their goals are very different.

（java太罗嗦了，太复杂了）

Limi: We're kind of the middle ground, where you want sound design decisions software-wise and not just a collection of scripts - but think Java is a bit too verbose and cumbersome to work with.

（Plone很容易定制）

Runyan: CMF comes with registration components (and lots of other components) that are easily swapped out (if you need to). And Plone puts the gloss on the components so that people can keep a nice UI on their customizations.

去年你和开发人员都干了些什么呢？

(优化和交流)

Runyan: Lots of polish and mind share.

（构建社区）

Limi: And community building.

太多了，大家自己看吧...