?

Log in

No account? Create an account

Previous Entry | Next Entry

Splinter and git bz

Owen opened the session by demoing Splinter, the web UI for reviewing patches.

Owen went to Bugzilla, listed his open patches, opened the patch view, clicked a line of the patch, and added an annotation. The UI is intended to facilitate adding your own comments but also efficiently view other people's comments in-context.

It stores the results in a normal Bugzilla comment that's human readable but also parseable by the Bugzilla extension. While you are reviewing, it stores your work in DOM storage so that you don't lose it if your browser crashes.

Ryan Lortie said that this is totally awesome. Wide agreement. He also wondered if Owen intends to push it upstream. Owen replied that he doesn't intend to push it upstream but go about rather pushing it as an extension--especially to the Bugzillas he's forced to use.

Owen then switched to git bz, the git bridge to Bugzilla. This tool allows posting patches for review. It turned out that most people in the room had tried it and agreed it is awesome, so a demo was skipped. Owen wants to make it better at merging patches.

A side project that they were thinking of doing was creating a gnome-terminal plugin for a toolbar that displayed your git status, showing all branches and your status with regard to upstream.

Emmanuele was hoping for a branch-per-bug. Owen replied that Dan Williams was hoping for this, but this is hard because, for example, what happens when you `git bz pull` in this branch? Does it pull the current bug status?

Someone asked about pushing git bz upstream. Owen thought that this would never happen: git bz is in Python and upstream is C, Perl and lots of Shell.

And that's it for the Summit Sessions!

At this point, the rest of Summit is hacking with a Beer Summit at 8 PM. (Which I will not be giving the play-by-play of, hopefully. Okay, maybe on Twitter. Check out @gnomesummit!)

Comments

( 4 comments — Leave a comment )
(Anonymous)
Oct. 11th, 2009 09:45 pm (UTC)
git info in the shell
You might want to look at vcs_info zsh module
ext_112319
Oct. 11th, 2009 10:34 pm (UTC)
git bz upstream
I don't understand the quick dismissal of upstreaming git-bz because of Python. Git folks are pragmatic and accept a good tool in any language (but perhaps not a replacement of the core). That said, would the git people carry it in the default "git distribution"? Perhaps.

Otherwise it could go in contrib/, where some Python scripts already reside:

$ find . -name "*.py"
./contrib/fast-import/import-zips.py
./contrib/hg-to-git/hg-to-git.py
./contrib/p4import/git-p4import.py

(More Python might go into git: Patch to add a python package helper for cvs in git: http://marc.info/?l=git&m=125048021702852&w=2 )
(Anonymous)
Oct. 12th, 2009 07:11 am (UTC)
Thanks for the detailed coverage of the event. The unlucky ones that couldn't make it deserve you a beer.
And <I even spotted kind words toward Red Hat :)
trs80 [typekey.com]
Oct. 13th, 2009 02:55 pm (UTC)
You might want to post a roundup, as Planet GNOME only shows the 2 most recent entries (presumably to prevent flooding).
( 4 comments — Leave a comment )

Profile

color, uphair, smile
jasondclinton
Jason D. Clinton

Latest Month

September 2011
S M T W T F S
    123
45678910
11121314151617
18192021222324
252627282930 

Tags

Powered by LiveJournal.com
Designed by Tiffany Chow