Status Reports: Jan 18, 2015

Theo Belaire

  • What project are you working on?
    • I’m working on finding the optimal parent_base
  • What you accomplished this week:

    • I found the git command to do this.
    • I implemented it in python in rbt’s git.parse_revision_spec
    • I wrote a test to exercise it.
  • What you plan to do next week:
    • Next week I have to catch up on homework that I missed for the sprint, but I will read about hg.
    • I also want to remove the hard-coded ‘origin’s from the code, and learn how to use the configuration option.
  • What, if anything, is blocking you from making progress?
    • I am clear for now.
  • Any other questions?
    • Nothing I can’t google atm.

Chester Lee

  • What project are you working on?
    • Add PEP 257 docstring linting to Review Bot

  • What you accomplished this week:

    • I worked on 3 bugs (including 2 easyFix bugs), one easyFix bug has landed, one easyFix bug is in progress and just needs a unit test to be shipped. The last bug is about double escaping character  in comment section, I added more details and dived into the      causation searching for a while with the help of Mike, anyway, Christian figured that out.
    • My logs for code sprint is still in progress and will be done by the end of Sunday.
    • I also picked a project and am currently working on that.
  • What you plan to do next week:
    • I am planning to finish review request 6786 (Download Diff issue in views.py) and keep working on my project. I am going to write logs for weekly work as well. Moreover, I will keep learning git and Django, get better understanding on the project.

  • What, if anything, is blocking you from making progress?
    • Lack of understanding of the whole structure of the project and unfamiliar code.

  • Any other questions?
    • Are we going to have a graph or other visualised project hierarchy document for future references?

Vincent Le

  • What project are you working on?
    • I am currently working on “File providers framework”, for easier file attachment uploading

  • What you accomplished this week:

    • Worked on the changenum bug (3685)
    • Started planning and research for the File Providers Framework project
    • Hanged out with the awesome ReviewBoard team
    • Started some small implementation with the File Providers framework in the form of objects, webapi and models.

  • What you plan to do next week:
    • Continue basic implementation with the webapi
    • Start building test cases for the webapi, probably similar to TestTool (from SCMTool) for the FileProvider object
  • What, if anything, is blocking you from making progress?
    • None for now

  • Any other questions?
    • I haven’t took a quick look into the decorator webapi_request_fields, I was wondering if it verifies if the length of the input parameters for optional parameters. Things like does it exist, does it make sure its not null, will it submit if it’s not null or empty.
    • If my framework requires packages like DropBoxFileProvider can use a DropBox package, should I tell the user to install it themselves or install it for them?

Chris Arnold

  • What project are you working on?
    • Mute and Archive Review Requests

  • What you accomplished this week:

    • investigating how closed review requests work and are displayed / hidden
    • getting more familiar with general Django, Djblets and Review Board concepts
  • What you plan to do next week:
    • make a more detailed plan for providing a visibility parameter to ReviewRequestVisit objects
    • figure out how and where to add UI to toggle review request visibility
  • What, if anything, is blocking you from making progress?
    • nothing right now, just learning as much as possible
  • Any other questions?
    • none

Jessica Yuen

  • What project are you working on?
    • I’m working on the very last project on the Hackpad: Repository access and registry service.

  • What you accomplished this week:

    • Removed change description from initial review request publishings and other refactored some code
    • Added instructions on running subtests to dev guide
    • Added some notes to Hackpad related to my project and screenshots of the architecture discussed at the sprint (to be uploaded shortly…)
    • Did a minor review:https://reviews.reviewboard.org/r/6784/#review15642
    • Started work on my project. Currently have a basic prototype running on a Flask webserver to fetch file blobs, and check for file existence.
  • What you plan to do next week:
    • I plan to keep working on my project: mainly integrating it into Review Board for this week.

  • What, if anything, is blocking you from making progress?
    • Just some learning to do with Git internals …

  • Any other questions?
    • Nope.

Jason Tseng

  • What project are you working on?
    • Responsive UI
  • What you accomplished this week:

    • Bug#3363 – fixing hashtag anchor url issue which clicking diff file names
    • adding responsive ui for main menu, [WIP] review details, diff viewer
    • in progress – learning codebase, rbtools, functionalities, backbone
  • What you plan to do next week:
    • Continue with Responsive UI, hopefully complete for most pages
    • Get more understanding with underlying backbone implementation
  • What, if anything, is blocking you from making progress?
    • none
  • Any other questions?
    • nope

Tien Vu

  • What project are you working on?
    • Commit message templates
  • What you accomplished this week:

    • Mostly investigating parts of the project + Django + Python + Git
    • Git review + common tools + some git internals (from the Git book, http://git-scm.com/book/en/v2/Git-Tools-Revision-Selection)
    • A lot of messing around with the web API with Postman to check out different resources (http://puu.sh/eHtoJ/10d012df70.png)
    • pdb
    • Python decorator
    • logging, argparse
    • setuptools/pck_resources/entry points (not sure if time on this was well spent)
    • explored how rbt commands work (mostly post, close and patch)
    • figured out where the unit tests are (they all ultimately subclass django’s unittest.TestCase, there are several custom subclasses as well). run with nosetests (I don’t know what nose is)
  • What you plan to do next week:
    • Explore rbt patch
    • Have some more idea of how rbt commands work in general
    • modify rbt patch to use a template and send output to stdout (right now it’s just printing stuff)
    • read parts of Django docs again
  • What, if anything, is blocking you from making progress?
    • I have a lot more to understand regarding the codebase, but progress is there and I’ll ask around on Slack for help

  • 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