1---
2name: External Source Code
3about: Submit a proposal to integrate external source code
4title: ''
5labels: TSC
6assignees: ''
7
8---
9
10## Origin
11
12Name of project hosting the original open source code
13Provide a link to the source
14
15## Purpose
16
17Brief description of what this software does
18
19## Mode of integration
20
21Describe whether you'd like to integrate this external component in the main tree
22or as a module, and why. If the mode of integration is a module, suggest a
23repository name for the module
24
25## Maintainership
26
27List the person(s) that will be maintaining the integration of this external code
28for the foreseeable future. Please use GitHub IDs to identify them. You can
29choose to identify a single maintainer only or add collaborators as well
30
31## Pull Request
32
33Pull request (if any) with the actual implementation of the integration, be it
34in the main tree or as a module (pointing to your own fork for now). Make sure
35the PR is correctly labeled as "DNM"
36
37## Description
38
39Long description that will help reviewers discuss suitability of the
40component to solve the problem at hand (there may be a better options
41available.)
42
43What is its primary functionality (e.g., SQLLite is a lightweight
44database)?
45
46What problem are you trying to solve? (e.g., a state store is
47required to maintain ...)
48
49Why is this the right component to solve it (e.g., SQLite is small,
50easy to use, and has a very liberal license.)
51
52## Dependencies
53
54What other components does this package depend on?
55
56Will the Zephyr project have a direct dependency on the component, or
57will it be included via an abstraction layer with this component as a
58replaceable implementation?
59
60## Revision
61
62Version or SHA you would like to integrate initially
63
64## License
65
66Please use an SPDX identifier (https://spdx.org/licenses/), such as
67``BSD-3-Clause``
68
69