Any other ideas? Or is my description defined well enough? On Tue, Sep 3, 2019 at 16:30, Matt Sicker <[email protected]> wrote:
> I'll start with my thoughts. > > 1. A friction log is a list of struggles that occur during the > onboarding of a new contributor to a project. This could include > 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. > > 2. One option could be to use Jira or GitHub issues. Another could be > wiki pages on our Confluence space. Another option could be some sort > of spreadsheet if the answers collected need to be somewhat private > yet accessible to the committee here (and interested members?). > > 3. Nope. I'm just sort of winging it here. > > On Tue, 3 Sep 2019 at 15:44, Katia Rojas <[email protected]> wrote: > > > > Hello folks, > > > > As you may know, we are currently participating in the Outreachy program! > > > > To make this experience more enriching we decided to capture a > contribution > > friction log from the interns. To do so, we need help creating a template > > that allows us to fulfil this task. > > > > Could you help us answering the following questions: > > > > > > 1. > > > > What is a friction log? > > 2. > > > > How can we track it? > > 3. > > > > Do you have any experience with friction log, could you share it with > us? > > > > > > This discussion is open for 72 hours. > > > > Thank you so much for your time and help! > > > > We are looking forward to hearing from you soon! > > > > Best regards, > > Katia > > > > -- > Matt Sicker <[email protected]> > -- Matt Sicker <[email protected]>
