Model of Proposal:

An IPD should include:

Summary - Two or three sentences summarizing the proposal.

Motivation - A statement on why the MetaDoosh Community should implement the proposal.

Justification - an explanation of how the proposal aligns with the MetaDoosh community's mission and guiding values.

Terms (optional) - definitions of any term within the proposal that is unique to the proposal, new to the APE community, and/or industry specific.

Specification - a detailed breakdown of the platforms and technologies that will be used.

Steps to implement - the steps to implement the proposal, including associated costs, labor, and other resources for each step where applicable.

Timeline - relevant time details including but not limited to start date, milestones, and end dates.

General cost – the total cost to implement the proposal.

The author can add additional fields to any template if necessary to fully communicate the intentions, details, and implications of the AIP Draft.

Proposals that did not go through the respective approval process and are resubmitted should also include:

• Link to the original proposal

• The reason it was not approved.

• Changes that have been made and why it should be approved now

• The author can add additional fields to any template if necessary to fully communicate the changes made and the intentions, details, and implications of the forwarded IPM Draft.

• Idea

• Draft

• Analysis

• Moderation

• Label

• Administrative review

• Final IPD

• Implementation