Babydev bait

[denise]

Last week, afuna made a list of babydev-bait in dw_dev. Well, we all rock so hard that most of those bugs have been patched (and the ones that weren't have been claimed), so it's time to make a new list.

All of these should be good starting places for someone who's just getting their feet wet with the codebase. I've scored each one on a level of 1-3, where 1 is "really really easy" and 3 is "still suitable for a beginner, but a little more complicated".

If you're just getting started with us, check out the Getting Started and the Beginning Dev Checklist!

NOTE: April 15 is the milestone freeze for open beta. Past April 15, we won't be checking in any patches that don't patch an open-beta-blocking item. This doesn't mean you shouldn't work on things that aren't open-beta blockers -- your code will get reviewed and checked in, just not immediately! (And those two weeks between milestone freeze and open beta launch can be a good time to work on something more complex.)

Some of these require perl knowledge; some require Javascript or CSS knowledge. If you look at one and go "I have no idea how to do this", try another one! There's a wide assortment in here.



[•] Bug 518: Add missing $EMBED_MODULE_DOMAIN to configuration
[•] Bug 671: Remove journal link from notification for being circled by openid users
[•]Bug 418: Browse button breaks box border
[•]Bug 774: manage/invitecodes.bml isn't linked from manage/index.bml
[•]Bug 773: ToS link on invite response page doesn't open a new window
[•]Bug 771: finish stripping /register.bml
[•]Bug 748: circle updates in inbox url should have 'friendplus' removed
[•]Bug 730: AIM icon in profile
[•]Bug 728: Contextual hover popup shows 'loading' over user links with site=foo
[•]Bug 725: Remove subscription tickybox
[•]Bug 702: Fix tab ordering on changeemail.bml
[•]Bug 698: Change synlevel to cut
[•]Bug 696: Repeat add button on add.bml
[•]Bug 685: Circle wording should be changed on edit community profile page
[•]Bug 679: All users can_manage themselves
[•]Bug 664: remove verticals from qotd
[•]Bug 632: Provide a "contact us if you can't use this" string under all CAPTCHAs
[•]Bug 627: user-tag /manage/circle/add.bml
[•]Bug 606: Tropo: CSS-style support/highscores.bml



[••]Bug 154: Add a link back to parent comment and its parent comment
[••]Bug 407: Manage circle should also include member status for communities
[••]Bug 586: alias ?format=light to ?style=light
[••]Bug 326: Add current subscription count to manage/settings/?cat=notifications
[••]Bug 126: Invalid form submission when posting comment should contain the comment text
[••]Bug 491: selecting/deselecting colors when adding to circle
[••]Bug 492: color previews on /manage/circle/add
[••]Bug 497: standardize custom color options between /add and /edit
[••]Bug 630: Navstrip color choice follows journal preference, not logged-in viewing preference
[••Bug 487: ajax-y track button (in S2 layouts) throws a JS error if you're a free account
[••]Bug 486: Hierarchical moodtheme tree does not have the proper indentation
[••]Bug 419: Auto-click 'from URL/file' radio buttons when user inputs URL or browses for file (JS)
[••]Bug 763: journal title on profile
[••]Bug 762: make tags in entries a horizontal list
[••]Bug 761: Highlight navlink on current view with a class
[••]Bug 751: public but unspecified location display
[••]Bug 743: Show access/subscriptions in common when viewing profiles
[••]Bug 742: Remove remnants of shared journal support
[••]Bug 701: ext_nnn form used for OpenID users in various PM-related locations
[••]Bug 673: OpenID accounts should be able to set a different website URL
[••]Bug 663: Allow S2 to access whether the viewer is allowed to manage tags on the journal they are viewing
[••]Bug 598: Change how <user> tag is rendered
[••]Bug 340: suspended journals shouldn't display adult content check


[•••]Bug 645: OpenID login from navbar should return you to page you were viewing
[•••]Bug 48: Respect lj-cut in the Inbox, as a user-defined parameter
[•••]Bug 596: Allow importer to correctly import from multiple sites.
[•••]Bug 571: Make frontend for importer (NB: talk to me about what it should have!)
[•••]Bug 764: Clarify that the tags module shows only the latest X tags
[•••]Bug 752: Rewrite user links on incoming LJ feeds
[•••]Bug 724: Deal with "lj" in opt_ljcut_disable_* options
[•••]Bug 721: Change lj- headers for email posting to site-agnostic forms
[•••]Bug 715: distinguished collapsed comments from screened/deleted/suspended comments
[•••]Bug 480: Add optional "reason I am deleting my journal"
[•••]Bug 420: Add separate 'email address to display on profile'

Comments

[mnfiddledragon]

I have a couple of questions:

1) Do all developers submitting code for check in run on some flavor of linux? (I do, I just have been going through the developer checklist and getting started guide and have some ideas...)

2) There's a lot of manual copying of files that leave room for human error in the development process - and this just for making sure that you've got your code in the cvs workspace for patchset checkin and in the live area for testing. It's good to it in both places...but wouldn't it be better to have some developer tools available to make these processes automated? It would make that grunt work a) easier, b) more consistent, and c) less prone to error which would allow for easier debugging of actual code as opposed to processes errors.

That's probably a good place to start. Bite off little bits and then move from there?

[denise]

1). I think everyone does right now, although someone was trying to get the code installed on their Mac. (Don't think they succeeded, though...) The Dreamhack service uses Ubuntu, and I think it's the same version as we run in production.

2). Well, there is bin/cvsreport.pl (which is legacy from the old way of LJ development, when LJ was still using cvs as opposed to Subversion, which I believe they're using now, or Mercurial, which is what we're using) -- that does all the copying around for you if you ask it to. But yeah, definitely room for improvement there.

[sophie]

The Dreamhack service uses Ubuntu, and I think it's the same version as we run in production.

Not quite - it used to be the same version, when production was running Hardy Heron, but now production is running Intrepid Ibex while the hack machine is still on Hardy.

I should update some time, but I'm not sure what (if any) breakage I can expect.

[sophie]

To expand on Denise's answer to 1), while pretty much all the DW installations are on a flavour of Linux, our devs themselves come from a variety of backgrounds. However, most of us use Dreamhacks to make our patches, which, as Denise said, runs Ubuntu.