[UCOSP] Status Reports – March 14, 2015

Jessica Yuen

1) What project are you working on?
  • rb-gateway
2) What you accomplished this week.
  • Added unit tests to Review Board Gateway on RB’s side; landed
  • Added a test suite for all Git functionalities that rb-gateway is currently performing
  • Submitted a review request to have rb-gateway return a diff for commits with no parent
3) Links to anything you’ve done this week:
4) What you plan to do next week.
  • Fix outstanding issues with existing review requests
  • Add more test collections for rb-gateway (Focus will be on the routes.go, but hopefully I’ll have time to add all remaining tests)
  • Depending on my progress against the above tasks, and whether or not there’s more work I can do for this project currently, I might pick up another mini project? I’m not sure. I really like this project and would like to keep working on it though.
5) What, if anything, is blocking you from making progress?
  • N/A
6) Any other questions
  • Not right now.

Chester Li

1) What project are you working on?
  • Post-commit review request support for GitLab
2) What you accomplished this week.
  • Added unit tests and debugged for the project. The whole project is waiting to be reviewed.
  • Did code reviews.
3) Links to anything you’ve done this week:
4) What you plan to do next week.
  • I think my current project is done so far, so probably start a new one?
  • Review peers’ code
5) What, if anything, is blocking you from making progress?
  • Only GitLab’s incomplete API
6) Any other questions
  • If I would like to start a new project, how much time I have until the end of the term?
  • May I get some regular feedback, say every 2 weeks, from mentors? For improving my development process, because it seems like we would not have feedback until finals besides some chunks of responses from Slack chat.

Tien Vu

1) What project are you working on?
  • Diff Doctor
2) What you accomplished this week.
3) Links to anything you’ve done this week:
4) What you plan to do next week.
  • Land these projects
  • Proceed to stage 2 of Diff Doctor
5) What, if anything, is blocking you from making progress?
  • I updated my 2 review requests. I closed “most” of the issues and commented on a few because I didn’t agree with the suggestions. Am I supposed to do this, or just drop the issue?
  • I injured my lower back, and can’t sit for more than 20 minutes at a time. Not good for any kind of studying. I’ll need to see a doctor next week
6) Any other questions
  • No, but I would like feedback on my 2 projects and land them sooner than later.

Vincent Le

1) What project are you working on?
  • FileProvider Framework
2) What you accomplished this week.
  • Changed the http status code for DUPLICATE_ITEM in djblets and reflected the changes in the test cases
  • Fixed my backbone models for FileProvider and FileProviderNode, to work and match the new changes
  • Added more functionality for File Provider UI: Changing accounts, navigating, selecting items
  • Cleaned up the mock/test code
3) Links to anything you’ve done this week:
4) What you plan to do next week.
  • Add displaying of meta-information
  • Fix a collection url issue (discussed in questions)
  • Create account
5) What, if anything, is blocking you from making progress?
  • Applied to this week, was sick and had lots of assignments
6) Any other questions
  • Is there any code styling for CSS or JS?
  • I am not sure if I am doing the backbone collection right. As an example:this._fileProviderAccountsCollection = new RB.ResourceCollection([], {
    model: RB.FileProvider,
    extraQueryData: {
    ‘order-by’: ‘account_name,provider_name’
    }
    });

    this._fileProviderAccountsCollection.url = “/api/file-providers/”;

    I am not sure how to set URL correctly to point to my FileProvider url. I have a feeling it has something to do with parentResource but I am not sure how.

Chris Arnold

1) What project are you working on?
  • Mute and Archive Review Requests
2) What you accomplished this week.
  • investigating ‘published’ triggers to handle automatic unarchiving
  • beginning testing
3) Links to anything you’ve done this week:
4) What you plan to do next week.
  • split up project into smaller review requests
  • finish automatic unarchiving
  • fix URL query
  • tests
5) What, if anything, is blocking you from making progress?
  • nothing right now
6) Any other questions
  • a follow up from last week’s question I asked (which Mike answered): “how should I approach simultaneously removing all archived states for one review request?”
    • the use case for this would be when there’s new activity for a review request and review request should become visible again to all users who archived it
    • should looping through every user (for that review request) be done on the JavaScript side or the webAPI?
  • what’s the best (easiest) way to split up my project into smaller review requests (probably into 3 or 4 separate review requests)?

Theo Belaire

1) What project are you working on?
  • rbtools
2) What you accomplished this week.
  • Cleaned up r/6797/, and writing more tests.
  • Read code for rbt post -u.
3) Links to anything you’ve done this week:
4) What you plan to do next week.
  • Finish tests, check for efficiency issues on large repos.
5) What, if anything, is blocking you from making progress?
6) Any other questions
  • Not right now.

Jason Tseng

1) What project are you working on?

  • Responsive UI

2) What you accomplished this week.

  • Finish code styling updates on part 1
  • Rebased all master branch and part 1 to the rest of the parts (2-6)
  • Revisited all parts with code styling comments from part 1

3) Links to anything you’ve done this week:

4) What you plan to do next week.

  • Secondary menu button design
  • Look up new projects

5) What, if anything, is blocking you from making progress?

  • Confirmation on changes in part 1 (#6796)

6) Any other questions

  • n/a
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