[Bf-python] quality and access to addons in blender contrib/trunk

Bassam Kurdali bassam at urchn.org
Tue Jul 15 21:14:05 CEST 2014


Hi all,

Became aware recently there is some discussion about quality of addons
in blender repo - and maintainers perhaps abandoning their addons there.

I'd like to add some issues that are preventing/have prevented updates
(they are needed) to the copy attributes menu addon (which I maintain)

1- after git migration I lost access/ can't figure out proper way to
commit to it (my addon is in addons/ not addons_contrib/ but I wouldn't
know either way)

This might be a common theme, but git is (Still!) new/scary to me, and
the submodule thing I don't understand. before I had svn access to
bf-extensions, now I don't know how to commit to my own code. I do not
have commit access to git afaik.

2- Resolved in phabricator? The tracker for the addon was one big 'bug
report' and I was the only subscriber (I think) - meaning that bugs got
mixed as comments, and also that the other two coders for the addons,
didn't ever see bugs on their own code. Would be better that addon bugs
just get submitted *as bugs* not as comments onto one bug. I don't
really know if this is fixed now because of problem 1.

3- Etiquette of submitting addons to contrib feels ambiguous still. (not
an issue for maintenance of existing ones)

This might be a special case, but if I can get back commit access I can
do bug fixes, enhancements, refactoring, taking advantage of newer
features, hotkey improvements (maybe it can use the pie menus when they
come out) etc... and make this a nice addon again








More information about the Bf-python mailing list