Phase: Elaboration

See ProcessOverview for a description of the process I'm going to be following as I develop this project.

Management

• Phase goal: Plan development.
• Iteration goal: Further refine the vision and architecture. This may be the final iteration in the elaboration phase, depending on the feedback I get as this is released to more people.
• Artifacts: Business Case | Software Development Plan | Vision | Work Breakdown Structure | Status

By the end of this iteration, I'd like to be using peppy to edit all my own source code, not just Python, so this will iteration be focused on extensibility.

Environment

• Phase goal: Install development environment and change management database.

The Trac process is documented in Software Development Plan, and I've used it successfully in Iteration 5 and Iteration 6. Further enhancements to the environment are possible. Given the success of the svn hooks that link svn checkins to trac ticket tracking, I'm on the lookout for further Trac plugins. Given the quantity of Trac spam that I acquired starting in May 2007, I had to turn off anonymous posting and submission of tickets. I would like some simple means of allowing anonymous ticket posting, perhaps using captchas (which I don't like) or solving some simple arithmetic problem (which I do like).

Requirements

• Phase goal: Define architecture objectives.
• Artifacts: Use Cases | Release Specifications | Vision

The primary goal of this release is to extend the functionality of the editor, as I would like to be using the editor as the primary editor for my all own code, not just python code, by the end of the release.

I hope to get contributions for other major modes that I don't use regularly. The only modes in emacs that I really use regularly are Python, C/C++, bash, Makefile, ChangeLog and HexEdit, so I expect that other people would be better at developing major modes for other languages than I would. I hope that the framework will be inviting enough, easy to use, and hide enough of the low level details, that other people will contribute.

See the roadmap for a complete list of current requirements, or the individual milestones for requirements for each release:

• release 0.7.0 requirements
• release 0.7.1 requirements

Design

• Phase goal: Describe architecture baseline.
• Artifacts: Design Models | Test Models | Architecture Description

The 0.7.0 release will be a quick turnaround from 0.6.x, with the goal of cleaning up the documentation so that it's easy to see how to add new major modes, minor modes, and actions. I probably won't document the internals quite as much, because this first release in iteration 7 will focus on the big features that peppy can provide.

Implementation

• Phase goal: Produce architecture baseline.

See the roadmap for the current status of the implementation.

Assessment

• Phase goal: Assess architecture.
• Artifacts: Release Specifications | User Manual

Deployment

• Phase goal: Define user manual.
• Artifacts: Executables | User Manual | Developer's Guide

Milestone

Milestones are available at the roadmap.