Re: [Mifos-developer] Web App: Unable to find data for some sections in the loan accounts section

[Sendoro Juma]

Dear Michael, 

Excellent and much appreciated, 

I would wish you the running version of these key software in the first
page of the application. 

Anyway; what was the key issues/prerequisite to consider during
migration from 5.6 to 5.7 if you had one?

On 2020-06-07 15:05, Michael Vorburger wrote:

> Dear Sendoro, thanks for the interest, happy to clarify: 
> 
> On Sun, Jun 7, 2020 at 12:19 PM Sendoro Juma  wrote: 
> 
>> Dear Michael, 
>> 
>> Sorry to jump on this thread; 
>> 
>> What is the MySQL version of the Dev Server: or may be you have it written 
>> the key software compoents running there?
> 
> https://www.fineract.dev runs on MySQL 5.7 on Google Cloud SQL, and using the 
> MySQL (not Drizzle) JDBC driver that Fineract includes in its Docker 
> container. 
> 
> Thanks 
> 
> On 2020-06-07 12:25, Michael Vorburger wrote: 
> Re. the "500 Internal error is been displayed" when you "upload any document 
> in the Loan Documents tab", that sounds like a bug in the Fineract back end.. 
>  
> 
> Which Fineract server do you use? Your own locally, or a Cloud hosted one? If 
> you run a local one, then check the log- is there an error with an exception? 
> If yes, please create a Fineract JIRA issue with that Exception, and another 
> contributor could look into it. 
> 
> If you use a hosted one, please use https://www.fineract.dev ... I have set 
> up https://cloud.google.com/error-reporting there, so I'll create a JIRA for 
> any 500 Internal Server error occuring on that server 
> 
> On Sun, 7 Jun 2020, 09:16 Muskan Khedia,  wrote: 
> Please look over the content below. Forwarding the mail as I missed to 
> mention the mailing list earlier.  
> 
> -- Forwarded message -
> From: MUSKAN KHEDIA 
> Date: Sat, Jun 6, 2020 at 9:56 PM
> Subject: Web App: Unable to find data for some sections in the loan accounts 
> section
> To: Ed Cable , Abhay Chawla , 
> Jivjyot Singh , Karan Takalkar 
>  
> 
> Sir,
> 
> I am working in the re-write of the community app. While developing the loans 
> section in the web-app I came across some problems that are creating a 
> barrier during the implementation. The problems are as follows: 
> 
> *  Unable to find data for Future Schedule tab, Loan Tranche Details tab, 
> Floating Interest Rates tab and Standing Instructions tab.
> *  Unable to upload any document in the Loan Documents tab, a 500 Internal 
> error is been displayed.
> 
> Can you please provide me with some details or solutions regarding the same?
> 
> -- 
> 
> Thank You 
> Muskan Khedia 
> -- 
> 
> Thank You 
> Muskan Khedia 
> Mifos-developer mailing list
> mifos-develo...@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Mifos-developer mailing list
mifos-develo...@lists.sourceforge.net
Unsubscribe or change settings at:
https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] Web App: Unable to find data for some sections in the loan accounts section

[Sendoro Juma]

Dear Michael, 

Sorry to jump on this thread; 

What is the MySQL version of the Dev Server: or may be you have it
written the key software compoents running there?  

Thanks 

On 2020-06-07 12:25, Michael Vorburger wrote:

> Re. the "500 Internal error is been displayed" when you "upload any document 
> in the Loan Documents tab", that sounds like a bug in the Fineract back end.. 
>  
> 
> Which Fineract server do you use? Your own locally, or a Cloud hosted one? If 
> you run a local one, then check the log- is there an error with an exception? 
> If yes, please create a Fineract JIRA issue with that Exception, and another 
> contributor could look into it. 
> 
> If you use a hosted one, please use https://www.fineract.dev ... I have set 
> up https://cloud.google.com/error-reporting there, so I'll create a JIRA for 
> any 500 Internal Server error occuring on that server 
> 
> On Sun, 7 Jun 2020, 09:16 Muskan Khedia,  wrote: 
> 
>> Please look over the content below. Forwarding the mail as I missed to 
>> mention the mailing list earlier.  
>> 
>> -- Forwarded message -
>> From: MUSKAN KHEDIA 
>> Date: Sat, Jun 6, 2020 at 9:56 PM
>> Subject: Web App: Unable to find data for some sections in the loan accounts 
>> section
>> To: Ed Cable , Abhay Chawla , 
>> Jivjyot Singh , Karan Takalkar 
>>  
>> 
>> Sir,
>> 
>> I am working in the re-write of the community app. While developing the 
>> loans section in the web-app I came across some problems that are creating a 
>> barrier during the implementation. The problems are as follows: 
>> 
>> *  Unable to find data for Future Schedule tab, Loan Tranche Details tab, 
>> Floating Interest Rates tab and Standing Instructions tab.
>> *  Unable to upload any document in the Loan Documents tab, a 500 Internal 
>> error is been displayed.
>> 
>> Can you please provide me with some details or solutions regarding the same?
>> 
>> -- 
>> 
>> Thank You 
>> Muskan Khedia 
>> -- 
>> 
>> Thank You 
>> Muskan Khedia
> 
> Mifos-developer mailing list
> mifos-develo...@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] Discussing Projects and Focus Areas for Interns working on Fineract

[Sendoro Juma]

Dear Ed, All, 

Indeed this is very critical, We must push ourselves to aliaviate from
'the technical dept" we are currently in;  

Technical dept is real and painful, also let's try to avoid going back
to the situation. 

We shall try our level best;  those use code to clienst; they are also
get practical feedback which must be channel back to the community. 

On 2020-05-23 13:33, Awasum Yannick wrote:

> On Thu, May 21, 2020 at 12:56 AM Ed Cable  wrote: 
> 
>> Hi all, 
>> 
>> Recently I was trying to get up to speed on all the great work around 
>> alleviating technical debt, upgrading core dependencies, strengthening and 
>> hardening Fineract, and improving overall code quality that Michael and 
>> Awasum have been leading with the support of Petri, Ivan, Manthan, Percy, 
>> Nasser, Georgio, and others.  
>> 
>> There really has been a flurry of activity across Github and JIRA from these 
>> rockstar volunteers but I also want to make sure that individuals from 
>> companies that are building and distributing solutions on Fineract become 
>> involved at the same level and are aware of this going activity and the need 
>> and opportunity to contribute as well.  
>> 
>> As many of the major issues related to upgrading of core dependencies have 
>> been starting to get resolved, I was trying to understand what 
>> projects/tasks our four interns working on Fineract (3 from GSOC through 
>> Apache and 1 from Outreachy through Mifos) would be focused on.  Both so I 
>> can document it for roadmap/planning purposes and also to see what 
>> additional capacity the interns have to take on items from the backlog, 
>> reviewing of incoming pull requests from partners, scalability, additional 
>> code quality etc.  
>> 
>> We'll have public gists for each of the interns summer objectives linking to 
>> the respective issue trackers available by start of the coding period (June 
>> 1).  
>> 
>> From looking at the proposals of our interns and the completed and 
>> in-progress activity on JIRA/Github, I've deduced the following: 
>> 
>> MANTHAN 
>> _Manthan's plate is very full at the moment as he works under the mentorship 
>> of Michael on:_ 
>> 
>> * Completing Swagger API documentation - 
>> https://jira.apache.org/jira/browse/FINERACT-733
>> * Implementing and Enforcing Checkstyle (and all of the corresponding 
>> sub-tasks) - https://issues.apache.org/jira/browse/FINERACT-821
>> * Fixing some of the 59 High Priority (p1 and p2) Issues in the Backlog - 
>> https://issues.apache.org/jira/browse/FINERACT-790?jql=issuetype%20%3D%20Bug%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20p1
>>  and 
>> https://issues.apache.org/jira/browse/FINERACT-754?jql=issuetype%20%3D%20Bug%20AND%20status%20%3D%20Open%20AND%20labels%20in%20(P2%2C%20p2)
>> * Use prepared statements instead of string concatenated SQL everywhere - 
>> https://issues.apache.org/jira/browse/FINERACT-854
>> 
>> NASSER 
>> _Nasser's primary focus is on the migration from OpenJPA to Eclipselink 
>> which I assume will take most of the summer._ 
>> 
>> * _ _https://issues.apache.org/jira/browse/FINERACT-854
>> 
>> At the moment I believe Awasum and Courage are mentoring Nasser and I think 
>> Saransh has been interested as well and I'm hoping @Ebenezer Graham and 
>> @Aleksandar Vidakovic can assist too.
> 
> Officially, on the GSoC portal, Courage and Sanyam are the mentors but i do 
> keep up with Nasser's work. Yes, Nasser already started on the OpenJPA to 
> EclipseLink migration project and has even made progress to the extend of 
> sending a draft PR: https://github.com/apache/fineract/pull/928 . Lets be 
> hopeful that Nasser gets this done earlier than expected but we could have a 
> lot of surprises there. Remember the Hibernate to OpenJPA migration for 
> Fineract 1.x? 
> 
>> PERCY 
>> _Percy's original focus included the upgrade to Java 11 but now that's 
>> complete, his focus is primarily around improving code quality by running 
>> and enforcing different codebase scanning tools and increasing testing 
>> coverage, and reducing run time of tests. _@percyayukashu@gmail.com_  can 
>> you share the links to the JIRA issues for the work you're doing. I was 
>> aware of:_ 
>> 
>> * 
>> 
>> Enable and Enforce Googe's Error Prone: 
>> https://issues.apache.org/jira/browse/FINERACT-822 
>> * 
>> 
>> https://issues.apache.org/jira/browse/FINERACT-713 
>> * 
>> 
>> Replace Joda time with Java.time - 
>> https://issues.apache.org/jira/browse/FINERACT-826 
>> 
>> Awasum is serving as the primary mentor.
> 
> Yes, We will tackle the Joda time migration, Error Prone should be done 
> soon(before end of May 2020). We will likely look into re-enabling PMD and 
> enforcing it: https://jira.apache.org/jira/browse/FINERACT-1001 then fix 
> major issues, warning, deprecations and errors as a result of the Java 11 
> upgrade ( see: https://issues.apache.org/jira/browse/FINERACT-959 ). The test 
> coverage one is very important for the community, we may look at 

Re: [Mifos-developer] fineract.dev CI/CD now always automatically deploys the latest Fineract develop branch

[Sendoro Juma]

Nice piece of work; 

Thanks a lot for the contribution.

---

On 2020-05-17 14:19, Michael Vorburger wrote:

> Hello everyone, 
> 
> I'm happy to share that https://www.fineract.dev now always automatically 
> updates itself from the very latest source code available on the develop 
> branch of Fineract! (I actually used to manually update it before.) 
> 
> New deployments take about 15' after any of our great committer merges Pull 
> Requests from you - our contributors. Something that is pretty cool is that 
> on https://demo.fineract.dev/fineract-provider/actuator/info anyone can now 
> actually see the exact Git commit revision that is currently running (this is 
> based on FINERACT-883 [1]). 
> 
> If you are curious about some of the technical details involved here behind 
> the scenes, 
> http://blog2.vorburger.ch/2020/05/fineractdev-cicd-from-github-to-google.html 
> may interest you. You can see one part of what my blog post describes in live 
> action on https://github.com/apache/fineract/actions - note the new "Deploy 
> to https://www.fineract.dev; workflow, driven by 
> https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml.
>  
> 
> Something perhaps worth pointing out here is that this is based on modern 
> cloud native CI/CD... to users, it's made to look like the "server" never 
> "stops". Incoming API HTTP traffic is transparently switched over from old to 
> new runtimes. So as you use fineract.dev [2], it's now entirely possible 
> that, following the merge of a Pull Request, in one instant you hit "old" 
> code, but your next API request hits "new" code that just got deployed! Cool, 
> right? 
> 
> I'm hoping this makes Fineract.dev even more useful to the community, and 
> will serve both as a showcase for the project, as well as be of value e.g. 
> for your QA. (Should you have an interest in a non-demo more stable hosted 
> instance of Apache Fineract, please reach out to me privately - I'm 
> interested in learning more about the need and expectations in this space.) 
> 
> Stay safe & keep hacking and contributing! 
> 
> Best, 
> M.
> ___
> Michael Vorburger
> http://www.vorburger.ch 
> Mifos-developer mailing list
> mifos-develo...@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
 

Links:
--
[1] https://issues.apache.org/jira/browse/FINERACT-883
[2] http://fineract.dev

Re: [Mifos-developer] Web-self-service app

[Sendoro Juma]

Dear Floyd,

Mifos has partners in many countries.

Please state your country and you can get support faster.



> On 30 Apr 2020, at 12:39, Floyd Nickson  wrote:
> 
> 
> Hello, am looking for someone who can deploy mifos web-self-service and 
> ensure that it's running.
> Mifos-developer mailing list
> mifos-develo...@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: Fineract JIRA: Assigning issues.

[Sendoro Juma]

+1

> On July 8, 2019 at 3:47 PM Myrle Krantz  wrote:
> 
> Hey Santosh,
> 
> We can adjust the workflow in Jira to reflect the need for QA.  It's not 
> necessary to assign to one specific person for QA, and it might discourage 
> others from joining in on that very important task.  A truck factor of 1 is a 
> bad thing for any project.
> 
> Santosh, would you be willing to help others learn to do QA as well?  
> Would the rest of y'all like me to edit our Jira workflow to make the QA step 
> an explicit part of it?
> 
> Best,
> Myrle
> 
> On Mon, Jul 8, 2019 at 2:20 PM Santosh Math 
> mailto:sant...@confluxtechnologies.com > 
> wrote:
> 
> > > Hi Awasum,
> > Whenever ticket is raised , it's assigned to developer/coder first 
> > so that he can get notification to work on it. Once it's 'Resolved' , then 
> > the same ticket is assigned QA so that QA person get notification that he 
> > can start QA on that. After QA , if the ticket is not properly resolved , 
> > then QA person will assign it back to developer with comments. If it is 
> > resolved, the QA person will close the ticket. 
> > Assigning a ticket is part of the workflow . There is nothing to do 
> > with taking credit or not. 
> > 
> > 
> > 
> > On Mon, Jul 8, 2019 at 3:54 PM Awasum Yannick  > mailto:awa...@apache.org > wrote:
> > 
> > > > > Hi Santosh,
> > > 
> > > Assigning an issue to you which has been fixed by another 
> > > person is not a good idea. People want to take credit for their work. 
> > > From this information we can know who to invite as committer and it be 
> > > part of their CV(just record).
> > > 
> > > Anyways, We do it via Github PRs. Should be a simpler way to 
> > > search and assign the right person who completed a task.
> > > 
> > > 
> > > On Mon, Jul 8, 2019 at 5:04 AM Santosh Math 
> > > mailto:sant...@confluxtechnologies.com > 
> > > wrote:
> > > 
> > > > > > > Hi Awasum,
> > > > If the issues are fixed/resolved , those tickets should 
> > > > be assigned to me. You can simply use filter . Go to Issues > Search 
> > > > for Issues . In next page , Select project as 'Apache Fineract' and 
> > > > select status , tick only 'Resolved'. It would list all the tickets 
> > > > which are in resolved status.
> > > > 
> > > > On Mon, Jul 8, 2019 at 3:07 AM Awasum Yannick 
> > > > mailto:awa...@apache.org > wrote:
> > > > 
> > > > > > > > > Hi All,
> > > > > 
> > > > > I wonder if we could make the process of 
> > > > > assigning an issue to someone other than yourself on Fineract JIRA?
> > > > > 
> > > > > There are cases where issues have been fixed in 
> > > > > the past and we need to assign that to the right person when closing 
> > > > > these issues...
> > > > > 
> > > > > Does anyone have an idea on what to do to make it 
> > > > > easy to search and assign anyone on Issues?
> > > > > 
> > > > > I noticed this a few times..
> > > > > 
> > > > > Thanks
> > > > > Awasum
> > > > > 
> > > > > > > > > 
> > > > 
> > > > --
> > > > Thanks & Regards
> > > >  
> > > > Santosh Math
> > > > QA Engineer
> > > > Conflux Technologies Pvt Ltd 
> > > > http://www.confluxtechnologies.com/
> > > > | Office: +91-080-41208662 | 
> > > >  
> > > > Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 
> > > > 1st Block, Bengaluru, Karnataka, 560043 INDIA
> > > > 
> > > > > > > 
> > > > > 
> > 
> > --
> > Thanks & Regards
> >  
> > Santosh Math
> > QA Engineer
> > Conflux Technologies Pvt Ltd http://www.confluxtechnologies.com/
> > | Office: +91-080-41208662 | 
> >  
> > Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, 
> > Bengaluru, Karnataka, 560043 INDIA
> > 
> > > 


 

Re: Fineract with PostgreSQL

[Sendoro Juma]

Dear Parth,


To my knowledge NO!


Regards

Sendoro

> On August 4, 2019 at 1:35 PM Parth Mangroliya  
> wrote:
> 
> Hi Devs,
> 
> Is PostgreSql is supported with Fineract ? I know that fineract-cn is 
> using postgresql. But not sure about Fineract project.
> 
> --
> Regards,
> Parth Mangroliya
> Developer
> 
> 
> The information contained herein (including attachments) is confidential 
> and is intended solely for the addressee(s). If you have erroneously received 
> this message, please notify the sender immediately and delete this message. 
> If you are not the Intended recipient, you are hereby notified that any 
> disclosure, copying or distribution of this message or any accompanying 
> document is strictly prohibited and is unlawful. Kuliza Technologies Pvt Ltd 
> is not responsible for any damage caused by a virus or Alteration of the 
> e-mail by a third party or otherwise. Views or opinions in this email are not 
> necessarily those of Kuliza Technologies Pvt Ltd.http://www.kuliza.com
> 

Re: Frequently Asked Questions (FAQ) as of May 14, 2019

[Sendoro Juma]

+1


> On May 14, 2019 at 11:16 PM James Dailey  wrote:
> 
> 
> Hi all - Please note recent changes and updates to the project FAQ.
> If you see any issues with this, please let me know, make a comment on 
> that page: 
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ 
> 
> I'm including it here in the hopes it gets a few more reads. 
> 
> Thanks 
> @jdailey67 
> 
> 
> Fineract FAQ https://cwiki.apache.org/confluence/display/FINERACT/FAQ
>  
>  
> 
>  
> * What is this project about?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-Whatisthisprojectabout?
> * Is this Mifos?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-IsthisMifos?
> * What is the difference between Fineract and Fineract-CN?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-WhatisthedifferencebetweenFineractandFineract-CN?
> * Do I have to get the code to use the solution?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-DoIhavetogetthecodetousethesolution?
> * What is the process for getting the code and setting up a 
> development environment?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-Whatistheprocessforgettingthecodeandsettingupadevelopmentenvironment?
> * How do I get up to speed on development tasks?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-HowdoIgetuptospeedondevelopmenttasks?
> * What is our Consensus approach?   
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-WhatisourConsensusapproach?
> * I'm new to Open Source, what is this all about?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-I'mnewtoOpenSource,whatisthisallabout?
> * Where do I find   
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-WheredoIfind
> * Where do I get the Pentaho Reports?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-WheredoIgetthePentahoReports?
> * How do I set this up on my machine?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-HowdoIsetthisuponmymachine?
> * How do I get something changed in the code?  How do I get a feature 
> added?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-HowdoIgetsomethingchangedinthecode?HowdoIgetafeatureadded?
> * I have a great idea for a collaboration tool for the community, how 
> do I make that happen? 
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-Ihaveagreatideaforacollaborationtoolforthecommunity,howdoImakethathappen?
> * I represent a Company and want to contribute, how do I do that?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-IrepresentaCompanyandwanttocontribute,howdoIdothat?
> * I found a security flaw, where do I report that?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-Ifoundasecurityflaw,wheredoIreportthat?
> * How do I raise a difficult or sensitive topic?  
> https://cwiki.apache.org/confluence/display/FINERACT/FAQ#FAQ-HowdoIraiseadifficultorsensitivetopic?
> 
>  
> 
> 
> 
> 
> What is this project about? 
> 
> Fineract provides a reliable, robust, and affordable solution for 
> entrepreneurs, financial institutions, and service providers to offer 
> financial services to the world’s 2 billion underbanked and unbanked. 
> Fineract is aimed at innovative mobile and cloud-based solutions, and enables 
> digital transaction accounts for all.  
> 
> The domain of fineract includes accounts, held by customers, with 
> transactions made to those accounts. The types of accounts include credit 
> accounts (e.g. loans to customers) and debit accounts (current accounts and 
> savings accounts), and for credit accounts there are different kinds of 
> interest rate schemes or shared profit schemes.  There is other functionality 
> that supports use cases for teller operations, basic treasury management, 
> accounting, portfolio management, authentication, account opening (including 
> KYC), and similar topics that are common to a retail banking operation.  
> 
> Initially aimed at Microfinance Institutions (MFIs), Savings 
> Cooperatives, and Credit Unions, the fineract solution is not limited to 
> those specific institutions.  A number of finTech innovators have used 
> fineract as their backend solution for offering "Direct Banking" or 
> "Neo-Banking" solutions as well as for "Agent Management" in some contexts. 
> The backend account transaction system is a common requirement in many 
> systems in financial services. 
> 
> Fineract was donated by Mifos.org, a US based charity with a financial 
> inclusion mission. While many members of the PMC trace their involvement to 
> the project to financial inclusion, the intent of the project is to attract a 
> range of innovators involved in offering account services to consumers 
> everywhere. 

Re: [ANNOUNCE] Welcome Isaac Kamga as a Fineract PMC Member

[Sendoro Juma]

Congrats to Isacc

> On May 5, 2019 at 5:06 PM Awasum Yannick  wrote:
> 
> Hi All,
> 
> I am happy to announce that Isaac Kamga has been voted in as a Fineract 
> PMC member.
> 
> Isaac has been a part of our community for over 18 months now and in that 
> time he has contributed invaluably to our project. He documented an initial 
> user manual for Fineract CN, carried out webinars to educate people on how to 
> develop on Fineract CN and is helping to reduce barrier of entry for new 
> developers on Fineract CN.
> 
> Isaac also documented the Fineract CN API last year, mentored GSoC 2018 
> and will be doing the same work this coming GSoC. He has been leading efforts 
> to make Fineract CN Apache compliant and moving us closer to a first release 
> by replacing MySQL with PostgreSQL.
> 
> Isaac has shown true leadership skills over the past few months.
> 
> Please join me in welcoming Isaac in his new role as a PMC Member.
> 
> 
> Thanks.
> Awasum Yannick,
> PMC Member, Apache Fineract
> 


 

Re: FAQ on Wiki, structure of wiki

[Sendoro Juma]

+1

> On February 28, 2019 at 2:51 AM James Dailey  wrote:
>
>
> Devs -
>
> I have noted a number of emails from people with basic questions about the
> project and have tried to collate those into a FAQ. Please see my changes
> to https://cwiki.apache.org/confluence/display/FINERACT/FAQ. If you
> object, either respond to this email or make comments on the page itself.
>
> As previously communicated I am also thinking we need to change the
> structure of the navigation for the project - the left side "Page Tree" at
> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home ; While
> it is now familiar to many of us, to a new person I think it remains very
> confusing.
>
> @Myrle Krantz  please suggest if this is something you'd
> like to collaborate on...
> The structure I think should follow this with other content below these two
> top levels:
>
> 1. Getting Involved & Community Norms
> 1. Getting Started
> 2. PMC reports
> 3. Contributors & Committers
> 4. How To Articles
> 2. Fineract
> 1. Roadmap
> 2. Releases
> 3. Getting started (pull out specifics to Fineract1.x)
> 4. Functional specs
> 5. User Zones
> 3. Fineract CN
> 1. Roadmap
> 2. Releases
> 3. Getting started (pull out specifics to Fineract-CN)
> 4. Functional specs
> 5. User Zones
> 4. Blog & Outbound Communications
> 1. Presentations Given
> 2. Speech text
> 5. FAQ

Re: LDAP Integration

[Sendoro Juma]

+1

Looking forward for  your results.

> On February 25, 2019 at 9:37 PM Mauricio Ghiorzi 
>  wrote:
> 
> Hi community,
> 
> I'm looking for an LDAP integration in Fineract. Anyone has developed 
> something similar? If not, I can take the challenge.
> 
> Regards
> 
>  
> 
> [Imágenes integradas 2]
> 
> Mauricio Ghiorzi -  Software Engineer
> Av. del Libertador 2442, Piso 2, CP 1636, Olivos
> Buenos Aires, Argentina -  Tel.: +54911 5046 6624
> 
> www.wenance.com http://www.wenance.com/
> 
>  
> 

Re: Identity and Fineract

[Sendoro Juma]

+1 

1. KYC | AML| CFT is FUNDAMENTAL/MUST HAVE
2. Mifos/Fineract should rely on External Identity-Claim Services


The above are very strategic point that must be worked on.


Please go ahead with with Wiki Page.


Cheers

Sendoro


> 
> On February 10, 2019 at 3:03 AM James Dailey  
> wrote:
> 
> I'd like to raise this important issue again. We are in the space of
> financial services, and so we must express kyc/aml/cft regulations.
> 
> Know Your Customer is a FUNDAMENTAL banking concept. It is currently
> supported via account opening in fineract but more needs to be done.
> 
> We must also address the opportunity and the gap in formal identity if we
> are to be a serious player in financial inclusion. I don't believe 
> fineract
> or mifos should do that function directly, but rather be able to speak to
> various identity/claims services.
> 
> At times a mifos implementation will have the best information about a
> specific customer. This also relates to credit bureaus and again, the
> concept of 'identity-claims'.
> 
> I'd like to suggest that we get a wiki page and then some detailed
> requirements going and develop some ticket. But, looking for someone to
> support this in coding and someone else who has a need now for this
> functionality.
> 
> Jdailey67
> 
> On Thu, Sep 13, 2018, 10:28 AM Ed Cable  
> > > 
> > James,
> > 
> > Thanks for starting up this topic on-list (I only just saw it now 
> > upon
> > Isaac's reply). I will try to forwards this along to others who 
> > have been
> > conversing on related topics of eKYC, verification via selfies, 
> > etc. I will
> > also get some of my volunteers assisting on the AML/CFT front 
> > involved in
> > this thread.
> > 
> > Thank you also for bringing up our conversations with the INDY at 
> > OSCON, I
> > will re-engage with Joyce so we can carry forward the conversations 
> > we
> > started there.
> > 
> > The discussion around identity and looking at claim-based systems 
> > and
> > decentralized identities are all the more relevant as systems like 
> > Aadhar
> > continue to get hacked and sensitive data gets exposed:
> > 
> > 
> > https://www.huffingtonpost.in/2018/09/11/uidai-s-aadhaar-software-hacked-id-database-compromised-experts-confirm_a_23522472/
> > 
> > See some additional replies inline.
> > 
> > On Mon, Sep 10, 2018 at 11:31 AM James Dailey 
> > 
> > wrote:
> > 
> > > > > 
> > > Hi Devs -
> > > 
> > > I'd like to raise an issue with regard to how Fineract 1.x 
> > > and the new
> > > Fineract-CN treats the concept of Identity.
> > > 
> > > I was recently looking at Isaac's work on
> > > 
> > > 
> > > https://github.com/apache/fineract-cn-customer/pull/7/commits/65a88b9879a46103fae440c42d1b0058909a93aa
> > > .
> > > It got me thinking... I was unclear if the tests are fully 
> > > covering our
> > > functionality, and wonder about how we are collectively 
> > > thinking about
> > > identity.
> > > 
> > > So, there has been a lot of work done recently on Digital 
> > > Identity and
> > > Credentials globally. I think we should have as part of our 
> > > thinking and
> > > structure of the identity service:
> > > 
> > > > > 
> > For these components and sub-components of Identity you are 
> > starting to
> > flesh out below, it'd be great to synthesize into a 
> > requirements/spec doc
> > on the. Fineract wiki.
> > 
> > >
> > 
> > > > >1. Issuing authority (this could be any 
> > relevant civil authority such
> > >   as
> > >   Federal Government, State Department, Provincial 
> > > Gov't), any private
> > >   or
> > >   non-profit but recognized entity (e.g. University), and 
> > > also any
> > >   commercial
> > >   entity that has a pre-existing relationship including 
> > > Bank, Mobile
> > >   Provider, Microfinance Entity, or even 
> > > Facebook/WeChat/Alibaba.
> > >   When dealing with the unbanked, or underbanked, a form 
> > > of digital
> > >   identity may be self-issued or issued on the spot, and 
> > > be trusted up
> > >   to
> > >   a
> > >   point (see KYC below).
> > > 
> > >2. Credentials and Forms of verification - this could be a 
> > > separate
> > >   concept in Fineract of [one to many] relationship where 
> > > Fineract CN
> > >   stores
> > >   that information or simply notes that multiple sources 
> > > of verification
> > >

Re: [ANNOUNCE] Apache Fineract Committer Sanyam Goel

[Sendoro Juma]

Excellent contribution Sanyam Goel.

Keep the good work.

> 
> On February 9, 2019 at 7:15 PM Ed Cable  wrote:
> 
> Hello Fineract community,
> 
> It is my pleasure to announce Sanyam Goel as our latest Apache Fineract
> committer.
> 
> Congrats Sanyam and thank you for your contributions thus far.
> 
> Sanyam is based out of Delhi and has been contributing to Fineract
> extensively as a GSOC intern and beyond through both the Swagger/OpenAPI
> project as well as his work on a payment gateway. Sanyam has also been a
> faithful mentor for GCI helping to shepherd new contributors to Fineract.
> 
> Join in giving a shout out to our newest committer, Sanyam!
> 
> Cheers,
> 
> Ed Cable
> PMC Member, Apache Fineract
> 


 

Re: Introduction to the Community

[Sendoro Juma]

Welcome Michael.


> 
> On February 6, 2019 at 9:10 AM Suleiman Omeiza Michael 
>  wrote:
> 
> Hello Everyone,
> 
> I am Michael Suleiman.
> 
> I am currently enrolled in a computing degree program at the African
> Leadership University in Mauritius.
> Although I have been in the community for a while now, this is my official
> introduction because I thought I needed to learn to work with the Spring
> framework before anything else.
> I am very comfortable with both Java and JavaScript and at a lower level
> intermediate level with Spring now. In the short term, I am hoping to
> participate in the Google Summer of Code program. However, I am hoping to
> remain an active member of this community in the long term.
> 
> Looking forward to interacting with you all!
> 
> Kind regards
> 

commit for FINERACT-52 (Null value not handled in 'ClientWritePlatformServiceJpaRepositoryImpl.CloseClient' date comparison) #176

[Sendoro Juma]

Devs,


Anyone to continue from where this ended?

https://github.com/apache/fineract/pull/176


Regards
Sendoro

Re: FINERACT-38: Period Close feature where inc & exp booked to retained earnings account

[Sendoro Juma]

Hello Robert,

Any response related to test data for regression testing?


> 
> On February 1, 2019 at 7:14 PM James Dailey  
> wrote:
> 
> I've looked at the ticket. This looks like a good enhancement and has been
> delayed since Nov, with January being the month that many organizations
> attempt to do year end closing. +1 to boost its importance.
> 
> Is there a set of test data for this to make sure it does what is
> expected? I am looking at the 39 files changed and don't see a test set
> there.
> 
> This seems significant enough of a change to make sure a) that a 
> regression
> test exists and b) that the behavior is demonstrated as expected
> 
> @jdailey67
> 
> On Sun, Jan 27, 2019 at 9:02 PM Santosh Math <
> sant...@confluxtechnologies.com> wrote:
> 
> > > 
> > +Avik Ganguly 
> > 
> > On Mon, Jan 28, 2019 at 3:28 AM Sendoro Juma  
> > wrote:
> > 
> > > > > 
> > > Devs,
> > > 
> > > What is the status of this key issue that has been raised by 
> > > Ippez,
> > > 
> > > Can we prioritize on it?
> > > 
> > > https://issues.apache.org/jira/browse/FINERACT-38
> > > 
> > > https://github.com/apache/fineract/pull/429
> > > 
> > > Thanks a lot in advance by responding to Ippez for inclusion 
> > > in our next
> > > release.
> > > 
> > > Regards
> > > 
> > > Sendoro
> > > 
> > > > > 
> > --
> > Thanks & Regards
> > 
> > Santosh Math
> > 
> > *QA Engineer*
> > 
> > *Conflux Technologies Pvt Ltd <http://www.confluxtechnologies.com/>*
> > | *Office*: +91-080-41208662 |
> > 
> > *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> > Bengaluru, Karnataka, 560043 INDIA
> > 
> > > 

FINERACT-38: Period Close feature where inc & exp booked to retained earnings account

[Sendoro Juma]

Devs,


What is the status of this key issue that has been raised by Ippez,


Can we prioritize on it?


https://issues.apache.org/jira/browse/FINERACT-38

https://github.com/apache/fineract/pull/429


Thanks a lot in advance by responding to Ippez for inclusion in our next 
release.


Regards

Sendoro

Re: Fineract PMC Chair change: Congratulations Vishwas!

[Sendoro Juma]

Congrats Vishwas

> 
> On December 20, 2018 at 2:54 PM Myrle Krantz  wrote:
> 
> Hello all,
> 
> I am ready to pass on the role of Fineract PMC chair.
> 
> I believe that a regular change of PMC chair will help to increase
> community empowerment, and develop skills among the Fineract PMC members. 
> I
> am looking forward to having more time for my other roles. I continue to
> be part of Fineract as a committer and PMC member.
> 
> The Fineract PMC has elected Vishwas Babu as my successor. The ASF board
> has approved his appointment. Vishwas is an excellent choice. Vishwas has
> been involved with Fineract for longer than I have, and has a deep
> knowledge of Fineract community dynamics.
> 
> Please congratulate Vishwas, and please support him as he serves our
> community in this new role.
> 
> Best Regards,
> Myrle
> V.P. Emeritus, Apache Fineract
> 


 

Re: Planning the Fineract 1.3 Release

[Sendoro Juma]

+1

> 
> On December 11, 2018 at 8:09 PM Ed Cable  wrote:
> 
> Hi all,
> 
> This to continue the discussion on the planning of the 1.3 release. With
> the slight delays in 1.2, we're a little more than a week behind schedule
> for 1.3. The wiki page (
> 
> https://cwiki.apache.org/confluence/display/FINERACT/1.3.0+-+Apache+Fineract)
> has been updated with the new schedule to reflect the following:
> 
> QA: Dec 14 - 26
> Publish Release Notes: Dec 26
> Vote on Release: Jan 1
> Target Release Date: Jan 7
> 
> The list of tickets that are ready to be merged or currently under
> development has been updated at 1.3.0. No additional tickets will be added
> to the scope of the 1.3.0 release - any new contributions that get raised
> will be targeted for the 1.4.0 release.
> 
> Some of the enhancements to be included include the GSIM and GLIM work led
> by Nikil, performance enhancements including parallelization of batch jobs
> led by Kumaranath, and the notifications framework done previously by
> Courage.
> 
> *Help the community out and build merit!*
> P1 bugs that couldn't be addressed during this release cycle have been
> tagged with 1.4.0 fix version. We welcome any volunteer contributors to
> work on some of these P1 issues.
> 
> Once again, I ask that if you have a contribution that you've worked on or
> would like to make, please begin discussing it on-list so we can aim to 
> get
> it into 1.4.0.
> 
> The planned cutoff date for new features going into 1.4.0 is January 7. 
> See
> more details at
> 
> https://cwiki.apache.org/confluence/display/FINERACT/1.4.0+-+Apache+Fineract
> 
> On Wed, Nov 21, 2018 at 9:56 AM Ed Cable  wrote:
> 
> > > 
> > Hello Community,
> > 
> > Earlier in the year we discussed and adopted a schedule for 
> > targeting
> > monthly releases. We're going to try and achieve that with the 
> > forthcoming
> > 1.3 release.
> > 
> > This email hearby kicks off the planning process for the Fineract 
> > 1.3
> > release. I've included the table discussing what is occurring at 
> > each phase
> > and how it differed from our previous processes.
> > 
> > So between now and November 30, on this email thread and in JIRA 
> > and the
> > release planning page, I want any individuals in the community 
> > whether
> > you're a volunteer, an intern, or a partner that's built out 
> > functionality,
> > to discuss and share if you have code that you would like to and 
> > think it'd
> > be ready to contribute for the 1.3 release.
> > 
> > The code should be near complete at this stage so if you do have a
> > contribute you want to make but it's still in progress, that can be
> > targeted for a future release, i.e. 1.4
> > 
> > Please discuss on this thread, add to this wiki page or open and tag
> > tickets with the release fix version of 1.3.0
> > 
> > Release Page on Wiki:
> > 
> > https://cwiki.apache.org/confluence/display/FINERACT/1.3.0+-+Apache+Fineract
> > JIRA Filter for Issues Tagged 1.3.0:
> > https://issues.apache.org/jira/issues/?filter=12345265
> > 
> > Plans for Release Apache Fineract 1.3
> > 
> > Planning Release - Start Discussion on November 21
> > 
> > Announce Release - Nov 30
> > 
> > QA - Nov 30 - Dec 14
> > 
> > Publish Release Notes - December 14
> > 
> > Vote on Release - December 21
> > 
> > Target release date - December 28
> > 
> > Stage
> > 
> > Description
> > 
> > Proposed Length
> > 
> > How Far in Advance of Release (Proposed)
> > 
> > How Far in Advance of Release (Currently)
> > 
> > Planning of Next Release
> > 
> > Discuss with community what would like to ship in next release and 
> > what
> > people could work on.
> > 
> > Create fix version on JIRA to assign to.
> > 
> > Action: modify existing email template to open up planning process,
> > schedule a meeting to discuss and set a tentative branching date 
> > (i.e. 2
> > weeks later, if release date is a month past that).
> > 
> > .
> > 
> > 1 week
> > 
> > 6 weeks
> > 
> > Doesn’t Exist
> > 
> > Announcement of Release
> > 
> > Announce what is going to come in the release (should be 80% done at
> > least).
> > 
> > Cut a release branch and freeze release branch and then develop 
> > branch
> > can still have active work on it but only in rare cases might 
> > anything
> > additional from develop
> > 
> > Email out sharing release branch details
> > 
> > 4 weeks prior
> > 
> > 1 - 2 months
> > 
> > QA
> > 
> > QA begins on the release branch - 

Re: [ANNOUNCE] Apache Fineract 1.2.0 Release

[Sendoro Juma]

 Dear Shruthi, Devs,


Congrats for job well done... 


Now looking forward for  v1.3.0



> 
> On December 8, 2018 at 1:22 PM Shruthi M R  
> wrote:
> 
> Hi all,
> The Apache Fineract team would like to announce the release of Apache
> Fineract 1.2.0 with source and binary artifacts.
> Apache Fineract is an open source system for core banking as a
> platform. Fineract provides a reliable, robust, and affordable
> solution for entrepreneurs,
> financial institutions, and service providers to offer financial
> services to the world’s 2 billion under banked and unbanked.
> 
> More details regarding Apache Fineract can be found at
> http://fineract.apache.org/
> The release artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/release/fineract/
> The release notes can be found here:
> 
> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract
> 
> Thanks!
> The Apache Fineract Team
> 


 Thanks

Re: [VOTE] APACHE FINERACT 1.2.0 Gentle reminder

[Sendoro Juma]

Dear Ippez,


Not sure if you meant this

https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract

> On December 4, 2018 at 10:47 AM Ippez Robert  wrote:
> 
> +1
> Shruthi M R, Please point us to the list of new features and enhancements 
> in this release. Thank you
> 
> On Tue, Dec 4, 2018 at 10:44 AM Mexina Daniel  wrote:
> 
> > > 
> > +1
> > 
> > > > > 
> > > On December 4, 2018 at 1:07 PM Shruthi M R 
> > > mailto:shru...@confluxtechnologies.com > 
> > > wrote:
> > > 
> > > Hello Fineract community,
> > > 
> > > Kindly vote.
> > > 
> > > Thank You,
> > > 
> > > *Shruthi M R*
> > > Skype: Shruthi Rajaram | Mobile: +91-8277012716
> > > 
> > > On Fri, Nov 30, 2018 at 5:25 PM Shruthi M R 
> > > mailto:shru...@confluxtechnologies.com >
> > > wrote:
> > > 
> > > > > > > 
> > > > Hello Fineract community,
> > > > 
> > > > We have created the Apache Fineract 1.2.0 release, with 
> > > > the artifacts
> > > > below up for a vote.
> > > > 
> > > > These are the goals of this release:
> > > > 
> > > > * Share the new features and bug fixes that have 
> > > > been developed so far
> > > >   by external contributors, the community engineer, 
> > > > and previous GSOC
> > > >   interns
> > > > 
> > > > *For more information including release notes, please 
> > > > see:*
> > > > 
> > > > *https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract
> > > > 
> > > > *
> > > > 
> > > > *Source & Binary files:*
> > > > *https://dist.apache.org/repos/dist/dev/fineract/1.2.0/
> > > > 
> > > > *
> > > > Source:
> > > > 
> > > > 
> > > > https://dist.apache.org/repos/dist/dev/fineract/1.2.0/apache-fineract-1.2.0-src.tar.gz
> > > > 
> > > > 
> > > > 
> > > > Binary/War :
> > > > 
> > > > 
> > > > https://dist.apache.org/repos/dist/dev/fineract/1.2.0/apache-fineract-1.2.0-binary.tar.gz
> > > > 
> > > > *Commit to be voted on:*
> > > > https://github.com/apache/fineract/commits/1.2.0
> > > > 
> > > > *Source build verification steps can be found at:*
> > > > Refer 'README.md' in apache-fineract-1.2.0-src.tar.gz
> > > > 
> > > > *Binary Deployment steps can be found at:*
> > > > 
> > > > 
> > > > https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Installation+on+Ubuntu+Server
> > > > 
> > > > *KEYS file containing PGP Keys we use to sign the 
> > > > release: *
> > > > https://dist.apache.org/repos/dist/dev/fineract/KEYS
> > > > 
> > > > Vote will be open for 72 hours.
> > > > 
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove (and reason why)
> > > > 
> > > > Let me know if there are any discrepancies in the 
> > > > signing process.
> > > > 
> > > > Here's my +1
> > > > 
> > > > Thank You,
> > > > 
> > > > *Shruthi M R*
> > > > Skype: Shruthi Rajaram | Mobile: +91-8277012716
> > > > 
> > > > > > > 
> > > > > 
> > 
> > Mexina Daniel
> > 
> > Singo Africa Limited
> > Block G, Mbezi Beach B | 7 Nakawale Road | P.O BOX 78908 | 14121 
> > Dar es
> > salaam
> > 
> > +255 71 211 0791 | +255 22 261 8511
> > 
> > amala.co.tz https://amala.co.tz/  | singo.africa 
> > https://singo.africa
> > 
> >  
> > 
> > > 
> 
> --
> Ippez Roberts
> Founder/C.E.O - Swift3 Technologies (U) Ltd
> "Redefining Next Generation I/O Systems"
> P.O.Box 155, Moyo
> UGANDA.
> Tel: +256777421862/775686538
> Skype ID: ippez.robert1
> Email: ippezrob...@gmail.com mailto:ippezrob...@gmail.com
> 


 

Re: [VOTE] APACHE FINERACT 1.2.0

[Sendoro Juma]

+1 

However, timing of this not correct this 72 hrs will be almost finish 
during weekends...  where some people may be not touching their computers :)

> 
> On November 30, 2018 at 2:55 PM Shruthi M R 
>  wrote:
> 
> Hello Fineract community,
> 
> We have created the Apache Fineract 1.2.0 release, with the artifacts 
> below
> up for a vote.
> 
> These are the goals of this release:
> 
> * Share the new features and bug fixes that have been developed so far
>   by external contributors, the community engineer, and previous GSOC
>   interns
> 
> *For more information including release notes, please see:*
> 
> *https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract
> 
> *
> 
> *Source & Binary files:*
> *https://dist.apache.org/repos/dist/dev/fineract/1.2.0/
> *
> Source:
> 
> https://dist.apache.org/repos/dist/dev/fineract/1.2.0/apache-fineract-1.2.0-src.tar.gz
> 
> 
> 
> Binary/War :
> 
> https://dist.apache.org/repos/dist/dev/fineract/1.2.0/apache-fineract-1.2.0-binary.tar.gz
> 
> *Commit to be voted on:*
> https://github.com/apache/fineract/commits/1.2.0
> 
> *Source build verification steps can be found at:*
> Refer 'README.md' in apache-fineract-1.2.0-src.tar.gz
> 
> *Binary Deployment steps can be found at:*
> 
> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Installation+on+Ubuntu+Server
> 
> *KEYS file containing PGP Keys we use to sign the release: *
> https://dist.apache.org/repos/dist/dev/fineract/KEYS
> 
> Vote will be open for 72 hours.
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> Let me know if there are any discrepancies in the signing process.
> 
> Here's my +1
> 
> Thank You,
> 
> *Shruthi M R*
> Skype: Shruthi Rajaram | Mobile: +91-8277012716
> 


 

Re: [ANNOUNCE] Apache Fineract Committer Mark van Veen

[Sendoro Juma]

Hello Mark,



Excellent contribution and keep the sprit... you never know the impact you are 
doing to the rest of the world.


Congrats


Regards

Sendoro

> 
> On November 20, 2018 at 12:03 PM Myrle Krantz  wrote:
> 
> Hello Fantastic Fineracters,
> 
> I'm proud to announce another Apache Fineract committer!
> 
> Congratulations Mark van Veen, and thank you for joining us.
> 
> Mark is a Software Engineer at Kuelap. He wrote the initial code for the
> fims web app on Fineract CN. He has contributed conceptually to most of
> the CN services as well. Mark and I have been colleagues at two different
> companies, and I have always enjoyed working with him.
> 
> Thanks,
> Myrle Krantz
> PMC Member, Apache Fineract
> 


 

Re: [GitHub] Ippezrobert commented on issue #429: EOY-Closure: FINERACT-38

[Sendoro Juma]

+1

> On November 9, 2018 at 2:43 PM GitBox  wrote:
> 
> 
> Ippezrobert commented on issue #429: EOY-Closure: FINERACT-38
> URL: https://github.com/apache/fineract/pull/429#issuecomment-437335756
>  
>  
>@avikganguly01 , @ShruthiRajaram, @raakeshtomarnew, @nazeer1100126, Ed 
> Cable and others, is it possible to review this and make it as part of the 
> next release since people are nearing end of year where expenses and income 
> have to be booked-off for beginning of year. The Front-end has not been 
> developed so someone good at front-end dev can take on it. Thanks
> 
> 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on GitHub and use the
> URL above to go to the specific comment.
>  
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> 
> 
> With regards,
> Apache Git Services

With Best Regards

Sendoro Juma

---

SingoAfrica Limited
Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.

P.O BOX 78908 | 14121 Dar es Salaam

info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz

Re: [ANNOUNCE] New Apache Fineract PMC Member Mexina Daniel

[Sendoro Juma]

Dear Mexina,


Congrats and wish you all the best in serving  the  Apache Fineract community 
and PMC in the best way possible!


Impossible is Nothing

> 
> On November 6, 2018 at 12:16 PM Myrle Krantz  wrote:
> 
> Please join me in welcoming Mexina Daniel as the newest member of our
> Project Management Committee.
> 
> Mexina has been contributing to the Fineract community since 2016, and is 
> a
> value member of our community. She's been enthusiastic about moving
> Fineract 1.x releasing forward. She let's us know when we need to improve
> things.
> 
> Welcome Mexina. I'm really glad you're on board.
> 
> Best Regards,
> Myrle Krantz
> V.P., Apache Fineract
> 

RE: Why are large code drops damaging to a community?

[Sendoro Juma]

+1

> 
> On October 19, 2018 at 4:18 AM r...@gardler.org wrote:
> 
> +1 to both Shane and Myrle's input here.
> 
> The Apache Way is all about consensus building in order to maximize the 
> potential for collaboration between partners. It is impossible to drive 
> consensus within a community of individuals without enabling them to be a 
> part of the whole process. Large code drops equate to a statement of "this is 
> the way it is - my way or the highway". It is not a model for consensus 
> building.
> 
> However, there are other models in which vendors define direction. Shane 
> refers to these as "maintainer led" but I think that is too general, I prefer 
> the more specific vendor led, because it is possible to have a consensus 
> driven maintainer led project.
> 
> Vendor led and the Apache Way are different models. One scales the 
> community very well (Apache Way) and is ideal for building frameworks and/or 
> components from which products are built. The other (vendor led) doesn't 
> scale so well but is ideal for building highly focused products. The Apache 
> Way maximizes the opportunity for cross-organizational collaboration and thus 
> drives combinatorial innovation. Vendor led limits the scope of the 
> collaboration but allows one to target a more clearly defined customer base.
> 
> The trick to success is ensuring that you are using the right model for 
> the right parts of the open source ecosystem. There is no single model for 
> governance of open source, success comes from understand when and how to 
> apply different models to different parts of your software solution.
> 
> Ross
> 
> -Original Message-
> From: Shane Curcuru 
> Sent: Thursday, October 18, 2018 8:26 PM
> To: Apache Community Development ; Apache 
> Fineract Dev 
> Subject: Re: Why are large code drops damaging to a community?
> 
> Myrle Krantz wrote on 10/18/18 7:18 AM:
> 
> > > 
> > Hey all,
> > 
> > There are many forms of offlist development. One form of offlist
> > development is working on large code drops in private and then
> > contributing them all at once. Threshold size is probably arguable,
> > and varies by project; put that aside for the moment. I've been
> > working on an explanation of how large code drops damage community 
> > and
> > code. I'd love to hear your feedback. I'm including my project and
> > the dev@community list in the hopes that people from other projects
> > also have a perspective. Here it goes:
> > 
> > > 
> Thanks Myrle for an excellent writeup, including details of how large 
> code drops harm Apache style open communities. This is a great set of 
> examples showing the "why" behind the ASF's requirement that the whole 
> community be allowed to participate in *all* parts of a project's technical 
> development.
> 
> The requirement for an open and consensus-driven development process at 
> the ASF doesn't just impact the individual perspective - which you've covered 
> in detail in your post. More importantly, it impacts the whole
> *community* ownership feeling of an Apache project.
> 
> This is a key difference I see between Apache projects and maintainer-led 
> projects. There are many examples of maintainer projects with issues, 
> successes, whatever. But they primarily focus on how a handful of maintainers 
> are struggling to keep their project growing for the benefit of all their 
> users.
> 
> The issue is the mindset of "maintainers". An Apache project should have 
> the entire community of contributors feeling like they have a stake in the 
> project, that they can help build new ideas, and that they
> *share* as a whole group the direction of the project. While much of the 
> actions are the same, my point is about the feeling of ownership.
> It's not just a few "maintainers" driving things; it's *everyone* who's a 
> committer (and hopefully soon, many of the contributors who get voted in).
> 
> Offlist development prevents this truly shared sense of ownership from 
> developing, which is why it's prohibited for Apache projects.
> 
> ...snip...
> 
> > > 
> > Open source projects require transparency, not just as a moral 
> > value,
> > but as a pragmatic prerequisite for collaboration. Offlist
> > development damages the community *and* the code.
> > 
> > > 
> More to the point, repeated significant offlist development will attract 
> the attention of the ASF board, which may well take direct action to prevent 
> that kind of behavior from happening going forward. One advantage of the 
> ASF's independent governance is that it can enforce the core open development 
> model that's a key part of the Apache Way.
> 
> Note that I'm struggling to find where "offlist development is forbidden" 
> is explicitly called out on the apache.org website, so 

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

[Sendoro Juma]

+1

> On October 17, 2018 at 8:06 PM James Dailey  wrote:
>
>
> Hi Myrle -
>
> I think the focus on a MVP (minimum viable product) is ideal. My list of
> functionality in the email thread here was focused on that - although happy
> to debate which are real MVP and which are nice to have (NTH). I know you
> are focused on the building blocks on up and I am focused on the
> customer/user experience, there will be some misses.
>
> @Isaac - I'm happy to add my list with modification to the wiki. I'll do
> so unless someone objects. (lazy consensus hereby called...24 hrs)
>
> And given that the topic here is a ROADMAP, I would suggest that we have a
> time-line or prioritization aspect to this that is documented on the wiki
> page. This gives focus to the areas of development that are needed first,
> second, third, etc.
>
> I strongly +1 the idea the first MVP release is not going to be
> functionally equiv to fineract1.x. It should however, point the way to
> that and other configurations - like a mobile money wallet or a credit
> union or MFB on the roadmap.
>
> +1 on "the minimal release should be based on what exists already"
>
> ~jdailey
>
>
> On Wed, Oct 17, 2018 at 7:28 AM Myrle Krantz  wrote:
>
> > Hey all,
> >
> > Here's an alternative suggestion that I've been toying with: we could make
> > our first release consist of just identity, provisioner, organization,
> > accounting, customer, notifications, and of course fims-web-app and the
> > supporting libraries. These pieces are enough to build a payment app on
> > top of but not enough to run a credit union or an MFI off of.
> >
> > By reducing the "surface area", we'd make it easier to test and get to our
> > first release. We could then pick and choose where to go from there.
> >
> > What do you think?
> >
> > Best Regards,
> > Myrle
> >
> >
> > On Tue, Oct 16, 2018 at 12:03 AM Ed Cable  wrote:
> >
> > > Isaac,
> > >
> > > Have you or Awasum starting looking into Section A any deeper - the
> > > elimination of Category X dependencies?
> > >
> > > Thanks,
> > >
> > > Ed
> > >
> > > On Mon, Oct 15, 2018 at 2:50 PM Isaac Kamga 
> > wrote:
> > >
> > >> Hello everyone,
> > >>
> > >> Thanks for your feedback Ed...it was very helpful.
> > >>
> > >> James, please could you edit the requirements you're suggesting into
> > >> the Community
> > >> roadmap
> > >> <
> > >>
> > https://cwiki.apache.org/confluence/display/FINERACT/Apache+Fineract+CN+Community+Roadmap
> > >> >
> > >> .
> > >>
> > >> I'd like to encourage the community to add items to the roadmap so that
> > we
> > >> move towards an initial release of Fineract CN.
> > >>
> > >> Given that some developers are working on issues on Fineract CN, I
> > suggest
> > >> we strike the items through ( like this strikethrough ) which have been
> > >> closed on JIRA as I've started doing.
> > >>
> > >> Cheers,
> > >> Isaac Kamga.
> > >>
> > >> On Wed, Jul 25, 2018 at 6:49 PM James Dailey 
> > >> wrote:
> > >>
> > >> > Hi - I would like to suggest some key high level functional criteria
> > >> for
> > >> > the formal release of Fineract-CN:
> > >> >
> > >> > 1. Use case orientation - that specific end-user roles and the
> > steps
> > >> > that the end-user takes in interaction with Fineract-CN front end
> > are
> > >> > written in a style that allows for both "tests" and communication
> > of
> > >> the
> > >> > requirements. For example:
> > >> > 1. The User:BankStaff is able to login to see a recent history
> > of
> > >> all
> > >> > transactions by specific accounts, according to the permissions
> > >> that
> > >> > they
> > >> > have that mask certain transaction details.
> > >> > 2. The User:Customer is able to login to a see current balances
> > >> and
> > >> > recent activity on both debit and credit accounts with a total
> > >> > showing for
> > >> > all of their accounts.
> > >> > 3. The User:FieldAgent is able to login and see a list of
> > >> payments by
> > >> > individuals for whom they are assigned to.
> > >> > 4. and so on...
> > >> >
> > >> > 2. That security and configuration guides be included in the
> > >> thinking
> > >> > from the beginning. An open source project often faces the false
> > >> > criticism
> > >> > that it is less secure so it is important to have ways of analyzing
> > >> and
> > >> > addressing security holes from the beginning. This may also take
> > the
> > >> > form
> > >> > of jira tickets that relate to ensuring that the logs are
> > inviolable
> > >> and
> > >> > that early detection mechanisms send alerts to the proper humans
> > >> > defined in
> > >> > the configuration file - which may require thinking that through
> > >> more.
> > >> > There are guides to how to secure infrastructure and I am sure
> > other
> > >> > Apache
> > >> > projects have had to deal with this - we should look to them for
> > >> advice.
> > >> >
> > >> > 3. That the surface area of the release includes:
> > >> > 1. Open an Account with at least two KYC levels
> > >> > 2. Open a second 

Re: Fineract CN Group Finance bug report

[Sendoro Juma]

Excellent... 



On Thu, Sep 27, 2018 at 9:40 PM +0300, "Awasum Yannick"  
wrote:










Hello Kelvin,

I have merged your PR.
Keep going.

On Wed, Sep 26, 2018 at 4:48 PM Ed Cable  wrote:

> Thanks Kelvin for these contributions. I will try to ping some folks to
> review your PRs.
>
> Ed
>
> On Wed, Sep 26, 2018 at 8:29 AM Kelvin Ikome  wrote:
>
> > Hi all,
> >
> > I have resolved the following issues on Fineract CN Group finance UI:
> >
> >- https://issues.apache.org/jira/projects/FINCN/issues/FINCN-89
> >- https://issues.apache.org/jira/projects/FINCN/issues/FINCN-90
> >- https://issues.apache.org/jira/projects/FINCN/issues/FINCN-91
> >- https://issues.apache.org/jira/projects/FINCN/issues/FINCN-92
> >
> > In addition to that, I have created a pull request and I'm hoping it will
> > be reviewed and merged. (Link to PR:
> > https://github.com/apache/fineract-cn-group-finance/pull/7)
> >
> >
> > On Sat, Sep 22, 2018 at 2:43 PM, Awasum Yannick 
> wrote:
> >
> > > Hi Kelvin,
> > >
> > > Thanks for doing some QA on the New Web App.
> > >
> > > What version of NPM, NodeJS are you using?
> > > Please can you send a PR for the issues you have resolved?
> > >
> > > Can you also fill and send in an icla to secreat...@apache.org ? You
> can
> > > find it here: https://www.apache.org/licenses/icla.pdf
> > > An individual Contribution license protects you as a Contributor as
> well
> > as
> > > the the Apache Foundation and its users; it does not change your rights
> > to
> > > use your own Contributions for any other purpose. When you submit your
> > > icla, your PRs will be merged with ease.
> > >
> > > If you have sometime, can you also help check and do some QA on
> > > fims-web-app?
> > >
> > > Thanks.
> > > Awasum
> > >
> > > On Sat, Sep 22, 2018 at 1:27 PM Kelvin Ikome 
> wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > I went through the UI for Fineract CN Group Finance (
> > > > https://github.com/apache/fineract-cn-group-finance) a couple of
> days
> > > ago.
> > > > It looks good for a start however, I came across a couple of bugs
> > > (details
> > > > below) and I decided to spend time fixing some of the bugs.
> > > >
> > > > *Bugs*
> > > >
> > > >- Login view
> > > >- Login component does not have a defined variable for password
> > input
> > > >field visibility state and this results to build failures
> > > >- On the login component, password input field is visible by
> default
> > > >- On the login component, password input visibility toggle is
> > reversed
> > > >- On the login component, no error message is shown when the user
> > > enters
> > > >wrong credentials
> > > >- CenterFormComponent view does not have a definition for "staffs"
> > > >object array and this causes a failure when building the UI
> > > >- Issue with views: Components get added (instead of being
> replaced)
> > > and
> > > >form some sort of list with the most recent at the top and every
> > > > subsequent
> > > >component opened gets added to the list. The screenshot can be
> found
> > > > here:
> > > >https://imgur.com/a/as7RPZs and the steps to replicate this issue
> > can
> > > > be
> > > >found below.
> > > >
> > > >
> > > >1. Login as "operator"
> > > >2. Click on "View Centers" on the left nav
> > > >3. Click on "show" from the list of centers
> > > >4. On the left nav, click on Employees, followed by Offices and
> any
> > > >other nav menu option you feel like
> > > >
> > > >
> > > >- Collection Sheet route not working. How to replicate: Login as
> > > >operator and click on "Collection Sheet" from the left nav
> > > >- "Alt + x" key combination not working for the search box in the
> > top
> > > >nav bar
> > > >- "View Centers" menu option on the left nav is not visible on
> small
> > > >screen sizes even when I scroll to the bottom
> > > >
> > > > On the top nav bar...
> > > >
> > > >- Clicking on "Group" routes to "Centers" from "Client" dropdown
> > menu
> > > >- Clicking on "Centers" routes to "QuickAccess" from "Client"
> > dropdown
> > > >menu
> > > >- No router link specified for "Accounting"
> > > >- Router links for both member and deposits on the reports
> dropdown
> > > menu
> > > >are not working
> > > >- Operator doesn't seem to have access to Teller and Products on
> the
> > > >admin dropdown menu (this one might not be a bug)
> > > >
> > > > For anyone using the Group Finance user interface, please check to
> see
> > if
> > > > you can identify bugs
> > > >
> > > >
> > > > Thanks,
> > > > Kelvin Ikome
> > > >
> > > > On Sat, Sep 22, 2018 at 12:48 PM, Kelvin Ikome 
> > > wrote:
> > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > *Hi everyone,I went through the new UI for Fineract CN
> > > > > 

A page on confluence for who are committers etc

[Sendoro Juma]

Hello Devs,

Yes, we  do announcement on who has become a committer etc. and we  send 
congratulates emails and after that all stay and left in mailing list in form 
of emails.

However, how can a new members know the committers and their roles easily by 
visiting Fineract Page?

I think a page in Fineract can help...

Will love also if roles can be indicated e.g. We have committers who are known 
to be great in Quality Assurance etc.

So it can look like below. Sorry with no number as can be considered as 
hierarchy

Developers

Xxx

Xxx

Xxx

Quality Assurance

xxx

xxx

Xxx

Release Management





Documentation

xxx

xxx

xxx


Also... You can as well list module wise Etc

What is your view?

I recall saw one community with this... I forgotten it.

WBR

Sendoro

A page on confluence for who are committers etc

[Sendoro Juma]

Hello Devs,




Yes, we announcement on who has become commiter etc. and we congratulates and 
all left on mailing list. 




However, how can a new members know the committers and their roles 




I think a page in Fineract can help...




Will love also if roles can be indicated e.g. We have committers who are known 
to be great in Quality Assurance etc.




So it can look like below. Sorry with no number as can be considered as 
hierarchy 




Developers


Xxx


Xxx


Xxx




Quality Assurance


xxx


xxx


Xxx




Release Management 












Also... You can as well list module wise Etc




What is your view?




I recall saw one community with this... I forgotten it.




WBR


Sendoro 

Re: PR Reviews

[Sendoro Juma]

+1




On Tue, Sep 11, 2018 at 5:12 PM +0200, "James Dailey"  
wrote:










I put the content here:
https://cwiki.apache.org/confluence/display/FINERACT/Committer%27s+Zone



On Tue, Sep 11, 2018 at 1:43 AM Myrle Krantz  wrote:

> Hey all,
>
> I believe that James has correctly captured the consensus and would
> encourage him to document that.
>
> James if you need any help finding a good spot in the wiki for that, just
> shout.
>
> Best Regards,
> Myrle
> On Tue, Sep 11, 2018 at 8:47 AM Sendoro Juma  wrote:
> >
> > +1
> >
> >
> >
> >
> > For document... Any change improvement will be done in the document
> page...
> >
> >
> >
> >
> > I would also like the page to indicate...
> >
> >
> >
> >
> > On Tue, Sep 11, 2018 at 4:40 AM +0200, "James Dailey" <
> jamespdai...@gmail.com> wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi all - I will comment that I think this is directionally great.
> >
> > As Sendoro suggested:
> > 1) The dev A should try to ask a specific person(s) to review if they
> can,
> > as in dev B, and to anyway give the list some time to review the PR.
> Then
> > 72 hrs later or so, they're able to commit their own PR under a principle
> > of lazy consensus.  This also assumes that people are fully discussing
> > their ideas for a PR in advance and there is a jira issue where the
> > requirements are documented.
> >
> > 2) The Committer may decide that the proposed PR is significant enough
> that
> > they really want someone to review and they can flag that too.
> >
> > Also, the other part of my suggestion (and the really cool insight at
> > Apache) was that:
> > 3) Members of the community who are NOT yet committers would be welcome
> to
> > pitch in on the review, thus earning karma. This creates a dynamic where
> > devs can give feedback and quality review without taking on a task of dev
> > themselves. +1 for the reviewer.
> >
> >
> > I also think Myrle is right in that we don't need a vote, but hope that
> > others will weigh in and consider so we can have a sense of consensus.
> If
> > not, our lazy consensus ideal is that we're in agreement...but first
> let's
> > keep discussion going.
> >
> > I'm happy to document the above on wiki if that's useful.  Not sure what
> > else is needed aside from the 1, 2, 3.  Thoughts?
> >
> > James
> >
> > On Wed, Aug 29, 2018 at 11:05 AM Myrle Krantz  wrote:
> >
> > > Hi all,
> > >
> > > I suggest we give people a chance to give input before we complete the
> > > decision making process.  If we converge on common ground we may not
> need
> > > to vote at all.  We may just need someone to summarize the consensus
> and
> > > document it in wiki.
> > >
> > > I like Sendoro's suggestion.  I don't see a need to hurry PR's merges
> to
> > > faster than 72 hours, and I'd like people to look at each other's code
> to
> > > increase quality, but if we can't get people to do that, it shouldn't
> block
> > > progress.
> > >
> > > Best Regards,
> > > Myrle
> > >
> > >
> > > On Wed 29. Aug 2018 at 08:03 Mexina Daniel  wrote:
> > >
> > > > Hello Ed
> > > >
> > > > Thank you for the prompt reply,
> > > >
> > > > So do we have to vote for James's proposal or we can implement it
> from
> > > now
> > > > on?
> > > >
> > > > Hello Sendoro
> > > >
> > > > Thanks for more inputs,
> > > >
> > > > Adding to that, i think even non-committers should be involved in
> > > > reviewing i.e non-committer A can review to any submitted PR that
> hasn't
> > > > started to be reviewed.
> > > >
> > > > Best Regards
> > > >
> > > > > On August 28, 2018 at 11:06 PM Sendoro Juma
> > > > wrote:
> > > > >
> > > > >
> > > > > Dear Ed, Mexina,
> > > > >
> > > > >
> > > > > I would wish we meet at the middle...  '"Peer Review",  i.e.
> > > > committer A, ask committer B reviewing his/her PR. and vice versa...
> > > > >
> > > > >
> > > > > However, as rule like you said if not happen in 72 hours.. then
> > > > Committer A can proceed especially w

Re: PR Reviews

[Sendoro Juma]

+1




For document... Any change improvement will be done in the document page...




I would also like the page to indicate... 




On Tue, Sep 11, 2018 at 4:40 AM +0200, "James Dailey"  
wrote:










Hi all - I will comment that I think this is directionally great.

As Sendoro suggested:
1) The dev A should try to ask a specific person(s) to review if they can,
as in dev B, and to anyway give the list some time to review the PR.  Then
72 hrs later or so, they're able to commit their own PR under a principle
of lazy consensus.  This also assumes that people are fully discussing
their ideas for a PR in advance and there is a jira issue where the
requirements are documented.

2) The Committer may decide that the proposed PR is significant enough that
they really want someone to review and they can flag that too.

Also, the other part of my suggestion (and the really cool insight at
Apache) was that:
3) Members of the community who are NOT yet committers would be welcome to
pitch in on the review, thus earning karma. This creates a dynamic where
devs can give feedback and quality review without taking on a task of dev
themselves. +1 for the reviewer.


I also think Myrle is right in that we don't need a vote, but hope that
others will weigh in and consider so we can have a sense of consensus.  If
not, our lazy consensus ideal is that we're in agreement...but first let's
keep discussion going.

I'm happy to document the above on wiki if that's useful.  Not sure what
else is needed aside from the 1, 2, 3.  Thoughts?

James

On Wed, Aug 29, 2018 at 11:05 AM Myrle Krantz  wrote:

> Hi all,
>
> I suggest we give people a chance to give input before we complete the
> decision making process.  If we converge on common ground we may not need
> to vote at all.  We may just need someone to summarize the consensus and
> document it in wiki.
>
> I like Sendoro's suggestion.  I don't see a need to hurry PR's merges to
> faster than 72 hours, and I'd like people to look at each other's code to
> increase quality, but if we can't get people to do that, it shouldn't block
> progress.
>
> Best Regards,
> Myrle
>
>
> On Wed 29. Aug 2018 at 08:03 Mexina Daniel  wrote:
>
> > Hello Ed
> >
> > Thank you for the prompt reply,
> >
> > So do we have to vote for James's proposal or we can implement it from
> now
> > on?
> >
> > Hello Sendoro
> >
> > Thanks for more inputs,
> >
> > Adding to that, i think even non-committers should be involved in
> > reviewing i.e non-committer A can review to any submitted PR that hasn't
> > started to be reviewed.
> >
> > Best Regards
> >
> > > On August 28, 2018 at 11:06 PM Sendoro Juma 
> > wrote:
> > >
> > >
> > > Dear Ed, Mexina,
> > >
> > >
> > > I would wish we meet at the middle...  '"Peer Review",  i.e.
> > committer A, ask committer B reviewing his/her PR. and vice versa...
> > >
> > >
> > > However, as rule like you said if not happen in 72 hours.. then
> > Committer A can proceed especially when s/he is sure Quality  of his/her
> PR.
> > >
> > >
> > > How about that?
> > >
> > > > >
> > > > On August 28, 2018 at 7:16 PM Ed Cable 
> > wrote:
> > > >
> > > > Mexina,
> > > >
> > > > Thank you for picking up on James' thread and putting it into
> > action with
> > > > some spot-on questions.
> > > >
> > > > Please see my replies inline:
> > > >
> > > > On Tue, Aug 28, 2018 at 6:46 AM Mexina Daniel
> >  wrote:
> > > >
> > > > > > >
> > > > > Hello fineract'ers
> > > > >
> > > > > Can someone help me to understand few things:
> > > > >
> > > > >1. Should the PR be reviewed by someone (who can be
> a
> > committer or not)
> > > > >   before being merged or a committer can merge
> > his/her PR even if it hasn't
> > > > >   being reviewed by anyone?
> > > > >
> > > > > > >
> > > > In the spirit of James' email requesting a cultural change
> > around PRs and
> > > > the feedback from Ross on minimizing any barriers to
> > contribution, James
> > > > had proposed and I vouch we adopt a lazy consensus policy
> > around committers
> > > > being able to merge their own PRs - if 

Re: PR Reviews

[Sendoro Juma]

Dear Ed, Mexina,


I would wish we meet at the middle...  '"Peer Review",  i.e. committer A, ask 
committer B reviewing his/her PR. and vice versa...


However, as rule like you said if not happen in 72 hours.. then Committer A can 
proceed especially when s/he is sure Quality  of his/her PR.


How about that?

> 
> On August 28, 2018 at 7:16 PM Ed Cable  wrote:
> 
> Mexina,
> 
> Thank you for picking up on James' thread and putting it into action with
> some spot-on questions.
> 
> Please see my replies inline:
> 
> On Tue, Aug 28, 2018 at 6:46 AM Mexina Daniel  wrote:
> 
> > > 
> > Hello fineract'ers
> > 
> > Can someone help me to understand few things:
> > 
> >1. Should the PR be reviewed by someone (who can be a committer 
> > or not)
> >   before being merged or a committer can merge his/her PR even 
> > if it hasn't
> >   being reviewed by anyone?
> > 
> > > 
> In the spirit of James' email requesting a cultural change around PRs and
> the feedback from Ross on minimizing any barriers to contribution, James
> had proposed and I vouch we adopt a lazy consensus policy around 
> committers
> being able to merge their own PRs - if nobody objects within 72 hours, the
> committer can merge their own PR. As James puts, if it breaks, it can be
> unmerged. This would be a shift from our currently policy in which all PRs
> (from everyone including committers) require a review before being merged.
> 
> >
> 
> > >1. Do we have reviewers of PRs (If yes, i would like 
> to know even few of
> >   them) or anyone can review?
> > 
> > > 
> Historically we only allowed committers to review PRs but based on Ross'
> insight into some of the breakthrough changes other projects recently 
> made,
> anybody can now review a PR (committer or not). It would be great to have 
> a
> dedicated team of reviewers but there is no barrier to reviewing PRs so we
> encourage anybody to review and comment on PRs - it's a great way to build
> merit and pave path towards becoming a committer.
> 
> Ed
> 
> >
> 
> > > 
> > Best Regards
> > 
> > Mexina
> > 
> > > 
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> 
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>  
> 

Re: [Web App - Proposal]: Add a forgot password feature

[Sendoro Juma]

+1

- Original Message -
From: "Abhay Chawla" 
To: "mifos-developer" , "dev" 

Cc: "Ed Cable" , "Anwesh Krishna Nayak" 
, "Gaurav Saini" , "Pranjal 
Goswami" , "Maulik Soneji" 
Sent: Saturday, July 14, 2018 10:13:28 PM
Subject: [Web App - Proposal]: Add a forgot password feature

Hello Everyone,

Currently, we don't have a forgot password feature within the community-app
which may allow a user to reset their password in case they have forgotten
and are unable to access the application. We could allow this in the new
web-app by asking the user to enter their username/email/mobile to verify
and then sending them a code/link via sms/email which will allow them to
reset their password (as an example).

I would like to propose this feature and know the views of the community on
the same.

Thanks
Abhay.

Re: [Mifos-users] [Mifos-developer] Which reports would you like to generate from Android Field Officer App?

[Sendoro Juma]

Hello Jubha,

Thanks it is clear and damn right, the other reports which are not requested 
used by loan officer or targeting loan officers  should then be under category 
others...

Solution should be extremely simple and intuitive to the intended user first

Priorities and Focus is an important element in product design I believe!!! 

And of course it should allow others to use in-frequent used features etc... 
Usually these loading of all features they end-up making solution seen by user 
as heavy.

Regards
Sendoro

- Original Message -
From: "jubha mayala" 
To: "mifos-users" 
Cc: "dev" , "mifos-developer" 
, "user" 
Sent: Thursday, June 28, 2018 10:49:15 AM
Subject: Re: [Mifos-users] [Mifos-developer] Which reports would you like to 
generate from Android Field Officer App?

Hi All,
The Android app is for Loan officers, but as long as is to be used in smart
phones even the senior level people will use it/ are using it, which means
the reports mentioned by Sifiso are still a plus to be included into the
new Android app!

Jubha!

On Thu, Jun 28, 2018 at 9:42 AM,  wrote:

> Hi Sendoro,
>
>
>
> The reason why I included the accounting reports is because we added the
> accounting module to the android app to add journal entries. This was
> designed to pay for small remittances like traveling costs, stationery,
> airtime ..etc Income and expenditure and balance sheet might be resourceful
> to develop. But the general ledger might be required for a loan officer to
> account for his or her expenses.
>
>
>
> Thanks and regards,
>
> Sifiso
>
>
>
>
>
> *From:* Sendoro Juma 
> *Sent:* Wednesday, June 27, 2018 9:35 PM
> *To:* mifos-developer 
> *Cc:* mifos-users ; user <
> u...@fineract.apache.org>
> *Subject:* Re: [Mifos-users] [Mifos-developer] Which reports would you
> like to generate from Android Field Officer App?
>
>
>
> Hello Sifiso,
>
>
>
> I would draw the requirements from the role of the user!!!
>
>
>
> I consider this person will be *loan officer* if that is the case...
>
>
>
> Then I see some reports you listed below is overkill.
>
>
>
> Regards
> Sendoro
>
>
>
>
> --
>
> *From: *sif...@skyburgsystems.org
> *To: *"mifos-developer" 
> *Cc: *"mifos-users" , "user" <
> u...@fineract.apache.org>
> *Sent: *Wednesday, June 27, 2018 6:46:20 PM
> *Subject: *Re: [Mifos-developer] Which reports would you like to generate
> from Android Field Officer App?
>
>
>
> Hi Ed,
>
>
>
> Here is a list of reports we feel are a priority for the android app.
>
> Balance Outstanding loans
>
> Expected payments (with missed installment column)
>
> General ledger
>
> Arrears report
>
> Collections report (with payment type column)
>
> Client listing report (with gender, address and mobile number)
>
> Disbursal report
>
> Income and expediture (if accounting module is to be included)
>
> Balance sheet (if accounting module is to be included)
>
>
>
> PDF is ideal but if the reports can be viewed in app and also as a PDF
> that would be great.
>
>
>
> Kind regards,
>
> Sifiso
>
>
>
> *From:* Ed Cable 
> *Sent:* Tuesday, June 12, 2018 8:33 AM
> *To:* Mifos software development ;
> u...@fineract.apache.org; mifos-users ;
> RM ; Aksh Gautam 
> *Subject:* [Mifos-developer] Which reports would you like to generate
> from Android Field Officer App?
>
>
>
> Hi all,
>
>
>
> Aksh, as part of his GSOC project working Android Field Officer App 5.0,
> is working on generating reports from the mobile field operations app. We'd
> like for any partners or financial institutions to share which reports
> they'd like to be able to generate and view from the mobile field
> operations app.
>
>
>
> In order to optimize viewing of the report on a mobile device, we'll also
> need to re-design these existing reports so please also share what
> information you'd like to display in the report and we'll design and build
> a new report specific to mobile devices.
>
>
>
> Also, what format would you like to view the report - just be displayed in
> the app or downloaded as PDF.
>
>
>
> Tarun, can you share how far you got in your implementation last year?
>
>
>
> Thanks,
>
>
>
> Ed
>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
>
> Virus-free. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
>
>
> --

Re: [Mifos-users] [Mifos-developer] Which reports would you like to generate from Android Field Officer App?

[Sendoro Juma]

Hello Sifiso,

Clear but not to the level of reports :)

- Original Message -
From: sif...@skyburgsystems.org
To: "mifos-users" 
Cc: "mifos-developer" , "user" 
, "dev" 
Sent: Thursday, June 28, 2018 8:42:46 AM
Subject: RE: [Mifos-users] [Mifos-developer] Which reports would you like to 
generate from Android Field Officer App?

Hi Sendoro,



The reason why I included the accounting reports is because we added the 
accounting module to the android app to add journal entries. This was designed 
to pay for small remittances like traveling costs, stationery, airtime ..etc 
Income and expenditure and balance sheet might be resourceful to develop. But 
the general ledger might be required for a loan officer to account for his or 
her expenses.



Thanks and regards,

Sifiso





From: Sendoro Juma 
Sent: Wednesday, June 27, 2018 9:35 PM
To: mifos-developer 
Cc: mifos-users ; user 

Subject: Re: [Mifos-users] [Mifos-developer] Which reports would you like to 
generate from Android Field Officer App?



Hello Sifiso,



I would draw the requirements from the role of the user!!!



I consider this person will be loan officer if that is the case...



Then I see some reports you listed below is overkill.



Regards
Sendoro





  _

From: sif...@skyburgsystems.org <mailto:sif...@skyburgsystems.org>
To: "mifos-developer" mailto:mifos-develo...@lists.sourceforge.net> >
Cc: "mifos-users" mailto:mifos-us...@lists.sourceforge.net> >, "user" mailto:u...@fineract.apache.org> >
Sent: Wednesday, June 27, 2018 6:46:20 PM
Subject: Re: [Mifos-developer] Which reports would you like to generate from 
Android Field Officer App?



Hi Ed,



Here is a list of reports we feel are a priority for the android app.

Balance Outstanding loans

Expected payments (with missed installment column)

General ledger

Arrears report

Collections report (with payment type column)

Client listing report (with gender, address and mobile number)

Disbursal report

Income and expediture (if accounting module is to be included)

Balance sheet (if accounting module is to be included)



PDF is ideal but if the reports can be viewed in app and also as a PDF that 
would be great.



Kind regards,

Sifiso



From: Ed Cable mailto:edca...@mifos.org> >
Sent: Tuesday, June 12, 2018 8:33 AM
To: Mifos software development mailto:mifos-develo...@lists.sourceforge.net> >; u...@fineract.apache.org 
<mailto:u...@fineract.apache.org> ; mifos-users 
mailto:mifos-us...@lists.sourceforge.net> 
>; RM mailto:rajanmaurya...@gmail.com> >; Aksh 
Gautam mailto:gaksh...@gmail.com> >
Subject: [Mifos-developer] Which reports would you like to generate from 
Android Field Officer App?



Hi all,



Aksh, as part of his GSOC project working Android Field Officer App 5.0, is 
working on generating reports from the mobile field operations app. We'd like 
for any partners or financial institutions to share which reports they'd like 
to be able to generate and view from the mobile field operations app.



In order to optimize viewing of the report on a mobile device, we'll also need 
to re-design these existing reports so please also share what information you'd 
like to display in the report and we'll design and build a new report specific 
to mobile devices.



Also, what format would you like to view the report - just be displayed in the 
app or downloaded as PDF.



Tarun, can you share how far you got in your implementation last year?



Thanks,



Ed




 
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient>

Virus-free.  
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
 www.avast.com


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Mifos-developer mailing list
mifos-develo...@lists.sourceforge.net 
<mailto:mifos-develo...@lists.sourceforge.net>
Unsubscribe or change settings at:
https://lists.sourceforge.net/lists/listinfo/mifos-developer



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: [Mifos-developer] Web-App (Angular 6): Choice of DesignFramework- Angular Material vs bootswatch and ng-bootstrap)

[Sendoro Juma]

Dear Jubha, 

As for 

- When transfering a client from one office to another, an option to choose a 
transfer date will be good also 

https://github.com/openMF/community-app/issues/2968 


Can you check the other two if there is no opened issue... so that you can 
open? 


Regards 
Sendoro 


From: "jubha mayala"  
To: "Ed Cable" , "mifos-developer" 
 
Cc: "Pranjal Goswami" , "dev" 
, gsoc-2...@mifos.org 
Sent: Thursday, June 21, 2018 10:53:23 AM 
Subject: RE: [Mifos-developer] Web-App (Angular 6): Choice of DesignFramework- 
Angular Material vs bootswatch and ng-bootstrap) 



Hi All! 

On my experience using and training users of Mifos x, I would recommend these 
things be added into the new coming Mifos x: 



- Data import tool (Bulk Import) menu to have numbers like the old data Import 
Tool, this helps a lot when you are training new users of Mifos x. (numbers are 
memorized easily compared to words!) 



- an option to display a total number of clients on list of client’s page. 



- When transferring a client from one office to another, an option to choose a 
transfer date will be good also. 



all of these I have attached print screen photos for more clarifications. 



Thank you all for the good job! 



Jubha. 







Sent from [ https://go.microsoft.com/fwlink/?LinkId=550986 | Mail ] for Windows 
10 




From: [ mailto:edca...@mifos.org | Ed Cable ] 
Sent: Wednesday, June 20, 2018 4:15 PM 
To: [ mailto:mifos-develo...@lists.sourceforge.net | Mifos software development 
] 
Cc: [ mailto:pranjal.b.gosw...@gmail.com | Pranjal Goswami ] ; [ 
mailto:dev@fineract.apache.org | Dev ] ; [ mailto:gsoc-2...@mifos.org | 
gsoc-2...@mifos.org ] 
Subject: Re: [Mifos-developer] Web-App (Angular 6): Choice of DesignFramework- 
Angular Material vs bootswatch and ng-bootstrap) 





Sifiso, Jubha, 





Allowing skinnable themes and more configuration of look and feel of UI is 
exactly one of the goals we want to support with rewrite of the UI on Angular 
6. 





We don't want the default UI to be a drastic departure from the current UX and 
redesigned skin that we rolled out but we do want to ensure we take into 
account Material guidelines and address and optimize the current portions of 
the UI that are challenging for end users. 





What would be great for you both to do is share your feedback on this thread 
about what works best about the current UX and want to ensure is replicated and 
what areas of the current UI you think need to be improved the most. 





Santosh is working closely with Anwesh and Abhay on this project to ensure 
usability is improved and doesn't drastically depart from the current Mifos X 
web app experience. 





Ed 





On Wed, Jun 20, 2018 at 5:53 AM jubha mayala < [ mailto:basston...@gmail.com | 
basston...@gmail.com ] > wrote: 





Hi all! 

Yes, the proposed UI looks great, but I would also recommend if possible Mifos 
x should have a feature to choose themes. Users to be able to choose the 
classic Mifos x UI or the new one  



Sent from [ https://go.microsoft.com/fwlink/?LinkId=550986 | Mail ] for Windows 
10 




From: [ mailto:sif...@skyburgsystems.org | sif...@skyburgsystems.org ] 
Sent: Wednesday, June 20, 2018 2:52 PM 
To: [ mailto:mifos-develo...@lists.sourceforge.net | 'Mifos software 
development' ] 
Cc: [ mailto:pranjal.b.gosw...@gmail.com | pranjal.b.gosw...@gmail.com ] ; [ 
mailto:gsoc-2...@mifos.org | gsoc-2...@mifos.org ] ; [ 
mailto:dev@fineract.apache.org | dev@fineract.apache.org ] 
Subject: Re: [Mifos-developer] Web-App (Angular 6): Choice of Design Framework- 
Angular Material vs bootswatch and ng-bootstrap) 




Hi guys, 



I like some of the UI that is being proposed for the system. But other 
suggestions are not really necessary like the top menu, client create, and the 
accounting new look UIs. So my question is can we choose what we want the 
system UI to look like and perform as? 



Kind regards, 

Sifiso 



From: Anwesh Krishna Nayak < [ mailto:anweshkna...@gmail.com | 
anweshkna...@gmail.com ] > 
Sent: Friday, June 15, 2018 6:13 PM 
To: Gaurav Saini < [ mailto:gauravsain...@gmail.com | gauravsain...@gmail.com ] 
> 
Cc: [ mailto:gsoc-2...@mifos.org | gsoc-2...@mifos.org ] ; Pranjal Goswami < [ 
mailto:pranjal.b.gosw...@gmail.com | pranjal.b.gosw...@gmail.com ] >; Mifos 
software development < [ mailto:mifos-develo...@lists.sourceforge.net | 
mifos-develo...@lists.sourceforge.net ] >; Dev < [ 
mailto:dev@fineract.apache.org | dev@fineract.apache.org ] > 
Subject: Re: [Mifos-developer] Web-App (Angular 6): Choice of Design Framework 
- Angular Material vs bootswatch and ng-bootstrap) 




I have attached below the doc containing redesigning of all UI and links 
respectively 





Link : [ 
https://docs.google.com/document/d/1H9w7QWenox9M0nb29WR4RmvV94Jsjj0LglUZ3wCzbw8/edit?usp=sharing
 | 
https://docs.google.com/document/d/1H9w7QWenox9M0nb29WR4RmvV94Jsjj0LglUZ3wCzbw8/edit?usp=sharing
 ] 





Thanks 




[ 

Re: [GitHub] fineract issue #451: FINERACT-613:500 Internal Server Errors on Data Tables

[Sendoro Juma]

Hello Ed,

You promised...

"@avikganguly01 @conradsp @nazeer1100126 @nikpawar Can we get this merged in so 
we can ship the point release that contains this hot fix?"

After this PR is merged, can we?

Regards
Sendoro

- Original Message -
From: "conradsp" 
To: comm...@fineract.apache.org
Sent: Monday, June 11, 2018 9:06:42 PM
Subject: [GitHub] fineract issue #451: FINERACT-613:500 Internal Server Errors 
on Data Tables

Github user conradsp commented on the issue:

https://github.com/apache/fineract/pull/451
  
I have merged this PR.
Thanks,
Steve


On Mon, Jun 11, 2018 at 1:19 PM edcable  wrote:

> @avikganguly01  @conradsp
>  @nazeer1100126
>  @nikpawar 
> Can we get this merged in so we can ship the point release that contains
> this hot fix?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or 
mute
> the thread
> 

> .
>



---

Re: Selection of chat/support tool for Customer-Facing Apps

[Sendoro Juma]

Hello Abhay,

Form license compatibility point of view; MIT & Apache License 2.0 is OK.

See
https://www.quora.com/Is-the-MIT-license-compatible-with-the-Apache-License-Version-2-APLv2

Regards
Sendoro

- Original Message -
From: "Abhay Chawla" 
To: "Ed Cable" 
Cc: "saksham handu2015" , ankur16...@iiitd.ac.in, 
"mifos-developer" , "dev" 
, "Gaurav Saini" 
Sent: Sunday, May 27, 2018 12:18:46 PM
Subject: Re: Selection of chat/support tool for Customer-Facing Apps

Hello Everyone,

I think we could try using Rocket.Chat Live Chat feature for adding chat
widgets to the Online Banking App and Mobile App on the client side.
Further, admins would respond to clients' queries from the Self Service
User Administrative Portal. Rocket.Chat is open source with MIT license, so
it can be customized accordingly and they offer
cross-platform compatibility (Android, Web, IOS) as well.
https://rocket.chat/
https://github.com/RocketChat/Rocket.Chat
Although it looks good, I am a bit confused on what kind of tool are we
exactly looking for. Can you please clarify a little bit on this?
Most of the other tools I could find are not having a proper license and
are paid. Rocket.Chat on the other hand can be hosted on the organisation's
own server as well.

I would also like to apologize for replying late as I got preoccupied with
the exams last week and could not participate in the conversation.

Thanks,
Abhay


On Fri, May 18, 2018 at 2:01 AM Ed Cable  wrote:

> Hi gentlemen,
>
> Since all three of you will possibly have some interaction with this
> functionality as part of your GSOC project, (Saksham - mobile banking 3.0
> app, abhay - self-service admin portal, and ankur- mobile wallet 2.0) I
> wanted to resurface the discussion on the list as to what tool(s) we've
> been evaluating and are proposing to use for this functionality.
>
> Saksham and Abhay, can you list out what you had been proposing so our
> mentors can help finalize a decision with the rest of the community.
>
> Thanks,
>
> Ed
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>

Re: [ANNOUNCE] New Apache Fineract Committer Aleksandar Vidakovic

[Sendoro Juma]

Congrats Alek


- Original Message -
From: "Courage Angeh" 
To: "dev" 
Sent: Saturday, May 5, 2018 3:57:51 PM
Subject: Re: [ANNOUNCE] New Apache Fineract Committer Aleksandar Vidakovic

Congratulations Alek

On Sat, May 5, 2018, 2:44 PM Ed Cable  wrote:

> Hello Fineract community!
>
> I'm happy to announce that Apache Fineract has a new committer.
>
> Aleks has been a long-time member of the Mifos and Fineract community
> dating back more than 5 years. He's deeply aware of all the intricacies of
> Fineract 1.x from his work he's done on it. Most recently he mentored
> Sanyam on his Swagger API documentation project and will be mentoring an
> intern this year working on a chatbot that integrates with Fineract.
>
> As a committer, he's eager to come on board and help the community in
> getting its public demo infrastructure set up. So stay tuned for those
> contributions!
>
> Congratulations Aleks! Thank you for your contributions, and thank
> you for accepting our invitation!  We look forward to continuing to
> work together with you.
>
> Best Regards,
>
> Ed Cable
> Apche Fineract
>
> P.S. Aleks, would you mind if we announce your committership on social
> media? I couldn't find your user.
>
> Cheers,
>
> Ed
>

Project Documentations

[Sendoro Juma]

Hello Devs, 

Does this look like a best practice to borrow leaf from for our projects? 

https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team 

Thanks 
Sendoro 

Re: New ASF Member: Myrle Krantz

[Sendoro Juma]

Hello Myrle,

Very proud of you keep going.

Regards
Sendoro

- Original Message -
From: "sharan" 
To: "dev" 
Sent: Wednesday, May 2, 2018 10:20:44 PM
Subject: New ASF Member: Myrle Krantz

Hi All

In today’s announcement of all our new ASF members – one name that I’m sure you 
will recognise from Fineract is in there too --- Myrle Krantz!

https://s.apache.org/D6iz

Becoming a ASF member is by invitation only so it’s great to see that Myrle has 
been recognised for her contribution to the Foundation as a whole!

Please join me in congratulating Myrle on becoming an ASF member!

Thanks
Sharan

Re: Introduction

[Sendoro Juma]

Hello Leo,

Welcome to the community.

Cheers
Sendoro

- Original Message -
From: "Myrle Krantz" 
To: "dev" 
Sent: Thursday, April 26, 2018 3:47:43 PM
Subject: Re: Introduction

Hey Leo,

I've added you to the Jira contributors group for the project FINCN.
Please check if that makes it possible for you to assign issues to
yourself, and if it doesn't, let me know.

Full disclosure for the Fineract community: Leo is a founding employee
of Zingr, which is the company I'm working for as well.

Best Regards,
Myrle


On Thu, Apr 26, 2018 at 3:41 PM, Leopold Joy  wrote:
> Hello everyone,
>
> My name is Leopold Joy and I am hoping to contribute to Fineract. I would
> like to assign one of the Jira issues to myself, but it seems I do not have
> the necessary permissions to do so. How can I get the permissions to assign
> an issue to myself? My Jira username is: leopoldjoy.
>
> Excited to be a part of the Fineract community!
>
> Best,
> Leopold Joy

Re: [Mifos-developer] 500 Internal Server Errors on Data Tables in Apache Fineract 1.1 Release

[Sendoro Juma]

Hello Devs,

Just a little question, 

>From the hot fixes mentioned, applied after 1.1.0 release; should we expect 
>1.1.x release?;  To be specific 1.1.1?

Regards
Sendoro

- Original Message -
From: "Ed Cable" 
To: "dev" 
Cc: "mifos-developer" 
Sent: Wednesday, April 25, 2018 8:27:30 AM
Subject: Re: [Mifos-developer] 500 Internal Server Errors on Data Tables in 
Apache Fineract 1.1 Release

Thanks Thynn!

On Tue, Apr 24, 2018, 23:23 Thynn Win  wrote:

> Hi all,
>
> FYI - after applying this fix 613 to version 18 (fineract 1.1), we still
> cannot create a new datatable. Validation rule on the front end is
> preventing the form submission.
>
>
> One of our team members is planning on committing a fix on UI. We'll link
> it to Fineract-613.
>
>
>
>
>
> 
> From: Ed Cable 
> Sent: Tuesday, April 10, 2018 2:36:53 PM
> To: Dev; Mifos software development
> Subject: [Mifos-developer] 500 Internal Server Errors on Data Tables in
> Apache Fineract 1.1 Release
>
> Some users have reported the following error with data tables on the new
> release:
>
> https://issues.apache.org/jira/browse/FINERACT-613
>
> A fix will soon be pushed as part of a  hotfix release.
>
> Thanks,
>
> Ed
>

Re: [Mifos-developer] 500 Internal Server Errors on Data Tables in Apache Fineract 1.1 Release

[Sendoro Juma]

Hello Devs,

Just a little questions, 

Fr the hot fixes mentioned, applied after 1.1.0 release; should we expect 1.1.x 
release?;  To be specific 1.1.1?

Regards
Sendoro

- Original Message -
From: "Ed Cable" 
To: "dev" 
Cc: "mifos-developer" 
Sent: Wednesday, April 25, 2018 8:27:30 AM
Subject: Re: [Mifos-developer] 500 Internal Server Errors on Data Tables in 
Apache Fineract 1.1 Release

Thanks Thynn!

On Tue, Apr 24, 2018, 23:23 Thynn Win  wrote:

> Hi all,
>
> FYI - after applying this fix 613 to version 18 (fineract 1.1), we still
> cannot create a new datatable. Validation rule on the front end is
> preventing the form submission.
>
>
> One of our team members is planning on committing a fix on UI. We'll link
> it to Fineract-613.
>
>
>
>
>
> 
> From: Ed Cable 
> Sent: Tuesday, April 10, 2018 2:36:53 PM
> To: Dev; Mifos software development
> Subject: [Mifos-developer] 500 Internal Server Errors on Data Tables in
> Apache Fineract 1.1 Release
>
> Some users have reported the following error with data tables on the new
> release:
>
> https://issues.apache.org/jira/browse/FINERACT-613
>
> A fix will soon be pushed as part of a  hotfix release.
>
> Thanks,
>
> Ed
>

Re: Apache Fineract 1.x.x Release Management

[Sendoro Juma]

Hello Ippez,

Look nice, 

Indeed it is time to improve and be better, thanks for the commitment!!!

Together we can make it happen



Regards
Sendoro

- Original Message -
From: "ippezrobert" <ippezrob...@gmail.com>
To: "dev" <dev@fineract.apache.org>
Cc: "Ed Cable" <edca...@mifos.org>
Sent: Monday, April 23, 2018 8:15:43 AM
Subject: Re: Apache Fineract 1.x.x Release Management

Hi all, I think we need to get back on our toes and do things like we used
to do when this was still a Mifos X project. I remember in a day we could
merge up to 3 - 5 PRs and also add new features every fortnight or so. So i
think with much experience we have learnt over couple of years we can do
better and with much ease since we are so exposed to the API design and
implementations. So i will actively want to participate in review and merge
of PRs as in the above link now that Myrle Krantz has given us 'How to
merge PR in Fineract 1.x
<https://cwiki.apache.org/confluence/display/FINERACT/Merge+a+pull+request+to+a+mirrored+Apache+repo>'
which we didn't know previous.

@Ed, if you could point where the following PRs can be got for reviews:-

   -

   The new feature(s) & bug fixes that have been developed so far by the
   core team
   - The new APIs that have been built by core team to enable GSOC
   projects.
   - The pull requests and features that have been contributed by several
   partner organizations: BOWPI, R116, etc.


Thanks
Regards
Ippez Roberts
Apache Committer

On Sun, Apr 22, 2018 at 5:58 PM, Sendoro Juma <sendoro@singo.africa> wrote:

> Devs/Ed,
>
> Are the date at clear close to reality?
>
> Look like there were confusion with release 1.1.0 dates... or am I getting
> it wrong?
>
> [ https://cwiki.apache.org/confluence/display/FINERACT/1.
> 2.0+-+Apache+Fineract | Apache Fineract 1.2.0 ]
> [ https://cwiki.apache.org/confluence/display/FINERACT/1.
> 3.0+-+Apache+Fineract | Apache Fineract 1.3.0 ]
>
>
> Even we missed plan for 1.1.0; But I think we can continuously improve!!!
>
>
> Regards
> Sendoro
>



-- 
Ippez Roberts
Founder/C.E.O - Swift3 Technologies (U) Ltd
"Redefining Next Generation I/O Systems"
P.O.Box 155, Moyo
UGANDA.
Tel: +256788725408/770602630
Skype ID: ippez.robert1
Email: ippezrob...@gmail.com

Apache Fineract 1.x.x Release Management

[Sendoro Juma]

Devs/Ed, 

Are the date at clear close to reality? 

Look like there were confusion with release 1.1.0 dates... or am I getting it 
wrong? 

[ https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract 
| Apache Fineract 1.2.0 ] 
[ https://cwiki.apache.org/confluence/display/FINERACT/1.3.0+-+Apache+Fineract 
| Apache Fineract 1.3.0 ] 


Even we missed plan for 1.1.0; But I think we can continuously improve!!! 


Regards 
Sendoro 

Re: [ANNOUNCE] New Apache Fineract PMC Member Awasum Yannick

[Sendoro Juma]

Hello Yannick,

Congrats for well deserved recognition!!!

Regards
Sendoro

- Original Message -
From: "Myrle Krantz" 
To: "dev" 
Sent: Thursday, April 19, 2018 8:52:19 PM
Subject: [ANNOUNCE] New Apache Fineract PMC Member Awasum Yannick

Hello Fineract Folks,

Please join me in welcoming Awasum Yannick as the newest member of our
Project Management Committee.

Awasum began contributing to the Fineract community last year in July,
and has since become a valued member of our community.  He's
contributed to both Fineract 1x, and Fineract CN on several topics.

He's been consistently encouraging and helpful to other community
members, demonstrating both leadership and technical skills.  We are
lucky to have him.

Best Regards,
Myrle Krantz
V.P., Apache Fineract

Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.

[Sendoro Juma]

Dear Myrle,

It may be irrelevant, but let me shoot anyway...!!!... please don't through 
stones onto me. 

PostgreSQL is believe to have very/most liberal license... as matter of 
facts... it will avoid now and any future license conflict.

The question is then, why don't we select PostgreSQL as our default DBMS?

- is it related with our skill set? or
- it is more just related to smooth transfer from MySQL to MariaDB?

Taking into Finaract CN project take a revolution approach from its predecessor 
Finaract; why also not take same approach on database? 
- after-all Fineract CN Architecture is decoupled from reliance on particular 
database system...


Refer
https://www.postgresql.org/about/licence/
https://www.postgresql.org/list/
https://opensource.org/licenses/MIT


Regards
Sendoro
- Original Message -
From: "Myrle Krantz" <my...@apache.org>
To: "dev" <dev@fineract.apache.org>
Sent: Wednesday, April 18, 2018 9:44:13 AM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to 
OpenJPA Migration.

Thank you Sendoro,

It's much appreciated.

FYI: I've captured the MariaDB work items in 2 new tickets:
https://issues.apache.org/jira/browse/FINCN-26
https://issues.apache.org/jira/browse/FINCN-27

Best Regards,
Myrle

On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma <sendoro@singo.africa> wrote:
> Hello Myrle,
>
> I got you.
>
> Let me know if there is any other component need to be checked!
>
> Cheers
> Sendoro

Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.

[Sendoro Juma]

Hello Myrle,

I got you.

Let me know if there is any other component need to be checked!

Cheers
Sendoro

- Original Message -
From: "Myrle Krantz" <my...@apache.org>
To: "dev" <dev@fineract.apache.org>
Sent: Monday, April 16, 2018 4:43:09 PM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to 
OpenJPA Migration.

Hey Sendoro,

Unfortunately that's not good enough.  I agree with your
interpretation of LGPL, but the ASF is, as a foundation, taking a more
conservative stance.  Apache projects are not allowed to depend on
LGPL libraries.  The ASF choses to be cautious on this matter, because
many companies depend on code produced by the ASF.

This sequence of events would be bad:
1.) We include LGPL software in our release.
2.) Our code, including the LGPL dependency is included in proprietary
code of CompanyOmega
3.) Some judge somewhere decides that the "firewall" separating our
code from the LGPL isn't strong enough to call prevent the viral
aspects of LGPL from taking effect.
4.) CompanyOmega's proprietary code is now all open source and they go
out of business.

It's not a likely sequence, but because of the size of the negative
outcome, we avoid it by not including LGPL (or any other Category X
software) in our releases.

We will have to remove any dependencies to CatX software before we
release Fineract CN.

Best Regards,
Myrle

(By the way, the Hibernate Validator, unlike the Hibernate JPA
implementation, is released under the Apache V2 license
https://github.com/hibernate/hibernate-validator/blob/master/license.txt)


On Sun, Apr 15, 2018 at 2:55 PM, Sendoro Juma <sendoro@singo.africa> wrote:
> Dear All,
>
> I believe this can resolve the issue with MariaDB client
>
> -
> Licenses used by MariaDB
> MariaDB is distributed under the GPL license, version 2.
>
> The MariaDB client libraries for C, Java and ODBC are distributed under the 
> LGPL license, version 2.1 or later. The LGPL license allows you to distribute 
> these MariaDB client libraries freely with any application.
>
> The MariaDB client library included with the MariaDB server is also GPL 
> version 2, but has a FLOSS exception that allows you to combine it with most 
> other open source software, without conflicting with their license, even if 
> that license is incompatible with the GPL. We do however recommend you to use 
> the new client libraries for any non-GPL application.
>
> About FLOSS exception #Below Apache Software License 2.0 is included.
>
>
> FLOSS License List
>
> License name Version(s)/Copyright Date
> Academic Free License 2.0
> Apache Software License 1.0/1.1/2.0
> Apple Public Source License 2.0
> Artistic license From Perl 5.8.0
> BSD license "July 22 1999"
> Common Development and Distribution License (CDDL) 1.0
> Common Public License 1.0
> Eclipse Public License 1.0
> GNU Library or "Lesser" General Public License (LGPL) 2.0/2.1
> Jabber Open Source License 1.0
> MIT license (As listed in file MIT-License.txt) ---
> Mozilla Public License (MPL) 1.0/1.1
> Open Software License 2.0
> OpenSSL license (with original SSLeay license) "2003" ("1998")
> PHP License 3.0
> Python license (CNRI Python License) ---
> Python Software Foundation License 2.1.1
> Sleepycat License "1999"
> University of Illinois/NCSA Open Source License ---
> W3C License "2001"
> X11 License "2001"
> Zlib/libpng License ---
> Zope Public License 2.0
>
> Due to the many variants of some of the above licenses, we
> require that any version follow the 2003 version of the Free
> Software Foundation's Free Software Definition
> (http://www.gnu.org/philosophy/free-sw.html) or version 1.9 of
> the Open Source Definition by the Open Source Initiative
> (http://www.opensource.org/docs/definition.php).
>
>  3. Definitions
>
>   a. Terms used, but not defined, herein shall have the
>  meaning provided in the GPL.
>   b. Derivative Work means a derivative work under copyright
>  law.
>
>  4. Applicability: This FLOSS Exception applies to all Programs
> that contain a notice placed by MySQL AB saying that the
> Program may be distributed under the terms of this FLOSS
> Exception. If you create or distribute a work which is a
> Derivative Work of both the Program and any other work
> licensed under the GPL, then this FLOSS Exception is not
> available for that work; thus, you must remove the FLOSS
> Exception notice from that work and comply with the GPL in all
> respects, including by retaining all GPL notices. You may
> choose to redistribute a copy of the Program exclusively under
> the ter

Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.

[Sendoro Juma]

Dear All,

I believe this can resolve the issue with MariaDB client

-
Licenses used by MariaDB
MariaDB is distributed under the GPL license, version 2.

The MariaDB client libraries for C, Java and ODBC are distributed under the 
LGPL license, version 2.1 or later. The LGPL license allows you to distribute 
these MariaDB client libraries freely with any application.

The MariaDB client library included with the MariaDB server is also GPL version 
2, but has a FLOSS exception that allows you to combine it with most other open 
source software, without conflicting with their license, even if that license 
is incompatible with the GPL. We do however recommend you to use the new client 
libraries for any non-GPL application.

About FLOSS exception #Below Apache Software License 2.0 is included.


FLOSS License List

License name Version(s)/Copyright Date
Academic Free License 2.0
Apache Software License 1.0/1.1/2.0
Apple Public Source License 2.0
Artistic license From Perl 5.8.0
BSD license "July 22 1999"
Common Development and Distribution License (CDDL) 1.0
Common Public License 1.0
Eclipse Public License 1.0
GNU Library or "Lesser" General Public License (LGPL) 2.0/2.1
Jabber Open Source License 1.0
MIT license (As listed in file MIT-License.txt) ---
Mozilla Public License (MPL) 1.0/1.1
Open Software License 2.0
OpenSSL license (with original SSLeay license) "2003" ("1998")
PHP License 3.0
Python license (CNRI Python License) ---
Python Software Foundation License 2.1.1
Sleepycat License "1999"
University of Illinois/NCSA Open Source License ---
W3C License "2001"
X11 License "2001"
Zlib/libpng License ---
Zope Public License 2.0

Due to the many variants of some of the above licenses, we
require that any version follow the 2003 version of the Free
Software Foundation's Free Software Definition
(http://www.gnu.org/philosophy/free-sw.html) or version 1.9 of
the Open Source Definition by the Open Source Initiative
(http://www.opensource.org/docs/definition.php).

 3. Definitions

  a. Terms used, but not defined, herein shall have the
 meaning provided in the GPL.
  b. Derivative Work means a derivative work under copyright
 law.

 4. Applicability: This FLOSS Exception applies to all Programs
that contain a notice placed by MySQL AB saying that the
Program may be distributed under the terms of this FLOSS
Exception. If you create or distribute a work which is a
Derivative Work of both the Program and any other work
licensed under the GPL, then this FLOSS Exception is not
available for that work; thus, you must remove the FLOSS
Exception notice from that work and comply with the GPL in all
respects, including by retaining all GPL notices. You may
choose to redistribute a copy of the Program exclusively under
the terms of the GPL by removing the FLOSS Exception notice
from that copy of the Program, provided that the copy has
never been modified by you or any third party.
--

- Original Message -
From: "Sendoro Juma" <sendoro@singo.africa>
To: "dev" <dev@fineract.apache.org>
Sent: Sunday, April 15, 2018 2:41:50 PM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to 
OpenJPA Migration.

There are these comments though

GNU GPL/GNU Affero GPL
Discussion of Apache License v2.0 and GPL Compatibility merits a separate page. 
http://www.apache.org/licenses/GPL-compatibility.html

GNU LGPL
The LGPL is ineligible primarily due to the restrictions it places on larger 
works, violating the third license criterion.
Special exceptions to the GNU GPL
Some copyright holders have licensed their works under the GPL with special 
exceptions. Although these exceptions may appear to be addressing the 
restrictions disallowed by the ASF's first and second license criteria, the 
exceptions may only apply to software not "derived from or based on" the 
covered work. This references terms defined in the GPL that include works that 
"use" or "contain" the work.

- Original Message -
From: "Sendoro Juma" <sendoro@singo.africa>
To: "dev" <dev@fineract.apache.org>
Sent: Sunday, April 15, 2018 2:38:45 PM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to 
OpenJPA Migration.

LPGL 2.1 is categorically included as not compliant.

WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?
Binary Code License (BCL)
Special exceptions to the GNU GPL (e.g. GNU Classpath)
GNU GPL 1, 2, 3
GNU LGPL 2, 2.1, 3
GNU Affero GPL 3





- Original Message -
From: "Awasum Yannick" <awa...@apache.org>
To: "dev" <dev@fineract.apache.org>
Sent: Saturday, March 10, 2018 6:29:51 PM
Subject: Moving Towards Apache Compliance for Fineract CN: Hi

Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.

[Sendoro Juma]

There are these comments though

GNU GPL/GNU Affero GPL
Discussion of Apache License v2.0 and GPL Compatibility merits a separate page. 
http://www.apache.org/licenses/GPL-compatibility.html

GNU LGPL
The LGPL is ineligible primarily due to the restrictions it places on larger 
works, violating the third license criterion.
Special exceptions to the GNU GPL
Some copyright holders have licensed their works under the GPL with special 
exceptions. Although these exceptions may appear to be addressing the 
restrictions disallowed by the ASF's first and second license criteria, the 
exceptions may only apply to software not "derived from or based on" the 
covered work. This references terms defined in the GPL that include works that 
"use" or "contain" the work.

- Original Message -
From: "Sendoro Juma" <sendoro@singo.africa>
To: "dev" <dev@fineract.apache.org>
Sent: Sunday, April 15, 2018 2:38:45 PM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to 
OpenJPA Migration.

LPGL 2.1 is categorically included as not compliant.

WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?
Binary Code License (BCL)
Special exceptions to the GNU GPL (e.g. GNU Classpath)
GNU GPL 1, 2, 3
GNU LGPL 2, 2.1, 3
GNU Affero GPL 3





- Original Message -
From: "Awasum Yannick" <awa...@apache.org>
To: "dev" <dev@fineract.apache.org>
Sent: Saturday, March 10, 2018 6:29:51 PM
Subject: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA 
Migration.

Hello Everyone,

I am hoping we could take some time to discuss and come up with approaches
for achieving full Apache compliance on the Fineract CN project.
I think there are still dependencies on Fineract CN which need some
attention in terms of checking the licenses and making sure they are
compliant with the Apache license.

To that end, I began looking at the Microservices and checking the license
of each dependency in accordance with this list:
https://www.apache.org/legal/resolved.html

Within the mariadb component, i realized that the
*mariadb-java-client* uses LGPL 2.1
 (Is this compliant with the Apache license? ).

I don't know if there are other dependencies which are not Apache
compliant like the known case: Hibernate.

To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
the following:

* Replace the Hibernate Validator with something more Apache compliant like
javax.validation.*
or a corresponding OpenJPA library if such exists.

* Configure and set the LocalContainerEntityManagerFactoryBean ( within

MariaDBJavaConfiguratio
n )
 
to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
HibernateJpaVendorAdapter ) within mariadb component. And also the set the
right properties for OpenJPA ( peristence unit etc ).

I will like more experienced developers/architects in the community weigh
in and provide additional details which will enable the gradual migration
from Hibernate to OpenJPA and to get other non-compliant dependencies
migrated too. From this point, volunteers can pick this up and make
progress.


Thanks.
Awasum Yannick.

Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.

[Sendoro Juma]

LPGL 2.1 is categorically included as not compliant.

WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?
Binary Code License (BCL)
Special exceptions to the GNU GPL (e.g. GNU Classpath)
GNU GPL 1, 2, 3
GNU LGPL 2, 2.1, 3
GNU Affero GPL 3





- Original Message -
From: "Awasum Yannick" 
To: "dev" 
Sent: Saturday, March 10, 2018 6:29:51 PM
Subject: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA 
Migration.

Hello Everyone,

I am hoping we could take some time to discuss and come up with approaches
for achieving full Apache compliance on the Fineract CN project.
I think there are still dependencies on Fineract CN which need some
attention in terms of checking the licenses and making sure they are
compliant with the Apache license.

To that end, I began looking at the Microservices and checking the license
of each dependency in accordance with this list:
https://www.apache.org/legal/resolved.html

Within the mariadb component, i realized that the
*mariadb-java-client* uses LGPL 2.1
 (Is this compliant with the Apache license? ).

I don't know if there are other dependencies which are not Apache
compliant like the known case: Hibernate.

To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
the following:

* Replace the Hibernate Validator with something more Apache compliant like
javax.validation.*
or a corresponding OpenJPA library if such exists.

* Configure and set the LocalContainerEntityManagerFactoryBean ( within

MariaDBJavaConfiguratio
n )
 
to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
HibernateJpaVendorAdapter ) within mariadb component. And also the set the
right properties for OpenJPA ( peristence unit etc ).

I will like more experienced developers/architects in the community weigh
in and provide additional details which will enable the gradual migration
from Hibernate to OpenJPA and to get other non-compliant dependencies
migrated too. From this point, volunteers can pick this up and make
progress.


Thanks.
Awasum Yannick.

Fwd: svn commit: r25905 - /release/fineract/1.1.0/

[Sendoro Juma]

Hello Devs,

The download page http://fineract.apache.org/ still has 1.0.0 is right?

Regards
Sendoro

- Forwarded Message -
From: "Avik Ganguly" 
To: comm...@fineract.apache.org
Sent: Friday, March 23, 2018 4:14:24 PM
Subject: svn commit: r25905 - /release/fineract/1.1.0/

Author: avikg
Date: Fri Mar 23 14:14:24 2018
New Revision: 25905

Log:
Publishing 1.1 release.

Added:
release/fineract/1.1.0/
release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz   (with props)
release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz.asc
release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz.sha
release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz   (with props)
release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz.asc
release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz.sha

Added: release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz
==
Binary file - no diff available.

Propchange: release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz
--
svn:mime-type = application/octet-stream

Added: release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz.asc
==
--- release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz.asc (added)
+++ release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz.asc Fri Mar 23 
14:14:24 2018
@@ -0,0 +1,11 @@
+-BEGIN PGP SIGNATURE-
+
+iQEzBAABCAAdFiEEaAUxUuW0grkZE5TDfqzYCTj4THIFAlqi7kQACgkQfqzYCTj4
+THIHSAf+Nw/LTn83AZ8CoYVpBI7img+V2i0duj852/4MmsISTNAXhHl5CaiXbFWD
+RzpvCugo/l4rONA345uCA/OwnWqTZnqVQdVTII/7lLprpi/Xn1fwWJAhHrghjgo2
+6Ci7kmNP44j8u09X2XDuQYwcW1y14WdLdmkwIaIBiXMxYGWd1IyErHN6k05BCvQ3
+runkieUPmEczxX0ggpdoPeGFa3jOPrZdMS32PpYDCx4MV/ZCeEoHtf/Wo0LLYRWa
+7Pg1W8Z0KUYUvcvjxdKJVSXqKb+R+n+CGovrZQ2WXafgyxSps0bIWE2mxxX2spTY
+BAfy/v6pIsceZx3zfRu/KS3ma8JGVw==
+=/jiy
+-END PGP SIGNATURE-

Added: release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz.sha
==
--- release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz.sha (added)
+++ release/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz.sha Fri Mar 23 
14:14:24 2018
@@ -0,0 +1,4 @@
+apache-fineract-1.1.0-binary.tar.gz: 4EC4D62F 1433C1FD 55198FF9 47BB7770
+ CEB48C06 7232B522 A726E7E9 F6C717E1
+ 9C872AE0 5C91A522 31097262 627FD3FE
+ 752FFD89 A6E2A3ED 8346D626 D9A257BA

Added: release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz
==
Binary file - no diff available.

Propchange: release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz
--
svn:mime-type = application/octet-stream

Added: release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz.asc
==
--- release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz.asc (added)
+++ release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz.asc Fri Mar 23 
14:14:24 2018
@@ -0,0 +1,11 @@
+-BEGIN PGP SIGNATURE-
+
+iQEzBAABCAAdFiEEaAUxUuW0grkZE5TDfqzYCTj4THIFAlqi7RMACgkQfqzYCTj4
+THKvcgf9FNXbE1f8q4TORY86JpJ9K0WZMYaXsQFMbtpk+iU2gHkgr6yQ5tVmf/tl
+OygGEWo/FhpMgwAKe71NAO/5AG+0LyXYfQycGe0JUDFZs7FlQFPQAYGM/IjDFRG9
+3w2hyIIxTYW4oGNRnHeP0+lSg4pA0gtHnYMchUtcCjNYcSUF7xnwDrwN4/P7X08Y
+TZUMHgb8oPBKWneP3fI8hRlaXgMAjnsqzKmsSKmVtTljg4VhvopA2R4TH/3dxBDl
+XA0UgP+0+0XVhEG2ZQ0OsO0HKCzzr20mAJEnXEQZcGgMHfQ8F0jf9Sw4zwareSQM
+h9+InASNd5YUNmeHjbfF5eb2kuWibg==
+=HJve
+-END PGP SIGNATURE-

Added: release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz.sha
==
--- release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz.sha (added)
+++ release/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz.sha Fri Mar 23 
14:14:24 2018
@@ -0,0 +1,4 @@
+apache-fineract-1.1.0-src.tar.gz: FB8003B5 F12A00AF B88657EC F811150A 537DA04C
+  41E1BB44 D917243C 105726B2 3076B967 D89BE96C
+  DDC16609 89C403FE 393405E8 DB0DBBD4 34151A85
+  DCAFD0CB

Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Sendoro Juma]

Hello Steve,

Indeed we are happy to have you as committer

Wish you all the best.

Cheers
Sendoro

- Original Message -
From: "Ed Cable" 
To: "dev" 
Sent: Wednesday, March 28, 2018 5:07:03 PM
Subject: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

Hello Fineract community,

I'm proud to announce that Apache Fineract has a new committer.

Steve has only been a part of the community for a couple months after being
introduced to us by the team at Musoni. By day Steve is a full-stack
developer at Dassault Systems. In his spare time, he's been doing all he
can to support the community. In that short time, he's added tremendous
value and as a committer will be able to help the community release more
frequently. He fixed a number of critical bugs in the latest release, added
support for MySQL 5.7 and is now working on both the payment gateway
project and Mojaloop integration with Fineract.

The Mifos Initiative recognized him as a Star Contributor recently so click
here to learn more about Steve:
http://mifos.org/blog/star-contributor-steve-conrad/

Congratulations Steve!  Thank you for your contributions, and we look
forward to your leadership in the community!

Best Regards,

Ed Cable

Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

[Sendoro Juma]

My comments below is related to item no.2 not 3

- Original Message -
From: "Sendoro Juma" <sendoro@singo.africa>
To: "dev" <dev@fineract.apache.org>
Cc: "mifos-developer" <mifos-develo...@lists.sourceforge.net>
Sent: Wednesday, March 21, 2018 8:07:34 AM
Subject: Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

Hello Ed, Dev

On item no. 3 on registration verification

I think mobile phone verification is even more important than email nowadays, 
so it can be both email and phone.. it should be added and I suggest to be a 
MUST.

Regards
Sendoro

- Original Message -
From: "Ed Cable" <edca...@mifos.org>
To: "dev" <dev@fineract.apache.org>
Cc: "mifos-developer" <mifos-develo...@lists.sourceforge.net>
Sent: Wednesday, March 21, 2018 5:40:22 AM
Subject: Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

Hi all,

As a follow-up to this thread, Sundari has fleshed out some more details
supporting the use cases Nayan had proposed for a client-facing digital
credit app at

https://cwiki.apache.org/confluence/display/FINERACT/Digital+Credit+App

Markus, Myrle, or others - it'd be great to get your input as to how you'd
securely enable clients to access the data needed in such an app.

Ed

On Fri, Jan 26, 2018 at 6:20 PM, Ed Cable <edca...@mifos.org> wrote:

> Hi Markus,
>
> Thanks for your replies.
>
> For the rest of the community,
>
> While I know that with the previous iteration of self-service apps, we
> focused on implementing the back-end first and then allowing front-end use
> cases to follow, a good approach this time around would be to get some
> solid client-facing use cases identified and then design the back-end and
> integration with the data to support those use cases. Nayan from RuPie has
> shared some initial use cases he has. I'm working with a Mifos volunteer,
> Sundari Swami, to flesh these out further but wanted to share the initial
> use cases Nayan had presented to stimulate further discussion on what the
> best approach to supporting a client-facing app on Apache Fineract CN that
> would support adequately:
>
> From customer side
>
> UC 1. Client signup with basic data, and spot verification either with OTP
> to mobile number or Aadhaar verification
> UC 2. Customer can enter customer's other details like address, family,
> work, income/expense details, once this data is verified from back office,
> customer can't edit any of these data
> UC 3. Apply for loans
> UC 4. Repay EMI
> UC 5. Preclose his/her loans
> UC 6. Log support request
> UC 7. Upload documents like photo of electricity bills, voter id, passport
> etc, once documents are verified and accepted from back office customer
> cab't edit , delete the verified documents, but customer can upload new
> documents
>
> From organization point of view
>
> UC 1, Offer loan products based below criteria
>
>
>- Location ( Example, Bengaluru has P1 and P2 products where as jaipur
>has P2 and P3 products )
>- Based on customer work profile ( for salaried person offer personal
>loans, for business person offer working capital )
>- based gander, income etc
>
> UC 2. User management, (In Rupie's case they have around six thousand self
>  service users, need effective user management suite, search user, user
> activity tracking etc)
> - So user management has to be a lot more robust than user management from
> the perspective of staff users.
> UC 3.  Push ad-hoc/rule based/event based notification to users
>
> Ed
>
> On Tue, Jan 16, 2018 at 11:58 AM, Markus Geiss <m...@apache.org> wrote:
>
>> Dear Ed,
>>
>> We at Kuelap have no plans because believe we should never give members,
>> agents, or other third parties direct access to the financial
>> institution's
>> data.
>> Aside from any regulatory standpoint this is a huge flaw in the current
>> system.
>>
>> My company is working on two offline-first clients that we think are more
>> secure
>> architecture; one will provide a reduced set of functionalities for
>> employees
>> working in remote areas; The second one will provide mobile banking
>> functionalities for members of financial institutions.
>>
>> Once the company feels the time is right to share our work, we may propose
>> these apps or at least the secure architecture to the community, but we
>> are
>> not nearly far enough along to do that now.
>>
>> Cheers
>>
>> Markus
>>
>> .::Yagni likes a DRY KISS::.
>>
>>
>> On Tue, Jan 16, 2018 at 3:54 PM Ed Cable <edca...@mifos.org> wrote:
>>
>> > Markus, Mark or

Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

[Sendoro Juma]

Hello Ed, Dev

On item no. 3 on registration verification

I think mobile phone verification is even more important than email nowadays, 
so it can be both email and phone.. it should be added and I suggest to be a 
MUST.

Regards
Sendoro

- Original Message -
From: "Ed Cable" 
To: "dev" 
Cc: "mifos-developer" 
Sent: Wednesday, March 21, 2018 5:40:22 AM
Subject: Re: Self-Service Access for Client-Facing Apps on Apache Fineract CN

Hi all,

As a follow-up to this thread, Sundari has fleshed out some more details
supporting the use cases Nayan had proposed for a client-facing digital
credit app at

https://cwiki.apache.org/confluence/display/FINERACT/Digital+Credit+App

Markus, Myrle, or others - it'd be great to get your input as to how you'd
securely enable clients to access the data needed in such an app.

Ed

On Fri, Jan 26, 2018 at 6:20 PM, Ed Cable  wrote:

> Hi Markus,
>
> Thanks for your replies.
>
> For the rest of the community,
>
> While I know that with the previous iteration of self-service apps, we
> focused on implementing the back-end first and then allowing front-end use
> cases to follow, a good approach this time around would be to get some
> solid client-facing use cases identified and then design the back-end and
> integration with the data to support those use cases. Nayan from RuPie has
> shared some initial use cases he has. I'm working with a Mifos volunteer,
> Sundari Swami, to flesh these out further but wanted to share the initial
> use cases Nayan had presented to stimulate further discussion on what the
> best approach to supporting a client-facing app on Apache Fineract CN that
> would support adequately:
>
> From customer side
>
> UC 1. Client signup with basic data, and spot verification either with OTP
> to mobile number or Aadhaar verification
> UC 2. Customer can enter customer's other details like address, family,
> work, income/expense details, once this data is verified from back office,
> customer can't edit any of these data
> UC 3. Apply for loans
> UC 4. Repay EMI
> UC 5. Preclose his/her loans
> UC 6. Log support request
> UC 7. Upload documents like photo of electricity bills, voter id, passport
> etc, once documents are verified and accepted from back office customer
> cab't edit , delete the verified documents, but customer can upload new
> documents
>
> From organization point of view
>
> UC 1, Offer loan products based below criteria
>
>
>- Location ( Example, Bengaluru has P1 and P2 products where as jaipur
>has P2 and P3 products )
>- Based on customer work profile ( for salaried person offer personal
>loans, for business person offer working capital )
>- based gander, income etc
>
> UC 2. User management, (In Rupie's case they have around six thousand self
>  service users, need effective user management suite, search user, user
> activity tracking etc)
> - So user management has to be a lot more robust than user management from
> the perspective of staff users.
> UC 3.  Push ad-hoc/rule based/event based notification to users
>
> Ed
>
> On Tue, Jan 16, 2018 at 11:58 AM, Markus Geiss  wrote:
>
>> Dear Ed,
>>
>> We at Kuelap have no plans because believe we should never give members,
>> agents, or other third parties direct access to the financial
>> institution's
>> data.
>> Aside from any regulatory standpoint this is a huge flaw in the current
>> system.
>>
>> My company is working on two offline-first clients that we think are more
>> secure
>> architecture; one will provide a reduced set of functionalities for
>> employees
>> working in remote areas; The second one will provide mobile banking
>> functionalities for members of financial institutions.
>>
>> Once the company feels the time is right to share our work, we may propose
>> these apps or at least the secure architecture to the community, but we
>> are
>> not nearly far enough along to do that now.
>>
>> Cheers
>>
>> Markus
>>
>> .::Yagni likes a DRY KISS::.
>>
>>
>> On Tue, Jan 16, 2018 at 3:54 PM Ed Cable  wrote:
>>
>> > Markus, Mark or others who could best respond,
>> >
>> > What is the planned design for enabling third parties (i.e. non-staff)
>> such
>> > as clients, agents, etc to authenticate themselves and access data
>> within
>> > Apache Fineract CN.
>> >
>> > From what I recalled, you were planning to take a more secure approach
>> than
>> > simply providing a self-service API that has access to the full
>> production
>> > database but rather have a separate data layer for self-service users?
>> >
>> > Could you update the community on what the plans are for providing
>> access
>> > to enable these client-facing applications? Is it documented anywhere?
>> >
>> > One reason I ask is it that as the Mifos Initiative thinks about GSOC
>> 2018,
>> > I'd like to consider a project on building out an initial mobile banking
>> > 

Re: [VOTE] Apache Fineract 1.1.0

[Sendoro Juma]

+1

- Original Message -
From: "Avik Ganguly" 
To: "dev" 
Sent: Tuesday, March 20, 2018 12:05:49 AM
Subject: [VOTE] Apache Fineract 1.1.0

Hello Fineract community,

We have created the Apache Fineract 1.1.0 release, with the artifacts
below up for a vote.

These are the goals of this release:

   - Share the new features & bugs fixes that have been developed so far,
   to give the community a good sense of the upcoming 1.1.0 release

*For more information including release notes, please see:*
https://cwiki.apache.org/confluence/display/FINERACT/1.1.0+-+Apache+Fineract

*Source & Binary files:*
https://dist.apache.org/repos/dist/dev/fineract/1.1.0/
Source:
https://dist.apache.org/repos/dist/dev/fineract/1.1.0/apache-fineract-1.1.0-src.tar.gz
Binary/War :

https://dist.apache.org/repos/dist/dev/fineract/1.1.0/apache-fineract-1.1.0-binary.tar.gz

*Commit to be voted on:*
https://git-wip-us.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.1.0

*Source build verification steps can be found at:*
Refer 'README.md' in apache-fineract-1.1.0-src.tar.gz

*Binary Deployment steps can be found at:*
https://cwiki.apache.org/confluence/display/FINERACT/
Fineract+Installation+on+Ubuntu+Server

*KEYS file containing PGP Keys we use to sign the release: *
https://dist.apache.org/repos/dist/dev/fineract/KEYS

Vote will be open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Let me know if there are any discrepancies in the signing process.


Here's my +1
Thanks,
Avik.

Re: [Mifos-developer] Existing Clients Not Appearing as Guarantors

[Sendoro Juma]

Hello Amit,

I have looked at, 

I think the best way is to open a New Ticket, Describing it clearly including 
the workaround fix, plus actual suggestion on what to be done.

In the New Ticket ensure referencing by putting the link of the old closed 
tickets!!!

Cheers
Sendoro 

- Original Message -
From: "Amit Sharma" <amkrsha...@gmail.com>
To: "dev" <dev@fineract.apache.org>
Cc: "mifos-users" <mifos-us...@lists.sourceforge.net>, "mifos-developer" 
<mifos-develo...@lists.sourceforge.net>
Sent: Monday, March 19, 2018 3:29:06 PM
Subject: Re: [Mifos-developer] Existing Clients Not Appearing as Guarantors

Sure Sendoro, should I re-open the closed JIRA ticket or raise a new one
for this

On Sun, Mar 18, 2018 at 3:53 PM, Sendoro Juma <sendoro@singo.africa> wrote:

> Hello Amit,
>
> Great you got a fix, but a work-around as far as community is concern,
>
> Would you please be so kind to initiate a respective ticket on this?
>
> Regards
> Sendoro
>
> - Original Message -
> From: "Amit Sharma" <amkrsha...@gmail.com>
> To: "dev" <dev@fineract.apache.org>, "mifos-users" <mifos-users@lists.
> sourceforge.net>
> Cc: "mifos-developer" <mifos-develo...@lists.sourceforge.net>
> Sent: Sunday, March 18, 2018 12:02:35 PM
> Subject: Re: [Mifos-developer] Existing Clients Not Appearing as Guarantors
>
> Hi All,
>
> I have been able to fix it at my end by updating ResourceFactoryProvider
> with text in blue
>
>  clientResource: defineResource(apiVer +
> "/clients/:clientId/:anotherresource", {clientId: '@clientId',
> anotherresource: '@anotherresource', sqlSearch: '@sqlSearch'}, {
> getAllClients: {method: 'GET', params: {limit:
> 1000, sqlSearch: '@sqlSearch'}},
> getAllClientsWithoutLimit: {method: 'GET',
> params: {limit:
> 0}},
>
>
> Thanks Robert and Team Conflux for the guidance and help. I suggest that we
> take this up in the upcoming release.
>
> Thanks & Regards,
> Amit Sharma
> Prashray Foundation for Micro Credit
>
> On Sat, Mar 17, 2018 at 12:51 PM, Ed Cable <edca...@mifos.org> wrote:
>
> > Amit,
> >
> > I'm adding this back onto the list so Nazeer and others can attempt to
> > respond.
> >
> > Ed
> >
> > -- Forwarded message --
> > From: Amit Sharma <amkrsha...@gmail.com>
> > Date: Sat, Mar 17, 2018 at 12:10 AM
> > Subject: Re: [Mifos-developer] Existing Clients Not Appearing as
> Guarantors
> > To: Santosh Math <sant...@confluxtechnologies.com>, Sampath Kumar G <
> > samp...@confluxtechnologies.com>, Ippez Robert <ippezrob...@gmail.com>,
> > Ed Cable <edca...@mifos.org>
> >
> >
> > Hi All,
> >
> > I looked into this further and am of the opinion that while fixing
> > MIFOSX-2543 and community-app/issues/1868 ; while we removed the
> parameter
> > limit=1000, we have now introduced a new bug in the system that restricts
> > the count to 200 and because of this none of the clients after row count
> > 200 are appearing as Guarantors to be added. Refer screenshots attached.
> >
> > Please assist in the way forward as all loan disbursements in our
> > organization have stopped. We disburse collateral free individual loans
> on
> > personal guarantees and this is a blocker for us.
> >
> >
> >
> >
> >
> >
> >
> >
> > Regards,
> > Amit Sharma
> > Prashray Foundation for Micro Credit
> >
> >
> >
> >
> > On Fri, Mar 16, 2018 at 4:06 PM, Santosh Math <
> > sant...@confluxtechnologies.com> wrote:
> >
> >> Adding +Robert.
> >>
> >> Hi Robert,
> >>
> >> Do you want to comment on this?
> >>
> >>
> >> On Fri, Mar 16, 2018 at 3:20 PM, Amit Sharma <amkrsha...@gmail.com>
> >> wrote:
> >>
> >>> Hi Santosh and Sampath,
> >>>
> >>> Found something with the hit and trial I am doing, looks like the cause
> >>> of the problem, you are better placed to confirm.
> >>>
> >>> Our Database has 212 client records, clients upto 200 are popping up as
> >>> existing clients that can be added as guarantor and the last 12 arent.
> >>>
> >>> I made the following API call : https://localhost/fineract-pro
> >>> vider/api/v1/clients?tenantIdentifier=default=true
> >>>
> >>> While it shows 212 filtered records, it shows only the first 200 under
> &g

Re: [ANNOUNCE] New Apache Fineract Committer Isaac Kamga

[Sendoro Juma]

Hello Isaac,

Congratulations and looking forward for the great work from you... 

Regards
Sendoro

- Original Message -
From: "Myrle Krantz" 
To: "dev" 
Sent: Monday, March 19, 2018 10:58:41 AM
Subject: [ANNOUNCE] New Apache Fineract Committer Isaac Kamga

Hello Fineract Fans!

I'm proud to announce that Apache Fineract has a new committer.

Isaac Kamga is a founder and FOSS evangelist at the The Google
Developer Group Buea in Cameroon, and a technical community evangelist
for the Mifos Initiative.  Isaac has been helping us bring Fineract CN
into the Fineract project.

Congratulations Isaac!  Thank you for your contributions, and thank
you for accepting our invitation!

Best Regards,
Myrle Krantz
PMC Member, Apache Fineract

P.S. Isaac, would you mind if I announce your committership on twitter
as well?  Your handle is ikamga right?

Re: Customer Chat/Support Use Cases in Mobile and ONline Banking Apps

[Sendoro Juma]

Hello Ed, 

My comment 

Isn't decision of which chat tool to use itself being extremely critical? 

Doesn't it qualify a sub-project on its own?, of which at the end of the day 
will bring out a report that tells which one and why? 
There must some principle of choosing e.g. simplicity, licensing match, 
architecture similarity, future of the tool etc... 

Regards 
Sendoro 


From: "Ed Cable"  
To: "dev" , "mifos-developer" 
, "user" , 
"mifos-users"  
Sent: Saturday, March 17, 2018 10:42:52 AM 
Subject: Customer Chat/Support Use Cases in Mobile and ONline Banking Apps 

Hello all, 
Part of the scope of a number of the GSOC projects we're exploring this summer 
is a customer support/chat interface within the mobile banking and online 
banking apps. We wanted to discuss potential use cases with the community for 
feedback as this chat/support interface would be a part of three GSOC projects 
- the mobile banking app, online banking app, and the self-service admin 
portal. 

>From the perspective of the client, the chat/customer support interface would 
>allow them to send asynchronous messages from a single view to all support 
>staff of the financial institution. From this single view, they should also be 
>able to see a full history of the chat. If a client has both the online and 
>mobile banking app, the it should be the same unified chat view that is shared 
>across both apps. 

>From the perspective of the staff, 
- The respective staff should get notified of incoming chat messages (either if 
they're the assigned loan officer, an admin or a designated support resource. 
- All respective staff that get notified should be able to respond uniquely as 
an individual but responses from all staff should be in the same interface so 
it's like a one to many chat. 
- Staff should receive these notifications and in the self-service admin portal 
there should be a view for responding to incoming chat/support messages. 
- Al chat history should also be displayed in a new tab in the client record so 
a fully history of communications can be viewed there. 

Can the community please provide feedback on these use cases, Is this a 
communication channel that your client base would actually utilize? 

For the prospective GSOC aspirants, as discussed on the list, we need to 
identify an open source tool that can be embedded in both the mobile and web 
apps. 

Raunak is going to be working on some mockups as well. 

Ed 

Re: [Mifos-developer] Service for OTP generation

[Sendoro Juma]

Hello Sridha, 

Good idea, 

Would you also mind looking at this 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67641984 

Cheers 
Sendoro 


From: "sridhar jajoo"  
To: "mifos-developer"  
Sent: Thursday, March 15, 2018 3:29:37 AM 
Subject: [Mifos-developer] Service for OTP generation 

Hello mentors 
I would like to know whether it would be a good idea to integrate OTP service 
for logging in into the account for fineract-cn-2.0 as it would lead to 
increased security? 

Thanks 

-- 
Check out the vibrant tech community on one of the world's most 
engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
Mifos-developer mailing list 
mifos-develo...@lists.sourceforge.net 
Unsubscribe or change settings at: 
https://lists.sourceforge.net/lists/listinfo/mifos-developer 

Re: [Mifos-developer] Interesting in fixing issues

[Sendoro Juma]

Hello Cabrel, 

I'm not sure what exactly you mean by Apache Fineract; but let me share this 
way: 

1. Apache Fineract Issues arranged in priority 
[ 
https://issues.apache.org/jira/projects/FINERACT/issues/FINERACT-602?filter=allopenissues
 | 
https://issues.apache.org/jira/projects/FINERACT/issues/FINERACT-602?filter=allopenissues
 ] 

PR already done: 
https://github.com/apache/fineract/pulls 

Candidate Release, to ensure you don't work on Issue that already worked on 
only not closed. 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12340624==12319420=Create_token=A5KQ-2QAV-T4JA-FDED%7C7616978f36b22cf7dc20a899a3cbf9f614960808%7Clin
 



2. [ https://github.com/openMF/community-app/issues | Mifos Community App ] 

Hope this helps 

Have cc dev; please include yourself in the Apache Fineract Mailing list. 


Regards 
Sendoro 

From: "Ghislain cabrel"  
To: "mifos-developer"  
Sent: Monday, March 5, 2018 12:22:09 PM 
Subject: [Mifos-developer] Interesting in fixing issues 

Good morning to all, 

I am Cabrel Kemfang software engineering student from the University of Buea, 
Cameroon. 

I am interested in Apache Fineract and I wish to start fixing issues on it . 
Please what are the priority issues for which i should start working on. 

Thank 
Regards 
Cabrel Kemfang 

-- 
Check out the vibrant tech community on one of the world's most 
engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
Mifos-developer mailing list 
mifos-develo...@lists.sourceforge.net 
Unsubscribe or change settings at: 
https://lists.sourceforge.net/lists/listinfo/mifos-developer 

Re: Migration to MySQL 5.7

[Sendoro Juma]

Hello Steve,

My input:-

Option 2: with plan for Release 1.3 o to ensure a thorough test as you put it 
right. 

Cheers
Sendoro

- Original Message -
From: "Steve Conrad" 
To: "dev" 
Cc: "mifos-developer" 
Sent: Thursday, February 22, 2018 5:29:36 PM
Subject: Re: Migration to MySQL 5.7

Hi all -

I wanted to revisit this conversation.I have been working on this
migration, and there are 2 possible approaches that we can take.

1) Require the user to turn off ONLY_FULL_GROUP_BY in sql_mode for the
MySQL instance (in /etc/mysql/my.cnf for most users). As of MySQL 5.7.5
this is turned on by default. The advantage of this approach is that it
requires only 1 change to migration files, and reduces the risks (as
pointed out by Nikhil and others) of breaking Read Platform services,
Pentaho reports, and any other externally configured queries.

2) Use the default settings where ONLY_FULL_GROUP_BY is on. This requires
more changes to the migration scripts and would require more testing of
external services and reports.

The following link gives some good background on ONLY_FULL_GROUP_BY -
http://rpbouman.blogspot.nl/2014/09/mysql-575-group-by-respects-functional.html

My recommendation would be to leave ONLY_FULL_GROUP_BY on and do the
thorough testing that is required. However, I welcome your input and
thoughts.
Thanks,
Steve


On Wed, Jan 17, 2018 at 8:00 PM, Nikhil Pawar  wrote:

> Hi Steve,
>
> +1 from my side as well.
> I think the areas where the application directly interacts with database (
> w/o any intermediate layer like OpenJPA) would be more vulnerable.
> The places to look out according to me would be:
>  1) Migration scripts (which you are already aware of)
>  2) Various ReadPlatform services wherein we have written SQLs to fetch
> data from database.
> 3) Pentaho Reports (not quite sure about it but this module needs to be
> thoroughly tested after migration).
>
> Regards,
> Nikhil
>
>
>
> On Wed, Jan 17, 2018 at 8:48 AM, Steve Conrad  wrote:
>
> > To the Mifos and Fineract dev communities -
> >
> > My name is Steve Conrad, and I have recently begun volunteering with the
> > Mifos/Fineract community and really appreciate the great work that you
> all
> > are doing.
> >
> > I wanted to propose a new project to migrate the Fineract platform to
> MySQL
> > 5.7. There are several features in MySQL 5.7 that would benefit the
> project
> > - performance, embedded JSON objects in the schema, multithreaded
> > replication, among others.
> >
> > When I installed Fineract locally, I used MySQL 5.7. I had to change a
> few
> > of the database migration scripts. I have obviously not gone through all
> of
> > the use cases, but so far am running with no issues.
> >
> > Does anyone know of any reasons why we could not move to MySQL 5.7?
> > Obviously there would be a large testing task, but it may be a worthwhile
> > investment to keep the Fineract platform current.
> >
> > Thanks,
> > Steve
> >
>

Re: Planning Apache Fineract 1.2 Release

[Sendoro Juma]

gt; On 2/12/18 9:32 AM, Ed Cable wrote:
>>>>>>> Here's the link to screencast from the discussion:
>>>>>>> https://youtu.be/xnTGf4R2s5k
>>>>>>>
>>>>>>> Ed
>>>>>>>
>>>>>>> On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable <edca...@mifos.org>
>> wrote:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Thanks to Nazeer for leading this session and the sizeable group
>> that
>>>>>>>> attended. Based on the process, we can clearly use the assistance
>> of
>>>>>> other
>>>>>>>> community members in the planning process and committers in the
>>>>> release
>>>>>>>> process so happy we had such good attendance.
>>>>>>>>
>>>>>>>> Based on the discussion, here's a proposal of how timing might
>> look
>>>>> for
>>>>>>>> monthly release cycles with planning (a new phase) starting out
>> six
>>>>>> months
>>>>>>>> prior to the release date.
>>>>>>>>
>>>>>>>> Screencast of session will be posted soon.
>>>>>>>>
>>>>>>>> Please comment on the notes in the table and here's proposed
>> timing
>>>>> for
>>>>>>>> the next 1.2 release:
>>>>>>>>
>>>>>>>> Plans for Release Apache Fineract 1.2
>>>>>>>>
>>>>>>>> Planning Release - Start with a Meeting on Feb 14
>>>>>> How about starting with a discussion on this list?  Relying on
>>>>>> synchronous meetings cuts out people who can't attend due to time
>>>>>> zones / other commitments.
>>>>>>
>>>>>> Phil
>>>>>>>> Announce Release - Feb 28
>>>>>>>>
>>>>>>>> QA - Feb 28 - March 14
>>>>>>>>
>>>>>>>> Publish Release Notes - March 14
>>>>>>>>
>>>>>>>> Vote on Release - March 21
>>>>>>>>
>>>>>>>> Target release date - March 28
>>>>>>>>
>>>>>>>> Stage
>>>>>>>>
>>>>>>>> Description
>>>>>>>>
>>>>>>>> Proposed Length
>>>>>>>>
>>>>>>>> How Far in Advance of Release (Proposed)
>>>>>>>>
>>>>>>>> How Far in Advance of Release (Currently)
>>>>>>>>
>>>>>>>> Planning of Next Release
>>>>>>>>
>>>>>>>> Discuss with community what would like to ship in next release and
>>>>> what
>>>>>>>> people could work on.
>>>>>>>>
>>>>>>>> Create fix version on JIRA to assign to.
>>>>>>>>
>>>>>>>> Action: modify existing email template to open up planning
>> process,
>>>>>>>> schedule a meeting to discuss and set a tentative branching date
>>>>> (i.e. 2
>>>>>>>> weeks later, if release date is a month past that).
>>>>>>>>
>>>>>>>> .
>>>>>>>>
>>>>>>>> 1 week
>>>>>>>>
>>>>>>>> 6 weeks
>>>>>>>>
>>>>>>>> Doesn’t Exist
>>>>>>>>
>>>>>>>> Announcement of Release
>>>>>>>>
>>>>>>>> Announce what is going to come in the release (should be 80% done
>> at
>>>>>>>> least).
>>>>>>>>
>>>>>>>> Cut a release branch and freeze release branch and then develop
>>>>> branch
>>>>>> can
>>>>>>>> still have active work on it but only in rare cases might anything
>>>>>>>> additional from develop
>>>>>>>>
>>>>>>>> Email out sharing release branch details
>>>>>>>>
>>>>>>>> 4 weeks prior
>>>>>>>>
>>>>>>>> 1 - 2 months
>>>>>>>>
>>

Re: Planning Apache Fineract 1.2 Release

[Sendoro Juma]

Dear Myrle,

I see your point:

I think primarily we should agree that it is time-driven:

Features listed or to be listed should be taken only as way of making focus and 
pushing for tasks to be completed in-time as per release schedule, should they 
fall short of time... we should move on... with our primary commitment which is 
time.

How about that?

Best Regards
Sendoro



- Original Message -
From: "Myrle Krantz" <my...@apache.org>
To: "dev" <dev@fineract.apache.org>
Sent: Wednesday, February 14, 2018 1:55:03 PM
Subject: Re: Planning Apache Fineract 1.2 Release

Our release can either be feature-driven or time-driven.  Not both.
If it's feature-driven, we don't release until the features are in
there.  If it's time-driven, we release on a certain date, based on
what's made it in.

Are we in agreement that we wish to make a time-driven release?  Then
we should be adding a feature to the list for a given release when
that feature is integrated, and not before.

Best Regards,
Myrle


On Wed, Feb 14, 2018 at 12:41 PM, Sendoro Juma <sendoro@singo.africa> wrote:
> Hello Ed,
>
> +1 on all you mentioned!
>
> I would propose additional point which you have kind of mention it already on 
> item related to API Swagger, but just as emphasize
>
> - APIs related issues/Enhancements that has been discovered by Mobile or Web 
> client application side.
>
> This is so,  because we might take longer in addressing issues already known 
> from client application side; buy just because of missing visibility;
> So having this branch in Wiki page will remind us.
>
>
> Best Regards
>
> - Original Message -
> From: "Sendoro Juma" <sendoro@singo.africa>
> To: "dev" <dev@fineract.apache.org>
> Cc: "robertjakech Jakech" <robertjak...@gmail.com>
> Sent: Wednesday, February 14, 2018 1:38:01 PM
> Subject: Re: Planning Apache Fineract 1.2 Release
>
> Hello Ed,
>
> +1 on all mentioned!
>
> I would propose additional point which you have kind of mention already on 
> API Swagger it, but just as emphasize
>
> - APIs related issues/Enhancements that has been discovered by Mobile or Web 
> Client Application side.
>
> This is so,  because we might take longer in addressing should known from 
> client application side by juts because of missing visibility;
> So having this branch in Wiki page will remind us.
>
>
> Best Regards
> Sendoro
>
>
>
> - Original Message -
> From: "Ed Cable" <edca...@mifos.org>
> To: "dev" <dev@fineract.apache.org>, "robertjakech Jakech" 
> <robertjak...@gmail.com>
> Sent: Wednesday, February 14, 2018 9:41:07 AM
> Subject: Planning Apache Fineract 1.2 Release
>
> That is a great suggestion Phil and of course any synchronous meeting would
> only complement the discussion on the list and collaboraton on the wiki
> that we'll be having.
>
> Taking up Phil's suggestion, let's begin the discussion on this new thread
> for planning what should goi into Apache Fineract 1.2. To assist in that
> I've set up a wiki page at
> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract
>
> Based on what I know others have been working on, here's my take on some of
> the work that could be included in the release.
>
>- GSIM/GLIM Work from Nikhil as part of GSOC
>- Swagger APIs work done by Sanyam and Chirag
>- Apache Fineract tasks completed by GCI students.
>- Changes contributed by Partners including:
>   - BOWPI Enhancements
>- Stellar/Fineract integration
>- Bug Fixes and Minor Enhancements.
>- PRs from the backlog
>
>
> Let's drive this discussion forward and then a have a synchronous meeting
> later to hammer out details.
>
> Ed
>
> On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz <phil.ste...@gmail.com> wrote:
>
>> On 2/12/18 9:32 AM, Ed Cable wrote:
>> > Here's the link to screencast from the discussion:
>> > https://youtu.be/xnTGf4R2s5k
>> >
>> > Ed
>> >
>> > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable <edca...@mifos.org> wrote:
>> >
>> >> Hi all,
>> >>
>> >> Thanks to Nazeer for leading this session and the sizeable group that
>> >> attended. Based on the process, we can clearly use the assistance of
>> other
>> >> community members in the planning process and committers in the release
>> >> process so happy we had such good attendance.
>> >>
>> >> Based on the discussion, here's a proposal of how timing might look for
>> >> monthly release cycles with planning (a new phase) starting o

Re: Planning Apache Fineract 1.2 Release

[Sendoro Juma]

Hello Ed,

+1 on all you mentioned!

I would propose additional point which you have kind of mention it already on 
item related to API Swagger, but just as emphasize

- APIs related issues/Enhancements that has been discovered by Mobile or Web 
client application side.

This is so,  because we might take longer in addressing issues already known 
from client application side; buy just because of missing visibility; 
So having this branch in Wiki page will remind us.


Best Regards

- Original Message -
From: "Sendoro Juma" <sendoro@singo.africa>
To: "dev" <dev@fineract.apache.org>
Cc: "robertjakech Jakech" <robertjak...@gmail.com>
Sent: Wednesday, February 14, 2018 1:38:01 PM
Subject: Re: Planning Apache Fineract 1.2 Release

Hello Ed,

+1 on all mentioned!

I would propose additional point which you have kind of mention already on API 
Swagger it, but just as emphasize

- APIs related issues/Enhancements that has been discovered by Mobile or Web 
Client Application side.

This is so,  because we might take longer in addressing should known from 
client application side by juts because of missing visibility; 
So having this branch in Wiki page will remind us.


Best Regards
Sendoro 



- Original Message -
From: "Ed Cable" <edca...@mifos.org>
To: "dev" <dev@fineract.apache.org>, "robertjakech Jakech" 
<robertjak...@gmail.com>
Sent: Wednesday, February 14, 2018 9:41:07 AM
Subject: Planning Apache Fineract 1.2 Release

That is a great suggestion Phil and of course any synchronous meeting would
only complement the discussion on the list and collaboraton on the wiki
that we'll be having.

Taking up Phil's suggestion, let's begin the discussion on this new thread
for planning what should goi into Apache Fineract 1.2. To assist in that
I've set up a wiki page at
https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract

Based on what I know others have been working on, here's my take on some of
the work that could be included in the release.

   - GSIM/GLIM Work from Nikhil as part of GSOC
   - Swagger APIs work done by Sanyam and Chirag
   - Apache Fineract tasks completed by GCI students.
   - Changes contributed by Partners including:
  - BOWPI Enhancements
   - Stellar/Fineract integration
   - Bug Fixes and Minor Enhancements.
   - PRs from the backlog


Let's drive this discussion forward and then a have a synchronous meeting
later to hammer out details.

Ed

On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz <phil.ste...@gmail.com> wrote:

> On 2/12/18 9:32 AM, Ed Cable wrote:
> > Here's the link to screencast from the discussion:
> > https://youtu.be/xnTGf4R2s5k
> >
> > Ed
> >
> > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable <edca...@mifos.org> wrote:
> >
> >> Hi all,
> >>
> >> Thanks to Nazeer for leading this session and the sizeable group that
> >> attended. Based on the process, we can clearly use the assistance of
> other
> >> community members in the planning process and committers in the release
> >> process so happy we had such good attendance.
> >>
> >> Based on the discussion, here's a proposal of how timing might look for
> >> monthly release cycles with planning (a new phase) starting out six
> months
> >> prior to the release date.
> >>
> >> Screencast of session will be posted soon.
> >>
> >> Please comment on the notes in the table and here's proposed timing for
> >> the next 1.2 release:
> >>
> >> Plans for Release Apache Fineract 1.2
> >>
> >> Planning Release - Start with a Meeting on Feb 14
>
> How about starting with a discussion on this list?  Relying on
> synchronous meetings cuts out people who can't attend due to time
> zones / other commitments.
>
> Phil
> >>
> >> Announce Release - Feb 28
> >>
> >> QA - Feb 28 - March 14
> >>
> >> Publish Release Notes - March 14
> >>
> >> Vote on Release - March 21
> >>
> >> Target release date - March 28
> >>
> >> Stage
> >>
> >> Description
> >>
> >> Proposed Length
> >>
> >> How Far in Advance of Release (Proposed)
> >>
> >> How Far in Advance of Release (Currently)
> >>
> >> Planning of Next Release
> >>
> >> Discuss with community what would like to ship in next release and what
> >> people could work on.
> >>
> >> Create fix version on JIRA to assign to.
> >>
> >> Action: modify existing email template to open up planning process,
> >> schedule a meeting to discuss and set a tentative branching date (

Re: Planning Apache Fineract 1.2 Release

[Sendoro Juma]

; QA
> >>
> >> QA begins on the release branch - staging Server setup
> >>
> >> Might fix some regression issues
> >>
> >> 1 - 2 weeks
> >>
> >> 4 weeks prior
> >>
> >> JIRA Sanitization/Publish RElease Notes
> >>
> >> Sanitize release documentation
> >>
> >> Create release notes and email community release information with links.
> >>
> >>
> >> 2 weeks prior
> >>
> >> Vote
> >>
> >> Create artifacts, sign release, etc. Open up votes
> >>
> >> 1 week prior
> >>
> >> Release
> >>
> >> Tally up votes, announce, update websites and infrastructure with new
> >> release artifacts.
> >>
> >> Release date
> >>
> >>
> >>
> >>
> >> On Sun, Feb 11, 2018 at 7:40 AM, Ed Cable <edca...@mifos.org> wrote:
> >>
> >>> Hi all,
> >>>
> >>> This meeting is happening now for anybody that wants to join.
> >>>
> >>> Ed
> >>>
> >>> On Sat, Feb 10, 2018 at 6:07 AM, Ed Cable <edca...@mifos.org> wrote:
> >>>
> >>>> Hi all
> >>>>
> >>>> Woule 1530GMT work on Sunday? Nazeer had a conflict on Saturday. I'll
> >>>> update the GoToTraining session.
> >>>>
> >>>> Ed
> >>>>
> >>>> On Thu, Feb 8, 2018 at 9:19 AM, Sendoro Juma <sendoro@singo.africa>
> >>>> wrote:
> >>>>
> >>>>> Hello Ed,
> >>>>>
> >>>>> Just in case, same Saturday(s) but starting 15:30GMT!
> >>>>>
> >>>>> if it is fine with Nazeer, then we will very much appreciate...
> >>>>>
> >>>>> Sorry our request is based on the fact on belief/religious related!
> >>>>>
> >>>>> Cheers
> >>>>> Sendoro
> >>>>>
> >>>>> - Original Message -
> >>>>> From: "Ed Cable" <edca...@mifos.org>
> >>>>> To: "dev" <dev@fineract.apache.org>
> >>>>> Cc: "Nazeer Hussain Shaik" <nazeerhussain.sh...@gmail.com>
> >>>>> Sent: Thursday, February 8, 2018 7:05:55 PM
> >>>>> Subject: Re: Meeting to Discuss Release Management Process
> >>>>>
> >>>>> Hmm... We can reschedule to accommodate everyone. Weekdays might be
> >>>>> difficult for Nazeer with his new schedule.
> >>>>>
> >>>>> Ed
> >>>>>
> >>>>> On Thu, Feb 8, 2018 at 7:42 AM, Sendoro Juma <sendoro@singo.africa>
> >>>>> wrote:
> >>>>>
> >>>>>> Hello Ed,
> >>>>>>
> >>>>>> Hope you will record,
> >>>>>>
> >>>>>> I see two members missing from our side because of that new timing.
> >>>>>>
> >>>>>> Cheers
> >>>>>> Sendoro
> >>>>>>
> >>>>>> - Original Message -
> >>>>>> From: "Ed Cable" <edca...@mifos.org>
> >>>>>> To: "dev" <dev@fineract.apache.org>
> >>>>>> Cc: "Nazeer Hussain Shaik" <nazeerhussain.sh...@gmail.com>
> >>>>>> Sent: Thursday, February 8, 2018 5:05:35 PM
> >>>>>> Subject: Re: Meeting to Discuss Release Management Process
> >>>>>>
> >>>>>> Hi all,
> >>>>>>
> >>>>>> Nazeer is not available till Saturday for this meeting so I am going
> >>>>> to
> >>>>>> adjust the timing to Saturday at 1400GMT and will update the
> >>>>> GoToTraining
> >>>>>> session accordingly.
> >>>>>>
> >>>>>> Ed
> >>>>>>
> >>>>>> On Thu, Feb 8, 2018 at 6:46 AM, Awasum Yannick <
> >>>>>> awasum.yann...@skylabase.com
> >>>>>>> wrote:
> >>>>>>> I already registered for it.
> >>>>>>>
> >>>>>>> I hope it happens.
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>> Awasum
> >>>>>>

Re: Meeting to Discuss Release Management Process

[Sendoro Juma]

Hello Ed,

Just in case, same Saturday(s) but starting 15:30GMT!

if it is fine with Nazeer, then we will very much appreciate... 

Sorry our request is based on the fact on belief/religious related!

Cheers
Sendoro 

- Original Message -
From: "Ed Cable" <edca...@mifos.org>
To: "dev" <dev@fineract.apache.org>
Cc: "Nazeer Hussain Shaik" <nazeerhussain.sh...@gmail.com>
Sent: Thursday, February 8, 2018 7:05:55 PM
Subject: Re: Meeting to Discuss Release Management Process

Hmm... We can reschedule to accommodate everyone. Weekdays might be
difficult for Nazeer with his new schedule.

Ed

On Thu, Feb 8, 2018 at 7:42 AM, Sendoro Juma <sendoro@singo.africa> wrote:

> Hello Ed,
>
> Hope you will record,
>
> I see two members missing from our side because of that new timing.
>
> Cheers
> Sendoro
>
> - Original Message -
> From: "Ed Cable" <edca...@mifos.org>
> To: "dev" <dev@fineract.apache.org>
> Cc: "Nazeer Hussain Shaik" <nazeerhussain.sh...@gmail.com>
> Sent: Thursday, February 8, 2018 5:05:35 PM
> Subject: Re: Meeting to Discuss Release Management Process
>
> Hi all,
>
> Nazeer is not available till Saturday for this meeting so I am going to
> adjust the timing to Saturday at 1400GMT and will update the GoToTraining
> session accordingly.
>
> Ed
>
> On Thu, Feb 8, 2018 at 6:46 AM, Awasum Yannick <
> awasum.yann...@skylabase.com
> > wrote:
>
> > I already registered for it.
> >
> > I hope it happens.
> >
> > Thanks
> > Awasum
> >
> > On Thu, Feb 8, 2018 at 1:23 PM, Nikhil Pawar <nickr...@gmail.com> wrote:
> >
> > > Is this meeting happening?
> > > I’ll be interested to participate.
> > >
> > > Regards,
> > > Nikhil
> > >
> > > On Wed, Feb 7, 2018 at 10:54 AM Ed Cable <edca...@mifos.org> wrote:
> > >
> > > > Nazeer,
> > > >
> > > > Per the other email thread, we'd like to set up a meeting to both
> > discuss
> > > > and improve our release management process and to transfer knowledge
> to
> > > > additional Apache Fineract committers who would like to help with the
> > > > release management process.
> > > >
> > > > Hopefully after this meeting, we'll be able to update our wiki page
> on
> > > > release management -
> > > > https://cwiki.apache.org/confluence/display/FINERACT/
> > Release+Management
> > > > -  with these processes and have an expanded team of release managers
> > to
> > > > help the community release more consistently and more often.
> > > >
> > > > Would this Friday at 1400GMT work? I'll create a GoToTraining session
> > in
> > > > which others can register and join:
> > > > https://attendee.gototraining.com/r/2808817190976822274
> > > >
> > > > Thanks,
> > > >
> > > > Ed
> > > >
> > > >
> > > >
> > > > --
> > > > *Ed Cable*
> > > > President/CEO, Mifos Initiative
> > > > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> > > >
> > > > *Collectively Creating a World of 3 Billion Maries | *
> http://mifos.org
> > > > <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
> > > >
> > >
> >
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>



-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Meeting to Discuss Release Management Process

[Sendoro Juma]

Hello Ed,

Hope you will record, 

I see two members missing from our side because of that new timing.

Cheers
Sendoro

- Original Message -
From: "Ed Cable" 
To: "dev" 
Cc: "Nazeer Hussain Shaik" 
Sent: Thursday, February 8, 2018 5:05:35 PM
Subject: Re: Meeting to Discuss Release Management Process

Hi all,

Nazeer is not available till Saturday for this meeting so I am going to
adjust the timing to Saturday at 1400GMT and will update the GoToTraining
session accordingly.

Ed

On Thu, Feb 8, 2018 at 6:46 AM, Awasum Yannick  wrote:

> I already registered for it.
>
> I hope it happens.
>
> Thanks
> Awasum
>
> On Thu, Feb 8, 2018 at 1:23 PM, Nikhil Pawar  wrote:
>
> > Is this meeting happening?
> > I’ll be interested to participate.
> >
> > Regards,
> > Nikhil
> >
> > On Wed, Feb 7, 2018 at 10:54 AM Ed Cable  wrote:
> >
> > > Nazeer,
> > >
> > > Per the other email thread, we'd like to set up a meeting to both
> discuss
> > > and improve our release management process and to transfer knowledge to
> > > additional Apache Fineract committers who would like to help with the
> > > release management process.
> > >
> > > Hopefully after this meeting, we'll be able to update our wiki page on
> > > release management -
> > > https://cwiki.apache.org/confluence/display/FINERACT/
> Release+Management
> > > -  with these processes and have an expanded team of release managers
> to
> > > help the community release more consistently and more often.
> > >
> > > Would this Friday at 1400GMT work? I'll create a GoToTraining session
> in
> > > which others can register and join:
> > > https://attendee.gototraining.com/r/2808817190976822274
> > >
> > > Thanks,
> > >
> > > Ed
> > >
> > >
> > >
> > > --
> > > *Ed Cable*
> > > President/CEO, Mifos Initiative
> > > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> > >
> > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> > >   
> > >
> >
>



-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

Re: Our January board report received praise

[Sendoro Juma]

Hello Ed, Myrle,

Proud of you!!!


Best Regards
Sendoro

- Original Message -
From: "Myrle Krantz" 
To: "dev" 
Sent: Tuesday, February 6, 2018 11:50:25 AM
Subject: Our January board report received praise

Hey all,

When we do well, I wish to highlight our successes.

Fineract was picked out as one of two projects which gave exemplary
board reports in January.  The board receives reports on roughly a
quarter of its more than 300 projects every month, and this month all
of them were very good.  But ours stood out.

As Phil said "challenges as well as progress are called out and a
complete picture of the state of the project is presented"

I'd especially like to thank Ed Cable for his contributions in this respect.

Best Regards,
Myrle
VP, Apache Fineract

Re: [Mifos-developer] Updates on Release Timing for Apache Fineract 1.1

[Sendoro Juma]

Hello Ed,

+1
Aligned...

Regards
Sendoro

- Original Message -
From: "Ed Cable" 
To: "dev" 
Cc: "mifos-developer" 
Sent: Monday, February 5, 2018 9:44:19 AM
Subject: Re: [Mifos-developer] Updates on Release Timing for Apache Fineract 1.1

+1 from my end on not holding up the release for the Issue 574 (thanks for
that suggestion Vishwas).

However, one show-stopping release is related to the notifications APIs
that have been added to Apache Fineract as a part of this release and the
server-side implementation issues that Dilpretty had noted in this thread:
https://goo.gl/DLua7i

Mexina & Sendoro, we've hit feature freeze for this release so we don't
want to add any new additional PRs that have not gone through the full QA
cycle yet.

We have a number of other new features to ship in a subsequent release
(i.e. all the Swagger work, other recent submissions by partners) so rest
assured that shortly after we issue this release, we'll begin QA and
prepping for the next release so that your fix can be shipped promptly.

Hopefully Avik, Nazeer, Nikhil, or Vishwas will be able to soon review and
merge in your PR.

Ed

On Sun, Feb 4, 2018 at 11:01 PM, Santosh Math <
sant...@confluxtechnologies.com> wrote:

> Hi Vishwas,
>
> It's an existing issue. As it's not blocker, it could be taken in next
> release.
>
> Regards
> Santosh
>
> On 04-Feb-2018 11:52 PM, "vishwas" 
> wrote:
>
> > Thanks for the fix Steve ! The same has been merged.
> >
> > @Santosh / Ed : https://issues.apache.org/jira/browse/FINERACT-574 <
> > https://issues.apache.org/jira/browse/FINERACT-574> is probably an issue
> > which has been existing for a while now ? Given that the large majority
> of
> > fineract users do no use the share management module, I would suggest
> that
> > we proceed with this release without waiting for the same to be fixed.
> >
> > Regards,
> > Vishwas
> >
> >
> >
> > > On Feb 3, 2018, at 4:19 PM, Steve Conrad  wrote:
> > >
> > > I made a fix for FINERACT-590 and submitted a PR this afternoon. Please
> > let
> > > me know if you have any questions.
> > > Thanks,
> > > Steve
> > >
> > > On Fri, Feb 2, 2018 at 2:03 AM Nikhil Pawar 
> wrote:
> > >
> > >> Ed,
> > >>
> > >> Apologies for delay!
> > >> Our new feature is scheduled to go live this weekend, so was busy
> > meeting
> > >> the deadline.
> > >> Will get back to you latest by Sunday evening.
> > >>
> > >> Regards,
> > >> Nikhil
> > >>
> > >> On Thu, Feb 1, 2018 at 8:01 AM, Ed Cable  wrote:
> > >>
> > >>> Nikhil,
> > >>>
> > >>> Any progress on issue 590 that you were looking into? I know you had
> > some
> > >>> outstanding questions.
> > >>>
> > >>> Ed
> > >>>
> > >>> On Tue, Jan 30, 2018 at 2:09 AM, Santosh Math <
> > >>> sant...@confluxtechnologies.com> wrote:
> > >>>
> >  Hi Ed,
> > 
> >  As discussed earlier, the following issues yet to be fixed.
> > 
> >  https://issues.apache.org/jira/browse/FINERACT-590
> > 
> >  https://issues.apache.org/jira/browse/FINERACT-574
> > 
> >  Regards
> >  Santosh
> > 
> >  On Tue, Jan 30, 2018 at 1:45 PM, Ed Cable 
> wrote:
> > 
> > > Santosh, Avik, or Madhukar,
> > >
> > > As you know the entire community has been eagerly awaiting the
> latest
> > > release of Apache Fineract.
> > >
> > > With transition of responsibilities and difficulty in accessing the
> > QA
> > > infrastructure, these delays have slipped further.
> > >
> > > So the community can be fully aware of the progress and delays
> facing
> > > the release, can you please update on this thread, what the
> remaining
> > >> tasks
> > > are to issue this release and what are the blockers so others in
> the
> > > community could assist.
> > >
> > > Thanks,
> > >
> > > Ed
> > >
> > > --
> > > *Ed Cable*
> > > President/CEO, Mifos Initiative
> > > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> > > <(484)%20477-8649>
> > >
> > > *Collectively Creating a World of 3 Billion Maries | *
> > http://mifos.org
> > >   
> > >
> > >
> > > 
> > > --
> > > Check out the vibrant tech community on one of the world's most
> > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > > Mifos-developer mailing list
> > > mifos-develo...@lists.sourceforge.net
> > > Unsubscribe or change settings at:
> > > https://lists.sourceforge.net/lists/listinfo/mifos-developer
> > >
> > 
> > 
> >  
> >  --
> >  Check out the vibrant tech community on one of the 

Re: [Mifos-developer] Updates on Release Timing for Apache Fineract 1.1

[Sendoro Juma]

Hello Vishwas,

While waiting for FINERACT-574

Can you review existing PRs... that haven't been merged? or the close has been 
closed?

As our circle take considerable, why don't we capitalize in accommodating open 
PRs. 

Regards
Sendoro

- Original Message -
From: "vishwas" 
To: "dev" 
Cc: "mifos-developer" 
Sent: Sunday, February 4, 2018 8:22:30 PM
Subject: Re: [Mifos-developer] Updates on Release Timing for Apache Fineract 1.1

Thanks for the fix Steve ! The same has been merged.

@Santosh / Ed : https://issues.apache.org/jira/browse/FINERACT-574 
 is probably an issue which 
has been existing for a while now ? Given that the large majority of fineract 
users do no use the share management module, I would suggest that we proceed 
with this release without waiting for the same to be fixed.

Regards,
Vishwas



> On Feb 3, 2018, at 4:19 PM, Steve Conrad  wrote:
> 
> I made a fix for FINERACT-590 and submitted a PR this afternoon. Please let
> me know if you have any questions.
> Thanks,
> Steve
> 
> On Fri, Feb 2, 2018 at 2:03 AM Nikhil Pawar  wrote:
> 
>> Ed,
>> 
>> Apologies for delay!
>> Our new feature is scheduled to go live this weekend, so was busy meeting
>> the deadline.
>> Will get back to you latest by Sunday evening.
>> 
>> Regards,
>> Nikhil
>> 
>> On Thu, Feb 1, 2018 at 8:01 AM, Ed Cable  wrote:
>> 
>>> Nikhil,
>>> 
>>> Any progress on issue 590 that you were looking into? I know you had some
>>> outstanding questions.
>>> 
>>> Ed
>>> 
>>> On Tue, Jan 30, 2018 at 2:09 AM, Santosh Math <
>>> sant...@confluxtechnologies.com> wrote:
>>> 
 Hi Ed,
 
 As discussed earlier, the following issues yet to be fixed.
 
 https://issues.apache.org/jira/browse/FINERACT-590
 
 https://issues.apache.org/jira/browse/FINERACT-574
 
 Regards
 Santosh
 
 On Tue, Jan 30, 2018 at 1:45 PM, Ed Cable  wrote:
 
> Santosh, Avik, or Madhukar,
> 
> As you know the entire community has been eagerly awaiting the latest
> release of Apache Fineract.
> 
> With transition of responsibilities and difficulty in accessing the QA
> infrastructure, these delays have slipped further.
> 
> So the community can be fully aware of the progress and delays facing
> the release, can you please update on this thread, what the remaining
>> tasks
> are to issue this release and what are the blockers so others in the
> community could assist.
> 
> Thanks,
> 
> Ed
> 
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> <(484)%20477-8649>
> 
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> Mifos-developer mailing list
> mifos-develo...@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
> 
 
 
 
 --
 Check out the vibrant tech community on one of the world's most
 engaging tech sites, Slashdot.org! http://sdm.link/slashdot
 Mifos-developer mailing list
 mifos-develo...@lists.sourceforge.net
 Unsubscribe or change settings at:
 https://lists.sourceforge.net/lists/listinfo/mifos-developer
 
>>> 
>>> 
>>> 
>>> --
>>> *Ed Cable*
>>> President/CEO, Mifos Initiative
>>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>> <(484)%20477-8649>
>>> 
>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>>   
>>> 
>>> 
>>

Re: [VOTE] Accept Android Client 2.0 (Fineract CN Mobile) into Apache Fineract

[Sendoro Juma]

+1

- Original Message -
From: "Ed Cable" 
To: "mifos-developer" , "dev" 

Sent: Saturday, January 6, 2018 12:23:11 AM
Subject: [VOTE] Accept Android Client 2.0 (Fineract CN Mobile) into Apache 
Fineract

Hello all,

Now that the discussion thread on this topic has concluded and Rajan has
answered Myrle's questions regarding licenses, headers, and Rajan's
continued desires to contribute and move existing tickets over to the
Apache Fineract JIRA infrastructure, I'd like to open the vote once again
to accept the codebase at https://github.com/openMF/Fineract-CN-mobile as
Apache Fineract CN mobile.

Read this blog post for an overview of Rajan's contributions on the
project.

https://medium.com/@therajanmaurya/apache-gsoc-2017-blog-post-f2791dc136b5

Here's the original thread:

>

Hello all,

In case you didn't know (which I think is the case for many of you),
longtime Mifos contributor, GSOC student and GCI mentor, Rajan Maurya
completed a GSOC internship this past summer under the mentorship of Markus
Geiss for Apache Fineract with the Apache Software Foundation as the
mentoring organization.

His project centered around building an Android Mobile Field Operations App
for the generation 3 architecture which we were referring to as Fineract
2.0 at the time but will now be Fineract CN.

All of his commits were made in a personal repository (since there was no
Apache Fineract CN repo yet) so they can't simply fall under Apache and
must go through the formal IP clearance process which starts with a vote
from the PMC before they can be part of Apache Fineract.

Rajan has transferred ownership of the repository over to the Mifos
Initiative so we will be providing the software grant agreement to
contribute if and when we get approval from the PMC.

So if you'd like to see the first incarnation of a mobile field operations
app for the new architecture be a part of Apache Fineract, please vote
accordingly.

You can view the repo at https://github.com/openMF/Fineract-CN-mobile and
test out the latest APK from https://github.com/
openMF/Fineract-CN-mobile/wiki

The APK has been updated to point to the baseURL with the most recent demo
credentials provided by Markus:

> Tenant: playground
> Username: apache.demo
> Password ven3t1@n

A list of all the pull requests can be found at
*https://github.com/openMF/Fineract-CN-mobile/pulls?q=is%3Apr+is%3Aclosed
*

and learn more about the project's original goals in his GSOC application
at https://goo.gl/qsUw2C

Cheers,

Ed

-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

Re: [VOTE] Accept Android Client 2.0 (Fineract CN Mobile) into Apache Fineract

[Sendoro Juma]

+1

- Original Message -
From: "Ed Cable" 
To: "dev" , "mifos-developer" 

Sent: Thursday, December 14, 2017 4:31:05 PM
Subject: [VOTE] Accept Android Client 2.0 (Fineract CN Mobile) into Apache 
Fineract

Hello all,

In case you didn't know (which I think is the case for many of you),
longtime Mifos contributor, GSOC student and GCI mentor, Rajan Maurya
completed a GSOC internship this past summer under the mentorship of Markus
Geiss for Apache Fineract with the Apache Software Foundation as the
mentoring organization.

His project centered around building an Android Mobile Field Operations App
for the generation 3 architecture which we were referring to as Fineract
2.0 at the time but will now be Fineract CN.

All of his commits were made in a personal repository (since there was no
Apache Fineract CN repo yet) so they can't simply fall under Apache and
must go through the formal IP clearance process which starts with a vote
from the PMC before they can be part of Apache Fineract.

Rajan has transferred ownership of the repository over to the Mifos
Initiative so we will be providing the software grant agreement to
contribute if and when we get approval from the PMC.

So if you'd like to see the first incarnation of a mobile field operations
app for the new architecture be a part of Apache Fineract, please vote
accordingly.

You can view the repo at https://github.com/openMF/Fineract-CN-mobile and
test out the latest APK from
https://github.com/openMF/Fineract-CN-mobile/wiki

The APK has been updated to point to the baseURL with the most recent demo
credentials provided by Markus:

> Tenant: playground
> Username: apache.demo
> Password ven3t1@n

A list of all the pull requests can be found at
*https://github.com/openMF/Fineract-CN-mobile/pulls?q=is%3Apr+is%3Aclosed
*

and learn more about the project's original goals in his GSOC application
at https://goo.gl/qsUw2C

Cheers,

Ed

Re: [DISCUSS] Fineract CN issue tracking

[Sendoro Juma]

Hello Myrle,

#2 is for me moderate and preferably 

Both #1 and #3 will bring complexity which may end-up bring volume of emails 
for just clarifications purpose only etc. 

Best Regards
Sendoro

- Original Message -
From: "Myrle Krantz" 
To: "dev" 
Sent: Tuesday, December 12, 2017 10:01:44 AM
Subject: [DISCUSS] Fineract CN issue tracking

Hey all, we need to decide how to do issue tracking for Fineract CN.

I see a couple of possibilities:
1.) We do it under Fineract and create new components for the Fineract
CN components.
2.) We request a new Jira project for Fineract CN.
3.) We request a new Jira project for each of our 33 Fineract CN repositories.

I recommend we go with option #2.  Option #1 is likely to cause
confusion.  Option #3 would force us to request a new jira project
each time we add a repo.

What do you all think?

Regards,
Myrle

Re: Fineract in Kibbles (project health and tracking)

[Sendoro Juma]

Hello Devs, 

See attached screenshot! 

Best Regards 
Sendoro 


From: "Ed Cable" <edca...@mifos.org> 
To: "dev" <dev@fineract.apache.org> 
Sent: Tuesday, December 12, 2017 12:22:16 AM 
Subject: Re: Fineract in Kibbles (project health and tracking) 

Sendoro, 
Could you resend the attachment? Only tab I can find a settable filter for is 
engagement and then setting Fineract as the sub-filter. That only then displays 
filtered data for that one tab. 


​ 

I just found the filter for the sections, Mailing Lists, etc. but the filters 
is only visible when I collapse "Emails, topics, authors over time" and even 
when it's visible, I can't actually select a value nor type one in and submit. 

​ 

Many of the other widgets also don't work and simply say: "Widget design not 
found" 


​ 




On Mon, Dec 11, 2017 at 12:55 PM, Myrle Krantz < [ mailto:my...@apache.org | 
my...@apache.org ] > wrote: 


Hi Nikhil, Hi Ed, 

Did the tips Daniel and Sendoro gave you help you to see the data? If 
something still isn't working right, do ask. Not only is the data 
useful for us, this is a beta, and I'm sure the kibbles team would 
appreciate our feedback. 

Greets, 
Myrle 


On Sun, Dec 10, 2017 at 11:41 AM, Sendoro Juma <sendoro@singo.africa> wrote: 
> Hello All, 
> 
> I applied this filters (see attachment) and I could spot Fineract related 
> info. 
> 
> Best Regards 
> Sendoro 
> 
> - Original Message - 
> From: "Daniel Carlson" < [ mailto:dancarl...@gmail.com | dancarl...@gmail.com 
> ] > 
> To: "dev" < [ mailto:dev@fineract.apache.org | dev@fineract.apache.org ] > 
> Sent: Sunday, December 10, 2017 12:26:02 PM 
> Subject: Re: Fineract in Kibbles (project health and tracking) 
> 
> I don't think so because I was able to see the data. Just type fineract in 
> the filter fields and you will see the data for just fineract. 
> 
> Cheers! 
> Daniel Carlson 
> 
> On Fri, Dec 8, 2017 at 11:16 PM, Ed Cable < [ mailto:edca...@mifos.org | 
> edca...@mifos.org ] > wrote: 
> 
>> I had same question too. 
>> 
>> Ed 
>> 
>> On Fri, Dec 8, 2017 at 11:40 AM, Nikhil Pawar < [ mailto:nickr...@gmail.com 
>> | nickr...@gmail.com ] > wrote: 
>> 
>> > Hi Myrle, 
>> > 
>> > Do we need to register to see Fineract data. 
>> > kibble demo login doesn't show our statistics. 
>> > 
>> > Regards, 
>> > Nikhil 
>> > 
>> > On Fri, Dec 8, 2017 at 3:18 AM, Myrle Krantz < [ mailto:my...@apache.org | 
>> > my...@apache.org ] > wrote: 
>> > 
>> > > Hey all, 
>> > > 
>> > > Remember, I requested our participation in the kibbles early demo? 
>> > > Fineract sources have now been added to kibbles. 
>> > > 
>> > > You can check it out in its early-beta state here: 
>> > > [ https://demo.kibble.apache.org/ | https://demo.kibble.apache.org/ ] 
>> > > 
>> > > This means that our github repositories, our dev and user e-mail 
>> > > lists, and our Jira tickets are used as sources to provide insights 
>> > > like: 
>> > > 
>> > > * Who are the top contributors? (Congratulations Nazeer, that's you!) 
>> > > * What percentage of our code by line count is in which programming 
>> > > languages? 
>> > > * Which other Apache projects is our project connected to? 
>> > > * How many companies are contributing to our project? (2) 
>> > > 
>> > > Especially PMC members should take a look. This is cold hard data 
>> > > that is relevant to project governance. 
>> > > 
>> > > Make sure to select fineract sources when surfing the data. Otherwise, 
>> > > you'll see our data mixed with the other projects taking part in the 
>> > > beta. The source selection is generally at the top right of the 
>> > > screen. 
>> > > 
>> > > Regards, 
>> > > Myrle Krantz, V.P. Apache Fineract 
>> > > 
>> > 
>> 
>> 
>> 
>> -- 
>> *Ed Cable* 
>> President/CEO, Mifos Initiative 
>> [ mailto:edca...@mifos.org | edca...@mifos.org ] | Skype: edcable | Mobile: 
>> [ tel:%2B1.484.477.8649 | +1.484.477.8649 ] 
>> 
>> *Collectively Creating a World of 3 Billion Maries | * [ http://mifos.org/ | 
>> http://mifos.org ] 
>> < [ http://facebook.com/mifos | http://facebook.com/mifos ] > < [ 
>> http://www.twitter.com/mifos | http://www.twitter.com/mifos ] > 
>> 






-- 
Ed Cable 
President/CEO, Mifos Initiative 
[ mailto:edca...@mifos.org | edca...@mifos.org ] | Skype: edcable | Mobile: 
+1.484.477.8649 

Collectively Creating a World of 3 Billion Maries | [ http://mifos.org/ | 
http://mifos.org ] [ http://facebook.com/mifos ] [ http://www.twitter.com/mifos 
] 

Re: Fineract in Kibbles (project health and tracking)

[Sendoro Juma]

Hello All,

I applied this filters (see attachment) and I could spot Fineract related info.

Best Regards
Sendoro

- Original Message -
From: "Daniel Carlson" 
To: "dev" 
Sent: Sunday, December 10, 2017 12:26:02 PM
Subject: Re: Fineract in Kibbles (project health and tracking)

I don't think so because I was able to see the data. Just type fineract in
the filter fields and you will see the data for just fineract.

Cheers!
Daniel Carlson

On Fri, Dec 8, 2017 at 11:16 PM, Ed Cable  wrote:

> I had same question too.
>
> Ed
>
> On Fri, Dec 8, 2017 at 11:40 AM, Nikhil Pawar  wrote:
>
> > Hi Myrle,
> >
> > Do we need to register to see Fineract data.
> > kibble demo login doesn't show our statistics.
> >
> > Regards,
> > Nikhil
> >
> > On Fri, Dec 8, 2017 at 3:18 AM, Myrle Krantz  wrote:
> >
> > > Hey all,
> > >
> > > Remember, I requested our participation in the kibbles early demo?
> > > Fineract sources have now been added to kibbles.
> > >
> > > You can check it out in its early-beta state here:
> > > https://demo.kibble.apache.org/
> > >
> > > This means that our github repositories, our dev and user e-mail
> > > lists, and our Jira tickets are used as sources to provide insights
> > > like:
> > >
> > > * Who are the top contributors? (Congratulations Nazeer, that's you!)
> > > * What percentage of our code by line count is in which programming
> > > languages?
> > > * Which other Apache projects is our project connected to?
> > > * How many companies are contributing to our project? (2)
> > >
> > > Especially PMC members should take a look.  This is cold hard data
> > > that is relevant to project governance.
> > >
> > > Make sure to select fineract sources when surfing the data. Otherwise,
> > > you'll see our data mixed with the other projects taking part in the
> > > beta.  The source selection is generally at the top right of the
> > > screen.
> > >
> > > Regards,
> > > Myrle Krantz, V.P. Apache Fineract
> > >
> >
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>

Re: Roles and Permissions - Query

[Sendoro Juma]

Hello Nazeer,

Can you please resend the screenshot, I also didn't manage to see it!!!

- Original Message -
From: "karthik" 
To: "dev" 
Sent: Thursday, November 30, 2017 7:32:35 AM
Subject: Re: Roles and Permissions - Query

Will check for errors. But I am unable to add permissions in staging also. How 
do we add new permissions if we add new Functionality?

 

I could not see the screenshot for some reason.

 

From: Nazeer Shaik 
Reply-To: 
Date: Wednesday, 29 November 2017 at 7:55 PM
To: Dev 
Subject: Re: Roles and Permissions - Query

 

Hi Karthik,

 

Are you getting any error? I don't see this problem even on latest code base 
(Fineract, community-app) which is hosted staging server. Please see the 
screenshot below. 

 

 

Regards,

Nazeer

 

On Wed, Nov 29, 2017 at 6:37 PM, Karthik Ananthakrishnan 
 wrote:

Dear Fineract Champions,



I have a query with regards to adding new permissions.



I am able to add new roles from Mifos UI. But don’t have an option to add new 
permission. Even if I created the new permission through scripts in DB and 
mapped it to Roles, I am not able to see the list of permissions to the users 
in View Role screen. Can someone help me on this.



Regards,

Karthik

Re: [ANNOUNCE] New Apache Fineract Committer Awasum Yannick

[Sendoro Juma]

Hello Awasum,

Indeed you contributions is invaluable. keep going!!!

Regards
Sendoro

- Original Message -
From: "Myrle Krantz" 
To: "dev" 
Sent: Friday, November 17, 2017 11:12:08 AM
Subject: [ANNOUNCE] New Apache Fineract Committer Awasum Yannick

Hey all,

I'm proud to announce that Apache Fineract has a new committer.

Congratulations Awasum Yannick, and thank you for joining us.

Awasum is the CTO of Skylabase, and has been helping out by providing
SMS bridge requirements and answering questions.

Best Regards,
Myrle Krantz
PMC Member, Apache Fineract

P.S.  Awasum, would you mind if I announce your committership on
twitter as well?

Re: Release Plan for Next Major Release of Apache Fineract: [Re: Need for help in reviewing PRs]

[Sendoro Juma]

Dear All,

My wish, is if we can include and merge at least all current pending PRs, in 
Fineract, 

As well as on those in  community app, android clients etc... so that we can 
ship a short time after Fineract. 

Thanks
Sendoro

- Original Message -
From: "Ed Cable" 
To: "dev" 
Cc: "Shaik Nazeer" , "mifos-developer" 
, "Avik Ganguly" 

Sent: Friday, October 20, 2017 12:09:56 PM
Subject: Release Plan for Next Major Release of Apache Fineract: [Re: Need for 
help in reviewing PRs]

Nazeer and others,

While this is a blend of several other threads out there, can we update the
wiki with a page which outlines out all the major features/external
contributions we are planning on including in the next major release so we
can ensure committers can assist in reviewing and Santosh knows what he
needs to focus on in terms of QA.

>From the other thread, on the Apache Fineract side, I know we're aiming to
ship the work related to two-factor authentication, notifications, data
import tool, credit bureau integration, GSIM/GLIM, Changes made by BowPi,
security changes from Thisura, and changes made by Sanyam for Swagger APIs.

I created a page at
https://cwiki.apache.org/confluence/display/FINERACT/1.1.0+-+Apache+Fineract
.

For now I just said it was 1.1 but I believe there's enough going in that
we could call it a more signficant release - but I'll let others on PMC
determine that.

Ed


On Tue, Oct 10, 2017 at 11:33 AM, Avik Ganguly 
wrote:

> Hi Nazeer,
>
> I have done one round of review for the open PRs. Please find my comments
> for the open PRs.
> 
>  Backlog Tracking
> 
> 
>
> Regards,
> Avik.
>
> On Tue, Oct 3, 2017 at 11:00 AM, Shaik Nazeer  confluxtechnologies.com> wrote:
>
>> Hi Avik,
>>
>>
>>
>> Most of them are reviewed and provided with review comments. Please have
>> a look again following the older PR(s) first as sometimes contributors will
>> update same PR without creating the new ones.
>>
>>
>>
>> Regards,
>>
>> Nazeer
>>
>>
>>
>> *From:* Avik Ganguly [mailto:avikganguly...@gmail.com]
>> *Sent:* 02 October 2017 00:05
>> *To:* Dev; Nazeer Shaik
>> *Cc:* Mifos software development; priv...@fineract.apache.org
>> *Subject:* Re: Need for help in reviewing PRs
>>
>>
>>
>> Hi Nazeer,
>>
>>
>>
>> Are there any particular PRs I can help in reviewing or should I do a
>> scan-through / follow up on the older PRs first?
>>
>>
>>
>> Regards,
>>
>> Avik.
>>
>>
>>
>> On Thu, Sep 14, 2017 at 12:00 PM, Ed Cable  wrote:
>>
>> Hi all,
>>
>> Once again not to sound like a broken record but echoing the same
>> sentiments in my previous email about the need for help in GSOC reviews.
>> The need for members of the PMC to review pull requests in general extends
>> beyond just these Google Summer of Code contributions. Nazeer, could use
>> help so there's not a backlog of pull requests to be reviewed.
>>
>> Apart from just needing more hands on deck to assist, it would be ideal
>> that we could have a second set of eyes review pull requests that Nazeer
>> has himself made before they can be merged. Right now with only one
>> maintainer, when Nazeer is writing new features, himself, he has nobody to
>> do an external review.
>>
>> Thanks,
>>
>> Ed
>>
>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>> <(484)%20477-8649>
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>   
>>
>>
>>
>
>


-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

Re: New Committer and Project Management Committee member: Avik Ganguly

[Sendoro Juma]

Hello Avik,

Congrats for the great work and recognition.

BR
Sendoro

- Original Message -
From: "vishwas" 
To: "dev" 
Cc: "user" 
Sent: Saturday, October 14, 2017 4:58:49 PM
Subject: New Committer and Project Management Committee member: Avik Ganguly

Hello Folks,

Please join me in welcoming Avik Ganguly as our newest Committer and member on 
the Project Management Committee.

Avik began his association with the Mifos community as a student participating 
in Google Summer Of Code in 2013, when he developed an excel based data import 
tool for MifosX . This user friendly tool has since been widely used by both 
MifosX specialists and MFI’s, thanks mainly to Avik's continued maintenance and 
support. To date, Avik continues to play an active role in the MifosX and 
Fineract communities and has most recently served as a mentor on "Two factor 
authentication" and "Enhancements to the data import tool” projects during this 
years Google Summer of Code.

In addition to being a highly skilled full stack developer, Avik has amassed a 
keen understanding of the Financial services domain through his work with 
organizations like Conflux Technologies and Novopay.

Avik is a firm believer in our mission of "3 Billion Maries" ( 
http://mifos.org/impact/social-mission-success/) and hopes to further the cause 
in his role as a newly minted committer and member of the PMC

Regards,
Vishwas

Re: [Mifos-developer] Transfer Exception : Repayment date cannot be on a non working day

[Sendoro Juma]

Hello Rajan, All, 

+1 

I think the proposition is correct! 

Generally, if we have to impose check/gate for a particular transaction e.g. 
(transfer money from my mobile wallet to a bank account may of different bank 
etc.) the check if needed will be at back office...e.g. of interbank transfers 
etc... 

However, from user perspective the actions from him/her is complete... 


But, a friendly message may probably needed regardless of the day e.g "Your 
transaction is being processed/Your transaction will be processed"; as not 
all transactions will be effected instantly, e.g. the transaction involving two 
banks... "think allowed for future possibilities". 





Thanks 


Sendoro 



From: "Rajan Maurya"  
To: "dev" , "mifos-developer" 
 
Sent: Wednesday, October 11, 2017 9:27:17 PM 
Subject: [Mifos-developer] Transfer Exception : Repayment date cannot be on a 
non working day 

Hi All, 
As we all know self-service is the end user application and the user can play 
with application any time whenever he wants. Doesn't matter it's Sunday or any 
festival day. 

The user should able to make any type of transaction, withdrawals etc whenever 
he wants. currently, we have validation according to the field officer that's 
why a user can't make any transfer. 

@Nazeer @Ed what you think about it. 

Here is the issue that I have created for more about exception: [ 
https://github.com/openMF/self-service-app/issues/441 | 
https://github.com/openMF/self-service-app/issues/441 ] 

-- 
Thanks 
Namaste 

Rajan Maurya 
Contact Number : +91 9015090523 [ https://mail.amala.co.tz/# ] 
Github: [ https://github.com/therajanmaurya | https://github.com/therajanmaurya 
] 
LinedIn: [ https://www.linkedin.com/in/therajanmaurya/ | 
https://www.linkedin.com/in/therajanmaurya/ ] 



‌ 

-- 
Check out the vibrant tech community on one of the world's most 
engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
Mifos-developer mailing list 
mifos-develo...@lists.sourceforge.net 
Unsubscribe or change settings at: 
https://lists.sourceforge.net/lists/listinfo/mifos-developer 

Re: Interest In Contributing To Mifos Community

[Sendoro Juma]

Hello Isaac,

Warmly welcome!

Regards
Sendoro

- Original Message -
From: "Isaac Kamga" 
To: "dev" , "mifos-developer" 

Sent: Wednesday, October 4, 2017 6:05:32 PM
Subject: Interest In Contributing To Mifos Community

Hello there,

I am Isaac Kamga from Cameroon, Africa

In the past I’ve been a contributor to BRL-CAD and currently lead a community 
of developers ( http://gdgbuea.net/  ) who are interested 
in the Mifos Initiative and it’s open source projects.

Over the past few weeks, I’ve learned about Financial Includion, Mifos 
Initiative and have built the Apache Fineract CN project.

I’m excited to share experiences as well as learn more from everyone in this 
awesome community of people eradicating poverty “one line of code at a time”.

Cheers,
Isaac Kamga

Re: DISCUSS: Personalization of Mobile Banking App by Financial Institution

[Sendoro Juma]

+1  retain mifos logo and allow respectice MFI's logo upload too...by admin.

Regards
Sendoro

- Original Message -
From: "Ed Cable" 
To: "mifos-developer" , "dev" 

Sent: Friday, September 29, 2017 9:29:10 PM
Subject: DISCUSS: Personalization of Mobile Banking App by Financial Institution

As we prepare to launch the Mifos Mobile Banking App powered by Apache
Fineract, one thing I realize we need to make easy for the sys admin of the
app is the ability to change the logo to that of the financial institution
offering the app to their customers.

Most organizations will want to have the app have the look and feel of
their organization (at least their logo)

While some orgs will want to take the codebase and build their own APK and
distribute their own version of the app directly or through the Play store,
I foresee the real-life scenario would be the financial institution would
direct their end users to go to the Google Play store and search for Mifos
Mobile. The user would download that app and then when logging in they
would see the logo of the financial institution that they belong to. This
logo would replace where the Mifos logo is currently (we still would like
to retain some of the Mifos branding in the app though). Ultimately they
might also want to change the mobile app icon too to their org.

Should we just create a section in the Mifos X web app, where they can
upload the logo they want displayed in the mobile banking app?

Perhaps within the Mifos X Web App admin section there will be a control
panel of sorts where the financial institution can manage their
self-service channels (mobile and online banking apps). This is where we
can also put the user creation/management functionality. It could also be
where they could initiate in-app notifications from. As we improve our
customer support mechanisms through the app, incoming requests could come
here.

I created ticket at https://github.com/openMF/self-service-app/issues/431
to track discussion. Will likely need to create the appropriate tickets on
Apache Fineract and Mifos X web app issue trackers to support the same.

Ed

Re: looking for 'loan service solution'

[Sendoro Juma]

Dear Orlando,

As far as I know, it is only support MySQL and strictly the version mentioned 
in the installation manual! Anyone can correct me... 

Should you be able to extend it, community will be more than happy to hear from 
you!

Regards
Sendoro

- Original Message -
From: "Orlando Cabrera" <idevelo...@live.com>
To: "mifos-developer" <mifos-develo...@lists.sourceforge.net>
Cc: "dev" <dev@fineract.apache.org>
Sent: Thursday, September 28, 2017 6:05:36 PM
Subject: Re: looking for 'loan service solution'

Hi Sendoro,


Can this tool support MS SQL database server? A potential fintech company 
already have existing windows platform including ms sql server. I just 
wondering if mifos x can configure to use other rdbms other than MySQL.


thanks,

Orlando


____
From: Sendoro Juma <send...@singoafrica.com>
Sent: September 23, 2017 9:46 AM
To: mifos-developer
Cc: dev
Subject: Re: [Mifos-developer] looking for 'loan service solution'

Hello Orlando,

Great that you have seen the tool as valuable to you.
- Yes you can come up with new requirement and sharing with the rest of 
community members. 
https://cwiki.apache.org/confluence/display/FINERACT/Contributor%27s+Zone
- About the license Apache Fineract licese see  http://www.apache.org/licenses/

Regards
Sendoro




From: "Orlando Cabrera" <idevelo...@live.com>
To: "mifos-developer" <mifos-develo...@lists.sourceforge.net>, 
"mifos-developer" <mifos-develo...@lists.sourceforge.net>
Cc: "dev" <dev@fineract.apache.org>
Sent: Saturday, September 23, 2017 4:23:13 PM
Subject: Re: [Mifos-developer] looking for 'loan service solution'

Thank you for your reply. I think this will solve most of my needs. I am also 
interested to contribute and add some functionality as well if some of my 
requirements  does not exist in this tool yet.
Another questions, what about branding? I will offer this solution to some of 
my fintech client and would like to know any licensing requirements. Please 
advice.

Regards,

Orlando

From: Sendoro Juma <send...@singoafrica.com>
Sent: Friday, September 22, 2017 10:52:41 AM
To: mifos-developer
Cc: dev
Subject: Re: [Mifos-developer] looking for 'loan service solution'

Hello Orlando,


Without knowing the details of your requirements, we still believe the answer 
is "Yes";
http://mifos.org/mifos-x/flexible-product-configuration/

Explore more from.

https://cwiki.apache.org/confluence/display/FINERACT/Contributor%27s+Zone


You can join the community
http://fineract.apache.org/

Of course terms and condition applies.


Regards
Sendoro



From: "Orlando Cabrera" <idevelo...@live.com>
To: "mifos-developer" <mifos-develo...@lists.sourceforge.net>
Sent: Friday, September 22, 2017 5:25:09 PM
Subject: [Mifos-developer] looking for 'loan service solution'


Greetings,


I am application developer/consultant. I have a project to develop a 'loan 
servicing solution'.  Please advise if this tool will give me almost close to 
what I need.


Thank you,

Orlando


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Mifos-developer mailing list
mifos-develo...@lists.sourceforge.net
Unsubscribe or change settings at:
https://lists.sourceforge.net/lists/listinfo/mifos-developer

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Mifos-developer mailing list
mifos-develo...@lists.sourceforge.net
Unsubscribe or change settings at:
https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] looking for 'loan service solution'

[Sendoro Juma]

Hello Orlando, 

Great that you have seen the tool as valuable to you. 
- Yes you can come up with new requirement and sharing with the rest of 
community members. 
https://cwiki.apache.org/confluence/display/FINERACT/Contributor%27s+Zone 
- About the license Apache Fineract licese see http://www.apache.org/licenses/ 

Regards 
Sendoro 




From: "Orlando Cabrera" <idevelo...@live.com> 
To: "mifos-developer" <mifos-develo...@lists.sourceforge.net>, 
"mifos-developer" <mifos-develo...@lists.sourceforge.net> 
Cc: "dev" <dev@fineract.apache.org> 
Sent: Saturday, September 23, 2017 4:23:13 PM 
Subject: Re: [Mifos-developer] looking for 'loan service solution' 

Thank you for your reply. I think this will solve most of my needs. I am also 
interested to contribute and add some functionality as well if some of my 
requirements does not exist in this tool yet. 
Another questions, what about branding? I will offer this solution to some of 
my fintech client and would like to know any licensing requirements. Please 
advice. 

Regards, 

Orlando 

From: Sendoro Juma <send...@singoafrica.com> 
Sent: Friday, September 22, 2017 10:52:41 AM 
To: mifos-developer 
Cc: dev 
Subject: Re: [Mifos-developer] looking for 'loan service solution' 
Hello Orlando, 


Without knowing the details of your requirements, we still believe the answer 
is "Yes"; 
http://mifos.org/mifos-x/flexible-product-configuration/ 

Explore more from. 

https://cwiki.apache.org/confluence/display/FINERACT/Contributor%27s+Zone 


You can join the community 
http://fineract.apache.org/ 

Of course terms and condition applies. 


Regards 
Sendoro 



From: "Orlando Cabrera" <idevelo...@live.com> 
To: "mifos-developer" <mifos-develo...@lists.sourceforge.net> 
Sent: Friday, September 22, 2017 5:25:09 PM 
Subject: [Mifos-developer] looking for 'loan service solution' 





Greetings, 




I am application developer/consultant. I have a project to develop a 'loan 
servicing solution'. Please advise if this tool will give me almost close to 
what I need. 




Thank you, 

Orlando 





-- 
Check out the vibrant tech community on one of the world's most 
engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
Mifos-developer mailing list 
mifos-develo...@lists.sourceforge.net 
Unsubscribe or change settings at: 
https://lists.sourceforge.net/lists/listinfo/mifos-developer 

-- 
Check out the vibrant tech community on one of the world's most 
engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
Mifos-developer mailing list 
mifos-develo...@lists.sourceforge.net 
Unsubscribe or change settings at: 
https://lists.sourceforge.net/lists/listinfo/mifos-developer 

Re: [Mifos-developer] looking for 'loan service solution'

[Sendoro Juma]

Hello Orlando, 


Without knowing the details of your requirements, we still believe the answer 
is "Yes"; 
http://mifos.org/mifos-x/flexible-product-configuration/ 

Explore more from. 

https://cwiki.apache.org/confluence/display/FINERACT/Contributor%27s+Zone 


You can join the community 
http://fineract.apache.org/ 

Of course terms and condition applies. 


Regards 
Sendoro 



From: "Orlando Cabrera"  
To: "mifos-developer"  
Sent: Friday, September 22, 2017 5:25:09 PM 
Subject: [Mifos-developer] looking for 'loan service solution' 





Greetings, 




I am application developer/consultant. I have a project to develop a 'loan 
servicing solution'. Please advise if this tool will give me almost close to 
what I need. 




Thank you, 

Orlando 





-- 
Check out the vibrant tech community on one of the world's most 
engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
Mifos-developer mailing list 
mifos-develo...@lists.sourceforge.net 
Unsubscribe or change settings at: 
https://lists.sourceforge.net/lists/listinfo/mifos-developer 

Re: SPM Survey Storage Blocker

[Sendoro Juma]

Dear Robert,

I concur and subscribe to your comments; 
We would still though suggest Mr. Nazeer to continue support us, while we 
continue building that capability to support him!!!

Regards
Sendoro

- Original Message -
From: "Ippez Robert" 
To: "dev" 
Cc: "mifos-developer" , "Shaik Nazeer" 
, "Raunak Sett" , 
"Adi Raju" , "Ed Cable" 
Sent: Thursday, September 14, 2017 9:20:23 AM
Subject: Re: SPM Survey Storage Blocker

How I wish I was technical enough to handle some of these things. Normally
when PRs are sent they stay long enough and i wish I have all the expertise
to handle this, a sent PR will not take more than one day and will be
merged if approved.



On 14 Sep 2017 09:15, "Santosh Math" 
wrote:

> Hi Ed,
>
> Yes , There was an issue, it's fixed and Nazeer sent PR almost 21 days ago
> here:
>
> https://github.com/apache/fineract/pull/406
>
> He had been expecting some one else should review his PR but no one did it.
>
> Nazeer would merge all the PRs by today evening and update the servers by
> tomorrow evening.
>
> Regards
> Santosh
>
>
> On Thu, Sep 14, 2017 at 11:35 AM, Ed Cable  wrote:
>
> > Nazeer,
> >
> > I'm replying on this thread here so we can give a response to Nathan
> about
> > when PPI will be available.
> >
> > Santosh - had you had a chance to make the issue per Nazeer's email on
> > August 3?
> >
> > Thanks,
> >
> > Ed
> >
> > On Thu, Aug 10, 2017 at 8:59 AM, Ed Cable  wrote:
> >
> >> Nazeer,
> >>
> >> Can you confirm with Raunak that you've resolved his blockers. On our
> >> call this morning, he was still facing some issues but I'm not sure if
> he
> >> had used the latest code with all of the fixes.
> >>
> >> Ed
> >>
> >> On Tue, Aug 8, 2017 at 12:29 PM, Raunak Sett 
> >> wrote:
> >>
> >>> @Nazeer also here is some implementation details documented by Markus
> >>> https://mifosforge.jira.com/wiki/display/MIFOSX/Socia
> >>> l+Performance+Management+Framework
> >>>  Performance+Management+Framework> also
> >>> can we discuss it further, I'm still having some troubles retrieving
> the
> >>> scorecard entries for a client.
> >>>
> >>> On Tue, Aug 8, 2017 at 10:35 PM, Ed Cable  wrote:
> >>>
>  Hi Raunak,
> 
>  Thanks for sending this along again.
> 
>  Nazeer, the results of the survey should be their score which measures
>  if they are above or below the poverty line and their movement out of
>  poverty via an improving score can be tracked over time.
> 
>  Please watch this video to learn more: http://www.progressoutof
>  poverty.org/ppi-overview-video
> 
>  Viewing the old PPI spec might be helpful too.
>  https://mifosforge.jira.com/wiki/display/MIFOS/PPI+Functional+Spec
> 
> 
> 
>  On Tue, Aug 8, 2017 at 9:50 AM, Raunak Sett 
>  wrote:
> 
> > @Nazeer, It was nice talking to you on call. I guess we will be able
> > to do it. I'm pasting a part of the thread with Ed and Nathan for the
> > context of what we need on the SPM framework. Check for [ ] for
> updates on
> > the points.
> >
> > 1) Build out the UI for creating survey from available PPI scorecard
> > [ Needs discussion ]
> >
> > Right now we should simply have to run the PPI-uploader tool on your
> > instance and it will upload the PPIs that have been added as XMLs.
> This
> > should work fine right now (apart from having to make some slight
> > modifications to the PPI-uploader based on the recent changes to
> resources
> > with switch to fineract from mifos x.  [ Resolved Already ]
> > 2) Capture/record surveys from a given entity in the web app
> >
> > This is currently available from the UI (you can test it out at
> > https://demo.openmf.org (mifos/password) by navigating to any
> client,
> > clicking more dropdown and then survey. You can then select the
> survey from
> > the dropdown and enter responses. We do have some work that needs to
> be
> > done to ensure the lookup tables are being linked to the scorecards
> and
> > scores are being properly tabulated. [ Resolved Already]
> >
> > 3) View recorded surveys from the web app
> >
> > This still needs to be built out. @Raunak - is this something you
> > could take up? [ @Ed We can do this now for a particular survey for
> a given
> > client ]
> >
> > 4) Interface to create new surveys from scratch via the UI [ Already
> > Done, Needs testing and modifications ]
> >
> >
> > On Tue, Aug 8, 2017 at 4:16 PM, Shaik Nazeer <
> > nazeer.sh...@confluxtechnologies.com> wrote:
> 

Re: GSOC Wrap-up Blog Post

[Sendoro Juma]

Dear Interns, 

Indeed your contributions is invaluable in our journey to financial inclusions 
initiatives 

Wishing you a continue contributions and thus make Apache Fineract/ Mifos X the 
best digital financial services platform ever! 

Thanks for the CEO/President and entire Staff of Mifos Initiatives for your 
great guidance!!! 

Kudos for the respective mentors. 


Thanks 
Sendoro 


From: "Ed Cable"  
To: "dev" , "mifos-developer" 
, "user" , 
"mifos-users"  
Sent: Wednesday, September 13, 2017 10:27:32 PM 
Subject: GSOC Wrap-up Blog Post 

Hi all, 
Join us in thanking the interns and mentors across the Mifos and Apache 
Fineract communities that made this summer's efforts a great success. 

We have documented their achievements with links to final reports, screencasts 
and screenshots in part 1 of our official GSOC wrap-up at [ 
http://mifos.org/blog/2017-google-summer-of-code-wrap-up/ | 
http://mifos.org/blog/2017-google-summer-of-code-wrap-up/ ] 

Part 2 will soon follow which gives our interns a chance to reflect on their 
journey this past summer. 

Cheers, 

Ed 

Re: [jira] [Created] (FINERACT-524) percentage field display blank message when entered value is text

[Sendoro Juma]

sorry: already read your notes!

- Original Message -
From: "Sendoro Juma" <send...@singoafrica.com>
To: "dev" <dev@fineract.apache.org>
Cc: "dev" <d...@fineract.incubator.apache.org>, "Nenge Masoya" 
<ne...@singoafrica.com>
Sent: Tuesday, September 12, 2017 4:52:45 PM
Subject: Re: [jira] [Created] (FINERACT-524) percentage field display blank 
message when entered value is text

Dear Santosh,

This issue is the same as https://github.com/openMF/community-app/issues/2332

Regards
Sendoro

- Original Message -
From: "Santosh Math (JIRA)" <j...@apache.org>
To: "dev" <d...@fineract.incubator.apache.org>
Sent: Monday, September 11, 2017 7:30:00 AM
Subject: [jira] [Created] (FINERACT-524) percentage field display blank message 
when entered value is text

Santosh Math created FINERACT-524:
-

 Summary: percentage field display blank message when entered value 
is text
 Key: FINERACT-524
 URL: https://issues.apache.org/jira/browse/FINERACT-524
 Project: Apache Fineract
  Issue Type: Bug
Affects Versions: 1.1.0
Reporter: Santosh Math
Assignee: Markus Geiss
 Attachments: 27510880-8c5277cc-5922-11e7-8d12-deff88f0294a.png

navigation: admin->products->manage Tax configurations->Manage tax 
components->create tax component
please see the attached screenshot.

Expected: Proper Error message should be displayed> 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [jira] [Created] (FINERACT-524) percentage field display blank message when entered value is text

[Sendoro Juma]

Dear Santosh,

This issue is the same as https://github.com/openMF/community-app/issues/2332

Regards
Sendoro

- Original Message -
From: "Santosh Math (JIRA)" 
To: "dev" 
Sent: Monday, September 11, 2017 7:30:00 AM
Subject: [jira] [Created] (FINERACT-524) percentage field display blank message 
when entered value is text

Santosh Math created FINERACT-524:
-

 Summary: percentage field display blank message when entered value 
is text
 Key: FINERACT-524
 URL: https://issues.apache.org/jira/browse/FINERACT-524
 Project: Apache Fineract
  Issue Type: Bug
Affects Versions: 1.1.0
Reporter: Santosh Math
Assignee: Markus Geiss
 Attachments: 27510880-8c5277cc-5922-11e7-8d12-deff88f0294a.png

navigation: admin->products->manage Tax configurations->Manage tax 
components->create tax component
please see the attached screenshot.

Expected: Proper Error message should be displayed> 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Request for comment - Two-Factor Authentication

[Sendoro Juma]

Dear Raunak,

Very much appreciated!

Regards
Sendoro 

- Original Message -
From: "Raunak Sett" <sett.rau...@gmail.com>
To: "Ed Cable" <edca...@mifos.org>
Cc: "dev" <dev@fineract.apache.org>, u...@fineract.apache.org, 
"mifos-developer" <mifos-develo...@lists.sourceforge.net>, "Dilpreet Singh" 
<dilpreet2...@gmail.com>
Sent: Thursday, August 10, 2017 11:09:26 AM
Subject: Re: Request for comment - Two-Factor Authentication

Hello Everyone,
The web-self-service app in in the first phase of development during this
Google Summer of Code, after which we can expect the first release. It's
being developed actively over on my fork on the gsoc-17 branch which will
be merged as the first version
https://github.com/botraunak/web-self-service-app/tree/gsoc-17

@Dilpreet is working on the next phase of the android self-service app for
which we already have the first version and he is working on an improved
and better version. You can check out his work on the android self-service
repository under Mifos.

The two factor authentication, for now, is being developed for the
community app for now, but as the self-service user registration and login
uses the same fineract users backend we will be able to have two factor
authentication for the self-service apps as well with little tweaks after
we have a release of the two factor authentication.

On Wed, Aug 9, 2017 at 8:46 PM, Ed Cable <edca...@mifos.org> wrote:

> Raunak and Dilpreet,
>
> Can you please respond on-list regarding the same?
>
> Ed
>
> On Tue, Aug 8, 2017 at 10:10 PM, Avik Ganguly <avikganguly...@gmail.com>
> wrote:
>
>> Hi Sendoro,
>>
>> It was not quite clear initially at what phase of development the
>> self-service web and android apps were.
>>
>> Now that there are demos and screencasts circulating for the two, it looks
>> like an official release is on the way.
>>
>> Under openMF apps, there seems to be a web self service app repository
>> <https://github.com/openMF/web-self-service-app/commits/develop> but the
>> last commit seems to be in mid June. It will be helpful if you can point
>> us
>> to the openMF / Apache repositories where we can find the up to date code
>> for this two apps.
>>
>> Regards,
>> Avik.
>>
>> On Sat, Aug 5, 2017 at 10:52 PM, Sendoro Juma <send...@singoafrica.com>
>> wrote:
>>
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > Hi Alex,
>> > Great job!
>> > Question: I saw you mentioned scope as community app and android client
>> > ... do you mean self-service app is out of scope for now?
>> > Looking forward for this critical feature to the platform!
>> > RegardsSendoro
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Sat, Aug 5, 2017 at 7:15 PM +0300, "Alex Ivanov" <
>> > alexivano...@gmail.com> wrote:
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > *(Bcc Avik)*
>> >
>> > Hello Mifos/Fineract Users and Developers,
>> >
>> > As part of Google Summer of Code I, with the help of my mentor Avik, am
>> > working on adding support for two-factor authentication to Fineract, the
>> > community-app and the Android clients.
>> >
>> > I have published a project spec and I am happy to get your feedback
>> about
>> > the project. The specification can be found here -
>> > https://mifosforge.jira.com/wiki/spaces/projects/pages/
>> > 185277689/GSoC+2017+-+Two-Factor+Authentication
>> >
>> >
>> > Look forward to your comments and feedback.
>> >
>> >
>> > Thanks,
>> > Alex
>> >
>> >
>> >
>> >
>> >
>> >
>>
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> <+1%20484-477-8649>
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>
>


-- 
Raunak Sett

Re: Advice Needed || Apache Fineract

[Sendoro Juma]

Dear Aswin,

Without pre-emptying Myrle's response...

can you check here?

https://cwiki.apache.org/confluence/display/FINERACT/Contributor%27s+Zone

regards
Sendoro

- Original Message -
From: "Aswin kumar" 
To: "dev" 
Sent: Wednesday, August 9, 2017 8:53:19 AM
Subject: Re: Advice Needed || Apache Fineract

Hi Myrle,

Thank you for a very good reply.I am familiar with core java and
collections framework.I also build test frameworks with Junit4 in my
day job.I am learning about REST and The Command Query Responsibility
Segregation pattern.So given my current knowledge, how can I start
contributing to Fineract CN? Can you please guide me regarding the
same?

Regards,
Aswin

On Wed, Aug 2, 2017 at 1:38 AM, Myrle Krantz  wrote:
> Hi Aswin,
>
> First some background:
>
> The current Fineract code base was donated to Apache by the Mifos
> community out of the MifosX code.  It is a traditional monolithic
> backend made up of a REST application fronting an SQL database.  It is
> used as a backend by the Mifos community application which was not
> donated to Apache.
>
> Several community members, including myself, are working on a
> rearchitecting of current generation Fineract core banking concepts
> into a cloud native microservices architecture. We are also working on
> a front-end based on Angular which we intend to contribute to the
> Apache project as well.  I am optimistically calling this set of
> modules Fineract Cloud Native, or Fineract CN for short.
>
> Because of the range of these projects anyone who answers your
> question will have to define the scope of their answer.  I'll answer
> for the backend of Fineract CN.  Hopefully if that is not the answer
> you were looking for, someone else will also speak up about other
> areas of the Fineract project.
>
> We are using the following technologies and concepts on a day-to-day
> basis in the development of the Fineract CN backend:
> *** REST
> *** The Command Query Responsibility Segregation pattern (CQRS -
> there's a good article online by Martin Fowler about this)
> *** Java 8 (lambdas and streams are fun!)
> **  Test-driven development
> **  Junit 4
> **  Mojito
> **  Spring Data JPA
> *   Feign
> *   Cassandra
> *   the java money library
> *   Java web tokens
> *   Eureka
> *   Ribbon
> *   Spring boot
> *   flyway
>
> Just a few things we'd like to add to the mix in the near future:
> *** Backwards compatibility and semantic versioning
> **  Liquibase
> **  Java 9
> *   Reactive programming
> *   Hystrix
> *   Milagro
> *   CouchDB/PouchDB
> *   jpos
>
> That's a long list, and I'm not sure where you are on your learning
> curve, so I've put it in the order of importance as I see it.  Feel
> free to ask more questions.  I'm glad that you're interested in
> Fineract, and I hope we can help you become productive in our
> community.
>
> Regards,
> Myrle
>
>
> On Sun, Jul 30, 2017 at 9:10 PM, Aswin kumar  
> wrote:
>> Hi,
>>
>> I am new to java and I am trying to learn software development by
>> contributing to fineract.I do not have much experience in web
>> development.From the chat conversation in Gitter, I have found that
>> fineract(https://github.com/apache/fineract) is the
>> backend.Community-app (https://github.com/openMF/community-app ) is
>> the front end.I am learning java and also in the process of learning
>> front end
>> technologies like HTML, CSS and javascript.I would like to know, to
>> contribute to backend fineract, what are the web technologies that I
>> should know to start contributing to fineract project.From google
>> search I came to know that I should learn JSP,Servlets  first and then
>> move on to frameworks like Spring.I would like to know your opinion
>> and please advice me regarding the same.Also please suggest if you
>> know of some good resources (books , links on the web) to learn the
>> technologies required to contribute to Fineract.
>>
>> Thanks!
>> Aswin

Re: [jira] [Commented] (FINERACT-508) Client name field character limit

[Sendoro Juma]

Dear Both

I tested too https://demo.openmf.org/#/viewclient/2559

- Original Message -
From: "Santosh Math (JIRA)" 
To: "dev" 
Sent: Tuesday, August 8, 2017 1:11:00 PM
Subject: [jira] [Commented] (FINERACT-508) Client name field character limit

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

Santosh Math commented on FINERACT-508:
---

Hi [~mmyint], There is no restriction on the number of characters for first 
name and last name in client creation. Check this.
https://demo.openmf.org/#/viewclient/2557

> Client name field character limit
> -
>
> Key: FINERACT-508
> URL: https://issues.apache.org/jira/browse/FINERACT-508
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Client
> Environment: Android app
>Reporter: May Myint
>Assignee: Markus Geiss
>  Labels: android, app
>
> The First Name and Last Name fields for client creation require a minimum of 
> 4 characters. This is a problem as clients may have a first or last name that 
> is only 3 characters or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Fineract August Board Report

[Sendoro Juma]

Dear Myrle,

I have forwarded you the email from Shaik regarding 17.07.01.RELEASE ... I'm 
not sure if it sync with below statement in the report.


"- The Mifos Initiative is currently preparing a Mifos release based on the 
current Apache Fineract release."

Regards
Sendoro 

- Original Message -
From: "Myrle Krantz" 
To: "dev" 
Sent: Monday, August 7, 2017 10:59:31 AM
Subject: Fineract August Board Report

Hi y'all,

The Fineract board report is due on Wednesday.  This is your reminder
to add any content to it that you feel the board or the other
Fineracters should know:

https://cwiki.apache.org/confluence/display/FINERACT/2017-08+August+Report

Best Regards,
Myrle Krantz

V.P., Apache Fineract

Re: Request for comment - Two-Factor Authentication

[Sendoro Juma]

Hi Alex,
Great job! 
Question: I saw you mentioned scope as community app and android client ... do 
you mean self-service app is out of scope for now?
Looking forward for this critical feature to the platform! 
RegardsSendoro 









On Sat, Aug 5, 2017 at 7:15 PM +0300, "Alex Ivanov"  
wrote:










*(Bcc Avik)*

Hello Mifos/Fineract Users and Developers,

As part of Google Summer of Code I, with the help of my mentor Avik, am
working on adding support for two-factor authentication to Fineract, the
community-app and the Android clients.

I have published a project spec and I am happy to get your feedback about
the project. The specification can be found here -
https://mifosforge.jira.com/wiki/spaces/projects/pages/185277689/GSoC+2017+-+Two-Factor+Authentication


Look forward to your comments and feedback.


Thanks,
Alex

Re: Next Steps for Bringing Generation 3 Architecture into Apache Fineract

[Sendoro Juma]

Dear Myrle,

It very clear; 

Thanks for taking up your time for this!

Regards
Sendoro

- Original Message -
From: "Myrle Krantz" 
To: "dev" 
Sent: Sunday, July 30, 2017 11:21:31 AM
Subject: Re: Next Steps for Bringing Generation 3 Architecture into Apache 
Fineract

Hello Ed,

It's exciting to see some interest in the work that Markus, Mark, and
I have been doing on Gen 3.  It has always been, and still is the
intention to bring this code into the Apache Fineract community.
However doing so will require considerable effort, especially from me.

Last November I did a presentation on Fineract at ApacheCon in
Seville, Spain [1].  The positive resonance was tremendous.  Several
people asked me in QA and again in the hall afterwards how they
personally could contribute. Unfortunately because I am working on Gen
3, I could not answer that question.  Instead I sent them to the
mailing list, where very sadly not one person found an answer which
enabled them to contribute to Fineract.  I want to be the kind of
person who provides actionable information, and requests, so I made a
decision based on that experience: I will not ask for help on a
project again until I am ready to personally guide a new contributor
through the process of contributing:
* getting the new project building,
* understanding the project structure,
* finding appropriate tickets, and
* getting their pull request merged.

I believe you are asking for this and more Ed.  You probably want:
* changes in features and additional features to support the community,
* help in deploying microservices in a cloud architecture,
* documentation assuring MFIs, and end users about our security
architecture, plus
* assistance in calls with potential customers of Gen 3.

Beyond both of these lists there is still more required to make this
code into part of a successful Apache project:
* addition of RAT to the build process,
* adjustments to the project to remove non-Apache licensed code (potentially),
* communications between Mifos and Apache to donate a tranche of code to a TLP,
* communication with the Apache INFRA team to set up source
repositories, and artifact repositories,
* adjustments to JIRA to make it possible to mark tickets for which
Gen, and which component,
* release management for a new kind of release structure, and
* collective decision-making about the future project direction.

There are probably a few tasks I haven't thought of that will have to
be added to these lists.

Unfortunately at this time, for various reasons, I'm not yet ready to
do any of these three lists.  That is the reason I have not yet
brought Gen 3 to the community.

Currently Kuelap is in startup mode, which I'm sure everyone here
understands is a very intense mode of software development.  At the
same time both of my daughters are at home for summer break, so I am
caring for them during work hours.  Frankly I'm swamped.  I'm hoping
that once I have both kids started into this school year, I'll have
the time to take on responsibilities within the Apache Fineract
community beyond those that I'm already fulfilling, such as those on
some of the lists above. It may, however, be October before the dust
on my end has settled enough to make time for extra responsibilities.

In the mean time however, I can give you the following assurance.
While Mark and I were in Seville in November, I talked to Apache Infra
about hosting multiple repositories for one project.  They are ready,
willing, and waiting for our tickets to create new repositories.  I
met with Roman in California while I was there on vacation August 2016
and again in Seville in November.  Apache projects do occasionally
perform re-architectings and release old and new in parallel for a
while.  There is no technical or organisational Apache-level obstacle
to our plan of releasing Gen 2, and Gen 3 side-by-side for a while. In
fact we have a lot of good will from the ASF.  As you know I've also
created a plan for how to assemble our releases out of multiple
independent repositories and sent it to the Fineract community for
feedback [2].  There is no currently identified obstacle to collecting
our release out of multiple repositories.

Best Regards,
Myrle Krantz

1.) 
https://feathercast.apache.org/2017/01/26/apachecon-seville-2016-introducing-apache-fineract-incubating-myrle-krantz/
2.) 
https://cwiki.apache.org/confluence/display/FINERACT/Composing+a+Release+out+of+Microservices



On Fri, Jul 28, 2017 at 11:10 PM, Ed Cable  wrote:
> Hello Apache Fineract Community,
>
> As communicated throughout numerous webinars and white papers across the
> Mifos and Apache Fineract communities, the future of our technology centers
> around our Generation 3 architecture (Apache Fineract 2.0).
>
> I'm starting this thread to initiate the process of moving this new
> codebase and next major version of Apache Fineract into the community so we
> can at last mobilize the 

Re: [Mifos-developer] Mifos X Latest Release

[Sendoro Juma]

+1 


From: sif...@skyburgsystems.org 
To: "Sampath Kumar G"  
Cc: "Santosh Math" , "Shaik Nazeer" 
, "Ed Cable" , "dev" 
, "dev"  
Sent: Tuesday, July 4, 2017 11:49:44 PM 
Subject: RE: [Mifos-developer] Mifos X Latest Release 



Hi guys, 



I want to contribute these two reports to the community as they may be useful 
in the analysis of data in day to day running for mfis: 

Aging analysis i.e. not aging detail 

Prospective individual payments (future expected client repayments) 



If you find them useful you may add these to the community app. Santosh and 
your team designed these so they meet the required standards. 



Kind regards, 

Sifiso 






From: Sampath Kumar G [mailto:samp...@confluxtechnologies.com] 
Sent: July 03, 2017 12:51 PM 
To: Sifiso Mtetwa 
Cc: Santosh Math; Shaik Nazeer; dev; dev@fineract.apache.org; Ed Cable 
Subject: Re: [Mifos-developer] Mifos X Latest Release 





You're welcome :) 








Regards, 


Sampath 





​ 


[ http://www.confluxtechnologies.com/ | Conflux Technologies Pvt Ltd ] 
#304, 2nd Floor, 7th Main Road 


HRBR Layout 1st Block 

Bengaluru, Karnataka, 560043 INDIA 





Disclaimer: The information contained in this e-mail message and any 
files/attachment transmitted with it is confidential and for the sole use of 
the intended recipient(s) or entity identified. If you are not the intended 
recipient, please email: [ mailto:supp...@confluxtechnologies.com | 
supp...@confluxtechnologies.com ] and destroy/delete all copies and attachment 
thereto along with the original message. Any unauthorised review, use, 
disclosure, dissemination, forwarding, printing or copying of this email or any 
action taken in reliance on this e-mail is strictly prohibited and is unlawful. 
The recipient acknowledges that Conflux Technologies Private Limited or its 
subsidiaries and associated companies are unable to exercise control or ensure 
or guarantee the integrity of/over the contents of the information contained in 
e-mail transmissions. Before opening any attachments, please check. 





On Mon, Jul 3, 2017 at 4:15 PM, < [ mailto:sif...@skyburgsystems.org | 
sif...@skyburgsystems.org ] > wrote: 


Hi Santosh, 



Yes I have had a chance to look at the report and it’s Excellent. Thanks for 
the great job Sampath. Total due in box wont matter when the due amount is so 
clear in the schedule and the transactions. Looks ready to be shipped. 



Thanks and regards, 

Sifiso 






From: Santosh Math [mailto: [ mailto:sant...@confluxtechnologies.com | 
sant...@confluxtechnologies.com ] ] 
Sent: July 03, 2017 11:17 AM 
To: Sifiso Mtetwa 
Cc: Ed Cable; dev ( [ mailto:d...@fineract.incubator.apache.org | 
d...@fineract.incubator.apache.org ] ); [ mailto:dev@fineract.apache.org | 
dev@fineract.apache.org ] ; Shaik Nazeer; Sampath Kumar G 


Subject: Re: [Mifos-developer] Mifos X Latest Release 





Sifiso, 





Did you get the time to look at the report? 





thanks 


Santosh 





On Fri, Jun 30, 2017 at 4:53 PM, Santosh Math < [ 
mailto:sant...@confluxtechnologies.com | sant...@confluxtechnologies.com ] > 
wrote: 


Hi Sifiso, 





Sampath has implemented the report (Export under Transactions tab) as per your 
requirements(except total due in box, it's difficult to fit in that box) and 
that report(Export) is deployed in demo server for your testing purpose. Let me 
have your feedback later. 





Check here: 
[ https://demo.openmf.org/#/viewloanaccount/1191 | 
https://demo.openmf.org/#/viewloanaccount/1191 ] 





Thanks 


Santosh 





On Thu, Jun 29, 2017 at 1:04 PM, < [ mailto:sif...@skyburgsystems.org | 
sif...@skyburgsystems.org ] > wrote: 


Hi Santosh, 



Yes you are right of importance is having the total paid amounts appearing as 
well as transaction type in order to know what these payments are actually for. 
And the total outstanding amount to include principal + interest + fees. The 
box at the top has a disbursed amount, but we need to have the Total due 
somewhere there as well. Since this report is designed for a customer who is 
mainly interested in knowing his balance and the payments he has made. 



The rest are improvements. 



Thanks and regards, 

Sifiso 






From: Santosh Math [mailto: [ mailto:sant...@confluxtechnologies.com | 
sant...@confluxtechnologies.com ] ] 
Sent: June 29, 2017 7:32 AM 
To: ConfluxNazeer Shaik; Sampath Kumar G 
Cc: dev ( [ mailto:d...@fineract.incubator.apache.org | 
d...@fineract.incubator.apache.org ] ); [ mailto:dev@fineract.apache.org | 
dev@fineract.apache.org ] ; Sifiso Mtetwa; Ed Cable 


Subject: Re: [Mifos-developer] Mifos X Latest Release 





Nazeer, 





[ https://issues.apache.org/jira/browse/FINERACT-486 | 
https://issues.apache.org/jira/browse/FINERACT-486 ] 





In above mentioned issue by Sifiso, there is one report 

Re: Requirement to capture Family details of client in Fineract

[Sendoro Juma]

Dear Nikhil,

Physical address: I believe keeping it available as option is better than 
eliminating it all together!!! Not binding... but future looking is always good.

Regards
Sendoro 

- Original Message -
From: "Nikhil Pawar" <nickr...@gmail.com>
To: "Sendoro Juma" <send...@singoafrica.com>, "dev" <dev@fineract.apache.org>
Cc: "Ed Cable" <edca...@mifos.org>, "Nayan Ambali" <nayan.amb...@gmail.com>, 
"Shaik Nazeer" <nazeer.sh...@confluxtechnologies.com>
Sent: Wednesday, June 14, 2017 9:17:42 PM
Subject: Re: Requirement to capture Family details of client in Fineract

Hi Sendoro,
Yes, you are correct regarding identification of family member. It was 
difficult for me to develop functionality which would update/ delete a family 
member record and then I came up with a work around of identifying the record 
by using its  client family member id. I am working on your requirement to add 
identifiers and mobile number. Let me figure out a proper structure and would 
enhance the api.
As of now, I am not storing physical address of client family member, will that 
be problem/inconvenience ?If yes, we can discuss this further.
Regards,Nikhil 

  From: Sendoro Juma <send...@singoafrica.com>
 To: dev@fineract.apache.org; Nikhil Pawar <nickr...@gmail.com> 
Cc: Ed Cable <edca...@mifos.org>; Nayan Ambali <nayan.amb...@gmail.com>; Shaik 
Nazeer <nazeer.sh...@confluxtechnologies.com>; Sendoro Juma 
<send...@singoafrica.com>
 Sent: Wednesday, 14 June 2017 11:09 PM
 Subject: Re: Requirement to capture Family details of client in Fineract
   
Hello Nikhil,

Family member(s) identify proof; I think is important so that the information 
collected can be of verified. 
Info. like ID #, ID Doc Type, Mobile # of the family members... //note Mobile 
#should be in first page because nowadays it might be the easier thing to 
verify.

I didn't see the address tab, I'm assuming that you will capture the physical 
address.

My few cents.


Regards
Sendoro

- Original Message -
From: "Nikhil Pawar" <nickr...@gmail.com>
To: "Sendoro Juma" <send...@singo.co.tz>
Cc: "Ed Cable" <edca...@mifos.org>, "Nayan Ambali" <nayan.amb...@gmail.com>, 
"Shaik Nazeer" <nazeer.sh...@confluxtechnologies.com>, "Nikhil Pawar" 
<nickr...@gmail.com>, "dev" <dev@fineract.apache.org>
Sent: Wednesday, June 14, 2017 8:18:28 PM
Subject: Re: Requirement to capture Family details of client in Fineract

Hello All,

Please find mock up of Family detail screen in the below 
link.https://cwiki.apache.org/confluence/display/FINERACT/Family+Members+details

Kindly let me know if you have any feedback/changes/concerns with respect to 
these screens.
Regards,Nikhil

      From: Nikhil Pawar <nickr...@gmail.com>
 To: Sendoro Juma <send...@singo.co.tz> 
Cc: Ed Cable <edca...@mifos.org>; Nayan Ambali <nayan.amb...@gmail.com>; Shaik 
Nazeer <nazeer.sh...@confluxtechnologies.com>; dev <dev@fineract.apache.org>
 Sent: Monday, 12 June 2017 12:13 PM
 Subject: Re: Requirement to capture Family details of client in Fineract
  
Hello Sendoro,
Thank you for your response. You are correct, we are using this information for 
making inquiry with credit bureau and then reporting the standing of client to 
credit bureau as well.(However, we are not using this information to determine 
the credit score ourselves)As you said, you are storing the identifiers of 
family members in custom fields. I am assuming that you must have created a 
separate  table for family members and in that table you are storing family 
identifiers as well.In order to simplify the design and be consistent with 
client model, we are planning to create a new table for storing family members' 
identifiers(similar to m_client_identifiers).Let us know, your take on this 
approach and would this be beneficial to you.
Regards,Nikhil

      From: Sendoro Juma <send...@singo.co.tz>
 To: dev <dev@fineract.apache.org>; Nikhil Pawar <nickr...@gmail.com> 
Cc: Ed Cable <edca...@mifos.org>; Nayan Ambali <nayan.amb...@gmail.com>; Shaik 
Nazeer <nazeer.sh...@confluxtechnologies.com>
 Sent: Friday, 9 June 2017 9:36 PM
 Subject: Re: Requirement to capture Family details of client in Fineract
  
Hello Nikhil,

Apologies for delay.

As I said earlier if I get you correct!!! This relation and information are 
considered 
1. credit score
2. Away to recover loan...

How we use today
- using custom fields

What info required

Marital status[mandatory] [Options are: Single, Married, Divorced, Widowed]
Nationa Identity #      [Mandatory]

Identity Document Type:  {Options Passport, National ID, Driving License, 
Election ID}
Mobile number# 
Physical Address 
  - Home Address
  - Work Address 

Future Lookin