Meeting notes today brought to you by Lisa

Facilitation brought to you by Jeffrey

Whither 0.6.1

• Seven bugs have been nominated for 0.6.1. There may be more if we decided to comb through other bugs.
• Suggestion that we should have a bar for bugs to be fixed in 0.6.1

Discussion of what the bar should be

• Not a new feature
• Blocks a 0.6 tenet, or installation
• Mitch has suggested that a bug that prevents CSG from dogfooding, should be fixed in 0.6.1
  • Lisa will follow up on whether that expands the scope of 0.6 after the fact

Design Dependency discovery -- 0.7

• All of Platform team current work is now documented in their meeting notes today
• Developers are currently working on known bugs or participating in the design process, or working on known architectural issues like updating SWIG; debugging enabling; preferences framework
• No developers are blocked by design work currently nor do we expect any blockage in the next week or so

Hot design Topics, 0.7

Look at Monday Design page for links and more details, this is a summary to get everybody on the same page

• Plausible dashboard
  • Proposal is out there; discussions on list
  • Meeting with Apps team
  • Philippe will start discussions on dev list for open technical issues; John will research
  • Getting closer to being able to write a functional spec
• Scheduling and invitations
  • Proposal on the list and discussions
• Dogfood calendar work
  • More work put into this
  • Will send email summarizing this and do informal survey within office
  • Draft proposal for next work
• Detail view enhancements
  • Stearns is working on
• Context menus speced out
• Preferences in discussions on design list
• Sidebar issues
  • Mimi has discussed issues like focus on design list
• Target user description work going on in background

Note that Mimi's summaries document decisions and give people a last chance to debate

• a lot of information!
• discussion about whether people are able to keep up? May be hard to follow! It's hard to know if we're on the verge of making a decision or are about to make a decision.
• "LAST CALL" would be a good tag to wake people up
  • Last call is hard! We could call something "last call" but when we go to implement it we find more information.
  • People want to know the design rationale behind decisions.
  • When the design team believes they're ready to make a decision is when somebody wants to look (unless it's a topic they were interested in from the start)
  • A last call may be more useful than weekly summary
  • Probably want to do the activity summaries as well, though -- people have given good feedback on the activity summaries
  • IETF does last calls in its WGs, and similarly, after people get through the last call and make decisions, they then start implementing and more issues are found!

Build plans for 0.7

List of known plans

• Switch to Ubuntu after 0.6.1
  • QA machines then need to switch
• Linux RPM packaging
• Milestone numbering
• Build Sheriff followup and tools

Milestone numbering

• PJE posted on Python Egg numbering and release number polisher
• We probably need to rethink what we came up with months ago and be compatible with that
• On the other hand we had a vote on the list and came to rough consensus back then!
• That might have been partial consensus - we didn't decide on the suffix for pre-releases

Ubuntu

1. Wait for 0.6.1
2. Certify and make work
3. Push out to build machines
4. then do QA machines

Build sheriff

• Do we have people who are free to work on more build sheriff automated tools? Not everybody could be freed up for this
• Heikki has a mail to send out

wrap-up

• Lisa will facilitate next week
  • we like having timed agenda per topic
  • we also need to figure out how to surface unknown stuff (issues, blocks...) without wasting huge time
• Sheila will take notes next week