launchpad development|
Size: 6539
Comment:
|
Size: 7420
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * Asia``Pac '''Tuesday 02-Dec-2008 0300 UTC - 0345 UTC''' * AMEU '''Wednesday 26-Nov-2008 1500 UTC - 1545 UTC''' |
* Asia``Pac '''Wednesday 04-Mar-2009 2230 UTC - 2315 UTC''' * AMEU '''Wednesday 04-Mar-2009 1500 UTC - 1545 UTC''' |
| Line 22: | Line 22: |
| * Come prepared for next meeting with top 1-2 m-p bugs for code review team to consider * If there's time, the old boring script * Next meeting * Action items * Queue status * Mentoring update * al-maisan looking for a mentor * Getting graphs in place before rolling out features (way before) - beuno |
* Reviewers to enforce bug<->branch linking for all non-trivial branches (intellectronica) * Determine official preference, if any, of Storm usage: And(expr, expr) vs. expr & expr, Gary * Determine why _get_store uses protected spelling, and if we think it should, Gary * Merge proposals and cover letters (barry) * Using OCR for JavaScript reviews (mars) * Peanut gallery (anything not on the agenda) * Mentoring update * Action items |
| Line 35: | Line 35: |
| * your name, date, reason | * your name, date |
| Line 39: | Line 39: |
| * barry to look into techniques for eliminating back-patching of schema types (avoiding circular imports) | * bigjools to take crack at helper functions for backpatching schemas to avoid circular imports * intellectronica to come back from sabbatical * thumper to open bug on `webservice` pagetests globs problem * abentley to experiment on storm base class * barry to add `field_id` to coding guideline * barry to update guidelines to never call `_foo()` methods from outside a class * barry to add `pretty()` functions to reviewers docs * flacoste to work on API reviewer cheat sheet |
| Line 45: | Line 52: |
| * your topic, your name |
|
| Line 48: | Line 57: |
| * [[ReviewerMeeting20090218]] * [[ReviewerMeeting20090211]] * [[ReviewerMeeting20090204]] * [[ReviewerMeeting20090128]] * [[ReviewerMeeting20090121]] * [[ReviewerMeeting20090114]] * [[ReviewerMeeting20090107]] * [[ReviewerMeeting20081217]] * [[ReviewerMeeting20081210]] * [[ReviewerMeeting20081209]] * [[ReviewerMeeting20081203]] |
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 04-Mar-2009 2230 UTC - 2315 UTC
AMEU Wednesday 04-Mar-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
Reviewers to enforce bug<->branch linking for all non-trivial branches (intellectronica)
Determine official preference, if any, of Storm usage: And(expr, expr) vs. expr & expr, Gary
- Determine why _get_store uses protected spelling, and if we think it should, Gary
- Merge proposals and cover letters (barry)
Using OCR for JavaScript reviews (mars)
- Peanut gallery (anything not on the agenda)
- Mentoring update
- Action items
Apologies
Please include the date for which you will be unavailable.
- your name, date
Outstanding Actions
- bigjools to take crack at helper functions for backpatching schemas to avoid circular imports
- intellectronica to come back from sabbatical
thumper to open bug on webservice pagetests globs problem
- abentley to experiment on storm base class
barry to add field_id to coding guideline
barry to update guidelines to never call _foo() methods from outside a class
barry to add pretty() functions to reviewers docs
- flacoste to work on API reviewer cheat sheet
Notes
Proposed items
- your topic, your name
Rejected items
