engineering mtg

• wxPython/wxWidgets 2.5.2 migration
  • We expect a release candidate late this week or early next. We expect a plan by next week.
• linux
  • Getting Chandler running on linux again is a high priority
  • We're going to standardize on fedora core 2 for 0.4.
  • We're blocking on Bug#1626: the current rev of wxPython doesn't play well with GTK 2.4. We expect the next rev to fix this problem.
  • John is going to try and make vmware work with FC2.
• irc tomorrow
  • security: One rule of thumb is to check paramaters, but this is not particularly pythonic. How should we approach this?
  • unit tests: What constitutes a unit test? What kind of coverage is expected? Do we require regression tests to be written when we fix defects?
  • code reviews: Perhaps talk about two different kinds of code reviews -- diffs to existing functionality vs reviewing a whole module at once. Is it ok to review diffs as they pass by on the commits list?
• future irc topics
  • queries
  • network architecture, servers, p2p
  • sharing
  • clouds, indexing
  • how we use bugzilla
• performance (PerformanceProject)
  • profile use cases in .4, look for some low hanging fruit but no promises
  • be prepared to allocate real time to addressing performance issues in .5, think about this in the planning process
  • get reference hardware (qa lab)
  • hook up profiling of use cases to tinderbox
  • Katie is on the hook for driving this, with Chao helping set priorities and Heikki helping hook up to tinderbox.
• bug voting
  • Jurgen will change bugzilla to allow 10 votes per person, with no more than 1 vote per person per bug
  • We'll experiment with using this mechanism as a way of aggregating diverse opinions.
  • If a bug is blocking work or indicates a feature is not done, it will have a high priority regardless of # of votes

-- KatieCappsParlante - 04 Aug 2004