02:01:31 <goozbach> #startmeeting
02:01:31 <goosebot> Meeting started Wed Dec  7 02:01:31 2011 UTC.  The chair is goozbach. Information about MeetBot at http://gooseproject.org/2011/11/07/weekly-meetings.html.
02:01:31 <goosebot> Useful Commands: #action #agreed #help #info #idea #link #topic.
02:01:38 <goozbach> #meetingname weekly
02:01:38 <goosebot> The meeting name has been set to 'weekly'
02:01:49 <goozbach> #chair herlo shalkie makfinsky Nafai
02:01:49 <goosebot> Current chairs: Nafai goozbach herlo makfinsky shalkie
02:03:18 <makfinsky> Hooray!
02:03:23 <goozbach> #topic status updates
02:03:53 <shalkie> Hooray
02:04:40 <herlo> Hooray!?
02:05:12 <makfinsky> Who goes first? Me? Ok.
02:05:18 <herlo> lol, sure
02:05:23 <goozbach> go
02:05:25 <goozbach> yeah sorry
02:05:31 <goozbach> go ahead
02:05:41 <makfinsky> Cleaned up vm hosts that weren't doing anything other than eating resources.
02:05:52 <makfinsky> Corrected sudoers config on gooseqa1.
02:06:10 <makfinsky> Almost have builder #4 online.
02:06:18 <herlo> +1
02:06:24 <makfinsky> Configured email notifications for koji.
02:06:56 <makfinsky> Halfway done with a build host add script.
02:07:30 <makfinsky> Kicked off a bunch of builds for m-p pkgs.
02:07:40 <makfinsky> And that's it for now.
02:07:50 <opapo> I guess I could make it
02:08:03 <opapo> I'll go
02:08:09 <goozbach> opapo: you're turn then
02:08:58 <opapo> I committed my version of repoquery.py along with a README file that is fairly explanatory
02:09:23 <herlo> +1
02:09:32 <opapo> I would appreciate feedback, because although I think it is great it may not be perfect, nor in a usable state.
02:09:50 <opapo> That's all.
02:09:54 <goozbach> herlo:
02:10:01 <herlo> oh hi
02:10:08 <goozbach> your turn
02:10:10 <herlo> so I've been a bit busy
02:10:19 <herlo> got grapple working on roman
02:10:39 <herlo> and wrote a new component to auto-launch builds
02:11:09 <herlo> finished skein 2.0 and it's currently in the release-2.0 branch, going through it's qa fixes
02:11:29 <herlo> should be in master by end of the week
02:12:18 <herlo> I also got packages q-z imported and will be working on others ongoing until we get them all built
02:12:27 <herlo> I'm hoping for this weekend to have *most* built
02:12:30 <herlo> done
02:12:54 <Nafai> I'll go
02:13:12 <Nafai> Didn't do anything this past week, but I plan on reviewing herlo's changes to grapple tonight and merging them with the main repo.
02:13:17 <Nafai> Done.
02:14:16 <goozbach> shalkie:
02:14:18 <goozbach> you're up
02:14:41 <shalkie> I don't think I have actually done anything of interest this week for the projet.
02:14:44 <shalkie> Sorry guys.
02:15:05 <goozbach> ok my turn I guess
02:15:48 <goozbach> I've finally got goosebot a permanent home. I've also done some work on getting autotest/autoqa installed (tis more bleeding edge than I thought)
02:16:07 <goozbach> I've also finished the email sending feature of meetbot.
02:16:20 <goozbach> which this is the first beta test of!
02:16:56 <goozbach> I'm also making good on my promise to dump the contents of the ascendos email brainstorm on the web for forking.
02:17:01 <goozbach> that should be done tonight
02:19:04 <goozbach> and that's me
02:19:38 <goozbach> #topic Build automation
02:19:49 <goozbach> herlo talk to us a min bout that
02:19:56 <goozbach> I need to step afk for a moment bb
02:20:29 <shalkie> goozbach: What about the email to ascend?
02:20:42 <herlo> oh, build automation
02:20:43 * shalkie just wants to ensure it isn't about to drop from queue.
02:21:02 <herlo> so
02:21:11 <herlo> I sent an email yesterday, I think
02:21:21 <herlo> with the whole process, but I'll recount it here quickly
02:21:44 <herlo> the essential part is, after a repo is granted. It will get imported to the repo
02:21:57 <herlo> an import is extract, upload and push, in that order
02:22:26 <herlo> when the commit happens, a post-receive hook calls grapple on roman/koji and adds it to a build queue
02:22:58 <herlo> a second 'client' component of grapple, pulls those commits down every ten minutes and launches a koji build as kojiadmin
02:23:15 <herlo> if the build succeeds, everything is peachy
02:23:38 <herlo> if the build fails, the owner (according to koji) gets an email with the link to the logs and such
02:24:15 <herlo> right now, we've probably got about 2/3 of the builds either going, completed or failed. I've personally seen around 20 failures in the packages I own
02:24:29 <herlo> so the next question is, what to do about failed builds
02:24:45 <herlo> well, the hope is that we can just run them again when we finish the first pass
02:24:54 <herlo> and narrow down the number of unbuildable packages
02:24:56 <goozbach> #action figure out what to do with failed builds
02:25:07 <herlo> goozbach: I already have a plan :)
02:25:21 <goozbach> #undo
02:25:21 <goosebot> Removing item from minutes: <ircmeeting.items.Action object at 0x1485c50>
02:25:29 <goozbach> #info herlo has a plan about failed builds
02:25:35 <herlo> eventually, we'll have only a handful (probably less than 100) packages that may need some sort of intervention
02:25:40 <goozbach> ?
02:25:42 <goozbach> ??
02:25:46 <herlo> for each of those builds
02:25:46 <goozbach> .;/ /
02:25:48 <herlo> lol
02:26:02 <goozbach> that was my son saying "HI"
02:26:07 <herlo> the owner will fix whatever problem is going on...
02:26:21 <goozbach> I gotta go guys
02:26:25 <goozbach> herlo: can you drive?
02:26:28 <herlo> apply patches as needed, or upload a new patch
02:26:30 <herlo> goozbach: sure
02:26:32 <goozbach> I'll email my update later
02:26:35 <opapo> see ya goozbach
02:26:46 <herlo> as I was saying
02:26:55 <herlo> upload a new tar ball rather
02:27:34 <herlo> once the package has been built successfully with koji, we'll need to make sure to send any spec file patches or other .patch files to the proper upstream
02:28:00 <herlo> my thoughts are to file a bug in bugzilla for any sort of item we want to push upstream.
02:28:22 <herlo> we should be able to perform this sort of thing over and over for each release.
02:28:28 <herlo> major or minor
02:28:33 <herlo> thoughts?
02:29:36 <herlo> makfinsky: shalkie: Nafai: opapo ??
02:30:18 <opapo> It sound great, but I'm not using this so I am not one to ask.
02:30:23 <opapo> It is all logical though
02:31:18 <opapo> what if ownership is transferred?
02:31:21 <makfinsky> +1 for the automation workflow.
02:31:31 <opapo> how does knowledge transfer happen?
02:31:55 <opapo> seperate issue?
02:32:10 <herlo> opapo: knowledge transfer?
02:32:46 <herlo> do you mean, 'how do we get patches upstream and available for others to know about them'?
02:32:51 <opapo> If I were to work on bash, then get pulled away and need to transfer ownership to you (let's say) how do you know what I did to work on it?
02:33:18 <opapo> I guess if everything is in the .patch files then we are ok
02:33:22 <herlo> you should commit your patches
02:33:26 <herlo> :) yep
02:33:32 <opapo> ok
02:33:37 <opapo> +1
02:33:38 <herlo> cool. Any other thoughts?
02:35:34 <makfinsky> I imagine that we'll work on adding depsort into the workflow later, perhaps next year.
02:35:41 <herlo> yes
02:36:01 <herlo> I am definitely interested in the work that opapo did there. It's going to be immensely helpful I think
02:36:08 <opapo> let's fine tune it before it is used in production
02:36:33 <herlo> opapo: of course :)
02:36:36 <makfinsky> Right.
02:37:00 <herlo> okay next topic
02:37:30 <herlo> #topic EOY Goals
02:37:55 <herlo> Essentially, I want to lay this out so we don't get blind sided by holiday plans
02:37:57 <makfinsky> I would still like to complete alpha by eoy.
02:38:08 <herlo> me too
02:38:26 <makfinsky> I'd also like to propose a sprint week - the week between xmas and ny.
02:38:39 <herlo> I could make parts of that for sure
02:38:45 <herlo> mostly evenings
02:39:21 <herlo> #info makfinsky wants to have a sprint week between christmas and new years
02:39:51 <herlo> so, let's talk about steps left to get there
02:40:10 <herlo> once we get the majority of the builds complete
02:40:52 <herlo> I'd like to target having all builds complete, even the difficult ones by 12/17
02:40:58 <makfinsky> We need a pungi compose.
02:41:08 <herlo> before that we need something else
02:41:20 <herlo> mash
02:41:41 <herlo> we're going to need to take the repos from koji and put them together in a slightly different way
02:41:45 <makfinsky> What is mash?
02:42:01 <herlo> specifically, we need to mash together the repos from koji so that some i686 libs are in the x86_64 repos
02:42:12 <herlo> and we need to put the noarch repos in both
02:42:19 <herlo> makfinsky: mash does that ^^
02:42:24 <makfinsky> Ah!
02:42:27 <makfinsky> Nice.
02:42:30 <herlo> once we have that
02:42:38 <herlo> we can start composing with pungi
02:42:55 <herlo> I suspect that the last week of the year will be daily if not twice daily composes
02:43:14 <herlo> I'd like to work toward automating that, of course.
02:43:28 <makfinsky> Of course.
02:43:47 <herlo> with a goal of having a reliable kickstart which will build the composes automatically when we hit beta
02:44:13 <herlo> the folks at ascendos can definitely help us here, since they arleady have some composes in place
02:44:24 <makfinsky> Ok, so for EOY goal of alpha we need:
02:44:28 <herlo> though they are having some difficulty with abi compliance
02:44:34 <makfinsky> 1. To complete rpms builds.
02:44:42 <makfinsky> 2. Mash installation and config.
02:44:59 <makfinsky> 3. Pungi and kickstart file for compose.
02:45:24 <herlo> sounds about right
02:46:38 <herlo> cool.
02:46:42 <herlo> #topic Open Floor
02:46:48 <herlo> anything else we want to discuss??
02:47:34 <makfinsky> Keep up the blogging folks!
02:47:41 <herlo> yay!
02:47:43 <makfinsky> Goes for me too... :P
02:47:44 <herlo> good idea
02:48:01 * herlo will be writing up docs the next couple weeks for skein when he has time as well
02:49:32 <herlo> well, I think that's it...closing the meeting shortly. Unless there's something else.
02:49:42 <herlo> 5
02:49:49 <herlo> 4
02:49:58 <herlo> 3
02:50:03 <herlo> 2
02:50:11 <herlo> 1
02:50:14 <herlo> #endmeeting