[jira] [Updated] (FINERACT-371) Make gradle callable from the top level directory.

2017-02-16 Thread Shaik Nazeer Hussain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FINERACT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shaik Nazeer Hussain updated FINERACT-371:
--
Fix Version/s: 0.7.0-incubating

> Make gradle callable from the top level directory.
> --
>
> Key: FINERACT-371
> URL: https://issues.apache.org/jira/browse/FINERACT-371
> Project: Apache Fineract
>  Issue Type: Wish
>Reporter: Myrle Krantz
>Assignee: Shaik Nazeer Hussain
>Priority: Minor
> Fix For: 0.7.0-incubating
>
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-374) Add Gradle wrapper download location in readme file

2017-02-16 Thread Shaik Nazeer Hussain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FINERACT-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shaik Nazeer Hussain updated FINERACT-374:
--
Fix Version/s: 0.7.0-incubating

> Add Gradle wrapper download location in readme file 
> 
>
> Key: FINERACT-374
> URL: https://issues.apache.org/jira/browse/FINERACT-374
> Project: Apache Fineract
>  Issue Type: Task
>Reporter: Shaik Nazeer Hussain
>Assignee: Shaik Nazeer Hussain
>Priority: Blocker
> Fix For: 0.7.0-incubating
>
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201701.mbox/%3CC8F9C232-D844-4920-BC9F-7DA536FAB6F5%40classsoftware.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-374) Add Gradle wrapper download location in readme file

2017-02-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/FINERACT-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871287#comment-15871287
 ] 

ASF GitHub Bot commented on FINERACT-374:
-

GitHub user nazeer1100126 opened a pull request:

https://github.com/apache/incubator-fineract/pull/292

FINERACT-374-Add Gradle wrapper download location in readme file



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-374

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-fineract/pull/292.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #292


commit fff5cef6a4bf6f7e094af6820b4b71d5cb6692d4
Author: Nazeer Hussain Shaik 
Date:   2017-02-17T06:44:23Z

FINERACT-374-Add Gradle wrapper download location in readme file




> Add Gradle wrapper download location in readme file 
> 
>
> Key: FINERACT-374
> URL: https://issues.apache.org/jira/browse/FINERACT-374
> Project: Apache Fineract
>  Issue Type: Task
>Reporter: Shaik Nazeer Hussain
>Assignee: Shaik Nazeer Hussain
>Priority: Blocker
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201701.mbox/%3CC8F9C232-D844-4920-BC9F-7DA536FAB6F5%40classsoftware.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (FINERACT-374) Add Gradle wrapper download location in readme file

2017-02-16 Thread Shaik Nazeer Hussain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FINERACT-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shaik Nazeer Hussain reassigned FINERACT-374:
-

Assignee: Shaik Nazeer Hussain  (was: Markus Geiss)

> Add Gradle wrapper download location in readme file 
> 
>
> Key: FINERACT-374
> URL: https://issues.apache.org/jira/browse/FINERACT-374
> Project: Apache Fineract
>  Issue Type: Task
>Reporter: Shaik Nazeer Hussain
>Assignee: Shaik Nazeer Hussain
>Priority: Blocker
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201701.mbox/%3CC8F9C232-D844-4920-BC9F-7DA536FAB6F5%40classsoftware.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-374) Add Gradle wrapper download location in readme file

2017-02-16 Thread Shaik Nazeer Hussain (JIRA) 

[ 
https://issues.apache.org/jira/browse/FINERACT-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871242#comment-15871242
 ] 

Shaik Nazeer Hussain commented on FINERACT-374:
---

The gradle link mentioned in attached mail thread doesn't have cli package. So 
adding download location from Fineract github reposiory. 
-
wget --no-check-certificate -P fineract-provider/gradle/wrapper 
https://github.com/apache/incubator-fineract/raw/develop/fineract-provider/gradle/wrapper/gradle-wrapper.jar
(or)
curl --insecure -L 
https://github.com/apache/incubator-fineract/raw/develop/fineract-provider/gradle/wrapper/gradle-wrapper.jar
 > fineract-provider/gradle/wrapper/gradle-wrapper.jar
-

> Add Gradle wrapper download location in readme file 
> 
>
> Key: FINERACT-374
> URL: https://issues.apache.org/jira/browse/FINERACT-374
> Project: Apache Fineract
>  Issue Type: Task
>Reporter: Shaik Nazeer Hussain
>Assignee: Markus Geiss
>Priority: Blocker
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201701.mbox/%3CC8F9C232-D844-4920-BC9F-7DA536FAB6F5%40classsoftware.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Loan Topup disburse when loan to be closed has transactions made on the same date

2017-02-16 Thread Lionel Raymundi - Poincenot 
Hi guys,

There is a business validation on a loan topup operation, which prevents
you to set the disbusement date of the new loan if the previous one has
transactions on the same date (or later):

error.msg.loan.disbursal.date.should.be.after.last.
transaction.date.of.loan.to.be.closed

It is not that unusual that we ask the client to settle some overdued
installments before we disbuse the new loan, as a willingness to
pay demonstration. And is not that unusual that the repayments are done the
same day of the disbursement of the new Loan.

So the question is: Could the validation be modified to check only for
transactions made later than the disbursement date, but not on the same
date? Or is it a business validation that must remain as is?

I hope I made myself clear, please dont hesitate on asking me if I didn't...

Regards

Lionel

[jira] [Commented] (FINERACT-371) Make gradle callable from the top level directory.

2017-02-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/FINERACT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869981#comment-15869981
 ] 

ASF GitHub Bot commented on FINERACT-371:
-

GitHub user nazeer1100126 opened a pull request:

https://github.com/apache/incubator-fineract/pull/291

FINERACT-371 - Make gradle callable from the top level directory.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-371

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-fineract/pull/291.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #291


commit 1dabd44b45662fc6c5104239bd7cda43f0b0258c
Author: Nazeer Hussain Shaik 
Date:   2017-02-16T14:08:08Z

FINERACT-371 - Make gradle callable from the top level directory.




> Make gradle callable from the top level directory.
> --
>
> Key: FINERACT-371
> URL: https://issues.apache.org/jira/browse/FINERACT-371
> Project: Apache Fineract
>  Issue Type: Wish
>Reporter: Myrle Krantz
>Assignee: Shaik Nazeer Hussain
>Priority: Minor
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-371) Make gradle callable from the top level directory.

2017-02-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/FINERACT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869953#comment-15869953
 ] 

ASF GitHub Bot commented on FINERACT-371:
-

Github user nazeer1100126 commented on the issue:

https://github.com/apache/incubator-fineract/pull/290
  
Closing this as RAT is still generating the report file in 
fineract-provider/build/report/rat/


> Make gradle callable from the top level directory.
> --
>
> Key: FINERACT-371
> URL: https://issues.apache.org/jira/browse/FINERACT-371
> Project: Apache Fineract
>  Issue Type: Wish
>Reporter: Myrle Krantz
>Assignee: Shaik Nazeer Hussain
>Priority: Minor
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (FINERACT-366) Issue With Creating RD account with 'Charge Time Type' Savings Activation

2017-02-16 Thread Satish S (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FINERACT-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Satish S reassigned FINERACT-366:
-

Assignee: Satish S  (was: Markus Geiss)

> Issue With Creating RD account with 'Charge Time Type' Savings Activation 
> --
>
> Key: FINERACT-366
> URL: https://issues.apache.org/jira/browse/FINERACT-366
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Satish S
>  Labels: p1
> Attachments: activate.png, savact.png
>
>
> Steps to reproduce:
> > Create a Charge with following data set:
>Charge Applies To: Savings & Deposits
>Charge Time Type: Savings Activation
>Charge Calculation:  Flat
>Amount: 50
> > Go to Client's page, Click on 'More' and click on 'New Recurring Deposit' 
> >select the RD product from drop-down  menu and then  enter the  following 
> >data sets:
> Recurring Deposit Amount: 5000
> Deposit Frequency: 1 month
> Deposit period: 6 month
> >Add the above created charge
> >Submit  it  on 01 Jan 2015.
> >Approve it and Activate it  on 01 Feb 2015.
> >In  RD account page, go to Charges Tab and select the charge and click on 
> >'Pay Charge'
> >Provide the date 01 January 2015 and 'Submit' it. 
> Then it throws the error, 
> "field is required
> validation.msg.savingsaccount.transaction.not.valid.cannot.pay.activation.time.charge.is.automated"
> Check  the screenshot 'activate.png'.
> Expected: When creating RD account with charge type 'Savings Activation', the 
>  charge  must be paid just after activation of RD account similar to  Savings 
> Activation.  check the screenshot savact.png 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-371) Make gradle callable from the top level directory.

2017-02-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/FINERACT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869778#comment-15869778
 ] 

ASF GitHub Bot commented on FINERACT-371:
-

GitHub user nazeer1100126 opened a pull request:

https://github.com/apache/incubator-fineract/pull/290

FINERACT-371 - Make gradle callable from the top level directory.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-371

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-fineract/pull/290.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #290


commit 739af7552b817b989ad3eed25152fda6a73bb1f3
Author: Nazeer Hussain Shaik 
Date:   2017-02-16T11:30:19Z

FINERACT-371 - Make gradle callable from the top level directory.




> Make gradle callable from the top level directory.
> --
>
> Key: FINERACT-371
> URL: https://issues.apache.org/jira/browse/FINERACT-371
> Project: Apache Fineract
>  Issue Type: Wish
>Reporter: Myrle Krantz
>Assignee: Shaik Nazeer Hussain
>Priority: Minor
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (FINERACT-377) Reinvesting Recurring Deposit is taking present date in stead of maturity date

2017-02-16 Thread Shaik Nazeer Hussain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FINERACT-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shaik Nazeer Hussain resolved FINERACT-377.
---
   Resolution: Fixed
 Assignee: Santosh Math  (was: Satish S)
Fix Version/s: 0.7.0-incubating

with PR https://github.com/apache/incubator-fineract/pull/289 issue is 
resolved. 

> Reinvesting Recurring Deposit is taking present date in stead of maturity date
> --
>
> Key: FINERACT-377
> URL: https://issues.apache.org/jira/browse/FINERACT-377
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Santosh Math
>  Labels: p1
> Fix For: 0.7.0-incubating
>
> Attachments: reinv.png
>
>
> 1. Create a Recurring deposit account for a client on 01 January 2016, term 
> is 3 months repaid every  month -> Approve and disburse on same date.
> 2. Make Deposits on 01 Jan, 01 Feb, and 01 March
> 3. Also run the scheduler job "Update Deposit Accounts Maturity details" -> 
> Navigate back to the Recurring deposit account page -> Click on Close button.
> 4. In Close account page, select the date as 01 April 2015(maturity date) and 
> in action drop-down select Reinvest as option -> Click on 'Submit' button.
> After clicking 'Submit' button, the previous RD account gets closed and new 
> RD account gets created with deposit amount = closing amount of previous RD 
> account. The reinvesting date should be 01 April 2015, but the application is 
> taking present date as 'Reinvesting Date'. Check the screenshot. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (FINERACT-377) Reinvesting Recurring Deposit is taking present date in stead of maturity date

2017-02-16 Thread Shaik Nazeer Hussain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FINERACT-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shaik Nazeer Hussain reassigned FINERACT-377:
-

Assignee: Satish S  (was: Shaik Nazeer Hussain)

> Reinvesting Recurring Deposit is taking present date in stead of maturity date
> --
>
> Key: FINERACT-377
> URL: https://issues.apache.org/jira/browse/FINERACT-377
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Satish S
>  Labels: p1
> Attachments: reinv.png
>
>
> 1. Create a Recurring deposit account for a client on 01 January 2016, term 
> is 3 months repaid every  month -> Approve and disburse on same date.
> 2. Make Deposits on 01 Jan, 01 Feb, and 01 March
> 3. Also run the scheduler job "Update Deposit Accounts Maturity details" -> 
> Navigate back to the Recurring deposit account page -> Click on Close button.
> 4. In Close account page, select the date as 01 April 2015(maturity date) and 
> in action drop-down select Reinvest as option -> Click on 'Submit' button.
> After clicking 'Submit' button, the previous RD account gets closed and new 
> RD account gets created with deposit amount = closing amount of previous RD 
> account. The reinvesting date should be 01 April 2015, but the application is 
> taking present date as 'Reinvesting Date'. Check the screenshot. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-377) Reinvesting Recurring Deposit is taking present date in stead of maturity date

2017-02-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/FINERACT-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869698#comment-15869698
 ] 

ASF GitHub Bot commented on FINERACT-377:
-

GitHub user satish-conflux opened a pull request:

https://github.com/apache/incubator-fineract/pull/289

FINERACT-377 : Reinvesting Recurring Deposit is taking present date in 
stead of maturity date.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/satish-conflux/incubator-fineract FINERACT-377

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-fineract/pull/289.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #289


commit abeab28cd7269bb61e68ea6a31f00184511f3da1
Author: satish-conflux 
Date:   2017-02-16T10:31:39Z

FINERACT-377 : Reinvesting Recurring Deposit is taking present date in 
stead of maturity date




> Reinvesting Recurring Deposit is taking present date in stead of maturity date
> --
>
> Key: FINERACT-377
> URL: https://issues.apache.org/jira/browse/FINERACT-377
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: reinv.png
>
>
> 1. Create a Recurring deposit account for a client on 01 January 2016, term 
> is 3 months repaid every  month -> Approve and disburse on same date.
> 2. Make Deposits on 01 Jan, 01 Feb, and 01 March
> 3. Also run the scheduler job "Update Deposit Accounts Maturity details" -> 
> Navigate back to the Recurring deposit account page -> Click on Close button.
> 4. In Close account page, select the date as 01 April 2015(maturity date) and 
> in action drop-down select Reinvest as option -> Click on 'Submit' button.
> After clicking 'Submit' button, the previous RD account gets closed and new 
> RD account gets created with deposit amount = closing amount of previous RD 
> account. The reinvesting date should be 01 April 2015, but the application is 
> taking present date as 'Reinvesting Date'. Check the screenshot. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FINERACT-401) when assigning a a loan officer to a client. Can we add and optional parameter called "inhertClientActiveAccounts" . This is similar to the one we have on assigning a l

2017-02-16 Thread Santosh Math (JIRA) 
Santosh Math created FINERACT-401:
-

 Summary: when assigning a a loan officer to a client. Can we add 
and optional parameter called "inhertClientActiveAccounts" . This is similar to 
the one we have on assigning a loan officer to a group
 Key: FINERACT-401
 URL: https://issues.apache.org/jira/browse/FINERACT-401
 Project: Apache Fineract
  Issue Type: Improvement
  Components: Loan
Reporter: Santosh Math
Assignee: Markus Geiss
Priority: Minor


Reported by Andrew at https://mifosforge.jira.com/browse/MIFOSX-2115

Original Description:
when assigning a a loan officer to a client. Can we add and optional parameter 
called "inhertClientActiveAccounts" . This is similar to the one we have on 
assigning a loan officer to a group.
I know the proposeAndAccept Transfer can do this but a lot of our clients make 
mistakes while making payments before transferring clients to differrent loan 
officer in the same office . Due to this they cannot adjust the transaction or 
undo disbursal since the client has been transferred. Adding this functionality 
will avoid them using the proposeAndAcceptTransfer.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-400) Manage Funds Enhancement

2017-02-16 Thread Santosh Math (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FINERACT-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-400:
--
Labels: p2  (was: )

> Manage Funds Enhancement
> 
>
> Key: FINERACT-400
> URL: https://issues.apache.org/jira/browse/FINERACT-400
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Organization
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2
>
> Reported by Dayna Harp at https://mifosforge.jira.com/browse/MIFOSX-2239
> Original Description:
> For those organizations that receive donor funds that are intended to be used 
> for specific loan programs, there should be the ability to indicate the 
> amount of money in the fund. As loans for that fund type are made, the 
> available remaining funds should decline. There should also be the feature to 
> alert the loan officer when loans from that fund are gone.
> For example: https://demo2.openmf.org/preview/#/managefunds/ Add fields to 
> indicate amount of fund, date of origination, end date (if applicable), 
> description field
> This fund maps to GL
> When loan is made, system automatically makes entry to decrease the fund.
> If loan is approved for $5000 and only $3500 left in fund, Loan Officer gets 
> an alert and system allows $3500 from fund then requests a secondary source 
> for remaining approved balance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

RE: Please help evaluate Fineract's readiness for graduation

2017-02-16 Thread Markus Geiß 
Done

Cheers

Markus

-Original Message-
From: Jim Jagielski [mailto:j...@jagunet.com] 
Sent: Wednesday, February 15, 2017 05:45 PM
To: dev@fineract.incubator.apache.org
Subject: Re: Please help evaluate Fineract's readiness for graduation

Can you add Write access for my cwiki account: Jim Jagielski, j...@apache.org

Thx
> On Feb 15, 2017, at 11:20 AM, Myrle Krantz  wrote:
> 
> Hello Fineracters,
> 
> I believe we've made enough progress to start the process of graduation.
> 
> Because I believe that we are ready for graduation, I've created a 
> draft "Graduation Resolution"
> 
> 
> https://cwiki.apache.org/confluence/display/FINERACT/Graduation+Resolu
> tion
> 
> Please review especially the following points:
> * the proposed list of initial members, (I want verification from 
> *every*
> *initial* *member*)
> * their associations, and
> * the proposed chair of the PMC. (Myrle Krantz)
> 
> I've adjusted the Maturity Evaluation.  Anywhere that I changed the 
> estimation of maturity, I removed people's approval, so please check 
> me and add your name back if you agree with the changed evaluation.  
> When you're looking at the maturity evaluation, you'll see that we 
> aren't perfect.  I do not believe the incubator provides us value in 
> addressing the remaining issues, so I'm not treating them as blockers for 
> graduation.
> 
> https://cwiki.apache.org/confluence/display/FINERACT/Maturity+Evaluati
> on
> 
> Once changes and discussions have settled down, and once we have a 
> final list of initial members, I will call a vote on submitting our 
> graduation to the incubator.  My goal is that our graduation 
> resolution be submitted to the ASF board by the March board meeting.
> 
> Greets,
> Myrle
> 
> 
> On Wed, Feb 15, 2017 at 1:32 AM, Ed Cable  wrote:
> 
>> Just doing a check-in as to where we stand.
>> 
>> Nazeer has been addressing some of the outstanding points and has 
>> recently posted some additional release management documentation 
>> which can be viewed at https://cwiki.apache.org/confluence/pages/viewpage.
>> action?pageId=67640333
>> 
>> I have pushed the changes to the Apache Fineract website github repo 
>> and these have been merged the but the website is not reflecting the 
>> edits I made.
>> 
>> Nazeer has requested feedback on the Findbugs Implementation he has 
>> ready go go.
>> 
>> 2 active threads are being discussed related to security and 
>> backwards compatibility.
>> 
>> We are also evaluating a couple additional committers and will soon 
>> be ready to call for graduation if our mentors too fee we are ready.
>> 
>> Ed
>> 
>> 
>> 
>> On Fri, Jan 27, 2017 at 10:14 AM, Jim Jagielski  wrote:
>> 
>>> Makes sense.
 On Jan 25, 2017, at 10:52 PM, Shaik Nazeer >> confluxtechnologies.com> wrote:
 
 Instead of modifying Fineract website on every Fineract releases, 
 can
>> we
>>> link required details to Fineract wiki pages?
 For example latest release details can be found at
>>> https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders
 
 Thanks,
 Nazeer
 -Original Message-
 From: Markus Geiß [mailto:mge...@mifos.org]
 Sent: 26 January 2017 01:55
 To: Ed Cable
 Cc: dev (dev@fineract.incubator.apache.org)
 Subject: Re: Please help evaluation Fineract's readiness for 
 graduation
 
 Hey Ed,
 
 the Apache Fineract website is a github repo you'll find at 
 Apache's
>>> github mirror.
 
 Simply fork it, create a new branch, do the needed changes and send 
 a
>> PR.
 
 Best wishes,
 
 Markus Geiss
 Chief Architect
 RɅĐɅЯ, The Mifos Initiative
 
 On Jan 24, 2017 15:58, "Ed Cable"  wrote:
 
> Markus,
> 
> Nazeer is continuing to work on addressing the areas of concern 
> related to QU10, QU40, and RE50.
> 
> Could you provide me access to the Apache Fineract website to 
> address
> CO10 and then for CS10 do we want that on the Apache Fineract 
> website or the wiki?
> 
> Thanks,
> 
> Ed
> 
> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski 
>> wrote:
> 
>> Agreed.
>> 
>>> On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik 
>>> 
>> wrote:
>>> 
>>> On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable  wrote:
 Could our Apache Fineract mentors please provide some guidance 
 on a
>> couple
 of the areas we need to improve upon:
 
 QU10 "*The project is open and honest about the quality of its
>> code.
 Various levels of quality and maturity for various modules are 
 natural
>> and
 acceptable as long as they are clearly communicated." -*
 
 Do you have any other projects you could point to that have 
 strong transparent