12.28.2011 Developer Meeting

Owned by Ed Cable
Last updated: Dec 28, 2011Version comment

On the Call

  • Jakub
  • Ed
  • Krishnan
  • Shiva
  • Venkat
  • Kakha

Action Items:

  • Send reminder to mifos-developer for all contributors to log into IRC channel.
  • Venkat to send issues with compiling build and patches to mailing list.
    • Developers and Users will review functionality of the changes. 
  • Next meeting to record screencast of first technical walkthrough
  • First bi-weekly triage meeting to take place next week
  • Venkat to update JIRA with progress on data migration tool
  • Krishnan to host accounting meeting with Venkat

Notes

From: http://sync.in/askBAQC5BN

Open Triage Process

  • Proposing a bi-weekly meeting led by Lukasz, incorporating local on the ground from each region (Binny/Chetan from India, etc.)
  • Currently Jakub's team does it weekly internally as they plan out each iteration

2.2.3 Release

  • 7 Bugs Open
  • Thousands Separator - being worked on. 
  • Hugo Technologies ticket going to next release. 
  • First week of January - target release.
  • Code Freeze - end of this week. 
  • Krishnan to send in some pull requests within the next day or so. 
  • Krishnan will create ticket in JIRA for his work, labeling with fix version to 2.2.3 
  • Last release from g-main branch. 

2.3 Release

  • Aim for late January
  • In the process of testing full master branch. 
  • Starting the process of having milestone releases as well, allowing users to participate in testing process
  • 2.3 Code Freeze - TBD
  • Will have one master development branch that is always stable to release
  • Big features will be done on separate branches, when ready will be merged to master branch
    • Goal is to release more frequently but still maintain stable builds.
    • Krishnan happy with the ability to make small but frequent commits
    • Krishnan commends SolDevelo on the fluidity of their git commits. 

Technical Discussion

Identifying corresponding tests within code

  • Krishnan: is there any way to identify what are corresponding tests when changing code
  • Jakub: hard question - so many different levels of tests
  • For low level tests - search for usages of these tests
  • For selenium-based acceptance tests, if changing view or page, classes used in selenium tests are named very well (i.e. loan creation, etc.)
  • Also difficult because a few methodologies used to create tests. 

Proposal  from Krishnan

  • Difficult to figure out how things are organized. 
  • On developer call propose having a small code walkthrough from a senior community member to incoming community members
  • Go through a small change to show how the framework, business layer, works. 
  • Jakub: send in advance the topic/question would like to be walked through - so can prepare the presentation
  • Krishnan: can be specific or could be very general and simple task - i.e. add new master data capability - what would be data changes, entity changes, etc. or changing navigation, etc. - what things are required to be changed?
  • Code is not very obvious or newcomers - can spend a lot of time trying to figure out what needs to be changed to get things done - lots of wasted time. 

Proposal from Jakub:

  • From these create screencasts or FAQs - since new community members don't know these - if going with effort to create this, share on website as all. 

Accounting Inputs from Venkat

  • Will connect with Krishnan and share his knowledge from past requirements of customers
  • Accounting team to meet again led by Krishnan. 

Technical Blockers:

Enhancements from Hugo Technologies

  • Having some trouble building the WAR file
  • Code changes have been shared with Keith
  • Trying to build a WAR file locally on system before doing checkins into git.
  • All changes have been tested but also want to test by building the WAR file. 
  • Able to run successfully in workspace but not able to build the WAR file from there. 
  • Action: Venkat to send patches and screenshots of error through to mailing list.
    • Documented changes and will
    • Krishnan: can help with git changes
    • Propose sending a pull request so changes can be viewed. 
      • Jakub: before commiting it to master propose some reviews. 
  • 2 minor enhancements, 1 major
    • Collection Screen - brought in member dropdown into collection sheet entry screen.
    • Added additional fields after select center or you could select just a group, or select specific members from the group. 
    • Don't need to display the entire center - can specify an individual group or member. 
    • Krishnan: Suggest adding an engineering limit potentially so there are not too many entries in the dropdown. 
  • Issue 5193 (http://mifosforge.jira.com/browse/MIFOS-5193)
    • LSIM - irrespective of meeting date, can disburse loan at any time.
    • When enabling specific interest type, can enable grace period which will only calculate interest for that period.
    • Currently system calculates interest from meeting date to meeting date, not disbursement date
    • If enable LSIM, disbursement will always be greater or equal to meeting date, will be less than a month.
    • If enabled along with LSIM, calculates interst for grace period for date of loan disbursement. 
    • Targeting 2.2.3 release - patches will be reviewed in next couple of days.
  • Other enhancements

Grace Periods for VI and Declining Balance Loans

http://mifosforge.jira.com/browse/MIFOS-4742

  • Jakub - concerns with enabling grace periods causing a lot of issues.
  • A lot of issues with declining balance.-Very easy to have negative interests
  • Venkat will check with his team to review the code and check the feasibility of making edits to it. 

Issues from Kakha

  • Any feedback on accounting requirements that have been sent
  • Reviewing gaps from AFP document with Binny
  • Introducing Gela - a new colleague who will be marketing Mifos in Georgia. 

Updates

Data Migration Tool Update

  • Completed fix to performance issue - can update that to GitHub with help from Krishnan - for 5000 clients time was reduced from 2.5 hour to 45 minutes
  • Savings - if comfortable - can share with scripts as of now, but still working with Chetan to incorporate this into the tool.
  • Compatibility for latest version - some issues with 2.1.6 - checking in again with Chetan about this.
  • Action: update JIRA case with this progress and estimates on when this tool will be ready.