28 August 2014 meeting

Agenda

Continue discussion of source tree layout.

Action items

• Greg will put notes on chimera2 wiki
• Greg will create git directories

Future issues

• Documenting our API with Sphinx
• Handling "private" modules -> future exports
• how chimera discovers tools on startup
• debugging from source tree
• build tools

Decisions

1. chimera will be top-level namespace:

   from chimera.core import graphics
   from chimera import MAV
   from chimera import extralibrary
   

2. Go with proposed layout from previous meeting
3. Tentative guidelines for core:
   • data structures that many tools need to agree on
   • facilities that many tools are likely to use
   • single version number
   • stable API
   • centrally and well documented
4. Tentative guidelines for non-core:
   • if it has no API
   • updated frequently
5. Rules for core
   • Data structures that most (many) tools need to agree on
   • Facilities that many tools are likely to use
   • Single version number
   • Stable API
   • Centrally (and well) documented
6. Rules for what's a tool
   • No API
   • Updated frequently