Community -
In other Apache Top Level Projects there is the notion of a SIP
(Significant Improvement Proposal). The SIP is intended to signal that
"hey, pay attention, this is important". It does not apply to small code
changes, or to features, but rather to architecture or testing frameworks,
or significant efforts to be undertaken.
We've had something like that at Apache Fineract(R) but, speaking as a
member of the PMC, I think we should formalize this a bit more. So, I'm
bringing this here. If there are objections within 72 hrs, let's please
use this template structure.
A Fineract-SIP should have the following things:
*Title: Specific Idea*
*Summary*
the TL;DR
*Status*: Under Discussion, Proposed, VOTE, Accepted/Rejected, Under
Development, Stalled, Completed
NOTE: This is per our normal process of Discussion, Proposal, Vote
and then takes it to the next step of tracking the SIP over time.
*Who is involved*: Owner and collaborators
*Background/Motivation*
NOTE: Why are we considering this?
*Goals and Exclusions*
NOTE: List high level goals and also things this will NOT address.
*Change Proposed*
examples.... and be specific
Architectural changes
Significant re-factoring
Test Framework
API versioning
*Alternatives Considered*
Note: Why this specific approach to the challenge.
*Phases of work*
Note: Specific timelines or "gates". We do this, learn that, then
proceed.
Examples from other Apache projects.
https://spark.apache.org/improvement-proposals.html
https://cwiki.apache.org/confluence/display/KAFKA/Kafka%20Improvement%20Proposals
https://cwiki.apache.org/confluence/display/BEAM/Beam+Improvement+Proposals
https://github.com/apache/pulsar/blob/master/pip/README.md
- jdailey
