Github Project - High Level Board

[elikling]

Motivation

As the number of people contributing and taking interest in PyWhy is growing there is a desire to provide some structure to communicating what is being worked on and in what stage it is.

The Kanban board provided by Github is a grate way to run daily stand-ups within a work-stream discussing the resolutions of issues and bugs. It feels too detailed to serve the weekly Discord call.

Suggested board approach

There are two possibilities to choose from for a high level "state of the project" review:

• Each column in the board represents a person
• Each column in the board represents an Epic or a Challenge

The PBIs (Product Backlog Items) can start of as notes which is decided, can be turned into issues that to be monitored in Kanban style boards.

As the board is used, the incorporation of pull requests can be explored.

The Devil is in the detail

The 2022 capability of managing a project alows for several view tabs. In the table view, it is possible to define a new field:
Name: Challenge
Type: Single select
Values: {

• DoWhy API V2,
• Causal Discovery,
• Causal Estimation,
• NetworkX,
• Documentation and Examples,
• GCM,
• bug fixing
  }

[petergtz]

Hey @elikling, may I bring in a slightly different suggestion? I'd like to follow an approach inspired by the approach presented here: https://alloverse.com/2022/05/31/github-projects-for-open-source-tracking/.

The reason is that I wouldn't want to assume a fixed set of people. Contributors come and go, and that's normal for an open source project. So using columns for contributors wouldn't work too well I believe. Also, people can be assigned to tasks or issues through the assignee property of an issue. Instead, I would recommend using GitHub Projects in the way they're intended, with some of the hacks suggested in the link above. I'll go ahead and create some epics (some of which you also listed).

[elikling]

I agree with you that it is not efficent to have a colum per person. I put it there for dicussions sake. I prefer the secon option I put there "Each column in the board represents an Epic or a Challenge".
The approach proposed in the link you share above is interesting. I just wonder if it is not a littl too much hasle for the purposes of having a simple board to review on the weekly meeings.
There is only one way to find out - try it out :-)