Re: Testimonials for potential graduation announcement?

[Jim Jagielski]

Presently, I cannot comment on my 'at-work' usage, but would
be willing to do so with my asf hat on, if that would be useful.

> On Mar 14, 2017, at 4:23 PM, Myrle Krantz  wrote:
> 
> Hello Fineracters
> 
> We are currently starting the process of graduation from the incubator.
> For the announcement (whenever that may be), we'd like to include customer
> testimonials.  Would anyone here like to provide a customer testimonial?
> How have you used Fineract?  How has it contributed to your success? Has
> the Fineract community supported you well?
> 
> Thanks in advance,
> Myrle

Re: Please help evaluate Fineract's readiness for graduation

[Jim Jagielski]

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+Resolution
> 
> 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+Evaluation
> 
> 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 Apache Fineract website
>>>>> or the wiki?
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Ed
>>>>> 
>>>>> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski <j...@jagunet.com>
>> wrote:
>>>>> 
>>>>>> Agreed.
>>>>>> 
>>>>>

Re: [Fineract] Maturity Evaluation - Quality - PMD & Findbugs integration

[Jim Jagielski]

All good. +1
> On Feb 14, 2017, at 7:30 AM, Shaik Nazeer 
>  wrote:
> 
> Hi all,
> 
> 
> 
> We are planning to integrate 'PMD' and 'Findbugs' gradle plugins as part of
> Fineract build script(s) to maintain the code quality. I feel there
> shouldn't be any licensing issue as these two are used only while building
> the code and these jars will not be included in final war file. Please let
> me know your opinion on this.
> 
> 
> 
> Note: Initial setup will be done to ignore the failures as we need to spend
> some time resolve them. Once existing failures are resolved, we will enable
> to fail the build in case of any error.
> 
> 
> 
> Thanks,
> 
> Nazeer
> 

Re: Please help evaluation Fineract's readiness for graduation

[Jim Jagielski]

Makes sense.
> On Jan 25, 2017, at 10:52 PM, Shaik Nazeer 
> <nazeer.sh...@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." -*
>>>>> 
>>>>> 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 
>> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>> 
>> 
> 

Re: [VOTE] Release Apache Fineract 0.6.0 (incubating)

[Jim Jagielski]

+1. Thx!

> On Jan 12, 2017, at 7:36 AM, Nazeer Shaik  wrote:
> 
> Hi John,
> 
> We have closed the Jira issue
> https://issues.apache.org/jira/browse/FINERACT-357 and created two separate
> jira issues for remaining two items.RAT is integrated such a way it will
> check all directories and files from top level directory. So nothing will
> be missed.
> 
> Thanks,
> Nazeer
> 
> On Thu, Jan 12, 2017 at 5:34 PM, John D. Ament 
> wrote:
> 
>> On Thu, Jan 12, 2017 at 2:23 AM Nazeer Shaik 
>> wrote:
>> 
>>> Hi John,
>>> 
>>> Thank you for reviewing this release.
>>> 
>>> 1) I have kept https://issues.apache.org/jira/browse/FINERACT-357 open
>> as
>>> we have addressed 4 out of 6 suggestions given for 0.5.0-incubating
>>> release. Other two will be addressed in next/future releases. I have
>> added
>>> these details in note section of current release email.
>>> 
>> 
>> I would ask that you close the ticket w/ the completed tasks, and create a
>> new one with the remaining items.
>> 
>> I'm willing to change to a +1 if this occurs.
>> 
>> 
>>> 2) You need to follow the build instructions mentioned in the readme.md
>>> file to build from source. We have mentioned these details on every
>>> release.
>>> 
>> 
>> My struggle is that you have a build directory in one of the child dirs.
>> There is no top level build - as a result, there's no easy way to run rat
>> from the root.  This means that there are a number of files not easily
>> verified.
>> 
>> 
>>> 
>>> *Build & RAT verification steps can be found at:*
>>> 
>>> 
>>> https://github.com/apache/incubator-fineract/blob/0.6.0-
>> incubating/README.md
>>> or refer 'README.md' in *apache-fineract-0.6.0-incubating-src.tar.gz*
>>> 
>>> Please let us know if you are still not able to build after following
>> these
>>> steps.
>>> 
>>> Nazeer
>>> 
>>> On Thu, Jan 12, 2017 at 8:28 AM, John D. Ament 
>>> wrote:
>>> 
 Nazeer,
 
 Sorry but -1.  There was a ticket raised to address release issues in
>> the
 prior release vote.  The IPMC typically looks to see those release
>> issue
 tickets reolved in the following release.
 
 https://issues.apache.org/jira/browse/FINERACT-357 was not resolved in
 this
 release.
 
 Can you explain why not?
 
 I still struggle to figure out how to build fineract.  In fact, the
 build.sh script still does not work.
 
 John
 
 On Wed, Jan 11, 2017 at 3:46 AM Nazeer Shaik >> 
 wrote:
 
> Hello Incubator PMC,
> 
> 
> 
> The Apache Fineract community has voted and approved the proposal to
> release Apache Fineract 0.6.0 (incubating). We now kindly request the
> Incubator *PMC* members review and vote on this incubator release.
> 
> 
> 
> Apache Fineract is an open source system for core banking as a
>>> platform.
> Fineract provides a reliable, robust, and affordable solution for
> entrepreneurs, financial institutions, and service providers to offer
> financial services to the world’s 2 billion under banked and
>> unbanked.
 More
> information can be found at http://fineract.incubator.apache.org/
> 
> 
> 
> The Apache Fineract-0.6.0-incubating release candidate is now
>> available
> with the following artifacts for a project vote:
> 
> 
> 
> *[VOTE] Thread:*
> 
> 
> http://mail-archives.apache.org/mod_mbox/incubator-
 fineract-dev/201701.mbox/%3CCAOSe2ysBL1pS6YMSbSHS-
 BT1PPb29K-ZuGqYBd2igepQSFMm%2Bg%40mail.gmail.com%3E
> 
> 
> 
> *[VOTE RESULT] Thread:*
> 
> 
> 
> http://mail-archives.apache.org/mod_mbox/incubator-
 fineract-dev/201701.mbox/%3CCAOSe2yuvdNRkt1cAbGQcEwdWVgT
 panz7kS5fAQUsnsZZWrRhCw%40mail.gmail.com%3E
> 
> 
> 
> *The release candidate(s) to be voted on is available at:*
> 
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
 6.0-incubating/
> 
> 
> 
> *Git tag for the release:*
> 
> https://github.com/apache/incubator-fineract/tree/0.6.0-incubating
> 
> or
> 
> 
> https://git-wip-us.apache.org/repos/asf?p=incubator-
 fineract.git;a=shortlog;h=refs/heads/0.6.0-incubating
> 
> 
> 
> *Source release verification:*
> 
> 
> 
> Source release candidate:
> 
> 
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
 6.0-incubating/apache-fineract-0.6.0-incubating-src.tar.gz
> 
> 
> 
> PGP signature:
> 
> 
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
 6.0-incubating/apache-fineract-0.6.0-incubating-src.tar.gz.asc
> 
> 
> 
> MD5/SHA Hash:
> 
> 
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
 

Re: [Apache Fineract] Steps for release signing

[Jim Jagielski]

Cool.

Some projects also use bz2 in addition to gz or even instead
of.

> On Jan 12, 2017, at 7:40 AM, Nazeer Shaik 
>  wrote:
> 
> Hi all,
> We have documented steps for signing Apache Fineract releases. Please find
> the document location
> https://cwiki.apache.org/confluence/display/FINERACT/Release+Sign
> 
> Thanks,
> Nazeer
> 
> *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 unauthorized 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.

Re: Please help evaluation Fineract's readiness for graduation

[Jim Jagielski]

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.

Re: [VOTE] [APACHE FINERACT] 0.6.0-incubating for release

[Jim Jagielski]

+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-license.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  file. *
>> 
>> 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)
>> 
>> 
>> *Here is my +1 (non-binding)*
>> 
>> 
>> 
>> Thanks,
>> 
>> Nazeer
>> 
>> 

Re: [VOTE] Release Apache Fineract 0.5.0 (incubating)

[Jim Jagielski]

Yeah, I just wanted it on the record :)
> On Dec 22, 2016, at 7:56 AM, Nazeer Shaik 
> <nazeer.sh...@confluxtechnologies.com> wrote:
> 
> Thank you Jim for reviewing and up voting the release.
> FYI: The release is already announced :-)
> 
> Thanks,
> Nazeer
> 
> Thanks,
> Nazeer
> 
> *Principal Architect, **Conflux Technologies Pvt Ltd
> <http://www.confluxtechnologies.com/>*
> 
> *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 unauthorized review, use, disclosure, dissemination,
> forwarding, printing or copying of this email or any action taken in
> reliance on this e-mail is strictly prohibited and is unlawful. The
> recipient acknowledges that Conflux Technologies Private Limited or its
> subsidiaries and associated companies are unable to exercise control or
> ensure or guarantee the integrity of/over the contents of the information
> contained in e-mail transmissions. Before opening any attachments, please
> check.
> 
> On Thu, Dec 22, 2016 at 6:02 PM, Jim Jagielski <j...@jagunet.com> wrote:
> 
>> +1 (binding)
>>> On Dec 19, 2016, at 3:33 AM, Nazeer Shaik <nazeer1100...@apache.org>
>> wrote:
>>> 
>>> Hi all,
>>> 
>>> We are extending voting time for another 48 hrs as we didn't get any
>>> response. Request you to review and vote for this release.
>>> 
>>> Thanks,
>>> Nazeer
>>> 
>>> On Tue, Dec 13, 2016 at 12:55 PM, Nazeer Shaik <nazeer1100...@apache.org
>>> 
>>> wrote:
>>> 
>>>> Hello Incubator PMC,
>>>> 
>>>> 
>>>> 
>>>> The Apache Fineract community has voted and approved the proposal to
>>>> release Apache Fineract 0.5.0 (incubating).
>>>> 
>>>> We now kindly request the Incubator PMC members review and vote on this
>>>> incubator release.
>>>> 
>>>> 
>>>> 
>>>> Apache Fineract is an open source system for core banking as a platform.
>>>> Fineract provides a reliable, robust, and affordable solution for
>>>> entrepreneurs, financial institutions, and service providers to offer
>>>> financial services to the world’s 2 billion under banked and unbanked.
>> More
>>>> information can be found at http://fineract.incubator.apache.org/
>>>> 
>>>> 
>>>> 
>>>> The Apache Fineract-0.5.0-incubating release candidate is now available
>>>> with the following artifacts for a project vote:
>>>> 
>>>> 
>>>> 
>>>> [VOTE] Thread:
>>>> 
>>>> http://mail-archives.apache.org/mod_mbox/incubator-
>>>> fineract-dev/201612.mbox/%3CCAOSe2ytMt6J5kk_6pBev1%2ByNSEj8q6%
>>>> 2BOKxVKPwhtAKe9J3MRAw%40mail.gmail.com%3E
>>>> 
>>>> 
>>>> 
>>>> [VOTE RESULT] Thread:
>>>> 
>>>> https://lists.apache.org/thread.html/81463c5e980d5d052003edf358b01d
>>>> b5894f7d300f06795a1270ea6a@%3Cdev.fineract.apache.org%3E
>>>> 
>>>> 
>>>> 
>>>> The release candidate(s) to be voted on is available at:
>>>> 
>>>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>>>> 5.0-incubating/
>>>> 
>>>> 
>>>> 
>>>> Git tag for the release:
>>>> 
>>>> https://github.com/apache/incubator-fineract/tree/0.5.0-incubating
>>>> 
>>>> or
>>>> 
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-
>>>> fineract.git;a=shortlog;h=refs/heads/0.5.0-incubating
>>>> 
>>>> 
>>>> 
>>>> Source release verification:
>>>> 
>>>> 
>>>> 
>>>> Source release candidate:
>>>> 
>>>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>>>> 5.0-incubating/apache-fineract-0.5.0-incubating-src.tar.gz
>>>> 
>>>> 
>>>> 
>>>> PGP signature:
>>>> 
>>>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>

Re: [VOTE] Release Apache Fineract 0.5.0 (incubating)

[Jim Jagielski]

+1 (binding)
> On Dec 19, 2016, at 3:33 AM, Nazeer Shaik  wrote:
> 
> Hi all,
> 
> We are extending voting time for another 48 hrs as we didn't get any
> response. Request you to review and vote for this release.
> 
> Thanks,
> Nazeer
> 
> On Tue, Dec 13, 2016 at 12:55 PM, Nazeer Shaik 
> wrote:
> 
>> Hello Incubator PMC,
>> 
>> 
>> 
>> The Apache Fineract community has voted and approved the proposal to
>> release Apache Fineract 0.5.0 (incubating).
>> 
>> We now kindly request the Incubator PMC members review and vote on this
>> incubator release.
>> 
>> 
>> 
>> Apache Fineract is an open source system for core banking as a platform.
>> Fineract provides a reliable, robust, and affordable solution for
>> entrepreneurs, financial institutions, and service providers to offer
>> financial services to the world’s 2 billion under banked and unbanked. More
>> information can be found at http://fineract.incubator.apache.org/
>> 
>> 
>> 
>> The Apache Fineract-0.5.0-incubating release candidate is now available
>> with the following artifacts for a project vote:
>> 
>> 
>> 
>> [VOTE] Thread:
>> 
>> http://mail-archives.apache.org/mod_mbox/incubator-
>> fineract-dev/201612.mbox/%3CCAOSe2ytMt6J5kk_6pBev1%2ByNSEj8q6%
>> 2BOKxVKPwhtAKe9J3MRAw%40mail.gmail.com%3E
>> 
>> 
>> 
>> [VOTE RESULT] Thread:
>> 
>> https://lists.apache.org/thread.html/81463c5e980d5d052003edf358b01d
>> b5894f7d300f06795a1270ea6a@%3Cdev.fineract.apache.org%3E
>> 
>> 
>> 
>> The release candidate(s) to be voted on is available at:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 5.0-incubating/
>> 
>> 
>> 
>> Git tag for the release:
>> 
>> https://github.com/apache/incubator-fineract/tree/0.5.0-incubating
>> 
>> or
>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-
>> fineract.git;a=shortlog;h=refs/heads/0.5.0-incubating
>> 
>> 
>> 
>> Source release verification:
>> 
>> 
>> 
>> Source release candidate:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 5.0-incubating/apache-fineract-0.5.0-incubating-src.tar.gz
>> 
>> 
>> 
>> PGP signature:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 5.0-incubating/apache-fineract-0.5.0-incubating-src.tar.gz.asc
>> 
>> 
>> 
>> MD5/SHA Hash:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 5.0-incubating/apache-fineract-0.5.0-incubating-src.tar.gz.md5
>> 
>> 
>> 
>> Binary release verification:
>> 
>> 
>> 
>> Binary release candidate:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 5.0-incubating/apache-fineract-0.5.0-incubating.tar.gz
>> 
>> 
>> 
>> PGP signature:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 5.0-incubating/apache-fineract-0.5.0-incubating.tar.gz.asc
>> 
>> 
>> 
>> MD5/SHA Hash:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.
>> 5.0-incubating/apache-fineract-0.5.0-incubating.tar.gz.md5
>> 
>> 
>> 
>> Keys to verify the signature of the release artifacts are available at:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/KEYS
>> 
>> 
>> 
>> Release Notes:
>> 
>> https://cwiki.apache.org/confluence/display/FINERACT/0.
>> 5.0-incubating+Release-+Apache+Fineract
>> 
>> 
>> 
>> Build verification steps can be found at:
>> 
>> https://github.com/apache/incubator-fineract/blob/0.5.0-
>> incubating/README.md
>> 
>> or 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
>> 
>> 
>> 
>> Note:
>> 
>>   - This release contains both source and binary artifacts.
>>   - We have included two license sections for bundled items of source
>>   and binary artifacts in same License and Notice file(s)
>> 
>> 
>> 
>> The vote will be open for at least 72 hours or until necessary number of
>> votes are reached. Members please be sure to indicate "(Binding)" with your
>> vote which will help in tallying the vote(s).
>> 
>> 
>> 
>> [ ] +1  approve
>> 
>> [ ] +0  no opinion
>> 
>> [ ] -1  disapprove (and reason why)
>> 
>> 
>> 
>> Here is my +1 (non-binding)
>> 
>> Thanks,
>> 
>> Nazeer
>> 

Re: [VOTE] Release Apache Fineract 0.5.0 (incubating)

[Jim Jagielski]

> On Dec 19, 2016, at 8:46 PM, John D. Ament  wrote:
> 
> Hi,
> 
> So to point out, release vote threads are open *at least* 72 hours.  There
> is no reason to add an extra 48 hours to the vote, it'll close when it
> passes

That's not quite 100% true... The vote doesn't "auto-close" once
the required number of +1s are cast, because you never know if
someone will cast a -1 (not a veto) due to some issue.

Re: [Apache Fineract] - License & Notice files for source and binary releases

[Jim Jagielski]

They look fine... I would have prefered a 80col limit
on the text though, to make it easier for humans to read.

> On Dec 6, 2016, at 12:29 AM, Nazeer Shaik 
>  wrote:
> 
> Hi Fineract Mentors,
> 
> We are planning to release Apache Fineract 0.5.0-incubating with source &
> binary artifacts. I need clarification on preparing license and notice
> files. Can we include two license sections for bundled items of source and
> binary distributions in same License and Notice file or do we need to have
> separate files?
> 
> Combined License & Notice files:
> 
> https://github.com/apache/incubator-fineract/blob/develop/LICENSE
> https://github.com/apache/incubator-fineract/blob/develop/NOTICE
> 
> 
> Thanks,
> Nazeer
> 
> *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 unauthorized 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.

JIRA vs. Email lists

[Jim Jagielski]

There have been a few discussions which have taken place on
JIRA when, ideally, they should have take place here on
the dev@ list.

I'd like to see us focus on using JIRA less as a communications
tool and try to get more discussion and conversation
here on-list.

Re: [MENTORS] Managing non-Apache code from ASF resources?

[Jim Jagielski]

> On Nov 28, 2016, at 7:54 PM, Roman Shaposhnik  wrote:
> 
> On Tue, Nov 22, 2016 at 4:53 AM, Myrle Krantz  wrote:
>> Hi Mentors,
>> 
>> As you know Apache Fineract has a UI project which Mifos did not donate to
>> the ASF because it's not licensable in the way the ASF requires.  This has
>> been a major communication challenge.  We've split the communication across
>> two lists, even though newbies don't understand the difference between the
>> UI and the backend code, and even though many discussions impact both.
>> 
>> At the ApacheCon I was asked if we have any volunteer opportunites for
>> non-techies.  Mifos does, and among those are translations or documentation
>> which are definitely more prevalent in the UI.
>> 
>> So here's the question (s): Is there any objection to us creating tickets
>> for non-Apache code in the Apache's Jira, or moving documentation of the UI
>> to Apache's Confluence? Is there any reason we should be careful about
>> having discussions about the UI on the Apache mailing list?
>> 
>> Because if we could move these kinds of communications into one channel,
>> instead of the two it currently is split between, it might help alleviate
>> some of the confusion...
> 
> Since what gets developed at ASF is basically the engine -- I'd assume that
> multiple different UIs would be possible. Hence it seems to me that a more
> natural relationship would be the other way around: folks working on Mifos
> point at ASF JIRA, etc. Btw, does Mifos have a publicly available, developer
> friendly tracker and wiki infrastructure?

+1

Re: Fineract Board Report for November

[Jim Jagielski]

Sounds like a plan to me :)

> On Oct 30, 2016, at 7:30 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> 
> On Thu, Oct 27, 2016 at 10:27 AM, Jim Jagielski <j...@jagunet.com> wrote:
>> Thx for the report!
>> 
>> I would like to raise the possibility of calling for Graduation
>> of Fineract. What does everyone think?
> 
> Personally I think having one more clean release would make me feel
> more comfortable about casting a +1 graduation vote. Also, sine I remember
> this community wanted to produce binary convenience artifacts at some
> point, I'd like to see that happen first.
> 
> All in all: -0.
> 
> Thanks,
> Roman.

Re: Fineract Board Report for November

[Jim Jagielski]

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
> *
> 
> 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

[Jim Jagielski]

+1

Re: Microservices release question

[Jim Jagielski]

++1

> On May 31, 2016, at 1:21 AM, Adi Raju  
> wrote:
> 
> I would expect there would be X number of microservices which are core/heart 
> of the application which no deployment can do away with. I would suggest 
> these to be released as a single package/release.
> 
> All other microservices should be optional based on the deployment/end user 
> requirements. They can be released individually by mentioning the minimum 
> core dependency version.
> 
> This suggestion would mean multiple projects under apache fineract, but I 
> feel this is where we are heading by keeping separate repo for each 
> microservice.
> 
> Regards,
> Adi
> 
> -Original Message-
> From: Myrle Krantz [mailto:mkra...@mifos.org] 
> Sent: 30 May 2016 23:43
> To: dev@fineract.incubator.apache.org
> Subject: Re: Microservices release question
> 
> We should create a docker image and host it on docker hub for small 
> organisations.  These users would install docker, and run a single command to 
> start the system.  They wouldn't even have to download our compiled source 
> directly; docker does that for you.  We would need to figure out how to make 
> installing a valid certificate for their domain in their docker image easy.
> 
> The answer to that question for larger organisations who want to take 
> advantage of the scalability that microservices offer, particularly ones 
> which wish to adjust the code before deploying it in their environments, will 
> depend on how we answer the question I started this thread with.
> 
> Greets,
> Myrle
> 
> 
> *Myrle Krantz*
> Solutions Architect
> RɅĐɅЯ, The Mifos Initiative
> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org 
>   
> 
> 
> On Mon, May 30, 2016 at 6:46 PM, Ashok 
> wrote:
> 
>> Hi Myrle,
>> 
>> Release process looks very interesting and same time highly confusing, 
>> I am wondering how small organisations or independent implementors 
>> will understand this process to carry out their implementations 
>> without much hurdles.
>> 
>> Regards,
>> Ashok
>> 
>> On Mon, 30 May 2016 at 7:57 PM, Myrle Krantz  wrote:
>> 
>>> Hi Fineract,
>>> 
>>> I'm starting a new thread for a question which Roman asked in the
>> multiple
>>> repos thread.  He asked how we'd like to release if we are dividing 
>>> our code into microservices.  Assuming we want to do clockwork 
>>> releases,
>> there
>>> are three major alternatives:
>>> 
>>> 1.) Release each microservice version separately, on its own 
>>> schedule,
>>> 2.) Release a set of microservices as one release which are 
>>> compatible
>> with
>>> each other, taking the newest service version from the leafs of the 
>>> dependency tree, or
>>> 3.) Release a set of microservice versions as one release which are 
>>> compatible with each other, taking the newest service from the root 
>>> of
>> the
>>> dependency tree.
>>> 
>>> 
>>> 2 and 3 probably require a bit more background to understand:
>>> Microservices will be dependent on each other.  For example all 
>>> services will depend on the tenant provisioning service, and on the 
>>> service for managing users and permissions.
>>> 
>>> So let's say you have services A, B, and C in multiple versions 
>>> which depend on each other like this:
>>> 
>>> Av1 -> {} (no dependencies)
>>> Av2 -> {}
>>> Av3 -> {}
>>> Av4 -> {}
>>> 
>>> Bv1 -> Av1
>>> Bv2 -> oneOf(Av1, Av2)
>>> Bv3 -> oneOf(Av2, Av3)
>>> Bv4 -> oneOf(Av3, Av4)
>>> 
>>> Service C: depends on B
>>> Cv1 -> Bv1
>>> Cv2 -> oneOf(Bv1, Bv2)
>>> 
>>> In solution one, we'd release a new version of A as soon as it was 
>>> complete, even if none of the other services were updated and still 
>>> required older versions of A.
>>> 
>>> In solution two, we'd release a source code tar ball containing Cv2, 
>>> Bv2, and Av2.  Even though Av3 and Av4 exists we wouldn't include it 
>>> in a release until all services were updated to be compatible with it.
>>> 
>>> In solution three we'd release a source code tar ball containing 
>>> Av4, and Bv4.  We wouldn't include any version of C because there 
>>> would be none which is transitively compatible with the latest 
>>> version of A. If C is a service which not everyone deploys, this may be 
>>> acceptable.
>>> 
>>> What do you guys think?  Keep in mind that in Apache the release is 
>>> a source code release. It's signed and it should include all the 
>>> source code...
>>> 
>>> Greets,
>>> Myrle
>>> 
>>> 
>>> 
>>> *Myrle Krantz*
>>> Solutions Architect
>>> RɅĐɅЯ, The Mifos Initiative
>>> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org 
>>>   
>>> 
>> --
>> Regards,
>> Ashok
>> 
>> Sent from mobile device
>> 
> 

Re: [VOTE] [FINERACT] 0.1.1-incubating for release

[Jim Jagielski]

Would it make sense to consider using tar instead of zip ??


> On May 6, 2016, at 1:49 AM, Nazeer Shaik 
> <nazeer.sh...@confluxtechnologies.com> wrote:
> 
> Hi all,
> 
> You are seeing the mentioned issues because we have prepared the release on
> windows machine. But we don't see any issues if we prepare same release on
> Linux machine. Even the mentioned test case passes without any code change.
> 
> *So we are withdrawing the current release from voting.*
> 
> We will work on 0.1.2-incubating release.
> 
> Thanks,
> Nazeer
> 
> 
> On Wed, May 4, 2016 at 5:26 PM, Jim Jagielski <j...@jagunet.com> wrote:
> 
>> Same on OSX. During the unzip the EOL chars are not translated
>> to native. According to zipinfo, text files lack the 't'
>> flag but are, instead, 'bx'
>> 
>> eg:
>> 
>> -rw-a-- 3.1 fat 1642 bx defN  2-May-16 18:03
>> apache-fineract-0.1.1-incubating-src/licenses/jQuery.txt
>> -rw-a-- 3.1 fat34388 bx defN  2-May-16 18:03
>> apache-fineract-0.1.1-incubating-src/licenses/jszip.txt
>> -rw-a-- 3.1 fat 1065 bx defN  2-May-16 18:03
>> apache-fineract-0.1.1-incubating-src/licenses/modernizr.txt
>> -rw-a-- 3.1 fat 1116 bx defN  2-May-16 18:03
>> apache-fineract-0.1.1-incubating-src/licenses/normalize.txt
>> 
>>> On May 4, 2016, at 6:02 AM, Myrle Krantz <mkra...@mifos.org> wrote:
>>> 
>>> -1
>>> 
>>> I checked the license and notifications.  They look good to me, so I
>> tried
>>> to build:
>>> 
>>> I'm building on ubuntu, and the instruction wouldn't work for me because
>>> gradlew has windows line feeds.
>>> 
>>> Going around that by calling gradle directly I can build with "clean
>> war",
>>> but if I call just "gradle build" I get a build failure because of a unit
>>> test failure.
>>> 
>>> I know that unit test has been failing for a very long time.  If it's not
>>> important we need to disable it, so that it doesn't distract from
>> important
>>> problems.  If it is important than we need to fix it before we release.
>>> 
>>> To get my +1, we need to fix gradlew so that it can build on linux
>> machines
>>> and we need to have all of our unit tests green.
>>> 
>>> Greets from the Voreifel, Germany,
>>> 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, May 4, 2016 at 5:02 AM, Nayan Ambali <nayan.amb...@gmail.com>
>> wrote:
>>> 
>>>> +1
>>>> 
>>>> On Wed, May 4, 2016, 12:43 AM Ed Cable <edca...@mifos.org> wrote:
>>>> 
>>>>> +1
>>>>> On May 3, 2016 4:09 AM, "Nazeer Shaik" <
>>>>> nazeer.sh...@confluxtechnologies.com>
>>>>> wrote:
>>>>> 
>>>>>> Hello All
>>>>>> 
>>>>>> We have addressed issues with Notice & License files and prepared
>>>>>> 0.1.1-incubating release for FINERACT.
>>>>>> The files are hosted at
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.1-incubating/
>>>>>> 
>>>>>> This is a source only release with no binaries, with instructions on
>>>> how
>>>>> to
>>>>>> build/test the application.
>>>>>> 
>>>>>> We couldn't migrate to Open JPA to avoid dependency on
>>>>> Hibernate(LGPLv2.1).
>>>>>> We are referring Hibernate Entity Manager, MySQLDialect,
>>>>>> annotations(LazyCollection, LazyCollectionOption)
>>>>>> at run time only and it doesn't include any source or binary from
>>>>>> Hibernate. We know that we have to get Legal VP approval on the same
>>>> and
>>>>> a
>>>>>> separate mail thread will be initiated.
>>>>>> 
>>>>>> I call for VOTING for this release and this voting closes by Friday
>>>>>> (06-May-2015).
>>>>>> 
>>>>>> Thanks,
>>>>>> Nazeer
>>>>>> 
>>>>> 
>>>> 
>> 
>> 

Re: Jim Jagielski: Will you be our mentor?

[Jim Jagielski]

I am afraid that by accepting I would be "agreeing" to the statement
that a "mistake" was made in my original offer to be a mentor ;)

It would be my extreme pleasure to accept with that caveat

> On May 5, 2016, at 2:08 AM, Myrle Krantz  wrote:
> 
> Dear Jim,
> 
> We made a mistake when we declined your offer to become our mentor.  Then as 
> now you are a qualified and experienced member of Apache.  You've remained 
> engaged with the Fineract project despite our initial decline of your offer, 
> and you continue to offer valuable insights.  Will you allow us to correct 
> our mistake and invite you formally to become a mentor for Fineract now?
> 
> Happy Father's Day from Germany,
> Myrle
> 
> 
> 
> Myrle Krantz
> Solutions Architect
> RɅĐɅЯ, The Mifos Initiative
> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org  
> 
> 

ramping up

[Jim Jagielski]

As people may recall, I offered to mentor fineract but we had
sufficient mentors. I am starting to ramp up my actual dev
involvement in anticipation of getting commit. Suggestions
and focus areas welcomed.