RoboStack / RoboStack/robostack.github.io
Upstream patches
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Astro
- Stars
- 385
- Forks
- 36
- Avg merge
- 5h 37m
- Merged PRs (30d)
- 18
Description
Many of the patches in https://github.com/RoboStack/ros-noetic/tree/master/patch are not conda/robostack specific and should be upstreamed. If someone would want to do that, that would be great.
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 patch directory in RoboStack/ros-noetic and classify which patches are not conda or RoboStack specific. Check the relevant upstream projects for their contribution process; the work is done when the applicable patches have been submitted upstream and their local copies can be addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100