Proposal: Proposals as a tracker

Status: Open. The status part has an approved design; see its own page.

Parts: Status for proposals · Pull requests and sub-proposals

Pull requests: None yet.

What changes

Proposals become the place where every change to Agpedia is described, discussed and followed until it is live: policy changes as today, and also changes to the software that readers or contributors will notice. Each proposal says where it stands, which pull requests implement it, and which larger proposal it belongs to.

Why

Today a software change is discussed in a pull request on GitHub or in a private document, and a policy change on a proposal page. Contributors cannot see in one place what is planned, what was decided and what has shipped. Putting both on Agpedia keeps the discussion where the community is, and gives every change a page that release notes on the blog can link to.

How it works

• One proposal for every change that people will notice. A large change gets a main proposal with smaller sub-proposals under it, each of which can be decided and built on its own.
• Changes that nobody can see, such as internal fixes, do not need a proposal.
• The two parts are described separately: Status for proposals and Pull requests and sub-proposals.
• Later, the same pages can hold other kinds of items, such as bug reports, without changing how proposals work.