Page History

...

In general we ask that you take the time to read the instructions and familiarize yourself with the listserv before posting questions about building the solution.  You can search the listserv archives at https://lists.apache.org/list.html?fineract.apache.org .  If you find something missing from the instructions, we welcome contributions of that sort as well.    Note that the listserv search is timebound, so that for example this search gets 24 months: https://lists.apache.org/list.html?dev@fineract.apache.org:lte=24M:pentaho (see lte=24M) and search term is "pentaho". 

How do I get up to speed on development tasks? 

...

The project is always interested in ideas about features. That said, we notice some people expect that a feature requested is automatically developed and incorporated. That is not the case. If you have code to suggest, first discuss on the list, add an issue to the issue tracker, and then find someone to help you contribute that feature.  You are still not guaranteed that your feature will make it in, because it must also be accepted by the community. 

I have a great idea for a collaboration tool for the community, how do I make that happen?

We know there are lots of great collaboration tools.  To keep things consistent across Apache, there is a philosophy of using current tools rather than cutting edge, while acknowledging there's always something new and cool. We use email listservs for their backwards compatibility, searchability, and simplicity. This wiki has hooks to the Issue Tracking (JIRA) and github commit entries hook to the same JIRA tickets for all Pull Requests (PRs).  A good flow is:  

email discourse >> wiki entry |or| issue (JIRA)

development sprint >> Pull Request >> email list for review and confirmation 

I represent a Company and want to contribute, how do I do that? 

...

Security is a mandatory feature in Apache projects. Please report your bug to security AT fineract.apache.org. 

How do I raise a difficult or sensitive topic? 

In general, you are invited to discuss problems you see with the Fineract project openly, on the dev@fineract.apache.org list.  In some limited cases, please send an email to private@fineract.apache.org.  Addressing problems early and openly will keep most problems from becoming too large to handle. A good rule of thumb is to compose and then wait overnight before firing off that flame.