| dholbach | good morning | 08:02 |
|---|---|---|
| === BlackZ_ is now known as BlackZ | ||
| === yofel_ is now known as yofel | ||
| nigelb | ok, the basic idea is, we get to see all bugs with patches attached that are open | 18:51 |
| nigelb | and the user should be able to select by package or by component (main, universe, etc) | 18:51 |
| nigelb | and select status of patch (unreviewed, needs-work, forwarded) | 18:52 |
| nigelb | and it should pop out the list of bugs and download the patch | 18:52 |
| qense | ok | 18:52 |
| nigelb | then if possible display what is the upstream for that project (#wishlist) | 18:52 |
| qense | that would be neat | 18:53 |
| nigelb | so a reviewer has an easy time doing the review | 18:53 |
| qense | that's what we want | 18:53 |
| nigelb | pulling source should also be part of this, but we dont need to go into ground control | 18:54 |
| nigelb | since review is a lot giving back to upstream | 18:54 |
| qense | You want to use the Debian watch files or the Vcs-* fields? | 18:54 |
| nigelb | thats where I'm doubtful | 18:54 |
| nigelb | when submitting a patch for upstream, it should be against their current trunk | 18:55 |
| nigelb | so someone is better off going to upstream | 18:55 |
| qense | then you don't want the watch file | 18:55 |
| nigelb | but sometimes a patch works against ubuntu source and we tweak it for upstream | 18:55 |
| nigelb | so, I'm undecided there | 18:55 |
| qense | The reviewer should be presented with an edit mode. | 18:56 |
| nigelb | so a terminal and text editor in one of the tabs | 18:56 |
| qense | Maybe: first try to autoapply the patch to trunk, if that doesn't work present the user with a clean trunk and ask if he or she wants to apply the patch step-by-step or wants to view the output of the previous autotry | 18:56 |
| qense | Inline text-editor, or embed gedit? | 18:57 |
| nigelb | embed gedit | 18:57 |
| qense | sounds like the best idea to me indeed | 18:57 |
| nigelb | so I'll get the wiki page and mockups over weekend and we can hack code next week? | 18:58 |
| qense | That's a testweek for me. :) It would not be very convenient. | 18:59 |
| nigelb | the week after then | 18:59 |
| nigelb | I need lotsa help with code. I'm usually better at organizing people to code :D | 18:59 |
| qense | the test week lasts from next week Wednesday until the Tuesday after that | 18:59 |
| qense | but I can start helping that week | 18:59 |
| nigelb | ok then exactly 2 weeks from now | 19:00 |
| qense | ok! :) | 19:01 |
| qense | But I may be reachable in between. If you need some advice you can always mail me. | 19:01 |
| nigelb | sure, will do :) | 19:02 |
| nigelb | I'll be on vacation next week (I just remembered) | 19:02 |
| qense | Just remembered. :D | 19:02 |
| qense | nigelb: and remember: the reference manual is your friend! | 19:04 |
| nigelb | qense, I remembered that when writing apport hooks :D | 19:04 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!