-
Put everyone’s name in, choose the “captains” and have they draft names for their teams? Is that what you have in mind?
-
@malvim something like that but perhaps with an option to see who is already in a team before they join it
@LoudLemur But the point of choosing teams (by one or two ppl only) is to aim for balance. Letting those getting picked the option to decide negates the supposed balance.
Anyway, you could try using something like Vikunja, or anything else that uses Kanban. I already do this with my domains. I make a Project called WEB, and in Kanban view, I make buckets. The buckets are the various VPSes I have. Then I make a new task in any given bucket. The Task is my domain name. I add tags such as Registrar, App, and Server, and use Notes to include info about the current app. I move my domains around often, so it's a visual cinch to just drag the Task/Domain from Bucket1(VPS1) to Bucket2(VPS2) or Bucket3(VPS3). Each bucket has an extra task containing details about that specific server. EVERY Task also has a Due Date which corresponds to the expiry date of the domain or server. Easy reminders!
How this can transfer to you is that you make a project called GAMES or TEAMS, and under it two Buckets, each for one person who will be choosing (Or just Captain 1 or Captain 2 if these people need their names in the Pool). Then, make a bunch of Tasks, maybe start in a neutral 3rd Bucket called Pool, and then as people are chosen you simply move their Task with their name from Pool to the appropriate Bucket1 or Bucket2. Everyone can also see who has moved where.
Good luck!
-
@LoudLemur But the point of choosing teams (by one or two ppl only) is to aim for balance. Letting those getting picked the option to decide negates the supposed balance.
Anyway, you could try using something like Vikunja, or anything else that uses Kanban. I already do this with my domains. I make a Project called WEB, and in Kanban view, I make buckets. The buckets are the various VPSes I have. Then I make a new task in any given bucket. The Task is my domain name. I add tags such as Registrar, App, and Server, and use Notes to include info about the current app. I move my domains around often, so it's a visual cinch to just drag the Task/Domain from Bucket1(VPS1) to Bucket2(VPS2) or Bucket3(VPS3). Each bucket has an extra task containing details about that specific server. EVERY Task also has a Due Date which corresponds to the expiry date of the domain or server. Easy reminders!
How this can transfer to you is that you make a project called GAMES or TEAMS, and under it two Buckets, each for one person who will be choosing (Or just Captain 1 or Captain 2 if these people need their names in the Pool). Then, make a bunch of Tasks, maybe start in a neutral 3rd Bucket called Pool, and then as people are chosen you simply move their Task with their name from Pool to the appropriate Bucket1 or Bucket2. Everyone can also see who has moved where.
Good luck!
-
Here is how it might look for Games:
Or don't use the title "Captain" just color code it.
Wekan and KanBoard might have tighter boxes. Vikunja's are rather tall for the info inside - you can see after 7 names the bottoms ones aren't visible. As people change you can then move their Task/name back into the Player list, you can color code who is the new captain for Teams going into Bloodsport Monkey Bars, you can set a Start date on the Task/name to keep track of when someone joined, and if you give everyone their own account they can edit the info in their own task/name!
I used the following image: Photo by <a href="https://unsplash.com/@schmig?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Anderson Schmig</a> on <a href="https://unsplash.com/photos/a-group-of-people-playing-a-game-of-tennis-ViQZi7AZ9aU?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Unsplash</a>
-
+1 Wekan. You can customize things further if you make use of the "rules" under board settings. Like assigning a custom tag "team red" when moving "Mary" from the pool to "captain 1's" list.
-
@scooke hey, thanks!
I love how you use kanbans to organize domains etc. That is so ingenious!I never thought of kanbans for this task.
I wonder if there is a way to tag rather than bucket like this. Eg time zone, or language
@LoudLemur You can assign tags in Wekan either manually or automatically via rules per specified conditions.
-
Here is how it might look for Games:
Or don't use the title "Captain" just color code it.
Wekan and KanBoard might have tighter boxes. Vikunja's are rather tall for the info inside - you can see after 7 names the bottoms ones aren't visible. As people change you can then move their Task/name back into the Player list, you can color code who is the new captain for Teams going into Bloodsport Monkey Bars, you can set a Start date on the Task/name to keep track of when someone joined, and if you give everyone their own account they can edit the info in their own task/name!
I used the following image: Photo by <a href="https://unsplash.com/@schmig?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Anderson Schmig</a> on <a href="https://unsplash.com/photos/a-group-of-people-playing-a-game-of-tennis-ViQZi7AZ9aU?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Unsplash</a>
@scooke said in Picking Teams for a Tournament:
Vikunja's are rather tall for the info inside - you can see after 7 names the bottoms ones aren't visible.
In Wekan, you simply have to scroll to see the rest.
-
@scooke said in Picking Teams for a Tournament:
Vikunja's are rather tall for the info inside - you can see after 7 names the bottoms ones aren't visible.
In Wekan, you simply have to scroll to see the rest.
@humptydumpty said in Picking Teams for a Tournament:
@scooke said in Picking Teams for a Tournament:
Vikunja's are rather tall for the info inside - you can see after 7 names the bottoms ones aren't visible.
In Wekan, you simply have to scroll to see the rest.
Same with Vikunja, I was just pointing out that at-a-glance is limited if the list is long.
-
