Author Archives: markstrmr

Status Reports

Kahlil

Status

  • Changed the XML format to meet the suggest changes by ChipX86 and m_conley
  • Completed refactoring code and cleaning it up
  • Started to work out the detail of my presentation. Spent a lot of time on converting XML to PDF, but I now have something that is produced !

Next Steps

  • Complete Demo
  • Prepare presentation for UBC
  • Submit code changes ASAP for review
  • Blog post for UCOSP

Road Blocks

  • I don’t know how to update my branch so that I can post-review those changes only.

Mengyun

Status

  • clean up code and post-review the option dir for dictionary in spell checking
  • try to speed up highlighting for spell errors.
  • make a demo for screencast

Next

  • try to improve the performance of spell error highlighting
  • get screencast ready

Steve

Status

  • integrated file-uploader into current version of ReviewBoard
  • created webcast of fill-database
  • started on presentation for U of S
  • worked on report for U of S
  • attempted many times to get the comment dialog box to work

Next Steps

  • get the comment dialog box to work
  • fix the text loss issue
  • finish presentation/report/webcasts for friday

RoadBlocks

  • the comment dialog box!

Crystal

Status

  • Fixing up quick search with regards of the comments from the review request
  • Chopped review request’s summary if it’s too long
  • Tried to do bug 1842 but haven’t found much luck. I need a little help.
  • Looked at potential ideas of what to do with the “Press tab to autocomplete”
  • Worked on issue tracking by trying a bunch of colours to make it easier on the eye and found 2 colours.

Next Steps

  • Continue with bug 1842 or at least have search be able to search review request id
  • Wrapping up quick search
  • RB presentation for school
  • RB screencast

Roadblock

  • Last week of school. Very busy!
  • I am not sure why searching by review request id does not include the review request in the results. I took a look at it and it seems implemented (not by me). I tried working with it and I can’t get it to work.

Mark

Status

  • Still working on OAuth.
  • Spent a lot of time reading the OAuth specification instead of guides online.
  • Started writing a client for testing the server and found out that the python-oauth2 module might not work out for the client (or server after reading the specification).
  • I’ve started writing a helper module for oauth2.0 stuff, I’d rather not do this, but it looks like there isn’t one written that matches the specification.

Next Steps

  • Keep plugging away at OAuth.
  • Get my screen cast done.
  • Make sure I get something usable out of all this OAuth research.

Roadblocks

  • OAuth 2.0 seems like a bit of a moving target, but 1.0a is quite complicated.
  • OAuth 2.0 libraries are few and far between.

Teresa

Status

  • working on my screencast
  • still going through defect reports to try and replicate them

Next Steps

  • write a report on the project for U of S
  • make a presentation for the project for U of S

Roadblocks

  • nothing but other classes

Meeting Minutes – March 26, 2011

We have less than 3 weeks left now.

Projects that are just starting aren’t necessarily going to be finished and that’s expected.

Presentations need to be done soon, quality is better than quantity. Presentations should be less than 10 minutes long, and being shorter is generally better than longer, don’t fill for time. Showing is better than telling and it helps to write a script for yourself and do a few trial runs before you start recording.

We will have a ‘post-mortem’ meeting on April 10th at 2 pacific time (an hour before our usual meetings).

Status Reports

Mengyun

Status

  • change pyaspell into pyenchant for spell checking
  • trying to decrease the time of highlighting spell error

Next step

  • Add bottons for users to choose hightlight or not and language options

Roadblocks

  • I planed to work more on branch in the reading break, but was pretty sick in the past week

Kahlil

Status

  • Learned a lot about the WEB API and was able to successfully query it in my resource
  • Got a working resource that returns back all the information that exists within a review request!
  • Created a pile of git mistakes, and then successfully worked through all of them with mike
  • Made a timeline for the rest of the semester

Next Steps

  • Change the format of what the resource returns to match what the initial feature request is.
  • Hook up the resource to the link within the review request

Roadblocks

  • None!

Crystal

Status

  • Had a very successful week!
  • Fixed up some SearchResource so that it also searches for groups’ display names and review requests’ summaries
  • Wrote the wrapper for AutoComplete, called SearchAutoComplete and it is able to autocomplete suggestions for users (username, firstname, lastname), groups (name, displayname) and review request (ID, summary). Looks to me that it works fully! =D

Next Step

  • More testing to make sure this always works
  • Clean up the code
  • Post review this to let others see how the code is working
  • Perhaps do something to make it look nicer (css time?) or be able to click on the suggestion and takes you to the page directly

Road Block

  • None

Steve

Status

  • Sent ReviewBoard blog to UCOSP headquarters
  • Altered fill-database.py based on David’s feedback
  • Attempted to get the diff’s to upload (unsuccessful)

Next Steps

  • Figure out what is happening in the forms.py example of uploading the diff file
  • Continue to attempt to get the diff’s to upload
  • Modify the current min & max variables to be a tuple as per David’s suggestion (minor fix)

Road Blocks

  • I don’t have a good understanding of what is actually happening in the forms.py
  • Trying to implement the needed parts of the form.py into the fill-database has been slow going

Mark

Status

  • Fixed tests for the git diff error
  • Wrote some JavaScript for a new issue and posted review #2133

Next Steps

  • Write more tests for the git issue
  • Update the JavaScript as per Christian’s review

Roadblocks

  • Nothing too bad 🙂

Teresa

Status

  • working on a file uploader (hoping to have it done by the meeting tonight)
    • for extending template components
  • stepping back a bit and going through some forms tutorials

Next Steps

  • figure out how to point the application at the extension templates before the default templates
  • get a way for the user to specify which template they are overriding

Roadblocks

  • having some trouble figuring out hooking the form handlers into a specific form

Meeting Minutes – February 13th, 2011

ChipX86 talked to a couple people about revised schedules and is hoping people have a bit better of an idea as to where they are in their current projects, and would love to see a rough time table based on that.

ChipX86 reviewed the requests that were online and people likely saw lots of comments. This is normal and is going to happen while people are learning the coding style and Pythonic ways of doing things.

ChipX86 says that every line of code in ReviewBoard must be reviewed. If you’re working on a big project, you probably want to post smaller reviews when you start out so that you can get feedback to make sure you’re on the right path.

Even David and Christian review each other’s code so that everything gets reviewed.

ChipX86 and purple_cow are working on a patch for the issue where running a subset of tests no longer works.

ChipX86  proceeded to help people with questions specific to their project.

Code Sprint

I started the code sprint by picking up bug #495: Add a To Me column to the Dashboard. The bug was really good for seeing how ReviewBoard and Djblets work together. I ended up doing a lot of digging in the DataGrid and Column classes.

I spent a good amount of time helping others with git on Saturday and got some help from ChipX86 with some issues I was having with my bug and finished that up and submitted my first review to ReviewBoard.

All in all the sprint seemed fairly successful, git is all set up and I now know how to post my stuff to ReviewBoard.