Status reports May 3

Stephanie Su

1. What you accomplished this week

• Fixed Ajax issue for removing widgets.
• Finished the functionality for adding and removing widgets.

2. What you plan to do next week

• Get my code reviewed and clean up/refactor my code.

3. What, if anything, is blocking you from making progress

• None

4. Any other questions

• None

Tomi Äijö

1. What you accomplished this week

• Fixed issues in r/5531
• Fixed issues in r/5745
• Added a bit more error handling to r/5531
• Created support for Bugzilla, will post a new request request before the meeting

2. What you plan to do next week

• -Start working on support for Google code

3. What, if anything, is blocking you from making progress

• None

4. Any other questions

• None

Joonas Lindholm

1. What you accomplished this week

•  Improving, testing and fixing bugs of this: https://reviews.reviewboard.org/r/5620/

2. What you plan to do next week

• Out of WIP hopefully on Sunday and then fixing things during the week according to reviews.

3. What, if anything, is blocking you from making progress

• None

4. Any other questions

• None

 

Bhushan Ramnani

1. What you accomplished this week

• Google Code post receive hook pushed to master. Discovered and logged a
  bug related to setting up and posting on Google Code Mercurial repository.

2. What you plan to do next week

• End of term. Will pick up another project or a bug fix as per mentors’
  advice

3. What, if anything, is blocking you from making progress

• None

4. Any other questions

• None

 

Edwin Zhang

1. What you accomplished this week

• Submitted r/5710
• Finishing up r/5709
• Continuing to work on sandboxing other hooks and adding unit tests

2. What you plan to do next week

• Continue sandboxing hooks and writing unit tests

3. What, if anything, is blocking you from making progress

• None

4. Any other questions

• None

Iines Piesala

1. What you accomplished this week

• I have worked the part two to get it finished. I’ll update the review request before sundays meeting.

2. What you plan to do next week

• Work on the bug Mike Conley suggested

3. What, if anything, is blocking you from making progress

• None

4. Any other questions

• None

Tami Forrester

1. What you accomplished this week

• Tried setting up extensions, and got a bit stuck on what to do

2. What you plan to do next week

• Figure that out, and start looking at checklist extension

3. What, if anything, is blocking you from making progress

• Last week was more busy than intended, so I didn’t get as much done as hoped, but setting up the extensions is the main blocker right now. The instructions here seems like it might be out of date.

4. Any other questions

• None

Mirai Akagawa

1. What you accomplished this week

• Completed Review Board Mobile for the Review Page.

2. What you plan to do next week

• Possibly taking care of minor issues if any.

3. What, if anything, is blocking you from making progress

• None

4. Any other questions

• None

Meeting Minutes: March 16, 2014

Announcements

•  As for opening announcements, my only announcement is for olessia and heapify – after this meeting, you’ve got two meetings left and then the UCOSP term ends

Round-robin

Tami

• I’m working on getting the tabs to show above both datagrids
• I wasn’t sure if i could just link to the datagrids since everything is shown using the djblets templates
• An idea i had was to make a tabs item, kind of like a sidebar, just for the rb.
  • I think that sounds fine to me. Re-usable components are good  – just don’t make more work for yourself than necessary.

Tomi

• I have been extremely busy with work this week and the whole weekend so I have not had time to code the things
• There are some concerns:  the configuration widget can be quite complex and there are some Options fields that would need to be read from Python side.
• What is left for you to complete besides configuration? Lots of clean up and adding support for other bug trackers. I mean support for things like posting comments and such.
• There are still a number of open issues on my review request. I have not fixed them yet, those files are still under development and change frequently. I have been planning to first implement all features and then polish things.

Stephanie

• I worked on the front end for adding widgets and posted a review request  even though its not finished, because I wanted design feedback.

Joonas

• Worked on responsive design on the login and registration pages: /r/5620/
  • really cool to see the responsive work you’re doing in those screenshots. 🙂
• I still need to test it more and probably do a better implementation which requires more investigation on the CSS media query usage in general

Mirai

• [Excused – CMU on Spring Break]

Olessia

•  I think I am basically done with my task. I would appreciate some feedback, because I might be wrong =) .
• But I have one problem with testing, testing getting_remote_remote is done with spy agency, so we don’t  need to call remote apis.But the problem is, when I setup the test, the HostingService object does not exist yet so I can’t replace the function call
• I’ll look for the fake HS, as purple_cow suggested, but I will need  some direction with implementing one if I need to

Anselina

• I talked to ChipX86 yesterday about the best way to refactor my code for the github hook, and will be going about doing that this week 🙂

Bhushan

• [Excused – Traveling]

Iines

• I have been quite busy this week, i updated the review request just now
• I think i have to clear at least a day for next week to dig deep with highlighting the url

Edwin

• So I’ve been trying to add functionality to the incremental diff expansion. When I click on it nothing happens and I think it has something to do with either the chunk I pass in or the file

General tips

• Keep up the good work. Please start looking at each other’s review requests
• Please review one another, even if it’s just to ask questions about how something is working.The more eyes, the better