Lemonfiber

Propose a change

Say what it should do.

A proposal is a pull request adding one file to the specification, with no identifier: a maintainer's approval allocates them. Fill this in, check the file it makes, and open it on GitHub, where you commit it under your own account and open the pull request.

What it is

A short phrase naming the capability.

A feature's identifier, like B3, or a page's path, like 20-architecture/overview.md. A gap names the one that is silent.

What does not work today, and for whom.

One statement a line, each using MUST, SHOULD or MAY: The dashboard MUST show each service's state.

Why this, and what was considered instead.

The file it makes

---
kind: proposal
area: 
title: 
status: draft
---

# 

## Problem

(none given)

## Proposed behaviour


## Rationale

(none given)

Before it can be opened

  • Choose the area it belongs to.
  • Give it a title: one line naming the capability.
  • Write at least one statement, and use MUST, SHOULD or MAY in each.

Nothing you type here leaves your browser until you open it on GitHub, which receives the file in the address.