RE: Editing on Fineract wiki

[Markus Geiß]

Hey Mexina,

we've provided you karma for the Apache Fineract Confluence page.

Cheers

Markus

-Original Message-
From: Mexina Daniel [mailto:mex...@singo.co.tz] 
Sent: Monday, April 3, 2017 11:43 AM
To: dev (dev@fineract.incubator.apache.org) 
Subject: Editing on Fineract wiki

Hi Dev!

I don't know if am right asking this here.

Can someone assist me, i want to share user requirements of one of the 
Outstanding features that our team has been working on the page in Fineract 
wiki , i have signed up  but i don't have a privilege to edit the page.

Thanks in advance.

--
Mexina M Daniel
Lead Software Developer
Research & Development

Tel:+255 222 618 511 | Mob: +255 712 110 791

Singo Africa Limited
Block G,Mbezi Beach B| 7 Nakawale Road| P.O.Box 78908| 14121 Dar es Salaam

singo.co.tz

Lets grow together

RE: [DISCUSS] Graduation

[Markus Geiß]

+1 on Graduation

I think the community has done a great job, and I'm happy that we were able to 
attract one new PMC member and two new committers in the last few month.

All looks good to me, and I look forward taking Apache Fineract to the next 
level with all of you.

Cheers

Markus

-Original Message-
From: Myrle Krantz [mailto:my...@apache.org] 
Sent: Friday, February 24, 2017 11:24 AM
To: dev@fineract.incubator.apache.org
Subject: [DISCUSS] Graduation

Hi everyone,

Apache Fineract is just about ready for graduation to a top-level project.

Please take one more look at our graduation resolution, before we send it to 
the incubator 
https://cwiki.apache.org/confluence/display/FINERACT/Graduation+Resolution

Is there anything that needs to be adjusted? Are there any objections to 
graduation?

Please make your comments or objections by Friday the 3rd of March.

Greets,
Myrle

RE: Please help evaluate Fineract's readiness for graduation

[Markus Geiß]

ed related to security and
> backwards
> > > > compatibility.
> > > >
> > > > We are also evaluating a couple additional committers and will 
> > > > soon
> be
> > > > ready to call for graduation if our mentors too fee we are ready.
> > > >
> > > > Ed
> > > >
> > > >
> > > >
> > > > On Fri, Jan 27, 2017 at 10:14 AM, Jim Jagielski 
> > > > <j...@jagunet.com>
> > wrote:
> > > >
> > > > > Makes sense.
> > > > > > On Jan 25, 2017, at 10:52 PM, Shaik Nazeer <nazeer.shaik@
> > > > > confluxtechnologies.com> wrote:
> > > > > >
> > > > > > Instead of modifying Fineract website on every Fineract 
> > > > > > releases,
> > can
> > > > we
> > > > > link required details to Fineract wiki pages?
> > > > > > For example latest release details can be found at
> > > > > https://cwiki.apache.org/confluence/display/FINERACT/
> Release+Folders
> > > > > >
> > > > > > Thanks,
> > > > > > Nazeer
> > > > > > -Original Message-
> > > > > > From: Markus Geiß [mailto:mge...@mifos.org]
> > > > > > Sent: 26 January 2017 01:55
> > > > > > To: Ed Cable
> > > > > > Cc: dev (dev@fineract.incubator.apache.org)
> > > > > > Subject: Re: Please help evaluation Fineract's readiness for
> > > graduation
> > > > > >
> > > > > > Hey Ed,
> > > > > >
> > > > > > the Apache Fineract website is a github repo you'll find at
> > Apache's
> > > > > github mirror.
> > > > > >
> > > > > > Simply fork it, create a new branch, do the needed changes 
> > > > > > and
> > send a
> > > > PR.
> > > > > >
> > > > > > Best wishes,
> > > > > >
> > > > > > Markus Geiss
> > > > > > Chief Architect
> > > > > > RɅĐɅЯ, The Mifos Initiative
> > > > > >
> > > > > > On Jan 24, 2017 15:58, "Ed Cable" <edca...@mifos.org> wrote:
> > > > > >
> > > > > >> Markus,
> > > > > >>
> > > > > >> Nazeer is continuing to work on addressing the areas of 
> > > > > >> concern related to QU10, QU40, and RE50.
> > > > > >>
> > > > > >> Could you provide me access to the Apache Fineract website 
> > > > > >> to
> > > address
> > > > > >> CO10 and then for CS10 do we want that on the Apache 
> > > > > >> Fineract
> > > website
> > > > > >> or the wiki?
> > > > > >>
> > > > > >> Thanks,
> > > > > >>
> > > > > >> Ed
> > > > > >>
> > > > > >> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski 
> > > > > >> <j...@jagunet.com
> >
> > > > wrote:
> > > > > >>
> > > > > >>> Agreed.
> > > > > >>>
> > > > > >>>> On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik <
> > > ro...@shaposhnik.org>
> > > > > >>> wrote:
> > > > > >>>>
> > > > > >>>> On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable 
> > > > > >>>> <edca...@mifos.org>
> > > wrote:
> > > > > >>>>> Could our Apache Fineract mentors please provide some
> guidance
> > on
> > > > > >>>>> a
> > > > > >>> couple
> > > > > >>>>> of the areas we need to improve upon:
> > > > > >>>>>
> > > > > >>>>> QU10 "*The project is open and honest about the quality 
> > > > > >>>>> of
> its
> > > > code.
> > > > > >>>>> Various levels of quality and maturity for various 
> > > > > >>>>> modules
> are
> > > > > >>>>> natural
> > > > > >>> and
> > > > > >>>>> acceptable as long as they are clearly communicated." -*
> > > > &

RE: Please help evaluate Fineract's readiness for graduation

[Markus Geiß]

Done

Cheers

Markus

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

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

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

RE: Please help evaluation Fineract's readiness for graduation

[Markus Geiß]

Hey Sendoro,

good question. ; o)

We are following the Semantic Version paradigm (http://semver.org/). Given we 
are usually also release new features and not only bugfixes within a release, 
we increase Y in favor of Z. If we'd create a bug fix only release with no 
changes to the API we'd increase Z.

With graduation we will set X to 1, this would also indicate that following 
1.y.z releases won't break because of incompatible API changes.

We were in need to change a lot internally to meet all policies and regulations 
at ASF, so we decided to run 0.y.z during incubation.

Hope this helps. ; o)

Cheers

Markus

-Original Message-
From: send...@singo.co.tz [mailto:send...@singo.co.tz] 
Sent: Wednesday, February 15, 2017 08:56 AM
To: dev@fineract.incubator.apache.org
Cc: Ed Cable <edca...@mifos.org>
Subject: Re: Please help evaluation Fineract's readiness for graduation

Dears,

I'm not sure if this is the right thread to ask this question.

So far till today we had been working with Fineract version  x.y.z; whereby, we 
have only touched  x,y i.e. 0.1.0, 0.2.0... and now 0.7.0

While I understand why we haven't touched x, I don't know when we shall touch 
z.  Or rather what is the criteria to touch version .z above?

Though, I thought that  our Fineract application would touch more of "z". Due 
to the level of development it is in.

For example...
- I thought critical bugs which affects core banking functionalities should be 
resolved with emergency priority through patching; and as for versioning, we 
should use the "z" above... and that only new functionalities should touch the 
"y" and "x".

- Also, how many votes are required to push emergence fixes. as for ITIL this 
usually they don't need fully CAB approval. O rather do we have operational 
change approval board... that will approve when what is needed is only "z"?

My apologies if my post is taking you back


Regards
Sendoro







On 2017-02-15 00:32, Ed Cable wrote:
> Just doing a check-in as to where we stand.
> 
> Nazeer has been addressing some of the outstanding points and has 
> recently posted some additional release management documentation which 
> can be viewed at
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640
> 333
> 
> I have pushed the changes to the Apache Fineract website github repo 
> and these have been merged the but the website is not reflecting the 
> edits I made.
> 
> Nazeer has requested feedback on the Findbugs Implementation he has 
> ready go go.
> 
> 2 active threads are being discussed related to security and backwards 
> compatibility.
> 
> We are also evaluating a couple additional committers and will soon be 
> ready to call for graduation if our mentors too fee we are ready.
> 
> Ed
> 
> 
> 
> On Fri, Jan 27, 2017 at 10:14 AM, Jim Jagielski <j...@jagunet.com>
> wrote:
> 
>> Makes sense.
>> > On Jan 25, 2017, at 10:52 PM, Shaik Nazeer <nazeer.shaik@
>> confluxtechnologies.com> wrote:
>> >
>> > Instead of modifying Fineract website on every Fineract releases, 
>> > can we
>> link required details to Fineract wiki pages?
>> > For example latest release details can be found at
>> https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders
>> >
>> > Thanks,
>> > Nazeer
>> > -Original Message-
>> > From: Markus Geiß [mailto:mge...@mifos.org]
>> > Sent: 26 January 2017 01:55
>> > To: Ed Cable
>> > Cc: dev (dev@fineract.incubator.apache.org)
>> > Subject: Re: Please help evaluation Fineract's readiness for 
>> > graduation
>> >
>> > Hey Ed,
>> >
>> > the Apache Fineract website is a github repo you'll find at 
>> > Apache's
>> github mirror.
>> >
>> > Simply fork it, create a new branch, do the needed changes and send a PR.
>> >
>> > Best wishes,
>> >
>> > Markus Geiss
>> > Chief Architect
>> > RɅĐɅЯ, The Mifos Initiative
>> >
>> > On Jan 24, 2017 15:58, "Ed Cable" <edca...@mifos.org> wrote:
>> >
>> >> Markus,
>> >>
>> >> Nazeer is continuing to work on addressing the areas of concern 
>> >> related to QU10, QU40, and RE50.
>> >>
>> >> Could you provide me access to the Apache Fineract website to 
>> >> address
>> >> CO10 and then for CS10 do we want that on the Apache Fineract 
>> >> website or the wiki?
>> >>
>> >> Thanks,
>> >>
>> >> Ed
>> >>
>> >> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski <j...@jagunet.com&

Re: Please help evaluation Fineract's readiness for graduation

[Markus Geiß]

Hey Ed,

the Apache Fineract website is a github repo you'll find at Apache's github
mirror.

Simply fork it, create a new branch, do the needed changes and send a PR.

Best wishes,

Markus Geiss
Chief Architect
RɅĐɅЯ, The Mifos Initiative

On Jan 24, 2017 15:58, "Ed Cable"  wrote:

> Markus,
>
> Nazeer is continuing to work on addressing the areas of concern related to
> QU10, QU40, and RE50.
>
> Could you provide me access to the Apache Fineract website to address CO10
> and then for CS10 do we want that on the Apache Fineract website or the
> wiki?
>
> Thanks,
>
> Ed
>
> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski  wrote:
>
>> Agreed.
>>
>> > On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik 
>> wrote:
>> >
>> > On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable  wrote:
>> >> Could our Apache Fineract mentors please provide some guidance on a
>> couple
>> >> of the areas we need to improve upon:
>> >>
>> >> QU10 "*The project is open and honest about the quality of its code.
>> >> Various levels of quality and maturity for various modules are natural
>> and
>> >> acceptable as long as they are clearly communicated." -*
>> >>
>> >> Do you have any other projects you could point to that have strong
>> >> transparent measures of quality and maturity clearly available We want
>> to
>> >> follow best practices and adopt similar to display at
>> >> http://fineract.incubator.apache.org
>> >
>> > Regular deployment of tools like Findbugs is a good indication that you
>> take
>> > this requirement seriously.
>> >
>> >> *QU30: The project provides a well-documented channel to report
>> security
>> >> issues, along with a documented way of responding to them.*
>> >>
>> >> Currently we just link to: http://www.apache.org/security/ Are we
>> able to
>> >> do as other projects at http://www.apache.org/security/projects.html
>> or is
>> >> a private channel not something we can set up till we're out of
>> >> incubation.  If we can move forwarde, I'd suggest we have a security
>> page
>> >> on our site, document and fix known vulnerabilities and then provide
>> clear
>> >> instruction on reporting vulnerabilities to a private channel like
>> >> secur...@fineract.incubator..apache.org
>> >
>> > This is less about security@fineract vs.
>> http://www.apache.org/security/
>> > and more about the community being ready for when the first 0 day
>> > hits either of those. Being ready is a combination of tribal knowledge,
>> > wiki recommendations and a release policy that would allow you to patch
>> > at a drop of a hat.
>> >
>> > Thanks,
>> > Roman.
>>
>>
>
>
> --
> *Ed Cable*
> Director of Community Programs, 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] [APACHE FINERACT] 0.6.0-incubating for release

[Markus Geiß]

+1 

Note: We may should clarify that Apache Fineract is currently only supporting 
MySQL 5.6.

-Original Message-
From: Jim Jagielski [mailto:j...@jagunet.com] 
Sent: Tuesday, January 10, 2017 02:46 PM
To: dev@fineract.incubator.apache.org
Subject: Re: [VOTE] [APACHE FINERACT] 0.6.0-incubating for release

+1 to all.

> On Jan 10, 2017, at 7:39 AM, Myrle Krantz  wrote:
> 
> Hi all,
> 
> +1
> 
> The build is working
> Signatures are good
> 
> Things we should improve by the next release:
> * Create a branch in git and tag the release changeset before the call 
> to vote is sent out.  In the future I will vote against a release if 
> the changeset it is drawn from is not tagged.
> * Instead of exempting files like uglify.js in the rat configuration, 
> we should add the allowed license text for those licenses. Here's how 
> http://creadur.apache.org/rat/apache-rat-plugin/examples/custom-licens
> e.html
> 
> Greets from the Voreifel, Germany,
> Myrle
> 
> 
> 
> *Myrle Krantz*
> Solutions Architect
> RɅĐɅЯ, The Mifos Initiative
> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org 
>   
> 
> 
> On Mon, Jan 9, 2017 at 11:06 AM, Adi Raju 
> 
> wrote:
> 
>> +1
>> 
>> Build working
>> Signatures are good
>> Checksums are good
>> Integration tests passing
>> 
>> Regards,
>> Adi Raju
>> 
>> Principal Architect, Conflux Technologies Pvt Ltd
>> Address: #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: 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.
>> 
>> 
>> 
>> -Original Message-
>> From: Nazeer Shaik [mailto:nazeer1100...@apache.org]
>> Sent: Saturday, January 7, 2017 4:05 PM
>> To: dev@fineract.incubator.apache.org
>> Subject: [VOTE] [APACHE FINERACT] 0.6.0-incubating for release
>> 
>> Hello Fineract community,
>> 
>> We have created Apache Fineract 0.6.0-incubating release, with the 
>> artifacts below up for a vote.
>> 
>> 
>> *These are the goals of this release:*
>> 
>>   - Address some of the review comments of Apache Fineract
>>   0.5.0-incubating release
>>   - Share the new features & bugs fixes that have been developed so far,
>>   to give the community a good sense of the upcoming 0.6.0 release
>> 
>> *For more information including release notes, please see:*
>> 
>> https://cwiki.apache.org/confluence/display/FINERACT/0.
>> 6.0-incubating+Release-+Apache+Fineract
>> 
>> 
>> 
>> *** Please download, review and vote by Mon Jan  09, 2017 @ 6pm PST 
>> ***
>> 
>> 
>> 
>> *Source & Binary files:*
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 6.0-incubating/
>> 
>> · Source:
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 6.0-incubating/apache-fineract-0.6.0-incubating-src.tar.gz
>> 
>> · Binary/War :
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 6.0-incubating/apache-fineract-0.6.0-incubating-binary.tar.gz
>> 
>> 
>> 
>> *Commit to be voted on:*
>> 
>> *https://git-wip-us.apache.org/repos/asf?p=incubator-
>> fineract.git;a=commit;h=refs/heads/0.6.0-incubating
>> > fineract.git;a=commit;h=refs/heads/0.6.0-incubating>*
>> 
>> 
>> 
>> *Source build verification steps can be found at:*
>> 
>> Refer 'README.md' in apache-fineract-0.6.0-incubating-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/incubator/fineract/KEYS
>> 
>> 
>> 
>> Note:
>> 
>>   - *Maven repo is not included in place of binary. This will be addressed
>>   in future releases*
>>   - *RAT (Release Audit Tool) is integrated in sub-directory. But it will
>>   check all directories and files  from top level directory. This 
>> will also
>>   be addressed in future releases. We have added steps how to run RAT in
>>   readme.md 

RE: [VOTE] [APACHE FINERACT] 0.5.0-incubating for release

[Markus Geiß]

+1
Verified build
Checked notice/license (waiting on OK by mentors for multi usage of files)

-Original Message-
From: Adi Raju [mailto:adi.r...@confluxtechnologies.com] 
Sent: Thursday, December 8, 2016 09:04 AM
To: dev@fineract.incubator.apache.org
Subject: RE: [VOTE] [APACHE FINERACT] 0.5.0-incubating for release

+1

Verified signatures and checksum
Build is fine
Integration tests are passing

Regards,
Adi Raju

Principal Architect, Conflux Technologies Pvt Ltd
Address: #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: 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.




-Original Message-
From: Nazeer Shaik [mailto:nazeer1100...@apache.org] 
Sent: 07 December 2016 18:31
To: dev@fineract.incubator.apache.org
Subject: [VOTE] [APACHE FINERACT] 0.5.0-incubating for release

Hello Fineract community,

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

*These are the goals of this release:*

   - Share deployable binary file with community, so that they no need to
   put effort to build the same
   - Share the new features that have been developed so far, to give the
   community a good sense of the upcoming 0.5.0 release

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

 *** Please download, review and vote by Thu Dec 09, 2016 @ 6pm PST ***

*Source & Binary files:*
https://dist.apache.org/repos/dist/dev/incubator/fineract/0.5.0-incubating/

· Source:
https://dist.apache.org/repos/dist/dev/incubator/fineract/0.5.0-incubating/apache-fineract-0.5.0-incubating-src.tar.gz

· Binary/War :
https://dist.apache.org/repos/dist/dev/incubator/fineract/0.5.0-incubating/apache-fineract-0.5.0-incubating.tar.gz

*Commit to be voted on:*

https://git-wip-us.apache.org/repos/asf?p=incubator-fineract.git;a=commit;h=refs/heads/0.5.0-incubating

*Source build verification steps can be found at: * Refer 'README.md' in 
apache-fineract-0.5.0-incubating-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/incubator/fineract/KEYS
Note: *We have included two license sections for bundled items of source and 
binary artifacts in same License and Notice file(s)*.

To help in tallying the vote, members please be sure to indicate "(binding)" 
with your vote.

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

Thank,
Nazeer

RE: Business Event Processor

[Markus Geiß]

Hey Adi,

thanks for the reply. ; o)

Triggering SMS or sending notifications are features that should happen 
asynchronous, because they are executed after a business logic was successfully 
executed. For validation we may should think about utilizing what the Spring 
framework has to offer instead of implementing it ourselves.

We may should try to find consensus on Data Driven Authorization within the 
community, given the configuration is usually very complex and the real benefit 
is questionable.

Cheers

Markus

-Original Message-
From: Adi Raju [mailto:adi.r...@confluxtechnologies.com] 
Sent: Wednesday, December 7, 2016 05:59 AM
To: dev@fineract.incubator.apache.org
Subject: RE: Business Event Processor

Hi Markus,

This proposal is mainly intended to help any synchronous processing 
requirements.
For eg, In case of validation failure the API(command) should fail. 
I do not see ActiveMQ of help here.

Data Driven Authorisation as such is bigger feature umbrella, in that we want 
to control data visibility even in the read APIs based on different business 
rules.
In the example provided, "Data Driven Authorisation" was a simple validation 
feature request, which requires allowing an API based on role and not just 
permission assigned to the App User.

Regards,
Adi Raju

Principal Architect, Conflux Technologies Pvt Ltd
Address: #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: 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.



-Original Message-
From: Markus Gei? [mailto:markus.ge...@live.de]
Sent: 05 December 2016 20:51
To: dev@fineract.incubator.apache.org
Subject: RE: Business Event Processor

Hey,

why not utilizing an existing event queue, e.g. ActiveMQ, to get this feature 
in. I don't see any real benefit of creating our own mechanism for this.

And I believe we are mixing requirements/features here, e.g. data driven auth 
is not an event feature ... so it should not be modeled to become one.

Cheers

Markus

From: Adi Raju [mailto:adi.r...@confluxtechnologies.com]
Sent: Monday, December 5, 2016 10:14 AM
To: dev@fineract.incubator.apache.org
Subject: Business Event Processor

Hi All,

Of late, community has been building features like 'Workflow using datatables', 
'Triggered SMS', 'Notifications' etc, also we have many more features in 
roadmap like 'Flagging of Accounts', 'Data Driven Authorisation', 'Tasks 
Framework' etc. In all of these features, there is one commonality, which is to 
listen on a business event on an entity and perform either additional 
validation or processing. Drawback being that on each such business event each 
of these additional processing/validation results in a Database query to check 
if any additional processing or validation is required. The more such features 
we continue to add, the more we are slowing down the system by way of adding 
more and more DB calls whether required or not. Also we are adding more and 
more new APIs and related processing code which in my view is mundane as well 
as time consuming. This design proposes to generalize all such features under 
one single framework and API modelling, thus reducing the calls to DB and also 
improving the turn-around time for feature addition.

https://cwiki.apache.org/confluence/display/FINERACT/Business+Event+Processo
r

Please review and provide your comments.

Regards,
Adi Raju

Principal Architect, Conflux Technologies Pvt 
Ltd
Address: #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:
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 

Re: [Mifos-developer] [Need help] Refernce UI and FS document for survey framework APIs

[Markus Geiß]

Hey Nayan,

sorry ... somehow your mail slipped through.

I'll take care about needed changes. and will provide a fix until early
next week.

Best wishes,

Markus Geiss
Chief Architect
RɅĐɅЯ, The Mifos Initiative

On Nov 17, 2016 19:29, "Ed Cable" <edca...@mifos.org> wrote:

> Markus,
>
> Are you able to respond to Nayan's comments?
>
> Santosh, let's please add this to the queue of code that needs to be
> tested.
>
> Nayan - how is your work on the surveys UI coming along? I plan on having
> one of our product management volunteers work with Mentors International to
> scope out the UI they'd like to see for the surveys.
>
> Ed
>
> On Wed, Oct 5, 2016 at 8:36 AM, Nayan Ambali <nayan.amb...@gmail.com>
> wrote:
>
>> Markus,
>>
>> I have few doubts w.r.t. SPM APIs,
>>
>> 1. Score card list always sends empty result (GET:
>> /surveys/{surveyId}/scorecards)
>>
>> Looking at code (Github link, dev branch
>> <https://github.com/apache/incubator-fineract/blob/develop/
>> fineract-provider/src/main/java/org/apache/fineract/spm/
>> api/ScorecardApiResource.java>
>> )
>> if (scorecards == null) {
>> return ScorecardMapper.map(scorecards);
>> }
>>
>> return Collections.EMPTY_LIST;
>>
>> it always return empty collections.
>>
>> If you confirm, I will fix and send the code back to community
>>
>> 2. Score card for client is also always sends empty result  [ *GET*:
>> /surveys/{surveyId}/scorecards/clients/{clientId}") ]
>> Looking at code (Github link, dev branch
>> <https://github.com/apache/incubator-fineract/blob/develop/
>> fineract-provider/src/main/java/org/apache/fineract/spm/
>> api/ScorecardApiResource.java>
>> )
>> if (scorecards == null) {
>> return ScorecardMapper.map(scorecards);
>> }
>> return Collections.EMPTY_LIST;
>>
>> If you confirm the issue is because of above code, I will fix it and send
>> the code back to community
>>
>> 3. Submitting survey also does not work
>> It gives database contraint voilation, after looking into deep,
>> *m_survey_scorecards* table has foreign key relation with not existing
>> table.
>>
>> If you confirm the issue is because of wrong db constraint, I will fix it
>> and send the code back to community
>>
>>
>> 4. After fixing the 3 point, a survey can be submitted many time and not
>> able to track which is the latest version from scorecard data.
>> How do I get the latest version of response?
>>
>> I am not regular developer, please correct me if am wrong in any of the
>> above analysis.
>>
>> @Ed,
>> Does any institute using SPM module? I want to understand how it is used
>> by
>> the end user. any pointers towards will help a lot.
>>
>>
>> -
>> Nayan Ambali
>>
>>
>>
>>
>>
>>
>>
>> On Wed, 5 Oct 2016 at 11:26 Gaurav Saini <gauravsain...@gmail.com> wrote:
>>
>> > Hello Nayan,
>> >
>> > All the code related to survey is in develop branch. Below are the path
>> of
>> > the files:
>> >
>> > app/scripts/controllers/client/SurveyController.js
>> > app/views/clients/survey.html
>> >
>> > Thanks
>> > Gaurav
>> >
>> >  Sent with Mailtrack
>> > <
>> > https://mailtrack.io/install?source=signature=en
>> al=gauravsain...@gmail.com=22
>> > >
>> >
>> > On Wed, Oct 5, 2016 at 11:19 AM, Nayan Ambali <nayan.amb...@gmail.com>
>> > wrote:
>> >
>> > > Thanks Markus link is useful to me.
>> > >
>> > > @Gaurav, can I get that UI code?
>> > >
>> > > -
>> > > Nayan Ambali
>> > >
>> > >
>> > > On Tue, 4 Oct 2016 at 17:17 Markus Geiß <mge...@mifos.org> wrote:
>> > >
>> > > > Hey Nayan,
>> > > >
>> > > > here you can find the concept docu:
>> > > >
>> > > >
>> > > > https://mifosforge.jira.com/wiki/display/MIFOSX/Social+
>> > > Performance+Management+Framework
>> > > >
>> > > > Best wishes,
>> > > >
>> > > > Markus Geiss
>> > > > Chief Architect
>> > > > RɅĐɅЯ, The Mifos Initiative
>> > > >
>> > > > On Oct 4, 2016 10:09, "Gaurav Saini" <gauravsain...@gmail.com>
>> wrote:
>> > > >
>>

RE: Fineract Board Report for November

[Markus Geiß]

+1

-Original Message-
From: Adi Raju [mailto:adi.r...@confluxtechnologies.com] 
Sent: Friday, October 28, 2016 02:58 AM
To: dev 
Subject: Re: Fineract Board Report for November

+1

On 27-Oct-2016 11:59 PM, "Jim Jagielski"  wrote:

> It's not only the release but also the general way in which things are 
> progressing...
>
> > On Oct 27, 2016, at 1:38 PM, Myrle Krantz  wrote:
> >
> > I think that would be great! This is my +1.
> >
> > I'm surprised that we would propose this after just one release though.
> Is that within the expected range?
> >
> > Greets,
> > Myrle
> >
> > Sent from my iPhone
> >
> >> On 27 Oct 2016, at 19:27, Jim Jagielski  wrote:
> >>
> >> Thx for the report!
> >>
> >> I would like to raise the possibility of calling for Graduation of 
> >> Fineract. What does everyone think?
> >>
> >>> On Oct 27, 2016, at 1:22 PM, Ed Cable  wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I've started the Board Report for November:
> >>>
> >>> *https://cwiki.apache.org/confluence/display/FINERACT/
> 2016-11+November+Report
> >>>  2016-11+November+Report>*
> >>>
> >>> Adi will be adding in technical details regarding the release and
> OpenJPA
> >>> integration. Please review and add any comments/additions that you 
> >>> may have. The report is due on November 2 so I will be submitting 
> >>> it at
> the end
> >>> of my work day on November 1 (PDT)
> >>>
> >>> Thanks,
> >>>
> >>> Ed
> >>
>
>

RE: [VOTE] [FINERACT] 0.4.0-incubating for release

[Markus Geiß]

+1

-Original Message-
From: Nazeer Shaik [mailto:nazeer1100...@apache.org] 
Sent: Monday, October 17, 2016 01:31 PM
To: dev@fineract.incubator.apache.org
Subject: [VOTE] [FINERACT] 0.4.0-incubating for release

Hello Fineract community,

We have created 0.4.0-incubating release, with the artifacts below up for a 
vote.

*These are the goals of this release:*

   - Removed hibernate dependency from the Fineract and integrated OpenJPA
   as default JPA provider


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


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


This is a *source code tar ball* only release.

*** Please download, review and vote by Thu Oct 20, 2016 @ 6pm PST ***

*Source Files:*
https://dist.apache.org/repos/dist/dev/incubator/fineract/0.4.0-incubating/


*Commit to be voted on:*

https://git-wip-us.apache.org/repos/asf?p=incubator-fineract.git;a=commit;h=refs/heads/0.4.0-incubating


*Build verification steps can be found at: * Refer 'README.md' in 
apache-fineract-0.4.0-incubating-src.tar.gz

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


*Note: *

   - This is a source only release with no binaries, with instructions on
   how to build/test the application.
   - We have removed hibernate dependency from running integration tests.
   Now Fineract is integrated with OpenJPA.

To help in tallying the vote, members please be sure to indicate "(binding)" 
with your vote.

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

Thank you,
Nazeer

Re: [Mifos-developer] Cashier Transactions - Non Portfolio Entries

[Markus Geiß]

Hey all,

just a heads up.

Given that the current accounting and ledger system is not made for a real
teller service, we will respect this with the work we are doing for the
next generation of Mifos.

All enhancements and additional requirements will be implemented in the new
framework, allowing way more flexibility than today.

Saying this, the current implementation of teller management serves the
purpose it was made for, just customer facing cash transactions, and will
be delivered as is.

Best wishes,


*Markus Geiss*
Chief Architect
RɅĐɅЯ, The Mifos Initiative
mge...@mifos.org | Skype: mgeiss.mifos.org | Mobil: +49.152.295.05306 |
http://mifos.org  




On Fri, Oct 7, 2016 at 2:15 PM, Ed Cable  wrote:

> Zayyad,
>
> Dayna along with Robert Ippez is working on specifications for an enhanced
> teller cash management module. I'm glad to see that we have so many
> community members with a need for it along with such valuable input. I'll
> have her share a draft of the specification when it's ready so everyone can
> give input and feedback on the requirements.
>
> Cheers,
>
> Ed
>
> On Fri, Oct 7, 2016 at 12:18 AM, Sendoro juma  wrote:
>
>> Dear Zayyad,
>> I see a room for improvement, may be branch this way!
>> Transactions  - Clients- Office
>> Best RegardsSendoro
>>
>>
>>
>>
>>
>>
>> On Fri, Oct 7, 2016 at 8:19 AM +0300, "Zayyad A. Said" <
>> zay...@intrasofttechnologies.com> wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Exactly my sentiments, cashiers should not have access to the main vault.
>>
>>
>>
>> I think this whole teller module in Mifos X needs to be enhanced. Having
>> it as a complete separate module would make more sense other than just
>> using payment type of cash.
>>
>>
>>
>> My experience with other banking platforms is that cashiers have their
>> own module where they can do deposit and withdrawal to either customer or
>> GL account.
>>
>>
>>
>> If we just limit the teller module for bank customers then it becomes
>> useless to those MFIs (especially non deposit taking) which do not take
>> cash payments from their clients but use mobile money or bank.
>>
>>
>>
>> Regards;
>>
>>
>>
>> ***
>>
>> Zayyad A. Said | Chairman & C.E.O
>>
>>
>>
>> Cell No.: +254 716 615274 | Skype: zsaid2011
>>
>> Email: zay...@intrasofttechnologies.com
>>
>>
>>
>>
>>
>>
>>
>> From: mitos imperial [mailto:nutcracke...@gmail.com]
>> Sent: 07 October 2016 08:12
>> To: serge.amega...@ovamba.com; Mifos software development
>> Cc: dev@fineract.incubator.apache.org; Zayyad A. Said
>> Subject: Re: [Mifos-developer] Cashier Transactions - Non Portfolio
>> Entries
>>
>>
>>
>> Best business practices would dictate that only cahier has access to the
>> cash vault..transactions are limited to bulk cash requisition ( in/out)
>> usually involving cash requisition or transfer by teller to cashier. All
>> daily  transactions either done with customer or payments of expenses are
>> done thru the tellers..
>>
>>
>>
>> On Oct 7, 2016 1:05 PM, "Serge AMEGAVIE" 
>> wrote:
>>
>> Yes I understand, but it will not be affected if the transaction is done
>> from the main vault, not from the cashier... In fact that is how it works
>> in my particular zone...we do a petty cash allowance from the vault, the
>> transaction show at the main vault and affect it balance along with
>> denomination and the payment is done via a General Ledger journal entry.
>>
>> Thank you
>> Sent from my BlackBerry® smartphone
>>
>> -Original Message-
>> From: "Zayyad A. Said" 
>> Date: Fri, 7 Oct 2016 07:36:50
>> To: ; 'Mifos software development'<
>> mifos-develo...@lists.sourceforge.net>; > .org>
>> Subject: RE: [Mifos-developer] Cashier Transactions - Non Portfolio
>> Entries
>>
>> I think it does make sense.
>>
>> Even though it's not a customer transaction but the cash position of the
>> cashier has been affected, if you want to settle cash don’t you think the
>> cashier will show to have more cash than what it is actually in the till?
>>
>> I have seen MFIs using cashiers tills for their petty disbursements, how
>> should this be handled?
>>
>> Regards;
>>
>> ***
>> Zayyad A. Said | Chairman & C.E.O
>>
>> Cell No.: +254 716 615274 | Skype: zsaid2011
>> Email: zay...@intrasofttechnologies.com
>>
>>
>>
>> -Original Message-
>> From: Serge AMEGAVIE [mailto:serge.amega...@ovamba.com]
>> Sent: 07 October 2016 02:15
>> To: Mifos software development; dev@fineract.incubator.apache.org
>> Subject: Re: [Mifos-developer] Cashier Transactions - Non Portfolio
>> Entries
>>
>> As this is not a "front office" transaction (meaning from a customer
>> account) I'm not really sure this make sens to appear in cash journal...
>> Best Regards
>> Sent from my BlackBerry® smartphone
>>
>> -Original 

Re: [Mifos-developer] [Need help] Refernce UI and FS document for survey framework APIs

[Markus Geiß]

Hey Nayan,

here you can find the concept docu:

https://mifosforge.jira.com/wiki/display/MIFOSX/Social+Performance+Management+Framework

Best wishes,

Markus Geiss
Chief Architect
RɅĐɅЯ, The Mifos Initiative

On Oct 4, 2016 10:09, "Gaurav Saini"  wrote:

Hello Nayan,

I have worked on the Survey UI a while back and its inside the code.
Actually, I didn't have any mockups with me just designed it directly
according to how the data is coming from APIs.
I think you can design and develop on top of that, code is in develop
branch for survey.

Thanks
Gaurav

 Sent with Mailtrack


On Tue, Oct 4, 2016 at 1:23 PM, Ed Cable  wrote:

> Markus,
>
> Can you help Nayan when you get the chance? Gaurav - can you point Nayan
> anywhere?
>
> Ed
>
> On Sat, Oct 1, 2016 at 10:26 PM, Nayan Ambali 
> wrote:
>
>> Dear Community,
>>
>> I need to develop user interface for SPM, I see API available for the
>> same in API documentation. Do we have reference UI or UI mock-ups and
>> functional specification document for the SPM/Survey.
>>
>> -
>> Nayan Ambali
>>
>>
>> 
>> --
>> 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*
> Director of Community Programs, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>


-- 
Regards,
*Gaurav Saini*

RE: Open Financial Exchange Protocol

[Markus Geiß]

Hey Sendoro,

Apache Fineract currently does not support OFX.

But you are welcome to add this capability to the platform. ; o)

Cheers

Markus

-Original Message-
From: Sendoro juma [mailto:send...@singo.co.tz] 
Sent: Sunday, September 4, 2016 07:02 PM
To: dev@fineract.incubator.apache.org
Subject: Open Financial Exchange Protocol

Dear All,
Does fineract support  http://www.ofx.net ? 

Best RegardsSendoro 

AW: [VOTE] [FINERACT] 0.3.1-incubating for release

[Markus Geiß]

+1

-Ursprüngliche Nachricht-
Von: Adi Raju [mailto:adi.r...@confluxtechnologies.com] 
Gesendet: Donnerstag, 7. Juli 2016 11:33
An: dev@fineract.incubator.apache.org
Betreff: RE: [VOTE] [FINERACT] 0.3.1-incubating for release

+1

-Original Message-
From: Myrle Krantz [mailto:mkra...@mifos.org]
Sent: 07 July 2016 15:00
To: dev@fineract.incubator.apache.org
Subject: Re: [VOTE] [FINERACT] 0.3.1-incubating for release

Hi all,

Nazeer has addressed my concerns (on his holiday -- that's dedication).
I'm changing my vote to +1.

Greets,
Myrle


*Myrle Krantz*
Solutions Architect
RɅĐɅЯ, The Mifos Initiative
mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org 
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>


On Wed, Jul 6, 2016 at 9:35 PM, Myrle Krantz <mkra...@mifos.org> wrote:

> I'm voting +0 on this release:
>
> Here's what I checked:
> Notice file: looks good
> License file: contains a reference to a license file (glyphicons.MIT) 
> which is not present under licenses. Also, I learned recently from 
> Justin's example project 1) that the version of the bundled project 
> should be included since sometimes licenses change from one version to the 
> next.
> Signature: Is signed with an apache e-mail address associated key, but 
> I was unable to verify the fingerprint with Nazeer.
> Buildable: works according to instructions in README
>
> I was unable to verify that the integration tests work according to 
> the instructions, because I'm having problems with my installation of 
> mysql, but I'm willing to assume the best.
>
> If we can fix the minor license file issues (add versions and add 
> glyphicons.MIT to licenses, and if I can verify the signature with 
> Nazeer, I'll change my vote to a +1.
>
> Greets from the Voreifel, Germany,
> Myrle
>
> 1.) https://github.com/justinmclean/ApacheWombat/blob/master/LICENSE
>
>
>
> *Myrle Krantz*
> Solutions Architect
> RɅĐɅЯ, The Mifos Initiative
> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org 
> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>
>
> On Wed, Jul 6, 2016 at 7:19 PM, Nazeer Shaik < 
> nazeer.sh...@confluxtechnologies.com> wrote:
>
>> Thank you Markus. I have addressed the issue and updated release files.
>>
>> The new commit to be voted is:
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-fineract.git;a=co
>> mmit;h=a62620811975f88e9741732c3cb04838dc44b634
>>
>> *Source Files:*
>>
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.3.1-incub
>> ating/
>>
>> *All, can you please review and vote again by July 07, 2016 @ 6pm
>> PST.*
>>
>> Thanks,
>> Nazeer
>>
>> On Wed, Jul 6, 2016 at 2:44 PM, Markus Geiß <markus.ge...@live.de> wrote:
>>
>> > -1 Still some UI related licenses packaged ...
>> >
>> > -Ursprüngliche Nachricht-
>> > Von: Nazeer Shaik [mailto:nazeer1100...@apache.org]
>> > Gesendet: Freitag, 1. Juli 2016 08:47
>> > An: dev@fineract.incubator.apache.org
>> > Betreff: [VOTE] [FINERACT] 0.3.1-incubating for release
>> >
>> > Hello Fineract community,
>> >
>> > We have created a 0.3.1-incubating release, with the artifacts 
>> > below up for a vote.
>> >
>> > This is the 1st release for Apache Fineract (incubating).
>> >
>> > There are two main goals of this release:
>> >
>> >- Clear all license issues in the code base and make it legally
>> ready to
>> >be adopted by the community.
>> >
>> >
>> >- Share the new features that have been developed so far, in order to
>> >give the community a good sense of the upcoming 0.3.1 release.
>> >
>> >
>> > *For more information including release notes, please see:*
>> >
>> https://cwiki.apache.org/confluence/display/FINERACT/0.3.1+Release-+A
>> pache+Fineract
>> >
>> > This is a *source code tar ball* only release.
>> >
>> > *** Please download, review and vote by Mon July 05, 2016 @ 6pm PST
>> > ***
>> >
>> > *Source Files:*
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.3.1-incub
>> ating/
>> >
>> > *Commit to be voted on:*
>> >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-fineract.git;a=co
>> mmit;h=1c2aa1980ea59b8decf5d954f74566fb393cda5f
>> >
>> > *Build verification steps can be found at: * Refer 'README.md' in 
>> > apache-fineract-0.3.1-incubating-src.tar.gz
>> >
>> > *KEYS file containing PGP Keys we use to sign the release:* 
>> > https://dist.apache.org/repos/dist/dev/incubator/fineract/KEYS
>> >
>> >
>> > *Note: *
>> >
>> >- This is a source only release with no binaries, with 
>> > instructions
>> on
>> >how to build/test the application.
>> >
>> >
>> >- We use hibernate for integration tests only and doesn't include any
>> >source or binary from Hibernate
>> >
>> > To help in tallying the vote, members please be sure to indicate 
>> > "(binding)" with your vote.
>> >
>> > [ ] +1  approve
>> > [ ] +0  no opinion
>> > [ ] -1  disapprove (and reason why)
>> >
>> > Thank you,
>> > Nazeer
>> >
>>
>
>

AW: [VOTE] [FINERACT] 0.3.1-incubating for release

[Markus Geiß]

-1 Still some UI related licenses packaged ...

-Ursprüngliche Nachricht-
Von: Nazeer Shaik [mailto:nazeer1100...@apache.org] 
Gesendet: Freitag, 1. Juli 2016 08:47
An: dev@fineract.incubator.apache.org
Betreff: [VOTE] [FINERACT] 0.3.1-incubating for release

Hello Fineract community,

We have created a 0.3.1-incubating release, with the artifacts below up for a 
vote.

This is the 1st release for Apache Fineract (incubating).

There are two main goals of this release:

   - Clear all license issues in the code base and make it legally ready to
   be adopted by the community.


   - Share the new features that have been developed so far, in order to
   give the community a good sense of the upcoming 0.3.1 release.


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

This is a *source code tar ball* only release.

*** Please download, review and vote by Mon July 05, 2016 @ 6pm PST ***

*Source Files:*
https://dist.apache.org/repos/dist/dev/incubator/fineract/0.3.1-incubating/

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

*Build verification steps can be found at: * Refer 'README.md' in 
apache-fineract-0.3.1-incubating-src.tar.gz

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


*Note: *

   - This is a source only release with no binaries, with instructions on
   how to build/test the application.


   - We use hibernate for integration tests only and doesn't include any
   source or binary from Hibernate

To help in tallying the vote, members please be sure to indicate "(binding)" 
with your vote.

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

Thank you,
Nazeer

AW: [Mifos-developer] [IMPORTANT] Query regarding standard address table

[Markus Geiß]

Hey all,

​​

agreed. BTW there is a ISO standard covering addressing, ISO 19160.

We should consider this when implementing addresses.



Cheers



Markus



Von: Saransh Sharma
Gesendet: Donnerstag, 30. Juni 2016 01:34
An: dev@fineract.incubator.apache.org
Betreff: Re: [Mifos-developer] [IMPORTANT] Query regarding standard address 
table



https://github.com/maektwain/INNOVA/blob/master/mifosng-provider/src/main/java/org/mifosplatform/portfolio/client/api/ClientAddressApiResource.java

We have been using this standard API of addresses you can have a look at
it, we have infact desgined the UI in community app, the business logic is
standard here, but we can always extend

On Thu, Jun 30, 2016 at 12:11 AM Ed Cable  wrote:

> +1 from my side to making client address a standard out of the box feature
> as a part of the core client record provided we address sander's feedback
> from the previous thread on this on April 12 -
>
> https://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201604.mbox/browser
> and make the fields generic enough such that it supports the most common
> address formats used worldwide. We should incorporate all the feedback and
> discussion from that thread regarding turning these fields on and off and
> the proper field-level validations.
>
> This is coming up on numerous active threads and I thank Nayan for
> recognizing all the different use cases where not having address fields as
> part of core client record is an inhibitor.
>
> On Wed, Jun 29, 2016 at 5:49 AM, Nayan Ambali 
> wrote:
>
> > Dayna, Markus,
> >
> > I feel, adding standard address to customer solves other problems too,
> > example address can be made mandatory before activating client, address
> can
> > be capture along with customer creation, Geo location based service on
> > Android can built.
> >
> > i vote for adding client address as standard(out of box) feature.
> >
> > Thanks
> > Nayan Ambali
> >
> >
> >
> > Thanks and Regards,
> > Nayan Ambali
> > +91 9591996042
> > skype: nayangambali
> >
> > On Wed, Jun 29, 2016 at 6:07 PM,  wrote:
> >
> >> Hello Devs,
> >>
> >> While designing the credit bureau module, I came across few design
> >> questions and I wanted community's opinion on that.
> >> When you make a credit check query, the credit bureau expects you to
> send
> >> the address along with few other identifiers.
> >>
> >> In order to fetch the address fields in a more hassle free and less
> error
> >> prone way, I was thinking if we can standardize the address as core
> table.
> >> By standardizing this address table, we may remove the need for defining
> >> custom data table for storing addresses.
> >>
> >> Let me know your thoughts on this proposal of mine.
> >>
> >> Regards,
> >> Nikhil
> >>
> >>
> >
> >
> >
> --
> > Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San
> > Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> > present their vision of the future. This family event has something for
> > everyone, including kids. Get more information and register today.
> > http://sdm.link/attshape
> > Mifos-developer mailing list
> > mifos-develo...@lists.sourceforge.net
> > Unsubscribe or change settings at:
> > https://lists.sourceforge.net/lists/listinfo/mifos-developer
> >
>

Question about micro services from Saransh

[Markus Geiß]

In addition to our multi-tenancy approach initially designed by Keith we will 
add a NoSQL solution to the mix.

Purely relational data with lower read/write performance will be stored in a 
RDBMS, data that is highly read/write will be stored in the NoSQL DB following 
the multi-tenancy approach using keyspaces and partitions.

Cheers

Markus

On Jun 20, 2016 19:51, "Saransh Sharma" 
> wrote:

As i was trying my hands on Micro-Services , it is really amazing and provides 
lot of support in terms of how an application can scale but i have few things 
in my mind which is how to support the mulit-tenancy

because in this kind of architecture providing again a monolithic DB with 
tenant Support with won't it be the same thing like right now

What are your thoughts on multi-tenancy for microservices

Re: Beginner at FOSS and development in general

[Markus Geiß]

no reason to apologize ... I guess you have installed gradle too ... just dir 
into the fineract-provider folder (where build.gradle is located) and execute 
gradle clean build.



On Sun, Jun 19, 2016 at 8:59 PM +0200, "Anirudh Jain" 
<spond...@gmail.com<mailto:spond...@gmail.com>> wrote:

Hi,

I have forked the github project and created a local copy on my eclipse
ide. I am a bit confused on how to proceed with the build next. The
instructions on the website say build it as a gradle project. Will that be
the fineract-provider folder?
I am sorry for asking such a basic question.

Rgds,
Anirudh

On Sun, Jun 19, 2016 at 6:04 PM, Markus Geiß <markus.ge...@live.de> wrote:

> Hey Anirudh,
>
> simply try to setup your dev environment to be able to mimic the bug,
>
> Then create a branch named after the issue and try to solve it. Once you
> feel comfortable, send a pull request and we will review and comment.
>
> Best,
>
> Markus
>
> .::YAGNI likes a DRY KISS::.
>
>
>
>
> From: Anirudh Jain <spond...@gmail.com>
> Sent: Saturday, June 18, 2016 9:36 PM
> To: dev@fineract.incubator.apache.org
> Subject: Re: Beginner at FOSS and development in general
>
> Hi Markus,
>
> Thanks for your help. After going through the bug list I think FINERACT-176
> is the one I would like to tackle first. It seems simple enough. But what
> should i do next?
>
> Rgds,
> Anirudh
> On 14-Jun-2016 9:21 AM, "Markus Geiß" <markus.ge...@live.de> wrote:
>
> > Hey Anirudh,
> >
> >
> > first of all welcome.
> >
> >
> > I'd recommend to search JIRA for a bug or two you fell attracted too.
> > Simply click here for a list:
> >
> >
> >
> >
> https://issues.apache.org/jira/browse/FINERACT-166?jql=project%20%3D%20FINERACT%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Open
> >
> >
> > Once you've found a, drop us line at the dev list and we will try to help
> > get all steps done needed to fix it.
> >
> >
> > Best,
> >
> > Markus
> >
> > .::YAGNI likes a DRY KISS::.
> >
> >
> > 
> > From: Anirudh Jain <spond...@gmail.com>
> > Sent: Monday, June 13, 2016 4:49 PM
> > To: dev@fineract.incubator.apache.org
> > Subject: Beginner at FOSS and development in general
> >
> > Hi all,
> >
> > I am a student and a coder and an open source enthusiast. After months of
> > going through projects and getting frustrated, in general, I would very
> > much like to be a part of the fineract project. I have read the
> > contributor's guide on the fineract web page but I am still a little bit
> > confused about how to get the developer environment running.
> >
> > I have forked the git repo and added to my eclipse IDE. I am a little
> > confused how to proceed from here and also taking my first steps. I will
> be
> > glad to accept any help I can get.
> >
> > Regards,
> > Anirudh Jain
> >
>
>

Re: Beginner at FOSS and development in general

[Markus Geiß]

Hey Anirudh,

simply try to setup your dev environment to be able to mimic the bug,

Then create a branch named after the issue and try to solve it. Once you
feel comfortable, send a pull request and we will review and comment.

Best,

Markus

.::YAGNI likes a DRY KISS::.   




From: Anirudh Jain <spond...@gmail.com>
Sent: Saturday, June 18, 2016 9:36 PM
To: dev@fineract.incubator.apache.org
Subject: Re: Beginner at FOSS and development in general
    
Hi Markus,

Thanks for your help. After going through the bug list I think FINERACT-176
is the one I would like to tackle first. It seems simple enough. But what
should i do next?

Rgds,
Anirudh
On 14-Jun-2016 9:21 AM, "Markus Geiß" <markus.ge...@live.de> wrote:

> Hey Anirudh,
>
>
> first of all welcome.
>
>
> I'd recommend to search JIRA for a bug or two you fell attracted too.
> Simply click here for a list:
>
>
>
>  
> https://issues.apache.org/jira/browse/FINERACT-166?jql=project%20%3D%20FINERACT%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Open
>
>
> Once you've found a, drop us line at the dev list and we will try to help
> get all steps done needed to fix it.
>
>
> Best,
>
> Markus
>
> .::YAGNI likes a DRY KISS::.
>
>
> 
> From: Anirudh Jain <spond...@gmail.com>
> Sent: Monday, June 13, 2016 4:49 PM
> To: dev@fineract.incubator.apache.org
> Subject: Beginner at FOSS and development in general
>
> Hi all,
>
> I am a student and a coder and an open source enthusiast. After months of
> going through projects and getting frustrated, in general, I would very
> much like to be a part of the fineract project. I have read the
> contributor's guide on the fineract web page but I am still a little bit
> confused about how to get the developer environment running.
>
> I have forked the git repo and added to my eclipse IDE. I am a little
> confused how to proceed from here and also taking my first steps. I will be
> glad to accept any help I can get.
>
> Regards,
> Anirudh Jain
>

Re: Beginner at FOSS and development in general

[Markus Geiß]

Hey Anirudh,


first of all welcome.


I'd recommend to search JIRA for a bug or two you fell attracted too. Simply 
click here for a list:


https://issues.apache.org/jira/browse/FINERACT-166?jql=project%20%3D%20FINERACT%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Open


Once you've found a, drop us line at the dev list and we will try to help get 
all steps done needed to fix it.


Best,

Markus

.::YAGNI likes a DRY KISS::.



From: Anirudh Jain 
Sent: Monday, June 13, 2016 4:49 PM
To: dev@fineract.incubator.apache.org
Subject: Beginner at FOSS and development in general

Hi all,

I am a student and a coder and an open source enthusiast. After months of
going through projects and getting frustrated, in general, I would very
much like to be a part of the fineract project. I have read the
contributor's guide on the fineract web page but I am still a little bit
confused about how to get the developer environment running.

I have forked the git repo and added to my eclipse IDE. I am a little
confused how to proceed from here and also taking my first steps. I will be
glad to accept any help I can get.

Regards,
Anirudh Jain

RE: Read up on Cloud Foundry

[Markus Geiß]

Hey Roman,

nope. ; o)

Cloud Foundry is one possible solution, if we run on a PaaS, but not
the only one. The sent resource to lookup should simply help get others
on speed on the topic.

We've spent a lot of time understanding the topic and believe it is fruitful
for others too to help create a solid base to find a decision within the
community.

Best,

Markus

.::YAGNI likes a DRY KISS::.



> Date: Thu, 2 Jun 2016 09:38:18 -0700
> Subject: Re: Read up on Cloud Foundry
> From: ro...@shaposhnik.org
> To: dev@fineract.incubator.apache.org
>
> Myrle, quick question: are you saying that CF will be the preferred
> runtime for Fineract?
>
> Thanks,
> Roman.
>
> On Thu, Jun 2, 2016 at 9:19 AM, Myrle Krantz  wrote:
>> Hi all,
>>
>> Here's an overview of the architecture of CloudFoundry Diego:
>>
>> https://docs.cloudfoundry.org/concepts/diego/diego-architecture.html
>>
>> This should help the detail-oriented reader understand how services are
>> deployed and balanced within a cloud deployment. This understanding, in
>> turn, should give you a framework for understanding how scalability and
>> availability are achieved within a cloud deployment.
>>
>> Greets,
>> Myrle
>>
>>
>> *Myrle Krantz*
>> Solutions Architect
>> RɅĐɅЯ, The Mifos Initiative
>> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
>>  
  

RE: [DISCUSSION] UPI Integration

[Markus Geiß]

> To: dev@fineract.incubator.apache.org
> From: meta1...@gmail.com
> Subject: [DISCUSSION] UPI Integration
> CC: mifos-develo...@lists.sourceforge.net
> Date: Tue, 31 May 2016 15:23:18 +0530
>
> Hi all,
>
> There are three components in UPI. PSP Apps (created by PSPs), PSP
> Servers (backend for PSP apps), and UPI Server (managed by NPCI).
>
> PSPs (Payment System Players) are Banks, Payment Banks, PPIs, or any
> other RBI regulated entities that are allowed to acquire customers and
> provide payment (credit/debit) services to individuals or
> entities. The list of authorized PSPs[1] is maintained on RBI website.
> [1] https://www.rbi.org.in/Scripts/PublicationsView.aspx?id=12043
>
> This is how an individual is supposed to use UPI: He has a bank
> account. He will install any of the PSP Apps on his mobile. Create his
> virtual address and tie a bank account with that address. Now he can
> pay or collect money to/from other virtual addresses.
>
> Let's refer to Fineract user as an MFI. MFIs are not interested in
> becoming a PSP. So they are not PSPs. So we won't be implementing a
> PSP Server. MFI can use an existing PSP App, which will be a mobile
> app. This is cumbersome/impractical. We cannot write our own client if
> their ToS prohibits it. So, we hope that PSPs will open up their
> backends to public, so that we can legally write our own custom client
> to talk to the PSP server. But it is not at all clear whether PSP's
> will open up their backends. Most of the UPI documents released by
> NPCI focus only on the protocol between PSP Server and UPI Server, and
> do not say anything about standardization of protocol between PSP Apps
> and PSP Servers. If this isn't standardized or opened up, we cannot
> have full UPI integration.
>
> On page 15, of the UPI Product Document[2], under §12 Certification of
> members, it says "b). It is also being explored if there is a need to
> certify every PSP Application that will talk to UPI. If the decision
> is in favor of certifying an application of the PSP, we will finalize
> the modalities thereto." I think they have messed up the terminology
> here. I think what they mean is they are exploring whether to require
> certification of PSP Servers which are allowed to talk to the UPI
> server.
>
> [2] https://mifosforge.jira.com/wiki/display/MIFOSX/Unified+Payment+Interface
>
> Even if PSPs don't open up their API, there is a way we can still use
> UPI. It is by creating a third party merchant mobile app. According to
> the diagram on page 10 of UPI API Tech Spec, third party apps can only
> use Collect methods of the API. These merchant apps are supposed to
> call into any of the PSP apps that are already installed on the
> device. On Android this will be using Intents.
>
> Other concerns:
>
> At several places in NPCI docs[2], it says the PSP apps 'need to use' the
> "common library" for secure credential capture
> (MPIN/Password/PIN/Biometrics etc). Since we are not building a mobile
> app, we won't be using the library for credential capture. Credentials
> will be saved in the database.
>
> At several places in NPCI docs, the term "Mobile device
> fingerprinting" is used. This is a bad sign for two reasons. First
> because relying on device fingerprint for identifying a physical
> mobile device is very insecure design decision. I don't know what
> constitutes the fingerprint, but things like IMEI, Android ID can be
> easily spoofed by using an emulator. Second reason is that it hints
> that PSP Server-App communication is not going to be standardized or
> opened up, and PSP's are free to use their own custom protocols there.
>
> So currently the only guaranteed way we can use UPI is by creating the
> merchant app. Since I believe we already have a Mifos mobile app, we
> only have to add this functionality there. An MFI will create a
> self-branded instance of this app and use it for collection/repayment
> (not possible for disbursement).
>
> What I could find though was that NPCI conducted a hackathon few
> months ago, wherein they had participants write PSP apps and
> servers. For the purpose of writing the apps, they defined a
> JSON-based protocol[3] and provisioned a sandbox PSP Server to test
> against. This protocol seems to have been defined for the sole purpose
> of the hackathon. If they wanted to standardize it they would have
> mentioned it in the tech spec documents. See Hackathon resouces[4] for
> more info.
>
> [3] 
> https://mifosforge.jira.com/wiki/download/attachments/138412058/Hackathon-PSP%20Server%20integration%20and%20usage.pdf?version=1=1464684199474=v2
> [4] 
> https://www.hackerearth.com/sprints/unified-payments-interface-hackathon/resources/
>
> According to a news article[5], 10 banks are ready with their apps but
> they won't be launching until mid-June.
> [5] 
> http://www.business-standard.com/article/finance/wait-for-2-months-to-transact-on-unified-payments-interface-116041200758_1.html
>

RE: [MENTORS] multiple repos for one Apache Product?

[Markus Geiß]

> Date: Thu, 26 May 2016 15:52:50 -0700
> Subject: Re: [MENTORS] multiple repos for one Apache Product?
> From: ro...@shaposhnik.org
> To: dev@fineract.incubator.apache.org
>
> On Thu, May 26, 2016 at 8:42 AM, Markus Geiß <markus.ge...@live.de> wrote:
>>
>> 
>>> Date: Thu, 26 May 2016 08:38:53 -0700
>>> Subject: Re: [MENTORS] multiple repos for one Apache Product?
>>> From: ro...@shaposhnik.org
>>> To: dev@fineract.incubator.apache.org
>>>
>>> On Thu, May 26, 2016 at 5:03 AM, Markus Geiß <markus.ge...@live.de> wrote:
>>>> Hey Roman,
>>>>
>>>> Given that every micro service is implemented as a standalone artifact that
>>>> can be replaced, and for this it utilizes its own versioning, I believe it 
>>>> would
>>>> be more in line with ASF if every service is a repo.
>>>>
>>>> We will release these independently from each other running their own 
>>>> versions.
>>>
>>> What are you planning as far as compatibility matrix? Will you guarantee 
>>> that
>>> any combination of versions will work together?
>>>
>>> Thanks,
>>> Roman.
>>
>> We are planing to allow the parallel usage of 2 major versions. Every micro 
>> service
>> will come with a versioned API and a versioned REST endpoint.
>>
>> Minor version will be backwards compatible by 'contract'.
>
> I think this could be a good case for separate repos then. Next
> question: how many of
> these would you consider requesting? Do you see the # growing over time? If 
> yes
> by how much?
>
> Thanks,
> Roman.

As far as we can foresee now I guess we'll end up with a dozen. If we detect 
another
needed business domain in the future this would result in requesting a new 
repo, but
I believe it will be only 1 or 2 per year, even less.

Best,

Markus

.::YAGNI likes a DRY KISS::.
  

RE: [MENTORS] multiple repos for one Apache Product?

[Markus Geiß]

> Date: Wed, 25 May 2016 18:56:14 -0700
> Subject: Re: [MENTORS] multiple repos for one Apache Product?
> From: ro...@shaposhnik.org
> To: dev@fineract.incubator.apache.org
>
> On Wed, May 25, 2016 at 12:29 AM, Markus Geiß <markus.ge...@live.de> wrote:
>> 
>>> Date: Tue, 24 May 2016 20:33:06 -0700
>>> Subject: Re: [MENTORS] multiple repos for one Apache Product?
>>> From: ro...@shaposhnik.org
>>> To: dev@fineract.incubator.apache.org
>>>
>>> On Tue, May 24, 2016 at 5:27 AM, Myrle Krantz <mkra...@mifos.org> wrote:
>>>> Hi Mentors,
>>>>
>>>> I asked this question in the thread on microservices, but the e-mail was
>>>> long and most of the content was not relevant for you guys so you may have
>>>> missed it:
>>>>
>>>> As far as I can tell the current mode of operation at Apache is one
>>>> repository to one product. I would prefer to work with one repository per
>>>> service. I believe that would help programmers remain strict about
>>>> division of labor between the services, and think more carefully about
>>>> interface breaking changes. Is there any reason a product can’t have
>>>> multiple repositories?
>>>
>>> Multiple repos are, of course, permissible. However, the question you should
>>> be asking your self are more along the lines of how much of a de-couple
>>> release policy AND community participation do you want to have between
>>> these projects. Because the thing is, if your repos are independent enough
>>> wrt. release schedules AND independent enough regarding who commits
>>> to them ASF will be asking a question of breaking you into a set of 
>>> projects.
>>>
>>> Does this answer you question?
>>>
>>> Thanks,
>>> Roman.
>>
>> Hey Roman,
>>
>> thanks for the answer. ; o)
>>
>> To provide a little more context. We are currently working on a per-service
>> repository approach to reduce unwanted cross service usage of internal
>> classes and implementations.
>>
>> Every business domain will become a micro service and a single repository
>> with multiple modules.
>
> The real question you should be asking yourself is how are you going to
> release those things. The "contract" that ASF has with the rest of the normal
> world is that we release software as tarballs/zips/etc. Source code
> repo(s) is an
> implementation details. With that in mind, please tell us about your release
> strategy for these multiple repos and then we may be able to help refine
> this.
>
> Thanks,
> Roman.

Hey Roman,

Given that every micro service is implemented as a standalone artifact that
can be replaced, and for this it utilizes its own versioning, I believe it would
be more in line with ASF if every service is a repo.

We will release these independently from each other running their own versions.

To answers Ross' question. We won't have different permissions for each micro
service. Once a committer, always a committer. It would simply lower the barrier
for a dev to pick the component he would like to work on, and frees him from
some complexity by using a small and dedicated source set.

Best,

Markus

.::YAGNI likes a DRY KISS::.

  

RE: [MENTORS] multiple repos for one Apache Product?

[Markus Geiß]

> Date: Tue, 24 May 2016 20:33:06 -0700
> Subject: Re: [MENTORS] multiple repos for one Apache Product?
> From: ro...@shaposhnik.org
> To: dev@fineract.incubator.apache.org
>
> On Tue, May 24, 2016 at 5:27 AM, Myrle Krantz  wrote:
>> Hi Mentors,
>>
>> I asked this question in the thread on microservices, but the e-mail was
>> long and most of the content was not relevant for you guys so you may have
>> missed it:
>>
>> As far as I can tell the current mode of operation at Apache is one
>> repository to one product. I would prefer to work with one repository per
>> service. I believe that would help programmers remain strict about
>> division of labor between the services, and think more carefully about
>> interface breaking changes. Is there any reason a product can’t have
>> multiple repositories?
>
> Multiple repos are, of course, permissible. However, the question you should
> be asking your self are more along the lines of how much of a de-couple
> release policy AND community participation do you want to have between
> these projects. Because the thing is, if your repos are independent enough
> wrt. release schedules AND independent enough regarding who commits
> to them ASF will be asking a question of breaking you into a set of projects.
>
> Does this answer you question?
>
> Thanks,
> Roman.

Hey Roman,

thanks for the answer. ; o)

To provide a little more context. We are currently working on a per-service
repository approach to reduce unwanted cross service usage of internal
classes and implementations.

Every business domain will become a micro service and a single repository
with multiple modules.

Do you think this approach would lead to get asked by ASF to break into multiple
projects? It wouldn't be that bad if we'd treat these as sub-project of Fineract
as the TLP umbrella for them.

Best,

Markus

.::YAGNI likes a DRY KISS::.
  

RE: Microservices

[Markus Geiß]

iginal design for savings tries to loop through all transactions
> each time interest needs to be calculated etc . This design was made in the
> context of organizations involved in financial inclusion and did not take
> into account the needs of agent banking/ wallets which have hundreds of
> thousands of transactions on an account
>
> -> Absence of archival strategies. The nature of our integrated accounting
> would mean that large organizations would quickly create hundreds of
> millions of records in the journal entry tables. Simple fixes like
> archiving this historical data during closing the books at the end of a
> financial year would drastically improve performance in such cases.
>
> -> Unoptimized batch jobs etc
>
> Given that Mifos v1 scaled to a million active customers accounts, there
> probably is no technical reason that Mifosxv2 shouldn't easily outdo this
> number. I would think that this is something that we should continue
> addressing independent of the development on v3.
>
> The experiences of other communities which have been in identical scenarios
> should also be taken into account, the closest example for us would
> probably be that of the angular community (whom we have relied on
> extensively for the development of our default user interface)
>
> Google informed the angular community that work on v1 would be stopped
> shortly in favor of a complete rewrite, the then as yet conceptual Angular
> v2. This resulted in heated arguments in the community and second thoughts
> in the mind of any organization wanting to start a new project on Angular
> v1 who were rightly concerned about the stability and the potential
> timelines for the rest of the ecosystem / plugins to catch up. Google had
> to eventually backtrack and promise continued development on both versions
> till v1 users decided to organically migrate over to v2.
>
> We should probably explore a similar rollout strategy, gently guiding new
> users to v3 once it approaches feature parity with v2 and independently
> continuing active development and support on v2 till a majority of the
> community has transitioned over.
>
> Regards,
> Vishwas
>
>
> On Tue, May 24, 2016 at 3:02 AM, Markus Geiß <markus.ge...@live.de> wrote:
>
>> Hey all,
>>
>> hope this finds you well. ; o)
>>
>> As mentioned by Myrle we are in the PoC phase, playing with multiple
>> concepts and tools to find a simple and clean approach.
>>
>> We've already shared some code during TechDays in March and have
>> made good progress based on the feedback we've gotten
>>
>> Once we feel the code is ready (meaning we feel comfortable sharing it)
>> we will add our work to the current Fineract repo utilizing a branch, or
>> if feasible setup a few more repos.
>>
>> Once this is done we will give a short intro on the used frameworks,
>> tools, and concepts so everybody is able to dig into it.
>>
>> Given the current issues we are facing in regard to performance (for
>> example every write operation is handled by a command, which is using
>> the same transaction for adjustments and is reaching some partial lock
>> situation on the DB) simply spinning up a second web service won't help.
>>
>> The latest statistics I saw, shared by Conflux, uncovered that the DB is
>> the bottleneck once we reach a critical mass of transactions. 95+% of
>> the time is spent in the DB, not in the web service.
>>
>> We will try to release some of the core features Myrle has talked about
>> pretty soon, so we can tackle some of the issues. For this we will keep
>> the implementation free from any new concept we are thinking about.
>>
>> Best,
>>
>> Markus
>>
>> .::YAGNI likes a DRY KISS::.
>>
>>
>> 
>>> Date: Tue, 24 May 2016 10:23:56 +0100
>>> Subject: Re: Microservices
>>> From: keithwoodl...@gmail.com
>>> To: dev@fineract.incubator.apache.org
>>>
>>> Myrle,
>>>
>>> Sounds like Markus/you have been on this journey for a while already.
>>> Everything sounds great. Be very interested in seeing it come together.
>>>
>>> For that reason I think the sooner you are transparent about where the
>> code
>>> is the better so the community can take a look also and help out where
>>> possible.
>>>
>>> regards,
>>> Keith.
>>>
>>>
>>>
>>> On Tue, May 24, 2016 at 9:07 AM, Myrle Krantz <mkra...@mifos.org> wrote:
>>>
>>>> Hey Keith,
>>>>
>>>> I’ll start with the easy questio

RE: Microservices

[Markus Geiß]

Hey all,

hope this finds you well. ; o)

As mentioned by Myrle we are in the PoC phase, playing with multiple
concepts and tools to find a simple and clean approach.

We've already shared some code during TechDays in March and have
made good progress based on the feedback we've gotten

Once we feel the code is ready (meaning we feel comfortable sharing it)
we will add our work to the current Fineract repo utilizing a branch, or
if feasible setup a few more repos.

Once this is done we will give a short intro on the used frameworks,
tools, and concepts so everybody is able to dig into it.

Given the current issues we are facing in regard to performance (for
example every write operation is handled by a command, which is using
the same transaction for adjustments and is reaching some partial lock
situation on the DB) simply spinning up a second web service won't help.

The latest statistics I saw, shared by Conflux, uncovered that the DB is
the bottleneck once we reach a critical mass of transactions. 95+% of
the time is spent in the DB, not in the web service.

We will try to release some of the core features Myrle has talked about
pretty soon, so we can tackle some of the issues. For this we will keep
the implementation free from any new concept we are thinking about.

Best,

Markus

.::YAGNI likes a DRY KISS::.



> Date: Tue, 24 May 2016 10:23:56 +0100
> Subject: Re: Microservices
> From: keithwoodl...@gmail.com
> To: dev@fineract.incubator.apache.org
>
> Myrle,
>
> Sounds like Markus/you have been on this journey for a while already.
> Everything sounds great. Be very interested in seeing it come together.
>
> For that reason I think the sooner you are transparent about where the code
> is the better so the community can take a look also and help out where
> possible.
>
> regards,
> Keith.
>
>
>
> On Tue, May 24, 2016 at 9:07 AM, Myrle Krantz  wrote:
>
>> Hey Keith,
>>
>> I’ll start with the easy questions:
>>
>> * Have I done this before? Yes. But no woman is an island. I’m happy to
>> have qualified advice.
>>
>> * Where will Markus and I be saving our work? We’ll send you a pointer once
>> we feel it would be productive for others to look at it. Until we have a
>> common understanding of the design and technologies sharing code would be
>> fruitless.
>>
>> I thought about your suggestion for a general approach. I agree we should
>> start with a limited scope, and I like your component break down. I would
>> refine that as follows: Since it’s always been important that
>> Mifos/Fineract is multi-tenanted, I think the best place to start is with a
>> service for tenant allocation and service orchestration. From there, a
>> service for user/permission provisioning would be the obvious next step.
>> Together these represent your service 1. Splitting them is not a
>> fundamentally different design. It is cleaner though, since the user
>> management would be within a tenant, and the only service that should be
>> “tenant-aware” is the one that does tenant allocation. For your second
>> service, you suggest attacking loans next. Savings is just as important as
>> loans, and fundamentally equivalent (just black numbers versus red ones).
>> So after tenant allocation and user creation were complete, the next
>> bare-bones service should be a ledger. Savings and loans products would
>> then be part of a fourth service for describing product offerings. Again,
>> I’ve taken what you represented as one service and made two out of it.
>>
>> All the services except the tenant creation service should treat all data
>> addition/adjustment as a command, just like you originally designed it for
>> Mifos. That approach has worked well and we should stick to it. But
>> command processing should be asynchronous for *everything*. High volumes
>> of write operations in *any* service should not throttle capacity for any
>> other service. The tenant creation service is the one service that can’t
>> use the command pattern, because commands are serialized to a database the
>> tenant creation service provisions.
>>
>> These are the components I just described:
>>
>> A.) A command module for writing and handling commands which would be used
>> by all services. This is a compile time dependency.
>>
>> B.) A tenant service which creates the databases needed for the other
>> services, plus the tables needed for command persistence.
>>
>> C.) A user service which creates the users in the system.
>>
>> D.) A ledger service which tracks payments. Depends on the command module,
>> the tenant service, and the user service.
>>
>> E.) A products service which can be used to configure savings and loans
>> products. Depends on all the other components I described.
>>
>> B & C = Keith’s 1.)
>>
>> D & E = Keith’s 2.)
>>
>>
>> As we move forward we'll probably break it down further than that.
>>
>> These services should be deployed in jetty or tomcat much as today’s Mifos
>> is. We 

[CANCEL] [VOTE] Release Apache Fineract 0.1.2 (incubating)

[Markus Geiß]

Our source release packages is still missing some licenses, and we
need to clean out the source dependency on Hibernate.

Given these issues we cancel this vote and like to thank everyone for
their great work analyzing our release package.

Best,

Markus

.::YAGNI likes a DRY KISS::.  

RE: [VOTE] [FINERACT] 0.1.2-incubating for release

[Markus Geiß]

+1

Best,

Markus

.::YAGNI likes a DRY KISS::.



> Date: Wed, 11 May 2016 16:15:03 +0530
> Subject: Re: [VOTE] [FINERACT] 0.1.2-incubating for release
> From: nayan.amb...@gmail.com
> To: dev@fineract.incubator.apache.org
>
> upvote
>
>
> Thanks and Regards,
> Nayan Ambali
> +91 9591996042
> skype: nayangambali
>
> On Wed, May 11, 2016 at 3:57 PM, Adi Raju 
> wrote:
>
>> +1
>>
>> -Original Message-
>> From: Nazeer Shaik [mailto:nazeer.sh...@confluxtechnologies.com]
>> Sent: 09 May 2016 17:46
>> To: dev@fineract.incubator.apache.org
>> Subject: Re: [VOTE] [FINERACT] 0.1.2-incubating for release
>>
>> Hi Myrle,
>>
>> Thank you for reviewing this release and please find my comments below.
>>
>>> I checked NOTICE and license files.
>>>We still have that pesky hibernate problem. This may well trip us up
>>>in general incubation voting.
>> As suggested by Justin we will initiate a separate mail thread with legal
>> VP for the approval on 'gpl' dependency before sending this release for
>> general incubating votes.
>>
>>>I did wonder why we do not include the gradlewrapper jar in the source
>>>distribution.
>> Since this is source only release, we shouldn't want to include any jar
>> file in it (as suggested by mentor).
>>
>>>I tried the instructions for running integration tests:
>>>I had to change my db password to mysql to get the gradle scripts to work.
>> We have hard coded database password as 'mysql' in migration scripts and
>> in integration tests only. Usually these properties are read from server
>> config files and platform tenants databases and Fineract takes care DB
>> migrations automatically once we restart server with new migration scripts.
>>
>>>FAILURE: Build failed with an exception.
>> The prerequisite for Fineract is MySQL 5.5 which is already mentioned in
>> README.md. You are facing the issue because you might have MySQL 5.7
>> version. Migration scripts won't work on MySQL 5.7. Please check on MySQL
>> 5.5
>>
>> Thanks,
>> Nazeer
>>
>> On Mon, May 9, 2016 at 4:33 PM, Myrle Krantz  wrote:
>>
>>> +1
>>>
>>> As you'll notice from my description below, there are several
>>> weaknesses in this release, but I want us to go through the experience
>>> of voting on a release in the general incubator board, so that we can
>>> get a more complete view of what further problems we might have and
>> start working on them.
>>> Nothing I saw was a blocker for an incubating release, but for a
>>> top-level project release, I will raise my standards.
>>>
>>> Greets from the Voreifel, Germany,
>>> Myrle
>>>
>>>
>>> 1.) I checked NOTICE and license files.
>>> We still have that pesky hibernate problem. This may well trip us up
>>> in general incubation voting.
>>>
>>> 2.) I also built from source:
>>> I did wonder why we do not include the gradlewrapper jar in the source
>>> distribution.
>>> I followed the instructions in the gradle website (
>>> https://docs.gradle.org/current/userguide/gradle_wrapper.html) to
>>> download the specified gradle wrapper, rather than following the
>>> instructions literally. My attempt to follow the instructions literally
>> failed.
>>>
>>> 3.) I tried the instructions for running integration tests:
>>> I had to change my db password to mysql to get the gradle scripts to
>> work.
>>> There's probably a better way, but I didn't bother to spend time
>> searching.
>>> Step 4.b. failed on my first attempt. I dropped the db
>>> mifostenant-default, and tried again and it still failed. Here's the
>>> error:
>>>
>>> "
>>> FAILURE: Build failed with an exception.
>>>
>>> * Where:
>>> Build file
>>>
>>>
>> '/home/myrle/Downloads/apache-fineract-0.1.2-incubating-src/fineract-provider/build.gradle'
>>> line: 264
>>>
>>> * What went wrong:
>>> Execution failed for task ':flywayMigrate'.
 Error occurred while executing flywayMigrate
>>> Error executing statement at line 235: call migrate_withdrwal_fees()
>>> Expression #3 of SELECT list is not in GROUP BY clause and contains
>>> nonaggregated column 'mifostenant-default.sa.withdrawal_fee_amount'
>>> which is not functionally dependent on columns in GROUP BY clause;
>>> this is incompatible with sql_mode=only_full_group_by
>>> Expression #3 of SELECT list is not in GROUP BY clause and contains
>>> nonaggregated column 'mifostenant-default.sa.withdrawal_fee_amount'
>>> which is not functionally dependent on columns in GROUP BY clause;
>>> this is incompatible with sql_mode=only_full_group_by "
>>>
>>> 4.) I checked the signature:
>>> I checked that the signature is valid, and did fingerprint check with
>>> Nazeer via Skype. This is not an ideal fingerprint check, but I don't
>>> know Nazeer well enough that any other method would give me any better
>>> information.
>>>
>>>
>>>
>>> *Myrle Krantz*
>>> Solutions Architect
>>> RɅĐɅЯ, The Mifos Initiative
>>> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
>>> 

FW: About FINERACT-11 | Certain loans crash entire server

[Markus Geiß]

Does someone has a fix for this already?

Best,

Markus

.::YAGNI likes a DRY KISS::.



> From: nels...@grupocspanama.com 
> Date: Mon, 9 May 2016 12:38:47 -0500 
> Subject: About FINERACT-11 | Certain loans crash entire server 
> To: markus.ge...@live.de 
> 
> Hello Markus, 
> 
> We are a small financial institution called Financiera Inverzone, we 
> have been using Mifos for about 1 year and just now we found this 
> problem with many of our loans, sadly, the workaround that is mentioned 
> does not work for us, we want to know if there is some way to support 
> or sponsor the fix of this bug that's critical to our organization. 
> 
> Thanks for your attention. 
> 
> Nelson Nieto 
> Inverzone. 
  

RE: Chained Command and Batch API

[Markus Geiß]

Hey Terence,

according to the API documentation the following actions can be batched:

- Create a new Client
- Update an existing Client
- Apply a Loan to a Client
- Apply Savings to a Client
- Add a new Loan Charge
- Collect an existing Loan Charge
- Activate a Pending Client
- Approve a Pending Loan
- Disburse a Loan

Data tables are currently not supported, and would need to be implemented.

Best,

Markus

.::YAGNI likes a DRY KISS::.



> Date: Tue, 19 Apr 2016 16:34:32 +0530
> Subject: Chained Command and Batch API
> From: tere...@sanjosesolutions.in
> To: dev@fineract.incubator.apache.org
>
> Hi Devs,
>
> While building the offline app, we have a need to run multiple commands
> because of the way Mifos separates out data into core entities and
> datatables. Let's say I have a datatable for client called Client_Fields
> with optional fields Email, Occupation, Country, City, StreetAddr, PIN. If
> I create a client while offline with the usual fields: firstname, lastname,
> dateOfBirth and so on and I also can enter the Email, Occupation, Country,
> City, StreetAddr and PIN and these need to go into the Client_Fields
> datatable, in online mode its as simple as:
>
> *1. Create Client Request*
> method: POST,
> url: baseUrl + "/clients",
> body: {
> firstname: "John",
> lastname: "Wayne",
> dateOfBirth: "1978-05-12",
> officeId: 4,
> 
> }
>
> Response:
> {
> "officeId": 4,
> "resourceId": 12,
> "clientId": 12
> }
>
> 2. Create Client_Fields record
> method: POST
> url: baseUrl + "/datatables/Client_Fields/12",
> body: {
> Country: "India",
> City: "Kolkata",
> ...
> }
>
> Now, if I have to do the same set of operations offline, I don't have
> connectivity to server for long periods and I need to save the additional
> fields and take a client photo in the same offline session, storing the
> state on the device and executing the cached commands when I come back
> online. The challenge is that I don't have the client id till the client
> was created and hence it's difficult to execute dependent operations like
> uploading a photo or creating a datatable record which needs the client id.
> While investigating this, I found the batch API and explored it, but am
> stuck while trying to create datatables. Here's a sample request and
> response for client create and datatable record create:
>
> [
> {
> requestId: 1,
> relativeUrl: "clients",
> method: "POST",
> body: "{ officeId: 4, firstname: 'John', lastname: 'Wayne' }"
> },
> {
> requestId: 2,
> relativeUrl: "datatables/Client_Fields/$.clientId/",
> method: "POST",
> reference: 1,
> body: "{ Country: 'India', City: 'Kolkata' }"
> }
> ]
>
> The response to the first is a 200 but the second yields a 501 Resource
> datatables/Client_Fields/216 does not exist. However if I POST the same
> content manually to the same generated URL datatables/Client_Fields/216,
> I'm able to successfully create the datatable record. Is datatables
> supported in the Batch API and this the expected behaviour for this kind of
> input or should I report a Jira issue if I want this feature?
>
> As an extension of the same requirement, lets say I wanted to upload a
> photo and I have the base64 photo in a string in my application. Can I
> substitute the request above with this:
>
> {
> requestId: 2,
> relativeUrl: "client/$.clientId/images",
> method: "POST",
> reference: 1,
> body: ""
> }
>
> Is this supported and would it work?
>
> --
> Best Regards,
> Terence Monteiro
> ​,​
> www.sanjosesolutions.in
  

RE: Unable to start Apache Fineract in Netbeans.

[Markus Geiß]

Hey Alex,

this is not an issue. Java simply wasn't able to determine your desktop 
environment.

If you see this message, don't hit enter, this is simply the default shutdown 
hook to end the application. Your server is running correctly.

Cheers

Markus

From: alex.ch...@intrasofttechnologies.com
To: dev@fineract.incubator.apache.org
Subject: Unable to start Apache Fineract in Netbeans.
Date: Wed, 13 Apr 2016 10:10:58 +0300

Dear all, I have had issues starting the Fineract project in Netbeans. I was 
able to import the project and successfully build and run it. However I get a 
message in the log window, then after that the project stops running. Here is a 
part of the log message: “09:55:12.752 [main] INFO  
o.a.f.ServerWithMariaDB4jApplication - Started ServerWithMariaDB4jApplication 
in 110.876 seconds (JVM running for 112.215)09:55:12.801 [main] INFO  
o.a.f.ServerWithMariaDB4jApplication - Not going to open UI homepage in local 
web browser, because !Desktop.isDesktopSupported() Hit Enter to 
quit...09:55:12.814 [main] INFO  o.s.c.s.DefaultLifecycleProcessor - Stopping 
beans in phase 0 BUILD SUCCESSFUL Total time: 2 mins 2.96 secs” I do not know 
what is wrong or what the issue may be. My laptop is running Windows 10 and I 
have Chrome and Firefox installed. Thank you in advance for your cooperation. 
Regards,Alex 

RE: Upload Button for Pentaho reports

[Markus Geiß]

Hey Cole,

I like the idea of having a button for uploading reports. Saying this
Pentaho integration is not part of the Fineract distribution, it is an
add on provided by Mifos.

If we are to generalize this feature, using configuration to store the
path where to store reports in general, and provide an API to process
the upload, I'd be fine with this.

The UI implementation needs to be picked up by whom ever provides
a UI for Fineract.

Best,

Markus

.::YAGNI likes a DRY KISS::.

> From: cole.tru...@gmail.com
> Date: Fri, 8 Apr 2016 01:00:17 +
> Subject: Upload Button for Pentaho reports
> To: dev@fineract.incubator.apache.org
> 
> I have to manually SSH to the server and put Pentaho reports into the
> .mifosx/pentahoReports folder if I create a custom Pentaho report. Can
> there just be a simple upload button like a lot of other websites use? I
> wish it were as simple as this:
> 
> I would love to make this feature. Has anyone mentioned this before? What
> should I know before I try to make this feature?
> -- 
> Best,
> Cole Trumbo
> 435.773.1488 mobile
  

RE: GSOC 2016: Implement integration for UPI

[Markus Geiß]

Hey Wepngong,
hope this finds you well. ; o)
I've reviewed your proposal and added a little comment.
We are looking for a Java SDK for UPI that can be used by others too,and the 
integration of tis SDK within transactions as a connector.
Please update your Milestones and Timeline according to this. 

Best,

Markus

.::YAGNI likes a DRY KISS::.

> Date: Sun, 20 Mar 2016 14:57:38 +0100
> Subject: GSOC 2016: Implement integration for UPI
> From: bwepng...@gmail.com
> To: dev@fineract.incubator.apache.org
> 
> Hello fineract devs,
> I am Wepngong Ngeh Benaiah, pursuing my BEng at the University of Buea,
> Cameroon.
> I have browsed through fineract projects and will love to work on
> https://issues.apache.org/jira/browse/FINERACT-81.
> 
> I have drafted a proposal on https://summerofcode.withgoogle.com and will
> appreciate you could read and appraise it for me.
> 
> Thanks in advance.
> -- 
> 
> Buea,Cameroon
> University of Buea
> Faculty of Engineering and Technology
> Computer Engineering
> Software Engineering
> * Wepngong Ngeh Benaiah*
> 
> *https://github.com/bwepngong *
  

RE: [GitHub] incubator-fineract pull request: adding organisation start in glob...

[Markus Geiß]

Nope, looks good to me.
Best,

Markus

.::YAGNI likes a DRY KISS::.

> Subject: Re: [GitHub] incubator-fineract pull request: adding organisation 
> start in glob...
> From: j...@jagunet.com
> Date: Fri, 26 Feb 2016 13:21:03 -0500
> To: dev@fineract.incubator.apache.org
> 
> Anyone have issues w/ this?
> 
> > On Feb 26, 2016, at 3:34 AM, sachinkulkarni12  wrote:
> > 
> > GitHub user sachinkulkarni12 opened a pull request:
> > 
> >https://github.com/apache/incubator-fineract/pull/12
> > 
> >adding organisation start in global configuartion
> > 
> > 
> > 
> > You can merge this pull request into a Git repository by running:
> > 
> >$ git pull https://github.com/sachinkulkarni12/incubator-fineract CC-58
> > 
> > Alternatively you can review and apply these changes as the patch at:
> > 
> >https://github.com/apache/incubator-fineract/pull/12.patch
> > 
> > To close this pull request, make a commit to your master/trunk branch
> > with (at least) the following in the commit message:
> > 
> >This closes #12
> > 
> > 
> > commit 757da409f34dc63731f5c1321927f348ae31ba78
> > Author: sachinkulkarni12 
> > Date:   2016-02-26T08:30:46Z
> > 
> >adding organisation start in global configuartion
> > 
> > 
> > 
> > 
> > ---
> > If your project is set up for it, you can reply to this email and have your
> > reply appear on GitHub as well. If your project does not have this feature
> > enabled and wishes so, or if the feature is enabled but not working, please
> > contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> > with INFRA.
> > ---
> 
  

RE: Expression language to extend datatables

[Markus Geiß]

I was thinking about Drools (http://www.drools.org/). It is the largest and 
most used BRE for Java.
And it would fit the policies, it is licensed under Apache License v2.0.

Best,

Markus

.::YAGNI likes a DRY KISS::.

> From: sandervanderhey...@musoni.eu
> Date: Thu, 25 Feb 2016 12:52:07 +0100
> Subject: Re: Expression language to extend datatables
> To: dev@fineract.incubator.apache.org
> 
> Hi Markus,
> 
> Thanks for your input, would you have any specific business rule engines in
> mind?
> 
> One of the things we had in mind on that would be the same way we use the
> current templates and for instance the previews of loanschedules, where you
> can just get a preview of the result without having to store data straight
> away. This way (online) consumers can use it without re-implementing logic.
> 
> Sander
> 
> 
> 
> 
> Sander van der Heyden
> 
> CTO Musoni Services
> 
> 
> 
> 
> Mobile (NL): +31 (0)6 14239505
> Skype: s.vdheyden
> Website: musonisystem.com
> Follow us on Twitter!  <https://twitter.com/musonimfi>
> Postal address: Hillegomstraat 12-14, office 0.09, 1058 LS, Amsterdam,
> The Netherlands
> 
> On Thu, Feb 25, 2016 at 11:27 AM, Markus Geiß <markus.ge...@live.de> wrote:
> 
> > Hey,
> > hope this finds you well. ; o)
> > I think using a language specific expression language will force consumers
> > notusing Java for the client implementation to re-implement the logic.
> > Maybe an approach using a business rule engine, returning the name of
> > therule in the meta data and allow a call to the back end with the rule
> > name andthe entity/object reference to use, is a solution that broadens the
> > usage.
> > In this case the same logic to execute the rule can be used for ad hoc
> > andserver side adjustment.
> >
> > Best,
> >
> > Markus
> >
> > .::YAGNI likes a DRY KISS::.
> >
> > > From: sandervanderhey...@musoni.eu
> > > Date: Wed, 24 Feb 2016 16:19:41 +0100
> > > Subject: Re: Expression language to extend datatables
> > > To: dev@fineract.incubator.apache.org
> > >
> > > Hi Keith,
> > >
> > > Hope you are well?! Long time!!
> > >
> > > Ultimately the goal is to get the calculated data stored in the actual
> > > datatable so that it can be used in reports, custom loan checks etc. So
> > > therefore what I would expect to happen as an API consumer is:
> > > - When pulling the template API for a certain datatable the configured
> > > expression will come back as metadata (same way field types or
> > > mandatory/non-mandatory is given back). This would allow any consumer of
> > > that API to also implement the same expression library in (for instance)
> > a
> > > Web UI or (offline) Android app and give instant results in their UI.
> > > - When saving the backend will expect this field to be empty (not
> > > submitted) and will evaluate the expression.
> > > - Any time the record is updated the expression will be evaluated again.
> > > - Potentially adding an endpoint/ability to just get back the generated
> > > results for a table, without storing, to allow online consumers to work
> > > with the results without implementing the same expression lib.
> > >
> > > As there is already quite some work done around datatables by conflux and
> > > musoni in extending the features, adding metadata to it, this seems like
> > a
> > > logical next step, although we can also debate whether it might be a
> > point
> > > where the datatables would be 'forked' into a separate endpoint more
> > > focussed on user-forms.
> > >
> > > So from our end the datatable>rule relationship would mainly be that the
> > > datatable metadata contains a user-defined expression which can be
> > > maintained using the CRUD on the datatables endpoint itself and is stored
> > > in the metadata as a (tiny)text field.
> > >
> > > All in all, this would be extending datatables quite significantly and
> > > therefore I think it would be good to agree on the need for doing that as
> > > part of a 'fork' of the datatables endpoint into a separate 'user-forms'
> > > endpoint, also keeping in mind other requests we've got on this such as:
> > > - conditional fields (Field B is only required if Field A has a value)
> > > - field types such as GPS or a document upload
> > >
> > > And obviously this also comes with a sensible decision on which
> > expression
> > > library to use, and other idea

RE: [GitHub] incubator-fineract pull request: Connector changes from mysql to d...

[Markus Geiß]

Integration tests are part of our current work too and they need to run with a
JDBC driver ...

Aside from that I agree that we may can ommit a driver from our source release.

If this is the case could one of our mentors weigh in and let us know if it is
compliant with the license policies to use a non-compliant library in a test
environment. If this is the case, it would also fix our Hibernate issue, but 
prevent
us from releasing a binary/distribution.

Best,

Markus

.::YAGNI likes a DRY KISS::.

> Date: Mon, 8 Feb 2016 12:15:11 +
> Subject: Re: [GitHub] incubator-fineract pull request: Connector changes from 
> mysql to d...
> From: keithwoodl...@gmail.com
> To: dev@fineract.incubator.apache.org
> 
> Markus,
> 
> Yes - I still feel if you just ommited the connector from any release and
> updated installation instructions you wouldnt have to make any code changes
> or do any testing - Having the platform supported and tested agaisnt the
> Drizzle Driver isnt that useful I would of thought.
> 
> Keith.
> 
> On Mon, Feb 8, 2016 at 12:12 PM, Markus Geiß <markus.ge...@live.de> wrote:
> 
> > Good point!
> >
> > Let me create an issue ... we may face something similar with Hibernate.
> >
> > Best,
> >
> > Markus
> >
> > .::YAGNI likes a DRY KISS::.
> >
> > > Date: Mon, 8 Feb 2016 12:11:28 +
> > > Subject: Re: [GitHub] incubator-fineract pull request: Connector changes
> > from mysql to d...
> > > From: keithwoodl...@gmail.com
> > > To: dev@fineract.incubator.apache.org
> > >
> > > Markus,
> > >
> > > Yes Markus, you should be able to do that.
> > >
> > > I dont see an apache fineract issue (to watch) for this work but if you
> > let
> > > me know when its finished I'd be happy to give a go at going through the
> > > (production/test) installation instructions.
> > >
> > > Keith.
> > >
> > > On Mon, Feb 8, 2016 at 12:00 PM, Markus Geiß <markus.ge...@live.de>
> > wrote:
> > >
> > > > The whole Core Team including our QA and Support will do testing the
> > > > next few days to ensure all is working.
> > > >
> > > > I'm also not happy with it, given the huge test effort we have, but it
> > > > would always
> > > > be feasible to replace the default driver with anything you like to use
> > > > for your
> > > > 'distribution'. ; o)
> > > >
> > > > Best,
> > > >
> > > > Markus
> > > >
> > > > .::YAGNI likes a DRY KISS::.
> > > >
> > > > > Date: Mon, 8 Feb 2016 11:51:13 +
> > > > > Subject: Re: [GitHub] incubator-fineract pull request: Connector
> > changes
> > > > from mysql to d...
> > > > > From: keithwoodl...@gmail.com
> > > > > To: dev@fineract.incubator.apache.org
> > > > >
> > > > > Hi Markus,
> > > > >
> > > > > Thats pretty frustrating. Did you consider retaining mysql
> > connector/j
> > > > > driver to use for development / testing and excluding from release
> > > > > artifact. It would become one of the installation instructions to
> > > > download
> > > > > the driver then to use the software.
> > > > >
> > > > > I only say this because there might be alot of risk with using
> > Drizzle
> > > > JDBC
> > > > > Driver for use with MySQL. You will have to do extensive testing to
> > > > ensure
> > > > > it works out of the box in the same way as the mysql connector j one
> > > > (and I
> > > > > doubt it does) i.e. does it support all types of SQL queries queries
> > that
> > > > > use temp tables etc Is it even still under active development?
> > > > >
> > > > > Keith.
> > > > >
> > > > > On Mon, Feb 8, 2016 at 11:27 AM, Markus Geiß <markus.ge...@live.de>
> > > > wrote:
> > > > >
> > > > > > Hey Keith,
> > > > > >
> > > > > > the change was necessary to fulfill the license policies. Both
> > > > Connector/J
> > > > > > and
> > > > > > the Maria DB driver are licensed under LGPL 2.1 and are not
> > compatible
> > > > with
> > > > > > Apache's policies. Drizzle is one of the only fits.
> > > > > >
> > > > > > Best,
> > > > 

[DISCUSSION] How to deal with runtime dependencies

[Markus Geiß]

Hey all,

hope this finds you well.

I thought instead of discussing this on top of pull request, because it is more
than just the JDBC driver, it is the right time to create a new thread.

We are currently using MySQL's Connector/J and Hibernate's EntityManager at
runtime as the JDBC driver and JPA implementation. Our source code is not
depending on both.

It would create a huge effort to replace both for test and production 
environments.

The questions is:

Would it be compliant with the license policies if we omit them for our source
release, but keeping them for our own integration tests.

If somebody is creating a deployable distribution, the expectation is that 
whomever
is creating the distribution can decide what he wants to use.

Best,

Markus

.::YAGNI likes a DRY KISS::.  

How to trigger GitHub mirror

[Markus Geiß]

Hey all,
hope this finds you well. ; o)

I've pushed the initial code for Fineract to the Apache git repo at master and 
wandering
how I can trigger the GitHub mirror to reflect these changes.

Best,

Markus

.::YAGNI likes a DRY KISS::.  

RE: Initial code push

[Markus Geiß]

Hey Keith,
thanks for the links.

I won't push over all branches b/c it would also contain all releases that we 
already made and we will change the versioning scheme.

I will proceed with doing an initial push of one branch where all the clean up 
work has happened.

Best,

Markus

.::YAGNI likes a DRY KISS::.

> Date: Wed, 27 Jan 2016 14:58:44 +
> Subject: Re: Initial code push
> From: keithwoodl...@gmail.com
> To: dev@fineract.incubator.apache.org
> 
> Markus,
> 
> Assume you want you bring over the commit history with it also.
> 
> There is a question about what branches you want to bring over? do you want
> to bring them all or just a few special ones.
> 
> - Best apporach is probably to clone the repository in full locally and
> then push up to the new remote apache repository.
> 
> This writeup talks about doing all branches or specific ones depending on
> what  you want to do:
> 
> https://developer.atlassian.com/blog/2016/01/totw-copying-a-full-git-repo/
> 
> Keith.
> 
> On Wed, Jan 27, 2016 at 2:32 PM, Markus Geiß <markus.ge...@live.de> wrote:
> 
> > Hey all,
> >
> > hope this finds you well.
> >
> > Finally we are able to push the code over. How should we proceed with this?
> >
> > 1) Add an additional upstream to a local clone, pull the branch and merge
> > into master,
> > 2) Copy all files over manually and do a initial push,
> > 3) other ways?
> >
> > Best,
> >
> > Markus
> >
> > .::YAGNI likes a DRY KISS::.