6663
Comment:
|
6981
|
Deletions are marked like this. | Additions are marked like this. |
Line 13: | Line 13: |
* Asia``Pac '''Tuesday 09-Dec-2008 0300 UTC - 0345 UTC''' * AMEU '''Wednesday 03-Nov-2008 1500 UTC - 1545 UTC''' |
* Asia``Pac '''Wednesday 18-Feb-2009 2300 UTC - 2345 UTC''' * AMEU '''Wednesday 18-Feb-2009 1500 UTC - 1545 UTC''' |
Line 22: | Line 22: |
* Printing strings in doctests (barry) * Is OCR still relevant in a world with merge proposals? (barry) * Sabbaticals? (barry) * Do we need a standard cover letter template for merge proposals? (barry) * https://pastebin.canonical.com/11767/ * If there's time, the old boring script * Next meeting * Action items * Mentoring update * Queue status |
* Action items * Mentoring update * Reviewers to enforce bug<->branch linking for all non-trivial branches (intellectronica) * Peanut gallery (anything not on the agenda) |
Line 38: | Line 31: |
* your name, date, reason | * abentley, Feb 18 * mars, flacoste, danilo, rockstar, intellectronica, Feb 18 |
Line 42: | Line 36: |
* barry to look into techniques for eliminating back-patching of schema types (avoiding circular imports) | * abentley to experiment on storm base class * barry to add `field_id` to coding guideline * barry to add `pretty()` functions to reviewers docs * flacoste to work on API reviewer cheat sheet |
Line 48: | Line 45: |
* Gotchas with new celebrities (Julian) | * your topic, your name * Determine official preference, if any, of Storm usage: And(expr, expr) vs. expr & expr, Gary |
Line 53: | Line 51: |
* [[ReviewerMeeting20090211]] * [[ReviewerMeeting20090204]] * [[ReviewerMeeting20090128]] * [[ReviewerMeeting20090121]] * [[ReviewerMeeting20090114]] * [[ReviewerMeeting20090107]] * [[ReviewerMeeting20081217]] * [[ReviewerMeeting20081210]] * [[ReviewerMeeting20081209]] |
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 Wednesday 18-Feb-2009 2300 UTC - 2345 UTC
AMEU Wednesday 18-Feb-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
- Action items
- Mentoring update
Reviewers to enforce bug<->branch linking for all non-trivial branches (intellectronica)
- Peanut gallery (anything not on the agenda)
Apologies
Please include the date for which you will be unavailable.
- abentley, Feb 18
- mars, flacoste, danilo, rockstar, intellectronica, Feb 18
Outstanding Actions
- abentley to experiment on storm base class
barry to add field_id to coding guideline
barry to add pretty() functions to reviewers docs
- flacoste to work on API reviewer cheat sheet
Notes
Proposed items
- your topic, your name
Determine official preference, if any, of Storm usage: And(expr, expr) vs. expr & expr, Gary
Rejected items