Re: [Bf-committers] Add-ons Policy Clarification/Discussion

2022-03-29 Thread Ryan Inch via Bf-committers
After speaking with Thomas, we've decided to move this discussion to the devtalk thread. Ryan Inch (Imaginer) ___ Bf-committers mailing list Bf-committers@blender.org List details, subscription details or unsubscribe: https://lists.blender.org/mailman/

Re: [Bf-committers] Add-ons Policy Clarification/Discussion

2022-03-13 Thread Ryan Inch via Bf-committers
I decided to post links to this discussion on devtalk as well to try and reach as many community add-on developers as possible, as this may directly affect them.  (Some comments I've read suggest that devtalk is followed more closely than the mailing list) https://devtalk.blender.org/t/add-ons

Re: [Bf-committers] Add-ons Policy Clarification/Discussion

2022-03-11 Thread Thomas Dinges via Bf-committers
Hey Ryan, Thanks for your mail on this topic. Disclaimer: The following is my opinion, a formal decision is up to the BF admins and the add-on module team. :) A) I don't think external links for bug reports are explicitly covered by the current key-requirements. They only mention to "offer

[Bf-committers] Add-ons Policy Clarification/Discussion

2022-03-10 Thread Ryan Inch via Bf-committers
Hey Thomas et al., I would like to discuss the new add-on policies with you in regard to their practical application and the needs of add-on developers. A. I use a custom url for the report a bug button in Blender that points to BlenderArtists.  I do this for two reasons:     a. to point peop