f938cc427e
As per the agreements in the Process Group Meeting, rework the procedure to include external code so that it reflects the reality of Zehyr today with the choice between modules and integration into the main tree, and decouple the non-Apache v2.0 license side of the question from the process from importing 3rd-party code. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
1.5 KiB
| name | about | title | labels | assignees |
|---|---|---|---|---|
| External Source Code | Submit a proposal to integrate external source code | TSC |
Origin
Name of project hosting the original open source code Provide a link to the source
Purpose
Brief description of what this software does
Mode of integration
Describe whether you'd like to integrate this exernal component in the main tree or as a module, and why. If the mode of integration is a module, suggest a repository name for the module
Pull Request
Pull request (if any) with the actual implementation of the integration, be it in the main tree or as a module (pointing to your own fork for now). Make sure the PR is correctly labeled as "DNM"
Description
Long description that will help reviewers discuss suitability of the component to solve the problem at hand (there may be a better options available.)
What is its primary functionality (e.g., SQLLite is a lightweight database)?
What problem are you trying to solve? (e.g., a state store is required to maintain ...)
Why is this the right component to solve it (e.g., SQLite is small, easy to use, and has a very liberal license.)
Dependencies
What other components does this package depend on?
Will the Zephyr project have a direct dependency on the component, or will it be included via an abstraction layer with this component as a replaceable implementation?
Revision
Version or SHA you would like to integrate initially
License
Please use an SPDX identifier (https://spdx.org/licenses/), such as
BSD-3-Clause