Re: Machine Learning Requirements Discussion: WAS [Introducing Maha Refai, Mifos Initiative volunteer, working on requirements for credit analytics]

[James Dailey]

Hi Maha -

I've been spending some time thinking about this for some business areas
adjacent to financial inclusion.

In financial inclusion, and financial services in general, there are of
course, many areas where some ML or even basic analysis would do a
wonderful job.

For Mifos I believe a key thing that is needed is the ability to extract
data in meaningful structures (flattened in appropriate ways) and within a
reasonable taxonomy of credit, accounting, and consumer terms.  Perhaps
that means making data more easily discoverable via APIs.  I also suspect
that permission and rights management to data - with screens for privacy
(or anonymizing) are needed.

Related, one concept I've come across is the ability for third parties to
get the "results" of machine learning models without actually getting
access to the data and to apply that in a kind of federated data approach -
where the models are trained up and then "call home" with the results.
This would imply that it is important for the data access APIs to be
structured consistently and with backwards compatibility.

For ML to work there needs to be some other "big" data sets related
together.  You may be interested in a recent world bank conference where a
bunch of new ML applications were introduced:
https://blogs.worldbank.org/developmenttalk/artificial-intelligence-economic-development-conference-roundup-27-presentations


Happy to get on a call at some point.

Thanks,
James


On Wed, Apr 4, 2018 at 10:45 AM Ed Cable  wrote:

> Maha,
>
> I wanted to resurrect this thread and invigorate some discussion as we have
> a GSOC prospect, Lalit, considering a project focused around machine
> learning. I've added him to this thread and going to also add the team at
> BowPI so they can contribute to the discussion around what they've done on
> the machine learning front to date.
>
> Ed
>
> On Thu, Nov 9, 2017 at 4:58 PM, Avik Ganguly 
> wrote:
>
> > Hi Maha,
> >
> > Welcome to the community! Cognitev looks like an exciting startup. The
> > current developments going on in Fineract; i.e. the upcoming Fineract CN
> > application probably makes this the right time to initiate this effort as
> > ML services usually needs to scale separately and the independence of
> > choosing a separate tech stack for these services matters a lot.
> >
> > Adding a bit on one part that Ed wrote - "monitor ongoing credit risk".
> In
> > the microfinance space, the most recurring problem statement I have heard
> > from risk heads in India is collusion by loan officers to meet targets
> with
> > / without ringleaders which is addressable through early warning systems.
> > Looking forward to working with you.
> >
> > With best regards,
> > Avik Ganguly.
> >
> > On Wed, Nov 8, 2017 at 9:02 PM, Ed Cable  wrote:
> >
> > > Hello community,
> > >
> > >
> > > I wanted to introduce to you a new Mifos Initiative volunteer, Maha
> Refai
> > > , who will be reaching out to
> > > members of the community to document their requirements around credit
> and
> > > risk analytics using artificial intelligence, machine learning and big
> > > data.
> > >
> > > Maha Refai is currently the co-founder and Head of Product at
> Cognitev, a
> > > startup based in UAE and Egypt using artificial intelligence to
> automate
> > > digital marketing. After receiving her bachelor’s in Computer Science
> she
> > > spent the past ten years primarily in product and project management in
> > the
> > > entertainment industry while also getting her MBA.
> > >
> > >
> > > She will be reaching out to some of you directly and documenting her
> > > findings on the wiki. But if you'd like to be part of this requirements
> > > gathering process, please reply to this thread and we'll set up a call.
> > >
> > > Based on her knowledge and expertise of artificial intelligence and
> > machine
> > > learning, she is going to help  develop a product management strategy
> for
> > > both the current Apache Fineract platform and the upcoming Apache
> > Fineract
> > > CN application framework that identifies and prioritizes what are the
> > > necessary microservices and modules that are part of the framework or
> > > integrated with it to facilitate the capture of data, the analysis of
> it,
> > > and the ability to make decisions upon the data.
> > >
> > > In short, volunteer will help identify how these predictive analytical
> > > tools along with big data can help make Mifos and Apache Fineract more
> > of a
> > > loan origination system, as well as means of developing a credit score
> to
> > > manage and monitor ongoing credit risk. You can see below for some more
> > of
> > > the specific tasks she’ll be undertaking.
> > >
> > >
> > >-
> > >
> > >Research on existing open source tools or libraries that could be
> > >integrated for machine learning such as weka.
> > >-
> > >
> > >Research on alternative credit scoring tools that are in existence
> > >-
> > >
> > >

Re: Code Standard Questions from BOWPI

[Awasum Yannick]

Hello Angel, Ed,

Going through the wiki pages, I found these posts which might be helpful to
the coding style issue:

https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68714707


https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions

https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

https://cwiki.apache.org/confluence/display/FINERACT/Becoming+a+Committer

To the best of my knowledge, If there are some classes within the platform
which do not follow some of these conventions then that seems to be code
which violates our conventions and that needs to be fixed.

What you can do in this case is reformat the code base in accordance to the
above specifications and send a PR.

For the rest of your query, I will give way for a more experienced
contributor to Fineract 1.x to respond.

Thanks.
Awasum Yannick



On Wed, Apr 4, 2018 at 6:46 PM, Ed Cable  wrote:

> I wanted to bump this thread back up to the top as unfortunately it's gone
> without reply and the team at BOWPI who are really itching to contribute
> are blocked.
>
> Could any of our committers please respond to their queries regarding
> coding standards so they can unblock themselves and make the changes they
> want to contribute to Fineract.
>
> Thanks,
>
> Ed
>
> On Fri, Mar 2, 2018 at 9:09 AM, Angel Cajas  wrote:
>
> > Hi, my name is Angel Cajas from BOWPI and I am making some changes to
> some
> > features developed by us some months ago to use the same methods and
> > validations already existing for some tasks such  as the permission
> > settings, the serialization and deserialization of json request and data
> > retrieval from database.
> >
> >
> > While I'm doing those changes and start to understand how fineract works
> > some questions have arisen for me. Some may seem trivial but I would like
> > to get some feedback from the dev team if it is possible.
> >
> >
> > -According to the wiki, the coding conventions used for this project are
> > based on Google Java Style
> >  of coding.
> Regarding
> > block indentation and column limit, I've seen in some classes those rules
> > aren't followed and I would like to know if another coding style that
> isn't
> > documented is being used as of right now or should I reformat the code
> > after modifying some existing classes.
> >
> >
> > -I've seen there isn't an option to create new permissions, so these must
> > be inserted directly into the database, should these be included in a new
> > script file or is there another way to add this new objects that I am not
> > aware of?
> >
> >
> > -When reading using a ReadService a RowMapper is being used to transform
> > the query result to a DTO I guess it's because the result shouldn't
> include
> > all the fields saved in the database and just show the relevant ones and
> > I've seen some queries are saved as strings. It's OK to use repository
> > functions to retrieve such data instead of saving the query in a string?
> > and It is necessary all the entities be converted to DTOs when using the
> > ReadPlatformService?
> >
> >
> > I would really appreciate your help and feedback and thanks for your
> > attention.
> >
> >
> >
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>

Re: Time to delete mifosio

[Awasum Yannick]

Hello Myrle, Ed,

With Mifos IO deleted, is this not the right time to make a hard turn and
change all import statements in Apache Fineract CN to use the
org.apache.fineract.cn aritifact ids within the Java components? Given we
can no longer have the mifos io artifact ids.

Myrle, last time you pointed out backward compatibility issues. With Mifos
IO deleted, is that still the case?

Are there Vendors out there using Fineract CN who will have makor problems
because of this change? Lets discuss this critical step.

This solves the problem of people needing to have Mifos IO artifacts in
their local .m2 artifactory before running the current demo server and
other sub projects.

Thanks
Awasum Yannick


On Wed, Apr 4, 2018 at 6:37 PM, Ebenezer Graham 
wrote:

> Feeling nostalgic right now. The name Mifos brings back good memories but
> this means progress :)
>
>
> *Best Regards,*
>
> *Ebenezer Graham*
>
> *BSc (Hons) Computing*
>
>
> [image: EmailSignature.png]
>
> Beau Plan Business Park | West Building
>
> Pamplemousses |  Mauritius
>
>
> 
> ​​ 
> www.pactmart.com | Freelancing made easy.
> ​
> skype:
> ​ebenezer.graham
> ​ | Phone:
> +230 5840 9206
> GitHub  | LinkedIn
>  | Twitter
>  | Facebook
>  | Personal Website / CV
> 
>
>
> *“Practice isn’t the thing you do once you’re good. It’s the thing you do
> that makes you good.”*
> -*Malcolm Gladwell*
>
>
>
> On 4 April 2018 at 20:51, Kevin A. McGrail  wrote:
>
> > So, Ed brings the gasoline, Myrle throws the match.  You guys are quite a
> > wrecking crew (that is a compliment in engineering speak).  +1
> >
> > --
> > Kevin A. McGrail
> > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> > On Wed, Apr 4, 2018 at 12:45 PM, Myrle Krantz  wrote:
> >
> > > Hey all,
> > >
> > > Summary: Burn it down.  Burn it *all* down.
> > >
> > > Details:
> > >
> > > mifosio has become a metaphorical "attractive nuisance" (1).  Some of
> > > the repositories there have over 40 forks.  Some people have made
> > > issue reports or pull requests against those repositories which should
> > > have been made against Fineract CN.
> > >
> > > I've taken one last stroll thru those repos in which I did the
> following:
> > > A.) Checked that the latest changeset is in the corresponding apache
> > > repository.
> > > B.) Checked that all of the data from the wiki is in the apache
> > confluence.
> > > C.) Checked there are no outstanding PRs -- if they are merge them
> over.
> > > D.) Checked there are no outstanding issues -- if they are close them
> > > and request the user to create new issues in the apache Jira.
> > >
> > > I had already done A and B, but I obviously missed some, so it was
> > > worthwhile to go through it again.
> > >
> > > The cases in which I had to cleanup were:
> > > * demo-server:
> > >- copied over liseri's changes
> > >- commented on open ticket (I didn't have the necessary rights in
> > > that case to close the ticket) to direct the github user to apache
> > > ticketing and apache mailing lists.
> > > * command
> > >   - pulled in 2 missing changesets from before the move (total 8
> > > lines, so no biggy)
> > > * default-setup
> > >   - merged 1 PR to fineract-cn-default-setup (A 1 liner so not a big
> > > deal.).  The PR's still open on mifosio because I don't have
> > > privileges in that project.
> > > * identity
> > >   - closed an old issue.
> > > * portfolio
> > >   - closed 3 old issues.
> > >
> > > The only repositories that I didn't check were the three integration
> > > test repositories.  These are all fairly out-of-date, and mostly just
> > > duplicate things that are already found in the demo-server.  Some of
> > > them don't even compile in their current form.  I recommend deleting
> > > these without replacement.
> > >
> > > Ed: I believe you are the only one who can delete these repositories.
> > > If you would do so quickly, you would save me having to spend *hours*
> > > going through these repositories carefully again.  Because these are
> > > public repositories, the 40 plus forks will continue to exist, so you
> > > aren't risking anyone's work.  And for just in case, I did take a
> > > 'snapshot' under a user named mifosio-04-04-2018, so we won't lose
> > > anything.
> > >
> > > If you can't do this today or tomorrow, Ed, please give me the
> > > necessary privileges in mifosio to do it myself.  My github account is
> > > myrle-krantz.
> > >
> > > Best Regards,
> > > Myrle
> > >
> > >
> > > 1.) https://en.wikipedia.org/wiki/Attractive_nuisance_doctrine
> > >
> >
>

Re: Code Standard Questions from BOWPI

[Ed Cable]

I wanted to bump this thread back up to the top as unfortunately it's gone
without reply and the team at BOWPI who are really itching to contribute
are blocked.

Could any of our committers please respond to their queries regarding
coding standards so they can unblock themselves and make the changes they
want to contribute to Fineract.

Thanks,

Ed

On Fri, Mar 2, 2018 at 9:09 AM, Angel Cajas  wrote:

> Hi, my name is Angel Cajas from BOWPI and I am making some changes to some
> features developed by us some months ago to use the same methods and
> validations already existing for some tasks such  as the permission
> settings, the serialization and deserialization of json request and data
> retrieval from database.
>
>
> While I'm doing those changes and start to understand how fineract works
> some questions have arisen for me. Some may seem trivial but I would like
> to get some feedback from the dev team if it is possible.
>
>
> -According to the wiki, the coding conventions used for this project are
> based on Google Java Style
>  of coding. Regarding
> block indentation and column limit, I've seen in some classes those rules
> aren't followed and I would like to know if another coding style that isn't
> documented is being used as of right now or should I reformat the code
> after modifying some existing classes.
>
>
> -I've seen there isn't an option to create new permissions, so these must
> be inserted directly into the database, should these be included in a new
> script file or is there another way to add this new objects that I am not
> aware of?
>
>
> -When reading using a ReadService a RowMapper is being used to transform
> the query result to a DTO I guess it's because the result shouldn't include
> all the fields saved in the database and just show the relevant ones and
> I've seen some queries are saved as strings. It's OK to use repository
> functions to retrieve such data instead of saving the query in a string?
> and It is necessary all the entities be converted to DTOs when using the
> ReadPlatformService?
>
>
> I would really appreciate your help and feedback and thanks for your
> attention.
>
>
>


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

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

Machine Learning Requirements Discussion: WAS [Introducing Maha Refai, Mifos Initiative volunteer, working on requirements for credit analytics]

[Ed Cable]

Maha,

I wanted to resurrect this thread and invigorate some discussion as we have
a GSOC prospect, Lalit, considering a project focused around machine
learning. I've added him to this thread and going to also add the team at
BowPI so they can contribute to the discussion around what they've done on
the machine learning front to date.

Ed

On Thu, Nov 9, 2017 at 4:58 PM, Avik Ganguly 
wrote:

> Hi Maha,
>
> Welcome to the community! Cognitev looks like an exciting startup. The
> current developments going on in Fineract; i.e. the upcoming Fineract CN
> application probably makes this the right time to initiate this effort as
> ML services usually needs to scale separately and the independence of
> choosing a separate tech stack for these services matters a lot.
>
> Adding a bit on one part that Ed wrote - "monitor ongoing credit risk". In
> the microfinance space, the most recurring problem statement I have heard
> from risk heads in India is collusion by loan officers to meet targets with
> / without ringleaders which is addressable through early warning systems.
> Looking forward to working with you.
>
> With best regards,
> Avik Ganguly.
>
> On Wed, Nov 8, 2017 at 9:02 PM, Ed Cable  wrote:
>
> > Hello community,
> >
> >
> > I wanted to introduce to you a new Mifos Initiative volunteer, Maha Refai
> > , who will be reaching out to
> > members of the community to document their requirements around credit and
> > risk analytics using artificial intelligence, machine learning and big
> > data.
> >
> > Maha Refai is currently the co-founder and Head of Product at Cognitev, a
> > startup based in UAE and Egypt using artificial intelligence to automate
> > digital marketing. After receiving her bachelor’s in Computer Science she
> > spent the past ten years primarily in product and project management in
> the
> > entertainment industry while also getting her MBA.
> >
> >
> > She will be reaching out to some of you directly and documenting her
> > findings on the wiki. But if you'd like to be part of this requirements
> > gathering process, please reply to this thread and we'll set up a call.
> >
> > Based on her knowledge and expertise of artificial intelligence and
> machine
> > learning, she is going to help  develop a product management strategy for
> > both the current Apache Fineract platform and the upcoming Apache
> Fineract
> > CN application framework that identifies and prioritizes what are the
> > necessary microservices and modules that are part of the framework or
> > integrated with it to facilitate the capture of data, the analysis of it,
> > and the ability to make decisions upon the data.
> >
> > In short, volunteer will help identify how these predictive analytical
> > tools along with big data can help make Mifos and Apache Fineract more
> of a
> > loan origination system, as well as means of developing a credit score to
> > manage and monitor ongoing credit risk. You can see below for some more
> of
> > the specific tasks she’ll be undertaking.
> >
> >
> >-
> >
> >Research on existing open source tools or libraries that could be
> >integrated for machine learning such as weka.
> >-
> >
> >Research on alternative credit scoring tools that are in existence
> >-
> >
> >Interviews with existing community members to discuss systems they
> have
> >implemented or how they’ve been able to do these data analysis using
> the
> >existing Mifos toolset.
> >-
> >
> >Interviews with existing community members who have desires to
> implement
> >credit scoring capabilities and big data analytics including
> stewarding
> >these conversations over our community mailing lists and documenting
> >requirements publicly
> >-
> >
> >Recommendations on a strategy of how to implement such features -
> either
> >as core microservices or ancillary modules.
> >-
> >
> >User Stories on actual features to implement within the framework or
> >product.
> >-
> >
> >Brainstorm and list out the insight and information that could be
> >analyzed so we can understand what data about the customer, their
> > behavior
> >and their loans must be captured in the framework and platform.
> >
> >
> >
> > --
> > *Ed Cable*
> > President/CEO, Mifos Initiative
> > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> > <(484)%20477-8649>
> >
> > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> >   
> >
>



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

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

Re: Time to delete mifosio

[Ebenezer Graham]

Feeling nostalgic right now. The name Mifos brings back good memories but
this means progress :)


*Best Regards,*

*Ebenezer Graham*

*BSc (Hons) Computing*


[image: EmailSignature.png]

Beau Plan Business Park | West Building

Pamplemousses |  Mauritius



​​ 
www.pactmart.com | Freelancing made easy.
​
skype:
​ebenezer.graham
​ | Phone:
+230 5840 9206
GitHub  | LinkedIn
 | Twitter
 | Facebook
 | Personal Website / CV



*“Practice isn’t the thing you do once you’re good. It’s the thing you do
that makes you good.”*
-*Malcolm Gladwell*



On 4 April 2018 at 20:51, Kevin A. McGrail  wrote:

> So, Ed brings the gasoline, Myrle throws the match.  You guys are quite a
> wrecking crew (that is a compliment in engineering speak).  +1
>
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
> On Wed, Apr 4, 2018 at 12:45 PM, Myrle Krantz  wrote:
>
> > Hey all,
> >
> > Summary: Burn it down.  Burn it *all* down.
> >
> > Details:
> >
> > mifosio has become a metaphorical "attractive nuisance" (1).  Some of
> > the repositories there have over 40 forks.  Some people have made
> > issue reports or pull requests against those repositories which should
> > have been made against Fineract CN.
> >
> > I've taken one last stroll thru those repos in which I did the following:
> > A.) Checked that the latest changeset is in the corresponding apache
> > repository.
> > B.) Checked that all of the data from the wiki is in the apache
> confluence.
> > C.) Checked there are no outstanding PRs -- if they are merge them over.
> > D.) Checked there are no outstanding issues -- if they are close them
> > and request the user to create new issues in the apache Jira.
> >
> > I had already done A and B, but I obviously missed some, so it was
> > worthwhile to go through it again.
> >
> > The cases in which I had to cleanup were:
> > * demo-server:
> >- copied over liseri's changes
> >- commented on open ticket (I didn't have the necessary rights in
> > that case to close the ticket) to direct the github user to apache
> > ticketing and apache mailing lists.
> > * command
> >   - pulled in 2 missing changesets from before the move (total 8
> > lines, so no biggy)
> > * default-setup
> >   - merged 1 PR to fineract-cn-default-setup (A 1 liner so not a big
> > deal.).  The PR's still open on mifosio because I don't have
> > privileges in that project.
> > * identity
> >   - closed an old issue.
> > * portfolio
> >   - closed 3 old issues.
> >
> > The only repositories that I didn't check were the three integration
> > test repositories.  These are all fairly out-of-date, and mostly just
> > duplicate things that are already found in the demo-server.  Some of
> > them don't even compile in their current form.  I recommend deleting
> > these without replacement.
> >
> > Ed: I believe you are the only one who can delete these repositories.
> > If you would do so quickly, you would save me having to spend *hours*
> > going through these repositories carefully again.  Because these are
> > public repositories, the 40 plus forks will continue to exist, so you
> > aren't risking anyone's work.  And for just in case, I did take a
> > 'snapshot' under a user named mifosio-04-04-2018, so we won't lose
> > anything.
> >
> > If you can't do this today or tomorrow, Ed, please give me the
> > necessary privileges in mifosio to do it myself.  My github account is
> > myrle-krantz.
> >
> > Best Regards,
> > Myrle
> >
> >
> > 1.) https://en.wikipedia.org/wiki/Attractive_nuisance_doctrine
> >
>

Re: Time to delete mifosio

[Ed Cable]

I was entering wrong organization name (using display name of Mifos I/O)
instead of mifosio. It's now deleted.

Ed

On Wed, Apr 4, 2018 at 10:30 AM, Ed Cable  wrote:

> Thanks Myrle for taking all the time to do that cleanup and assurance that
> nothing is lost.
>
> I'm attempting to delete the org now but running into some difficulties.
> I'll let you know as soon as it's deleted.
>
> Ed
>
> On Wed, Apr 4, 2018 at 9:51 AM, Kevin A. McGrail 
> wrote:
>
>> So, Ed brings the gasoline, Myrle throws the match.  You guys are quite a
>> wrecking crew (that is a compliment in engineering speak).  +1
>>
>> --
>> Kevin A. McGrail
>> Asst. Treasurer & VP Fundraising, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
>> On Wed, Apr 4, 2018 at 12:45 PM, Myrle Krantz  wrote:
>>
>> > Hey all,
>> >
>> > Summary: Burn it down.  Burn it *all* down.
>> >
>> > Details:
>> >
>> > mifosio has become a metaphorical "attractive nuisance" (1).  Some of
>> > the repositories there have over 40 forks.  Some people have made
>> > issue reports or pull requests against those repositories which should
>> > have been made against Fineract CN.
>> >
>> > I've taken one last stroll thru those repos in which I did the
>> following:
>> > A.) Checked that the latest changeset is in the corresponding apache
>> > repository.
>> > B.) Checked that all of the data from the wiki is in the apache
>> confluence.
>> > C.) Checked there are no outstanding PRs -- if they are merge them over.
>> > D.) Checked there are no outstanding issues -- if they are close them
>> > and request the user to create new issues in the apache Jira.
>> >
>> > I had already done A and B, but I obviously missed some, so it was
>> > worthwhile to go through it again.
>> >
>> > The cases in which I had to cleanup were:
>> > * demo-server:
>> >- copied over liseri's changes
>> >- commented on open ticket (I didn't have the necessary rights in
>> > that case to close the ticket) to direct the github user to apache
>> > ticketing and apache mailing lists.
>> > * command
>> >   - pulled in 2 missing changesets from before the move (total 8
>> > lines, so no biggy)
>> > * default-setup
>> >   - merged 1 PR to fineract-cn-default-setup (A 1 liner so not a big
>> > deal.).  The PR's still open on mifosio because I don't have
>> > privileges in that project.
>> > * identity
>> >   - closed an old issue.
>> > * portfolio
>> >   - closed 3 old issues.
>> >
>> > The only repositories that I didn't check were the three integration
>> > test repositories.  These are all fairly out-of-date, and mostly just
>> > duplicate things that are already found in the demo-server.  Some of
>> > them don't even compile in their current form.  I recommend deleting
>> > these without replacement.
>> >
>> > Ed: I believe you are the only one who can delete these repositories.
>> > If you would do so quickly, you would save me having to spend *hours*
>> > going through these repositories carefully again.  Because these are
>> > public repositories, the 40 plus forks will continue to exist, so you
>> > aren't risking anyone's work.  And for just in case, I did take a
>> > 'snapshot' under a user named mifosio-04-04-2018, so we won't lose
>> > anything.
>> >
>> > If you can't do this today or tomorrow, Ed, please give me the
>> > necessary privileges in mifosio to do it myself.  My github account is
>> > myrle-krantz.
>> >
>> > Best Regards,
>> > Myrle
>> >
>> >
>> > 1.) https://en.wikipedia.org/wiki/Attractive_nuisance_doctrine
>> >
>>
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>


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

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

Re: Time to delete mifosio

[Ed Cable]

Thanks Myrle for taking all the time to do that cleanup and assurance that
nothing is lost.

I'm attempting to delete the org now but running into some difficulties.
I'll let you know as soon as it's deleted.

Ed

On Wed, Apr 4, 2018 at 9:51 AM, Kevin A. McGrail 
wrote:

> So, Ed brings the gasoline, Myrle throws the match.  You guys are quite a
> wrecking crew (that is a compliment in engineering speak).  +1
>
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
> On Wed, Apr 4, 2018 at 12:45 PM, Myrle Krantz  wrote:
>
> > Hey all,
> >
> > Summary: Burn it down.  Burn it *all* down.
> >
> > Details:
> >
> > mifosio has become a metaphorical "attractive nuisance" (1).  Some of
> > the repositories there have over 40 forks.  Some people have made
> > issue reports or pull requests against those repositories which should
> > have been made against Fineract CN.
> >
> > I've taken one last stroll thru those repos in which I did the following:
> > A.) Checked that the latest changeset is in the corresponding apache
> > repository.
> > B.) Checked that all of the data from the wiki is in the apache
> confluence.
> > C.) Checked there are no outstanding PRs -- if they are merge them over.
> > D.) Checked there are no outstanding issues -- if they are close them
> > and request the user to create new issues in the apache Jira.
> >
> > I had already done A and B, but I obviously missed some, so it was
> > worthwhile to go through it again.
> >
> > The cases in which I had to cleanup were:
> > * demo-server:
> >- copied over liseri's changes
> >- commented on open ticket (I didn't have the necessary rights in
> > that case to close the ticket) to direct the github user to apache
> > ticketing and apache mailing lists.
> > * command
> >   - pulled in 2 missing changesets from before the move (total 8
> > lines, so no biggy)
> > * default-setup
> >   - merged 1 PR to fineract-cn-default-setup (A 1 liner so not a big
> > deal.).  The PR's still open on mifosio because I don't have
> > privileges in that project.
> > * identity
> >   - closed an old issue.
> > * portfolio
> >   - closed 3 old issues.
> >
> > The only repositories that I didn't check were the three integration
> > test repositories.  These are all fairly out-of-date, and mostly just
> > duplicate things that are already found in the demo-server.  Some of
> > them don't even compile in their current form.  I recommend deleting
> > these without replacement.
> >
> > Ed: I believe you are the only one who can delete these repositories.
> > If you would do so quickly, you would save me having to spend *hours*
> > going through these repositories carefully again.  Because these are
> > public repositories, the 40 plus forks will continue to exist, so you
> > aren't risking anyone's work.  And for just in case, I did take a
> > 'snapshot' under a user named mifosio-04-04-2018, so we won't lose
> > anything.
> >
> > If you can't do this today or tomorrow, Ed, please give me the
> > necessary privileges in mifosio to do it myself.  My github account is
> > myrle-krantz.
> >
> > Best Regards,
> > Myrle
> >
> >
> > 1.) https://en.wikipedia.org/wiki/Attractive_nuisance_doctrine
> >
>



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

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

Re: Time to delete mifosio

[Kevin A. McGrail]

So, Ed brings the gasoline, Myrle throws the match.  You guys are quite a
wrecking crew (that is a compliment in engineering speak).  +1

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Wed, Apr 4, 2018 at 12:45 PM, Myrle Krantz  wrote:

> Hey all,
>
> Summary: Burn it down.  Burn it *all* down.
>
> Details:
>
> mifosio has become a metaphorical "attractive nuisance" (1).  Some of
> the repositories there have over 40 forks.  Some people have made
> issue reports or pull requests against those repositories which should
> have been made against Fineract CN.
>
> I've taken one last stroll thru those repos in which I did the following:
> A.) Checked that the latest changeset is in the corresponding apache
> repository.
> B.) Checked that all of the data from the wiki is in the apache confluence.
> C.) Checked there are no outstanding PRs -- if they are merge them over.
> D.) Checked there are no outstanding issues -- if they are close them
> and request the user to create new issues in the apache Jira.
>
> I had already done A and B, but I obviously missed some, so it was
> worthwhile to go through it again.
>
> The cases in which I had to cleanup were:
> * demo-server:
>- copied over liseri's changes
>- commented on open ticket (I didn't have the necessary rights in
> that case to close the ticket) to direct the github user to apache
> ticketing and apache mailing lists.
> * command
>   - pulled in 2 missing changesets from before the move (total 8
> lines, so no biggy)
> * default-setup
>   - merged 1 PR to fineract-cn-default-setup (A 1 liner so not a big
> deal.).  The PR's still open on mifosio because I don't have
> privileges in that project.
> * identity
>   - closed an old issue.
> * portfolio
>   - closed 3 old issues.
>
> The only repositories that I didn't check were the three integration
> test repositories.  These are all fairly out-of-date, and mostly just
> duplicate things that are already found in the demo-server.  Some of
> them don't even compile in their current form.  I recommend deleting
> these without replacement.
>
> Ed: I believe you are the only one who can delete these repositories.
> If you would do so quickly, you would save me having to spend *hours*
> going through these repositories carefully again.  Because these are
> public repositories, the 40 plus forks will continue to exist, so you
> aren't risking anyone's work.  And for just in case, I did take a
> 'snapshot' under a user named mifosio-04-04-2018, so we won't lose
> anything.
>
> If you can't do this today or tomorrow, Ed, please give me the
> necessary privileges in mifosio to do it myself.  My github account is
> myrle-krantz.
>
> Best Regards,
> Myrle
>
>
> 1.) https://en.wikipedia.org/wiki/Attractive_nuisance_doctrine
>

Re: Interest in Contributing to Fineract

[Myrle Krantz]

Welcome Kelvin!

If you want a search which returns all the Fineract CN repositories,
this may be helpful:
https://github.com/search?q=org%3Aapache+fineract-cn

Here you can see instructions for building:
https://cwiki.apache.org/confluence/display/FINERACT/How+To+Build+Apache+Fineract+CN

The Fineract CN project is very young, and the number of people
working on it is still quite small, so you will find areas in which
the documentation is missing or in need of improvement.  Please feel
welcome at any time to suggest improvements or make changes yourself.

Best Regards,
Myrle
Committer, Apache Fineract


On Wed, Apr 4, 2018 at 6:11 PM, kelvin ikome  wrote:
> Hi everyone,
>
> I am Kelvin Ikome, a Software Engineer from Buea, Cameroon.
>
> Recently I have been searching for ways to improve my skills by
> contributing to open source projects and Fineract CN seems to be a great
> place for me to start with.
>
> Financial exclusion is a problem faced especially in third world countries
> and I believe Fineract CN is a potential solution which will improve on the
> living standards and impact the lives of thousands of people.
>
> I am proficient in Java and some frameworks like Spring, Spring Boot,
> Jersey (Jax-RS) and as well as some front end technologies and I would be
> happy to contribute to Fineract CN projects during my leisure time.
>
>
> Thanks.
> Kelvin -

Time to delete mifosio

[Myrle Krantz]

Hey all,

Summary: Burn it down.  Burn it *all* down.

Details:

mifosio has become a metaphorical "attractive nuisance" (1).  Some of
the repositories there have over 40 forks.  Some people have made
issue reports or pull requests against those repositories which should
have been made against Fineract CN.

I've taken one last stroll thru those repos in which I did the following:
A.) Checked that the latest changeset is in the corresponding apache repository.
B.) Checked that all of the data from the wiki is in the apache confluence.
C.) Checked there are no outstanding PRs -- if they are merge them over.
D.) Checked there are no outstanding issues -- if they are close them
and request the user to create new issues in the apache Jira.

I had already done A and B, but I obviously missed some, so it was
worthwhile to go through it again.

The cases in which I had to cleanup were:
* demo-server:
   - copied over liseri's changes
   - commented on open ticket (I didn't have the necessary rights in
that case to close the ticket) to direct the github user to apache
ticketing and apache mailing lists.
* command
  - pulled in 2 missing changesets from before the move (total 8
lines, so no biggy)
* default-setup
  - merged 1 PR to fineract-cn-default-setup (A 1 liner so not a big
deal.).  The PR's still open on mifosio because I don't have
privileges in that project.
* identity
  - closed an old issue.
* portfolio
  - closed 3 old issues.

The only repositories that I didn't check were the three integration
test repositories.  These are all fairly out-of-date, and mostly just
duplicate things that are already found in the demo-server.  Some of
them don't even compile in their current form.  I recommend deleting
these without replacement.

Ed: I believe you are the only one who can delete these repositories.
If you would do so quickly, you would save me having to spend *hours*
going through these repositories carefully again.  Because these are
public repositories, the 40 plus forks will continue to exist, so you
aren't risking anyone's work.  And for just in case, I did take a
'snapshot' under a user named mifosio-04-04-2018, so we won't lose
anything.

If you can't do this today or tomorrow, Ed, please give me the
necessary privileges in mifosio to do it myself.  My github account is
myrle-krantz.

Best Regards,
Myrle


1.) https://en.wikipedia.org/wiki/Attractive_nuisance_doctrine

Interest in Contributing to Fineract

[kelvin ikome]

Hi everyone,

I am Kelvin Ikome, a Software Engineer from Buea, Cameroon.

Recently I have been searching for ways to improve my skills by
contributing to open source projects and Fineract CN seems to be a great
place for me to start with.

Financial exclusion is a problem faced especially in third world countries
and I believe Fineract CN is a potential solution which will improve on the
living standards and impact the lives of thousands of people.

I am proficient in Java and some frameworks like Spring, Spring Boot,
Jersey (Jax-RS) and as well as some front end technologies and I would be
happy to contribute to Fineract CN projects during my leisure time.


Thanks.
Kelvin -