launchpad development|
Size: 6557
Comment:
|
Size: 6863
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * Asia``Pac '''Tuesday 23-Dec-2008 0300 UTC - 0345 UTC''' * AMEU '''Wednesday 07-Jan-2009 1500 UTC - 1545 UTC''' |
* Asia``Pac '''Tuesday 03-Feb-2009 0300 UTC - 0345 UTC''' * AMEU '''Wednesday 28-Jan-2009 1500 UTC - 1545 UTC''' |
| Line 31: | Line 31: |
| * your name, date, reason | * intellectronica, January 28th, Scheduling error |
| Line 43: | Line 43: |
| * Should new classes be forbidden to use SQLObject compatibility layer, abentley * encourage appropriate RENormalizer use in doctests (it is nicer than ellipses in many cases), gary |
|
| Line 48: | Line 50: |
| * [[ReviewerMeeting20090121]] * [[ReviewerMeeting20090114]] * [[ReviewerMeeting20090107]] |
Agenda of the next Launchpad review team meeting
Launchpad review team meetings are held on #launchpad-meeting on irc.freenode.net, and are chaired by BarryWarsaw for both the Asia/Pacific (AsiaPac) and Americas/EU (AMEU) time zone meetings. We use MootBot to record the meetings.
The purpose of the meetings is to coordinate Launchpad code reviews, and particularly to ensure that emerging issues with the review process are addressed - such as getting people to take on tough reviews, keeping the latency down, etc.. Blockage in reviews leads to blockage in Launchpad code landings.
The next Launchpad review team meeting will be held at this time:
AsiaPac Tuesday 03-Feb-2009 0300 UTC - 0345 UTC
AMEU Wednesday 28-Jan-2009 1500 UTC - 1545 UTC
You can add new items to the list of proposed items. If they don't make it onto this meetings agenda, they'll most likely get onto the next meeting's agenda instead.
Agenda
- Roll call
- Peanut gallery (anything not on the agenda)
- Action items
- Mentoring update
Apologies
Please include the date for which you will be unavailable.
- intellectronica, January 28th, Scheduling error
Outstanding Actions
- barry to look into techniques for eliminating back-patching of schema types (avoiding circular imports)
barry to add pretty() functions to reviewers docs
- flacoste to work on API reviewer cheat sheet
Notes
Proposed items
- Should new classes be forbidden to use SQLObject compatibility layer, abentley
- encourage appropriate RENormalizer use in doctests (it is nicer than ellipses in many cases), gary
- your topic, your name
Rejected items
