Pencils Down Status Report
Mike Conley
From what I can tell, the extensions branch is in better shape than
when I started. I've added the following features:
- Extension enabling/disabling API, and management UI
- Extensions can now be dependent upon one another
- Extensions can now create their own models/tables
- Extensions can now extend the Review Board API
- TemplateHook's can be selective based on the URL that is being
referenced
- Unit tests for the Extensions classes
- Basic Issue tracking
As a framework proof-of-concept, I've created an extension that
gathers reviewing time telemetry, an extension that calculates "review
karma", and an extension that allows other extensions (like the
reviewing time and karma extensions) to display useful statistics in a
single, unified view.
Early on, I closed a couple of simple tickets. I ported the
devserver.sh script to Python. Little things like that.
I wrote a bunch of blog posts about what I was doing, and what I was
finding out during GSoC. All of these are filed under this category:
http://mikeconley.ca/blog/category/technology/computer-science/gsoc-computer-science/
What's Left:
Plenty. The code still needs to get merged into one branch or
another. Documentation never got started, since the whole extensions
framework still seems a bit young and volatile. I'm not done with
this. When GSoC is over, I'll still be here working on it.
I hope that's enough for your reports - but let me know if you need
more,
-Mike
Mario Đanić
hope you are doing well. Its about time I write pencils down
status report, which if all goes well, will be the last report
to this list for this year ;)
What was I supposed to do:
- ultra super fancy review board installer framework
- conquer the world
What did I do:
The framework and the installer went through a lot of iterations,
and I expect both of them to change more over time.
The installer was capable of various things during this
summer, but I believe its now in best shape ever -
json specifications are split in three parts, code
is (for my standards) pretty ok, and error handling
is ... well, better than if it was non-existent :p
I also started writing beginnings of so-called documentation :p
I recently posted another update to the code on
RB instance: http://reviews.reviewboard.org/r/1696/
Please excuse the trailing white-spaces for the moment.
I know you might disagree with some of the choices
and decisions, but we're here to change and improve
on them together, help me learn more, and get something
useful out of it all.
The world conquering part is slowing coming to fruition,
but an NDA forbids me to talk about it more until it
happens, so please stay tuned.
What did I learn:
Plenty! I learned some new python tricks, learned that reviews
can be fun and teach you a lot of new cool stuff you didn't know,
and I learned that ReviewBoard is a very very cool project - I just
wish David and Chris had more time.
What's left:
There are tons of TODO's in the code, there are tons more things
I'd want to do, and I'm sure you have a lot of ideas for changes
and improvements as well. That being said, I hope you'll welcome
me to work with you even after GSoC is over.
With uni fast approaching, next week will be spent on preparing
for it, so I'll have almost no time for coding - however, if for any
reason you feel that I did not do enough for GSoC, please do tell
me and I will *somehow* try to find a bit of time to do a couple
more things as it would really be a pity to fail after having such
a wonderful time.
See ya on IRC ;)
Cheers,
Mario