Page History

...

• 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? non-goal, for now

  • 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

...

•  confirm, clean, and capture manual notes, etherpad, release notes here Unknown User (meonkeys) 08 Oct 2025 
•  confirm, clean, and capture notes from Zoom chat / fireflies.ai bot / etc. here Unknown User (jdailey) 11 Oct 2025 

RAW notes from Fireflies AI meeting bot

Community Priorities and Developer Experience

...