15:00:50 #startmeeting Council (2019-02-13) 15:00:50 Meeting started Wed Feb 13 15:00:50 2019 UTC. 15:00:50 This meeting is logged and archived in a public location. 15:00:50 The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:50 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:50 The meeting name has been set to 'council_(2019-02-13)' 15:00:55 #meetingname council 15:00:55 The meeting name has been set to 'council' 15:01:08 #chair jonatoni bex contyk dgilmore dperpeet langdon mattdm sumantrom tyll bcotton pbrobinson 15:01:08 Current chairs: bcotton bex contyk dgilmore dperpeet jonatoni langdon mattdm pbrobinson sumantrom tyll 15:01:26 #topic Introductions, Welcomes 15:01:41 .hello till 15:01:43 tyll: till 'Till Maas' 15:01:48 * mattdm is here but going to go run get a cup of coffee in a few seconds 15:01:55 .hello psabata 15:01:56 contyk: psabata 'Petr Ĺ abata' 15:02:01 mattdm: please bring some for the whole class 15:03:02 bcotton: it's fair trade! 15:03:10 unsubscribe! 15:04:07 * langdon was in the wrong room :/ 15:04:10 .hello2 15:04:11 langdon: langdon 'Langdon White' 15:04:28 oops forgot to #chair stickster 15:04:30 #chair stickster 15:04:30 Current chairs: bcotton bex contyk dgilmore dperpeet jonatoni langdon mattdm pbrobinson stickster sumantrom tyll 15:04:32 ok all set 15:04:57 bcotton: you want to #agenda or shall i take over? 15:05:05 i can do it 15:05:13 cool 15:05:17 we have 1/4 objective leads at the moment, so it should be pretty easy :-) 15:05:29 and i don't have much of an update 15:05:37 #topic Agenda 15:05:44 then we should add "objectives writing hackfest" to the list 15:05:48 #info Today is an Objectives update meeting 15:05:50 mattdm: ack 15:05:57 #info 1. Modularity 15:06:00 i was just going to write that ticket 15:06:04 #info 2. Objectives writing hackfest 15:06:14 #info 3. Other objectives if the leads arrive 15:06:23 #topic Modularity Objective update 15:06:27 all you, langdon 15:06:53 sorry.. was distracted 15:07:13 still making steady progress on UI elements and consistency of behavior 15:07:50 we have status in the taiga board.. /me waits for it to load 15:08:01 is that end user or packager ux? 15:08:02 https://tree.taiga.io/project/modularity-wg/timeline 15:08:22 langdon: should we be moving to the fpo instance? 15:08:29 #info still making steady progress on UI elements and consistency of behavior 15:08:40 #info status is in the Taiga board 15:08:41 end user.. however, we need to focus on "packager/developer ux" as a higher priority for a conference that I need to present at :) 15:08:50 #link https://tree.taiga.io/project/modularity-wg/timeline 15:08:51 contyk: i believe the fedora taiga is not ready yet 15:08:56 unless i missed a memo 15:09:17 It's almost ready 15:09:22 it popped up during the team meeting yesterday 15:09:28 sometime in the next week i think 15:09:52 i mean, https://teams.fedoraproject.org/project/modularity-wg/timeline *seems to be a thing :) 15:10:06 ok.. would be nice to move it when we can.. i think it has export/import but i have never really done it 15:10:35 mattdm: weird.. i wonder who made that 15:10:51 langdon: probably a test import 15:11:08 looks like it's out of date though 15:11:12 yeah.. seems a little out of date (6 days) 15:11:16 plus i see that fas login isn't the default currently 15:11:23 it has openid as an option 15:11:28 but we want it to be _the_ thing 15:11:39 are we expecting to use openid or fas? 15:11:48 FAS, I believe 15:12:03 ohh.. it is called openid but is actually fas when you click on it 15:12:22 I also recall someone saying the taiga folks could help us with the migration, which could hopefully include user remapping 15:12:46 ooo and a 500 when i try to use fas! 15:12:48 i'm going to gently nudge the conversation back toward modularity now 15:12:50 * bcotton nudges 15:13:00 ha 15:13:18 ohh.. i think scratch builds are pretty close 15:13:37 contyk: what else would you highlight? 15:13:57 I can only think of the bad stuff 15:14:04 ha.. yeah.. 15:14:15 .hello bex - sorry I am late 15:14:16 bexelbie: Sorry, but you don't exist 15:14:19 but overall it's on track 15:14:22 contyk: can we have a rundown of that, then? 15:14:30 just the lowlights :) 15:14:39 oh, I guess I should have said hi as well :) 15:14:42 .hello dperpeet 15:14:43 dperpeet: dperpeet 'None' 15:14:49 .hello bex 15:14:50 bexelbie: bex 'Brian (bex) Exelbierd' 15:14:55 I think a major pain point right now is the total lack of modularity support in dnf system-upgrade 15:15:12 which was just recently added to the release acceptance criteria 15:15:24 #info A major pain point right now is the lack of modularity support in `dnf system-upgrade`, which was just recently added to the release acceptance criteria 15:15:32 it was broken for f28->f29 and it still is for f29->f30; the difference is now we're going to block on it 15:16:18 what does the dnf team say about delivering it for f30? 15:16:39 nothing yet; we'll discuss it next week 15:17:02 contyk: um, oops. that seems kind of important. 15:17:15 there are two related issues, one of which is more of an rfe 15:17:36 if we drop that, I would expect the other part (simply respecting streams) should be simple 15:18:47 on the more postive front.... copr is getting an upgrade which includes improved module support.. today i belive 15:18:53 *positive 15:19:07 #info COPR is getting improved module support in an upgrade today-ish 15:19:09 positive+festive=postive 15:19:23 contyk++ 15:19:23 ha 15:20:57 anything else from or for langdon & contyk before we move on? 15:21:06 i think that's all i had 15:21:12 * pbrobinson is sort of here 15:21:16 hey I am here 15:21:30 theoretically there should be a refreshed objective proposal. but that can wait until the hackfest discussion at the end of this meeting 15:21:48 yeah 15:22:17 okay, then let's throw it to dperpeet 15:22:24 #topic CI Objective update 15:23:02 so 15:23:32 for CI, I first want to nod towards the hackfest discussion on writing the new proposals 15:23:42 I think the current one is pretty much done 15:23:57 and for the new one, pingou is driving the gating rawhide effort 15:24:18 #link https://fedoraproject.org/wiki/Changes/GatingRawhidePackages?rd=Changes/GatingRawhide 15:24:53 which will be the interface point for a lot of developers to come into contact with the CI 15:25:17 dperpeet: is that change _basically_ the objetive for the next 6 months, or is there more surrounding it? 15:25:32 also, we'll want to link upstream work to Fedora directly 15:25:36 by automating packaging 15:25:53 gating is an enabler 15:26:12 but CI happens when we give feedback on changes 15:26:31 so that developers see "hey, this is what my new release does in Fedora" 15:26:49 target for us is Flock 15:27:05 but don't nail me down on the details, we'll write those up 15:27:37 incidentally, the same tests will still run for stable 15:27:45 or rather, for non-rawhide 15:28:07 so the work that developers / packagers put into the first iteration of the CI Objective will keep serving them 15:28:24 #info Target for gating implementation is Flock 15:28:49 done 15:28:50 :) 15:28:59 questions for dperpeet? 15:29:36 i asked mine :) 15:29:51 i didn't follow the answer though.. 15:30:18 is the change pingou is working on the current CI objective? 15:30:19 the gating proposal change is an important enabler for the Objective 15:30:33 right ok 15:30:41 you can't have CI without gating 15:30:46 so we're helping with that as we can 15:31:18 Objective is: running tests + providing feedback (via automated packaging and other means) 15:31:45 langdon, does that help? 15:31:57 yep.. got it 15:32:32 yay! pbrobinson are you here enough to give an IoT objective update? 15:34:03 let's call that a "no" for now 15:34:11 #topic Objective Writing Hackfest 15:34:23 #link https://pagure.io/Fedora-Council/tickets/issue/245 15:34:23 oo.. i made a ticket 15:34:29 yes 15:34:31 sorry 15:34:40 double undo 15:35:12 #undo 15:35:12 Removing item from minutes: 15:35:13 #undo 15:35:13 Removing item from minutes: 15:35:20 #topic IoT Objective update 15:35:29 go ahead, pbrobinson 15:35:37 we've having quite a bit of interest 15:35:59 \o/ 15:36:10 some serious big deployment interest, as I understand it 15:36:32 from a combination of RH customers (NDA unfortunately), a number of Arm partners (mostly NDA until they stick their head up) and a number of small start ups 15:36:46 #info Quite a bit of interest in Fedora IoT from Red Hat customers, Arm partners, and startups 15:37:06 some of this will begin to become public in the coming months as they start to participate actively 15:37:44 pbrobinson++ 15:37:44 mattdm: Karma for pbrobinson changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:38:08 we have a tech writer for a number of hours that is rapidly improving the getting started docs (yes, the ones I originally wrote we're great) 15:38:12 #link https://docs.fedoraproject.org/en-US/iot/ 15:38:21 feedback on that welcome 15:38:47 we're blocked somewhat there because we don't have a landing page 15:39:16 There's a long-open ticket for the landing page 15:39:25 I've raised that as an escalated priority 15:39:31 at the moment it's ~10 days before I can even discuss getting it priortised and I get the feeling then it'll be low :-/ 15:39:51 and the design team don't seem to want to engage with what I feel the requirements are 15:39:59 It seems liek something we should be able to have *done* in 10 days 15:40:35 the users are going to be widely different and I feel that ramming it in with all the other various deliverables is going to be confusing for those users 15:41:31 pbrobinson: I think that's a consideration for the revised getfedora page with IoT as an edition, not for the landing page, right? 15:41:37 let's make sure those don't get mixed up 15:41:41 #link https://pagure.io/fedora-websites/issue/788 15:41:41 #link https://pagure.io/design/issue/596 15:41:58 In my impression I'm hearing some degree of "we want to do this grand thing with a new vision, so we can't do a simple thing now" 15:42:16 mattdm: TBH I no longer know, I feel it's like the tail is wagging the dog and now I just have a head ache 15:43:20 grand visions are great..... they're like govt IT transformation projects... they're suppose to take 6 months and cost $1m and take 10 years, cost a billion and are still a failure 15:43:46 I need something now, I've only been asking since, from mem, when the objective was approved which is coming up a year 15:44:09 pbrobinson: is getting https://iot.stg.fedoraproject.org/ into production with automatically updated links something that meets your needs? 15:44:13 or does it need something more? 15:44:29 mattdm: it's a good start 15:45:08 I'm sure we could tweak the content, and when the grand unification comes along we can update the look and feel then which would be fab 15:45:17 pbrobinson: I'll push on that, then. 15:45:32 let's move on to the hackfest so we have some time to discuss that? 15:45:55 or when we go from what we have no to an Edition with F-30 it could have the vis refresh then if it's ready as a celebration or something 15:46:23 anyway, other than site things are going along OK, given the resources we have available 15:46:39 we're doing a 29 dot release this week 15:46:57 #info Fedora 29 IoT dot release this week 15:47:17 #topic IoT Objective update 15:47:17 and as time allows between various explosions I'm trying to get the core F-30 bits finished like UEFI on ARMv7 15:47:21 #link https://pagure.io/Fedora-Council/tickets/issue/245 15:47:34 pbrobinson: that sounds like a good plan but I think we need to have *some* site in place soon 15:47:47 bcotton: I think you topiced that wrong :) 15:48:04 just a little 15:48:06 mattdm: d'oh 15:48:07 #undo 15:48:07 Removing item from minutes: 15:48:09 #undo 15:48:09 Removing item from minutes: 15:48:14 mattdm: yes, a lot of people are getting confused and it would make my life a LOT easier to be able to point at a single link 15:48:15 #topic Objective Writing Hackfest 15:48:20 #link https://pagure.io/Fedora-Council/tickets/issue/245 15:48:40 hey, it had the word "objective" in it. what more do you want from me? 15:49:08 LOL 15:49:17 so.. i know it seems odd but it would work much better for me to do a sunday& monday combo and i am not sure if that is actually any different than a fri & sat combo 15:50:26 it doesn't matter to me. karen's going to be mad either way 15:50:34 although less mad about philly than ireland :) 15:50:42 ha 15:50:47 there is a BIG bell 15:50:57 * pbrobinson wonders why I never got this opportunity when I was proposing an objective ;-) 15:50:59 yeah but it's broken 15:51:10 pbrobinson: you didn't ask :) 15:51:23 mattdm: didn't know it was an option ;) 15:51:27 since I'm not an objective lead, I think you can drop me to cut down the costs 15:51:30 * mattdm should have used that as an excuse to go to London. Or Australia. 15:51:30 i just made it up 15:51:51 March 3+4 doesn't work for me, the other is a maybe 15:52:05 London would be ideal :D 15:52:07 So anyway, I'm in support of this and in support of doing it sooner rather than later 15:52:12 I wouldn't need a hotel for London 15:52:13 :D 15:52:18 ha 15:52:27 i am also in support of it, and have a few things i'll leave as a comment 15:52:34 Is the outcome going to be finished proposals? 15:52:46 the reason for philly is because ben is based there and can only do it if there is no travel 15:52:51 bexelbie: thats the idea 15:52:59 dperpeet: Ben Rosser is a student in Philadelphia so it'd be nice to meet him where he lives. Helps us include people who aren't full time 15:53:08 yes, I followed the thread 15:53:18 cool 15:53:27 bexelbie: is that what you wanted for breakdown? 15:53:30 langdon, bexelbie Let's go ahead and state that explicitly in the proposal 15:53:37 ok, this is about 16% of our working budget, assuming no changes in our funding from RH next year 15:54:01 count me out, save costs :) 15:54:06 i am not sure we need everyone on the list 15:54:44 dperpeet: is tomas' the right answer from your perspective? should it be pingou? someone else? 15:55:26 5 minute warning 15:55:42 langdon, Tomas' work is part of it, yes 15:55:55 dperpeet: It kind of sounds like we need you for the top level view 15:56:03 yeah 15:56:30 can you do remote? at least in the us mornings? 15:56:42 I will check March 17+18, remote should be possible at the very least 15:56:50 I will follow up on the ticket 15:56:50 I would do remote if a channel will be available 15:56:52 i added an "outcome" to the ticket 15:58:07 langdon++ 15:58:21 langdon can you also make sure each of the potential invitees knows we put their names in the hat? :) 15:58:47 last call for final question or comment on this before we #endmeeting 15:58:47 yeah... should i tag them in the ticket you think? or send an email? 15:59:10 langdon: definitely tag them in the ticket. a separate email with context is probably good for those who haven't been a part of the discussion already 15:59:13 bexelbie: do you have the info you need? 15:59:15 Can you share in the ticket some of hte agenda/structure that helps us get these aligned in a way we haven't been able to ? 15:59:27 langdon, info I need for what? The budget breakdown - sort of 15:59:42 I think we should look to reduce costs on the hotel from the estimate - but that is a site selection issue 15:59:46 bexelbie: ok.. want to reply in the ticket? i am just not sure what you are looking for 15:59:48 we can work through our system to get you a rate 16:00:02 for budget that was enough - let's do a site bid 16:00:06 for the agenda - that isn't in the ticket yet 16:00:10 bexelbie: yeah.. i just took a swing via kayak 16:00:18 airfare is airfare 16:00:24 the hotel costs and food costs are more controllable 16:00:36 re: agenda.. i would have to think about it.. i am not sure how it is more than .. we all sit in a room and write and are able to ask each other questions.. 16:00:38 I'll loop you in on hte site selection form 16:00:49 okay, we're at the top of the hour 16:00:51 bexelbie: kayak remark was about hotel too 16:00:53 thanks everyone! 16:01:02 bcotton: thanks for running! 16:01:06 #endmeeting