Agenda
Before each meeting we'll post a proposed agenda. You can add any item you would like to cover to the agenda by emailing the user list or editing this wiki page.
Session | Description | Presenter | Time |
|---|
Introduction | We will also have an introduction of everyone on the call so the community can get more personally connected. | Ed Cable | 5 min |
Implementer Show & Tell | | n/a | 0 min |
| Discussion | Mifos Summit Recap Esha K Overview | Ed Ed/Lukasz | 10 min 20 min |
Demo/Tutorial | n/a | | 0 min |
| Open Office Hours | Support/feedback | | 25 min |
On the Call
- Lukasz (SolDevelo - Poland)
- Shiva (Hugo - India)
- Nayan (Conflux - India)
- Vishwas (Conflux - India)
- Miguel (IMM - Mozambique)
- Natu (IMM - Mozambique
- Lassaad (enda - Tunisia)
- Ed (COSM - USA)
- Marco (Quipu - Peru)
Notes
From: http://sync.in/GNtQpOOkXa
Mifos User Meet-up 10.25.2012
Agenda:
Mifos Summit Highlights
- Roadmap: notes to be posted and massaged into a roadmap and corresponding tickets created in JIRA
- Specialist Track: notes and action items to be posted - main next steps - publish minimum specialist criteria, launch new directory, begin launch of new site, come up promotional materials and consistent branding for Mifos X.
- Developer Track: notes and action items to be posted - ongoing weekly developer call to be scheduled and started up.
Esha K Overview
- Targeted for late December
- Exact dates to be posted online
Dashboard
- Simple scope for Esha K: set of indicators that will be displayed
- What's not included: configurable by role
- Status updates/notifications
- These are all in scope for Mifos X so don't hestitate to provide requirements
Chart of Accounts Interface
- Natu: Will it be run-time only or configurable after first install.
- By default the initial hierarchy will be there at initialization and can't be be changed.
- At any point in future through interface you can change the specific accounts in CoA
- It will now be through a GUI rather than a config file.
- Shiva: corrections to top-level hierarchy will still not be able to be made.
- Natu: why is it not possible to change the top-level?
- Existing hierarchy completely built on config file so too big of a technical issue to have these changes be made on Mifos.
File Upload Module
- Will work in simple way to uploading admin documents.
- Will it just be at the client and account level?
- No limits on file types - word docs, pdfs.
- Natu: are these documents going to be in the filesystem and not the database?
- Lukasz: this how it will be - like how client photos are added.
- Natu - don't want to add these into database because it will bloat database - putting in filesystem is lighter for overall system.
- Shiva: need to have a segregation between type of files - need separate directories for loan accounts versus client accounts, etc.
- Can files be accessed from different places?
- Natu: yes - user will not be able to experience differences on the back-end whether it is in database or file system.
- Nayan: some limitations for sys admin in terms of setting up clusters, etc.
- Shiva: larger apps general follow filesystem module and not database
- Natu: queries can get slow with blob data type - makes MySQL more prone to corruption.
- Shiva: need to follow naming conventions, folders, etc.
- Nayan: can we make this configurable?
- What will limit on file size be?
- Mifos X currently has File Upload Module which is quite similar to what is being discussed
- choice of appenders: currently file system appender is functional, S3 being developed
- Natu: where is it stored in Mifos X?
- Nayan: S3 and file system - not the database.
Good Time for Developer Meeting
- Thursdays one hour earlier would work ok.
- Saturdays might work too.