You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Awasum Yannick <aw...@apache.org> on 2018/03/10 16:29:51 UTC
Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Hello Everyone,
I am hoping we could take some time to discuss and come up with approaches
for achieving full Apache compliance on the Fineract CN project.
I think there are still dependencies on Fineract CN which need some
attention in terms of checking the licenses and making sure they are
compliant with the Apache license.
To that end, I began looking at the Microservices and checking the license
of each dependency in accordance with this list:
https://www.apache.org/legal/resolved.html
Within the mariadb component, i realized that the
*mariadb-java-client* uses LGPL 2.1
(Is this compliant with the Apache license? ).
I don't know if there are other dependencies which are not Apache
compliant like the known case: Hibernate.
To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
the following:
* Replace the Hibernate Validator with something more Apache compliant like
javax.validation.*
or a corresponding OpenJPA library if such exists.
* Configure and set the LocalContainerEntityManagerFactoryBean ( within
MariaDBJavaConfiguratio
n )
to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
HibernateJpaVendorAdapter ) within mariadb component. And also the set the
right properties for OpenJPA ( peristence unit etc ).
I will like more experienced developers/architects in the community weigh
in and provide additional details which will enable the gradual migration
from Hibernate to OpenJPA and to get other non-compliant dependencies
migrated too. From this point, volunteers can pick this up and make
progress.
Thanks.
Awasum Yannick.
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Ed Cable <ed...@mifos.org>.
Hello everyone,
This is a critical topic that Yannick has raised and I want to elevate it
once again to the inboxes of our community and namely our committers so
they can weigh in.
Thanks,
Ed
On Mon, Mar 12, 2018 at 10:24 AM, Ed Cable <ed...@mifos.org> wrote:
> Thanks Yannick for initiating progress on this important topic and doing
> some initial analysis and giving some early recommendations. I'll try and
> get word out to some of the folks who worked on the previous Hibernate to
> OpenJPA migration as well.
>
> Ed
>
> On Sat, Mar 10, 2018 at 8:29 AM, Awasum Yannick <aw...@apache.org> wrote:
>
>> Hello Everyone,
>>
>> I am hoping we could take some time to discuss and come up with approaches
>> for achieving full Apache compliance on the Fineract CN project.
>> I think there are still dependencies on Fineract CN which need some
>> attention in terms of checking the licenses and making sure they are
>> compliant with the Apache license.
>>
>> To that end, I began looking at the Microservices and checking the license
>> of each dependency in accordance with this list:
>> https://www.apache.org/legal/resolved.html
>>
>> Within the mariadb component, i realized that the
>> *mariadb-java-client* uses LGPL 2.1
>> (Is this compliant with the Apache license? ).
>>
>> I don't know if there are other dependencies which are not Apache
>> compliant like the known case: Hibernate.
>>
>> To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
>> the following:
>>
>> * Replace the Hibernate Validator with something more Apache compliant
>> like
>> javax.validation.*
>> or a corresponding OpenJPA library if such exists.
>>
>> * Configure and set the LocalContainerEntityManagerFactoryBean ( within
>>
>> MariaDBJavaConfiguratio
>> n )
>>
>> to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
>> HibernateJpaVendorAdapter ) within mariadb component. And also the set
>> the
>> right properties for OpenJPA ( peristence unit etc ).
>>
>> I will like more experienced developers/architects in the community weigh
>> in and provide additional details which will enable the gradual migration
>> from Hibernate to OpenJPA and to get other non-compliant dependencies
>> migrated too. From this point, volunteers can pick this up and make
>> progress.
>>
>>
>> Thanks.
>> Awasum Yannick.
>>
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>
>
--
*Ed Cable*
President/CEO, Mifos Initiative
edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos> <http://www.twitter.com/mifos>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Ed Cable <ed...@mifos.org>.
Thanks Yannick for initiating progress on this important topic and doing
some initial analysis and giving some early recommendations. I'll try and
get word out to some of the folks who worked on the previous Hibernate to
OpenJPA migration as well.
Ed
On Sat, Mar 10, 2018 at 8:29 AM, Awasum Yannick <aw...@apache.org> wrote:
> Hello Everyone,
>
> I am hoping we could take some time to discuss and come up with approaches
> for achieving full Apache compliance on the Fineract CN project.
> I think there are still dependencies on Fineract CN which need some
> attention in terms of checking the licenses and making sure they are
> compliant with the Apache license.
>
> To that end, I began looking at the Microservices and checking the license
> of each dependency in accordance with this list:
> https://www.apache.org/legal/resolved.html
>
> Within the mariadb component, i realized that the
> *mariadb-java-client* uses LGPL 2.1
> (Is this compliant with the Apache license? ).
>
> I don't know if there are other dependencies which are not Apache
> compliant like the known case: Hibernate.
>
> To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
> the following:
>
> * Replace the Hibernate Validator with something more Apache compliant like
> javax.validation.*
> or a corresponding OpenJPA library if such exists.
>
> * Configure and set the LocalContainerEntityManagerFactoryBean ( within
>
> MariaDBJavaConfiguratio
> n )
>
> to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
> HibernateJpaVendorAdapter ) within mariadb component. And also the set the
> right properties for OpenJPA ( peristence unit etc ).
>
> I will like more experienced developers/architects in the community weigh
> in and provide additional details which will enable the gradual migration
> from Hibernate to OpenJPA and to get other non-compliant dependencies
> migrated too. From this point, volunteers can pick this up and make
> progress.
>
>
> Thanks.
> Awasum Yannick.
>
--
*Ed Cable*
President/CEO, Mifos Initiative
edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos> <http://www.twitter.com/mifos>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Myrle Krantz <my...@apache.org>.
+1.
Someone had contacted me offlist with a ...creative approach to
resolving this problem which would have been much easier. But that
approach won't come to fruition after all in our time frame.
My apologies for blocking on this. It seems clear in retrospect that
I shouldn't have.
Best Regards,
Myrle
On Wed, Oct 31, 2018 at 8:58 AM Isaac Kamga <is...@mifos.org> wrote:
>
> Hello everyone,
>
> I'm following up on this thread because we still haven't made progress with
> eliminating Category X dependencies in Fineract CN which Yannick evoked
> half a year ago.
>
> @Myrle and @Awasum, I've read through this thread and I second Sendoro's
> suggestion that we completely move Fineract CN's dependence on MariaDB to
> PosgreSQL instead. Besides MariaDB's license
> <https://mariadb.com/kb/en/library/licensing-faq/> being an inadmissible
> Category X dependency, PostgreSQL is Apache-compliant and is a good
> alternative for MariaDB.
>
> I think this will entail writing an equivalent library to
> fineract-cn-mariadb <https://github.com/apache/fineract-cn-mariadb> which
> we can name *fineract-cn-postgresql*. It may use the OpenJPA ORM which
> replaces Hibernate and use PostgreSQL's PgJDBC driver. I've started
> dabbling with this and will share the link to the code base tomorrow.
>
> I want to work on this task and share my thoughts, challenges and progress
> here with you too.
>
> What do you think about it ?
>
> Cheers,
> Isaac Kamga.
>
> On Wed, Apr 18, 2018 at 9:13 AM Myrle Krantz <my...@apache.org> wrote:
>
> > I think that's an excellent suggestion Sendoro. Would you like to
> > take the lead on that? I'd be happy to provide you with any help you
> > need to make it happen!
> >
> > Best Regards,
> > Myrle
> >
> > On Wed, Apr 18, 2018 at 9:47 AM, Sendoro Juma <se...@singo.africa>
> > wrote:
> > > Dear Myrle,
> > >
> > > It may be irrelevant, but let me shoot anyway...!!!... please don't
> > through stones onto me.
> > >
> > > PostgreSQL is believe to have very/most liberal license... as matter of
> > facts... it will avoid now and any future license conflict.
> > >
> > > The question is then, why don't we select PostgreSQL as our default DBMS?
> > >
> > > - is it related with our skill set? or
> > > - it is more just related to smooth transfer from MySQL to MariaDB?
> > >
> > > Taking into Finaract CN project take a revolution approach from its
> > predecessor Finaract; why also not take same approach on database?
> > > - after-all Fineract CN Architecture is decoupled from reliance on
> > particular database system...
> > >
> > >
> > > Refer
> > > https://www.postgresql.org/about/licence/
> > > https://www.postgresql.org/list/
> > > https://opensource.org/licenses/MIT
> > >
> > >
> > > Regards
> > > Sendoro
> > > ----- Original Message -----
> > > From: "Myrle Krantz" <my...@apache.org>
> > > To: "dev" <de...@fineract.apache.org>
> > > Sent: Wednesday, April 18, 2018 9:44:13 AM
> > > Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate
> > to OpenJPA Migration.
> > >
> > > Thank you Sendoro,
> > >
> > > It's much appreciated.
> > >
> > > FYI: I've captured the MariaDB work items in 2 new tickets:
> > > https://issues.apache.org/jira/browse/FINCN-26
> > > https://issues.apache.org/jira/browse/FINCN-27
> > >
> > > Best Regards,
> > > Myrle
> > >
> > > On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma <se...@singo.africa>
> > wrote:
> > >> Hello Myrle,
> > >>
> > >> I got you.
> > >>
> > >> Let me know if there is any other component need to be checked!
> > >>
> > >> Cheers
> > >> Sendoro
> >
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Sendoro Juma <se...@singo.africa>.
+1
As I believe PostgreSQL has been the more open source than their counter part at least....
>
> On October 31, 2018 at 10:57 AM Isaac Kamga <is...@mifos.org> wrote:
>
> Hello everyone,
>
> I'm following up on this thread because we still haven't made progress with
> eliminating Category X dependencies in Fineract CN which Yannick evoked
> half a year ago.
>
> @Myrle and @Awasum, I've read through this thread and I second Sendoro's
> suggestion that we completely move Fineract CN's dependence on MariaDB to
> PosgreSQL instead. Besides MariaDB's license
> <https://mariadb.com/kb/en/library/licensing-faq/> being an inadmissible
> Category X dependency, PostgreSQL is Apache-compliant and is a good
> alternative for MariaDB.
>
> I think this will entail writing an equivalent library to
> fineract-cn-mariadb <https://github.com/apache/fineract-cn-mariadb> which
> we can name *fineract-cn-postgresql*. It may use the OpenJPA ORM which
> replaces Hibernate and use PostgreSQL's PgJDBC driver. I've started
> dabbling with this and will share the link to the code base tomorrow.
>
> I want to work on this task and share my thoughts, challenges and progress
> here with you too.
>
> What do you think about it ?
>
> Cheers,
> Isaac Kamga.
>
> On Wed, Apr 18, 2018 at 9:13 AM Myrle Krantz <my...@apache.org> wrote:
>
> > >
> > I think that's an excellent suggestion Sendoro. Would you like to
> > take the lead on that? I'd be happy to provide you with any help you
> > need to make it happen!
> >
> > Best Regards,
> > Myrle
> >
> > On Wed, Apr 18, 2018 at 9:47 AM, Sendoro Juma <se...@singo.africa>
> > wrote:
> >
> > > > >
> > > Dear Myrle,
> > >
> > > It may be irrelevant, but let me shoot anyway...!!!... please don't
> > > through stones onto me.
> > >
> > > PostgreSQL is believe to have very/most liberal license... as matter of
> > > facts... it will avoid now and any future license conflict.
> > >
> > > The question is then, why don't we select PostgreSQL as our default DBMS?
> > >
> > > * is it related with our skill set? or
> > > * it is more just related to smooth transfer from MySQL to MariaDB?
> > >
> > > Taking into Finaract CN project take a revolution approach from its
> > > predecessor Finaract; why also not take same approach on database?
> > >
> > > * after-all Fineract CN Architecture is decoupled from reliance on
> > > particular database system...
> > >
> > > Refer
> > > https://www.postgresql.org/about/licence/
> > > https://www.postgresql.org/list/
> > > https://opensource.org/licenses/MIT
> > >
> > > Regards
> > > Sendoro
> > > ----- Original Message -----
> > > From: "Myrle Krantz" <my...@apache.org>
> > > To: "dev" <de...@fineract.apache.org>
> > > Sent: Wednesday, April 18, 2018 9:44:13 AM
> > > Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate
> > > to OpenJPA Migration.
> > >
> > > Thank you Sendoro,
> > >
> > > It's much appreciated.
> > >
> > > FYI: I've captured the MariaDB work items in 2 new tickets:
> > > https://issues.apache.org/jira/browse/FINCN-26
> > > https://issues.apache.org/jira/browse/FINCN-27
> > >
> > > Best Regards,
> > > Myrle
> > >
> > > On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma <se...@singo.africa>
> > > wrote:
> > >
> > > > > > >
> > > > Hello Myrle,
> > > >
> > > > I got you.
> > > >
> > > > Let me know if there is any other component need to be checked!
> > > >
> > > > Cheers
> > > > Sendoro
> > > >
> > > > > > >
> > > > >
> > >
With Best Regards
Sendoro Juma
-------------------------------
SingoAfrica Limited
Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
P.O BOX 78908 | 14121 Dar es Salaam
info@singo.africa mailto:info@singo.africa | +255 71 262 8896 | singo.africa https://singo.africa | amala.co.tz https://amala.co.tz
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Isaac Kamga <is...@mifos.org>.
Happy weekend fineracters,
I have created an issue for the MariaDB to PostgreSQL migration [1]
alongside 14 sub-tasks [2] so work continues in this regard.
I hope this helps.
[1] https://issues.apache.org/jira/browse/FINCN-113
[2] https://issues.apache.org/jira/browse/FINCN-14 to
https://issues.apache.org/jira/browse/FINCN-127
Cheers,
Isaac Kamga.
On Tue, Dec 11, 2018 at 2:59 AM Isaac Kamga <is...@mifos.org> wrote:
> Thanks for the clarification Markus and Myrle.
>
> On Mon, Dec 10, 2018 at 10:43 AM Myrle Krantz <my...@apache.org> wrote:
>
>> Hey Isaac,
>>
>> Hibernate validator was always Apache licensed. It's Hibernate JPA which
>> is the problem.
>>
>> Best Regards,
>> Myrle
>>
>> On Sat, Dec 8, 2018 at 1:55 AM Isaac Kamga <is...@mifos.org> wrote:
>>
>> > Happy weekend fineracters,
>> >
>> > It appears the hibernate-validator is Apache licensed as this link[1]
>> > shows ? Their license probably changed sometime this year.
>> > Is there any other hibernate tool which we used to develop Fineract CN ?
>> >
>> > Cheers,
>> > Isaac Kamga.
>> >
>> > [1]
>> >
>> https://github.com/hibernate/hibernate-validator/blob/master/license.txt
>> >
>> > On Tue, Nov 20, 2018 at 1:43 PM Sendoro Juma <se...@singo.africa>
>> wrote:
>> >
>> >> Indeed Hurray to you!!!
>> >>
>> >>
>> >> With Best Regards
>> >>
>> >> Sendoro
>> >>
>> >> On November 20, 2018 at 3:06 PM Isaac Kamga <is...@mifos.org>
>> >> wrote:
>> >>
>> >> Hurray !
>> >>
>> >> It took about a dozen hours for the created repo to show option "...or
>> >> push
>> >> existing repo from command line" on my end although it finally did.
>> >>
>> >> So the PostgreSQL repo is now on Apache Infrastructure
>> >> <https://github.com/apache/fineract-cn-postgresql> and work can
>> continue
>> >> on
>> >> there.
>> >>
>> >> On Tue, Nov 20, 2018 at 12:55 PM Isaac Kamga <is...@mifos.org>
>> >> wrote:
>> >>
>> >> Hello there,
>> >>
>> >> The INFRA team has created the repo
>> >> <https://github.com/apache/fineract-cn-postgresql> and I can't push
>> to it
>> >> because I don't have the right karma to do so.
>> >>
>> >> Can anyone on the PMC get the code
>> >> <https://github.com/Izakey/fineract-cn-postgresql> I've worked on and
>> >> push it to the newly created repository ?
>> >>
>> >> Cheers,
>> >> Isaac Kamga.
>> >>
>> >> On Mon, Nov 19, 2018 at 11:06 PM Isaac Kamga <is...@mifos.org>
>> >> wrote:
>> >>
>> >> Hello there,
>> >>
>> >> Thanks for your response Myrle.
>> >>
>> >> I tried creating a repo using these instructions
>> >> <
>> >>
>> https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN
>> >
>> >> and
>> >> hit an error, so I created an INFRA ticket
>> >> <https://issues.apache.org/jira/browse/INFRA-17273> to address it.
>> >>
>> >> In the meantime, if anyone is able to successfully create the ticket
>> >> using the details in the aforementioned ticket's description, it will
>> be a
>> >> step in the right direction.
>> >>
>> >> Cheers,
>> >> Isaac Kamga.
>> >>
>> >> On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz <my...@apache.org> wrote:
>> >>
>> >> Hey Isaac,
>> >>
>> >> Awesome Isaac. In general it's better to put stuff into Apache Infra
>> >> earlier rather than later. Things don't have to be finished. You're a
>> >> committer, so you have all the karma you need to create that repo. If
>> no
>> >> one else objects, then do it.
>> >>
>> >> : o),
>> >> Myrle
>> >>
>> >>
>> >>
>> >>
>> >> With Best Regards
>> >>
>> >> Sendoro Juma
>> >>
>> >> -------------------------------
>> >>
>> >> SingoAfrica Limited
>> >> Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
>> >>
>> >> P.O BOX 78908 | 14121 Dar es Salaam
>> >>
>> >> info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz
>> >>
>> >>
>> >>
>> >
>>
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Isaac Kamga <is...@mifos.org>.
Thanks for the clarification Markus and Myrle.
On Mon, Dec 10, 2018 at 10:43 AM Myrle Krantz <my...@apache.org> wrote:
> Hey Isaac,
>
> Hibernate validator was always Apache licensed. It's Hibernate JPA which
> is the problem.
>
> Best Regards,
> Myrle
>
> On Sat, Dec 8, 2018 at 1:55 AM Isaac Kamga <is...@mifos.org> wrote:
>
> > Happy weekend fineracters,
> >
> > It appears the hibernate-validator is Apache licensed as this link[1]
> > shows ? Their license probably changed sometime this year.
> > Is there any other hibernate tool which we used to develop Fineract CN ?
> >
> > Cheers,
> > Isaac Kamga.
> >
> > [1]
> > https://github.com/hibernate/hibernate-validator/blob/master/license.txt
> >
> > On Tue, Nov 20, 2018 at 1:43 PM Sendoro Juma <se...@singo.africa>
> wrote:
> >
> >> Indeed Hurray to you!!!
> >>
> >>
> >> With Best Regards
> >>
> >> Sendoro
> >>
> >> On November 20, 2018 at 3:06 PM Isaac Kamga <is...@mifos.org>
> >> wrote:
> >>
> >> Hurray !
> >>
> >> It took about a dozen hours for the created repo to show option "...or
> >> push
> >> existing repo from command line" on my end although it finally did.
> >>
> >> So the PostgreSQL repo is now on Apache Infrastructure
> >> <https://github.com/apache/fineract-cn-postgresql> and work can
> continue
> >> on
> >> there.
> >>
> >> On Tue, Nov 20, 2018 at 12:55 PM Isaac Kamga <is...@mifos.org>
> >> wrote:
> >>
> >> Hello there,
> >>
> >> The INFRA team has created the repo
> >> <https://github.com/apache/fineract-cn-postgresql> and I can't push to
> it
> >> because I don't have the right karma to do so.
> >>
> >> Can anyone on the PMC get the code
> >> <https://github.com/Izakey/fineract-cn-postgresql> I've worked on and
> >> push it to the newly created repository ?
> >>
> >> Cheers,
> >> Isaac Kamga.
> >>
> >> On Mon, Nov 19, 2018 at 11:06 PM Isaac Kamga <is...@mifos.org>
> >> wrote:
> >>
> >> Hello there,
> >>
> >> Thanks for your response Myrle.
> >>
> >> I tried creating a repo using these instructions
> >> <
> >>
> https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN
> >
> >> and
> >> hit an error, so I created an INFRA ticket
> >> <https://issues.apache.org/jira/browse/INFRA-17273> to address it.
> >>
> >> In the meantime, if anyone is able to successfully create the ticket
> >> using the details in the aforementioned ticket's description, it will
> be a
> >> step in the right direction.
> >>
> >> Cheers,
> >> Isaac Kamga.
> >>
> >> On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz <my...@apache.org> wrote:
> >>
> >> Hey Isaac,
> >>
> >> Awesome Isaac. In general it's better to put stuff into Apache Infra
> >> earlier rather than later. Things don't have to be finished. You're a
> >> committer, so you have all the karma you need to create that repo. If no
> >> one else objects, then do it.
> >>
> >> : o),
> >> Myrle
> >>
> >>
> >>
> >>
> >> With Best Regards
> >>
> >> Sendoro Juma
> >>
> >> -------------------------------
> >>
> >> SingoAfrica Limited
> >> Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
> >>
> >> P.O BOX 78908 | 14121 Dar es Salaam
> >>
> >> info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz
> >>
> >>
> >>
> >
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Myrle Krantz <my...@apache.org>.
Hey Isaac,
Hibernate validator was always Apache licensed. It's Hibernate JPA which
is the problem.
Best Regards,
Myrle
On Sat, Dec 8, 2018 at 1:55 AM Isaac Kamga <is...@mifos.org> wrote:
> Happy weekend fineracters,
>
> It appears the hibernate-validator is Apache licensed as this link[1]
> shows ? Their license probably changed sometime this year.
> Is there any other hibernate tool which we used to develop Fineract CN ?
>
> Cheers,
> Isaac Kamga.
>
> [1]
> https://github.com/hibernate/hibernate-validator/blob/master/license.txt
>
> On Tue, Nov 20, 2018 at 1:43 PM Sendoro Juma <se...@singo.africa> wrote:
>
>> Indeed Hurray to you!!!
>>
>>
>> With Best Regards
>>
>> Sendoro
>>
>> On November 20, 2018 at 3:06 PM Isaac Kamga <is...@mifos.org>
>> wrote:
>>
>> Hurray !
>>
>> It took about a dozen hours for the created repo to show option "...or
>> push
>> existing repo from command line" on my end although it finally did.
>>
>> So the PostgreSQL repo is now on Apache Infrastructure
>> <https://github.com/apache/fineract-cn-postgresql> and work can continue
>> on
>> there.
>>
>> On Tue, Nov 20, 2018 at 12:55 PM Isaac Kamga <is...@mifos.org>
>> wrote:
>>
>> Hello there,
>>
>> The INFRA team has created the repo
>> <https://github.com/apache/fineract-cn-postgresql> and I can't push to it
>> because I don't have the right karma to do so.
>>
>> Can anyone on the PMC get the code
>> <https://github.com/Izakey/fineract-cn-postgresql> I've worked on and
>> push it to the newly created repository ?
>>
>> Cheers,
>> Isaac Kamga.
>>
>> On Mon, Nov 19, 2018 at 11:06 PM Isaac Kamga <is...@mifos.org>
>> wrote:
>>
>> Hello there,
>>
>> Thanks for your response Myrle.
>>
>> I tried creating a repo using these instructions
>> <
>> https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN>
>> and
>> hit an error, so I created an INFRA ticket
>> <https://issues.apache.org/jira/browse/INFRA-17273> to address it.
>>
>> In the meantime, if anyone is able to successfully create the ticket
>> using the details in the aforementioned ticket's description, it will be a
>> step in the right direction.
>>
>> Cheers,
>> Isaac Kamga.
>>
>> On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz <my...@apache.org> wrote:
>>
>> Hey Isaac,
>>
>> Awesome Isaac. In general it's better to put stuff into Apache Infra
>> earlier rather than later. Things don't have to be finished. You're a
>> committer, so you have all the karma you need to create that repo. If no
>> one else objects, then do it.
>>
>> : o),
>> Myrle
>>
>>
>>
>>
>> With Best Regards
>>
>> Sendoro Juma
>>
>> -------------------------------
>>
>> SingoAfrica Limited
>> Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
>>
>> P.O BOX 78908 | 14121 Dar es Salaam
>>
>> info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz
>>
>>
>>
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Markus Geiss <ma...@apache.org>.
Hey Isaac,
the maridb core component is using Hibernate as the JPA provider, that's it.
Given Hibernate ORM is not compliant this needs to be adjusted.
Cheers
Markus
On Sat, Dec 8, 2018, 01:55 Isaac Kamga <isaac.kamga@mifos.org wrote:
> Happy weekend fineracters,
>
> It appears the hibernate-validator is Apache licensed as this link[1]
> shows ? Their license probably changed sometime this year.
> Is there any other hibernate tool which we used to develop Fineract CN ?
>
> Cheers,
> Isaac Kamga.
>
> [1]
> https://github.com/hibernate/hibernate-validator/blob/master/license.txt
>
> On Tue, Nov 20, 2018 at 1:43 PM Sendoro Juma <se...@singo.africa> wrote:
>
>> Indeed Hurray to you!!!
>>
>>
>> With Best Regards
>>
>> Sendoro
>>
>> On November 20, 2018 at 3:06 PM Isaac Kamga <is...@mifos.org>
>> wrote:
>>
>> Hurray !
>>
>> It took about a dozen hours for the created repo to show option "...or
>> push
>> existing repo from command line" on my end although it finally did.
>>
>> So the PostgreSQL repo is now on Apache Infrastructure
>> <https://github.com/apache/fineract-cn-postgresql> and work can continue
>> on
>> there.
>>
>> On Tue, Nov 20, 2018 at 12:55 PM Isaac Kamga <is...@mifos.org>
>> wrote:
>>
>> Hello there,
>>
>> The INFRA team has created the repo
>> <https://github.com/apache/fineract-cn-postgresql> and I can't push to it
>> because I don't have the right karma to do so.
>>
>> Can anyone on the PMC get the code
>> <https://github.com/Izakey/fineract-cn-postgresql> I've worked on and
>> push it to the newly created repository ?
>>
>> Cheers,
>> Isaac Kamga.
>>
>> On Mon, Nov 19, 2018 at 11:06 PM Isaac Kamga <is...@mifos.org>
>> wrote:
>>
>> Hello there,
>>
>> Thanks for your response Myrle.
>>
>> I tried creating a repo using these instructions
>> <
>> https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN>
>> and
>> hit an error, so I created an INFRA ticket
>> <https://issues.apache.org/jira/browse/INFRA-17273> to address it.
>>
>> In the meantime, if anyone is able to successfully create the ticket
>> using the details in the aforementioned ticket's description, it will be a
>> step in the right direction.
>>
>> Cheers,
>> Isaac Kamga.
>>
>> On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz <my...@apache.org> wrote:
>>
>> Hey Isaac,
>>
>> Awesome Isaac. In general it's better to put stuff into Apache Infra
>> earlier rather than later. Things don't have to be finished. You're a
>> committer, so you have all the karma you need to create that repo. If no
>> one else objects, then do it.
>>
>> : o),
>> Myrle
>>
>>
>>
>>
>> With Best Regards
>>
>> Sendoro Juma
>>
>> -------------------------------
>>
>> SingoAfrica Limited
>> Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
>>
>> P.O BOX 78908 | 14121 Dar es Salaam
>>
>> info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz
>>
>>
>>
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Isaac Kamga <is...@mifos.org>.
Happy weekend fineracters,
It appears the hibernate-validator is Apache licensed as this link[1] shows
? Their license probably changed sometime this year.
Is there any other hibernate tool which we used to develop Fineract CN ?
Cheers,
Isaac Kamga.
[1] https://github.com/hibernate/hibernate-validator/blob/master/license.txt
On Tue, Nov 20, 2018 at 1:43 PM Sendoro Juma <se...@singo.africa> wrote:
> Indeed Hurray to you!!!
>
>
> With Best Regards
>
> Sendoro
>
> On November 20, 2018 at 3:06 PM Isaac Kamga <is...@mifos.org> wrote:
>
> Hurray !
>
> It took about a dozen hours for the created repo to show option "...or push
> existing repo from command line" on my end although it finally did.
>
> So the PostgreSQL repo is now on Apache Infrastructure
> <https://github.com/apache/fineract-cn-postgresql> and work can continue
> on
> there.
>
> On Tue, Nov 20, 2018 at 12:55 PM Isaac Kamga <is...@mifos.org>
> wrote:
>
> Hello there,
>
> The INFRA team has created the repo
> <https://github.com/apache/fineract-cn-postgresql> and I can't push to it
> because I don't have the right karma to do so.
>
> Can anyone on the PMC get the code
> <https://github.com/Izakey/fineract-cn-postgresql> I've worked on and
> push it to the newly created repository ?
>
> Cheers,
> Isaac Kamga.
>
> On Mon, Nov 19, 2018 at 11:06 PM Isaac Kamga <is...@mifos.org>
> wrote:
>
> Hello there,
>
> Thanks for your response Myrle.
>
> I tried creating a repo using these instructions
> <
> https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN>
> and
> hit an error, so I created an INFRA ticket
> <https://issues.apache.org/jira/browse/INFRA-17273> to address it.
>
> In the meantime, if anyone is able to successfully create the ticket
> using the details in the aforementioned ticket's description, it will be a
> step in the right direction.
>
> Cheers,
> Isaac Kamga.
>
> On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz <my...@apache.org> wrote:
>
> Hey Isaac,
>
> Awesome Isaac. In general it's better to put stuff into Apache Infra
> earlier rather than later. Things don't have to be finished. You're a
> committer, so you have all the karma you need to create that repo. If no
> one else objects, then do it.
>
> : o),
> Myrle
>
>
>
>
> With Best Regards
>
> Sendoro Juma
>
> -------------------------------
>
> SingoAfrica Limited
> Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
>
> P.O BOX 78908 | 14121 Dar es Salaam
>
> info@singo.africa | +255 71 262 8896 | singo.africa | amala.co.tz
>
>
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Sendoro Juma <se...@singo.africa>.
Indeed Hurray to you!!!
With Best Regards
Sendoro
>
> On November 20, 2018 at 3:06 PM Isaac Kamga <is...@mifos.org> wrote:
>
> Hurray !
>
> It took about a dozen hours for the created repo to show option "...or push
> existing repo from command line" on my end although it finally did.
>
> So the PostgreSQL repo is now on Apache Infrastructure
> <https://github.com/apache/fineract-cn-postgresql> and work can continue on
> there.
>
> On Tue, Nov 20, 2018 at 12:55 PM Isaac Kamga <is...@mifos.org> wrote:
>
> > >
> > Hello there,
> >
> > The INFRA team has created the repo
> > <https://github.com/apache/fineract-cn-postgresql> and I can't push to it
> > because I don't have the right karma to do so.
> >
> > Can anyone on the PMC get the code
> > <https://github.com/Izakey/fineract-cn-postgresql> I've worked on and
> > push it to the newly created repository ?
> >
> > Cheers,
> > Isaac Kamga.
> >
> > On Mon, Nov 19, 2018 at 11:06 PM Isaac Kamga <is...@mifos.org>
> > wrote:
> >
> > > > >
> > > Hello there,
> > >
> > > Thanks for your response Myrle.
> > >
> > > I tried creating a repo using these instructions
> > > <https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN> and
> > > hit an error, so I created an INFRA ticket
> > > <https://issues.apache.org/jira/browse/INFRA-17273> to address it.
> > >
> > > In the meantime, if anyone is able to successfully create the ticket
> > > using the details in the aforementioned ticket's description, it will be a
> > > step in the right direction.
> > >
> > > Cheers,
> > > Isaac Kamga.
> > >
> > > On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz <my...@apache.org> wrote:
> > >
> > > > > > >
> > > > Hey Isaac,
> > > >
> > > > Awesome Isaac. In general it's better to put stuff into Apache Infra
> > > > earlier rather than later. Things don't have to be finished. You're a
> > > > committer, so you have all the karma you need to create that repo. If no
> > > > one else objects, then do it.
> > > >
> > > > : o),
> > > > Myrle
> > > >
> > > > > > >
> > > > >
> > >
With Best Regards
Sendoro Juma
-------------------------------
SingoAfrica Limited
Mbezi Beach | Bagamoyo Road | 7 Nakawale Str.
P.O BOX 78908 | 14121 Dar es Salaam
info@singo.africa mailto:info@singo.africa | +255 71 262 8896 | singo.africa https://singo.africa | amala.co.tz https://amala.co.tz
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Isaac Kamga <is...@mifos.org>.
Hurray !
It took about a dozen hours for the created repo to show option "...or push
existing repo from command line" on my end although it finally did.
So the PostgreSQL repo is now on Apache Infrastructure
<https://github.com/apache/fineract-cn-postgresql> and work can continue on
there.
On Tue, Nov 20, 2018 at 12:55 PM Isaac Kamga <is...@mifos.org> wrote:
> Hello there,
>
> The INFRA team has created the repo
> <https://github.com/apache/fineract-cn-postgresql> and I can't push to it
> because I don't have the right karma to do so.
>
> Can anyone on the PMC get the code
> <https://github.com/Izakey/fineract-cn-postgresql> I've worked on and
> push it to the newly created repository ?
>
> Cheers,
> Isaac Kamga.
>
> On Mon, Nov 19, 2018 at 11:06 PM Isaac Kamga <is...@mifos.org>
> wrote:
>
>> Hello there,
>>
>> Thanks for your response Myrle.
>>
>> I tried creating a repo using these instructions
>> <https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN> and
>> hit an error, so I created an INFRA ticket
>> <https://issues.apache.org/jira/browse/INFRA-17273> to address it.
>>
>> In the meantime, if anyone is able to successfully create the ticket
>> using the details in the aforementioned ticket's description, it will be a
>> step in the right direction.
>>
>> Cheers,
>> Isaac Kamga.
>>
>> On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz <my...@apache.org> wrote:
>>
>>> Hey Isaac,
>>>
>>> Awesome Isaac. In general it's better to put stuff into Apache Infra
>>> earlier rather than later. Things don't have to be finished. You're a
>>> committer, so you have all the karma you need to create that repo. If no
>>> one else objects, then do it.
>>>
>>> : o),
>>> Myrle
>>>
>>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Isaac Kamga <is...@mifos.org>.
Hello there,
The INFRA team has created the repo
<https://github.com/apache/fineract-cn-postgresql> and I can't push to it
because I don't have the right karma to do so.
Can anyone on the PMC get the code
<https://github.com/Izakey/fineract-cn-postgresql> I've worked on and push
it to the newly created repository ?
Cheers,
Isaac Kamga.
On Mon, Nov 19, 2018 at 11:06 PM Isaac Kamga <is...@mifos.org> wrote:
> Hello there,
>
> Thanks for your response Myrle.
>
> I tried creating a repo using these instructions
> <https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN> and
> hit an error, so I created an INFRA ticket
> <https://issues.apache.org/jira/browse/INFRA-17273> to address it.
>
> In the meantime, if anyone is able to successfully create the ticket using
> the details in the aforementioned ticket's description, it will be a
> step in the right direction.
>
> Cheers,
> Isaac Kamga.
>
> On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz <my...@apache.org> wrote:
>
>> Hey Isaac,
>>
>> Awesome Isaac. In general it's better to put stuff into Apache Infra
>> earlier rather than later. Things don't have to be finished. You're a
>> committer, so you have all the karma you need to create that repo. If no
>> one else objects, then do it.
>>
>> : o),
>> Myrle
>>
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Isaac Kamga <is...@mifos.org>.
Hello there,
Thanks for your response Myrle.
I tried creating a repo using these instructions
<https://cwiki.apache.org/confluence/display/FINERACT/Working+with+gitbox+to+contribute+to+Apache+Fineract+CN>
and
hit an error, so I created an INFRA ticket
<https://issues.apache.org/jira/browse/INFRA-17273> to address it.
In the meantime, if anyone is able to successfully create the ticket using
the details in the aforementioned ticket's description, it will be a
step in the right direction.
Cheers,
Isaac Kamga.
On Sun, Nov 18, 2018 at 1:59 PM Myrle Krantz <my...@apache.org> wrote:
> Hey Isaac,
>
> Awesome Isaac. In general it's better to put stuff into Apache Infra
> earlier rather than later. Things don't have to be finished. You're a
> committer, so you have all the karma you need to create that repo. If no
> one else objects, then do it.
>
> : o),
> Myrle
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Myrle Krantz <my...@apache.org>.
Hey Isaac,
Awesome Isaac. In general it's better to put stuff into Apache Infra
earlier rather than later. Things don't have to be finished. You're a
committer, so you have all the karma you need to create that repo. If no
one else objects, then do it.
: o),
Myrle
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Isaac Kamga <is...@mifos.org>.
Thanks for the support Myrle, Sendoro and Awasum.
I just created a corresponding issue
<https://issues.apache.org/jira/browse/FINCN-103> and have pushed the work
done on the PostgreSQL core component to this repository
<https://github.com/Izakey/fineract-cn-postgresql>.
PostgreSQL came along with it's PgJDBC driver, its default port number
being *5432*, default database instance being *postgres* and default host
being *localhost*. The HibernateJpaVendorAdapter was replaced with
OpenJpaVendorAdapter and the Hibernate dialect for MySQL was replaced with
the OpenJPA dictionary for PostgreSQL. I'm still unclear about whether
users need to employ a specific password as was done with MySQL given that
best practice says it shouldn't be so. For now, developers would have to
ensure they're logged into their *postgres* account for connection to
databases to work.
These are just the basics and I'm uncear about the specific workings of
BoneCP with PostgreSQL. Maybe the constants used have to be modified.
@Markus, @Myrle, @Awasum, Please I await your feedback on what needs to be
improved upon here.
@Myrle, if you think it's time to transfer this repository
<https://github.com/Izakey/fineract-cn-postgresql> to Apache infra,
please let me know.
At Your Service,
Isaac Kamga.
On Sat, Nov 3, 2018 at 11:14 PM Awasum Yannick <aw...@apache.org> wrote:
> Brilliant Idea, Isaac.
>
> Maybe it will be a good idea to create an issue on JIRA for this.
>
> On Wed, Oct 31, 2018 at 8:58 AM Isaac Kamga <is...@mifos.org> wrote:
>
> > Hello everyone,
> >
> > I'm following up on this thread because we still haven't made progress
> with
> > eliminating Category X dependencies in Fineract CN which Yannick evoked
> > half a year ago.
> >
> > @Myrle and @Awasum, I've read through this thread and I second Sendoro's
> > suggestion that we completely move Fineract CN's dependence on MariaDB to
> > PosgreSQL instead. Besides MariaDB's license
> > <https://mariadb.com/kb/en/library/licensing-faq/> being an inadmissible
> > Category X dependency, PostgreSQL is Apache-compliant and is a good
> > alternative for MariaDB.
> >
> > I think this will entail writing an equivalent library to
> > fineract-cn-mariadb <https://github.com/apache/fineract-cn-mariadb>
> which
> > we can name *fineract-cn-postgresql*. It may use the OpenJPA ORM which
> > replaces Hibernate and use PostgreSQL's PgJDBC driver. I've started
> > dabbling with this and will share the link to the code base tomorrow.
> >
> > I want to work on this task and share my thoughts, challenges and
> progress
> > here with you too.
> >
> > What do you think about it ?
> >
> > Cheers,
> > Isaac Kamga.
> >
> > On Wed, Apr 18, 2018 at 9:13 AM Myrle Krantz <my...@apache.org> wrote:
> >
> > > I think that's an excellent suggestion Sendoro. Would you like to
> > > take the lead on that? I'd be happy to provide you with any help you
> > > need to make it happen!
> > >
> > > Best Regards,
> > > Myrle
> > >
> > > On Wed, Apr 18, 2018 at 9:47 AM, Sendoro Juma <se...@singo.africa>
> > > wrote:
> > > > Dear Myrle,
> > > >
> > > > It may be irrelevant, but let me shoot anyway...!!!... please don't
> > > through stones onto me.
> > > >
> > > > PostgreSQL is believe to have very/most liberal license... as matter
> of
> > > facts... it will avoid now and any future license conflict.
> > > >
> > > > The question is then, why don't we select PostgreSQL as our default
> > DBMS?
> > > >
> > > > - is it related with our skill set? or
> > > > - it is more just related to smooth transfer from MySQL to MariaDB?
> > > >
> > > > Taking into Finaract CN project take a revolution approach from its
> > > predecessor Finaract; why also not take same approach on database?
> > > > - after-all Fineract CN Architecture is decoupled from reliance on
> > > particular database system...
> > > >
> > > >
> > > > Refer
> > > > https://www.postgresql.org/about/licence/
> > > > https://www.postgresql.org/list/
> > > > https://opensource.org/licenses/MIT
> > > >
> > > >
> > > > Regards
> > > > Sendoro
> > > > ----- Original Message -----
> > > > From: "Myrle Krantz" <my...@apache.org>
> > > > To: "dev" <de...@fineract.apache.org>
> > > > Sent: Wednesday, April 18, 2018 9:44:13 AM
> > > > Subject: Re: Moving Towards Apache Compliance for Fineract CN:
> > Hibernate
> > > to OpenJPA Migration.
> > > >
> > > > Thank you Sendoro,
> > > >
> > > > It's much appreciated.
> > > >
> > > > FYI: I've captured the MariaDB work items in 2 new tickets:
> > > > https://issues.apache.org/jira/browse/FINCN-26
> > > > https://issues.apache.org/jira/browse/FINCN-27
> > > >
> > > > Best Regards,
> > > > Myrle
> > > >
> > > > On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma <se...@singo.africa>
> > > wrote:
> > > >> Hello Myrle,
> > > >>
> > > >> I got you.
> > > >>
> > > >> Let me know if there is any other component need to be checked!
> > > >>
> > > >> Cheers
> > > >> Sendoro
> > >
> >
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Awasum Yannick <aw...@apache.org>.
Brilliant Idea, Isaac.
Maybe it will be a good idea to create an issue on JIRA for this.
On Wed, Oct 31, 2018 at 8:58 AM Isaac Kamga <is...@mifos.org> wrote:
> Hello everyone,
>
> I'm following up on this thread because we still haven't made progress with
> eliminating Category X dependencies in Fineract CN which Yannick evoked
> half a year ago.
>
> @Myrle and @Awasum, I've read through this thread and I second Sendoro's
> suggestion that we completely move Fineract CN's dependence on MariaDB to
> PosgreSQL instead. Besides MariaDB's license
> <https://mariadb.com/kb/en/library/licensing-faq/> being an inadmissible
> Category X dependency, PostgreSQL is Apache-compliant and is a good
> alternative for MariaDB.
>
> I think this will entail writing an equivalent library to
> fineract-cn-mariadb <https://github.com/apache/fineract-cn-mariadb> which
> we can name *fineract-cn-postgresql*. It may use the OpenJPA ORM which
> replaces Hibernate and use PostgreSQL's PgJDBC driver. I've started
> dabbling with this and will share the link to the code base tomorrow.
>
> I want to work on this task and share my thoughts, challenges and progress
> here with you too.
>
> What do you think about it ?
>
> Cheers,
> Isaac Kamga.
>
> On Wed, Apr 18, 2018 at 9:13 AM Myrle Krantz <my...@apache.org> wrote:
>
> > I think that's an excellent suggestion Sendoro. Would you like to
> > take the lead on that? I'd be happy to provide you with any help you
> > need to make it happen!
> >
> > Best Regards,
> > Myrle
> >
> > On Wed, Apr 18, 2018 at 9:47 AM, Sendoro Juma <se...@singo.africa>
> > wrote:
> > > Dear Myrle,
> > >
> > > It may be irrelevant, but let me shoot anyway...!!!... please don't
> > through stones onto me.
> > >
> > > PostgreSQL is believe to have very/most liberal license... as matter of
> > facts... it will avoid now and any future license conflict.
> > >
> > > The question is then, why don't we select PostgreSQL as our default
> DBMS?
> > >
> > > - is it related with our skill set? or
> > > - it is more just related to smooth transfer from MySQL to MariaDB?
> > >
> > > Taking into Finaract CN project take a revolution approach from its
> > predecessor Finaract; why also not take same approach on database?
> > > - after-all Fineract CN Architecture is decoupled from reliance on
> > particular database system...
> > >
> > >
> > > Refer
> > > https://www.postgresql.org/about/licence/
> > > https://www.postgresql.org/list/
> > > https://opensource.org/licenses/MIT
> > >
> > >
> > > Regards
> > > Sendoro
> > > ----- Original Message -----
> > > From: "Myrle Krantz" <my...@apache.org>
> > > To: "dev" <de...@fineract.apache.org>
> > > Sent: Wednesday, April 18, 2018 9:44:13 AM
> > > Subject: Re: Moving Towards Apache Compliance for Fineract CN:
> Hibernate
> > to OpenJPA Migration.
> > >
> > > Thank you Sendoro,
> > >
> > > It's much appreciated.
> > >
> > > FYI: I've captured the MariaDB work items in 2 new tickets:
> > > https://issues.apache.org/jira/browse/FINCN-26
> > > https://issues.apache.org/jira/browse/FINCN-27
> > >
> > > Best Regards,
> > > Myrle
> > >
> > > On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma <se...@singo.africa>
> > wrote:
> > >> Hello Myrle,
> > >>
> > >> I got you.
> > >>
> > >> Let me know if there is any other component need to be checked!
> > >>
> > >> Cheers
> > >> Sendoro
> >
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Isaac Kamga <is...@mifos.org>.
Hello everyone,
I'm following up on this thread because we still haven't made progress with
eliminating Category X dependencies in Fineract CN which Yannick evoked
half a year ago.
@Myrle and @Awasum, I've read through this thread and I second Sendoro's
suggestion that we completely move Fineract CN's dependence on MariaDB to
PosgreSQL instead. Besides MariaDB's license
<https://mariadb.com/kb/en/library/licensing-faq/> being an inadmissible
Category X dependency, PostgreSQL is Apache-compliant and is a good
alternative for MariaDB.
I think this will entail writing an equivalent library to
fineract-cn-mariadb <https://github.com/apache/fineract-cn-mariadb> which
we can name *fineract-cn-postgresql*. It may use the OpenJPA ORM which
replaces Hibernate and use PostgreSQL's PgJDBC driver. I've started
dabbling with this and will share the link to the code base tomorrow.
I want to work on this task and share my thoughts, challenges and progress
here with you too.
What do you think about it ?
Cheers,
Isaac Kamga.
On Wed, Apr 18, 2018 at 9:13 AM Myrle Krantz <my...@apache.org> wrote:
> I think that's an excellent suggestion Sendoro. Would you like to
> take the lead on that? I'd be happy to provide you with any help you
> need to make it happen!
>
> Best Regards,
> Myrle
>
> On Wed, Apr 18, 2018 at 9:47 AM, Sendoro Juma <se...@singo.africa>
> wrote:
> > Dear Myrle,
> >
> > It may be irrelevant, but let me shoot anyway...!!!... please don't
> through stones onto me.
> >
> > PostgreSQL is believe to have very/most liberal license... as matter of
> facts... it will avoid now and any future license conflict.
> >
> > The question is then, why don't we select PostgreSQL as our default DBMS?
> >
> > - is it related with our skill set? or
> > - it is more just related to smooth transfer from MySQL to MariaDB?
> >
> > Taking into Finaract CN project take a revolution approach from its
> predecessor Finaract; why also not take same approach on database?
> > - after-all Fineract CN Architecture is decoupled from reliance on
> particular database system...
> >
> >
> > Refer
> > https://www.postgresql.org/about/licence/
> > https://www.postgresql.org/list/
> > https://opensource.org/licenses/MIT
> >
> >
> > Regards
> > Sendoro
> > ----- Original Message -----
> > From: "Myrle Krantz" <my...@apache.org>
> > To: "dev" <de...@fineract.apache.org>
> > Sent: Wednesday, April 18, 2018 9:44:13 AM
> > Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate
> to OpenJPA Migration.
> >
> > Thank you Sendoro,
> >
> > It's much appreciated.
> >
> > FYI: I've captured the MariaDB work items in 2 new tickets:
> > https://issues.apache.org/jira/browse/FINCN-26
> > https://issues.apache.org/jira/browse/FINCN-27
> >
> > Best Regards,
> > Myrle
> >
> > On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma <se...@singo.africa>
> wrote:
> >> Hello Myrle,
> >>
> >> I got you.
> >>
> >> Let me know if there is any other component need to be checked!
> >>
> >> Cheers
> >> Sendoro
>
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Myrle Krantz <my...@apache.org>.
I think that's an excellent suggestion Sendoro. Would you like to
take the lead on that? I'd be happy to provide you with any help you
need to make it happen!
Best Regards,
Myrle
On Wed, Apr 18, 2018 at 9:47 AM, Sendoro Juma <se...@singo.africa> wrote:
> Dear Myrle,
>
> It may be irrelevant, but let me shoot anyway...!!!... please don't through stones onto me.
>
> PostgreSQL is believe to have very/most liberal license... as matter of facts... it will avoid now and any future license conflict.
>
> The question is then, why don't we select PostgreSQL as our default DBMS?
>
> - is it related with our skill set? or
> - it is more just related to smooth transfer from MySQL to MariaDB?
>
> Taking into Finaract CN project take a revolution approach from its predecessor Finaract; why also not take same approach on database?
> - after-all Fineract CN Architecture is decoupled from reliance on particular database system...
>
>
> Refer
> https://www.postgresql.org/about/licence/
> https://www.postgresql.org/list/
> https://opensource.org/licenses/MIT
>
>
> Regards
> Sendoro
> ----- Original Message -----
> From: "Myrle Krantz" <my...@apache.org>
> To: "dev" <de...@fineract.apache.org>
> Sent: Wednesday, April 18, 2018 9:44:13 AM
> Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
>
> Thank you Sendoro,
>
> It's much appreciated.
>
> FYI: I've captured the MariaDB work items in 2 new tickets:
> https://issues.apache.org/jira/browse/FINCN-26
> https://issues.apache.org/jira/browse/FINCN-27
>
> Best Regards,
> Myrle
>
> On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma <se...@singo.africa> wrote:
>> Hello Myrle,
>>
>> I got you.
>>
>> Let me know if there is any other component need to be checked!
>>
>> Cheers
>> Sendoro
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Sendoro Juma <se...@singo.africa>.
Dear Myrle,
It may be irrelevant, but let me shoot anyway...!!!... please don't through stones onto me.
PostgreSQL is believe to have very/most liberal license... as matter of facts... it will avoid now and any future license conflict.
The question is then, why don't we select PostgreSQL as our default DBMS?
- is it related with our skill set? or
- it is more just related to smooth transfer from MySQL to MariaDB?
Taking into Finaract CN project take a revolution approach from its predecessor Finaract; why also not take same approach on database?
- after-all Fineract CN Architecture is decoupled from reliance on particular database system...
Refer
https://www.postgresql.org/about/licence/
https://www.postgresql.org/list/
https://opensource.org/licenses/MIT
Regards
Sendoro
----- Original Message -----
From: "Myrle Krantz" <my...@apache.org>
To: "dev" <de...@fineract.apache.org>
Sent: Wednesday, April 18, 2018 9:44:13 AM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
Thank you Sendoro,
It's much appreciated.
FYI: I've captured the MariaDB work items in 2 new tickets:
https://issues.apache.org/jira/browse/FINCN-26
https://issues.apache.org/jira/browse/FINCN-27
Best Regards,
Myrle
On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma <se...@singo.africa> wrote:
> Hello Myrle,
>
> I got you.
>
> Let me know if there is any other component need to be checked!
>
> Cheers
> Sendoro
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Myrle Krantz <my...@apache.org>.
Thank you Sendoro,
It's much appreciated.
FYI: I've captured the MariaDB work items in 2 new tickets:
https://issues.apache.org/jira/browse/FINCN-26
https://issues.apache.org/jira/browse/FINCN-27
Best Regards,
Myrle
On Mon, Apr 16, 2018 at 4:39 PM, Sendoro Juma <se...@singo.africa> wrote:
> Hello Myrle,
>
> I got you.
>
> Let me know if there is any other component need to be checked!
>
> Cheers
> Sendoro
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Sendoro Juma <se...@singo.africa>.
Hello Myrle,
I got you.
Let me know if there is any other component need to be checked!
Cheers
Sendoro
----- Original Message -----
From: "Myrle Krantz" <my...@apache.org>
To: "dev" <de...@fineract.apache.org>
Sent: Monday, April 16, 2018 4:43:09 PM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
Hey Sendoro,
Unfortunately that's not good enough. I agree with your
interpretation of LGPL, but the ASF is, as a foundation, taking a more
conservative stance. Apache projects are not allowed to depend on
LGPL libraries. The ASF choses to be cautious on this matter, because
many companies depend on code produced by the ASF.
This sequence of events would be bad:
1.) We include LGPL software in our release.
2.) Our code, including the LGPL dependency is included in proprietary
code of CompanyOmega
3.) Some judge somewhere decides that the "firewall" separating our
code from the LGPL isn't strong enough to call prevent the viral
aspects of LGPL from taking effect.
4.) CompanyOmega's proprietary code is now all open source and they go
out of business.
It's not a likely sequence, but because of the size of the negative
outcome, we avoid it by not including LGPL (or any other Category X
software) in our releases.
We will have to remove any dependencies to CatX software before we
release Fineract CN.
Best Regards,
Myrle
(By the way, the Hibernate Validator, unlike the Hibernate JPA
implementation, is released under the Apache V2 license
https://github.com/hibernate/hibernate-validator/blob/master/license.txt)
On Sun, Apr 15, 2018 at 2:55 PM, Sendoro Juma <se...@singo.africa> wrote:
> Dear All,
>
> I believe this can resolve the issue with MariaDB client
>
> -------------
> Licenses used by MariaDB
> MariaDB is distributed under the GPL license, version 2.
>
> The MariaDB client libraries for C, Java and ODBC are distributed under the LGPL license, version 2.1 or later. The LGPL license allows you to distribute these MariaDB client libraries freely with any application.
>
> The MariaDB client library included with the MariaDB server is also GPL version 2, but has a FLOSS exception that allows you to combine it with most other open source software, without conflicting with their license, even if that license is incompatible with the GPL. We do however recommend you to use the new client libraries for any non-GPL application.
>
> About FLOSS exception.... #Below Apache Software License 2.0 is included.
>
>
> FLOSS License List
>
> License name Version(s)/Copyright Date
> Academic Free License 2.0
> Apache Software License 1.0/1.1/2.0
> Apple Public Source License 2.0
> Artistic license From Perl 5.8.0
> BSD license "July 22 1999"
> Common Development and Distribution License (CDDL) 1.0
> Common Public License 1.0
> Eclipse Public License 1.0
> GNU Library or "Lesser" General Public License (LGPL) 2.0/2.1
> Jabber Open Source License 1.0
> MIT license (As listed in file MIT-License.txt) ---
> Mozilla Public License (MPL) 1.0/1.1
> Open Software License 2.0
> OpenSSL license (with original SSLeay license) "2003" ("1998")
> PHP License 3.0
> Python license (CNRI Python License) ---
> Python Software Foundation License 2.1.1
> Sleepycat License "1999"
> University of Illinois/NCSA Open Source License ---
> W3C License "2001"
> X11 License "2001"
> Zlib/libpng License ---
> Zope Public License 2.0
>
> Due to the many variants of some of the above licenses, we
> require that any version follow the 2003 version of the Free
> Software Foundation's Free Software Definition
> (http://www.gnu.org/philosophy/free-sw.html) or version 1.9 of
> the Open Source Definition by the Open Source Initiative
> (http://www.opensource.org/docs/definition.php).
>
> 3. Definitions
>
> a. Terms used, but not defined, herein shall have the
> meaning provided in the GPL.
> b. Derivative Work means a derivative work under copyright
> law.
>
> 4. Applicability: This FLOSS Exception applies to all Programs
> that contain a notice placed by MySQL AB saying that the
> Program may be distributed under the terms of this FLOSS
> Exception. If you create or distribute a work which is a
> Derivative Work of both the Program and any other work
> licensed under the GPL, then this FLOSS Exception is not
> available for that work; thus, you must remove the FLOSS
> Exception notice from that work and comply with the GPL in all
> respects, including by retaining all GPL notices. You may
> choose to redistribute a copy of the Program exclusively under
> the terms of the GPL by removing the FLOSS Exception notice
> from that copy of the Program, provided that the copy has
> never been modified by you or any third party.
> --------------------------
>
> ----- Original Message -----
> From: "Sendoro Juma" <se...@singo.africa>
> To: "dev" <de...@fineract.apache.org>
> Sent: Sunday, April 15, 2018 2:41:50 PM
> Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
>
> There are these comments though....
>
> GNU GPL/GNU Affero GPL
> Discussion of Apache License v2.0 and GPL Compatibility merits a separate page. http://www.apache.org/licenses/GPL-compatibility.html
>
> GNU LGPL
> The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion.
> Special exceptions to the GNU GPL
> Some copyright holders have licensed their works under the GPL with special exceptions. Although these exceptions may appear to be addressing the restrictions disallowed by the ASF's first and second license criteria, the exceptions may only apply to software not "derived from or based on" the covered work. This references terms defined in the GPL that include works that "use" or "contain" the work.
>
> ----- Original Message -----
> From: "Sendoro Juma" <se...@singo.africa>
> To: "dev" <de...@fineract.apache.org>
> Sent: Sunday, April 15, 2018 2:38:45 PM
> Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
>
> LPGL 2.1 is categorically included as not compliant.
>
> WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?
> Binary Code License (BCL)
> Special exceptions to the GNU GPL (e.g. GNU Classpath)
> GNU GPL 1, 2, 3
> GNU LGPL 2, 2.1, 3
> GNU Affero GPL 3
> ....
> ....
> ....
>
>
> ----- Original Message -----
> From: "Awasum Yannick" <aw...@apache.org>
> To: "dev" <de...@fineract.apache.org>
> Sent: Saturday, March 10, 2018 6:29:51 PM
> Subject: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
>
> Hello Everyone,
>
> I am hoping we could take some time to discuss and come up with approaches
> for achieving full Apache compliance on the Fineract CN project.
> I think there are still dependencies on Fineract CN which need some
> attention in terms of checking the licenses and making sure they are
> compliant with the Apache license.
>
> To that end, I began looking at the Microservices and checking the license
> of each dependency in accordance with this list:
> https://www.apache.org/legal/resolved.html
>
> Within the mariadb component, i realized that the
> *mariadb-java-client* uses LGPL 2.1
> (Is this compliant with the Apache license? ).
>
> I don't know if there are other dependencies which are not Apache
> compliant like the known case: Hibernate.
>
> To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
> the following:
>
> * Replace the Hibernate Validator with something more Apache compliant like
> javax.validation.*
> or a corresponding OpenJPA library if such exists.
>
> * Configure and set the LocalContainerEntityManagerFactoryBean ( within
>
> MariaDBJavaConfiguratio
> n )
>
> to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
> HibernateJpaVendorAdapter ) within mariadb component. And also the set the
> right properties for OpenJPA ( peristence unit etc ).
>
> I will like more experienced developers/architects in the community weigh
> in and provide additional details which will enable the gradual migration
> from Hibernate to OpenJPA and to get other non-compliant dependencies
> migrated too. From this point, volunteers can pick this up and make
> progress.
>
>
> Thanks.
> Awasum Yannick.
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Myrle Krantz <my...@apache.org>.
Hey Sendoro,
Unfortunately that's not good enough. I agree with your
interpretation of LGPL, but the ASF is, as a foundation, taking a more
conservative stance. Apache projects are not allowed to depend on
LGPL libraries. The ASF choses to be cautious on this matter, because
many companies depend on code produced by the ASF.
This sequence of events would be bad:
1.) We include LGPL software in our release.
2.) Our code, including the LGPL dependency is included in proprietary
code of CompanyOmega
3.) Some judge somewhere decides that the "firewall" separating our
code from the LGPL isn't strong enough to call prevent the viral
aspects of LGPL from taking effect.
4.) CompanyOmega's proprietary code is now all open source and they go
out of business.
It's not a likely sequence, but because of the size of the negative
outcome, we avoid it by not including LGPL (or any other Category X
software) in our releases.
We will have to remove any dependencies to CatX software before we
release Fineract CN.
Best Regards,
Myrle
(By the way, the Hibernate Validator, unlike the Hibernate JPA
implementation, is released under the Apache V2 license
https://github.com/hibernate/hibernate-validator/blob/master/license.txt)
On Sun, Apr 15, 2018 at 2:55 PM, Sendoro Juma <se...@singo.africa> wrote:
> Dear All,
>
> I believe this can resolve the issue with MariaDB client
>
> -------------
> Licenses used by MariaDB
> MariaDB is distributed under the GPL license, version 2.
>
> The MariaDB client libraries for C, Java and ODBC are distributed under the LGPL license, version 2.1 or later. The LGPL license allows you to distribute these MariaDB client libraries freely with any application.
>
> The MariaDB client library included with the MariaDB server is also GPL version 2, but has a FLOSS exception that allows you to combine it with most other open source software, without conflicting with their license, even if that license is incompatible with the GPL. We do however recommend you to use the new client libraries for any non-GPL application.
>
> About FLOSS exception.... #Below Apache Software License 2.0 is included.
>
>
> FLOSS License List
>
> License name Version(s)/Copyright Date
> Academic Free License 2.0
> Apache Software License 1.0/1.1/2.0
> Apple Public Source License 2.0
> Artistic license From Perl 5.8.0
> BSD license "July 22 1999"
> Common Development and Distribution License (CDDL) 1.0
> Common Public License 1.0
> Eclipse Public License 1.0
> GNU Library or "Lesser" General Public License (LGPL) 2.0/2.1
> Jabber Open Source License 1.0
> MIT license (As listed in file MIT-License.txt) ---
> Mozilla Public License (MPL) 1.0/1.1
> Open Software License 2.0
> OpenSSL license (with original SSLeay license) "2003" ("1998")
> PHP License 3.0
> Python license (CNRI Python License) ---
> Python Software Foundation License 2.1.1
> Sleepycat License "1999"
> University of Illinois/NCSA Open Source License ---
> W3C License "2001"
> X11 License "2001"
> Zlib/libpng License ---
> Zope Public License 2.0
>
> Due to the many variants of some of the above licenses, we
> require that any version follow the 2003 version of the Free
> Software Foundation's Free Software Definition
> (http://www.gnu.org/philosophy/free-sw.html) or version 1.9 of
> the Open Source Definition by the Open Source Initiative
> (http://www.opensource.org/docs/definition.php).
>
> 3. Definitions
>
> a. Terms used, but not defined, herein shall have the
> meaning provided in the GPL.
> b. Derivative Work means a derivative work under copyright
> law.
>
> 4. Applicability: This FLOSS Exception applies to all Programs
> that contain a notice placed by MySQL AB saying that the
> Program may be distributed under the terms of this FLOSS
> Exception. If you create or distribute a work which is a
> Derivative Work of both the Program and any other work
> licensed under the GPL, then this FLOSS Exception is not
> available for that work; thus, you must remove the FLOSS
> Exception notice from that work and comply with the GPL in all
> respects, including by retaining all GPL notices. You may
> choose to redistribute a copy of the Program exclusively under
> the terms of the GPL by removing the FLOSS Exception notice
> from that copy of the Program, provided that the copy has
> never been modified by you or any third party.
> --------------------------
>
> ----- Original Message -----
> From: "Sendoro Juma" <se...@singo.africa>
> To: "dev" <de...@fineract.apache.org>
> Sent: Sunday, April 15, 2018 2:41:50 PM
> Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
>
> There are these comments though....
>
> GNU GPL/GNU Affero GPL
> Discussion of Apache License v2.0 and GPL Compatibility merits a separate page. http://www.apache.org/licenses/GPL-compatibility.html
>
> GNU LGPL
> The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion.
> Special exceptions to the GNU GPL
> Some copyright holders have licensed their works under the GPL with special exceptions. Although these exceptions may appear to be addressing the restrictions disallowed by the ASF's first and second license criteria, the exceptions may only apply to software not "derived from or based on" the covered work. This references terms defined in the GPL that include works that "use" or "contain" the work.
>
> ----- Original Message -----
> From: "Sendoro Juma" <se...@singo.africa>
> To: "dev" <de...@fineract.apache.org>
> Sent: Sunday, April 15, 2018 2:38:45 PM
> Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
>
> LPGL 2.1 is categorically included as not compliant.
>
> WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?
> Binary Code License (BCL)
> Special exceptions to the GNU GPL (e.g. GNU Classpath)
> GNU GPL 1, 2, 3
> GNU LGPL 2, 2.1, 3
> GNU Affero GPL 3
> ....
> ....
> ....
>
>
> ----- Original Message -----
> From: "Awasum Yannick" <aw...@apache.org>
> To: "dev" <de...@fineract.apache.org>
> Sent: Saturday, March 10, 2018 6:29:51 PM
> Subject: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
>
> Hello Everyone,
>
> I am hoping we could take some time to discuss and come up with approaches
> for achieving full Apache compliance on the Fineract CN project.
> I think there are still dependencies on Fineract CN which need some
> attention in terms of checking the licenses and making sure they are
> compliant with the Apache license.
>
> To that end, I began looking at the Microservices and checking the license
> of each dependency in accordance with this list:
> https://www.apache.org/legal/resolved.html
>
> Within the mariadb component, i realized that the
> *mariadb-java-client* uses LGPL 2.1
> (Is this compliant with the Apache license? ).
>
> I don't know if there are other dependencies which are not Apache
> compliant like the known case: Hibernate.
>
> To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
> the following:
>
> * Replace the Hibernate Validator with something more Apache compliant like
> javax.validation.*
> or a corresponding OpenJPA library if such exists.
>
> * Configure and set the LocalContainerEntityManagerFactoryBean ( within
>
> MariaDBJavaConfiguratio
> n )
>
> to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
> HibernateJpaVendorAdapter ) within mariadb component. And also the set the
> right properties for OpenJPA ( peristence unit etc ).
>
> I will like more experienced developers/architects in the community weigh
> in and provide additional details which will enable the gradual migration
> from Hibernate to OpenJPA and to get other non-compliant dependencies
> migrated too. From this point, volunteers can pick this up and make
> progress.
>
>
> Thanks.
> Awasum Yannick.
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Sendoro Juma <se...@singo.africa>.
Dear All,
I believe this can resolve the issue with MariaDB client
-------------
Licenses used by MariaDB
MariaDB is distributed under the GPL license, version 2.
The MariaDB client libraries for C, Java and ODBC are distributed under the LGPL license, version 2.1 or later. The LGPL license allows you to distribute these MariaDB client libraries freely with any application.
The MariaDB client library included with the MariaDB server is also GPL version 2, but has a FLOSS exception that allows you to combine it with most other open source software, without conflicting with their license, even if that license is incompatible with the GPL. We do however recommend you to use the new client libraries for any non-GPL application.
About FLOSS exception.... #Below Apache Software License 2.0 is included.
FLOSS License List
License name Version(s)/Copyright Date
Academic Free License 2.0
Apache Software License 1.0/1.1/2.0
Apple Public Source License 2.0
Artistic license From Perl 5.8.0
BSD license "July 22 1999"
Common Development and Distribution License (CDDL) 1.0
Common Public License 1.0
Eclipse Public License 1.0
GNU Library or "Lesser" General Public License (LGPL) 2.0/2.1
Jabber Open Source License 1.0
MIT license (As listed in file MIT-License.txt) ---
Mozilla Public License (MPL) 1.0/1.1
Open Software License 2.0
OpenSSL license (with original SSLeay license) "2003" ("1998")
PHP License 3.0
Python license (CNRI Python License) ---
Python Software Foundation License 2.1.1
Sleepycat License "1999"
University of Illinois/NCSA Open Source License ---
W3C License "2001"
X11 License "2001"
Zlib/libpng License ---
Zope Public License 2.0
Due to the many variants of some of the above licenses, we
require that any version follow the 2003 version of the Free
Software Foundation's Free Software Definition
(http://www.gnu.org/philosophy/free-sw.html) or version 1.9 of
the Open Source Definition by the Open Source Initiative
(http://www.opensource.org/docs/definition.php).
3. Definitions
a. Terms used, but not defined, herein shall have the
meaning provided in the GPL.
b. Derivative Work means a derivative work under copyright
law.
4. Applicability: This FLOSS Exception applies to all Programs
that contain a notice placed by MySQL AB saying that the
Program may be distributed under the terms of this FLOSS
Exception. If you create or distribute a work which is a
Derivative Work of both the Program and any other work
licensed under the GPL, then this FLOSS Exception is not
available for that work; thus, you must remove the FLOSS
Exception notice from that work and comply with the GPL in all
respects, including by retaining all GPL notices. You may
choose to redistribute a copy of the Program exclusively under
the terms of the GPL by removing the FLOSS Exception notice
from that copy of the Program, provided that the copy has
never been modified by you or any third party.
--------------------------
----- Original Message -----
From: "Sendoro Juma" <se...@singo.africa>
To: "dev" <de...@fineract.apache.org>
Sent: Sunday, April 15, 2018 2:41:50 PM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
There are these comments though....
GNU GPL/GNU Affero GPL
Discussion of Apache License v2.0 and GPL Compatibility merits a separate page. http://www.apache.org/licenses/GPL-compatibility.html
GNU LGPL
The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion.
Special exceptions to the GNU GPL
Some copyright holders have licensed their works under the GPL with special exceptions. Although these exceptions may appear to be addressing the restrictions disallowed by the ASF's first and second license criteria, the exceptions may only apply to software not "derived from or based on" the covered work. This references terms defined in the GPL that include works that "use" or "contain" the work.
----- Original Message -----
From: "Sendoro Juma" <se...@singo.africa>
To: "dev" <de...@fineract.apache.org>
Sent: Sunday, April 15, 2018 2:38:45 PM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
LPGL 2.1 is categorically included as not compliant.
WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?
Binary Code License (BCL)
Special exceptions to the GNU GPL (e.g. GNU Classpath)
GNU GPL 1, 2, 3
GNU LGPL 2, 2.1, 3
GNU Affero GPL 3
....
....
....
----- Original Message -----
From: "Awasum Yannick" <aw...@apache.org>
To: "dev" <de...@fineract.apache.org>
Sent: Saturday, March 10, 2018 6:29:51 PM
Subject: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
Hello Everyone,
I am hoping we could take some time to discuss and come up with approaches
for achieving full Apache compliance on the Fineract CN project.
I think there are still dependencies on Fineract CN which need some
attention in terms of checking the licenses and making sure they are
compliant with the Apache license.
To that end, I began looking at the Microservices and checking the license
of each dependency in accordance with this list:
https://www.apache.org/legal/resolved.html
Within the mariadb component, i realized that the
*mariadb-java-client* uses LGPL 2.1
(Is this compliant with the Apache license? ).
I don't know if there are other dependencies which are not Apache
compliant like the known case: Hibernate.
To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
the following:
* Replace the Hibernate Validator with something more Apache compliant like
javax.validation.*
or a corresponding OpenJPA library if such exists.
* Configure and set the LocalContainerEntityManagerFactoryBean ( within
MariaDBJavaConfiguratio
n )
to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
HibernateJpaVendorAdapter ) within mariadb component. And also the set the
right properties for OpenJPA ( peristence unit etc ).
I will like more experienced developers/architects in the community weigh
in and provide additional details which will enable the gradual migration
from Hibernate to OpenJPA and to get other non-compliant dependencies
migrated too. From this point, volunteers can pick this up and make
progress.
Thanks.
Awasum Yannick.
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Sendoro Juma <se...@singo.africa>.
There are these comments though....
GNU GPL/GNU Affero GPL
Discussion of Apache License v2.0 and GPL Compatibility merits a separate page. http://www.apache.org/licenses/GPL-compatibility.html
GNU LGPL
The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion.
Special exceptions to the GNU GPL
Some copyright holders have licensed their works under the GPL with special exceptions. Although these exceptions may appear to be addressing the restrictions disallowed by the ASF's first and second license criteria, the exceptions may only apply to software not "derived from or based on" the covered work. This references terms defined in the GPL that include works that "use" or "contain" the work.
----- Original Message -----
From: "Sendoro Juma" <se...@singo.africa>
To: "dev" <de...@fineract.apache.org>
Sent: Sunday, April 15, 2018 2:38:45 PM
Subject: Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
LPGL 2.1 is categorically included as not compliant.
WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?
Binary Code License (BCL)
Special exceptions to the GNU GPL (e.g. GNU Classpath)
GNU GPL 1, 2, 3
GNU LGPL 2, 2.1, 3
GNU Affero GPL 3
....
....
....
----- Original Message -----
From: "Awasum Yannick" <aw...@apache.org>
To: "dev" <de...@fineract.apache.org>
Sent: Saturday, March 10, 2018 6:29:51 PM
Subject: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
Hello Everyone,
I am hoping we could take some time to discuss and come up with approaches
for achieving full Apache compliance on the Fineract CN project.
I think there are still dependencies on Fineract CN which need some
attention in terms of checking the licenses and making sure they are
compliant with the Apache license.
To that end, I began looking at the Microservices and checking the license
of each dependency in accordance with this list:
https://www.apache.org/legal/resolved.html
Within the mariadb component, i realized that the
*mariadb-java-client* uses LGPL 2.1
(Is this compliant with the Apache license? ).
I don't know if there are other dependencies which are not Apache
compliant like the known case: Hibernate.
To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
the following:
* Replace the Hibernate Validator with something more Apache compliant like
javax.validation.*
or a corresponding OpenJPA library if such exists.
* Configure and set the LocalContainerEntityManagerFactoryBean ( within
MariaDBJavaConfiguratio
n )
to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
HibernateJpaVendorAdapter ) within mariadb component. And also the set the
right properties for OpenJPA ( peristence unit etc ).
I will like more experienced developers/architects in the community weigh
in and provide additional details which will enable the gradual migration
from Hibernate to OpenJPA and to get other non-compliant dependencies
migrated too. From this point, volunteers can pick this up and make
progress.
Thanks.
Awasum Yannick.
Re: Moving Towards Apache Compliance for Fineract CN: Hibernate to
OpenJPA Migration.
Posted by Sendoro Juma <se...@singo.africa>.
LPGL 2.1 is categorically included as not compliant.
WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?
Binary Code License (BCL)
Special exceptions to the GNU GPL (e.g. GNU Classpath)
GNU GPL 1, 2, 3
GNU LGPL 2, 2.1, 3
GNU Affero GPL 3
....
....
....
----- Original Message -----
From: "Awasum Yannick" <aw...@apache.org>
To: "dev" <de...@fineract.apache.org>
Sent: Saturday, March 10, 2018 6:29:51 PM
Subject: Moving Towards Apache Compliance for Fineract CN: Hibernate to OpenJPA Migration.
Hello Everyone,
I am hoping we could take some time to discuss and come up with approaches
for achieving full Apache compliance on the Fineract CN project.
I think there are still dependencies on Fineract CN which need some
attention in terms of checking the licenses and making sure they are
compliant with the Apache license.
To that end, I began looking at the Microservices and checking the license
of each dependency in accordance with this list:
https://www.apache.org/legal/resolved.html
Within the mariadb component, i realized that the
*mariadb-java-client* uses LGPL 2.1
(Is this compliant with the Apache license? ).
I don't know if there are other dependencies which are not Apache
compliant like the known case: Hibernate.
To migrate Fineract CN from using Hibernate to using OpenJPA, we might do
the following:
* Replace the Hibernate Validator with something more Apache compliant like
javax.validation.*
or a corresponding OpenJPA library if such exists.
* Configure and set the LocalContainerEntityManagerFactoryBean ( within
MariaDBJavaConfiguratio
n )
to use the right JpaVendorAdapter ( OpenJPAs own equivalent of
HibernateJpaVendorAdapter ) within mariadb component. And also the set the
right properties for OpenJPA ( peristence unit etc ).
I will like more experienced developers/architects in the community weigh
in and provide additional details which will enable the gradual migration
from Hibernate to OpenJPA and to get other non-compliant dependencies
migrated too. From this point, volunteers can pick this up and make
progress.
Thanks.
Awasum Yannick.