You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

This page is auto-generated! Please do NOT edit it, all changes will be lost on next update

APISIX

JSON Schema to Form UI for APISIX Dashboard

APISIX plugins ship JSON Schema definitions for their configuration. If APISIX Dashboard can render plugin configuration forms directly from JSON Schema, developer experience improves significantly and reduces manual UI maintenance.

        <p>Goals (Deliverables)<br/>
        Must-have:</p>
        <ul>
        	<li>A reusable <tt>SchemaForm</tt> (or equivalent) that renders basic types: string/number/integer/boolean/object/array.</li>
        	<li><tt>enum</tt> support (Select/Radio etc), defaults, required fields, basic constraints (min/max, pattern, etc) where
        feasible.</li>
        	<li>Support at least the key complex patterns used by APISIX plugin schemas:
        	<ul>
        		<li><tt>oneOf</tt> (select one option and render corresponding fields)</li>
        		<li><tt>dependencies</tt> / conditional fields</li>
        		<li>(Stretch) <tt>anyOf</tt> if present in target schemas</li>
        	</ul>
        	</li>
        	<li>Validation pipeline: validate form values against schema (AJV) and show errors in UI consistently.</li>
        	<li>Documentation + developer guide: how to add/extend schema-to-widget mapping.</li>
        	<li>Tests (unit + minimal integration) to prevent regressions for schema parsing and conditional rendering.</li>
        </ul>
        
     </div>
     <div class="actions" style="padding-left: 30px;">
        <div><strong>Difficulty:</strong> Major
        </div>
        <div><strong>Project size:</strong> ~350 hour (large)
        </div>
        <div>
           <div><strong>Potential mentors:</strong></div>
           <div style="padding-left: 30px;"><i>Yuan Bao</i>, mail: baoyuan (at) apache.org
              							
           </div>
           <div style="padding-left: 30px;"><i>Project Devs</i>, mail: dev (at) apisix.apache.org
           </div>
        </div>
     </div>
  </div>
  <h1 id="#GSoC2026Ideaslist-ApacheFineract">Apache Fineract</h1>
  <div class="item" style="padding: 10px;">
     <h3 id="#GSoC2026Ideaslist-CreateanewbackendforfrontendcomponentPOC" style="border-bottom: 1px solid #cccccc;"><a href="https://issues.apache.org/jira/browse/FINERACT-2439">Create a new backend for front end component POC</a></h3>
     <div class="desc" style="padding: 20px 0;"><h3><a name="BuildaSelfServiceAPIComponentthatConnectstoApacheFineract"></a><b>Build a Self-Service API Component that Connects
        to Apache Fineract</b></h3>
        
        <p>When the project removed self-service APIs in 2025, it did so understanding that we would need an outside component to
        make that connection as part of an overall solution. </p>
        
        <p>This project is to create - as a Proof of Concept (POC) - a new dedicated Self-Service API component or service that integration
        with Fineract backend.  It will need to expose APIs to consumer facing applications for typical activities like viewing account
        balances, transaction initiation, loan application, etc.  </p>
        
        <p>The idea is for GSOC candidates to propose a design and build the POC. </p>
        
        <p>Minimal criteria include testing, authentication methodology, documentation.  </p>
        
        <p>Not included in this GSOC would be the end consumer APP, although that may be undertaken by another project and coordination
        would be needed. </p>
     </div>
     <div class="actions" style="padding-left: 30px;">
        <div><strong>Difficulty:</strong> Minor
        </div>
        <div><strong>Project size:</strong> ~350 hour (large)
        </div>
        <div>
           <div><strong>Potential mentors:</strong></div>
           <div style="padding-left: 30px;"><i>James Dailey</i>, mail: jdailey (at) apache.org
              							
           </div>
           <div style="padding-left: 30px;"><i>Project Devs</i>, mail: dev (at) fineract.apache.org
           </div>
        </div>
     </div>
  </div>
  <div class="item" style="padding: 10px;">
     <h3 id="#GSoC2026Ideaslist-FrontendapplicationMVP(POC)" style="border-bottom: 1px solid #cccccc;"><a href="https://issues.apache.org/jira/browse/FINERACT-2440">Front end application MVP (POC)</a></h3>
     <div class="desc" style="padding: 20px 0;"><h3><a name="BuildasimpleselfservicefrontendthattalkstotheSelfServiceAPI"></a><b>Build a simple self-service front end that
        talks to the Self-Service API</b></h3>
        
        <p>We need a new, user-friendly front end app that connects to our Backend for Front end (<b>Self-Service API component)</b>
        This will be the “customer portal” experience where users can log in, see their accounts, and check recent activity. It should
        be straightforward, easy to use, and a good reference example for others to build on.  </p>
        
        <p>Functionality needed would include:  </p>
        <ul class="alternate" type="square">
        	<li>Login</li>
        	<li>Check balances</li>
        	<li>Transfer between accounts owned by the same customer.  </li>
        	<li>Submit application for a new loan </li>
        </ul>
        
        
        
        
        <p>Testing end to end required. <br/>
        Solid UI design <br/>
        Modern app framework <br/>
        Documentation </p>
     </div>
     <div class="actions" style="padding-left: 30px;">
        <div><strong>Difficulty:</strong> Minor
        </div>
        <div><strong>Project size:</strong> ~350 hour (large)
        </div>
        <div>
           <div><strong>Potential mentors:</strong></div>
           <div style="padding-left: 30px;"><i>James Dailey</i>, mail: jdailey (at) apache.org
              							
           </div>
           <div style="padding-left: 30px;"><i>Project Devs</i>, mail: dev (at) fineract.apache.org
           </div>
        </div>
     </div>
  </div>
  <div class="item" style="padding: 10px;">
     <h3 id="#GSoC2026Ideaslist-BIconnectoranddemonstration" style="border-bottom: 1px solid #cccccc;"><a href="https://issues.apache.org/jira/browse/FINERACT-2441">BI connector and demonstration</a></h3>
     <div class="desc" style="padding: 20px 0;"><p>The idea is to create a connector and a demonstration of analytics that would consume and organize data from Fineract.
         </p>
        
        <p>For example, create a way to pull data out of Fineract and make it easy to use in common analytics  such as Power BI or
        Tableau or, better yet, an open source variant.   The data should probably go to a Data Warehouse.  </p>
        
        <p>Start by proposing and exploring different options and write up the pros and cons.  </p>
        
        <p>Create a demonstration project that takes into account security, levels of access, and security of PII data if it exists. </p>
     </div>
     <div class="actions" style="padding-left: 30px;">
        <div><strong>Difficulty:</strong> Minor
        </div>
        <div><strong>Project size:</strong> ~350 hour (large)
        </div>
        <div>
           <div><strong>Potential mentors:</strong></div>
           <div style="padding-left: 30px;"><i>James Dailey</i>, mail: jdailey (at) apache.org
              							
           </div>
           <div style="padding-left: 30px;"><i>Project Devs</i>, mail: dev (at) fineract.apache.org
           </div>
        </div>
     </div>
  </div>
  <div class="item" style="padding: 10px;">
     <h3 id="#GSoC2026Ideaslist-LoanOriginationPOC" style="border-bottom: 1px solid #cccccc;"><a href="https://issues.apache.org/jira/browse/FINERACT-2442">Loan Origination POC</a></h3>
     <div class="desc" style="padding: 20px 0;"><p>Fineract has some loan origination functionality but it is not robust enough for many operations.   The POC would demonstrate
        the kind of functionality that could be built and/or help to demonstrate the full capabilities of the Fineract system.  </p>
        
        <p>Using data that is typically in a fineract installation, create a way to score risk and a more full featured loan origination
        process.  Propose and explore other sources of data and how to integrate in a flexible and extensible manner.  </p>
        
        <p>This needs further definition... </p>
        
        <p> </p>
     </div>
     <div class="actions" style="padding-left: 30px;">
        <div><strong>Difficulty:</strong> Minor
        </div>
        <div><strong>Project size:</strong> ~350 hour (large)
        </div>
        <div>
           <div><strong>Potential mentors:</strong></div>
           <div style="padding-left: 30px;"><i>James Dailey</i>, mail: jdailey (at) apache.org
              							
           </div>
           <div style="padding-left: 30px;"><i>Project Devs</i>, mail: dev (at) fineract.apache.org
           </div>
        </div>
     </div>
  </div>
  • No labels