On 2019/10/04 19:10:41, Kenneth Knowles <[email protected]> wrote:
> I've been asking and searching around about friction logs* and here's some
> resources that helped. Google has blogged about it:
> https://devrel.net/developer-experience/an-introduction-to-friction-logging.
> It does seem to be a mostly Google-specific name for the concept, so if
> anyone knows what other people call this that would help to find more
> examples and ideas.
>
> Here are some public examples:
> -
> https://docs.google.com/document/d/1HVG3t-mgGZKU4iMeguTWGejbnQ54qUTXwdCFkA5xHG0/edit
> - https://github.com/kubeflow/kubeflow/issues/927
> - https://github.com/istio/istio.io/issues/1299
>
> I think the "bug filed with pain points" is not the right model, but the
> green/yellow/red journaling seems applicable. The templates are very
> minimal so maybe need to think about how this work is different from the
> usual software usability usage.
>
> Two extensions that I think fit well with this project are (1) separating
> the logger from the person going through the process (2) having multiple
> loggers.
>
> And what do you think about separate friction logs for the intern as well
> as the mentor?
>
> Kenn
>
> *not these: https://www.smokinlicious.com/friction-logs.html
>
> On Tue, Sep 10, 2019 at 11:41 AM Matt Sicker <[email protected]> wrote:
>
> > Oh, I like that idea! We should certainly try to get both rough and
> > smooth aspects of the friction (because nothing is frictionless except
> > for spherical cows in vacuum, right?).
> >
> > On Tue, 10 Sep 2019 at 02:33, Dirk-Willem van Gulik
> > <[email protected]> wrote:
> > >
> > > For what it is worth:
> > >
> > > Matt wrote:
> > >
> > > > 1. A friction log is a list of struggles that occur during the
> > > > onboarding of a new contributor to a project. This could include
> > >
> > > One could also turn this around - i.e. make it about hurdles and what
> > would make things smoother/easier - as opposed to a `struggle'.
> > >
> > > > things like lack of or unclear documentation, setup issues, community
> > > > issues, language issues, and anything else that's intimidating or
> > > > slows down the process in getting up to speed as a contributor to a
> > > > project.
> > >
> > >
> > > > .. snipped the process bit of themail.
> > >
> > > And emphasise that this is to help others have a smoother path `in'.
> > >
> > > I've found that in a more corporate setting - that the latter generally
> > elicits more energy, going the extra mile & pride and all that.
> > >
> > > And more than once found that I accidentally created a body of
> > new-people buddies for the next generation.
> > >
> > > Dw
> > >
> >
> >
> > --
> > Matt Sicker <[email protected]>
> >
>
