Difference between revisions of "Development"

From VistrailsWiki
Jump to navigation Jump to search
Line 13: Line 13:


* Update on [[PythonSource error reporting and logging]] (Tommy)
* Update on [[PythonSource error reporting and logging]] (Tommy)
** Need to make sure that all messages are printed through debug.X, so that the debug level (verboseness in preferences) is correctly used


* Update on subworkflow (Daniel)
* Update on subworkflow (Daniel)

Revision as of 19:46, 12 October 2010

Roadmap

Weekly Meetings

Oct 12, 2010

  • Trac and Roadmap (Emanuele): Emanuele suggested we should create a development roadmap and make it a permanent item on the agenda. The idea is to go through the Trac tickets and use them to build the roadmap that would be made public.
    • go through trac and sort by priority
    • add other suggestions to roadmap as well
    • admins can add milestones via the admin tab
    • David will assign tasks on list; those assigned need to follow up and check and fix them
  • Update on subworkflow (Daniel)
  • New utility added by Carlos (currently at scripts/module_appearance) to draw

fringes visually, which generates output that can be pasted directly into the add_module call. We need to test this on Mac and Windows.

  • Preparing a "Get Started" tutorial for SIGMOD repeatability
    • Do we have instructions on how to use the latex package without crowdlabs?
    • Metadata associated with VisTrails: should we have the ability to add vistrail-level metadata? e.g., who created the vistrail, its purpose, etc.
  • Maintaining VTK package

Oct 5, 2010

  • Welcome Tommy!
  • Update on subworkflow (Daniel)
  • Issues raised by Matthias:

- need to automatically upgrade subworkflows. Currently it is necessary to manually upgrade a subworkflow whenever the version of one of the modules inside them changes.

- explorations do not detect an MplFigureCell embedded in a subworkflow.