| dholbach | good morning | 07:59 |
|---|---|---|
| hyperair | dholbach: i think you could benefit from a script that sends "good morning" to every channel you've joined just after you've connected ;-) | 08:00 |
| dholbach | haha | 08:01 |
| dholbach | hey hyperair | 08:01 |
| hyperair | hi dholbach =) | 08:01 |
| dholbach | nigelbabu: meet bobbo | 09:17 |
| dholbach | bobbo: meet nigelbabu | 09:17 |
| dholbach | :) | 09:17 |
| nigelbabu | hello bobbo :) | 09:17 |
| bobbo | hello nigelbabu :) | 09:18 |
| dholbach | bobbo: basically we don't want to expect patch submitters to do all the leg work, but give them a good experience of getting their patch somewhere | 09:19 |
| dholbach | bobbo: we might have submitters there who know about upstream, debian and all the rest of it already and they'll surely help out if they can | 09:19 |
| dholbach | but I wouldn't expect that to be the majorit | 09:20 |
| dholbach | y | 09:20 |
| bobbo | yeah, it took me a while to understand that when I first started contributing | 09:20 |
| nigelbabu | since you're fairly new to the process, you can perhaps look at our docs and give us feedback on what's missing | 09:21 |
| dholbach | it's tough, particularly with all the different upstream bug trackers and all the rest of it | 09:21 |
| nigelbabu | or what's confusing - it helps a *lot* | 09:21 |
| bobbo | nigelbabu, okay, I'm reading over them now, I'll say if I see anything :) | 09:22 |
| nigelbabu | bobbo: awesome! thanks :) | 09:22 |
| nigelbabu | I'm at work, so I may respond a bit late | 09:22 |
| bobbo | nigelbabu, ping | 09:28 |
| nigelbabu | bobbo: yes? | 09:28 |
| bobbo | nigelbabu, those docs are pretty good, there seems to be enough there to fully explain the process to a newbie and get them ready to start reviewing :) | 09:29 |
| nigelbabu | bobbo: awesome :) | 09:29 |
| dholbach | bobbo: these are the plans for this cycle for the patch reviewers team: | 09:30 |
| dholbach | https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-initiative/ | 09:30 |
| dholbach | https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-process | 09:30 |
| dholbach | maybe you can see if there's anything on there you'd like to help with that looks particularly good or important to you? | 09:30 |
| bobbo | dholbach, looking now :) | 09:31 |
| dholbach | cool :) | 09:31 |
| bobbo | dholbach, maybe one of the more "technical" ones, I'm not the greatest documentation writer, the edit-patch feature (Bug #586787) was one that immediately stood out | 09:36 |
| ubot4 | Launchpad bug 586787 in ubuntu-dev-tools (Ubuntu) "edit-patch should take an existing patch as an argument and apply it (affects: 1)" [Undecided,New] https://launchpad.net/bugs/586787 | 09:36 |
| dholbach | bobbo: sure, if you want to have a look at it, that'd be awesome | 09:37 |
| dholbach | bobbo: mvo wrote most of edit-patch so it'd might be worth talking to him | 09:37 |
| dholbach | bobbo: also there's james_w who wrote some kind of "test patches from bug X for sponsoring" tool, stefanlsd was interested in that task too | 09:38 |
| dholbach | that's all the info I can dump on you :) | 09:38 |
| bobbo | dholbach, so I should take a look at edit-patch and report in if I hit any brick walls? | 09:40 |
| dholbach | bobbo: sure, just try having a chat with the others if they have an immediate idea or a piece of code you can use and see how far you get with the tool :) | 09:41 |
| dholbach | good luck :) | 09:42 |
| bobbo | dholbach, great :D | 09:42 |
| dholbach | nigelbabu: http://daniel.holba.ch/blog/?p=689 | 10:58 |
| * nigelbabu hugs dholbach | 10:59 | |
| * dholbach hugs nigelbabu back | 11:00 | |
| dholbach | if you all can blog about it too, that'd be sweet | 11:00 |
| dholbach | ALL: ^ | 11:00 |
| nigelbabu | dholbach: Also, I'm writing a script all report-debian, takes an LP bug as input and forwards that bug through report-debian to debian! | 11:00 |
| nigelbabu | s/all/called | 11:00 |
| dholbach | nigelbabu: isn't the LP team working on something like that? | 11:01 |
| nigelbabu | dholbach: I haven't heard of them working on that | 11:01 |
| nigelbabu | I heard bryce working on a pedro button | 11:01 |
| dholbach | also it might be worth wrapping it around submittodebian (from ubuntu-dev-tools) | 11:02 |
| nigelbabu | but submittodebian is when we have a patch already in a package and want to forward it | 11:04 |
| nigelbabu | at least thats the impression I got when I tried it last | 11:04 |
| dholbach | nigelbabu: yes, so you just want to forward bugs to debian? | 11:23 |
| nigelbabu | dholbach: yep, seb128 asked if we had something for it and I started writing | 11:23 |
| dholbach | nigelbabu: I'd have a chat with the LP folks first | 11:23 |
| nigelbabu | I already talked to bryce, he helped me a bit when I got stuck | 11:24 |
| dholbach | just in case they're working on it so we don't duplicate work :) | 11:25 |
| nigelbabu | hm, I should perhaps talk to jml today | 11:26 |
| BlackZ | hey dholbach | 11:41 |
| dholbach | hi BlackZ | 11:52 |
| nigelbabu | BlackZ: btw, you guys should think of taking a class at developer week ( when it happens ) | 11:56 |
| BlackZ | dholbach: I'm following up your e-mail | 11:57 |
| BlackZ | nigelbabu: will be done | 12:00 |
| nigelbabu | :) | 12:00 |
| BlackZ | currently we're re-working to the program | 12:01 |
| vish | dholbach: hmm , whats up with the countdown meter? [on the blog] it just shows a black strip with red patch on the side | 13:35 |
| vish | or is it a progress bar? | 13:35 |
| vish | oops , it is a progress bar :D , for some reason i was expecting a number there ;) | 13:36 |
| dholbach | vish: progress bar | 13:42 |
| dholbach | vish: if you can improve the script to make it prettier… :-) | 13:43 |
| vish | dholbach: yeah , i'm trying to find a pretty progress bar , we used it for the -manual | 13:43 |
| dholbach | I use python-imaging | 13:44 |
| dholbach | it's very primitive | 13:44 |
| vish | dholbach: hmm , the guy who did the progressbar for the manual site isnt around right now. I'll hook you up with the good stuff soon ;p | 13:50 |
| dholbach | awesome | 13:54 |
| dholbach | bobbo: how are things looking? do you think the process will be easy enough for my mom and dad to make use of? ;-) | 14:53 |
| bobbo | dholbach, yeah, the instructions are pretty good, I've worked through quite a few of the bugs and not really hit any problems | 14:54 |
| dholbach | cool, that's how we like it | 14:55 |
| bobbo | one thing I'm not sure about though is that the instructions tell you to remove the "patch" tag whenever we add "patch-forwarded-upstream" etc. | 14:55 |
| dholbach | nigelb, bdmurray: ^? | 14:55 |
| * dholbach doesn't know about the state of the discussions and I don't particularly care either way | 14:55 | |
| bobbo | haha, I struggled with that when I was forwarding a patch to gwibber because I know they use the patch tag to identify patches in their bugs and didn't want to trample all over their project | 14:56 |
| bobbo | dholbach, should I just keep working through these bugs or is there anything else you'd like me to do? | 15:00 |
| dholbach | let me have a look at the blueprints again and see if there's something | 15:04 |
| dholbach | bobbo: what do you think about "add documentation about how to turn a patch into a merge proposal if it's a project maintained in Launchpad"? it might be interesting for cases like gwibber and I wrote up a few bits for that already | 15:06 |
| dholbach | bobbo: if you have a look at https://wiki.ubuntu.com/Bugs/HowToFix - there's a few reusable bits | 15:06 |
| bobbo | dholbach, branch merge proposal? | 15:06 |
| dholbach | yep | 15:06 |
| bobbo | I could have a look at it, basically grabbing the project's trunk, applying the patch, (testing it?), then committing, pushing and merge requesting? | 15:08 |
| dholbach | yep, there might be something on help.launchpad.net too | 15:08 |
| dholbach | I don't think you need to write a lot of docs yourself | 15:09 |
| dholbach | just string those bits nicely together, so people can work on that if they hit such a case | 15:09 |
| bobbo | sure I'll give that a go, you say you've already written up some stuff for it? | 15:09 |
| dholbach | https://wiki.ubuntu.com/Bugs/HowToFix | 15:09 |
| bobbo | great, thanks :) | 15:10 |
| dholbach | if you could blog about the operation cleansweep some time this week that'd be nice too | 15:10 |
| dholbach | so we keep the message on everybody's radar | 15:10 |
| dholbach | bobbo: where do you think we should post the message too? | 15:10 |
| bobbo | my domain name has just expired :( too poor to buy it again :D | 15:10 |
| dholbach | I think right now we just covered planet ubuntu, maybe ubuntu-devel@ | 15:11 |
| bobbo | twitter/identi.ca covered? | 15:11 |
| dholbach | bobbo: nevermind - that's fine - I just saw you were listed on planet | 15:11 |
| dholbach | might be worth mentioning it there too | 15:11 |
| dholbach | bobbo: do you think we have enough examples in the docs and stuff that explains when to forward upstream and when not to? | 15:12 |
| dholbach | bobbo: somehow I get the feeling that's what's probably most complicated to newcomers | 15:12 |
| dholbach | nigelb, stefanlsd and I agreed to have a look at the docs again and I already did a few bits | 15:13 |
| bobbo | dholbach, actually yeah, I think that could be expanded, I can imagine people not knowing when to send it up (and whether to go to Debian or straight to upstream) | 15:14 |
| dholbach | bobbo: if you have an idea what else to add there in terms of indication or documentation, that'd be nice | 15:15 |
| dholbach | bobbo: some times it's just 2 or 3 bullet points that make a difference | 15:15 |
| dholbach | … when you're new | 15:15 |
| bobbo | dholbach, cool, I'll give it a think :) | 15:16 |
| dholbach | thanks muchly :) | 15:16 |
| bobbo | dholbach, how does https://wiki.ubuntu.com/DavidFutcher/PatchMergeRequests look? | 15:54 |
| dholbach | bobbo: I'll take a look in a sec | 15:55 |
| bobbo | dholbach, it's just a "first draft", I've never written any (decent) technical docs before :) | 15:56 |
| dholbach | bobbo: it's great | 15:56 |
| dholbach | bobbo: I'd probably add a link to general bzr docs somewhere and put "bzr lp-open" somewhere too, because I like it so much | 15:57 |
| dholbach | bobbo: other than that it's in a perfectly mergable state | 15:57 |
| dholbach | maybe Mr nigelb can take another look | 15:57 |
| dholbach | bobbo: very awesome | 15:57 |
| bobbo | dholbach, great, thanks alot, I'd never head of lp-open before | 15:57 |
| dholbach | bobbo: opens the lp page of the branch | 15:59 |
| dholbach | bobbo: so you just need to click on "submit for merge" or whatever it's called | 15:59 |
| bobbo | dholbach, yeah, it's awesome, don't know why more people don't use it :D | 15:59 |
| dholbach | bobbo: you're there to improve things: you documented it :-D | 16:00 |
| bobbo | heh :D | 16:00 |
| nigelb | bobbo: yes, there should only be one tag at a time patch or patch-* | 16:02 |
| bobbo | nigelb, what if the upstream actively uses the patch tag to identify bugs with patches? Or should we tell them to just use the "Bugs with patches" filter instead? | 16:04 |
| nigelb | bobbo: upstream using LP? | 16:04 |
| nigelb | then its a mess :p | 16:04 |
| bobbo | hehe :D | 16:04 |
| bobbo | are the LP team going to implement a patch status system or are we stuck using tags for a long time? | 16:05 |
| nigelb | bobbo: in that case, you can have both. I see no other way, sadly :( | 16:05 |
| dholbach | bobbo: I think we'll get it at some stage, people should be using branches :-D | 16:05 |
| bobbo | awesome :) | 16:05 |
| dholbach | bobbo: or we should auto-reflow-patches-into-branches | 16:05 |
| dholbach | patches, interdiffs, .diff.gz, tarballs *SHUDDER* | 16:06 |
| bobbo | hehe :P | 16:06 |
| bobbo | I've added some more links in my merge request docs (one to BZR's own docs site and one to help.lp's code review page :) | 16:07 |
| nigelb | dholbach: I think there was some talk of having the code review workflow for patches too | 16:07 |
| dholbach | nigelb: yep | 16:07 |
| nigelb | that would rock! | 16:08 |
| bobbo | that'd be awesome :D | 16:08 |
| dholbach | bobbo: awesome - are you going to merge it into the guide? | 16:08 |
| dholbach | nigelb: you happy with that? | 16:08 |
| nigelb | dholbach: what? where? | 16:09 |
| bobbo | :D | 16:09 |
| dholbach | nigelb: the document bobbo wrote | 16:09 |
| bobbo | nigelb, https://wiki.ubuntu.com/DavidFutcher/PatchMergeRequests | 16:09 |
| dholbach | nigelb: bobbo is totally rocking it | 16:10 |
| nigelb | I got busy with work and missed what was happening here | 16:11 |
| dholbach | no worries - take it easy :) | 16:11 |
| nigelb | bobbo: ROCK! | 16:11 |
| dholbach | seems we're all a pretty excitable bunch :-) | 16:11 |
| nigelb | you can make it part of the knowledge base | 16:11 |
| nigelb | dholbach: there is a low hanging task for anyone intrested | 16:12 |
| dholbach | make it part of the ReviewersTeam namespace and link it from the reviewguide and the knowledge base? | 16:12 |
| nigelb | hunt through the linux packaging that we're subscribed, confirm that kernel patch is required and unsubscribe the team | 16:12 |
| nigelb | dholbach: yep | 16:12 |
| nigelb | bobbo: so, it would be ReviewersTeam/PatchMergeRequests and you can link both to review guide and knowledge base :) | 16:13 |
| bobbo | nigelb, great, I'm on it now :) | 16:14 |
| dholbach | nigelb: hemanth wants to get involved too | 16:15 |
| nigelb | dholbach: get in and get participating :) | 16:15 |
| hemanth | :) | 16:16 |
| dholbach | nigelb: eh? | 16:16 |
| nigelb | ah, I did see him join | 16:16 |
| hemanth | nigelb, hi | 16:17 |
| nigelb | hemanth: hello, thanks for helping out! | 16:19 |
| hemanth | nigelb, my pleasure, was blogging the same, wanted more info on involvement, more related info rather, i went through the wiki | 16:20 |
| bobbo | okay, that's the merge proposals guide linked from the Knowledge Base and review Guide and prettied up a bit :) | 16:30 |
| * hemanth going through the Workflow | 16:41 | |
| bobbo | dholbach, any more jobs to offload to me today? I'm working through some more patch bugs but if there're any other things you'd like me to do? | 16:41 |
| dholbach | bobbo: is there anything in the patch review blueprint work items that's glaring at you? | 16:42 |
| bobbo | dholbach, documentation to help make the decision whether to go upstream or Debian looks do-able? | 16:43 |
| dholbach | bobbo: sure, if you have some additional thoughts for it, that'd be fantastic | 16:43 |
| bobbo | dholbach, okay, I'll give it a closer look, first idea is a subsection of the page linked to from the workflow that explains it in more detail but won't bulk up the workflow paragraph, maybe gives some example bug reports etc | 16:44 |
| dholbach | that sounds like music to my ears | 16:45 |
| bobbo | haha, I'll get looking at it then :D | 16:45 |
| dholbach | bobbo: https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-process has your name on it twice now :) | 16:46 |
| dholbach | you just went and took over for somebody else :) | 16:46 |
| bobbo | wooot :D | 16:46 |
| bobbo | dholbach, is there an official Canonical time to stop working? | 16:47 |
| dholbach | bobbo: I guess that depends on what your contract is ;-) | 16:48 |
| === yofel_ is now known as yofel | ||
| nigelb | bobbo: how much of coding do you do? | 17:40 |
| nigelb | if you'd like to code, I have a task you might want to take over | 17:41 |
| dholbach | nigelb: bobbo's gone for today I think | 17:42 |
| dholbach | and I'm just about to leave too so I'll make it home before the rain starts | 17:43 |
| dholbach | see you tomorrow | 17:43 |
| bobbo | nigelb, ping | 17:56 |
| === nhandler_ is now known as nhandler | ||
| ajmitch | greetings | 23:43 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!