r2 - 31 Jan 2006 - 16:33:46 - SheilaMooneyYou are here: OSAF >  Journal Web  >  EngineeringMeetingNotes > EngineeringMeetingNotes20050131
Facilitation: Lisa Note Taker: Sheila

Agenda

  • Agenda bashing
  • 0.6.1 clarification
  • Status mail decisions
  • What should we cover in this meeting
    • discuss shorter agenda for this meeting - cover more on the lists

Notes

What should we cover in this meeting?

  • Purpose of this meeting
    • surfacing issues
    • notice when things are stalling

Chandler 0.6.1

  • We made a decision that we will use 0.6.1 for Pycon, Katie nominated some bugs for 0.6.1 that might be candidates for fixed.
    • We will have a bug triage after this meeting to dicuss
  • Release date - Feb 9th
  • Need a candidate build by Feb 6th
  • Send an email out to the list notifying everyone of the dates

Status mail decisions

  • Moving to Thursday and everyone is ok with this.

Surfacing Issues - What is your top worry?

  • Aparna: 0.6.1
  • Heikki: sheriff stuff and build tools
    • Bear and PJE working on fixing one tool -
      • email will go out to everyone who checked in since the last build. Those people will be on the hook for following up (if they break the build they will fix it)
      • need support for this
    • Milestone version numbering - proposal will need to go to the list
  • Phlippe: no big worries
    • Freenode - done
    • Intership - need to have comments from others
  • Katie: time to engage in responses
  • Sheila: scheduling all the design meetings and getting all the designs
  • Lisa: concern that the design process is taking too long - trying to get too many people involved
  • Ted: QA
    • getting more people involved and Aparna's absence
    • how can we leverage people in the communtity

Brainstorming - getting more functional and unit tests

  • How to we get people to write more functional and unit tests?
  • Perhaps we should do verifying qa sessions more often and get more people to write tests - use the 2 office hour slots
  • Another sprint for writing unit/functional tests - 1/2 day
  • Tests out of the sprint - there weren't as many tests created as we thought
  • We probably need to get buy-in organizationally
  • Aparna will initiate a discussion on the development lists

Plan for next meeting

  • Facilitator: Katie
  • Note Taker: Lisa

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.