Re: Improving Fineract CN a Community survey

[Myrle Krantz]

On Mon, Sep 27, 2021 at 8:33 PM Saransh Sharma 
wrote:

> To summarise the survey
>
> Monolithic versus Micro-services
>
> Right now Fineract CN is a monolithic application although services
> interact with a set of core libs that are acting as dependencies . These
> dependencies need to be maintained alongside the core service
>

Fineract CN is not a monolith and no survey has claimed that.  Stop it
Saransh; you're spreading misinformation.

Best,
Myrle

Re: [DISCUSS] Apache Fineract CN Community Roadmap

[Myrle Krantz]

Saransh,

Can you please stop trying to direct every conversation to your personal
agenda?

Best,
Myrle

On Mon, Sep 27, 2021 at 6:38 PM Saransh Sharma 
wrote:

> Great ,anyone is willing to pick up the above task and complete it in a
> timely manner, I would like to attach a bounty worth 5000 USD here
> with the help of Awasum and PR closing rate. It will be distributed to the
> developers and committers
> Please note pick an issue, discuss them over the Dev mailing list and once
> you get an idea what to do please proceed ahead, Once the work is done in
> terms of the PR open and merged you will receive your bounty amount.
> We can do gitcoin also if you like
> Thanks
>
> On Mon, Sep 27, 2021 at 9:27 PM Awasum Yannick  wrote:
>
>> Hi All,
>>
>> This roadmap was developed in 2019 and acts as a guide for anyone looking
>> to help out on Apache Fineract CN:
>> https://cwiki.apache.org/confluence/display/FINERACT/Apache+Fineract+CN+Community+Roadmap
>>
>> Are there volunteers looking to pick up some tasks based on the above
>> document? Are there blocker issues which are missing in the above document?
>>
>>
>>
>
> --
> Thanks and regards,
>
> Saransh Sharma
> Research Partner
>
> This mail is governed by Muellners®  IT policy.
> The information contained in this e-mail and any accompanying documents
> may contain information that is confidential or otherwise protected from
> disclosure. If you are not the intended recipient of this message, or if
> this message has been addressed to you in error, please immediately alert
> the sender by reply e-mail and then delete this message, including any
> attachments. Any dissemination, distribution or other use of the contents
> of this message by anyone other than the intended recipient is strictly
> prohibited. All messages sent to and from this e-mail address may be
> monitored as permitted by applicable law and regulations to ensure
> compliance with our internal policies and to protect our business. E-mails
> are not secure and cannot be guaranteed to be error free as they can be
> intercepted, amended, lost or destroyed, or contain viruses. You are deemed
> to have accepted these risks if you communicate with us by e-mail.
>

Re: Improving Fineract CN a Community survey

[Myrle Krantz]

So much wrong here, I'm just gonna skip to the end.

On Mon, Sep 27, 2021 at 3:09 PM Saransh Sharma 
wrote:

> Ok , understood we can put more fire power once we get this rolling, but
> if you look at the work I asked was to develop the Proposal not actual
> development, think that's a lot ?
>

Saransh, I do not trust you, and won't be entering into a business
relationship with you already for that reason.  But even if I did, your
management approach here is completely wrong: you are trying to replace
intrinsic motivation to bank the unbanked, or build a software architecture
I can believe in, or (equally valid) build a business that I can own.  You
are trying to replace that intrinsic motivation with extrinsic motivation
of $1500 and  blockchain.  (Which, given the way you dismissed
Sander, you clearly don't understand either.)  I shouldn't need to tell you
that that is... unlikely to lead to your own success.  The people here have
earned more dignity than that.

Best Regards,
Myrle

Re: Improving Fineract CN a Community survey

[Myrle Krantz]

On Mon, Sep 27, 2021 at 8:23 AM Saransh Sharma 
wrote:

>
> On Sun, Sep 26, 2021 at 2:54 PM Awasum Yannick  wrote:
>
>> Hi Saransh,
>>
>> Right now, the most important things we need to do on Fineract are to:
>>
>> 1.) Upgrade the major project dependencies.
>>  a.) Upgrade to Spring Boot 2 ( this is already in progress and needs
>> testing) .
>>  b.) Upgrade from Java 8 to Java 11 (LTS). Java 17 is another LTS
>> version but we can do that later.
>>  c.) Upgrade to a more recent version of Angular, say 10, 11 or 12.
>> How much effort do you think will be required for all these?
>>
>
> Honestly manually upgrading 40 repos is a daunting task don't you think?
>
>
> 2.) Deploy a Sandbox Environment for Testing Fineract CN. So the community
>> will have a demo environment for playing around and learning about the new
>> system.
>> 3.) Figure out how to Release Fineract CN. Myrle, Markus and Mark will
>> help us when we get here, they have a lot of experiences in that area.
>> Others will be available to help including Petri, Juhan, Mike, Aleks and
>> many others.
>> 4.) Write Documentation on how to host Fineract CN on major Cloud
>> Infrastructure.
>> 5.) Decide on how to host Fineract CN artifacts either using JFrog or
>> whatever solution is available out there... Juhan already did a lot of work
>> in that direction
>>
> I think this is where we have to put a lot of time artifacts are binded in
> single language, if we say that we stick to certain codebase always then it
> make sense are we sticking to such choice then we are always binded to such
> methods , now choice is do we want to move away from this?
>

So you would suggest moving from keeping up to date in one set of languages
and frameworks to keeping up to date in 40 languages and frameworks?
Interesting approach.


> 6.) With 5. in place, we can figure out a complete CI/CD environment for
>> auto deploying to the sandbox environment we defined in 2. above..
>> .
>>
>> Why dont we add these also ::
> Why dont we retire some services from FineractCN and perhaps these
> services could be
> 1. Auth service instead use PKI and Public Key based AUTH that are already
> in use. or let people use whatever auth they like ?
>

While I do think we should be replacing Identity with something externally
maintained, it's not going to be a simple swap out.  The entire permissions
system bases around identity and anubis.  The changes would be easier to
make once the framework and library updates are completed.


> 2. Retire provisioner,  and its supported libs that are like anubis
> If we retire some services and make the product light weight then we have
> a chance to quickly upgrade the project.
>

Anubis is more than just provisioning.


>
> This is going to be controversial:: Maybe we retire the DB support since
> sticking with one single DB could be problematic in the design patterns of
> the Microservices. (I know a lot will say what will happen to Multi-tenancy
> and migration)
> I think we could use a different kind of DB that just stores on log level
> and has inbuilt encryption like a blockchain DB ?
>

You've misunderstood the Fineract CN architecture here.  It can use a
single DB or it can use multiple DBs.  You also seem to have misunderstood
what the relationship is between microservice architecture and DBs.


>
> There are so many things to do on Fineract CN. These are some of the most
>> important things which this community needs. We can start drawing up a road
>> map for these things and begin working on them.
>> As a community, we have not been able to achieve even a fraction of these
>> important goals over the past few years since the initial importation of
>> code into Apache Infra. Some powerful and forward thinking Orgs have hard
>> forked Fineract CN and are making progress and it has been successful for
>> them. This shows Fineract CN can work. Let's not abandon it, let's make it
>> better and even do an initial release of Apache Fineract CN before we start
>> talking about doing other things. We can build whatever blockchain or smart
>> contract solutions on top of the fundamental release. If we cannot do the
>> above as a community then we won't be able to do whatever you or
>> anyone else will propose.
>>
>> Why have we not been able to make progress with releasing Apache Fineract
>> CN? Why? That should be a question on our minds.
>>
>> Then once we have that then we can ask the community to roll features on
> top in their language by the support of generators in their lang choice and
> support
>

If you don't know how to code and don't intend to participate in the
coding, what does "ask the community to..." look like for you in a
community of volunteers.

Frankly the architecture you propose has so little in common with Fineract
CN that it looks like a start over to me.  If you want to do that, go
ahead.  No reason why not.  But why insist then on calling it Fineract CN?

>
> Hey, Ronald and Awasum , this superset 

Re: ApacheCon 2021 is almost here! Join us and have some fun!

[Myrle Krantz]

Saransh,

Wikipedia would have helped you on this one.  Greg Stein is one of the
earliest members of the Apache Software Foundation.  He was a long time
board member, including a board chair for five years.  He is currently
working as Infrastructure Administrator for The ASF where he has contact
with all 200 project communities.  I'm not certain, but he may not have
missed a single ASF board call for the last 20 years.  Beyond that Greg was
VP of Subversion for several years, and he has made significant
contributions to the Python programming language.  He is also one of the
incubation mentors for Apache Fineract.  We elected him into that role in
part to guide us on implementing the Apache way, and we were *honored* that
he chose to serve our community in that role.

Basically: you just told someone who played a significant role in defining
the Apache Way as part of his life's work, that he doesn't understand it.
Hence his reaction.

Best Regards,
Myrle Krantz

https://en.wikipedia.org/wiki/Greg_Stein


On Sun, Sep 26, 2021 at 2:23 AM Greg Stein  wrote:

> On Sat, Sep 25, 2021 at 08:13:54PM +0530, Saransh Sharma wrote:
> >...
> > Greg, seems like your understanding is limited, community over code is
> the
> > Apache way.
>
> Hahahaaa This is one of the funniest things I've read all week.
>
> Thank you for the laugh,
> -g
>

Re: ApacheCon 2021 is almost here! Join us and have some fun!

[Myrle Krantz]

As one of the two primary architects of Fineract CN:

It was not buzzword bingo, nor, as Saransh asserted in his ApacheCon 2020
talk, a "resume-driven" set of decisions.  Those statements are insulting
and do not promote collaboration nor goodwill.  I would encourage community
participants to always assume good-will, especially with respect to people
doing coding work.  We were doing the best work we knew how, and we ran out
of funding for the open source work.  I personally accepted a wage far
under my market value for two years of work, because I sincerely believed
in the work we were doing.  It took me months to accept that it wasn't to
be.  I then attempted to drive the work forward for several months
*unpaid*.  In that context, I *really* *really* do not appreciate emails
like this one.

IMO the idea of Fineract CN is still sound.  But it is also *not* in
conflict with Fineract.

Claims that Fineract CN has driven the community apart are absurd: Fineract
CN was never released; most of the community is focused on Fineract 1.x;
And I'm here cheering y'all on from the sidelines.  Nobody needs to spend
time on Fineract CN who doesn't want to, and the people spending time on
Fineract CN probably aren't interested in Fineract 1.x.

Stop with the attacks already Saransh and Co; it's hurtful and unnecessary.

Best Regards,
Myrle Krantz

On Sat, Sep 25, 2021 at 9:01 PM Giorgio Zoppi 
wrote:

> Hi all,
> this is scary:
>
> Documentation is scattered and use cases other than micro-finance need to
> be highlighted. There is hardly a senior functional fintech influencer
> connected to the project at Product engineering level.
> The CN vs 1.x question would be much better if it had an open answering
> option, my opinion: CN has driven the community apart, abandoning an
> existing product that has active users on it and businesses relying on it
> like that was not a good decision of the project, and also not one made the
> apache way, it was very much driven by the team at that time pushing people
> onto a tech stack and buzzword bingo whereas the featureset was forgotten
> about (in a similar way it happened between Mifos and MifosX). It
> ultimately drove the efforts of collaboration apart and has resulted in
> various larger implementers/developer teams forking away.
>
>
> BR,
> Giorgio.
>
>
>

Re: ApacheCon 2021 is almost here! Join us and have some fun!

[Myrle Krantz]

Saransh,

The Apache Fineract PMC members are appointed by the Apache board.  The
board almost always ratifies the suggestions of the Fineract PMC.  Awasum
Yannick, the Vice President of Apache Fineract, has already shared with you
documentation on how the Fineract PMC comes to those suggestions.  Your
response to him was dismissive, disrespectful, and entitled.  As was your
response in the last couple of days to several other people who didn't give
you things that you have demanded.  Several of the people you have been
rude to are well-liked and respected in The ASF and in the Fineract
community.  I could be reading the room wrong, but I do not believe the
Apache Fineract PMC is inclined to appoint you to their midst.

The board has a strong interest in promoting and enabling healthy
communities, and for that reason they will very very very likely defer to
the Apache Fineract PMC.  If I were a board member (and I was a board
member recently), I would likely question your PMC appointment, even if the
Fineract PMC were to suggest it.

If you believe a community exists here that is not represented by the
Apache Fineract PMC, then what you actually want is a new project.  You can
discuss this with the Apache Incubator.  But if I were a member of the
Apache Incubator PMC (and I am), I would vote against a fork of Apache
Fineract.

You can fork or copy the code to another forum if you like.  But as one of
the main architects of Fineract CN, I can tell you for certain: I would not
follow you, nor would I recommend anyone else do so.

And even if you succeed at forking the community and the code (very very
very unlikely), what you can't do is call it Fineract, or Fineract CN.
You'll have to find a new name for it.

Best Regards,
Myrle

On Tue, Sep 21, 2021 at 5:52 PM Saransh Sharma 
wrote:

>
> Thanks KAG for clarifying but in my opinion the term self is not the
> focus,let me state the context for you here, that this is regarding the
> decision making or rather consensus from the community.  But the term is
> misleading and needs to be modified .
>
> What if the community or the volunteers want to select  PMC ?As I have
> read its a closed system to select a PMC,
>
> Is there any provision for that ? Then we have an open system. Current
> system and selection of those who get to decide most of the stuff happens
> behind the scenes like selection of PMC could we do it openly?
>
> Right now the participation of the project happens via the PMC and
> committers and developers are left behind since they don't hold any right
> over the project direction. This plagues the direction of the project since
> only handful are there to select or vote out.  We need to empower all the
> participants through some common exchange of value system. Like users ,
> developers who could vote for PMC selection.
> Let me know your thoughts
>
> On Tue, Sep 21, 2021 at 5:56 PM Jim Jagielski  wrote:
>
>>
>>
>> On Sep 21, 2021, at 8:03 AM, Saransh Sharma 
>> wrote:
>>
>> Awasum for your reference
>>
>> Apache Projects are overseen by a self-selected team
>>
>>
>> Saransh for your reference.
>>
>>
>> Wrong.
>>
>
>
> --
> Thanks and regards,
>
> Saransh Sharma
> Research Partner
>
> This mail is governed by Muellners®  IT policy.
> The information contained in this e-mail and any accompanying documents
> may contain information that is confidential or otherwise protected from
> disclosure. If you are not the intended recipient of this message, or if
> this message has been addressed to you in error, please immediately alert
> the sender by reply e-mail and then delete this message, including any
> attachments. Any dissemination, distribution or other use of the contents
> of this message by anyone other than the intended recipient is strictly
> prohibited. All messages sent to and from this e-mail address may be
> monitored as permitted by applicable law and regulations to ensure
> compliance with our internal policies and to protect our business. E-mails
> are not secure and cannot be guaranteed to be error free as they can be
> intercepted, amended, lost or destroyed, or contain viruses. You are deemed
> to have accepted these risks if you communicate with us by e-mail.
>

Re: ApacheCon 2021 is almost here! Join us and have some fun!

[Myrle Krantz]

Saransh,

Allow me to introduce: Jim Jagielski was one of the Apache Fineract mentors
through incubation, and he is one of the longest serving members of the
board of The Apache Software Foundation.  He's also served as the chair of
Apache OpenOffice and numerous other projects.

Kevin McGrail is a former VP Fundraising and former Assistant Treasurer for
the Foundation, as well as a long serving chair for the SpamAssassin
project.

Neither of them is always right; in fact I'm often in disagreement with
both of them.  But they and I are in agreement here.

Best Regards,
Myrle Krantz

On Tue, Sep 21, 2021 at 2:26 PM Jim Jagielski  wrote:

>
>
> On Sep 21, 2021, at 8:03 AM, Saransh Sharma  wrote:
>
> Awasum for your reference
>
> Apache Projects are overseen by a self-selected team
>
>
> Saransh for your reference.
>
>
> Wrong.
>

Re: ApacheCon 2021 is almost here! Join us and have some fun!

[Myrle Krantz]

As a former PMC member I have exactly as much right to vote on this
nomination as Sarensh has to make it (none ; o)

Nonetheless here is my nonbinding vote:
-1

Best,
Myrle

On Tue, Sep 21, 2021 at 9:30 AM Saransh Sharma 
wrote:

> I think the appointment of track chair was never done publicly or asked
> for from the community unless it was self appointed or appointed in
> shadows!
>
> If I am not on the list and how can I vote the talks !
>
> Silence is the consent but raising objection is needed if seen any time .
> There is no limit to that in terms of a time frame as you are pressing here
> .
>
> If Javier and Rich gets to decide certain rules and get it approved by
> silence then we could definitely use lazy consent at any given time to redo
> those decision.
>
>
> As a volunteer , I would like to share that community need to work
> together rather than a single benevolent dictator making rules on whims and
> small timeframes and making excuses on the fact that what others will say
> or it’s disrespectful for other volunteers or speakers if we change !
>
> In my opinion , this Stone Age practice of deciding things a decade ago
> need to be revisited. Better start now then  year better.
>
> I would like to propose Saransh Sharma as PMC if no one has any problem
> with that in next three days then we can conclude this .
>
> Please use +1 and -1 for your votes , note your silence will be used a
> consent so please vote and let’s amend some nice changes in the community
>
> Thanks
>
>
> On Monday, September 20, 2021, Rich Bowen  wrote:
>
>>
>>
>> On 2021/09/19 07:35:33, Muellners ApS  wrote:
>> > Community for some time, we have debated whether it is right for Track
>> > Chairs to self approve their own proposals in a public conf. - Apache
>> Con,
>> > organised by charitable donations.
>> >
>> > For whatever reasons, a single self appointed track chair should not
>> > approve his own proposals, as this sets up a very dangerous precedent in
>> > this community.
>> >
>> > I strongly object & condemn this type of deterioration of human values
>> in
>> > our society and this community.
>> >
>> > Alternate route is to continue the track by dropping the talks which the
>> > Track Chair has decided that he/she/they will present themselves.
>> > This also gives space for newer budding ideas to come forward.
>>
>> You were invited, on this list, to participate in the process. You
>> declined to do so. That thread is here:
>> https://lists.apache.org/thread.html/r54be0953f95399fbd28d124c6643a568e70fc9c631bf61b10e78833b%40%3Cdev.fineract.apache.org%3E
>>
>> You were also invited to help rate and select the talks, via the CFP
>> system. You declined that invitation also.
>>
>> You also declined to object when Javier was the track chair for this
>> track last year, and the year before that.
>>
>> As for whether track chairs can run their own talks - that was my
>> decision, not Javier's. And I made that decision more than a decade ago,
>> and have been consistent with it every year since then. Track chairs are,
>> by definition, subject matter experts, and excluding them from being
>> speakers would be self-defeating. So we don't do that. Nobody has objected
>> to it, because the track chair was, in every case, approved by the project
>> community. You, specifically, approved Javier as your track chair by your
>> silence, and by not volunteering for that committee.
>>
>> For whatever it's worth, Saransh, the rating of talks for this event
>> *was* run by an anoymized voting platform (ie, speakers name was not on the
>> abstract). And everyone who asked to be part of that review process was
>> granted access to do so. I note that your name is not on that list.
>>
>> This entire conversation is profoundly disrespectful to the HUNDREDS of
>> volunteer hours that went into putting this event together. And having this
>> conversation on this list, 2 days before the event is to start, would be
>> laughable if it wasn't so incredibly inappropriate.
>>
>> This entire dispute is about a requested change to the schedule that
>> happened less than a week before the conference starts. *I* am the one who
>> vetoed that change, not Javier. And I did so because events have deadlines,
>> and the request was long after an already-extended deadline.
>>
>> Join the plann...@apachecon.com list and be part of the solution next
>> year. Discussing *here* and *now* how ApacheCon should be run is neither
>> effective nor appropriate.
>>
>>
>
> --
> Saransh Sharma
> Research Partner
>
> Sent from my phone
> This mail is governed by Muellners®  IT policy.
> The information contained in this e-mail and any accompanying documents
> may contain information that is confidential or otherwise protected from
> disclosure. If you are not the intended recipient of this message, or if
> this message has been addressed to you in error, please immediately alert
> the sender by reply e-mail and then delete this message, including any
> attachments. Any 

Re: Announcement : Welcoming Awasum as the new chair of Apache Fineract

[Myrle Krantz]

Congratulations Awasum

Well deserved!

Best Regards,
Myrle

On Sat, Aug 22, 2020 at 8:28 AM Awasum Yannick  wrote:

> Thank you alll very much.
>
> I am delighted to serve you all.
>
> Thanks.
> Awasum.
>
> On Thu, Aug 20, 2020, 16:35 Stephen Bireley  wrote:
>
>> Congratulations Awasum!
>>
>>
>>
>> Best Regards,
>>
>>
>>
>> Steve Bireley
>>
>> CTO
>>
>> Lokyata
>>
>> www.lokyata.com
>>
>> +1 571 216 3530
>>
>>
>>
>> *From:* Sanyam Goel 
>> *Sent:* Thursday, August 20, 2020 10:55 AM
>> *To:* Dev 
>> *Subject:* Re: Announcement : Welcoming Awasum as the new chair of
>> Apache Fineract
>>
>>
>>
>> Congratulations Awasum!
>>
>> Best Regards,
>> Sanyam Goel
>>
>>
>>
>> On Thu, Aug 20, 2020 at 8:01 PM carl collins 
>> wrote:
>>
>> Congratulations Awasum.
>>
>>
>>
>> On Wed, Aug 19, 2020, 11:48 PM Vishwas Babu 
>> wrote:
>>
>> Hello Community,
>>
>>
>>
>> On behalf of Apache Fineract's PMC, I am pleased to announce that Awasum
>> Yannick has been appointed as our new chair.
>>
>>
>>
>> In addition to being one of our most active community members, Awasum is
>> also a member of the Apache Software Foundation and is actively involved in
>> Apache's diversity and inclusion initiatives.
>>
>>
>>
>> Please join me in congratulating Awasum on this new role.
>>
>>
>>
>> Regards,
>>
>> Vishwas
>>
>>
>>
>>
>> --
>>
>> SANYAM GOEL
>>
>> Profile: https://plu.us/sanyam96
>>
>> LinkedIn: https://goo.gl/NkmHkf
>> Github: https://goo.gl/STw1Rq
>>
>

Re: Twitter access for committers/PMC members

[Myrle Krantz]

Michael, you are now an admin.  Congratulations!

On Wed, Jul 22, 2020 at 4:06 PM Michael Vorburger  wrote:

> On Tue, 21 Jul 2020, 11:26 Myrle Krantz,  wrote:
>
>> Changing the subject so that this reaches people who are interested in
>> the topic.
>>
>> If a PMC member or a committer wishes to contribute to the community by
>> maintaining our social media presence on twitter, you need two things: a
>> twitter account, and contributor permissions on the @ApacheFineract
>> account.  To get the latter, someone with Admin access to the twitter
>> account will need to add you.  Either Ed or I can do this.  Ed has had
>> contributor access to twitter for a long time, and admin access to twitter
>> since July 13th.
>>
>> Ed and I are currently the only Fineract tweeps with this access, but I
>> (and I'm sure Ed too) would be glad to add any PMC member who wants access
>> to the admin group.  More people means things should run more smoothly.
>>
>
> I'm interested, my Twitter Account is https://twitter.com/vorburger. Will
> you add me to admin access to https://twitter.com/apachefineract? Tx!
>
> I am not reading the fineract dev mailing list very frequently anymore,
>> though for the last week or so, I have been checking in daily to look for
>> this email.  I missed it because the subject was "ApacheCon", and I had
>> already decided I would not be submitting a talk to the Fineract track.
>>
>> With respect to promoting the CfP for ApacheCon, however, this is too
>> late.  The CfP closed on the 13th of July.
>>
>> Best Regards,
>> Myrle
>>
>> On 2020/07/15 20:59:26, Michael Vorburger  wrote:
>> > On Wed, 8 Jul 2020, 14:59 Myrle Krantz,  wrote:
>> >
>> > > Hey Ed,
>> > >
>> > > You could also promote this via twitter.  Because you are a PMC
>> member,
>> > > you have access to the Apache Fineract twitter account to do so.
>> > >
>> >
>> > Myrle, how do PMC members get access to (the password which) lets us
>> post
>> > as https://twitter.com/apachefineract ?
>> >
>> > Best,
>> > > Myrle
>> > >
>> > > On Mon, Jul 6, 2020 at 6:24 PM Javier Borkenztain 
>> wrote:
>> > >
>> > >> Thanks James,
>> > >>
>> > >> I want to insist on this, we have only 3 proposals submitted so far
>> for
>> > >> the Fineract Track.
>> > >>
>> > >>
>> > >> We need more, I know there are lots of awesome things you are doing
>> out
>> > >> there, and this event will be the perfect opportunity to showcase it
>> to the
>> > >> world and the entire Apache Community!
>> > >>
>> > >> Please don't be shy and submit your proposal for presentation!
>> > >>
>> > >> Thanks,
>> > >> Javier
>> > >>
>> > >> [image: Logo] <https://www.fiter.io>
>> > >> *Javier Borkenztain* *| CEO*
>> > >> *e:* jav...@fiter.io
>> > >> *w:* fiter.io <http://www.fiter.io>
>> > >> *m:* +598 94621188
>> > >> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>> > >> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ>
>> [image:
>> > >> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>> > >>
>> > >> Sent via Superhuman <https://sprh.mn/?vip=jav...@fiter.io>
>> > >>
>> > >>
>> > >> On Fri, Jul 03, 2020 at 15:45:53, James Dailey <
>> jamespdai...@gmail.com>
>> > >> wrote:
>> > >>
>> > >>> I want to boost this request.  If you are at a company using
>> Fineract
>> > >>> and can participate, this is a great way to show the strength of the
>> > >>> Community of use.
>> > >>>
>> > >>> Thanks Javier!
>> > >>>
>> > >>>
>> > >>> On Wed, Jul 1, 2020 at 6:44 AM Javier Borkenztain 
>> > >>> wrote:
>> > >>>
>> > >>>> Hi Fineracters!
>> > >>>>
>> > >>>> We are eager to see what is happening "out of the list" in this
>> > >>>> community.
>> > >>>>
>> > >>>> Which Fintechs are being served by Fineract? Which NeoBanks and big
>> > >>>>

Twitter access for committers/PMC members

[Myrle Krantz]

Changing the subject so that this reaches people who are interested in the 
topic.

If a PMC member or a committer wishes to contribute to the community by 
maintaining our social media presence on twitter, you need two things: a 
twitter account, and contributor permissions on the @ApacheFineract account.  
To get the latter, someone with Admin access to the twitter account will need 
to add you.  Either Ed or I can do this.  Ed has had contributor access to 
twitter for a long time, and admin access to twitter since July 13th.

Ed and I are currently the only Fineract tweeps with this access, but I (and 
I'm sure Ed too) would be glad to add any PMC member who wants access to the 
admin group.  More people means things should run more smoothly.

I am not reading the fineract dev mailing list very frequently anymore, though 
for the last week or so, I have been checking in daily to look for this email.  
I missed it because the subject was "ApacheCon", and I had already decided I 
would not be submitting a talk to the Fineract track.

With respect to promoting the CfP for ApacheCon, however, this is too late.  
The CfP closed on the 13th of July.

Best Regards,
Myrle

On 2020/07/15 20:59:26, Michael Vorburger  wrote: 
> On Wed, 8 Jul 2020, 14:59 Myrle Krantz,  wrote:
> 
> > Hey Ed,
> >
> > You could also promote this via twitter.  Because you are a PMC member,
> > you have access to the Apache Fineract twitter account to do so.
> >
> 
> Myrle, how do PMC members get access to (the password which) lets us post
> as https://twitter.com/apachefineract ?
> 
> Best,
> > Myrle
> >
> > On Mon, Jul 6, 2020 at 6:24 PM Javier Borkenztain  wrote:
> >
> >> Thanks James,
> >>
> >> I want to insist on this, we have only 3 proposals submitted so far for
> >> the Fineract Track.
> >>
> >>
> >> We need more, I know there are lots of awesome things you are doing out
> >> there, and this event will be the perfect opportunity to showcase it to the
> >> world and the entire Apache Community!
> >>
> >> Please don't be shy and submit your proposal for presentation!
> >>
> >> Thanks,
> >> Javier
> >>
> >> [image: Logo] <https://www.fiter.io>
> >> *Javier Borkenztain* *| CEO*
> >> *e:* jav...@fiter.io
> >> *w:* fiter.io <http://www.fiter.io>
> >> *m:* +598 94621188
> >> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
> >> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> >> linkedin icon] <https://www.linkedin.com/company/fiter-io>
> >>
> >> Sent via Superhuman <https://sprh.mn/?vip=jav...@fiter.io>
> >>
> >>
> >> On Fri, Jul 03, 2020 at 15:45:53, James Dailey 
> >> wrote:
> >>
> >>> I want to boost this request.  If you are at a company using Fineract
> >>> and can participate, this is a great way to show the strength of the
> >>> Community of use.
> >>>
> >>> Thanks Javier!
> >>>
> >>>
> >>> On Wed, Jul 1, 2020 at 6:44 AM Javier Borkenztain 
> >>> wrote:
> >>>
> >>>> Hi Fineracters!
> >>>>
> >>>> We are eager to see what is happening "out of the list" in this
> >>>> community.
> >>>>
> >>>> Which Fintechs are being served by Fineract? Which NeoBanks and big
> >>>> banks are been brought to live on top of Fineract (we at Fiter are 
> >>>> helping
> >>>> several NeoBanks, and we will present on the ApacheCon @home Event), what
> >>>> cool integrations are being brought to live,
> >>>>
> >>>> Don't be shy, we are doing awesome things here, and this is the
> >>>> opportunity to share with the rest of the community!   Submit your
> >>>> talks today at https://acna2020.jamhosted.net/
> >>>>
> >>>> Also, if you want to collaborate on the organization of the track,
> >>>> please join us tomorrow and register for a work session on the
> >>>> organization of the event:
> >>>>
> >>>>
> >>>> https://us02web.zoom.us/meeting/register/tZUvf--rrTkrH9CFxD6xDoV_JvEokaCHJ6dG
> >>>>
> >>>>
> >>>> Thanks,
> >>>> Javier
> >>>>
> >>>>
> >>>> [image: Logo] <https://www.fiter.io>
> >>>> *Javier Borkenztain* *| CEO*
> >>>> *e:* jav...@fiter.io
> >>>> *w:* fiter.io <http://www.fiter.io>
> >>>> *m:* +598 94621188
> >>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
> >>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> >>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
> >>>>
> >>>> Sent via Superhuman <https://sprh.mn/?vip=jav...@fiter.io>
> >>>>
> >>>
> >>
> 

Myrle will soon no longer be moderating Fineract lists

[Myrle Krantz]

Hey all,

FYI, I'm stepping down as moderator for the Fineract lists:
https://issues.apache.org/jira/browse/INFRA-20513

Up till now, I've been doing this task multiple times daily.

I don't know if anyone else is moderating these lists.  My impression is
that they may be, at best, irregularly moderated.  Hopefully I'm wrong.
But the Fineract PMC may wish to check in with the other moderators to
ensure an acceptable level of service in this role.

Note also, that many of the messages I end up accepting on dev@fineract
were also sent to Mifos mailing lists.  Not accepting them on dev@fineract
in a timely manner will have the effect of moving community interactions
from the Apache Fineract project to the Mifos Initiative.

Best Regards,
Myrle

Re: ApacheCon @Home 2020

[Myrle Krantz]

Hey Ed,

You could also promote this via twitter.  Because you are a PMC member, you
have access to the Apache Fineract twitter account to do so.

Best,
Myrle

On Mon, Jul 6, 2020 at 6:24 PM Javier Borkenztain  wrote:

> Thanks James,
>
> I want to insist on this, we have only 3 proposals submitted so far for
> the Fineract Track.
>
>
> We need more, I know there are lots of awesome things you are doing out
> there, and this event will be the perfect opportunity to showcase it to the
> world and the entire Apache Community!
>
> Please don't be shy and submit your proposal for presentation!
>
> Thanks,
> Javier
>
> [image: Logo] 
> *Javier Borkenztain* *| CEO*
> *e:* jav...@fiter.io
> *w:* fiter.io 
> *m:* +598 94621188
> [image: twitter icon]  [image: youtube icon]
>  [image:
> linkedin icon] 
>
> Sent via Superhuman 
>
>
> On Fri, Jul 03, 2020 at 15:45:53, James Dailey 
> wrote:
>
>> I want to boost this request.  If you are at a company using Fineract and
>> can participate, this is a great way to show the strength of the Community
>> of use.
>>
>> Thanks Javier!
>>
>>
>> On Wed, Jul 1, 2020 at 6:44 AM Javier Borkenztain 
>> wrote:
>>
>>> Hi Fineracters!
>>>
>>> We are eager to see what is happening "out of the list" in this
>>> community.
>>>
>>> Which Fintechs are being served by Fineract? Which NeoBanks and big
>>> banks are been brought to live on top of Fineract (we at Fiter are helping
>>> several NeoBanks, and we will present on the ApacheCon @home Event), what
>>> cool integrations are being brought to live,
>>>
>>> Don't be shy, we are doing awesome things here, and this is the
>>> opportunity to share with the rest of the community!   Submit your talks
>>>  today at https://acna2020.jamhosted.net/
>>>
>>> Also, if you want to collaborate on the organization of the track,
>>> please join us tomorrow and register for a work session on the
>>> organization of the event:
>>>
>>>
>>> https://us02web.zoom.us/meeting/register/tZUvf--rrTkrH9CFxD6xDoV_JvEokaCHJ6dG
>>>
>>>
>>> Thanks,
>>> Javier
>>>
>>>
>>> [image: Logo] 
>>> *Javier Borkenztain* *| CEO*
>>> *e:* jav...@fiter.io
>>> *w:* fiter.io 
>>> *m:* +598 94621188
>>> [image: twitter icon]  [image: youtube
>>> icon]  [image:
>>> linkedin icon] 
>>>
>>> Sent via Superhuman 
>>>
>>
>

Re: Status of fineract-cn-interoperation

[Myrle Krantz]

Hey all,

I just checked, and Marta does not have an ICLA on file with the ASF.  This
isn't a minor change that's being merged.  it's an entire repository.

I imagine, at the current rate, it'll be a while before Fineract CN is
released, but we will not be able to release it at all if we have
significant pieces of code with unclear provenance.

Marta,
Any chance you can submit an ICLA to the ASF?  You can find the form and
the instructions here: https://www.apache.org/licenses/icla.pdf

Best Regards,
Myrle

On Wed, Nov 27, 2019 at 12:07 PM Juhan Aasaru  wrote:

> Hi!
>
> Marta, thank you for clearing that up.
>
> I created a Jira ticket with two-sub tasks about this matter:
> https://issues.apache.org/jira/browse/FINCN-192
> One task is what Marta wrote about and the other is bringing the new micro
> service up to date with the others.
> I wonder if there is anyone here who would be willing to work on those
> tasks.
>
> As you can see from Marta's email I already created the apache repository
> and imported the code from Marta's repo:
> https://github.com/apache/fineract-cn-interoperation
>
> Kind regards
> Juhan
>
> Kontakt Marta Jankovics () kirjutas kuupäeval K,
> 27. november 2019 kell 12:04:
>
>> Hi Ed, Juhan,
>>
>> I've sent pull requests in March 2019 to several services of Fineract CN.
>> These requests should be handled together as all of them are needed to
>> handle the interoperability functions.
>> The merge process was stopped at some point although I think I answered
>> all the open questions there.
>>
>>
>> https://github.com/apache/fineract-cn-interoperation/commits/mojaloop-fineract_1.0
>>
>> - New interoperability service. This request contains the majority of the
>> code changes.
>>
>> https://github.com/apache/fineract-cn-api/pull/7/commits
>>
>> https://github.com/apache/fineract-cn-accounting/pull/10/commits
>>
>> - Some additions to already existing services in order to support
>> interoperability. No change of existing functions.
>>
>> https://github.com/apache/fineract-cn-demo-server/pull/26/commits
>>
>> - Added build dependencies of the new service.
>>
>> https://github.com/apache/fineract-cn-fims-web-app/pull/14
>>
>> - Minor change in the web application to show the tenant user friendly
>> name instead of the tenant identifier. Not a must have.
>>
>> Thanks,
>>
>> Marta
>> On 2019. 11. 27. 8:54, Ed Cable wrote:
>>
>> Juhan,
>>
>> Thanks for flagging this and bringing on list. It is very important that
>> we bring it up to date as its necessary component to continue integrating
>> with ongoing with that Mifos is leading around the payment hub.
>>
>> These changes were made by the DPC team supported by Mifos through the
>> grant from DIAL.
>>
>> Although this and changes to Fineract 1.x were discussed and worked on
>> months back, the changes for Fineract 1.x were only just merged and this
>> repo was never moved over.
>>
>> Can you create a repo under the Apache namespace? Are you then and to
>> clone Marta's repository and move code over.
>>
>> Marta, can you please assist Juhan?
>>
>> Juhan, it would great to create tickets for the tasks needed to bring
>> this up to date and if you have time, to take on some of those.
>>
>> Cheers,
>>
>> Ed
>>
>> On Tue, Nov 26, 2019, 05:58 Juhan Aasaru  wrote:
>>
>>> Hi!
>>>
>>> I found from archives that there have been efforts to integrate
>>> Fineract-CN with Mojaloop and for this purpose a
>>> repository fineract-cn-interoperation has been created.
>>>
>>> I didn't find it under apache repositories but I found this repo:
>>> https://github.com/marta-jankovics/fineract-cn-interoperation
>>> (I don't know if it is the correct one)
>>>
>>> The problem is that since it is not under Apache namespace it hasn't
>>> been kept up to date with the latest changes (uploading to Artifactory,
>>> MariaDB to Postgres migration, introducing EclipseLink, upgrading Gradle
>>> version, building Docker images etc) and thus it has fallen out of loop.
>>>
>>> I wanted to ask what is the situation with this repository and
>>> functionality and should we put some efforts to bring this repository under
>>> the Apache hat and bring it up to date so it could be started together with
>>> other services.
>>>
>>> Juhan
>>>
>>

Re: [CVE-2016-4977] Apache Fineract remote code execution vulnerabilities fixed in v1.3.0

[Myrle Krantz]

Hey Vishwas,

Apparently your announcement was not accepted to the annou...@apache.org
list.  If you've received an explanation for why, I'd be curious to know
what it is.  I assume you are working on formulating a mail that is
accepted?

If you need help with anything, let me know.

Also if you want examples of successful announcements, you can use:
https://lists.apache.org/list.html?annou...@apache.org  Go to advanced
search and look for mails with CVE in the subject line.

Best Regards,
Myrle


On Wed, Oct 16, 2019 at 8:26 AM Vishwas Babu (Apache) <
vishwasb...@apache.org> wrote:

> Hello,
>
> The Apache Fineract project would like to hereby disclose that our 1.3.0
>
> release includes a fix for CVE-2016-4977 : A known vulnerability in spring
>
> security upstream dependencies allowed malicious users to trigger remote code
>
> execution. See https://nvd.nist.gov/vuln/detail/CVE-2016-4977 for details of
>
> the upstream CVE.
>
> We would like to thank Roberto (extranewb...@gmail.com) for reporting
>
> this issue and the Apache Security team for their assistance.
>
> Additional details at 
> https://cwiki.apache.org/confluence/display/FINERACT/Apache+Fineract+Security+Report.
>
> Regards,
> Vishwas
>
>

Re: github notifications going to wrong mailing list

[Myrle Krantz]

Hey Juhan,

Don't apologize for working!  : o)  It looks like it may be resolved.
Thanks for pointing to the ticket.  If you need any help nudging action
there, please let me know.

Best,
Myrle

On Thu, Sep 19, 2019 at 9:04 PM Juhan Aasaru  wrote:

> Hi!
>
> I'm sorry, most of the notifications have been triggered by my actions,
> I'll try to keep away from the repo until it is fixed.
> The ticket with infra has been already created
> https://issues.apache.org/jira/browse/INFRA-19022
> but for some reason resolving it is getting delayed.
>
> Kind regards
> Juhan
>
> Kontakt Myrle Krantz () kirjutas kuupäeval N, 19.
> september 2019 kell 21:57:
>
>> Hey all,
>>
>> We've just had a rather large number of people request to be removed from
>> the mailing list.  I don't know the reason, but one thing about the
>> dev@fineract.a.o mailing list that is bothering *me* currently is the
>> large number of notifications coming from fineract-cn-docker-compose.
>> Those notifications belong on commits@.
>>
>> Can whoever requested that github repo, please create a ticket to infra
>> to fix the notifications so that they go to the right place?
>>
>> Thank you,
>> Myrle
>>
>

github notifications going to wrong mailing list

[Myrle Krantz]

Hey all,

We've just had a rather large number of people request to be removed from
the mailing list.  I don't know the reason, but one thing about the
dev@fineract.a.o mailing list that is bothering *me* currently is the large
number of notifications coming from fineract-cn-docker-compose.  Those
notifications belong on commits@.

Can whoever requested that github repo, please create a ticket to infra to
fix the notifications so that they go to the right place?

Thank you,
Myrle

Re: Hibernate Validator is Apache Compliant

[Myrle Krantz]

Please don't migrate the hibernate validator.  I've put a lot of work into
making it work well, including very detailed validation and tests for that
validation.  There is no reason to migrate it to anything else.  It's all
apache licensed.

Best,
Myrle

On Sat, Jul 27, 2019 at 5:43 PM Awasum Yannick  wrote:

>
>
> On Sat, Jul 27, 2019 at 4:15 PM Ebenezer Graham 
> wrote:
>
>> Hi Awasum,
>>
>> I am aware that Hibernate validator is compliant. I initially, didn't
>> want to change it, however, in consultation with my mentor, we thought it
>> would be better to completely switch to EclipseLink related software if we
>> are moving away from Hibernate.
>>
>> What's your suggestion?
>>
>
> I think limited time should be spent migrating what absolutely needs to be
> migrated. You can continue with the validator after the core ORM is
> migrated. If that has been done then you send your PRs so we begin testing.
>
>
>> *Cheers*
>>
>> On Sat, 27 Jul 2019 at 18:32, Awasum Yannick  wrote:
>>
>>> Hi Graham,
>>>
>>> Hibernate Validator is Apache compliant:
>>> https://github.com/hibernate/hibernate-validator/blob/master/license.txt
>>>
>>> I was looking at your weekly check in
>>> here
>>> and saw that you were trying to migrate from Hibernate Validator to Eclipse
>>> Validator. I dont know if thats the case..I dont know all the details but
>>> just wanted to share.
>>>
>>> Let me know.
>>>
>>>
>>> Thanks.
>>> Awasum
>>>
>>

Re: Time for a new global summit?

[Myrle Krantz]

Hey all,

The 2020 dates probably won't go out before November.  But there's no harm
in starting to think about what kinds of talks we might want to give now.
When we start looking for track chairs, I'll put James and Javier on the
contact list!

I've been very involved in ApacheCon Europe, but I'm guessing you all are
more interested in ApacheCon North America.

Being a track chair means that you get to pick the talks for your track,
and you are responsible for soliciting proposals and promoting your track.
So the first thing you need is a name, and you have that.  Great! : o)

Best Regards,
Myrle


On Fri, Jul 19, 2019 at 10:16 PM James Dailey 
wrote:

> Myrle -
>
> Thanks for the offer and suggestions.
>
> I'd like to get a bit more information on the Track development idea (can
> you send me a template or more details on what 'best tracks' look like?)
>
> And, Javier - let's collaborate so we have a strong offering/proposal to
> ApacheCon.
>
> Finally - what dates and where (sorry couldn't find it).
>
> . thanks
>
>
> On Fri, Jul 19, 2019, 12:36 PM Javier Borkenztain  wrote:
>
>> Hi Myrle, thanks for bringing this up, I think this is a great idea of
>> getting the support of the ApacheCon. This will help us a lot with the
>> logistics and also, will help us mingle with the rest of the communities.
>>
>> I would love to volunteer to serve as a track chair of the Fineract track
>> at the ApacheCon 2020. If nobody has any issue, please introduce me to the
>> ApacheCOn planners so we can start thinking ahead.
>>
>> Thanks,
>> Javier
>>
>>
>>
>> On Wed, May 29, 2019 at 7:55 AM Myrle Krantz  wrote:
>>
>>> Hey Javier,
>>>
>>> I'm not just on the board.  I'm also the Chair of ApacheCon Europe.  :
>>> o)  Which is why I haven't been around much lately...
>>>
>>> But as such, I'd like to suggest that Fineract request a sub-conference
>>> at ApacheCon 2020.  Either in Europe or in North America or both.  This
>>> would dramatically reduce the cost of the conference and effort to our
>>> community, allow the Fineract community to leverage Apache offerings like
>>> TAC (Which enabled the attendance of 5 Fineract community members in
>>> Montreal in 2018! : o), and allow us to play with the "big boys" in PR and
>>> Media relations for our conference.  We'd also have a hackathon space, and
>>> the opportunity to cross-pollinate with other Apache communities.
>>>
>>> All we'd need is someone from the community who is willing to step up
>>> and serve as track chair.  Track chair would coordinate with the community,
>>> review submissions, and ultimately select the talks for the Fineract
>>> track.  If anyone wants to volunteer, I'd be happy to introduce you to the
>>> ApacheCon planners list.
>>>
>>> Best,
>>> Myrle
>>>
>>>
>>> On Wed, May 22, 2019 at 6:18 PM Javier Borkenztain 
>>> wrote:
>>>
>>>> Hi Fineracters, how are you doing?
>>>>
>>>> It has been now 5 years since our last global summit and I believe our
>>>> community has lots to share since then.
>>>>
>>>> Since Sharjah, collectively we have
>>>>
>>>>- Created Apache Fineract 1.x and Fineract CN
>>>>- Grow our community and expand it to Fintech new users
>>>>- Got our former chairman into Apache board :)
>>>>- and much more stuff that I would love to see on the
>>>>presentations...
>>>>
>>>> Hence, I would like to propose we do a new summit, where we can all
>>>> meet and greet, present what are we doing all over the world, share new
>>>> ideas and grow our community.
>>>>
>>>> We should have a technical, business, and strategic tracks on how we
>>>> should move forward.
>>>>
>>>> Thanks!
>>>> Javier
>>>>
>>>> --
>>>>
>>>
>>
>> --
>>
>>

Re: Fineract JIRA: Assigning issues.

[Myrle Krantz]

On Tue, Jul 9, 2019 at 9:53 AM Awasum Yannick  wrote:

> Can we give any authenticated apache jira user contributor status?
>

Yes.

FYI: I don't have the karma to edit our workflow.  I've asked for it now.

Best,
Myrle

Re: Fineract JIRA: Assigning issues.

[Myrle Krantz]

Hey Santosh,

We can adjust the workflow in Jira to reflect the need for QA.  It's not
necessary to assign to one specific person for QA, and it might discourage
others from joining in on that very important task.  A truck factor of 1 is
a bad thing for any project.

Santosh, would you be willing to help others learn to do QA as well?  Would
the rest of y'all like me to edit our Jira workflow to make the QA step an
explicit part of it?

Best,
Myrle

On Mon, Jul 8, 2019 at 2:20 PM Santosh Math 
wrote:

> Hi Awasum,
> Whenever ticket is raised , it's assigned to developer/coder first so that
> he can get notification to work on it. Once it's 'Resolved' , then the same
> ticket is assigned QA so that QA person get notification that he can start
> QA on that. After QA , if the ticket is not properly resolved , then QA
> person will assign it back to developer with comments. If it is resolved,
> the QA person will close the ticket.
> Assigning a ticket is part of the workflow . There is nothing to do with
> taking credit or not.
>
>
>
> On Mon, Jul 8, 2019 at 3:54 PM Awasum Yannick  wrote:
>
>> Hi Santosh,
>>
>> Assigning an issue to you which has been fixed by another person is not a
>> good idea. People want to take credit for their work. From this information
>> we can know who to invite as committer and it be part of their CV(just
>> record).
>>
>> Anyways, We do it via Github PRs. Should be a simpler way to search and
>> assign the right person who completed a task.
>>
>>
>> On Mon, Jul 8, 2019 at 5:04 AM Santosh Math <
>> sant...@confluxtechnologies.com> wrote:
>>
>>> Hi Awasum,
>>> If the issues are fixed/resolved , those tickets should be assigned to
>>> me. You can simply use filter . Go to Issues > Search for Issues . In next
>>> page , Select project as 'Apache Fineract' and select status , tick only
>>> 'Resolved'. It would list all the tickets which are in resolved status.
>>>
>>> On Mon, Jul 8, 2019 at 3:07 AM Awasum Yannick  wrote:
>>>
 Hi All,

 I wonder if we could make the process of assigning an issue to someone
 other than yourself on Fineract JIRA?

 There are cases where issues have been fixed in the past and we need to
 assign that to the right person when closing these issues...

 Does anyone have an idea on what to do to make it easy to search and
 assign anyone on Issues?

 I noticed this a few times..

 Thanks
 Awasum

>>>
>>>
>>> --
>>> Thanks & Regards
>>>
>>> Santosh Math
>>>
>>> *QA Engineer*
>>>
>>> *Conflux Technologies Pvt Ltd *
>>> | *Office*: +91-080-41208662 |
>>>
>>> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
>>> Bengaluru, Karnataka, 560043 INDIA
>>>
>>
>
> --
> Thanks & Regards
>
> Santosh Math
>
> *QA Engineer*
>
> *Conflux Technologies Pvt Ltd *
> | *Office*: +91-080-41208662 |
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>

Fwd: Apache Roadshow India in 2020?

[Myrle Krantz]

This seems like something several Fineract devs might be interested in. If
you want to give feedback or help with planning, subscribe to
dev@community.a.o and provide feedback there.

Best,
Myrle

-- Forwarded message -
From: Sharan Foga 
Date: Sun, Jun 2, 2019 at 11:22 AM
Subject: Apache Roadshow India in 2020?
To: 


Hi All

With all the suggestions coming up for locations for potential Roadshows,
the idea of doing a Roadshow in India has been raised again. The suggested
timeframe is Q1 2020 as the weather is good (not too hot, not too cold)
also not too many other conferences are happening around that time. The
potential location is Gurgaon / Gurugram which has good transport links and
seems to be a tech hub. I am working with Swapnil ,who is active on this
list and few others I know from OFBiz who are based in India who have
offered to help with the organisation and management. We are currently
working to put together a proposal.

So as part of an initial step I would like to gauge the feedback from our
community. What do people think? (And also is anyone interested in helping
out ?)

Thanks
Sharan



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

Re: [ANNOUNCE] Welcome Courage Angeh to the Apache Fineract PMC

[Myrle Krantz]

Congratulations Courage!  Well-deserved!

Best,
Myrle

On Fri, May 24, 2019 at 1:25 PM Courage Angeh 
wrote:

> Hello,
>
> Thanks for the warm welcome.
> I really appreciate it.
>
> Regards,
> Courage.
>
> On Thu, May 23, 2019, 8:14 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Congratulations!
>>
>> On Thu, May 23, 2019 at 9:26 PM Fuh Debenick 
>> wrote:
>>
>>> Well done Courage, more grease!
>>>
>>> On Wed, May 22, 2019, 19:42 Awasum Yannick  wrote:
>>>
 Hi All,

 I am delighted to announce that Courage Angeh has been voted in as a
 new PMC Member at Apache Fineract.

 Courage has been a valuable member of our community for over 2 years
 now and in that time she has shown great leadership skills. She developed
 an In-App Notifications for Fineract 1.x as part of GSoC 2017. She
 containerized Fineract CN and is currently leading efforts towards enabling
 a production deployment in a Cloud Environment. Courage has been
 consistently active in helping to onboard new devs on our project. She is
 also a mentor for GSoC 2019 at Fineract and Outreachy via Mifos.

 Those are some remarkable accomplishments for our project.

 Please join me in Congratulating Courage for her contributions to the
 Fineract Community.


 Thanks.
 Awasum Yannick

>>>

Re: Time for a new global summit?

[Myrle Krantz]

Hey Javier,

I'm not just on the board.  I'm also the Chair of ApacheCon Europe.  : o)
Which is why I haven't been around much lately...

But as such, I'd like to suggest that Fineract request a sub-conference at
ApacheCon 2020.  Either in Europe or in North America or both.  This would
dramatically reduce the cost of the conference and effort to our community,
allow the Fineract community to leverage Apache offerings like TAC (Which
enabled the attendance of 5 Fineract community members in Montreal in 2018!
: o), and allow us to play with the "big boys" in PR and Media relations
for our conference.  We'd also have a hackathon space, and the opportunity
to cross-pollinate with other Apache communities.

All we'd need is someone from the community who is willing to step up and
serve as track chair.  Track chair would coordinate with the community,
review submissions, and ultimately select the talks for the Fineract
track.  If anyone wants to volunteer, I'd be happy to introduce you to the
ApacheCon planners list.

Best,
Myrle


On Wed, May 22, 2019 at 6:18 PM Javier Borkenztain  wrote:

> Hi Fineracters, how are you doing?
>
> It has been now 5 years since our last global summit and I believe our
> community has lots to share since then.
>
> Since Sharjah, collectively we have
>
>- Created Apache Fineract 1.x and Fineract CN
>- Grow our community and expand it to Fintech new users
>- Got our former chairman into Apache board :)
>- and much more stuff that I would love to see on the presentations...
>
> Hence, I would like to propose we do a new summit, where we can all meet
> and greet, present what are we doing all over the world, share new ideas
> and grow our community.
>
> We should have a technical, business, and strategic tracks on how we
> should move forward.
>
> Thanks!
> Javier
>
> --
>

Fwd: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.

[Myrle Krantz]

Hey fine Fineracters,

Every year TAC (travel assistance committee) provides travel assistance to
people who might not otherwise be able to attend Apache conferences.  This
is available for both ApacheCons this year: Las Vegas and Berlin.

Please consider applying and attending.  I would love to see you there!

The forwarded message below contains the details for Las Vegas.  Berlin
will be coming soon.

Best Regards,
Myrle

-- Forwarded message -
From: Gavin McDonald 
Date: Fri, May 17, 2019 at 8:30 AM
Subject: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.
To: 


Hi PMCs!

Please redistribute the below to your user and dev lists, feel free to also
use social media to spread the word. Thanks!

Gav... TAC Team

---

The Travel Assistance Committee (TAC) are pleased to announce that travel
assistance applications for ApacheCon NA 2019 are now open!

We will be supporting ApacheCon NA Las Vegas, Nevada on 9th - 12th
September 2019

 TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons.
For more info on this years applications and qualifying criteria, please
visit the TAC website at < http://www.apache.org/travel/ <
http://www.apache.org/travel/> >. Applications opened today and will close
around the 21st June.

Important: Applications close on June 21st, 2019. Applicants have until the
closing date above to submit their applications (which should contain as
much supporting material as required to efficiently and accurately process
their request), this will enable TAC to announce successful awards shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a diverse
range of backgrounds. We therefore encourage (as always) anyone thinking
about sending in an application to do so ASAP.
We look forward to greeting many of you in Las Vegas!

Kind Regards,
Gavin - (On behalf of the Travel Assistance Committee)

Re: Indexing of Posts to Mailing List to Search Engines

[Myrle Krantz]

Hey Ed,

If you use "Advanced Search" you can refine the time frame of the search:
https://lists.apache.org/list.html?dev@fineract.apache.org

If you'd like to ask for a feature or a change to that UI, you can join the
mailing list for that project, or submit a ticket:
https://lists.apache.org/list.html?d...@ponymail.apache.org
https://github.com/apache/incubator-ponymail/issues

: o),
Myrle



On Fri, May 3, 2019 at 10:14 PM Chris Thistlethwaite 
wrote:

> Ed,
>
> Have you tried the same query on lists.apache.org? I was able to quickly
> find both posts by searching all Fineract lists older than a day. While
> that doesn't answer your question about Googleability, it's just a
> better way to search mailing lists. I don't think we have anything
> specifically keeping google from crawling us/lists/archives (aside from
> them just hammering our sites and bringing them down).
>
> -Chris T.
> #asfinfra
>
> On 5/3/19 3:41 PM, Ed Cable wrote:
> > Is there a setting that we can change or request to be changed to make
> > mailing lists posts more searchable?
> >
> > This problem is evident in both the archive as well as general Google
> > searches.
> >
> > In theory, one should be able to simply search via Google and find
> > mailing list posts from at any point in time, but it appears posts
> > older than one month aren't easily found in searches.
> >
> > For example if I search for a post with the subject line, "API and
> > Channel Concepts" with the query, "API and Channel Concepts Fineract",
> > the archive of this mailing list post shows up nowhere in the results.
> >
> > Likewise, searching for: "Schema `mifostenant-default` contains a
> > failed migration to version 164 !" the subject line of a posting on
> > March 22, 2019 yields no results via Google?
> >
> > Does this have anything to do with the default setting on our archive
> > which only lists posts and displays search results the from the "last
> > 1 month" until that filter is changed?
> >
> > Thanks,
> >
> > Ed Cable
>

Re: [ANNOUNCE] Welcome Juhan Aasaru as Fineract committer

[Myrle Krantz]

Welcome Juhan!

Best Regards,
Myrle

On Wed, May 1, 2019 at 7:28 PM Juhan Aasaru  wrote:

> Hi everyone!
>
> Thank you all for good wishes and for accepting me as Apache Fineract
> committer.
> I plan to keep up contributing to the project and currently my main goal
> is to make
> Fineract-cn projects easier for anyone to set up and work with.
>
> Kind regards
> Juhan Aasaru
>
> Kontakt Ed Cable () kirjutas kuupäeval K, 1. mai 2019
> kell 17:17:
>
>> Congratulations Juhan and thank you for all your contributions thus far.
>>
>> Ed
>>
>> On Wed, May 1, 2019 at 5:09 AM Mua Rachmann 
>> wrote:
>>
>>> Welcome Juhan,
>>> Congrats
>>>
>>> On Wed, May 1, 2019, 11:45 Ruphine Kengne 
>>> wrote:
>>>
 Congratulations Juhan. Keep up

 On Wed, 1 May 2019 at 11:34, Nkep Kerlyn  wrote:

> Congrats Juhan!!
>
> On Tue, Apr 30, 2019, 8:20 AM Awasum Yannick 
>> Hi All,
>>
>> I am happy to announce that Juhan Aasaru has been voted in as a
>> Fineract Committer.
>>
>> Juhan has been in the community for just over 6 months now and has
>> already shown how valuable they are to our project.
>>
>> Juhan has contributed to Fineract 1.x as well as Fineract CN in areas
>> like Containerization and recently enabled Continuous Integration on
>> Fineract CN. Juhan has also contributed to key discussions on the mailing
>> list and also created and updated documentations to unblock new
>> contributors. Thank you very much Juhan.
>>
>> Please join me in welcoming Juhan as a new Committer on Fineract.
>>
>> Thanks.
>> Awasum Yannick.
>> PMC Member, Apache Fineract
>>
>>
>>
>>
>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>   
>>
>>

[ANNOUNCE] Welcome Angel Cajas as Fineract committer

[Myrle Krantz]

Hey all,

Please welcome Angel Cajas as our newest Apache Fineract committer!

Best Regards,
Myrle

Re: [ANNOUNCE] Myrle Krantz is a Board Member at the Apache Software Foundation.

[Myrle Krantz]

Thank you everyone for your well wishes!  I got my start in open source in
this community, and thank you especially for giving me the opportunity to
learn together with you!

Best Regards,
Myrle

On Fri, Mar 29, 2019 at 7:26 PM Rahul Goel  wrote:

> Congrats Myrle!
>
> On Fri, Mar 29, 2019 at 5:31 PM Chirag Gupta 
> wrote:
>
> > Congratulations Myrle!
> >
> > On Fri, Mar 29, 2019 at 3:38 PM Sanyam Goel 
> > wrote:
> >
> > > Congrats Myrle!
> > >
> > > Regards,
> > > Sanyam Goel
> > >
> > > On Fri, Mar 29, 2019 at 2:55 PM Sendoro Juma 
> > wrote:
> > >
> > >> Wh... congratulations
> > >>
> > >> On March 29, 2019 at 2:12 AM Vishwas Babu <
> > >> vish...@confluxtechnologies.com> wrote:
> > >>
> > >> Congrats Myrle !
> > >>
> > >> Regards,
> > >> Vishwas
> > >>
> > >> On Thu, Mar 28, 2019 at 2:50 PM Javier Borkenztain 
> > >> wrote:
> > >>
> > >> Congratulations Myrle!!
> > >>
> > >> On Thu, Mar 28, 2019, 18:39 Kevin A. McGrail 
> > wrote:
> > >>
> > >> +1
> > >>
> > >> On 3/28/2019 5:25 PM, Ruphine Kengne wrote:
> > >>
> > >> Congratulations Myrle,
> > >> All the best in your new role
> > >>
> > >> Regards
> > >>
> > >> On Thu, 28 Mar 2019 at 22:07, Zayyad A. Said <
> > >> zay...@intrasofttechnologies.com> wrote:
> > >>
> > >> This is good news.
> > >>
> > >> Congratulations Myrle, keep up with the spirit of the community.
> > >>
> > >> Regards;
> > >>
> > >> *
> > >>
> > >> *Zayyad A. Said | Chairman & C.E.O*
> > >>
> > >> Cell No.: +254 716 615274 | Skype: *zsaid2011*
> > >>
> > >> Email: zay...@intrasofttechnologies.com
> > >>
> > >> Schedule Meetings: https://calendly.com/zayyadsaid
> > >>
> > >> [image: Description: Email banner]
> > >>
> > >> -Original Message-
> > >> From: Ed Cable [mailto:edca...@mifos.org]
> > >> Sent: 28 March 2019 11:54 PM
> > >> To: Dev
> > >> Subject: Re: [ANNOUNCE] Myrle Krantz is a Board Member at the Apache
> > >> Software Foundation.
> > >>
> > >> Congrats Myrle!
> > >>
> > >> Thanks for sharing the news Awasum.
> > >>
> > >> On Thu, Mar 28, 2019 at 1:42 PM Isaac Kamga 
> > >> wrote:
> > >>
> > >> Congratulations Myrle Krantz,
> > >> We're happy for your progress and we also trust that your newly found
> > >> role will help Apache Fineract grow by leaps and bounds.
> > >> Cheers,
> > >> Isaac Kamga.
> > >> On Thu, Mar 28, 2019 at 9:36 PM Ebenezer Graham
> > >> 
> > >> wrote:
> > >>
> > >> Congratulations Myrle. :)
> > >> On Fri, 29 Mar 2019 at 00:32, Awasum Yannick 
> > >> wrote:
> > >>
> > >> Hello Everyone,
> > >> At The Apache Software Foundation (ASF) Members' Meeting held this
> > >> week
> > >> and
> > >> one of our Community members was elected to the ASF Board.
> > >> Please, Join me in Congratulating Myrle Krantz on becoming an ASF
> > >> Board
> > >> of
> > >> Director.
> > >> https://blogs.apache.org/foundation/entry/announcing-new-asf-board
> > >> -of1
> > >> We know you will keep doing great things.
> > >> Thanks.
> > >> Awasum Yannick.
> > >> PMC Member, Apache Fineract.
> > >>
> > >> --
> > >>
> > >> *Ed Cable*
> > >>
> > >> President/CEO, Mifos Initiative
> > >>
> > >> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> > >>
> > >> *Collectively Creating a World of 3 Billion Maries | *
> > >> http://mifos.org
> > >> <
> > >> ">http://facebook.com/mifos> <http://facebook.com/mifos%3E> <
> > >> http://www.twitter.com/mifos>
> > >>
> > >> --
> > >> Kevin A. McGrail
> > >> Member, Apache Software Foundation
> > >> Chair Emeritus Apache SpamAssassin Project
> > >> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > >>
> > >>
> > >>
> > >>
> > >> With Best Regards
> > >>
> > >> Sendoro Juma
> > >>
> > >> ---
> > >>
> > >> SingoAfrica Limited
> > >> Mbezi Beach "B"  | Mwai Kibaki Road | 6 Wasafi Str.
> > >>
> > >> P.O BOX 78908 | 14121 Dar es Salaam
> > >>
> > >> info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz
> > >>
> > >>
> > >>
> > >
> > >
> > > --
> > > SANYAM GOEL
> > > Profile: plu.us/sanyam96
> > > LinkedIn: https://goo.gl/NkmHkf
> > > Github: https://goo.gl/STw1Rq
> > > Hackerrank: https://goo.gl/va9Npm
> > > +91-9818060934
> > >
> >
>
>
> --
> RAHUL GOEL
> +91-9873124753
>

Re: Query regarding license

[Myrle Krantz]

Hey Anshul,

There are two parts to this question:

a.) What license does it have?  For example the MIT and BSD licenses are
both Category A, which means they can be included in Apache Software
without problems.  (1)

b.) Does this make your software's runtime dependent on a single vendor's
service?  Put differently, would your project promote vendor lock-in?  If
it does, then it would not be in the spirit of open source at Apache.  If
this vendor's service has competitors you could resolve this by making the
code flexible enough to support those other vendors.  If the vendor's
service is based solely on open source components, then you could argue
that someone else at least *could* deploy that service as well, but you
should be sure to make any addresses configurable rather than hard-coded.
(2)

Best Regards,
Myrle

1.) https://apache.org/legal/resolved.html
2.) https://blogs.apache.org/foundation/entry/apache-is-open

On Sun, Mar 24, 2019 at 6:13 AM Anshul Singh 
wrote:

> Hello everyone,
>
> I have a query regarding license, can anyone who is concerned with it help
> me.
> Can we *use* dialogflow (https://dialogflow.com/) inside an Apache 2.0
> licensed project for implementing chatbot in Google assistant?
> Thank you
>
> Regards
> Anshul Singh
>

Re: [ANNOUNCE] New Fineract PMC member Santosh Math

[Myrle Krantz]

Congratulations Santosh!

Best Regards,
Myrle

On Mon, Mar 25, 2019 at 12:03 PM Pembe Miriam 
wrote:

> Good work Santosh, congrats
>
>
> On Mon, Mar 25, 2019 at 8:23 AM Massabe Lydiane <
> kengnelydiane...@gmail.com>
> wrote:
>
> > Congratulations Santosh Math
> >
> > Thanks
> > Lydiane
> >
> > On Mon, Mar 25, 2019 at 8:18 AM Mua Rachmann 
> > wrote:
> >
> > > Congrats Santosh,
> > >
> > > More grease to carry on.
> > >
> > > On Mon, Mar 25, 2019, 08:11 Mexina Daniel  wrote:
> > >
> > >> Congrats Santosh! You  deserve this!
> > >>
> > >> On March 24, 2019 at 1:32 PM Vishwas Babu <
> > >> vish...@confluxtechnologies.com> wrote:
> > >>
> > >> Hello All,
> > >>
> > >> It gives me great pleasure to announce the addition of Santosh Math as
> > the
> > >> newest member of Fineract's Project Management Committee. Please join
> me
> > >> in giving him a warm welcome.
> > >>
> > >> Santosh has been a part of the community since forever (2014!). For
> > those
> > >> of you who do not know of him, here's a snippet from Ed Cable's
> > >> announcement of Santosh's committer status back in 2017.
> > >>
> > >> Santosh has been an active member of the community since 2014 playing
> > >> many roles
> > >> initially as the lead support resource, guiding documentation for the
> > >> platform. Most recently in his role as lead QA engineer for the
> > community,
> > >> he has gone well beyond those duties doing triage and product
> management
> > >> for Apache Fineract (as well as the Mifos X distribution and apps that
> > >> consume it). Santosh is patient, thorough, and a deeply committed
> > >> community
> > >> member. He has greatly enhanced the quality of the software and has
> > helped
> > >> to streamline contributions by improving our triage and release
> > management
> > >> processes. He is continually helping other partners, assisting
> > volunteers
> > >> and interns, and most importantly supporting users of Apache Fineract.
> > You
> > >> can see his active presence on the mailing lists, the issue trackers,
> > and
> > >> our wikis.
> > >>
> > >> Regards,
> > >> Vishwas
> > >>
> > >>
> > >> Mexina Daniel
> > >>
> > >> Singo Africa Limited
> > >>
> > >> Mbezi Beach "B"  | Mwai Kibaki Road | 6 Wasafi Str.
> > >> P.O BOX 78908 | 14121 Dar es salaam
> > >>
> > >> +255 71 211 0791 | +255 22 261 8511
> > >>
> > >> amala.co.tz | singo.africa
> > >>
> > >>
> > >>
> > >
> >
>

Re: [PROPOSAL] use git branches for large or risky changes

[Myrle Krantz]

Excellent.  I'm going to call that a consensus.  On that basis, I've
created a branch for FINERACT-614, pulled in angelboxes changes and closed
this PR: https://github.com/apache/fineract/pull/465

Best Regards,
Myrle

On Fri, Mar 15, 2019 at 8:33 PM Nikhil Pawar  wrote:

> I agree, at least commiters should be allowed to do this.
>
> Regards,
> Nikhil
>
> On Fri, Mar 15, 2019 at 3:19 PM Isaac Kamga  wrote:
>
> > Hello Myrle,
> >
> > I support this proposal especially as it encourages developers to bring
> in
> > their changes earlier than later.
> >
> > The community would also have to ensure that work doesn't suffer from
> > negligence too. Is there already the motivation to do that ? Asking
> because
> > sometimes even PRs on develop which are ready take months to get merged.
> >
> > Cheers,
> > Isaac Kamga.
> >
> > On Wed, Mar 13, 2019 at 11:57 AM Myrle Krantz  wrote:
> >
> > > Hey all,
> > >
> > > PROPOSAL:
> > > "Rather than ask contributors to squash everything into a single commit
> > and
> > > our committers to merge it all at once, we should suggest the use of
> git
> > > branches for development which occurs over longer periods or larger
> line
> > or
> > > file counts.  The branch should be named after the Jira ticket it
> > > corresponds to."
> > >
> > > This would have the following advantages:
> > > * make it possible for other contributors to collaborate on larger
> > changes
> > > that aren't yet ready for primetime.  By choosing a finer granularity
> of
> > > collaboration, we would enable smaller contributions, and better engage
> > our
> > > more casual volunteers.
> > > * bring the development process to Apache infrastructure earlier, which
> > > would provide more complete data for proposals to make a contributor
> > into a
> > > committer.
> > > * provide more satisfaction to contributors: they get affirmation on
> each
> > > step of their process rather than getting that affirmation only once at
> > the
> > > end. [1]  Psychology research shows this is a more motivating and kind
> > way
> > > of giving feedback.
> > > * make it easier for me, personally to follow the development process
> > > retroactively.
> > >
> > > If y'all don't object to my proposal in the next 72 hours then I'm
> going
> > to
> > > start applying it.
> > >
> > > Best Regards,
> > > Myrle
> > >
> > > 1.)
> > >
> https://upraise.io/blog/frequency-key-successful-performance-management/
> > >
> >
>

Re: Road Map for deploying Fineract CN

[Myrle Krantz]

FYI,

I still have access to the mifos org docker hub account from when I was
employed there.  James does too apparently.

Uploading that stuff to the apache docker hub account is tricky.  Generally
it's not allowed to put non-released software there and Fineract CN isn't
released yet.

Best Regards,
Myrle

On Wed, Mar 13, 2019 at 10:00 PM Courage Angeh 
wrote:

> They are on docker hub. On my account for now, `anh3h/fineract-cn- name>`  e.g anh3h/fineract-cn-office
>
> On Wed, Mar 13, 2019 at 4:18 PM Patrick Finken 
> wrote:
>
> > Ok. Once we have the images pushed in the docker hub, I will update your
> > scripts and test it locally.
> >
> > Regards,
> > Patrick
> >
> > On Wed, Mar 13, 2019 at 2:18 PM Courage Angeh 
> > wrote:
> >
> > > Hi Patrick,
> > >
> > > I am aware of the possibility to use minikube. But considering the
> number
> > > of services I have run simultaneously,
> > > K8 using minikube locally will just crash my computer.
> > >
> > > if have made some progress on the k8 scripts pls feel free to create a
> > PR.
> > > I will review it
> > >
> > > On Wed, Mar 13, 2019 at 2:12 PM Patrick Finken <
> patr...@finksolutions.ca
> > >
> > > wrote:
> > >
> > > > I worked on the deployment of fineract-cn on k8s and I produced some
> > > > scripts based on what courage started. I can push them to the repo. I
> > can
> > > > start working on it as soon as with have to docker image pushed to
> the
> > > > docker hub.
> > > >
> > > > @courage, you can install minikube to run k8s locally so that you
> don't
> > > > need a GKE account.
> > > >
> > > > Patrick
> > > >
> > > > On Wed, Mar 13, 2019 at 2:05 PM Courage Angeh <
> couragean...@gmail.com>
> > > > wrote:
> > > >
> > > > > The project is still under Mifos Initiative,
> > > > > https://github.com/openMF/fineract-cn-containers
> > > > >
> > > > > Most of the Dockerfiles have been pushed to the different Finerect
> CN
> > > > > repositories.  The idea
> > > > > is to have the compose file pull directly from Docker hub.
> > > > >
> > > > > On Wed, Mar 13, 2019 at 1:52 PM Awasum Yannick 
> > > > wrote:
> > > > >
> > > > > > Thanks Courage. Please, Which Github repos ? Are they on Fineract
> > > > Repos?
> > > > > Do
> > > > > > you want to put them there?
> > > > > >
> > > > > > On Wed, Mar 13, 2019 at 6:48 PM Courage Angeh <
> > > couragean...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > They are all on the GitHub repo.
> > > > > > > Still working on the swarm thing though.
> > > > > > >
> > > > > > > Previously was updating the deployment for docker and k8
> > > > > simultaneously,
> > > > > > > but my credits for my GKE account is finished so the K8 scripts
> > > are a
> > > > > > > little behind.
> > > > > > >
> > > > > > > On Wed, Mar 13, 2019 at 1:42 PM Awasum Yannick <
> > awa...@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Courage,
> > > > > > > >
> > > > > > > > Are the Docker Compose, Swarm scripts and K8 scripts all
> > > available
> > > > on
> > > > > > our
> > > > > > > > Apache Github repos? I think that will be great.
> > > > > > > >
> > > > > > > > On Wed, Mar 13, 2019 at 6:38 PM Courage Angeh <
> > > > > couragean...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Patrick and Myrle,
> > > > > > > > >
> > > > > > > > > Actually, we started some work on Kubernetes.
> > > > > > > > > If you have the physical resource to set-up Kubernetes and
> > > > > implement
> > > > > > > the
> > > > > > > > > scripts to deploy with
> > > > > > > > >  Fineract CN using k8 please go ahead to send your
> > > contribution

Re: Road Map for deploying Fineract CN

[Myrle Krantz]

Hey Patrick,

I would love to see that.  There's no reason not to do both!

Best,
Myrle

On Wed, Mar 13, 2019 at 6:29 PM Patrick Finken 
wrote:

> Hello guys,
>
> I was wondering since the industry tends toward kubernetes for containers
> orchestration, wouldn't be better to configure fineract-cn deployment with
> K8s instead of docker swarm? Or maybe keeping the two versions? I could
> help to contribute to the K8s version.
>
> regards,
> Patrick
>
> On Wed, Mar 13, 2019 at 12:24 PM Juhan Aasaru  wrote:
>
> > Hey!
> >
> > Great work, Courage!
> >
> > Regarding what you wrote in your first mail:
> > Lastly, we could publish the built Fineract CN services libraries to a
> > Maven Artifactory so developers will not have to manually clone and
> publish
> > these services by themselves.
> >
> > You didn't put that into the Jira ticket but I got an idea how we could
> > smoothly solve this step using jitpack.io
> > I thought it would be good to share this idea in the current discussion.
> >
> > Publishing a new version of a library to Maven Central is quite a work.
> > With jitpack.io one can just use a git commit hash as a version number
> (or
> > branchname-SNAPSHOT to get the build of the latest commit).
> > Basically, you one needs to configure jitpack repository as a dependency
> (I
> > use maven style as example):
> >
> > 
> > jitpack.io
> > https://jitpack.io
> > 
> >
> > and then there is need to specify the dependency using Github url:
> >
> > For example
> > https://github.com/apache/fineract-cn-identity
> > with Latest commit 6f8498d  4 days ago
> >
> > turns into the following dependency:
> >
> >  
> > com.github.aasaru
> > fineract-cn-identity
> > 6f8498d
> > 
> >
> > Jitpack checks out and builds the jar during the first request.
> > And it can be also downloaded from the public Maven repo that jitpack
> > serves. Url would be something like:
> > https://jitpack.io/com/github/apache/fineract-cn-identity/6f8498d/...
> >
> > For now this doesn't work yet (I suspect the gradle command that
> > jitpack uses doesn't result with a build
> > due to the current configuration of fineract-cn-identity build.gradle.
> This
> > needs yet to be investigated.
> >
> > Kind regards
> > Juhan
> >
> > Kontakt Courage Angeh () kirjutas kuupäeval P,
> 10.
> > märts 2019 kell 23:03:
> >
> > > Hi Guys,
> > >
> > > I have created this task on Jira:
> > > https://issues.apache.org/jira/browse/FINCN-139
> > >
> > > I think the project to should be added to the GSoC 2019 idealist.
> > >
> > > Thanks,
> > > Courage
> > >
> > > On Sat, Mar 9, 2019 at 2:04 PM Courage Angeh 
> > > wrote:
> > >
> > > > Thanks and you're welcome.
> > > >
> > > > On Sat, Mar 9, 2019, 8:01 AM Myrle Krantz  wrote:
> > > >
> > > >> Wonderful!
> > > >>
> > > >> I've merged.
> > > >>
> > > >> Thank you Courage,
> > > >> Myrle
> > > >>
> > > >> On Sat, Mar 9, 2019 at 1:14 AM Courage Angeh <
> couragean...@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > Hello guys,
> > > >> >
> > > >> > Hope this email finds you well. For the past weeks, I have been
> > > working
> > > >> on
> > > >> > moving the different Fineract CN service Dockerfiles to their
> > > respective
> > > >> > repositories. Here are the PRs, can some please view and merge
> them:
> > > >> >
> > > >> > https://github.com/apache/fineract-cn-rhythm/pull/7
> > > >> > https://github.com/apache/fineract-cn-identity/pull/8
> > > >> > https://github.com/apache/fineract-cn-office/pull/8
> > > >> > https://github.com/apache/fineract-cn-accounting/pull/9
> > > >> > https://github.com/apache/fineract-cn-deposit-account-management
> > > >> > https://github.com/apache/fineract-cn-portfolio
> > > >> > https://github.com/apache/fineract-cn-teller/pull/10
> > > >> >
> > > >> > What work is left for successful deployment?
> > > >> >
> > > >> > First, we need to configure Docker scripts to deploy and manage
> the
> > > >> system
> > > >> > on swarm mode. Then update provision and migration script to work
> > with
> > > >> > cluster environments and create the chart accounts.
> > > >> > We also have to add Jenkins to the different Fineract CN services,
> > > then
> > > >> > each service to its image on DockerHub.
> > > >> > Lastly, we could publish the built Fineract CN services libraries
> > to a
> > > >> > Maven Artifactory so developers will not have to manually clone
> and
> > > >> publish
> > > >> > these services by themselves.
> > > >> >
> > > >> > But all this needs resources like a DockerHub and Jenkins account.
> > > >> > I would like to propose this project for a GSoC project.
> > > >> >
> > > >> > Thanks,
> > > >> > Courage.
> > > >> >
> > > >>
> > > >
> > >
> >
>
>
> --
> Patrick Finken,
> Owner
>

Re: [DISCUSS] Upgrade gradle for fineract?

[Myrle Krantz]

Mua,

You are absolutely right.  I had seen that, and then forgotten about it!

Best Regards,
Myrle

On Wed, Mar 13, 2019 at 11:25 AM Mua Rachmann  wrote:

> Hello Micheal, Myrle
>
> On my findings i see Micheal already got this.
> https://issues.apache.org/jira/browse/FINERACT-700
> and here is his PR - https://github.com/apache/fineract/pull/525
> Thanks I will look for some other issue to work on. I will come back on my
> issues once its upgraded.
>
> Thanks
>
> On Wed, Mar 13, 2019 at 10:32 AM Mua Rachmann 
> wrote:
>
> > Hi Myrle,
> >
> > I could start by here if that is ok. Currently Gradle is at version 5.2
> > I am opting for this, but if it needs some core development then I would
> > say
> > some experience developer get involved to assist as I am a newbie.
> >
> > Afterwards i could continue with the spotsBug integration accordingly.
> >
> > Regards,
> >  Mua
> >
> > On Wed, Mar 13, 2019 at 10:25 AM Myrle Krantz  wrote:
> >
> >> Hey all,
> >>
> >> We have a volunteer trying to improve our build time error discovery (
> >> https://issues.apache.org/jira/browse/FINERACT-702)
> >>
> >> Mua is blocked by the fact that we're using a fairly old gradle version.
> >> Does anyone object to our upgrading the gradle version we use?
> >>
> >> Best Regards,
> >> Myrle
> >>
> >
>

[PROPOSAL] use git branches for large or risky changes

[Myrle Krantz]

Hey all,

PROPOSAL:
"Rather than ask contributors to squash everything into a single commit and
our committers to merge it all at once, we should suggest the use of git
branches for development which occurs over longer periods or larger line or
file counts.  The branch should be named after the Jira ticket it
corresponds to."

This would have the following advantages:
* make it possible for other contributors to collaborate on larger changes
that aren't yet ready for primetime.  By choosing a finer granularity of
collaboration, we would enable smaller contributions, and better engage our
more casual volunteers.
* bring the development process to Apache infrastructure earlier, which
would provide more complete data for proposals to make a contributor into a
committer.
* provide more satisfaction to contributors: they get affirmation on each
step of their process rather than getting that affirmation only once at the
end. [1]  Psychology research shows this is a more motivating and kind way
of giving feedback.
* make it easier for me, personally to follow the development process
retroactively.

If y'all don't object to my proposal in the next 72 hours then I'm going to
start applying it.

Best Regards,
Myrle

1.) https://upraise.io/blog/frequency-key-successful-performance-management/

[DISCUSS] Upgrade gradle for fineract?

[Myrle Krantz]

Hey all,

We have a volunteer trying to improve our build time error discovery (
https://issues.apache.org/jira/browse/FINERACT-702)

Mua is blocked by the fact that we're using a fairly old gradle version.
Does anyone object to our upgrading the gradle version we use?

Best Regards,
Myrle

Finding beginner's issues in JIRA

[Myrle Krantz]

Hey all,

Do we have a label for beginner's issues?  I could not find one.  I
searched Confluence, and I looked through a few issues in JIRA too.  (But I
had to stop looking because right now there's maintenance for JIRA.)

If we want our project to be welcoming to newcomers, we need to make it
easier to find beginner's issues.

If we already have such a label, let me know, and I'll add a search for it
to one of our getting started pages in confluence.  If not, I'll invent one.

Best Regards,
Myrle

Re: Road Map for deploying Fineract CN

[Myrle Krantz]

Wonderful!

I've merged.

Thank you Courage,
Myrle

On Sat, Mar 9, 2019 at 1:14 AM Courage Angeh  wrote:

> Hello guys,
>
> Hope this email finds you well. For the past weeks, I have been working on
> moving the different Fineract CN service Dockerfiles to their respective
> repositories. Here are the PRs, can some please view and merge them:
>
> https://github.com/apache/fineract-cn-rhythm/pull/7
> https://github.com/apache/fineract-cn-identity/pull/8
> https://github.com/apache/fineract-cn-office/pull/8
> https://github.com/apache/fineract-cn-accounting/pull/9
> https://github.com/apache/fineract-cn-deposit-account-management
> https://github.com/apache/fineract-cn-portfolio
> https://github.com/apache/fineract-cn-teller/pull/10
>
> What work is left for successful deployment?
>
> First, we need to configure Docker scripts to deploy and manage the system
> on swarm mode. Then update provision and migration script to work with
> cluster environments and create the chart accounts.
> We also have to add Jenkins to the different Fineract CN services, then
> each service to its image on DockerHub.
> Lastly, we could publish the built Fineract CN services libraries to a
> Maven Artifactory so developers will not have to manually clone and publish
> these services by themselves.
>
> But all this needs resources like a DockerHub and Jenkins account.
> I would like to propose this project for a GSoC project.
>
> Thanks,
> Courage.
>

Fineract slack channel

[Myrle Krantz]

Hey fine Fineracters!

The ASF has a Slack instance.  Anyone who has an apache.org email address
can sign up:

https://the-asf.slack.com/

I created a Fineract channel there nearly two years ago.  I suspect it's
not widely known (there are currently 7 members there), so I wanted to
advertise it to you again.  If you are a slack user please join!

https://the-asf.slack.com/messages/C4QPZURQQ/

This could be a good place to help other Fineract committers, or to just
chat.  Please remember to bring decision making, and general helpful
information back to this list or our other more public infrastructure.

If you'd like to join, and need help, please ask.

Best Regards,
Myrle

Re: FAQ on Wiki, structure of wiki

[Myrle Krantz]

If you're going to be carrying over information from Jira, you should look
into whether its possible to use the jira integration in confluence so that
it can be done automatically.  Then create shared filters on release
numbers and you have "one source of truth" rather than spreading
information between two systems and leaving everyone to wonder which is
canonical.

I don't know though if this will work without Infra involvement.  You may
need to ask.

Best Regards,
Myrle

On Mon, Mar 4, 2019 at 4:36 AM James Dailey  wrote:

> Hi Isaac -- Thanks for the input. I'd also like to have community members
> be able to more easily understand the needs and the priorities.  Some of
> that, I hope, can be incorporated into the FAQ.
>
> At the risk of expanding this topic just a tad, there should be a norm for
> a newbie to:
> * Consult the main page, consult the FAQ, high level pages on wiki
> * Join the listserv
> * Browse some tickets
> * Set up dev environment (if coding) or demo environment (if documentation
> or UI)
> * Dig further into wiki
> * Ask questions about specific tasks or code on the list
>
> I take Myrle's suggestion as to not have a roadmap that makes the project
> look bad when we don't meet specific dates and capabilities. We want an
> accurate reflection of the level of work going on and the actual
> priorities. The PMC report has had good information about what is actually
> going on.
>
> Looking at just roadmaps, we want to focus, I think, on three levels:
>
> *Level A)* high level product roadmap - laying out broad areas of
> improvement or enhancement to communicate "what would be useful?" ;
> in my mind, the high level community roadmap should be something that
> is able to be referenced and not changed much over an 18 month period
>this should not have dates, more about priorities
>
> *Level B)* roadmap of specific enhancements that stand in for the lack of
> "Epics"  in apache jira set up. This may be too labor intensive so only
> should be done for specific higher profile things.  ("Epics" are high
> level, can be related to a product need, and reference multiple jira
> tickets)
>
> *Level C)* a bit more controversial perhaps, but one thing I know about
> open source projects is that they (we) should also have the "anti-roadmap",
> the areas that fineract does NOT intend to do.  Why?  This gives space for
> the commercial users of the code to come up with add-ons and wrappers that
> then create the virtuous cycle of contribution. That anti-roadmap should be
> fairly broadly stated.  e.g. we won't develop deployment tools or training
> materials we leave that to other players in market
>
> So, I think for now, I'd like to mark "To-be-deprecated" on pages that are
> not active, haven't been updated in over 12 months. If they are actually
> active and relevant, then the person involved in maintaining that page can
> easily remove that term, and if not, then after a reasonable period of time
> - say 30 days - we put those pages into full Deprecated status.
>
> Given the discussion thus far and using our lazy consensus approach, I'm
> going to move forward on the restructuring first.
>
> Thanks,
> jdailey
>
>
> On Sun, Mar 3, 2019 at 6:49 PM Isaac Kamga  wrote:
>
> > Hello James,
> >
> > Thanks for the immense efforts you're putting into making the wiki more
> > visible and supple.
> >
> > Besides being open source best practice, I think the community roadmap
> > should be left there given it provides clarity to volunteers, puts open
> > issues in context and doesn't coerce anyone with tight deadlines.
> >
> > Cheers,
> > Isaac Kamga.
> >
> > On Thu, Feb 28, 2019 at 2:56 PM Myrle Krantz  wrote:
> >
> > > Hey James,
> > >
> > > The FAQ looks good.  Really good.
> > >
> > > I like your proposed restructuring of the Wiki too.  I would suggest
> two
> > > changes:
> > > * Leave a space for discussing/document architecture/design decisions.
> > > * Remove the roadmap.  We are mostly volunteers.  We shouldn't be
> making
> > > promises about future development.  We'll only be making liars out of
> > > ourselves.  And besides, this area is mostly duplication of Jira
> anyways,
> > > so creating an area like this creates unnecessary data duplication
> > > efforts.  Or it means the task data are being captured solely in
> > > confluence, which just is less good than jira for that purpose.
> > >
> > > But since I won't have time to help you on it, you can take my opinions
> > or
> > > leave them.
> &

Re: FAQ on Wiki, structure of wiki

[Myrle Krantz]

Hey James,

The FAQ looks good.  Really good.

I like your proposed restructuring of the Wiki too.  I would suggest two
changes:
* Leave a space for discussing/document architecture/design decisions.
* Remove the roadmap.  We are mostly volunteers.  We shouldn't be making
promises about future development.  We'll only be making liars out of
ourselves.  And besides, this area is mostly duplication of Jira anyways,
so creating an area like this creates unnecessary data duplication
efforts.  Or it means the task data are being captured solely in
confluence, which just is less good than jira for that purpose.

But since I won't have time to help you on it, you can take my opinions or
leave them.

Best Regards,
Myrle

On Thu, Feb 28, 2019 at 12:51 AM James Dailey 
wrote:

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

Chicago Roadshow Call for Papers looking for Fintech submissions

[Myrle Krantz]

Hey Fellow Fineracters,

Apache is organizing a mini-conference in Chicago.  They are interested in
Fintech submissions.  If anyone is close, or interested in traveling to
Chicago, check if there's a topic you'd like to talk about:

https://apachecon.com/chiroadshow19/index.html

Best Regards,
Myrle

Re: Upgrade Gradle version used in Fineract

[Myrle Krantz]

On Mon, Feb 18, 2019 at 8:39 PM Vishwas Babu <
vish...@confluxtechnologies.com> wrote:

> @Juhan : While I am not sure why the readme has instructions for
> downloading gradle wrapper separately (given that it is a part of the
> project repo and committed into the code),
>

ASF policy is that releases should not include binaries.  That includes the
gradle.jar.  So before a release is cut the gradle jar is deleted.  Many
developers work from forks.  We include the gradlel jar for them.  But we
don't want two versions of the readme.  That makes it necessary to download
the gradle wrapper or install gradle locally, and necessary to include that
in the instructions.

Best Regards,
Myrle

Re: DISCUSS: Architecture/Design for Enabling External Apps to securely access data on Apache Fineract CN

[Myrle Krantz]

My current thinking on customer facing functionality is that, for an
offline-first strategy, we should place a PouchDB/CouchDB database/cache
between the customer app and any APIs.  Domain-driven design does not
(necessarily) mean that all self-service functionality must land in one
microservice.  For example, customer authentication should probably be
handled in a service separately from retrieving account information (and
separately from back-office employee authentication).

Best Regards,
Myrle

On Tue, Feb 12, 2019 at 1:28 PM Vishwas Babu <
vish...@confluxtechnologies.com> wrote:

> Hi All,
>
> Adding some context based on our (Conflux Technologies) experiences with
> MifosX / Fineract 1.x and summarizing a recent discussion I had with a
> community member.
>
> When it comes to customer self-service, the kind of institutions that we
> have come across can be broadly divided into three categories
>
> Bucket 1:
> Traditional MFI's and Fintech lenders providing customers views of their
> accounts through online, USSD and IVR channels. These organizations also
> offer customers the ability to originate new accounts online.
> A majority of the current Fineract1.x users would fall into this bucket
>
> Bucket 2:
> Digital banks and Fintech companies which provide additional self-service
> capabilities including digital wallets, bill payments, money transfers and
> remittances. Interesting needs in this sector include features like money
> transfers without an active internet connection through channels like call
> back IVR.
>
> Bucket 3:
> Financial Institutions with agents and business correspondents who
> sometimes model their agents as customers with additional privileges and
> serve them through enhanced customer self-service apps.
> This sector occasionally has the need for offline functionality ( which is
> robust only when combined with organization enforced business rules )
>
> These applications themselves are built out independently and interface
> with Fineract 1.x through the available back-office API's (NOT the
> self-service API's which provide each customer a separate login) and
> webhook callbacks. Some of the reasoning behind this approach as against
> thin UI's talking directly to Fineract 1.x are listed below. With the
> architecture followed in Fineract-CN, when customer self-service API's are
> exposed through a new microservice, a majority of these items would be
> automatically taken care of and we would then only have to contend with the
> threat list that David alludes to.
>
> -> Back-office CBS and customer-self service has clearly demarcated
> boundaries
> Tying them up in a single deployable unit would hinder their ability to
> evolve independently. Organizations tend to be very opinionated about
> self-service channels and these apps follow short release cycles with some
> amount of customization going into each new implementation.
> - A customer on the self-service app needn't necessarily be present on the
> CBS.
> Ex: Self-service apps for organizations like Fintech lenders typically
> allow users to sign up, create a profile and apply for a loan.
> - Customer/loans/savings statuses and lifecycle on the self-service app do
> not map directly with those on the CBS.
> For example, an application initiated by a customer goes through a process
> of automated and manual sanity checks on the self-service apps, after which
> they are moved to the CBS with a predefined state to join the regular
> workflow (de-duplication, eligibility and credit checks etc). This is
> typically different from the lifecycle of an application originated by a
> teller.
> - Fine-grained control is required on the granularity of information
> presented on the self-service apps, which is different from that presented
> to the back office. Ex: All products in the CBS are not shown as options in
> the self-service portal. Similarly, for the products that are shown, the
> granularity of information in the terms is a greatly reduced subset of that
> available in the product definition at the CBS.
>
> -> Deployment and scalability scenarios
>  While these issues can be easily addressed through a combination of code
> modifications on the self-service API's of Fineract 1.x and deployment
> configurations, they have been listed here for completeness.
> - Client facing apps need to be scaled independently of back-office facing
> CBS and also need to have different configurations for rate limiting etc.
> - The client-facing apps should cache all lookup data fetched from the CBS,
> route read traffic to a cluster of Fineract1.x servers talking to
> replicated databases etc to ensure that the traffic to the cluster serving
> the back-office is kept to a minimum and remains largely unaffected by
> spikes in customer traffic.
> - Easy to turn off, monitor and audit client-self service happening through
> a single login at Fineract 1.x
>
> -> Security implications
>  While these issues can be easily addressed through a 

Enable Travis for Fineract repo?

[Myrle Krantz]

Hey all,

Michael has suggested enabling Travis for the Fineract repo.  What this
would do is automatically call the build on code submitted with a PR.  We
could also configure it to automatically run integration tests (that will
only be useful if the integration tests are currently working).  This will
make merging good PRs a little easier and rejecting PRs which break the
build a lot easier.

This question is only for Fineract 1.x currently.  Fineract CN will require
a bit more work to get CI support running because of the way it is spread
across multiple repositories.

What do you think?  If there are no objections in the next 72 hours, I'd
like to give Infra the go-ahead.

Best Regards,
Myrle

Re: [ANNOUNCE] Apache Fineract Committer Sanyam Goel

[Myrle Krantz]

Congratulations Sanyam!

Best Regards,
Myrle

On Sun, Feb 10, 2019 at 3:15 AM Courage Angeh 
wrote:

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

Re: One-process deployment of Fineract CN

[Myrle Krantz]

My idea was to produce jars without mains and then run them all from one
main.  This would mean that they all run under the same service name.  This
in turn makes it necessary to solve problems around collisions:

* In most cases endpoints don't have the same names, but there's an
"iniitialize" in every service.
* permissions would need to include the name of the service in
the @Permittable annotation.

It sounds like a small set of changes, but it's actually quite extensive.
The changes to @Permittable require a lot of re-engineering in anubis.

If one process can run multiple services and keep their names, that's so
much better.

Best Regards,
Myrle

On Fri, Feb 8, 2019 at 3:39 AM Isaac Kamga  wrote:

>
> Myrle, thanks a million for your input. While I'm digging into ways to fix
> the current errors, can you kindly share the other approach which you
> thought would be less promising to solve this issue ? Maybe others
> interested could try that out in parallel too.
>
> Cheers,
> Isaac Kamga.
>

Re: One-process deployment of Fineract CN

[Myrle Krantz]

Kelvin,

The problem Isaac is trying to solve is that many of our contributors don’t
have enough memory or fast enough swap speeds to run the services all at
once on their computers for doing development testing. Also startup speeds
are very slow because some services need to be completely up and
provisioned before other services can be started.

Isaac is not trying to create a production environment here.  If he were,
than the rate at which requests can be handled would, of course, matter.
But demo-server was never intended as a production environment; correct
production environment will be *highly* dependent on use case.

Nonetheless I would welcome your contribution of docker specifications. I
do think the docker files should go into the service repositories rather
than the demo-server. There are also exciting ideas in circulation for
doing this with OpenShift instead.

Best Regards,
Myrle

On Sat, Feb 2, 2019 at 9:04 PM Kelvin Ikome  wrote:

> Hi Isaac,
>
> Technically, running the services within a single process should reduce
> required number of virtual processors (cores). However, this might also
> lead to a rise in processing speed.
>
> For example, if using one process per service requires about 2.0Ghz Quad
> core processing power, running the very same services using a single thread
> per service might require about 3.0Ghz Dual core processing power.
>
> Using multi threading to run the microservices within a single process is a
> great idea and will help simplify the process of running the platform.
> However, I don't think this might be the best approach to optimize the
> required processing power. The most effective way to run the platform I can
> think of would be to ditch demo server and run the services within docker
> containers. In addition to that, using containers gives you the flexibility
> of working with each individual service in a sort of "plug and play" manner
> as well.
>
> Just my thoughts :)
>
> On Mon, Jan 28, 2019 at 8:54 PM Myrle Krantz  wrote:
>
> > Sorry Isaac,
> >
> > can't help you here.  I had an entirely different idea in mind for how to
> > do this, and yours looks more promising, actually.  But I can't tell you
> > why it's not working.
> >
> > Best Regards,
> > Myrle
> >
> > On Sun, Jan 27, 2019 at 12:46 AM Isaac Kamga 
> > wrote:
> >
> > > Happy weekend fineracters,
> > >
> > > Hope this email finds you in good health.
> > >
> > > In an effort to facilitate local development of Fineract CN, I picked
> up
> > > the One-process deployment issue [1] which when resolved can enable
> > > developers to run the platform in a single process.
> > >
> > > Some research led me to the possibility of running each microservice
> in a
> > > it's own ClassLoader while ensuring that the ServiceRunner uses a
> single
> > > JVM to run in a single process. After having tried to adapt the method
> in
> > > [2] where several Spring Boot apps are launched in the same process to
> > our
> > > Service-starter and demo-server, I encountered this error [3]. The code
> > of
> > > the workdone so far is on the *oneprocess* branch of my fork of
> > > service-starter[4] and demo-server [5].
> > >
> > > @Myrle Krantz   Is there a way to have the "java
> -jar
> > > xyz-service-boot-0.1.0-BUILD-SNAPSHOT.jar" command run a single Thread
> as
> > > opposed to running in the process assigned by ProcessBuilder() ?
> > >
> > > @Markus Geiss  , is it possible that what could help
> in
> > > this case is using an entire Pool of threads to get this executed ?
> > Asking
> > > as you developed the fineract-cn-async [6] library and I observed that
> > upon
> > > running demo-server, when the processors on my machine get exhausted,
> the
> > > logs indicate that a separate thread (not main) shows up to run any
> > > available service like Notifications and Groups.
> > >
> > > Any help from the community would be much appreciated.
> > >
> > > At Your Service,
> > > Isaac Kamga.
> > >
> > > [1] https://issues.apache.org/jira/browse/FINCN-25
> > > [2]
> > >
> >
> https://github.com/rameez4ever/springboot-demo/tree/master/springboot-multi-service-launcher
> > >
> > > [3] https://pastebin.com/qBDW52Y5
> > > [4]
> > https://github.com/Izakey/fineract-cn-service-starter/tree/oneprocess
> > > [5] https://github.com/Izakey/fineract-cn-demo-server/tree/oneprocess
> > > [6] https://github.com/apache/fineract-cn-async
> > >
> >
>

Re: One-process deployment of Fineract CN

[Myrle Krantz]

Sorry Isaac,

can't help you here.  I had an entirely different idea in mind for how to
do this, and yours looks more promising, actually.  But I can't tell you
why it's not working.

Best Regards,
Myrle

On Sun, Jan 27, 2019 at 12:46 AM Isaac Kamga  wrote:

> Happy weekend fineracters,
>
> Hope this email finds you in good health.
>
> In an effort to facilitate local development of Fineract CN, I picked up
> the One-process deployment issue [1] which when resolved can enable
> developers to run the platform in a single process.
>
> Some research led me to the possibility of running each microservice in a
> it's own ClassLoader while ensuring that the ServiceRunner uses a single
> JVM to run in a single process. After having tried to adapt the method in
> [2] where several Spring Boot apps are launched in the same process to our
> Service-starter and demo-server, I encountered this error [3]. The code of
> the workdone so far is on the *oneprocess* branch of my fork of
> service-starter[4] and demo-server [5].
>
> @Myrle Krantz   Is there a way to have the "java -jar
> xyz-service-boot-0.1.0-BUILD-SNAPSHOT.jar" command run a single Thread as
> opposed to running in the process assigned by ProcessBuilder() ?
>
> @Markus Geiss  , is it possible that what could help in
> this case is using an entire Pool of threads to get this executed ? Asking
> as you developed the fineract-cn-async [6] library and I observed that upon
> running demo-server, when the processors on my machine get exhausted, the
> logs indicate that a separate thread (not main) shows up to run any
> available service like Notifications and Groups.
>
> Any help from the community would be much appreciated.
>
> At Your Service,
> Isaac Kamga.
>
> [1] https://issues.apache.org/jira/browse/FINCN-25
> [2]
> https://github.com/rameez4ever/springboot-demo/tree/master/springboot-multi-service-launcher
>
> [3] https://pastebin.com/qBDW52Y5
> [4] https://github.com/Izakey/fineract-cn-service-starter/tree/oneprocess
> [5] https://github.com/Izakey/fineract-cn-demo-server/tree/oneprocess
> [6] https://github.com/apache/fineract-cn-async
>

Re: Review PR

[Myrle Krantz]

Hey Santosh,

You are a committer.  You should have permissions to merge PR's unless you
haven't followed the steps to link your github account to your
Apache account.

Follow the instructions in these two links, and you should be able to merge
PRs:
https://gitbox.apache.org/setup/
https://github.com/settings/two_factor_authentication/configure

If after you've followed those steps, you are still having difficulties,
please file a ticket with INFRA.

Best Regards,
Myrle



On Fri, Jan 25, 2019 at 4:21 AM Santosh Math <
sant...@confluxtechnologies.com> wrote:

> Hi Ed,
>
> The following PR  is approved by Rahul. I don't have permission to merge
> it.
> https://github.com/apache/fineract/pull/511
>
>
> On Wed, Jan 23, 2019 at 11:01 AM Santosh Math <
> sant...@confluxtechnologies.com> wrote:
>
> > Hi Devs,
> >
> > Can someone please review the PR sent by Courage (in Cc)?
> >
> > https://github.com/apache/fineract/pull/511
> >
> > --
> > Thanks & Regards
> >
> > Santosh Math
> >
> > *QA Engineer*
> >
> > *Conflux Technologies Pvt Ltd *
> > | *Office*: +91-080-41208662 |
> >
> > *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> > Bengaluru, Karnataka, 560043 INDIA
> >
>
>
> --
> Thanks & Regards
>
> Santosh Math
>
> *QA Engineer*
>
> *Conflux Technologies Pvt Ltd *
> | *Office*: +91-080-41208662 |
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>

Re: Fineract 1.3.0 Release Notes Published

[Myrle Krantz]

Thank *you* Vishwas for completing the last step of the release!

: o),
Myrle

On Sat, Jan 12, 2019 at 1:15 AM Vishwas Babu <
vish...@confluxtechnologies.com> wrote:

> Hi Myrle,
>
> Thanks for bringing this issue to the communities attention. I have sent
> out the announce mail for 1.2.0.
>
> Regards,
> Vishwas
>
>
> On Fri, Jan 11, 2019 at 8:30 AM Myrle Krantz  wrote:
>
> > Hey Ed,
> >
> > The Fineract 1.2 release still isn't complete.
> >
> > An announce email hasn't been sent to annou...@apache.org.
> >
> > An attempt at an announcement was made by Santosh here:
> >
> >
> https://lists.apache.org/thread.html/20839b7a902de5df175f7bcbed72e1125c01a9b25e390e1e6ea30c93@%3Cdev.fineract.apache.org%3E
> >
> > But it was unsuccessful.  I explained the reason and gave an example of
> how
> > to do it correctly here:
> >
> >
> https://lists.apache.org/thread.html/c6fbe766f5b455d74bdcda99d442d8cb2259403682e751b95a5396bf@%3Cdev.fineract.apache.org%3E
> >
> > It's actually not difficult.  It's important to me to spread the
> knowledge
> > about how to do it correctly.  So, unlike with 1.1, I'm not going to do
> it
> > myself.
> >
> > Best Regards,
> > Myrle
> >
> >
> > On Wed, Jan 9, 2019 at 1:54 AM Ed Cable  wrote:
> >
> > > Hello Fineract community,
> > >
> > > The next release of Fineract is slightly behind schedule but we're
> > getting
> > > closer to our target of monthly releases. As usual we could use
> > assistance
> > > with reviewing of outstanding pull requests. The release notes have
> been
> > > published at
> > >
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342874=Html=12319420
> > >
> > > It's also been added to the release page at
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FINERACT/1.3.0+-+Apache+Fineract
> > >
> > > Final QA is underway but you can continue with testing process at this
> > > staging server located at https://staging.openmf.org (mifos/password).
> > >
> > > January 7 was the original intended release date but it will now be
> next
> > > week after the Final QA and vote takes place.
> > >
> > > Emails will be sent out soon with plans for Fineract 1.4 and any
> tickets
> > > that didn't make their way into 1.3 - we'll include a list of
> outstanding
> > > bugs that volunteers could work on.
> > >
> > > --
> > > *Ed Cable*
> > > President/CEO, Mifos Initiative
> > > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> > >
> > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> > > <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
> > >
> >
>

Re: Revamping logo slightly in time for FOSDEM?

[Myrle Krantz]

+1

For those who don’t know: Daniel works for Infra and did the wonderful
ApacheCon intro for Montreal this year. He’s helped Fineract “behind the
scenes” for a long time now.

I will indeed be at FOSDEM on the second day, as I expressed on the comdev
list.

Best Regards,
Myrle

On Sat, Jan 19, 2019 at 10:05 AM Daniel Gruno  wrote:

> Hi, awesome Fineract people.
>
> I was looking through the FOSDEM sticker orders, and thus the Fineract
> logo, and I was wondering if you as a project were willing to get the
> logo touched up a bit before then?
>
> My proposed touch-up can be found at https://i.imgur.com/1w9X0Cb.png,
> and if you would like to use this, I can get the original SVG uploaded
> to our central database and hopefully it will make it to FOSDEM in time
> :). And if you prefer to stick with the original logo, that's also
> totally cool - just throwing this to you in case.
>
> Whatever the outcome, if you could please let me and/or Sharan Foga
> (sha...@apache.org) know which one you prefer within a day or two, we
> can get the stickers sorted.
>
> With regards,
> Daniel.
>

Re: Fineract 1.3.0 Release Notes Published

[Myrle Krantz]

Hey Ed,

The Fineract 1.2 release still isn't complete.

An announce email hasn't been sent to annou...@apache.org.

An attempt at an announcement was made by Santosh here:
https://lists.apache.org/thread.html/20839b7a902de5df175f7bcbed72e1125c01a9b25e390e1e6ea30c93@%3Cdev.fineract.apache.org%3E

But it was unsuccessful.  I explained the reason and gave an example of how
to do it correctly here:
https://lists.apache.org/thread.html/c6fbe766f5b455d74bdcda99d442d8cb2259403682e751b95a5396bf@%3Cdev.fineract.apache.org%3E

It's actually not difficult.  It's important to me to spread the knowledge
about how to do it correctly.  So, unlike with 1.1, I'm not going to do it
myself.

Best Regards,
Myrle


On Wed, Jan 9, 2019 at 1:54 AM Ed Cable  wrote:

> Hello Fineract community,
>
> The next release of Fineract is slightly behind schedule but we're getting
> closer to our target of monthly releases. As usual we could use assistance
> with reviewing of outstanding pull requests. The release notes have been
> published at
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342874=Html=12319420
>
> It's also been added to the release page at
>
> https://cwiki.apache.org/confluence/display/FINERACT/1.3.0+-+Apache+Fineract
>
> Final QA is underway but you can continue with testing process at this
> staging server located at https://staging.openmf.org (mifos/password).
>
> January 7 was the original intended release date but it will now be next
> week after the Final QA and vote takes place.
>
> Emails will be sent out soon with plans for Fineract 1.4 and any tickets
> that didn't make their way into 1.3 - we'll include a list of outstanding
> bugs that volunteers could work on.
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>

Re: [ANNOUNCE] Apache Fineract 1.2.0 Release

[Myrle Krantz]

Hey Shruthi,

I've merged your PR.  You just need to merge it to the branch asf-site as
well, and then it will automagically publish.

Greets,
Myrle

On Tue, Dec 11, 2018 at 7:12 AM Shruthi M R 
wrote:

> Thanks everyone.
>
> I have raised a PR for fineract-site containing changes that point to 1.2.0
> release. Kindly review it and let me know if any changes need to be made  (
> https://github.com/apache/fineract-site/pull/14).
>
> Once those changes are merged, we have to update the website. Can someone
> please share details on how & who can refresh/restart so that I can point
> to the website  and send a mail to announce.apache.org. !
>
> Thank you,
> Shruthi
>
> On Mon, Dec 10, 2018 at 3:12 PM Myrle Krantz  wrote:
>
> > Excellent job Shruthi,
> >
> > Unfortunately, the e-mail was not posted to announce.  You probably know
> > this, because announce should have given you an explanation when it
> > "bounced" your message.  But you may not have been certain of how to
> > resolve this.  Moderators for announce always reject emails which link
> > directly to our download repositories instead of going through Apache
> > mirrors.  Here is an example of an announce mail for a Fineract release
> > which was accepted.
> >
> >
> >
> https://lists.apache.org/thread.html/e76e5402ab0eaea5bdf189d023d4758f5213e5775208b69b252730af@%3Cannounce.apache.org%3E
> >
> > Best Regards,
> > Myrle
> >
> > On Mon, Dec 10, 2018 at 9:11 AM Santosh Math <
> > sant...@confluxtechnologies.com> wrote:
> >
> >> Thank you Shruthi, You really did a great job.
> >>
> >> On Sat, Dec 8, 2018 at 4:08 PM Sendoro Juma 
> wrote:
> >>
> >> >  Dear Shruthi, Devs,
> >> >
> >> >
> >> > Congrats for job well done...
> >> >
> >> >
> >> > Now looking forward for  v1.3.0
> >> >
> >> >
> >> >
> >> > >
> >> > > On December 8, 2018 at 1:22 PM Shruthi M R <
> >> > shruthiraja...@apache.org> wrote:
> >> > >
> >> > > Hi all,
> >> > > The Apache Fineract team would like to announce the release of
> >> Apache
> >> > > Fineract 1.2.0 with source and binary artifacts.
> >> > > Apache Fineract is an open source system for core banking as a
> >> > > platform. Fineract provides a reliable, robust, and affordable
> >> > > solution for entrepreneurs,
> >> > > financial institutions, and service providers to offer financial
> >> > > services to the world’s 2 billion under banked and unbanked.
> >> > >
> >> > > More details regarding Apache Fineract can be found at
> >> > > http://fineract.apache.org/
> >> > > The release artifacts can be downloaded here:
> >> > > https://dist.apache.org/repos/dist/release/fineract/
> >> > > The release notes can be found here:
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract
> >> > >
> >> > > Thanks!
> >> > > The Apache Fineract Team
> >> > >
> >> >
> >> >
> >> >  Thanks
> >> >
> >>
> >>
> >> --
> >> Thanks & Regards
> >>
> >> Santosh Math
> >>
> >> *QA Engineer*
> >>
> >> *Conflux Technologies Pvt Ltd <http://www.confluxtechnologies.com/>*
> >> | *Office*: +91-080-41208662 |
> >>
> >> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> >> Bengaluru, Karnataka, 560043 INDIA
> >>
> >
>

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

[Myrle Krantz]

Hey Isaac,

Hibernate validator was always Apache licensed.  It's Hibernate JPA which
is the problem.

Best Regards,
Myrle

On Sat, Dec 8, 2018 at 1:55 AM Isaac Kamga  wrote:

> Happy weekend fineracters,
>
> It appears the hibernate-validator is Apache licensed as this link[1]
> shows ?  Their license probably changed sometime this year.
> Is there any other hibernate tool which we used to develop Fineract CN ?
>
> Cheers,
> Isaac Kamga.
>
> [1]
> https://github.com/hibernate/hibernate-validator/blob/master/license.txt
>
> On Tue, Nov 20, 2018 at 1:43 PM Sendoro Juma  wrote:
>
>> Indeed Hurray to you!!!
>>
>>
>> With Best Regards
>>
>> Sendoro
>>
>> On November 20, 2018 at 3:06 PM Isaac Kamga 
>> wrote:
>>
>> Hurray !
>>
>> It took about a dozen hours for the created repo to show option "...or
>> push
>> existing repo from command line" on my end although it finally did.
>>
>> So the PostgreSQL repo is now on Apache Infrastructure
>> <https://github.com/apache/fineract-cn-postgresql> and work can continue
>> on
>> there.
>>
>> On Tue, Nov 20, 2018 at 12:55 PM Isaac Kamga 
>> wrote:
>>
>> Hello there,
>>
>> The INFRA team has created the repo
>> <https://github.com/apache/fineract-cn-postgresql> and I can't push to it
>> because I don't have the right karma to do so.
>>
>> Can anyone on the PMC get the code
>> <https://github.com/Izakey/fineract-cn-postgresql> I've worked on and
>> push it to the newly created repository ?
>>
>> Cheers,
>> Isaac Kamga.
>>
>> On Mon, Nov 19, 2018 at 11:06 PM Isaac Kamga 
>> wrote:
>>
>> Hello there,
>>
>> Thanks for your response Myrle.
>>
>> I tried creating a repo using these instructions
>> <
>> https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN>
>> and
>> hit an error, so I created an INFRA ticket
>> <https://issues.apache.org/jira/browse/INFRA-17273> to address it.
>>
>> In the meantime, if anyone is able to successfully create the ticket
>> using the details in the aforementioned ticket's description, it will be a
>> step in the right direction.
>>
>> Cheers,
>> Isaac Kamga.
>>
>> On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz  wrote:
>>
>> Hey Isaac,
>>
>> Awesome Isaac. In general it's better to put stuff into Apache Infra
>> earlier rather than later. Things don't have to be finished. You're a
>> committer, so you have all the karma you need to create that repo. If no
>> one else objects, then do it.
>>
>> : o),
>> Myrle
>>
>>
>>
>>
>> With Best Regards
>>
>> Sendoro Juma
>>
>> ---
>>
>> SingoAfrica Limited
>> Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
>>
>> P.O BOX 78908 | 14121 Dar es Salaam
>>
>> info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz
>>
>>
>>
>

Re: [ANNOUNCE] Apache Fineract 1.2.0 Release

[Myrle Krantz]

Excellent job Shruthi,

Unfortunately, the e-mail was not posted to announce.  You probably know
this, because announce should have given you an explanation when it
"bounced" your message.  But you may not have been certain of how to
resolve this.  Moderators for announce always reject emails which link
directly to our download repositories instead of going through Apache
mirrors.  Here is an example of an announce mail for a Fineract release
which was accepted.

https://lists.apache.org/thread.html/e76e5402ab0eaea5bdf189d023d4758f5213e5775208b69b252730af@%3Cannounce.apache.org%3E

Best Regards,
Myrle

On Mon, Dec 10, 2018 at 9:11 AM Santosh Math <
sant...@confluxtechnologies.com> wrote:

> Thank you Shruthi, You really did a great job.
>
> On Sat, Dec 8, 2018 at 4:08 PM Sendoro Juma  wrote:
>
> >  Dear Shruthi, Devs,
> >
> >
> > Congrats for job well done...
> >
> >
> > Now looking forward for  v1.3.0
> >
> >
> >
> > >
> > > On December 8, 2018 at 1:22 PM Shruthi M R <
> > shruthiraja...@apache.org> wrote:
> > >
> > > Hi all,
> > > The Apache Fineract team would like to announce the release of
> Apache
> > > Fineract 1.2.0 with source and binary artifacts.
> > > Apache Fineract is an open source system for core banking as a
> > > platform. Fineract provides a reliable, robust, and affordable
> > > solution for entrepreneurs,
> > > financial institutions, and service providers to offer financial
> > > services to the world’s 2 billion under banked and unbanked.
> > >
> > > More details regarding Apache Fineract can be found at
> > > http://fineract.apache.org/
> > > The release artifacts can be downloaded here:
> > > https://dist.apache.org/repos/dist/release/fineract/
> > > The release notes can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract
> > >
> > > Thanks!
> > > The Apache Fineract Team
> > >
> >
> >
> >  Thanks
> >
>
>
> --
> Thanks & Regards
>
> Santosh Math
>
> *QA Engineer*
>
> *Conflux Technologies Pvt Ltd *
> | *Office*: +91-080-41208662 |
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>

Re: Almost no one is subscribed to our security mailing list

[Myrle Krantz]

Hello Zayyad,

Thank you for the excellent question.

The security list is a list that only committers and PMC members can view.
But anyone can send emails to it.  The security list can be used to report
security vulnerabilities.  It can also be used to handle responses to those
vulnerabilities.

If you are wondering how security vulnerabilities are handled at Apache,
this is an excellent guide:
https://www.apache.org/security/committers.html

When we started a security list it was to replace the use of the private
list for planning security responses.  One potential advantage to this
change is that committers can participate, whereas only PMC members can
participate on private.

By creating the security list, we offered all of our committers a
promotion.  : o)

Best Regards,
Myrle


On Wed, Dec 5, 2018 at 11:54 AM Zayyad A. Said <
zay...@intrasofttechnologies.com> wrote:

> Dear Myrle,
>
> Was the list created to serve a special purpose other than what the dev
> list serves?
>
> It's critical to understand the purpose of the list before one subscribes
> to it.
>
> Kindly enlighten us.
>
> Regards,
>
> Zayyad A. Said
> On Wed, Dec 5, 2018, 13:16 Myrle Krantz  wrote:
>
>> Current subscribees are:
>>
>> * me
>> * Ed
>> * Vishwas
>>
>> Thank you Ed and Vishwas for sharing responsibility for this critical
>> aspect of our project.
>>
>> Potential subscribees are anyone who has a committership or is on the PMC
>> of Fineract.
>>
>> If you wish to subscribe please write an email to
>> security-subscr...@fineract.apache.org.  If you have any difficulties,
>> please write an email to dev@fineract.apache.org to let us know.
>>
>> Unless people start subscribing, I will ask INFRA to remove the mailing
>> list.  With so few people subscribed, the security mailing list cannot
>> serve its purpose, and will be more of a problem than a solution.
>>
>> Best Regards,
>> Myrle
>>
>

Almost no one is subscribed to our security mailing list

[Myrle Krantz]

Current subscribees are:

* me
* Ed
* Vishwas

Thank you Ed and Vishwas for sharing responsibility for this critical
aspect of our project.

Potential subscribees are anyone who has a committership or is on the PMC
of Fineract.

If you wish to subscribe please write an email to
security-subscr...@fineract.apache.org.  If you have any difficulties,
please write an email to dev@fineract.apache.org to let us know.

Unless people start subscribing, I will ask INFRA to remove the mailing
list.  With so few people subscribed, the security mailing list cannot
serve its purpose, and will be more of a problem than a solution.

Best Regards,
Myrle

Re: Creating a security mailing list for Fineract

[Myrle Krantz]

Hey all,

I've created the security list: secur...@fineract.apache.org.

I put the people as moderators who were moderating our other lists
(subtracting our mentors).

Any committer or PMC member who wants to can now subscribe.  Just write an
email to security-subscr...@fineract.apache.org

Best Regards,
Myrle

P.S.  In the process I learned about this: https://selfserve.apache.org/
Cool stuff.

On Mon, Nov 26, 2018 at 4:40 PM Myrle Krantz  wrote:

> Alright,
>
> I'd say we have consensus.  I'll file the INFRA ticket.
>
> Best Regards,
> Myrle
>
> On Wed, Nov 21, 2018 at 8:12 PM Sendoro Juma  wrote:
>
>> +1
>>
>> On November 21, 2018 at 2:18 PM Myrle Krantz  wrote:
>>
>> Hey all,
>>
>> I'd like to create a security list for Apache Fineract. The list would be
>> private, but archived. Anyone who is on the PMC or who is a committer
>> could subscribe. I expect traffic to be very low.
>>
>> This would make it possible for committers who aren't on the Fineract PMC
>> to participate in the response to reports of security-related bugs.
>>
>> I would moderate this list + anyone else who wants to help moderate.
>>
>> What do you think? If you are in favor, would you be willing to help
>> moderate this new list?
>>
>> Best Regards,
>> Myrle
>>
>>
>>
>>
>> With Best Regards
>>
>> Sendoro Juma
>>
>> ---
>>
>> SingoAfrica Limited
>> Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
>>
>> P.O BOX 78908 | 14121 Dar es Salaam
>>
>> info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz
>>
>>
>>
>

Re: Creating a security mailing list for Fineract

[Myrle Krantz]

Alright,

I'd say we have consensus.  I'll file the INFRA ticket.

Best Regards,
Myrle

On Wed, Nov 21, 2018 at 8:12 PM Sendoro Juma  wrote:

> +1
>
> On November 21, 2018 at 2:18 PM Myrle Krantz  wrote:
>
> Hey all,
>
> I'd like to create a security list for Apache Fineract. The list would be
> private, but archived. Anyone who is on the PMC or who is a committer
> could subscribe. I expect traffic to be very low.
>
> This would make it possible for committers who aren't on the Fineract PMC
> to participate in the response to reports of security-related bugs.
>
> I would moderate this list + anyone else who wants to help moderate.
>
> What do you think? If you are in favor, would you be willing to help
> moderate this new list?
>
> Best Regards,
> Myrle
>
>
>
>
> With Best Regards
>
> Sendoro Juma
>
> ---
>
> SingoAfrica Limited
> Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
>
> P.O BOX 78908 | 14121 Dar es Salaam
>
> info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz
>
>
>

Creating a security mailing list for Fineract

[Myrle Krantz]

Hey all,

I'd like to create a security list for Apache Fineract.  The list would be
private, but archived.  Anyone who is on the PMC or who is a committer
could subscribe.  I expect traffic to be very low.

This would make it possible for committers who aren't on the Fineract PMC
to participate in the response to reports of security-related bugs.

I would moderate this list + anyone else who wants to help moderate.

What do you think?  If you are in favor, would you be willing to help
moderate this new list?

Best Regards,
Myrle

Re: [Mifos-users] Announcement: Fineract 1.2.0.RELEASE

[Myrle Krantz]

All respondents:

Please stop sending emails about work on the Fineract release to
d...@community.apache.org .

My emails to the mifos lists always bounce, so I ask someone who has access
to those lists to also post this information there.

Best Regards,
Myrle

On Wed, Nov 21, 2018 at 7:06 AM Abiy Atsbha  wrote:

> Dear Santosh,
>
> I have been trying to access the staging demo and I have some points to
> suggest:
>
> 1. The system is not accepting decimals. In cash management/ cash
> allocation and in saving, loan dispalying invalid decimal.
>
> 2. The value in date fields are not capturing, you will have to click back
> again for the system to capture.
>
> Regards,
> Abuy A.
>
> On Tue, Nov 20, 2018 at 10:26 AM Santosh Math <
> sant...@confluxtechnologies.com> wrote:
>
>> Dear Community,
>>
>> We are pleased to announce that the release of Fineract 1.2.0 is
>> scheduled on November 30, 2018, pending the final QA and a vote to take
>> place next week.You can help with the testing process by accessing the
>> staging server at https://staging.openmf.org (mifos/password)
>>
>> You can see and track the Release Notes in the following link:
>>
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319420=12342856
>> 
>>
>> Any tickets that didn't make it into 1.2 will be going into Fineract 1.3,
>> of which planning is already underway.
>>
>> We will call for vote of Fineract 1.2.0 release within few days and I
>> expect you to clarify any doubts/queries referring the above link of
>> Release Notes.
>>
>> --
>> Thanks & Regards
>>
>> Santosh Math
>>
>> *QA Engineer*
>>
>> *Conflux Technologies Pvt Ltd *
>> | *Office*: +91-080-41208662 |
>>
>> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
>> Bengaluru, Karnataka, 560043
>> 
>>  INDIA
>> 
>> ___
>> Mifos-users mailing list
>> mifos-us...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mifos-users
>>
>

[ANNOUNCE] Apache Fineract Committer Mark van Veen

[Myrle Krantz]

Hello Fantastic Fineracters,

I'm proud to announce another Apache Fineract committer!

Congratulations Mark van Veen, and thank you for joining us.

Mark is a Software Engineer at Kuelap.  He wrote the initial code for the
fims web app on Fineract CN.  He has contributed conceptually to most of
the CN services as well.  Mark and I have been colleagues at two different
companies, and I have always enjoyed working with him.

Thanks,
Myrle Krantz
PMC Member, Apache Fineract

Re: Announcement: Fineract 1.2.0.RELEASE

[Myrle Krantz]

Hello Santosh,

In general, it's not an announcement until the Fineract PMC approves the
release, and we haven't put it up for a vote yet.  Once that is
accomplished, d...@community.apache.org is not the place to announce it when
that comes time either.  dev@community is for discussing community
development in an over-arching Apache context.

With respect to the specifics, I'll respond further on the dev@fineract
list.

Best Regards,
Myrle
PMC Member, Apache Fineract

On Tue, Nov 20, 2018 at 8:25 AM Santosh Math <
sant...@confluxtechnologies.com> wrote:

> Dear Community,
>
> We are pleased to announce that the release of Fineract 1.2.0 is scheduled
> on November 30, 2018, pending the final QA and a vote to take place next
> week.You can help with the testing process by accessing the staging server
> at https://staging.openmf.org (mifos/password)
>
> You can see and track the Release Notes in the following link:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319420=12342856
> <
> https://www.google.com/url?q=https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId%3D12319420%26version%3D12342856=D=hangouts=1542778870955000=AFQjCNFO2eKmn0ggbKEv3vrVJyDLEnl7yA
> >
>
> Any tickets that didn't make it into 1.2 will be going into Fineract 1.3,
> of which planning is already underway.
>
> We will call for vote of Fineract 1.2.0 release within few days and I
> expect you to clarify any doubts/queries referring the above link of
> Release Notes.
>
> --
> Thanks & Regards
>
> Santosh Math
>
> *QA Engineer*
>
> *Conflux Technologies Pvt Ltd *
> | *Office*: +91-080-41208662 |
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>

Re: Announcement: Fineract 1.2.0.RELEASE

[Myrle Krantz]

So and now for the Fineracters,

Santosh, can you please tag the code in github for the version that's on
the test server?  This would improve transparency, and make me feel more
comfortable when it comes time to vote on the release.

Also, can you please provide a pointer to where planning for 1.3 is
underway?

Best Regards,
Myrle

On Tue, Nov 20, 2018 at 9:34 AM Myrle Krantz  wrote:

> Hello Santosh,
>
> In general, it's not an announcement until the Fineract PMC approves the
> release, and we haven't put it up for a vote yet.  Once that is
> accomplished, d...@community.apache.org is not the place to announce it
> when that comes time either.  dev@community is for discussing community
> development in an over-arching Apache context.
>
> With respect to the specifics, I'll respond further on the dev@fineract
> list.
>
> Best Regards,
> Myrle
> PMC Member, Apache Fineract
>
> On Tue, Nov 20, 2018 at 8:25 AM Santosh Math <
> sant...@confluxtechnologies.com> wrote:
>
>> Dear Community,
>>
>> We are pleased to announce that the release of Fineract 1.2.0 is scheduled
>> on November 30, 2018, pending the final QA and a vote to take place next
>> week.You can help with the testing process by accessing the staging server
>> at https://staging.openmf.org (mifos/password)
>>
>> You can see and track the Release Notes in the following link:
>>
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319420=12342856
>> <
>> https://www.google.com/url?q=https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId%3D12319420%26version%3D12342856=D=hangouts=1542778870955000=AFQjCNFO2eKmn0ggbKEv3vrVJyDLEnl7yA
>> >
>>
>> Any tickets that didn't make it into 1.2 will be going into Fineract 1.3,
>> of which planning is already underway.
>>
>> We will call for vote of Fineract 1.2.0 release within few days and I
>> expect you to clarify any doubts/queries referring the above link of
>> Release Notes.
>>
>> --
>> Thanks & Regards
>>
>> Santosh Math
>>
>> *QA Engineer*
>>
>> *Conflux Technologies Pvt Ltd <http://www.confluxtechnologies.com/>*
>> | *Office*: +91-080-41208662 |
>>
>> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
>> Bengaluru, Karnataka, 560043 INDIA
>>
>

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

[Myrle Krantz]

Hey Isaac,

Awesome Isaac.  In general it's better to put stuff into Apache Infra
earlier rather than later.  Things don't have to be finished.  You're a
committer, so you have all the karma you need to create that repo.  If no
one else objects, then do it.

: o),
Myrle

Re: WEBINAR - Showcase of MIMO Mobile App Integration with Mifos/Fineract by Mann India - Tuesday Nov 20 at 1400GMT

[Myrle Krantz]

Hey Ed,

This sounds very cool.  Would you like to tweet about it too?

Best Regards,
Myrle

On Fri, Nov 16, 2018 at 2:59 PM Ed Cable  wrote:

> Hello community,
>
> It's been a while since a webinar has been held to highlight some of the
> work in the ecosystem.
>
> Longtime partner, Mann India would like to showcase the integration they've
> completed between Mifos/Fineract and their mobile app, MIMO for agent and
> field officer management.
>
> The webinar will be this Tuesday November 20 at 1400GMT via GoToTraining:
>
> https://attendee.gototraining.com/r/859407270420434946
>
> Learn more about Mann India and MIMO at http://www.mann-india.com/mimo/
>
> Mann India will be showcasing the integration between Mifos and MIMO, their
> mobile app for enabling field processes via Android devices.
>
> MIMO integration with MIFOS enables directly in the field pre-process,
> in-process and post-process support through capabilities like field officer
> task assignments, tracking and management of agents, and service
> notifications for core procedures.
>
> The Integration points between MIMO & MIFOS to be showcased include:
> - Client pnboarding
> - Savings Applications
> - Loan Application
> - Collection Sheet generation
> - Loan Repayment etc
>
> MIMO enhances productivity using on-demand API calls and runs on affordable
> and easily accessible Android devices, providing a wide array of services
> through its core MIMO backend developed on the Java platform.
>
> Thanks,
>
> Ed Cable
>

Re: [ANNOUNCE] New Apache Fineract Committer Cabrel Kemfang

[Myrle Krantz]

(I'd like to tweet about it too.  Do you have a twitter account I can @?)

Greets,
Myrle

On Tue, Nov 13, 2018 at 1:03 PM Myrle Krantz  wrote:

> Thank you so much for joining us Cabrel!
>
> : o),
> Myrle
>
> On Tue, Nov 13, 2018 at 12:54 PM Mexina Daniel 
> wrote:
>
>> Congratulations Cabrel
>>
>> On November 13, 2018 at 5:14 PM Santosh Math <
>> sant...@confluxtechnologies.com> wrote:
>>
>> Congratulations Cabrel.
>>
>> On Tue, Nov 13, 2018 at 5:07 PM Awasum Yannick  wrote:
>>
>> Hello Everyone,
>>
>> I'm proud to announce that Apache Fineract has a new committer.
>>
>> Congratulations Cabrel Kemfang, and thank you for joining us.
>>
>> Cabrel is a Software Engineer at Skylabase, and has been contributing to
>> fims web app on Fineract CN.
>>
>> Thanks,
>> Awasum Yannick
>> PMC Member, Apache Fineract
>>
>> --
>> Thanks & Regards
>>
>> Santosh Math
>>
>> *QA Engineer*
>>
>> *Conflux Technologies Pvt Ltd <http://www.confluxtechnologies.com/>*
>> | *Office*: +91-080-41208662 |
>>
>> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
>> Bengaluru, Karnataka, 560043 INDIA
>>
>>
>> Mexina Daniel
>>
>> Singo Africa Limited
>> Block G, Mbezi Beach B | 7 Nakawale Road | P.O BOX 78908 | 14121 Dar es
>> salaam
>>
>> +255 71 211 0791 | +255 22 261 8511
>>
>> amala.co.tz | singo.africa
>>
>>
>>
>

Re: [ANNOUNCE] New Apache Fineract Committer Cabrel Kemfang

[Myrle Krantz]

Thank you so much for joining us Cabrel!

: o),
Myrle

On Tue, Nov 13, 2018 at 12:54 PM Mexina Daniel  wrote:

> Congratulations Cabrel
>
> On November 13, 2018 at 5:14 PM Santosh Math <
> sant...@confluxtechnologies.com> wrote:
>
> Congratulations Cabrel.
>
> On Tue, Nov 13, 2018 at 5:07 PM Awasum Yannick  wrote:
>
> Hello Everyone,
>
> I'm proud to announce that Apache Fineract has a new committer.
>
> Congratulations Cabrel Kemfang, and thank you for joining us.
>
> Cabrel is a Software Engineer at Skylabase, and has been contributing to
> fims web app on Fineract CN.
>
> Thanks,
> Awasum Yannick
> PMC Member, Apache Fineract
>
> --
> Thanks & Regards
>
> Santosh Math
>
> *QA Engineer*
>
> *Conflux Technologies Pvt Ltd *
> | *Office*: +91-080-41208662 |
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>
>
> Mexina Daniel
>
> Singo Africa Limited
> Block G, Mbezi Beach B | 7 Nakawale Road | P.O BOX 78908 | 14121 Dar es
> salaam
>
> +255 71 211 0791 | +255 22 261 8511
>
> amala.co.tz | singo.africa
>
>
>

Re: Fineract CN - UI build issues

[Myrle Krantz]

Hey Awasum,

Short answer is: I don't know.  While fineract-cn was still in the mifosio
repos, I was able to get travis running for lang (because it doesn't have
any dependencies to other fineract artifacts).  I don't know if the same
method can be used within a gitbox repository or if Infra's involvement is
needed.  The best way to find out is to try.

But whatever the answer to your question, before we can use travis for most
of the repositories, we need to start publishing artifacts to a maven
repository.

Best Regards,
Myrle

On Sat, Nov 3, 2018 at 11:18 PM Awasum Yannick  wrote:

> Hello Mark,
>
> Can you throw more light on how the config settings for travis will look
> like?
>
> Myrle, Can Travis be configured on the Repos or do we need help from Infra?
>
> On Fri, Oct 19, 2018 at 11:00 AM Mark van Veen 
> wrote:
>
> > With this PR the build should work again:
> > https://github.com/apache/fineract-cn-fims-web-app/pull/13
> >
> > The issue was because the use of a local component variable within a for
> > loop. I still don't know 100% why its not working when doing so but for
> > this implementation a for loop is not needed at all and can be replaced
> > with a map.
> >
> > I strongly recommend to have travis ci build(or any other build tool)
> > enabled to automatically run the build(to verify the build is not broken)
> > and tslint(to guarantee readable, maintainable and functionally correct
> > code) to avoid such issues for future pushes.
> >
> > Thanks,
> > Mark
> >
> > On Fri, Oct 12, 2018 at 8:54 AM Karthik Ananthakrishnan
> >  wrote:
> >
> > > Thanks Kelvin. Feedback is helpful.
> > >
> > > Let me try and see if i can find the issue for ng build --prod.
> > >
> > > I will raise the PR in couple of days.
> > >
> > > Regards,
> > > Karthik.
> > >
> > > On Fri, Oct 12, 2018 at 11:52 AM Kelvin Ikome 
> > wrote:
> > >
> > > > Hello Kathik,
> > > >
> > > > I have tried the solution you came up with and it works when I build
> > > using
> > > > "npm run build". However, I still get the same error when I try to
> > build
> > > > using "ng build --prod".
> > > >
> > > > Please send a pull request for the fix you did and take a look at
> this
> > > > issue on Jira (
> > https://issues.apache.org/jira/browse/FINCN-96?filter=-2)
> > > > related to this bug.
> > > >
> > > > Thanks
> > > >
> > > > On Fri, Oct 5, 2018 at 3:51 PM Ruphine Kengne <
> ruphineken...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Hello Karthik,
> > > > >
> > > > > I have done those changes to the package.json file but it did not
> > solve
> > > > the
> > > > > build error in my case.
> > > > >
> > > > > Since yours worked, Please can you sent a PR for it to be merge so
> > > that I
> > > > > can pull ??
> > > > >
> > > > > Thanks
> > > > > Ruphine Kengne
> > > > >
> > > > > On Fri, 5 Oct 2018 at 14:17, Karthik Ananthakrishnan
> > > > >  wrote:
> > > > >
> > > > > > Hello all,
> > > > > >
> > > > > > We made this below change in package.json and build worked.
> > > > > >
> > > > > > Before
> > > > > > "runProd": "ng serve --proxy-config proxy.conf.json --prod",
> > > > > >  "build": "ng build --prod",
> > > > > >
> > > > > > After
> > > > > > "runProd": "ng serve --proxy-config proxy.conf.json
> > > > > *--environment=prod*",
> > > > > > "build": "ng build *--environment=prod*",
> > > > > >
> > > > > > For people who are facing UI build error, please check.
> > > > > >
> > > > > > Thanks,
> > > > > > Karthik
> > > > > >
> > > > > > On Fri, Sep 28, 2018 at 9:18 PM Karthik Ananthakrishnan <
> > > > > > karthi...@beyondsquare.com> wrote:
> > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://user-images.githubusercontent.com/33152020/46206285-1f497b00-c341-11e8-9fe9-4fdc43ecb88e.png
> > > > > > >
> > > > > > > Image is attached in the git branch. Link is given above.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Karthik
> > > > > > >
> > > > > > > On Fri, Sep 28, 2018 at 5:46 PM Awasum Yannick <
> > > > > > > awasum.yann...@skylabase.com> wrote:
> > > > > > >
> > > > > > >> Hey Karthik,
> > > > > > >>
> > > > > > >> This list seems not to take attachments or pictures. Can you
> > link
> > > > the
> > > > > > >> error
> > > > > > >> to an external service and use url here?
> > > > > > >> Or just paste the error in the email body.
> > > > > > >>
> > > > > > >>
> > > > > > >> Thanks.
> > > > > > >>
> > > > > > >> On Fri, Sep 28, 2018 at 1:01 PM Karthik Ananthakrishnan
> > > > > > >>  wrote:
> > > > > > >>
> > > > > > >> > Hello All,
> > > > > > >> >
> > > > > > >> > I tried running the "build" command from the latest
> > fims-web-app
> > > > > > branch
> > > > > > >> > and i am getting the following error. Is anyone facing this
> > and
> > > > have
> > > > > > >> > resolved the issue?
> > > > > > >> >
> > > > > > >> > [image: UI_Build_Error.png]
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

[ANNOUNCE] New Apache Fineract PMC Member Mexina Daniel

[Myrle Krantz]

Please join me in welcoming Mexina Daniel as the newest member of our
Project Management Committee.

Mexina has been contributing to the Fineract community since 2016, and is a
value member of our community. She's been enthusiastic about moving
Fineract 1.x releasing forward.  She let's us know when we need to improve
things.

Welcome Mexina.  I'm really glad you're on board.

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

Re: Merging dev and user lists for Fineract (INFRA-17176)

[Myrle Krantz]

Hey all,

Gavin has closed the user list for us. (If you're reading, thanks, Gavin!)
Now if you send an e-mail to u...@fineract.apache.org, your e-mail will
bounce with the message:

"Fineract user list is closed. Please see dev.at.fineract list instead"

Best Regards,
Myrle


On Fri, Oct 26, 2018 at 9:08 AM Santosh Math <
sant...@confluxtechnologies.com> wrote:

> +1
>
> On Fri, Oct 26, 2018 at 12:30 PM Mexina Daniel 
> wrote:
>
> > +1 option 1
> >
> > > On October 25, 2018 at 10:42 PM Myrle Krantz  wrote:
> > >
> > >
> > > Hey James,
> > >
> > > On Thu, Oct 25, 2018 at 7:04 PM James Dailey 
> > wrote:
> > > > Will it preserve a future reopening of list? I.e. Can it be
> > re-established
> > > > or re-opened later?
> > >
> > > I understood Gavin's response to my question this way, yes.
> > >
> > > > Then ... Comms...can we make sure to follow up w key members of users
> > that
> > > > aren't part of dev to make sure they know the why and what? (I'm
> happy
> > to
> > > > craft an email to them... I think it should go out first to them as a
> > > > notification).
> > >
> > > Thanks.  Please wait the 72 hours for people on dev to object.  Then
> > > I'll wait to confirm the Infra request until after you've sent the
> > > mail to the user's list.  You might want to include instructions for
> > > subscribing to dev.
> > >
> > > : o),
> > > Myrle
> >
> > Mexina Daniel
> >
> >
> > Singo Africa Limited
> > Block G, Mbezi Beach B | 7 Nakawale Road | P.O BOX 78908 | 14121 Dar es
> > salaam
> >
> > +255 71 211 0791 | +255 22 261 8511
> >
> > amala.co.tz | singo.africa
> >
>
>
> --
> Thanks & Regards
>
> Santosh Math
>
> *QA Engineer*
>
> *Conflux Technologies Pvt Ltd <http://www.confluxtechnologies.com/>*
> | *Office*: +91-080-41208662 |
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>

Re: Fineract-CN getting to a build or get hosted

[Myrle Krantz]

Hey James,

>From your pastebin:

"Could not find org.apache.fineract.cn.payroll:api:0.1.0-BUILD-SNAPSHOT.
  Searched in the following locations:
  
https://jcenter.bintray.com/org/apache/fineract/cn/payroll/api/0.1.0-BUILD-SNAPSHOT/maven-metadata.xml
  
https://jcenter.bintray.com/org/apache/fineract/cn/payroll/api/0.1.0-BUILD-SNAPSHOT/api-0.1.0-BUILD-SNAPSHOT.pom
  
https://jcenter.bintray.com/org/apache/fineract/cn/payroll/api/0.1.0-BUILD-SNAPSHOT/api-0.1.0-BUILD-SNAPSHOT.jar
  
file:/Users/jamesdailey/.m2/repository/org/apache/fineract/cn/payroll/api/0.1.0-BUILD-SNAPSHOT/maven-metadata.xml
  
file:/Users/jamesdailey/.m2/repository/org/apache/fineract/cn/payroll/api/0.1.0-BUILD-SNAPSHOT/api-0.1.0-BUILD-SNAPSHOT.pom
  
file:/Users/jamesdailey/.m2/repository/org/apache/fineract/cn/payroll/api/0.1.0-BUILD-SNAPSHOT/api-0.1.0-BUILD-SNAPSHOT.jar
  Required by:
  project :"

Have you cloned and locally published payroll?

Best Regards,
Myrle

P.S.  For little things like this, pastebin is both unnecessary and
problematic.  It means important information gets moved "offlist"
where people with the same problem can't use our lists to search for a
solution.

On Tue, Oct 30, 2018 at 11:01 PM James Dailey  wrote:
>
> Awasum - yep. Missed that.  Thanks.
>
> Ok. with java 1.8 JDK installed I made good progress.  Build successful.
> Then Failed on the demo server and fims.
>
> Then some Build failures... help please.
> https://pastebin.com/cHE2kgjj
>
> James
>
> On Mon, Oct 29, 2018 at 10:49 PM Awasum Yannick  wrote:
>
> > Hello James,
> >
> > Use Java 1.8 (Java 8)
> >
> > On Tue, Oct 30, 2018 at 6:32 AM James Dailey 
> > wrote:
> >
> > > FIRST...
> > > I'm trying to follow the instructions to get to a build, per
> > >
> > >
> > https://cwiki.apache.org/confluence/display/FINERACT/How+To+Build+Apache+Fineract+CN
> > > .
> > > I will provide some feedback on this if I can get further, but at the
> > > moment the Builds are failing.
> > >
> > > I wonder if anyone has had issues with this script
> > > <
> > >
> > https://github.com/apache/fineract-cn-demo-server/blob/develop/scripts/Unix/initial-setup.sh
> > > >
> > >  and the builds of each of the microservices and how to troubleshoot?
> > >
> > > I keep getting an error during "* Configuring > 0/1 projects > root
> > project
> > > > Resolving dependencies ':classpath'"   *
> > > for each of the builds (I think it would be the script line: > /gradlew
> > > publishToMavenLocal )
> > >
> > > https://pastebin.com/XHz4JZQg  for output
> > >
> > > I think I skipped this step:  "Ensure that artifacts are in
> > > $USER_HOME/.m2/repository"
> > > ,
> > >
> > > $USER_HOME/.m2 exists but is empty
> > >
> > > When/how is the repository supposed to be created?
> > >
> > >
> > > Macintosh-2:fineractCN jamesdailey$ mvn -version
> > >
> > > *Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> > > 2018-06-17T11:33:14-07:00)*
> > >
> > > Maven home: /usr/local/Cellar/maven/3.5.4/libexec
> > >
> > > Java version: 1.7.0_79, vendor: Oracle Corporation, runtime:
> > > /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre
> > >
> > > Default locale: en_US, platform encoding: UTF-8
> > >
> > > OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"
> > > ---
> > > SECOND...
> > > At the end of the day, what I am really trying to get to is a deployment
> > of
> > > Fineract-CN with a server on AWS or Google or other hosted
> > infrastructure.
> > > This makes me think I should follow
> > >
> > >
> > https://cwiki.apache.org/confluence/display/FINERACT/Containerizing+Fineract+CN
> > > to get to a run time version.
> > >
> > > The key think I would like to get is a set of basic APIs visible so that
> > > other devs (I have a small group I would like to bring into the project)
> > > can do some basic app work, and that might hopefully extend
> > > https://github.com/apache/fineract-cn-fims-web-app  . Additional
> > > microservices may be needed.
> > >
> > > Thanks
> > >
> >

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

[Myrle Krantz]

+1.

Someone had contacted me offlist with a ...creative approach to
resolving this problem which would have been much easier.  But that
approach won't come to fruition after all in our time frame.

My apologies for blocking on this.  It seems clear in retrospect that
I shouldn't have.

Best Regards,
Myrle


On Wed, Oct 31, 2018 at 8:58 AM Isaac Kamga  wrote:
>
> Hello everyone,
>
> I'm following up on this thread because we still haven't made progress with
> eliminating Category X dependencies in Fineract CN which Yannick evoked
> half a year ago.
>
> @Myrle and @Awasum, I've read through this thread and I second Sendoro's
> suggestion that we completely move Fineract CN's dependence on MariaDB to
> PosgreSQL instead. Besides MariaDB's license
> <https://mariadb.com/kb/en/library/licensing-faq/> being an inadmissible
> Category X dependency, PostgreSQL is Apache-compliant and is a good
> alternative for MariaDB.
>
> I think this will entail writing an equivalent library to
> fineract-cn-mariadb <https://github.com/apache/fineract-cn-mariadb> which
> we can name *fineract-cn-postgresql*. It may use the OpenJPA ORM which
> replaces Hibernate and use PostgreSQL's PgJDBC driver. I've started
> dabbling with this and will share the link to the code base tomorrow.
>
> I want to work on this task and share my thoughts, challenges and progress
> here with you too.
>
> What do you think about it ?
>
> Cheers,
> Isaac Kamga.
>
> On Wed, Apr 18, 2018 at 9:13 AM Myrle Krantz  wrote:
>
> > I think that's an excellent suggestion Sendoro.  Would you like to
> > take the lead on that?  I'd be happy to provide you with any help you
> > need to make it happen!
> >
> > Best Regards,
> > Myrle
> >
> > On Wed, Apr 18, 2018 at 9:47 AM, Sendoro Juma 
> > wrote:
> > > Dear Myrle,
> > >
> > > It may be irrelevant, but let me shoot anyway...!!!... please don't
> > through stones onto me.
> > >
> > > PostgreSQL is believe to have very/most liberal license... as matter of
> > facts... it will avoid now and any future license conflict.
> > >
> > > The question is then, why don't we select PostgreSQL as our default DBMS?
> > >
> > > - is it related with our skill set? or
> > > - it is more just related to smooth transfer from MySQL to MariaDB?
> > >
> > > Taking into Finaract CN project take a revolution approach from its
> > predecessor Finaract; why also not take same approach on database?
> > > - after-all Fineract CN Architecture is decoupled from reliance on
> > particular database system...
> > >
> > >
> > > Refer
> > > https://www.postgresql.org/about/licence/
> > > https://www.postgresql.org/list/
> > > https://opensource.org/licenses/MIT
> > >
> > >
> > > Regards
> > > Sendoro
> > > - Original Message -
> > > From: "Myrle Krantz" 
> > > To: "dev" 
> > > Sent: Wednesday, April 18, 2018 9:44:13 AM
> > > Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate
> > to OpenJPA Migration.
> > >
> > > Thank you Sendoro,
> > >
> > > It's much appreciated.
> > >
> > > FYI: I've captured the MariaDB work items in 2 new tickets:
> > > https://issues.apache.org/jira/browse/FINCN-26
> > > https://issues.apache.org/jira/browse/FINCN-27
> > >
> > > Best Regards,
> > > Myrle
> > >
> > > On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma 
> > wrote:
> > >> Hello Myrle,
> > >>
> > >> I got you.
> > >>
> > >> Let me know if there is any other component need to be checked!
> > >>
> > >> Cheers
> > >> Sendoro
> >

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

[Myrle Krantz]

On Fri, Oct 19, 2018 at 10:32 PM James Dailey  wrote:
>
> +1 on this civil discourse.
>
> I would like to offer that sometimes large code drops are unavoidable and
> necessary.  Jim's explanation of httpd contribution of type 1 is a good
> example.

I suspect that Jim's example of Robert Thau's httpd contribution may
not have been necessary were he working with the source control tools
and methods available today.  That was in 1995.  Even when we assume
it was necessary in 1995, it was risky and probably only succeeded
because of an abundance of communication and real good will with the
community.  I'm guessing though.  I haven't given up hope that Jim
will provide more details.

> I think we would find that many projects started with a large code drop
> (maybe more than one) - a sufficient amount of code - to get a project
> started.  When projects are young it would be normal and expected for this
> to happen. It quickly gets a community to a "thing" that can be added to.

Many do start with a large code drop.  They go through incubation, and
sometimes fail to attract communities.  If they fail to attract
communities, they eventually reach the attic.  Many projects also
succeed in starting at the ASF with an empty repository and building
from zero.  These are often very successful at attracting communities.
People like to work on things in which they are empowered to
participate in decision making.  People like the feeling of trust and
community which results.  PLC4X which Chris Dutz is working on is an
excellent example.

> It obviously depends on the kinds of components, tools, frameworks, etc
> that are being developed. Game theory is quite apropos - you need a
> sufficient incentive for *timely* collaboration, of hanging together.
>
> Further, if your "thing" is going to be used directly in market (i.e. with
> very little of a product wrapper ), then there is a strong *disincentive*
> to share back the latest and greatest. The further from market immediacy
> the easier it is to contribute. Both the Collaboration space and
> Competitive space are clearly delineated, whereas in a close to market
> immediacy situation you have too much overlap and therefore a built in
> delay of code contribution to preserve market competitiveness.

This is one important reason that there are very few full applications
at the ASF.  Fortunately for Fineract, we don't have to function as a
full application.  This might be an argument for our community to stay
away from customer-facing front-ends.

If working together with others on your code would cause you important
market disadvantages, then you probably don't want to take part in
open source as it is conceived at the Apache Software Foundation.  If
a vendor's goal is simply to publish their source, then a plain old
github account is probably the least expensive method available to
that vendor.  If a vendor's goal is to dominate a project, then there
are 501(c)6's out there which have the latitude to make that sort of
collaboration possible.  Those are valid and reasonable approaches.
The ASF isn't trying to compete in those spaces.  The ASF wants its
projects to be built as a community of equals.

> So, combining the "sufficient code to attract contribution" metric with the
> market-immediacy metric and you can predict engagement by outside vendors
> (or their contributors) in a project.

A "Sufficient code" metric isn't one I've ever personally used to
decide which project to contribute to.  I don't believe vendors use
this either.  I think some developers are even turned off by the
existence of massive amounts of code.  It triggers the "not invented
here" complex many developers have. : o)  But I'm happy to look at
data that shows I'm wrong.

Perhaps  you mean a "sufficient business functionality" metric?  But
even then, what I've seen more often is a "sufficiently healthy
community" metric.  Ie: how long has the project existed, how long is
it likely to continue to exist?  These are the questions I get asked
by people outside of our project.

> In such a situation, it is better, in
> my view, to accept any and all branched code even if it is dev'd off-list.

The Apache Software Foundation does not "accept any and all" off-list
development.  There are reasonable arguments to be had about the grey
areas and how far they extend, but there is *never* carte blanche.

> This allows for inspection/ code examination and further exploration - at a
> minimum.  Accepting on a branch is neither the same as accepting for
> release, nor merging to master branch.

Inspection/examination can also be accomplished on github.  We don't
need to accept code into an Apache project in order to be able to see
it.  If a vendor wishes to propose merging a branch, we can look at
that code and determine whether it is inside or outside our project's
grey area *before* we accept the code.  If code is large, that
proposal can be made available in reviewable-sized chunks by the
vendor, as 

Re: Project structure

[Myrle Krantz]

Good idea!

Thanks James,
Myrle
On Thu, Oct 25, 2018 at 9:40 PM James Dailey  wrote:
>
> I've updated
> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+CN+Project+Structure
>
> with links to the various apache github repos that correspond to each of
> these.
>
> It may be better to have a single wiki page for each of these repos, and
> ticketing for each repo and so on, but the top down listing seems like the
> right place to build out more content.

Re: github auth initial-setup.sh

[Myrle Krantz]

Hey James,

Ditto to what Awasum said.

Your repo is public (I checked).  Cloning is a read operation.
Therefore, you should be able to clone without any authentication
whatsoever.

Which gradle command are you using to build fineract-cn-lang?
./gradlew build ?  or ./gradlew publishToMavenLocal ?  Or are you
building from within an IDE?  Which one?

Have you followed the instructions here:
https://cwiki.apache.org/confluence/display/FINERACT/How+To+Build+Apache+Fineract+CN
?

Best Regards,
Myrle

On Mon, Oct 29, 2018 at 7:33 AM Awasum Yannick  wrote:
>
> Hi James,
>
> I wonder why you will need your Github username and password given you are
> cloning from a public repository (do you have private repos?).
>
> If you need to access your repos using github username and password, you
> need to use your personal access token ( a string which replaces your
> password for 2Factor enabled accounts). Use this together with the username
> when logging in on the terminal to clone a private repo. See more here
> 
>
> Your second email looks like a network problem. Something to do with
> SSL...but restarting your network switch or router should solve that
> problem. Or use a VPN or maybe check if Github is down(I doubt that).
>
> Explore these and give feedback.
>
>
> Thanks.
> Awasum
>
> On Mon, Oct 29, 2018 at 5:06 AM James Dailey  wrote:
>
> > Ebenezer G - thanks for the script
> >
> > https://github.com/apache/fineract-cn-demo-server/blob/develop/scripts/Unix/initial-setup.sh
> >
> >
> > I'm trying to follow along and perhaps figure out what is a difficult step
> > for other devs.
> >
> > I have forked to my github acct each of the fineract-cn repos as called on
> > the line starting "get_modules fineract-cn-lang fineract-cn-api
> > fineract-cn-async"
> >
> > Using your script, I get an error on authentication.  My github account
> > uses 2-factor authentication, so I think that's the source of the error as
> > it errors out on the first repo you start with in the
> > get modules () function.
> >
> > > Cloning into 'fineract-cn-lang'...
> >
> > > remote: Invalid username or password.
> >
> > > fatal: Authentication failed for '
> > https://github.com//fineract-cn-lang.git/'
> >
> > > -bash: cd: fineract-cn-lang: No such file or directory
> >
> >
> > It would be useful to be able to use your script to clone each of the core
> > git repos locally.
> >
> > Any thoughts on how to use your script with two-factor auth enabled on
> > github?  Or bypass that?
> >
> > Thanks,
> > James
> >

Re: Merging dev and user lists for Fineract (INFRA-17176)

[Myrle Krantz]

Hey James,

On Thu, Oct 25, 2018 at 7:04 PM James Dailey  wrote:
> Will it preserve a future reopening of list? I.e. Can it be re-established
> or re-opened later?

I understood Gavin's response to my question this way, yes.

> Then ... Comms...can we make sure to follow up w key members of users that
> aren't part of dev to make sure they know the why and what? (I'm happy to
> craft an email to them... I think it should go out first to them as a
> notification).

Thanks.  Please wait the 72 hours for people on dev to object.  Then
I'll wait to confirm the Infra request until after you've sent the
mail to the user's list.  You might want to include instructions for
subscribing to dev.

: o),
Myrle

Re: Merging dev and user lists for Fineract (INFRA-17176)

[Myrle Krantz]

Alright, Fineract Fans,

That went faster than I expected.  Infra is amazing.

Here are our options:
1.) close the user list.  Keep its archive separate.  Don't merge the
subscriber list to dev.  Bounce messages to user with a message
describing the new place to send questions.
2.) merge the user and dev lists.  Merge their archives.   Merge the
subscribers.

I'd prefer 1.  I don't feel comfortable autosubscribing people to the
much noisier dev list without their permission, and I like the idea of
keeping the archives separate.  Also, 1 is less work for infra.

But I don't have a strong preference.  If nobody comments in the next
72 hours, I'll request that Infra take option #1.

Best Regards,
Myrle

On Thu, Oct 25, 2018 at 12:53 PM Myrle Krantz  wrote:
>
> Hey Master Fineracters, : o)
>
> As per our current consensus on merging user and dev lists, I've
> created an Infra ticket.  There are a few open questions for me, which
> I've asked Infra.  Once they respond, I'll come back to you, and ask
> again "are  you sure?", before I confirm the request with Infra.
>
> https://issues.apache.org/jira/browse/INFRA-17176
>
> Best Regards,
> Myrle

Merging dev and user lists for Fineract (INFRA-17176)

[Myrle Krantz]

Hey Master Fineracters, : o)

As per our current consensus on merging user and dev lists, I've
created an Infra ticket.  There are a few open questions for me, which
I've asked Infra.  Once they respond, I'll come back to you, and ask
again "are  you sure?", before I confirm the request with Infra.

https://issues.apache.org/jira/browse/INFRA-17176

Best Regards,
Myrle

Re: Updates on Demo Server

[Myrle Krantz]

Rajan,

Would you like to help with this?  You *are* a committer...

Best Regards,
Myrle

On Sat, Oct 20, 2018 at 5:00 AM Rajan Maurya  wrote:
>
> Hi All,
>
> It's been a really long time. we don't have demo server up. I kindly
> request fineract contributors. Please help to run the demo server.
> Mobile development get stuck because of that. So, please...
>
> Thanks
> Rajan Maurya
>
> On Tue, Sep 18, 2018 at 8:24 AM Ed Cable  wrote:
>
> > Thanks for our reply Aleks. I will add it to the thread on the list.
> >
> > Ed
> >
> > On Mon, Sep 17, 2018 at 5:03 AM Aleksandar Vidakovic <
> > chee...@monkeysintown.com> wrote:
> >
> >> Hi Ed,
> >>
> >> ... sorry for the radio silence, I ran a bit out of time... I had to fix
> >> some unanticipated issues for a client's software rollout in Canada. I am
> >> planning approximately one more day with this and can get back to the demo
> >> server. If I'm not interrupted I can have this in one day.
> >>
> >> There are 2 possible approaches how to proceed:
> >> - continue with the JUnit based startup sequence of the demo module; the
> >> one thing that I would need to change is to split up the startup sequence
> >> and recompile
> >> - create a set of Docker Compose files to do the startup on the 2 VM
> >> instances (maybe I could borrow some stuff from Courage)
> >>
> >> I would prefer the latter, because you have more fine grained control and
> >> it's easier move service instances around... and you don't have to
> >> recompile anything.
> >>
> >> BTW: I'm at the moment in Toronto, a little bit nearer to your timezone
> >>
> >> Will ping you tomorrow evening again.
> >>
> >> Cheers,
> >>
> >> Aleks
> >>
> >> On Sun, Sep 16, 2018 at 11:17 PM Ed Cable  wrote:
> >>
> >>> Aleks,
> >>>
> >>> It's been a little while since you've been able to give an update on the
> >>> demo server work. We're in dire need for it as the GSOC interns are trying
> >>> to commit their work and test against the actual platform. It would also 
> >>> be
> >>> critical to have it in place prior to ApacheCon. If you're unable to wrap
> >>> up the work, can you please let me know so I can find someone else to take
> >>> over.
> >>>
> >>> If so, could you also let me know what is outstanding.
> >>>
> >>> Thanks,
> >>>
> >>> Ed
> >>>
> >>
> >
> > --
> > *Ed Cable*
> > President/CEO, Mifos Initiative
> > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> >
> > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> >   
> >
> >
>
> --
> *Thanks*
> *Namaste*
>
> Rajan Maurya
> Contact Number : +91 9015090523
> Github : @Github/therajanmaurya ,
> LinkedIn: @LinkedIn/therajanmaurya
> ,
> Medium: @medium/therajanmaurya 

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

[Myrle Krantz]

(Chris accidentally left out the fineract dev list here, but this is
definitely relevant to the topic at hand.)

Best Regards,
Myrle

-- Forwarded message -
From: Christofer Dutz 
Date: Sat, Oct 20, 2018 at 8:17 PM
Subject: Re: Why are large code drops damaging to a community?
To: d...@community.apache.org 


Trying to keep this short ...

Well I think it's important to keep the others in the loop no matter
what it's about. Especially if it's about code.

The probably most extreme example is the Edgent incubating project.
After IBM pulling the plug, it's sort of only me still being involved.
So right now I have a project, I know 100% of the build, but about 10%
of the code. Now people are asking me questions, I just can't answer,
which is damaging. From my point of view, it feels like a huge code
drop (even if I know it wasn't).

My 2,5 cents,

Chris

Outlook for Android<https://aka.ms/ghei36> herunterladen

From: mike peoni 
Sent: Saturday, October 20, 2018 7:01:47 AM
To: d...@community.apache.org
Subject: Re: Why are large code drops damaging to a community?

In talking about https  MyOpj.VisibleEh would this be appropriate for a
large Apl so you wouldn't raise flags and further more i put 2 Apl on face
book just anonymized on my page then they put up a developers page and i
liked it and i went to close my
account and my Apl where there
In the dev, page and i was told
I would forfit my data I'm deeply
concerned because they tried to issue a visa for a substantial amount but
not what the Apl
worth they have been negotiating as of now i don't
know where i stand "please comment as to the dev, page
Apache is neg, on fees. As far
as big data goes if th framework was done right there shouldn't be a
problem with it intergrating unless it's branched invasively.

On Sat, Oct 20, 2018, 12:41 AM Myrle Krantz  wrote:

> Hey Jim,
>
> I’d say they are a symptom *and* a problem. But putting that aside, can you
> unroll what you mean please?
>
> What was that code drop from SGI a symptom of?
>
> What did Robert Thau do (or not do), before during or after to ensure the
> success of httpd?
>
> Best Regards,
> Myrle
>
> On Sat 20. Oct 2018 at 00:28 Jim Jagielski  wrote:
>
> > I would say that, in general, large code drops are more a *symptom* of a
> > problem, rather than a problem, in and of itself...
> >
> > > On Oct 19, 2018, at 5:12 PM, Alex Harui 
> > wrote:
> > >
> > > IMO, the issue isn't about large code drops.  Some will be ok.
> > >
> > > The issue is about significant collaboration off-list about anything,
> > not just code.
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 10/19/18, 1:32 PM, "James Dailey"  wrote:
> > >
> > >+1 on this civil discourse.
> > >
> > >I would like to offer that sometimes large code drops are
> unavoidable
> > and
> > >necessary.  Jim's explanation of httpd contribution of type 1 is a
> > good
> > >example.
> > >
> > >I think we would find that many projects started with a large code
> > drop
> > >(maybe more than one) - a sufficient amount of code - to get a
> project
> > >started.  When projects are young it would be normal and expected
> for
> > this
> > >to happen. It quickly gets a community to a "thing" that can be
> added
> > to.
> > >
> > >It obviously depends on the kinds of components, tools, frameworks,
> > etc
> > >that are being developed. Game theory is quite apropos - you need a
> > >sufficient incentive for *timely* collaboration, of hanging
> together.
> > >
> > >Further, if your "thing" is going to be used directly in market
> (i.e.
> > with
> > >very little of a product wrapper ), then there is a strong
> > *disincentive*
> > >to share back the latest and greatest. The further from market
> > immediacy
> > >the easier it is to contribute. Both the Collaboration space and
> > >Competitive space are clearly delineated, whereas in a close to
> market
> > >immediacy situation you have too much overlap and therefore a built
> in
> > >delay of code contribution to preserve market competitiveness.
> > >
> > >So, combining the "sufficient code to attract contribution" metric
> > with the
> > >market-immediacy metric and you can predict engagement by outside
> > vendors
> > >(or their contributors) in a project. In such a situation, it is
> > better, in
> > >my view, to accept any and all branched code even if it 

Re: Pull Request Review

[Myrle Krantz]

Thank you Ruphine, for giving Cabrel the opportunity to earn some
"karma" by reviewing your pull request.  And thank you Cabrel for
relieving me of that work.  I know y'all aren't finished yet.  Keep
going, you'll get it!

Best Regards,
Myrle
On Sat, Oct 20, 2018 at 1:10 PM Ruphine Kengne  wrote:
>
> Hello Cabrel,
>
> I have replied to your comment and I have sent another commit.
> Please can you pull it and review?
>
> Thanks
>
>
> On Sat, 20 Oct 2018 at 12:03, Cabrel Kemfang <
> ghislaincabrel.kemf...@gmail.com> wrote:
>
> > Hello Myrle,
> >
> > I have reviewed the pr and there is an error .I have left a comment .
> >
> > On Thu, Oct 18, 2018 at 7:43 PM Myrle Krantz  wrote:
> >
> >> Hey Cabrel,
> >>
> >> I've merged your latest PR.  You are absolutely on a role!
> >>
> >> Cabrel, can you please review Ruphine's PR?  If you say it's good,
> >> then I'll merge it.
> >>
> >> Best Regards,
> >> Myrle
> >> On Wed, Oct 17, 2018 at 5:32 PM Ruphine Kengne 
> >> wrote:
> >> >
> >> > Hello Myrle,
> >> >
> >> > I have sent the pull request
> >> > https://github.com/apache/fineract-cn-fims-web-app/pull/12
> >> > which solves the issue :
> >> https://issues.apache.org/jira/browse/FINCN-101
> >> >
> >> > Please can you review it?
> >> >
> >> > Regards,
> >> > Ruphine Kengne
> >> >
> >> > On Wed, 17 Oct 2018 at 11:14, Cabrel Kemfang <
> >> ghislaincabrel.kemf...@gmail.com> wrote:
> >> >>
> >> >> Hello Myrle,
> >> >> I have sent another pr
> >> >> https://github.com/apache/fineract-cn-fims-web-app/pull/11  which
> >> solves
> >> >> the issue https://issues.apache.org/jira/browse/FINCN-87.
> >> >> Please can you review it?.
> >> >>
> >> >> On Tue, Oct 16, 2018 at 8:28 PM Myrle Krantz  wrote:
> >> >>
> >> >> > Awesome Cabrel!
> >> >> >
> >> >> > : o),
> >> >> > Myrle
> >> >> > On Tue, Oct 16, 2018 at 1:01 PM Cabrel Kemfang
> >> >> >  wrote:
> >> >> > >
> >> >> > > Hello Myrle,
> >> >> > > I have send a pull request (
> >> >> > https://github.com/apache/fineract-cn-fims-web-app/pull/10) which
> >> solves
> >> >> > the issue: https://issues.apache.org/jira/browse/FINCN-99
> >> >> > > Please can you review my pull request.
> >> >> > >
> >> >> > > Thanks
> >> >> > >
> >> >> > > On Thu, Oct 11, 2018 at 7:36 PM Myrle Krantz 
> >> wrote:
> >> >> > >>
> >> >> > >> I've added you to the contributors role in Jira and assigned you
> >> the
> >> >> > >> two tickets I know you've worked on and closed them.
> >> >> > >>
> >> >> > >> Keep up the good work!
> >> >> > >> Myrle
> >> >> > >> On Thu, Oct 11, 2018 at 8:14 PM Cabrel Kemfang
> >> >> > >>  wrote:
> >> >> > >> >
> >> >> > >> > Hello Myrle,
> >> >> > >> > I have create a Jira account  the user name is :cabrelkemfang
> >> >> > >> >
> >> >> > >> > On Thu, Oct 11, 2018 at 12:37 PM Myrle Krantz  >> >
> >> >> > wrote:
> >> >> > >> >
> >> >> > >> > > Hey Cabrel,
> >> >> > >> > >
> >> >> > >> > > Can you please create a Jira account and tell me what your
> >> user name
> >> >> > >> > > is?  Then I can assign bugs to you that I close.  I'd like to
> >> make
> >> >> > >> > > sure that you get credit.
> >> >> > >> > >
> >> >> > >> > > Here's the signup:
> >> >> > >> > > https://issues.apache.org/jira/secure/Signup!default.jspa
> >> >> > >> > >
> >> >> > >> > > Best Regards,
> >> >> > >> > > Myrle
> >> >> > >> > > On Thu, Oct 11, 2018 at 1:33 PM Myrle Krantz <
> >> my...@apache.org>
> >> >> > wrote:
> >> >> > >> > > >
> >> >> > >> > > > merged!
> >> >> > >> > > > On Thu, Oct 11, 2018 at 10:43 AM Cabrel Kemfang
> >> >> > >> > > >  wrote:
> >> >> > >> > > > >
> >> >> > >> > > > > Hello Myrle,
> >> >> > >> > > > > I have send a pull request (
> >> >> > >> > > https://github.com/apache/fineract-cn-fims-web-app/pull/9)
> >> which
> >> >> > solves
> >> >> > >> > > the issue: https://issues.apache.org/jira/browse/FINCN-88
> >> >> > >> > > > > Please can you review my pull request.
> >> >> > >> > > > >
> >> >> > >> > > > > Thanks
> >> >> > >> > >
> >> >> >
> >>
> >

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

[Myrle Krantz]

Hey Jim,

I’d say they are a symptom *and* a problem. But putting that aside, can you
unroll what you mean please?

What was that code drop from SGI a symptom of?

What did Robert Thau do (or not do), before during or after to ensure the
success of httpd?

Best Regards,
Myrle

On Sat 20. Oct 2018 at 00:28 Jim Jagielski  wrote:

> I would say that, in general, large code drops are more a *symptom* of a
> problem, rather than a problem, in and of itself...
>
> > On Oct 19, 2018, at 5:12 PM, Alex Harui 
> wrote:
> >
> > IMO, the issue isn't about large code drops.  Some will be ok.
> >
> > The issue is about significant collaboration off-list about anything,
> not just code.
> >
> > My 2 cents,
> > -Alex
> >
> > On 10/19/18, 1:32 PM, "James Dailey"  wrote:
> >
> >+1 on this civil discourse.
> >
> >I would like to offer that sometimes large code drops are unavoidable
> and
> >necessary.  Jim's explanation of httpd contribution of type 1 is a
> good
> >example.
> >
> >I think we would find that many projects started with a large code
> drop
> >(maybe more than one) - a sufficient amount of code - to get a project
> >started.  When projects are young it would be normal and expected for
> this
> >to happen. It quickly gets a community to a "thing" that can be added
> to.
> >
> >It obviously depends on the kinds of components, tools, frameworks,
> etc
> >that are being developed. Game theory is quite apropos - you need a
> >sufficient incentive for *timely* collaboration, of hanging together.
> >
> >Further, if your "thing" is going to be used directly in market (i.e.
> with
> >very little of a product wrapper ), then there is a strong
> *disincentive*
> >to share back the latest and greatest. The further from market
> immediacy
> >the easier it is to contribute. Both the Collaboration space and
> >Competitive space are clearly delineated, whereas in a close to market
> >immediacy situation you have too much overlap and therefore a built in
> >delay of code contribution to preserve market competitiveness.
> >
> >So, combining the "sufficient code to attract contribution" metric
> with the
> >market-immediacy metric and you can predict engagement by outside
> vendors
> >(or their contributors) in a project. In such a situation, it is
> better, in
> >my view, to accept any and all branched code even if it is dev'd
> off-list.
> >This allows for inspection/ code examination and further exploration
> - at a
> >minimum.  Accepting on a branch is neither the same as accepting for
> >release, nor merging to master branch.
> >
> >Now, the assumption that the code is better than what the community
> has
> >developed has to be challenged.  It could be that the branched code
> should
> >be judged only on the merits of the code (is it better and more
> complete),
> >or it could be judged on the basis that it "breaks the current build".
> >There can be a culture of a project to accept such code drops with the
> >caveat that if the merges cannot be done by the submitting group,
> then the
> >project will have a resistance to such submissions (you break it, you
> fix
> >it), or alternatively that there will be a small group of people that
> are
> >sourced from such delayed-contribution types - that work on doing the
> >merges.  The key seems to be to create the incentive to share code
> before
> >others do, to avoid being the one that breaks the build.
> >
> >~jdailey67
> >
> >
> >
> >
> >On Fri, Oct 19, 2018 at 6:10 AM Jim Jagielski 
> wrote:
> >
> >> Large code drops are almost always damaging, since inherent in that
> >> process is the concept of "throwing the code over a wall". But
> sometimes it
> >> does work out, assuming that continuity and "good intentions" are
> followed.
> >>
> >> To show this, join me in the Wayback Machine as Sherman and I travel to
> >> the year 1995...
> >>
> >> This is right around the start of Apache, back when Apache meant the web
> >> server, and at the time, the project was basically what was left of the
> >> NCSA web server plus some patches and bug fixes... Around this time,
> one of
> >> the core group, Robert Thau, started independent work on a
> re-architecture
> >> of the server, which he code-named "Shambala". It was basically a single
> >> contributor effort (himself). One day he simply said to the group,
> "Here, I
> >> have this new design and architecture for Apache. It adds a lot of
> >> features." So much of what defines httpd today can find its origin right
> >> there: modular framework, pools, preforking (and, as such, the initial
> >> gleaming towards MPMs), extendable API, etc...
> >>
> >> In many ways, this was a large code drop. What made it different is that
> >> there was *support* by the author and the community to work on
> integrating
> >> it into the whole. It became, basically, a community effort.
> >>
> >> Now 

Re: Pull Request Review

[Myrle Krantz]

Hey Cabrel,

I've merged your latest PR.  You are absolutely on a role!

Cabrel, can you please review Ruphine's PR?  If you say it's good,
then I'll merge it.

Best Regards,
Myrle
On Wed, Oct 17, 2018 at 5:32 PM Ruphine Kengne  wrote:
>
> Hello Myrle,
>
> I have sent the pull request
> https://github.com/apache/fineract-cn-fims-web-app/pull/12
> which solves the issue : https://issues.apache.org/jira/browse/FINCN-101
>
> Please can you review it?
>
> Regards,
> Ruphine Kengne
>
> On Wed, 17 Oct 2018 at 11:14, Cabrel Kemfang 
>  wrote:
>>
>> Hello Myrle,
>> I have sent another pr
>> https://github.com/apache/fineract-cn-fims-web-app/pull/11  which solves
>> the issue https://issues.apache.org/jira/browse/FINCN-87.
>> Please can you review it?.
>>
>> On Tue, Oct 16, 2018 at 8:28 PM Myrle Krantz  wrote:
>>
>> > Awesome Cabrel!
>> >
>> > : o),
>> > Myrle
>> > On Tue, Oct 16, 2018 at 1:01 PM Cabrel Kemfang
>> >  wrote:
>> > >
>> > > Hello Myrle,
>> > > I have send a pull request (
>> > https://github.com/apache/fineract-cn-fims-web-app/pull/10) which solves
>> > the issue: https://issues.apache.org/jira/browse/FINCN-99
>> > > Please can you review my pull request.
>> > >
>> > > Thanks
>> > >
>> > > On Thu, Oct 11, 2018 at 7:36 PM Myrle Krantz  wrote:
>> > >>
>> > >> I've added you to the contributors role in Jira and assigned you the
>> > >> two tickets I know you've worked on and closed them.
>> > >>
>> > >> Keep up the good work!
>> > >> Myrle
>> > >> On Thu, Oct 11, 2018 at 8:14 PM Cabrel Kemfang
>> > >>  wrote:
>> > >> >
>> > >> > Hello Myrle,
>> > >> > I have create a Jira account  the user name is :cabrelkemfang
>> > >> >
>> > >> > On Thu, Oct 11, 2018 at 12:37 PM Myrle Krantz 
>> > wrote:
>> > >> >
>> > >> > > Hey Cabrel,
>> > >> > >
>> > >> > > Can you please create a Jira account and tell me what your user name
>> > >> > > is?  Then I can assign bugs to you that I close.  I'd like to make
>> > >> > > sure that you get credit.
>> > >> > >
>> > >> > > Here's the signup:
>> > >> > > https://issues.apache.org/jira/secure/Signup!default.jspa
>> > >> > >
>> > >> > > Best Regards,
>> > >> > > Myrle
>> > >> > > On Thu, Oct 11, 2018 at 1:33 PM Myrle Krantz 
>> > wrote:
>> > >> > > >
>> > >> > > > merged!
>> > >> > > > On Thu, Oct 11, 2018 at 10:43 AM Cabrel Kemfang
>> > >> > > >  wrote:
>> > >> > > > >
>> > >> > > > > Hello Myrle,
>> > >> > > > > I have send a pull request (
>> > >> > > https://github.com/apache/fineract-cn-fims-web-app/pull/9) which
>> > solves
>> > >> > > the issue: https://issues.apache.org/jira/browse/FINCN-88
>> > >> > > > > Please can you review my pull request.
>> > >> > > > >
>> > >> > > > > Thanks
>> > >> > >
>> >

Why are large code drops damaging to a community?

[Myrle Krantz]

Hey all,

There are many forms of offlist development.  One form of offlist
development is working on large code drops in private and then
contributing them all at once.  Threshold size is probably arguable,
and varies by project; put that aside for the moment.  I've been
working on an explanation of how large code drops damage community and
code.  I'd love to hear your feedback.  I'm including my project and
the dev@community list in the hopes that people from other projects
also have a perspective.  Here it goes:


Imagine you are an individual contributor on a project.  You would
like to contribute something.  You see a feature you'd like to add or
a bug you'd like to fix, a user you would like to support, or a
release you'd like to test.  You start on it.  You submit your pull
request, you answer the user's question, you test the release.  You
continue doing this at a low level for a few months.  You see other
people starting to contribute too.  This is nice.  You're working
together with others towards a common goal.  Then, out of the blue a
company with multiple paid contributors shows up.  Let's name them
Acme. Acme drops a year of code on the project.  They could do this
many ways.  For example:  A.) Acme could develop in the repository you
were working in, or B.) Acme could create a project-internal fork and
create a new repository. C.) Acme could even telegraph months in
advance that they intend to do this, by posting to the dev list or
contacting key contributors offlist, or just by having done it a few
times already.


A.) First let's imagine that Acme made massive changes in the
repository you were working in.  Perhaps they already solved the
problem you solved, but in a different way.  Perhaps, they deleted
functions you made changes in.  Perhaps they added significant
functionality you would have liked to help with.  What good were your
efforts?  Wouldn't you find this discouraging?

And now you want to continue to make changes, but the code you want to
change has commit messages referencing tickets which you have no
access to.  Or it has no reference to tickets at all.  You find an
area that seems to be needlessly complex: can you remove the
complexity?  You have no way of knowing what you'd be breaking.

Perhaps you have a proprietary UI which depends on a behavior which
was removed or changed.  Now your UI is broken.  Because the code drop
is so large, you have no way to reasonably review it for
incompatibilities.  It is not possible to review a year of development
all at once.  And if your review turns up problems?  Do you accept the
entire pull request or decline the whole thing?  Putting all the code
into one pull request is a form of blackmail (commonly used in the
formulation of bills for Congress).  If you want the good you have to
take the bad.


B.) Now let's imagine that Acme forked the code and created a new
repository which they then added to the project.  None of the work you
did is in this new repository.  If those features you implemented were
important to you, you will have to re-introduce them into the new
repository.

You'll have to start from zero learning to work in the new repository.
You also had no say in how that code was developed, so maybe the
feature that you need is unnecessarily difficult to implement in that
repository.   You don't know why things are the way they are there, so
you're walking through a mine field without a map when you're making
changes.

And anyways, why is Acme Corp so certain you had nothing of value to add?

Releasing this code also becomes contentious. Which of the two
competing repositories gets released?  Both of them? How does the
project communicate to users about how these pieces fit together.


C.) Imagine Acme gave you lots of forewarning that this was coming.
You still have no say in how the code is developed.  You know that
anything you might contribute could be obsoleted.  You can't tell
users whether the up-and-coming release will be compatible.  And
what's the point in testing that release?  You don't know how to check
that your needs are being considered in the architecture of the new
code base.

You have no sense of ownership over what comes out of that process.

You see that nobody else outside of Acme is working on the project
either, for the same reasons.


Most contributors would get discouraged and prefer not to participate
if those were the conditions.  If contributors didn't get discouraged,
they would fairly quickly be taking orders from the employees of Acme
Corp.  Acme Corp has all the inside information about what's coming in
a year in the next code dump.  Information is power.  Contributors who
are also users may also chose to stop contributing and become free
riders.  Why not just depend on Acme Corp for all of the development?

What Acme seems to be getting out of this scenario is an Apache
feather.  It's a form of free-riding on Apache's reputation.


Now let's imagine that you are the CTO of another company, 

Fwd: Request for Participation in University of Cincinnati - Open Source Survey

[Myrle Krantz]

Hey all,

The researcher involved here has expressed an interest specifically in
hearing from Fineract devs.  Please consider taking the survey linked
below.

Best Regards,
Myrle

-- Forwarded message -
From: Sharan Foga 
Date: Tue, Oct 16, 2018 at 8:24 PM
Subject: Request for Participation in University of Cincinnati - Open
Source Survey
To: 


Hi Everyone

Please see below for a message from some researchers from the
University of Cincinnati who are running a survey on participation in
Open Source. The survey is open to all Apache contributors and
committers and the researchers have said they make a donation to the
ASF for completed responses up to a maximum of $1000.

Please feel free to circulate this message within your projects.

Thanks
Sharan

==

October 16, 2018

Dear Apache Software Foundation Contributors and Committers,

We are researchers at the University of Cincinnati. We want to
understand how a firm's participation in open source software (OSS)
development affects you and your job. Since you are significant
contributors to the OSS community, we invite you to participate in our
study by completing an online survey.

The survey will take approximately 15 minutes to complete. In
appreciation of your time, $5 will be donated to Apache for each
completed survey response up to a total of $1,000. In addition, each
survey participant will be entered into a prize drawing. Two people
will be randomly selected—each person will receive a $250 Visa gift
card.

Your individual responses will be kept confidential and anonymous.
Your participation is voluntary. You may start and then change your
mind and exit the survey at any time. You can complete the survey any
time before November 10th.  We will send one reminder on October 21st
and one on November 8th.

Your inputs are extremely valuable to improving our understanding of
how OSS development impacts developers’ career experiences.

Please click the following link to start the survey.
http://cincinnati.ca1.qualtrics.com/jfe/form/SV_3h3D0bMEHrQ47xr

Thank you again for your time!

Sincerely,
Dr. Sherae Daniel, Dr. Jaime Windeler, and Dr. Liwei Chen
University of Cincinnati
Carl H. Lindner College of Business
Department of Operations, Business Analytics & Info Systems (OBAIS)
Room 618 Carl H. Lindner Hall
2925 Campus Green Dr.
Cincinnati, OH 45221
***
Sherae Daniel, Ph.D.
sherae.dan...@uc.edu
New OSS Research
London School of Economics Blog Post
http://blogs.lse.ac.uk/businessreview/2018/09/26/can-your-organisation-benefit-from-embracing-the-open-source-way/
Maruping, L., Daniel, S.L., Cataldo, M., Herbsleb, J. (2018)
“Developer Centrality and the Impact of Value Congruence and
Incongruence on Commitment and Code Contribution Activity in Open
Source Software Communities” Management Information Systems Quarterly
(Accepted).
Daniel, S.L., Maruping, L., Cataldo, M. (2018) “The Impact of Ideology
Fit on Companies and OSS Communities” Management Information Systems
Quarterly (Accepted).
Daniel, S.L., Midha, V., Bhattacherhjee, Singh, S. (2018) "Sourcing
Knowledge in open source software projects: The impacts of internal
and external social capital on project success" The Journal of
Strategic Information Systems (In Press).
https://authors.elsevier.com/a/1XhMS3RA8iSVl3


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

Re: [ DISCUSS ] Apache Fineract CN Tentative Community Roadmap

[Myrle Krantz]

Hey all,

Here's an alternative suggestion that I've been toying with: we could make
our first release consist of just identity, provisioner, organization,
accounting, customer, notifications, and of course fims-web-app and the
supporting libraries.  These pieces are enough to build a payment app on
top of but not enough to run a credit union or an MFI off of.

By reducing the "surface area", we'd make it easier to test and get to our
first release.  We could then pick and choose where to go from there.

What do you think?

Best Regards,
Myrle


On Tue, Oct 16, 2018 at 12:03 AM Ed Cable  wrote:

> Isaac,
>
> Have you or Awasum starting looking into Section A any deeper - the
> elimination of Category X dependencies?
>
> Thanks,
>
> Ed
>
> On Mon, Oct 15, 2018 at 2:50 PM Isaac Kamga  wrote:
>
>> Hello everyone,
>>
>> Thanks for your feedback Ed...it was very helpful.
>>
>> James, please could you edit the requirements you're suggesting into
>> the Community
>> roadmap
>> <
>> https://cwiki.apache.org/confluence/display/FINERACT/Apache+Fineract+CN+Community+Roadmap
>> >
>> .
>>
>> I'd like to encourage the community to add items to the roadmap so that we
>> move towards an initial release of Fineract CN.
>>
>> Given that some developers are working on issues on Fineract CN, I suggest
>> we strike the items through ( like this strikethrough ) which have been
>> closed on JIRA as I've started doing.
>>
>> Cheers,
>> Isaac Kamga.
>>
>> On Wed, Jul 25, 2018 at 6:49 PM James Dailey 
>> wrote:
>>
>> > Hi -  I would like to suggest some key high level functional criteria
>> for
>> > the formal release of Fineract-CN:
>> >
>> >1. Use case orientation - that specific end-user roles and the steps
>> >that the end-user takes in interaction with Fineract-CN front end are
>> >written in a style that allows for both "tests" and communication of
>> the
>> >requirements.  For example:
>> >   1. The User:BankStaff is able to login to see a recent history of
>> all
>> >   transactions by specific accounts, according to the permissions
>> that
>> > they
>> >   have that mask certain transaction details.
>> >   2. The User:Customer is able to login to a see current balances
>> and
>> >   recent activity on both debit and credit accounts with a total
>> > showing for
>> >   all of their accounts.
>> >   3. The User:FieldAgent is able to login and see a list of
>> payments by
>> >   individuals for whom they are assigned to.
>> >   4. and so on...
>> >
>> >   2. That security and configuration guides be included in the
>> thinking
>> >from the beginning.  An open source project often faces the false
>> > criticism
>> >that it is less secure so it is important to have ways of analyzing
>> and
>> >addressing security holes from the beginning.  This may also take the
>> > form
>> >of jira tickets that relate to ensuring that the logs are inviolable
>> and
>> >that early detection mechanisms send alerts to the proper humans
>> > defined in
>> >the configuration file - which may require thinking that through
>> more.
>> >There are guides to how to secure infrastructure and I am sure other
>> > Apache
>> >projects have had to deal with this - we should look to them for
>> advice.
>> >
>> >3. That the surface area of the release includes:
>> >   1. Open an Account with at least two KYC levels
>> >   2. Open a second account for the same person or entity
>> >   3. Make a deposit
>> >   4. Make a withdrawal
>> >   5. Transfer funds within accounts held by the same person
>> >   6. Enforce rules related to transfer amounts (subject to KYC
>> limits)
>> >   7. Have a simple approval process for a loan application (an agent
>> >   can approve)
>> >   8. Configure a loan product with min and max amounts and two
>> methods
>> >   of interest calc
>> >   9. Transfer funds from a "lending department" to a customer
>> >   10. Generate an expected payments schedule based on the product
>> >   definition
>> >   11. Write off the loan
>> >   12. Close the account (put into one of several different states)
>> >
>> >   4. That there is sufficient test coverage for the release.
>> >
>> >
>> > Thanks,
>> > James
>> >
>> > On Wed, Jul 25, 2018 at 10:00 AM Ed Cable  wrote:
>> >
>> > > Isaac,
>> > >
>> > > Thanks for compiling the tickets and composing into a cohesive initial
>> > > roadmap for our release candidate. Myrle - thank you as well for the
>> > > feedback that you have provided thus far.
>> > >
>> > > Myrle and everyone else in the community,
>> > >
>> > > Can you please help define what an MVP is for the first demo-able
>> > solution
>> > > on top of the first official release of the framework? Namely, I want
>> to
>> > > know what if any additional microservices (i.e. reporting) need to be
>> > > implemented in order to have an end to end solution on Fineract CN.
>> This
>> > > roadmap has 

Re: Invitation to contribute: October 2018 Apache Board Report for Fineract

[Myrle Krantz]

I'll attend.  I'd welcome anyone else in the Fineract PMC who wants to
to attend as well.

Best Regards,
Myrle
On Sun, Oct 14, 2018 at 3:22 PM Jim Jagielski  wrote:
>
> It is quite possible that the board may have questions during the meeting... 
> I try to attend all board meetings, but, unfortunately, I will be unable to 
> this Weds due to presenting at DevOps Days Hartford this week. Maybe having 
> someone from the PMC attending might be a Good Idea.
>
> > On Oct 12, 2018, at 12:04 PM, Ed Cable  wrote:
> >
> > Myrle,
> >
> > I made one small change to the board report - it looks good from my
> > perspective - thanks for compiling the stats. Sorry for the delayed
> > feedback. Do you need help submitting or are you able to take care of that?
> >
> > Ed
> >
> > On Thu, Oct 4, 2018 at 6:32 AM Myrle Krantz  wrote:
> >
> >> Fearless Fineracters,
> >>
> >> The board report for this quarter is due on October 10th.
> >> I've started preparing it; I would appreciate your contributions:
> >>
> >> https://cwiki.apache.org/confluence/display/FINERACT/2018-10+October+Report
> >>
> >> In particular I need your help filling out the the Activities section.
> >> I've added a few keywords that should be expanded upon, and I welcome
> >> other activities contributions.  I would suggest again that the GSoC
> >> interns capture their own activity.
> >>
> >> Best Regards,
> >> Myrle
> >> V.P., Apache Fineract
> >>
> >
> >
> > --
> > *Ed Cable*
> > President/CEO, Mifos Initiative
> > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> >
> > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> > <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>

Re: Dev vs User Mailing Lists

[Myrle Krantz]

mmunity, I think Whatsapp group is great for that and
> > the community to grow.
> >
> > We are changing an entire industry as a community because the community
> > outperforms the individuals.
> >
> > Let's keep rocking!!
> > Javier
> >
> > El mié., 10 oct. 2018 a las 13:00, Ed Cable () escribió:
> >
> >> Reading over the escalation guide and the advice it gave on directing
> >> appropriate issues/matters to the respective mailing lists, it got me
> >> thinking about our Fineract Dev and Fineract User lists.
> >>
> >> We are always trying to be inclusive especially around awarding merit or
> >> committership in valuing non-technical contributions to the project. In
> >> that same spirit, I worry we sometimes might be leaving out non-technical
> >> members of the community who might only be subscribed to the user list when
> >> we treat dev as the primary list for all communications (community-related,
> >> etc whether they're technical or not).
> >>
> >> I know we don't want to clutter the mailing lists and we don't want to
> >> cross-post everything across both lists but what do ewe think are some ways
> >> to address this?
> >>
> >> One possible option is just to consolidate the lists into dev but I don't
> >> think that is good long-term because as community grows we will have
> >> distinct technical vs. functional/design conversations happening.
> >>
> >> I know that user list is small but that might be a product of the fact that
> >> we direct everyone to sign up for dev because most conversations happen on
> >> dev
> >>
> >> Should everyone just operate under the norm that dev is the primary list
> >> and any public community-related matter or announcement will come through
> >> there and that everyone should be subscribed to that list to not miss any
> >> key information?
> >>
> >> Or should we just operate in the fashion of cross-posting to both lists if
> >> it's relevant to both audiences - that requires extra effort and ensures
> >> everybody receives the message but then it does dilute the discussion as
> >> input given on @user wouldn't be seen by @Dev 
> >>
> >> CC'ing ComDev too because they probably have some good suggestions based on
> >> on other projects. However our community might be distinct in that we have
> >> a larger user-facing community than most more
> >> technical/infrastructure-oriented Apache projects.
> >>
> >> Thanks,
> >>
> >> Ed
> >>
> >> -- Forwarded message -
> >> From: Myrle Krantz 
> >> Date: Tue, Oct 9, 2018 at 11:41 PM
> >> Subject: Escalation guide for project issues
> >> To: dev 
> >>
> >>
> >> Hey all,
> >>
> >> An escalation guide for Apache issues was just posted on
> >> d...@community.apache.org.  I wanted to make sure our community was
> >> aware of this as well:
> >>
> >> https://www.apache.org/board/escalation
> >>
> >> In general, I invite you to discuss problems you see with the Fineract
> >> project.  Discussion should be done openly, on the
> >> dev@fineract.apache.org list, or, in some cases,
> >> priv...@fineract.apache.org.  Addressing problems early and openly
> >> will keep most problems from becoming too large to handle.
> >>
> >> Best Regards,
> >> Myrle
> >> Committer, Apache Fineract
> >>
> >>
> >> --
> >> *Ed Cable*
> >> President/CEO, Mifos Initiative
> >> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> >>
> >> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> >> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
> >>
> >
>

Re: Pull Request Review

[Myrle Krantz]

I've added you to the contributors role in Jira and assigned you the
two tickets I know you've worked on and closed them.

Keep up the good work!
Myrle
On Thu, Oct 11, 2018 at 8:14 PM Cabrel Kemfang
 wrote:
>
> Hello Myrle,
> I have create a Jira account  the user name is :cabrelkemfang
>
> On Thu, Oct 11, 2018 at 12:37 PM Myrle Krantz  wrote:
>
> > Hey Cabrel,
> >
> > Can you please create a Jira account and tell me what your user name
> > is?  Then I can assign bugs to you that I close.  I'd like to make
> > sure that you get credit.
> >
> > Here's the signup:
> > https://issues.apache.org/jira/secure/Signup!default.jspa
> >
> > Best Regards,
> > Myrle
> > On Thu, Oct 11, 2018 at 1:33 PM Myrle Krantz  wrote:
> > >
> > > merged!
> > > On Thu, Oct 11, 2018 at 10:43 AM Cabrel Kemfang
> > >  wrote:
> > > >
> > > > Hello Myrle,
> > > > I have send a pull request (
> > https://github.com/apache/fineract-cn-fims-web-app/pull/9) which solves
> > the issue: https://issues.apache.org/jira/browse/FINCN-88
> > > > Please can you review my pull request.
> > > >
> > > > Thanks
> >

Re: [Discussion] Fineract CN SMS & Email Notifications Project

[Myrle Krantz]

Hey Ebenezer,

I really hope you keep the name Wada.  I love personal touches like
this.  Hermes isn't Egyptian and his Egyptian counterpart Thoth is
already taken by another service.  But far more important: Wada means
something to you.

No problem on the 404s  Your repos are public so it wasn't really an obstacle.

Have you been able to make headway with my explanation?  If something
is unclear please tell me.  But also keep in mind I have several
deadlines coming up so I'm going to be slow in replying through the
next week.

Best Regards,
Myrle


On Mon, Oct 8, 2018 at 10:59 PM Ebenezer Graham
 wrote:
>
> Wow! the reason for Anubis is deep. I should have consulted you for
> suggestions.
>
> First of all apologies for the 404s. I clean up my repo ( squashed some
> commits and deleted a few test branches) and so I had to force push to my
> git repo when I wanted to pull onto the VM. All the new code on the
> authentication is here
> https://github.com/ebenezergraham/fineract-cn-notifications/tree/permitted-feign-client-auth.
> I will be mindful of squash and force push next time.
>
> Wada means "To be loved".The notification service is my first ever open
> source project and as a wannabe open source advocate this was a really big
> deal for me hence *"my love for it".* Also partly because it's an
> Indigenous Kalanga name, I am fascinated by southern African languages and
> as such, I leave a trail of it on significant things in my life. :)
>
> But after reading the meaning of Anubis. I guess *hermes* would be a
> perfect name. One of the twelve Olympian gods ( mostly known as the
> messenger god). :0

Re: Pull Request Review

[Myrle Krantz]

Hey Cabrel,

Can you please create a Jira account and tell me what your user name
is?  Then I can assign bugs to you that I close.  I'd like to make
sure that you get credit.

Here's the signup: https://issues.apache.org/jira/secure/Signup!default.jspa

Best Regards,
Myrle
On Thu, Oct 11, 2018 at 1:33 PM Myrle Krantz  wrote:
>
> merged!
> On Thu, Oct 11, 2018 at 10:43 AM Cabrel Kemfang
>  wrote:
> >
> > Hello Myrle,
> > I have send a pull request ( 
> > https://github.com/apache/fineract-cn-fims-web-app/pull/9) which solves the 
> > issue: https://issues.apache.org/jira/browse/FINCN-88
> > Please can you review my pull request.
> >
> > Thanks

Re: Pull Request Review

[Myrle Krantz]

merged!
On Thu, Oct 11, 2018 at 10:43 AM Cabrel Kemfang
 wrote:
>
> Hello Myrle,
> I have send a pull request ( 
> https://github.com/apache/fineract-cn-fims-web-app/pull/9) which solves the 
> issue: https://issues.apache.org/jira/browse/FINCN-88
> Please can you review my pull request.
>
> Thanks

Escalation guide for project issues

[Myrle Krantz]

Hey all,

An escalation guide for Apache issues was just posted on
d...@community.apache.org.  I wanted to make sure our community was
aware of this as well:

https://www.apache.org/board/escalation

In general, I invite you to discuss problems you see with the Fineract
project.  Discussion should be done openly, on the
dev@fineract.apache.org list, or, in some cases,
priv...@fineract.apache.org.  Addressing problems early and openly
will keep most problems from becoming too large to handle.

Best Regards,
Myrle
Committer, Apache Fineract

Re: Database errors when starting up rhythm microservice

[Myrle Krantz]

Hey Courage,

I assume you mean this?
rhythm-ms| 22:52:39.200 [pool-9-thread-1] ERROR
o.h.e.jdbc.spi.SqlExceptionHelper - Table 'seshat.khepri_beats'
doesn't exist

What's happening there is that there's an event which triggers at
regular intervals and checks if its time to trigger events to the
other services.  In order to check, it needs to know when the events
for the other services are due.  That is saved in the database table.
So it queries that table.  But because rhythm isn't provisioned yet,
that exception flies.  As soon as rhythm is provisioned you'll stop
getting that error.

This isn't ideal.  Non-fatal errors shouldn't show up like that in the
log.  Pull requests (very) welcome.  But as long as you're not getting
that error message after provisioning is complete, the error is not
something you need to worry about.

Best Regards,
Myrle

On Tue, Oct 9, 2018 at 4:52 AM Courage Angeh  wrote:
>
> Hi Myrle,
>
> Hope this message finds you well. I get this error:
> https://pastebin.com/kgCR320x when starting up the rhythm microservice.
> I have done some debugging and I think its a configuration error 'cause it
> starts-up normally and it supposed to stop at `[main] INFO
> o.a.f.c.r.service.RhythmApplication - Started RhythmApplication in 28.08
> seconds (JVM running for 29.812)`. But it goes ahead to try to provision
> before time therefore it get that error.
> Here is the configuration: https://pastebin.com/YaeFT61a that's applied on
> the microservice.
>
> I will really appreciate some help
>
> Thanks,
> Courage

Re: [Discussion] Fineract CN SMS & Email Notifications Project

[Myrle Krantz]

Hey Ebenezer,
those code
First the easy question:
The services do all have code names, which we use to name the tables.
Most of them are named after Egyptian gods.  Anubis for example plays
a part in the judgement of the newly dead, and so it seemed
appropriate that the library responsible for authentication and
authorization at the service level should also be called anubis.
There's a Maat's feather in there somewhere too.

I'm glad you picked a code name for notifications too.  I bellieve it
actually makes communication about the services more precise, and it's
also fun.

Does "wada" mean anything?

Unfortunately the code links you included don't work (I'm getting
404's).  But I took a look through your repositories as they are in
github anyways.  And it seems likely that you haven't understood how
this works yet.  Which is understandable since it is complex and
poorly documented.

The current best I have available is here, but this may be confusing
because the interaction being prepared is with identity, in addition
to identity's involvement with the provisioning of permissions:
https://cwiki.apache.org/confluence/display/FINERACT/Fineract+CN+demo-server
 (In other words identity is involved in two parts of that problem
instead of just one, and that muddies the waters.)

Let me take another swing at it.  I'm currently assuming the only
function you need from customer is CustomerManager.findCustomer.  That
function is in the permittable group customer__v1__customer.  Here's
what will need to happen and how your code fits in.  I've put stars
next to the parts which will require you to do something.  I'll
explain below what you need to do for each star.  Some of it you are
already doing, so you can take those stars home : o)

demo_server -> provisioner: add customer service to the tenant
(skipping some parts here)
  provisioner -> customer: ask what permissions are part of customer
  provisioner -> identity: create the permission groups which are part
of customer, including the permittable group customer__v1__customer.
demo_server -> identity: create the role notificationAdmin, set it to
include permissions to the parts of customer you want to access. *1
demo_server -> identity: add user wadaadmin with the role notificationAdmin. *2
demo_server -> provisioner: add wada service to the tenant *3
  provisioner -> wada: provision signature with same timestamp as
current identity signature.
  provisioner -> identity: create application with signature returned by wada
  provisioner -> wada: ask what permissions wada needs.  Wada responds
that it needs customer__v1__customer. *4
  provisioner -> identity: create permission request for wada to
access customer to get customer information.
  provisioner -> wada: initialize tenant data tables in separate database. *5
demo_server -> identity: allow wada to call customer__v1__customer as
wadaadmin. *6

*1.  You are already doing this in the demo-server function
ServiceRunner::defineNotificationRole
*2.  You are already doing this in the demo-server function
ServiceRunner::createNotificationsAdmin
*3.  You are already doing this in the demo-server function
ServiceRunner::provisionAppsViaSeshat
*4.  This is done by creating a feign interface for customer within
the notification service code.  You can find an example in rhythm
under ApplicationPermissionRequestCreator, intended to make it
possible for rhythm to access identity.  In your case though you want
wada to access customer, so you'll create a class that looks something
like this:

@EndpointSet(identifier = "notificiations__v1__customer__v1")
@FeignClient(name="customer-v1", path="/customer/v1",
configuration=PermittedFeignClientsConfiguration.class)
public interface ApplicationPermissionRequestCreator {
  @RequestMapping(...) /* copy params from CustomerManager */
  @ThrowsException(...)/* copy params from CustomerManager */
  @Permittable(groupId =
org.apache.fineract.cn.customer.PermittableGroupIds.CUSTOMER)
  Customer findCustomer(...); /* copy params from CustomerManager */
}

*5.  You are already doing this in notifications function
MigrationAggregate::provisionAppsViaSeshatForTenant with a call to
provisionApp for notificationManager.
*6.  After all the other pieces are in place, login as wadaadmin and
call.  This won't work until after notificationManager is provisioned.
identityManager.api().setApplicationPermissionEnabledForUser(
notificationManager.name(),
org.apache.fineract.cn.customer.PermittableGroupIds.CUSTOMER,
notificationsAdminUser.getIdentifier(),
true);

If you still can't figure it out after this, I'd like to puzzle
together with you.  Write me an e-mail and we'll set up a pair
programming session, and then bring back anything we learn to the
list.

Best Regards,
Myrle Krantz

On Mon, Oct 8, 2018 at 12:21 AM Ebenezer Graham
 wrote:
>
> HI Myrle,
>
> I will try this approa

Re: [Discussion] Fineract CN SMS & Email Notifications Project

[Myrle Krantz]

Hey Ebenezer,

I've never debugged a process on a remote server, but it should be
possible.  First you'll need to find out what port debugging is
running on and open that port.

Aside from that, I've included the text you linked to in pastebin
below (for snippets this short it's easier on me if you just include
them in the mail.)

It seems like your problem is actually in the start up of demo-server,
is that correct?  But what line number?  What call is producing this
exception?

I can explain a bit about the permission requesting mechanism in
identity.  If service B needs to call service A, then the following
happens:
* at provisioning, service A tells provisioner about its permission
groups.  provisioner then tells identity.
* The demo-server than creates a user (Fred?) which which has access
to that permission group.
* Then when service B is being provisioned, it tells identity about
the permission groups that it will need in service A.
* The demo-server, in the name of Fred, gives service B permission to
call service A on that permission group as Fred.

This line looks like you're expecting a permission group in customer
called wada.  There is no such permission group.  Are you trying to
get information from customer?  Is that why you need this permission?
You'll need to call identity.setApplicationPermissionEnabledForUser.

Can you share the code throwing this exception?  It would make things
much easier.

Best Regards,
Myrle


1) startDevServer(org.apache.fineract.cn.dev.ServiceRunner)
org.apache.fineract.cn.api.util.NotFoundException:
{"timestamp":1538925629122,"status":404,"error":"Not
Found","exception":"org.apache.fineract.cn.lang.ServiceException","message":"Application
permission 'notification-v1.customer__v1__wada' doesn't
exist.","path":"/identity/v1/applications/notification-v1/permissions/customer__v1__wada/users/imhotep/enabled"}
at 
org.apache.fineract.cn.api.util.AnnotatedErrorDecoder.getAlternative(AnnotatedErrorDecoder.java:76)
at 
org.apache.fineract.cn.api.util.AnnotatedErrorDecoder.decode(AnnotatedErrorDecoder.java:65)
at 
feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:138)
at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:76)
at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:103)
at com.sun.proxy.$Proxy207.setApplicationPermissionEnabledForUser(Unknown
Source)
at 
org.apache.fineract.cn.dev.ServiceRunner.provisionAppsViaSeshatForTenant(ServiceRunner.java:451)
at 
org.apache.fineract.cn.dev.ServiceRunner.provisionAppsViaSeshat(ServiceRunner.java:359)
at 
org.apache.fineract.cn.dev.ServiceRunner.startDevServer(ServiceRunner.java:257)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at 
org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
at 
org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:252)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at 
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at