Status Reports

[Steven MacLeod]

Since it wasn't discussed at the meeting, I thought I'd collect the Status Reports for this week.

Bogdana, before each meeting, someone will collect status reports from the other students, and make a blog post. Collection usually occurs the day before, and the blog post should be up at least 1 hour before the meeting. Since there is only two of us, collection should be pretty simple :D. Please reply with your status report.

The reports should be a quick summary of what you've been working on, what your next steps are, and any roadblocks you have. For some examples, you can look at previous reports posted to the blog here: https://reviewboardstudents.wordpress.com/category/status-reports/

Steve

[Bogdana Popa]

Hey Steve,

Good idea. Here's what I've been doing since the meeting:

Status:

• Made final changes and published a minimal working prototype of the action feed (r/3121/ )
• Trying to get a better understanding of the code from django-activity-stream, in order to emulate it

Next Steps:

• Start working on the GUI
• If a decision is made one way or the other, start improving the functionality for the action feed or reimplement the current functionality.

Roadblocks:

• Not a major one for now, but we should probably decide whether or not to use django-activity stream

Thanks,

Bogdana

--
You received this message because you are subscribed to the Google Groups "Review Board Summer of Code" group.
To view this discussion on the web visit https://groups.google.com/d/msg/reviewboard-gsoc/-/s2HH3HVvsgcJ.
To post to this group, send email to reviewbo...@googlegroups.com.
To unsubscribe from this group, send email to reviewboard-gs...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reviewboard-gsoc?hl=en.

[Steven MacLeod]

Please reply with this weeks status report.

[Bogdana Popa]

Hi!

This week was a bit slow for me:

Status:

• Reading about RabbitMQ and Celery and trying to asses their utility for the action feed

Next Steps:

• Finishing up the GUI

Roadblocks:

• Same as last week, needing a final design decision (although I am aware of how important this is and that there's no reason to rush it so far)

Cheers,

Bogdana

On Sun, Jun 10, 2012 at 8:06 AM, Steven MacLeod <ste...@smacleod.ca> wrote:

Please reply with this weeks status report.

--

You received this message because you are subscribed to the Google Groups "Review Board Summer of Code" group.

[Steven MacLeod]

[Bogdana Popa]

Status:

• implementing a prototype of the action feed, which stores history as a JSON field in the ReviewRequest table
• implementing a prototype that stores actions as separate entries in a separate Actions table (this was just to satisfy my own curiosity)
• building a script that fills the database in order to test the implementations above
• currently running the tests and trying to reach some conclusions

Next Steps:

• Decide on one of the proposed implementations and start working on the final version of the feature

Roadblocks:

• None

On Sat, Jun 16, 2012 at 9:37 PM, Steven MacLeod <ste...@smacleod.ca> wrote:

Please reply with this weeks status report.

--

[Bogdana Popa]

Hi Steve!

This is the status request email template. Please perform the appropriate actions :)

Thanks,

Bogdana