Setting up a github project

Stream: Equational

[Terence Tao]

Shreyas Srinivas said:

Terence Tao : Do you want to give the task interface in that video a try?

Sure, one of the main objectives of this project is to experiment with new workflows, so if you are willing to take the lead on this, that would be great.

[Shreyas Srinivas]

@Terence Tao : I tried it on my fork. Github requires the project owner and repository owner to be identical. So only you can create the project for the main repo

[Terence Tao]

OK. I have to go offline now, will try to look at this tomorrow

[Shreyas Srinivas]

I'll create a series of images as a tutorial:

[Notification Bot]

4 messages were moved here from #Equational > Thoughts and impressions thread by Shreyas Srinivas.

[Shreyas Srinivas]

Step 1:
Go to your repository's main page and select the Project tab on top. This is highlighted slightly in the image below:
Screenshot from 2024-09-27 00-30-36.png

[Shreyas Srinivas]

Step 2: You are in a screen that looks like below:
image.png

Click on the green button New Project

[Shreyas Srinivas]

Then you will be taken to a list of templates. The "Iterative Development" template feels closest to the current workflow

[Shreyas Srinivas]

Once you are in there, you can add collaborators to the project in the settings (this is different from your repository collaborators).

[Shreyas Srinivas]

You then get a number of views to organise your items. You can create github issues and assign them to people, match them with Pull Requests and so on. You can also delegate some of these tasks to your contributors.

[Shreyas Srinivas]

For example:
Screenshot from 2024-09-27 00-42-59.png

[Shreyas Srinivas]

When you click on the issue you can perform the usual actions on an issue. For example I assigned Pietro to one of the CI related issues (@Pietro Monticone : this is a test) : and you can see this on the dashboard.
Screenshot from 2024-09-27 00-44-06.png

[Shreyas Srinivas]

Users can claim issues by commenting on them and you can assign it to them

[Shreyas Srinivas]

Each "outstanding task" becomes a github issue

[Notification Bot]

This topic was moved here from #Equational > Setting up a kanban github project by Shreyas Srinivas.

[Shreyas Srinivas]

Further you can add issues to the repository directly from this project dashboard

[Shreyas Srinivas]

We can discuss out how to put the project to use effectively

[Terence Tao]

I think I created the project following your instructions. Do you see it on your end? I unfortunately don't have time to play with it in the near term, but I would be happy to grant permissions to others to manage it.

[Shreyas Srinivas]

I can't see it. I think you have to separately invite collaborators from the project settings

[Shreyas Srinivas]

Further, I just suggest that we run one version of "Outstanding Tasks" through this setup

[Edward van de Meent]

in the sense that we use either the outstanding tasks channel on zulip or the github project, but not both?

[Shreyas Srinivas]

Yes

[Shreyas Srinivas]

We can still discuss things here, but basically every task becomes a GitHub issue

[Shreyas Srinivas]

Whoever comments first gets it assigned and they comment their PR on the issue

[Shreyas Srinivas]

And if the project visibility is changed to public, we get to see the dashboard.

[Shreyas Srinivas]

Each version of Outstanding Tasks becomes an iteration

[Shreyas Srinivas]

The nice thing is Terence does not have to manually update the message every time a request comes in. He can delegate to a set of collaborators

[Shreyas Srinivas]

Further, you get some nice automation to update some of these lists (for example, moving PRs between various task queues)

[Shreyas Srinivas]

For mass collaboration it is going to quickly get tedious to maintain the outstanding task messages

[Terence Tao]

I just made the project public. I unfortunately am busy for most of the day and won't be able to actively participate but I fully endorse the experiment to try to move "outstanding tasks" over onto the projects framework, the current manual update system is certainly unsustainable for anything larger than the current project of trying to map out a subgraph of ~20 vertices