forked from orbit-oss/flask
Add Rule #0 to extension development.
This commit is contained in:
parent
3bf1750b5d
commit
c1a2e3cf14
1 changed files with 4 additions and 0 deletions
|
|
@ -326,6 +326,10 @@ new releases. These approved extensions are listed on the `Flask
|
||||||
Extension Registry`_ and marked appropriately. If you want your own
|
Extension Registry`_ and marked appropriately. If you want your own
|
||||||
extension to be approved you have to follow these guidelines:
|
extension to be approved you have to follow these guidelines:
|
||||||
|
|
||||||
|
0. An approved Flask extension requires a maintainer. In the event an
|
||||||
|
extension author would like to move beyond the project, the project should
|
||||||
|
find a new maintainer including full source hosting transition and PyPI
|
||||||
|
access. If no maintainer is available, give access to the Flask core team.
|
||||||
1. An approved Flask extension must provide exactly one package or module
|
1. An approved Flask extension must provide exactly one package or module
|
||||||
named ``flask_extensionname``. They might also reside inside a
|
named ``flask_extensionname``. They might also reside inside a
|
||||||
``flaskext`` namespace packages though this is discouraged now.
|
``flaskext`` namespace packages though this is discouraged now.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue