LakeEffectRobotics / LakeEffectRobotics/LakeEffectScoutingApp
Split scouting up
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 10
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
One of our ideas is to combine qual and quant scouting a little bit for the end, but if we have enough people, it would be best to split match scouting in two parts to lower workload.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current match-scouting flow and how qualitative and quantitative scouting are combined. Determine the intended split between the two parts, accounting for the available people and workload; done means the scouting responsibilities are clearly separated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100