The why

Manage tasks of own work packages, add assignees, communication and collaboration with other institutions, follow task/milestone progress.

The how

in stream-project, create private repository "work-package-x", may add short description
- goto this repository Settings>Features: uncheck Wikis and Projects and in Settings>Actions: Disable Actions
in stream-project/projects, create private project "Work Package X" with Template "Basic kanban" and linked to your repository.

add tasks (notes) to the columns To do or In progress, order tasks by drag and drop
convert a note to issue to allow comments, define labels, assignees, milestone etc
use Assignees to add everyone who is working on an issue. Every assignee gets mail notifications on changes over the issue.
use Labels for: work package grouping (eg. "WPX.Y") or priority (eg "Important")
use checkbox lists to add subtasks to a task
use Milestone to group multiple tasks and see their progress
close an issue and move to column done if its requirements are fulfilled
to add existing issues to a column click Add cards

Filter issues by label, assignee or milestone is simply click on a label, assignee or milestone
Browse all issues assigned to you (even from other work packages): goto https://github.com/issues (see top left navigation) and filter by organisation stream-project

Google Drive integration is not the best
GitHub Projects is designed for code issue management. For our project tasks management it has a lack of some functionality. But its OK?!
Goal: share information about tasks, results, work together, communicate, collaborate
Extra repositories should be used for code in general and components