Summary
Propose a new version of the Device Repository with web-based device onboarding.
The idea is to provide a web application where device makers can create or update device definitions through guided forms, test payload codecs in the browser, upload device images, and submit the generated definition as a GitHub pull request.
GitHub would remain the source of truth.
Why do we need this?
Adding a device to the Device Repository currently requires git knowledge, local tooling, and manually creating YAML/JS files that must follow the repository schema.
This works well for technical users, but it can be difficult for some device makers who only want to submit or maintain their device definitions without setting up a local development environment.
A web-based onboarding flow would make device submissions easier while keeping the existing review and validation process in place.
What is already there? What do you see now?
The current Device Repository already provides:
- A GitHub-based source of truth
- YAML/JS-based device definitions
- A schema for validating device files
- CI validation
- Maintainer review through pull requests
- Support for payload codec files and device images
This workflow works, but it requires contributors to understand the repository structure and prepare the files manually.
What is missing? What do you want to see?
A web-based device onboarding flow where device makers can:
- Fill in vendor and device information through guided forms
- Add hardware, firmware, regional profiles, and codec information
- Test payload codecs directly in the browser
- Upload and validate device images
- Generate the required YAML/JS files automatically
- Submit the result as a GitHub pull request
The goal is not to replace the existing repository workflow, but to provide an easier submission path for device makers.
How do you propose to implement this?
mplement a web application that uses the existing Device Repository schema and file format.
The first version could focus on:
- A guided device submission flow
- Schema-based validation using the existing schema
- Browser-based codec testing
- Image upload validation
- GitHub integration for automatic branch, commit, and pull request creation
The existing repository structure, CI validation pipeline, and maintainer review process would remain unchanged.
A more detailed technical proposal can be prepared before starting the implementation.
Can you do this yourself and submit a Pull Request?
Yes, I can work on the technical proposal and implementation
@johanstokking @mfilipan
Summary
Propose a new version of the Device Repository with web-based device onboarding.
The idea is to provide a web application where device makers can create or update device definitions through guided forms, test payload codecs in the browser, upload device images, and submit the generated definition as a GitHub pull request.
GitHub would remain the source of truth.
Why do we need this?
Adding a device to the Device Repository currently requires git knowledge, local tooling, and manually creating YAML/JS files that must follow the repository schema.
This works well for technical users, but it can be difficult for some device makers who only want to submit or maintain their device definitions without setting up a local development environment.
A web-based onboarding flow would make device submissions easier while keeping the existing review and validation process in place.
What is already there? What do you see now?
The current Device Repository already provides:
This workflow works, but it requires contributors to understand the repository structure and prepare the files manually.
What is missing? What do you want to see?
A web-based device onboarding flow where device makers can:
The goal is not to replace the existing repository workflow, but to provide an easier submission path for device makers.
How do you propose to implement this?
mplement a web application that uses the existing Device Repository schema and file format.
The first version could focus on:
The existing repository structure, CI validation pipeline, and maintainer review process would remain unchanged.
A more detailed technical proposal can be prepared before starting the implementation.
Can you do this yourself and submit a Pull Request?
Yes, I can work on the technical proposal and implementation
@johanstokking @mfilipan