[00:02] if u want === shardy is now known as shardy_mtg === shardy_mtg is now known as shardy === rangerpbzzzz is now known as rangerpb [16:38] harlowja: how can I fork or work on cloud-init in LP git? [16:39] ok so I create a new repo in my own account and push a clone of cloud-init in their? there is no fork button? [17:18] mgagne it seems so [17:18] larks documented this in https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/301310 [17:18] its a little different than github [17:18] harlowja: yes. [17:18] harlowja: but do you have a specific change you'd like to see? [17:18] will read [17:19] not me, mgagne was wondering where is the fork button :-P [17:19] Oh sorry. [17:19] Ha! [17:19] * larsks wishes we would all just use gerrit. [17:20] looks to not be that bad (LP) [17:20] time will tell =) [17:21] its better than bzr [17:21] imho :-P [17:22] cause i only ever understood the basics of bzr, lol [17:22] harlowja, going to get over to get completely here shortly. [17:22] no argument here :) [17:22] with the changge s that larsks had and mine there. [17:22] cool [17:22] and then its not ata ll impossible for us to have a c-i that mirrors launchpad to github [17:22] then my jenkins pipeline will work! [17:22] lol [17:22] dont know how i feel about that thoguh [17:23] ie, i coudl put github/cloud-init-dev/cloud-init to jsut be pushed to from lp:cloud-init by a bot [17:23] meh, i'm ok with this launchpad bzr [17:23] not perfect imho, but good enough [17:23] github not perfect imho either [17:24] the big thing is that if i do it there, then it implies we'd take reviews from there. [17:24] ya, meh, don't do it then :-P [17:24] or u can do what openstack-infra does, and they shutdown all PR(s) that come through that [17:24] auto-shutdown [17:24] oh. [17:24] hm. [17:25] https://github.com/openstack/taskflow/pull/3 [17:25] for example [17:25] i'm pretty sure that person though never followed through with the PR [17:25] (for worse imho) [17:25] so just a warning :-P [17:26] and i don't think people in projects know about how many/if PR(s) have been auto-closed [17:26] for example [17:26] https://github.com/openstack/nova/pulls?q=is%3Apr+is%3Aclosed [17:26] there are 65 lost reviews there? [17:26] * harlowja i think i complained about that once [17:26] (ie at least send an email to the PTL when a PR gets auto-closed) [17:27] so PTL can at least follow up with person (if they want) [17:35] harlowja: I think monty emailed the list about improving their generic message pushed up to github, to make it more clear how toa ctually contribute [17:38] JayF possibly [17:38] i'd like a 'cc' to the PTL that it got closed on also [17:39] i'm pretty sure that not many people (PTL or other) know to go look and see whats been closed [17:40] I mean [17:40] PTLs haev no time as is [17:40] meh [17:40] life is hard [17:40] that would get filed into a folder and never read ever [17:40] at least for the major projects [17:40] i don't accept the life is hard part [17:40] life is hard, therefore /dev/null [17:40] sounds like a cop-out to me ;) [17:41] back to sucking my thumb in the corner [17:41] ha [17:41] it's all a matter of priorities right? [17:41] sure [17:41] but if right now it goes to /dev/null u can't even assign someone from the PTL(s) team to even look at that stuff [17:41] like folks would rather 1) work a reasonable number of hours and 2) spend those hours working on project priorities, instead of holding the hand of someone who can't read a $#@%$!@#ing doc about how to contribue :P [17:42] thats what interns are for? [17:42] 3) assign task to followup with the folks that got PR closed on them (that may or may not have submitted code to the gerrit system) and be nice and kind to them, and see if they need help [17:42] treat others like u would want to be treated, blah blah [19:03] are unit tests really trying to read files in /proc ? [19:16] harlowja: how do you link your personal repo to the upstream one? I'm following steps found in README, reading LP help page and not much details here, there is no Propose for merge in my repo [19:18] hmmm [19:18] on for example [19:18] https://code.launchpad.net/~harlowja/cloud-init/+git/cloud-init/+ref/fix-distro-tags [19:18] yep, link is showing here [19:18] there was a 'propose for merging' that i clikced thed [19:18] u don't got one? [19:18] there is none for me: https://code.launchpad.net/~mgagne/+git/cloud-init/+ref/bond_name [19:18] *clicked there [19:19] hmmm [19:19] so I think the repo isn't linked with "upstream" [19:19] and I'm not sure how to fix that [19:19] maybe it also needs some commits? [19:19] there is a commit [19:19] which I'm trying to propose for merge [19:19] ah, kk, it shows i think the author as scott [19:20] unsure here [19:20] yes, I didn't code that feature [19:20] i call in smoser who might know, ha [19:20] so I'm not putting my name in there [19:20] k [19:26] harlowja: found it [19:26] Change repository details -> Target: Project: cloud-init [19:27] this detail isn't part of any documentation if found (cloud-init or LP) [19:28] harlowja: ok merge proposal done =) [19:29] mgagne, whats up? [19:29] smoser: a review request? =) [19:30] smoser: was struggling to find how to link my personal repo to the upstream one [19:30] now it's done with above steps === rangerpb is now known as rangerpbzzzz [20:56] smoser: I think the test you are referring to was to test bond_slaves, not bond name. Maybe i'm wrong: http://paste.ubuntu.com/20492837/ [20:57] let me know if I misunderstood the purpose of the test