Status Reports: Feb 22, 2013

Currently being formatted…

Yuri Honami

CURRENT

  • [accounts/managers.py]
    *Add compute_user_all_trophies(user) to TrophyManager class.
    *Hiro gonna create TrophyManager class and add compute_trophies(rid) func later. I add this func after that.
  • [accounts/models.py]
    *Import TrophyManager and add it to Trophy class
  • [reviews/templatetags/reviewtags.py]
    *Import Trophy and create compute_user_all_trophies(user) func.
    *This func calls TrophyManager’s function(see accounts/managers.py).
  • [templates/reviews/user_page.html]
    *add a template tag for call compute_user_all_trophies(user).
    *fix the list of trophies … (<br> –> <ul> and <li>)
  • [accounts/tests.py]
    *add test_wip(self), which is assumed name.
    *test_wip(self) creates user, creates some review requests, publishes them and erases them.

( see http://reviews.reviewboard.org/r/3878/ )

ROADBLOCKS

  • I don’t have any idea which ReviewRequests’ elements I should use assert func.

NEXT

  • write accounts/tests.py
  • Add mark to check whether a trophy case has been set up.

QUESTIONS

  • Probably, I should add assert() to accounts/test.py.
  • Then, which elements do I have to check?

Jon Demelo

CURRENT

  • Finished all task goals, including dependency support, blocking inversion, front end and backend support.
  • Browsing bug list for future ideas while waiting for request to be dealt with.

ROADBLOCKS

  • Nothing

NEXT

  • Maybe fix some bugs and see what’s next.

QUESTIONS

  • Nothing.

Surya Nallu

CURRENT

  • Fix the bug with checking if an extension has been already installed — not all packages have their “name” parameter passed in as the package name @ setup.py. Fix relates to accessing the actual package name within the entrypoint.
  • Fix some edge case bugs still exist with the installation that might halt the server fatally (see last week’s status report — “next” section)
  • Submit a WIP review request with the work so far.
  • Submitted the blog post.

ROADBLOCKS

  • None

NEXT

  • Polish the work so far – Add spinner during installation/search, being able to see screenshots related to the extensions, RB versions an extension is comptatible with (As suggessted by ChipX86 after discussions about proceeding ahead).
  • Breakdown of dependencies and the subsequent checks involved for an extension. For example, an extension might have other extensions/python modules as its dependencies and these have to be present before the installation can go through.

QUESTIONS

  • None

Hiroki Gohara

CURRENT

  • Created a manager for Trophy model.
  • Created a function which compute trophies in the manager.
  • Added the manager to Trophy model.
  • In the process of writing unit tests for compute_trophies function.

ROADBLOCKS

  • None

NEXT

  • Work up Creating a test for a Compute_trophies.

QUESTIONS

  • None

Greg Wang

CURRENT

  • Add rich_text db evolution script.
  • Enable markdown rendering with code highlight for `review.body_top` (for testing and style demo purpose only)
  • Play around with `PageDown` editor

ROADBLOCKS

  • None

NEXT

  • Try JS/Python markdown libraries and collect info…
  • How the text been formated/styled
  • How is the performance
  • Whether effecting the anchor or scrolling

QUESTIONS

  • No sure whether should add `rich_text` field into `BaseReviewRequestDetails`, so `Description` and `Testing Done` will be have the Markdown capability as well.

Miguel Flores

CURRENT

  • Placed Error Handling around the code that runs extensions code.
  • Working on learning about Django signals and placing error handling code around them.
  • Will be working most of tomorrow, so I will see where i am tomorrow.

ROADBLOCKS

  • None

NEXT

  • Will disable Extensions if they continuous crash.
  • Other sandboxing?

QUESTIONS

  • None

Katherine Schramm

CURRENT

  • Working on review data grid

ROADBLOCKS

  • Continuing the same over the weekend
  • Put together a WIP post

NEXT

  • None

QUESTIONS

  • None

Felix Sung

CURRENT

Finished Django tutorial

ROADBLOCKS

None

QUESTIONS

None

NEXT

Can I work on the checklist extension?

Niklas Hambüchen

CURRENT

  • Mike helped me to find out where the problem with users having RR edit permission but not seeing issue buttons is.
  • I fixed it.
  • Had lengthy conversation with Steve about how post-review -n works and what –revision_-range=SINGLE_REVISION does.
  • We agreed that it should be changed to what the docs say.

ROADBLOCKS

None

NEXT

  • Fix the post-review issue mentioned above.
  • Try to get my main change committed.
  • Try focus on smaller changes or helping to review other peoples requests since my exams are approaching.
  • Improve the RB docs with a HOWTO about reviewing hosted public repos (e.g. Github) – the fact that you have to have a local git repo and you have to make sure latest changes are pulled always bothered me and it is a barrier for Github-style projects.

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