QuantEcon Enhancement Proposals (QEPs)

Contents

QuantEcon Enhancement Proposals (QEPs)#

QEPs document decisions that affect multiple repositories or how the QuantEcon team operates — label conventions, editorial policy, tooling standards, licensing, and similar cross-cutting choices. Each QEP records what was decided, when, and why, so the reasoning behind an organisation-wide convention is easy to find later.

Routine, single-repository work does not need a QEP — the process is for choices that reach across the project.

The proposals and the process that governs them live at:

quantecon.github.io/qeps (source: QuantEcon/qeps)

How it works#

The workflow has four stages, defined formally in QEP-1:

  1. Discussion — open an issue to check whether a QEP is actually needed.

  2. Drafting — write the proposal from the template, marked Status: Draft, and open a pull request.

  3. Comment period — announce the PR and leave a 1–2 week window for review.

  4. Resolution — the Core Maintainers reach a decision by lazy consensus and merge the PR with the outcome recorded (Accepted, Rejected, or Withdrawn).

Tip

Anyone in the community can propose a QEP; the Core Maintainers make the final decision at the end of the comment period.

See also

For the proposal template, the full process (QEP-1), and the index of accepted proposals, see quantecon.github.io/qeps.

Contents