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 <[email protected]> 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 <[email protected]> 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 [email protected] | 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>
