Mailing-List: contact dev-help@fineract.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@fineract.apache.org
MIME-Version: 1.0
In-Reply-To: <CABCVDbLhm=JS38GGep_JK=5LmaNfdAerspqGSs12Wknud6Lf2Q@mail.gmail.com>
References: <CAJdZ4O2vOrk_srCnrggg9PvGP4iX1i0TgZsQyP_2soR4y_0D_Q@mail.gmail.com>
 <CABCVDbLhm=JS38GGep_JK=5LmaNfdAerspqGSs12Wknud6Lf2Q@mail.gmail.com>
From: Ed Cable <edcable@mifos.org>
Date: Tue, 22 Aug 2017 06:12:11 -0700
Message-ID: <CAPnWRThGCmGG-g7Pn8-shURfWeyKpXqNB8gT6S5OX4nQuP6MPw@mail.gmail.com>
Subject: Re: Upping our truck factor
To: Dev <dev@fineract.apache.org>
Content-Type: multipart/alternative; boundary="f403045ec28618e1ca055757598d"

--f403045ec28618e1ca055757598d
Content-Type: text/plain; charset="UTF-8"

1.) Are you doing something that only you are doing, and that you
believe should be shared more widely?

- Requirements Gathering -  both on Apache Fineract and as we move towards
Apache Fineract CN - we need to have open discussions with community
members on what is needed by users and what requirements partners are
building. This includes discussing use cases, identifying solutions, and
designing mockups
- Triage & Feature Prioritization - this is also shared by new committer,
Santosh, and Nazeer - but we welcome other community members to join weekly
meetings to triage new bugs and discuss and prioritize feature requests.
- Volunteer Engagement - we've all seen and discussed on this list that it
goes a long way when properly onboarding and engaging a volunteer, I have
phone calls with new volunteers and try to connect each one with an
individual project. I welcome others in helping parcel out manageable tasks
for volunteers and helping project manage/mentor volunteers as they're
making contribution. We have a lot of interest in contributing but need to
help some more of those individuals.


2.) What are the reasons why you aren't doing one of the activities on
our "bottleneck" list?


- List Moderation - let me know how I can help more here - but I think I am
playing a role with moderation - thus far I try to respond to new community
members, I guide traffic to the mailing list that comes from other sources,
and I try to ensure emails get a response when I can't reply to them by
escalating them to others.

For the release management and merging of PRs, I am engaged on a
non-technical level already. For the actual making of the release, I am now
trying to get comfortable with signing off and verifying a new elease and
hopefully can help with actual releases in future.

Ed


On Mon, Aug 21, 2017 at 6:57 AM, Markus Geiss <markus.geiss@kuelap.io>
wrote:

> Hey all,
>
> here are my answers. (;
>
> 1.) Are you doing something that only you are doing, and that you
> believe should be shared more widely?
>
> No.
>
> 2.) What are the reasons why you aren't doing one of the activities on
> our "bottleneck" list?
>
> I don't feel comfortable enough to merge pull requests on a functionality
> side.
> I can offer to provide validations on a code formatting and best practices
> basis,
> but if it comes to how things fit into the current set of products I'm
> lacking skills.
>
> It would be possible for me to spend some time doing list moderation, but
> I'm
> not 100% sure what is needed. If somebody can shed a light on this, I'm
> happy
> to jump in.
>
> Cheers
>
> Markus
>
> On Thu, Aug 17, 2017 at 10:06 AM Myrle Krantz <myrle@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/
> >
>


-- 
*Ed Cable*
President/CEO, Mifos Initiative
edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
<(484)%20477-8649>

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

--f403045ec28618e1ca055757598d--