* Implemented the models and first few views for the OAuth support
* Did a lot more reading on how OAuth works
* Continue implementing OAuth support
* Write an OAuth client for testing the OAuth server
appears to be version 1.0 and will no longer work for testing
* corrected critiques on fill-database script
* chose next project (an unfinished project from last year)
* review code in unfinished project
* figure out what needs to be done & where to start
* get the code itself (we don’t have access to original project, Christian is
* unfamiliar territory on this new project, looks like lots of alterations to
various parts of reviewboard.
* Fixed this annoying bug with quick search that took me forever. It turned out I was searching for a private review request and so it was returning stuff that was undefined.
* Post reviewed and David has given some feedback. I have fixed those and updated it.
* Had some trouble with grabbing Mike’s code of issue tracking but Christian helped me on that. I started looking into it and played around with it for a bit.
* Waiting on feedback for quick search
* Tried playing around with issue tracking but I’m getting an error so I didn’t get a chance to use it
* Making the inline of issue tracking prettier
* Start working on screencast?
* Need to figure out how issue tracking works exactly and figure out why I’m running into an error
* I have 3 midterms and a project due next week and going to Texas on Friday. Super time management is key
* Implement context menu for spell checking on diffviewer
* make ‘ignore once’ and ‘add to dictionary’ work for the feature
* clean up code
* improve and add functions
* maybe it’s time to think about improving the performance for highlighting errors
* not sure if I’m on the right way..
* Working through review comments (fixing problems).
* Re-working templates (found some places where the smaller components had more than they should to be easily extendable).
* Wrote up instructions on how to extend a template along with a simple example.
* Wrote up a blog post for UCOSP.
* Probably ready to start thinking about a new project (or possibly try some bug fixes).
* Finish up the fixes from the review.
* Try some bug fixes/look into screencast software.
* Nothing right now
* Completed most of screen shots into XML transformation
* Received some advice on how to handle code diffs and have been trying to figure it out
* Complete the code diffs part
* After taking ChipX86’s advice, I spent a lot of time trying to implement various pieces in order to get the diff. I am getting the results back, but I don’t know how to handle the data so that it is produced in the format I need it.
– Mike is running the meeting. Christian could not attend meeting.
– 4 weeks left till this term ends
– Start thinking of screencast
– A very good idea to download and try out the application for your screencast now
– Script something out for the screencast
– Length wise: prefer short and snappy, show rather than tell. Long doesn’t mean better
– People looking for new projects: Crystal
This is what I’ve been doing!
Post review so Christian/David/Mike can see what I am up to and if my code could use some changes and provide screenshots for it. (This week)
Make it look nicer. I assume this is done with css. (This week)
Have another features such as:
Clicking on the suggestion takes you directly to the suggestion’s url. (Ex: suggestion of a specific user takes you the user’s url) (in 2 weeks)
Pressing something like tab can help you automatically autocomplete (in 3 weeks)
These are some ideas for my autocomplete. I guess there are more features I can add to the autocomplete.
One of the best parts about programming is when I make progress at what I’m trying to do. I would be lying if I didn’t say at some point I had a panic attack over if I was ever going to complete my quick search feature. Learning this ReviewBoard has been challenging, since I know nothing about Python and the whole Django framework before I started. Luckily, I have some awesome mentors and they are really willing to help me out even when I am asking a lot of questions. Even though this term so far has been extremely challenging trying to balance myself between school, ReviewBoard (I don’t count it as school work!) and Ultimate, I find joining UCOSP and working on this project have been extremely rewarding. This is nothing like what you learn in school. I haven’t done much in web development at all so learning Django has been very interesting. This is something completely different from what I would be learning at school with languages like C++, Java etc…
It’s been 2 weeks since the code sprint and I am really hoping to pick up the pace of my project especially I don’t have any midterms right now and reading week is upcoming! Lately, I’ve been working with the Web API resource to filter objects from models. After a bunch of trial and error, I’m able to display the list of users, review groups and review requests through my new resource. The search is mostly working for now. This is my first time writing code in Python so progress has been slow. At the same time, I’m happy to finally be accomplish part 1 of many for my project. In the mean time, I’ll keep pushing hard to make more progress. Hopefully my next blog post will be more interesting! 🙂
First Meeting after sprint:
- Team photo: Karen has it and Mike has emailed her about it
- Steve’s presentation. A course requirement for him. He talked mostly about the scalability testing.
- Our mentors (Chris, David, Kevin and Mike) do the technical bits of RB but not so much about the University/course requirements.
- Mentors love to hear about what we are doing. Keep up with postings on the blog about your progress
- Do not commit code to ‘master’ or ‘extensions’ branch. Always create a branch for each review request. If you do make a mistake in committing to master or extension, go get help to reverse it.
- Send emails or post on blog about your project development plan if you haven’t done so.
- Meet Minutes: Post the highlights of the meeting
- UCOSP folks would like more posts on their blog about our project. So bi-weekly, they would like some high-level progress reports of what has been done. By high-leveling, it means screenshots, language for people who’ve never used RB, etc… These posts should be interesting, not just status reports. Ex: personal observations on project, problem encountered and how to resolve, issue that hasn’t been solved but the rest of community can help with, description of a feature/tool, victory dance when a feature is completed.
- Mike will be adding names to “Who’s Doing What” for this bi-weekly posts about updates. Stay tune (thru email + blog) for who’s doing on which days/weeks
- Chris will be doing the first post. The ucosp.ca blog is inaccessible to us and so we have to email our blog to email@example.com for them to update the blog for us.
- Keep blogging!