# 06-10-2025 Blender Admins Meeting

## Attendees
* Bastien Montagne
* Campbell Barton
* Jacques Lucke
* Philipp Oeser

## AI written pull requests / patch descriptions
* How to deal with AI written code or the suspicion that code has been written with AI?
* Should docs / info when creating a pull request be more explicit on this?

***Conclusion:*** Bottom line would be that using these tools is fine, as long as the reporter does the work to analyze and present it in an understandable way. Do not just create a report or PR with the raw outcome of the AI tool. Ultimately, similar to using other analysis tools like sanitizer, static analyzer, etc.
Regarding AI generated code:
* The author should be able to respond to requests to cleanup to make up for the shortfalls from the tools they use.
* Inability to respond to follow up requests \- if the author is not capable of managing this, we should not invest too much time into this \- *up to the judgement of the reviewer*.

## License Header for code Templates
* Campbell noticed that some recent new templates (for OSL cameras) have been added with a SPDX header (copyright to the Blender Foundation, `Apache-2.0` license).
* The undocumented practice so far was to have no license info at all for these templates (implicit ‘public domain’ release).
* This allows everyone to use them as base, without any form of constraints.
* However, having no copyright and no explicit license is not a good thing, as this does not provide any legal validity under many jurisdictions.

***Proposal:***
* Add a SPDX header to all templates, using the `MIT-0` [license](https://opensource.org/license/mit-0).
* Add that license to the `release/license/spdx` directory.
* Document this special case in our developer handbook ([https://developer.blender.org/docs/handbook/guidelines/license\_headers/](https://developer.blender.org/docs/handbook/guidelines/license_headers/)).
* Use the `SPDX-FileCopyrightText: 2025 Blender Authors` generic info in files without any existing copyright info.

***Conclusion:*** Meeting agrees with the proposal. This does not apply to the code examples in the documentation.

## Styleguides regarding some C++ features (templates, lambdas, auto)
* Bastien raises concerns about relying too much on 'advanced implicitness' in our code (type deduction, generic parameters capture in lambdas, and so on). Especially in non-trivial usages.
* Inlining of comlex lambdas into function calls can also be a concern for readability.
* Jacques adds the `auto` usages to the list.

***Conclusion:***
* Meeting agrees in general with the concerns.
* How exactly to define what is allowed or not remains a work in progress.
* Bastien will create a devtalk thread to:
* Have a clear and concrete proposal.
* Gather more feedback from the whole development team.

## New dependency: Jpeg XL
* During the last Pipeline & I/O [module meeting](https://devtalk.blender.org/t/2025-06-05-pipeline-i-o-module-meeting/40942/1), Jesse suggested that we may want to add support for [Jpeg XL](https://jpeg.org/jpegxl/) in Blender 5.0. This implies adding the `libjxl` library to our dependencies, and rebuilding OpenImageIO.
* `libjxl` has itself a significant number of [dependencies](https://github.com/libjxl/libjxl/blob/main/deps.sh#L17).
* OpenImageIO itself is still pending some improvements of its jxl integration, expected with this summer's release.

***Conclusion:*** Meeting has no strong opinion. It's not clear if it’s really a widely used format yet. Probably not a hard target for now, it can also make it to a later release.

## [Namespace Naming Proposal](https://devtalk.blender.org/t/blenkernel-and-editors-namespaces-proposal/40229)
* Nothing really conclusive came out of the discussions on the proposal, expressed opinions are fairly divergent. This remains work in progress.