Fwd: Slack Invites

[Myrle Krantz]

Hi Fineract development,

John has registered the ASF for a Slack organization.  In case any of
you would like to discuss Fineract via Slack, I've created a Fineract
channel there for us:
https://the-asf.slack.com/messages/C4QPZURQQ/details/

I'm aware that this is YAM (yet another messenger), so consider this
an offer for those who would prefer to interact via Slack over the
other messengers.  Final decision-making should never occur via a
messenger anyways. so if some people are using Slack and others are
using Gitter, Skype, HipChat, Olark, Secos, Google Hangouts,
GoToMeeting, WebEx, Zoho, Facebook Messenger, Whatsapp, LinkedIn
Messenger, Apple Facetime, smoke signals, Xing messenger, Twitter,
or... WhatsEver I don't see a problem.

Greets,
Myrle


-- Forwarded message --
From: John D. Ament 
Date: Wed, Mar 29, 2017 at 3:54 PM
Subject: Slack Invites
To: "gene...@incubator.apache.org" 


All,

Based on the on-going discussions, I decided to move ahead with a single
organization for Slack.  I've opened up registrations to all @apache.org
email addresses.  To get set up, please use https://the-asf.slack.com/signup to
get your account up and running.

Happy Slacking!

John

Re: Google Summer of Code 2017 Mentor Registration

[Myrle Krantz]

Hey Markus, Maek, and Ed,

I'll start in the process for getting Markus and Maek mentor-status.
Here are a couple of potential problems:

* I'm not sure that the tickets y'all want to mentor for exist and are
labeled.  As of this writing, a search for the labels "gsoc" and
"gsoc2017" [1] only reveals three appropriately labeled tickets.  None
of them look very promising. Ed I believe you have specific tickets in
mind.  Could you please make sure they're entered and labeled?
* Maek in particular may have problems because as I understand it you
must be a committer to mentor.

Greets,
Myrle

[1] 
https://issues.apache.org/jira/browse/FINERACT-419?jql=project%20%3D%20FINERACT%20AND%20labels%20in%20(gsoc%2C%20gsoc2017)


On Sat, Mar 25, 2017 at 10:11 AM, Maek Twain  wrote:
> Hi all I would like to mentor for ASF 2017
>
> Sent from my iPhone
>
>> On 25-Mar-2017, at 1:39 PM, Markus Geiß  wrote:
>>
>> Hey Myrle,
>>
>> sorry for the late reply.
>>
>> I'm willing to mentor a student during GSOC this year.
>>
>> Cheers
>>
>> Markus
>>
>> -Original Message-
>> From: Myrle Krantz [mailto:my...@apache.org]
>> Sent: Tuesday, March 7, 2017 09:44 AM
>> To: dev@fineract.incubator.apache.org
>> Subject: Fwd: Google Summer of Code 2017 Mentor Registration
>>
>> Hi Finerators,
>>
>> Who is interested in mentoring for Google Summer of Code 2017?  Do we have 
>> JIRA tickets you want to mentor for?  If I can get at least one of each 
>> (mentor + ticket), I'll register Fineract for GSOC, and acknowledge your 
>> mentoring request.  Tag tickets you think are suitable with "gsoc2017" or 
>> "gsoc".
>>
>> My question is specifically for Fineract mentors and tickets.  Projects and 
>> tickets to produce code outside of Apache repos would run under Mifos 
>> participation in GSOC and not Apache's.  Code in "https://github.com/openMF/";
>> is Mifos code.
>>
>> Greets,
>> Myrle
>>
>> -- Forwarded message --
>> From: Ulrich Stärk 
>> Date: Mon, Mar 6, 2017 at 8:39 PM
>> Subject: Google Summer of Code 2017 Mentor Registration
>> To: ment...@community.apache.org
>> Cc: "d...@community.apache.org" 
>>
>>
>> Dear PMCs,
>>
>> I'm happy to announce that the ASF has made it onto the list of accepted 
>> organizations for Google Summer of Code 2017! [1,2]
>>
>> It is now time for mentors to sign up, so please pass this email on to your 
>> community and podlings. If you aren’t already subscribed to 
>> ment...@community.apache.org you should do so now else you might miss 
>> important information.
>>
>> Mentor signup requires two steps: mentor signup in Google's system [3] and 
>> PMC acknowledgement.
>>
>> If you want to mentor a project in this year's SoC you will have to
>>
>> 1. Be an Apache committer.
>> 2. Request an acknowledgement from the PMC for which you want to mentor 
>> projects. Use the below template and *do not forget to copy 
>> ment...@community.apache.org*. We will use the email adress you indicate to 
>> send the invite to be a mentor for Apache.
>>
>> PMCs, read carefully please.
>>
>> We request that each mentor is acknowledged by a PMC member. This is to 
>> ensure the mentor is in good standing with the community. When you receive a 
>> request for acknowledgement, please ACK it and cc 
>> ment...@community.apache.org
>>
>> Lastly, it is not yet too late to record your ideas in Jira (see my previous 
>> emails for details).
>> Students will now begin to explore ideas so if you haven’t already done so, 
>> record your ideas immediately!
>>
>> Cheers,
>>
>> Uli
>>
>> mentor request email template:
>> 
>> to: private@.apache.org
>> cc: ment...@community.apache.org
>> subject: GSoC 2017 mentor request for 
>>
>>  PMC,
>>
>> please acknowledge my request to become a mentor for Google Summer of Code
>> 2017 projects for Apache
>> .
>>
>> I would like to receive the mentor invite to 
>>
>> 
>>
>> 
>>
>> [1] https://summerofcode.withgoogle.com/organizations/
>> [2] https://summerofcode.withgoogle.com/organizations/5416945173135360/
>> [3] https://summerofcode.withgoogle.com/
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org

[RESULT] [VOTE] Apache Fineract podling graduation

[Myrle Krantz]

Hello Incubator,

The vote to graduate Apache Fineract from the incubator passes with 8
binding votes,  2 non-binding votes, and no down-votes

+1 binding: John D. Ament, Daniel Gruno, Bertrand Delacretaz, Roman
Shaposhnik, Niclas Hedhman, Jim Jagielski, Justin Mclean, Tom Barber
+1 non-binding: Pierre Smits, Markus Geiß

(+1 binding votes not carried over from the pre-proposal-correction
vote thread: Jean-Baptiste Onofré, Ross Gardler)

We at Apache Fineract deeply appreciate the expressions of good will
that came together with your votes.

Thank you,
Myrle


On Wed, Mar 22, 2017 at 3:11 PM, Myrle Krantz  wrote:
> Greetings Incubator,
>
> I propose that we graduate Apache Fineract from the Incubator.  The
> full text of the proposal is below.
>
> This is a restarted VOTE thread to correct an error in the resolution
> from the original thread. Here's the previous VOTE thread:
>
> [https://lists.apache.org/thread.html/1cbc738bbb4083e50b7772d5226b88d3fe321b91451303a69dbc4fa8@%3Cgeneral.incubator.apache.org%3E]
>
> And here's the DISCUSS thread:
>
> [https://lists.apache.org/thread.html/630d3ec22b4f72f827cd817a0a4da5c3c52dee4f96f47a1369f5dc50@%3Cgeneral.incubator.apache.org%3E]
>
>
> Thank you,
> Myrle Krantz
>
>
> Resolution:
>
> Establish the Apache Fineract Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to a core banking platform that provides a reliable,
> robust, and affordable solution for entrepreneurs, financial
> institutions, and service providers to offer financial
> services to the world's underbanked and unbanked.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Fineract Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Fineract Project be and hereby is
> responsible for the creation and maintenance of software
> related to a core banking platform that provides a reliable,
> robust, and affordable solution for entrepreneurs, financial
> institutions, and service providers to offer financial
> services to the world's underbanked and unbanked.
>
> RESOLVED, that the office of "Vice President, Apache Fineract" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Fineract Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Fineract Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Fineract Project:
>
> * Vishwas Babu AJ 
> * Edward Cable 
> * Markus Geiss 
> * Sander van der Heijden 
> * Ishan Khanna 
> * Myrle Krantz 
> * Terence Monteiro 
> * Adi Nayaran Raju 
> * Gaurav Saini 
> * Nazeer Hussain Shaik 
> * Jim Jagielski 
> * Michael Vorburger 
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Myrle Krantz
> be appointed to the office of Vice President, Apache Fineract, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Fineract PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Fineract Project; and be it further
>
> RESOLVED, that the Apache Fineract Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Fineract podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Fineract podling encumbered upon the Apache Incubator
> Project are hereafter discharged.

Re: Testimonials for potential graduation announcement?

[Myrle Krantz]

Hey Jim,

That'd be much appreciated.  We still need user testimonials though.
Anybody?  If you don't respond I'm going to start pinging people directly.
; o)

Greets,
Myrle


On Fri, Mar 17, 2017 at 3:38 PM, Jim Jagielski  wrote:

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

Testimonials for potential graduation announcement?

[Myrle Krantz]

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: [DISCUSS] Graduation

[Myrle Krantz]

Hi everyone,

It has taken longer than expected because I wanted to get our two newest
committers in on the proposal, but I have launched our graduation proposal
into the incubator.  There will be a discussion period.  Assuming the
discussion goes well, I will wait for it to settle down, and then call the
vote in the incubator.  Should we pass the vote, the proposal will be
submitted by the incubator to the Apache Software Foundation board at their
next meeting in April.  If the board accepts our proposal, Fineract will
become a top level project at Apache.

I am very optimistic that this process will end in success, and I'm looking
forward to continuing to work with you all.  On the way there, please
participate in the process in the incubator.

Greetings from Germany,
Myrle


On Fri, Feb 24, 2017 at 11:23 AM, Myrle Krantz  wrote:

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

Please welcome Zayyad Said and Robert Ippez to Apache Fineract

[Myrle Krantz]

Hi all,

Please welcome two new committers to Apache Fineract: Zayyad Said, and
Robert Ippez.

Zayyad has been an active member of the community since at least 2010. He
supports dozens of microfinance institutions in Mombasa, Kenya. He has
provided invaluable feedback, bug reports, and support. He never hesitates
to answer a question. Zayyad is also a knowledgeable resource on Islamic
microfinance.

Robert has contributed since late 2013. He supports one of the first
Savings and Credit Cooperatives to use Apache Fineract. In that role, he
has provided detailed requirements, user stories and bug reports, including
requirements for the dormant savings accounts, interest rate bands for
deposit accounts, and shares and dividends accounts. He provides user
support on the mailing lists as well.

Thank you Zayyad and Robert for your contributions and for accepting our
invitation. I look forward to continuing our work together toward providing
financial services to all.

Welcome!
Myrle Krantz

P.S. Thank you also to Ed Cable for driving the process of extending
committership, including collecting the information for the committer
introductions contained in this e-mail.

Fwd: Google Summer of Code 2017 Mentor Registration

[Myrle Krantz]

Hi Finerators,

Who is interested in mentoring for Google Summer of Code 2017?  Do we have
JIRA tickets you want to mentor for?  If I can get at least one of each
(mentor + ticket), I'll register Fineract for GSOC, and acknowledge your
mentoring request.  Tag tickets you think are suitable with "gsoc2017" or
"gsoc".

My question is specifically for Fineract mentors and tickets.  Projects and
tickets to produce code outside of Apache repos would run under Mifos
participation in GSOC and not Apache's.  Code in "https://github.com/openMF/";
is Mifos code.

Greets,
Myrle

-- Forwarded message --
From: Ulrich Stärk 
Date: Mon, Mar 6, 2017 at 8:39 PM
Subject: Google Summer of Code 2017 Mentor Registration
To: ment...@community.apache.org
Cc: "d...@community.apache.org" 


Dear PMCs,

I'm happy to announce that the ASF has made it onto the list of accepted
organizations for
Google Summer of Code 2017! [1,2]

It is now time for mentors to sign up, so please pass this email on to your
community and
podlings. If you aren’t already subscribed to ment...@community.apache.org
you should do so now else
you might miss important information.

Mentor signup requires two steps: mentor signup in Google's system [3] and
PMC acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an acknowledgement from the PMC for which you want to mentor
projects. Use the below
template and *do not forget to copy ment...@community.apache.org*. We will
use the email adress you
indicate to send the invite to be a mentor for Apache.

PMCs, read carefully please.

We request that each mentor is acknowledged by a PMC member. This is to
ensure the mentor is in good
standing with the community. When you receive a request for
acknowledgement, please ACK it and cc
ment...@community.apache.org

Lastly, it is not yet too late to record your ideas in Jira (see my
previous emails for details).
Students will now begin to explore ideas so if you haven’t already done so,
record your ideas
immediately!

Cheers,

Uli

mentor request email template:

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2017 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code
2017 projects for Apache
.

I would like to receive the mentor invite to 





[1] https://summerofcode.withgoogle.com/organizations/
[2] https://summerofcode.withgoogle.com/organizations/5416945173135360/
[3] https://summerofcode.withgoogle.com/

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [MENTORS] Preparing graduation

[Myrle Krantz]

Never mind Mentors,  Craig Russell got it going for us.

Thank you anyways,
Myrle

On Fri, 3 Mar 2017 at 10:38 Myrle Krantz  wrote:

> Hey Mentors,
>
> It seems Michael Vorburger assumed that he had an apache id since he's
> already signed a CLA.  He was wrong, but Apache does have record of his
> CLA*.  We need to create a new account for him, and I don't have the
> necessary karma to do it**.
>
> Can one of our mentors please create an account under the name vorburger
> for him?  His e-mail is m...@vorburger.ch.
>
> I'm going to hold off on ending the graduation proposal discussion until
> we have that last detail taken care of.
>
> Thank you,
> Myrle
>
>
> *https://people.apache.org/unlistedclas.html
> **https://id.apache.org/acreq/
>
>
>
>
> On Fri, Feb 24, 2017 at 11:13 AM, Myrle Krantz  wrote:
>
> Hey Roman,
>
> I'll start a thread labeled [DISCUSS].  Here's the most recent state of
> discussions among the community:
> http://markmail.org/thread/4vzjbopjeozrccka  In that thread seven people
> gave their +1, and there were no objections.
>
> Here's a log of what happened with respect to the community growth
> 12 committers at induction into incubation
> +1 committer: Jim Jagielski
> -1 committer: Michael Vorburger (couldn't find an apache id for him, when
> assembling the proposal.  Please correct me if I'm wrong.)
> -1 committer: Andrew Dzakpasu (received no response in public or in
> private from him to the above referenced thread.)
> > 11 PMC members
>
> I'd like to keep Andrew on the committer list, and I'd like to add him to
> the PMC, but I don't feel comfortable doing the latter without his
> permission.  The same goes for Michael, except that I don't even know how
> to keep him on the committer list without an apache id.
>
> This all brings me to a question: is the list of initial committers in the
> graduation proposal also the PMC? Or is it possible to start with a
> difference in the list of committers and PMC?
>
> Greets,
> Myrle
>
>
> On Fri, Feb 24, 2017 at 12:01 AM, Roman Shaposhnik 
> wrote:
>
> On Thu, Feb 23, 2017 at 9:48 AM, Myrle Krantz  wrote:
> > Hi Greg, Jim, Roman, and Ross,
> >
> > We of the Apache Fineract community, have reached a consensus that we are
> > ready for graduation.  I've put together a proposal (
> >
> https://cwiki.apache.org/confluence/display/FINERACT/Graduation+Resolution
> )
> > to send to the incubator.  Would you please review it and make/suggest
> any
> > changes you believe still need to be made?
>
> It looks fine, my biggest concerns are:
>* you are not articulating PMC growth during the incubation period
>* looking at 11 PMC vs 12 commiters makes me wonder why single
>  out that one person
>
> Also, I'll update http://incubator.apache.org/projects/fineract.html
> shortly
>
> > Which one of you would like to submit it to incubator general?
>
> The process is for you to send it first as a [DISCUSS] thread within your
> own
> community. Give it 5 days or so to stew and unless somebody objects I can
> then open up an IPMC [DISCUSS] and then a [VOTE]
>
> > Thank you all four for getting us this far.
>
> Thanks for listening.
>
> Thanks,
> Roman.
>
>
>
>

Re: [MENTORS] Preparing graduation

[Myrle Krantz]

Hey Mentors,

It seems Michael Vorburger assumed that he had an apache id since he's
already signed a CLA.  He was wrong, but Apache does have record of his
CLA*.  We need to create a new account for him, and I don't have the
necessary karma to do it**.

Can one of our mentors please create an account under the name vorburger
for him?  His e-mail is m...@vorburger.ch.

I'm going to hold off on ending the graduation proposal discussion until we
have that last detail taken care of.

Thank you,
Myrle


*https://people.apache.org/unlistedclas.html
**https://id.apache.org/acreq/




On Fri, Feb 24, 2017 at 11:13 AM, Myrle Krantz  wrote:

> Hey Roman,
>
> I'll start a thread labeled [DISCUSS].  Here's the most recent state of
> discussions among the community: http://markmail.
> org/thread/4vzjbopjeozrccka  In that thread seven people gave their +1,
> and there were no objections.
>
> Here's a log of what happened with respect to the community growth
> 12 committers at induction into incubation
> +1 committer: Jim Jagielski
> -1 committer: Michael Vorburger (couldn't find an apache id for him, when
> assembling the proposal.  Please correct me if I'm wrong.)
> -1 committer: Andrew Dzakpasu (received no response in public or in
> private from him to the above referenced thread.)
> > 11 PMC members
>
> I'd like to keep Andrew on the committer list, and I'd like to add him to
> the PMC, but I don't feel comfortable doing the latter without his
> permission.  The same goes for Michael, except that I don't even know how
> to keep him on the committer list without an apache id.
>
> This all brings me to a question: is the list of initial committers in the
> graduation proposal also the PMC? Or is it possible to start with a
> difference in the list of committers and PMC?
>
> Greets,
> Myrle
>
>
> On Fri, Feb 24, 2017 at 12:01 AM, Roman Shaposhnik 
> wrote:
>
>> On Thu, Feb 23, 2017 at 9:48 AM, Myrle Krantz  wrote:
>> > Hi Greg, Jim, Roman, and Ross,
>> >
>> > We of the Apache Fineract community, have reached a consensus that we
>> are
>> > ready for graduation.  I've put together a proposal (
>> > https://cwiki.apache.org/confluence/display/FINERACT/Graduat
>> ion+Resolution)
>> > to send to the incubator.  Would you please review it and make/suggest
>> any
>> > changes you believe still need to be made?
>>
>> It looks fine, my biggest concerns are:
>>* you are not articulating PMC growth during the incubation period
>>* looking at 11 PMC vs 12 commiters makes me wonder why single
>>  out that one person
>>
>> Also, I'll update http://incubator.apache.org/projects/fineract.html
>> shortly
>>
>> > Which one of you would like to submit it to incubator general?
>>
>> The process is for you to send it first as a [DISCUSS] thread within your
>> own
>> community. Give it 5 days or so to stew and unless somebody objects I can
>> then open up an IPMC [DISCUSS] and then a [VOTE]
>>
>> > Thank you all four for getting us this far.
>>
>> Thanks for listening.
>>
>> Thanks,
>> Roman.
>>
>
>

Re: NoSQL DB Option

[Myrle Krantz]

Hi Archzilon,

Apache Fineract does not use a NoSQL DB.  Some Apache Fineract committers
are working in not-exactly secret on a Fineract 2.0, that uses a mix of a
NoSQL DB (Cassandra specifically) and an SQL DB.  We're using Cassandra for
the command part of CQRS (in http terms: POSTs and PUTs and DELETEs),
updating the SQL DB asynchronously and answering queries (GETs,) out of the
SQL DB.

Out of curiosity: what do you hope to gain from an OrientDB integration?

Greets,
Myrle


On Wed, Mar 1, 2017 at 5:50 AM, Archzilon Eshun-Davies <
lauda...@qremiaevolution.org> wrote:

> Hi
>
> I would like to know if a NoSQL DB like mongo or orientdb was considered,
> if not
> would it be possible to do so, I am willing to do that(OrientDB
> integration).
>
> Regards.
>

[DISCUSS] Graduation

[Myrle Krantz]

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: [MENTORS] Preparing graduation

[Myrle Krantz]

Hey Roman,

I'll start a thread labeled [DISCUSS].  Here's the most recent state of
discussions among the community: http://markmail.org/thread/4vzjbopjeozrccka
 In that thread seven people gave their +1, and there were no objections.

Here's a log of what happened with respect to the community growth
12 committers at induction into incubation
+1 committer: Jim Jagielski
-1 committer: Michael Vorburger (couldn't find an apache id for him, when
assembling the proposal.  Please correct me if I'm wrong.)
-1 committer: Andrew Dzakpasu (received no response in public or in private
from him to the above referenced thread.)
> 11 PMC members

I'd like to keep Andrew on the committer list, and I'd like to add him to
the PMC, but I don't feel comfortable doing the latter without his
permission.  The same goes for Michael, except that I don't even know how
to keep him on the committer list without an apache id.

This all brings me to a question: is the list of initial committers in the
graduation proposal also the PMC? Or is it possible to start with a
difference in the list of committers and PMC?

Greets,
Myrle


On Fri, Feb 24, 2017 at 12:01 AM, Roman Shaposhnik 
wrote:

> On Thu, Feb 23, 2017 at 9:48 AM, Myrle Krantz  wrote:
> > Hi Greg, Jim, Roman, and Ross,
> >
> > We of the Apache Fineract community, have reached a consensus that we are
> > ready for graduation.  I've put together a proposal (
> > https://cwiki.apache.org/confluence/display/FINERACT/
> Graduation+Resolution)
> > to send to the incubator.  Would you please review it and make/suggest
> any
> > changes you believe still need to be made?
>
> It looks fine, my biggest concerns are:
>* you are not articulating PMC growth during the incubation period
>* looking at 11 PMC vs 12 commiters makes me wonder why single
>  out that one person
>
> Also, I'll update http://incubator.apache.org/projects/fineract.html
> shortly
>
> > Which one of you would like to submit it to incubator general?
>
> The process is for you to send it first as a [DISCUSS] thread within your
> own
> community. Give it 5 days or so to stew and unless somebody objects I can
> then open up an IPMC [DISCUSS] and then a [VOTE]
>
> > Thank you all four for getting us this far.
>
> Thanks for listening.
>
> Thanks,
> Roman.
>

[MENTORS] Preparing graduation

[Myrle Krantz]

Hi Greg, Jim, Roman, and Ross,

We of the Apache Fineract community, have reached a consensus that we are
ready for graduation.  I've put together a proposal (
https://cwiki.apache.org/confluence/display/FINERACT/Graduation+Resolution)
to send to the incubator.  Would you please review it and make/suggest any
changes you believe still need to be made?  Which one of you would like to
submit it to incubator general?

Thank you all four for getting us this far.

Greets,
Myrle

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

[Myrle Krantz]

+1  I agree this is the best approach Nazeer.

-Myrle

On Tue, Feb 14, 2017 at 1:30 PM, Shaik Nazeer <
nazeer.sh...@confluxtechnologies.com> 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 evaluate Fineract's readiness for graduation

[Myrle Krantz]

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  wrote:

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

Re: Please help evaluation Fineract's readiness for graduation

[Myrle Krantz]

Hey Ed,

Isn't that what Jira is for?  Wouldn't it be enough to just tag the release
version when a ticket is resolved?

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 Thu, Jan 26, 2017 at 8:01 PM, Ed Cable  wrote:

> To address Sendoro's comment, could we maintain the changelog (
> https://github.com/apache/incubator-fineract/blob/develop/CHANGELOG.md)
>
> just as we do the Mifos X changelog
>
>  https://github.com/openMF/incubator-fineract/blob/
> master/MIFOS-CHANGELOG.md
>
> whereby from the changelog you can immediately see history of changes and
> do as Sendoro would like and quickly decide whether to upgrade or not.
>
> Ed
>
> On Thu, Jan 26, 2017 at 10:58 AM, Ed Cable  wrote:
>
> > Nazeer,
> >
> > We do need to link to the latest download which in this case is 0.6.0
> from
> > https://dist.apache.org/repos/dist/release/incubator/fineract/
> >
> > Markus - is there a way in which to dynanmically link to the latest
> > release or do we always have to manually update.
> >
> >
> > On Wed, Jan 25, 2017 at 7:52 PM, Shaik Nazeer  > confluxtechnologies.com> wrote:
> >
> >> Instead of modifying Fineract website on every Fineract releases, can we
> >> link required details to Fineract wiki pages?
> >> For example latest release details can be found at
> >> https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders
> >>
> >> Thanks,
> >> Nazeer
> >> -Original Message-
> >> From: Markus Geiß [mailto:mge...@mifos.org]
> >> Sent: 26 January 2017 01:55
> >> To: Ed Cable
> >> Cc: dev (dev@fineract.incubator.apache.org)
> >> Subject: Re: Please help evaluation Fineract's readiness for graduation
> >>
> >> Hey Ed,
> >>
> >> the Apache Fineract website is a github repo you'll find at Apache's
> >> github mirror.
> >>
> >> Simply fork it, create a new branch, do the needed changes and send a
> PR.
> >>
> >> Best wishes,
> >>
> >> Markus Geiss
> >> Chief Architect
> >> RɅĐɅЯ, The Mifos Initiative
> >>
> >> On Jan 24, 2017 15:58, "Ed Cable"  wrote:
> >>
> >> > Markus,
> >> >
> >> > Nazeer is continuing to work on addressing the areas of concern
> >> > related to QU10, QU40, and RE50.
> >> >
> >> > Could you provide me access to the Apache Fineract website to address
> >> > CO10 and then for CS10 do we want that on the Apache Fineract website
> >> > or the wiki?
> >> >
> >> > Thanks,
> >> >
> >> > Ed
> >> >
> >> > On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski 
> wrote:
> >> >
> >> >> Agreed.
> >> >>
> >> >> > On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik  >
> >> >> wrote:
> >> >> >
> >> >> > On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable 
> wrote:
> >> >> >> Could our Apache Fineract mentors please provide some guidance on
> >> >> >> a
> >> >> couple
> >> >> >> of the areas we need to improve upon:
> >> >> >>
> >> >> >> QU10 "*The project is open and honest about the quality of its
> code.
> >> >> >> Various levels of quality and maturity for various modules are
> >> >> >> natural
> >> >> and
> >> >> >> acceptable as long as they are clearly communicated." -*
> >> >> >>
> >> >> >> Do you have any other projects you could point to that have strong
> >> >> >> transparent 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 w

Re: [ANNOUNCE] Apache Fineract 0.6.0-incubating Release

[Myrle Krantz]

Hey Andy,

Fineract is made up of REST services.  The Mifos Initiative produces an
open source web app called "The Community App" which can serve as a front
end to Fineract.

Here's a youtube demo: https://www.youtube.com/watch?v=h61g9TptMBo (Demo
starts after the introduction at about 3:20).

If you'd like some information about where this is used in real life, one
company using Fineract in their financial inclusion products is Musoni.
They have some nice charts and use cases here:
https://musoni.co.ke/impact/

Conflux is another company using Fineract to produce a product they call
Finflux.

That's pretty introductory material; perhaps you had something more
specific in mind?

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 Tue, Jan 17, 2017 at 2:18 PM, Andy Wenk  wrote:

> Hey all,
>
> congrats for the new release ;-). I heard about Fineract the first time
> and had a look to the website and the wiki pages (just scanned a bit). It
> sounds interesting. I would love to read  more about real life usecases.
> Can anyone point me to some posts or info where I get an idea how to use
> this piece of software?
>
> Thanks a lot in advance!
>
> All the best
>
> Andy
>
> --
> Andy Wenk
> RockIt!
>
> Hamburg / Germany
>
> GPG public key: https://pgp.mit.edu/pks/lookup?op=get&search=
> 0x4F1D0C59BC90917D
>
> > On 17 Jan 2017, at 13:54, Nazeer Shaik  wrote:
> >
> > Hi all,
> >
> > The Apache Fineract team would like to announce the release of Apache
> Fineract 0.6.0-incubating with source and binary artifacts.
> >
> > Apache Fineract is an open source system for core banking as a platform.
> Fineract provides a reliable, robust, and affordable solution for
> entrepreneurs, financial institutions, and service providers to offer
> financial services to the world’s 2 billion under banked and unbanked.
> >
> > More details regarding Apache Fineract can be found at
> http://fineract.incubator.apache.org/
> >
> > The release artifacts can be downloaded here:
> > https://dist.apache.org/repos/dist/release/incubator/
> fineract/0.6.0-incubating/
> >
> > The release notes can be found here:
> > https://cwiki.apache.org/confluence/display/FINERACT/0.
> 6.0-incubating+Release-+Apache+Fineract
> >
> > Thanks!
> > The Apache Fineract Team
> > --- DISCLAIMER  Apache Fineract is an effort undergoing incubation at
> The Apache Software Foundation (ASF), sponsored by the Apache Incubator
> PMC. Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects. While incubation status is not necessarily a reflection of
> the completeness or stability of the code,it does indicate that the project
> has yet to be fully endorsed by the ASF.
> >
>
>

build.sh in Release

[Myrle Krantz]

Hey all,

why do we have build.sh in the root directory of our release?  I had
ignored it before I saw John's comment in the incubator general list.  But
given that it's called build.sh, he's right: it is kind of misleading.

Build.sh doesn't work on my computer either, but I peeked into it to see
what it's supposed to do.  It looks like it will only work if the
community-app is successfully pulled from the mifos github repository in
the script.  It's a little shady to be getting sources from a non-apache
git repository in the build script of what is supposed to be a source code
release.

The mifos community-app is not even being checked as part of the Apache
Fineract release.  As such, if build.sh did work, it may actually be a
potential legal problem for the ASF if the community-apps source become a
quasi-component of Fineract.

Since it doesn't work anyways, let's delete build.sh.  Then nobody can call
it and complain that our build doesn't work.

What do you all think?

Greets,
Myrle

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

[Myrle Krantz (JIRA)]

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

Myrle Krantz closed FINERACT-369.
-
Resolution: Duplicate

Jira was experiencing timeouts which caused requests to be resent and duplicate 
tickets to be created.

> Make gradle callable from the top level directory.
> --
>
> Key: FINERACT-369
> URL: https://issues.apache.org/jira/browse/FINERACT-369
> Project: Apache Fineract
>  Issue Type: Wish
>        Reporter: Myrle Krantz
>Assignee: Markus Geiss
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Myrle Krantz (JIRA)]

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

Myrle Krantz closed FINERACT-370.
-
Resolution: Duplicate

Jira was experiencing timeouts so I didn't see that I had created this ticket.

> Make gradle callable from the top level directory.
> --
>
> Key: FINERACT-370
> URL: https://issues.apache.org/jira/browse/FINERACT-370
> Project: Apache Fineract
>  Issue Type: Wish
>    Reporter: Myrle Krantz
>Assignee: Markus Geiss
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-357) Address the review comments for 0.6.0-incubating release

[Myrle Krantz (JIRA)]

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

Myrle Krantz commented on FINERACT-357:
---

Branched out the first two points as
https://issues.apache.org/jira/browse/FINERACT-371
https://issues.apache.org/jira/browse/FINERACT-368

> Address the review comments for 0.6.0-incubating release
> 
>
> Key: FINERACT-357
> URL: https://issues.apache.org/jira/browse/FINERACT-357
> Project: Apache Fineract
>  Issue Type: Task
>  Components: User Management
>Reporter: Shaik Nazeer Hussain
>Assignee: Shaik Nazeer Hussain
>
> As part of 0.5.0-incubating release, we got the following review comments 
> from IPMC members which should be addressed for 0.6.0-incubating release.
> 3) Including License and License.md will confuse the people
> 4) The LICENSE maye be missing a license for jquery
> 5) Remove the list of software included in the binary release from the source 
> release LICENSE file. It’s fine to have two different license files
> 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in 
> the top level, however the LICENSE and NOTICE file is inside the war and look 
> correct
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CE4A4287E-8A78-4A61-9666-0F111BFA9D7C%40classsoftware.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FINERACT-357) Address the review comments for 0.6.0-incubating release

[Myrle Krantz (JIRA)]

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

Myrle Krantz resolved FINERACT-357.
---
Resolution: Fixed

Closing this issue as fixed.

> Address the review comments for 0.6.0-incubating release
> 
>
> Key: FINERACT-357
> URL: https://issues.apache.org/jira/browse/FINERACT-357
> Project: Apache Fineract
>  Issue Type: Task
>  Components: User Management
>Reporter: Shaik Nazeer Hussain
>Assignee: Shaik Nazeer Hussain
>
> As part of 0.5.0-incubating release, we got the following review comments 
> from IPMC members which should be addressed for 0.6.0-incubating release.
> 3) Including License and License.md will confuse the people
> 4) The LICENSE maye be missing a license for jquery
> 5) Remove the list of software included in the binary release from the source 
> release LICENSE file. It’s fine to have two different license files
> 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in 
> the top level, however the LICENSE and NOTICE file is inside the war and look 
> correct
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CE4A4287E-8A78-4A61-9666-0F111BFA9D7C%40classsoftware.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-357) Address the review comments for 0.6.0-incubating release

[Myrle Krantz (JIRA)]

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

Myrle Krantz updated FINERACT-357:
--
Description: 
As part of 0.5.0-incubating release, we got the following review comments from 
IPMC members which should be addressed for 0.6.0-incubating release.
3) Including License and License.md will confuse the people
4) The LICENSE maye be missing a license for jquery
5) Remove the list of software included in the binary release from the source 
release LICENSE file. It’s fine to have two different license files
6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in the 
top level, however the LICENSE and NOTICE file is inside the war and look 
correct

Relevant e-mails:
http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CE4A4287E-8A78-4A61-9666-0F111BFA9D7C%40classsoftware.com%3E

  was:
As part of 0.5.0-incubating release, we got the following review comments from 
IPMC members which should be addressed for 0.6.0-incubating release.
1) Maven repo should be included in place of war file for the next release
2) Gradle should be integrated in the top level directory. Currently it is 
integrated with fineract-provider. (RAT issue)
3) Including License and License.md will confuse the people
4) The LICENSE maye be missing a license for jquery
5) Remove the list of software included in the binary release from the source 
release LICENSE file. It’s fine to have two different license files
6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in the 
top level, however the LICENSE and NOTICE file is inside the war and look 
correct

Relevant e-mails:
http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CE4A4287E-8A78-4A61-9666-0F111BFA9D7C%40classsoftware.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E


> Address the review comments for 0.6.0-incubating release
> 
>
> Key: FINERACT-357
> URL: https://issues.apache.org/jira/browse/FINERACT-357
> Project: Apache Fineract
>  Issue Type: Task
>  Components: User Management
>Reporter: Shaik Nazeer Hussain
>Assignee: Shaik Nazeer Hussain
>
> As part of 0.5.0-incubating release, we got the following review comments 
> from IPMC members which should be addressed for 0.6.0-incubating release.
> 3) Including License and License.md will confuse the people
> 4) The LICENSE maye be missing a license for jquery
> 5) Remove the list of software included in the binary release from the source 
> release LICENSE file. It’s fine to have two different license files
> 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in 
> the top level, however the LICENSE and NOTICE file is inside the war and look 
> correct
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CE4A4287E-8A78-4A61-9666-0F111BFA9D7C%40classsoftware.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Myrle Krantz (JIRA)]

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

Myrle Krantz commented on FINERACT-371:
---

"branched" this issue out of https://issues.apache.org/jira/browse/FINERACT-357.

Comments relevant to this part of the ticket from there:
[~nazeer1100126] "I believe, integrating RAT on top level directory is 
unnecessary effort as either we need to duplicate the gradle scripts at top 
level for RAT only or we need to move the complete source and build scripts 
from fineract-provider to top level directory."
[~myrle] "2.) I agree with Shaik Nazeer Hussain that providing details in the 
README is sufficient. What Roman says about lowering the hurdles for reviewers 
is important, but we also need to keep effort in concordance with benefit. 
Should we choose to do this point anyways, a possible technical solution is to 
create a gradle composite build at the top level."

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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Myrle Krantz (JIRA)]

Myrle Krantz created FINERACT-371:
-

 Summary: Make gradle callable from the top level directory.
 Key: FINERACT-371
 URL: https://issues.apache.org/jira/browse/FINERACT-371
 Project: Apache Fineract
  Issue Type: Wish
Reporter: Myrle Krantz
Assignee: Markus Geiss
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Myrle Krantz (JIRA)]

Myrle Krantz created FINERACT-370:
-

 Summary: Make gradle callable from the top level directory.
 Key: FINERACT-370
 URL: https://issues.apache.org/jira/browse/FINERACT-370
 Project: Apache Fineract
  Issue Type: Wish
Reporter: Myrle Krantz
Assignee: Markus Geiss
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Myrle Krantz (JIRA)]

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

Myrle Krantz updated FINERACT-371:
--
Description: 
Relevant e-mails:
http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E

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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Myrle Krantz (JIRA)]

Myrle Krantz created FINERACT-369:
-

 Summary: Make gradle callable from the top level directory.
 Key: FINERACT-369
 URL: https://issues.apache.org/jira/browse/FINERACT-369
 Project: Apache Fineract
  Issue Type: Wish
Reporter: Myrle Krantz
Assignee: Markus Geiss
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (FINERACT-368) Make the release artifact into a maven artefact.

[Myrle Krantz (JIRA)]

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

Myrle Krantz edited comment on FINERACT-368 at 1/12/17 8:38 AM:


"branched" this issue out of https://issues.apache.org/jira/browse/FINERACT-357.

Comments relevant to this part of the ticket from there:
[~nazeer1100126] "I am not sure whether it is feasible to have maven repo as we 
are distributing deployable war file. Waiting for mentors to give their 
opinion."
[~myrle] "It is possible to create a maven artifact for a war file. But do any 
of our users need this from us? The way it is now is not creating an obstacle 
to reviews, so I'd wait for the request from our users."


was (Author: myrle):
"branched" this issue out of https://issues.apache.org/jira/browse/FINERACT-357.

> Make the release artifact into a maven artefact.
> 
>
> Key: FINERACT-368
> URL: https://issues.apache.org/jira/browse/FINERACT-368
> Project: Apache Fineract
>  Issue Type: Wish
>Reporter: Myrle Krantz
>Assignee: Markus Geiss
>Priority: Minor
>
> Relevant e-mail:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-368) Make the release artifact into a maven artefact.

[Myrle Krantz (JIRA)]

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

Myrle Krantz commented on FINERACT-368:
---

"branched" this issue out of https://issues.apache.org/jira/browse/FINERACT-357.

> Make the release artifact into a maven artefact.
> 
>
> Key: FINERACT-368
> URL: https://issues.apache.org/jira/browse/FINERACT-368
> Project: Apache Fineract
>  Issue Type: Wish
>Reporter: Myrle Krantz
>Assignee: Markus Geiss
>Priority: Minor
>
> Relevant e-mail:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-368) Make the release artifact into a maven artefact.

[Myrle Krantz (JIRA)]

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

Myrle Krantz updated FINERACT-368:
--
Description: 
Relevant e-mail:
http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E

> Make the release artifact into a maven artefact.
> 
>
> Key: FINERACT-368
> URL: https://issues.apache.org/jira/browse/FINERACT-368
> Project: Apache Fineract
>  Issue Type: Wish
>        Reporter: Myrle Krantz
>Assignee: Markus Geiss
>Priority: Minor
>
> Relevant e-mail:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FINERACT-368) Make the release artifact into a maven artefact.

[Myrle Krantz (JIRA)]

Myrle Krantz created FINERACT-368:
-

 Summary: Make the release artifact into a maven artefact.
 Key: FINERACT-368
 URL: https://issues.apache.org/jira/browse/FINERACT-368
 Project: Apache Fineract
  Issue Type: Wish
Reporter: Myrle Krantz
Assignee: Markus Geiss
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Myrle Krantz]

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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>


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
> <https://git-wip-us.apache.org/repos/asf?p=incubator-
> 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 <http://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
>
>

Jira Ticket version fields for Apache Fineract project.

[Myrle Krantz]

Hi all,

When checking a release, I'd like to be able to look at which Jira issues
affect a particular release.  I noticed that our JIRA project isn't
configured to display the fixed in version and affects version fields.
These version fields would be useful not only for creating release notes,
and checking a release.  They would also be useful for customers trying to
understand the quality of a particular release or to find out if an issue
they are seeing is new or not.  I'd like us to add the JIRA fields, and set
them for the currently open tickets.

What do you all think?

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>

Re: [Apache Fineract] Addressing review comments of 0.5.0-incubating release

[Myrle Krantz]

Hey Nazeer,

*I'm* sorry for expressing myself in a confusing manner.  I didn't mean to
imply you had done something wrong.  You haven't.

When I said "We shouldn't automatically disregard [our mentors] advice", I
didn't mean to imply that you were.  I was just setting the context for the
suggestion that we *do* disregard their advice, but only on maven
artifacts, and top-level RAT checks for the upcoming version.

Hopefully I haven't made things even more confusing...

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 Fri, Jan 6, 2017 at 8:22 AM, Nazeer Shaik <
nazeer.sh...@confluxtechnologies.com> wrote:

> Thank you Myrle. Sorry I was not disregarding mentors review comments
> rather I was trying to get some help/opinion from all of you for the next
> release.
> I will go ahead with releasing 0.6.0-incubating today by mentioning the
> same.
>
> 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 Wed, Jan 4, 2017 at 6:32 PM, Myrle Krantz  wrote:
>
> > Hey Nazeer,
> >
> > Keep in mind, that, if it's not about the license, you can usually treat
> > what our mentors and reviewers says as advice that we can follow or not.
> > We shouldn't automatically disregard their advice, because that would
> > impact their willingness to review our releases.  But if the effort is
> > large, and the benefit small, no one is going to be offended if we say
> > "no", or "later".  If our mentors aren't responding on this issue, it's
> > likely because it's not very important to them.
> >
> > So we shouldn't let those points block our next release, but rather treat
> > them like any other ticket.
> >
> > 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 Fri, Dec 30, 2016 at 11:12 AM, Shaik Nazeer <
> > nazeer.sh...@confluxtechnologies.com> wrote:
> >
> > > Hi Fineract mentors,
> > >
> > >
> > >
> > > After analysing a bit, integrating RAT to top level directory is
> > difficult
> > > as our complete build scripts are under sub directory.
> > >
> > > Either we need to add Gradle scripts to top level directory also or
> move
> > > the
> > > complete source tree from Fineract-provider to top level directory.
> > >
> > > I feel above two approaches area not good. So do you have any
> suggestions
> > > on
> > > this or shall I try to proceed with next release by adding "How to run
> > RAT"
> > > in readme without integrating RAT to top level directory?
> > >
> > >
> > >
> > > And I don't understand how maven is going to help here as we are giving
> > > complete deployable war file.
> > >
> > >
> > >
> > > Can you let me know your opinion on this please.
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Nazeer
> > >
> > > From: Shaik Nazeer [mailto:nazeer.sh...@confluxtechnologies.com]
> > > Sent: 29 December 2016 18:27
> > > To: dev@fineract.incubator.apache.org
> > > Subject: [Apache Fineract] Addressing review comments of
> 0.5.0-incubating
> > > release
> > >
> > >
> > >
> > > Hi all,
> > >
> > >
> > >
> > > I have created a JIRA task to address all review comments of
> > > 0.5.0-incubating release.
> > >
> > > https://issues.apache.org/jira/browse/FINERACT-357
> > >
> > >
> > >
> > > I can handle all review comments except maven related. Does anybody
> know
> > > how
> > > to include maven repo as part of Fineract release?
> > >
> > >
> > >
> > > Thanks
> > >
> > > Nazeer
> > >
> > >
> >
>

Re: [Apache Fineract] Addressing review comments of 0.5.0-incubating release

[Myrle Krantz]

Hey Nazeer,

Keep in mind, that, if it's not about the license, you can usually treat
what our mentors and reviewers says as advice that we can follow or not.
We shouldn't automatically disregard their advice, because that would
impact their willingness to review our releases.  But if the effort is
large, and the benefit small, no one is going to be offended if we say
"no", or "later".  If our mentors aren't responding on this issue, it's
likely because it's not very important to them.

So we shouldn't let those points block our next release, but rather treat
them like any other ticket.

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 Fri, Dec 30, 2016 at 11:12 AM, Shaik Nazeer <
nazeer.sh...@confluxtechnologies.com> wrote:

> Hi Fineract mentors,
>
>
>
> After analysing a bit, integrating RAT to top level directory is difficult
> as our complete build scripts are under sub directory.
>
> Either we need to add Gradle scripts to top level directory also or move
> the
> complete source tree from Fineract-provider to top level directory.
>
> I feel above two approaches area not good. So do you have any suggestions
> on
> this or shall I try to proceed with next release by adding "How to run RAT"
> in readme without integrating RAT to top level directory?
>
>
>
> And I don't understand how maven is going to help here as we are giving
> complete deployable war file.
>
>
>
> Can you let me know your opinion on this please.
>
>
>
> Thanks,
>
> Nazeer
>
> From: Shaik Nazeer [mailto:nazeer.sh...@confluxtechnologies.com]
> Sent: 29 December 2016 18:27
> To: dev@fineract.incubator.apache.org
> Subject: [Apache Fineract] Addressing review comments of 0.5.0-incubating
> release
>
>
>
> Hi all,
>
>
>
> I have created a JIRA task to address all review comments of
> 0.5.0-incubating release.
>
> https://issues.apache.org/jira/browse/FINERACT-357
>
>
>
> I can handle all review comments except maven related. Does anybody know
> how
> to include maven repo as part of Fineract release?
>
>
>
> Thanks
>
> Nazeer
>
>

[jira] [Commented] (FINERACT-357) Address the review comments for 0.6.0-incubating release

[Myrle Krantz (JIRA)]

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

Myrle Krantz commented on FINERACT-357:
---

I strongly recommend splitting this ticket so the items are easier to work on 
and discuss separately.

1.) It is possible to create a maven artifact for a war file.  But do any of 
our users need this from us?  The way it is now is not creating an obstacle to 
reviews, so I'd wait for the request from our users.
2.) I agree with [~nazeer1100126] that providing details in the README is 
sufficient.  What Roman says about lowering the hurdles for reviewers is 
important, but we also need to keep effort in concordance with benefit.  Should 
we choose to do this point anyways, a possible technical solution is to create 
a gradle composite build at the top level.

> Address the review comments for 0.6.0-incubating release
> 
>
> Key: FINERACT-357
> URL: https://issues.apache.org/jira/browse/FINERACT-357
> Project: Apache Fineract
>  Issue Type: Task
>  Components: User Management
>Reporter: Shaik Nazeer Hussain
>Assignee: Shaik Nazeer Hussain
>
> As part of 0.5.0-incubating release, we got the following review comments 
> from IPMC members which should be addressed for 0.6.0-incubating release.
> 1) Maven repo should be included in place of war file for the next release
> 2) Gradle should be integrated in the top level directory. Currently it is 
> integrated with fineract-provider. (RAT issue)
> 3) Including License and License.md will confuse the people
> 4) The LICENSE maye be missing a license for jquery
> 5) Remove the list of software included in the binary release from the source 
> release LICENSE file. It’s fine to have two different license files
> 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in 
> the top level, however the LICENSE and NOTICE file is inside the war and look 
> correct
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CE4A4287E-8A78-4A61-9666-0F111BFA9D7C%40classsoftware.com%3E
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-357) Address the review comments for 0.6.0-incubating release

[Myrle Krantz (JIRA)]

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

Myrle Krantz updated FINERACT-357:
--
Description: 
As part of 0.5.0-incubating release, we got the following review comments from 
IPMC members which should be addressed for 0.6.0-incubating release.
1) Maven repo should be included in place of war file for the next release
2) Gradle should be integrated in the top level directory. Currently it is 
integrated with fineract-provider. (RAT issue)
3) Including License and License.md will confuse the people
4) The LICENSE maye be missing a license for jquery
5) Remove the list of software included in the binary release from the source 
release LICENSE file. It’s fine to have two different license files
6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in the 
top level, however the LICENSE and NOTICE file is inside the war and look 
correct

Relevant e-mails:
http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CE4A4287E-8A78-4A61-9666-0F111BFA9D7C%40classsoftware.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E

  was:
As part of 0.5.0-incubating release, we got the following review comments from 
IPMC members which should be addressed for 0.6.0-incubating release.
1) Maven repo should be included in place of war file for the next release
2) Gradle should be integrated in the top level directory. Currently it is 
integrated with fineract-provider. (RAT issue)
3) Including License and License.md will confuse the people
4) The LICENSE maye be missing a license for jquery
5) Remove the list of software included in the binary release from the source 
release LICENSE file. It’s fine to have two different license files
6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in the 
top level, however the LICENSE and NOTICE file is inside the war and look 
correct



> Address the review comments for 0.6.0-incubating release
> 
>
> Key: FINERACT-357
> URL: https://issues.apache.org/jira/browse/FINERACT-357
> Project: Apache Fineract
>  Issue Type: Task
>  Components: User Management
>Reporter: Shaik Nazeer Hussain
>Assignee: Shaik Nazeer Hussain
>
> As part of 0.5.0-incubating release, we got the following review comments 
> from IPMC members which should be addressed for 0.6.0-incubating release.
> 1) Maven repo should be included in place of war file for the next release
> 2) Gradle should be integrated in the top level directory. Currently it is 
> integrated with fineract-provider. (RAT issue)
> 3) Including License and License.md will confuse the people
> 4) The LICENSE maye be missing a license for jquery
> 5) Remove the list of software included in the binary release from the source 
> release LICENSE file. It’s fine to have two different license files
> 6) The convenience binary file is missing LICENSE, NOTICE and DISCLAIMER in 
> the top level, however the LICENSE and NOTICE file is inside the war and look 
> correct
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CE4A4287E-8A78-4A61-9666-0F111BFA9D7C%40classsoftware.com%3E
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Please help evaluation Fineract's readiness for graduation

[Myrle Krantz]

Hi all,

Apache has a project maturity model which can be used to evaluate readiness
for graduation.  It's a guide rather then a set of requirements, but I
believe we can use it.  I've used it to create a page evaluating *our*
readiness:

https://cwiki.apache.org/confluence/display/FINERACT/Maturity+Evaluation

The evaluation is not finished.  Apache Fineract needs the following from
you:
* Evaluate the criteria which I did not evaluate.  I've highlighted them in
blue.
* Check the evaluation of the criteria which already have one.  If your
evaluation differs, document your disagreement. If you agree with the
evaluation, add your committer id.
* On those criteria in which Apache Fineract still has work to do before
graduation (highlighted in red), check if you can do that work.  I've left
at least one low-hanging fruit in there.  Who will find it first?
* If you feel we need to add a criteria, add it, and explain why.

Once we have met all criteria, we should propose ourselves for graduation.

Looking at our current state, we've made tremendous progress since we
entered incubation in December 2015, and I'd like us to make the push for
those last few bits in 2017.  I believe that, if we as a community wish to,
we can achieve this in the first quarter of this year.

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>

Re: [ANNOUNCE] Apache Fineract 0.5.0-incubating Release

[Myrle Krantz]

Thanks Nazeer!

I've tweeted the release under our Apache Fineract twitter account too.

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 Thu, Dec 22, 2016 at 7:27 AM, Nazeer Shaik 
wrote:

> Hi all,
>
>
>
> The Apache Fineract team would like to announce the release of Apache
> Fineract 0.5.0-incubating with source and binary artifacts.
>
>
>
> *Apache Fineract is an open source system for core banking as a platform.
> Fineract provides a reliable, robust, and affordable solution for
> entrepreneurs, financial institutions, and service providers to offer
> financial services to the world’s 2 billion under banked and unbanked.*
>
>
>
> More details regarding Apache Fineract can be found at
> http://fineract.incubator.apache.org/
>
>
>
> The release artifacts can be downloaded here:
>
> https://dist.apache.org/repos/dist/release/incubator/
> fineract/0.5.0-incubating/
>
>
>
> The release notes can be found here:
>
> https://cwiki.apache.org/confluence/display/FINERACT/0.
> 5.0-incubating+Release-+Apache+Fineract
>
>
>
> Thanks!
>
> The Apache Fineract Team
>
>
>
> --- DISCLAIMER  Apache Fineract is an effort undergoing incubation at The
> Apache Software Foundation (ASF), sponsored by the Apache Incubator
> PMC.Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have
>
> stabilized in a manner consistent with other successful ASF projects. While
> incubation status is not necessarily a reflection of the completeness or
> stability of the code,it does indicate that the project has yet to be fully
> endorsed by the ASF.
>

Fwd: ApacheCon Miami is coming in May, and is focused on innovation at Apache

[Myrle Krantz]

Hi Fineracters,

Our project was very well-received at the European ApacheCon.  I'd like to
give another talk on Fineract at the ApacheCon in North America in May.

I would especially enjoy doing so, if I could get some support from you all:

* Is anyone else considering attending? Speaking?
* Are there any real life use cases, that I could highlight to emphasize
the positive impact of our project? (And that you're proud of and want
people to know about?)
* Are there any tasks I could suggest attendees try out to get an
introduction to the project?  Anyone who would be interested in reserving
some of their time to helping introduce newbies mid-May?

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>


-- Forwarded message --
From: Rich Bowen 
Date: Wed, Nov 30, 2016 at 7:37 PM
Subject: ApacheCon Miami is coming in May, and is focused on innovation at
Apache
To: gene...@incubator.apache.org


Dear Apache Incubator participant,


ApacheCon and Apache Big Data will be held at the Intercontinental in
Miami, Florida, May 16-18, 2017. Submit your talks, and register, at
http://apachecon.com/  Talks aimed at the Big Data section of the event
should go to
http://events.linuxfoundation.org/events/apache-big-data-
north-america/program/cfp
while other talks should go to
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp



Apache is where the future gets invented, and projects in the Incubator
are where this happens. For Miami, we want to have a strong focus on
what’s happening in the Incubator today that’s going to change the
industry tomorrow.


The goal of the conference is to strengthen and grow our project
communities, and to build the relationships between your project and the
larger Apache Software Foundation. But it’s also to showcase to the
world what new things will be coming out of the ASF.


If you’re a committer on an incubating project, you can take advantage
of the committer discount when you register. You can register any time
between today and April 16th for the low, low price of $275. This is
more than half off of the early bird rate of $600 that everyone else
pays, and about a quarter of the on-site fee of $1000.


If you’re a mentor of an incubating project, please encourage the
members of your podling to take advantage of this opportunity. ApacheCon
is a great way to attract new contributors to an incubating project, as
well as a way to get the project in front of the press.


Here’s some ways, beyond just showing up, that you can make this your
conference.


Content track: Plan a track of content dedicated to your project, or
several related projects. Content tracks are much easier to sell to
attendees and sponsors than isolated talks, and give attendees a way to
go from introductory level to deep dives into your technology. This
builds your user community, and helps potential contributors get to a
level of proficiency more quickly than they could on their own. If you
think you have enough content for a track, get in touch with Rich
(rbo...@apache.org) to discuss how this works.


Sponsor: It costs money to put on a conference, and this is a great
opportunity for companies involved in Apache projects - your employers -
to get their name and products in front of the community. Sponsors can
start any any monetary level, and can sponsor everything from the
conference badge lanyard, through larger items such as video recordings
and evening events. For more information on sponsoring ApacheCon, see
http://apachecon.com/sponsor/


Volunteer: Volunteers are needed for various parts of putting on this
event. These include, but are probably not limited to, the following:


* Content committee: Review submissions and select final schedule for
the event.

* TAC (Travel Assistance Committee): We offer travel assistance for
attendees of this event. This is a work-intensive process, to ensure
that these awards are given out in an impartial manner to the people who
will benefit from them the most.

* Tour guides and on-site assistants: Conferences are a better
experience for everyone if we have an on-site native to assist the
visitors. We need recommendations of the best places to eat and play
around the venue. We’ll be collecting these on the ApacheCon wiki at
http://wiki.apache.org/apachecon


So, get your tickets today at http://apachecon.com/ and submit your
talks. ApacheCon Miami is going to be our best ApacheCon yet, and you,
and your project, can’t afford to miss it.


--
Rich Bowen - rbo...@apache.org
VP, Conferences
http://apachecon.com
@apachecon

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Myrle Krantz]

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

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>

Speaker's notes from the Shark Tank ApacheCon EU

[Myrle Krantz]

Hi all,

On Friday I gave a five minute presentation to the incubation Shark Tank.
The idea behind the shark tank is to take a critical look in public at
whether a podling is ready for graduation.  Here are the notes I used to
prepare for this short presentation:

https://cwiki.apache.org/confluence/display/FINERACT/Shark+Tank+Notes

You'll note that at the end, I included some of the things I felt we needed
to improve/complete before we can call ourselves a mature project.

What do you, the Apache Fineract developers, feel is left to do?

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>

Speakers notes from yesterday's ApacheCon EU 2016 talk on Fineract

[Myrle Krantz]

Hi all,

For those who couldn't attend, here are the notes from my talk yesterday on
Apache Fineract 1.0.

https://cwiki.apache.org/confluence/display/FINERACT/ApacheCon+EU+2016+Fineract+Speaker%27s+Notes

Greets,


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

Tasks for non-techies?

[Myrle Krantz]

Hey all,

One of the questions I got today after my Fineract presentation was whether we 
have any good tasks for non-techies. I'd love to be able to answer the question 
with "here's a few Jira tickets" tomorrow to keep up the enthusiasm people were 
showing today. Can someone point me to tickets for non-techies please?

Greets,
Myrle 

Re: Excel import/export help needed?

[Myrle Krantz]

Ed, Nayan,

As I understand Nick's question it relates to the current generation of 
Fineract. He and Dave would like to start helping out right away (as would many 
of the people I've talked to today at the ApacheCon). In fact, it's possible 
that with a clear task for the POI guys they could complete something tomorrow 
for us.

Do you have a concrete ticket for them?

Greets,
Myrle 

Sent from my iPhone

> On 17 Nov 2016, at 18:32, Ed Cable  wrote:
> 
> Hi Nick,
> 
> Thanks for reaching out. I will let Myrle respond as it relates to the
> plans for getting data to and from Excel for Apache Fineract Version 2, the
> new framework architecture, she was presenting on.
> 
> Right now, we do currently have a need for volunteers to assist with our
> Excel-based data import tool which is in fact based on Apache POI. It
> currently is a separate module from the Apache Fineract platform but we do
> want to integrate it into the platform and continue to add support for
> additional data that can be imported in via Excel.
> 
> You can find the source code at https://github.com/openMF/DataImportTool
> 
> The gitter chatroom for the tool is at:
> https://gitter.im/openMF/DataImportTool
> 
> Here are the docs on the data import tool:
> https://mifosforge.jira.com/wiki/display/docs/Getting+started+with+-+Data+Import+Tool
> 
> I've also cc'd Nayan, one of our community mentors, who has overseen the
> previous developers and interns working on it.
> 
> Ed
> 
>> On Thu, Nov 17, 2016 at 9:23 AM, Nick Burch  wrote:
>> 
>> Hi All
>> 
>> Earlier today, a few of us from Apache POI saw a great talk on Fineract by
>> Myrle at ApacheCon. Afterwards, we were wondering if there was a way we
>> could help out a bit during the rest of the event, especially in areas we
>> know well.
>> 
>> Getting data to or from Excel files sprang to mind, as that's something
>> POI helps a lot with, and something that we from the project all know well
>> how to do + do efficiently. It's also, we understand, quite a common thing
>> for people in finance to want to do.
>> 
>> Is that something that might be of help? And if so, could someone give us
>> some pointers to get started?
>> 
>> Cheers
>> Nick
>> 
> 
> 
> 
> -- 
> *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
>   

Anyone else at ApacheCon?

[Myrle Krantz]

Hey all,

I'm organizing a dinner for Fineracters at ApacheCon.  If you are going to
be in Seville and I don't know it yet, let me know so I can send you the
information privately.

I've already got:
Guarav
Roman
Jim
Greg

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>

Composing a Release out of Microservices

[Myrle Krantz]

Hi all,

It's been a few months but we talked about how we wish to compose a release
out of microservices when we "finish" decomposing Fineract from a monolith
into microservices.  After our conversation, I put a lot of thought into
what that would look like.  In fact, it's the basis of a talk I'm giving
next Thursday at ApacheCon.  I've put together a description of the
constraints and the possible solutions in our Confluence:

https://cwiki.apache.org/confluence/display/FINERACT/Composing+a+Release+out+of+Microservices

I very much welcome your feedback.  Perhaps you have some insights I've
missed, or maybe just some points I could explain more clearly.  Your
feedback will help me next week, but it will also be the basis of how we
decide to compose our microservice release train, and as a consequence,
what kind of infrastructure support we need from Apache.

Greets,
Myrle

P.S.  I know it's missing some graphic support.  When I get time, I'll use
the presentation for next week as the basis for creating the necessary
graphic support.  The presentation slides are available here:
http://schd.ws/hosted_files/apacheconeu2016/c3/ApacheCon%20EU%202016%20Versioning%20REST%20Microservices.pdf



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

Re: Twitter account

[Myrle Krantz]

Good point Roman,

Anyone who is a Committer and wants to tweet for Fineract, let me know, and
I'll add you.

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 Fri, Nov 4, 2016 at 9:28 PM, Roman Shaposhnik 
wrote:

> On Fri, Nov 4, 2016 at 11:12 AM, Myrle Krantz  wrote:
> > FYI,
> >
> > I just claimed the twitter handle @ApacheFineract for us. If anyone
> wants to tweet something as a community, let me know.
>
> FWIW: I encourage all of my podlings to give Tweetdeck a try:
> https://tweetdeck.twitter.com/
>
> It has a very nice property of allowing other Tweeter accounts to
> post tweets for a shared account without knowing said accounts
> credentials.
>
> Thanks,
> Roman.
>

Twitter account

[Myrle Krantz]

FYI,

I just claimed the twitter handle @ApacheFineract for us. If anyone wants to 
tweet something as a community, let me know.

Greets,
Myrle


Sent from my iPhone

Please welcome our newest Committer: Jim Jagielski

[Myrle Krantz]

Hello Fineract Community,

I am very pleased to announce that the Fineract PMC has asked Jim Jagielski
to become a Committer, and he has accepted!

Jim was a co-founder of the Apache Software Foundation and has been a
member for nearly 22 years.  He has served as one of our mentors in
incubation since May of this year.

As a senior tech fellow at Capital One, he understands the domain we are
working in. As a software architect on multiple related projects, he
understands the technologies we are working with. As a dedicated
open-source advocate, he understands the environment we are working
together in.

Congratulations to both Jim and the rest of the Fineract Community are in
order.

Greets,
Myrle

[jira] [Created] (FINERACT-245) Introduce RAT checks

[Myrle Krantz (JIRA)]

Myrle Krantz created FINERACT-245:
-

 Summary: Introduce RAT checks
 Key: FINERACT-245
 URL: https://issues.apache.org/jira/browse/FINERACT-245
 Project: Apache Fineract
  Issue Type: Task
Reporter: Myrle Krantz
Assignee: Markus Geiss


GIVEN a contributor or committer forks the fineract code base, and builds it 
locally to fix bugs and add features,
WHEN an apache policy violating library dependency is accidentally introduced 
to the source code,
THEN the build fails.

See https://github.com/apache/incubator-geode/blob/develop/gradle/rat.gradle 
for an example of how to do this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Fineract Board Report for November

[Myrle Krantz]

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

[Myrle Krantz]

+1

I checked:
* NOTICE file
* LICENSE file
* source builds
* signature valid

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, Oct 19, 2016 at 3:35 PM, Markus Geiß  wrote:

> +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: [MENTORS] ApacheCon EU 2016

[Myrle Krantz]

FYI: I've gotten my answer. One of my proposals was accepted.


*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, Sep 28, 2016 at 11:45 AM, Myrle Krantz  wrote:

> Hi Mentors,
>
> I submitted three speaking proposals for the ApacheCon EU in November,
> 2016. The website says that notifications will be out by the 26th (or the
> 27th depending on the website).  I still haven't heard anything back.
>
> Is that normal? Does it mean the proposals weren't accepted? Or just that
> planning is behind schedule?  I'm new to Apache conventions, and I'm just
> wondering what I should expect here.
>
> To everyone on this list: is anyone else planning on attending the
> ApacheCon EU?
>
> Greets from the flatlands,
> 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>
>
>

[MENTORS] ApacheCon EU 2016

[Myrle Krantz]

Hi Mentors,

I submitted three speaking proposals for the ApacheCon EU in November,
2016. The website says that notifications will be out by the 26th (or the
27th depending on the website).  I still haven't heard anything back.

Is that normal? Does it mean the proposals weren't accepted? Or just that
planning is behind schedule?  I'm new to Apache conventions, and I'm just
wondering what I should expect here.

To everyone on this list: is anyone else planning on attending the
ApacheCon EU?

Greets from the flatlands,
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>

[MENTORS] Fineract Board Report submitted

[Myrle Krantz]

Hello Finnis,

I just submitted our apache incubator board report.  Two changes of note
from what we worked on together:

* I added the information about our mifos release problems to the board
report.
* I added Jim to the list of mentors who can check off.  Jim: I don't know
how that gets added to the board report template.  We may have something
"official" left to do?

The report there is now ready for mentor review.

One last reminder: I will not be doing board reports again until we have
some Fineract microservices in an Apache repo or two.

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>

Fineract Board Report for September

[Myrle Krantz]

Hello everyone,

I've started the Board Report for September.
https://cwiki.apache.org/confluence/display/FINERACT/2016-09+September+Report

Please review and edit by tomorrow. I will submit it September 7th at the
end of my work day (CET).

In case you don't look into the board report, there is one detail you
should be aware of anyways:
After the September report, I will no longer prepare or submit board
reports.  I believe at this time that Ed Cable, as the community director
at Mifos, is in a better position to do this.  That may change once Markus
and I are ready to open up the work we've been doing.  But currently I'm
missing too much of the picture to be effective in this role.

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>

Upcoming Apache Board Report

[Myrle Krantz]

Hi all,

Since Fineract failed to report in August, we will need to submit a report
in September.  That will be due in the coming week.

I don't actually know what's going on with the community right now.  I have
the impression most of the communication is still occurring on the old
mifos infrastructure instead of on the apache infrastructure. I am not
registered to those mailing lists.

So I present the community with two options:
1.) Someone other than me does the report.
2.) I write the report and communicate in it that the project is in
trouble. We have failed to move communications onto ASF infrastructure.  We
have failed to acquire new contributors.  We have failed to publish an
acceptable release.  We have identified problems (deep-rooted hibernate
dependencies) that make a release of MifosX under the ASF unlikely in the
near future.

Any optimists out there who see things differently and would prefer to
communicate their view?  I'll gladly pass the task on to you...  If you
need any tips on how to do it, feel free to ask.

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>

Move mifosforge.jira.com/wiki to Apache?

[Myrle Krantz]

Hey all,

I noticed we still have lots of info on mifosforge.jira.com/wiki that could 
also be in our Apache wiki space. Do you all want it to stay where it is, or do 
you want it hosted in the Apache project?

Greets from the New Mexico/Texas border,
Myrle 

Sent from my iPhone

Fwd: [DRAFT] Incubator PMC Board Report - August 2016

[Myrle Krantz]

Hello Finerators,

Given that I let you all know that I wouldn't be able to submit the report this 
August, and given that we all, together, are responsible for submitting the 
report, I'm deeply disappointed, that nothing (not even the partially complete 
report I prepared a month ago) got submitted.

Greetings from Southern Colorado with spotty reception,
Myrle

Sent from my iPhone

Begin forwarded message:

> From: "John D. Ament" 
> Date: 6. August 2016 um 19:12:48 GMT-6
> To: "gene...@incubator.apache.org" 
> Subject: [DRAFT] Incubator PMC Board Report - August 2016
> Reply-To: gene...@incubator.apache.org
> 
> Below is the current draft of the incubator board report.  There's still a
> few podlings who haven't reported.
> 
> Incubator PMC report for August 2016
> 
> The Apache Incubator is the entry path into the ASF for projects and
> codebases wishing to become part of the Foundation's efforts.
> 
> < narrative >
> 
> * Community
> 
>  New IPMC members:
> 
>  - None
> 
>  People who left the IPMC:
> 
>  - None
> 
> * New Podlings
> 
>  - SensSoft
>  - Traffic Control
> 
> 
> * Graduations
> 
>  The board has motions for the following:
> 
> 
> 
> * Releases
> 
>  The following releases entered distribution during the month of
>  July:
> 
>  - Apache Trafodion 2.0.1-incubating
>  - Apache Atlas 0.7-incubating
>  - Apache Ranger 0.6.0-incubating
>  - Apache Eagle 0.4.0-incubating
> 
> 
> * IP Clearance
> 
> 
> 
> * Legal / Trademarks
> 
> 
> 
> * Infrastructure
> 
> 
> 
> * Miscellaneous
> 
> 
> 
> * Credits
> 
>  - Report Manager:
> 
>  Summary of podling reports 
> 
> * Still getting started at the Incubator
> 
>  - CarbonData
>  - DistributedLog
>  - Juneau
>  - Pirk
>  - Pony Mail
>  - SensSoft
>  - Trafic Control
> 
> * Not yet ready to graduate
> 
>  No release:
> 
>  - Blur
>  - CMDA
>  - Guacamole
>  - Impala
>  - iota
>  - PredictionIO
>  - Quickstep
>  - S2Graph
> 
>  Community growth:
> 
>  - Beam
>  - Eagle
>  - Fluo
>  - Joshua
>  - Slider
>  - SystemML
> 
> 
> * Ready to graduate
> 
>  The Board has motions for the following:
> 
> 
> 
> * Did not report, expected next month
> 
>  - Fineract
>  - Quarks
>  - Toree
> 
> --
>   Table of Contents
> BatchEE
> Beam
> Blur
> CarbonData
> Climate Model Diagnostic Analyzer
> DistributedLog
> Eagle
> Fineract
> Fluo
> Guacamole
> Impala
> iota
> Joshua
> Juneau
> OpenAz
> Pirk
> Pony Mail
> PredictionIO
> Quarks
> Quickstep
> S2Graph
> SensSoft
> Sirona
> Slider
> SystemML
> Tamaya
> Toree
> Traffic Control
> Unomi
> 
> --
> 
> 
> BatchEE
> 
> BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a
> set of useful extensions for this specification.
> 
> BatchEE has been incubating since 2013-10-03.
> 
> Three most important issues to address in the move towards graduation:
> 
>  1. -
>  2.
>  3.
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> 
>  No
> 
> How has the community developed since the last report?
> 
>  We got several new users and interest in advanced integration (in
>  particular our GUI).
> 
> How has the project developed since the last report?
> 
>  Not much but it is quite stable and no new spec was out since last report
>  so it behaves as expected.
> 
> Date of last release:
> 
>  2015-12-08
> 
> When were the last committers or PMC members elected?
> 
> 
> 
> Signed-off-by:
> 
>  [ ](batchee) Jean-Baptiste Onofré
>  [ ](batchee) Olivier Lamy
>  [X](batchee) Mark Struberg
> 
> Shepherd/Mentor notes:
>  struberg: I think this podling is ready to graduate.
> 
>  johndament: Report is basically empty
> 
> 
> 
> Beam
> 
> Apache Beam is an open source, unified model and set of language-specific
> SDKs for defining and executing data processing workflows, and also data
> ingestion and integration flows, supporting Enterprise Integration Patterns
> (EIPs) and Domain Specific Languages (DSLs). Beam pipelines simplify the
> mechanics of large-scale batch and streaming data processing and can run on
> a number of runtimes such as Apache Flink, Apache Gearpump, Apache Spark,
> and Google Cloud Dataflow (a cloud service). Beam also brings SDKs in
> different languages, allowing users to easily implement their data
> integration processes.
> 
> Beam has been incubating since 2016-02-01.
> 
> Three most important issues to address in the move towards graduation:
> 
>  1. Additional and continued Beam releases
>  2. Grow the community of Beam users and contributors
>  3. Add to and improve upon documentation, code samples, and project
> website
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> None.
> 
> How has the community developed since the last report?
> 
>  * 425 closed/merged pull requests
>  * High e

Re: [Vote] Address API inclusion in Fineract

[Myrle Krantz]

+1

> On 07.07.2016, at 16:15, Nayan Ambali  wrote:
> 
> +1
> 
> 
> Thanks and Regards,
> Nayan Ambali
> +91 9591996042
> skype: nayangambali
> 
>> On Thu, Jul 7, 2016 at 7:34 PM, Nikhil Pawar  wrote:
>> 
>> Hello All,
>> 
>> You must be aware of the discussion which is been happening in the
>> community since last week regarding Address API. I wanted to start
>> development of this module as soon as possible(already running behind
>> scheduled because of the delayed response from credit bureaus) .
>> Please find the wiki links they have been updated with the latest
>> discussion.
>> Wiki link:
>> 
>> https://mifosforge.jira.com/wiki/display/projects/Technical+Description+of+Address+API
>> 
>> Requirements spec:
>> https://mifosforge.jira.com/wiki/display/MIFOSX/Address
>> 
>> In case you have any feedback, please write as soon as possible and we
>> will look in to.
>> If you find things are ok(for the first release),I would request you to
>> vote for its inclusion.
>> 
>> 
>> 
>> 
>> Regards,
>> Nikhil
>> 

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

[Myrle Krantz]

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  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=commit;h=a62620811975f88e9741732c3cb04838dc44b634
>>
>> *Source Files:*
>>
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.3.1-incubating/
>>
>> *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ß  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-+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
>> >
>>
>
>

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

[Myrle Krantz]

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=commit;h=a62620811975f88e9741732c3cb04838dc44b634
>
> *Source Files:*
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.3.1-incubating/
>
> *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ß  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-+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
> >
>

Board Report July -> August

[Myrle Krantz]

Hi all,

I made a mistake.  The Fineract incubator board report is not due until
August.  I have moved the wiki page to
https://cwiki.apache.org/confluence/display/FINERACT/2016-08+August+Report
to reflect the August due date.  Anyone is welcome to add to or change the
report until the report is due in August.

Since I will be at a conference at that time, I will not be able to submit
it.  Please decide who will submit it instead.  Keep in mind that you will
have to get karma for wiki.apache.org before you can submit.

Greets,

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

Reminder: Apache Board Report July

[Myrle Krantz]

Please add your content to the Apache Board Report for July by 8pm CET
today.

https://cwiki.apache.org/confluence/display/FINERACT/2016-07+July+Report

Greets,


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

July Board Report

[Myrle Krantz]

Hi all,

as before, I've set up a wiki page for us to collaborate on the July Board
Report.  You can find it here:
https://cwiki.apache.org/confluence/display/FINERACT/2016-07+July+Report

I've filled in some content out of my head, but others know more so please
(please, please) don't treat my content as holy scripture.  Delete my
content and replace it at will.

As an aside, I really hope that by the next report we can include mention
of a release, and maybe even a new contributor.  I feel that we as a
community are a bit stuck.

Greets from the Voreifel, Germany,

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

Re: Address API docs

[Myrle Krantz]

Thanks Nayan,

I'm just trying to understand is all.  Where do potential values for
"state_province_id" come from?

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 Mon, Jul 4, 2016 at 4:16 PM, Nayan Ambali  wrote:

> Dear Nikhil,
>
> It would be nice if you can document it in wiki and share the link here :)
> as reference for discussion.
>
> Thanks
> Nayan Ambali
>
>
>
> Thanks and Regards,
> Nayan Ambali
> +91 9591996042
> skype: nayangambali
>
> On Mon, Jul 4, 2016 at 7:15 PM, Nikhil Pawar  wrote:
>
>> Hello Myrle,
>>
>> Thank you for your response.I did not take into account ISO identifiers
>> for country_id field.
>> However, now, as recommended by you, the code-code values would in
>> accordance with ISO standard.
>> Is there any thing else you would like to be in compliance with ISO?
>>
>> Regards,
>> Nikhil
>>
>> On Mon, Jul 4, 2016 at 7:01 PM, Myrle Krantz  wrote:
>>
>>> Hi Nikhil,
>>>
>>> Is the country id the ISO-3166-1 country numeric identifier?
>>>
>>> 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 Mon, Jul 4, 2016 at 2:55 PM, Nikhil Pawar  wrote:
>>>
>>>> Hello Markus,Myrle,Adi,Nazeer
>>>>
>>>>
>>>> As we have agreed in previous mail chain regarding adding of Address
>>>> API as part of core product, I thought of completing its development prior
>>>> to other dependent modules.
>>>>
>>>> I have come up with REST API docs for this module and wanted your
>>>> feedback.Kindly provide your feedback as soon as possible, since  this is a
>>>> pre-requisite for other modules. Please note that I have added an
>>>> additional field 'is_active' to support address change of same type of
>>>> address( and also to keep track of past address for audit purpose).
>>>>
>>>>
>>>>
>>>>1. Create new address for client:
>>>>
>>>>
>>>> POST https://DomainName/api/v1/clients/{clientid}/address/
>>>>
>>>> *Sample request:*
>>>>
>>>>
>>>> POST address
>>>>
>>>> Content-Type: application/json Request Body:
>>>>
>>>> {
>>>>
>>>> "address_type": 1,
>>>>
>>>> "street": "507 west street",
>>>>
>>>> "address_line_1": "apt no 5",
>>>>
>>>> "address_line_2": "opposite to college park",
>>>>
>>>> "city":"Dallas",
>>>>
>>>> "state_province_id":1,
>>>>
>>>> "country_id":2,
>>>>
>>>> "postal_code":"40041",
>>>>
>>>> }
>>>>
>>>>
>>>>
>>>> 2. Retrieve all addresses of all types for particular client:
>>>>
>>>>
>>>> GET https://DomainName/api/v1/clients/{clientid}/address/
>>>>
>>>>
>>>> *Sample response:*
>>>>
>>>>
>>>> [
>>>>
>>>> {
>>>>
>>>>   "clientId":1,
>>>>
>>>>   "addressId":2,
>>>>
>>>> "address_type": 1,
>>>>
>>>> "street": "507 west street",
>>>>
>>>> "address_line_1": "apt no 5",
>>>>
>>>> "address_line_2": "opposite to college park",
>>>>
>>>> "city":"Dallas",
>>>>
>>>> "state_province_id":1,
>>>>
>>>> "country_id":2,
>>>>
>>>> "postal_code":"40041",
>>>>
>>>> "is_active":1
>>>>
>>>> },
>>>>
>>>> {
>>>>
>>>>   "clientId":2,
>>>>
>>>>   "addressId":3,
&

Re: Address API docs

[Myrle Krantz]

Hi Nikhil,

Is the country id the ISO-3166-1 country numeric identifier?

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 Mon, Jul 4, 2016 at 2:55 PM, Nikhil Pawar  wrote:

> Hello Markus,Myrle,Adi,Nazeer
>
>
> As we have agreed in previous mail chain regarding adding of Address API
> as part of core product, I thought of completing its development prior to
> other dependent modules.
>
> I have come up with REST API docs for this module and wanted your
> feedback.Kindly provide your feedback as soon as possible, since  this is a
> pre-requisite for other modules. Please note that I have added an
> additional field 'is_active' to support address change of same type of
> address( and also to keep track of past address for audit purpose).
>
>
>
>1. Create new address for client:
>
>
> POST https://DomainName/api/v1/clients/{clientid}/address/
>
> *Sample request:*
>
>
> POST address
>
> Content-Type: application/json Request Body:
>
> {
>
> "address_type": 1,
>
> "street": "507 west street",
>
> "address_line_1": "apt no 5",
>
> "address_line_2": "opposite to college park",
>
> "city":"Dallas",
>
> "state_province_id":1,
>
> "country_id":2,
>
> "postal_code":"40041",
>
> }
>
>
>
> 2. Retrieve all addresses of all types for particular client:
>
>
> GET https://DomainName/api/v1/clients/{clientid}/address/
>
>
> *Sample response:*
>
>
> [
>
> {
>
>   "clientId":1,
>
>   "addressId":2,
>
> "address_type": 1,
>
> "street": "507 west street",
>
> "address_line_1": "apt no 5",
>
> "address_line_2": "opposite to college park",
>
> "city":"Dallas",
>
> "state_province_id":1,
>
> "country_id":2,
>
> "postal_code":"40041",
>
> "is_active":1
>
> },
>
> {
>
>   "clientId":2,
>
>   "addressId":3,
>
> "address_type": 1,
>
> "street": "100 west street",
>
> "address_line_1": "apt no 7",
>
> "address_line_2": "opposite to college park",
>
> "city":"Dallas",
>
> "state_province_id":1,
>
> "country_id":2,
>
> "postal_code":"40041",
>
> "is_active":0
>
> }
>
> ]
>
>
>
> 3. Retreive all addresses of particular type for specified client
>
>
> GET https://DomainName/api/v1/clients/{clientid}/address/{addtypId}
>
> *Sample response:*
>
>
> [
>
> {
>
>   "clientId":2,
>
>   "addressId":2,
>
> "address_type": 1,
>
> "street": "507 west street",
>
> "address_line_1": "apt no 5",
>
> "address_line_2": "opposite to college park",
>
> "city":"Dallas",
>
> "state_province_id":1,
>
> "country_id":2,
>
> "postal_code":"40041",
>
> "is_active":0
>
> },
>
> {
>
>   "clientId":2,
>
>   "addressId":2,
>
> "address_type": 1,
>
> "street": "100 west street",
>
> "address_line_1": "apt no 7",
>
> "address_line_2": "opposite to college park",
>
> "city":"Dallas",
>
> "state_province_id":1,
>
> "country_id":2,
>
> "postal_code":"40041",
>
> "is_active":1
>
> }
>
> ]
>
>
>
>
>
>
> 4. Retrieve active address of particular type for specified clientid
>
>
> GET
> https://DomainName/api/v1/clients/{clientid}/address/{addtypId}?command=active
>
>
> Sample response:
>
> {
>
> "clientId":1,
>
>   "addressId":2,
>
> "address_type": 1,
>
> "street": "507 west street",
>
> "address_line_1": "apt no 5",
>
> "address_line_2": "opposite to college park",
>
> "city":"Dallas",
>
> "state_province_id":1,
>
> "country_id":2,
>
> "postal_code":"40041",
>
> "40041",
>
> "is_active":1
>
> }
>
>
>
> 5. update:
>
>
> update particular "active" address of client
>
> PUT https://DomainName/api/v1/clients/{clientid}/address/{addtypId}
>
> sample request
>
> {
>
> is_active:false
>
> }
>
>
> supported fields:
>
> address line fields,addresstypeid,is_active
>
>
>
> Regards,
>
> Nikhil
>
>

Re: Requirement for adding new status

[Myrle Krantz]

Would we add a status for every check that needs to be performed before
approving a loan application?  Are there any additional steps in planning?

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, Jun 29, 2016 at 2:43 PM, Nayan Ambali 
wrote:

> +1 for additional status
>
>
> Thanks and Regards,
> Nayan Ambali
> +91 9591996042
> skype: nayangambali
>
> On Wed, Jun 29, 2016 at 6:07 PM,  wrote:
>
>> Hello Devs,
>>
>> In order to park in applications which have completed the credit check, I
>> felt a need of an additional status for loan application.
>> Currently, if a loan application is in pending status, the status is 100.
>> The moment it is approved it changes to 200.
>> However, if a organisation has made credit check mandatory before the
>> approving the loan application, we need to have an additional status.
>> Kindly let me know your reviews on adding a new status to the loan
>> application.
>>
>>
>> [image: Inline image]
>>
>>
>>
>> Regards,
>> Nikhil
>>
>
>

Re: How to Unsubscribe

[Myrle Krantz]

Hi Cole,

Either unsubscribe from dev@fineract.incubator.apache.org or set up a
filter based on the subject line of the e-mail.

If your question is actually: "Why do these mails have to be sent to the
dev list?" Presumably it's because people subscribed to the dev list are
typically those who can merge pull requests.

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 Thu, Jun 9, 2016 at 12:48 PM, Cole Trumbo  wrote:

> How do I unsubscribe from emails with subject lines of "[GitHub]
> incubator-fineract pull request #XX ..."?
> --
> Best,
> Cole Trumbo
> 435.773.1488 mobile
>

Read up on Cloud Foundry

[Myrle Krantz]

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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: Microservices release question

[Myrle Krantz]

Hi Nayan,

Good question.  I would expect it to consist of the tenant provisioning
service, the security service, and the supporting libraries for the command
bus, and a couple of other shared functionality tidbits.

As to Adi's wish to keep them together in one repository: it's not my
preferred solution, but I see several arguments for it and I can live with
it if that's what you guys prefer.

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, Jun 1, 2016 at 6:51 AM, Nayan Ambali  wrote:

> Adi, Myrle,
>
> When you say core, what core is constituted of?
>
> Thanks
> Nayan Ambali
>
>
>
> Thanks and Regards,
> Nayan Ambali
> +91 9591996042
> skype: nayangambali
>
> On Wed, Jun 1, 2016 at 12:28 AM, Roman Shaposhnik 
> wrote:
>
> > On Tue, May 31, 2016 at 6:51 AM, Adi Raju
> >  wrote:
> > > My thought would be to keep core microservices as single repo and
> single
> > release.
> >
> > FWIW: that'd be my preference as well.
> >
> > Thanks,
> > Roman.
> >
>

Re: Microservices release question

[Myrle Krantz]

Adi,

I like your approach.  So within the core set of microservices, we'd take
solution 2 right?

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 Tue, May 31, 2016 at 7: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 <
> http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>
>
> 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

Re: Microservices release question

[Myrle Krantz]

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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>


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
> > <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
> >
> --
> Regards,
> Ashok
>
> Sent from mobile device
>

Microservices release question

[Myrle Krantz]

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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

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

[Myrle Krantz]

I would expect anyone working on one of these services to have rights to
the other services too, and to participate in conversations about the
others. I wouldn't want to segment the community.  Just the code.  I like
being able to download artifacts instead of code to speed up a build.  I
like having just the code I am working on open.  I appreciate the
discipline having physically separate code bases adds to my own thought
processes.  I also would prefer to be able to upgrade each of the
microservices independently of the others in a deployment (within
reasonable limits) and be able to correspond one branch in one repository
to one microservice release.

I doubt the incubator community would want to review up to 10 releases for
one community, so I don't think a 1 TLP :: 1 microservice approach would be
accepted by Apache.

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, May 25, 2016 at 10:37 AM, Keith Woodlock 
wrote:

> Myrle, Markus,
>
> For lots of reasons it would make sense for the Fineract Platform to be one
> project (on apache and github).
>
> If the main driver for saying service-per-repository is about putting in a
> physical barrier to stop developers leaking code or abstractions into one
> another then I think having just one code repository / project is fine and
> you need to split the 'Fineract Platform' into a number of sub-projects
> (folders) for each service.
>
> A quick example of that type of setup would be:
> https://github.com/ewolff/microservice, the microservice-demo folder is
> split into the various services that compose it etc
>
> regards,
> Keith.
>
> On Wed, May 25, 2016 at 8:48 AM, Ross Gardler 
> wrote:
>
> > At Apache we don't like umbrella projects - that is projects that can
> > stand on their own as separate projects being gathered together under
> > one-uber project. This tends to be damaging for community development.
> > However, there is nothing wrong with one project having multiple
> "services"
> > each represented as a separate project within a parent PMC when those
> > services are not useful projects outside of Fineract itself.
> >
> > Another warning sign is if the services start to build their own
> > governance structure within the parent project. Merit earned on one part
> of
> > a Top Level Project gives equal authority over all other parts. Now you
> may
> > have social policies that say "don't touch code you don't understand" but
> > you can't have byelaws that prevent it. If it is necessary to separate
> your
> > community in this way then you probably need to have multiple TLPs.
> >
> > So the answer is "it depends ;-)
> >
> > Ross
> >
> > > -Original Message-
> > > From: Markus Geiß [mailto:markus.ge...@live.de]
> > > Sent: Wednesday, May 25, 2016 12:29 AM
> > > To: dev@fineract.incubator.apache.org
> > > Subject: RE: [MENTORS] multiple repos for one Apache Product?
> > >
> > > 
> > > > 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

Re: Microservices

[Myrle Krantz]

In answer to Nayan's mail:

Our shared end goal is not a beautiful architecture.  Our shared goal is
also not to make any particular company financially successful.  Our goal
is to make it possible for those people who today have no access to banking
services to attain access to secure and timely savings and loans.  This is
the key to expanding economies and bridging financial hard times.  This is
the single most effective way to fight poverty!  I believe we are in
agreement here.

I loved the article from Joel you included.  The author has many valuable
points, but he unfortunately assumes that all rewrites are initiated to
cure code rot.  If that were true, then he would be right.  When I read
Joel's article the first time, roughly a year after it was written, I was
working on my first major software project: a successful rewrite of a major
feature.  Microsoft's main business model is based on finding successful
products, then re-writing them better.  Many successful Open Source
projects, including several at Apache, do the same.  After reading Joel's
article, I decided to think about what makes some rewrites more successful
than the examples Joel listed.

Here are some factors which can make a rewrite necessary:

* new platforms for a piece of software to run on.  new standards software
needs to conform to.  (Smart phones, cloud)
* new libraries available.  A rewrite can actually *increase* code reuse be
replacing hand-spun implementations.
* significant new use cases.  For example a massive increases in scale, or
features which could not have been foreseen at the time of the original
implementation.
* the skill set of programmers available for work on the project undergoes
a significant change.  For example, it is nearly impossible to find COBOL
programmers for old banking systems.
* anti-patterns have begun to self-propagate faster than they can be fixed,
making it impossible to expunge them from the code.  I loved Joel's
"FuckedString" example.  That sounds like this sort of problem.  This is
the only kind of code rot I would admit as a reason.  For everything else
you're right; fix it where you find it.

Here is what can make a rewrite successful:

* Continue releasing versions of the previous gen of a product or feature
while the rewrite begins.
* Don't duplicate all features.  To counter Joel's example: it would be
wasteful to reproduce support for Windows '95.
* Choose an architecture and technologies that are attractive to potential
contributors. (Especially important in an open source project.)
* Carefully choose which use cases to focus on when migrating deployments.
It may make sense to focus on use cases *not* well-covered by the previous
gen, thus giving both product generations space to live during the
transition.

Joel's first example is particularly telling (written in April of 2000).
Yes the Netscape rewrite was a company-destroying failure.  The first time
I read that article it was on Internet Explorer (major rearchitecting for
version 8 released March 2009).  This time I read it on Safari (first
release January 2003).  I'm writing this e-mail using Firefox (first
release November 2004).  Some of you may use Chrome (first release
September 2008).

Apparently rewriting a web browser is not quite the death sentence Joel
believes it to be.  I leave it as an exercise to the reader to imagine why
some of these rewrites are successful, applying the criteria listed above.

Here's how I would apply these generalizations to Fineract:

* new platforms: Microservices are the best architecture for a cloud-based
or hosted platform.  These are much less expensive then purchasing the
hardware yourself.
* new libraries: For saving commands, Markus and I have picked Cassandra.
This would obviate any need for caching (mentioned by Vishwas), because
Cassandra handles that naturally via its distributed architecture.  For
service discovery we've picked Eureka and Ribbon.  For java-based APIs to
talk to REST, we've chosen Feign.  (There are more details here that I'm
leaving out because this e-mail is getting too long.)  The transition to
Cassandra and asynchronous commands alone, should give us a huge
performance boost.
* significant new use cases.  Here most of what we are seeing is increases
in scale.

* continue releasing previous gen: we are all in agreement here.
* carefully choose which features to duplicate: Fineract has always focused
on loans.  I believe the next gen should start by focusing on savings.
* attractive architecture and technologies: I suspect a lot of devs out
there are interested in Microservices and the accompanying technologies
right now.
* choose use cases: This area still needs considerable work.

So that's all for this week.  You won't hear from me again till next
Monday.  I'll try to make the focus more educational in my next e-mail.
(Feel free to wish for a topic.)

Greet

[MENTORS] multiple repos for one Apache Product?

[Myrle Krantz]

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?

Greetings from the Voreifel,
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>

Re: Microservices

[Myrle Krantz]

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 can use Eureka and Ribbon for service discovery if we are deploying
multiple instances of a given service.  I’ve also really liked what I’ve
seen of docker.  I would like to ultimately build a docker image for each
service, and make the build scripts for those docker images part of the
service projects.

This leaves me with a question for a mentor: 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?

Lest I create a false impression, this is not my design alone.  Markus
created most of it.  I’ve been refining it together with him.


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 Mon, May 23, 2016 at 11:16 AM, Keith Woodlock 
wrote:

> Mryle,
>
> >> Now please excuse me while I get back to just doing it. ; o)
>
> Ok sounds like decision made that yourself and Markus will be going ahead
> with this :)
>
> Can you let us know where you will be checking in the code so we in the
> community can follow along.
>
> Given your are going to go ahead with developing a proof of concept
> starting from a blank canvas it might be good to layout a scope and some
> goals to get to in a time-boxed period of time. I would suggest something
> like:
>
> 1) A single microservice implemented from API to Database including
> deployment related capabilities
>
> The emphasis on this would be to show off the tech approach/pattern
> involved in implementing a microservice over the domain of the microservice
> so feel free to choose a simpler area
>
> This hopefully could be provided in a mu

Re: HEADS UP: JIRA email patterns are changing over the weekend

[Myrle Krantz]

Thank you very very very much Roman!

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 Sat, May 21, 2016 at 5:24 AM, Roman Shaposhnik 
wrote:

> Hi!
>
> to alleviate some of the chattiness concerns of dev@fineract
> I'll be changing JIRA setup in such a way that the first email
> for every issue will go to dev@fineract but all the future ones
> will go to issues@fineract.
>
> May sure to subscribe to that other mailing list if you still want
> the emails.
>
> Thanks,
> Roman.
>

Re: Microservices

[Myrle Krantz]

Hi,

I won't be able to write a complete answer.  Nobody would read an e-mail
that long.  So I’m going to “nibble” at it bit by bit.

Of the three approaches Keith lists, I favor the third approach "Re-imagine
the fineract platform from ground up again (hope it solves the problems you
see and doesnt introduce new problems)".  I've been in the industry long
enough (16 years) to understand that there are significant risks in
"starting over from scratch", and I hope that we can learn enough from the
existing code base to avoid some of those road bumps.


I would imagine multiple phases here:

1.) Markus and I start work on a framework, and basic services for this
refactoring.  Everyone else continues work on MifosX

2.) We do a proof of concept with a bare bones implementation.

3.) Report to the community based on what we learn by end of this year.

4.) Based on what we have learned, together with the community consider
migration of:

   a.) New microservice-based code into the Fineract community.

   b.) Community man-power from the existing codebase to the new code base.

   c.) Existing customer data into the new microservice-based code via
migration scripts.

   d.) Existing projects onto the new microservice-based product.

   e.) The community app onto the new microservice-based backend.

We can do a subset of the above migration steps.  There are several
possible approaches.  But I really want to do this together with the
Fineract community.  There’s much know-how here, and I think we can copy
code over wholesale in many areas, and in other areas plagiarize good
architectural decisions and problem-solving approaches which the existing
Fineract codebase illustrates.

Because I want to do this with the Fineract community, I want to start
getting people in the community up to speed on the concepts early.  Even if
people decide they don't like this approach, nobody will be poorer for the
extra information.  I also very much want people’s feedback on where they
see problems with our approach. I haven’t given much in the way of
specifics yet; I want people to have some background first. Which was the
reason for my original mail.

Now please excuse me while I get back to just doing it. ; o)

(My next email will come tomorrow, and will focus on Roman’s very important
deployment question.)

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 Thu, May 19, 2016 at 11:49 PM, Keith Woodlock 
wrote:

> Hi Mryle,
>
> Thanks for your detailed reply, I added my comments (please remember I am
> not involved in code base for sometime so might be missing alot) below but
> its a pretty long email so I summarise what I think here:
>
> The decision to move from one approach to developing a system to another is
> a big one and not without its costs. I am not really for or against it and
> I'll be interested in seeing how things turn out whichever way the
> community decides to go. If everyone really feels it will be the solution
> to any problems that exist then they should go for it. The risk of course
> is that its a very tech solution to things.
>
> I think Chris Richardson does a good job on http://microservices.io of
> outlining the differences between the monolith (
> http://microservices.io/patterns/monolithic.html) and the microservices (
> http://microservices.io/patterns/microservices.html) approaches.
>
> You probably have the following 3 directions you can go:
>
> 1) Stay with the monolith and attempt to tackle the problems you see with
> the system (domain, performance etc)
>
> 2) Gradually move services from the monolith into microservices (hope it
> solves the problems you see and doesnt introduce new problems)
>
> 3) Re-imagine the fineract platform from ground up again (hope it solves
> the problems you see and doesnt introduce new problems)
>
> - Approach 2 sounds like it will be a drawn out affair and take a long time
> to reach the end with the drawback of having to support both approaches
>
> - Approach 3 it too would be alot of effort but you could use something
> like http://eventuate.io/ to get to a poof of concept faster
>
>
>
>
> Before devling into some of the points you raised I wanted to highlight two
> aspects of the fineract platform:
>
> *- Everything is exposed a HTTP API / Service*
>
> All the functionality that exists in the platform is or should be exposed
> by a HTTP API. This HTTP API is a techonology agonistic contract that
> developers can build their apps/clients on or integrate with easily.
>
> Developers can choose to build their apps/clients in any technology they
> wish and to use as much or as little

Re: Microservices

[Myrle Krantz]

microservice is such a functionality group.

There are other advantages to microservices that are more general in nature
and not specific to our use case; read the links I sent in my first e-mail
and you should start to get a feel for it.

(Roman, I’m going to watch and see if your questions are answered as we
discuss.  If not I’ll circle back to them, and see what was missed.)

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 Thu, May 19, 2016 at 1:01 AM, Keith Woodlock 
wrote:

> Hi Myrle,
>
> First off, thanks for starting a conversation around this within the
> fineract dev community. I was wondering when this was going to come up.
>
> Rather than delving into the technicalities of what a microservice is and
> isnt I thought it would be good if the people proposing this could go into
> a bit of detail here of why they are proposing it, the pros and cons of a
> microservice approach over the existing approach and the existing problems
> within fineract/mifos that it will help solve/remove.
>
> I think that could promote some good discussion and following on from that
> later we could delve into how it could be achieved if going that direction.
>
> regards,
> Keith.
>
>
> On Wed, May 18, 2016 at 11:14 PM, Roman Shaposhnik 
> wrote:
>
> > Hi Myrle,
> >
> > microservices are indeed a nice architectural pattern with an
> exponentially
> > growing adoption in the enterprise. It typically leverages some kind of a
> > PaaS
> > solution to be available for deployment. My current understanding is that
> > your
> > deployment model today is a traditional appserver. Are you going to
> change
> > that?
> > If so, what will be the deployment requirements for the project?
> >
> > Thanks,
> > Roman.
> >
> > On Wed, May 18, 2016 at 2:35 AM, Myrle Krantz  wrote:
> > > Hi all,
> > >
> > > As many of you know Markus and I are thinking through a rearchitecting
> of
> > > Fineract into microservices. Markus gave some of you a preview into our
> > > work at the Mifos tech conference in Amsterdam in March (those of you
> who
> > > are interested and weren’t able to attend can check it out on Youtube
> > here:
> > > https://www.youtube.com/watch?v=iIrnZpoNZ9A -- my apologies for the
> poor
> > > video quality)
> > >
> > > If you want to get an introductory understanding of what a microservice
> > is,
> > > this is a good place to go:
> > >
> > > http://martinfowler.com/articles/microservices.html
> > >
> > > If there is interest, (and I have time), I’ll try to send you more
> > > information about my ideas as they take shape.
> > >
> > > Greets,
> > >
> > > Myrle
> > >
> > > P.S.  Here’s Spring’s take on this:
> > > https://spring.io/blog/2015/07/14/microservices-with-spring
> > >
> > >
> > > *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>
> >
>

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

[Myrle Krantz]

+1 (non-binding)

With apologies to the dev@fineract list who got this twice.

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 Tue, May 17, 2016 at 3:00 PM, Nazeer Shaik <
nazeer.sh...@confluxtechnologies.com> wrote:

> Hello Incubator PMC,
>
> The Apache Fineract community has voted and approved the proposal to
> release Apache Fineract 0.1.2 (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.1.2-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/201605.mbox/%3CCAOSe2yvmLHfHtQnPTH1j777AEakKrVw7pzTe%2BWu%3DVw_fw9RnJA%40mail.gmail.com%3E
>
> [VOTE RESULT] Thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201605.mbox/%3CCAOSe2yuyYv4bp7PL52JvzchdANGS-waXxteFKboY%2BaUZSw_YPQ%40mail.gmail.com%3E
>
> The release candidate to be voted on is available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/apache-fineract-0.1.2-incubating-src.tar.gz
>
> Git tag for the release:
> https://github.com/apache/incubator-fineract/tree/0.1.2-incubating
> or
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-fineract.git;a=tree;h=refs/heads/0.1.2-incubating;hb=refs/heads/0.1.2-incubating
>
> Source release verification:
> PGP signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/apache-fineract-0.1.2-incubating-src.tar.gz.asc
> MD5/SHA Hash:
>
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/apache-fineract-0.1.2-incubating-src.tar.gz.md5
> Keys to verify the signature of the release artifact are available at:
> https://dist.apache.org/repos/dist/dev/incubator/fineract/KEYS
>
> Release Notes:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62697180
>
> Build verification steps can be found at:
>
> https://github.com/apache/incubator-fineract/blob/0.1.2-incubating/README.md
> or refer 'README.md' in apache-fineract-0.1.2-incubating-src.tar.gz
>
>
> *Note: *1) This is a source only release with no binaries, with
> instructions on how to
> build/test the application.
> 2) 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 doesn't include any source or binary from Hibernate. A
> separate mail will be initiated to get legal VP approval.
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Here is my +1 (non binding)
>
> Thanks,
> Nazeer
>

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

[Myrle Krantz]

+1 (non binding)


*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 Tue, May 17, 2016 at 3:00 PM, Nazeer Shaik <
nazeer.sh...@confluxtechnologies.com> wrote:

> Hello Incubator PMC,
>
> The Apache Fineract community has voted and approved the proposal to
> release Apache Fineract 0.1.2 (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.1.2-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/201605.mbox/%3CCAOSe2yvmLHfHtQnPTH1j777AEakKrVw7pzTe%2BWu%3DVw_fw9RnJA%40mail.gmail.com%3E
>
> [VOTE RESULT] Thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201605.mbox/%3CCAOSe2yuyYv4bp7PL52JvzchdANGS-waXxteFKboY%2BaUZSw_YPQ%40mail.gmail.com%3E
>
> The release candidate to be voted on is available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/apache-fineract-0.1.2-incubating-src.tar.gz
>
> Git tag for the release:
> https://github.com/apache/incubator-fineract/tree/0.1.2-incubating
> or
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-fineract.git;a=tree;h=refs/heads/0.1.2-incubating;hb=refs/heads/0.1.2-incubating
>
> Source release verification:
> PGP signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/apache-fineract-0.1.2-incubating-src.tar.gz.asc
> MD5/SHA Hash:
>
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/apache-fineract-0.1.2-incubating-src.tar.gz.md5
> Keys to verify the signature of the release artifact are available at:
> https://dist.apache.org/repos/dist/dev/incubator/fineract/KEYS
>
> Release Notes:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62697180
>
> Build verification steps can be found at:
>
> https://github.com/apache/incubator-fineract/blob/0.1.2-incubating/README.md
> or refer 'README.md' in apache-fineract-0.1.2-incubating-src.tar.gz
>
>
> *Note: *1) This is a source only release with no binaries, with
> instructions on how to
> build/test the application.
> 2) 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 doesn't include any source or binary from Hibernate. A
> separate mail will be initiated to get legal VP approval.
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Here is my +1 (non binding)
>
> Thanks,
> Nazeer
>

Microservices

[Myrle Krantz]

Hi all,

As many of you know Markus and I are thinking through a rearchitecting of
Fineract into microservices. Markus gave some of you a preview into our
work at the Mifos tech conference in Amsterdam in March (those of you who
are interested and weren’t able to attend can check it out on Youtube here:
https://www.youtube.com/watch?v=iIrnZpoNZ9A -- my apologies for the poor
video quality)

If you want to get an introductory understanding of what a microservice is,
this is a good place to go:

http://martinfowler.com/articles/microservices.html

If there is interest, (and I have time), I’ll try to send you more
information about my ideas as they take shape.

Greets,

Myrle

P.S.  Here’s Spring’s take on this:
https://spring.io/blog/2015/07/14/microservices-with-spring


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

Re: [RESULT][VOTE] [FINERACT] 0.1.2-incubating for release

[Myrle Krantz]

I believe you have a vote in this too Nazeer.  So that would presumably be
total +5.

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 Thu, May 12, 2016 at 7:49 AM, Nazeer Shaik <
nazeer.sh...@confluxtechnologies.com> wrote:

> Hello all,
>
> Voting for Apache Fineract 0.1.2-incubating is now closed.The release has
> passed this step of the process. The vote breakdown is as follows:
>
> +1 Myrle Krantz
> +1 Markus Geiß
> +1 Adi Raju
> +1 Nayan Ambali
>
> Total: +4
>
> We can now call a vote on the general@incubator list.
> Thank you all for inputs and votes.
>
> Thanks,
> Nazeer
>

[MENTORS] Re: [VOTE] [FINERACT] 0.1.2-incubating for release

[Myrle Krantz]

The hibernate issue, I was merely mentioning for completeness

gradlewrapper.jar, I don't want changed in this release, but for the next
release: MENTORS? Is there a reason we shouldn't include a
gradlewrapper.jar in our release zip?

w.r.t password: it'd be really nice if we could override that property for
the gradle scripts.  It should theoretically be possible. I'll look into it
for the next release. As a matter of habit, I don't like using default
passwords.

w.r.t. MySQL version: you're right.  My bad.

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 Mon, May 9, 2016 at 2:15 PM, Nazeer Shaik <
nazeer.sh...@confluxtechnologies.com> wrote:

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

[MENTORS] Re: Jim Jagielski: Will you be our mentor?

[Myrle Krantz]

Hey Mentors,

Is there anything else we need to do to make Jim our mentor in the context
of the broader Apache organization?  Or is that invitation all we need?

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 Thu, May 5, 2016 at 3:30 PM, Myrle Krantz  wrote:

> Oh dear. It's good we understand each other. :o)
>
> Greets,
> Myrle
>
> > On 05.05.2016, at 13:49, Jim Jagielski  wrote:
> >
> > 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
> >>
> >>
> >
>

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

[Myrle Krantz]

+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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>


On Mon, May 9, 2016 at 5:59 AM, Roman Shaposhnik 
wrote:

> Hi Nazeer,
>
> thanks for working on the release. VOTE threads on ASF releases
> typically follow a particular pattern of what information they communicate
> to make the voting process easier. Here's a good example:
>
> http://mail-archives.apache.org/mod_mbox/incubator-madlib-dev/201602.mbox/%3CCAKBQfzT6fn1Mzhs9gtEBC6m_pe=U1qzaRLF2rV5=7wpgv-s...@mail.gmail.com%3E
>
> Also, I would highly encourage you to start a wiki page documenting
> the process of releases to make next RM's job easier. Once again,
> here's a good (if only exhaustive!) example:
>  https://cwiki.apache.org/confluence/display/GEODE/Release+proccess
>
> Thanks,
> Roman.
>
> On Fri, May 6, 2016 at 5:03 AM, Nazeer Shaik
>  wrote:
> > Hi all,
> >
> > We have resolved windows line feeds issue and prepared 0.1.2-incubating
> > release for FINERACT. The files are hosted at
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/
> >
> > The git repository is located at
> > https://github.com/apache/incubator-fineract/tree/0.1.2-incubating
> >
> > Again, this is source only release with no binaries, with instructions on
> > how to build/test the application.
> >
> > I call for VOTING for this release and this voting closes by Wednesday
> > (11-May-2016) evening.
> >
> > Thanks,
> > Nazeer
>

Re: Jim Jagielski: Will you be our mentor?

[Myrle Krantz]

Oh dear. It's good we understand each other. :o)

Greets,
Myrle 

> On 05.05.2016, at 13:49, Jim Jagielski  wrote:
> 
> 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  
>> 
>> 
> 

Jim Jagielski: Will you be our mentor?

[Myrle Krantz]

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
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

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

[Myrle Krantz]

-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  wrote:

> +1
>
> On Wed, May 4, 2016, 12:43 AM Ed Cable  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
> > >
> >
>

recent call to vote on release on general incubator list

[Myrle Krantz]

Hi all,

I propose that we withdraw the recent call to vote on the general incubator
list, to fix the problems in the release, and get clearance from legal on
the hibernate issues.  If no one objects by the end of my work day (around
3pm CET), I'll send the withdrawal on the general incubator list, in order
to be respectful of people's time there.

Greets,


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

Fwd: Final draft of the Incubator Board Report - April 2016

[Myrle Krantz]

Hi Fineract Mentors,

Is it normal that only one mentor signs off on an incubator's report? Or do
I need to worry that there was something wrong with the report to cause
Greg and Ross to choose not to sign off on it?  If the latter is the case,
please share your feedback.

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>


-- Forwarded message --
From: John D. Ament 
Date: Mon, Apr 11, 2016 at 12:56 PM
Subject: Final draft of the Incubator Board Report - April 2016
To: "gene...@incubator.apache.org" 


All,

Below is the final draft of the board report.  Remember, mentors have until
tomorrow end of day to sign off on podlings.  We have two podlings with no
sign offs - Mnemonic and Wave.  Wave is especially concerning since its
just Upyavira now.

I've extended the months of the non-reporting podlings at this point.  I
would ask that if any of those podlings do create a report between now and
end of day tomorrow, to first reach out on the general@ list to confirm.
I'd rather a podling miss a report than hurry a report that few people can
review.

- John
-

Incubator PMC report for April 2016

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

There are 56 podlings currently undergoing incubation.  We have four
podlings planning to graduate this month and added five podlings to
the roster.  As is typical in the months following the annual members
meeting, we have seen a jump in the number of IPMC members join.

* Community

  New IPMC members:

  - Marvin Humphrey
  - Suneel Marthi
  - Uma Gangumalla
  - Henri Yandell

  People who left the IPMC:

  - Jukka Zitting

* New Podlings

  - Airflow
  - Gearpump
  - Mnemonic
  - Omid
  - Tephra

* Graduations

  The board has motions for the following:

  - Apex
  - Johnzon
  - TinkerPop
  - AsterixDB

* Releases

  The following releases entered distribution during the month of
  March:

  2016-03-02 Apache MRQL 0.9.6-incubating
  2016-03-03 Apache Apex Malhar 3.3.1-incubating
  2016-03-03 Apache Htrace 4.1.0-incubating
  2016-03-04 Apache Mynewt-0.8.0-b1-incubating
  2016-03-09 Apache Kudu 0.7.1-incubating
  2016-03-10 Apache Ranger 0.5.2-incubating
  2016-03-11 Apache Taverna-language 0.15.1-incubating
  2016-03-11 Apache Taverna-osgi 0.2.1-incubating
  2016-03-14 Apache MADlib v1.9alpha-rc2-incubating
  2016-03-21 Apache Unomi 1.0.0-incubating
  2016-03-25 Apache Mynewt 0.8.0-b2-incubating
  2016-03-27 Apache FreeMarker 2.3.24-incubating


* IP Clearance

  - Apache Sling Dynamic Includes

* Legal / Trademarks



* Infrastructure

  We continue to struggle with podling report reminders.
  A suite of manual reminders were sent, some were received
  by the podlings and some were not.

* Miscellaneous

  Based on group understanding, it appears that the Concerted podling
  will retire soon.



* Credits

  - Report Manager:

--- Summary of podling reports 

* Still getting started at the Incubator

  - Gearpump
  - iota
  - Joshua
  - Metron
  - Milagro
  - Mnemonic
  - Quarks

* Not yet ready to graduate

  No release:

  - Hawq
  - Horn
  - Impala
  - Rya
  - Toree

  Community growth:

  - Fineract
  - Geode
  - MADlib
  - Ranger
  - Wave

* Ready to graduate

  The Board has motions for the following:

  - Apex
  - Johnzon
  - TinkerPop
  - AsterixDB

* Did not report, expected next month

  - Concerted
  - OpenAz
  - Tephra

--
   Table of Contents
Apex
BatchEE
Concerted
DataFu
Fineract
FreeMarker
Gearpump
Geode
HAWQ
HORN
HTrace
Impala
iota
Johnzon
Joshua
MADlib
Metron
Milagro
Mnemonic
Mynewt
ODF Toolkit
Quarks
Ranger
Rya
Sirona
Toree

--


Apex

Apex is an enterprise grade native YARN big data-in-motion platform that
unifies stream processing and batch processing.

Apex has been incubating since 2015-08-17.

Three most important issues to address in the move towards graduation:

  None. Incubator graduation VOTE passed: https://s.apache.org/qhTf

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  Resolution to establish Apache Apex as TLP submitted to board.

How has the community developed since the last report?

  The community is very engaged with the development of the project.  We see
  continious uptick in mailing list participaton (2180 messages on dev@ for
  March, 122+ subscribers).

  The community discussed graduation, addressed outstanding issues and
  completed VOTE.

  The community has been active building additional meetup groups:
  http:/

Re: [VOTE] [FINERACT] 0.1.0.incubating for release

[Myrle Krantz]

I looked at the NOTICE (1) and LICENSE (2) files, and I was surprised to
see BSD- and MIT-licensed libraries mentioned in the NOTICE file.  If I
understand the guidelines (3) correctly, these are not necessary.  Also if
I understand the guidelines correctly, it is desirable to put as little as
possible into the NOTICE file as possible.  After looking at the Eclipse
license (4), I suspect libraries licensed under that also do not require an
entry in the NOTICE file.  For the other licenses, I'm even less certain
than I am for these.  So I hope our mentors will weigh in on these three
licenses (BSD, MIT, and Eclipse), and once we have that, I'll check the
remaining ones.

In the LICENSE file, I was surprised to see the entire license text of all
these licenses copied in.  If I understand the guidelines correctly, it is
preferable to include a link to these licenses within the distribution
unless they are very short (which most of them aren't).

I especially feel uneasy about the copying in of GPL into the LICENSE
text.  Not sure how rational that is, but I just don't like it.

Neither of these are blockers for release, depending on how well we want to
do it on our first go.  I would give the release a +1 vote despite these
objections, if we could resolve the GPL license issue.  I would expect us
to resolve the other issues before our next release though (if they
actually are issues -- again: *MENTORS?*).

Greets from the Voreifel, Germany,
Myrle Krantz


1.)
https://github.com/apache/incubator-fineract/blob/0.1.0-incubating/NOTICE
2.)
https://github.com/apache/incubator-fineract/blob/0.1.0-incubating/LICENSE
3.) http://www.apache.org/dev/licensing-howto.html#permissive-deps
4.) http://www.eclipse.org/org/documents/edl-v10.php


*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 Tue, Apr 12, 2016 at 7:04 AM, Adi Raju 
wrote:

> Release files correspond to the following fineract source branch
> https://github.com/apache/incubator-fineract/tree/0.1.0-incubating
>
> Regards,
> Adi
>
>
> -Original Message-
> From: Markus Geiß [mailto:markus.ge...@live.de]
> Sent: 12 April 2016 10:08
> To: dev@fineract.incubator.apache.org
> Subject: RE: [VOTE] [FINERACT] 0.1.0.incubating for release
>
> +1
>
> Maybe we can add a link to the GitHub tag, so it is easier to validate the
> content.
>
> > Date: Mon, 11 Apr 2016 16:15:16 +0530
> > Subject: [VOTE] [FINERACT] 0.1.0.incubating for release
> > From: raj...@apache.org
> > To: dev@fineract.incubator.apache.org
> >
> > Hello All,
> >
> > I have prepared the files for first release of FINERACT.
> > The files are hosted at
> > https://dist.apache.org/repos/dist/dev/incubator/fineract/
> > This is a source only release with no binaries, with instructions on
> > how to build/test the application.
> >
> > Being the first release, I request the mentors to review the content,
> > especially of LICENSE, NOTICE, DISCLAIMER files.
> >
> > We have multi-tenancy architecture. Main DB contains list of tenants
> > and their corresponding DB names and access details.
> > These tenant specific DB can even have variations in schema. Access to
> > these tenant databases are created at runtime.
> > Enhancement of entity objects corresponding to tenant databases fails
> > with OpenJPA. This is because access to DB metadata of tenant
> > databases is not available at boot time.
> > We couldn't migrate to OpenJPA and avoid dependency on
> Hibernate(LGPLv2.1).
> > Since we are making source only distribution, can we get waiver on
> > this dependency?
> >
> > With this background, I call for formal VOTING for the first release.
> >
> > Regards,
> > Adi Raju
>
>
>

Re: SUGGESTION: Create a Developer/Contributor FAQ on Fineract Wiki

[Myrle Krantz]

+1

> On 06.04.2016, at 18:57, Adi Raju  wrote:
> 
> +1
>> On 06-Apr-2016 10:23 pm, "Nayan Ambali"  wrote:
>> 
>> We need it Ed, +1
>> 
>>> On Wed, Apr 6, 2016, 10:00 PM Ed Cable  wrote:
>>> 
>>> Hi all,
>>> 
>>> In helping out a fellow contributor, Saransh though it best to have one
>>> centralized place where we could document common small problems/errors
>> and
>>> their corresponding fixes. He had suggested a FAQ and I think that's a
>>> great idea.
>>> 
>>> While this existed on our old Mifos wiki and our AnswerHub site with
>>> MifosConnect, we need to have this as part of our Fineract wiki. I would
>>> suggest creating a new page in the Contributor's Zone
>> https://cwiki.apache.org/confluence/display/FINERACT/Contributor%27s+Zone
>>> <
>> https://web.chilipiper.com/link/mifos.org/57053886e4b02bbec5bc215a?link=aHR0cHMlM0ElMkYlMkZjd2lraS5hcGFjaGUub3JnJTJGY29uZmx1ZW5jZSUyRmRpc3BsYXklMkZGSU5FUkFDVCUyRkNvbnRyaWJ1dG9yJTI1MjdzJTJCWm9uZQ==
>>> as a Developer or Contributor FAQ.
>>> 
>>> If others agree, Saransh, please take the lead in creating such a page -
>> I
>>> can assist as needed.
>>> 
>>> Ed
>>> 
>>> --
>>> *Ed Cable*
>>> Director of Community Programs, Mifos Initiative
>>> edca...@mifos.org
>>> <
>> https://web.chilipiper.com/link/mifos.org/57053886e4b02bbec5bc215a?link=bWFpbHRvJTNBZWRjYWJsZSU0MG1pZm9zLm9yZw==
>>> |
>>> Skype: edcable | Mobile: +1.484.477.8649
>>> 
>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>> <
>> https://web.chilipiper.com/link/mifos.org/57053886e4b02bbec5bc215a?link=aHR0cCUzQSUyRiUyRm1pZm9zLm9yZw==
>>> 
>>> <
>> https://web.chilipiper.com/link/mifos.org/57053886e4b02bbec5bc215a?link=aHR0cCUzQSUyRiUyRmZhY2Vib29rLmNvbSUyRm1pZm9z
>>> 
>>> <
>> https://web.chilipiper.com/link/mifos.org/57053886e4b02bbec5bc215a?link=aHR0cCUzQSUyRiUyRnd3dy50d2l0dGVyLmNvbSUyRm1pZm9z
>> 

April Board Report

[Myrle Krantz]

I've now copied our board report into the official board report:

https://wiki.apache.org/incubator/April2016

Thank you Sander and Ed for contributing the content.

Greets from the Voreifel,Germany


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

April Board Report

[Myrle Krantz]

Hi all,

This month I'm trying something different for the April Fineract Board
report:

https://cwiki.apache.org/confluence/display/FINERACT/2016-04+April+Report

I've set it up COMPLETELY EMPTY.

I'm just as concerned at the lack of participation as Greg and Markus are.
I ask everyone on this list to add at least one sentence to the board
report by Tuesday evening.  More is also welcome.  I don't care if it
overlaps  with what others have written, I'll take care of that after
you've added your content.  Tuesday I'll edit it to give it a consistent
style and structure and to remove any redundancies, but if there's nothing
in it by then, it'll stay that way.

If it has to be sent to the board empty, then that's important information
too.  After we've sent it off, I'll ask you if you want to take the same
approach next month.

Greets from the Voreifel, Germany,


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