As part of an SIP centric forking model, this SIP tracks the first step in the approval process for any SIP to be included in a fork or upgrade. Specifically, the stage where the Core Developers vet the concept of an SIP and give a βgreen lightβ sufficient for SIP authors to move forward in development.
Abstract
The pipeline for Core SIPs, per the SIP-Centric upgrade model, is as follows.
This SIP documents all SIPs marked as Eligible For Inclusion by the All Core Devs. Typically to reach this stage, an SIP must be discussed in brief on an AllCoreDevs Call and motioned by rough consenses to be moved to this stage. Any additions to this list are required to provide a link to the meeting notes when this discussion and decision took place.
The requirements for Eligible for Inclusion is that the AllCoreDevs, representing the major clients and ecosystem stakeholders etc:
Are positive towards the SIP,
Would accept (well written) PRs to include the SIP into the codebase.
So that it could be toggled on for testingβ¦
β¦but not with an actual block number for activation
Motivation
Development of clear specifications and pull requests to existing Sila Clients is a large investment of time and resources. The state of Eligible for Inclusion is a signal from the Sila Core Developers to an SIP Author validiating the idea behind an SIP and confirms investing their time further pursing it is worthwhile.
James Hancock (@MadeofTin), "SIP-2378: SIPs Eligible for Inclusion [STAGNANT]," Sila Improvement Proposals, no. 2378, November 2019. Available: https://sips.sila.org/SIPS/sip-2378.