From BlenderWiki
Work in Progress
Addons Project 2.8x
Addons Dev Team
- Moderators/Admins:
- Sergey, Mont29, Sybren, meta-androcto
- Roles
- To maintain & improve the quality of the addons project.
- Maintain the Blender addons project in phab: bug fixes, tasks, projects.
- Successfully see the addons project into the Blender 2.8 series.
- Talk with other Blender project module owners.
- Encourage & liaise with new addons developers.
- Approve new contributors.
- Maintain mail lists.
- Review new addons & patches.
- Maintain Blender Python Api.
Addons To do/think
Important To write list of current addons & the authors & maintainers if the author is no longer active.
- Wiki tasks:
- Note: For some reference about script guidelines look at this page too: https://wiki.blender.org/index.php/Dev:2.4/Py/Scripts/Guidelines
- New Wiki for 2.8 addons, archive old one?
- Better descriptions for addons dev & git use.
- Better descriptions for addons ui & move towards "acceptable ui practices"
- Better handling of api changes, given the popularity of paid for addons & popular free addons, how to handle api breakages better.
- Style Guide - suggest using Flake8 as a default checker for new addon developers/contributors, list the ignored warnings (defined in tests/python/pep8.py like E122, E402 etc.)
- If third party maintained / developed add-ons have a wiki page entry (the current External category or future similar one), it should have a notice on top informing users that the maintenance and bug reports are not handled by Blender Org, but the add-on authors / maintainers.
- Phab tasks:
- do we have new addons section for 2.8 addons? (I think yes, solves the issue of removing invalid/inactive project members)
- keep current addons project running until 2.79 or January 2017? discussions with Sergey suggest close now
- batch thank & reply/close all 2.7x addons tracker tasks, bugs & submitted addons?
- for 2.8 is it possible to change the repositories system? currently there's addons project & blender project, would be good to have ui project with all the other python folder structures also.
- The permissions system would be: Addons devs: only addons project, UI devs: ui py & addons project, Core devs: Access to Blender main repo & the sub repo's.
- Blender tasks:
- decide on addons system changes, currently there are 2 three tiered systems, in Blender the "Official", "Community", "Testing", in the Wiki, "Release", "Contrib" & "Extern".
- decide on future of current addons, do we remove when broken during changeover to 2.8?
- decide on the future of i/o addons, do we remove the old outdated formats?
- decide on accepting a new addon into release should it conform to the style first as a condition? Consider maximum length of scripts per file too (to prevent single scripts with thousands of lines)
- define policies about addon cleanup patches in general by third parties (shouldn't do batch changes, is the maintainer informed about it/approved, are they tested, no drive-by patching)
- think about possibility/viability of implementation of some addon features, functionality in Blender when and where possible. If there is no current developer interest, it can be opened as a task for the future (similar to Quick Hacks)
- how to handle bug reporting of external / third party developed add-ons from the Blender side? A possible subject for the add-on manager? Currently the report a bug links to the Phabricator page
- consider adding some general information about Blender add-on development to the manual
