Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarity on roles and responsibilities for Task lead #30

Open
twoude opened this issue May 29, 2024 · 4 comments
Open

Clarity on roles and responsibilities for Task lead #30

twoude opened this issue May 29, 2024 · 4 comments
Assignees
Labels

Comments

@twoude
Copy link

twoude commented May 29, 2024

@RaduGiurgiu @fennyvanegmond we obtained this feedback a few times during meetings. Project partners don't know what they need to contribute or their responsibilities. Also, the difference between responsibilities. We should make this clear.

  • Task leads
  • WP leads
  • Component leads
  • User case lead
@RaduGiurgiu
Copy link
Contributor

Other than the GA description on each WP lead, task lead and use case lead description, what else should we do for this issue?

@twoude
Copy link
Author

twoude commented Jun 26, 2024

Perhaps we could sit down with each project partner where they contribute, and what their responsibilities are? One on one?

@RaduGiurgiu
Copy link
Contributor

Perhaps we could sit down with each project partner where they contribute, and what their responsibilities are? One on one?

@twoude can you break down this issue in more specific issues? or what's the plan to progress on it ?

@twoude
Copy link
Author

twoude commented Jul 24, 2024

For WP1, we had this conversation with the task leads, but this was also raised for other WPs. I would say to sit down with the task leads for each WP to say what they should do, but I leave that up to you. For WP1, that is what we are doing.

@twoude twoude added the WP7 label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants