Define and publish device certification process
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 385
- Forks
- 88
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 82
Description
One of the core missions of Isaac Teleop is to build a vibrant ecosystem of device plugins. However, we are running into bottlenecks as it’s hard to follow up with partners who want to integrate their devices into Isaac Teleop.
To address this, we'd like to establish a streamline and scalable device certification and benchmark process that device manufactures and users of such devices can certificate and evaluate on their own.
Contributor guide
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
The issue names no files, tests, or entry points. Start by clarifying the certification and benchmark requirements, then define completion as a scalable process that device manufacturers and users can follow and publish independently.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, robotics, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100