meetingminutes April 2014

meetingminutes@lists.fedoraproject.org

27 participants
55 discussions

[FZH] Fedora Chinese Meeting Minutes (2014-04-25)
by Alick Zhao 25 Apr '14

25 Apr '14

Hi all, The IRC meeting minutes today are available at the links below. Thanks everyone for attending the meeting. In the meeting we talked about FUDCon bid progress. Please review the proposed ideas and actions. The next IRC meeting will be held on next Friday (2014-05-02). Please come and join the discussion if you can! * Minutes: http://meetbot.fedoraproject.org/fedora-zh/2014-04-25/fedora-zh.2014-04-25-… ================== #fedora-zh Meeting ================== Meeting started by alick at 13:00:09 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-zh/2014-04-25/fedora-zh.2014-04-25-… . Meeting summary --------------- * Roll Call (alick, 13:00:15) * FUDCon APAC 2014 (alick, 13:12:35) * LINK: https://fedoraproject.org/wiki/FUDCon:Beijing_2014 (alick, 13:12:53) * LINK: https://wp-awesome.rhcloud.com/2014/04/20/fad-china-2014-report/ (alick, 13:13:29) * LINK: alick zsun sent out Red Hat meetup minutes (alick, 13:13:48) * ACTION: endle add hotel information (alick, 13:16:28) * LINK: https://lists.fedoraproject.org/pipermail/chinese/2014-April/014637.html (zsun, 13:18:24) * 维基上已有的宾馆信息是陈旧的，没有参考价值，需要更新，补充上北航周边若干不同标准的住宿作为备选。 (alick, 13:20:22) * 可以到网上搜索北航周边各种宾馆的信息、价格，更新到wiki (zsun, 13:21:36) * ACTION: alick tell Red Hat how many slots are available after confirmation with gbraad (alick, 13:25:12) * the topic (How upstram used in downstream or enterprise) is quite good and acceptable. (alick, 13:26:59) * ACTION: zsun Confirm visa status after all invitation letters are sent. (alick, 13:35:32) * ACTION: alick query emily about lennart's invitation letter and visa status (alick, 13:35:51) * LINK: https://docs.google.com/forms/d/11w1Ny0yjOSlM6HNpyGDzNxJdOU06ITNbQlrYE3PALc… (zsun_, 13:43:16) * LINK: https://docs.google.com/forms/d/13-WvTP42MnQCzj_itu6s-nPCF0ouUkEkSFl0Ws_7vO… (alick, 13:44:47) * FUDCon 演讲者 check in & out date 统计大概于下周一完成 (alick, 13:46:23) * ACTION: zsun collect speaker check-in and check-out info and willing of one day tour (zsun_, 13:46:29) * LINK: https://lists.fedoraproject.org/pipermail/fudcon-planning/2014-April/004899… (alick, 13:48:21) * ACTION: zsun query how to have other expense reimbursed since it is a lot for local to pay first (zsun_, 13:51:54) * we use the budget for lodging to cover RMS's fee. (alick, 13:53:28) * LINK: https://lists.fedoraproject.org/pipermail/fudcon-planning/2014-April/004891… (alick, 13:53:59) * ACTION: alick send out first round of invitation letters for non speaker attendees (alick, 13:55:31) * ACTION: zsun send reminder to fudcon-planning for foreign attendees on invitation letter or other help (zsun_, 13:55:55) * ACTION: alick use "邮件合并向导" in libre office to make all the invitation letters at once (alick, 13:56:25) * ACTION: alick zsun cicku List the *need Red Hat's help* items and sync with Grace if needed. (zsun_, 13:59:38) * ACTION: zsun dongfengweixiao Query how other fedora community/FUDCon/FLOCK manage finacial sponsorship or offer receipts for sponsorship, especially how Red Hat was involved (zsun_, 14:00:16) * ACTION: diseng cicku dongfengweixiao Leave possible place for sponsorship on poster (alick, 14:24:43) * ACTION: dongfengweixiao Ask Red Hat and tonghuix for help on possible sponsorship companies (alick, 14:30:09) * ACTION: dongfengweixiao share sponsor docs with others (alick, 14:31:43) * ACTION: dongfengweixiao Query Infrastructure for FUDCon Beijing mailbox alias. (alick, 14:40:36) * LINK: https://fedorahosted.org/fedora-infrastructure/ticket/3309 (alick, 14:41:11) Meeting ended at 14:44:27 UTC. Action Items ------------ * endle add hotel information * alick tell Red Hat how many slots are available after confirmation with gbraad * zsun Confirm visa status after all invitation letters are sent. * alick query emily about lennart's invitation letter and visa status * zsun collect speaker check-in and check-out info and willing of one day tour * zsun query how to have other expense reimbursed since it is a lot for local to pay first * alick send out first round of invitation letters for non speaker attendees * zsun send reminder to fudcon-planning for foreign attendees on invitation letter or other help * alick use "邮件合并向导" in libre office to make all the invitation letters at once * alick zsun cicku List the *need Red Hat's help* items and sync with Grace if needed. * zsun dongfengweixiao Query how other fedora community/FUDCon/FLOCK manage finacial sponsorship or offer receipts for sponsorship, especially how Red Hat was involved * diseng cicku dongfengweixiao Leave possible place for sponsorship on poster * dongfengweixiao Ask Red Hat and tonghuix for help on possible sponsorship companies * dongfengweixiao share sponsor docs with others * dongfengweixiao Query Infrastructure for FUDCon Beijing mailbox alias. Action Items, by person ----------------------- * alick * alick tell Red Hat how many slots are available after confirmation with gbraad * alick query emily about lennart's invitation letter and visa status * alick send out first round of invitation letters for non speaker attendees * alick use "邮件合并向导" in libre office to make all the invitation letters at once * alick zsun cicku List the *need Red Hat's help* items and sync with Grace if needed. * diseng * diseng cicku dongfengweixiao Leave possible place for sponsorship on poster * dongfengweixiao * zsun dongfengweixiao Query how other fedora community/FUDCon/FLOCK manage finacial sponsorship or offer receipts for sponsorship, especially how Red Hat was involved * diseng cicku dongfengweixiao Leave possible place for sponsorship on poster * dongfengweixiao Ask Red Hat and tonghuix for help on possible sponsorship companies * dongfengweixiao share sponsor docs with others * dongfengweixiao Query Infrastructure for FUDCon Beijing mailbox alias. * zsun * zsun Confirm visa status after all invitation letters are sent. * zsun collect speaker check-in and check-out info and willing of one day tour * zsun query how to have other expense reimbursed since it is a lot for local to pay first * zsun send reminder to fudcon-planning for foreign attendees on invitation letter or other help * alick zsun cicku List the *need Red Hat's help* items and sync with Grace if needed. * zsun dongfengweixiao Query how other fedora community/FUDCon/FLOCK manage finacial sponsorship or offer receipts for sponsorship, especially how Red Hat was involved * **UNASSIGNED** * endle add hotel information People Present (lines said) --------------------------- * alick (198) * zsun_ (73) * dongfengweixiao (40) * zsun (18) * zodbot (17) * BinLi (16) * BadGirl (12) * diseng (10) * kraks (8) * isyangxin (2) * xielingyun__ (1) * biergaizi (1) * CyrusYzGTt (0) * gbraad_ (0) * tiansworld (0) * microcai (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Alick Fedora release 20 (Heisenbug) user https://fedoraproject.org/wiki/User:Alick

1 0

Sumarry/Minutes from today's Fedora Infrastructure meeting (2014-04-24)
by Kevin Fenzi 24 Apr '14

24 Apr '14

============================================ #fedora-meeting: Infrastructure (2014-04-24) ============================================ Meeting started by nirik at 18:00:48 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-04-24/infrastructure.2… . Meeting summary --------------- * aloha (nirik, 18:00:48) * New folks introductions and Apprentice tasks. (nirik, 18:03:09) * LINK: http://fedoraproject.org/easyfix/ (webpigeon, 18:14:47) * LINK: http://fedoraproject.org/easyfix/ (nirik, 18:14:47) * Applications status / discussion (nirik, 18:17:10) * new fedocal in prod this week (pingou, 18:17:28) * new pkgdb2 in stg this week (pingou, 18:17:37) * new copr release went out this morning with some minor bugfixes (nirik, 18:17:39) * Sysadmin status / discussion (nirik, 18:28:07) * sent out last announcement about ssl certs all redone for heartbleed (nirik, 18:28:49) * new virthost in ibiblio... ibiblio04 to replace 01 thats going end of life. (nirik, 18:29:17) * LINK: http://paste.fedoraproject.org/96714/64701139 is the full list (nirik, 18:38:50) * LINK: https://admin.fedoraproject.org/nagios/ (nirik, 18:44:02) * ideas to reduce nagios alerts welcome. (nirik, 18:45:07) * Upcoming Tasks/Items (nirik, 18:46:37) * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/ (nirik, 18:46:38) * LINK: https://fedoraproject.org/wiki/FAD_Bodhi2_Taskotron_2014 (threebean, 18:48:16) * Open Floor (nirik, 18:53:54) * LINK: https://github.com/stef/pywik (pingou, 18:56:21) Meeting ended at 18:59:57 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (108) * pingou (42) * threebean (18) * henderbj (17) * Penasio (14) * bwood09 (13) * adimania (11) * lmacken (7) * tflink (6) * ghostalker (6) * webpigeon (6) * kjs (6) * mirek-hm (6) * zodbot (5) * smooge (5) * relrod (3) * oddshocks (2) * janeznemanic (1) * blob (1) * mpduty (1) * dgilmore (1) * mdomsch (0) * puiterwijk (0) * abadger1999 (0) -- 18:00:48 <nirik> #startmeeting Infrastructure (2014-04-24) 18:00:48 <zodbot> Meeting started Thu Apr 24 18:00:48 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:48 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:48 <nirik> #meetingname infrastructure 18:00:48 <nirik> #topic aloha 18:00:48 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 18:00:48 <zodbot> The meeting name has been set to 'infrastructure' 18:00:48 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 18:01:11 <janeznemanic> hi 18:01:20 * adimania is here 18:01:24 * pingou 18:01:32 * ghostalker is here 18:01:54 <dgilmore> hola 18:02:23 * relrod here 18:02:23 * threebean is here 18:02:36 * bwood09 is here 18:03:06 <nirik> cool. lots of new folks too. ;) 18:03:09 <nirik> #topic New folks introductions and Apprentice tasks. 18:03:13 * lmacken 18:03:22 <nirik> anyone new like to give a short introduction of themselves? 18:03:28 <nirik> or apprentices with questions or comments? 18:03:31 <ghostalker> Sure 18:03:55 <ghostalker> I'm a 28 year old Sr Systems Engineer looking to take my operations experience and development skills to the next level, while giving back to the community. I'm also the one who didn't include the IRC nick in the email to the infra distro yesterday. 18:04:17 <nirik> welcome ghostalker! 18:04:25 <bwood09> Guess I should too 18:04:26 <pingou> welcome on board :) 18:04:29 <nirik> are you more interested in sysadmin type things? or application development? or both? 18:05:25 <ghostalker> A little of both. I have been just lurking since yesterday trying to get an idea of how things are structured. My development tends to be around helping do SysAdmin things. 18:05:49 <nirik> excellent. Always a need for sysadmin tooling too. :) 18:05:54 <nirik> bwood09: welcome and go ahead. ;) 18:05:55 <kjs> hi 18:05:58 <bwood09> I'm a (mostly hobbiest) sysadmin that is really into open source projects, but not a full-on programmer. Figure it'd be fun to try working with you guys 18:06:04 <ghostalker> As stated though my Python is weak so I would like to focus on SysAdmin related things will learning my way around. 18:06:13 <ghostalker> while* 18:06:32 <bwood09> I'm trying to work on my python skills too 18:06:41 <threebean> welcome :) 18:07:01 <Penasio> .fas 18:07:01 <zodbot> Penasio: (fas <query>) -- Search the Fedora Account System usernames, full names, and email addresses for a match. 18:07:07 <kjs> I'm interested in women, drugs and alcohol... 18:07:16 <henderbj> Hello all... first time on Infraestructure meeting 18:07:24 <Penasio> hi all... 18:07:28 <kjs> hi bj 18:07:32 <nirik> great. :) See me after the meeting over in #fedora-admin and I can get anyone interested added to our apprentice group: https://fedoraproject.org/wiki/Infrastructure_Apprentice 18:07:38 <Penasio> first time to me too 18:07:55 <pingou> it's cool to see so many new folks :) 18:08:17 <kjs> nirik: is kevin ? 18:08:36 <henderbj> Tnx, nirik... i want to get into apprentice group 18:08:40 <nirik> kjs: thats me, yes. well, one of them anyhow.... it's a somewhat common name. 18:08:56 <kjs> thought i recognised your nick 18:08:59 <blob> hello -- I'm interested in volunteering with releng and/or infrastructure. I've got quite a bit of sysadmin and development experience and currently work on a release engineering team for a large software project. I'm a long time fedora user and free software advocate that would like to give back. 18:09:19 <nirik> wow. lots of new folks ;) welcome blob as well. 18:09:39 <pingou> blob: cool 18:10:58 * oddshocks here late 18:11:03 * oddshocks in lecture 18:11:23 <pingou> oddshocks: enjoy 18:11:27 <nirik> Penasio / henderbj: care to introduce yourselves quickly and let us know if you are intested more in sysadmin or app devel? 18:11:51 <Penasio> My name is Claudio Penasio Jr. 18:11:54 * mpduty is here 18:12:13 <henderbj> Hello... i has been sysadmin a long time now... i can help there if you like 18:12:16 <Penasio> i'm Fedora user since 2003 18:12:37 <Penasio> sysadmin since 2000 18:12:45 <kjs> fyi im interested in sysadmin, but dont mind crossing the line every now and again, especially if it's security related. 18:12:49 <henderbj> I am willing to work in development too 18:12:57 <Penasio> i'm from ambassadors group 18:13:07 <webpigeon> O/ 18:13:29 <henderbj> I have experience programming... most on C, and Visual C, for Windows and a little for linux 18:13:39 <Penasio> 2009 to now i'm working on IT support manager 18:13:40 <nirik> excellent. :) Welcome everyone. I can add interested sysadmin folks to our apprentice group after the meeting over in #fedora-admin and we have #fedora-apps for our application development stuff... we can point you to easyfix tickets to look at getting started, etc. 18:13:43 <Penasio> :( 18:13:55 <henderbj> I programmed on Pascal, Matlab, PIC (assembler and C) 18:14:22 <Penasio> easyfix 18:14:25 <nirik> Most of our application development is python related and various python frameworks. ;) 18:14:36 <Penasio> look's like good 18:14:46 <henderbj> Ok... time to learn puthon then ;) 18:14:47 <webpigeon> http://fedoraproject.org/easyfix/ 18:14:47 <nirik> http://fedoraproject.org/easyfix/ 18:14:53 <nirik> :) 18:14:56 <webpigeon> :) 18:14:58 <Penasio> i'll need some menthoring 18:15:09 <henderbj> python, sorry!! 18:15:32 <threebean> lots of us can help ;) if you get stuck anywhere, be sure to ask (more than once.. sometimes, everyone is sleeping or something) 18:15:32 <nirik> Penasio: feel free to ask questions in any of our channels as you go and anyone available can answer and help you out. ;) 18:15:34 <henderbj> with u is kind of a bad word on spanish ;) 18:15:45 <nirik> henderbj: :) 18:16:06 <Penasio> thank's a lot 18:16:11 <pingou> henderbj: I guess it's close to the French one ^^ 18:16:16 <Penasio> i'm looking the easyfix 18:16:19 <nirik> ok, anyone else new who hasn't typed up yet? 18:16:58 <nirik> ok, great. ;) 18:17:02 <nirik> welcome again everyone! 18:17:10 <nirik> #topic Applications status / discussion 18:17:16 <henderbj> Tnx for warm welcome :) 18:17:21 <nirik> any application development news this week? 18:17:28 <pingou> #info new fedocal in prod this week 18:17:29 <nirik> I saw there was a new copr release... 18:17:37 <pingou> #info new pkgdb2 in stg this week 18:17:39 <nirik> #info new copr release went out this morning with some minor bugfixes 18:17:43 <pingou> (likely another one coming tomorrow) 18:17:48 <pingou> (pkgdb2 not copr :)) 18:18:01 <nirik> ok, cool. 18:18:14 <pingou> I spent today fix bugs and RFE on pkgdb2 after the announce I sent to the devel list 18:18:19 <pingou> which is nice :) 18:18:36 <lmacken> lots of bodhi2 development since PyCon. threebean has been working on a slick web fontend, and it's looking great. 18:18:41 * nirik looks for abompard. I wonder where we are with hyperkitty. Perhaps we could do some targeted testing on it and see about migrating a list or two? 18:18:43 <pingou> the other part of the day was spent on https://github.com/jmflinuxtx/kerneltest-harness/tree/master/frontend 18:19:02 <threebean> I bet abompard is vacationing still after pycon.. I think he was going to be travelling. 18:19:11 <pingou> which is a small app gather kernel test results 18:19:14 <nirik> for new folks: https://apps.fedoraproject.org/ has a overview of all these apps... where you can find more info on the source, etc. 18:19:27 <pingou> gathering* 18:19:37 <nirik> pingou: great. Thats redone in flask? or ? 18:19:43 <pingou> nirik: yes flask 18:19:54 <nirik> and it would use postgres? 18:20:00 <nirik> threebean: ah, gotcha 18:20:04 <pingou> Justing is working on import its data in it so we can test it a bit more 18:20:10 <pingou> I still have one idea for it 18:20:23 <pingou> nirik: yup, flask and sqlalchemy so we can use whatever we want :) 18:20:40 <threebean> great :) 18:20:43 <nirik> pingou: can you reply to the list post about that? so we keep people just watching the list in the loop 18:20:49 <pingou> nirik: will do 18:21:28 <threebean> i've been working on some monitoring stuff for fedmsg based on this stuff - http://threebean.org/blog/threading-moksha/ 18:21:37 <nirik> lmacken: is that up on the dev instance? or just local ahcking so far? 18:21:55 <threebean> i've got new moksha rpms in our staging environment that are working well now. soon to follow are some new nagios checks and collectd plugins. 18:22:29 <pingou> threebean: nice! 18:22:40 <pingou> threebean: you should blog about which approach you took finally :) 18:22:48 <threebean> oh, the last one. :) 18:23:09 <pingou> dedicated queue per thread 18:23:28 * threebean nods 18:23:36 <nirik> another thing I wanted to bring up: the bugzilla cookie/token change. :) Seems it's pushed back now, but we could still try and be ready. 18:23:37 <lmacken> nirik: just local right now, it's super easy to setup and import a db snapshot 18:23:39 <pingou> oh on the app front, I made some nice progress on gitsync https://github.com/pypingou/gitsync (also with the help of threebean :)) 18:24:11 * pingou sees the readme needs an update 18:24:15 <nirik> lmacken: nice. Question: is there anything private in bodhi db dumps? or could we make them public? 18:24:27 <lmacken> nirik: they've been public from day 1 of bodhi 18:24:44 <nirik> oh? I had no idea... :) where at? 18:24:54 <pingou> I also converted the DB model of mirrormanager to sqlalchemy, as a first step for MM2 :] 18:25:34 <threebean> nice. abadger1999 was talking about working on a mirrormanager rewrite. you may want to catch up with him about it when he's back from vacation. 18:25:39 <lmacken> nirik: https://fedorahosted.org/releases/b/o/bodhi/ - `make init` in bodhi1 pulls it in automatically, and the bodhi2 readme has instructions for importing it as well 18:25:50 <nirik> excellent. :) 18:25:52 <pingou> threebean: I've heard we would team up ;-) 18:26:46 <nirik> ok, any other application news or questions or comments? 18:27:24 <smooge> the sky is blue 18:27:30 <pingou> smooge: grey here 18:27:41 <adimania> dark black here :( 18:27:45 <nirik> sort of a off white ceiling color here. ;) 18:28:07 <nirik> #topic Sysadmin status / discussion 18:28:34 <nirik> ok, on the sysadmin side of things... 18:28:49 <nirik> #info sent out last announcement about ssl certs all redone for heartbleed 18:28:58 <nirik> hopefully we are done with heartbleed stuff now 18:29:17 <nirik> #info new virthost in ibiblio... ibiblio04 to replace 01 thats going end of life. 18:29:49 <bwood09> I have a quick question 18:29:50 <nirik> new machines in phx2 are going to be installed by smooge over the next few weeks. 18:29:56 <nirik> bwood09: sure, fire away anytime. 18:30:34 <bwood09> I was looking at the easyfix list; why are we switching from puppet to ansible? Since I'm new, I'd like to hear the thought behind that. 18:30:50 <bwood09> (Ticket 4220) 18:30:56 <nirik> bwood09: I suppose I should make a wiki page for it or something, as people keep asking about it. ;) 18:31:08 <nirik> basically ansible meets our needs better. 18:31:42 * mirek-hm is late 18:32:00 <relrod> I started working on porting the puppet nagios server module to ansible this morning, but still have a long way to go. No ETA yet. 18:32:37 <nirik> It's simpler, it's in python (and we are mostly a python shop), it's agentless so we don't need to run a agent on all machines, it uses ssh instead of a seperate protocol, it allows us to manage things that are different oses more easily (fedora and rhel), etc 18:32:45 <bwood09> alright 18:32:50 <henderbj> sysadmin work has levels, like level 1, level 2, level 3? 18:32:50 <bwood09> Makes sense, actually 18:33:11 <nirik> relrod: cool. threebean had some ideas around that a while back I think... how to autogenerate much of it? 18:33:54 <nirik> henderbj: well, there's various groups... the apprentice group allows people to login to a bunch of machines and see our git repos, etc... but it's read only, you need someone else to review and make the actual change... 18:33:55 <henderbj> where i worked, level 1 are those facing clients, level 2 is medium problems, and level 3 for developers problems 18:33:59 <relrod> hm ok. I just started doing a straight port, I figured we could automate it later if we decide to...but if we want to do it as we port, we can try 18:34:48 <nirik> henderbj: next are sysadmin-something groups... those are areas that can make changes... like 'sysadmin-noc' is people who can login to machines, has sudo on some and can commit changes, etc. 18:34:58 <threebean> relrod: yeah, I didn't have much :) 18:35:14 <henderbj> got it... tnx 18:35:18 <nirik> then there is sysadmin-main, which is the folks who have access to everything... thats a small group that people are added to only after a long record of contribution. ;) 18:35:35 <threebean> relrod: we could probably automatically determine things like dependencies between hosts and guests. but services get trickier. 18:35:37 <nirik> so, speaking of nagios... 18:35:38 <henderbj> i read about it a little before 18:35:47 <pingou> nirik: and few craig of beers 18:36:03 <nirik> I wanted to do a new thing in the meeting every week in this section... 18:36:22 <nirik> I want to go over the last weeks nagios alerts, and see if we can come up with ways to cut them down. ;) 18:36:23 <pingou> oh, shiny new things every week! :) 18:36:33 <adimania> +1 18:36:48 <adimania> I am doing something every similar these days at work. 18:37:08 <adimania> We generate a report of all the alert sent out every day and review it. 18:37:27 <nirik> adimania: cool. nagios? do you have a script for it that we could reuse? 18:37:34 <nirik> I just manually looked before the meeting. ;) 18:37:49 <nirik> there were 77 alerts in the last 7 days. 18:38:00 <nirik> 11 of those were from unbound-telia01 18:38:14 <adimania> We just send a metric to graphite every time we create any noise. 18:38:31 <nirik> 29 of them were from network problems at coloamerica... various instances there 18:38:31 <adimania> and do an aggregate at the end of the day. 18:38:50 <nirik> http://paste.fedoraproject.org/96714/64701139 is the full list 18:40:05 <nirik> so, I think I will adjust unbound-telia01 to do more retries before alerting... or longer timeframe. 18:40:32 <nirik> any other patterns folks can see or things we could adjust? 18:41:13 <threebean> at very least, it can give admin apprentices something to look for in the coming week 18:41:17 <nirik> if you come up with any, please do let me know or propose changes. ;) 18:41:21 <pingou> ftr, there are a *bunch* of email on the queue on bastion 18:41:35 <pingou> -- 77340 Kbytes in 7426 Requests. 18:41:37 <nirik> pingou: thats always been the case... it's the mail gateway... so it gets deferred stuff 18:41:42 <henderbj> disconnection alerts are good 18:41:43 <pingou> ok 18:42:03 <henderbj> they inform about poor connections, bottlenecks, or something 18:42:22 <nirik> another source of alerts for a while (or perhaps it was just emails) was fas02... it was getting overloaded from time to time. 18:42:34 <webpigeon> couple of disk space alerts in there 18:42:34 <adimania> swap alerts? 18:42:35 <nirik> I tweaked it's config some and it's been much better 18:42:39 <henderbj> maybe the other side has high cpu usage, etc 18:43:41 <nirik> yeah, a few swap alerts... usually thats when something gets hammered with requests or there's some problem processing. 18:43:55 <nirik> you can all also look at nagios directly to see the exact times, etc 18:44:02 <nirik> https://admin.fedoraproject.org/nagios/ 18:44:40 <nirik> also, there's a few easyfix tickets I filed about adding some machines to nagios. ;) 18:45:07 <nirik> #info ideas to reduce nagios alerts welcome. 18:45:20 <nirik> Finally on the sysadmin side, there may be a outage next week... 18:45:24 <adimania> I can pick that up, if no one else is looking for easyfixes. 18:45:41 <nirik> the storage folks are finally hoping to move our backend storage. They say it won't cause any problems, but we should schedule an outage just in case. 18:45:54 <pingou> +1 18:46:03 <nirik> adimania: feel free. I need to file another one too.... lots for everyone. ;) 18:46:22 <nirik> any other sysadmin news/questions/comments? 18:46:37 <nirik> #topic Upcoming Tasks/Items 18:46:38 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/ 18:46:46 <nirik> anything upcoming folks would like to note or schedule? 18:46:47 * webpigeon still needs to refine his dns script, but hasn't had time with work 18:46:50 <nirik> threebean: hows the fad looking? 18:47:01 <adimania> FUDCon APAC is in less than a month. I am looking for a really really easyfix puppet module which I can migrate to Ansible in a probable workshop. 18:47:06 <nirik> webpigeon: no worries. we will get there when we do. ;) 18:48:08 <threebean> nirik: good, I think. we've got hotels and flights set at this point. 18:48:16 <threebean> https://fedoraproject.org/wiki/FAD_Bodhi2_Taskotron_2014 18:48:17 <pingou> threebean: nice :) 18:48:51 <nirik> cool. 18:48:57 <mirek-hm> I am working on ansible manifest to install recent open stack - I am sowhere in half a way. If somebody want to help, just ping me 18:49:02 <nirik> I still need to send out info asking for interest in an ansible one. 18:49:07 <threebean> unless I'm forgetting something, we just need to get there and make the magic happen. 18:49:30 <nirik> threebean: excellent. ;) 18:49:48 <nirik> mirek-hm: thanks for working on that... are you basing on icehouse? 18:49:58 <mirek-hm> nirik: yes 18:50:02 <nirik> great 18:50:56 <tflink> threebean: are there any plans to work on the 1st? I'm trying to figure out when to head up to Denver 18:50:57 <nirik> oh, one other thing upcoming... not next week, but the week after, I will be out mon-wed... really the 1st-5th. 18:51:06 <tflink> mirek-hm: what kind of help are you looking for? 18:51:47 <mirek-hm> tflink: at least some review would be welcome 18:51:52 <threebean> tflink: I was hoping to work then, but we haven't sorted that out. bocecha is actually getting in on the 31st. 18:51:57 <pingou> nirik: the same week, I'll be out, Mond to Friday, 5th to 9th 18:52:27 <mirek-hm> tflink: or take some chapter from installation guide and implement it (that would be super cool) 18:52:39 <bwood09> Oh, wow, Nagios let me log in with my creds 18:53:02 <nirik> bwood09: yeah, should be open to any fas accounts for read only. It likely won't let you ack alerts or anything tho 18:53:10 <bwood09> Figured as much 18:53:44 <nirik> but you can see history and such. 18:53:54 <nirik> #topic Open Floor 18:53:59 <nirik> anyone have items for open floor? 18:54:18 <nirik> questions, comments, favorite chocolate? 18:54:22 <bwood09> nirik, also, I mentioned in my welcome email that I'm unemployed, I am planning on devoting my time to this pretty much like a full time job. That's not a bad thing, is it? lol 18:54:24 <smooge> blue 18:54:27 <pingou> nirik: do we have any web-monitor solution in place? 18:54:38 <adimania> how about the slimming advice :P 18:54:43 <pingou> I remember we had awstats but it's not working so much it is? 18:54:53 <nirik> bwood09: :) you're welcome to spend as much time as you like... just don't get burned out. :) 18:55:06 <tflink> threebean: I was waiting on that before making a hotel reservation but I suppose that I could just commute for a day or two. it's only an hour or so 18:55:09 <nirik> pingou: for web logs? or monitoring web pages for alerts? 18:55:17 <bwood09> I'll try not to. I really, really like doing sysadmin work 18:55:17 * pingou wonders if there is an equivalent of piwik in python 18:55:20 <smooge> fedoramagazine is updated 18:55:28 <pingou> nirik: web-logs 18:55:29 <nirik> smooge: cool! :) 18:55:36 <tflink> mirek-hm: where are the playbooks that you're working on? 18:55:36 <smooge> pingou, look for pywik? 18:55:38 <webpigeon> nirik: Galaxy, as it happens. (but cool that nagios lets people login with their FAS creds) 18:55:42 <nirik> pingou: we don't, but it would be good if we did. 18:55:45 <pingou> smooge: does it? :D 18:56:19 <smooge> pingou, maybe pywyk? or pypiwik? [I am just pulling your leg now.] 18:56:21 <pingou> https://github.com/stef/pywik 18:56:34 <mirek-hm> tflink: on my machine, only. But I will push them to github and send link to infra mailing list so you can review if you want, ok? 18:56:53 <nirik> mirek-hm: that would be great. 18:56:59 <threebean> tflink: well, we're all only in town for so long and I know we've got tons of stuff to do.. so I'd vote for "yes, let's plan to hack on June 1st" 18:57:28 <tflink> mirek-hm: yeah, that'd be great 18:57:48 <nirik> threebean: +1 18:57:54 <tflink> threebean: ok, I'll double check to make sure that mike can do the 1st as well 18:58:01 <lmacken> yeah, I'm not sure when people are showing up, but I'm cool with hacking any time :) 18:58:53 * nirik too 18:59:11 <lmacken> let's talk fad logistics in #fedora-apps. we need to figure out what to do other than slay code :) 18:59:15 <nirik> also, we should definitely be active in our usual channels and #fedora-fad during the fad. :) 18:59:49 <nirik> alright, we are out of time. Lets continue over in #fedora-admin, #fedora-apps and #fedora-noc. :) 18:59:53 <nirik> thanks for coming everyone! 18:59:57 <nirik> #endmeeting

1 0

Fedora Cloud Workgroup Meeting Minutes 24 April 2014
by Joe Brockmeier 24 Apr '14

24 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ======================= #fedora-meeting Meeting ======================= Meeting started by jzb at 14:08:17 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-04-24/fedora-meeting.2… . Meeting summary - --------------- * roll call (jzb, 14:08:26) * Meeting tickets (jzb, 14:10:06) * LINK: https://fedorahosted.org/cloud/query?keywords=~meeting&status=!closed (jzb, 14:10:12) * rename cloud spin kickstart to distinguish the cloud base image (jzb, 14:11:14) * https://fedorahosted.org/cloud/ticket/16 (jzb, 14:11:48) * File F22 change: Re-factor cloud-init (jzb, 14:19:24) * https://fedorahosted.org/cloud/ticket/23 (jzb, 14:20:36) * LINK: https://github.com/coreos/coreos-cloudinit (red_trela, 14:26:08) * LINK: https://fedorahosted.org/fedora-infrastructure/ (jzb, 14:27:22) * ACTION: number80 to take lead on Ticket #23 (https://fedorahosted.org/cloud/ticket/23) (jzb, 14:30:52) * Ticket #45 need three packages added to the fedora21 cloud image (jzb, 14:31:28) * ACTION: jzb to follow up on Ticket 45, will herd cats until we come to a conclusion on it. (jzb, 14:49:27) * Project Atomic and Fedora Docker Host Image (jzb, 14:50:03) * LINK: https://fedorahosted.org/cloud/ticket/46 (jzb, 14:50:41) * LINK: https://fedorahosted.org/cloud/ticket/41 (roshi, 15:05:02) * ACTION: roshi to send note to the list for review of his QA draft (jzb, 15:06:59) Meeting ended at 15:14:27 UTC. Action Items - ------------ * number80 to take lead on Ticket #23 (https://fedorahosted.org/cloud/ticket/23) * jzb to follow up on Ticket 45, will herd cats until we come to a conclusion on it. * roshi to send note to the list for review of his QA draft Action Items, by person - ----------------------- * jzb * jzb to follow up on Ticket 45, will herd cats until we come to a conclusion on it. * number80 * number80 to take lead on Ticket #23 (https://fedorahosted.org/cloud/ticket/23) * roshi * roshi to send note to the list for review of his QA draft * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * jzb (101) * red_trela (40) * number80 (36) * mattdm (25) * roshi (22) * frankieonuonga (17) * geppetto (12) * erjohnso (6) * zodbot (4) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTWTuhAAoJEKbW5zOgIHzUYS8IALn7fdfRdqzMGYTJ9F1Euz1X 8Cq4aC5CgaHRwqG/WveU2w4QRUrrQrUOiTyJeZ6FwH3tjk8SNJBlBiy4DcrTk9qn WsYeZIfw2zpziE7hUcKfdjTsH1RiPiaujIE6oys5BPaBiy3JURi2W4CmS7yY7uEL 4YQSZ8/oGE72L1GIioGnoi0uq1qtrCl0FfMsi0dLaRoaNQ5+VEHR+LSWbcTOFx7R 2WFS6hJ9O+cJICdUJCFfzAbVQXvXSNcEHUa6V7y3a2SEfdLXOn4RmprFVpWf3lkq IPlW3h9qcoAlBB4mCjWnWQh7QVmuvsfYXee+CDvW1gnN+lm2Y9T0BTuDJ3IUi5I= =4HvG -----END PGP SIGNATURE-----

1 0

Logs for ROS and RPM packaging IRC workshop #2
by Ankur Sinha 24 Apr '14

24 Apr '14

Hi, We had a quick workshop. We basically just walked through the "how to create a gnu hello world rpm" wiki page. Minutes: http://meetbot.fedoraproject.org/fedora-classroom/2014-04-24/ros-rpm_irc_se… Minutes (text): http://meetbot.fedoraproject.org/fedora-classroom/2014-04-24/ros-rpm_irc_se… Log: http://meetbot.fedoraproject.org/fedora-classroom/2014-04-24/ros-rpm_irc_se… -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG

1 0

[Embajadores-fedora-latam] Fedora Latam Meeting Logs / Registros de la Reunion de Embajadores de Latino america 2014-04-23
by Eduardo Javier Echeverria Alvarado 23 Apr '14

23 Apr '14

Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-04-23/fedora_latam.201… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-04-23/fedora_latam.201… Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-04-23/fedora_latam.201… --

1 0

Summary/Minutes from today's FESCo Meeting (2014-04-23)
by Kevin Fenzi 23 Apr '14

23 Apr '14

=================================== #fedora-meeting: FESCO (2014-04-23) =================================== Meeting started by nirik at 17:00:08 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-04-23/fesco.2014-04-23… . Meeting summary --------------- * init process (nirik, 17:00:08) * #1221 → Product working group activity reports (nirik, 17:04:17) * LINK: https://fedorahosted.org/fesco/ticket/1221 (nirik, 17:04:17) * LINK: https://fedorahosted.org/rel-eng/ticket/5891 (nirik, 17:05:36) * working groups should note on the releng ticket changes they need/desire. (nirik, 17:05:51) * #1250 → F21 Self Contained Changes (nirik, 17:07:59) * LINK: https://fedorahosted.org/fesco/ticket/1250 (nirik, 17:07:59) * LINK: https://fedorahosted.org/fesco/ticket/1250#comment:18 (nirik, 17:08:37) * sgallagh was -1 for the remote journal change and +1 for all the rest (nirik, 17:09:05) * AGREED: all self contained changes proposed this week approved, except remote journal, we will work more with change owners and revisit next week. (+6,0,0) (nirik, 17:22:50) * #1287→ approve directory /opt/fedora (nirik, 17:23:07) * LINK: https://fedorahosted.org/fesco/ticket/1287 (nirik, 17:23:08) * AGREED: This is approved (+6,0,0) (nirik, 17:24:49) * #1288 F21 System Wide Change: Changes/(A)Periodic Updates to (nirik, 17:25:24) * LINK: https://fedorahosted.org/fesco/ticket/1288 (nirik, 17:25:25) * sgallagh was +1 in ticket (nirik, 17:27:04) * AGREED: change approved (+5,-1,0) (nirik, 17:37:55) * ACTION: mattdm to take this back to the cloud wg and ask for the communication with qa, releng, and security to get started _now_ (mattdm, 17:38:13) * #1289 F21 System Wide Change: Playground repository - https://fedoraproject.org/wiki/Changes/Playground_repository· (nirik, 17:38:18) * LINK: https://fedorahosted.org/fesco/ticket/1289 (nirik, 17:38:18) * LINK: https://fedoraproject.org/wiki/Changes/Playground_repository (nirik, 17:38:37) * LINK: https://github.com/akozumpl/dnf-plugins-core/blob/master/plugins/copr.py#L53 (nirik, 17:52:46) * AGREED: : change approved (+6,0,0) (nirik, 18:02:33) * #1290 F21 System Wide Change: Anaconda Support for Server Roles - https://fedoraproject.org/wiki/Changes/AnacondaServerRoleSupport (nirik, 18:02:43) * LINK: https://fedorahosted.org/fesco/ticket/1290 (nirik, 18:02:44) * AGREED: This change is approved. (+7,0,0) (nirik, 18:07:10) * #1291 F21 System Wide Change: BerkeleyDB 6 - https://fedoraproject.org/wiki/Changes/BerkeleyDB_6 (nirik, 18:07:27) * LINK: https://fedorahosted.org/fesco/ticket/1291 (nirik, 18:07:27) * LINK: http://paste.fedoraproject.org/96336/39827674 (nirik, 18:12:47) * AGREED: ask the owner for clarification, and suggest that we need a plan that doesn't result in license violations by ommission (+5,0,0) (nirik, 18:19:42) * ACTION: mitr to talk to change owners about db6 (nirik, 18:20:00) * #1292 F21 System Wide Change: Cockpit Management Console - https://fedoraproject.org/wiki/Changes/CockpitManagementConsole (nirik, 18:20:15) * LINK: https://fedorahosted.org/fesco/ticket/1292 (nirik, 18:20:16) * AGREED: change is approved, but instead of shifting schedule will allow this change to land later if needed. (+7,0,0) (nirik, 18:24:37) * #1293 F21 System Wide Change: Fedora 21 Make 4.0 Update - https://fedoraproject.org/wiki/Changes/F21Make40 (nirik, 18:24:45) * LINK: https://fedorahosted.org/fesco/ticket/1293 (nirik, 18:24:45) * AGREED: Change is approved (+7,0,0) (nirik, 18:26:54) * ACTION: dgilmore will followup about make change and make-devel subpackage needs (nirik, 18:28:00) * #1294 F21 System Wide Change: TCL/TK 8.6 - https://fedoraproject.org/wiki/Changes/f21tcl86 (nirik, 18:28:06) * LINK: https://fedorahosted.org/fesco/ticket/1294 (nirik, 18:28:06) * AGREED: Change is approved (+7,0,0) (nirik, 18:29:39) * #1295 F21 System Wide Change: SCL - https://fedoraproject.org/wiki/Changes/SCL (nirik, 18:29:50) * LINK: https://fedorahosted.org/fesco/ticket/1295 (nirik, 18:29:50) * LINK: https://lists.fedoraproject.org/pipermail/devel/2014-April/198242.html (nirik, 18:35:53) * AGREED: Change is accepted. change owner to update details based on feedback on list and discussion with releng (+6,0,0) (nirik, 18:42:40) * #1296 F21 System Wide Change: Ruby193 in SCL - https://fedoraproject.org/wiki/Changes/Ruby193_in_SCL (nirik, 18:42:55) * LINK: https://fedorahosted.org/fesco/ticket/1296 (nirik, 18:42:55) * AGREED: Change is accepted. (+7,0,0) (nirik, 18:44:15) * #1297 F21 System Wide Change: Workstation: Enable Software Collections - https://fedoraproject.org/wiki/Changes/Workstation_Enable_Software_Collecti… (nirik, 18:45:08) * LINK: https://fedorahosted.org/fesco/ticket/1297 (nirik, 18:45:08) * LINK: https://www.softwarecollections.org/en/docs/quick-start/ (nirik, 18:51:45) * AGREED: ask for clarification, and... particularly, whether the approved change for _in_ Fedora software collections makes this moot (+5,-1,0) (nirik, 18:55:44) * #1298 F21 System Wide Change: The securetty file is empty by default - https://fedoraproject.org/wiki/Changes/securetty_file_is_empty_by_default (nirik, 18:55:47) * LINK: https://fedorahosted.org/fesco/ticket/1298 (nirik, 18:55:47) * ACTION: mattdm to ask for clarification on enable scls for workstation (nirik, 18:56:55) * AGREED: change is rejected (0,-7,0) (nirik, 18:58:02) * AGREED: counterproposal: Remove securetty from default PAM configuration and remove /etc/securetty, and note this in the release notes. (+6,0,0) (nirik, 18:59:52) * ACTION: mattdm to file bugs and talk to docs (nirik, 19:00:03) * #1299 F21 System Wide Change: Smaller Cloud Image Footprint - https://fedoraproject.org/wiki/Changes/Smaller_Cloud_Image_Footprint (nirik, 19:00:12) * LINK: https://fedorahosted.org/fesco/ticket/1299 (nirik, 19:00:12) * AGREED: Change is approved (+7,0,0) (nirik, 19:05:08) * ACTION: mattdm to follow up on networkd with cloud wg (mattdm, 19:05:20) * #1300 F21 System Wide Change: Use license macro in RPMs for packages in Cloud Image - https://fedoraproject.org/wiki/Changes/Use_license_macro_in_RPMs_for_packag… (nirik, 19:05:30) * LINK: https://fedorahosted.org/fesco/ticket/1300 (nirik, 19:05:30) * AGREED: Change is approved (+7,0,0) (nirik, 19:06:52) * #1301 F21 System Wide Change: Workstation: Disable firewall - https://fedoraproject.org/wiki/Changes/Workstation_Disable_Firewall (nirik, 19:08:22) * LINK: https://fedorahosted.org/fesco/ticket/1301 (nirik, 19:08:23) * AGREED: Change is rejected (-5,+2,0) (nirik, 19:21:31) * #1286 New upstream version of dracut inappropriately pushed as stable release update, introduces major regression (nirik, 19:25:57) * LINK: https://fedorahosted.org/fesco/ticket/1286 (nirik, 19:25:58) * AGREED: Fesco agrees this is not ok, needs to be fixed, needs determining what else might be broken, and should not be allowed to happen moving forward. (+6,0,0) (nirik, 19:42:43) * Next week's chair (nirik, 19:42:59) * dgilmore to chair next week (nirik, 19:44:11) * Open Floor (nirik, 19:44:18) Meeting ended at 19:53:58 UTC. Action Items ------------ * mattdm to take this back to the cloud wg and ask for the communication with qa, releng, and security to get started _now_ * mitr to talk to change owners about db6 * dgilmore will followup about make change and make-devel subpackage needs * mattdm to ask for clarification on enable scls for workstation * mattdm to file bugs and talk to docs * mattdm to follow up on networkd with cloud wg Action Items, by person ----------------------- * dgilmore * dgilmore will followup about make change and make-devel subpackage needs * mattdm * mattdm to take this back to the cloud wg and ask for the communication with qa, releng, and security to get started _now_ * mattdm to ask for clarification on enable scls for workstation * mattdm to file bugs and talk to docs * mattdm to follow up on networkd with cloud wg * mitr * mitr to talk to change owners about db6 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (258) * mattdm (115) * mitr (83) * jwb (74) * pjones (63) * dgilmore (62) * notting (52) * t8m (42) * adamw (28) * zodbot (24) * jreznik_q10 (11) * jreznik (8) * twoerner (5) * patsy (1) * smooge (1) * randomuser (1) * sgallagh (0) * abadger1999 (0) * mmaslano (0) -- 17:00:08 <nirik> #startmeeting FESCO (2014-04-23) 17:00:08 <zodbot> Meeting started Wed Apr 23 17:00:08 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:08 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:08 <nirik> #meetingname fesco 17:00:08 <zodbot> The meeting name has been set to 'fesco' 17:00:08 <nirik> #chair abadger1999 dgilmore mattdm mitr notting nirik pjones t8m sgallagh mmaslano jwb 17:00:08 <nirik> #topic init process 17:00:09 <zodbot> Current chairs: abadger1999 dgilmore jwb mattdm mitr mmaslano nirik notting pjones sgallagh t8m 17:00:19 * notting is here 17:00:20 <nirik> who all is around for an exciting fesco meeting? 17:00:21 <t8m> hello 17:00:42 <mitr> Hello 17:00:55 * jreznik is around for fesco but only for limited time today, so hello! 17:01:26 <patsy> hi! 17:01:26 <nirik> we need 1 more for quorum I think. 17:01:40 <pjones> sorry, my other previous just finished, and I'm going to be AFK for 2-3 minutes now. 17:02:29 <jwb> hi 17:02:32 <nirik> no worries. 17:03:58 <pjones> I see nothing happened in my absence 17:04:08 <nirik> it all happened so fast. ;) 17:04:17 <nirik> #topic #1221 → Product working group activity reports 17:04:17 <nirik> .fesco 1221 17:04:17 <nirik> https://fedorahosted.org/fesco/ticket/1221 17:04:20 <zodbot> nirik: #1221 (Product working group activity reports) – FESCo - https://fedorahosted.org/fesco/ticket/1221 17:04:41 <nirik> anything anyone would like to discuss or highlight from working groups this week? 17:05:24 <nirik> I'd like to note that jreznik opened a rel-eng ticket asking working groups to note what releng changes they need/want. 17:05:31 <jreznik> I have only one thing for working groups - deliverables email I sent todya 17:05:36 <nirik> https://fedorahosted.org/rel-eng/ticket/5891 17:05:38 <nirik> yeah. 17:05:47 <jreznik> nirik: you were faster, thanks :) 17:05:51 <nirik> #info working groups should note on the releng ticket changes they need/desire. 17:06:25 <jreznik> and how theirs deliverables would look like aka lives, install iso, images etc. 17:06:26 <nirik> anything else on working groups ? or shall we move on. We have a full changes slate. ;( 17:06:40 <mattdm> sorry, irc client was glitched on this channel. 17:06:42 * mattdm is here now. 17:07:18 <nirik> mattdm: anything to discuss or note from working groups this week? or shall we move on... 17:07:24 <nirik> (aside from whats in the ticket) 17:07:30 <mattdm> nirik nothing other than what's in the ticket. 17:07:36 <nirik> cool 17:07:59 <nirik> #topic #1250 → F21 Self Contained Changes 17:07:59 <nirik> .fesco 1250 17:07:59 <nirik> https://fedorahosted.org/fesco/ticket/1250 17:08:00 <zodbot> nirik: #1250 (F21 Self Contained Changes) – FESCo - https://fedorahosted.org/fesco/ticket/1250 17:08:05 <jreznik> for changes - there are still a few to announce, mostly self contained, trying to get more info or just in backlog as I was out + bank holidays.... but mostly, system wide are reported 17:08:17 <nirik> jreznik: thanks. 17:08:37 <nirik> https://fedorahosted.org/fesco/ticket/1250#comment:18 17:08:41 <nirik> has the list for this week 17:09:05 <nirik> #info sgallagh was -1 for the remote journal change and +1 for all the rest 17:09:31 <t8m> I agree with sgallagh that the remote journal change should be promoted to Systemwide 17:09:35 <mitr> I'm fine with all of them 17:09:57 <mitr> The remote journal change is not actually saying that this is the recommended way to do it or the like 17:10:30 <t8m> mitr, well it can be perceived so because we would be advertising it in relnotes 17:10:30 <nirik> mitr: true, but saying it's a 'change' means more people will try and use it 17:10:32 <mattdm> I'm fine with all of them too. We can ask the journal change to include the clarification that it is one of several possible approaches 17:10:34 <pjones> I wish we'd rename "Adopt Your Cattle" to something descriptive. 17:11:01 <nirik> "fedora server in the cloud" ? 17:11:12 <mitr> t8m, nirik: true. We can clarify, e.g. saying that Server has chosen to keep recommending rsyslog perhaps? 17:11:21 <mattdm> pjones, nirik: that's fine with me, although I would enjoy keeping the fun name in there somewhere as well 17:11:30 <mattdm> (does it really matter?) 17:11:43 <mitr> t8m, nirik: though that would be a different conversation to have I think 17:11:47 <jwb> mattdm, for documentation purposes, yes 17:11:53 <pjones> (does it matter that it's hard to look at it and tell what it's about? Are you serious?) 17:12:10 <jwb> the current name is cute and fun if you know wtf it's talking about. otherwise it's really confusing 17:12:17 <t8m> pjones, +1 17:12:24 <jwb> maybe it's a feature about Cowsay! 17:12:33 <mattdm> I mean, does the name used in the change directly translate to the words used in user-facin documentation? 17:12:34 <pjones> jwb: I was really hoping it was :) 17:12:34 <nirik> all hail cowsay! 17:12:45 * mattdm would love a new feature about cowsay. that thing isn't unicode compliant 17:12:57 <jwb> mattdm, says the guy that repeatedly argued with me about PRDs and media impacts... 17:13:09 <jwb> mattdm, so yeah, the name of the change should be descriptive 17:13:16 <jwb> because people look at the change list 17:13:23 <jwb> not the change pages, just the list 17:13:29 <mattdm> Okay, I'm swayed -- I can rename it 17:13:41 <jwb> and then they write "here are the features in the upcoming fedora release" 17:13:46 <jwb> *splat* 17:14:07 <mattdm> although I think that _for the certain segment where it has instant meaning_, it's more interesting/exciting 17:14:19 * mattdm goes and edits now 17:14:27 <pjones> anyway, didn't mean to completely derail this 17:14:54 * jreznik asked sgallagh_afk if adopt catle is what they want, mattdm wasn't online :D 17:15:10 <nirik> so, I'm +1 to all of them except the remote journal... on that one I really hope we can convince them to change the implementation...but I guess we could adjust the change if so... 17:15:56 <notting> nirik: is your concern the usage of http, or something else? 17:16:50 <nirik> http and ssl certs and two ssl libraries. ;( 17:17:07 <t8m> I actually have no problem with the implementation - the use of https is convenient for some environments. It just shouldn't be advertised as "The preferred way for remote journal" 17:17:36 <t8m> advertised and/or perceived 17:18:42 <notting> ... well, if it's the only implemented way, it's preferred by default 17:18:59 <nirik> so, in the interests of moving on to the other pile of changes... proposal: all self contained changes proposed this week approved, except remote journal, we will work more with change owners and revisit next week. 17:19:00 <mitr> I'm generally unhappy with the whole area, the reinventing and reimplementing and rediscovering the data loss problems, but that's not solving anything; the best I can do is suggest changes to the implementation. 17:20:37 * nirik listens to crickets. Other proposals? 17:20:42 <mitr> nirik: +1, if you take the action to raise specific concerns :) 17:21:03 <t8m> nirik, +1 17:21:06 <pjones> nirik: +1 17:21:08 <mattdm> nirik: +1 17:21:22 <mitr> (Reading the mailing list thread I didn't see much indication this was going to be proposed to be deferred :/) 17:21:35 <nirik> well, it sounds like we have 2: 1) still some questions about protocol... is this going to be the final setup? 2) is this change just to say 'here it is, try it if you want' and not 'this is the default method of doing remote syslogs in fedora 21 17:22:13 <mitr> notting: for the record, rsyslog can AFAIK transport journal in full, modulo record length limits 17:22:26 <nirik> #agreed all self contained changes proposed this week approved, except remote journal, we will work more with change owners and revisit next week. (+5,0,0) 17:22:36 <notting> nirik: +1 17:22:38 <nirik> I'll try and raise those concerns, please do raise any I miss 17:22:46 <nirik> #undo 17:22:46 <zodbot> Removing item from minutes: AGREED by nirik at 17:22:26 : all self contained changes proposed this week approved, except remote journal, we will work more with change owners and revisit next week. (+5,0,0) 17:22:50 <nirik> #agreed all self contained changes proposed this week approved, except remote journal, we will work more with change owners and revisit next week. (+6,0,0) 17:23:07 <nirik> #topic #1287→ approve directory /opt/fedora 17:23:08 <nirik> .fesco 1287 17:23:08 <nirik> https://fedorahosted.org/fesco/ticket/1287 17:23:09 <zodbot> nirik: #1287 (approve directory /opt/fedora) – FESCo - https://fedorahosted.org/fesco/ticket/1287 17:24:00 <nirik> so, I guess this is just a rubber stamp to apply for a name for scls to use? 17:24:14 * notting is +1 17:24:19 <t8m> +1 17:24:19 <pjones> +1 17:24:23 <mattdm> +1 17:24:26 <nirik> +1 17:24:27 <mitr> It's kind of curious that it isn't through the FPC, but whatever, +1 17:24:27 <pjones> nirik: yeah, looks that way 17:24:49 <nirik> #agreed This is approved (+6,0,0) 17:25:24 <nirik> #topic #1288 F21 System Wide Change: Changes/(A)Periodic Updates to 17:25:24 <nirik> Images - https://fedoraproject.org/wiki/Changes/%28A%29Periodic_Updates_to_Images· 17:25:25 <nirik> .fesco 1288· 17:25:25 <nirik> https://fedorahosted.org/fesco/ticket/1288 17:25:26 <zodbot> nirik: Error: '1288\xc2\xb7' is not a valid integer. 17:25:36 <nirik> nice. ;) 17:26:16 <jwb> i think someone asked the title be changed to reflect it was for cloud images 17:26:19 <mattdm> this obviously is a declaration of intent to do a lot of actual work, including writing policies -- none of which is done 17:26:28 <mattdm> jwb yes that is fair 17:26:33 * mattdm edits more titles 17:27:04 <nirik> #info sgallagh was +1 in ticket 17:27:14 <mattdm> These titles all came directly from the Cloud SIG todo list, where they were in context. They're now out of that context.... 17:27:43 <pjones> right 17:27:52 * nirik is +1 we will see if we can tool up for it. ;) 17:28:23 <mitr> +1 17:28:29 <pjones> I'm not against this, but rel-eng really needs to weigh in heavily 17:28:45 <nirik> I think (as I noted on the list) we need to be clear what we will do updated images for. 17:28:53 <jwb> pjones, and QA? 17:28:54 <pjones> nirik: fair 17:28:57 <pjones> jwb: yes 17:29:04 <t8m> +1 with hope we will be able to do this as it is highly useful 17:29:28 <pjones> So I'm actually -1 until that input has happened 17:29:36 <mattdm> jwb/pjones yes, definitely want input/help from those groups. Planning to feed contributions/effort *back* to those groups as needed 17:30:09 <mattdm> and nirik, pjones -- making those policies is item #1 in the "detailed description". (In collaboration with Fedora Security) 17:30:20 <jreznik> jwb: I pinged adamw with this change 17:30:30 <adamw> ahoy 17:30:35 <nirik> sure. 17:31:01 <adamw> gah, sorry, didn't really get to taking a look atit 17:31:07 <notting> i'm not against the idea of the change. still seems a little nebulous in implementation. so i guess +1, with the caveat that it seems like a good chance of yanking later if it can't be done, or agreed upon how 17:31:21 <mattdm> right now, we're doing these things as fire drills. I'd like to get out of that. 17:31:24 <nirik> right. if it doesn't come together we can drop it. 17:31:40 <nirik> well, fire drill, singular. ;) 17:31:53 <adamw> hey, we did respin like one time before...ever... 17:31:55 <adamw> :P 17:31:59 <mattdm> nirik We've done it twice so far -- once for heartbleed, once for root password 17:32:15 <nirik> oh yeah, forgot about that one, so ok. 2 times. 17:32:29 <adamw> ok, as a handwave, i'd be ok with 'yes but...', can't speak for the rest of QA as I don't think it was run by test@, sorry :( 17:32:32 <nirik> oh, to clarify, would these be just the security updates? or all updates at the time? 17:32:38 <jwb> mattdm, there's really nothing in terms of content in the Change. 17:32:41 <jwb> nirik, right 17:32:42 <notting> almost as much fun as respinning install dvds & the install image inside them 17:33:21 * jreznik is moving to his smartphone (but with hw keyboard, don't worry!) 17:33:31 <jwb> nirik, the detailed description seems to imply "all updates" 17:33:42 <jwb> i mean... why else would you do them monthly? 17:33:44 * nirik nods. 17:33:54 <adamw> cloud validation as it stands isn't really a lot of work (there's no installer and no desktop, which helps a lot) so i don't think it'd be too impossible from a quality perspective, but we would need someone to really commit to testing each of these images as it comes out, or automate it properly. 17:33:58 <mattdm> jwb yes, the intention was for the monthly updates to include everything. 17:34:07 <mattdm> adamw *nod* 17:34:10 <pjones> yeah, and all updates is really the only sensible policy. 17:34:29 <mattdm> Right now, when we _have_ done the updates, I've lived in fear of a brown paper bag moment after 17:34:30 <nirik> so, where are we on votes... +4, -1? 17:34:48 <mattdm> uh, I am +1 17:34:49 <nirik> like the f20 respun lives? ;) 17:35:01 <adamw> the cloud quality requirements are a reasonable target for automation, but i'm not sure it could get Done in time for this change to kick in, so we'd need to cover at least the possibility of it requiring manual testing for a while. 17:35:37 * pjones wonders where dgilmore is 17:35:54 <adamw> the testing requirements should definitely be covered in the Change page somewhere. 17:36:25 <nirik> ok, so +5, -1... unless pjones wants to change? 17:36:27 <adamw> (it's kinda mentioned atm, but more as 'we need to document this' than...actually documenting it.) 17:36:56 <nirik> and notting hasn't voted I think... 17:37:03 <pjones> nirik: I'd still rather hear from rel-eng before I vote yes. As you've already got 5, I'm willing to stay -1 on that basis, especially since it won't hold it back anyway. 17:37:15 <nirik> sure, fair enough. 17:37:23 <mattdm> I can take this back to the cloud wg and ask for the communication with qa, releng, and security to get started _now_ 17:37:32 <pjones> mattdm: that would be good. 17:37:55 <nirik> #agreed change approved (+5,-1,0) 17:38:13 <mattdm> #action mattdm to take this back to the cloud wg and ask for the communication with qa, releng, and security to get started _now_ 17:38:18 <nirik> #topic #1289 F21 System Wide Change: Playground repository - https://fedoraproject.org/wiki/Changes/Playground_repository· 17:38:18 <nirik> .fesco 1289· 17:38:18 <nirik> https://fedorahosted.org/fesco/ticket/1289 17:38:18 <zodbot> nirik: Error: '1289\xc2\xb7' is not a valid integer. 17:38:31 <nirik> picky picky 17:38:37 <nirik> https://fedoraproject.org/wiki/Changes/Playground_repository 17:39:52 <pjones> What's with the trailing elevated dot? 17:40:18 <nirik> thats my fault. 17:40:37 * nirik has vim show trailing spaces that way. 17:40:42 <pjones> aah 17:40:46 <notting> were people's concerns addressed in the additional week of discussion? 17:41:50 <nirik> some of mine were, it still seems a bit handwavy tho 17:42:01 <dgilmore> sorry I had an appointment this morninga nd it went late 17:42:09 * dgilmore is here now 17:43:21 <nirik> I guess I am a weak +1 on it now... and we can see how it works out. 17:43:24 <mattdm> I'm +1 to this. Although I hope it can grow into a 'real' repository in future releases. 17:43:26 <jreznik_q10> well, it was discussed several times on env and stacks meetings, it's mostly effortless way how to have something now as Beta and see how it's really being used 17:43:31 <jreznik_q10> that's the idea 17:43:33 <mitr> I can't see any outstanding questions; the plan is somewhat curious but AFAICT fairly definite 17:43:35 <mitr> +1 17:43:35 <jwb> mattdm, huh? 17:43:59 <nirik> yeah, I am curious to see how many things will actually be in it... 17:44:13 <t8m> +1 from me as well we will see how it will be used 17:44:17 <dgilmore> im not oppsed but there is a lot of implementation details not yet available 17:44:18 <nirik> I'm not sure the demand is as high as people think 17:44:21 <jreznik_q10> mattdm, yes, that's the plan - one day full repository 17:44:25 <mattdm> jwb right now, it's implemented as a DNF plugin that pulls together Coprs. 17:44:34 <jwb> mattdm, yes 17:44:44 <jwb> so what do you mean by "real"? 17:45:08 <notting> do we have any stats as to who is currently using coprs for 'stuff not able to be put in fedora due to assorted pkging rules' vs 'newer test versions of existing stuff'? 17:45:14 <jreznik_q10> it's not repository but more set of repositories, real means one standalone repository with all implications it means 17:45:23 <mattdm> as jreznik says, a "full" repository that's mirrored and everything. 17:45:44 <mattdm> but that's kind of a separate discussion and I don't want to hold up the meeting with it.... 17:45:52 <jwb> mattdm, jreznik_q10: would it's repo file be shipped in fedora-release and sit alongside e.g. the updates-testing repo? 17:45:57 <nirik> notting: not that I know of, we might be able to mine some tho 17:46:01 <jwb> because... i'm pretty sure i would dislike that 17:46:15 <jwb> if you just want someone to go and run createrepo on it, fine whatever 17:46:21 <jreznik_q10> jwb, not now, it's just Dnf plugin 17:46:26 <nirik> notting: I'd guess a lot of use is 'newer version' (which this doesn't address) 17:46:32 <jwb> jreznik_q10, yes, i got that. i'm asking about your and mattdm's desires 17:46:56 <mitr> jwb: AFAICT this is always going to be optional (and I would insist on that) 17:47:01 * pjones can be +1 here 17:47:13 <jwb> mitr, that doesn't answer my question. updates-testing is optional too 17:47:17 <jreznik_q10> jwb, well I still prefer this lightweight version for interested folks, future is currently not yet set 17:47:32 <dgilmore> mattdm: so we will need to setup releng processes around it 17:47:39 <mitr> jwb: sorry, I missed the -testing part 17:47:59 <nirik> we are at +5 17:48:05 <mattdm> jwb, I *would* like to see it something like updates-testing. But that's really a discussion for the future. Willing to be wrong on that, and still in favor of this. :) 17:48:13 <jreznik_q10> idea is to try something really lightweight and maybe nirik is true and there's no interest 17:48:23 <notting> jreznik_q10: by 'dnf plugin', that means the plugin is configured/coded out of the box to know where the list of approved coprs is, etc? i.e., it's essentially shipping a repo definition that may or may not be considered third party 17:48:26 <nirik> dgilmore: well, there isn't any I guess... it's all really just in copr... a collection of existing coprs 17:48:46 <jwb> mattdm, ooof. well, with that in mind it certainly gives me pause in my potential inclusion of things in it. 17:48:54 <jwb> so i'll have to think about it. 17:49:42 <jreznik_q10> notting, as far as I know, it's optional plugin now 17:50:01 <notting> jreznik_q10: that... didn't respond to my questin 17:50:04 <dgilmore> nirik: but if they want it mirrored then we need to setup some way to mirror it 17:50:05 <nirik> notting: yeah, it would know about the playground collection... right now it knows about copr... 17:50:21 <mitr> jwb: What are you concerned/thinking about? You've mentioned some things you dislike, but not why 17:50:22 <nirik> dgilmore: no mirroring proposed in this change. 17:50:44 <dgilmore> nirik: 17:45 < mattdm> as jreznik says, a "full" repository that's mirrored and everything. 17:50:48 <dgilmore> nirik: was going on that 17:50:58 <jreznik_q10> notting, I hope definition of repos is not shipped with that plugin 17:51:00 <nirik> notting: but users have to enable... http://dnf.baseurl.org/2014/03/19/copr-plugin/ 17:51:25 <nirik> dgilmore: that is not this change, but some indeterminate future that some people desire. ;) 17:51:42 <nirik> if we move to that then yes, lots more releng work. 17:51:44 <notting> jreznik_q10: then how does it know what's part of the playground repo if it's not configured to go to the playground repo? 17:52:30 * notting can't shake the idea that we keep piecemeal talking about having a playground repo, having coprs, setting some rules on third-party software, discussing the web apps thing, and yet don't actually have a plan on where we expect to end up 17:52:40 <jwb> mitr, i'm concerned about support implications of it being shipped as a mirrored and official optional repo 17:52:46 <nirik> https://github.com/akozumpl/dnf-plugins-core/blob/master/plugins/copr.py#L53 17:52:48 <jreznik_q10> it's defined on copr side, plugin just knows who to talk but I really don't have these details, msuchy gave some details in his mail 17:53:06 <nirik> ^ code of plugin 17:53:21 <mitr> jwb: I haven't seen big support implications of shipping updates-testing, so I don't expect much more with this... 17:53:37 <nirik> it warns and asks and downloads the repo file from copr.fedoraproject.org 17:53:46 <jwb> mitr, updates-testing is imminently destined for updates. playground is almost exactly the opposite 17:53:51 <dgilmore> nirik: okay 17:54:01 <jreznik_q10> jwb, and that's why this change for beta is really minimalistic - begin with something that's achievable 17:54:01 <mattdm> jwb you mean if someone installs something from this, forgets that they did, and then files bug reports or otherwise asks for help? 17:54:01 <nirik> mitr: we did have problems with rawhide tho. ;) 17:54:03 <mitr> notting: AFAICT the big theme is "avoid overhead of too prescriptive packaging guidelines and review process" 17:54:15 <jwb> mattdm, that, and even why would we ask the mirrors to mirror a repo of stuff that is explicitly unsupported? 17:54:21 <mattdm> I know that env-and-stacks *did* talk about that to some degree 17:54:35 <mattdm> jwb mirrors mirror all kinds of stuff -- contrib trees and whatnot. 17:54:54 <smooge> mattdm, only a very very few these days. 17:55:06 <jwb> mattdm, for lack of a better analogy, the playground repo is almost equivalent to the staging stuff in the kernel. it's crap, we know it's crap, it needs work to not be crap. 17:55:19 <jwb> why include a pointer to crap in fedora-release and ask the mirrors to ship it? 17:55:20 <nirik> do we need to discuss long term plans? (ie, does that matter to approval of this feature?) 17:55:35 <jwb> nirik, no. i just said those desires gave me pause. they asked me why. 17:55:37 <notting> mitr: ... which is orienting the software installation experience given to users on axes of how it affects packagers 17:55:41 <dgilmore> nirik: i think we need to know where it is headed 17:55:43 <jwb> i'm perfectly happy not talking about it 17:55:48 <mitr> notting: A really general plan for packaging, or for what Workstation will end up doing for developers, would be interesting, yes; but with Docker and Atomic and DNF at the same time I'm not sure that any one person can even see the full picture right now 17:55:49 <notting> mitr: that seems the wrong way to go 17:56:22 <mattdm> jwb to be clear, I'm happy to talk about it sometime _later_ :) 17:56:34 * jwb shrugs 17:57:08 <jwb> i had some plans. i might not execute on those depending on what people's end-game is for playground. we can talk about that when/whereever 17:57:36 <nirik> well, to my mind, this change would be a way to see if it's even worth doing... and if people want to make it more of a thing, I'd probibly want to discuss that after I see how popular this thing is. 17:57:37 <mitr> notting: I think this is kind of bifurcating the "mere user" case (default repos), and "ubercool software developer with entirely new in-flux ecosystems" case (now they can live within the Fedora ecosystem, by only one more command) 17:58:09 <jwb> nirik, unless the dnf plugin is tracking hits to playground, you aren't going to know it's popularity 17:58:18 <mattdm> nirik +1 17:58:30 <nirik> jwb: true. I wonder if we could ask for some stats as part of this. 17:58:39 <mitr> jwb: that could be tracked server-side (especially now that it isn't mirrored everywhere) 17:58:41 <nirik> althought we would see get anecdotes. 17:58:48 <nirik> still 17:58:59 <jwb> mitr, or that, sure 17:59:14 <nirik> right, it's one instance for frontend and 1 for backend with packages 17:59:21 * mattdm would love to see more stats for more things in general 17:59:30 <notting> mitr: one? with scls in copr, scls maybe in main, docker indicies, openshift cartridges... 17:59:47 <mitr> notting: true 18:00:06 <nirik> anyhow, I think we are at +5, so it's approved? or would anyone who hasn't voted like to vote? or anyone want to change their existing vote? 18:00:25 <notting> nirik: i can be +1 on your logic of 'try something, see how and if it sticks' 18:00:26 * nirik will suggest stats 18:01:32 <nirik> ok. 18:01:38 <nirik> dgilmore: ? 18:02:33 <nirik> #agreed: change approved (+6,0,0) 18:02:43 <nirik> #topic #1290 F21 System Wide Change: Anaconda Support for Server Roles - https://fedoraproject.org/wiki/Changes/AnacondaServerRoleSupport 18:02:43 <nirik> .fesco 1290 18:02:44 <nirik> https://fedorahosted.org/fesco/ticket/1290 18:02:45 <zodbot> nirik: #1290 (F21 System Wide Change: Anaconda Support for Server Roles - https://fedoraproject.org/wiki/Changes/AnacondaServerRoleSupport) – FESCo - https://fedorahosted.org/fesco/ticket/1290 18:02:59 <dgilmore> im not yet decided 18:03:24 <dgilmore> nirik: scls cant be done as coprs 18:04:01 <nirik> dgilmore: hum? 18:04:13 <dgilmore> nirik: I brought it up on the list 18:04:36 <nirik> ok. I'm not sure I follow, but will read up on list. ;) 18:04:57 <mitr> +1 18:05:12 <dgilmore> i am +1 to Anaconda Server Role Support 18:05:15 <nirik> +1 to this change 18:05:39 <pjones> I mean, +1 to them developing all the plugins they like... 18:05:53 <t8m> +1 18:06:32 <notting> i do like the idea of starting with kickstart, so +1. 18:06:43 <nirik> #agreed This change is approved. (+6,0,0) 18:06:59 <mattdm> (um, +1) 18:07:06 <mattdm> (sorry, cat emergency.) 18:07:06 <nirik> #undo 18:07:06 <zodbot> Removing item from minutes: AGREED by nirik at 18:06:43 : This change is approved. (+6,0,0) 18:07:07 <notting> a little nervous of the 'anaconda has plugins! everyone write plugins to change anaconda!' aspect, rather than perhaps considering whether the core can be changed 18:07:10 <nirik> #agreed This change is approved. (+7,0,0) 18:07:27 <nirik> #topic #1291 F21 System Wide Change: BerkeleyDB 6 - https://fedoraproject.org/wiki/Changes/BerkeleyDB_6 18:07:27 <nirik> .fesco 1291 18:07:27 <nirik> https://fedorahosted.org/fesco/ticket/1291 18:07:28 <zodbot> nirik: #1291 (F21 System Wide Change: BerkeleyDB 6 - https://fedoraproject.org/wiki/Changes/BerkeleyDB_6) – FESCo - https://fedorahosted.org/fesco/ticket/1291 18:07:33 <mattdm> notting isn't this exactly _why_ anaconda has plugins? 18:08:03 <notting> mattdm: in the sense that it's only useful for one product? perhaps. 18:08:27 <nirik> I'm +1 to this change, but the license thing is sad. :) 18:08:30 <notting> re: bdb 6. '+ugh' 18:08:56 <mattdm> notting yeah. and for adding easily separable separate config. anyway, next thing. 18:09:03 <mitr> +1 18:09:07 <dgilmore> im with notting here 18:09:13 <mattdm> +1 to the change -- a) no real choice, b) old version is preserved 18:09:18 <dgilmore> +1 18:09:56 <notting> is there a provenpackager signed up to do the work determining whether packages can migrate, and patching those that can/can't? 18:10:01 <notting> (preferably, before mass rebuild) 18:10:54 <nirik> notting: not that I can see... the change owners are just signed up to make the compat package, update, etc... 18:11:16 <nirik> how many packages are we looking at? 18:11:19 * nirik hits repoquery 18:12:01 <nirik> the repoquery in the change page is not right. ;) 18:12:10 <mitr> Provenpackagers helping certainly doesn't hurt, still, I'd expect this is something that the individual package owners both can do, and can do fairly efficiently 18:12:13 <t8m> +1 although I am concerned about the work needed for license compatibility checking of dependencies as well 18:12:29 <nirik> 67 packages 18:12:42 <pjones> +1 with the ugh caveat 18:12:47 <nirik> http://paste.fedoraproject.org/96336/39827674 18:13:00 <t8m> mitr, yes, they can do but there is nothing to force them to do it actually 18:13:14 <nirik> so, one gotcha here... 18:13:25 <mitr> t8m: I'm not entirely sure that packages staring at v5 is a bad thing 18:13:33 <nirik> the new one with the new license will be default right? so a simple rebuild will get the new one with no other action? 18:13:56 <notting> mitr: my concern is it requires an *active* decision on the part of 60+ packages 18:14:15 <nirik> right, someone may not notice, rebuild for something else and get the new one. 18:14:34 <mitr> ah, right; v5 will be the "new" one. 18:15:12 <dgilmore> someone will have to sit down and work out what can link to the new one and make some change so that it uses it 18:15:13 <notting> nirik: if that's going to happen, -1. not really liking the idea of automatic license breaking OOTB. 18:15:32 <nirik> I'm not sure if thats the case, but it seems like. 18:17:22 <mitr> propoal: ask the owner for clarification, and suggest that we need a plan that doesn't result in license violations by ommission 18:17:31 <nirik> +1 18:17:51 <dgilmore> mitr: +1 18:18:17 <notting> mitr: +1. i.e., something like 'unmodified package continues to use old version' would be simple enough for me 18:18:29 <t8m> mitr, +1 18:18:41 <mitr> notting: yes, or a provenpackager signing up 18:18:56 <mattdm> +1 mitr 18:19:12 <nirik> ok, thats +5... who wants an action item to do that for us? ;) 18:19:41 <mitr> I can send that mail right now 18:19:42 <nirik> #agreed ask the owner for clarification, and suggest that we need a plan that doesn't result in license violations by ommission (+5,0,0) 18:20:00 <nirik> #action mitr to talk to change owners about db6 18:20:02 <nirik> thanks mitr 18:20:15 <nirik> #topic #1292 F21 System Wide Change: Cockpit Management Console - https://fedoraproject.org/wiki/Changes/CockpitManagementConsole 18:20:16 <nirik> .fesco 1292 18:20:16 <nirik> https://fedorahosted.org/fesco/ticket/1292 18:20:17 <zodbot> nirik: #1292 (F21 System Wide Change: Cockpit Management Console - https://fedoraproject.org/wiki/Changes/CockpitManagementConsole) – FESCo - https://fedorahosted.org/fesco/ticket/1292 18:20:28 <mitr> +1 18:20:47 <t8m> +1 18:20:57 <mattdm> is the system wide aspect here simply the timeline delay request? 18:21:14 <nirik> not sure. 18:21:15 <nirik> +1 18:21:33 <nirik> I'm fine with just allowing them to land later if they need to... instead of moving the entire schedule 18:21:42 <mattdm> because I'm for the feature in general, but want to be clear on whether we are voiting to bump the schedule by 2-4 weeks 18:21:49 <notting> proposal: allow this feature to land later, as opposed to shifting schedule 18:21:55 <nirik> notting: +1 18:21:56 <pjones> +1 18:22:01 <dgilmore> +1 18:22:05 <mattdm> notting +1 18:22:08 <pjones> (that was to notting) 18:22:18 <t8m> notting, +1 18:22:22 <mitr> notting: +1 18:23:01 <notting> actually, anyone disagree with rewording that as 'approve feature, but allow this feature ...'? 18:23:06 <nirik> ok, sounds like +6 to accepting the change and allowing it to land later... 18:23:38 <pjones> no, that's fine 18:23:56 <dgilmore> nirik: i think notting agrees so +7 18:23:58 <nirik> proposed #agreed change is approved, but instead of shifting schedule will allow this change to land later if needed. 18:24:15 <notting> (and please holler if they can't work with that) 18:24:23 <nirik> dgilmore: yeah. 18:24:37 <nirik> #agreed change is approved, but instead of shifting schedule will allow this change to land later if needed. (+7,0,0) 18:24:45 <nirik> #topic #1293 F21 System Wide Change: Fedora 21 Make 4.0 Update - https://fedoraproject.org/wiki/Changes/F21Make40 18:24:45 <nirik> .fesco 1293 18:24:45 <nirik> https://fedorahosted.org/fesco/ticket/1293 18:24:46 <zodbot> nirik: #1293 (F21 System Wide Change: Fedora 21 Make 4.0 Update - https://fedoraproject.org/wiki/Changes/F21Make40) – FESCo - https://fedorahosted.org/fesco/ticket/1293 18:24:56 <mitr> +1 18:25:01 <nirik> +1 18:25:21 <notting> +1 18:25:34 <t8m> +1 18:25:34 * mattdm had trouble reading that verb 18:26:02 <mattdm> If we're gonna be asking people to reword titles for clarity to less-technical journalists.... 18:26:07 <mattdm> +1 in any case 18:26:08 <pjones> +1 18:26:17 <dgilmore> +1 though im not sure what Releng is to do with the new make-devel sub-package 18:26:54 <nirik> #agreed Change is approved (+7,0,0) 18:27:04 <dgilmore> its not a huge deal and will be sorted however needed 18:27:05 <nirik> dgilmore: I guess it makes make multilib? 18:27:25 <dgilmore> nirik: or does it need to be included in the minimal buildroot 18:27:39 <nirik> dunno. Could you followup on list about that? 18:27:46 <dgilmore> yeah 18:28:00 <nirik> #action dgilmore will followup about make change and make-devel subpackage needs 18:28:02 <nirik> thanks 18:28:06 <nirik> #topic #1294 F21 System Wide Change: TCL/TK 8.6 - https://fedoraproject.org/wiki/Changes/f21tcl86 18:28:06 <nirik> .fesco 1294 18:28:06 <nirik> https://fedorahosted.org/fesco/ticket/1294 18:28:07 <zodbot> nirik: #1294 (F21 System Wide Change: TCL/TK 8.6 - https://fedoraproject.org/wiki/Changes/f21tcl86) – FESCo - https://fedorahosted.org/fesco/ticket/1294 18:28:09 <mitr> dgilmore: very unlikely to be needed in minimal; "gnumake.h", what would need it? 18:28:37 <mitr> +1 18:28:41 <nirik> +1 18:28:48 <t8m> +1 18:29:02 <notting> +1 18:29:12 <mattdm> +1 18:29:16 <pjones> I'd always rather remove them but that's not what we do so +1 18:29:22 <dgilmore> +1 18:29:39 <nirik> #agreed Change is approved (+7,0,0) 18:29:46 <dgilmore> mitr: no idea, email sent asking what releng is supposed to actually do 18:29:50 <nirik> #topic #1295 F21 System Wide Change: SCL - https://fedoraproject.org/wiki/Changes/SCL 18:29:50 <nirik> .fesco 1295 18:29:50 <nirik> https://fedorahosted.org/fesco/ticket/1295 18:29:51 <zodbot> nirik: #1295 (F21 System Wide Change: SCL - https://fedoraproject.org/wiki/Changes/SCL) – FESCo - https://fedorahosted.org/fesco/ticket/1295 18:30:25 <dgilmore> as they want this shipped in the main repos we have to build in koji 18:30:38 <dgilmore> so we will need to work out the workflows 18:30:46 <mattdm> dgilmore yeah, I see that it says "3. Build SCL in koji or magically add SCL builds from Copr (depends on preference of releng) " 18:30:51 <mattdm> and I know your preference :) 18:31:05 <dgilmore> I did bring it up on the list 18:31:43 <dgilmore> but other than working out the workflows and how to build in koji. I'm okay with it 18:31:55 <dgilmore> they will need to have packaging guidelines also 18:31:58 <mattdm> I didn't get a chance to comment on the list, but I'd like to see a timeline for the playground->main plan 18:32:01 <mattdm> "'d like to add it into Playground repo. If everything goes well, I'd like to add it into main Fedora repository." 18:32:31 <dgilmore> mattdm: well they want ruby 1.93 in f21 18:32:40 <mattdm> when do we decide if everything goes well? presumably we need everything for that by alpha? 18:32:40 <nirik> we will also need to finalize the git setup 18:32:48 <dgilmore> mattdm: so i think its safe to assume it will eb skipping playground 18:33:09 <dgilmore> we will need it all in place by branching I think 18:33:45 <mattdm> proposal: ask for detailed description to be updated assuming building straight into the main repo with koji 18:33:57 <dgilmore> +1 18:34:17 <mattdm> nirik can you summarize the git setup issues in ... one or two lines of IRC? 18:35:17 <nirik> mattdm: it was brought up on list. Change owner just wants to use the existing git repos... ie 'ruby' would build both real ruby and the scl ruby. But it means a ton of junk in the package spec... counter proposal was seperate git repos for them... scl-ruby193 or whatever. 18:35:53 <nirik> https://lists.fedoraproject.org/pipermail/devel/2014-April/198242.html 18:35:54 <mattdm> the separate git repos also means building in koji is easier, right? 18:36:18 <dgilmore> mattdm: doesnt make much difference 18:36:18 <nirik> I'm not sure. I don't know how building scls in koji works (I think it does tho) 18:36:35 <pjones> eh, I like separate repos more, but I know some will disagree 18:36:36 <dgilmore> mattdm: all in one they have to do fedpkg build --target=sct-target 18:36:49 <dgilmore> seperate branches they do fedpkg build 18:36:51 <pjones> to me the spec file becomes unmaintainable once you start having so many conditionals 18:37:02 <notting> i'm not sure why i should care one way or another? 18:37:06 <dgilmore> I personally prefer seperate branches 18:37:06 <mattdm> okay. so... I guess I don't care. 18:37:26 <mattdm> I think that the decision weight should go to whoever is maintaining those spec files 18:37:28 <nirik> with seperate branches could someone bypass review? 18:37:45 <dgilmore> mattdm: well the easiest way for it to work is kinda a mix 18:38:08 <dgilmore> have separate beanches for say ruby 18:38:21 <dgilmore> but use a common branch for the ruby modules 18:38:40 <dgilmore> but that makes it ugly to get the sources 18:38:57 <dgilmore> as its not consistent how you get the sources from git 18:39:17 <nirik> proposal: defer a week, ask change owner to update based on feedback on list and discuss with releng how best to implement and what timeline might be? 18:40:13 <mattdm> +1, but maybe also note that we are generally in favor and just working out the details? 18:40:34 <nirik> sure, counter proposal? ;) 18:40:46 <t8m> nirik, +1 with mattdm's addition 18:40:47 <notting> meh. we approved 1288 with less detail on implementation 18:41:03 <mattdm> how about.... 18:41:22 <nirik> well, toshio will also be back next week, and he's dug into things a lot more than I on this, so it would be nice to have his feedback 18:41:23 <mattdm> proposal: accept change, ask change owner to update details based on feedback on list and discussion with releng 18:41:29 <dgilmore> Im okay with approving it today, its going to take some work to get the details sorted. it will make its deadline or not 18:41:37 <dgilmore> mattdm: +1 18:41:38 <mitr> nirik: note thet there has been very little specific feedback on the list, there's... very little to update based on what's now there 18:41:45 <pjones> mattdm: +1 18:41:51 <nirik> alright. 18:41:53 <notting> mattdm: +1 18:42:14 <mitr> mattdm: +1 18:42:25 <mattdm> mitr Well, there's important notes from dgilmore (eg. should work in koji, so let's go straight to that) 18:42:29 <t8m> mattdm, ₊ 18:42:33 <t8m> mattdm, +1 18:42:40 <nirik> #agreed Change is accepted. change owner to update details based on feedback on list and discussion with releng (+6,0,0) 18:42:55 <nirik> #topic #1296 F21 System Wide Change: Ruby193 in SCL - https://fedoraproject.org/wiki/Changes/Ruby193_in_SCL 18:42:55 <nirik> .fesco 1296 18:42:55 <nirik> https://fedorahosted.org/fesco/ticket/1296 18:42:57 <zodbot> nirik: #1296 (F21 System Wide Change: Ruby193 in SCL - https://fedoraproject.org/wiki/Changes/Ruby193_in_SCL) – FESCo - https://fedorahosted.org/fesco/ticket/1296 18:43:27 <dgilmore> +1 here with the same caveats as the previous change 18:43:28 <notting> as a first scl to ship? sure, +1 18:43:39 <dgilmore> they go hand in hand 18:43:44 <mattdm> +1 18:43:53 <nirik> sure, +1 18:43:55 <mitr> +1 18:43:57 <pjones> yeah, same as previous one, +1 18:44:10 <t8m> +1 18:44:15 <nirik> #agreed Change is accepted. (+7,0,0) 18:44:17 <mattdm> As I understand it, openshift won't work in f21 without this -- it's not going to be updated to the new rails in time 18:45:00 <dgilmore> mattdm: it doesnt work in f20 afaik 18:45:08 <nirik> #topic #1297 F21 System Wide Change: Workstation: Enable Software Collections - https://fedoraproject.org/wiki/Changes/Workstation_Enable_Software_Collecti… 18:45:08 <nirik> .fesco 1297 18:45:08 <nirik> https://fedorahosted.org/fesco/ticket/1297 18:45:10 <zodbot> nirik: #1297 (F21 System Wide Change: Workstation: Enable Software Collections - https://fedoraproject.org/wiki/Changes/Workstation_Enable_Software_Collecti…) – FESCo - https://fedorahosted.org/fesco/ticket/1297 18:46:00 <nirik> hum. did I miss number here... 18:46:09 <notting> this implies that they're separate repos? 18:46:33 <mitr> Or a "no action but comps update" if they are not 18:46:34 <mattdm> I think they might be asking to enable softwarecollections.org upstream repos? 18:47:07 <nirik> ah, ticket title is wrong. 18:47:27 <nirik> or I am just confused. nevermind. 18:47:33 <mattdm> jwb do you know the details here? 18:47:42 <nirik> They are simply installing the 'scl' tool by default 18:47:47 <dgilmore> afaik this is enabling the repos provided by softarecollections.org 18:48:00 <dgilmore> softwarecollections.org 18:48:30 <mitr> hhorak asked on the list whether this means enabling softwarecollections.org, and nobody said "no" 18:48:37 <mitr> So, actually that would seem to be the case 18:48:43 <jwb> mattdm, not aware 18:48:59 <dgilmore> and I guess a comps change so that the tooling to make it all work is installed by default 18:49:17 <mitr> That does seem to move us into a world with way too many different repo mechanisms 18:49:19 <nirik> the scl tool doesn't have anything enabled by default I don't thinnk. 18:49:19 <jwb> i was under the impression it was basically "install the tools, have the tools do whatever they do OOTB" 18:49:32 <mattdm> proposal: ask for clarification, and... particularly, whether the approved change for _in_ Fedora software collections makes this moot 18:49:45 <notting> mattdm: sure, +1 18:49:47 <mitr> mattdm: +1 18:49:50 <jwb> proposal: stop waiting until the meeting to ask for feedback... 18:49:50 <dgilmore> mattdm: +1 18:49:58 <t8m> mattdm, +1 18:50:03 <nirik> -1 18:51:03 <nirik> this is just adding scl-utils... 18:51:18 <mattdm> jwb the meeting is basically when we sit down together and go over them. it'd probably be more efficient to make sure everything was covered before, but it's basically been the way we've been functioning.... 18:51:28 <notting> jwb: people did. one person said it was just adding scl-utils, another said it was enabling softwarecollections.org 18:51:33 <jwb> mattdm, yep, and it isn't working and it's frustrating. 18:51:45 <nirik> https://www.softwarecollections.org/en/docs/quick-start/ 18:51:46 <jwb> notting, and nobody followed up 18:52:08 <notting> jwb: in terms of the feature owner? yep. 18:52:25 <jwb> notting, in terms of everyone 18:52:41 <mitr> jwb: AFAICT various people came into this meeting with definite, but differing, ideas of what this was; not with unresolved questions 18:53:12 <mattdm> jwb it sometimes means that there is a one week delay, and it _definitely_ makes these meetings go on. but it could be worse. 18:53:22 <jwb> ok, i'm done on this tangent. it's not going to be productive. if you guys want to continue to wait a week to get questions answered because you asked them in IRC, fine. 18:53:41 * nirik is +1 for the change, but if folks want to clarify we can 18:54:18 <pjones> jwb: I think you can just as clearly state that as "because the feature owner didn't show up to the meeting", which has also always been something we've asked. 18:54:31 <pjones> (also clearly not working) 18:54:42 <pjones> mattdm: +1 18:54:43 <mattdm> pjones although we haven't done a great job of making that clear or calling people in. 18:54:47 <pjones> true 18:54:54 <mattdm> anyway.... 18:54:56 <nirik> ok, thats +5 on mattdm's proposal... 18:55:14 <pjones> so probably we should be doing better on both asking for feedback earlier /and/ soliciting participation during the meetings. 18:55:44 <nirik> #agreed ask for clarification, and... particularly, whether the approved change for _in_ Fedora software collections makes this moot (+5,-1,0) 18:55:47 <nirik> #topic #1298 F21 System Wide Change: The securetty file is empty by default - https://fedoraproject.org/wiki/Changes/securetty_file_is_empty_by_default 18:55:47 <nirik> .fesco 1298 18:55:47 <nirik> https://fedorahosted.org/fesco/ticket/1298 18:55:48 <zodbot> nirik: #1298 (F21 System Wide Change: The securetty file is empty by default - https://fedoraproject.org/wiki/Changes/securetty_file_is_empty_by_default) – FESCo - https://fedorahosted.org/fesco/ticket/1298 18:55:49 <mitr> pjones: I don't think we've typically expected participation; it certainly helps the conversation if possible, but it's never been required and it may be rather impractical 18:56:10 <nirik> oh, who was going to ask for clarification on the last change? any takers? 18:56:23 <pjones> mitr: it's been something we've asked for, but not demanded 18:56:25 <mattdm> nirik I guess I'll do it -- my proposal 18:56:40 <nirik> mattdm: thanks. 18:56:45 <mitr> -1 on empty securetty—the original owner is supporting the counterproposal as well :) 18:56:51 <t8m> -1 for this change 18:56:52 <dgilmore> -1 18:56:55 <nirik> #action mattdm to ask for clarification on enable scls for workstation 18:56:57 <notting> mitr: i think we've expected that at least one of answering questions on-list or in meeting happens 18:57:06 <mitr> notting: the first one, definitely 18:57:13 <nirik> -1 for the change. 18:57:19 <notting> (which may have been delayed due to summit stuff) 18:57:24 <notting> -1 for the change as posted 18:57:25 <t8m> And yes, I can be persuaded to support the removal of pam_securetty from the default pam config for login 18:57:26 <pjones> -1 18:57:55 <mattdm> -1 to change 18:58:02 <nirik> #agreed change is rejected (0,-7,0) 18:58:11 <mattdm> from the ticket, my counter-proposal.... 18:58:15 <nirik> + 18:58:19 <mattdm> Counter-proposal: Remove securetty from default PAM configuration and remove /etc/securetty, and note this in the release notes. 18:58:20 <nirik> +1 rather 18:58:28 <mattdm> +1 18:58:40 <t8m> mattdm, +1 18:58:58 <notting> +1 18:59:06 <pjones> +1 18:59:11 <mitr> +1? Might just as well be happy with only a recommendation to the util-linux maintainer 18:59:30 <mitr> Please make sure that upgrades don't start silently allowing more logins, though 18:59:52 <nirik> #agreed counterproposal: Remove securetty from default PAM configuration and remove /etc/securetty, and note this in the release notes. (+6,0,0) 19:00:03 <nirik> #action mattdm to file bugs and talk to docs 19:00:12 <nirik> #topic #1299 F21 System Wide Change: Smaller Cloud Image Footprint - https://fedoraproject.org/wiki/Changes/Smaller_Cloud_Image_Footprint 19:00:12 <nirik> .fesco 1299 19:00:12 <nirik> https://fedorahosted.org/fesco/ticket/1299 19:00:13 <zodbot> nirik: #1299 (F21 System Wide Change: Smaller Cloud Image Footprint - https://fedoraproject.org/wiki/Changes/Smaller_Cloud_Image_Footprint) – FESCo - https://fedorahosted.org/fesco/ticket/1299 19:00:19 <t8m> mitr, they will start to 19:00:40 <t8m> mitr, I don't see how we could avoid that 19:00:58 <t8m> mitr, rpm will replace the config file unless changed by admin 19:01:22 <t8m> mitr, it must be release noted 19:01:36 <mitr> t8m: touch the file in %pre on upgrades? I don't know. But, oh well. 19:02:00 <mitr> Re: #1299, +1 to the general idea, -1 to introducing networkd in this fashion 19:02:05 <dgilmore> im +1 to Smaller Cloud 19:02:35 <mitr> Perhaps with the import of existing config file format 19:02:35 <mattdm> mitr Yeah, this is a grab bag of things that will be tried. networkd probably isn't ready in any case. 19:02:53 <pjones> So to make the cloud a bigger thing we need to vote yes to smaller cloud, eh? 19:02:59 <t8m> same as mitr +1 to the idea -1 to introducing networkd this way 19:03:03 <mattdm> pjones .... yes? :) 19:03:36 <mattdm> I'm +1 with the assumption that we won't go all crazy with networkd before it's ready :) 19:03:43 <randomuser> mattdm, using the fedora_requires_release_note flag on bugs will do, fwiw 19:03:59 <nirik> +1 here... I'm also worried about adding another network setup before it's ready 19:04:01 <notting> mattdm: might be worth removing that from the change page if it's not the plan anymore.in any case, +1 19:04:17 <mitr> mattdm: Well... I'd argue that Yet Another Config Format is intherently never ready. But I can be outvoted on such things :) 19:04:41 <mitr> or, "never" is too strong 19:04:41 <nirik> so, thats +6? 19:04:57 * pjones +1 19:05:08 <nirik> #agreed Change is approved (+7,0,0) 19:05:20 <mattdm> #action mattdm to follow up on networkd with cloud wg 19:05:30 <nirik> #topic #1300 F21 System Wide Change: Use license macro in RPMs for packages in Cloud Image - https://fedoraproject.org/wiki/Changes/Use_license_macro_in_RPMs_for_packag… 19:05:30 <nirik> .fesco 1300 19:05:30 <nirik> https://fedorahosted.org/fesco/ticket/1300 19:05:31 <zodbot> nirik: #1300 (F21 System Wide Change: Use license macro in RPMs for packages in Cloud Image - https://fedoraproject.org/wiki/Changes/Use_license_macro_in_RPMs_for_packag…) – FESCo - https://fedorahosted.org/fesco/ticket/1300 19:05:43 <mitr> +1 19:05:54 <nirik> sure, +1, perhaps it will take off. ;) 19:06:01 <pjones> why not, +1 19:06:12 <notting> +1. i don't suppose a provenpackager is bored enough to change *everything* 19:06:13 <dgilmore> +1 19:06:25 <mattdm> +1 19:06:34 <t8m> +1 19:06:34 <mattdm> notting spot definitely said he wasn't that bored :) 19:06:52 <nirik> #agreed Change is approved (+7,0,0) 19:07:20 <t8m> are the packaging guidelines already changed so at least for new packages we already get the licenses as %license ? 19:08:01 <mattdm> t8m that's in progress 19:08:19 <nirik> and a fun one for last... 19:08:22 <nirik> #topic #1301 F21 System Wide Change: Workstation: Disable firewall - https://fedoraproject.org/wiki/Changes/Workstation_Disable_Firewall 19:08:23 <nirik> .fesco 1301 19:08:23 <nirik> https://fedorahosted.org/fesco/ticket/1301 19:08:24 <zodbot> nirik: #1301 (F21 System Wide Change: Workstation: Disable firewall - https://fedoraproject.org/wiki/Changes/Workstation_Disable_Firewall) – FESCo - https://fedorahosted.org/fesco/ticket/1301 19:09:19 <mattdm> ooh. time for the fireworks. :) 19:09:20 <nirik> there was a ton of posts on the list on this one 19:09:25 <t8m> I'd say +1, let's make the hell freeze :) 19:09:28 <nirik> much of it noise. ;) 19:09:45 <mitr> I can actually see some merit in the proposal, but the presented rationale, and presented plans to enable functionality and "secure it later", force me to be -1 19:10:23 * mattdm notes that we have never shipped firewalld on the cloud image 19:10:31 <nirik> I've not heard much from change owners or workstation working group about all the list stuff... is there any sense that they might want to revisit this? or ? 19:11:11 <mattdm> and disabled iptables for f20. because the cloud images are meant to be used in an environment which provides its own firewall layer, and both amazon and openstack recommend disabling per-image package filtering. 19:11:24 <notting> mattdm: cloud != workstation, though 19:11:43 <mitr> nirik: Some GNOME people have replied on the list, but not specifically the owner 19:11:47 <nirik> FYI, there were 173 posts on the devel list on this change. Might be a record. ;) 19:11:49 <mattdm> notting Yes, definitely. I just wanted to put that there for full disclosure :) 19:12:54 <mattdm> To me, this is the kind of thing that should trust the workgroups for for their own products -- unless the security team wants to pull the emergency brake 19:13:22 <pjones> honestly the language here isn't very clear (but I haven't read the thread) - he switches between "disable the firewall" and "disable firewalld" 19:13:22 <nirik> I'm a bit torn... I'd normally be -1, but I also trust the folks in the workstation group to do whats best... and rejecting this seems like second guessing them 19:14:20 <jwb> christian replied several times. he's in the WG 19:14:21 <mitr> mattdm: So, hypothetically, if the firewall were to be removed, I'd want an automated test that is constantly verifying we haven't enabled more incoming ports unexpectedly (like we've had 2 cases resently), and perhaps even keep the firewall running but open ports >1024. 19:14:26 <nirik> so, other votes? discussion? proposals? 19:14:27 <notting> i can but help read how the change is written as 'we don't like how it works now, so we want to write a new thing, but we don't know how to do it yet, so we'll disable it in the meantime.'. and as such, i'd be -1. either fix it, or come up with something better, but removal in favor of maybe doing something later? 19:14:37 <jwb> mclasen has opened https://bugzilla.gnome.org/show_bug.cgi?id=727580 to try and fix the underlying problem 19:15:16 <dgilmore> i think i have to agree with notting -1 19:15:21 <mitr> mattdm: But with the approach of "damn security, just do the minimum that enables DAAP to work", that's seems a bit too much to ask 19:15:22 <jwb> twoerner has suggested he's willing to work towards fixing things 19:15:38 <twoerner> jwb: this has been proposed 3 years ago.. but has been rejected by the gnome team 19:15:50 <twoerner> jwb: yes I am still interested 19:15:58 <jwb> twoerner, it was rejected 3 years ago, or it was similarly rejected 3 days ago? 19:16:27 <twoerner> 3 years ago 19:16:30 <jwb> because 1) workstation isn't GNOME and 2) it seems like something that happened 3 years ago isn't set in stone. 19:16:59 <twoerner> jwb: yes, hopefully 19:17:25 <jwb> the contingency plan, to me, seems reasonable 19:17:25 * pjones is also -1 ; there needs to be a better transition plan that doesn't just leave everything open 19:17:48 <nirik> so, we are at -4, +1 I think? 19:17:49 <pjones> jwb: yeah, that actually seems like a better stop gap than this plan 19:18:03 <mitr> jwb: Actually, the contingency plan is essentially "disable the firewall by default but use a different mechanism to override it" 19:18:25 <jwb> mitr, there's no discussion on what the home zone does or doesn't do. 19:18:47 <pjones> or how "public" and "unknown" differ 19:18:54 <mitr> jwb: I'm taking it for granted that home has ~zero restrictions 19:19:04 <pjones> so those would both need to be fleshed out 19:19:17 <jwb> i'm taking it for granted that 3 zones is better than the existing set, which is really confusing and has much more overlap 19:19:36 <jwb> what those zones do can be discussed between workstation and firewalld developers 19:19:50 <nirik> I guess I'll go with -1 as well and we can ask firewalld folks and workstation folks to try and come up with a better plan? 19:19:55 <mattdm> I'll go on the record as +1 based on my comments above. 19:20:04 <mitr> jwb: That's orthogonal. We can have $n sets but if the "contingency" is to use the zone that is least restrictive by default that's the same thing. 19:20:26 <pjones> so it's -5 +2 19:20:27 <jwb> mitr, you're making an assumption. it may be accurate, but it's an assumption. 19:20:34 <mitr> jwb: true 19:20:50 <nirik> pjones: who was the other +1, did I miss someone? 19:20:56 <pjones> t8m 19:21:08 <pjones> (and mattdm now) 19:21:13 <nirik> ah... right. 19:21:31 <nirik> #agreed Change is rejected (-5,+2,0) 19:21:33 <mattdm> proposal: ask the proposal owners to work with firewalld developers and reframe proposal based around current contingency plan 19:21:46 <dgilmore> +1 19:21:49 <pjones> mattdm: +1 19:21:53 <notting> mattdm: +1 19:21:55 <mattdm> +1 to self 19:21:57 <nirik> +1 19:22:30 <mitr> mattdm: -1; the possibility to reframe is implied, and based on my current understanding the current contingency plan is a _bad_ starting point 19:22:47 * mattdm notes that already-in-progress firewalld rewrite in C may help with one of the other issues noted in the discussion: startup performance 19:22:49 <mitr> But they will be talking anyway :) 19:23:10 <nirik> well, that was +5,-1... unless we want to rephrase? 19:23:19 <notting> mitr: they will? the original proposal seemed to imply a lack of talking, if it got to this point 19:24:06 <twoerner> btw: there will be a meeting about "Firewall and Desktop" tomorrow 19:24:07 <mitr> notting: All I really know is that there is a phone call scheduled. No opinion on whether it is sufficient or indicative of long-term changes. 19:24:11 <mitr> ^^^ 19:24:24 <nirik> ok, then perhaps we should just leave it to that? 19:25:14 <mitr> nirik: The two accepted proposals are not in conflict, so let's move on and deal with any future proposal if any? 19:25:22 <mitr> ... future Change proposal 19:25:34 <nirik> right. ok. 19:25:49 <nirik> there's one more ticket that I didn't notice that adamw wanted us to look at today... 19:25:57 <nirik> #topic #1286 New upstream version of dracut inappropriately pushed as stable release update, introduces major regression 19:25:57 <nirik> .fesco 1286 19:25:58 <nirik> https://fedorahosted.org/fesco/ticket/1286 19:26:00 <zodbot> nirik: #1286 (New upstream version of dracut inappropriately pushed as stable release update, introduces major regression) – FESCo - https://fedorahosted.org/fesco/ticket/1286 19:26:16 <t8m> Sorry I had to be afk for a moment 19:26:57 * dgilmore needs to run and pick up daughter, 19:28:03 <nirik> Not sure what admonishing the dracut maintainer will end up doing, but I guess we can. 19:28:05 * mattdm reads 19:28:17 <mitr> so... an update to fix that one bug is in testing https://admin.fedoraproject.org/updates/dracut-037-11.git20140402.fc20 19:28:25 <t8m> I agree with adamw that such update should not be done in critical package such as dracut 19:28:31 <mattdm> it looks like the bug *did* get attention 19:28:34 <mitr> Other than that, accept adamw's proposal as stated? 19:29:04 <nirik> mattdm: sure, after it broke stuff. ;( 19:29:10 <nirik> mitr: +1 19:29:15 <pjones> I'd like to see what haraldh has to say; he's so far not commented in the ticket 19:29:16 <t8m> mitr, +1 19:29:26 <mattdm> nirik yeah. not good, just noting that part of what adam asked for did happen without our involvement 19:29:33 <pjones> but ... yeah, +1 to mitr's proposal. 19:29:39 <mattdm> I'm +1 to mitr/adamw 19:29:44 <mattdm> and pjones too 19:29:46 * mitr notes this wasn't a proposal actually 19:29:52 <jwb> mattdm, because adamw did it... 19:29:55 <adamw> so I basically fixed the bug 19:29:59 <mitr> I'm not sure how much would that "comprehensive evaluation of changes" be enforceable, or matter, or actually be different from just plain "reviewing of incompatible changes" beyond using scary language 19:30:02 <jwb> mattdm, not because the maintainer did 19:30:12 <adamw> but harald has not responded at all, so i'd really like fesco to be aware that this is going on. 19:30:20 <jwb> is he on PTO or something? 19:30:36 <jwb> he's normally fairly responsive 19:30:40 <t8m> pjones, I have to say that he had at least 7 days to do that 19:30:52 <t8m> since the time he was cced on the ticket 19:31:15 <pjones> t8m: yeah, that's why I'm +1 19:31:19 <adamw> not listed at https://apps.fedoraproject.org/calendar/list/vacation/ 19:31:33 <jwb> adamw, the usage of that is... spotty. 19:31:42 * mattdm goes to put my upcoming vacation in the calendar 19:31:44 <adamw> true, but it's what we got. (or is there an RH-internal one too?) 19:31:56 <adamw> maintainers of mission-critical components should be using it, at least. 19:31:58 * pjones checks 19:32:00 <jwb> come on. it's not "what we've got." 19:32:20 <adamw> ? how else can we check? 19:32:27 <nirik> yeah, he's not been active in irc for about the last 10days. 19:32:28 <jwb> what we've got is a bunch of people that work for the same company involved here that can answer that question by asking internally. pretending we don't have that is silly 19:32:51 <adamw> er...hence the part which came next right on the very same line you paraphrased? 19:32:58 <pjones> Well, I'm trying to look up his internal calendar. 19:33:04 <adamw> thanks... 19:33:10 <pjones> I don't anticipate success given the results of my attempt so far. 19:33:28 <jwb> adamw, my point is that this all went down without anyone actually checking that before filing tickets and voting to admonish someone 19:33:35 <adamw> so yeah, the feedback so far indicates my 'fix' (actually reverting the upstream change which seems to be causing the problems) is covering at least the major breakage we know about so far 19:34:05 <adamw> jwb: whether he's on vacation or not seems irrelevant to the issue of whether this update violated the updates policy. 19:34:10 <mattdm> jwb but... pushing out a major change in a critpath component and then going on vacation is also not so great 19:34:24 <adamw> if I'm not supposed to report violations of the updates policy to fesco, what am I supposed to do? 19:34:29 <pjones> yeah, that's not working. 19:34:34 <jwb> adamw, mattdm: sure. but people are saying "well the maintainer had 7 days... <blah blah>" 19:34:37 <t8m> jwb, I have to agree with adamw on this one 19:34:41 <nirik> so, thats +5? 19:34:45 * nirik recounts 19:34:59 <mitr> nirik: count me as 0 for now 19:35:06 <nirik> ok, +4 then... 19:35:07 <adamw> obviously harald should be able to state his position, i'm not calling for a summary burning at the stake. =) i just want fesco to be aware this is going on, and talk to harald about it. 19:35:16 <mattdm> +1 adamw 19:35:37 <nirik> proposal: attempt contacting maintainer and revisit next week. 19:35:45 <jwb> frankly, we should probably have a discussion on why we only have 1 person as a maintainer for something critical like this to begin with, but that's a different issue 19:35:48 <adamw> at the time of filing the ticket i also thought fesco might be able to help fix the immediate breakage, but that's no longer needed at least so far. 19:36:13 <mitr> jwb: https://admin.fedoraproject.org/pkgdb/acls/name/dracut shows 2 19:36:39 <nirik> well, dracut-maint is ? number. ;) 19:36:57 <jwb> if you're going by commits and approveacls... i don't think that's accurate. 19:36:58 <adamw> maybe we should suspend kay from fedora development? ;) 19:37:04 <mitr> jwb: But honestly our practical options in these situations are kind of limited 19:37:16 <notting> proposal's probably worded a bit more strongly than i would have, but +1 on the "that's not ok, plz fix ASAP, and determine what might else be broken" idea 19:37:41 <mitr> notting: I could go with that wording :) +1 19:37:44 <jwb> mitr, i'll disagree politely. anyway, not a problem to solve here 19:38:06 * dgilmore is reading back 19:38:28 <mattdm> and "seriously, try not to do again" 19:38:45 <adamw> jwb: btw, now I come to think of it, there may be some dupes of the bug filed against kernel, might be worth looking out for when doing triage... 19:38:59 <jwb> adamw, well aware of those. duped several myself 19:39:03 <adamw> ah, thanks. 19:39:14 * mitr still dimly remembers the age when "Fedora is the OS that fixes bugs by rebasing, not by backporting" was the received truth... 19:39:17 <nirik> ok, so thats +6 to... what... does someone want to reword? or want me to? 19:39:26 <jwb> which is to say, i'm guilty of not tracking down someone to fix it as well. i feel shame for that. 19:41:02 <pjones> mitr: *and it was so so bad* 19:41:07 <notting> nirik: you don't need to reword it on my behalf 19:41:11 <adamw> mitr: given dracut's development practices, sensitivity, and certain previous incidents...rebasing dracut to fix bugs doesn't seem like it's ever going to work out well. 19:41:47 <nirik> ok. 19:41:50 <mitr> adamw: Oh certainly. Also in some ideal hypothetical case, upstream regressions would be so extremely rare that Fedora's update policy wouldn't matter 19:42:02 <adamw> (some of the apparent, ahem, frustration evident in the ticket is due to the fact that this is not an isolated incident; we've had major problems with dracut before.) 19:42:43 <nirik> #agreed Fesco agrees this is not ok, needs to be fixed, needs determining what else might be broken, and should not be allowed to happen moving forward. (+6,0,0) 19:42:48 <nirik> (hope thats ok with everyone) 19:42:50 <adamw> thanks. 19:42:59 <nirik> #topic Next week's chair 19:43:04 <nirik> who wants it? 19:43:15 <dgilmore> nirik: im +1 19:43:19 <dgilmore> to above 19:43:34 <nirik> dgilmore: ok, will note in ticket. 19:43:41 * dgilmore can do next week 19:43:42 <t8m> I will not be able to attend next week 19:44:03 <nirik> thanks dgilmore 19:44:11 <nirik> #info dgilmore to chair next week 19:44:18 <nirik> #topic Open Floor 19:44:23 <nirik> any items for open floor? 19:44:51 <mattdm> I guess I want to amplify jwb's admonishment that we would be more productive here if we made sure more questions were answered *before* the meeting 19:45:12 <mattdm> Possibly would help us have shorter meetings too 19:45:21 <pjones> and we should *also* more strongly request stakeholders to show up for the discussion 19:45:41 <notting> so, people should request beforehand items be removed from agenda if questions unanswered? 19:46:11 <mattdm> pjones and if they can't (timezones, other commitments), at least get an rsvp along those lines 19:46:12 <t8m> Sometimes only rejecting changes at the meeting makes the change owners to respond to questions... but of course we should be asking questions earlier than at the meeting. 19:46:18 <pjones> mattdm: yeah 19:46:43 <mattdm> notting if we remove items from the agenda, that just seems like it's asking for a pile of unaddressed items 19:47:33 <nirik> perhaps do agenda eariler so we can ask questions about items in it ? 19:47:52 <nirik> dunno. 19:47:57 <jwb> perhaps not wait for the agenda and review the Changes as they are announced. 19:47:59 <mitr> nirik: For Changes, we already _know_ the agenda in advance. 19:48:19 <mitr> Dropping them from the agenda to indicate that the questions haven't been answered is an idea. 19:48:27 <jwb> they're announced and sit on the devel list for at a minimum of a week before they have that 'meeting' keyword added. 19:48:29 <mitr> Or perhaps, just in the Change threads, mark questions as "blocking my vote"? 19:48:43 <jwb> mitr, sure 19:49:12 <mattdm> When we had the PRDs due on a monday before the wednesday meeting, that worked pretty well, I think. 19:49:29 <mitr> I don't know... I'd kind of assume that to be the default... and it still doesn't address "i have received an answer but I don't like it so I'll propose sending it back for changes" 19:49:34 <mattdm> I've kind of gotten into the habit of thinking of wednesday as "fesco ticket review time" 19:49:48 <jwb> mattdm, uh... the Changes are announced a _week_ before they're even added to the agenda 19:49:51 <mattdm> which I freely admit is the root of the problem. 19:49:57 <jwb> mattdm, exactly 19:50:09 <jwb> waiting for the agenda means you're wasting everyone's time. 19:50:16 <mattdm> I know, and I try and read them and comment on them, but I assume that the meeting is when we all get together to talk about them. 19:50:26 <pjones> mattdm: likewise. 19:51:12 <mattdm> If I/we shift that assumption to "these will be discussed and commented on _before_ wednesday", that _should_ help 19:51:19 <nirik> yeah, we can all try and do better... :( 19:51:42 <mattdm> but sometimes it's hard to beat the back-and-forth of conversational meeting 19:52:13 <nirik> ok, anything else? or shall we close out? 19:52:37 <mattdm> I guess that's all, unless we want to make more formalized demands of ourselves 19:53:26 * nirik would like to demand of himself lunch. ;) 19:53:55 <nirik> ok, thanks for coming everyone. 19:53:58 <nirik> #endmeeting

1 0

FAmSCo meeting minutes 2014-04-22
by Jiri Eischmann 22 Apr '14

22 Apr '14

Hi, we had a regular FAmSCo meeting, 5 members attended and we mostly discussed regional budgets for FY2015, budgets for FUDCons etc. You can find more in the minutes: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-04-22/famsco.2014-04… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-2/2014-04-22/famsco.2014-04… Log: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-04-22/famsco.2014-04… The next meeting will be on April 29th. Jiri

1 0

Meeting minutes for Env-and-Stacks WG meeting (2014-04-22)
by Marcela Mašláňová 22 Apr '14

22 Apr '14

============================================ #fedora-meeting: Env and Stacks (2014-04-22) ============================================ Meeting started by mmaslano at 15:01:39 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-04-22/env-and-stacks.2… . Meeting summary --------------- * init process (mmaslano, 15:03:19) * Allow to delete builds/coprs from playground? (mmaslano, 15:05:32) * feature request - dnf plugin should be able to block view of some copr repositories in Playground (mmaslano, 15:08:39) Meeting ended at 15:24:08 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mmaslano (25) * hhorak (9) * zodbot (4) * randomuser (3) * samkottler (1) * drieden (1) * bkabrda (0) * abadger1999 (0) * tjanez (0) * juhp (0) * pkovar (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Fedora Server WG Meeting Minutes (2014-04-22)
by Stephen Gallagher 22 Apr '14

22 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =================================================================== #fedora-meeting-1: Server Working Group Weekly Meeting (2014-04-22) =================================================================== Meeting started by sgallagh at 14:59:09 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2014-04-22/fedora-meeting… . Meeting summary - --------------- * roll call (sgallagh, 14:59:17) * mizmo, nirik sgallagh present (sgallagh, 14:59:59) * mitr present (sgallagh, 15:01:03) * ACTION: sgallagh to contact jperrin about whether he wishes to retain his position on the WG (sgallagh, 15:14:48) * Meeting did not reach quorum (sgallagh, 15:15:58) Meeting ended at 15:16:02 UTC. Action Items - ------------ * sgallagh to contact jperrin about whether he wishes to retain his position on the WG Action Items, by person - ----------------------- * sgallagh * sgallagh to contact jperrin about whether he wishes to retain his position on the WG * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * sgallagh (18) * mizmo (7) * mitr (5) * zodbot (5) * danofsatx-dt (5) * nirik (3) * adamw (0) * Evolution (0) * tuanta (0) * davidstrauss (0) * simo (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlNWiIMACgkQeiVVYja6o6MqEgCfUIHNWeYNJnbytYFH3z/POpLE MSsAoIKVG9r5Vo2NkHfX7TZiHJ0Ew7P4 =O3p+ -----END PGP SIGNATURE-----

1 0

Re: FUDCon IRC meeting for subsidy decision
by Alick Zhao 22 Apr '14

22 Apr '14

On 04/22/2014 10:16 AM, Alick Zhao wrote: > Hi all, > > We have began to make decisions on subsidy applications for FUDCon APAC > 2014. Yesterday's meeting minute is at [1]. We will have another meeting > tonight: 18:00--19:00 UTC+8 April 22 (Tue). Hopefully we can make finish > decisions in today's meeting. > > [1] > http://meetbot.fedoraproject.org/fudcon-planning/2014-04-21/fudcon_beijing_… > Second meeting: http://meetbot.fedoraproject.org/fudcon-planning/2014-04-22/fudcon_beijing_… -- Alick Fedora release 20 (Heisenbug) user https://fedoraproject.org/wiki/User:Alick

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

meetingminutes April 2014