• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 5. The Zope 3 Development Process > From Idea to Implementation

From Idea to Implementation

With a big software project, it is necessary to have some sort of formal process that controls the development. Such a process stops developers from hacking and checking in half-baked code, and this requires a lot of discipline among free software developers because they generally don't receive any compensation. The developers of Zope 3 tried to implement a flexible process that can be adjusted to the task at hand.

When a developer has an idea about a desired feature, he or she usually presents the idea on the Zope 3 developer's mailing list or on IRC. The developer can figure out whether his or her feature already exists and whether the task the feature seeks to complete can be accomplished otherwise. If the idea is a good one, then one of the core Zope developers usually suggests that the submitter write a formal proposal that will be available in the Zope 3 Proposals Wiki. After the developer has written a proposal, he or she announces it to the mailing list for discussion. Comments to the proposals are usually made via email or directly as comments on the Wiki page. The discussion often requires changes to be made to the proposal through adjustment of the design or thinking of further use-cases. After a draft is approved by the other developers—silence is consent, though Jim Fulton normally likes to have the last say—it can be implemented. Although the developers of Zope 3 tried hard not to make the proposal writer the implementer, it works out that the proposal writer almost always has to implement his or her proposal.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint