Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Awasum Yannick]

Congratulations Steve, thanks very much for your contributions.

On Thu, Mar 29, 2018 at 6:10 AM, Mexina Daniel  wrote:

> Congratulation Steve
>
> - Original Message -
> From: "Sanyam Goel" 
> To: "dev" 
> Sent: Wednesday, March 28, 2018 9:42:51 PM
> Subject: Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad
>
> Congratulations Steve!
>
> Regards,
> Sanyam Goel
>
>
>
> On Wed, Mar 28, 2018 at 11:59 PM, Zayyad A. Said <
> zay...@intrasofttechnologies.com> wrote:
>
> > Congratulations Steve.
> >
> >
> >
> > ***
> > Zayyad A. Said | Chairman & C.E.O
> >
> > Cell No.: +254 716 615274 | Skype: zsaid2011
> > Email: zay...@intrasofttechnologies.com
> >
> >
> >
> > -Original Message-
> > From: Steve Conrad 
> > Sent: 28 March 2018 06:14 PM
> > To: Dev 
> > Subject: Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad
> >
> > Thanks Myrle. You can feel free to tweet that update. I am not on
> Twitter,
> > so no handle to link to...
> > Steve
> >
> > On Wed, Mar 28, 2018 at 9:10 AM, Myrle Krantz  wrote:
> >
> > > Congratulations Steve!
> > >
> > > Would it be okay with you if we tweet your committership as well?  If
> > > so, do you have a twitter handle, you'd like me to @?
> > >
> > > Thanks,
> > > Myrle
> > >
> > >
> > > On Wed, Mar 28, 2018 at 4:07 PM, Ed Cable  wrote:
> > > > Hello Fineract community,
> > > >
> > > > I'm proud to announce that Apache Fineract has a new committer.
> > > >
> > > > Steve has only been a part of the community for a couple months
> > > > after
> > > being
> > > > introduced to us by the team at Musoni. By day Steve is a full-stack
> > > > developer at Dassault Systems. In his spare time, he's been doing
> > > > all he can to support the community. In that short time, he's added
> > > > tremendous value and as a committer will be able to help the
> > > > community release more frequently. He fixed a number of critical
> > > > bugs in the latest release,
> > > added
> > > > support for MySQL 5.7 and is now working on both the payment gateway
> > > > project and Mojaloop integration with Fineract.
> > > >
> > > > The Mifos Initiative recognized him as a Star Contributor recently
> > > > so
> > > click
> > > > here to learn more about Steve:
> > > > http://mifos.org/blog/star-contributor-steve-conrad/
> > > >
> > > > Congratulations Steve!  Thank you for your contributions, and we
> > > > look forward to your leadership in the community!
> > > >
> > > > Best Regards,
> > > >
> > > > Ed Cable
> > >
> >
> >
>
>
> --
> SANYAM GOEL
> LinkedIn: https://goo.gl/6SJMg3
> Github: https://goo.gl/u51wRZ
> Hackerrank: https://goo.gl/4kzLf7
> +91-9818060934
> --
> Mexina M Daniel
> Lead Software Developer
> Research & Development
>
> Office: +255 22 261 8511 | Mobile: +255 712 110 791
>
> Singo Africa Limited
> Block G, Mbezi Beach B | 7Nakawale Road | P.O BOX 78908 | 14121 Dar es
> salaam
>
> singo.africa | amala.co.tz
>
> Let's grow together
>

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

[Awasum Yannick]

Hey Isaac,

I don't have permission to comment on your Fineract Infra doc above.



On Thu, Mar 29, 2018 at 6:35 AM, Awasum Yannick  wrote:

> Hello All,
>
> Isaac and Viswa, I agree with all what you say.
>
> I use an i7 Processor with 32 GB RAM and 250 GB SSD for testing. Given we
> might be running ActiveMQ, Cassandra and MySQL/Mariadb.
> Nginx will likely be running fims-web-app. And given there will be
> instances when demo server is running along with the containerization tests
> which might run over the next 6 months, I think the above specs might just
> work for us.  What do you think?
>
>
> Thanks.
>
>
> On Thu, Mar 29, 2018 at 4:52 AM, Isaac Kamga 
> wrote:
>
>> Hello Ed,
>>
>> On Thu, Mar 29, 2018 at 12:27 AM Viswa Ramamoorthy <
>> viswaramamoor...@yahoo.com> wrote:
>>
>> > For the services currently available (as started by demo server), I
>> > estimate 4 core/16 GB/100 GB would be minimum needed.
>> >
>>
>> Viswa, I agree with most of these specifications but I think 4 Cores won't
>> run demo-server without unnecessary timeouts. I think we need at least 8
>> processors there. What do you think ?
>>
>>
>> >
>> > On ‎Wednesday‎, ‎March‎ ‎28‎, ‎2018‎ ‎03‎:‎05‎:‎12‎ ‎PM‎ ‎EDT, Ed Cable
>> <
>> > edca...@mifos.org> wrote:
>> >
>> >
>> > As we discussed earlier, the work to set up and configure the demo
>> server
>> > on the Apache infrastructure needs to be carried out by committers.
>> >
>> > Fortunately, Nikhil, Rajan, and Isaac, all committers, have graciously
>> > volunteered their time to assist. Can you all please provide your Apache
>> > IDs on the issue at https://issues.apache.org/jira/browse/INFRA-16203
>> so
>> > you can get the necessary access.
>> >
>>
>> I have just commented on the issue about my ID.
>>
>>
>> >
>> > We will then discuss on this thread the needed steps to proceed forward.
>> > However, before that, we need to answer some of the questions from Chris
>> > about what base packages would need to be installed:
>> https://goo.gl/iixSGX
>> >
>>
>> I started compiling a document  on specifications
>> for the VM. We could supplement it before continuing our request to the
>> Apache Infra team.
>>
>>
>> >
>> >
>> > Myrle, Viswa,
>> >
>> > Can we please solidify on the base packages, minimum specs this VM needs
>> > for deployment of the Fineract CN demo server?
>> >
>> > Once we have established that, those individuals with the needed
>> expertise
>> > can assist the committers above who have volunteered to assist with
>> this.
>> >
>> > Ed
>> >
>> > On Mon, Mar 26, 2018 at 3:27 AM, Courage Angeh 
>> > wrote:
>> >
>> > > Hi Viswa,
>> > >
>> > > I agree with you about Demo Server being largely oriented towards a
>> quick
>> > > use but it has a lot of useful data. I have gone through demo server
>> too
>> > > and I see they introduce RSA keys through external properties so I was
>> > > thinking changing all the microservices will be a little more
>> stressful,
>> > we
>> > > could pass external properties to it when running the different jar
>> > files.
>> > > True talk about Eureka, I am trying to work on that too.
>> > > But I was thinking we don't need that much scripts and we don't have
>> to
>> > > change too much.
>> > > I wrote a proposal about this for a GSOC project,
>> > > https://docs.google.com/document/d/1zp6CeYP6ox51tGSu1fE9cBAWpaQnq
>> > > jeBBVIa-n0evso/edit?usp=sharing
>> > > , could you check it out? I will be delighted to get you point of view
>> > and
>> > > comments about this doc :)
>> > >
>> > > Thanks Courage
>> > >
>> > > On Sat, Mar 24, 2018 at 1:06 PM, Viswa Ramamoorthy <
>> > > viswaramamoor...@yahoo.com.invalid> wrote:
>> > >
>> > > >  Hello,
>> > > > I think services need more work to get to deployable state. Demo
>> server
>> > > is
>> > > > largely oriented towards a quick use in laptops/desktops but using
>> > Junit
>> > > to
>> > > > bootsrap services may result in inconsistencies.
>> > > > I have been reviewing for sometime now. Based on my review, below
>> are
>> > the
>> > > > changes needed to get to deployment in a VM
>> > > > 1. Currently services need RSA key to bootstrap. That is fine. But
>> > there
>> > > > is no self acquire mode to get them deployed to environments like
>> demo
>> > > > envs.  a) Ideally a spring configured (say demo config) can be
>> > > > introduced to self acquire RSA keys to continue with service start.
>> > > > b) With this change, we could just start services using spring boot
>> jar
>> > > > with a configuration property at the time of service start up
>> c) I
>> > > > have tried this change in my laptop for fineract-cn-provisioner. I
>> can
>> > > > raise a PR. Needs to be propagated to other services
>> > > > 2. Eureka registration and renewal is bit flaky. Needs work on self
>> > > > registration front as well as health indicator front. Spring has
>> > tooling
>> > > on
>> > > > this front. We just need to add and 

Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Mexina Daniel]

Congratulation Steve

- Original Message -
From: "Sanyam Goel" 
To: "dev" 
Sent: Wednesday, March 28, 2018 9:42:51 PM
Subject: Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

Congratulations Steve!

Regards,
Sanyam Goel



On Wed, Mar 28, 2018 at 11:59 PM, Zayyad A. Said <
zay...@intrasofttechnologies.com> wrote:

> Congratulations Steve.
>
>
>
> ***
> Zayyad A. Said | Chairman & C.E.O
>
> Cell No.: +254 716 615274 | Skype: zsaid2011
> Email: zay...@intrasofttechnologies.com
>
>
>
> -Original Message-
> From: Steve Conrad 
> Sent: 28 March 2018 06:14 PM
> To: Dev 
> Subject: Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad
>
> Thanks Myrle. You can feel free to tweet that update. I am not on Twitter,
> so no handle to link to...
> Steve
>
> On Wed, Mar 28, 2018 at 9:10 AM, Myrle Krantz  wrote:
>
> > Congratulations Steve!
> >
> > Would it be okay with you if we tweet your committership as well?  If
> > so, do you have a twitter handle, you'd like me to @?
> >
> > Thanks,
> > Myrle
> >
> >
> > On Wed, Mar 28, 2018 at 4:07 PM, Ed Cable  wrote:
> > > Hello Fineract community,
> > >
> > > I'm proud to announce that Apache Fineract has a new committer.
> > >
> > > Steve has only been a part of the community for a couple months
> > > after
> > being
> > > introduced to us by the team at Musoni. By day Steve is a full-stack
> > > developer at Dassault Systems. In his spare time, he's been doing
> > > all he can to support the community. In that short time, he's added
> > > tremendous value and as a committer will be able to help the
> > > community release more frequently. He fixed a number of critical
> > > bugs in the latest release,
> > added
> > > support for MySQL 5.7 and is now working on both the payment gateway
> > > project and Mojaloop integration with Fineract.
> > >
> > > The Mifos Initiative recognized him as a Star Contributor recently
> > > so
> > click
> > > here to learn more about Steve:
> > > http://mifos.org/blog/star-contributor-steve-conrad/
> > >
> > > Congratulations Steve!  Thank you for your contributions, and we
> > > look forward to your leadership in the community!
> > >
> > > Best Regards,
> > >
> > > Ed Cable
> >
>
>


-- 
SANYAM GOEL
LinkedIn: https://goo.gl/6SJMg3
Github: https://goo.gl/u51wRZ
Hackerrank: https://goo.gl/4kzLf7
+91-9818060934
-- 
Mexina M Daniel
Lead Software Developer
Research & Development

Office: +255 22 261 8511 | Mobile: +255 712 110 791

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

singo.africa | amala.co.tz

Let's grow together

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

[Isaac Kamga]

Hello Ed,

On Thu, Mar 29, 2018 at 12:27 AM Viswa Ramamoorthy <
viswaramamoor...@yahoo.com> wrote:

> For the services currently available (as started by demo server), I
> estimate 4 core/16 GB/100 GB would be minimum needed.
>

Viswa, I agree with most of these specifications but I think 4 Cores won't
run demo-server without unnecessary timeouts. I think we need at least 8
processors there. What do you think ?


>
> On ‎Wednesday‎, ‎March‎ ‎28‎, ‎2018‎ ‎03‎:‎05‎:‎12‎ ‎PM‎ ‎EDT, Ed Cable <
> edca...@mifos.org> wrote:
>
>
> As we discussed earlier, the work to set up and configure the demo server
> on the Apache infrastructure needs to be carried out by committers.
>
> Fortunately, Nikhil, Rajan, and Isaac, all committers, have graciously
> volunteered their time to assist. Can you all please provide your Apache
> IDs on the issue at https://issues.apache.org/jira/browse/INFRA-16203 so
> you can get the necessary access.
>

I have just commented on the issue about my ID.


>
> We will then discuss on this thread the needed steps to proceed forward.
> However, before that, we need to answer some of the questions from Chris
> about what base packages would need to be installed: https://goo.gl/iixSGX
>

I started compiling a document  on specifications
for the VM. We could supplement it before continuing our request to the
Apache Infra team.


>
>
> Myrle, Viswa,
>
> Can we please solidify on the base packages, minimum specs this VM needs
> for deployment of the Fineract CN demo server?
>
> Once we have established that, those individuals with the needed expertise
> can assist the committers above who have volunteered to assist with this.
>
> Ed
>
> On Mon, Mar 26, 2018 at 3:27 AM, Courage Angeh 
> wrote:
>
> > Hi Viswa,
> >
> > I agree with you about Demo Server being largely oriented towards a quick
> > use but it has a lot of useful data. I have gone through demo server too
> > and I see they introduce RSA keys through external properties so I was
> > thinking changing all the microservices will be a little more stressful,
> we
> > could pass external properties to it when running the different jar
> files.
> > True talk about Eureka, I am trying to work on that too.
> > But I was thinking we don't need that much scripts and we don't have to
> > change too much.
> > I wrote a proposal about this for a GSOC project,
> > https://docs.google.com/document/d/1zp6CeYP6ox51tGSu1fE9cBAWpaQnq
> > jeBBVIa-n0evso/edit?usp=sharing
> > , could you check it out? I will be delighted to get you point of view
> and
> > comments about this doc :)
> >
> > Thanks Courage
> >
> > On Sat, Mar 24, 2018 at 1:06 PM, Viswa Ramamoorthy <
> > viswaramamoor...@yahoo.com.invalid> wrote:
> >
> > >  Hello,
> > > I think services need more work to get to deployable state. Demo server
> > is
> > > largely oriented towards a quick use in laptops/desktops but using
> Junit
> > to
> > > bootsrap services may result in inconsistencies.
> > > I have been reviewing for sometime now. Based on my review, below are
> the
> > > changes needed to get to deployment in a VM
> > > 1. Currently services need RSA key to bootstrap. That is fine. But
> there
> > > is no self acquire mode to get them deployed to environments like demo
> > > envs.  a) Ideally a spring configured (say demo config) can be
> > > introduced to self acquire RSA keys to continue with service start.
> > > b) With this change, we could just start services using spring boot jar
> > > with a configuration property at the time of service start up  c) I
> > > have tried this change in my laptop for fineract-cn-provisioner. I can
> > > raise a PR. Needs to be propagated to other services
> > > 2. Eureka registration and renewal is bit flaky. Needs work on self
> > > registration front as well as health indicator front. Spring has
> tooling
> > on
> > > this front. We just need to add and configure.
> > > 3. Develop scripts to start services. Simple shell scripts good enough
> at
> > > this point.a) One use case is to build/deploy for use in VMb)
> > > Another use case is to facilitate selective service launch approach
> that
> > > was alluding to a while back. For example, if some one needs to work on
> > > 'accounting' services and depends on 'customer' services, they could
> > bring
> > > up 'customer' along with infrastructures using shell scripts (to be
> > > developed) and continue with development in accounting.
> > > 4. Deploy basic infrastructure needed for services - Eureka, ActiveMQ,
> > > Cassandra and MariaDB. These can be Dockers and I already sent PR on
> this
> > > front.
> > > Proposal is to create a new repo to have build/deployment scripts
> stored
> > > to get this used in VM and support laptop use cases to help with
> > > development.
> > > I can help/guide as needed.
> > >
> > > RegardsViswa Ramamoorthy
> > >On ‎Friday‎, ‎March‎ ‎23‎, ‎2018‎ ‎06‎:‎52‎:‎27‎ ‎AM‎ ‎EDT, Isaac
> > > Kamga 

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

[Ed Cable]

As we discussed earlier, the work to set up and configure the demo server
on the Apache infrastructure needs to be carried out by committers.

Fortunately, Nikhil, Rajan, and Isaac, all committers, have graciously
volunteered their time to assist. Can you all please provide your Apache
IDs on the issue at https://issues.apache.org/jira/browse/INFRA-16203 so
you can get the necessary access.

We will then discuss on this thread the needed steps to proceed forward.
However, before that, we need to answer some of the questions from Chris
about what base packages would need to be installed: https://goo.gl/iixSGX

Myrle, Viswa,

Can we please solidify on the base packages, minimum specs this VM needs
for deployment of the Fineract CN demo server?

Once we have established that, those individuals with the needed expertise
can assist the committers above who have volunteered to assist with this.

Ed

On Mon, Mar 26, 2018 at 3:27 AM, Courage Angeh 
wrote:

> Hi Viswa,
>
> I agree with you about Demo Server being largely oriented towards a quick
> use but it has a lot of useful data. I have gone through demo server too
> and I see they introduce RSA keys through external properties so I was
> thinking changing all the microservices will be a little more stressful, we
> could pass external properties to it when running the different jar files.
> True talk about Eureka, I am trying to work on that too.
> But I was thinking we don't need that much scripts and we don't have to
> change too much.
> I wrote a proposal about this for a GSOC project,
> https://docs.google.com/document/d/1zp6CeYP6ox51tGSu1fE9cBAWpaQnq
> jeBBVIa-n0evso/edit?usp=sharing
> , could you check it out? I will be delighted to get you point of view and
> comments about this doc :)
>
> Thanks Courage
>
> On Sat, Mar 24, 2018 at 1:06 PM, Viswa Ramamoorthy <
> viswaramamoor...@yahoo.com.invalid> wrote:
>
> >  Hello,
> > I think services need more work to get to deployable state. Demo server
> is
> > largely oriented towards a quick use in laptops/desktops but using Junit
> to
> > bootsrap services may result in inconsistencies.
> > I have been reviewing for sometime now. Based on my review, below are the
> > changes needed to get to deployment in a VM
> > 1. Currently services need RSA key to bootstrap. That is fine. But there
> > is no self acquire mode to get them deployed to environments like demo
> > envs.   a) Ideally a spring configured (say demo config) can be
> > introduced to self acquire RSA keys to continue with service start.
> > b) With this change, we could just start services using spring boot jar
> > with a configuration property at the time of service start up   c) I
> > have tried this change in my laptop for fineract-cn-provisioner. I can
> > raise a PR. Needs to be propagated to other services
> > 2. Eureka registration and renewal is bit flaky. Needs work on self
> > registration front as well as health indicator front. Spring has tooling
> on
> > this front. We just need to add and configure.
> > 3. Develop scripts to start services. Simple shell scripts good enough at
> > this point. a) One use case is to build/deploy for use in VM b)
> > Another use case is to facilitate selective service launch approach that
> > was alluding to a while back. For example, if some one needs to work on
> > 'accounting' services and depends on 'customer' services, they could
> bring
> > up 'customer' along with infrastructures using shell scripts (to be
> > developed) and continue with development in accounting.
> > 4. Deploy basic infrastructure needed for services - Eureka, ActiveMQ,
> > Cassandra and MariaDB. These can be Dockers and I already sent PR on this
> > front.
> > Proposal is to create a new repo to have build/deployment scripts stored
> > to get this used in VM and support laptop use cases to help with
> > development.
> > I can help/guide as needed.
> >
> > RegardsViswa Ramamoorthy
> > On ‎Friday‎, ‎March‎ ‎23‎, ‎2018‎ ‎06‎:‎52‎:‎27‎ ‎AM‎ ‎EDT, Isaac
> > Kamga  wrote:
> >
> >  Hi Ed,
> >
> > I am willing to assist in configuring the VM requested for Apache
> Fineract
> > CN.
> >
> > I don't have all the required skills but with commitment and some
> > mentorship, this up and running within a few weeks.
> >
> > At Your Service,
> > Isaac Kamga.
> >
> >
> >
> >
> >
> > On Thu, Mar 22, 2018 at 10:17 PM, Ed Cable  wrote:
> >
> > > Committers,
> > >
> > > We need a committer who can assist in configuring the VM we've
> requested
> > > for a public demo server for Apache Fineract CN.  The massive hardware
> > > requirements to build locally have made this a huge barrier to
> > prospective
> > > GSOC applicants. We were trying to get this infrastructure set up but
> > don't
> > > have anybody with committer status who've raised their hands to
> configure
> > > the VM that Apache infrastructure is providing us.
> > >
> > > If you're able to, please 

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

[Ed Cable]

Thanks Courage for sharing that proposal. We'll keep you posted as GSOC
proposals get evaluated.

Ed

On Mon, Mar 26, 2018 at 3:27 AM, Courage Angeh 
wrote:

> Hi Viswa,
>
> I agree with you about Demo Server being largely oriented towards a quick
> use but it has a lot of useful data. I have gone through demo server too
> and I see they introduce RSA keys through external properties so I was
> thinking changing all the microservices will be a little more stressful, we
> could pass external properties to it when running the different jar files.
> True talk about Eureka, I am trying to work on that too.
> But I was thinking we don't need that much scripts and we don't have to
> change too much.
> I wrote a proposal about this for a GSOC project,
> https://docs.google.com/document/d/1zp6CeYP6ox51tGSu1fE9cBAWpaQnq
> jeBBVIa-n0evso/edit?usp=sharing
> , could you check it out? I will be delighted to get you point of view and
> comments about this doc :)
>
> Thanks Courage
>
> On Sat, Mar 24, 2018 at 1:06 PM, Viswa Ramamoorthy <
> viswaramamoor...@yahoo.com.invalid> wrote:
>
> >  Hello,
> > I think services need more work to get to deployable state. Demo server
> is
> > largely oriented towards a quick use in laptops/desktops but using Junit
> to
> > bootsrap services may result in inconsistencies.
> > I have been reviewing for sometime now. Based on my review, below are the
> > changes needed to get to deployment in a VM
> > 1. Currently services need RSA key to bootstrap. That is fine. But there
> > is no self acquire mode to get them deployed to environments like demo
> > envs.   a) Ideally a spring configured (say demo config) can be
> > introduced to self acquire RSA keys to continue with service start.
> > b) With this change, we could just start services using spring boot jar
> > with a configuration property at the time of service start up   c) I
> > have tried this change in my laptop for fineract-cn-provisioner. I can
> > raise a PR. Needs to be propagated to other services
> > 2. Eureka registration and renewal is bit flaky. Needs work on self
> > registration front as well as health indicator front. Spring has tooling
> on
> > this front. We just need to add and configure.
> > 3. Develop scripts to start services. Simple shell scripts good enough at
> > this point. a) One use case is to build/deploy for use in VM b)
> > Another use case is to facilitate selective service launch approach that
> > was alluding to a while back. For example, if some one needs to work on
> > 'accounting' services and depends on 'customer' services, they could
> bring
> > up 'customer' along with infrastructures using shell scripts (to be
> > developed) and continue with development in accounting.
> > 4. Deploy basic infrastructure needed for services - Eureka, ActiveMQ,
> > Cassandra and MariaDB. These can be Dockers and I already sent PR on this
> > front.
> > Proposal is to create a new repo to have build/deployment scripts stored
> > to get this used in VM and support laptop use cases to help with
> > development.
> > I can help/guide as needed.
> >
> > RegardsViswa Ramamoorthy
> > On ‎Friday‎, ‎March‎ ‎23‎, ‎2018‎ ‎06‎:‎52‎:‎27‎ ‎AM‎ ‎EDT, Isaac
> > Kamga  wrote:
> >
> >  Hi Ed,
> >
> > I am willing to assist in configuring the VM requested for Apache
> Fineract
> > CN.
> >
> > I don't have all the required skills but with commitment and some
> > mentorship, this up and running within a few weeks.
> >
> > At Your Service,
> > Isaac Kamga.
> >
> >
> >
> >
> >
> > On Thu, Mar 22, 2018 at 10:17 PM, Ed Cable  wrote:
> >
> > > Committers,
> > >
> > > We need a committer who can assist in configuring the VM we've
> requested
> > > for a public demo server for Apache Fineract CN.  The massive hardware
> > > requirements to build locally have made this a huge barrier to
> > prospective
> > > GSOC applicants. We were trying to get this infrastructure set up but
> > don't
> > > have anybody with committer status who've raised their hands to
> configure
> > > the VM that Apache infrastructure is providing us.
> > >
> > > If you're able to, please respond to this thread and jump on to comment
> > > thread on the Apache Infrastructure ticket at
> > > https://issues.apache.org/jira/browse/INFRA-16203
> > >
> > > Thanks,
> > >
> > > Ed
> > >
> > > On Thu, Mar 22, 2018 at 1:54 PM, Ed Cable  wrote:
> > >
> > > > Aleks,
> > > >
> > > > Apache IDs are only available to committers. The guide to becoming a
> > > > committer is at https://cwiki.apache.org/
> confluence/display/FINERACT/
> > > Beco
> > > > ming+a+Committer
> > > >
> > > > I know that the major body of your work related to Fineract isn't yet
> > > > something the customer was willing to contribute back yet so you've
> > been
> > > > trying to build your public contributions in other ways. I was hoping
> > > that
> > > > this task could be a great way to do that but 

Re: Share Dividends wrongly calculated

[Ed Cable]

Sander,

As far as I know according to the designs that the community had moved
forward with implementing it was going to be based on the following whereby
dividends would be calculated based on average share balances held by
members on date of record for the dividend:

Whereby the average share balance is calculated by the balance between the
two dates selected when initiating the dividend?

Is this not the desired behavior? If so, what is the desired behavior you'd
like to see in terms of calculation of the dividend - it would be good if
we could fully document this (the spec we have on the wiki isn't too
detailed unfortunately.).

Clearly in this case though, Robert has found a bug whereby dividends are
being allocated to an individual whose share account is still pending
approval.

Thanks Robert for creating the JIRA ticket, we'll try to get it resolved
promptly!


   -

   Calculate Dividends for Each Shareholder
   -

  Dividends must calculated based on average share account balances
  held by shareholders as of the date of record for the dividend:
  -

 The dividend calculation will be based on the following
 configurations which may be captured and stored for each
period for which
 calculations are to be done.
 -

Calculate Dividend for members who are no longer active
(True/False)
-

 Minimum active period (in days/weeks/months) for member to be
 eligible for dividend (Numeric + period type)
 -

 Amount to be distributed or percentage of profits to be distributed
 -

 Dividend to be calculated based on (Daily balances, monthly
 balances etc)
 -

 Balance to be considered between (Two dates)


On Tue, Mar 27, 2018 at 12:01 AM, Ippez Robert 
wrote:

> @Santosh and all
> I have created a Jira ticket at https://issues.apache.org/
> jira/browse/FINERACT-608 for this.
>
> @Sander, In our setting in SACCOs, dividend calculation is based on the
> whether the account is created within financial year and below or not.
>
> Example, If we are calculating dividend for 2017, we get the total shares
> at the organisation since inception of the organisation e.g if the
> organisation started in 2003, we shall get total shares from 2003 upto 31st
> Dec 2017. Say its 360 shares.
>
> Then if the approved dividend to be given to members is 720,000, we then
> get how much each share will get i.e 720,000/360 = *2,000*
> Now that we know each share gets 2,000, this will be the multiplying
> factor for each members total share.
>
> Eg.
> *Client Name   Total Shares  Dividend*
> Client 1 1
> 2,000
> Client 2 5
>  10,000
> Client 310
> 20,000
> ... etc
>
> *TOTAL   360
>  720,000*
>
> Total amount given to clients should be equal to approved dividend.
>
> I think this is the logic in shares and dividend especially in SACCO
> operation and i think its the same
>
> Thanks
> Regards
> Ippez Robert
>
>
>
>
> ‌
>
> On Tue, Mar 27, 2018 at 9:11 AM, Sander van der Heyden <
> sandervanderhey...@musonisystem.com> wrote:
>
>> Just quickly chipping in with a thought: is this not related to the fact
>> that dividend calculation is done depending on how long the shares were
>> held during the period? I've seen this as well in the past and find this
>> also undesired behaviour, and not sure why it was designed this way.
>>
>> @Ed when you were working on the design together with Dayna, do you know
>> why this was done like this?
>>
>>
>>
>>
>> Sander van der Heyden
>>
>> CTO Musoni Services
>>
>>
>>
>>
>> Mobile (NL): +31 (0)6 14239505
>> Skype: s.vdheyden
>> Website: musonisystem.com
>> Follow us on Twitter!  
>> Postal address: Papiermolen 10, 3994DK Houten, Netherlands
>>
>> On 27 March 2018 at 08:09, Santosh Math 
>> wrote:
>>
>>> Yes Robert, I can see in the case of Amatura Women's Group. Did you raise
>>> the ticket related to this?
>>>
>>> On Tue, Mar 27, 2018 at 11:12 AM, Ippez Robert 
>>> wrote:
>>>
>>> > Hi Santosh,
>>> > I think it just skipped my mind that *posting of Dividend* is done by
>>> *Scheduler
>>> > Job*. I was just posting my response to that then i saw your response.
>>> >
>>> > But the major issue here left is the dividend allocation as described
>>> (by
>>> > me) early, this is very critical.  @Santosh, Were you able to
>>> reproduce the
>>> > same at your ends?.
>>> >
>>> > This has halted our posting because if we continue, wrong values will
>>> be
>>> > posted to clients savings account as dividend when job scheduler is
>>> run. We
>>> > can not proceed with dividend posting unless this is solved for us, yet
>>> > members are demanding their dividend for last year since it just
>>> remains
>>> > 

Re: Merging Swagger API work for Fineract 1.2 release

[Avik Ganguly]

Hi Sanyam,

Last time (couple of months back) I tried to build your branch, it failed
to build and I remember having some discussion regarding the build issues
(although I can't seem to find that discussion in mail or Github).

Are the build issues resolved or is there any manual steps still left which
needs automation to make the build successful?

Regards,
Avik.

On Thu, Mar 29, 2018 at 12:14 AM, Sanyam Goel 
wrote:

> Hi Aleks,
>
> Have you got a chance to review the Pull Request?
> Please let me know if you want to discuss anything regarding the PR, we
> can schedule the meeting on google hangouts or skype and let's try to wrap
> up all the work and push it to the main codebase to boost up the release of
> Fineract 1.2.
>
> Thanks,
> Sanyam
>
> On Fri, Mar 23, 2018 at 3:00 AM, Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> I'll try to get a look at this tomorrow
>>
>>
>> On Thu, Mar 22, 2018, 10:04 PM Sanyam Goel 
>> wrote:
>>
>>> Hi Ed,
>>>
>>> All the GCI work was pushed on the same Pull Request #409.
>>> Please let me know if I need to do any other changes in the PR.
>>>
>>> Thanks,
>>> Sanyam
>>>
>>> On Fri, Mar 23, 2018 at 2:18 AM, Ed Cable  wrote:
>>>
 Sanyam,

 I know that the Swagger work you did during GSOC for Mifos last summer
 is all contained in the open pull request at
 https://github.com/apache/fineract/pull/409

 For the remaining Swagger work on the portfolio APIs that Chirag
 completed, where are those pull requests at?

 Aleks, could you please do any final comments/review on these pull
 requests to help assist Avik and other committers who are soon reviewing
 and merging this code?

 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
   


>>>
>>>
>>> --
>>> SANYAM GOEL
>>> LinkedIn: https://goo.gl/6SJMg3
>>> Github: https://goo.gl/u51wRZ
>>> Hackerrank: https://goo.gl/4kzLf7
>>> +91-9818060934
>>>
>>
>
>
> --
> SANYAM GOEL
> LinkedIn: https://goo.gl/6SJMg3
> Github: https://goo.gl/u51wRZ
> Hackerrank: https://goo.gl/4kzLf7
> +91-9818060934
>

Re: Merging Swagger API work for Fineract 1.2 release

[Sanyam Goel]

Hi Aleks,

Have you got a chance to review the Pull Request?
Please let me know if you want to discuss anything regarding the PR, we can
schedule the meeting on google hangouts or skype and let's try to wrap up
all the work and push it to the main codebase to boost up the release of
Fineract 1.2.

Thanks,
Sanyam

On Fri, Mar 23, 2018 at 3:00 AM, Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> I'll try to get a look at this tomorrow
>
>
> On Thu, Mar 22, 2018, 10:04 PM Sanyam Goel 
> wrote:
>
>> Hi Ed,
>>
>> All the GCI work was pushed on the same Pull Request #409.
>> Please let me know if I need to do any other changes in the PR.
>>
>> Thanks,
>> Sanyam
>>
>> On Fri, Mar 23, 2018 at 2:18 AM, Ed Cable  wrote:
>>
>>> Sanyam,
>>>
>>> I know that the Swagger work you did during GSOC for Mifos last summer
>>> is all contained in the open pull request at https://github.com/apache/f
>>> ineract/pull/409
>>>
>>> For the remaining Swagger work on the portfolio APIs that Chirag
>>> completed, where are those pull requests at?
>>>
>>> Aleks, could you please do any final comments/review on these pull
>>> requests to help assist Avik and other committers who are soon reviewing
>>> and merging this code?
>>>
>>> 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
>>>   
>>>
>>>
>>
>>
>> --
>> SANYAM GOEL
>> LinkedIn: https://goo.gl/6SJMg3
>> Github: https://goo.gl/u51wRZ
>> Hackerrank: https://goo.gl/4kzLf7
>> +91-9818060934
>>
>


-- 
SANYAM GOEL
LinkedIn: https://goo.gl/6SJMg3
Github: https://goo.gl/u51wRZ
Hackerrank: https://goo.gl/4kzLf7
+91-9818060934

Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Sanyam Goel]

Congratulations Steve!

Regards,
Sanyam Goel



On Wed, Mar 28, 2018 at 11:59 PM, Zayyad A. Said <
zay...@intrasofttechnologies.com> wrote:

> Congratulations Steve.
>
>
>
> ***
> Zayyad A. Said | Chairman & C.E.O
>
> Cell No.: +254 716 615274 | Skype: zsaid2011
> Email: zay...@intrasofttechnologies.com
>
>
>
> -Original Message-
> From: Steve Conrad 
> Sent: 28 March 2018 06:14 PM
> To: Dev 
> Subject: Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad
>
> Thanks Myrle. You can feel free to tweet that update. I am not on Twitter,
> so no handle to link to...
> Steve
>
> On Wed, Mar 28, 2018 at 9:10 AM, Myrle Krantz  wrote:
>
> > Congratulations Steve!
> >
> > Would it be okay with you if we tweet your committership as well?  If
> > so, do you have a twitter handle, you'd like me to @?
> >
> > Thanks,
> > Myrle
> >
> >
> > On Wed, Mar 28, 2018 at 4:07 PM, Ed Cable  wrote:
> > > Hello Fineract community,
> > >
> > > I'm proud to announce that Apache Fineract has a new committer.
> > >
> > > Steve has only been a part of the community for a couple months
> > > after
> > being
> > > introduced to us by the team at Musoni. By day Steve is a full-stack
> > > developer at Dassault Systems. In his spare time, he's been doing
> > > all he can to support the community. In that short time, he's added
> > > tremendous value and as a committer will be able to help the
> > > community release more frequently. He fixed a number of critical
> > > bugs in the latest release,
> > added
> > > support for MySQL 5.7 and is now working on both the payment gateway
> > > project and Mojaloop integration with Fineract.
> > >
> > > The Mifos Initiative recognized him as a Star Contributor recently
> > > so
> > click
> > > here to learn more about Steve:
> > > http://mifos.org/blog/star-contributor-steve-conrad/
> > >
> > > Congratulations Steve!  Thank you for your contributions, and we
> > > look forward to your leadership in the community!
> > >
> > > Best Regards,
> > >
> > > Ed Cable
> >
>
>


-- 
SANYAM GOEL
LinkedIn: https://goo.gl/6SJMg3
Github: https://goo.gl/u51wRZ
Hackerrank: https://goo.gl/4kzLf7
+91-9818060934

Re: Planned Features for Fineract 1.2 Release

[Ed Cable]

For the sake of transparency to the community, we're going to miss the
target ship date of this Fineract 1.2 release which was today, March 28.

We've not been able to begin QA yet because we still need to review and
merge the pull requests for features that were ready to be shipped
documented at https://issues.apache.org/jira/projects/FINERACT/versions
/12342856

These
include:

Swagger API work: https://github.com/apache/fineract/pull/409
GSIM & GLIM work: https://github.com/apache/fineract/pull/445
Support for MySQL 5.7: https://github.com/apache/fineract/pull/448
Fix for Fineract-546: https://github.com/apache/fineract/pull/446
Fix for Fineract-574: https://github.com/apache/fineract/pull/441
Fix for Fineract-431: https://github.com/apache/fineract/pull/437

Fineract committers, could you please help with review of these pull
requests so we can move towards the monthly release cycle the community's
been yearning for.

Thanks,

Ed

On Thu, Mar 8, 2018 at 11:06 AM, Ed Cable  wrote:

> Fineract Committers,
>
> We need to merge the pull requests at https://issues.apache.org/
> jira/projects/FINERACT/versions/12342856 into develop branch so we can
> push this to our staging server and QA can begin. Could I please get some
> help with the review and merge of these PRs.
>
> Thanks,
>
> Ed
>
>
>
> On Fri, Mar 2, 2018 at 9:47 AM, Ed Cable  wrote:
>
>> Hi all,
>>
>> Just so we can keep in line with the target that we had given initially
>> around dates for the 1.2 release, here's a pseudo-announcement of the
>> release.
>>
>> The features that were ready as of the cut-off dates during our planning
>> period have been tagged and put in this fix version:
>>
>> https://issues.apache.org/jira/projects/FINERACT/versions/12342856
>>
>> They include the Swagger API Documentation by Chirag Sanyam and GSIM/GLIM
>> enhancements by Nikhil.
>>
>> Apart from small issues or enhancements that I might have missed that are
>> already complete, for 1.2 we won't be shipping any major work apart from
>> there.
>>
>> We're getting our boards configured to visualize the planning for each
>> release and are now starting the planning for 1.3 so if you have work that
>> you're planning to contribute, please make sure it has a corresponding JIRA
>> ticket.
>>
>> Thanks,
>>
>> Ed
>>
>> On Tue, Feb 27, 2018 at 9:22 AM, Ed Cable  wrote:
>>
>>> Myrle,
>>>
>>> Thanks for adding that clarity as my initial email was probably
>>> confusing. We are moving to time-driven releases and the initial planning
>>> period I mentioned was to determine which features or work was ready to be
>>> integrated and could be included in the cut-off date for that time-driven
>>> release.
>>>
>>> I have set up a scrum board and requested karma to grant Robert access
>>> so he can assist in planning out the next release, Apache Fineract 1.2
>>>
>>> Ed
>>>
>>> On Wed, Feb 14, 2018 at 4:01 AM, Sendoro Juma 
>>> wrote:
>>>
 Dear Myrle,

 I see your point:

 I think primarily we should agree that it is time-driven:

 Features listed or to be listed should be taken only as way of making
 focus and pushing for tasks to be completed in-time as per release
 schedule, should they fall short of time... we should move on... with our
 primary commitment which is time.

 How about that?

 Best Regards
 Sendoro



 - Original Message -
 From: "Myrle Krantz" 
 To: "dev" 
 Sent: Wednesday, February 14, 2018 1:55:03 PM
 Subject: Re: Planning Apache Fineract 1.2 Release

 Our release can either be feature-driven or time-driven.  Not both.
 If it's feature-driven, we don't release until the features are in
 there.  If it's time-driven, we release on a certain date, based on
 what's made it in.

 Are we in agreement that we wish to make a time-driven release?  Then
 we should be adding a feature to the list for a given release when
 that feature is integrated, and not before.

 Best Regards,
 Myrle


 On Wed, Feb 14, 2018 at 12:41 PM, Sendoro Juma 
 wrote:
 > Hello Ed,
 >
 > +1 on all you mentioned!
 >
 > I would propose additional point which you have kind of mention it
 already on item related to API Swagger, but just as emphasize
 >
 > - APIs related issues/Enhancements that has been discovered by Mobile
 or Web client application side.
 >
 > This is so,  because we might take longer in addressing issues
 already known from client application side; buy just because of missing
 visibility;
 > So having this branch in Wiki page will remind us.
 >
 >
 > Best Regards
 >
 > - Original Message -
 > From: "Sendoro Juma" 

RE: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Zayyad A. Said]

Congratulations Steve.



***
Zayyad A. Said | Chairman & C.E.O
 
Cell No.: +254 716 615274 | Skype: zsaid2011
Email: zay...@intrasofttechnologies.com 
 


-Original Message-
From: Steve Conrad  
Sent: 28 March 2018 06:14 PM
To: Dev 
Subject: Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

Thanks Myrle. You can feel free to tweet that update. I am not on Twitter, so 
no handle to link to...
Steve

On Wed, Mar 28, 2018 at 9:10 AM, Myrle Krantz  wrote:

> Congratulations Steve!
>
> Would it be okay with you if we tweet your committership as well?  If 
> so, do you have a twitter handle, you'd like me to @?
>
> Thanks,
> Myrle
>
>
> On Wed, Mar 28, 2018 at 4:07 PM, Ed Cable  wrote:
> > Hello Fineract community,
> >
> > I'm proud to announce that Apache Fineract has a new committer.
> >
> > Steve has only been a part of the community for a couple months 
> > after
> being
> > introduced to us by the team at Musoni. By day Steve is a full-stack 
> > developer at Dassault Systems. In his spare time, he's been doing 
> > all he can to support the community. In that short time, he's added 
> > tremendous value and as a committer will be able to help the 
> > community release more frequently. He fixed a number of critical 
> > bugs in the latest release,
> added
> > support for MySQL 5.7 and is now working on both the payment gateway 
> > project and Mojaloop integration with Fineract.
> >
> > The Mifos Initiative recognized him as a Star Contributor recently 
> > so
> click
> > here to learn more about Steve:
> > http://mifos.org/blog/star-contributor-steve-conrad/
> >
> > Congratulations Steve!  Thank you for your contributions, and we 
> > look forward to your leadership in the community!
> >
> > Best Regards,
> >
> > Ed Cable
>

Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Ebenezer Graham]

Congratulations Steve!

*Best Regards,*

*Ebenezer Graham*

*BSc (Hons) Computing*


[image: EmailSignature.png]

Beau Plan Business Park | West Building

Pamplemousses |  Mauritius



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



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



On 28 March 2018 at 19:13, Steve Conrad  wrote:

> Thanks Myrle. You can feel free to tweet that update. I am not on Twitter,
> so no handle to link to...
> Steve
>
> On Wed, Mar 28, 2018 at 9:10 AM, Myrle Krantz  wrote:
>
> > Congratulations Steve!
> >
> > Would it be okay with you if we tweet your committership as well?  If
> > so, do you have a twitter handle, you'd like me to @?
> >
> > Thanks,
> > Myrle
> >
> >
> > On Wed, Mar 28, 2018 at 4:07 PM, Ed Cable  wrote:
> > > Hello Fineract community,
> > >
> > > I'm proud to announce that Apache Fineract has a new committer.
> > >
> > > Steve has only been a part of the community for a couple months after
> > being
> > > introduced to us by the team at Musoni. By day Steve is a full-stack
> > > developer at Dassault Systems. In his spare time, he's been doing all
> he
> > > can to support the community. In that short time, he's added tremendous
> > > value and as a committer will be able to help the community release
> more
> > > frequently. He fixed a number of critical bugs in the latest release,
> > added
> > > support for MySQL 5.7 and is now working on both the payment gateway
> > > project and Mojaloop integration with Fineract.
> > >
> > > The Mifos Initiative recognized him as a Star Contributor recently so
> > click
> > > here to learn more about Steve:
> > > http://mifos.org/blog/star-contributor-steve-conrad/
> > >
> > > Congratulations Steve!  Thank you for your contributions, and we look
> > > forward to your leadership in the community!
> > >
> > > Best Regards,
> > >
> > > Ed Cable
> >
>

Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Steve Conrad]

Thanks Myrle. You can feel free to tweet that update. I am not on Twitter,
so no handle to link to...
Steve

On Wed, Mar 28, 2018 at 9:10 AM, Myrle Krantz  wrote:

> Congratulations Steve!
>
> Would it be okay with you if we tweet your committership as well?  If
> so, do you have a twitter handle, you'd like me to @?
>
> Thanks,
> Myrle
>
>
> On Wed, Mar 28, 2018 at 4:07 PM, Ed Cable  wrote:
> > Hello Fineract community,
> >
> > I'm proud to announce that Apache Fineract has a new committer.
> >
> > Steve has only been a part of the community for a couple months after
> being
> > introduced to us by the team at Musoni. By day Steve is a full-stack
> > developer at Dassault Systems. In his spare time, he's been doing all he
> > can to support the community. In that short time, he's added tremendous
> > value and as a committer will be able to help the community release more
> > frequently. He fixed a number of critical bugs in the latest release,
> added
> > support for MySQL 5.7 and is now working on both the payment gateway
> > project and Mojaloop integration with Fineract.
> >
> > The Mifos Initiative recognized him as a Star Contributor recently so
> click
> > here to learn more about Steve:
> > http://mifos.org/blog/star-contributor-steve-conrad/
> >
> > Congratulations Steve!  Thank you for your contributions, and we look
> > forward to your leadership in the community!
> >
> > Best Regards,
> >
> > Ed Cable
>

For those trying to understand the motivation of certain Apache policies

[Myrle Krantz]

Hey all,

A discussion has started on the apache community dev list which I
believe may be helpful for those wishing to understand the motivation
behind some of Apache's policies (1).  In particular,

" "communities are expected to be open for new people to flow in" - this
is a requirement. A known anti-pattern is when one employer's employees
who are committers start doing project work while ignoring other
committers, and while freezing out (either in terms of code or new
committers being elected) anyone not from that company. That's when the
board will get involved, if the PMC can't self-correct." --Shane Curcuru

This statement isn't just true about companies, it's also true about
"sub-communities" of any sort.  No sub-group of committers or PMC
members should ever gain control over a project and then shut out the
remaining community members.  That would strangle the project in the
long term, since company's attention to a project, or non-profits
funding is fickle and unpredictable.

The rest of that thread is interesting and relevant too, as it
describes the tension between payed work and volunteer work, and the
reasons Apache has taken various decisions and approaches over the
years.

I'd encourage anyone interested in understanding the Apache Software
Foundation better to read that exchange.

Best Regards,
Myrle


1.) 
https://lists.apache.org/thread.html/9a0b1c318f3e29e3150217125c6387a511aba35e11e1f9577de331ff@%3Cdev.community.apache.org%3E

Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Isaac Kamga]

Congratulations And Welcome Aboard Steve Conrad.

On Wed, Mar 28, 2018 at 3:22 PM Chirag Gupta 
wrote:

> Congratulations Steve !!
>
> On Wed, Mar 28, 2018, 7:40 PM Myrle Krantz  wrote:
>
> > Congratulations Steve!
> >
> > Would it be okay with you if we tweet your committership as well?  If
> > so, do you have a twitter handle, you'd like me to @?
> >
> > Thanks,
> > Myrle
> >
> >
> > On Wed, Mar 28, 2018 at 4:07 PM, Ed Cable  wrote:
> > > Hello Fineract community,
> > >
> > > I'm proud to announce that Apache Fineract has a new committer.
> > >
> > > Steve has only been a part of the community for a couple months after
> > being
> > > introduced to us by the team at Musoni. By day Steve is a full-stack
> > > developer at Dassault Systems. In his spare time, he's been doing all
> he
> > > can to support the community. In that short time, he's added tremendous
> > > value and as a committer will be able to help the community release
> more
> > > frequently. He fixed a number of critical bugs in the latest release,
> > added
> > > support for MySQL 5.7 and is now working on both the payment gateway
> > > project and Mojaloop integration with Fineract.
> > >
> > > The Mifos Initiative recognized him as a Star Contributor recently so
> > click
> > > here to learn more about Steve:
> > > http://mifos.org/blog/star-contributor-steve-conrad/
> > >
> > > Congratulations Steve!  Thank you for your contributions, and we look
> > > forward to your leadership in the community!
> > >
> > > Best Regards,
> > >
> > > Ed Cable
> >
>

Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Chirag Gupta]

Congratulations Steve !!

On Wed, Mar 28, 2018, 7:40 PM Myrle Krantz  wrote:

> Congratulations Steve!
>
> Would it be okay with you if we tweet your committership as well?  If
> so, do you have a twitter handle, you'd like me to @?
>
> Thanks,
> Myrle
>
>
> On Wed, Mar 28, 2018 at 4:07 PM, Ed Cable  wrote:
> > Hello Fineract community,
> >
> > I'm proud to announce that Apache Fineract has a new committer.
> >
> > Steve has only been a part of the community for a couple months after
> being
> > introduced to us by the team at Musoni. By day Steve is a full-stack
> > developer at Dassault Systems. In his spare time, he's been doing all he
> > can to support the community. In that short time, he's added tremendous
> > value and as a committer will be able to help the community release more
> > frequently. He fixed a number of critical bugs in the latest release,
> added
> > support for MySQL 5.7 and is now working on both the payment gateway
> > project and Mojaloop integration with Fineract.
> >
> > The Mifos Initiative recognized him as a Star Contributor recently so
> click
> > here to learn more about Steve:
> > http://mifos.org/blog/star-contributor-steve-conrad/
> >
> > Congratulations Steve!  Thank you for your contributions, and we look
> > forward to your leadership in the community!
> >
> > Best Regards,
> >
> > Ed Cable
>

Re: [ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Myrle Krantz]

Congratulations Steve!

Would it be okay with you if we tweet your committership as well?  If
so, do you have a twitter handle, you'd like me to @?

Thanks,
Myrle


On Wed, Mar 28, 2018 at 4:07 PM, Ed Cable  wrote:
> Hello Fineract community,
>
> I'm proud to announce that Apache Fineract has a new committer.
>
> Steve has only been a part of the community for a couple months after being
> introduced to us by the team at Musoni. By day Steve is a full-stack
> developer at Dassault Systems. In his spare time, he's been doing all he
> can to support the community. In that short time, he's added tremendous
> value and as a committer will be able to help the community release more
> frequently. He fixed a number of critical bugs in the latest release, added
> support for MySQL 5.7 and is now working on both the payment gateway
> project and Mojaloop integration with Fineract.
>
> The Mifos Initiative recognized him as a Star Contributor recently so click
> here to learn more about Steve:
> http://mifos.org/blog/star-contributor-steve-conrad/
>
> Congratulations Steve!  Thank you for your contributions, and we look
> forward to your leadership in the community!
>
> Best Regards,
>
> Ed Cable

[ANNOUNCE] New Apache Fineract Committer Steve Conrad

[Ed Cable]

Hello Fineract community,

I'm proud to announce that Apache Fineract has a new committer.

Steve has only been a part of the community for a couple months after being
introduced to us by the team at Musoni. By day Steve is a full-stack
developer at Dassault Systems. In his spare time, he's been doing all he
can to support the community. In that short time, he's added tremendous
value and as a committer will be able to help the community release more
frequently. He fixed a number of critical bugs in the latest release, added
support for MySQL 5.7 and is now working on both the payment gateway
project and Mojaloop integration with Fineract.

The Mifos Initiative recognized him as a Star Contributor recently so click
here to learn more about Steve:
http://mifos.org/blog/star-contributor-steve-conrad/

Congratulations Steve!  Thank you for your contributions, and we look
forward to your leadership in the community!

Best Regards,

Ed Cable

Re: Discussing Mojaloop and Fineract Integration

[Steve Conrad]

Good questions, Ed. There is not a central UI/front end for the Mojaloop
platform, so you won't see anything if you navigate to mifosmojaloop.com.
You can make REST calls to the specific services at the ports that I
mentioned in my previous email.

I can work on some basic flows for the transactions that we identified:
Peer-to-peer payment, Merchant receiving payment, and bulk payments (ie.
payroll disbursement or bulk loan disbursement). Isaac and Rahul, do you
have thoughts or ideas on these?

Thanks,
Steve


On Tue, Mar 27, 2018 at 7:03 PM, Ed Cable  wrote:

> Steve,
>
> Thanks for getting this set up on the Mifos AWS infrastructure so the
> broader community can benefit and we can start demonstrating some end to
> end to scenarios/use cases which demonstrate the capability of the Fineract
> and Mojaloop integration.
>
> Should the http://mifosmojaloop.com URL be accessible via a browser or
> only through a REST client when testing the API connections? I can't access
> it from a browser currently.
>
> James, thanks for updating the document that Isaac had started. I think a
> good next step would be as you suggested to identify the specific flows for
> the use cases that demonstrate the different scenarios/setups we had
> outlined before. From there we can then have solid tasks in place for the
> points of integration with Fineract 1.x APIs and look at the overlap
> between Mojaloop and Fineract CN APIs.
>
> Sanyam put in a proposal around this for GSOC and getting further clarity
> will be beneficial if we move forward with that proposal.
>
> Ed
>
> On Mon, Mar 26, 2018 at 5:02 PM, James Dailey 
> wrote:
>
>> Hi All -
>>
>> I'm iterating on https://docs.google.com/doc
>> ument/d/1p1MaVXhNJqTptS532cyA3hbaYJB3IqudY8ScHLM6EJI/edit#  until we get
>> tasks into the Fineract-CN setup.
>>
>> Steve - what's the next step for the community to work on do you think?
>>  Should we look at the flows specifically for use cases?
>>
>> James
>>
>> On Sat, Mar 24, 2018 at 7:30 AM Steve Conrad  wrote:
>>
>>> I have created a test instance of Mojaloop that people can use to test
>>> and play with. You can access this test instance at
>>> http://mifosmojaloop.com
>>>
>>> It is a single Ubuntu box with 4 different VMs running on it - the
>>> Mojaloop core, the IST server, and 2 simulated DFSP instances (just like we
>>> saw in the demo/screencast that Ed referred to earlier). Because we are
>>> accessing all 4 servers through a single machine, I had to forward
>>> different ports to route to the different services. Here are some of the
>>> basic mappings:
>>>
>>> mifosmojaloop.com:3000 - Central Directory service
>>> mifosmojaloop.com:3001 - End User Registry
>>> mifosmojaloop.com:3002 - Central Ledger
>>>
>>> mifosmojaloop.com:3119 - DFSP USSD test client 1 (this is the cell
>>> phone simulator created by Software Group that is shown in the screencast)
>>> mifosmojaloop.com:3219 - DFSP USSD test client 2
>>>
>>> There are several other services/endpoints available - if you would like
>>> access to those, let me know and I can get the full port mapping to you.
>>> Steve
>>>
>>> On Fri, Mar 9, 2018 at 7:01 PM, Ed Cable  wrote:
>>>
 Thanks James for sharing that summary of the discussion. For anyone
 that wants to listen to the audio recording of the session, you can find it
 at https://youtu.be/Ur7rb0jHzOg

 Here's a brief summary of next steps and action items for those who
 weren't able to attend, can get involved.


- Fineract 1.x Integration - Steve Conrad is going to be heading up
exploring the Mojaloop APIs and their points of integration with 
 Fineract
1.x and and the needed configurations for the different use
cases/simulation environments that James listed above. In parallel he's
going to bring this into alignment with the payment gateway project to
ensure that the structure of a payment in Fineract aligns with that of
Mojaloop
- Fineract CN Integration - Isaac Kamga and Rahul Goel are going to
drive similar efforts but with the Fineract CN architecture based on
availability of requisite APIs, etc.
- Public Lab Environment - working with Steve, I'll make available
AWS infrastructure from the Mifos Initiative so we can make a publicly
accessible environment of Mojaloop connected to Fineract so others can 
 test
it out.
- GSOC Project - Steve will be helping to draft out some tasks that
a student could work on to contribute towards these efforts to build out
this public lab environment simulating a fully connected payments 
 ecosystem
of different flavors of DFS providers running Fineract that are all
connected via the Mojaloop platform.

 Ed

 On Thu, Mar 8, 2018 at 10:55 PM, James Dailey 

Re: Introducing Myself to Fineract Community

[Achia Rolence]

Thanks very much Ed.

I will begin looking at them and will contact the team in case any
difficulties.

Rolence

On Wed, Mar 28, 2018 at 2:27 PM, Ed Cable  wrote:

> Welcome Achia Rolence,
>
> You can fix a P1 bug  or find an issue with the
> Volunteer tag in Apache Fineract 1.x  to get
> started. Do let us know if you have any questions or difficulties in
> getting your dev environment set up.
>
> If you'd like to work on a more in-depth or involved task than you find in
> the last we can also connect you with one as well.
>
> Ed
>
>
>
> On Wed, Mar 28, 2018 at 4:34 AM, rolence achia 
> wrote:
>
> > Hello Fineracters, I am Achia Rolence from Buea, Cameroon. I have a
> > background in Telecoms and recently I have decided to improve my
> > programming and architectural skills and open source is one of the best
> way
> > to gain these competencies. Fineract is a necessary project/tool to help
> > fight poverty.
> > To this end I am passionate to help grow the project and provide
> solutions
> > which will help eliminate Financial Exclusion
> > and lift people out of poverty within my community (Africa) and the rest
> of
> > the world.
> > The Finract CN project provides a unique opportunity given it's open
> source
> > and provides a platform for innovation in unlimited ways.
> > I am familiar with some front end tech (JavaScript/Angular/Ionic) as well
> > as some skills in Java Spring and Spring Boot.
> > I am currently getting upto speed with Fineract 1.x as well as Fineract
> CN
> > (very interesting project). Are there any beginner or high priority tasks
> > which needs to be delivered in the next few months? I will be willing to
> > put in a few hours per week to help out. Thanks very much for the
> > opportunity. Achia Rolence
> >
>
>
>
> --
> *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: Introducing Myself to Fineract Community

[Ed Cable]

Welcome Achia Rolence,

You can fix a P1 bug  or find an issue with the
Volunteer tag in Apache Fineract 1.x  to get
started. Do let us know if you have any questions or difficulties in
getting your dev environment set up.

If you'd like to work on a more in-depth or involved task than you find in
the last we can also connect you with one as well.

Ed



On Wed, Mar 28, 2018 at 4:34 AM, rolence achia 
wrote:

> Hello Fineracters, I am Achia Rolence from Buea, Cameroon. I have a
> background in Telecoms and recently I have decided to improve my
> programming and architectural skills and open source is one of the best way
> to gain these competencies. Fineract is a necessary project/tool to help
> fight poverty.
> To this end I am passionate to help grow the project and provide solutions
> which will help eliminate Financial Exclusion
> and lift people out of poverty within my community (Africa) and the rest of
> the world.
> The Finract CN project provides a unique opportunity given it's open source
> and provides a platform for innovation in unlimited ways.
> I am familiar with some front end tech (JavaScript/Angular/Ionic) as well
> as some skills in Java Spring and Spring Boot.
> I am currently getting upto speed with Fineract 1.x as well as Fineract CN
> (very interesting project). Are there any beginner or high priority tasks
> which needs to be delivered in the next few months? I will be willing to
> put in a few hours per week to help out. Thanks very much for the
> opportunity. Achia Rolence
>



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

Introducing Myself to Fineract Community

[rolence achia]

Hello Fineracters, I am Achia Rolence from Buea, Cameroon. I have a
background in Telecoms and recently I have decided to improve my
programming and architectural skills and open source is one of the best way
to gain these competencies. Fineract is a necessary project/tool to help
fight poverty.
To this end I am passionate to help grow the project and provide solutions
which will help eliminate Financial Exclusion
and lift people out of poverty within my community (Africa) and the rest of
the world.
The Finract CN project provides a unique opportunity given it's open source
and provides a platform for innovation in unlimited ways.
I am familiar with some front end tech (JavaScript/Angular/Ionic) as well
as some skills in Java Spring and Spring Boot.
I am currently getting upto speed with Fineract 1.x as well as Fineract CN
(very interesting project). Are there any beginner or high priority tasks
which needs to be delivered in the next few months? I will be willing to
put in a few hours per week to help out. Thanks very much for the
opportunity. Achia Rolence

Re: GSoC 2018: Fineract CN SMS & Email Notifications

[Viswa Ramamoorthy]

 Ed,
I am interested. Please send me an invite
RegardsViswa

On ‎Tuesday‎, ‎March‎ ‎27‎, ‎2018‎ ‎08‎:‎11‎:‎04‎ ‎PM‎ ‎EDT, Ed Cable 
 wrote:  
 
 Viswa,

There are some GSOC prospects who would like to work on some of these
containerization ideas/projects. You'd be a great fit to help mentor. I'm
going to send you an invite to mentor in case you'd like to be involved.

Ed

On Sun, Mar 11, 2018 at 4:05 PM, Viswa Ramamoorthy <
viswaramamoor...@yahoo.com.invalid> wrote:

>  Hi, Myrtle,
> I can make Docker infrastructure enabled explicitly that would leave
> embedded ActiveMQ and Eureka default. I will update PR on this front.
> Eclipse plugin is to get  project files for import into an IDE typically
> Spring STS. When 'eclipse' gradle plugin is included, I could typically run
> './gradlew eclipse' that would create ".project" and ".classpath" files.
> After this I can import project and add gradle config to have the project
> available in IDE for debugging purposes. I typically use Spring STS as IDE
> which is built on top of Eclipse.
> Regarding second point, I need to check and I will add back.
> One other design aspect that stood out was RSA feature (i.e. system
> properties like public key, private key etc related to certificate) baked
> into each service and made mandatory. Any reasons to have it mandatory?
> Would it not be a deployment addition rather than making it mandatory for
> service start up? Reason I bring this up is that it makes service rely on a
> pre-step to acquire certificate keys before launch. Even if it is needed in
> each service, can it be made optional so development environments do not
> have to deal with this?
> RegardsViswa Ramamoorthy
>
>    On ‎Sunday‎, ‎March‎ ‎11‎, ‎2018‎ ‎03‎:‎38‎:‎48‎ ‎PM‎ ‎EDT, Myrle
> Krantz  wrote:
>
>  Hey Viswa,
>
> You make some fair points.
>
> But with respect to micro service architecture, it is possible to get
> deploy in one process, but, by keeping the data for the services
> separate, leave the path open to a "proper" micro-service deployment.
> This is what we need to do if we wish to enable developers to work on
> Fineract CN who can't afford higher end machines.
>
> I suggest we:
> * add the dockerization, but not make it the default.  This is a
> demo-server and not a "real" deployment.
> * add instructions to the demo-server readme to cover the log and
> debugging problems.
>
> Beyond that there are two (solveable) problems with your pull request:
> 1.) you're using the eclipse gradle plugin.  It's probably under the
> eclipse license.  The eclipse license is a so-called Category B
> license.  You either need to follow that license's requirements or
> remove the plugin.  I haven't looked closely enough at the plugin to
> learn the benefit you derive from adding it.  If you can explain why
> you want it, I'll help you figure out how to conform to the licensing
> requirements.
> 2.) You've accidentally removed spin down code for ActiveMQ and
> Eureka.  These are both @ClassRules in the original code.  This means
> that their "after" functions are called when the test ends.  By moving
> their spin up from the ClassRule into "before", and not adjusting
> "after", you loose the cleanup code.
>
> Best Regards,
> Myrle
>
>
> On Tue, Mar 6, 2018 at 12:54 AM, Viswa Ramamoorthy
>  wrote:
> >  Hello Myrle,
> > Thanks for sharing your thoughts on Dockerization of services.
> > My experience with embedding infrastructure inside application JVM (even
> for development purposes) has not been great. In a development, when things
> change so much, embedding infrastructure adds additional time to bootstrap
> the whole thing when application restarts needed. Having external
> infrastructures gives better visibility as well as their failure to start
> can be diagnosed better (e.g. a port is not available because another
> instance of a infrastructure is already running in the background).
> > With external infrastructures, installation becomes cumbersome if we go
> with installation of infrastructure and every one need to follow those
> steps to install to get there. My PR is really to solve that part.
> > Some of the complexity, that you alluded to, are really complexity of
> design/developing in micro services architecture.
> > Couple of points about logging (that stays within Docker) as well as
> debug mode with Docker deployment, are very much solvable with Docker
> deployment.
> > Regarding high amount of resources needed for deployment, one strategy
> that could be looked into is to provide capability to selectively start
> services needed for a feature to complete and leave the full deployment to
> integration environments.
> > If you looking into collapsing micro-services into a single war, for
> development purposes, it can be a strategy that would work. But all of the
> services need to be using compatible version of frameworks and managing
> different configurations can be