Dev:WeeklyMeetingAgenda/2006-07-30th

Python

• API Stability what is the current and future
• API coverage - LetterRip suggested it would be a good idea if we could create a rough estimate of what modules are missing still and how complete existing modules are
• Deprecation - potentially keep old version of the API but renamed for one release, so users can still use it. Theeth suggested a warning one release and removed the next.
• a 'spec' - what should we have for goals be and what should it consist of?
• near term todos

1) split mathutils into a geometry module and mathutils, and possibly add primitives to geometry, theeth will coordinate with ascotan

2) script guidelines - see below

Python Script Guidelines

We want better integration of scripts in Blender. They should look and work like other functionalities in the program and, most important, be robust (proper error checking and reporting) and well documented.

For that we will use a forum (probably BlenderArtists' Python and Plugins forum) to discuss scripts and use wiki for better documentation.

The first step will be to define clear guidelines for scripts that are bundled with Blender. This will be done during this week here:

http://mediawiki.blender.org/index.php/ScriptDev/Guidelines

And advertised next week on forums and mailing lists so all interested readers can share their opinions about it.

The next steps will probably be:

1) Remove all scripts from cvs 2) Only add back the ones that (are updated to) conform to the accepted guidelines.

PS: we will also start using the scripts project's cvs to collect and manage scripts. There more script developers can have write access.

Ghost

• lukep has started the refactor of Ghost (our low level event and device system) and could use some assistance for changes needed for X11 and Windows - this will involve adding improved internationational keyboard support, better event system resolution and other work