1ad2d8fda4
Quite often Oslo is requested to create (or adopt) new libraries for various purposes and it would be good to (as a group) have a stance on new libraries and the process they need to go through to either become a new library in Oslo or to become a new library that is independently maintained on pypi. Co-Authored-By: ChangBo Guo(gcb) <eric.guo@easystack.cn> Change-Id: Ib1ed8aad4859ca8313ac841fb9a57db1d08a2f10
3.1 KiB
Proposed new library XXX
Introduction paragraph -- why are we proposing new library?
Proposed library mission
A detailed description of the problem.
Consuming projects
Who is going to use this (project involvement).
Alternatives library
Existing similar libraries (if any) and why they aren't being used
Proposed adoption model/plan
which adoption model the new library will choose ?
Reviewer activity
who will be responsible for reviewing, how many reviewers are active, how many could be active.
Implementation
Author(s)
Who is leading the proposal of the new library? Must have at least two individuals from the community committed to triaging and fixing bugs, and responding to test failures in a timely manner.
- Primary authors:
-
<launchpad-id or None> <launchpad-id or None>
- Other contributors:
-
<launchpad-id or None>
Work Items
List any concrete steps we need to take to implement the policy.
References
Please add any useful references here. You are not required to have any references. Moreover, this policy should still make sense when your references are unavailable. Examples of what you could include are:
- Links to mailing list or IRC discussions
- Links to notes from a summit session
- Links to relevant research, if appropriate
- Related policies as appropriate
- Anything else you feel it is worthwhile to refer to
Revision History
| Release Name | Description |
|---|---|
| Introduced |
Note
This work is licensed under a Creative Commons Attribution 3.0 Unported License. http://creativecommons.org/licenses/by/3.0/legalcode