Markus, >> We would still need our own dev list b/c of enhancements we are doing ontop >> of Fineract, we simply need to state clearly where to post what. ; o) For implementer and end users, Mifos release is what it matters, thanks for empathizing our needs, +1 to retaining the mifos-dev list.
Thanks and Regards, Nayan Ambali +91 9591996042 skype: nayangambali On Fri, Apr 1, 2016 at 6:00 PM, Markus Geiß <markus.ge...@live.de> wrote: > Hey all, > I agree with the notification issue, this makes it hard to followthe list in > general. > @Greg What needs to be done to push it to a notifications@ list? > We are currently in a process to get all current community membersfrom our > Mifos dev list over to Fineract. There is a lot going on andwe simply failed > in engaging people to jump over. Maybe this is becausewe never officially > announced the transition, given some misinterpretingof policies, or b/c we > are still don't really have a release. > We would still need our own dev list b/c of enhancements we are doing ontop > of Fineract, we simply need to state clearly where to post what. ; o) > > Best, > > Markus > > .::YAGNI likes a DRY KISS::. > >> From: nayan.amb...@gmail.com >> Date: Fri, 1 Apr 2016 09:57:49 +0000 >> Subject: Re: Concerned about quiet dev@ >> To: dev@fineract.incubator.apache.org >> >> I agree with Keith and Greg, JIRA and Github notifications should not be >> broadcasted through list. Then list will become noisy. >> >> As already there are options for someone interested can always subscribe to >> those notifications directly. >> >> @Keith, i am glad to see you again :) >> >> Thanks >> Nayan Ambali >> >> >> On Fri, Apr 1, 2016, 3:02 PM Keith Woodlock <keithwoodl...@gmail.com> wrote: >> >> > Greg, >> > >> > I agree with your comments in full. In addition I dont see much value in >> > having github and jira notifications channelled through the dev list as I >> > can just use those tools for notifications if I am really interested in >> > seeing update to them. >> > >> > Being bombarded with their notifications through the dev lists de-values >> > the dev list for me. >> > >> > Keith. >> > >> > On Fri, Apr 1, 2016 at 10:21 AM, Greg Stein <gst...@gmail.com> wrote: >> > >> > > Hello all, >> > > >> > > I am growing concerned about the lack of activity on dev@. There is *no* >> > > conversation occurring. Just JIRA notifications and pull requests. >> > > >> > > A community needs conversation. Discussion. Consideration of topics, >> > > roadmaps, and feature development. From what I'm seeing on dev@, none of >> > > this is occurring. >> > > >> > > Some may suggest "discussion is occurring in JIRA", but that does not >> > form >> > > a community. That is a bunch of silo'd conversations on very narrow, >> > > singular topics. >> > > >> > > I raised the concern about JIRA-focus a while back, and am seeing the >> > > outcome now. To *participate* requires JIRA access, or a GitHub account >> > for >> > > pull requests. The ASF prefers a *much* lower bar: send an email. With no >> > > discussion occurring on dev@, it appears very difficult for a potential >> > > participant to "step in" and begin to work with the Fineract community. >> > > >> > > I'll repeat: please use dev@ more, and JIRA less. >> > > >> > > Cheers, >> > > -g >> > > >> > >
