meetingminutes June 2013

meetingminutes@lists.fedoraproject.org

13 participants
35 discussions

Summary/Minutes from today's Fedora Infrastructure meeting (2013-06-27)
by Kevin Fenzi 27 Jun '13

27 Jun '13

============================================ #fedora-meeting: Infrastructure (2013-06-27) ============================================ Meeting started by nirik at 19:00:03 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-06-27/infrastructure.2… . Meeting summary --------------- * welcome y'all (nirik, 19:00:03) * New folks introductions and Apprentice tasks. (nirik, 19:02:37) * Applications status / discussion (nirik, 19:05:07) * Sysadmin status / discussion (nirik, 19:07:15) * ansible playbook runs logging is being worked on by skvidal (nirik, 19:08:19) * more ansible porting from puppet is happening slowly (since we are in freeze) (nirik, 19:08:33) * limited fedorapeople.org web logs available on request, will flesh out down the road more (nirik, 19:11:49) * help wanted to work on tbgrep scripting (nirik, 19:13:22) * get new bladecenter installed (nirik, 19:14:26) * get new ppc builder installed (nirik, 19:14:32) * phx2 trip for nirik in late july. (nirik, 19:14:41) * Fedora 19 release tasks (nirik, 19:18:00) * Private Cloud status update / discussion (nirik, 19:22:33) * Upcoming Tasks/Items (nirik, 19:23:58) * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/ (nirik, 19:23:59) * Open Floor (nirik, 19:24:47) * f17 eol likely july 30th (nirik, 19:25:48) Meeting ended at 19:30:25 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (65) * skvidal (34) * smooge (10) * dgilmore (8) * abadger1999 (6) * pingou (5) * zodbot (4) * cyberworm54 (3) * suehle (2) * threethirtyWork (1) * kc4zvw (1) * lmacken (0) * threebean (0) * ricky (0) * mdomsch (0) * CodeBlock (0) -- 19:00:03 <nirik> #startmeeting Infrastructure (2013-06-27) 19:00:03 <zodbot> Meeting started Thu Jun 27 19:00:03 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:03 <nirik> #meetingname infrastructure 19:00:03 <nirik> #topic welcome y'all 19:00:03 <nirik> #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean 19:00:03 <zodbot> The meeting name has been set to 'infrastructure' 19:00:03 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean 19:00:15 * skvidal is here 19:00:26 <kc4zvw> is here 19:00:30 * cyberworm54 is here 19:00:40 * pingou here 19:00:46 * dgilmore is kinda here 19:01:23 * nirik waits another min for folks to wander in 19:02:30 <nirik> ok... 19:02:37 <nirik> #topic New folks introductions and Apprentice tasks. 19:02:45 <nirik> any new folks or apprentices with questions or comments? 19:03:10 <suehle> here 19:03:14 * cyberworm54 was wondering for easy tickets to fix 19:03:32 <pingou> suehle: welcome to the infra :) 19:03:44 <suehle> I'm always wandering into the wrong meeting. But hi! 19:03:54 <nirik> hi suehle! :) 19:04:00 <pingou> suehle: always a pleasure to see you :) 19:04:35 * abadger1999 here 19:04:40 <cyberworm54> nirik: I have a few questions.. but I swing by fedora later 19:04:47 <threethirtyWork> suehle: is there marketing meeting today? 19:04:53 <nirik> cyberworm54: ok. 19:05:07 <nirik> #topic Applications status / discussion 19:05:15 <nirik> any applications news this week or upcoming? 19:05:31 <pingou> I fixed a couple of bugs on gnome-tagger 19:05:38 <pingou> abadger1999: news on python-fedora? 19:06:11 <abadger1999> pingou: same as last week -- got the old changes backed out and baseclient changes done but not proxyclient. 19:06:27 <abadger1999> been a lot of things needing fixing that popped up on my radar ths week :-( 19:06:50 <nirik> we hopefully will leave freeze next week, but we will see. ;) 19:07:15 <nirik> #topic Sysadmin status / discussion 19:07:26 <nirik> any sysadmin news this week or upcoming? 19:07:27 * skvidal has been working on the ansible logger 19:07:33 <skvidal> to capture all the events on the server side 19:07:38 <skvidal> so we can mine them 19:07:48 <skvidal> that has hit some interesting hangups but last night I think I got through most of them 19:07:48 * nirik has been porting virthosts and postgresql-server and next is koji hub 19:07:57 <skvidal> and now I'm working on refining what we log 19:08:13 <skvidal> I'll have some sample logs for people to look at shortly - I'd like feed back on what other data we need 19:08:19 <nirik> #info ansible playbook runs logging is being worked on by skvidal 19:08:33 <nirik> #info more ansible porting from puppet is happening slowly (since we are in freeze) 19:09:17 <skvidal> nirik: you did the db server thing, rightr? 19:09:28 <skvidal> nirik: oh you already mentioned it 19:09:31 <skvidal> sorry, was typing :) 19:09:39 <nirik> yeah, I setup a base postgresql server one. It likely needs more work. 19:10:02 <skvidal> also - I setup a system to let people get logs from specific searches against fedorapeople.org 19:10:22 <skvidal> so, for example if you wanted logs from skvidal.fedorapeople.org it could return logs containing 'skvidal' 19:10:41 <skvidal> it doesn't have any passwording on it - so they are simply hidden and protected through permissions 19:10:54 <nirik> we should hopefully look at mod_auth_openid for it and just enable it for everyone down the road. 19:10:57 <skvidal> nod 19:11:12 <skvidal> if there are specific repos, for example, that we wanted logs on 19:11:17 <skvidal> this is a good way of doing it and it works now 19:11:49 <nirik> #info limited fedorapeople.org web logs available on request, will flesh out down the road more 19:12:12 <skvidal> did anyone other than nirik read or care about the traceback/http logs thing on infra-list? 19:12:42 <skvidal> I thought getting tbgrep working (as per lmacken's suggestion) could help us get rid of errors we're currently just not ever noticing 19:12:56 <skvidal> if someone wants to tinker with tbgrep on their own and work out how we should be running it 19:13:07 <skvidal> that might be a low-hanging task that could help us al out 19:13:22 <nirik> #info help wanted to work on tbgrep scripting 19:13:40 * skvidal notices a lot of crickets in here 19:14:00 <nirik> seems like. ;) we're just boring. 19:14:18 <nirik> other stuff upcoming after free is: 19:14:26 <nirik> #info get new bladecenter installed 19:14:32 <nirik> #info get new ppc builder installed 19:14:41 <nirik> #info phx2 trip for nirik in late july. 19:14:48 * abadger1999 likes the idea of automated tbgrep 19:15:15 <abadger1999> the mechanics of gettings logs to the right places ... I'm not qualified to critique :-) 19:15:16 <nirik> yeah, I don't know how big it will end up being, but it's worth a try 19:15:28 <skvidal> abadger1999: you are so qualified 19:16:00 <nirik> anything else on the sysadmin side of things? 19:16:03 <skvidal> abadger1999: all I wanted was some way so that when you set up the host you can easily annotate it's hostvars with a 'has_http_logs=true' 19:16:12 <skvidal> abadger1999: and then the other side could know to grab them 19:16:21 <abadger1999> <nod> 19:16:31 <skvidal> abadger1999: the current mechanism requires remembering to setup rsync on the host and then add that to log02 to retrieve 19:16:38 <nirik> skvidal: so, on that... would it be worth making some of these variables required? 19:16:40 <skvidal> which, at least in my case, I always forget to do 19:17:02 <nirik> ie, you MUST set has_http_logs to either true or false. if you fail to, it errors? 19:17:04 <skvidal> nirik: certainly possible - though a reasonable default in group_vars/all does solve that 19:17:18 <skvidal> nirik: I wouldn't want to have to put has_http_logs=False in every frelling hostvar 19:17:21 <skvidal> that would get.... old 19:17:25 <nirik> yeah, just thinking about us adding a host and making sure we thought of all the things we needed for it. 19:17:31 <nirik> yeah, I suppose so 19:17:47 <skvidal> nod 19:17:52 <nirik> just a idle thought, we can adjust as we go. 19:18:00 <nirik> #topic Fedora 19 release tasks 19:18:13 <nirik> so, anything we need to do to get ready for release? or are we all pretty set? 19:18:42 <nirik> we still do need to check content/permissions/sizes when there's something to stage. ;) 19:18:42 <smooge> we should rebuild all servers next week 19:19:00 <smooge> I am thinking a 2 day outage 19:19:09 <nirik> clearly... monday and tuesday? sounds good to me. ;) 19:19:11 <dgilmore> we should send smooge a big box of corn 19:19:38 <smooge> according to my latest set of tests I am actually not allergic to corn but to something else in Illinois 19:19:39 <nirik> heh 19:19:50 <dgilmore> smooge: probably me :) 19:19:59 <smooge> I don't think you were there in 1996 19:20:12 <nirik> did anyone have a chance to look at archiving old releases? I guess we do that after release now? 19:20:23 <dgilmore> i dont think we did 19:21:06 <nirik> so, we are over 1T for pub/fedora... will that cause mirrors to hate us? 19:21:35 <nirik> new mirrormanager seems to be doing great now. 19:21:50 <smooge> I would do that after release. 19:21:57 <dgilmore> maybe 19:22:02 <nirik> ok. 19:22:14 <nirik> not too much we can do about it right now anyhow. 19:22:33 <nirik> #topic Private Cloud status update / discussion 19:22:34 <smooge> Well I could move them today.. and then they can scream about giant rsyncs 19:22:43 <nirik> smooge: yeah, lets wait 19:22:54 <skvidal> nothing to report on private cloud, is there? 19:22:57 <skvidal> it's just running, at 19:22:58 <skvidal> m 19:22:59 <nirik> not much on cloud. I loaded f19rc2 in there. 19:23:06 <skvidal> cool 19:23:09 <nirik> so if anyone wants to play with it, feel free. 19:23:22 <nirik> much faster boot times now, they fixed the cloud-init thing. 19:23:40 <nirik> it seemed to work fine in my testing. 19:23:58 <nirik> #topic Upcoming Tasks/Items 19:23:59 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/ 19:24:08 <nirik> anything upcoming people would like to note or schedule? 19:24:47 <nirik> #topic Open Floor 19:24:52 <nirik> anyone have items for open floor? 19:24:54 <smooge> how long does F17 stay good after F19 comes out? 19:25:00 <nirik> 1 month... 19:25:25 <dgilmore> likely July 30 19:25:48 <nirik> #info f17 eol likely july 30th 19:26:28 <smooge> ok thanks. I was thinking of when to archive it. 19:26:41 <nirik> what all do we still have in there? 19:26:42 * nirik looks 19:27:07 <dgilmore> smooge: august 1 ;) 19:27:07 <smooge> 15 and 16 could go 19:27:21 <nirik> yeah, we could do 15/16 sometime in july and 17 in aug? 19:27:28 <smooge> okie dokie 19:27:40 <dgilmore> ill pull down 19 alpha and beta in a couple of weeks 19:28:03 <nirik> we still also need to schedule /mnt/koji move sometime in july... 19:28:36 <nirik> but we can figure it out after release. 19:29:23 <nirik> ok, if nothing else, will close out in a min here. 19:30:22 <nirik> thanks for coming everyone! 19:30:25 <nirik> #endmeeting

1 0

Summary/Minutes from today's irc support sig meeting (2013-06-27)
by Kevin Fenzi 27 Jun '13

27 Jun '13

============================================= #fedora-meeting: IRC Support SIG (2013-06-27) ============================================= Meeting started by nirik at 18:00:00 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-06-27/irc-support-sig.… . Meeting summary --------------- * init process (nirik, 18:00:00) * Week in review (nirik, 18:01:40) * ticket #151 "The help channel for fedora is not too friendly" (nirik, 18:05:16) * remember to use @ops to get operator attention when something is happening. (nirik, 18:07:40) * will close ticket out and try and get folks to use more professional language when talking about unwanted PM's. (nirik, 18:25:46) * Open Floor (nirik, 18:26:23) Meeting ended at 18:28:40 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (58) * Sparks (34) * EvilBob (32) * dcr226 (28) * cyberworm541 (5) * zodbot (3) * N3LRX (1) -- 18:00:00 <nirik> #startmeeting IRC Support SIG (2013-06-27) 18:00:00 <zodbot> Meeting started Thu Jun 27 18:00:00 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:00 <nirik> #meetingname irc-support-sig 18:00:00 <nirik> #topic init process 18:00:00 <zodbot> The meeting name has been set to 'irc-support-sig' 18:00:03 <EvilBob> nirik: You able to run this thing today> 18:00:07 <nirik> yeah. 18:00:09 <EvilBob> K 18:00:20 <nirik> hopefully it won't be too long a meeting, but who knows. ;) 18:00:39 * N3LRX is here 18:00:44 * EvilBob 18:00:51 * dcr226 kicks zodbot's tyres 18:01:02 <dcr226> ...sounds expensive 18:01:10 <nirik> but it's not. ;) 18:01:32 <nirik> ok, lets go ahead and dive in then... 18:01:40 <nirik> #topic Week in review 18:01:43 * cyberworm541 is here 18:01:55 <nirik> anything anyone wants to note from the previous week? common problems people are hitting, etc? 18:02:08 <EvilBob> Like every release the there are "trolls o' plenty" 18:02:09 <nirik> I'll note http://www.scrye.com/wordpress/nirik/2013/06/23/attention-fedora-19-prerele… 18:02:33 <nirik> (since f19 is very close, updates-testing is disabled now there, and manual action is required to get back in sync) 18:02:57 <nirik> EvilBob: yeah. 18:03:12 <nirik> release day is likely busy as always. 18:03:23 <EvilBob> nirik: I've been sharing that link, it should be shared more. 18:03:55 <nirik> I did a blog, posted in the g+ group, saw it on faceboot, even posted the forums. ;) 18:04:11 <EvilBob> With the troll population as it is just remember to try to stay frosty and if they push the line, mute/remove them promptly IMO 18:04:23 <cyberworm541> Lol faceboot 18:04:25 * nirik nods. 18:04:35 <nirik> cyberworm541: I always typo it that way, sorry. ;) 18:04:39 <dcr226> nirik, you forgot diaspora 18:04:45 <dcr226> oh wait...so did the world 18:04:50 <nirik> har 18:05:10 <nirik> ok, anything else, or shall we move on? 18:05:16 <nirik> #topic ticket #151 "The help channel for fedora is not too friendly" 18:05:26 <EvilBob> We all try to just tolerate the trolls because we never want to kick someone that is not guilty. 18:05:29 <cyberworm541> Nirik: I thought you were serious 18:05:37 <nirik> so, this ticket is a bit of a puzzlement and drifted around a lot. 18:05:46 <EvilBob> But that can just lead to tickets like this. 18:06:09 <nirik> EvilBob: yeah. if they had been booted more promptly, it would have been less of a issue. 18:06:44 <nirik> anyhow, my thoughts: 18:06:51 <EvilBob> users/non-ops remember that @ops is available to get attention of the channel ops. 18:07:00 <nirik> a) we can't know what the orig person found 'not too friendly' 18:07:17 <nirik> b) the orig person was disruptive/difficult 18:07:37 <Sparks> nirik: If I may add my two cents 18:07:38 <dcr226> third-partied tickets should be ignored imho 18:07:40 <nirik> #info remember to use @ops to get operator attention when something is happening. 18:07:46 <nirik> Sparks: please do. 18:08:07 <Sparks> nirik: I read the transcripts several times since I opened the ticket... 18:08:17 <nirik> IMHO the take away to me is to act more quickly and also avoid some triggering comments that make people flare up... like the 'no netsex' thing 18:08:32 <nirik> Sparks: how far back did you go? 18:08:43 <Sparks> nirik: It is true that the person in question was quite difficult to deal with towards the end of the time period 18:08:49 <cyberworm541> nirik: just do what the folks at #rhel do 18:08:52 <Sparks> nirik: I went back several days 18:09:10 <nirik> ok, I'll note that they appeared from a live and got many hours of help installing... 18:09:10 <Sparks> nirik: I feel that there were some precipitating factors, as I interpretted it. 18:09:53 <dcr226> the ticket was filed by Sparks, who got the information second-hand, and in a different channel. And although he means well with the filing, the point is..he is filing on behalf of someone else, who very likely doesn't care enough to file it on their own 18:10:13 <Sparks> nirik: I'm more concerned with the people that show up for help and get turned off by poor responses to questions and worse language from Fedora people 18:10:13 <cyberworm541> nirik: they try to be helpful but if the guy is just being obviously completely butt then kick 18:10:20 <dcr226> my take is, if you aren't present in the channel to get the context, why file it on behalf of someone else? 18:11:13 <nirik> so, the reason for these tickets is to help us do better and learn. What can we learn from this one? what items can we do differently/better? 18:11:47 <Sparks> nirik: I would say that it is inappropriate to say that someone is trying to have "sexy time" with you on the channel. 18:11:55 <nirik> my takeaway was: a) nip disruptive people faster to avoid them causing lots of long drawn out anguish, and b) talk to some people about trying to use better language in channel? 18:12:23 <Sparks> nirik: I would also say that giving short answers to questions (it's in the config file) without actually explaining it to someone isn't helpful either. It's demeaning. 18:12:27 <dcr226> nothing, the ticket is irrelavent because it wasn't filed by the person who was supposedly offended..its like reporting sexual harrasment against someone else when you weren't there to witness it 18:12:43 <EvilBob> It's inappropriate to start sending people private messages period 18:12:46 <Sparks> dcr226: I have a problem with how it was handled. Okay? 18:13:01 <dcr226> Sparks, noted. But you were not present to see the context 18:13:07 <nirik> well, everyone has a level of support they are willing to provide... 18:13:10 <Sparks> dcr226: I saw the transcripts 18:13:10 <dcr226> Sparks, also, neither was I 18:13:17 <EvilBob> I have a problem with the fact YOU named me in the ticket. 18:13:22 <dcr226> Sparks, so why did it become your problem? 18:13:26 <dcr226> (ooc) 18:13:41 <nirik> from: google it, to read the docs, to read this doc, to read this section of this doc, to 'heres a config file that does what you want' to 'can I login and do it for you' 18:13:53 <EvilBob> I'm glad slandering my name helped you get reelected 18:13:56 <dcr226> are you really making a stand, and want to effect the way that the sig is run...or is it a PR thing? 18:14:04 <Sparks> EvilBob: I simply provided what provoked the ticket. I've even said *publically* that for all I know you were providing excellent support 18:14:07 <dcr226> if its the former, awesome..welcome aboard 18:14:20 <Sparks> dcr226: Because I'm a Board member and I take seriously the way people think about Fedora 18:14:38 <dcr226> Sparks, why now? 18:14:39 <Sparks> dcr226: A PR thing? 18:14:48 <dcr226> yeah, as in: Public Relations 18:14:48 <Sparks> dcr226: This is not the first time I've provided feedback. 18:14:51 * nirik agrees we can always do better... concrete ideas welcome. 18:15:04 <Sparks> EvilBob: Seriously? 18:15:11 <EvilBob> Sparks: Seriously 18:15:13 <dcr226> Sparks, that doesn't answer my question 18:15:33 * nirik thinks this is some kind of offtopic sideline... can we get back to things we can do to improve? 18:15:40 <dcr226> Sparks, its awesome that you want to provide feedback, would be great if you could /j #fedora more often and really get a feel for people :) 18:15:52 <Sparks> dcr226: A friend tells a friend when he sees something happening that can be improved. 18:16:08 <dcr226> Sparks, how come you can't get ahold of this friend to clarify the position now? 18:16:19 <dcr226> or are we talking about a different thing? 18:16:21 <dcr226> possibly I guess 18:16:22 <Sparks> dcr226: I'm counting you all as friends 18:16:26 <dcr226> ah..gotya 18:16:31 <EvilBob> dcr226: I challenged Sparks to step up and do the job. 18:16:43 <EvilBob> dcr226: 20 hours a week for 4 weeks 18:16:48 * nirik would love to have Sparks helpout in #fedora (time permitting) 18:16:48 <Sparks> My intention is to point out something I see as a problem. 18:16:53 <EvilBob> dcr226: Best I can tell he's refused 18:17:02 <Sparks> EvilBob: Hey, if my being in the room means you'll actually be nice to people I'll be in there all the time. 18:17:14 <EvilBob> Sparks: Do the job 18:17:16 <Sparks> nirik: I'm in there now. 18:17:17 <EvilBob> Help people 18:17:24 <dcr226> Sparks, awesome..like I said, would be awesome if you could /j #fedora and see these things unravelling over time 18:17:29 <nirik> Sparks: ok, so, where do we go from here? I'lll try and talk to folks about the netsex comment... beyond that? 18:17:30 <EvilBob> That is the difference 18:18:16 <Sparks> nirik: I'd say that one of the precipitating problems is people giving half answers. It's almost egging them on to become frustrated. It's one of the biggest complaints I've heard over the last few months. 18:18:38 <EvilBob> Sparks: I was nice to this user, I helped them for hours 18:18:38 <Sparks> nirik: We're here to help people not try to show how much more we know than the people asking the questions. 18:18:42 <nirik> Sparks: I'm not sure how to change that aside from you or someone who wants to providing more full answers. 18:19:07 <nirik> ie, we can't force volenteers to do things they don't want to do. I mean we can ask them to... but... 18:19:32 <Sparks> nirik: I feel that the couple of people doing so are conscious of this. If they truly cannot provide a complete answer they shouldn't respond at all, IMO. 18:19:34 <nirik> a number of folks also just answer as they have time... so a quick answer pointing to a doc between dayjob 18:19:38 <EvilBob> Many of us do not spoon feed, nor should we be required to. There is NOTHING wrong with giving users enough help for them to easily help themselves. 18:19:57 <Sparks> nirik: Sure, that's okay. 18:20:08 <EvilBob> Sparks: You can't have it both ways 18:20:09 <nirik> Sparks: perhaps then it's worth trying to talk to those folks directly? ask them if they could try and do better? 18:20:21 * nirik isn't sure he can think of anything else barring more detailed info. 18:20:25 <Sparks> nirik: I've tried and then I get accused of things... 18:20:29 <EvilBob> You can not say that we can't help and that we can in the same breath 18:20:31 <Sparks> so I'm bringing it here. 18:21:13 <Sparks> I'll happily bring back specific examples if needed. I didn't have the time to do so this week. 18:21:17 <dcr226> Sparks, do you have a summary solution/suggestion for action? 18:21:37 <nirik> y

1 0

F19 Final Blocker Bug Review #9 Minutes
by Tim Flink 26 Jun '13

26 Jun '13

================================================= #fedora-blocker-review: f19final-blocker-review-9 ================================================= Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-26/f19final-… Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-26/f19final-… Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-26/f19final-… Meeting summary --------------- * Roll Call (tflink, 16:01:21) * Introduction (tflink, 16:06:50) * Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and freeze exception bugs. (tflink, 16:07:56) * We'll be following the process outlined at: (tflink, 16:08:02) * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (tflink, 16:08:02) * The bugs up for review today are available at: (tflink, 16:08:07) * LINK: http://qa.fedoraproject.org/blockerbugs/current (tflink, 16:08:07) * The criteria for release blocking bugs can be found at: (tflink, 16:08:13) * LINK: https://fedoraproject.org/wiki/Fedora_19_Final_Release_Criteria (tflink, 16:08:13) * LINK: https://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria (tflink, 16:08:16) * LINK: https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria (tflink, 16:08:19) * Up for review today, we have: (tflink, 16:08:24) * 2 Proposed Blockers (tflink, 16:08:31) * 3 Accepted Blockers (tflink, 16:08:31) * 10 Proposed Freeze Exceptions (tflink, 16:08:31) * 24 Accepted Freeze Exceptions (tflink, 16:08:31) * (977764) missing gnu-free fonts cause warnings when anaconda is run (tflink, 16:10:43) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=977764 (tflink, 16:10:46) * Proposed Blocker, LiveCD, VERIFIED (tflink, 16:10:49) * this was accepted as a freeze exception and fixed in RC2 - no need to consider it as a blocker (tflink, 16:11:51) * (976415) Missing usermode-gtk in dependencies (tflink, 16:12:08) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=976415 (tflink, 16:12:08) * Proposed Blocker, liveusb-creator, MODIFIED (tflink, 16:12:09) * AGREED: 976415 - AcceptedBlocker - Violates the following F19 final release criteria for the KDE live spin: "All applications listed under the Applications menu or category must start successfully" (tflink, 16:26:20) * no proposed FEs need to be discussed at this time with go/no-go tomorrow (tflink, 16:33:09) * all accepted blockers are VERIFIED (tflink, 16:33:19) * Fedup Builds for F19 (tflink, 16:34:06) * LINK: https://fedorahosted.org/rel-eng/ticket/5648 (tflink, 16:34:13) * LINK: https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-install-18&arch=x8… (nirik, 16:51:52) * fedup can be tested using the development/19 tree as a package source and the RC2 tree as instrepo (tflink, 17:05:23) * there will be the usual uncertainty with regard to mirrormanager integration, but that's always been the case (tflink, 17:05:51) * if any mirrormanager integration issues surface, they will be dealt with (tflink, 17:06:17) * Open Floor (tflink, 17:08:49) * LINK: http://dl.fedoraproject.org/pub/fedora/linux/releases/test/19-Beta/Fedora/x… <- what fedora-install-19 gives you now. (nirik, 17:08:56) * Go/No-GO and Readiness meetings are tomorrow (2013-06-27) (tflink, 17:10:10) * ACTION: adamw or tflink to create F19 retrospective pages (tflink, 17:11:57) Meeting ended at 17:17:11 UTC. Action Items ------------ * adamw or tflink to create F19 retrospective pages Action Items, by person ----------------------- * adamw * adamw or tflink to create F19 retrospective pages * tflink * adamw or tflink to create F19 retrospective pages * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * tflink (147) * adamw (94) * kparal (56) * nirik (45) * dgilmore (40) * Viking-Ice (26) * jreznik (17) * zodbot (5) * satellit_e (5) * loadiid (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

FAmNA Meeting (25 June 2013)
by Jon 25 Jun '13

25 Jun '13

====================== #fedora-meeting: FAmNA ====================== Meeting started by masta at 01:00:01 UTC. The full logs are available athttp://meetbot.fedoraproject.org/fedora-meeting/2013-06-26/famna.2013-06-… . Meeting summary --------------- * === FAmNA Roll Call === (masta, 01:00:01) * === Announcements === (masta, 01:04:59) * === Tickets === (masta, 01:06:55) * LINK: https://fedorahosted.org/famna/report/9 (masta, 01:07:13) * >>> #56 (Indiana LinuxFest) - FAmNA general trac - https://fedorahosted.org/famna/ticket/56 (masta, 01:08:09) * ACTION: award3535 to harass suehle for payment of ILF sponsorship (masta, 01:14:20) * ACTION: award3535 to setup a swag ticket to have NB send t-shirts (masta, 01:15:28) * media (masta, 01:18:01) * AGREED: ordering 5,000 of the multi-live DVD-9's like we did last time, provided they come up with a quote that is similar to before, $1.10 each, total cost of $5,500 (masta, 01:24:15) * we are talking about the multi ISO image, fitting all the desktop spins, and which ones we keep if space is an issue. (masta, 01:31:39) * == Open Floor === (masta, 01:34:59) Meeting ended at 01:40:15 UTC. Action Items ------------ * award3535 to harass suehle for payment of ILF sponsorship * award3535 to setup a swag ticket to have NB send t-shirts Action Items, by person ----------------------- * award3535 * award3535 to harass suehle for payment of ILF sponsorship * award3535 to setup a swag ticket to have NB send t-shirts * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * masta (53) * nb (36) * award3535 (25) * dan408 (18) * handsome_pirate (14) * inode0 (13) * zodbot (8) * dgilmore (7) * quaid (2) * inode (0)

1 0

F19 Final Blocker Bug Review #8 Minutes
by Tim Flink 24 Jun '13

24 Jun '13

================================================= #fedora-blocker-review: f19final-blocker-review-8 ================================================= Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-24/f19final-… Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-24/f19final-… Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-24/f19final-… Meeting summary --------------- * Roll Call (tflink, 16:00:43) * Introduction (tflink, 16:07:08) * Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and freeze exception bugs. (tflink, 16:07:13) * We'll be following the process outlined at: (tflink, 16:07:18) * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (tflink, 16:07:18) * The bugs up for review today are available at: (tflink, 16:07:23) * LINK: http://qa.fedoraproject.org/blockerbugs/current (tflink, 16:07:23) * The criteria for release blocking bugs can be found at: (tflink, 16:07:28) * LINK: https://fedoraproject.org/wiki/Fedora_19_Final_Release_Criteria (tflink, 16:07:28) * LINK: https://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria (tflink, 16:07:31) * LINK: https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria (tflink, 16:07:34) * Up for review today, we have: (tflink, 16:07:37) * 3 Proposed Blockers (tflink, 16:07:40) * 3 Accepted Blockers (tflink, 16:07:40) * 14 Proposed Freeze Exceptions (tflink, 16:07:40) * 20 Accepted Freeze Exceptions (tflink, 16:07:40) * (964443) Fedora 19 Live Alpha and Beta hangs in boot on HP Envy 23 (tflink, 16:08:07) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=964443 (tflink, 16:08:10) * Proposed Blocker, kernel, NEW (tflink, 16:08:12) * AGREED: 964443 - RejectedBlocker - While unfortunate, there have not been enough reports of this bug to indicate that it is widespread enough to justify blocking release of F19 final. (tflink, 16:14:27) * (974811) NetworkManager dispatchers dbus services misconfiguration (tflink, 16:14:34) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=974811 (tflink, 16:14:37) * Proposed Blocker, NetworkManager, NEW (tflink, 16:14:39) * AGREED: 974811 - RejectedBlocker AcceptedFreezeException - The issues described are not critpath, not 100% applicable to live images and could be fixed with an update. Thus it doesn't qualify as a release blocking issue but a tested fix would be considered after freeze. (tflink, 16:22:01) * (973019) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 0: ordinal not in range(128) (tflink, 16:22:09) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=973019 (tflink, 16:22:12) * Proposed Blocker, python-blivet, POST (tflink, 16:22:15) * LINK: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&… (adamw, 16:29:51) * LINK: https://lists.fedorahosted.org/pipermail/anaconda-patches/2013-June/004732.… (adamw, 16:36:01) * AGREED: 973019 - AcceptedBlocker - Violates the following F19 final release criterion for many live installs using non-english languages: "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above" (tflink, 17:21:30) * (973384) UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128) (tflink, 17:21:37) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=973384 (tflink, 17:21:40) * ProposedBlocker, python-blivet, NEW (tflink, 17:21:43) * AGREED: 973384 - AcceptedBlocker - Violates the following F19 final release criterion for many live installs using non-english languages: "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above" (tflink, 17:25:00) * (874381) USB stick install is running from doesn't get filtered out as an install target (tflink, 17:25:43) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=874381 (tflink, 17:25:46) * Proposed Freeze Exceptions, anaconda, MODIFIED (tflink, 17:25:49) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=960794 (adamw, 17:27:26) * AGREED: 874381 - AcceptedFreezeException - While this isn't severe enough to be a release blocking issue, allowing users to install to the install media is generally unwise. A tested fix would be considered after freeze (tflink, 17:35:20) * (977279) poor handling of disks that report no media present (tflink, 17:39:46) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=977279 (tflink, 17:39:49) * ProposedBlocker, anaconda, ASSIGNED (tflink, 17:39:52) * AGREED: 977279 - This looks like it could be problematic but we need more data on the involved devices and any potential workarounds before making a decision on blocker status (tflink, 17:56:47) * (976931) Make name and icon more understandable (tflink, 17:57:51) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=976931 (tflink, 17:57:52) * Proposed Freeze Exceptions, bijiben, MODIFIED (tflink, 17:57:52) * AGREED: 976931 - AcceptedFreezeException - bijiben is on the DVD and it would be nice to have the name change in the base repos. A tested fix would be considered after freeze. (tflink, 18:01:39) * (954054) [abrt] gnome-shell-3.8.1-1.fc19: _gdk_x11_display_error_event: Process /usr/bin/gnome-shell was killed by signal 5 (SIGTRAP) (tflink, 18:01:51) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=954054 (tflink, 18:01:55) * Proposed Freeze Exceptions, clutter, MODIFIED (tflink, 18:01:57) * LINK: https://bug701974.bugzilla-attachments.gnome.org/attachment.cgi?id=246475 (tflink, 18:05:52) * LINK: http://koji.fedoraproject.org/koji/buildinfo?buildID=428866 (tflink, 18:06:31) * AGREED: 954054 - While it's too close to go/no-go to take this as FE at the moment, it would be accepted in the case that we end up slipping F19 final as long as it goes into the first post-slip spin. (tflink, 18:15:54) * (977472) dragonegg broken dep in F19 (tflink, 18:18:20) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=977472 (tflink, 18:18:20) * Proposed Freeze Exceptions, dragonegg, NEW (tflink, 18:18:20) * AGREED: 977472 - RejectedFreezeException - dragonegg isn't on the DVD or live media and could be fixed with a post-release update. (tflink, 18:20:41) * (914942) [abrt] gnome-shell-3.7.90-1.fc19: g_str_hash: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) (tflink, 18:20:56) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=914942 (tflink, 18:20:59) * Proposed Freeze Exceptions, gnome-shell, ON_QA (tflink, 18:21:01) * LINK: https://retrace.fedoraproject.org/faf/problems/907952/ (kparal, 18:25:44) * LINK: https://retrace.fedoraproject.org/faf/problems/783527/ (kparal, 18:25:46) * AGREED: 914942 - AcceptedFreezeException - While this isn't severe enough to block release of F19 final, it could cause problems on live media and post-install. A tested fix would be considered after freeze. (tflink, 18:28:48) * (976935) mysqld.service is disactivated on upgrade from F18 to F19 (tflink, 18:29:05) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=976935 (tflink, 18:29:08) * Proposed Freeze Exceptions, mariadb, ON_QA (tflink, 18:29:10) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=976935#c5 explains the rationale here, i'm not married to it, if people are -1 that's okay by me (adamw, 18:31:10) * AGREED: 976935 - RejectedFreezeException - While this could cause problems with media sourced upgrades, that was deemed too much of a corner case to take new builds post freeze and network upgrades will function post-release once the update hits stable (tflink, 18:36:13) * (972881) Suspend is not working when laptop's lid is closed (tflink, 18:36:57) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=972881 (tflink, 18:37:00) * Proposed Freeze Exceptions, mate-power-manager, MODIFIED (tflink, 18:37:03) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=973618 ? (adamw, 18:45:14) * AGREED: 972881 - RejectedFreezeException - While unfortunate, suspending on lid close seems like too much of a corner case to take a fix for after freeze. (tflink, 18:49:51) * (968122) SystemError : Unsupported PPC machine type: PMac (tflink, 18:50:04) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=968122 (tflink, 18:50:04) * Proposed Freeze Exceptions, python-blivet, MODIFIED (tflink, 18:50:04) * AGREED: 968122 - AcceptedFreezeException - The change does enable greater hardware support and is isolated to ppc-specific code. A tested fix would be considered after freeze. (tflink, 18:54:46) * (924162) A software selection with dependency errors is allowed to proceed if the dependency check runs twice (tflink, 19:03:10) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924162 (tflink, 19:03:13) * Accepted Blocker, anaconda, NEW (tflink, 19:03:15) * there is a build ready that should fix this (tflink, 19:05:41) * this should be fixed in the latest yum build (3.4.3-99) and the other changes should be minor and low risk (tflink, 19:27:31) * will try -99 and revert to requesting -95.1 if problems arise (tflink, 19:31:51) * (958426) 19 Final TC1 x86_64 Desktop Live is oversized (larger than 1 GB) (tflink, 19:31:58) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=958426 (tflink, 19:32:01) * Accepted Blocker, LiveCD, NEW (tflink, 19:32:04) * work on this has been ongoing, latest unofficial build suggests that it may be fixed (tflink, 19:34:18) * will need to verify with TC7/RC1 (tflink, 19:35:18) * (679486) Liveinst doesn't start if hostname changes (tflink, 19:36:21) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=679486 (tflink, 19:36:21) * Accepted Blocker, xorg-x11-xauth, ASSIGNED (tflink, 19:36:21) * we have a proposed workaround that appears to address the primary symptom of this bug (tflink, 19:40:14) * if there are no better solutions before the next TC/RC, we're likely to take that workaround for final (tflink, 19:40:40) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=679486#c86 (adamw, 19:41:31) * waiting for ajax and bcl to comment on the workaround in https://bugzilla.redhat.com/show_bug.cgi?id=679486#c86 (tflink, 19:44:11) * (974801) MDRaidError: invalid raid level descriptor ãªã— (tflink, 19:45:53) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=974801 (tflink, 19:45:53) * Proposed Freeze Exception, anaconda, POST (tflink, 19:45:53) * AGREED: 974801 - AcceptedFreezeException - This is a bit of a corner case with setting the RAID level when using languages which have translated "None" as a RAID level. A tested fix would be considered after freeze (tflink, 19:49:43) * Open Floor (tflink, 19:50:06) * we have a planned fix for the unicode blockers - liveimage for testing will be sent out shortly (tflink, 19:51:09) * there will be a TC7/RC1 request today (tflink, 19:51:32) * LINK: http://koji.fedoraproject.org/koji/taskinfo?taskID=5536817 is a scratch build of the new old pyparted if anyone wants to get a head start. (adamw, 19:52:23) Meeting ended at 19:56:07 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * adamw (313) * tflink (287) * Viking-Ice (112) * kparal (110) * jreznik (61) * nirik (54) * dan408_ (39) * bcl (24) * drago01 (16) * dgilmore (15) * mclasen (11) * zodbot (9) * rdieter (7) * kalev (5) * geppetto (4) * ontossa (1) * satellit_e (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Docs Project Meeting Summary - 24 June 2013
by Pete Travis 24 Jun '13

24 Jun '13

==================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings ==================================================================================================== Meeting started by randomuser at 14:00:03 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-06-24/fedora_docs.2013… . Meeting summary --------------- * Roll Call (randomuser, 14:00:03) * Follow up on last week's action items (randomuser, 14:06:57) * LINK: http://fedoraproject.org/wiki/Docs_Project_Review_Table maybe ? (randomuser, 14:10:10) * LINK: https://fedoraproject.org/wiki/Docs_Project?rd=DocsProject maybe under "Current Issues'? (Capesteve, 14:10:18) * LINK: http://fedoraproject.org/wiki/Docs_Project_F18_Sys-Admin_Guide-Review_Table (Capesteve, 14:11:14) * Release Notes - Changes coming (randomuser, 14:11:44) * we should start thinking about F20 *now* (randomuser, 14:12:15) * Guide status (randomuser, 14:13:47) * it looks like we should have security guide, IG, sysadmin guide, and virt guide for f19 (randomuser, 14:15:52) * System Administrator's Guide (randomuser, 14:34:34) * Outstanding BZ Tickets (randomuser, 14:48:09) * LINK: http://tinyurl.com/lbrq84 (randomuser, 14:48:17) * all bugs should have docs-qa(a)lists.fp.o as QA contact, subscribe there to track (randomuser, 14:49:41) * Open Floor (randomuser, 14:50:01) * LINK: https://fedoraproject.org/wiki/Docs_Project_Review_Table << Please take a look (Capesteve, 14:50:43) * LINK: https://fedoraproject.org/wiki/Docs_Project_Review_Table (randomuser, 14:51:05) Meeting ended at 15:00:38 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * randomuser (68) * Capesteve (25) * jskarvad (17) * pbokoc (14) * jhradilek (9) * jjmcd (6) * zodbot (5) * LoKoMurdoK (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

1 0

APAC meeting Summary = Saturday, June 22nd, 2013 at 04:00 UTC
by Suresh Packiyarajah 22 Jun '13

22 Jun '13

Hello All, ====================== #fedora-meeting: FAmAPAC ====================== Meeting started by Tuanta at 04:01:46 2013 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-06-22/apac.2013-06-22-… http://meetbot.fedoraproject.org/fedora-meeting/2013-06-22/apac.2013-06-22-… http://meetbot.fedoraproject.org/fedora-meeting/2013-06-22/apac.2013-06-22-… ============================== ================= Meeting summary --------------- * Roll Call (tuanta, 04:02:07) * Announcements (tuanta, 04:05:31) * LINK: https://admin.fedoraproject.org/voting (FranciscoD, 04:06:13) * Voting ends in a day or two. Please please vote! (FranciscoD, 04:06:20) * We'll probably have name voting next week (FranciscoD, 04:06:51) * F19 TC6 is out (FranciscoD, 04:07:08) * LINK: #link http://flocktofedora.org/schedule/ (tuanta, 04:08:58) * Review action items from last meeting (tuanta, 04:16:48) * LINK: http://meetbot.fedoraproject.org/fedora-meeting/2013-05-18/fedora_apac_amba… (tuanta, 04:17:31) * LINK: https://fedoraproject.org/wiki/Ambassadors/APAC/Budget#Q1_.28March_-_May_20… (tuanta, 04:25:35) * ACTION: FranciscoD think of feedback: ascertain status of event to start with (FranciscoD, 04:27:47) * Trac tickets (tuanta, 04:28:36) * LINK: https://fedorahosted.org/fedora-apac/report/9 (tuanta, 04:29:01) * APAC Budget review (tuanta, 04:35:02) * LINK: https://fedoraproject.org/wiki/Ambassadors/APAC/Budget#Q1_.28March_-_May_20… (tuanta, 04:35:18) * LINK: https://fedoraproject.org/wiki/Ambassadors/MalaysianTeam/EventBox (KageSenshi, 04:54:16) * ACTION: FranciscoD file ticket for event boxes (FranciscoD, 04:59:11) * ACTION: FranciscoD file ticket for event boxes: stage 1 -> decide contents (FranciscoD, 05:00:07) Meeting ended at 05:09:02 UTC. Action Items ------------ * FranciscoD think of feedback: ascertain status of event to start with * FranciscoD file ticket for event boxes * FranciscoD file ticket for event boxes: stage 1 -> decide contents Action Items, by person ----------------------- * FranciscoD * FranciscoD think of feedback: ascertain status of event to start with * FranciscoD file ticket for event boxes * FranciscoD file ticket for event boxes: stage 1 -> decide contents * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * FranciscoD (120) * tuanta (113) * KageSenshi (23) * suresht (12) * zodbot (11) * nangthang (3) Thanks, Suresh

1 0

Fedora Chinese Meeting Minutes (2013-06-21)
by Alick Zhao 21 Jun '13

21 Jun '13

Hi all, The IRC meeting minutes tonight are available at the link [1]. Thanks everyone for attending the meeting. In the meeting we talked about FUDCon APAC 2014 bid progress, L10N tasks, upcoming offline events, and so on. Please review the proposed ideas and actions. The next IRC meeting will be held on next Friday (2013-06-28). Please come and join the discussion if you can! [1]: http://meetbot.fedoraproject.org/fedora-zh/2013-06-21/fedora-zh.2013-06-21-… ================== #fedora-zh Meeting ================== Meeting started by alick at 13:00:45 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-zh/2013-06-21/fedora-zh.2013-06-21-… . Meeting summary --------------- * 点名 (alick, 13:01:42) * FUDCON APAC 2014 申办筹备 (alick, 13:09:43) * IDEA: 最好几个在北京的组织者，一同前去学校进行沟通。 (alick, 13:15:19) * IDEA: 在列表通知召集在京组织者准备线下会面 (alick, 13:18:18) * ACTION: alick 在列表通知召集在京组织者准备线下会面 (alick, 13:20:45) * 中文翻译（包括文档翻译、维基 FAQ 翻译） (alick, 13:22:28) * LINK: http://fedorapeople.org/groups/schedule/f-19/f-19-trans-tasks.html (alick, 13:23:41) * Translation Deadline: Websites (POs done) Mon 2013-06-24 (alick, 13:24:24) * LINK: https://fedora.transifex.com/projects/p/fedora/language/zh_CN/?project=2060 (alick, 13:25:42) * LINK: https://fedora.transifex.com/projects/p/fedora-web/translate/#zh_CN/spins-f… (endle, 13:31:56) * 线下活动（包括 F19 发行派对） (alick, 13:46:24) * IDEA: 我建议开始建维基页、用列表征集话题了 (alick, 13:51:48) * ACTION: alick to set up wiki page for relparty (alick, 13:55:49) * ACTION: alick to email the list to call for topics (alick, 13:56:16) * ACTION: endle to email the list to discuss time/place of relparty (alick, 13:58:46) * 自由讨论 (alick, 13:59:17) Meeting ended at 14:01:19 UTC. Action Items ------------ * alick 在列表通知召集在京组织者准备线下会面 * alick to set up wiki page for relparty * alick to email the list to call for topics * endle to email the list to discuss time/place of relparty Action Items, by person ----------------------- * alick * alick 在列表通知召集在京组织者准备线下会面 * alick to set up wiki page for relparty * alick to email the list to call for topics * endle * endle to email the list to discuss time/place of relparty * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * alick (49) * endle (18) * tiansworld (13) * dada533 (10) * BadGirl (5) * zodbot (4) * amos_huang (0) * microcai1 (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Summary/Minutes from today's Fedora Infrastructure meeting (2013-06-20)
by Kevin Fenzi 20 Jun '13

20 Jun '13

============================================ #fedora-meeting: Infrastructure (2013-06-20) ============================================ Meeting started by nirik at 19:00:01 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-06-20/infrastructure.2… . Meeting summary --------------- * welcome y'all (nirik, 19:00:02) * New folks introductions and Apprentice tasks (nirik, 19:02:15) * Applications status / discussion (nirik, 19:03:43) * mirrormanager 1.4 is humming along in production now. :) (nirik, 19:04:04) * badges work is moving rapidly ahead (nirik, 19:04:58) * badges has a number of open issues, see oddshocks or threebean if you want to help out implementing. (nirik, 19:10:10) * LINK: http://ambre.pingoured.fr/thisweekinfedora/ (pingou, 19:10:37) * LINK: http://ambre.pingoured.fr/thisweekinfedora/ <- results of tuesday work (pingou, 19:13:12) * http://ambre.pingoured.fr/thisweekinfedora/ hopefully themed and added to planet soon (nirik, 19:15:45) * Sysadmin status / discussion (nirik, 19:21:31) * ansible migration continues new machines are in ansible and slowly we are porting things over to it. (nirik, 19:25:21) * LINK: http://paste.fedoraproject.org/19948/71747790/ <-- that's the basics (skvidal, 19:28:35) * working out how to let folks run specific playbook runs themselves. (nirik, 19:38:28) * working out how triggering playbook runs should work. (nirik, 19:38:46) * ansible help welcome. See skvidal. :) (nirik, 19:43:39) * new bladecenter is all arrived, trying to get network to it. (nirik, 19:44:42) * will be adding mem and replacing 2 bvirthosts sometime this quarter (nirik, 19:45:00) * phx2 on-site visit time probibly in mid/late july. (nirik, 19:45:16) * working on new rdiff-backup setup for backups, probibly after freeze (nirik, 19:46:04) * Private Cloud status update / discussion (nirik, 19:46:50) * moving networking on a spare node so we can do a multihost grizzly setup (nirik, 19:47:49) * f19 test compose images available for testing/tweaking. (nirik, 19:48:03) * Upcoming Tasks/Items (nirik, 19:48:21) * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/ (nirik, 19:48:21) * Open Floor (nirik, 19:49:34) Meeting ended at 19:52:44 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (112) * skvidal (112) * pingou (16) * threebean (10) * abadger1999 (7) * smooge (6) * zodbot (4) * relrod (4) * oddshocks (3) * mdomsch (3) * kc4zvw_ (1) * lmacken (1) * LoKoMurdoK (1) * ricky (0) * dgilmore (0) * CodeBlock (0) -- 19:00:01 <nirik> #startmeeting Infrastructure (2013-06-20) 19:00:01 <zodbot> Meeting started Thu Jun 20 19:00:01 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:01 <nirik> #meetingname infrastructure 19:00:01 <zodbot> The meeting name has been set to 'infrastructure' 19:00:02 <nirik> #topic welcome y'all 19:00:02 <nirik> #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean 19:00:02 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean 19:00:24 <nirik> who all is around for a nice meeting? 19:00:25 * relrod here 19:00:26 * threebean is here 19:00:31 * LoKoMurdoK here 19:00:35 <oddshocks> Holla! 19:00:50 * skvidal is here 19:01:07 * lmacken 19:01:31 <smooge> ere 19:02:12 <nirik> ok, lets go ahead and dive in... 19:02:15 <nirik> #topic New folks introductions and Apprentice tasks 19:02:25 * mdomsch 19:02:25 <nirik> any new folks want to say hi, or apprentices with questions or comments? 19:02:36 * abadger1999 here 19:03:24 * nirik waits a minute. 19:03:43 <nirik> #topic Applications status / discussion 19:03:49 <nirik> ok, any applications news? 19:04:00 <mdomsch> MM upgraded! 19:04:04 <nirik> #info mirrormanager 1.4 is humming along in production now. :) 19:04:10 <nirik> thanks for working so much on that mdomsch 19:04:17 <oddshocks> Tahrir, badges, etc all humming along. Threebean and I are slaying some code 19:04:20 <threebean> mdomsch: nice blog post on it too :) 19:04:43 <threebean> yeah, and the badges repo can be found here if anyone wants to poke through it http://infrastructure.fedoraproject.org/infra/badges/rules/ 19:04:44 <mdomsch> glad to have finally had the time. My apologies for the crappy overnight pages and debugging sessions all weekend long! 19:04:44 <nirik> oddshocks: excellent. :) 19:04:58 <nirik> #info badges work is moving rapidly ahead 19:05:08 * pingou late 19:05:18 <nirik> oddshocks / threebean: any milestones coming up or things others could help with? 19:05:26 <pingou> oh I got something app related (after badges) 19:05:27 <nirik> mdomsch: no worries. It was worth it to get it all sorted out. :) 19:05:36 <threebean> oh, a question on badge-land. in the next few weeks, can we set up the production badge machines even while we're still in freeze? 19:06:04 <smooge> mdomsch, we need to do that every now and then to remind of us why we don't like to have them 19:06:14 <nirik> we could, just would need a freeze break explaining exactly what is being done. 19:06:30 <skvidal> what is the badges production setup look like? 19:06:35 <threebean> cool. we're not there yet, but when we do get there I'll write it up 19:06:44 <skvidal> are we doing a separate db server for it or relying on db01,etc? 19:07:05 <threebean> skvidal: two "webapp" nodes and one "backend" node. db usage should be pretty light.. I was anticipating adding it to db01. 19:07:23 * nirik really hopes to work on our db 'story' at flock some 19:07:38 <skvidal> nirik: +1 19:07:48 <threebean> yeah, that story right now is "how many eggs do you think we can fit in this basket?" 19:07:54 <nirik> yeah. :( 19:08:14 * relrod has an idea for a web app that I ran by threebean and puiterwijk a while back, but haven't asked anyone else yet because I haven't had time to work on it - but could maybe get some thoughts: 19:08:16 <nirik> we have some mitigation of a db server dying, but it could be/should be much better. 19:08:55 * nirik waits for relrod. 19:09:01 <oddshocks> As far as badges milestones, we're going to be seeing major front-end changes now that we've got the backend all groovy, and there are plenty of issues open peeps can help with on the github repo, just ping me or threebean about em if ya want :) 19:09:26 <relrod> Basically it would be neat/handy for some of our apps (e.g. Fedora Packages and Fedora Mobile) if there was a way for package maintainers to upload screenshots of their packages, and we could show them on package info pages. This could also play into if we ever move to an app-store style system in Fedora, it'd be nice if you could see screenshots before you install an app. 19:09:51 <pingou> relrod: you should talk with hugshie about that 19:10:10 <nirik> #info badges has a number of open issues, see oddshocks or threebean if you want to help out implementing. 19:10:29 <nirik> yeah, we probibly need to discuss app store stuff at flock? 19:10:37 <pingou> http://ambre.pingoured.fr/thisweekinfedora/ 19:10:46 <nirik> I could see screenshots and/or screencasts being nice to have for that 19:10:47 <relrod> pingou: will do. It's pretty low priority on my list, but just a thought I had. I don't have time to do much with it yet, but if it's something that not everybody hates then I'll make a repo and at least hack on it once in a while ;) 19:11:38 <threebean> relrod: same story with me and fedmsg-notifications :) 19:11:54 <nirik> The app store story is still unclear to me. I know hugshie was working on it again, but we need to determine what of that falls on us to implment and if it makes sense to do things that way. 19:12:04 * threebean nods 19:12:24 <pingou> nirik: well afaiu fedora-tagger lift already a good part of the burden 19:12:27 * skvidal recuses himself from this discussion 19:12:32 <pingou> only icons and screenshots are missing 19:12:43 <nirik> pingou: ok. 19:12:49 <threebean> he unfortunately never responded to my pings after we launched the rewrite of fedora-tagger. that was supposed to enable app store stuff integration but its not being taken advantage of as far as I can tell. 19:12:50 <nirik> any other application type news? 19:13:12 <pingou> http://ambre.pingoured.fr/thisweekinfedora/ <- results of tuesday work 19:13:43 <nirik> pingou: very nice! 19:13:48 <pingou> tatica said she was interested in theming it and I hope to plug it onto the planet one of these days 19:14:20 <nirik> sounds great. ;) 19:14:28 <nirik> thats all fedmsg based right? 19:14:43 <pingou> datagrepper actually 19:15:30 <nirik> yeah, ok. 19:15:45 <nirik> #info http://ambre.pingoured.fr/thisweekinfedora/ hopefully themed and added to planet soon 19:16:09 <nirik> any other app news? or shall we move on? 19:16:53 <pingou> I have to put some pressure on abadger1999 to release python-fedora with the flask openid plugin by the end of freeze :) 19:17:02 <abadger1999> <nod> 19:17:05 <abadger1999> It will be done :) 19:17:17 <abadger1999> and hopefully not buggy as hell ;-) 19:17:18 <nirik> is that needed for fedocal openid? 19:17:19 <nirik> or ? 19:17:35 <abadger1999> yeah -- fedocal openid should wor with the beta package + hotfix in infra 19:17:38 <pingou> nirik: yes, that's the last change I have on the todo before releasing 0.2.0 19:17:51 <abadger1999> but it won't work with just hte packages in the fedora/epel repos 19:18:12 <nirik> ok. 19:18:16 <skvidal> question on flask and openid in general 19:18:32 <skvidal> is there a status on the groups/teams work 19:18:46 <pingou> the group extension? 19:18:52 <skvidal> so we can do group-limited openid logins to websites via flask or mod_auth_openid 19:18:53 <skvidal> pingou: yes 19:19:10 <nirik> yeah, I know puiterwijk was waiting for some package for that, but I don't know current status 19:19:11 <skvidal> so I can say 'allow openid from fedora who are in this group' 19:19:21 <nirik> we also want it for the trac openid on hosted. 19:19:22 <skvidal> thx - in the long term I think it will really help us 19:19:27 <skvidal> nirik: yes we do 19:19:40 <pingou> skvidal: afaik for the moment the app is responsible for that 19:19:42 <nirik> I'd love to kick mod_auth_pgsql to the curb. ;) 19:19:54 <skvidal> pingou: right - but I need some way of requesting which groups a user is in 19:20:00 <skvidal> nirik: it's just nagios, right? 19:20:00 <nirik> python-openid-teams I think is the package? 19:20:16 <nirik> nagios and logs I think? or were we going to leave logs alone? 19:20:17 <pingou> nirik: I think so yes 19:20:22 <skvidal> nirik: I'd like to move logs 19:20:28 <skvidal> but logs is not mod_auth_pgsl 19:20:30 <skvidal> afaik 19:20:33 <skvidal> it's that local htpasswd thing 19:20:37 <nirik> it would mean that if openid is down we couldn't get to logs, but meh 19:20:41 <nirik> yeah 19:20:43 <skvidal> nirik: yah we could 19:20:51 <skvidal> nirik: we could either do a fallback or just ssh into the frelling box 19:21:00 <nirik> well, we couldn't get to html versions of the epylogs via a remote browser. ;) 19:21:07 <nirik> so, no big deal. 19:21:14 <nirik> since we would be likely fixing openid anyhow then. ;) 19:21:17 <skvidal> nirik: scp log02:/path/to/file.html . ; firefox file.html :) 19:21:25 <nirik> yep. ;) 19:21:27 <nirik> anyhow... 19:21:28 <skvidal> I'm okay with that 19:21:31 <nirik> #topic Sysadmin status / discussion 19:21:38 <nirik> lets see... sysadmin items... 19:21:43 <abadger1999> skvidal: that's in the extension. 19:21:47 <skvidal> abadger1999: excellent 19:21:51 <skvidal> I went to ansiblefest last week 19:21:54 <nirik> we have a number of things that are going to be pending after freeze. 19:22:03 <skvidal> and mainly heard about how other people are doing things in their infrastructures 19:22:07 <nirik> skvidal: you should do a trip report thingie/blog post/etc. ;) 19:22:10 <skvidal> ah 19:22:16 * skvidal goes back to lurking 19:22:17 <skvidal> :) 19:22:42 <nirik> so it sounded like we aren't doing anything _too_ crazy from others, right? 19:22:51 <skvidal> nirik: not too bad 19:23:03 <skvidal> I will note that a lot of folks are using it to merge between sets of tools 19:23:13 <skvidal> lots of 'use ansible to orchestrate other systems' 19:23:21 <skvidal> 'use ansible to manage merging multiple inventory sources' 19:23:33 <skvidal> 'use ansible to make our devs shut up and break their own systems' 19:23:42 <skvidal> and then by far 19:23:47 <skvidal> some really great new modules 19:23:50 <skvidal> that folks have written 19:23:58 <skvidal> mysql_replication was by far the most exciting imo 19:24:09 <skvidal> their able to flap their master back and forth 19:24:14 <skvidal> orchestrated in a playbook 19:24:21 <nirik> very nice. 19:24:24 <skvidal> and it is kinda seriously neat 19:24:29 * nirik wishes for a similar postgresql one. ;) 19:24:29 <skvidal> yah - I'd like to be there 19:24:34 <skvidal> on both of our db servers 19:24:48 <skvidal> okay I'll be quiet now :) 19:25:06 <pingou> and start write the email ;) 19:25:21 <nirik> #info ansible migration continues new machines are in ansible and slowly we are porting things over to it. 19:25:27 <skvidal> one thing I'll bring up 19:25:34 <nirik> skvidal: so what are our next steps on ansible migration? 19:25:47 <skvidal> so 19:25:54 <skvidal> in order to allocate access to folks 19:26:02 <skvidal> 2 or 3 folks at the conference who spoke are using jenkins 19:26:10 <skvidal> to allocate access to non-root users to run ansible 19:26:19 <skvidal> so they setup jenkins to access the right keys 19:26:28 <skvidal> and then give the users in jenkins access to run certain scripts 19:26:41 <skvidal> then the user sees the whole output and jenkins logs it, etc 19:26:48 <skvidal> so if they break it - they can fix it, too :) 19:27:03 <pingou> neat 19:27:09 <skvidal> I have to admit I like that - but running jenkins as part of the admin process feels...... weird to me 19:27:15 <nirik> it's a nice idea (althought I think jenkins is not a solution for us, but perhaps one of the other things like it would be) 19:27:26 <skvidal> right 19:27:31 <skvidal> so my wonder is this 19:27:48 <skvidal> if we did RBAC via a script + your user/groups + sudo on lockbox 19:27:56 <skvidal> that let you see the output AND it captured the output 19:28:00 <skvidal> 1. is that ridiculous? 19:28:13 <skvidal> 2. is there something stupid about this I'm not thinking about? 19:28:35 <skvidal> http://paste.fedoraproject.org/19948/71747790/ <-- that's the basics 19:29:03 <nirik> I think that would work... but in addition I think we still would need a trigger based thing... so even if you couldn't run the playbook then, you could commit and let it trigger off. 19:29:10 <skvidal> nirik: triggers STILL have to happen 19:29:11 <skvidal> yes 19:29:14 <skvidal> nirik: no dispute 19:29:23 <nirik> yep. In agreement here then. :) 19:29:35 <skvidal> about triggers then 19:29:39 <skvidal> I was looking at our commits 19:30:05 <skvidal> and so man y of them would either actually be 'apply-global' or they are the kind that make it almost impossible to know what systems would definitely be impacted - which means 'apply-global' 19:30:09 <skvidal> so in the apply-global case 19:30:27 <skvidal> how often do we check for that 19:30:40 <skvidal> since clearly it cannot be 'apply-global immediately following any check in that could impact it' 19:30:48 <skvidal> that would just be a recipe for people making bad commit decisions 19:30:55 <nirik> so, that would run all playbooks on all affected hosts in those playbooks? 19:31:08 <nirik> yeah 19:31:24 <skvidal> apply-global means 'we dcannot tell which hosts are affected so we have to assume all' 19:31:54 <nirik> yeah. 19:32:03 <skvidal> I guess I was thinking 19:32:14 * nirik needs to ponder on this a bit more I think... I think we can come up with something... 19:32:16 <skvidal> in the abscence of any commits we should not run 19:32:29 <skvidal> that seems fairly obvious, right? 19:32:33 <nirik> yeah, that sounds reasonable. 19:32:42 <nirik> or if we did, it would be a nightly job or something. 19:32:56 <nirik> and it should SCREAM that something changed. 19:33:18 <skvidal> nirik: sfromm's ansible-report can produce email reports - which are kinda nice 19:33:46 <skvidal> I talked to him a bit last week and earlier this week - there's some.... tricks with it - but I think they can be worked around 19:33:52 <skvidal> okay so 19:33:57 <skvidal> let's say that a commit comes in 19:34:00 <nirik> we could put some of the burden on the committer... to indicate what host(s) or groups to run on... but thats not ideal I guess. 19:34:09 <skvidal> we look up which hosts it applies to 19:34:15 <skvidal> we write that out to a file 19:34:22 <skvidal> which a cron job checks for.... how often? 19:34:33 <nirik> 30min? 19:34:33 <skvidal> every hour? every half-hour? every 15 minutes? 19:34:54 <skvidal> so every 30 m the job will open up the file, look for which playbooks/hosts to run against and run those 19:34:58 <skvidal> if it exists 19:35:27 * nirik notes we can adjust down the road if it seems like the time isn't right... 19:35:40 <nirik> IMHO if it's urgent you want to run the playbook yourself or find someone to. 19:36:06 <nirik> if it's just a cleanup/whatever you want it to run and do those things before you forget about it, but with enough time to realize if you made a mistake/typo (or for other people to) 19:36:23 <skvidal> okay 19:36:52 <skvidal> so even more than before - this means if you're playbook is NOT idempotent - you need to make it be so 19:36:53 <skvidal> :) 19:37:05 <nirik> yes, I think we should strive to make them all so. 19:37:34 <nirik> that would help for a nightly run too... then if something changed, we know someone futzed with things. 19:38:16 <skvidal> okay 19:38:28 <nirik> #info working out how to let folks run specific playbook runs themselves. 19:38:39 <skvidal> so one more thing on the triggered runs 19:38:46 <nirik> #info working out how triggering playbook runs should work. 19:39:00 <skvidal> here's what i've been basing from 19:39:05 <skvidal> for determining which hosts 19:39:18 <skvidal> if the playbook is in playbooks/[hosts,groups] 19:39:21 <skvidal> then it is obvious and simple 19:39:30 <nirik> yeah, --list-hosts will show it. 19:39:41 <nirik> (for that easy case with a playbook) 19:39:48 <skvidal> if it is a task - then look up which playbooks that task shows up and run those playbooks 19:39:59 <skvidal> if the file is in $files then apply-global 19:40:15 <skvidal> I can probably make the files thing a BIT more specific - but it's kind a crapshoot :) 19:40:26 <skvidal> if the modification is in groupvars/hostvars - obvious rules apply 19:40:45 <nirik> roles would be like tasks? (ie, look up which it's included in)? 19:40:51 <skvidal> yah - that's the idea 19:41:25 <skvidal> so it's any mod/add/rm 19:41:33 <skvidal> does that make no sense to anyone? 19:41:54 <nirik> makes sense to me. I think there may be corner cases, but we can deal with them. 19:42:06 <skvidal> the paths i've not looked at are the plugins and library, handlers, etc 19:42:29 <nirik> we change those so rarely, just apply-global as a first cut 19:42:33 <nirik> IMHO 19:42:34 <skvidal> and finally people making 'inventory' changes makes things.. tricky 19:42:56 <skvidal> since it is impossible to know if the inventory change is substantive :) 19:43:00 <nirik> yeah. 19:43:10 <skvidal> okay that's all I have 19:43:12 <smooge> I am working a couple of tickets. Will be installing another PPC once it is racked and stacked and I get a kernel fix so I can run KVM sessions again 19:43:21 <nirik> and cases like if you remove a playbook, do nothing, etc. 19:43:21 <skvidal> if anyone is interested in any of this stuff - please let me know 19:43:39 <nirik> #info ansible help welcome. See skvidal. :) 19:43:48 <nirik> smooge: cool. 19:44:01 <smooge> KVM on PPC is not possible yet 19:44:01 <skvidal> nirik: removing a playbook - yes - would be doing nothing - but.... that's a little different ;) 19:44:06 <smooge> so it will be LPAR 19:44:12 <nirik> smooge: :( bummer. 19:44:29 <nirik> so other pending sysadmin items: 19:44:42 <nirik> #info new bladecenter is all arrived, trying to get network to it. 19:45:00 <nirik> #info will be adding mem and replacing 2 bvirthosts sometime this quarter 19:45:16 <nirik> #info phx2 on-site visit time probibly in mid/late july. 19:46:04 <nirik> #info working on new rdiff-backup setup for backups, probibly after freeze 19:46:25 <nirik> Anything else on the sysadmin side of things? 19:46:46 * skvidal has nothing else 19:46:50 <nirik> #topic Private Cloud status update / discussion 19:46:57 <nirik> not much cloud news recently. 19:47:05 <skvidal> well - sorta 19:47:10 <skvidal> openstack renamed more random crap 19:47:12 <nirik> I have some f19-tc5 images loaded in, need to update them to tc6. ;) 19:47:16 <nirik> yeah, boo. 19:47:30 <skvidal> nirik: hopefully we can get 03 moved to an external port 19:47:35 <skvidal> nirik: and we can do multihost grizzly setup 19:47:49 <nirik> #info moving networking on a spare node so we can do a multihost grizzly setup 19:48:03 <nirik> #info f19 test compose images available for testing/tweaking. 19:48:21 <nirik> #topic Upcoming Tasks/Items 19:48:21 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/ 19:48:33 <nirik> any upcoming tasks/items folks would like to schedule or note? 19:49:29 * nirik is crossing fingers for an on time release, but you know how it is... ;) 19:49:34 <nirik> #topic Open Floor 19:49:52 <nirik> anyone have items for open floor? 19:49:57 <nirik> questions? comments? suggestions? 19:50:59 <kc4zvw_> nirik: I have access issues to work after meeting 19:51:00 <skvidal> where is everyone today? 19:51:00 * nirik will close out the meeting in a minute if not 19:51:17 <smooge> ok 19:51:22 <nirik> kc4zvw_: ok. Can try and assist over in #fedora-admin 19:51:32 <nirik> skvidal: not sure. 19:52:42 <nirik> Thanks for coming everyone! 19:52:44 <nirik> #endmeeting

1 0

F19 Final Blocker Bug Review #7.1 Minutes
by Tim Flink 20 Jun '13

20 Jun '13

=================================================== #fedora-blocker-review: f19final-blocker-review-7.1 =================================================== Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-20/f19final-… Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-20/f19final-… Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-20/f19final-… Meeting summary --------------- * Roll Call (tflink, 15:01:16) * Introduction (tflink, 15:11:29) * Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and freeze exception bugs. (tflink, 15:11:35) * We'll be following the process outlined at: (tflink, 15:11:40) * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (tflink, 15:11:40) * The bugs up for review today are available at: (tflink, 15:11:46) * LINK: http://qa.fedoraproject.org/blockerbugs/current (tflink, 15:11:46) * The criteria for release blocking bugs can be found at: (tflink, 15:11:52) * LINK: https://fedoraproject.org/wiki/Fedora_19_Final_Release_Criteria (tflink, 15:11:52) * LINK: https://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria (tflink, 15:11:55) * LINK: https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria (tflink, 15:11:58) * Up for review today, we have: (tflink, 15:12:01) * 5 Proposed Blockers (tflink, 15:12:17) * 8 Accepted Blockers (tflink, 15:12:18) * 13 Proposed Freeze Exceptions (tflink, 15:12:18) * 25 Accepted Freeze Exceptions (tflink, 15:12:18) * (975521) unable to change settings using dconf (tflink, 15:12:44) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=975521 (tflink, 15:12:47) * Proposed Blocker, dconf, ASSIGNED (tflink, 15:12:49) * AGREED: 975521 - AcceptedBlocker - Violates the following F19 final release criterion for at least dconf data after an unclean shutdown: "All known bugs that can cause corruption of user data must be fixed or documented at Common F19 bugs" (tflink, 15:26:23) * (976389) Missing dependencies on Fedora-19-TC6-x86_64-DVD.iso (tflink, 15:26:34) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=976389 (tflink, 15:26:37) * Proposed Blocker, distribution, NEW (tflink, 15:26:40) * Already closed as NOTABUG (tflink, 15:29:16) * (976107) gnome-games 17 to 19 update fails (tflink, 15:29:38) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=976107 (tflink, 15:29:38) * Proposed Blocker, gnome-games, MODIFIED (tflink, 15:29:39) * AGREED: 976107 - AcceptedFreezeException - While unfotunate, Fn-2 to Fn upgrades are not directly supported and it is unclear on whether this violates any criteria. However, a tested fix would be considered after freeze (tflink, 15:46:04) * (974680) Intel HDA sound issue (tflink, 15:46:12) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=974680 (tflink, 15:46:12) * Proposed Blocker, kernel, NEW (tflink, 15:46:13) * AGREED: 974680 - There is not enough information here to make a decision on blocker status for this bug. Will revisit at the next meeting but if there is still not enough information, will reject as a blocker for F19 final (tflink, 15:53:03) * (976415) Missing usermode-gtk in dependencies (tflink, 15:53:44) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=976415 (tflink, 15:53:44) * Proposed Blocker, liveusb-creator, NEW (tflink, 15:53:44) * AGREED: 976415 - RejectedBlocker - The images are writable to USB and this bug can be fixed with an update post-release. (tflink, 16:20:13) * (976306) PHP 5.5.0 final (tflink, 16:24:08) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=976306 (tflink, 16:24:08) * Proposed Freeze Exceptions, php, MODIFIED (tflink, 16:24:08) * AGREED: 976306 - AcceptedFreezeException - As we understand it, the fix would remove non-free sources from the base F19 repo. As this is important to do, a tested fix would be considered after freeze. (tflink, 16:32:02) * (976017) Please push latest selinux policy to fix denials for gvfs and others (tflink, 16:32:14) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=976017 (tflink, 16:32:17) * Proposed Freeze Exceptions, selinux-policy, MODIFIED (tflink, 16:32:19) * AGREED: 976017 - RejectedFreezeException - There aren't many details in this bug and the requested build is already being pulled in to F19 final TC6 anyways. (tflink, 16:40:34) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=975497 is actually ON_QA or better, but i think dgilmore was having second thoughts about including it (adamw, 16:42:01) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=970030 seems like the latest incarnation of the bug for the cat's name (adamw, 16:43:10) * (970030) F19 release-name â€œSchrÃ¶dingerâ€™s Catâ€ shown as "SchrÃ´dingerÅ«s Cat" on the linux console (tflink, 16:49:03) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=970030 (tflink, 16:49:06) * Proposed Freeze Exceptions, kernel, NEW (tflink, 16:49:08) * AGREED: 970030 - AcceptedFreezeException - It would be good to have the release name show up correctly on consoles and a relatively safe, tested fix would be considered after freeze (tflink, 16:58:00) * (962092) [abrt] gnome-initial-setup-0.9-2.fc19: _clutter_stage_window_get_geometry: Process /usr/libexec/gnome-initial-setup-player was killed by signal 11 (SIGSEGV) (tflink, 16:58:08) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=962092 (tflink, 16:58:12) * Proposed Freeze Exceptions, gnome-initial-setup, NEW (tflink, 16:58:15) * AGREED: 962092 - AcceptedFreezeException - While the exact cause of this isn't 100% clear right now, crashing on the introduction video is bad form and a relatively safe, tested fix would be considered after freeze (tflink, 17:01:16) * (975497) subpackage growpart so the package doesn't pull unnecessary deps into cloud image (tflink, 17:01:26) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=975497 (tflink, 17:01:29) * Proposed Freeze Exceptions, cloud-utils, NEW (tflink, 17:01:31) * AGREED: 975497 - RejectedFreezeException - While it might be nice to have, this doesn't seem to be a big enough problem to justify changing things after freeze. However, if we've misunderstood something here, feel free to repropose as a freeze exception with more explanation on why this needs to change now. (tflink, 17:07:02) * (975159) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 0: ordinal not in range(128) (tflink, 17:13:21) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=975159 (tflink, 17:13:24) * Accepted Blocker, anaconda, MODIFIED (tflink, 17:13:26) * (924162) A software selection with dependency errors is allowed to proceed if the dependency check runs twice (tflink, 17:14:52) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924162 (tflink, 17:14:55) * Accepted Blocker, anaconda, NEW (tflink, 17:14:58) * devs are aware of the problem, progress is being made. nothing for us to do at the moment (tflink, 17:17:42) * (958426) 19 Final TC1 x86_64 Desktop Live is oversized (larger than 1 GB) (tflink, 17:17:56) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=958426 (tflink, 17:17:59) * Accepted Blocker, LiveCD, NEW (tflink, 17:18:02) * for F19 final TC6: the i386 media is OK, x86_64 is still oversized (tflink, 17:20:07) * (964006) cloud-init hostname service failing on initial boot (tflink, 17:20:45) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=964006 (tflink, 17:20:48) * Accepted Blocker, selinux-policy, MODIFIED (tflink, 17:20:51) * fix has been submitted, waiting for new spin to test the fix (tflink, 17:22:06) * TC6 cloud images are available to test the fix (tflink, 17:22:40) * waiting for verification of fix right now (tflink, 17:24:16) * (679486) Liveinst doesn't start if hostname changes (tflink, 17:24:20) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=679486 (tflink, 17:24:20) * Accepted Blocker, xorg-x11-xauth, ASSIGNED (tflink, 17:24:20) * no movement on this since monday when it was accepted as a blocker (tflink, 17:24:50) * will be keeping an eye on progress (tflink, 17:25:08) * (974680) Intel HDA volume haywire after kernel-3.6.10 (tflink, 17:29:57) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=974680 (tflink, 17:29:57) * Proposed Blocker, kernel, NEW (tflink, 17:29:58) * AGREED: 974680 - RejectedBlocker - The issue as described does not violate any of the F19 release criteria and thus is rejected as a release blocking bug for F19 final. If there is a new showstopper in Intel HDA, please file as a new bug. (tflink, 17:31:49) * Open Floor (tflink, 17:32:08) Meeting ended at 17:34:46 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * tflink (232) * adamw (99) * Viking-Ice (90) * jreznik (47) * kparal (45) * pschindl (14) * Martix (7) * nirik (5) * zodbot (5) * satellit_e (5) * dan408 (4) * ignatenkobrain (3) * lmacken (1) * jreznik_ (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

meetingminutes June 2013