[ 
https://issues.apache.org/jira/browse/FINERACT-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206810#comment-17206810
 ] 

Francis Guchie edited comment on FINERACT-1125 at 10/3/20, 5:12 PM:
--------------------------------------------------------------------

[~vorburger]  and ALL, 

I have designed more then 30 Pentaho reports and still counting (*I have shared 
them in the Fineract community*), I cannot count the reports I have designed 
using crystal reports (by SAP). These are the only (2) reporting tools i have 
used. 
Pentaho 3.9.1 lacks a number of "nice to have" options. If we could plug into 
the latest versions then life would be great 

I have this to comment
 1- it is nice to have as many tools as possible these has downsides and upsides
 upside - we will get a few more contributors joining in (those who dont like 
moving from what they are used to)
 downside - with a limited number of enthusiastic and consistent contributors, 
we will only have a few passers-by looking to complete their projects and then 
they leave 
 This might leave us with too many reporting tools to look at / consider in 
every build  those left behind we be junks of all trade (too many tools to 
master)
 *(I am looking at it from a layman's point of view)*

2- I am of the view that if we can agree on a working reporting tool (or just 2 
max 3), use [~vorburger]'s approach then we can concentrate on those few. 
 if someone gave me a choice today, I would want to go back to the old 
reporting tool i used before but in the end this does not in any way as it 
kills the intentions of Fineract. 

With the amount of experience from all of you here (i see my self at the bottom 
of the list) we can help the community and decide which tool is easy to use and 
answers our challenge 

One crazy idea is to build a tool our selves ( i love dreaming)


was (Author: francisguchie):
[~vorburger]  and ALL, 

I have designed more then 30 Pentaho reports and still counting (*I have shared 
them in the Fineract community*), I cannot count the reports I have designed 
using crystal reports (by SAP). These are the 2 tools i have used. Pentaho 
3.9.1 lacks a number of "nice to have" options I enjoyed CR when I was with the 
"closed source" applications. 

I have this to comment
1- it is nice to have as many tools as possible these has downsides and upsides
upside - we will get a few more contributors joining in (those who dont like 
moving from what they are used to)
downside - with a limited number of enthusiastic and consistent contributors, 
we will only have a few passers-by looking to complete their projects and then 
they leave 
This might leave us with too many reporting tools to look at / consider in 
every build  those left behind we be junks of all trade (too many tools to 
master)
*(I am looking at it from a layman's point of view)*

2- I am of the view that if we can agree on a working reporting tool (or just 2 
max 3), use [~vorburger]'s approach then we can concentrate on those few. 
if someone gave me a choice today, I would want to go back to the old reporting 
tool i used before but in the end this does not in any way as it kills the 
intentions of Fineract. 

With the amount of experience from all of you here (i see my self at the bottom 
of the list) we can help the community and decide which tool is easy to use and 
answers our challenge 

One crazy idea is to build a tool our selves ( i love dreaming)

> Integrate Alternative Reporting tool for Fineract 1.x without Apache License 
> violations
> ---------------------------------------------------------------------------------------
>
>                 Key: FINERACT-1125
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1125
>             Project: Apache Fineract
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 1.4.0
>            Reporter: Francis Guchie
>            Priority: Major
>              Labels: hard
>
> read here [https://github.com/apache/fineract/pull/1262]
> and 
> [https://www.apache.org/legal/resolved.html#category-x]
> and 
> [https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License]
> We need a reporting support that will not have licensing violations
> for example the following 
> h1. BIRT
> [https://www.eclipse.org/birt/about/]  their license details are 
> [https://en.wikipedia.org/wiki/Eclipse_Public_License]
> h1. KNIME
> [|https://www.knime.com/downloads/full-license] 
> [https://www.knime.com/knime-report-designer 
> |https://www.knime.com/knime-report-designer]their licence details are 
> [https://www.knime.com/downloads/full-license] 
> h1. METABASE
> [https://www.metabase.com/] and their license is 
> [https://www.metabase.com/license/]
> h1. SEAL REPORT 
> [https://sealreport.org/] and their License is 
> [https://sealreport.org/#lineRequirements]
> [https://www.spagobi.org/] and their license is 
> [https://www.spagobi.org/communities/license/]



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

Reply via email to