- Wilson is unable to attend this weekend, but everybody else is in attendance.
- Django upgrade: if you’re still having problems, talk to one m_conley/ChipX86/purple_cow or send a general request to the IRC channel.
- request for feedback on comment on the open issue (r/2810)
- brief discussion on the proper placement of select_related, i.e., near the construction of the query, and before the query will be instantiated/executed
- tips for fighting coding burnout
- break up the larger tasks with non-coding tasks or smaller side-tasks with more immediate results
- deconstruct the large task into smaller chunks/milestones with their own immediate/tangible results. nurture a sense of accomplishment and definite progress.
- issues with naive timezone warnings when passing in __range (snippet)
- python issue (snippet)
New Student Project Idea: reviewable pasting service
- Busy week, but no roadblocks moving forward
- discussed proper location of admin command. examples provided using find `reviewboard/ -name management -type d`
- question about blog post: high-level idea of the semester so far for an audience that has a passing knowledge of Review Board, refer to other blog posts for examples.
- issue regarding reintroducing a fork from github into a local branch
- discussed action log for admin site, selected course of action is to remove the link
- reminder that there may be some reviewed requests that haven’t been updated yet, so check in on any pending requests.
At the code sprint, I fiddled around with github and set up backup forks of reviewboard and rbtools. I addressed issue 495, submitted a code review and it was accepted into master.
Additionally, I filed issues 2457 and 2460, and worked on some code reviews for other team members.
I picked the Extension Scaffold Generator student project from the wiki, and delved into the sample extensions here (RBBugTracker), and here (toy extensions). After creating a simplified example extension, I modelled the script after postreview.py. The file generation code uses Jinja2 templates, and wrote up a version of the script that could generate extensions that could be installed; after some tweaking, I have submitted a code review.
My next steps are to:
- Figure out what other options might be useful for extensions
- Flesh out the documentation on the wiki article for building extensions
I am Anthony Mok, and I am in my last term of the Computer Science program at the University of Waterloo. I picked the Review Board project for UCOSP due to favourable past experiences with the software and a desire to want to contribute to the community; it also felt like a good opportunity to learn new skills and technologies. I met the other students and Mike from the Review Board UCOSP team for the first time this weekend at the Code Sprint at UBC.
The sprint began with a short group session, and shortly afterwards we split up into our individual teams and began what would be a solid weekend of productivity. We set up our development environments and workflows, and although it wasn’t without hardware and software issues, we more or less got straight to work fixing bugs, picking up long-term projects, and doing peer code reviews using Review Board itself. The code sprint had many good lessons, both explicitly in the form of a git tutorial (a version control system that is crucial in sharing and backing up work between distributed team members), and implicitly as we got comfortable working with the other members of our group and got our code reviewed.
I have picked up a long-term project in the form of a helper script that will generate the scaffolding for Review Board extensions. Essentially, this will fill out a bare-bones skeleton for a working extension based on a simplified configuration scheme that will be provided by a user. Currently, documentation on extensions is scarce, but I hope to be able to flesh out documentation on the wiki page with fellow team member Steven.
I am posting this as I wait for my flight home from an exciting and productive code sprint. I am confident that working on the project will continue to be as enjoyable and enlightening as this code sprint has been.