Author Archives: Olessia

Status Reports, Feb 15, 2014

Anselina Chia

Last Week

  • Handled corner cases (new branches created in a push, etc.) in my Git hook
  • Started refactoring the hook

Next Week

  • Finish refactoring the hook, and put it all up for review
  • Start working on the Git pre-receive hook

Blockers

None

Questions

None

Bhushan Ramnani

Last Week

  • Made the requested review changes for issue 3201
  • Fixed the IntegrityError issue which appeared when trying to load the dashboard. Fix under review process.
  • Started work on building the HostingServices url infrastructure, so that web hooks can be written for it.

Next Week

  • Close pending review requests
  • Finish work on enabling the urls for HostingServices.
  • Start building a web hook instance.

Blockers

None

Questions

None

Edwin Zhang

Last Week

  • Getting familiar with the code around my project and starting to work on the front end for the incremental diff expansion on the review page.

Next Week

  • Finishing up the visuals and start working on the functionality for the incremental diff expansion.

Blockers

None

Questions

None

Iines Piesala

Last Week

  • I have been enjoying San Francisco, so I haven’t worked on my project.
  • I’ll be in plane when we have the weekly meeting, so I won’t participating in the weekly meeting.

Next Week

  • I’ll continue to work on my project and create a WIP of it to review.

Blockers

None

Questions

None

Joonas Lindholm

Last Week

  • Making and sending out a survey (with Mirai) about Review Board mobile usage to help better define our project.

Next Week

  • Use the survey results to make an action plan and then start working on it.

Blockers

None

Questions

None

Olessia Karpova

Last Week

  • Worked on hosting services: getting remote repository information for a given userservices: bitbucket, beanstalk, git – figuring out paginated responses

Next Week

  • Will need to talk about my project in/after the meeting

Blockers

Beanstalk – cannot do much testing, since the free account only allows one repo

Questions

  • Would love some feedback on the review requests

Mirai Akagawa

Last Week

  • Worked on Mobile UI, figuring out issues and bugs
  • Sent out a survey seeking for usage cases in mobile
  • Initial take on comment box zoom on mobile issue.

Next Week

  • Finish off comment box zoom issue for now
  • Look into survey results and think of plan for next couple of weeks.

Blockers

None

Questions

None

Stephanie Su

Last Week

  • I’ve been working on the backend for saving drag and drop positions.

Next Week

  • Go over my code review from last week and keep working on the backend.

Blockers

None

Questions

None

Tomi Äijö

Last Week

  • Continued where I left of at the code sprint. I have been experimenting with a new bug tracker integration feature that emerged from community discussions (creating a new issue when a RR is posted).

Next Week

  • Make the whole bug tracker integration configurable so that end user can tie actions to different RB events such as when “RR created”, do “post a comment to bug tracker”. Also I will need to discuss the separation of bug trackers and HostingService class. Now the bug tracker is merely a text field in HostingService providing formattable string for bug url.

Blockers

None

Questions

None

Tami Forrester

Last Week

  • I’ve been working on the backend for adding reviews to a user profile.

Next Week

  • Get it to work, and debug as necessary

Blockers

None

Questions

None – I’ll have pictures up this weekend! (sorry for delay)

Advertisements

Meeting Minutes: February 4, 2014

Attendees

Mentors: Christian, David, Mike, Steven

Students: Anselina, Bhushan, Iines, Joonas, Olessia, Mirai, Tomi

Announcements

Sprint

It’s the meeting before the sprint! Ensure you have flight confirmation.

Status Reports

Keep sending the status report on time, that helps the mentors a lot.

Hackpad

Students should all feel completely free to create pages on Hackpad, and then link those in your status reports when you’ve made changes.
It’s helpful for mentors to see any design notes and thoughts, and you’ll likely find it useful yourself to keep notes as you go.  Ask the mentor if you have any questions on how to use Hackpad.

Bug tracking

If you find a bug, file it, unless you know it already exists.

Round-robin

Anselina

  • Have been working on the SCM Hooks project. The core work for the Git post-receive hook is done, and is working.
  • Will modify it to handle merge commits better, then do some more testing.

Bhoushan

  • Will take up New Hooks project.

Iines

  • Looked at Issue #3078, but i just found out it’s already fixed in master branch(2.0).
  • Will take up Issue #2442.
  • Interested in improving links between code and issues. Would need to start by figuring out the design.

Joonas

  • Reproduced Issue #3204 on dev server, figuring out how to implement it.
  • interested in the Mobile / Touch Enabled Device Support as a project.

Mike suggest starting with sketches and mock-ups. Figure out which form-factor your targeting first – mobile phones, or tablets) and ensure that you have access to that form factor. Christian suggests a hackpad with lots of things for to look at.

Mirai

  • Generally trying to get use to the code base and the structure.

Make sure to ask the mentors if you need any info on the codebase. There’s a lot of code. If you’ve gone 2 days stuck on where code lives, it’s absolutely time to hop in IRC.

  • Have been looking at Issue #3302.
  • Interested in Mobile / Touch Enabled Device Support project. Work will be divided with Joonas.

Olessia

  • Submitted a patch for Issue #3200 for review.The code has been pushed to master.
  • Worked on Issue #3217.
  • Going to take up HostingService as a project. Details and specifications to be discussed with the mentors.

Tomi

  • Submitted fix to issue 3189 for review. The code has been pushed to master.
  • Interested in working on bug tracker integration, possibly Jira.
  • Would need to start by talking with people on the mailing list (reviewboard-dev), because a lot of people have asked for deeper bug tracker integration, but we don’t know quite what they have in mind. Then start putting together a plan and timeline.

If you guys aren’t on reviewboard@googlegroups.com and reviewboard-dev@googlegroups.com, please subscribe