Use GitHub "project" for general SRT tasks?

[Fraser Tweedale]

We currently use GitHub issues to track general SRT tasks. There are many tasks that are not
related to the content of the security-advisories repo itself (e.g. announcements, planning, engaging
with related projects). Perhaps GitHub projects would be a nicer way to track those things. It can be
something like a Kanban board. See https://github.com/orgs/haskell/projects/3 for an example.

What do team members think about the idea?

Projects are attached to the organisation, not the repo. If we decide to do it, we should gather SRT
github accounts into a "team" and grant team access to the project, as well as the security-advisories
repo. That ensure a single place to manage SRT membership, as it changes over time.

Please comment below and we can decide either here, or at the next SRT meeting.

update: looks like each "cards" in a project board represents an issue in some repo. So we would
still have issues in security-advisories repo for each task. But a project board might still be a good
way to organise the work, see what is in progress and what is upcoming, etc.

[Fraser Tweedale]

Closing this for now. We can revisit it another time.