Meeting Notes:
Latest Meeting Notes at the top.
Meeting Notes 11th Mar 25
Attendees:
Aleks Vidakovic
Bowen
David Higgins
Notes:
Shorter meeting today due to reduce attendees and time pressures on some of the team. However we did discuss a new team of Devs that might want to be part of the Mifos community working on Fineract or perhaps MifosX and docker issues they had seen deploying Fineract. Discussion that Mifos Gazelle would deploy it in Kubernetes as part of MifosX but release is not the latest published last week.
Meeting Notes 25th Feb 25
Attendees:
Aleks Vidakovic
Bowen
David Higgins
Ed Cable
Notes:
David shared the new Wiki space and walked through it. He asked members to check the following:
They have had their right identities tagged on the Members section
They have access to add to meeting notes and the discussion topics list
To add topics for discussion
Aleks gave an update on the Command Processor proposal and progress highlighting that there was a complexity now in that the existing module also did a maker/checker function although it was not its core purpose and how to handle this needs to be agreed as thats mixing 2 concepts in a single module
Ed gave some topics for discussion which have been added to the discussion page, he will review and add more
Ed also said he will contact some more potential members of the Architecture Working Group directly and ask them to join
Bowen raised that the API layer especially Interop and Self Service needs to be looked at as he is trying to apply current best practice in Authentication to these, but documentation is poor. Ed asked which documentation so we can review it and Bowen agreed to share links here in the meeting notes or in the slack channel so it can be looked at.
Meeting Notes 11th Feb 25
Attendees:
Aleks Vidakovic
Bowen
Ed Cable
David Higgins
Notes:
Todays call we did a quick check around the attendees of what they want to achieve out of the working group moving forwards, the following were the points expressed:
An opportunity to not be restrained by being careful of breaking eggs, but instead able to rip apart and explore options
Look at Tech Debt
Look at what we do around Code Quality/Speed
Look at how we shape Mifos Architecture to future tech
Look at alignment to Web3.0 framework
Make it clear to understand underlying architecture and how we can contribute.
Explore if over time it could evolve to a formal steering board, design authority
Provide a forum to allow more members/orgs in the ecosystem to be able to input into strategic decisions
Allow broader views/discussions
Allow more contribution from individuals on the sidelines
Be a voice out from Mifos to other communities/orgs/dependencies on our views on direction
(Please feel free in this thread to add things to this discussion even if you were not part of the call)We also discussed a few next steps prior to the next WG Call:
David to create a Wiki for the WG (we will be doing this for all the working groups) to show the following:
Members
Lists of Topics for consideration
Running order of Topics
To discuss as a group Topics we want to discuss over the next few meetings idea will be that someone will start the discussion at a meeting on one or two of these and enable discussion
Need to have a diagram showing how the WG fits into the broader roadmapping of our projects and external projects such as Fineract. (Probably to be on the Wiki)
Review our community code of conduct and share to the working groups as a reminder of our inclusive and welcoming approach and standards.