Turn feedback from IPFS Thing 2022 into action items

[galargh]

Let's gather things that we'd like to talk about during IPFS Thing 2022.

To start:

• team post-mortems
• PR review expectations
• go-ipfs "low-hanging-fruit" week

[galargh]

Let's discuss paid Github subscription - it'd be nice to have an increased number of GitHub Actions runners available.

[galargh]

https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration#usage-limits

[galargh]

Did we ever think about using GitLab instead of GitHub? Or other open source alternatives?

[laurentsenta]

Could we get started on metrics?

https://github.com/libp2p/go-libp2p/pull/1639#pullrequestreview-1031484125 https://github.com/pl-strflt/ipdx/issues/27

[galargh]

team post-mortems

Team post-mortems:

• reflect about planning
• what's the expiration date of our top priorities? when do we come up with new ones?
  • we might be missing dates next to our proirities - how long are things happening for
  • what's the outcome - less about time, more about concrete outcomes
  • when are we done

Planning:

• roadmaps - with blockers explicitly stated (let's build on Laurent's freelancing experience in dealing with external dependencies)
• every month/every 2 months - isn't that too often
• let's start in September after Laurent's back from holiday
• or we can start straight away and formalise our current plans
• involve Steve in output review - not necessary for him to join the full planning cycle

Meeting plan:

• review the past plan
  • what happened
  • what didn't happen that we planned
  • what happened but we didn't plan it
• upadte plans
• put concrete desired outcomes next to the new plan items

PR review expectations

• let's finally put codeowners where we should codeowners
• let's not be shy about reasking for a review
• we care about reviews and what other people are thinking
• expect reviews immediately
• let's start our days with review session; if we start doing dailies let's put them a little bit into the day so that there is time to review stuff in the morning

go-ipfs "low-hanging-fruit" week

• Peter talked with Gus about this and they concluded that IPDX getting involved with the next kubo release will be the best starting point
• write down action items from that excercise

paid GitHub subscription

• we need Steve for this discussion
• alternative: other CI/CD providers (gitlab for example), self-hosted runners, organization number explosion

GitHub Actions debugging

• let's enable ssh when debug logging is enabled (let's add it to unified CI but let's make it an action in marketplace)

[galargh]

(triage to close it, we should extract action items from https://github.com/pl-strflt/ipdx/issues/42#issuecomment-1184768380)