CODE BOUNTIES LANDING PAGE - NO OPEN FEATURES CURRENTLY

The two features are described in these pdf files:

• Declining Balance Calculation and Schedule Creation with Example in Excel- $750 REMOVED FROM CODE BOUNTIES
• Attendance values inherited from previous entries- $150 PENDING ACCEPTANCE

These small features we estimate at anywhere from 15-30 hours of work.

In brief, you will need to get the current code, develop a patch, submit it ( to mifos @ gfusa.org), have it accepted, and get paid. This is something of an experiment, so we are interested in your feedback on the process. We will acknowledge the receipt of the submitted code patch on the listserv and we will not evaluate code submissions after the first submission unless and until that first submission is rejected.

Guidelines

• You will need to write jUnit tests for the feature and conform (as possible) with our use of Hibernate and Struts.
• Our expectation is that you will ask questions first about the feature and then develop a patch which you can submit to our mifos @ gfusa.org address.
• We will be available on irc://freenode/mifos to answer questions as well as the listserv at mifos-developer@lists.sourceforge.net. You are welcome to peruse the archives or join in.
• We think many of your questions are answered in our FAQ
• For additional clarifications on the patch process, see here.

Getting started

• There are good instructions for getting a sandbox from the SVN and doing the build in the README.
• See also KickStart for more help in getting up to speed

Conditions for acceptance

• The code must follow good practices - clear concise code with relevant commenting, see CodingStandards
• You have to acknowledge these terms of participation to contribute code.
• You have to provide information to our legal department to get paid, per CodeBountiesPaymentRequirements.

-- Main.jdailey - 13 Jul 2006