launchpad development|
Size: 7172
Comment:
|
Size: 7694
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * AMEU '''Wednesday 18-Mar-2009 1500 UTC - 1545 UTC''' * Asia``Pac '''Wednesday 18-Mar-2009 2230 UTC - 2315 UTC''' |
* AMEU '''Wednesday 22-Apr-2009 1500 UTC - 1545 UTC''' * Asia``Pac '''Wednesday 22-Apr-2009 2230 UTC - 2315 UTC''' |
| Line 22: | Line 22: |
| * Action items * Mentoring update |
|
| Line 23: | Line 25: |
| * Mentoring update * Action items |
|
| Line 34: | Line 34: |
| * gary_poster to add `getStore()` as an alias for `_get_store()` * flacoste to look into storm/sqlobject result set compatibility * gary_poster will check to see if there's a bug open for adding a hook to `bzr send`, and submit one if there isn't * bigjools to take crack at helper functions for backpatching schemas to avoid circular imports * thumper to open bug on `webservice` pagetests globs problem |
* allenap to look into storm/sqlobject result set compatibility |
| Line 43: | Line 39: |
| gary writes: * What is the goal (are the goals?) of our use of security proxies and the import nazi? My understanding is that they are "belt and suspenders" to try and keep us from revealing private information. * Do we still agree with those goals? * Do we feel that our use of security proxies helps us with these goals? * Do we feel that our use of the import nazi helps us with these goals? As we know, security is very hard, and trying to answer these questions well should not be done lightly or too quickly. I am hopeful that the small, specific question of whether we should import removeSecurityProxies in view code will fall out obviously, if not easily, from our answers to the discussion above. |
|
| Line 46: | Line 56: |
| * plurals, curtis | * don't return unwrapped objects from view methods, barry and gary ("the fightin' arries!") |
| Line 51: | Line 61: |
| * [[ReviewerMeeting20090415]] * [[ReviewerMeeting20090408]] |
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:
AMEU Wednesday 22-Apr-2009 1500 UTC - 1545 UTC
AsiaPac Wednesday 22-Apr-2009 2230 UTC - 2315 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
- Peanut gallery (anything not on the agenda)
Apologies
Please include the date for which you will be unavailable.
- your name, date
Outstanding Actions
- allenap to look into storm/sqlobject result set compatibility
- flacoste to work on API reviewer cheat sheet
Notes
gary writes:
- What is the goal (are the goals?) of our use of security proxies and the import nazi? My understanding is that they are "belt and suspenders" to try and keep us from revealing private information.
- Do we still agree with those goals?
- Do we feel that our use of security proxies helps us with these goals?
- Do we feel that our use of the import nazi helps us with these goals?
As we know, security is very hard, and trying to answer these questions well should not be done lightly or too quickly.
I am hopeful that the small, specific question of whether we should import removeSecurityProxies in view code will fall out obviously, if not easily, from our answers to the discussion above.
Proposed items
- your topic, your name
- don't return unwrapped objects from view methods, barry and gary ("the fightin' arries!")
Rejected items
