[
https://issues.apache.org/jira/browse/FINERACT-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dailey updated FINERACT-2442:
-----------------------------------
Description:
*Note: GSOC applicants - this is a "draft concept". Do not work on your
proposal until we kick off the process at Fineract for evaluating. We may
significantly edit this concept or create new ones to replace it.*
*No one should work on this specific ticket unless assigned - the GSOC
candidate we choose will be assigned this ticket.*
*For more information, you should be reviewing emails on this subject and
following the Wiki pages.*
*[https://lists.apache.org/[email protected]]*
*[https://cwiki.apache.org/confluence/display/FINERACT/GSOC+Program+at+Fineract]*
h2.
*LOAN ORIGINATION CONTEXT*
Fineract has some loan origination functionality but it is not robust enough
for many operations. Several vendors, working with Fineract have created new
Loan Origination plug ins.
There is also a major enhancement underway that would build out a full Loan
Origination flow by supporting the backend needs of data storage for such LOS.
See ticket https://issues.apache.org/jira/browse/FINERACT-2418 .
The GSOC student would be expected to propose something as a POC (proof of
concept) that would either - use the developed Fienract backend solution, or
build a new component outside of Fineract to create the flows that would
demonstrate the LOS functionality.
That is, this is a moving target, and we would need different proposals from
prospective candidates to explore the area of Loan Origination. This may
require expertise in risk assessment, loan origination models and business
acumen. There will not be much more explanation that this available. The
student would be expected to be a self starter.
The mentor for this would need to be an expert at risk modeling, understand
Loan Origination, and support a conceptual basis that may involve some things
internal to Fineract and some processing elements outside of Fineract. Please
comment below if you are an existing Fineract contributor with this expertise.
To try to illustrate: one possible GSOC Proposal archtype we could accept
would be a survey of Loan Origination Models, their strengths and weaknesses
and to identify commonalities for the community to focus on. This would thus
be a Requirements exercise and may help identify future roadmap concepts. In
this case, the code to be developed may just expose a few APIs into different
screen flows. Thus, perhaps FIGMA flows (or similar) connecting to a set of
APIs on the backend.
If those new LOS APIs are existing in June 2026 (ticket 2418 resolved), then
those APIs are to be used. if they are NOT there in Fineract, then the student
would be requested to create a fork and to implement the POC outside of the
main Dev branch.
I welcome additions to this write up. [~jdailey]
was:
*Note: GSOC applicants - this is a "draft concept". Do not work on your
proposal until we kick off the process at Fineract for evaluating. We may
significantly edit this concept or create new ones to replace it.*
*No one should work on this specific ticket unless assigned - the GSOC
candidate we choose will be assigned this ticket.*
*For more information, you should be reviewing emails on this subject and
following the Wiki pages.*
*[https://lists.apache.org/[email protected]]*
*[https://cwiki.apache.org/confluence/display/FINERACT/GSOC+Program+at+Fineract]*
Fineract has some loan origination functionality but it is not robust enough
for many operations. Several vendors, working with Fineract have created new
Loan Origination plug ins.
There is also a major enhancement underway that would build out a full Loan
Origination flow by supporting the backend needs of data storage for such LOS.
See ticket https://issues.apache.org/jira/browse/FINERACT-2418 .
The GSOC student would be expected to propose something as a POC (proof of
concept) that would either - use the developed Fienract backend solution, or
build a new component outside of Fineract to create the flows that would
demonstrate the LOS functionality.
That is, this is a moving target, and we would need different proposals from
prospective candidates to explore the area of Loan Origination. This may
require expertise in risk assessment, loan origination models and business
acumen. There will not be much more explanation that this available. The
student would be expected to be a self starter.
The mentor for this would need to be an expert at risk modeling, understand
Loan Origination, and support a conceptual basis that may involve some things
internal to Fineract and some processing elements outside of Fineract. Please
comment below if you are an existing Fineract contributor with this expertise.
To try to illustrate: one possible GSOC Proposal archtype we could accept
would be a survey of Loan Origination Models, their strengths and weaknesses
and to identify commonalities for the community to focus on. This would thus
be a Requirements exercise and may help identify future roadmap concepts. In
this case, the code to be developed may just expose a few APIs into different
screen flows. Thus, perhaps FIGMA flows (or similar) connecting to a set of
APIs on the backend.
If those new LOS APIs are existing in June 2026 (ticket 2418 resolved), then
those APIs are to be used. if they are NOT there in Fineract, then the student
would be requested to create a fork and to implement the POC outside of the
main Dev branch.
I welcome additions to this write up. [~jdailey]
> Loan Origination POC
> --------------------
>
> Key: FINERACT-2442
> URL: https://issues.apache.org/jira/browse/FINERACT-2442
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: James Dailey
> Assignee: James Dailey
> Priority: Minor
> Labels: GSOC, gsoc2026, mentor
>
> *Note: GSOC applicants - this is a "draft concept". Do not work on your
> proposal until we kick off the process at Fineract for evaluating. We may
> significantly edit this concept or create new ones to replace it.*
> *No one should work on this specific ticket unless assigned - the GSOC
> candidate we choose will be assigned this ticket.*
> *For more information, you should be reviewing emails on this subject and
> following the Wiki pages.*
> *[https://lists.apache.org/[email protected]]*
> *[https://cwiki.apache.org/confluence/display/FINERACT/GSOC+Program+at+Fineract]*
>
> h2.
> *LOAN ORIGINATION CONTEXT*
> Fineract has some loan origination functionality but it is not robust enough
> for many operations. Several vendors, working with Fineract have created new
> Loan Origination plug ins.
> There is also a major enhancement underway that would build out a full Loan
> Origination flow by supporting the backend needs of data storage for such
> LOS. See ticket https://issues.apache.org/jira/browse/FINERACT-2418 .
> The GSOC student would be expected to propose something as a POC (proof of
> concept) that would either - use the developed Fienract backend solution, or
> build a new component outside of Fineract to create the flows that would
> demonstrate the LOS functionality.
> That is, this is a moving target, and we would need different proposals from
> prospective candidates to explore the area of Loan Origination. This may
> require expertise in risk assessment, loan origination models and business
> acumen. There will not be much more explanation that this available. The
> student would be expected to be a self starter.
> The mentor for this would need to be an expert at risk modeling, understand
> Loan Origination, and support a conceptual basis that may involve some things
> internal to Fineract and some processing elements outside of Fineract.
> Please comment below if you are an existing Fineract contributor with this
> expertise.
> To try to illustrate: one possible GSOC Proposal archtype we could accept
> would be a survey of Loan Origination Models, their strengths and weaknesses
> and to identify commonalities for the community to focus on. This would thus
> be a Requirements exercise and may help identify future roadmap concepts. In
> this case, the code to be developed may just expose a few APIs into different
> screen flows. Thus, perhaps FIGMA flows (or similar) connecting to a set of
> APIs on the backend.
> If those new LOS APIs are existing in June 2026 (ticket 2418 resolved), then
> those APIs are to be used. if they are NOT there in Fineract, then the
> student would be requested to create a fork and to implement the POC outside
> of the main Dev branch.
> I welcome additions to this write up. [~jdailey]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
