---
# System prepended metadata

title: Extensions Meetings

---



* [Extension Sprint TODO's](https://hackmd.io/c24RioERQ8u0dNaUY1RGow?both)

# Meeting Notes

Next:
* Update meta-data based on latest version [#111](https://projects.blender.org/infrastructure/extensions-website/issues/111).
* Feature Image + Icon
* Pagination

Tuesday:
* Blender: validate tagline (no period and size limit 64).
* Tag: Add Camera + Tracking.
* [Add-on changes](https://devtalk.blender.org/t/changes-to-add-on-bundling-4-2-onwards/34593#core-add-ons-1)
* New repositories:
    * [x] Move to subfolder: "source"
    * [x] Add a README
* Experimental-less:
    * [x] Upload all extensions
    * [x] Create all repos
    * addons(-contribs) read-only/archive
    * Finish to a satisfactory level the check for update
    * Copy scripts to addons_core
    * Update maks install
    * Move out of experimental
    * For release: create a .zip + documentation with addons bundle.

Tuesday afternoon:
* Must have:
    * Larger upload size (300MB)
    * Multi-OS basic
        * optional schema
        * extensions API lsitng 
    * Blender version max:
        * Moderators to be able to edit too.
        * Needs a different visualization.
    * Activity log:
        * Add more changes to the activity log.
    * Teams:
        * Editing by Team members.
        * Basically what is here: https://projects.blender.org/infrastructure/extensions-website/issues/106
    * Moderators:
        * New page, linked from about.
        * #extensions-moderation as contact info.
        * List all moderators.
        * Badge on activity feed for "moderators"
    * Approval Queue "pagination"
* Nice to have
    * Hotlinks/videos on description
    * Multi-OS package split
* Postpone until needed:
    * Server-side blocklist

Monday Meeting - 13/05/2024:
* Tags on the server repository
* Handling big files
    * Molecular Nodes: All OSs: 278MB
    * BlenderBIM: 160MB
    * Need to determine the new limit: 300MB.
    * Need to inform the user before the upload ends if it won't fit.
    * Include "contact team" in the error message: #extensions-moderators
    * The server can handle this traffic.
* LTS release considerations
* Multi-OS
* API entry point
    * Having an explicit API version entry point is probably fine for the forseeable future.



Wednesday Meeting:
* Dalai:
    * Move some official add-ons to blender-addons organization.
* Wheels:
    * Linux: An import may find the the system module nor the bundle module (potential simple solution, make blender's wheels first on the sys.path).
    * Some Linux distros already use a different versions of Python to Blender's official releases. I don't think there is a lot we can do about this - besides requiring extensions bundle multiple Python versions... or force distros to use a different Python version.

## Add-ons
* bl_pkg (Campbell)
    * Add-on move to Blender, keeping it an experimental feature.
    * Rename add-on name from "bl_pkg" to "bl_extensions"
      (this wont be accessed by scruipts typically).
* Existing GIT submodules "addons" and "addons_contrib" will be "removed" (read-only).
  Note that we wont delete incase users have their own local branches.
* Core addons
    * Move "core" add-ons to the scripts folder as "addons_core" on the source code.
    * On install copy "addons_core" to "addons" (and ignore the submodules).
    * See which ones has user preferences, try to move these preferences to c code, and add-on acess it.
    * All add-ons will be "on" by default, if the add-on (e.g., VR) needs to be hidden from the UI, Blender should add a new option on the preferences for that, which the add-on reads.
* For each community add-on:
    * Create a new repository on https://projects.blender.org/extensions/
    * Create a new repository locally with the [isolated code + git logs](https://developer.blender.org/docs/handbook/guidelines/hosted_extensions/#migrate-from-the-add-ons-repository).
    * Create manifest from bl_info.
    * Build extension + featured image + gallery image + icon.
    * Upload extension under a blender_addons account. (use selenium if there is no API).
    * Contact authors if they want to take over, if so add them as maintainers of the extension + collaborators of the repository.


## Official add-ons
Recommendation is for to people to host add-ons on their person repo on git.blender.org.

Add-ons which are popular (or currently bundled with Blender) if they have no place to go they can go to `blender-addon` org: 1 repository per add-on.

See the [documentation](https://developer.blender.org/docs/handbook/guidelines/hosted_extensions/).


## Topics

TOML Validation
* In the future once we have new manifest schemas we will need a way to handle this. For example, different schemas may accept different "permissions".
* To be looked at after the website launched.
* Low tech solutions are acceptable.

API Listing stress test:
* Pagination will be required soon as part of V1.
* To be implemented on a the server first either as a branch or as a feature flag (to be tested on staging).
* To help stress testing staging could be populated with tons of extensions.

Blender update checks:
* Work start tomorrow.
* Implementation needs to be aware of potential unavailability.
* Oleg suggests to have a chat with Campbell once this works starts.
* This should prevent Blender from freezing, as well as DDoSing the server.

Wheels:
* Loosing preferences bug (needs to be reported).
* Python cannot handle well multiple versions of the same wheel.
* Vendorizing is already working.
* Current [branch](https://projects.blender.org/ideasman42/blender-addons-contrib/src/branch/temp-wheel-support) is to handle importing.
    * Could be merged already.
    * Needs wheel comparison.
    * Needs to [update documentation](https://docs.blender.org/manual/en/dev/extensions/addons.html#rd-party-python-modules).
    * List popular modules (e.g., PIL) with recommended version.


# Previous Meetings Notes

* [2024-05-21 - Extensions Project](https://devtalk.blender.org/t/2024-05-21-extensions-project/34751).
* [2024-04-30 Extensions Platform - Backend](https://devtalk.blender.org/t/2024-04-30-extensions-platform-backend/34413)
* [2024-04-02 Exte.nsions Project - Backend](https://devtalk.blender.org/t/2024-04-02-extensions-platform-backend/34147).
* [Multi-OS](https://projects.blender.org/infrastructure/extensions-website/issues/74).
* [2024-04-16 Extensions Platform - Backend ](https://devtalk.blender.org/t/2024-04-16-extensions-platform-backend/34247).

Reference:

![image](https://hackmd.io/_uploads/H1yQoHCWR.png)
