Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

make the TIP adoption process more predictable and understandable #359

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

make the TIP adoption process more predictable and understandable #359

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 17 additions & 3 deletions src/standard/workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,22 @@ Each TIP should have the following parts (which are heavily copy-pasted from BIP
- Rationale — The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work. The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion;
- Backwards compatibility — All TIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The TIP must explain how the author proposes to deal with these incompatibilities;

Each TIP should pass the following process of acceptance:
## Workflow

`Proposal` → `Discussion` → `Community Voting` → `Reference Implementations Contest` → `Final TIP with Reference Implementations`
Each TIP should pass the following process of acceptance:

- Reference implementation — The reference implementation must be completed before any TIP is given status `Final`, but it need not be completed before the TIP is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code. The final implementation must include test code and documentation appropriate for the Everscale protocol.
**Reference Implementation** — The reference implementation must be completed before any TIP is given status `Review`, but it need not be completed before the TIP is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code. The final implementation must include test code and documentation appropriate for the Everscale protocol.

```mermaid
stateDiagram-v2
Idea --> Draft: Reference Implementation
Draft --> Proposal: Pull Request in ready\nfor review and conversation
Proposal --> Draft: Pull Request in draft\nfor resolve request changes
Proposal --> Review: Approving and merge Pull Request
Review --> Stagnant: If inactive for a period\nof greater 6 months
Stagnant --> Review
Review --> Withdrawn: The author have withdrawn
Review --> Living: The has integration\nof more one of ecosystem projects
Living --> Finalization: This is the final review for an TIP\nbefore moving to Final
Finalization --> Final
```
Loading