foxfirefey (
foxfirefey) wrote in
dw_dev_training2009-05-18 02:49 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Entry tags:
Starter bugs
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.
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.
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
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
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 customizationBug 1177: put userhead in "To: [user]" field in PM replyBug 1135: enable maintainers to leave comm if comm is deletedBug 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 subscribeBug 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.
no subject
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.
no subject
I also love the idea of having a Bugzilla search for suitable starter bugs.
no subject
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...
no subject
no subject
no subject
no subject
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?
no subject
But yes, it'd be nice to be able to sort through bugs by what kind of work they do, too.