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.

Sign up for GitHub

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

Jump to bottom

Consider formalizing team composition #7

Open
Ainali opened this issue Apr 16, 2020 · 1 comment
Open

Consider formalizing team composition #7

Ainali opened this issue Apr 16, 2020 · 1 comment

Comments

@Ainali
Copy link
Collaborator

Ainali commented Apr 16, 2020 •
edited
Loading

@Hugo-ter-Doest made an insightful comment on the impact the composition of the teams may have in #3 . This might need some collaborative thinking and discussion to get a solution that fits this project. Because of that I have created this issue.

The question at hand is, do we want to formalize the composition of the teams to only allow one member per party in them?
@Ainali Ainali mentioned this issue Apr 16, 2020
Merged
@Hugo-ter-Doest
Copy link

For now we can see how the communities and committees develop. Maybe add a guideline for now of one member per party? Not a strict rule (yet).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Ainali @Hugo-ter-Doest