Starter bugs

[foxfirefey]

This post is an attempt to reach out to people who aren't in IRC but still interested in starting development, to assist them and get things rolling. Here I've made a list of things that look like good starter candidates from effort-minor and unassigned tickets on Bugzilla in this post. People who have suggestions for other bugs or think some should not be included, let me know.

You can browse through the code at the repository, and we have a page on the layout of the main folder. If you want to start doing development, the easiest way is to get ahold of a Dreamhack. That's a ready made and hosted DW install. Once you have one, you'll have to keep the code updated. Right now we have around one month until our next code push due to mark's wedding and honeymoon!

More documentation:

Beginning dev checklist
Bugzilla workflow -- here you can find instructions on creating an account and claiming bugs
Dev Finding Things
Dev Programming Guidelines, summaried in Programming Guideline Checklist
Dev Version Control

The following is a list of about 60 smaller bugs; some are easier than others. If you feel like doing one, browse through them and see if there are any that strike your fancy. If you want to claim one, claim it on Bugzilla and post a comment about it here so I can mark it as taken.

• Bug 1217: Expanded comments don't have contextual hovers
• Bug 1214: Add "join community" link on protected entries in open communities
• Bug 1183: Tags module on Tags page ignores tags limit
• Bug 1182: Link to advanced customization
• Bug 1177: put userhead in "To: [user]" field in PM reply
• Bug 1135: enable maintainers to leave comm if comm is deleted
• Bug 1060: Journal title on profile page needs to be bigger
• Bug 1104: Replyto page lacks context
• Bug 1123: Post image link broken on update page -- afuna is tackling this one
• Bug 1044: add warning when buying paid time for a deleted account
• Bug 1043: remove "upgrade" step in creation flow when code pre-loaded with paid time
• Bug 1042: prevent purchase of paid time for someone who's banned you
• Bug 1035: Add comment-count image to crossposted entries
• Bug 1029: Conextual hover on openID should offer grant access instead of subscribe
• Bug 1018: 'View in my style' link on navigation strip behaves weirdly
• Bug 989: Additional elements should be wrapped in a heading tag
• Bug 992: Links on standout have poor contrast in tropo purple
• Bug 936: site="dreamwidth.org" in user tag parsed as unknown external site -- note, this shouldn't be hard coded to accept dreamwidth.org, but to use $LJ::DOMAIN as a guide
• Bug 962: manage circle page doesn't error if an invalid account is provided
• Bug 930: Need to go over tag cloud for semantics/accessibility
• Bug 921: importer not rewriting <lj user> tags in subjects for cross-site
• Bug 924: Modules section of wizard needs better labels
• Bug 912: Page does not jump to just-posted comment when collapsed
• Bug 898: rename user layer to wizard layer
• Bug 887: add link to "display" options to logged-out pages
• Bug 890: Misleading link text on navstrip when there is a one-way relationship
• Bug 892: Remove @PROTECTED_USERNAMES from etc/config.pl
• Bug 878: Inbox has tropo-red colours hard-coded
• Bug 858: Private messages strip (rather than escape) HTML -- foxfirefey is using this one for a dev walkthrough
• Bug 846: Replying to a private message doesn't mark it as read
• Bug 939: allow people to choose whether or not to be notified on crosspost
• Bug 844: Prefatory + in tag name renders tag unusable
• Bug 827: Allow community admins to remove subscribers -- misleading title; this is more about not having deleted accounts show up as subscribers on profiles
• Bug 809: popup overlaps links on create widget -- mostly a specific browser problem for Safari/Mac and Chrome
• Bug 807: Improve print_module_syndicate (core2)
• Bug 814: Tropo: <q> needs to be re-added to the CSS definitions
• Bug 806: Improve CSS for displaying regular mini-calendar in sidebar (negatives)
• Bug 813: warn if you are about to send a PM with no text
• Bug 815: User's default icon is cut off in the title bar
• Bug 725: Remove subscription tickybox
• Bug 715: distinguished collapsed comments from screened/deleted/suspended comments
• Bug 684: Logo does not link to $SITEROOT in Camino/Mac -- a very fiddly tricky bug for Camino
• Bug 701: ext_nnn form used for OpenID users in various PM-related locations
• Bug 724: Deal with "lj" in opt_ljcut_disable_* options
• Bug 611: linebreak quoted material in private messages at 80 characters
• Bug 586: alias ?format=light to ?style=light
• Bug 480: Add optional "reason I am deleting my journal"
• Bug 479: Add "link to top of thread" to comment email
• Bug 476: Make site scheme menus available to S2
• Bug 361: Disable/remove "Comment" button when user isn't allowed to comment
• Bug 356: Resubscribing to an inactive subscription results in multiple subscriptions
• Bug 340: suspended journals shouldn't display adult content check
• Bug 318: Add "useful posting" links to update.bml
• Bug 313: refreshing Inbox page doesn't clear checked "check all" checkbox if not all items acted on
• Bug 282: kill journaltype N support
• Bug 238: "Turn on cookies?" warning on certain login redirects
• Bug 206: Birthday display management
• Bug 200: Limit the number of characters that can be entered as custom CSS

If you run into problems or have questions, I encourage you to ask them in comments to this post or in the community; use as much detail as you can describing what you're trying to do and how you want to do it. People who already do DW development, I encourage you to track this post or pop in from time to time for people asking questions.

Comments

[ct]

What's the protocol if we think that a bug may have been fixed but not closed?

I'm looking at Bug #1131 from above - Untrack this has a pushpin instead of a bell. Under all four site schemes, I'm seeing a bell with an X on it on posts that I'm tracking, not a pushpin.

[foxfirefey]

You're right--but I don't think the bug is fixed entirely yet. When you're subscribing to a post with the AJAX option, it replaces it with the pushpin image instead of the bell with the X. I've added that as a note on the bug report, thanks!

[wyntarvox]

That's actually reported separately (I believe afuna just marked #1131 as a duplicate), and should be fixed soon as long as my patch checks out okay.

[foxfirefey]

Apparently so! Thank for the update, I'll take it off the list.

[ct]

Ah. That makes sense. I'm only vaguely aware of what "the AJAX option" is. Live and learn...

As long as I'm bugging you with questions... is O'Reilly's camel book still considered a good perl reference? I'd like to be able to contribute to development, but I'm more of a Java person so I have some learning to do first.

[foxfirefey]

Bug away! That's what this post is for.

Your comment made me realize I should give a little more explanation for anybody who doesn't know what I meant by the AJAX option (bad me, slipping into inaccessible lingo): basically if you click on the tracking button on a post, a little div pops up with options which all disappear when you hit the save button, letting you dynamically submit your request without a page reload. This technique is called AJAX.

We have two freely available online books for Perl that we point people to:

Beginning Perl and Picking Up Perl. There is also a Wikibook on Perl Programming.

However, I have always liked the Camel book myself, so if you have access to it, I recommend it. But it's not your only option, and nobody needs to buy a book just to catch up!

[ct]

Gotcha. Thanks :)

[wyntarvox]

Another update! #618 is actually a dupe of the resolved fixed #335, which I just indicated on zilla as well.

[foxfirefey]

Well, that's one way to reduce a bug count! Thanks for the sharp eye.

[afuna]

Just claimed Bug 1123

[foxfirefey]

Noted!

[afuna]

I wonder -- does this search work for you? http://bugs.dwscoalition.org/buglaist.cgi?cmdtype=runnamed&namedcmd=starter

Only a partial list so far, as an experiment. I can't get to it logged out, and I don't know if being logged in as someone else will let me see it.

[foxfirefey]

No--it tells me "the search named starter does not exist". (I fixed the typo of an "a" in "buglaist".)

I also love the idea of having a Bugzilla search for suitable starter bugs.

[afuna]

Aw, man. I did that using the "named tag" for bugs thing, but I guess that is only for personal use. I think that only D and Mark can share searches, but if we used named-tags, I think that would mean that the person doing the sharing would have to do the updating, which would be a lot of effort.

Maybe we could ask for a "suitable for starters" keyword, instead? Anyone can add a keyword, and we can set up a search quite easily...

[foxfirefey]

I think a keyword is a good idea, and very much in line with our babydev friendly ethos!

[afuna]

Bring it up to Mark and D if you can catch them online? I think right now is very late for all of you! *g*

[foxfirefey]

It is getting late! I will do it if I see them.

[afuna]

One more thought:

should we split it up into "css-y", "js-y", "perl-ish", "s2-ish" etc? Would that makes things easier to find, for someone looking for a bug within their range?

[foxfirefey]

I don't think it'd be bad to have additionally keywords for expertise focus for all bugs, either! Probably want "database", too? Not sure what others.

But yes, it'd be nice to be able to sort through bugs by what kind of work they do, too.

[afuna]

Took :

Bug 1135
Bug 1043
Bug 1042

And I've just finished adding the "introduction" keyword up to bug 936 on the list.

[yvi]

I have no idea whether anyone is still using this, but I assigned myself:

Bug 1177: put userhead in "To: [user]" field in PM reply

and

Bug 846: Replying to a private message doesn't mark it as read

Let's see how that works out.

[foxfirefey]

I know that it's a bit outdated; people have been doing bugs but not commenting here. I also know that the system has started to be revamped so that there is an introduction tag, and I should make a post about that. But I'm glad you are taking some!