launchpad development|
Size: 7842
Comment:
|
Size: 8419
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * AMEU '''Wednesday 09-Sep-2009 1500 UTC - 1545 UTC''' * Asia``Pac '''Wednesday 09-Sep-2009 2230 UTC - 2315 UTC''' |
* AMEU '''Wednesday 07-Oct-2009 1500 UTC - 1545 UTC''' * Asia``Pac '''Wednesday 07-Oct-2009 2100 UTC - 2145 UTC''' |
| Line 24: | Line 24: |
| * `__iter__()` in model objects? [cprov, barry] * mkstemp()/open() combination leaks file-descriptors [cprov] * Guidelines changes for tests checking systems pre-requisites (specific umasks, app configurations) [maxb, cprov] * Invalid markup; The <script> tag requires a close tag (Do not: <script type="text/javascript" src="..."/>) [Curtis] * 4-space indents for CSS styles [barry] |
* Careful with those drive-bys, they make reviewing unnecessarily harder [intellectronica] * How can we better incorporate drive-bys and other tech debt payoff into our development process? [barry] * Noodles and I (Edwin) discovered that we were using different guidelines for what goes into the view.label property. * My method reduces the amount of redundancy between the <h1> and the breadcrumbs directly below it. For example: || '''Define upstream link''' <<BR>> Ubuntu >> 9.04 >> “mozilla-firefox” source package >> Define upstream link || * Noodle's method could have better google foo, since it puts more relevant info in the <h1>. For example: || '''Define upstream link for mozilla-firefox in Ubuntu Jaunty''' <<BR>> Ubuntu >> 9.04 >> “mozilla-firefox” source package >> Define upstream link || |
| Line 47: | Line 49: |
| Line 50: | Line 53: |
| * [[ReviewerMeeting20090930]] * [[ReviewerMeeting20090923]] * [[ReviewerMeeting20090916]] * [[ReviewerMeeting20090909]] |
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 07-Oct-2009 1500 UTC - 1545 UTC
AsiaPac Wednesday 07-Oct-2009 2100 UTC - 2145 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
- UI review call update
- Careful with those drive-bys, they make reviewing unnecessarily harder [intellectronica]
- How can we better incorporate drive-bys and other tech debt payoff into our development process? [barry]
- Noodles and I (Edwin) discovered that we were using different guidelines for what goes into the view.label property.
My method reduces the amount of redundancy between the <h1> and the breadcrumbs directly below it. For example:
Define upstream link
Ubuntu >> 9.04 >> “mozilla-firefox” source package >> Define upstream link
Noodle's method could have better google foo, since it puts more relevant info in the <h1>. For example:
Define upstream link for mozilla-firefox in Ubuntu Jaunty
Ubuntu >> 9.04 >> “mozilla-firefox” source package >> Define upstream link
- Peanut gallery (anything not on the agenda)
Apologies
Please include the date for which you will be unavailable.
yourname, date
Outstanding Actions
- gary_poster and barry will transfer review guidelines from the old wiki and old old wiki to the new wiki
Notes
Proposed items
yourtopic [yourname]
Rejected items
