Hi Myrle, Thanks for your message and apologies for the late reply, I blame the holiday season ;-)
*1.) Are you doing something that only you are doing, and that youbelieve should be shared more widely?* Definitely, but we also have had a huge backlog of issues and improvements to merge into the fineract codebase. This is legacy from the switchover from MifosX > Fineract and has accumulated over time. Currently one of my team is working dedicated on getting that sorted. Once that is done, commits made by myself, and others in the team can be put forward again and then merged. *2.) What are the reasons why you aren't doing one of the activities onour "bottleneck" list?* Reason I'm not carrying out many merges on other PR's is that I don't feel confident about the actual use cases of their work, business requirements that are supposed to be met and test cases around it. In a project that is as involved in business processes as this one, I think we should discuss more the aspect of use cases behind PR's, or in case of bug fixes ensuring that the corresponding item contains a clear example of what was wrong before, and then a test case showing that it was fixed. Otherwise it does not provide me with enough confidence to go ahead. Finally it's also just a case of being able to spend the time on this, which currently is just not there for me. Apologies for that. S Sander van der Heyden CTO Musoni Services Mobile (NL): +31 (0)6 14239505 Skype: s.vdheyden Website: musonisystem.com Follow us on Twitter! <https://twitter.com/musonimfi> Postal address: Hillegomstraat 12-14, office 0.09, 1058 LS, Amsterdam, The Netherlands On 29 August 2017 at 15:27, Myrle Krantz <my...@apache.org> wrote: > Hi Fineracters, > > There are 9 PMC members who have not responded (8 if we excuse > Nazeer). As a reminder, the questions are: > > 1.) Are you doing something that only you are doing, and that you > believe should be shared more widely? > 2.) What are the reasons why you aren't merging PRs or helping out > with releases? > > I would appreciate a response. You might also want to say, "I'm too > busy right now", or "I'm waiting for Fineract CN", or "I've lost > confidence that the project can help me achieve my goals". If that's > the case, then it is important information too. > > Thanks, > Myrle Krantz > > On Thu, Aug 17, 2017 at 10:06 AM, Myrle Krantz <my...@apache.org> wrote: > > Hi all, > > > > We have an awesome community. In particular, we've been very good at > > responding to people's request for help getting Fineract working for > > their use cases. But we also have some things we need to work on. > > > > Specifically we have several bottlenecks in our community: > > > > 1.) Only Nazeer is merging PR's. > > 2.) Only Nazeer is serving as a release manager. > > 3.) Only Myrle is moderating the lists (apart from the mentors who > > will eventually step out). > > > > This is called "having a truck factor of one", because if a truck hits > > one of us (or if we win the lottery and decide never to do anything > > for Fineract again), then the entire project would fail (1). This is > > already causing us problems in some areas: for example our PR's are > > backed up > > > > I'm not writing this to lecture anyone. I know there are reasons for > > the way things are. That doesn't mean we should just accept it > > though. > > > > Let's start by improving our understanding of the problem. Would each > > committer please say: > > 1.) Are you doing something that only you are doing, and that you > > believe should be shared more widely? > > 2.) What are the reasons why you aren't doing one of the activities on > > our "bottleneck" list? > > > > > > I'll start: > > 1.) List moderation. > > 2.) I'm not merging PR's because I'm not sufficiently familiar with > > the current generation Fineract code to feel comfortable evaluating > > those PR's. I'm not serving as a release manager, because I don't > > have enough insight into when we are release-ready, and because there > > are several pieces of technical knowledge I'd need to acquire to be a > > release manager which I don't yet have. For these reasons, I've > > chosen to focus my energies on Fineract CN instead. > > > > Best Regards, > > Myrle Krantz > > > > P.S. After we have a list of causes, I'll initiate a round of > > discussion about how we can resolve the causes. > > > > 1.) http://www.agileadvice.com/2005/05/15/agilemanagement/truck-factor/ >
