Zope

IBM's Model M keyboard is a classic.

Translation files for Plone

System Administration and Site Management for BlueBream

Now that the ZODB book is on the planning stages and writing will start soon, it's a good time to think about what tools will be used for writing it.I propose to use Sphinx to generate the documentation. The text will probably be stored in a ... [More] Subversion repository, which could be svn.zope.org, for example. All of the book code will also live in a repository. I'm not opposed to the use of Github or Bitbucket if most people think that's the way to go, but personally I find I can get by with the above mentioned tools.After we have at least a couple of chapters in a presentable state, the documentation could be automatically generated every day, so we can start to have a (slightly) useful resource well before the book is finished. We might be able to give the book a home like book.zodb.org or something.Right now I'm not sure about whether we should use a wiki or an issue tracker, but it's something that could become useful if more people participate as voluntary reviewers of the book.Well, this is how I see the writing process at the moment. Am I missing something? Do you have any ideas or suggestions? I'm willing to consider other options if that would get more people participating in the process. [Less]

This is a Zope PAS plugin that authenticates users against a CAS (Central Authentication Service) server.

On a new versioning approach for Zope-based applications

We have received an encouraging amount of participation from the community. There are two ways to participate, writing blog entries or financial contributions. I have already been in contact with Adam Groszer and Matthias(Nitro) by adding them to ... [More] the blog. Hopefully we will see some articles from these two guys in the near term. Anyone is welcome to post a mini-howto, recipe or just their experience with the ZODB. All material is welcome. Financial contributions will fund Carlos to focus to develop the book to completion. We currently have the first round of money to get an advance to Carlos. We need significantly more money to finish the book. All donors will be listed on the blog. I have put the first batch of donors on the widget. This will be updated occasionally as we get more contributions.If you have either money or experience with ZODB -- you can participate. Contact me. All those who have contributed - thank you. [Less]

Update: to avoid continuous posting and reposting of the outline, we have created a page where the latest version will always be available. A link to this page is located in the top right portlet on this blog.At the start of this project we posted a ... [More] suggested outline, but while the research phase is going on, the book structure will likely undergo several changes. Please remember that on this phase your comments and suggestions are specially valuable and can be more influential on the final result. We really look forward to getting more comments and ideas.Right now the outline I propose for the book is the following (thanks to Shane Hathaway for his input on this):Part one: getting started. This part will have an emphasis on getting an application up and running while making simple use of the ZODB. A developer who just needs to add a simple persistent layer to his application might have enough with this.Introduction to ZODB.This will be a very short chapter, just to get things going. What is the ZODB. Maybe some bits about the NoSQL craze, how the ZODB has been doing that for more than 10 years. Why is the ZODB a nice tool to keep in your Python developer's arsenal and when is it a good fit for your apps?Your first ZODB application.Installation and running the first app. The objective of this chapter is to let the reader do something that works immediately. Just the basics to get an app running. Not a lot of details here.Transactions.The ZODB depends on the transaction package and understanding this package is very important to working effectively with it. This chapter introduces transactions, shows what happens when you commit or abort, describes what a conflict error is and explains why it's a good idea to avoid long running transactions.A more complex application.A bit more involved explanation of how the ZODB works and a more useful sample application. This chapter will build on our understanding of transactions.Basic indexing and searching.The Catalog and indexes. I propose to use repoze.catalog here, which uses zope.index.Maintenance.Packing, backups, etc.Scaling.The ZODB cache, ZEO and replication services.Part two - advanced topics. This will be a more in-depth review of techniques and concepts for ZODB development.A more in-depth look at the ZODB internals.A little more information about how the ZODB works. At least enough stuff to understand the later chapters about storages and debugging.Advanced transaction management. How to create data managers for working with other storages in the same transaction, how to best approach the need for well behaved, long running transactions.ZODB Storages.Details about the FS storage and discussion of RelStorage and maybe DirectoryStorage.Popular third party packages.Some of the most important packages for the ZODB will be described here.Other indexing and searching strategies.Other catalog implementations, third party indexes and using external indexing solutions, like Solr.Advanced ZODB.Evolving schemas, creating custom indexes, using ZODB in an asynchronous framework like twisted.The debugging FAQ: frequent problems and suggested solutions.General debugging strategies and then a FAQ with common problems. For example, common traps like attempting to load an object state when the connection is closedPart three - ZODB APIThe official public API will be documented here. This could serve as a really quick reference for developers. We might include APIs for some other modules, like transaction. [Less]