Status Reports: Mar 8, 2013

Jonathan Demelo:

Currently

  • Moved on from first task and began second task, which added new fields to the submitted/discarded banner.
  • Added the fields into reviews/models.py, and connected it to the admin panel.
  • Developed an initial front-end display for the fields in the banner.
  • Addressed some of the connections in the views.py, reviews.js, etc.

Roadblocks

  • I believe I’ve found something odd… possibly an existing bug with the banner. It seems that if you publish a review, then go to the submitted banner, it’s submitted. But if you attempt to add the optional description, it’ll add the text, but then discard the submission. Is this a bug?
  • Changing the current way the description is saved, as the current way is quite limiting to the possibility of adding additional fields (see line 708 in reviews/views.py).

Next

  • Address the roadblocks and move forward for the frontend-backend connections.

Questions

  • See roadblocks.

Yuri Honami

Currently:

Roadblocks

  • I don’t detect the cause why unit-test doesn’t work.

Next

  • detect the cause of that

Questions

  • None.

Hiroki Gohara:

Current

Roadblocks

None.

Next

  • Implement handling many trophies.

Questions

  • How review request should be separated?
  • I’m about to separate tasks, “Using database for trophy” and “Handling many trophies”

Greg Wang:

Current

  • Move `FileAttachmentComment` evolution into separate evolution script.
  • Insert rendered text along the page loading process using document.write()
  • Use PIPELINE to include js and css

Roadblocks

  • None.

Next

  • Adjust the css style for markdown text
  • Apply Markdown to more textfields

Questions

  • None.

Katherine Schramm:

Current

  • Continued work on Review datagrid.

Roadblocks

  • None

Next

  • The Same
  • Will update WIP patch this weekend

Questions

  • None

Surya Nallu:

Current

  • Implement a modal box with tabs inside it for handling the extension information, screenshots, dependencies and pre-install information.
  • Migrate previous javascript work to Backbone: create a model/view for every transaction.
  • Change the extension information boxes, installation procedure to accommodate new changes: Tabbed modal box on the front-end and Backbone in the backend. This is still WIP.

Roadblocks

  • None

Next

  • Note: Some tasks have been bottenecked until the backbone migration is complete.
  • Add spinners when backbone is attempting to fetch information.
  • Usability issue mentioned last week (here: http://pastie.org/private/tnpp7yu06m4nsn8b6iydrq ). Shifted over to the week ahead because (after discussing with m_conley and ChipX86) it was decided that a modal box with tabs would be more appropriate.
  • Add category information to extensions.

Questions

  • None.

Felix Sung

Current

  • Have skeleton of an extension as per the Reviewboard Extension Guide
  • Schema proposal for Checklist Extension here:
  • Mockups on the blog post above too

Roadblocks

None

Next

  • Get feedback on design
  • Start code

Questions

  • I will need to change the “view” for reviews. I’m guessing ideally an extension shouldn’t need to do anything to the original project code. How should I insert elements, for example the checklist? I can imagine appending them through Javascript/Jquery, but that sounds somehow suboptimal.

Niklas Hambüchen

None this week, since I’m pretty sick, staying in bed and using
my computer only when I really have to.

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