Babydev bait

[denise]

It's been a while since we've had a list of babydev bait (for those who are new: "babydev bait" means bugs that are quick and relatively uncomplicated, and that don't look intimidating, that are likely to tempt people into getting started with DW development). And, since I recently did a suggestions run, there's a whole bunch of new bugs in Bugzilla to pick from!

This list is sorted from one point to three points, where one is "really suitable for a beginner with little to no knowledge of the DW codebase" and three is "more complex, but still quite do-able". I'll try to keep the list updated by striking out any that get claimed for at least the next week!

Some require HTML and CSS knowledge, some require JS, some require perl, some require a mixture. If one of these doesn't suit you, check out another. This list is also only from the recent suggestions run & other recent bugs logged, so there might still be more lurking in the older stuff.



[•]

Bug 2909: Remember ?style=mine when moving between entries in a journal
Bug 2908: remember "send me a copy of my own message" selection for next time
Bug 2906: better subject line for a copy of your own message
Bug 2903: Repeat links to original articles at the bottom of every feed entry
Bug 2900: Outdated "locations" menu - the Balkans remix
Bug 2887: Add entry title to "view this entry" email link
Bug 2886: Allow title attributes to links list entries
Bug 2885: Allow XFN relationships to be defined in Links List
Bug 2875: Your Layers page: sort by name instead of number
Bug 2866: Attach a note when transferring points
Bug 2840: Page title should not change to just "Post comment" on the post comment (?mode=reply) page
Bug 2839: Display tags on the post comment page
Bug 2836: Prevent OpenID relationships from cluttering profile pages
Bug 2830: Add Ravelry as a profile external site
Bug 2827: Also count screened comments
Bug 2814: Don't announce upcoming birthdays for memorial journals


[••]

Bug 2923: Entries marked as nsfw/18+ by maintainers don't have an explanatory message
Bug 2920: ajax cut expander should work on latest things page
Bug 2890: Accepting closed community invite and adding to reading list doesn't add to default view
Bug 2871: Button to Bulk-Delete 0-Entry Tags
Bug 2865: style=mine in Inbox
Bug 2852: Separate "Edit Profile: Success" message for communities
Bug 2816: Create option for easy embedding of cut text into entry

[•••]

Bug 2927: create better dw-free index.bml
Bug 2879: Collapse Cut button at end of cut
Bug 2876: Your Layers page: redesign layers table as a tree
Bug 2843: Show tags in Inbox Entries

Comments

[sporky_rat]

So if I wanted to try bug 2900, where would be the logical (or illogical, if the case may be) place to start?

[yvi]

dw/bin/upgrading/base-data.sql , I would say :)

[sporky_rat]

Thanks, Yvi! Now if I can just get the internet to connect to my hack, I could see about poking around!

[tangent_woman]

Erm... I was wondering the same thing (different bug) and I'll be reading the information here:
http://wiki.dwscoalition.org/notes/Beginning_dev_checklist

Not sure if that's of use to you, but it will do me for starters.

[sporky_rat]

I've been following that, but my trouble is finding where in the code data base to really start for something in particular. My only coding experiences have been HTML, a little CSS and some Pascal.

[yvi]

If it helps, I just searched for "germany" in the codebase :)

[tyggerjai]

http://wiki.dwscoalition.org/notes/Dev_Finding_Things has some good tips.

[bork]

So, I have a question, if no one minds.

Is there a document anywhere that explains the bug fixing process? I'm interested in fixing some of the technical documentation and usability bugs that are out there; I have the time, I have the interest, and I have the ability. I'm thinking of Bugzilla bug #2979 - "change 'site scheme' to 'site skin'" in particular.

Like, I make an account on Bugzilla, but then what do I do? Just find a bug I think I can fix and do so? Or, do I submit the change to someone?

Thanks, bork.

[denise]

There's information on the Wiki:

http://wiki.dwscoalition.org/notes/Category:Development
http://wiki.dwscoalition.org/notes/Dreamhack_Getting_Started
http://wiki.dwscoalition.org/notes/Dev_Getting_Started

[bork]

Great - thank you!!

[denise]

You're welcome! Welcome to DW dev :)

[bork]

Also - should I sandbox documentation bugs? (Not bugs where a word is hard coded into code, but bugs where a phrase just needs to get swapped out in a FAQ?)

Or, just follow the procedures outlined here: http://dw-docs.dreamwidth.org/28244.html?

Thanks for answering my questions on this!

[denise]

If they're big (new FAQs, etc), put them in Bugzilla as described in http://dw-docs.dreamwidth.org/28143.html -- if they're little (small phrase changes) they go at http://dw-docs.dreamwidth.org/28420.html?style=mine#comments