Pegasus Enhancement Proposal (PEP)

PEP#: XXX <Number assigned at submission time It is the submitters responsibility to pick the next available number from the PEP web page>

PEP Type: <The type of this PEP - Concept / Functional / Release / Procedural>

Title: Title <Short title for the proposal>

Status:  draft <state of this PEP: draft, accepted, rejected, withdrawn, deferred. Initial state is always "draft">

 Version History:

Version Date Author Change Description
1.0 dd mmm yyyy   Initial Submission
       

 

Abstract: <short abstract of the proposal>

<Body of the proposal. The proposed format is as follows (blue <> enclosed comments are helpers to PEP writers and should be removed.>

Definition of the Problem

< What is this change/enhancement trying to solve?>

Proposed Solution

<This is the meat of any PEP. This section should describe the objectives, and characteristics of the enhancement. The definition of the project should be detailed enough to allow adequate discussion and review of the proposal. The objective is to provide a project management and architecture level of information, so that the steering committee and architecture team reviews and approvals can be accomplished.>

Rationale

<The rationale fleshes out the specification by describing what motivated the proposal and why particular design decisions were made. It should describe alternate designs that were considered and related work that might help reviewers understand the solution.>

Schedule

<Proposed schedule for implementation>

Discussion

<Additional information from discussions,  reviews, and decisions of the steering committee and architecture team can be recorded here. Information in this section is to help reviewers but MUST also be reflected in the Proposed Solution / Rationale, etc. sections. This section is for information only during the review process.>

<Add your copyright here>

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Template last modified: February 17th 2009 by Martin Kirk
Template version: 1.15