@Avinaash M Vijayvargiya has joined the channel
#fineract 2026-03-13
how about any time we want/need a vote on a code/process change, we create a FSIP? exceptions: (1) releases -- we don't need a FSIP for every release, (2) if the proposal is compact/obvious/non-controversial
👍 1
also, my fingers want to type `FISP` every darn time, for no good reason. :laughing:
If you look around at other Apache projects, they typically use the SIPs (Significant Improvement Projects) for decisions that need a deliberation because of the impact on the architecture or trajectory of the project.
- Releases already have a VOTE.
- Tickets and code changes we have code reviews.
- Less significant changes we have a norm of "lazy consensus".... if no one objects in 72 hrs, you can do the thing you proposed.
👍 1
also, fyi, I created a skeleton FSIP for standardizing on postgres based on ongoing discussion. That one does seem big enough to warrant a FSIP
🙌 2
👍 2
@Mansi Maurya please send me your public PGP key (the one with fingerprint `A1DF78CD6B0B1C356D2E37F3FABE1D422F103FA2`) (reply to this w/key attached or email it to me, either is fine)
also, great work so far on https://github.com/apache/fineract-site/pull/56 ... I'll have more comments for you shortly