[jira] [Updated] (FINCN-352) Fineract Improvement Proposals

["Saransh Sharma (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FINCN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Saransh Sharma updated FINCN-352:
---------------------------------
    Description: 
Purpose 

The purpose of a Fineract CN Improvement Proposal (FIP) is to introduce any major change into Fineract CN. This is required in order to balance the need to support new features, uses cases , automation . Given the nature of the project that is micro services and its functional implications. To be able to bring changes in core libs and changes in the core services.

What is considered as major change?

Any of the following should be considered a major change:
 * Any major new feature, subsystem, or piece of functionality
 * Any change that removes the core lib
 * Design patterns changes that may take away the way project interact with respect to the services and db
 * Removal of services and core libs 
 * Adding a new type and frameworks 
 * Adding external service like automation and boilerplates 
 * Architectural changes overhaul like moving service or merging service in single piece

What should be included in the FIP
 * Motivation: describe the problem to be solved.
 * Proposed Change: describe the new thing you want to do. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences, depending on the scope of the change.
 * New or Changed Public Interfaces: impact to any of the "compatibility commitments" described above. We want to call these out in particular so everyone thinks about them.
 * New dependencies: describe any third-party libraries that the feature will require, from PyPI or NPM. In particular, make sure their license is compatible with the [Apache License v2.0] ([https://www.apache.org/licenses/LICENSE-2.0]).
 * Migration Plan and Compatibility: if this feature requires additional support for seamless upgrades describe how that will work. In particular, it’s important to mention if:
 ** The feature requires a change in some way to core libs
 ** Some API level change 
 ** Removing some lib or its generation
 ** The feature will coexist with similar functionality for some period of time, allowing for a deprecation period.
 * Rejected Alternatives: What are the other alternatives you considered and why are they worse? The goal of this section is to help people understand why this is the best solution now, and also to prevent churn in the future when old alternatives are reconsidered.

Who should initiate FIP

Anyone can initiate a FIP, but preferably someone with the intention of implementing it.

Process
 # [Create an issue|https://github.com/apache/incubator-superset/issues] with the prefix “[FIP]” in the title. The issue will be tagged as “fip” by a committer, and the title will be updated with the current SIP number.
 # Notify the {{dev@}} mailing list that the FIP has been created, use the subject line {{[DISCUSS] FIP-0 Fineract Improvement Proposals}}, the body of the email should look something like {{Please discuss & subscribe here: https://github.com/apache/fineract-CN-repo/issues/5602}}
 # When writing the issue, fill in the sections as described above in “What should be included in a FIP?”.
 # A committer will initiate the discussion, and ensure that there’s enough time to analyze the proposal. Before accepting the FIP, a committer should call for a vote, requiring 3 votes and no vetoes from committers. Votes are timebox at 1 week, and conducted through email (with the subject [VOTE]).
 # Create a pull request implementing the FIP, and referencing the issue.

 

 

 

 

  was:
Purpose 

The purpose of a Fineract CN Improvement Proposal (FIP) is to introduce any major change into Fineract CN. This is required in order to balance the need to support new features, uses cases , automation . Given the nature of the project that is micro services and its functional implications. To be able to bring changes in core libs and changes in the core services.

What is considered as major change?

Any of the following should be considered a major change:
 * Any major new feature, subsystem, or piece of functionality
 * Any change that removes the core lib
 * Design patterns changes that may take away the way project interact with respect to the services and db
 * Removal of services and core libs 
 * Adding a new type and frameworks 
 * Adding external service like automation and boilerplates 
 * Architectural changes overhaul like moving service or merging service in single piece.
 * 

 


> Fineract Improvement Proposals
> ------------------------------
>
>                 Key: FINCN-352
>                 URL: https://issues.apache.org/jira/browse/FINCN-352
>             Project: Fineract Cloud Native
>          Issue Type: Improvement
>            Reporter: Saransh Sharma
>            Priority: Major
>
> Purpose 
> The purpose of a Fineract CN Improvement Proposal (FIP) is to introduce any major change into Fineract CN. This is required in order to balance the need to support new features, uses cases , automation . Given the nature of the project that is micro services and its functional implications. To be able to bring changes in core libs and changes in the core services.
> What is considered as major change?
> Any of the following should be considered a major change:
>  * Any major new feature, subsystem, or piece of functionality
>  * Any change that removes the core lib
>  * Design patterns changes that may take away the way project interact with respect to the services and db
>  * Removal of services and core libs 
>  * Adding a new type and frameworks 
>  * Adding external service like automation and boilerplates 
>  * Architectural changes overhaul like moving service or merging service in single piece
> What should be included in the FIP
>  * Motivation: describe the problem to be solved.
>  * Proposed Change: describe the new thing you want to do. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences, depending on the scope of the change.
>  * New or Changed Public Interfaces: impact to any of the "compatibility commitments" described above. We want to call these out in particular so everyone thinks about them.
>  * New dependencies: describe any third-party libraries that the feature will require, from PyPI or NPM. In particular, make sure their license is compatible with the [Apache License v2.0] ([https://www.apache.org/licenses/LICENSE-2.0]).
>  * Migration Plan and Compatibility: if this feature requires additional support for seamless upgrades describe how that will work. In particular, it’s important to mention if:
>  ** The feature requires a change in some way to core libs
>  ** Some API level change 
>  ** Removing some lib or its generation
>  ** The feature will coexist with similar functionality for some period of time, allowing for a deprecation period.
>  * Rejected Alternatives: What are the other alternatives you considered and why are they worse? The goal of this section is to help people understand why this is the best solution now, and also to prevent churn in the future when old alternatives are reconsidered.
> Who should initiate FIP
> Anyone can initiate a FIP, but preferably someone with the intention of implementing it.
> Process
>  # [Create an issue|https://github.com/apache/incubator-superset/issues] with the prefix “[FIP]” in the title. The issue will be tagged as “fip” by a committer, and the title will be updated with the current SIP number.
>  # Notify the {{dev@}} mailing list that the FIP has been created, use the subject line {{[DISCUSS] FIP-0 Fineract Improvement Proposals}}, the body of the email should look something like {{Please discuss & subscribe here: https://github.com/apache/fineract-CN-repo/issues/5602}}
>  # When writing the issue, fill in the sections as described above in “What should be included in a FIP?”.
>  # A committer will initiate the discussion, and ensure that there’s enough time to analyze the proposal. Before accepting the FIP, a committer should call for a vote, requiring 3 votes and no vetoes from committers. Votes are timebox at 1 week, and conducted through email (with the subject [VOTE]).
>  # Create a pull request implementing the FIP, and referencing the issue.
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)