Gerstmann-Bradley / Mograph-Presets-of-Geometry-Nodes

79 stars 5 forks source link

upload of your addon to blender extensions website #4

Open ghost opened 3 months ago

ghost commented 3 months ago

Hi

I want to request the upload of your addon to blender extensions website (Install blender 4.2) so it can be found more easy and become popular in the blender community.

https://extensions.blender.org/

Gerstmann-Bradley commented 3 months ago

I have thought about that, but there were certain parts I was not too sure how to proceed, such as

  1. Whether it's really acceptable by blender foundation that these assets are downloaded elsewhere every time they started blender? This means it can technically bypass code review requirement of blender foundation.
  2. Documentation to Add-on, but no documentation to assets. These assets are also strongly following my personal workflow, which I am not sure if blender foundation will be too happy about it.
  3. currently assets are in CC-BY instead of required CC-0. (of course, this part is easier to manage than the previous two points).

Despite other solutions, for now I don't want to be bothered with these issues. So this is how it is now.

ghost commented 3 months ago

I have thought about that, but there were certain parts I was not too sure how to proceed, such as

1. Whether it's really acceptable by blender foundation that these assets are downloaded elsewhere every time they started blender? This means it can technically bypass code review requirement of blender foundation.

There is a setting "allow online access" . If this is enabled it should download, otherwise it should not. So if "allow online access" is enabled, your extension can download whatever it wants from any place! Since this setting needs to be enabled anyway for add-ons who access the internet, I don't see any problem here. I'm not a developer but I believe it's a python variable you need to check. You can make a message box saying "please enable "allow online access" in order to download the assets" when a user has disabled the setting. In this way you respect the blender setting and everything will be OK.

afbeelding

2. Documentation to Add-on, but no documentation to assets. These assets are also strongly following my personal workflow, which I am not sure if blender foundation will be too happy about it.

If you upload the extension, there is a review by the blender team. They tell you what is accepted or not and also what to change to be accepted on the extensions website! I don't think there are any rules for assets because it's defined by your addon.

3. currently assets are in CC-BY instead of required CC-0. (of course, this part is easier to manage than the previous two points).

Despite other solutions, for now I don't want to be bothered with these issues. So this is how it is now.

I personally think there is no problem at all.

I also think that many people will be able to discover the add-on because here on github it's stays in obscurity a bit. This means more users and more people who can test it and report bugs! I hope you consider one day to upload it.

Gerstmann-Bradley commented 3 months ago

There is a setting "allow online access" . If this is enabled it should download, otherwise it should not. So if "allow online access" is enabled, your extension can download whatever it wants from any place! Since this setting needs to be enabled anyway for add-ons who access the internet, I don't see any problem here. I'm not a developer but I believe it's a python variable you need to check. You can make a message box saying "please enable "allow online access" in order to download the assets" when a user has disabled the setting. In this way you respect the blender setting and everything will be OK.

It's not that simple. Normally even if you allow online access, it only means you can download extension from website, While extension has its code-review requirement to prevent any malicious activity. However this add-on require online access, and without online access this add-on is 100% pointless because it doesn't include the assets. The main part of this add-on is not the add-on functionality itself but the assets it downloads from github, and the asset file is not under constant review and check. It's not impossible to implant malicious code inside to do harms, and it will cause trouble which is likely forbidden by blender foundation.

You can also see from the tooltip it clearly says that "Blender can not prevent third-party add-ons from violating this rule", which is the reason why this add-on is still working as a third-party add-on regardless of your settings.

I personally think there is no problem at all. It's mentioned on the guideline that assets are required to be in CC-0, along with many other comments I mentioned. Overall, passing the check from blender foundation is not that simple as you think. If you can discuss with blender foundation to get their opinions on the problems I mentioned it will be great.

I always think and consider the possibility uploading it to extension website. Nevertheless there are many concerns and for now I don't want to spend much time dealing with it.