Community (all) - As we grow and increase our visibility as well as our usage in the world, we should consider how to conduct ourselves in a way the improves quality and stability.
I'd like to point out how SPARK , another Apache Project, uses a formal process to adopt major changes to their project. https://spark.apache.org/improvement-proposals.html *As a way to proceed - what are your reactions to this idea. * *Here is what it would look like here at FINERACT. * The purpose of a Fineract Improvement Proposal (FIP) is to inform and involve the user community in major improvements to the Fineract codebase throughout the development process, to increase the likelihood that user needs are met. FIPs should be used for significant user-facing or cross-cutting changes, not small incremental improvements. When in doubt, if a committer thinks a change needs an FIP, it does. (as examples, in the future, instead of just an email describing the idea, we would also have a formal FIP listed on the confluence page and recording a vote on it). What is a FIP? An FIP is similar to a product requirement document commonly used in product management.
