Status Reports: June 8, 2014

Salam Alyahya

  • What you accomplished this week.

    • Organized my git repository and created local branches so that I can post clean commits. A branch for updating the extension, a branch for updating html template in the js file, and a branch for style changes.
    • I have changed the extension so that it uses .less files instead of .css for styling.
    • Modified the extension template so that it is in a table format to give more styling options. Encapsulated the table with a div tag to fix an issue where after minimizing the extension, the maximize button (to go back to normal) does not show.
    • Also, changes the styling and colours of the extension in style.less file so that the extension fits with RB colour scheme.

 

Volodymyr Lyubinets

  • What do you plan to do next week?

    • Iterate on existing reviews
    • Finish modifying logic behind displaying thumbnails to show only fresh version of each file, etc.
  • What, if anything, is blocking you from making progress?

    • Still exploring the codebase.
  • Do you have any other questions?

    • No

 

Peter Tran

  • What you accomplished this week.

    • Created a hackpad with higher level details of how people will use requests.
    • Took meeting minutes for last week’s meeting.
  • What you plan to do next week.

    • Start writing out test cases
  • What, if anything, is blocking you from making progress?

    • Confirmation of UI design.
  • Any other questions

    • Are there any other use cases for requests? The mockups I made are based on small actionable but quick requests between users based on review requests. Is there another capacity which requests need to be made?

 

Matthew Maclean

  • What you accomplished this week.

    • updated review request https://reviews.reviewboard.org/r/5869/
      • added classes to handle revisioning code
      • clone/load repo on startup
    • asked more questions about the architecture and how stuff should be laid out
  • What you plan to do next week.

    • give tool file path to the original repository
    • (bonus) switch to base commit
  • What, if anything, is blocking you from making progress?

 

Raheman Vaiya

  • What you accomplished this week.

    • Structured mock up code so it is ready for review

(review request to be created with corresponding code shortly)

  •  What you plan to do next week.

    • Formalize API requirements
    • Finalize front end code (to extent possible without a working API)
  • What, if anything, is blocking you from making progress?

    • Nothing
  • Any other questions

    • No
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