12:04:47 <mmaslano> #startmeeting Env and Stacks (2014-06-24)
12:04:47 <zodbot> Meeting started Tue Jun 24 12:04:47 2014 UTC.  The chair is mmaslano. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:04:47 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:04:52 <mmaslano> #meetingname env-and-stacks
12:04:52 <zodbot> The meeting name has been set to 'env-and-stacks'
12:04:57 <mmaslano> #chair pkovar tjanez samkottler bkabrda hhorak juhp mmaslano
12:04:57 <zodbot> Current chairs: bkabrda hhorak juhp mmaslano pkovar samkottler tjanez
12:05:04 <mmaslano> #topic init process
12:05:21 <hhorak> Hello guys!
12:05:26 <juhp_> hi!
12:05:42 <mmaslano> hi
12:09:32 <hhorak> So, which topic to begin with? free seats?
12:09:53 <mmaslano> sure :) let's speak about free seats when we have only three people here
12:10:46 <mmaslano> how will we attract more people?
12:10:46 <hhorak> really only 3? even nobody invisible?
12:10:48 <mmaslano> with docker?
12:11:00 <juhp_> :)
12:11:49 <juhp_> to be honest I only just noticed we have the meeting today, but yeah...
12:11:53 <hhorak> mmaslano: so docker will be indeed our part, right? or it is not yet decided..?
12:12:12 <mmaslano> hhorak: I spoke to Matt, he'd like to see more agenda in our WG
12:12:31 <mmaslano> imho other members should work on docker or atomic or something like that
12:15:11 <hhorak> it definitely make sense to me. we should come with some docker-aimed marketing strategy to attract someone..
12:16:02 <juhp_> what kind of docker work?  workflow for releasing images?
12:16:16 <mmaslano> no idea...
12:16:19 <juhp_> ok
12:16:30 <mmaslano> someone could play with taskotron too
12:16:43 <mmaslano> I'd like to look at it in next few weeks
12:17:01 <mmaslano> I'm quite sure I won't finish ruby&rails scl on time, because guidelines are still pending
12:17:25 <mmaslano> so maybe I can look at taskotron and rules for playground
12:19:10 * pkovar si late
12:19:18 <hhorak> mmaslano: I'm also in the look-at-taskotron phase, but enough time is missing.. however, I have some more concrete vision at least (also spoke with ed, rpmgrill maintainer, who accepted and did some of my proposed changes to be more usable in Fedora)
12:20:14 <mmaslano> hhorak: sounds great
12:20:18 <mmaslano> rpmgrill could help
12:22:16 <hhorak> mmaslano: definitely and in the end it won't be so hard, because the taskotron should provide the resultsdb for storing and displaying results, so we won't necessary need infrastructure for it..
12:23:00 <mmaslano> hhorak: sounds like problem with Taskotron is solved
12:23:27 <juhp_> what is rpmgrill?
12:23:28 <mmaslano> #info rpmgrill will be usable by Taskotron
12:23:53 <hhorak> juhp_: https://git.fedorahosted.org/git/rpmgrill.git
12:24:00 <juhp_> thanks
12:24:36 <hhorak> mmaslano: I shortly spoke with mirek about whether to have one instance of taskotron for copr & koji or use a separete one and we agreed that we'd rather use one -- that would probably require some patches for taskotron, but I didn't look at it yet.
12:25:00 <hhorak> also haven't asked taskotron guys, which seems I should do as the first thing
12:26:45 <hhorak> tflink: ^ Tim, if you're nearby, does it seem feasible to have one taskotron instance for both, copr and koji?
12:28:25 <tflink> why would having separate instances be desired over a single instnace?
12:29:35 <tflink> I don't know of any reason why a single instance work
12:29:48 <juhp_> tflink, I think hhorak is suggesting just a single instance :)
12:29:59 <hhorak> tflink: that's it, I don't actually have any reason to have separate instances.
12:30:14 <tflink> why a single instance wouldn't work (complete thoughts help)
12:30:30 <hhorak> tflink: just wanted to check with you if I'm not missing something
12:30:37 <tflink> the bits that are missing which would be needed to work with copr are:
12:30:51 <tflink> 1) enhancements to our trigger code to handle fedmsg emitted by copr
12:31:08 <tflink> 2) code to download things from copr (all we have is koji right now)
12:32:59 <hhorak> tflink: I've already thought about 2) and spoke with mirek a bit -- it seems to me we should have something like `koji download-build` in `copr-cli`. I'll try to come up with a patch.
12:33:21 <tflink> hhorak: is there already a client library for copr?
12:34:07 <hhorak> tflink: yes, copr-cli
12:34:11 <tflink> the way that our koji libarary works is that it gets urls for packages to download through koji's api and downloads them with urlgrabber (for now, it'll eventually be requests)
12:35:59 <hhorak> the copr-cli should be probably the part responsible for transforming copr-build-id or user/coprname to repository urls, then yumdownloader or dnf alternative may be used
12:37:08 * tflink wonders if getting rpmgrill working with koji builds would be a good first step
12:39:07 <mmaslano> tflink: definitely good to investigate whether it's a good idea or not
12:40:23 <hhorak> tflink: I do think it should be done, not sure what should be done first (if speed-up things by not be blocked by copr-things now or test the rpmgrill on copr build before doing it for koji)
12:41:33 <tflink> hhorak: rpmgrill could likely be run in taskotron with our current codebase, copr would require patches
12:43:40 <hhorak> tflink: it seems so. so I'll try to come up with libtaskotron-rpmgrill-module (or how should I call it?) in case nobody else is willing to do so before me :)
12:44:46 <hhorak> (it may take me some time, since I have more unrelated tasks in parallel -- hopefully not more than 2 weeks)
12:45:44 <tflink> hhorak: I'd call it a rpmgrill task, but that's just the name :)
12:46:05 <tflink> let me know if you have any questions, I'm happy to help
12:46:32 <hhorak> tflink: great, thanks!
12:46:37 <mmaslano> tflink: btw don't you want to join Env and Stacks WG? :)
12:48:08 <tflink> mmaslano: not sure I'm the best choice for that, don't know that much about it, to be honest
12:48:11 <hhorak> mmaslano: actually I had a similar idea, to have someone from fedora qe here, which would be great
12:48:31 <juhp_> yes
12:48:36 <mmaslano> tflink: you are doing something, which is great
12:48:41 <mmaslano> related to WG
12:51:49 <mmaslano> tflink: think about it :)
12:51:51 * tflink will re-read the WG docs and think about it, still isn't sure what he'd bring to the table
12:51:53 <mmaslano> more topics?
12:53:34 <hhorak> well, about the other seat, the docker-related one, I guess it would make better sense if someone from RH would take it.. (s)he would simply have some information quicker..
12:53:56 <juhp_> aha
12:54:51 <mmaslano> vpavlin for example :)
12:55:55 <hhorak> well, thinking more about it, the RH-internal thing should definitely not be a requirement, I just thought the things would work a bit better.
12:56:22 <hhorak> vpavlin seems fine, I'm wondering what he things about it :)
12:57:05 <hhorak> or I had also thrcka on my mind
12:58:36 <mmaslano> maybe he's wondering about different candidate :)
12:59:10 <hhorak> Actually, should we offer these too seats on fedora-devel right now or ask those guys first?
12:59:38 <vpavlin> hhorak, mmaslano: I haven't been following the WG's topics for some time:)
13:00:40 <mmaslano> vpavlin: but you are following docker
13:01:29 <vpavlin> mmaslano: Yes, most of the day (yay!)
13:01:59 <mmaslano> vpavlin: you could think also about docker in Fedora and join us ;-)
13:02:18 <mmaslano> hhorak: I guess i can post free seats on fedora-devel and wait who will sign up
13:03:11 <vpavlin> mmaslano: Yes, I guess I could;) I will sign up if you post it on fedora-devel
13:03:32 <hhorak> vpavlin: Great!
13:04:04 <mmaslano> sounds good
13:04:06 <mmaslano> end of meeting?
13:04:23 <mmaslano> we can find new time for next week if you want
13:05:44 <hhorak> mmaslano: nothing else to say today :)
13:06:33 <mmaslano> #endmeeting