• Created by Unknown User (meonkeys), last updated on Oct 08, 2025 1 minute read

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Date

J oin Zoom Meeting:
https://us02web.zoom.us/j/83789770574?pwd=iz231dGaYqioYfmdpqOTJj6JZaVGVQ.1&jst=2

7am PDT / 2pm GMT / 5pm CEST / 7:30pm IST 

Presentation 

Attendees

Attendee locations

  • Mumbai, India
  • Seattle, WA USA
  • London, UK
  • Marseille, France
  • Delhi, India
  • Budapest, Hungary
  • Melbourne, Austrailia
  • Bangalore, India

Notes

  • James presents slides
  • The Apache Way, licensing, etc.
  • Survey Results 2025 August

  • Developer experience

    • very important!

    • gradle tasks are complex

    • hard to figure out even just how to run Fineract, how to know it is healthy

  • releases

    • goals for releases

      • ( consider these value-driven goals first, then get to improvements, ideal frequency, automation )

      • stable, reliable, frequent, well-documented

      • avoid vendor lock-in, leverage open source, release from any platform

      • reproducible?

    • current

      • complex and manual

      • robust and inefficient

      • large codebase, gradle tasks, project & roadmap management, ASF policies

    • proposed and in-progress work and other notes

      • understand, simplify, standardize, automate

      • test/evaluate ATR (Apache Trusted Release) tool

      • policy/culture improvements to ease releasing

        • keep develop clean: be careful with WIP code/features

        • maintain your issues

      • improve documentation and release plugin, or shift to other automation

      • we don’t currently maintain releases, vendors could do this

      • what is ideal release frequency? depends on type of fix … we may need/want to differentiate between major, minor, patch/hotfix releases (e.g. full ceremony doesn’t make sense for a hotfix)

  • roadmap mechanism - Fineract Significant Improvement Proposals
  • gaps
  • progress
    • readme updates
    • docker scout
    • sharding of tests
    • build process improvements
  • security
  • NextGen / vNext ideas
    • modularity
    • UUIDs, no db-dependent incrementing primary keys

Action items

  • No labels