The states of a proposal
| State | Meaning |
|---|---|
| received | sent in, address not yet confirmed; deleted after 7 days if it stays so |
| confirmed | the address was confirmed, or the sender was signed in; waits for review |
| reviewing | the team has opened it |
| admitted | accepted, not yet in the catalogue |
| published | in the catalogue under the submitter's name |
| rejected | declined, with the reason |
| withdrawn | taken back by the submitter while it was open |
Who decides what
- Admit, hold, reject: a reviewer or the owner, always with a reason of at least three characters. The reason goes to the submitter by mail.
- Publish: the owner alone. Admit and publish is one step for the owner, so a published module appears at once.
- Take back: the owner alone. The module leaves the catalogue and returns to admitted; its points and contributor list go with it.
- Withdraw: the submitter, as long as the proposal is open.
The gate before publishing
Publishing runs a set of checks and refuses if one fails: the submitter has a name, the submitter is a contributor, the record trail attached to the proposal verifies, area and title are set, the summary is there, and file links are well formed. The console shows the list, and the status page of the proposal shows the same.
What publishing does
- Writes the module into the catalogue file, which lives in the code repository.
- Adds a line to the record trail with the owner's account number and the reason.
- Makes the submitter the first contributor of the module.
- Mails the submitter.