Status Reports: March 1, 2014

Anselina Chia

Last Week

  • Fixed review issues for the Git hooks (/r/5403)
  • Separated RBTools changes (/r/5543), and am fixing its issues today
  • Started working on the GitHub post-receive hook

Next Week

  • Fix issues that come up for my review requests above
  • Continue working on the GitHub hook

Blockers

  • None

Questions

  • None

Bhushan Ramnani

Last Week

  • Implemented test cases for generating urls for HostingService.

Next Week

  • Finish testing, make changes to review request, commit urls code and start working on mercurial web hook.

Blockers

  • Again having problems rebasing with master. Will get it resolved tonight.

Questions

  • None

Edwin Zhang

Last Week

  • Better understanding the diffviewer code and how it works
  • Fixed the 500 errors that I had been getting when adding the diff expansion links (although clicking the links do nothing right now)

Next Week

  • Implement the functionality for the diff expansion and get more familiar with the diffviewer code

Blockers

  • None

Questions

  • None

Iines Piesala

Last Week

  • I updated my review request with a diff.

Next Week

  • Make progress on my project ( I’ll try finish with the pop up containing the link to the row.)

Blockers

  • None

Questions

  • None

Joonas Lindholm

Last Week

  • Had a look at Mirai’s mobile mockups. Investigating and testing the django-mobile package (https://github.com/gregmuellegger/django-mobile). It provides a way to detect a mobile browser and to serve the correct (eg. mobile or full) template to the user.

Next Week

  • I’m thinking that if we have a “mobile version” of certain pages and a full desktop version, it’s probably enough (no need for a “tablet version” because tablet users could choose whether they want to use the full desktop version or the mobile version). If we do like this, then I probably should start implementing a mobile version of some page (maybe with the help of django-mobile or some other similar solution). I could start with something easy, for example the login page.

Blockers

  • When I run the site / development server inside a VM, how do I access it with a mobile device? When I run ifconfig inside the VM, should I see a wlan0 section?

Questions

  • None

Olessia Karpova

Last Week

  • Fixed the code written last week to incorporate reviews
  • Added tests for Bitbucket and Beanstalk functions
  • Started writing tests for the new hosting service api

Next Week

  • Finish tests and start the implementation

Blockers

  • Not sure why a basic test I have now fails

Questions

  • None

Mirai Akagawa

Last Week

  • Worked on more mockups, with an idea for the dashboard.
  • Started some layout code for the navigation offline from Review Board, with just html css and js.

Next Week

  • Consolidate mockup into more realistic plans, either mockup code or on illustrator.

Blockers

  • None

Questions

  • None

Stephanie Su

Last Week

  • Incorporated code reviews. Fixed the 2 bugs from last week.

Next Week

  • Get feedback and make improvements.

Blockers

  • None

Questions

  • None

Tomi Äijö

Last Week

  • Worked on bug infobox that shows information about mouse hovered bug (similar to the one that shows for users currently)
  • Fixed a few bugs on Gitlab hosting service integration that I discovered. Will post a review request once I complete testing with different Gitlab API versions
  • Created a mockup of the configuration dialog. It is attached in my review request (r/5531)

Next Week

  • Fix issues raised on my review request (r/5531)
  • Implement the configuration dialog

Blockers

  • None

Questions

  • Is there any examples on how to implement the “Add another” -button shown in the configuration dialog mockup that dynamically creates new pairs of Django widgets to a form?
  • Older versions of Gitlab API v3 only allow creating the token with email as the username (See https://github.com/gitlabhq/gitlabhq/commit/559e83d30004e0c41a30f4ce3463f695eb7e26a1). Currently review board only posts “login” parameter so older versions of Gitlab do not work. Should I add new input field for the configuration dialog for the email in addition to the username, or change the current one to accept either? If latter, should I try to recognize emails and use “email” parameter accordingly?

Tami Forrester

Last Week

  • fixed django errors \o.o/
  • working on adding the columns to the datagrid (and figuring out how they work)
  • resolved some of the issues on the review request (will update tonight)

Next Week

  • Finish the columns, start working on the frontend

Blockers

  • None

Questions

  • None
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s