ncsurobotics / ncsurobotics/documentation
Onboarding onboard ONBOARD now now onbird woo
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
- Rust learning
- Read the book
- Do rustlings things?
- Where are the repos
- What are the repos
- Where are the things in the repos
- What are the things in the repos
- How vision
- What yolo
- What opencv
- How comms
- Running the code
- What is our hardware
- Histoey
- Old codebases
- How contrib
- What bad?
- Fix bad
- Push fix bad to place
- Merge place into main place
- SVG thingy with links to the things that need to be located (whatever they may be [like missions {or vission}])
- Goodberry's
Bikecar
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
No files, tests, or entry points are named. Start by organizing the listed onboarding topics around the repositories, Rust learning, vision/OpenCV, communications, hardware, history, and contribution workflow; done means these topics are documented, including an SVG with links to relevant locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- opencv, rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100