15:40:38 <dgilmore> #startmeeting RELENG (2015-05-11)
15:40:38 <zodbot> Meeting started Mon May 11 15:40:38 2015 UTC.  The chair is dgilmore. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:40:38 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:40:44 <dgilmore> #meetingname releng
15:40:44 <zodbot> The meeting name has been set to 'releng'
15:40:44 <dgilmore> #chair dgilmore nirik tyll sharkcz bochecha masta pbrobinson pingou maxamillion
15:40:44 <zodbot> Current chairs: bochecha dgilmore masta maxamillion nirik pbrobinson pingou sharkcz tyll
15:40:47 <dgilmore> #topic init process
15:40:53 * masta is here
15:40:58 <masta> howdy folks
15:41:11 * maxamillion is here
15:41:13 <jkurik> hi there
15:41:14 * pbrobinson is here
15:41:20 <dgilmore> bloody squirrel
15:41:22 * nirik is here
15:41:23 * sharkcz is here
15:41:31 * bochecha is here
15:41:37 <dgilmore> he is in my back yard digging up where I just put down grass seed
15:42:02 <pbrobinson> it's legal to own guns there, don't see your issue!
15:42:19 <dgilmore> never eaten squirrel
15:42:21 <maxamillion> pbrobinson: it's not legal to fire them in residential areas though ... it's not quite the wild west anymore
15:42:37 <dgilmore> maxamillion: it is illinois, kinda is :P
15:42:43 <maxamillion> dgilmore: heh
15:42:58 <nirik> bb gun. ;) Just startle him
15:43:12 <dgilmore> okay
15:43:21 <pbrobinson> LOL
15:43:22 <dgilmore> #topic #6158 Request to discuss Rel-Eng Project Planning Proposal
15:43:26 <masta> Your daughter could use a dog dgilmore
15:43:28 <dgilmore> https://fedorahosted.org/rel-eng/ticket/6158
15:43:45 <dgilmore> masta: I had one, the ex has him
15:43:56 <dgilmore> so maxamillion setup a meeting for this
15:43:59 <maxamillion> I did
15:44:14 <dgilmore> to discuss with others so we get something useful for all of fedora
15:44:17 <maxamillion> after talking about it here last week it kind of seemed like something larger in scope than just the rel-eng group
15:44:22 <maxamillion> +1
15:44:29 <dgilmore> though QA is heavily invested inphabricator
15:44:46 <dgilmore> and does not seem to want to change
15:44:48 <maxamillion> I should probably make a wiki page or something for the meeting with background information
15:44:56 <dgilmore> maxamillion: that would be good
15:45:10 * pbrobinson didn't get a chance to look @ whenisgood but i'm fairly flexible
15:45:26 <dgilmore> #info metting on wednesday to discuss
15:45:34 <maxamillion> pbrobinson: https://apps.fedoraproject.org/calendar/infrastructure/2015/5/13/?tzone=UTC#m2538
15:45:42 <dgilmore> #action maxamillion to setup a wiki page with background
15:46:15 <dgilmore> I think it is best for us to use what is agreed upon, I will chime in at the meeting
15:46:26 <pbrobinson> maxamillion: looks OK
15:46:44 <dgilmore> #topic #6159 Request to discuss Git workflow for rel-eng tooling
15:46:50 <dgilmore> https://fedorahosted.org/rel-eng/ticket/6159
15:46:59 <dgilmore> #info going to move to pagure
15:47:19 <dgilmore> #info nirik was setting up a production instance last night
15:47:30 <dgilmore> nirik: how far did you get?
15:47:40 <nirik> no where. :)
15:47:48 <dgilmore> okay
15:47:53 <nirik> I got confused on how exactly we wanted to call it...
15:47:59 <dgilmore> pingou: ?
15:47:59 <pingou> pagure01?
15:48:01 <nirik> and then got caught in mm2 doom
15:48:18 <nirik> pagure01.fedoraproject.org ?
15:48:28 <nirik> and it can answer for pagure.org and pagure.io ?
15:48:30 <pingou> I started reinstalling the stg instance on el7 today, but we managed to lock ourself out :)
15:48:31 <dgilmore> dns wise it will be available at pagure.org and pagure.io right?
15:48:38 <pingou> nirik: yes I think so
15:48:47 <nirik> ok, I can set it up.
15:48:56 <pingou> dgilmore: we have the hand at the dns level for both domains so we can adjust as needed :)
15:49:05 <dgilmore> #action nirik to setup prod pagure
15:49:09 <maxamillion> +1
15:49:11 <nirik> we have a cert for pagure.io... not sure about the others.
15:49:15 <pingou> nirik: still at osuol02 right?
15:49:15 <nirik> but we can set it up
15:49:15 <maxamillion> prod pagure ++
15:49:20 <dgilmore> does anyone have a strong preference for either domain?
15:49:37 <pingou> people seems to like the .org better
15:49:39 <dgilmore> pagure.io is one character shorter
15:49:46 <pingou> but there is that :)
15:49:50 <pingou> and .io are trendy :)
15:49:52 * nirik doesn't care, can adapt to whatever.
15:49:57 * maxamillion has no preference
15:50:18 * pingou doesn't really care either
15:50:33 * pbrobinson things what evah!!
15:50:40 * jkurik likes pagure.org
15:50:40 <pbrobinson> s/thing/thinks
15:50:42 <dgilmore> I perosnaly think .org is a little more respectable
15:50:51 <dgilmore> but I do not have a strong opinion
15:50:59 <pbrobinson> but it's not as hipster!
15:51:07 <lmacken> pagure.ninja is clearly the way to go
15:51:27 <nirik> ha
15:51:28 <pingou> nirik: how annoying/expensive is it to get new certs?
15:51:42 <dgilmore> pingou: what do we have certs for?
15:51:45 <pingou> .io
15:51:48 <nirik> somewhat... we have to do a dance to get authorized to order certs for that domain, then order one.
15:51:50 <dgilmore> then lets use that
15:52:06 * masta kinda likes .io
15:52:08 <nirik> sounds fine
15:52:16 <pingou> problem solved :)
15:52:22 <dgilmore> singe there is a pagure.io cert lets just use that
15:52:40 <dgilmore> #info domain will be pagure.io due to existing ssl cert
15:53:08 <dgilmore> #action dgilmore to get everything setup and moved over once it is in prod and announce
15:53:18 <dgilmore> #topic #6164 bodhi2 status update requested
15:53:24 <dgilmore> https://fedorahosted.org/rel-eng/ticket/6164
15:53:34 <dgilmore> lmacken: ping, what happened in bodhi2 this week?
15:53:58 <lmacken> bodhi2 was going to head to staging last week, but bodhi1 in production exploded
15:54:08 <dgilmore> :( okay
15:54:10 <lmacken> so mash was upgraded on releng04/relepel01 after not having been for 2 years
15:54:17 <lmacken> which caused all sorts of issues to arise
15:54:30 <nirik> along with the issues from eariler in the week before that
15:54:30 <dgilmore> fun
15:54:30 <lmacken> so, it would be great to start running mash in staging
15:54:37 <nirik> +1000
15:54:48 <pingou> sounds nice
15:54:57 <dgilmore> I am planning on a doing some mash dev work in the next few weeks
15:55:00 <lmacken> so I deployed a new version of bodhi1 yesterday with a workaround
15:55:05 <dgilmore> there is some things not working right
15:55:09 <lmacken> and plan on doing work on bodhi2 in staging this week
15:55:17 <dgilmore> and there is areas where we should be performing better
15:55:33 <dgilmore> #info lmacken to get bodhi2 in staging this week
15:55:34 <lmacken> yeah, soon mash will no longer be the bottleneck in the push process, which is awesome.
15:55:48 <nirik> I nuked the old/broken/notused releng01.stg in favor of a new ansible made bodhi-backend01.stg
15:55:57 <lmacken> nirik: cool, thanks
15:56:15 <nirik> if we think 2 is going to be out before too long we could just repurpose it for bodhi2.
15:56:28 <nirik> since out stg setup for bodhi1 is... not functional
15:56:29 <lmacken> sounds good
15:57:00 <dgilmore> ideally we get bodhi2 out soon after f22 is out, we need it to deliver all the things atomic wants
15:57:14 <nirik> that would be just fine with me. ;)
15:57:24 <dgilmore> hopefully it is flexible enough that we can easily extend it for new and different outputs
15:57:27 <lmacken> I'm not sure if bodhi should be The Thing that delivers the atomic stuff, but it can definitely trigger it
15:58:07 <lmacken> ideally our task-running artifact manager system will handle the heavy lifting. "koji 2.0" or whatever.
15:58:09 <dgilmore> lmacken: as long as we have reliable integrated pushing processes, it is less important what does what
15:58:12 <pbrobinson> would need to verify it's sane too to some degree? Not sure you can just fire and hope it all works out
15:58:18 <masta> lmacken: it will never end, feature creep.
15:58:23 <lmacken> masta: srsly
15:58:31 <dgilmore> the thing that is important is that when updates go out, the updates for everything goes out
15:59:12 <pbrobinson> Just wait for rkt/app-c
15:59:14 <dgilmore> when we get the next heartbleed, we are able to update all the bits at once
15:59:24 <dgilmore> pbrobinson: right
15:59:40 <dgilmore> likely we will need to make docker base images as part of the updates process
15:59:51 <dgilmore> and tehn updated docker layered images when tehy come along
16:00:03 <dgilmore> as well as different container formats etc
16:00:30 <dgilmore> I only see the list of deliverables for updates rapidly increasing
16:00:32 <pbrobinson> and I want a pony!
16:01:19 <dgilmore> pbrobinson: why stop there, we have unicorns to get
16:02:15 <dgilmore> what we need to get from a updates push, tomorrow will be different and more than the package repos of yesterday, and the package repos and atomic repo of today
16:02:19 <nirik> unicorn dragon kittens for everyone!
16:02:36 <dgilmore> anyway enough on that. I look forward to seeing how bodhi2 comes along in staging this week
16:02:46 <dgilmore> #topic Secondary Architectures updates
16:02:47 <dgilmore> #topic Secondary Architectures update - ppc
16:02:52 <dgilmore> nirik: +!
16:02:54 <dgilmore> +1
16:03:04 <dgilmore> pbrobinson: how was ppc this week?
16:03:14 <dgilmore> how is the migration to ansible going?
16:03:38 * nirik saw a power8 builder in ansible. ;)
16:04:56 <pbrobinson> we're getting there
16:05:10 <pbrobinson> I spent a bunch of time debugging oz/imagefactory and go
16:05:12 <pbrobinson> co
16:05:17 <pbrobinson> about to get back to that now
16:05:54 <dgilmore> cool
16:06:04 <sharkcz> pbrobinson: how did the TC1, you tried earlier today, go?
16:06:05 <pbrobinson> there's an issue I discovered with some optimised/extra packages which I need to quiz dgilmore over later
16:06:06 * nirik still hasn't had time to make s390 hub/db. Too many fires to put out and not enough hours in the day.
16:06:14 <dgilmore> so for f23 we can/will have different images for ppc
16:06:28 <pbrobinson> sharkcz: it's mashed, just need to look at the compose side
16:06:29 <dgilmore> pbrobinson: happy to help
16:06:38 <dgilmore> pbrobinson: can go over it now if its quick.
16:06:44 <pbrobinson> dgilmore: better later
16:06:48 <dgilmore> if not we should discuss in #fedora-releng later
16:06:50 <pbrobinson> lets get the meeting done
16:07:00 <dgilmore> #topic Secondary Architectures update - s390
16:07:11 <dgilmore> sharkcz: ping, how is s390 this week
16:07:34 <dgilmore> nirik: have we started on teh new hub/db boxes for s390 yet?
16:07:44 * nirik still hasn't had time to make s390 hub/db. Too many fires to put out and not enough hours in the day.
16:07:45 <sharkcz> no major news here, I'm going to start composing TC1 in the morning, didn't get to it today
16:07:51 <dgilmore> okay
16:07:55 <dgilmore> #topic Secondary Architectures update - arm
16:07:59 <nirik> hopefully with freeze I will get some more time to.
16:08:00 <sharkcz> updated lorax is in repos, so this time with productized images
16:08:05 <dgilmore> pbrobinson: aarch64 this week
16:08:12 <dgilmore> sharkcz: cool
16:08:21 <pbrobinson> similar to ppc I'm in process of doing TC1
16:08:52 <dgilmore> cool. Final Change freeze takes effect at 00:00 UTC tomorrow
16:08:57 <dgilmore> so in about 8 hours
16:09:31 <dgilmore> I expect at least one more TC before we get a RC request
16:09:39 <pbrobinson> oh, so not midnight tues/wed like I thought.... oops
16:10:03 <dgilmore> pbrobinson: no, as of Tuesday things a frozen
16:10:45 <dgilmore> #topic Open Floor
16:10:51 <dgilmore> I have one thing for open floor
16:10:52 <nirik> I had one quick item:
16:10:58 <dgilmore> nirik: go ahead
16:11:02 <maxamillion> I have something also when nirik is done
16:11:50 <nirik> I updated all the primary builders. Applied updates and rebooted them. There was a firewall issue on buildhw, but I corrected it now. There was a mergerepo_c issue that has a bug filed, so we downgraded koji back a bit. Otherwise let me know if you see any problems.
16:12:08 <dgilmore> cool
16:13:09 <maxamillion> nirik: what was the mergerepo_c issue?
16:13:32 <maxamillion> I thought mergerepo_c was supposed to fix things
16:13:50 <nirik> https://bugzilla.redhat.com/show_bug.cgi?id=1220082
16:13:56 <dgilmore> maxamillion: the issue was that the koji internal repo was pointing at non existant locations
16:13:59 <nirik> it wasn't setting the prefix right and broke epel builds
16:14:26 <dgilmore> maxamillion: go with your issue, I will do mine last
16:14:55 <pbrobinson> maxamillion: like all things... fix 1 thing, break 6 others ;-)
16:17:14 <dgilmore> maxamillion: what is your item?
16:17:20 <maxamillion> just a sec, typing
16:17:52 <bochecha> squeezing mine in, as it's just an fyi kind of thing: I have some patches to rpkg that I posted to the list last week, which would be nice to review/merge (among other things, they would help migrate away from md5 after f22 is released)
16:17:56 <maxamillion> I just wanted to point out that I'm going to be working on some "Fedora" Atomic stuff (in quotes because it might be a Remix in the man time) to work with upstream to try and sort out how we're going to handle the Atomic bits better in the future ... for now Project Atomic is kind of focusing on CentOS more so than Fedora because it's the path of least resistance, I wanted to try and open a c
16:18:02 <maxamillion> onversation around how I can work on integrating some of the end result of this work when we eventually come to something that's workable for everyone involved
16:18:30 <maxamillion> it's highly possible this is a bigger conversation point than for the open floor but I wanted to bring it up
16:19:00 <dgilmore> maxamillion: we can fit them in if they come and talk to us and work with us.  to date they ahve done a really poor job of that
16:19:00 <maxamillion> brainstorming and proof of concept work is happening here https://github.com/CentOS/sig-atomic-buildscripts .... and I'm going to do my best to participate there and make sure that Fedora concerns are taken into account
16:19:41 <dgilmore> maxamillion: when they come last minute and say we need all this stuff, it makes it impossible toa ccomodate them
16:19:45 <dgilmore> to accomodate
16:20:08 <dgilmore> I know they want to have a spin of fedora atomic every two weeks based on the latest stable fedora bits
16:20:15 <maxamillion> dgilmore: I guess I don't know what you mean by "talk to us and work with us" ... what's the formal process for that? I've had irc conversations with them in #fedora-releng a number of times
16:20:19 <dgilmore> we need to figure out how to do that automatically
16:20:36 <dgilmore> maxamillion: us is releng
16:21:16 <dgilmore> maxamillion: they have never come and tried to work with releng, they have come and made demands. and the times they have done so it is too late and difficult in teh release cycle to make changes
16:21:32 <maxamillion> dgilmore: yes, I understand the concept of who the greater "us" is ... I'm asking what's the process to formally request some sort of co-op? is there a document somewhere on how to handle this properly?
16:22:00 <dgilmore> maxamillion: as features are being developed that need new deliverables, atomic needs to talk to releng so that we can develop plans to integrate the tooling
16:22:25 <dgilmore> maxamillion: the process is to talk on teh mailing list.
16:22:35 <dgilmore> maxamillion: keeping dialog open
16:22:51 <dgilmore> as there is concrete thinsg for releng to do file tickets
16:23:22 <pbrobinson> dgilmore: maxamillion: I think it's a great idea and we can discuss the implications at the FAD which is in a couple of weeks
16:23:31 <maxamillion> dgilmore: hasn't this been done? also, I wrote a patch for the lorax wrapper weeks ago to help enable some of that and it's still unreviewed
16:23:46 <pbrobinson> ultimately the Atomic team have been terrible at communication
16:23:49 <dgilmore> maxamillion: to date communications have been very poor. that needs to change to enable everyone to be able to be productive and get the new things done
16:23:56 <maxamillion> pbrobinson: I don't want the FAD to be a giant brain storm session, I was hoping to do actual work there ... but alright
16:24:41 <dgilmore> maxamillion: it is too late for F22 tooling changes. I have not reviewed because f22 tasks are taking priority over rawhide things
16:24:44 <pbrobinson> maxamillion: well if you have more solid stuff by then it's not a brainstorm session but a high bandwidth discussion of the proposal  and implementation
16:24:50 <dgilmore> which is where that needs to go
16:25:06 <dgilmore> maxamillion: the FAD will not be that
16:25:30 <masta> The FAD will be many things
16:25:31 <pbrobinson> I agree with dgilmore in that the F-22 boat has pretty much sailed, we/they should be looking @ F-23 now
16:25:36 <dgilmore> that leads into my item. I sent a quick note with FAD deliverables to the list last night https://lists.fedoraproject.org/pipermail/rel-eng/2015-May/020075.html
16:25:54 <dgilmore> there is a few things I know i missed
16:26:13 <maxamillion> dgilmore: koji 2.0?
16:26:23 <dgilmore> and I can expand on the items with more detail if they are not clear to all
16:26:42 <dgilmore> maxamillion: its not going to happen for the fad or f23
16:27:07 <dgilmore> maxamillion: I am trying to get people to talk about the needed features and set a road map
16:27:11 <maxamillion> dgilmore: it's going to have to, I've been told I need to be working on it within the next 6-ish weeks
16:27:21 <dgilmore> so far I am getting less traction than I would like
16:27:24 <masta> dgilmore: nice list.
16:27:39 <dgilmore> maxamillion: we have to make thinsg work without koji 2
16:27:56 <maxamillion> dgilmore: I'm getting traction, I had a meeting with mikem last week and we're going to be discussing it again this Thurs
16:28:01 <pbrobinson> I think it should be on the list. mikem was going to get a public discussion/wiki happening since devconf and he hasn't
16:28:02 <dgilmore> maxamillion: we need it and it has to be part of the longer term goals
16:28:05 <masta> dgilmore: I really want to get pungi4 going soon. the #1 item on that list.
16:28:06 <maxamillion> dgilmore: you have the meeting invite for Thurs
16:28:08 <dgilmore> its not going to magically happen
16:28:15 <dgilmore> maxamillion: ?
16:28:27 <dgilmore> maxamillion: what meeting?
16:28:30 <pbrobinson> maxamillion: it would be nice to get some of that discussion happening on the public list
16:28:45 <pingou> or minutes at least :)
16:28:51 <maxamillion> dgilmore: we've talked about it a couple times ... Amanda C. set it up
16:28:55 <dgilmore> maxamillion: the discussion for koji 2 has to happen on the buildsys list or a new dedicated koji devel list
16:29:01 <dgilmore> maxamillion: thats not koji 2
16:29:05 <maxamillion> dgilmore: you should have it to both your @redhat.com and personal account
16:29:10 <dgilmore> maxamillion: that is only layered docker images
16:29:14 <maxamillion> dgilmore: part of that meeting will be to discuss koji 2
16:29:27 <maxamillion> no, it's not ... that meeting has morphed into a lot of things
16:29:28 <dgilmore> maxamillion: not that I know of
16:30:01 <maxamillion> we're way off in the weeds and it doesn't matter, my point is that I would like to see koji 2 on the roadmap for the FAD in at least *some* capacity
16:30:32 <dgilmore> maxamillion: Its not happening, you can add it but we are no where near close enough to start on code for it
16:31:07 <dgilmore> maxamillion: if you want the fad to be all talk and no action then koji2 will take up the whole thing
16:31:09 <pbrobinson> +1 to have it on the FAD agenda
16:31:42 <maxamillion> dgilmore: mikem is going to publish docs on it this week so we can get a lot of discussion in between now and the FAD on the mailing list
16:32:04 <dgilmore> maxamillion: whatever
16:32:10 <maxamillion> dgilmore: what?
16:32:17 <lmacken> I think being able to utilize our build farm for composing all of the updates deliverables is essential. Whether that's koji 2.0 or distill + koji1 + runroot plugin
16:32:37 <masta> maxamillion: sure. Right now the koji2 stuff is still in planning stage, but the koji folks will be there. It will happen =)
16:33:01 <maxamillion> masta: dgilmore just said it won't, I'm trying to understand
16:33:02 <pbrobinson> lmacken: that why we're aiming distill for F-23 with it's functionality
16:33:34 <lmacken> pbrobinson: good, so I'll probably be working on plugins for that during the fad.
16:33:45 <pbrobinson> maxamillion: IMO the koji2 discussion needs to be more public, not 1-2-1 calls
16:33:53 <masta> maxamillion: mikem will be at the FAD, so... it can be formal or informal, but it should not eat away of valuable time spent on FAD things.
16:33:56 <maxamillion> pbrobinson: I'm trying *very* hard to make that happen
16:34:24 <dgilmore> maxamillion: we have a simple way we have to opperate and if any of what you are talking about with koji 2 is true, 1) it is new to me and in violation of how things are supposed to be done.
16:34:28 <maxamillion> pbrobinson: every time I have a call with different teams internally I press the issue of getting it all out in the open so we can have an open discussion with the larger Fedora community
16:34:38 <dgilmore> maxamillion: I am going on what I know and has been discussed in a public forum
16:35:06 <dgilmore> maxamillion: the internal people need to stop having internal calls and do things in the public in an open forum
16:35:14 <dgilmore> without that we will all fail
16:35:28 <masta> yeah
16:35:29 <maxamillion> I'm trying to pull things out in the open, we can't fix the problems of things of internal things being internal by ignoring them
16:35:49 <maxamillion> like, literally ... I'm nagging that issue to the point I'm sure people are sick of me
16:35:51 <dgilmore> I am not saying we can\
16:36:01 <dgilmore> I am saying they need to be told do things right
16:36:22 <masta> maxamillion: nag the good nag, nag conscientiously.
16:36:27 <maxamillion> masta: :)
16:38:00 <dgilmore> maxamillion: in the end we need to take steps to being more open and transparent. the list of deliverables is based on what I think we can do, given the knowledge I have of teh state of things
16:38:22 <maxamillion> dgilmore: fair
16:38:23 <maxamillion> so to round back, as someone who is not yet intimiately familiar with all things Fedora Rel-Eng, what exactly do I need to be aware of and take into consideration so I can advise the Atomic team on how to properly request something so that it's not just considered a demand?
16:38:28 <dgilmore> if my knowledge is wrong we need to get the people who have other plans to open up about tehm in the appropriate places
16:38:36 <maxamillion> dgilmore: I completely agree
16:39:00 <dgilmore> maxamillion: https://fedoraproject.org/wiki/ReleaseEngineering/Philosophy
16:39:46 <dgilmore> there needs to be communicatiion in teh planning of new deliverables so that we can advise how things should be integrated
16:39:55 <maxamillion> dgilmore: I've read that, I like the doc
16:40:01 <maxamillion> dgilmore: alright, thanks
16:40:35 * nirik thinks koji2 may be a ton of work, I don't think it will be done in a fad or quickly.
16:40:35 <dgilmore> maxamillion: it is a requirement that for any new deliverable before a Change is filed releng is approached about how that deliverable will be made and delivered
16:41:01 <maxamillion> dgilmore: alright
16:41:41 <maxamillion> nirik: I don't think it will be done, but I would like it to at least get moving ... I've heard rumors about koji 2.0 for *years* and I just want to make sure it finally makes its way into reality
16:42:24 <dgilmore> maxamillion: the most concrete discussions on koji 2.0 was at fosdem and devconf this year
16:42:47 <dgilmore> before that it was only when we do koji 2.0 we should do foo
16:43:03 <dgilmore> so I would be surprissed if you have hearing chatter about it for years
16:43:05 <masta> dgilmore: on fad task #6, in your opinion does that depend on pungi4/distill working, or can it depend on task #8 runroot working, or could it be made into a pure koji task instead?
16:43:41 <misc> maxamillion: are you sure that's not bodhi 2.0 who you heard ?
16:43:48 <dgilmore> masta: I was pplanning to do taht in koji itself
16:43:52 * masta tries to clarify what things may entail before cherry picking fad tasks
16:44:00 <masta> dgilmore: ok
16:44:08 <maxamillion> dgilmore: I heard it mentioned the first time a FUDCon Lawrence
16:44:10 <dgilmore> maxamillion: bodhi 2.0 has been in development for years now
16:44:15 <maxamillion> dgilmore: yes, I know
16:44:25 <dgilmore> maxamillion: that would be news to me
16:45:00 <maxamillion> anyways ... none of that matters
16:45:38 <dgilmore> what does matter is we need to get a concerete list of things that we want to achieve at the fad
16:45:58 <dgilmore> the things I listed are all things I think we can do at the FAD
16:46:11 <masta> dgilmore: yes
16:46:28 <dgilmore> there is probbaly things that need to be added
16:47:27 <dgilmore> so if there is things people want added. contribute to that thread
16:47:34 <maxamillion> right, I was just trying to suggest koji2 be something on the list ... what the scope of that means can be worked out into an unit of work that is consumable within the timeframe of the FAD, I wasn't suggesting we rebuild Rome in a weekend
16:47:37 <masta> having pagure before the FAD will be excellent.
16:47:53 <dgilmore> if there is things I listed people do not think should be, contribute to that thread
16:48:12 <dgilmore> maxamillion: we can add it
16:48:37 <dgilmore> I will speak to mikem today and try sort out what is going on and get things pulled onto buildsys list
16:48:40 <maxamillion> masta: +1
16:49:20 <maxamillion> dgilmore: he said he'd post something to env-and-stacks this week
16:50:12 <dgilmore> maxamillion: that would be the wrong place I think
16:50:23 <dgilmore> buildsys would be the right place for koji
16:50:28 <maxamillion> dgilmore: rgr
16:50:40 <dgilmore> but maybe there is something I am missing
16:50:47 <dgilmore> because all of this is news to me
16:51:05 <maxamillion> dgilmore: I thought maybe he knew something I didn't so I was going to defer to him on where to post about it
16:52:36 <dgilmore> does anyone have anything else for open floor?
16:55:55 <dgilmore> I will take that as no
16:55:59 <dgilmore> #endmeeting