Jun. 28th, 2010

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
A comment made in Bugzilla this morning had me thinking: what are the variables we use by convention (or should use) everywhere throughout the code? I want to make a list of them so that a) people can know what they are and not re-use them for other things, and b). we can go through and change things that don't use them.

The ones I immediately thought of are:

$u: user object
$remote: remote logged-in viewer


What else is there? (And if there isn't a convention for a specific reference, and it's got five or six variable names throughout the code, mention that too, so we can standardize.)
azurelunatic: aerial view of freeways.  (freeway)
[personal profile] azurelunatic
This code tour is brought to you by the San Andreas or San Gregorio Fault, which provided the bulk of this morning's excitement in Miss Lunatic's neighborhood.

Welcome to new patch contributor [personal profile] catness! This code tour also introduces documentation changes being tracked through Bugzilla, as well as other tasks. There are 37 feature-and-bugfix bugs resolved this week, and 1 documentation bug.

Out in front in this week's resolved bugs is [personal profile] szabgab, who is responsible for many patches over quite some time on one testing megabug. It may only have been one bug, but it was an enormous amount of work, and we salute you.

Then we've 9 patches from [staff profile] denise, 8 patches from [personal profile] kareila, 3 patches from [personal profile] fu, 3 patches and some serious image wrangling by [personal profile] ninetydegrees, 2 patches each from [personal profile] foxfirefey, [personal profile] rho, and new developer [personal profile] catness, and one patch each from [personal profile] exor674, [personal profile] aveleh, [personal profile] kaisa, [personal profile] allen, [personal profile] chemicallace, [personal profile] yvi, and returning developer [personal profile] penemue. SpamAssassin handling was implemented by [staff profile] mark.

Thanks to the other people who help keep these running: the reviewers, the people debating the best way to implement, everybody in Support troubleshooting and reporting things, the people who cheer when a new patch lands in IRC, and many more. Some specific shoutouts: policy from [staff profile] mark and [staff profile] denise, reviewing from [personal profile] allen, [personal profile] domtheknight keeping a Support-ive eye on things, some good Support bug descriptions from [personal profile] cesy and [personal profile] zarhooie, [personal profile] pauamma monitoring [livejournal.com profile] changelog for useful changes to the code we inherited, [livejournal.com profile] andy and colleagues at LiveJournal for their continuing work on our parent codebase (1 patch imported from them this time around), some nice teamwork and troubleshooting from [personal profile] yvi, [personal profile] domtheknight, [personal profile] kareila, [personal profile] exor674, [personal profile] kaisa, [staff profile] mark, [personal profile] fu, [personal profile] foxfirefey, [personal profile] cesy, and [personal profile] sophie, and bonus backchannel (over-the-shoulder?) support from [personal profile] alierak.

Stuff in this code tour won't be live until the next code push. See [site community profile] dw_maintenance for advance notice of scheduling, and @dreamwidth for up-to-the-minute information if stuff has gotten all weird.


And onward to the actual tour!


Bugs and Improvements



Read more... )

Documentation



Read more... )

Profile

dw_dev: The word "develop" using the Swirly D logo.  (Default)
Dreamwidth Open Source Development

May 2025

S M T W T F S
    123
4 5678910
11121314151617
18192021222324
25262728293031

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 8th, 2025 08:44 am
Powered by Dreamwidth Studios