We had a discussion on IRC with Luca, Nathan, Ton and myself. outcome as agreed on by Nathan and myself:
* keep core scripts in bf-blender svn (ui, operators needed for blender to function). * allow existing core io scripts to move into addons and enabled by default allowing greater community contribution. * add metadata to spesify an addon as officially BF maintained. * rename addon header dictionary 'bl_addon_info' --> 'bl_info', this is more generic and means we can use for plugins, modifiers, nodes etc later on (assuming they even use python). This also allows to rename "scripts/addons" to something else without confusion. * defer Luca's proposal for a week, since this also raises other issues which need further investigation. We actually had very long discussion so I hope this summery is adequate. - Campbell On Fri, Jan 14, 2011 at 12:37 PM, Jonathan Smith <[email protected]> wrote: > I would have to agree with Campbell about the naming point. > > However I would think it would be better to implement this proposal sooner > rather then later, unless you were referring to later as after 2.5x > development is complete. The sooner it is implemented the more time we have > to work out any kinks that may arise and to further modify the whole process > if needed. Instead of waiting till the last minute, (although I'm sure we > probably wouldn't do that) and then running out of time. > > So from me, +1 for immediate implementation. > > On Fri, Jan 14, 2011 at 2:37 PM, Campbell Barton <[email protected]>wrote: > >> Hi Luca, while having a clearer division between core and community >> scripts could be good I don't there is one thing I don't agree with. >> >> >From what I can see with your proposal: >> current bundled "addons" become "extensions" and can be enabled by >> default, and community maintained addons (currently contrib addons), >> become "addons". >> >> To me this isn't a useful distinction to make, to the point of giving >> them different names since they are essentially the same thing from >> different places. >> If we need to tag scripts this can be a field in the script metadata >> and displayed in our UI so its clear that some addons are community >> maintained, downloaded from a 3rd party. bundled etc. >> >> to me an "addon" is just a standalone component which can be >> enabled/disabled, I don't see a problem with having a few officially >> maintained addons enabled in our default preferences. >> >> >> Aside from this one point your suggestions seem reasonable, at the >> moment the layout of scripts directories will probably need updating >> in the future though I'm inclined to wait-and-see since I don't think >> the current layout is holding back development. >> >> In short, Id like to go ahead with my smaller proposal and move io >> scripts to addons, and I'm open to larger changes in the future but >> don't think they need to be made right now. >> >> - Campbell > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > -- - Campbell _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
