[00:38] Question: HOW do you fix bugs when you aren't allowed to upload? I want to start with small things like spelling errors and small stuff. [00:55] Jeffrey_f: In which project? [00:57] in general [01:00] maybe this: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1348873 [01:00] Ubuntu bug 1348873 in shadow (Ubuntu) ""remove" spelled as "remvoe" in "usermod -h"" [Undecided,New] [01:06] Jeffrey_f: Ah, in Ubuntu? [01:06] Sending patches for that kind of thing doesn't really save anyone any time - it's no quicker to review your patch than it would be to just fix it. I'd suggest finding something a little more substantial, honestly. [01:07] (I mean, I understand the sentiment and I know it's necessary to start reasonably small, but maybe not quite that small ...) [01:07] http://community.ubuntu.com/contribute/developers/ might be of interest [01:08] Substantial will come later, getting my feet wet at this point. As I get more comfortable, I may wade a little deeper. lol [01:10] Sometimes, the little stuff is brushed off. One had been a problem for well over 7 yrs from the bug report and the problem still exists in current source [01:10] Right, but you want something that people will want to spend any time reviewing, or you won't get good feedback. [01:10] The actual answer to your original question is to send something in patch format. [01:10] so, how do I do that cjwatson [01:11] Skill zero here is learning how to search based on keywords :-) [01:12] https://wiki.ubuntu.com/UbuntuDevelopment/Patches may be helpful, also http://packaging.ubuntu.com/html/patches-to-packages.html, also the debdiff manual page [01:12] or http://packaging.ubuntu.com/html/fixing-a-bug.html [01:12] yep, In my view, even the little things count. And I just worked through those.......I will look the links over again [01:13] Well, I can only give advice on what I've seen work. It's up to you. [01:20] Thanks! Advice under advisement [02:08] So I have a branch under my login, how do I propose a merge to production code? [02:12] I found it. needed to link a bug to my change then add a merge proposal. === bradm1 is now known as bradm [09:55] hi, why can't I register this project if it doesn't exist? https://launchpad.net/winsparkle [09:55] previously deleted? [09:58] mark06: or it may exist privately; it might be blacklisted/reserved. [09:59] mark06: I can't tell if its there-and-private [09:59] mark06: (but wgrant et al can) [10:02] ok thanks, so a question if I get to register it successfully... [10:03] I want to register after this kind of attitude from the upstream developer [10:03] https://github.com/vslavik/winsparkle/issues/18 [10:04] since I want it translated, I need to implement it myself, then add the suggested launchpad integration for actually feeding the translations... [10:04] the question is: I'm not the original developer, but I do not want someone else to take control over the project and block the launchpad translations I will rely upon [10:05] so is there a chance for that to happen? [10:06] I sincerely would not like to register but... [10:14] uhm [10:15] so if the upstream group came to LP and asked to unregister the project [10:15] thats a tricky one right? [10:15] I wouldn't want to prejudge what will happen [10:20] If I could just build this thing myself, I'd merge it with pidgin++, I think it would make things easier actually... [10:21] but it awesomely can only be built manually with the visual studio monster :-/ [10:26] * mark06 realizes he would need to build it anyway... === mark06 is now known as mark06-away === mark06-away is now known as mark06 === mark09 is now known as mark06 === mark06 is now known as mark06-away === mark06 is now known as mark06-away === kitterma is now known as ScottK === lazyPower_ is now known as lazyPower === Guest7846 is now known as wallyworld