「利用者:Mont29/Addons/Temp/Dev:Py/Sharing」の版間の差分
(→Rules for Extension Developers) |
細 (1版 をインポートしました) |
(相違点なし)
|
2018年6月29日 (金) 04:46時点における最新版
bf-extensions Trackers
If you are a script or plugins developer, you can upload your extensions in one of Bf-Extensions Trackers:
Workflow
To get your script/plugin tested and then accepted in Blender you have to follow this workflow:
- Upload your extension (a script or a plugin) …read all here.
- If ok the script goes in Contrib tracker, and in bf-extensions svn …read all here.
- If really ok it goes in the official Blender distribution …read all here.
Here are some quick and general advices, once your addon is in contrib, and you have got a SVN access. Please also read above links!
Rules for Extension Developers
- DO’S
-
- Join bf-extensions-cvs and bf-python mailing lists.
- Ask questions on #blenderpython IRC channel.
- Make your script pep8 compliant (for best practice see: best practice).
- Create a wiki page, at least briefly documenting your addon, and a few pics showing it at work.
- Feel free to test other coders’ addons, and commit small fixes to their code (like e.g. typo, obvious bug fixes).
- DON’TS
-
- Commit code that is not GPL2+.
- Commit code you are not the author (unless of course you have the author’s authorization)!
- Move your addon from contrib to trunk! This will be done by an admin, once your code has been reviewed and got consensus.
- Commit changes to other coders’s addons (like e.g. adding/removing features, or changing behavior), unless you get the author’s permission.
- Commit binary files like .exe .pyc, .pyd, dlls, etc.
- Add full log inside your code – svn is here for this!
IRC Channels
Please come and discuss any problem or idea in our developers channels. Especially you’ll find people to help you in #blenderpython. See you there!