You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Myrle Krantz <my...@apache.org> on 2017/09/19 08:18:15 UTC
[DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Hey all,
I'd like to begin discussion to bring Mifos I/O in to the Fineract
project as Apache Fineract CN. I propose the following process to get
us there. Note that this is a discussion thread. I will send a
voting thread once discussion has died down.
A.) Discuss and vote to accept the code into the Fineract project and
begin the Apache processes. We should not proceed beyond this point
until at least 2/3 of the Committers have voted. My preference is that
we reach 100%.
B.) Go through the IP clearance process (1) for that code via the
Incubator. This will probably require at least:
a.) A software grant from the Mifos Initiative
b.) A CLA from Kuelap
c.) An iCLAs from Mark van Veen, Nina Delvos, and Riana Allen.
d.) A thorough check through of the code to make sure those of us
working on it haven't missed any licensing issues.
C.) Discuss the necessary infrastructure for the code, and place the
corresponding requests with the INFRA team. This will at least include
JIRA, and github.
D.) Move the code and rename the packages from Mifos to Fineract.
E.) After migrating the code resolve any release-blockers which might remain.
F.) Go through the final QA/Release process for the new code base.
Release under the name Fineract CN to disambiguate from the current
Fineract code base.
G.) Announce and document.
H.) goto E.
I am *not* proposing that we stop development on the existing Fineract
code base. That is a decision for each individual contributor to
make, and it's not a decision that needs to be made at this time.
This will be a long process. It may be late October before we are even
at C. Please be patient once we get going.
Do you see anything that I've missed? Do you have any concerns?
Best Regards,
Myrle Krantz
Individual Contributor, Apache Fineract
1.) http://incubator.apache.org/ip-clearance/
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Ashok Auty <as...@confluxtechnologies.com>.
Hi Ed,
Do we have a demo instance setup for generation 3? If not, can it be done?
I am hearing of the generation 3 from long time (approximately from two
years if I am not wrong) but don't have an opportunity to take a first look
of the product.
I as a business user feel like completely left out of this project without
the demo access.
Is Generation 3 a Mifos initiative funded project?
Regards,
Ashok Auty
Sent from mobile device
On Sep 26, 2017 10:47 PM, "Ed Cable" <ed...@mifos.org> wrote:
Myrle,
I myself apologize that I hadn't replied or acknowledged your email. I
thank you for taking that step and documenting all that needs to be done.
I do wish there would have been some discussion but I do think the last
thread we had was sufficient discussion and interest and enthusiasm and
that we could call for a vote amongst the committers. There was a lot to
absorb in the email and I think once we have the vote and software
clearance process underway, we could start separate threads and align
individuals in separate working groups to tackle some of the remaining
items C through H.
I foresee no obstacles in the software grant process from the Mifos side. I
will get approval from my board but they are all in favor so no issues
there.
Ed
On Tue, Sep 26, 2017 at 1:39 AM, Myrle Krantz <my...@apache.org> wrote:
> I've gotten no response on this, and given the previously displayed
> enthusiasm, I'm a little surprised.
>
> Ed, do you foresee any problems with the software grant process from
> Mifos? Is that something you decide, or will you need to get the OK
> from your board?
>
> Thanks,
> Myrle
>
> On Tue, Sep 19, 2017 at 10:18 AM, Myrle Krantz <my...@apache.org> wrote:
> > Hey all,
> >
> > I'd like to begin discussion to bring Mifos I/O in to the Fineract
> > project as Apache Fineract CN. I propose the following process to get
> > us there. Note that this is a discussion thread. I will send a
> > voting thread once discussion has died down.
> >
> > A.) Discuss and vote to accept the code into the Fineract project and
> > begin the Apache processes. We should not proceed beyond this point
> > until at least 2/3 of the Committers have voted. My preference is that
> > we reach 100%.
> > B.) Go through the IP clearance process (1) for that code via the
> > Incubator. This will probably require at least:
> > a.) A software grant from the Mifos Initiative
> > b.) A CLA from Kuelap
> > c.) An iCLAs from Mark van Veen, Nina Delvos, and Riana Allen.
> > d.) A thorough check through of the code to make sure those of us
> > working on it haven't missed any licensing issues.
> > C.) Discuss the necessary infrastructure for the code, and place the
> > corresponding requests with the INFRA team. This will at least include
> > JIRA, and github.
> > D.) Move the code and rename the packages from Mifos to Fineract.
> > E.) After migrating the code resolve any release-blockers which might
> remain.
> > F.) Go through the final QA/Release process for the new code base.
> > Release under the name Fineract CN to disambiguate from the current
> > Fineract code base.
> > G.) Announce and document.
> > H.) goto E.
> >
> > I am *not* proposing that we stop development on the existing Fineract
> > code base. That is a decision for each individual contributor to
> > make, and it's not a decision that needs to be made at this time.
> >
> > This will be a long process. It may be late October before we are even
> > at C. Please be patient once we get going.
> >
> > Do you see anything that I've missed? Do you have any concerns?
> >
> > Best Regards,
> > Myrle Krantz
> > Individual Contributor, Apache Fineract
> >
> > 1.) http://incubator.apache.org/ip-clearance/
>
--
*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: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Myrle Krantz <my...@apache.org>.
On Thu, Sep 28, 2017 at 4:53 PM, Ippez Robert <ip...@gmail.com> wrote:
> For the future
> there needs to be optimisation for resources usage specially for those
> going to host locally.
Definitely. Right now each service is started via spring boot in its
own process. Doing it this way is how we got the whole thing working
with Eureka, but the resource-intensiveness of this approach causes
problems. It is not just a problem for developers, it is a stumbling
block for QA as well. It makes manual QA of branches near impossible,
and, even if you have a computer with sufficient resources it makes
integration testing very slow. This has forced us to neglect
integration testing.
In short, it needs to change, and I welcome any assistance in changing
it. It's probably good enough if we can start all the services in the
same process for the demo server and the integration tests. I'd even
be willing to sacrifice the coverage of service discovery via Eureka
in the tests for this, though I would *prefer* a solution which still
checks that the whole landscape works with Eureka.
Best Regards,
Myrle
>
> Cheers...
> Regards
> Ippez Robert
>
> On 28 Sep 2017 17:47, "Markus Geiss" <ma...@kuelap.io> wrote:
>
>> Hey Mohit,
>>
>> the current version is build to work with Google Chrome only recommended
>> version is 59+
>>
>> If possible can you share the console output of
>>
>> Cheers
>>
>> Markus
>>
>> .::Yagni likes a DRY KISS::. the browser ...
>>
>> On Thu, Sep 28, 2017 at 4:25 PM Mohit Bajoria <mo...@gmail.com>
>> wrote:
>>
>> > Hello Yannick,
>> >
>> > I am not able to access it https://training.kuelap.io:8443/index.html ,
>> it
>> > just keeps on loading the webpage
>> >
>> > Regards
>> > Mohit
>> >
>> > On 28 September 2017 at 16:42, Markus Geiss <ma...@kuelap.io>
>> > wrote:
>> >
>> > > Yannick is right. (;
>> > >
>> > > With an upcoming update we will have a fix for the index.html issue.
>> > >
>> > > Cheers
>> > >
>> > > Markus
>> > >
>> > > .::Yagni likes a DRY KISS::.
>> > >
>> > > On Thu, Sep 28, 2017 at 12:50 PM Awasum Yannick <
>> yannickawasum@gmail.com
>> > >
>> > > wrote:
>> > >
>> > > > Hello Nayan,
>> > > >
>> > > > The problem is you are trying to access it with incomplete URL:
>> > > > https://training.kuelap.io:8443/
>> > > >
>> > > > You have to use the complete URL each time you want to login:
>> > > > https://training.kuelap.io:8443/index.html
>> > > >
>> > > > With the "index.html" included.
>> > > >
>> > > > Thanks
>> > > >
>> > > >
>> > > > On Thu, Sep 28, 2017 at 11:42 AM, Nayan Ambali <na...@rupie.co>
>> wrote:
>> > > >
>> > > > > Hello Markus,
>> > > > >
>> > > > > Hope you are doing good.
>> > > > >
>> > > > > Eager to have look at Gen 3. I am getting below error when I visit
>> > the
>> > > > URL
>> > > > > above URL
>> > > > >
>> > > > > Whitelabel Error Page
>> > > > >
>> > > > > This application has no explicit mapping for /error, so you are
>> > seeing
>> > > > this
>> > > > > as a fallback.
>> > > > > Thu Sep 28 10:36:56 UTC 2017
>> > > > > There was an unexpected error (type=Not Found, status=404).
>> > > > > Not Found
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Thu, Sep 28, 2017 at 1:20 PM, Markus Geiss <
>> > markus.geiss@kuelap.io>
>> > > > > wrote:
>> > > > >
>> > > > > > Hey all,
>> > > > > >
>> > > > > > I believe that engaging business people into the discussion is a
>> > good
>> > > > > > thing.
>> > > > > >
>> > > > > > Saying this, Kuelap decided to offer a demo site where you can
>> look
>> > > at
>> > > > > the
>> > > > > > application.
>> > > > > >
>> > > > > > We will wipe all existing data with every new update, to keep the
>> > > demo
>> > > > > > small and clean.
>> > > > > >
>> > > > > > Here you'll find it:
>> > > > > >
>> > > > > > https://training.kuelap.io:8443/index.html
>> > > > > >
>> > > > > > Tenant: playground
>> > > > > > Username: demo
>> > > > > > Password ven3t1@n
>> > > > > >
>> > > > > > Cheers
>> > > > > >
>> > > > > > Markus
>> > > > > >
>> > > > > > .::Yagni likes a DRY KISS::.
>> > > > > >
>> > > > > > On Thu, Sep 28, 2017 at 9:15 AM Myrle Krantz <my...@apache.org>
>> > > wrote:
>> > > > > >
>> > > > > > > Hey Ed, Ashok, (and Markus)
>> > > > > > >
>> > > > > > > On Wed, Sep 27, 2017 at 6:31 PM, Ed Cable <ed...@mifos.org>
>> > > wrote:
>> > > > > > >
>> > > > > > > > All that being said, I know that Rajan had a playground/demo
>> > site
>> > > > > that
>> > > > > > he
>> > > > > > > > was testing on for GSOC. Can we share this demo instance with
>> > the
>> > > > > > broader
>> > > > > > > > community so they could have a sense of where the Apache
>> > Fineract
>> > > > CN
>> > > > > is
>> > > > > > > at
>> > > > > > > > functionally?
>> > > > > > >
>> > > > > > > That demo site is a QA site hosted by Kuelap (and subject to
>> > > frequent
>> > > > > > > updates and service hickups). Markus will have to answer as to
>> > > > > > > whether he wants Kuelap's SRE to set up a demo-site for
>> > evaluation
>> > > > for
>> > > > > > > y'all.
>> > > > > > >
>> > > > > > > Alternately, Mifos could host a demo instance. Or Ashok could
>> > > follow
>> > > > > > > the instructions for the demo-server and run it locally; for
>> > this,
>> > > > I'd
>> > > > > > > be happy to provide support.
>> > > > > > >
>> > > > > > > Best Regards,
>> > > > > > > Myrle
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> >
>> > *Regards*
>> > *Mohit Kumar Bajoria*
>> > *http://mohitbajoria.com <http://mohitbajoria.com>*
>> >
>>
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Ippez Robert <ip...@gmail.com>.
I was able to interact with it... trying to understand the functionality
though....
Thanks for the demo because setting local instance is a challenge
especially for computers using HDD as compared to SSD. For the future
there needs to be optimisation for resources usage specially for those
going to host locally.
Cheers...
Regards
Ippez Robert
On 28 Sep 2017 17:47, "Markus Geiss" <ma...@kuelap.io> wrote:
> Hey Mohit,
>
> the current version is build to work with Google Chrome only recommended
> version is 59+
>
> If possible can you share the console output of
>
> Cheers
>
> Markus
>
> .::Yagni likes a DRY KISS::. the browser ...
>
> On Thu, Sep 28, 2017 at 4:25 PM Mohit Bajoria <mo...@gmail.com>
> wrote:
>
> > Hello Yannick,
> >
> > I am not able to access it https://training.kuelap.io:8443/index.html ,
> it
> > just keeps on loading the webpage
> >
> > Regards
> > Mohit
> >
> > On 28 September 2017 at 16:42, Markus Geiss <ma...@kuelap.io>
> > wrote:
> >
> > > Yannick is right. (;
> > >
> > > With an upcoming update we will have a fix for the index.html issue.
> > >
> > > Cheers
> > >
> > > Markus
> > >
> > > .::Yagni likes a DRY KISS::.
> > >
> > > On Thu, Sep 28, 2017 at 12:50 PM Awasum Yannick <
> yannickawasum@gmail.com
> > >
> > > wrote:
> > >
> > > > Hello Nayan,
> > > >
> > > > The problem is you are trying to access it with incomplete URL:
> > > > https://training.kuelap.io:8443/
> > > >
> > > > You have to use the complete URL each time you want to login:
> > > > https://training.kuelap.io:8443/index.html
> > > >
> > > > With the "index.html" included.
> > > >
> > > > Thanks
> > > >
> > > >
> > > > On Thu, Sep 28, 2017 at 11:42 AM, Nayan Ambali <na...@rupie.co>
> wrote:
> > > >
> > > > > Hello Markus,
> > > > >
> > > > > Hope you are doing good.
> > > > >
> > > > > Eager to have look at Gen 3. I am getting below error when I visit
> > the
> > > > URL
> > > > > above URL
> > > > >
> > > > > Whitelabel Error Page
> > > > >
> > > > > This application has no explicit mapping for /error, so you are
> > seeing
> > > > this
> > > > > as a fallback.
> > > > > Thu Sep 28 10:36:56 UTC 2017
> > > > > There was an unexpected error (type=Not Found, status=404).
> > > > > Not Found
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Sep 28, 2017 at 1:20 PM, Markus Geiss <
> > markus.geiss@kuelap.io>
> > > > > wrote:
> > > > >
> > > > > > Hey all,
> > > > > >
> > > > > > I believe that engaging business people into the discussion is a
> > good
> > > > > > thing.
> > > > > >
> > > > > > Saying this, Kuelap decided to offer a demo site where you can
> look
> > > at
> > > > > the
> > > > > > application.
> > > > > >
> > > > > > We will wipe all existing data with every new update, to keep the
> > > demo
> > > > > > small and clean.
> > > > > >
> > > > > > Here you'll find it:
> > > > > >
> > > > > > https://training.kuelap.io:8443/index.html
> > > > > >
> > > > > > Tenant: playground
> > > > > > Username: demo
> > > > > > Password ven3t1@n
> > > > > >
> > > > > > Cheers
> > > > > >
> > > > > > Markus
> > > > > >
> > > > > > .::Yagni likes a DRY KISS::.
> > > > > >
> > > > > > On Thu, Sep 28, 2017 at 9:15 AM Myrle Krantz <my...@apache.org>
> > > wrote:
> > > > > >
> > > > > > > Hey Ed, Ashok, (and Markus)
> > > > > > >
> > > > > > > On Wed, Sep 27, 2017 at 6:31 PM, Ed Cable <ed...@mifos.org>
> > > wrote:
> > > > > > >
> > > > > > > > All that being said, I know that Rajan had a playground/demo
> > site
> > > > > that
> > > > > > he
> > > > > > > > was testing on for GSOC. Can we share this demo instance with
> > the
> > > > > > broader
> > > > > > > > community so they could have a sense of where the Apache
> > Fineract
> > > > CN
> > > > > is
> > > > > > > at
> > > > > > > > functionally?
> > > > > > >
> > > > > > > That demo site is a QA site hosted by Kuelap (and subject to
> > > frequent
> > > > > > > updates and service hickups). Markus will have to answer as to
> > > > > > > whether he wants Kuelap's SRE to set up a demo-site for
> > evaluation
> > > > for
> > > > > > > y'all.
> > > > > > >
> > > > > > > Alternately, Mifos could host a demo instance. Or Ashok could
> > > follow
> > > > > > > the instructions for the demo-server and run it locally; for
> > this,
> > > > I'd
> > > > > > > be happy to provide support.
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Myrle
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> >
> > *Regards*
> > *Mohit Kumar Bajoria*
> > *http://mohitbajoria.com <http://mohitbajoria.com>*
> >
>
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Markus Geiss <ma...@kuelap.io>.
Hey Mohit,
the current version is build to work with Google Chrome only recommended
version is 59+
If possible can you share the console output of
Cheers
Markus
.::Yagni likes a DRY KISS::. the browser ...
On Thu, Sep 28, 2017 at 4:25 PM Mohit Bajoria <mo...@gmail.com> wrote:
> Hello Yannick,
>
> I am not able to access it https://training.kuelap.io:8443/index.html , it
> just keeps on loading the webpage
>
> Regards
> Mohit
>
> On 28 September 2017 at 16:42, Markus Geiss <ma...@kuelap.io>
> wrote:
>
> > Yannick is right. (;
> >
> > With an upcoming update we will have a fix for the index.html issue.
> >
> > Cheers
> >
> > Markus
> >
> > .::Yagni likes a DRY KISS::.
> >
> > On Thu, Sep 28, 2017 at 12:50 PM Awasum Yannick <yannickawasum@gmail.com
> >
> > wrote:
> >
> > > Hello Nayan,
> > >
> > > The problem is you are trying to access it with incomplete URL:
> > > https://training.kuelap.io:8443/
> > >
> > > You have to use the complete URL each time you want to login:
> > > https://training.kuelap.io:8443/index.html
> > >
> > > With the "index.html" included.
> > >
> > > Thanks
> > >
> > >
> > > On Thu, Sep 28, 2017 at 11:42 AM, Nayan Ambali <na...@rupie.co> wrote:
> > >
> > > > Hello Markus,
> > > >
> > > > Hope you are doing good.
> > > >
> > > > Eager to have look at Gen 3. I am getting below error when I visit
> the
> > > URL
> > > > above URL
> > > >
> > > > Whitelabel Error Page
> > > >
> > > > This application has no explicit mapping for /error, so you are
> seeing
> > > this
> > > > as a fallback.
> > > > Thu Sep 28 10:36:56 UTC 2017
> > > > There was an unexpected error (type=Not Found, status=404).
> > > > Not Found
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Thu, Sep 28, 2017 at 1:20 PM, Markus Geiss <
> markus.geiss@kuelap.io>
> > > > wrote:
> > > >
> > > > > Hey all,
> > > > >
> > > > > I believe that engaging business people into the discussion is a
> good
> > > > > thing.
> > > > >
> > > > > Saying this, Kuelap decided to offer a demo site where you can look
> > at
> > > > the
> > > > > application.
> > > > >
> > > > > We will wipe all existing data with every new update, to keep the
> > demo
> > > > > small and clean.
> > > > >
> > > > > Here you'll find it:
> > > > >
> > > > > https://training.kuelap.io:8443/index.html
> > > > >
> > > > > Tenant: playground
> > > > > Username: demo
> > > > > Password ven3t1@n
> > > > >
> > > > > Cheers
> > > > >
> > > > > Markus
> > > > >
> > > > > .::Yagni likes a DRY KISS::.
> > > > >
> > > > > On Thu, Sep 28, 2017 at 9:15 AM Myrle Krantz <my...@apache.org>
> > wrote:
> > > > >
> > > > > > Hey Ed, Ashok, (and Markus)
> > > > > >
> > > > > > On Wed, Sep 27, 2017 at 6:31 PM, Ed Cable <ed...@mifos.org>
> > wrote:
> > > > > >
> > > > > > > All that being said, I know that Rajan had a playground/demo
> site
> > > > that
> > > > > he
> > > > > > > was testing on for GSOC. Can we share this demo instance with
> the
> > > > > broader
> > > > > > > community so they could have a sense of where the Apache
> Fineract
> > > CN
> > > > is
> > > > > > at
> > > > > > > functionally?
> > > > > >
> > > > > > That demo site is a QA site hosted by Kuelap (and subject to
> > frequent
> > > > > > updates and service hickups). Markus will have to answer as to
> > > > > > whether he wants Kuelap's SRE to set up a demo-site for
> evaluation
> > > for
> > > > > > y'all.
> > > > > >
> > > > > > Alternately, Mifos could host a demo instance. Or Ashok could
> > follow
> > > > > > the instructions for the demo-server and run it locally; for
> this,
> > > I'd
> > > > > > be happy to provide support.
> > > > > >
> > > > > > Best Regards,
> > > > > > Myrle
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
>
> *Regards*
> *Mohit Kumar Bajoria*
> *http://mohitbajoria.com <http://mohitbajoria.com>*
>
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Mohit Bajoria <mo...@gmail.com>.
Hello Yannick,
I am not able to access it https://training.kuelap.io:8443/index.html , it
just keeps on loading the webpage
Regards
Mohit
On 28 September 2017 at 16:42, Markus Geiss <ma...@kuelap.io> wrote:
> Yannick is right. (;
>
> With an upcoming update we will have a fix for the index.html issue.
>
> Cheers
>
> Markus
>
> .::Yagni likes a DRY KISS::.
>
> On Thu, Sep 28, 2017 at 12:50 PM Awasum Yannick <ya...@gmail.com>
> wrote:
>
> > Hello Nayan,
> >
> > The problem is you are trying to access it with incomplete URL:
> > https://training.kuelap.io:8443/
> >
> > You have to use the complete URL each time you want to login:
> > https://training.kuelap.io:8443/index.html
> >
> > With the "index.html" included.
> >
> > Thanks
> >
> >
> > On Thu, Sep 28, 2017 at 11:42 AM, Nayan Ambali <na...@rupie.co> wrote:
> >
> > > Hello Markus,
> > >
> > > Hope you are doing good.
> > >
> > > Eager to have look at Gen 3. I am getting below error when I visit the
> > URL
> > > above URL
> > >
> > > Whitelabel Error Page
> > >
> > > This application has no explicit mapping for /error, so you are seeing
> > this
> > > as a fallback.
> > > Thu Sep 28 10:36:56 UTC 2017
> > > There was an unexpected error (type=Not Found, status=404).
> > > Not Found
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Thu, Sep 28, 2017 at 1:20 PM, Markus Geiss <ma...@kuelap.io>
> > > wrote:
> > >
> > > > Hey all,
> > > >
> > > > I believe that engaging business people into the discussion is a good
> > > > thing.
> > > >
> > > > Saying this, Kuelap decided to offer a demo site where you can look
> at
> > > the
> > > > application.
> > > >
> > > > We will wipe all existing data with every new update, to keep the
> demo
> > > > small and clean.
> > > >
> > > > Here you'll find it:
> > > >
> > > > https://training.kuelap.io:8443/index.html
> > > >
> > > > Tenant: playground
> > > > Username: demo
> > > > Password ven3t1@n
> > > >
> > > > Cheers
> > > >
> > > > Markus
> > > >
> > > > .::Yagni likes a DRY KISS::.
> > > >
> > > > On Thu, Sep 28, 2017 at 9:15 AM Myrle Krantz <my...@apache.org>
> wrote:
> > > >
> > > > > Hey Ed, Ashok, (and Markus)
> > > > >
> > > > > On Wed, Sep 27, 2017 at 6:31 PM, Ed Cable <ed...@mifos.org>
> wrote:
> > > > >
> > > > > > All that being said, I know that Rajan had a playground/demo site
> > > that
> > > > he
> > > > > > was testing on for GSOC. Can we share this demo instance with the
> > > > broader
> > > > > > community so they could have a sense of where the Apache Fineract
> > CN
> > > is
> > > > > at
> > > > > > functionally?
> > > > >
> > > > > That demo site is a QA site hosted by Kuelap (and subject to
> frequent
> > > > > updates and service hickups). Markus will have to answer as to
> > > > > whether he wants Kuelap's SRE to set up a demo-site for evaluation
> > for
> > > > > y'all.
> > > > >
> > > > > Alternately, Mifos could host a demo instance. Or Ashok could
> follow
> > > > > the instructions for the demo-server and run it locally; for this,
> > I'd
> > > > > be happy to provide support.
> > > > >
> > > > > Best Regards,
> > > > > Myrle
> > > > >
> > > >
> > >
> >
>
--
*Regards*
*Mohit Kumar Bajoria*
*http://mohitbajoria.com <http://mohitbajoria.com>*
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Markus Geiss <ma...@kuelap.io>.
Yannick is right. (;
With an upcoming update we will have a fix for the index.html issue.
Cheers
Markus
.::Yagni likes a DRY KISS::.
On Thu, Sep 28, 2017 at 12:50 PM Awasum Yannick <ya...@gmail.com>
wrote:
> Hello Nayan,
>
> The problem is you are trying to access it with incomplete URL:
> https://training.kuelap.io:8443/
>
> You have to use the complete URL each time you want to login:
> https://training.kuelap.io:8443/index.html
>
> With the "index.html" included.
>
> Thanks
>
>
> On Thu, Sep 28, 2017 at 11:42 AM, Nayan Ambali <na...@rupie.co> wrote:
>
> > Hello Markus,
> >
> > Hope you are doing good.
> >
> > Eager to have look at Gen 3. I am getting below error when I visit the
> URL
> > above URL
> >
> > Whitelabel Error Page
> >
> > This application has no explicit mapping for /error, so you are seeing
> this
> > as a fallback.
> > Thu Sep 28 10:36:56 UTC 2017
> > There was an unexpected error (type=Not Found, status=404).
> > Not Found
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Sep 28, 2017 at 1:20 PM, Markus Geiss <ma...@kuelap.io>
> > wrote:
> >
> > > Hey all,
> > >
> > > I believe that engaging business people into the discussion is a good
> > > thing.
> > >
> > > Saying this, Kuelap decided to offer a demo site where you can look at
> > the
> > > application.
> > >
> > > We will wipe all existing data with every new update, to keep the demo
> > > small and clean.
> > >
> > > Here you'll find it:
> > >
> > > https://training.kuelap.io:8443/index.html
> > >
> > > Tenant: playground
> > > Username: demo
> > > Password ven3t1@n
> > >
> > > Cheers
> > >
> > > Markus
> > >
> > > .::Yagni likes a DRY KISS::.
> > >
> > > On Thu, Sep 28, 2017 at 9:15 AM Myrle Krantz <my...@apache.org> wrote:
> > >
> > > > Hey Ed, Ashok, (and Markus)
> > > >
> > > > On Wed, Sep 27, 2017 at 6:31 PM, Ed Cable <ed...@mifos.org> wrote:
> > > >
> > > > > All that being said, I know that Rajan had a playground/demo site
> > that
> > > he
> > > > > was testing on for GSOC. Can we share this demo instance with the
> > > broader
> > > > > community so they could have a sense of where the Apache Fineract
> CN
> > is
> > > > at
> > > > > functionally?
> > > >
> > > > That demo site is a QA site hosted by Kuelap (and subject to frequent
> > > > updates and service hickups). Markus will have to answer as to
> > > > whether he wants Kuelap's SRE to set up a demo-site for evaluation
> for
> > > > y'all.
> > > >
> > > > Alternately, Mifos could host a demo instance. Or Ashok could follow
> > > > the instructions for the demo-server and run it locally; for this,
> I'd
> > > > be happy to provide support.
> > > >
> > > > Best Regards,
> > > > Myrle
> > > >
> > >
> >
>
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Awasum Yannick <ya...@gmail.com>.
Hello Nayan,
The problem is you are trying to access it with incomplete URL:
https://training.kuelap.io:8443/
You have to use the complete URL each time you want to login:
https://training.kuelap.io:8443/index.html
With the "index.html" included.
Thanks
On Thu, Sep 28, 2017 at 11:42 AM, Nayan Ambali <na...@rupie.co> wrote:
> Hello Markus,
>
> Hope you are doing good.
>
> Eager to have look at Gen 3. I am getting below error when I visit the URL
> above URL
>
> Whitelabel Error Page
>
> This application has no explicit mapping for /error, so you are seeing this
> as a fallback.
> Thu Sep 28 10:36:56 UTC 2017
> There was an unexpected error (type=Not Found, status=404).
> Not Found
>
>
>
>
>
>
>
>
>
> On Thu, Sep 28, 2017 at 1:20 PM, Markus Geiss <ma...@kuelap.io>
> wrote:
>
> > Hey all,
> >
> > I believe that engaging business people into the discussion is a good
> > thing.
> >
> > Saying this, Kuelap decided to offer a demo site where you can look at
> the
> > application.
> >
> > We will wipe all existing data with every new update, to keep the demo
> > small and clean.
> >
> > Here you'll find it:
> >
> > https://training.kuelap.io:8443/index.html
> >
> > Tenant: playground
> > Username: demo
> > Password ven3t1@n
> >
> > Cheers
> >
> > Markus
> >
> > .::Yagni likes a DRY KISS::.
> >
> > On Thu, Sep 28, 2017 at 9:15 AM Myrle Krantz <my...@apache.org> wrote:
> >
> > > Hey Ed, Ashok, (and Markus)
> > >
> > > On Wed, Sep 27, 2017 at 6:31 PM, Ed Cable <ed...@mifos.org> wrote:
> > >
> > > > All that being said, I know that Rajan had a playground/demo site
> that
> > he
> > > > was testing on for GSOC. Can we share this demo instance with the
> > broader
> > > > community so they could have a sense of where the Apache Fineract CN
> is
> > > at
> > > > functionally?
> > >
> > > That demo site is a QA site hosted by Kuelap (and subject to frequent
> > > updates and service hickups). Markus will have to answer as to
> > > whether he wants Kuelap's SRE to set up a demo-site for evaluation for
> > > y'all.
> > >
> > > Alternately, Mifos could host a demo instance. Or Ashok could follow
> > > the instructions for the demo-server and run it locally; for this, I'd
> > > be happy to provide support.
> > >
> > > Best Regards,
> > > Myrle
> > >
> >
>
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Nayan Ambali <na...@rupie.co>.
Hello Markus,
Hope you are doing good.
Eager to have look at Gen 3. I am getting below error when I visit the URL
above URL
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this
as a fallback.
Thu Sep 28 10:36:56 UTC 2017
There was an unexpected error (type=Not Found, status=404).
Not Found
On Thu, Sep 28, 2017 at 1:20 PM, Markus Geiss <ma...@kuelap.io>
wrote:
> Hey all,
>
> I believe that engaging business people into the discussion is a good
> thing.
>
> Saying this, Kuelap decided to offer a demo site where you can look at the
> application.
>
> We will wipe all existing data with every new update, to keep the demo
> small and clean.
>
> Here you'll find it:
>
> https://training.kuelap.io:8443/index.html
>
> Tenant: playground
> Username: demo
> Password ven3t1@n
>
> Cheers
>
> Markus
>
> .::Yagni likes a DRY KISS::.
>
> On Thu, Sep 28, 2017 at 9:15 AM Myrle Krantz <my...@apache.org> wrote:
>
> > Hey Ed, Ashok, (and Markus)
> >
> > On Wed, Sep 27, 2017 at 6:31 PM, Ed Cable <ed...@mifos.org> wrote:
> >
> > > All that being said, I know that Rajan had a playground/demo site that
> he
> > > was testing on for GSOC. Can we share this demo instance with the
> broader
> > > community so they could have a sense of where the Apache Fineract CN is
> > at
> > > functionally?
> >
> > That demo site is a QA site hosted by Kuelap (and subject to frequent
> > updates and service hickups). Markus will have to answer as to
> > whether he wants Kuelap's SRE to set up a demo-site for evaluation for
> > y'all.
> >
> > Alternately, Mifos could host a demo instance. Or Ashok could follow
> > the instructions for the demo-server and run it locally; for this, I'd
> > be happy to provide support.
> >
> > Best Regards,
> > Myrle
> >
>
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Markus Geiss <ma...@kuelap.io>.
Hey all,
I believe that engaging business people into the discussion is a good thing.
Saying this, Kuelap decided to offer a demo site where you can look at the
application.
We will wipe all existing data with every new update, to keep the demo
small and clean.
Here you'll find it:
https://training.kuelap.io:8443/index.html
Tenant: playground
Username: demo
Password ven3t1@n
Cheers
Markus
.::Yagni likes a DRY KISS::.
On Thu, Sep 28, 2017 at 9:15 AM Myrle Krantz <my...@apache.org> wrote:
> Hey Ed, Ashok, (and Markus)
>
> On Wed, Sep 27, 2017 at 6:31 PM, Ed Cable <ed...@mifos.org> wrote:
>
> > All that being said, I know that Rajan had a playground/demo site that he
> > was testing on for GSOC. Can we share this demo instance with the broader
> > community so they could have a sense of where the Apache Fineract CN is
> at
> > functionally?
>
> That demo site is a QA site hosted by Kuelap (and subject to frequent
> updates and service hickups). Markus will have to answer as to
> whether he wants Kuelap's SRE to set up a demo-site for evaluation for
> y'all.
>
> Alternately, Mifos could host a demo instance. Or Ashok could follow
> the instructions for the demo-server and run it locally; for this, I'd
> be happy to provide support.
>
> Best Regards,
> Myrle
>
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Myrle Krantz <my...@apache.org>.
Hey Ed, Ashok, (and Markus)
On Wed, Sep 27, 2017 at 6:31 PM, Ed Cable <ed...@mifos.org> wrote:
> All that being said, I know that Rajan had a playground/demo site that he
> was testing on for GSOC. Can we share this demo instance with the broader
> community so they could have a sense of where the Apache Fineract CN is at
> functionally?
That demo site is a QA site hosted by Kuelap (and subject to frequent
updates and service hickups). Markus will have to answer as to
whether he wants Kuelap's SRE to set up a demo-site for evaluation for
y'all.
Alternately, Mifos could host a demo instance. Or Ashok could follow
the instructions for the demo-server and run it locally; for this, I'd
be happy to provide support.
Best Regards,
Myrle
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Ed Cable <ed...@mifos.org>.
Myrle,
See my reply inline.
> > I do wish there would have been some discussion
>
> This is a discuss thread, and it can continue as long as discussion is
> needed. What questions do we still need to cover?
>
>
I think the previous presentations, whitepapers, and the recent wiki pages
you've put up describing the project structure help to nicely articulate
the technical benefits and rationale for the new architecture.
I do agree with Ashok's concerns to an extent that for business users, it
would be worthwhile to see a demo site to understand where Apache Fineract
CN is currently at and it will also help to show the vision of where it's
going for the future. I don't fully agree though that access to a demo site
should be the most telling decision factor as it will only be when we get
the new codebase into Apache that we can really scale it's breadth and
demonstrate its potential.
All that being said, I know that Rajan had a playground/demo site that he
was testing on for GSOC. Can we share this demo instance with the broader
community so they could have a sense of where the Apache Fineract CN is at
functionally?
To conclude though, I believe that amongst our committers and PMC, they've
been sufficiently educated and updated that we could call a vote and if
they've not raised any questions or concerns to please do so now.
Ed
--
*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: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Myrle Krantz <my...@apache.org>.
Hey Ed,
On Tue, Sep 26, 2017 at 7:16 PM, Ed Cable <ed...@mifos.org> wrote:
> I myself apologize that I hadn't replied or acknowledged your email. I
> thank you for taking that step and documenting all that needs to be done.
NP, we've all had a lot to do.
> I do wish there would have been some discussion
This is a discuss thread, and it can continue as long as discussion is
needed. What questions do we still need to cover?
> I foresee no obstacles in the software grant process from the Mifos side. I
> will get approval from my board but they are all in favor so no issues
> there.
That's good news.
Best Regards,
Myrle
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Ed Cable <ed...@mifos.org>.
Myrle,
I myself apologize that I hadn't replied or acknowledged your email. I
thank you for taking that step and documenting all that needs to be done.
I do wish there would have been some discussion but I do think the last
thread we had was sufficient discussion and interest and enthusiasm and
that we could call for a vote amongst the committers. There was a lot to
absorb in the email and I think once we have the vote and software
clearance process underway, we could start separate threads and align
individuals in separate working groups to tackle some of the remaining
items C through H.
I foresee no obstacles in the software grant process from the Mifos side. I
will get approval from my board but they are all in favor so no issues
there.
Ed
On Tue, Sep 26, 2017 at 1:39 AM, Myrle Krantz <my...@apache.org> wrote:
> I've gotten no response on this, and given the previously displayed
> enthusiasm, I'm a little surprised.
>
> Ed, do you foresee any problems with the software grant process from
> Mifos? Is that something you decide, or will you need to get the OK
> from your board?
>
> Thanks,
> Myrle
>
> On Tue, Sep 19, 2017 at 10:18 AM, Myrle Krantz <my...@apache.org> wrote:
> > Hey all,
> >
> > I'd like to begin discussion to bring Mifos I/O in to the Fineract
> > project as Apache Fineract CN. I propose the following process to get
> > us there. Note that this is a discussion thread. I will send a
> > voting thread once discussion has died down.
> >
> > A.) Discuss and vote to accept the code into the Fineract project and
> > begin the Apache processes. We should not proceed beyond this point
> > until at least 2/3 of the Committers have voted. My preference is that
> > we reach 100%.
> > B.) Go through the IP clearance process (1) for that code via the
> > Incubator. This will probably require at least:
> > a.) A software grant from the Mifos Initiative
> > b.) A CLA from Kuelap
> > c.) An iCLAs from Mark van Veen, Nina Delvos, and Riana Allen.
> > d.) A thorough check through of the code to make sure those of us
> > working on it haven't missed any licensing issues.
> > C.) Discuss the necessary infrastructure for the code, and place the
> > corresponding requests with the INFRA team. This will at least include
> > JIRA, and github.
> > D.) Move the code and rename the packages from Mifos to Fineract.
> > E.) After migrating the code resolve any release-blockers which might
> remain.
> > F.) Go through the final QA/Release process for the new code base.
> > Release under the name Fineract CN to disambiguate from the current
> > Fineract code base.
> > G.) Announce and document.
> > H.) goto E.
> >
> > I am *not* proposing that we stop development on the existing Fineract
> > code base. That is a decision for each individual contributor to
> > make, and it's not a decision that needs to be made at this time.
> >
> > This will be a long process. It may be late October before we are even
> > at C. Please be patient once we get going.
> >
> > Do you see anything that I've missed? Do you have any concerns?
> >
> > Best Regards,
> > Myrle Krantz
> > Individual Contributor, Apache Fineract
> >
> > 1.) http://incubator.apache.org/ip-clearance/
>
--
*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: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Myrle Krantz <my...@apache.org>.
I've gotten no response on this, and given the previously displayed
enthusiasm, I'm a little surprised.
Ed, do you foresee any problems with the software grant process from
Mifos? Is that something you decide, or will you need to get the OK
from your board?
Thanks,
Myrle
On Tue, Sep 19, 2017 at 10:18 AM, Myrle Krantz <my...@apache.org> wrote:
> Hey all,
>
> I'd like to begin discussion to bring Mifos I/O in to the Fineract
> project as Apache Fineract CN. I propose the following process to get
> us there. Note that this is a discussion thread. I will send a
> voting thread once discussion has died down.
>
> A.) Discuss and vote to accept the code into the Fineract project and
> begin the Apache processes. We should not proceed beyond this point
> until at least 2/3 of the Committers have voted. My preference is that
> we reach 100%.
> B.) Go through the IP clearance process (1) for that code via the
> Incubator. This will probably require at least:
> a.) A software grant from the Mifos Initiative
> b.) A CLA from Kuelap
> c.) An iCLAs from Mark van Veen, Nina Delvos, and Riana Allen.
> d.) A thorough check through of the code to make sure those of us
> working on it haven't missed any licensing issues.
> C.) Discuss the necessary infrastructure for the code, and place the
> corresponding requests with the INFRA team. This will at least include
> JIRA, and github.
> D.) Move the code and rename the packages from Mifos to Fineract.
> E.) After migrating the code resolve any release-blockers which might remain.
> F.) Go through the final QA/Release process for the new code base.
> Release under the name Fineract CN to disambiguate from the current
> Fineract code base.
> G.) Announce and document.
> H.) goto E.
>
> I am *not* proposing that we stop development on the existing Fineract
> code base. That is a decision for each individual contributor to
> make, and it's not a decision that needs to be made at this time.
>
> This will be a long process. It may be late October before we are even
> at C. Please be patient once we get going.
>
> Do you see anything that I've missed? Do you have any concerns?
>
> Best Regards,
> Myrle Krantz
> Individual Contributor, Apache Fineract
>
> 1.) http://incubator.apache.org/ip-clearance/
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Myrle Krantz <my...@apache.org>.
Hey all,
I believe we are finished with this discussion.
As the next step, I'm going to start the vote. I will close the vote
after 72 hours or 2/3 of committers have voted (whichever comes
later). When I call the vote I will individually list +1's, 0's,
-1's, and abstentions.
Best Regards,
Myrle
Committer, Apache Fineract
On Mon, Oct 16, 2017 at 8:33 PM, Phil Steitz <ph...@gmail.com> wrote:
> On 10/16/17 4:32 AM, Myrle Krantz wrote:
>> Hey Fineracters,
>>
>> Before I bring Fineract CN to vote, I need to bring up one last topic
>> which is painful for us all: hibernate-jpa
>>
>> I know: nobody wants to talk about that, but we don't really have a choice.
>>
>> Most of the Fineract CN services have a run-time-only dependency on
>> hibernate-jpa. Unlike the other hibernate libraries we use,
>> hibernate-jpa is an LGPL library. The Apache Software Foundation does
>> not allow LGPL source dependencies because of the legal risks they
>> pose to potential commercial users of our code. LGPL is a category X
>> license. Hibernate-jpa implements a JSR specification which is
>> available under the CDDL 1.1 and TCK. CDDL 1.1 is a category B
>> license (1); it won't block us releasing dependent code. Because the
>> JPA interface is licensed via a category B license, and because
>> FineractCN does not use any "non-JPA" features of hibernate, the
>> FineractCN service code has no compile-time dependencies to a category
>> X license. Component-test code is a different matter. Our
>> component-tests do depend on hibernate-jpa via
>> spring-boot-starter-data-jpa.
>>
>> We might argue that if we only make a source release of the service
>> and API code and not the component-test code, that we are within
>> policy. Binary releases of FineractCN would be ruled out, or someone
>> would have to do the pre-release testing work with OpenJPA. This
>> approach is complicated by our multiple-repository approach. We need
>> to produce artifacts from "lower" projects before we can build
>> "higher" projects. And building would be so much easier if we could
>> place those artifacts in an artifactory rather than making everyone
>> build everything every time. But even build-snapshot artifacts could
>> be considered a source release. Likewise, running integration tests
>> would be easier if we could reference build artifacts in an
>> artifactory rather than locally.
>>
>> It remains to be seen if the ASF would accept this argument and this
>> approach. If the ASF does not accept this approach, there are two
>> potential paths forward:
>>
>> a.) We bring the source into the project, then resolve this issue
>> before the first release.
>> b.) We resolve this issue before we accept the source into the project.
>>
>> I personally would prefer a, so that we can get back into on-list
>> development. I don't know if the ASF would accept that approach
>> though.
>>
>> Does anybody else have an opinion? Am I missing any important
>> information? Please share.
>
> Hi Merle,
>
> I don't see any problem at all with a). This happens frequently in
> the Incubator, where initially granted code has dependencies on
> libraries with unapproved licenses. Step 0 is to get the code in so
> getting it ready for release can be done by the community. Getting
> the code granted and formally incorporated into the project is
> important. Accepting the grant does not commit the project to
> actually releasing it or anything based on it. It just means that
> it is part of the project and you can point people at the sources,
> accept patches under the ASF CLA, etc. Once the code is granted
> and accepted into the project, you can decide how to solve the
> dependency problems. Unless the sources that you are bringing in
> themselves include LGPL code, you are not violating any ASF policy
> by incorporating them into your project. You are correct, though,
> that ASF policy [1] forbids release of code that has non-optional
> LGPL dependencies and you will need to find a way to handle that
> before first release.
>
> Phil
>
> [1] https://www.apache.org/legal/resolved.html#optional
>
>
>>
>> Greetings,
>> Myrle
>>
>> 1.) https://www.apache.org/legal/resolved.html
>>
>> On Tue, Sep 19, 2017 at 10:18 AM, Myrle Krantz <my...@apache.org> wrote:
>>> Hey all,
>>>
>>> I'd like to begin discussion to bring Mifos I/O in to the Fineract
>>> project as Apache Fineract CN. I propose the following process to get
>>> us there. Note that this is a discussion thread. I will send a
>>> voting thread once discussion has died down.
>>>
>>> A.) Discuss and vote to accept the code into the Fineract project and
>>> begin the Apache processes. We should not proceed beyond this point
>>> until at least 2/3 of the Committers have voted. My preference is that
>>> we reach 100%.
>>> B.) Go through the IP clearance process (1) for that code via the
>>> Incubator. This will probably require at least:
>>> a.) A software grant from the Mifos Initiative
>>> b.) A CLA from Kuelap
>>> c.) An iCLAs from Mark van Veen, Nina Delvos, and Riana Allen.
>>> d.) A thorough check through of the code to make sure those of us
>>> working on it haven't missed any licensing issues.
>>> C.) Discuss the necessary infrastructure for the code, and place the
>>> corresponding requests with the INFRA team. This will at least include
>>> JIRA, and github.
>>> D.) Move the code and rename the packages from Mifos to Fineract.
>>> E.) After migrating the code resolve any release-blockers which might remain.
>>> F.) Go through the final QA/Release process for the new code base.
>>> Release under the name Fineract CN to disambiguate from the current
>>> Fineract code base.
>>> G.) Announce and document.
>>> H.) goto E.
>>>
>>> I am *not* proposing that we stop development on the existing Fineract
>>> code base. That is a decision for each individual contributor to
>>> make, and it's not a decision that needs to be made at this time.
>>>
>>> This will be a long process. It may be late October before we are even
>>> at C. Please be patient once we get going.
>>>
>>> Do you see anything that I've missed? Do you have any concerns?
>>>
>>> Best Regards,
>>> Myrle Krantz
>>> Individual Contributor, Apache Fineract
>>>
>>> 1.) http://incubator.apache.org/ip-clearance/
>
>
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Phil Steitz <ph...@gmail.com>.
On 10/16/17 4:32 AM, Myrle Krantz wrote:
> Hey Fineracters,
>
> Before I bring Fineract CN to vote, I need to bring up one last topic
> which is painful for us all: hibernate-jpa
>
> I know: nobody wants to talk about that, but we don't really have a choice.
>
> Most of the Fineract CN services have a run-time-only dependency on
> hibernate-jpa. Unlike the other hibernate libraries we use,
> hibernate-jpa is an LGPL library. The Apache Software Foundation does
> not allow LGPL source dependencies because of the legal risks they
> pose to potential commercial users of our code. LGPL is a category X
> license. Hibernate-jpa implements a JSR specification which is
> available under the CDDL 1.1 and TCK. CDDL 1.1 is a category B
> license (1); it won't block us releasing dependent code. Because the
> JPA interface is licensed via a category B license, and because
> FineractCN does not use any "non-JPA" features of hibernate, the
> FineractCN service code has no compile-time dependencies to a category
> X license. Component-test code is a different matter. Our
> component-tests do depend on hibernate-jpa via
> spring-boot-starter-data-jpa.
>
> We might argue that if we only make a source release of the service
> and API code and not the component-test code, that we are within
> policy. Binary releases of FineractCN would be ruled out, or someone
> would have to do the pre-release testing work with OpenJPA. This
> approach is complicated by our multiple-repository approach. We need
> to produce artifacts from "lower" projects before we can build
> "higher" projects. And building would be so much easier if we could
> place those artifacts in an artifactory rather than making everyone
> build everything every time. But even build-snapshot artifacts could
> be considered a source release. Likewise, running integration tests
> would be easier if we could reference build artifacts in an
> artifactory rather than locally.
>
> It remains to be seen if the ASF would accept this argument and this
> approach. If the ASF does not accept this approach, there are two
> potential paths forward:
>
> a.) We bring the source into the project, then resolve this issue
> before the first release.
> b.) We resolve this issue before we accept the source into the project.
>
> I personally would prefer a, so that we can get back into on-list
> development. I don't know if the ASF would accept that approach
> though.
>
> Does anybody else have an opinion? Am I missing any important
> information? Please share.
Hi Merle,
I don't see any problem at all with a). This happens frequently in
the Incubator, where initially granted code has dependencies on
libraries with unapproved licenses. Step 0 is to get the code in so
getting it ready for release can be done by the community. Getting
the code granted and formally incorporated into the project is
important. Accepting the grant does not commit the project to
actually releasing it or anything based on it. It just means that
it is part of the project and you can point people at the sources,
accept patches under the ASF CLA, etc. Once the code is granted
and accepted into the project, you can decide how to solve the
dependency problems. Unless the sources that you are bringing in
themselves include LGPL code, you are not violating any ASF policy
by incorporating them into your project. You are correct, though,
that ASF policy [1] forbids release of code that has non-optional
LGPL dependencies and you will need to find a way to handle that
before first release.
Phil
[1] https://www.apache.org/legal/resolved.html#optional
>
> Greetings,
> Myrle
>
> 1.) https://www.apache.org/legal/resolved.html
>
> On Tue, Sep 19, 2017 at 10:18 AM, Myrle Krantz <my...@apache.org> wrote:
>> Hey all,
>>
>> I'd like to begin discussion to bring Mifos I/O in to the Fineract
>> project as Apache Fineract CN. I propose the following process to get
>> us there. Note that this is a discussion thread. I will send a
>> voting thread once discussion has died down.
>>
>> A.) Discuss and vote to accept the code into the Fineract project and
>> begin the Apache processes. We should not proceed beyond this point
>> until at least 2/3 of the Committers have voted. My preference is that
>> we reach 100%.
>> B.) Go through the IP clearance process (1) for that code via the
>> Incubator. This will probably require at least:
>> a.) A software grant from the Mifos Initiative
>> b.) A CLA from Kuelap
>> c.) An iCLAs from Mark van Veen, Nina Delvos, and Riana Allen.
>> d.) A thorough check through of the code to make sure those of us
>> working on it haven't missed any licensing issues.
>> C.) Discuss the necessary infrastructure for the code, and place the
>> corresponding requests with the INFRA team. This will at least include
>> JIRA, and github.
>> D.) Move the code and rename the packages from Mifos to Fineract.
>> E.) After migrating the code resolve any release-blockers which might remain.
>> F.) Go through the final QA/Release process for the new code base.
>> Release under the name Fineract CN to disambiguate from the current
>> Fineract code base.
>> G.) Announce and document.
>> H.) goto E.
>>
>> I am *not* proposing that we stop development on the existing Fineract
>> code base. That is a decision for each individual contributor to
>> make, and it's not a decision that needs to be made at this time.
>>
>> This will be a long process. It may be late October before we are even
>> at C. Please be patient once we get going.
>>
>> Do you see anything that I've missed? Do you have any concerns?
>>
>> Best Regards,
>> Myrle Krantz
>> Individual Contributor, Apache Fineract
>>
>> 1.) http://incubator.apache.org/ip-clearance/
Re: [DISCUSS] Begin the process for bringing in Mifos I/O as Apache
Fineract CN
Posted by Myrle Krantz <my...@apache.org>.
Hey Fineracters,
Before I bring Fineract CN to vote, I need to bring up one last topic
which is painful for us all: hibernate-jpa
I know: nobody wants to talk about that, but we don't really have a choice.
Most of the Fineract CN services have a run-time-only dependency on
hibernate-jpa. Unlike the other hibernate libraries we use,
hibernate-jpa is an LGPL library. The Apache Software Foundation does
not allow LGPL source dependencies because of the legal risks they
pose to potential commercial users of our code. LGPL is a category X
license. Hibernate-jpa implements a JSR specification which is
available under the CDDL 1.1 and TCK. CDDL 1.1 is a category B
license (1); it won't block us releasing dependent code. Because the
JPA interface is licensed via a category B license, and because
FineractCN does not use any "non-JPA" features of hibernate, the
FineractCN service code has no compile-time dependencies to a category
X license. Component-test code is a different matter. Our
component-tests do depend on hibernate-jpa via
spring-boot-starter-data-jpa.
We might argue that if we only make a source release of the service
and API code and not the component-test code, that we are within
policy. Binary releases of FineractCN would be ruled out, or someone
would have to do the pre-release testing work with OpenJPA. This
approach is complicated by our multiple-repository approach. We need
to produce artifacts from "lower" projects before we can build
"higher" projects. And building would be so much easier if we could
place those artifacts in an artifactory rather than making everyone
build everything every time. But even build-snapshot artifacts could
be considered a source release. Likewise, running integration tests
would be easier if we could reference build artifacts in an
artifactory rather than locally.
It remains to be seen if the ASF would accept this argument and this
approach. If the ASF does not accept this approach, there are two
potential paths forward:
a.) We bring the source into the project, then resolve this issue
before the first release.
b.) We resolve this issue before we accept the source into the project.
I personally would prefer a, so that we can get back into on-list
development. I don't know if the ASF would accept that approach
though.
Does anybody else have an opinion? Am I missing any important
information? Please share.
Greetings,
Myrle
1.) https://www.apache.org/legal/resolved.html
On Tue, Sep 19, 2017 at 10:18 AM, Myrle Krantz <my...@apache.org> wrote:
> Hey all,
>
> I'd like to begin discussion to bring Mifos I/O in to the Fineract
> project as Apache Fineract CN. I propose the following process to get
> us there. Note that this is a discussion thread. I will send a
> voting thread once discussion has died down.
>
> A.) Discuss and vote to accept the code into the Fineract project and
> begin the Apache processes. We should not proceed beyond this point
> until at least 2/3 of the Committers have voted. My preference is that
> we reach 100%.
> B.) Go through the IP clearance process (1) for that code via the
> Incubator. This will probably require at least:
> a.) A software grant from the Mifos Initiative
> b.) A CLA from Kuelap
> c.) An iCLAs from Mark van Veen, Nina Delvos, and Riana Allen.
> d.) A thorough check through of the code to make sure those of us
> working on it haven't missed any licensing issues.
> C.) Discuss the necessary infrastructure for the code, and place the
> corresponding requests with the INFRA team. This will at least include
> JIRA, and github.
> D.) Move the code and rename the packages from Mifos to Fineract.
> E.) After migrating the code resolve any release-blockers which might remain.
> F.) Go through the final QA/Release process for the new code base.
> Release under the name Fineract CN to disambiguate from the current
> Fineract code base.
> G.) Announce and document.
> H.) goto E.
>
> I am *not* proposing that we stop development on the existing Fineract
> code base. That is a decision for each individual contributor to
> make, and it's not a decision that needs to be made at this time.
>
> This will be a long process. It may be late October before we are even
> at C. Please be patient once we get going.
>
> Do you see anything that I've missed? Do you have any concerns?
>
> Best Regards,
> Myrle Krantz
> Individual Contributor, Apache Fineract
>
> 1.) http://incubator.apache.org/ip-clearance/