Re: Self-Service APIs for GSOC Students

[Abhay Chawla]

Hello Everyone,

As I was exploring the APIs that I will be using for user management I saw
that we don't have a field for mobile no in the API for users, only the
email. On the other hand, clients have both email and mobile. I want to
know why do we don't have a mobile no in the users API, considering that
for self-service registration in the Online banking app as I see the user
requires one of them for authentication. Also according to my
understanding, I want to confirm are all self-service users definitely
clients? I would appreciate if anyone of you could clarify this.

And yes Welcome, Shruthi and thanks for your help on the APIs.

Thanks
Abhay.


On Fri, Jul 6, 2018 at 6:26 PM Ed Cable  wrote:

> As you all saw via the intro to the dev list, I wanted to introduce you to
> Shruthi, who is beginning to work on the self-service API wrappers.
>
> She'll be on our check-in today so hopefully she can schedule some time
> with each of the interns who need assistance as well.
>
> On Thu, Jun 21, 2018 at 3:23 PM Ed Cable  wrote:
>
>> Saksham and Ankit,
>>
>> Thanks for your patience and your engagement with Adi thus far in helping
>> to get clarity around the APIs needed for your projects.
>>
>> I do have a resource finally coming on board that will be able to assist
>> directly by building out the wrappers around existing APIs to enable them
>> as self-service.
>>
>> Can you please confirm that these are the APIs that are missing and/or
>> lacking documentation:
>>
>> *Lacking Documentation:*
>> @Dilpreet Singh   Are you able to document these
>> on the Fineract API docs page since you consumed them last summer?
>>
>> Or Perhaps @Sampath Kumar G  you could
>> do documentation with support of Adi/Nazeer and Dilpreet.
>>
>>- View Reports
>>- Notification Service
>>   - GET device/registration/client/{clientId}
>>   - POST device/registration
>>   - PUT device/registration/{id}
>>- Registration Service
>>   - POST registration
>>   - POST registration/user
>>
>> *New APIs to be Built*
>> Saksham and Ankit have documented the new APIs that need to be created at
>> https://issues.apache.org/jira/browse/FINERACT-628 inclusive of:
>>
>> 1) Support for applying for for savings accounts
>> 2) Support for viewing share accounts
>> 3) Support for adding guarantors
>> 4) Support for editing user details.
>> 5) Support for surveys
>>
>> 6) Support for Applying for new Shares Account
>>
>> 7) Support for uploading new Client's Image
>>
>> 8) Support for the list of Loan, Savings, Shares product along with their
>> details
>>
>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>   
>>
>>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
> --
> You received this message because you are subscribed to the Google Groups
> "Mifos Google Summer of Code 2018" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gsoc-2018+unsubscr...@mifos.org.
>

Re: Apache Fineract CN API Documentation

[Ebenezer Graham]

Thank you so much, Isaac.

This documentation will make life much easier.

Will there be documentation for the portfolio service anytime soon?

*At your service,*

*Ebenezer Graham*

*BSc (Hons) Computing*


[image: EmailSignature.png]

African Leadership University,

Power Mill Road, Pamplemousses,

Mauritius.


​
*skype*:
​ebenezer.graham
GitHub  | LinkedIn
 | Twitter
 | Facebook

www.pactmart.com | Freelancing made easy.


*“Talk is cheap, show me the code.” *- *Linus Torvalds*



On 5 July 2018 at 19:26, Isaac Kamga  wrote:

> Hello there,
>
> Trust that this email finds you in good health.
>
> I just hosted the Apache Fineract CN API documentation
>  which I've been working
> on
> so Fineracters can view and give some feedback. This will be quite helpful
> for GSoC students and developers working with Fineract CN as well as
> business persons who want a feel of the API Documentation. Note that this
> is just a temporary site for these docs, they'll eventually be hosted on
> Apache infrastructure.
>
> @Myrle Kindly take some time to review the aforementioned Pull Request so
> we make progress on that front.
>
> I hope this helps.
>
> At Your Service,
> Isaac Kamga.
>
> On Thu, Jun 28, 2018 at 11:21 AM Isaac Kamga 
> wrote:
>
> > Hi James,
> >
> > Thanks for your email.
> >
> > Yes, I think the API documentation can be an important part of the Apache
> > Fineract CN project.
> >
> > The document
> >  Apache+Fineract+CN+API+Documentation>
> > I wrote which you quoted above helps anyone generate the snippets and
> view
> > the api docs...developers would be okay with it.
> > When I'm done with another iteration of the project, I'll update the
> > community on how the documentation actually looks.
> >
> > At Your Service,
> > Isaac Kamga.
> >
> > On Fri, May 25, 2018 at 10:42 PM James Dailey 
> > wrote:
> >
> >> Isaac - This is a thread I am trying to follow.  Thank you for all the
> >> work
> >> you're putting in, and to Myrle for being a mentor on this work.  Seems
> >> like it is leading to something really important for the project.
> >>
> >> I wonder if this <
> >>
> >> https://cwiki.apache.org/confluence/display/FINERACT/
> Apache+Fineract+CN+API+Documentation
> >> >
> >> should or could be expanded to explain and document the API or if we
> >> should
> >> have a separate API Documentation File.
> >>
> >> At a requirements level, I'm trying to figure out how Mojaloop APIs and
> >> Fineract-CN APIs would interact, perhaps as a model for how Fineract-CN
> >> and
> >> other outside API driven systems will function together.  On the
> Mojaloop
> >> project they have a 190 page documentation of the standard API starting
> >> with some statements that I think may also be relevant to how the
> >> Fineract-CN services architecture is set up.
> >>
> >> https://github.com/mojaloop/mojaloop-specification/blob/
> master/API%20Definition%20v1.0.pdf
> >>
> >>
> >> Specifically, I'm referring to section 3.1.1. .  Of those
> characteristics
> >> mentioned, which apply to Fineract-CN? :
> >>
> >>- Fully Asychronous (esp for long running processes) :  my guess,
> seems
> >>likely yes on Fineract-CN - yes?
> >>- Decentralized (no central authority):  My current understanding is
> >>that Fineract-CN has dependencies but not centralization?
> >>- Service Oriented :  that seems like a given in Fineract-CN as it is
> >>also a micro-services arch.
> >>- Not fully stateless (some info required to be kept client and
> server
> >>side to complete fin tranx):  Hmm...
> >>- Client (side) decided common ID (complexity reduced by relying on
> >>client to initiate tranx calls):  Maybe not yet in our thinking ?
> >> contrary?
> >>
> >> Similarly, there is a reference to how generic URI's are formed with a
> >> given example:
> >> scheme:[//[user:password@]host[:port]][/]path[?query][#fragment]
> >>
> >> and other things like max header size and so forth.
> >>
> >> As I lack the skills to actually work on this code, I'm hoping I can
> >> contribute at the level of conceptual understanding and requirements,
> and
> >> perhaps add to the Documentation if I can understand what is actually
> >> going
> >> on here.  If this is already documented, please send me there.
> >>
> >> ( Myrle - hope this is helpful, if not, let me know please.  )
> >>
> >> Thanks,
> >> - James
> >>
> >>
> >> On Thu, May 24, 2018 at 6:00 AM Isaac Kamga 
> >> wrote:
> >>
> >> > Hello Myrle,
> >> >
> >> > Trust that you're doing great.
> >> >
> >> > Following your recommendations, I intended solving the issue using a
> >> 3-step
> >> > approach;
> >> >
> >> > 1. Obtain token
> >> > 2. Validate token
> >> > 3. Add token to MockMvc call as a header.
> >> >
> >> > However, I've been 

Re: Questions regarding Swagger APIs for GSOC

[Dingfan Zhao]

Dear Ed, ALeks & Sanyam, 

Dear Ed, thanks for your help on facilitating our communication. Actually I 
found out some of the usage of APIs based on the requirements, could you all 
take a look and tell me if there is any inappropriate usage about the API?

The reference of APIs: https://demo.openmf.org/api-docs/apiLive.htm#loans_list 

Outstanding principal and interest
GET https://DomainName/fineract-provider/api/v1/loans 

There are two fields in the response of this request principalOutstanding & 
interestOutstanding
Next due date, due principal and interest
For due principal, GET https://DomainName/api/v1/loans/{loanId} 
 There is a field called 
“principalOverdue”
I have a question about the difference between overdue and due 
For due date, “overdueSinceDate” + “repaymentEvery” (one time period of 
repayment)
For due interest, “interestOverdue”
Previous payment date, principal and interest (the last transaction of loan)
For previous due date, GET https://DomainName/api/v1/loans/{loanId} 
 inside there is a field called 
“overdueSinceDate”
Loan maturity date
GET https://DomainName/api/v1/loans/{loanId} 
 “expectedMaturityDate”
Overdue loan principal and interest (if have)
GET https://DomainName/api/v1/loans/{loanId} 
 “principalOverdue”, 
“interestOverdue”
Number of days in arrears for loan
Current date - “overdueSinceDate”
Penalty fees/charges
GET https://DomainName/api/v1/loans/{loanId} 
 “penaltyChargesCharged”
Client activation date
GET https://DomainName/api/v1/clients/template 
 “activationDate”
Loan disbursed date/amount/interest
GET https://DomainName/api/v1/loans/{loanId} 
 fields about disbursement
First repayment date
POST https://DomainName/api/v1/loans?command=calculateLoanSchedule 
 “period” —> 
“dueDate”
Regards,
Dingfan

> On 6 Jul 2018, at 10:28 PM, Ed Cable  wrote:
> 
> Dingfan,
> 
> I'll let you connect with Sanyam on list about your Swagger connections for 
> your GCI Swagger API pull request: Swagger API work: 
> https://github.com/apache/fineract/pull/409 
> 
> 
> Ed
> 

Re: Apache Fineract CN API Documentation

[Ruphine Kengne]

Hello Isaac,

Congratulations and thank you for your work done.
I am already getting some help from that API docs to consume some of the
endpoints for the Group Microservice to actually know what data to send in
for a particular endpoint.

It is actually helpful. Thanks

Regards,

Ruphine Kengne

On 5 July 2018 at 16:26, Isaac Kamga  wrote:

> Hello there,
>
> Trust that this email finds you in good health.
>
> I just hosted the Apache Fineract CN API documentation
>  which I've been working
> on
> so Fineracters can view and give some feedback. This will be quite helpful
> for GSoC students and developers working with Fineract CN as well as
> business persons who want a feel of the API Documentation. Note that this
> is just a temporary site for these docs, they'll eventually be hosted on
> Apache infrastructure.
>
> @Myrle Kindly take some time to review the aforementioned Pull Request so
> we make progress on that front.
>
> I hope this helps.
>
> At Your Service,
> Isaac Kamga.
>
> On Thu, Jun 28, 2018 at 11:21 AM Isaac Kamga 
> wrote:
>
> > Hi James,
> >
> > Thanks for your email.
> >
> > Yes, I think the API documentation can be an important part of the Apache
> > Fineract CN project.
> >
> > The document
> >  Apache+Fineract+CN+API+Documentation>
> > I wrote which you quoted above helps anyone generate the snippets and
> view
> > the api docs...developers would be okay with it.
> > When I'm done with another iteration of the project, I'll update the
> > community on how the documentation actually looks.
> >
> > At Your Service,
> > Isaac Kamga.
> >
> > On Fri, May 25, 2018 at 10:42 PM James Dailey 
> > wrote:
> >
> >> Isaac - This is a thread I am trying to follow.  Thank you for all the
> >> work
> >> you're putting in, and to Myrle for being a mentor on this work.  Seems
> >> like it is leading to something really important for the project.
> >>
> >> I wonder if this <
> >>
> >> https://cwiki.apache.org/confluence/display/FINERACT/
> Apache+Fineract+CN+API+Documentation
> >> >
> >> should or could be expanded to explain and document the API or if we
> >> should
> >> have a separate API Documentation File.
> >>
> >> At a requirements level, I'm trying to figure out how Mojaloop APIs and
> >> Fineract-CN APIs would interact, perhaps as a model for how Fineract-CN
> >> and
> >> other outside API driven systems will function together.  On the
> Mojaloop
> >> project they have a 190 page documentation of the standard API starting
> >> with some statements that I think may also be relevant to how the
> >> Fineract-CN services architecture is set up.
> >>
> >> https://github.com/mojaloop/mojaloop-specification/blob/
> master/API%20Definition%20v1.0.pdf
> >>
> >>
> >> Specifically, I'm referring to section 3.1.1. .  Of those
> characteristics
> >> mentioned, which apply to Fineract-CN? :
> >>
> >>- Fully Asychronous (esp for long running processes) :  my guess,
> seems
> >>likely yes on Fineract-CN - yes?
> >>- Decentralized (no central authority):  My current understanding is
> >>that Fineract-CN has dependencies but not centralization?
> >>- Service Oriented :  that seems like a given in Fineract-CN as it is
> >>also a micro-services arch.
> >>- Not fully stateless (some info required to be kept client and
> server
> >>side to complete fin tranx):  Hmm...
> >>- Client (side) decided common ID (complexity reduced by relying on
> >>client to initiate tranx calls):  Maybe not yet in our thinking ?
> >> contrary?
> >>
> >> Similarly, there is a reference to how generic URI's are formed with a
> >> given example:
> >> scheme:[//[user:password@]host[:port]][/]path[?query][#fragment]
> >>
> >> and other things like max header size and so forth.
> >>
> >> As I lack the skills to actually work on this code, I'm hoping I can
> >> contribute at the level of conceptual understanding and requirements,
> and
> >> perhaps add to the Documentation if I can understand what is actually
> >> going
> >> on here.  If this is already documented, please send me there.
> >>
> >> ( Myrle - hope this is helpful, if not, let me know please.  )
> >>
> >> Thanks,
> >> - James
> >>
> >>
> >> On Thu, May 24, 2018 at 6:00 AM Isaac Kamga 
> >> wrote:
> >>
> >> > Hello Myrle,
> >> >
> >> > Trust that you're doing great.
> >> >
> >> > Following your recommendations, I intended solving the issue using a
> >> 3-step
> >> > approach;
> >> >
> >> > 1. Obtain token
> >> > 2. Validate token
> >> > 3. Add token to MockMvc call as a header.
> >> >
> >> > However, I've been unable to get status different from 404 (Not Found)
> >> and
> >> > 403 (Forbidden) in the MockMvc calls...so I think I'm getting at least
> >> one
> >> > of the 3 steps above wrong.
> >> >
> >> > Regarding 1.), I used TenantApplicationSecurityTestRule's
> >> > getPermissionToken() method to obtain some tokens based on Allowed
> >> > 

Questions regarding Swagger APIs for GSOC

[Ed Cable]

Dingfan,

I'll let you connect with Sanyam on list about your Swagger connections for
your GCI Swagger API pull request: Swagger API work:
https://github.com/apache/fineract/pull/409

Ed

Re: Self-Service APIs for GSOC Students

[Ed Cable]

As you all saw via the intro to the dev list, I wanted to introduce you to
Shruthi, who is beginning to work on the self-service API wrappers.

She'll be on our check-in today so hopefully she can schedule some time
with each of the interns who need assistance as well.

On Thu, Jun 21, 2018 at 3:23 PM Ed Cable  wrote:

> Saksham and Ankit,
>
> Thanks for your patience and your engagement with Adi thus far in helping
> to get clarity around the APIs needed for your projects.
>
> I do have a resource finally coming on board that will be able to assist
> directly by building out the wrappers around existing APIs to enable them
> as self-service.
>
> Can you please confirm that these are the APIs that are missing and/or
> lacking documentation:
>
> *Lacking Documentation:*
> @Dilpreet Singh   Are you able to document these
> on the Fineract API docs page since you consumed them last summer?
>
> Or Perhaps @Sampath Kumar G  you could
> do documentation with support of Adi/Nazeer and Dilpreet.
>
>- View Reports
>- Notification Service
>   - GET device/registration/client/{clientId}
>   - POST device/registration
>   - PUT device/registration/{id}
>- Registration Service
>   - POST registration
>   - POST registration/user
>
> *New APIs to be Built*
> Saksham and Ankit have documented the new APIs that need to be created at
> https://issues.apache.org/jira/browse/FINERACT-628 inclusive of:
>
> 1) Support for applying for for savings accounts
> 2) Support for viewing share accounts
> 3) Support for adding guarantors
> 4) Support for editing user details.
> 5) Support for surveys
>
> 6) Support for Applying for new Shares Account
>
> 7) Support for uploading new Client's Image
>
> 8) Support for the list of Loan, Savings, Shares product along with their
> details
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>

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

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

Re: Status of Demo Server on Apache VM Infrastructure

[Ed Cable]

Aleks,

Have you made any progress on the additional suggestions from Myrle about
prioritizing which microservices run initially?

Thanks,

Ed

On Tue, Jun 26, 2018 at 8:40 AM Ed Cable  wrote:

> In case others haven't been following the ticket on the Infra Issue
> Tracker, below are the latest comments:
>
> Looks like our short-term options are the following:
>
> 1) Try running demo server without Rhythm (Aleks - what is status of this?)
> 2) Run an additional VM on Apache Infra
>
> while a long-term fix is to deploy all services from one process that
> Myrle documented at
> https://issues.apache.org/jira/projects/FINCN/issues/FINCN-25 and has
> been worked on by Leo
>
> Chris Lambertus had escalated our request for additional RAM to VP Infra
> and "he said that you will need to make a request to the board for budget
> for a machine sufficient to run the demo, as this is far beyond the level
> of resources Infra is able to provide."
>
> To which Myrle, replied:
>
> This is a microservice architecture.  It is so resource intensive because
> there are 13 services being run, each in its own process.  Plus a Cassandra
> database, an ActiveMQ instance, an instance of Eureka, and a MySQL server.
> And then the UI as well.  (I'm probably forgetting something.)  I can run
> all of this on my own computer, but it *is* very resource intensive.  It is
> for this reason that Ed would like to see us hosting an instance: some of
> the interns are programming against these APIs and they can't run all the
> services because they don't have the computational power necessary.
>
> But it is precisely for this reason, that this *can* be run on multiple
> VM's.  My understanding though is that projects only get one VM.  Is that
> wrong [~cml]?
>
> At the same time, it's fair to criticize this situation for this kind of
> install.  At Zingr, I was doing pair programming with [~leopoldjoy] to try
> to make it possible to deploy all of the services from one process.  That
> work got interrupted mid-May, and I don't know if Leo is still up for it.
> We can assume, one way or the other, that that work will not complete
> before the end of GSoC however.
>
> In the meantime, it might help to prioritize the services and not deploy
> all of them.  We might start with just:
> * Provisioner
> * IdentityManager
> * OrganizationManager
> * CustomerManager
> * LedgerManager
> * PortfolioManager
>
> If we can get that up and running, we should be able to decide from there
> whether we believe we can get the one-process solution working, whether
> multiple VMs is an option, or whether we wish to submit a request to the
> board for more resources.  I suggest we discuss that *on-list*.  (It would
> be so awesome if I could just @ a user right now and get this comment cc'ed
> to the dev list.)
>
> Best Regards,
> Myrle
>
> On Tue, Jun 19, 2018 at 2:15 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi Myrle,
>>
>> ... excellent... I'll try this out later today.
>>
>> Thanks again your help... will keep you posted.
>>
>> Cheers,
>>
>> Aleks
>>
>> On Mon, Jun 18, 2018 at 5:42 PM Myrle Krantz  wrote:
>>
>> > Hey Aleks,
>> >
>> > It looks like that exception is coming from Rhythm.  I suspect it's not
>> the
>> > cause of your difficulties, since you say your other services are going
>> > down too.  You can run most of the Fineract server without Rhythm.  You
>> > could edit the demo-server script to leave it out for the purposes of
>> > testing.  The consequence will be a lack of interest calculations for
>> > disbursed loans, but for finding out what the real problem is, it'd be
>> good
>> > to get this one out of the way.
>> >
>> > Best Regards,
>> > Myrle
>> >
>> > (FYI: I've removed the non-list subscribers from the to.  Most of them
>> are
>> > already subscribed, and those who aren't, don't want to be.)
>> >
>> > On Wed, Jun 13, 2018 at 1:40 AM Aleksandar Vidakovic <
>> > chee...@monkeysintown.com> wrote:
>> >
>> > > I managed to further improve the startup procedure (aka less
>> exceptions
>> > > than before)... there are still some timeouts, but not as many as
>> before.
>> > >
>> > >  The demo server still dies after this exception:
>> > >
>> > > 23:27:41.896 [AsyncResolver-bootstrap-executor-0] INFO
>> > > c.n.d.s.r.aws.ConfigClusterResolver - Resolving eureka endpoints via
>> > > configuration
>> > > 23:27:44.564 [AsyncResolver-bootstrap-executor-0] INFO
>> > > c.n.d.s.r.aws.ConfigClusterResolver - Resolving eureka endpoints via
>> > > configuration
>> > > 23:28:43.669 [AsyncResolver-bootstrap-executor-0] INFO
>> > > c.n.d.s.r.aws.ConfigClusterResolver - Resolving eureka endpoints via
>> > > configuration
>> > > 23:28:45.990 [pool-9-thread-1] ERROR
>> > o.s.s.s.TaskUtils$LoggingErrorHandler
>> > > - Unexpected error occurred in scheduled task.
>> > > org.springframework.transaction.CannotCreateTransactionException:
>> Could
>> > not
>> > > open JPA EntityManager for transaction; nested exception is
>> > > 

Re: Introducing Shruthi Rajaram, Mifos Community Engineer

[Edmore Tshuma]

 Shruthi Rajaram ,

Warm welcome..

Ed

On Fri, Jul 6, 2018 at 11:53 AM Pembe Miriam 
wrote:

> I am also excited to work with you Shruthi, Once more you are welcome
>
> On Thu, Jul 5, 2018 at 7:57 AM Shruthi M R <
> shru...@confluxtechnologies.com>
> wrote:
>
> > Thanks everyone for the warm welcome.
> >
> > I wish to take few moments to say hello and to introduce myself as a
> > newest member of the team.
> > I have been working as a Senior Software Engineer since March 2017 with
> > Conflux Technologies, which gave good insight of fineract. Prior to
> Conflux
> > I have worked with  Accenture for 3 + years.
> >
> > I am excited about the projects we will be working on together in the
> > future and will genuinely try to fulfill the responsibilities of the
> Mifos
> > Community Engineer.
> >
> > Sincerly,
> >
> > *Shruthi M R*
> >
> >
> > * shru...@confluxtechnologies.com
> >   | Skype: Shruthi Rajaram | Mobile:
> > +91-8277012716*
> >
> > On Wed, Jul 4, 2018 at 7:17 PM, Ed Cable  wrote:
> >
> >> Hello Mifos and Fineract communities,
> >>
> >> I wanted to formally introduce Shruthi Rajaram of Conflux Technologies
> >> who is just starting out her role as Mifos Community Engineer as of
> >> yesterday. You'll hopefully be seeing a lot of her on the lists as she's
> >> stepping into the role that Nazeer once filled in presiding over the
> >> community. I'll let her introduce herself and her background.
> >>
> >> The Mifos Initiative as fortunate enough to secure funding from DIAL
> >> through one of their catalytic grants to get the Dirty Jobs work done.
> Her
> >> role is made possible by this grant.
> >>
> >> As you've seen over the past several months, there have been delays in
> >> shipping releases, merging pull requests, fixing bugs, building new
> APIs.
> >> Having a dedicate person in this role will certainly help with these
> delays
> >> but I don't want it to reduce the pressure or remove the need for our
> >> committers and community at large to be helping with these vital duties
> >> because our aim is to help make the Fineract and Mifos communities
> >> self-functioning without intervention of funded dedicated developers.
> >>
> >> For the near immediate future, she'll be working on the APIs that our
> >> GSOC students need and getting the outstanding pull requests merged for
> >> Fineract 1.2.
> >>
> >> Her scope of focus across Fineract and Mifos will include:
> >>
> >>
> >>
> >> * - Review and merge pull requests from interns, partners, and
> volunteers
> >> in our community to the Apache Fineract platform- Review and merge pull
> >> requests from interns, partners, and volunteers in our community to the
> >> Mifos X web and mobile apps- Guide the QA process and release management
> >> process as part of the Apache Way to publicly release Apache Fineract-
> >> Prepare and package corresponding Mifos X web and mobile app releases
> that
> >> consume the stable Apache Fineract platform. - Triage incoming bug
> reports
> >> and feature requests. - Fix critical and show-stopping bugs and security
> >> vulnerabilities that arise and release them promptly as hot fixes.  -
> Fix
> >> outstanding P1 bugs and feature requests from our backlog that requires
> >> deep platform-level knowledge that volunteers can’t take on. - Develop
> new
> >> APIs, integrations, and minor features which are dependencies for other
> >> projects which will be developed upon by interns and volunteers.-
> >> Architectural Design and Technical Onboarding - as new external
> >> contributors come to the project, we need an expert on our platform to
> give
> >> them an initial technical onboarding and help them properly design new
> >> features they’d like to build - Dev Ops to maintain continuous
> integration
> >> servers and build pipelines to push merged code to our staging server
> and
> >> push stable releases to our demo servers. *Join in welcoming Shruthi to
> >> our communities!
> >>
> >> Cheers,
> >>
> >> *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 Shruthi Rajaram, Mifos Community Engineer

[Pembe Miriam]

I am also excited to work with you Shruthi, Once more you are welcome

On Thu, Jul 5, 2018 at 7:57 AM Shruthi M R 
wrote:

> Thanks everyone for the warm welcome.
>
> I wish to take few moments to say hello and to introduce myself as a
> newest member of the team.
> I have been working as a Senior Software Engineer since March 2017 with
> Conflux Technologies, which gave good insight of fineract. Prior to Conflux
> I have worked with  Accenture for 3 + years.
>
> I am excited about the projects we will be working on together in the
> future and will genuinely try to fulfill the responsibilities of the Mifos
> Community Engineer.
>
> Sincerly,
>
> *Shruthi M R*
>
>
> * shru...@confluxtechnologies.com
>   | Skype: Shruthi Rajaram | Mobile:
> +91-8277012716*
>
> On Wed, Jul 4, 2018 at 7:17 PM, Ed Cable  wrote:
>
>> Hello Mifos and Fineract communities,
>>
>> I wanted to formally introduce Shruthi Rajaram of Conflux Technologies
>> who is just starting out her role as Mifos Community Engineer as of
>> yesterday. You'll hopefully be seeing a lot of her on the lists as she's
>> stepping into the role that Nazeer once filled in presiding over the
>> community. I'll let her introduce herself and her background.
>>
>> The Mifos Initiative as fortunate enough to secure funding from DIAL
>> through one of their catalytic grants to get the Dirty Jobs work done. Her
>> role is made possible by this grant.
>>
>> As you've seen over the past several months, there have been delays in
>> shipping releases, merging pull requests, fixing bugs, building new APIs.
>> Having a dedicate person in this role will certainly help with these delays
>> but I don't want it to reduce the pressure or remove the need for our
>> committers and community at large to be helping with these vital duties
>> because our aim is to help make the Fineract and Mifos communities
>> self-functioning without intervention of funded dedicated developers.
>>
>> For the near immediate future, she'll be working on the APIs that our
>> GSOC students need and getting the outstanding pull requests merged for
>> Fineract 1.2.
>>
>> Her scope of focus across Fineract and Mifos will include:
>>
>>
>>
>> * - Review and merge pull requests from interns, partners, and volunteers
>> in our community to the Apache Fineract platform- Review and merge pull
>> requests from interns, partners, and volunteers in our community to the
>> Mifos X web and mobile apps- Guide the QA process and release management
>> process as part of the Apache Way to publicly release Apache Fineract-
>> Prepare and package corresponding Mifos X web and mobile app releases that
>> consume the stable Apache Fineract platform. - Triage incoming bug reports
>> and feature requests. - Fix critical and show-stopping bugs and security
>> vulnerabilities that arise and release them promptly as hot fixes.  - Fix
>> outstanding P1 bugs and feature requests from our backlog that requires
>> deep platform-level knowledge that volunteers can’t take on. - Develop new
>> APIs, integrations, and minor features which are dependencies for other
>> projects which will be developed upon by interns and volunteers.-
>> Architectural Design and Technical Onboarding - as new external
>> contributors come to the project, we need an expert on our platform to give
>> them an initial technical onboarding and help them properly design new
>> features they’d like to build - Dev Ops to maintain continuous integration
>> servers and build pipelines to push merged code to our staging server and
>> push stable releases to our demo servers. *Join in welcoming Shruthi to
>> our communities!
>>
>> Cheers,
>>
>> *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
>>   
>>
>>
>

HipChat for Fineract?

[Myrle Krantz]

Hey all,

As Shane pointed out to me, Apache has HipChat, and several projects
have rooms there:
https://apache.hipchat.com

Does anyone object to my requesting a room for Fineract?

Best Regards,
Myrle

Re: Confluence w Fineract-CN and Fineract

[Myrle Krantz]

Hey James,

As you've noted, Fineract CN already has it's own area.  Fineract 1.x
is doing a bit more manspreading, but given that it was there first,
that's understandable.  If Fineract CN content has strayed, that's
also normal when volunteers contribute things without fully
understanding the structure.  I could only find one such article
though, and that was in the user zone.  I don't have any objections to
you wrangling that one.

As I see it, top-level entries should be:
* Committer's Zone
* Contributor's Zone
* Project Management
* Release Management
* 1.x
* CN
* Requirements

That's nearly what we already have.

Best Regards,
Myrle
On Thu, Jul 5, 2018 at 8:48 PM James Dailey  wrote:
>
> Hi all -
>
> I believe a decision was taken to have both Fineract and the new
> Fineract-CN on the same confluence pages and on the same listserv.  Unless
> we can get a new Fineract-CN namespace on the apache confluence
> established, this means that we will have pages showing up in various
> places for Fineract-CN and discussions on this list also covering both code
> bases.
>
> My first suggestion - after watching the email traffic for a few months -
> is to include in emails and the documentation pages a tag of either
> [Fineract-1.x] or [Fineract-CN].   This may be best in the header or merely
> somewhere in the top of the message so that it is searchable.  This is
> already occurring in the ticketing on jira, right?
>
> My second suggestion is to restructure the pages on
> https://cwiki.apache.org/confluence/display/FINERACT.  I think we
> should create a structure where Fineract-1.x and Fineract-CN are top level
> entries and then all of the content follows as children of those. I'd be
> happy to try to work on that.  It means almost everything must be moved one
> level deeper, but I think that will help given that this is a rather large
> architectural departure.  That said, I know there are a few things that are
> shared at the top, i.e.
> https://cwiki.apache.org/confluence/display/FINERACT/Committer%27s+Zone and
> much of Contributor Zone.
>
> If we don't do this, then I believe we need to tag pages carefully and to
> have notes saying "this is Fineract-1.x or Fineract-CN" throughout.  Right
> now we have Fineract-CN entries showing up in various places on the pages
> and I suspect more will come as we develop that further.  To anticipate -
> yes, most of the content is under the page
> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+CN but not
> all, and in any case, having this be a secondary level where everything
> else is Fineract-1.x is confusing.
>
> Lastly, I do believe we should try to have the authoritative fineract and
> fineract-CN documentation be sufficient and complete, and therefore a place
> where others will link to.
>
> Thanks,
> James

Re: Fineract intro text proposed changes

[Myrle Krantz]

Hey James,

I made that change and several more.  I've pushed them as a separate branch.

All, have a look at
https://github.com/apache/fineract-site/tree/FINERACT-639  My first
changeset there is content-free.  It's just a reflow, with the
intention of making subsequent changes easier to see.  If there are no
objections by early next week, I'll merge that branch and it'll go
live.

Best Regards,
Myrle

On Wed, Jul 4, 2018 at 10:47 PM James Dailey  wrote:
>
> Hi Myrle
>
> Thanks.  Please make that minor change if that's ok w you.
>
> James
>
> On Wed, Jul 4, 2018, 7:58 AM Myrle Krantz  wrote:
>
> > Hey James,
> >
> > I saw your ICLA submission, and I love your changes.  I agree 100%
> > with your approach to the changes.  I also see you caught a bug and
> > fixed it: the link to the old incubating fineract repository.
> > Awesome!  Thank you.
> >
> > I need you to change one thing though before I can merge your changes:
> >  The mention of Mifos that you added stretches the boundaries of what
> > Apache projects are allowed to do in terms of crediting organizations
> > and companies which contribute to Apache projects.  "Fineract code was
> > originally developed by contributors to Mifos.org, a US-Based Charity
> > with a mission for financial inclusion globally."  What you write
> > there is true of the original code base, but it downplays the
> > contributions of individuals who've contributed since Fineract joined
> > Apache.  If you want to say a few words about the history of the
> > project, I would love to see that on a sub-page, but not on our main
> > page.
> >
> > Would you like me to fix that minor issue, or would you prefer to do
> > it yourself?
> >
> > Best Regards,
> > Myrle
> >
> > P.S.  I've created an issue for the changes, in case you prefer to
> > name your branch after Jira issues:
> > https://issues.apache.org/jira/browse/FINERACT-639
> >
> > On Fri, Jun 29, 2018 at 1:17 AM James Dailey 
> > wrote:
> > >
> > > Hi Myrle - Ok. Got my ICLA approved and proposed a PR via Github. my id
> > > there is jdailey.
> > > https://github.com/apache/fineract-site/pull/12
> > >
> > >
> > > On Tue, Jun 26, 2018 at 1:26 PM Myrle Krantz  wrote:
> > >
> > > > Hey James,
> > > >
> > > > it would be easier for me to see what you're actually changing if I
> > > > could see the diff.  Can you submit a PR containing your suggestions?
> > > > In case you need help, follow the following steps:
> > > >
> > > > 1.) Create a github account for yourself.
> > > > 2.) Fork the repository at https://github.com/apache/fineract-site
> > > > 3.) (Optionally clone it to your computer locally or just edit
> > > > directly on github.)
> > > > 4.) Edit index.html to contain your changes.
> > > > 5.) Submit a pull request (PR) via github.
> > > >
> > > > I know you don't have much experience developing, but because you're
> > > > asking for simple text changes, this is also possible for a
> > > > non-developer who's willing to "get his hands dirty".  If you have any
> > > > questions on the details of any of these steps, please ask.
> > > >
> > > > When you do this, anyone who is interested can review the PR, make
> > > > change suggestions directly via the same source code you submitted,
> > > > and finally merge the changes.  Once a PR is merged, it can take up to
> > > > 30 minutes for those changes to be reflected on the website.
> > > >
> > > > Also, no matter how the change suggestion is submitted or accepted,
> > > > you will need to submit an ICLA to the Apache Software Foundation
> > > > before any of your content can be accepted.  You can find that form
> > > > here:
> > > > https://www.apache.org/licenses/icla.pdf
> > > >
> > > > Best Regards,
> > > > Myrle
> > > > On Tue, Jun 26, 2018 at 9:10 PM Ed Cable  wrote:
> > > > >
> > > > > +1 from my side and I'm happy to make these changes to the website
> > text
> > > > > once agreed upon.
> > > > >
> > > > > Ed
> > > > >
> > > > > On Tue, Jun 26, 2018 at 12:04 PM James Dailey <
> > jamespdai...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi all -
> > > > > >
> > > > > > Fineract was contributed by Mifos.org which began life in the
> > world of
> > > > > > Microfinance, however has since then expanded to a broader concept
> > of
> > > > > > Financial Inclusion.  And, the concept behind contributing to
> > Apache
> > > > was to
> > > > > > broaden the appeal even more. That is, the fineract platform is
> > > > intended to
> > > > > > serve finTechs and any number of financial service providers.  I
> > > > believe
> > > > > > that it is important to have a landing page that aligns with that
> > > > vision,
> > > > > > gives people a way to see their projects fitting into fineract,
> > and I
> > > > think
> > > > > > that the current articulation might brand the project as
> > "microfinance
> > > > > > only".
> > > > > >
> > > > > > To that end, I think it would be useful to be more general-purpose
> > and
> > > > more
> > > > > > aspirational in our introductory