Basie Blog

Status

• Completed ticket #192, do not show Locked projects
• Started work on ticket #118, project descriptions and catchphrases
• Started work on the new portal welcome page #212

Next

• Add a ticket for the new portal page ( Nikita did this for me.. I still can’t add tickets )
• Complete ticket #118, project descriptions and catchphrases
• Complete the new portal welcome page ( #212 and #213 )

Roadblocks

• Make sure that everyone agrees on the new portal welcome page for 0.6
• Figure out if we really want to hide Locked projects or not
• Figure out why I can’t add new tickets anymore

Status

• Posted patch for bug #71 (Hardcoded prefixes in Atom feed)
• Added changes suggested by Fancois to developers.txt, new diff is up on Review Board

Next Steps

• Work on bug #63(/login and /preferences should be secure (https))
• Test and include new Windows installation instruction into developers.txt
• Work on bug #175 (Download errors running bootstrap.py)

Roadblocks

• Doing 6 CS courses isn’t very easy, especially when they all have something due the same week

Status:

-Submitted a small iteration for the milestones list page.

- Began work on sorting of Milestones list, and a bug on editing milestones. (Ticket #115 and #168)

Road Blocks:

- Other than other school projects, None.

Read the rest of this entry »

Status

• Submitted patches for #119 (2), and #155.
• Started working on #97 (which has grown significantly), but not yet completed.
• Tested Nikita’s random generator, left comments.
• Did a whole bunch of compatibility testing on Windows, and created screen shots of bugs (IE8=10, Chrome=3, IE7=12, IE6=10, FF3.5=1?, FF3=0, FF2=2, general=5). NB: Currently assigned tickets #161 (IE8) and #160 (IE7) for compatibility testing.

Roadblocks

Next Steps

• File tickets for all known compatibility issues.
• Possibly do some testing for Opera(9,10) and Safari(4,3).
• Finish ticket #97.
• Start working on fixes for IE compatibility issues.

Status

• IRC mockup
• Tickets mockup
• Chat with Greg. In summary:
  • For 0.6, introduce a toggle to global search to search between portal and project. When in project mode, user can choose to switch between project or portal search. When in portal mode (e.g. user preferences), user can only search within the portal. For 0.7, search should account for user’s workflow mentality (e.g. going from a project to user preferences and then using search).
  • For 0.7: hide/show column preferences should be stored in user profiles.
  • For 0.7: re:search–allow users to “pin”/reference a ticket when searching.
• Catching up with mailing list/previous week’s questions:
  • Working with Guillaume to resolve project description visibility/editing
  • Re: wiki cheatsheet: a link should live in the footer, with lite WSYIWYG editor for wiki editable fields + link to cheatsheet.
  • Re: milestone history: Resolved to keep track of milestone history (detail to be mapped out).

Roadblocks

Next Steps (in order of priority?)

• File backlog of tickets from the last two weeks; file tickets for UI inconsistencies
• Flush out search and filtering across system
• Ticket details mockup
• Revise milestone details mockup to include history
• Revisit new header for switching between projects (like 37 Signals has done with BaseCamp–thanks Chris for the example).
• Personas for Basie?
• Blog/post mortem about the codesprint (from two weeks ago)

Status

• Milestone changes must show up in project history ( #29 ) Waiting for review
• Commited Check that ALL models are exposed through Django admin application ( #88 )

Next step

• Already started tickets # 54 and 109 ( Wiki: Cannot edit Wiki page title nor slug, Text in filter control for ‘Events’ much larger than text in filter control for ‘Tickets’ )
• Ticket 125 ( The links on the result page of the search (on the server) are broken. )
• Ticket 30 ( tickets: unassociation )

RoadBlocks

• I’ve sent a email concerning the project_slug for ticket #54 ( the edit wiki page ). The method to add field for the slug does’nt seem to be the same as name, content or comments…

Status

• Finished with the 2nd iteration of the dashboard, getting “Open Tickets Assigned to Me” working

RoadBlocks

• None

Next Steps

• Work on the 3rd iteration of the Dashboard, getting “Recent Activity” working
• work on assigned tickets #138  and #168 for 0.6 final

Status

• Worked mainly on
  • Improved Navigation — with current section highlighted, new styles
  • Sitewide Breadcrumbs
  • Dashboard (now on Iteration 3)
• Reviewed
  • Chad’s footer navigation
  • Guillame’s work on extracting inline JS from add_multiple_users template
  • Nikita’s fixes for “My Tickets,” for sorting tickets with filters, and his random-data tool
  • Jackie’s Milestone UI changes (Iteration 2)
  • Alex’s work on the “Open Tickets” for new Dashboard (Iteration 2)
  • A bunch of items on the mailing list
• Committed
  • Fix to Ticket #169: Owner and Status fields became links when adding/editing a ticket
  • Fix to Ticket #57: Fixed Wiki diff table
  • Fix to Ticket #150: Improved search form, added semantic elements (fixed 4 validation errors sitewide)
  • Pending Review (for Ticket #150): Navigation — current section highlighted (Iteration 1)
• New Tickets
  • Added Ticket #177 (Move common styles into separate stylesheets)
  • Added Ticket #174 (Home: Edit Homepage link appears for anonymous user)
  • Added Ticket #170 (Tickets: Filters are reset when table is sorted)
  • Added Ticket #168 (Edit Milestones broken)

Next Steps

• Working on “Recent Activity” sidebar for new Dashboard UI
• Uploading Breadcrumbs to ReviewBoard in piecemeal
• Continuing to work on patches for bug fixes for assigned tickets

Roadblocks

• None yet

Status

• Extracted javascript from the “Manage” app’s templates ( #48 )
• Extracted javascript from the “VCS” app’s templates ( #48 )
• Started a discussion on the mailing list concerning project descriptions in Basie ( #118 )

Next steps

• Implement the chosen solution for the project description ( #118 )
• Review some patches ( I’ll try to be faster than Nikita this time )
• Maybe work on 1-2 new tickets ?

Roadblocks

• I can’t work on the project description as long as we don’t decide where it should be visible and where it should be edited.