You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Markus Geiss <ma...@apache.org> on 2018/02/15 16:40:12 UTC
Re: Current Development Status of Apache Fineract CN
Hey all,
I've learned that my last statement was a bit misleading, and community
members seemed to be blocked by this.
I do apologize, because it never was my intention to fend or block anybody
from contributing.
As of yesterday, all pending code was send as a PR to Fineract CN
repositories at the Apache Gitbox.
Cheers
Markus
.::Yagni likes a DRY KISS::.
On Fri, Jan 19, 2018 at 8:00 AM Myrle Krantz <my...@apache.org> wrote:
> Hey Markus,
>
> Developing in a hidden repo against requirements not visible to the
> Fineract community is not open source development.
>
> Philosophy aside, it prevents other people from contributing to the
> project. That undermines our ability to energize and grow our community.
>
> I share the blame for this. All the more reason that I should try to set
> this right. I will upload the Mifos IO source to the Apache repos on
> Monday. Then the community will be welcome to join in development including
> renames of the packages and a migration to OpenJPA. At that point it will
> gradually become more difficult for Kuelap to merge the changes from your
> repository.
>
> I know how valuable the Kuelap code is. But in the Apache spirit of
> community over code, we cannot indefinitely continue delaying the switch to
> open source development.
>
> Best Regards,
> Myrle Krantz
> VP, Apache Fineract
>
> On Thu 18. Jan 2018 at 14:44 Markus Geiss <ma...@apache.org> wrote:
>
> > we are currently retrofitted most of the product api's based on the first
> > feedback
> > we got in the field.
> >
> > So yes, once we are done with this ... there will come some changes that
> > also
> > have impact on the API, given we never released a version to production.
> >
> > Cheers
> >
> > Markus
> >
> > .::Yagni likes a DRY KISS::.Cheers
> >
> > On Thu, Jan 18, 2018 at 10:40 AM Ed Cable <ed...@mifos.org> wrote:
> >
> > > Markus,
> > >
> > > Could you provide some visibility into the stability of the current
> > version
> > > of framework that's on Github. I wanted to provide an update during
> > > tomorrow's developer meeting and the folks like Ramesh and Simon who
> are
> > > testing out deployment in the cloud would like be aware if major
> changes
> > > are coming soon - I had heard that there be some major API changes
> coming
> > > Jan 29 but not sure if this is affecting the whole framework or not.
> > >
> > > Thanks,
> > >
> > > Ed
> > >
> >
>
Re: Current Development Status of Apache Fineract CN
Posted by ayuk etta <ay...@apache.org>.
Thanks Markus for doing this, I am sure everyone willing to contribute in
the community has been unblocked by this.
Ayuk
On 16 Feb 2018 7:04 a.m., "Kevin A. McGrail" <ke...@mcgrail.com>
wrote:
> On 2/15/2018 11:40 AM, Markus Geiss wrote:
>
>> I've learned that my last statement was a bit misleading, and community
>> members seemed to be blocked by this.
>>
>> I do apologize, because it never was my intention to fend or block anybody
>> from contributing.
>>
>> As of yesterday, all pending code was send as a PR to Fineract CN
>> repositories at the Apache Gitbox.
>>
> +1
>
Re: Current Development Status of Apache Fineract CN
Posted by "Kevin A. McGrail" <ke...@mcgrail.com>.
On 2/15/2018 11:40 AM, Markus Geiss wrote:
> I've learned that my last statement was a bit misleading, and community
> members seemed to be blocked by this.
>
> I do apologize, because it never was my intention to fend or block anybody
> from contributing.
>
> As of yesterday, all pending code was send as a PR to Fineract CN
> repositories at the Apache Gitbox.
+1