meetingminutes October 2013

meetingminutes@lists.stg.fedoraproject.org

31 participants
53 discussions

Re: Plan for tomorrow's Fedora Infrastructure meeting (2013-10-31)
by Kevin Fenzi 31 Oct '13

31 Oct '13

============================================ #fedora-meeting: Infrastructure (2013-10-31) ============================================ Meeting started by nirik at 19:00:07 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-10-31/infrastructure.2… . Meeting summary --------------- * welcome y'all (nirik, 19:00:07) * New folks introductions and Apprentice tasks (nirik, 19:02:50) * Applications status / discussion (nirik, 19:06:25) * still working on askbot upgrade in stg (nirik, 19:07:40) * bodhi bug 960642 hopefully quashed. (nirik, 19:07:54) * fedocal in stg is 0.3.0 prerelease. Please test. (nirik, 19:08:53) * LINK: https://gist.github.com/ralphbean/7204706 (threebean, 19:17:20) * Applications status / discussion (nirik, 19:19:33) * Sysadmin status / discussion (nirik, 19:27:50) * LINK: https://github.com/ansible/ansible-examples (abadger1999, 19:35:02) * Upcoming Tasks/Items (nirik, 19:40:29) * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/ (nirik, 19:40:29) * Open Floor (nirik, 19:44:03) * apprentice feedback mail will optionally go to list next time. (nirik, 19:48:04) Meeting ended at 19:48:55 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (82) * abadger1999 (27) * threebean (24) * pingou (23) * lmacken (19) * anshprat (18) * ianweller (15) * masta (7) * smooge (7) * croberts (7) * zodbot (4) * dgilmore (4) * puiterwijk (0) * mdomsch (0) * relrod (0) -- 19:00:07 <nirik> #startmeeting Infrastructure (2013-10-31) 19:00:07 <zodbot> Meeting started Thu Oct 31 19:00:07 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:07 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:07 <nirik> #meetingname infrastructure 19:00:07 <nirik> #topic welcome y'all 19:00:07 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 19:00:07 <zodbot> The meeting name has been set to 'infrastructure' 19:00:07 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 19:00:19 * pingou here 19:00:26 * masta waves 19:00:36 * abadger1999 here 19:00:41 <threebean> hi :) 19:00:41 * anshprat here 19:00:44 <smooge> Hello from my phone 19:00:48 * lmacken 19:00:59 <ianweller> hi 19:01:05 <ianweller> also from phone :I 19:01:12 <ianweller> :o * 19:01:44 <nirik> hello smooge's phone. meet ianweller's phone. :) 19:02:14 <dgilmore> hola 19:02:21 <dgilmore> ¿como estas? 19:02:43 <nirik> :) 19:02:50 <nirik> #topic New folks introductions and Apprentice tasks 19:03:05 <nirik> any new folks want to say hi, or apprentices have questions or comments? 19:03:10 <masta> yes 19:03:18 <masta> I'm new - hello all 19:03:24 <anshprat> hi masta 19:03:40 * croberts waves 19:03:48 * masta waves back 19:03:50 <nirik> hey masta. Welcome 19:03:58 <masta> glad to be here 19:04:08 <nirik> you wanted to help out with the aarch64 stuff with dgilmore ? or did you have other interests as well? 19:04:44 <dgilmore> nirik: im going to get him involved in helping me 19:04:48 <dgilmore> not just aarch64 19:04:54 <masta> will probably just focus on aarch64, and while doing that watch and learn from all of you... pickup tasks where I can 19:04:55 <nirik> excellent. 19:05:13 <nirik> well, welcome and do ask questions as things come up, etc. 19:05:16 <croberts> nirik: i closed that wiki ticket with the timeout i will be working on picking up more and working on them 19:05:42 <nirik> croberts: great. I can dig out the wiki related ones if you want those specifically. ;) 19:05:45 <masta> I'm sure I'll be helping rel-eng alot... that is my goal 19:05:51 <croberts> nirik: yes please :) 19:05:51 <anshprat> askbot - upstream says they have hardcoded version on one of the dependency - and that could be the issue. 19:06:11 <anshprat> so I need to figure out how to fix that without hardcoding version dependency 19:06:11 <nirik> anshprat: hey. :) Back from vacation? 19:06:25 <nirik> #topic Applications status / discussion 19:06:38 <anshprat> nirik: :) yes, but haven't been able to spend much time yet. 19:07:23 <lmacken> bodhi bug #960642 popped back up this week, but I am fairly confident that I squashed it yesterday. 19:07:29 <nirik> anshprat: no worries. I reenabled puppet on it (since it mails every 30min about puppet being off... we can disable it again when you are ready to work on it) 19:07:40 <nirik> #info still working on askbot upgrade in stg 19:07:44 <anshprat> nirik: alright 19:07:54 <nirik> #info bodhi bug 960642 hopefully quashed. 19:08:06 <nirik> Any other application news? 19:08:09 <pingou> fedocal on stg is running a pre-release of 0.3.0 19:08:33 <lmacken> working on the bodhi2 masher as a fedmsg consumer, which will let us take advantage of twisted deferred callback chains, easy threading, etc. 19:08:41 <pingou> and the unit-tests coverage of pkgdb2 bumped to 97% today (with all the precautions we should take on this measurement) 19:08:51 <lmacken> pingou: win! 19:08:53 <nirik> #info fedocal in stg is 0.3.0 prerelease. Please test. 19:09:21 <pingou> lmacken: but that does imply fedmsg becomes a source of information that we rely on, right? 19:09:22 <nirik> lmacken: cool. How far are we from tossing up a cloud instance or something where we can see bodhi2. ;) 19:09:49 * croberts goes afk for a few 19:10:11 <lmacken> pingou: yeah, to trigger a push it would be. we could also potentially avoid the public bus by having the bodhi-client send the message locally on a releng box, etc. 19:10:30 <lmacken> but I think we could do it w/o changing any of the current bodhi masher messages 19:10:41 <nirik> someone at the door here, brb 19:10:42 <pingou> cool 19:11:17 <threebean> lmacken: cool. if you need to change them though, we can update fedmsg.meta to match it no problem. 19:11:25 <threebean> agility! 19:11:27 <lmacken> nirik: there are no widgets or templates ported, which is probably a little ways off. the json api is solid at the moment, and I'm going to focus on getting headless mashing & API working first 19:11:38 <lmacken> python-fedora compat, etc. 19:11:57 <lmacken> threebean: cool. I'd also want to ensure that the masher message is signed by someone in releng 19:12:01 <smooge> Sounds good 19:12:24 * threebean nods 19:12:46 <threebean> lmacken: yeah, we can make the required cert group readable by an appropriate releng group. 19:12:52 <ianweller> datagrepper 0.2.1 still has most of the new 0.2.x features broken in production, i'll be working on that this weekend hopefully 19:13:02 <lmacken> threebean: perfect. 19:13:02 <ianweller> (at least, openid login is broken) 19:13:18 <ianweller> (this is due to it being two servers and only having tested it in staging on one) 19:13:26 <lmacken> is /raw still sluggish? 19:13:32 <ianweller> yeah i don't know why it is. 19:13:39 <ianweller> it was fine when we upgraded and restarted apache 19:13:40 <lmacken> are we using indexes? 19:13:44 <nirik> cool. 19:13:47 <ianweller> upgraded datagrepper / restarted apache that is 19:13:52 <anshprat> puiterwijk: any news on postja? 19:14:17 <ianweller> so, datagrepper getting really slow / impossible to use is still an open issue 19:14:59 <anshprat> :! 19:15:25 <threebean> lmacken: yes 19:15:31 <smooge> Ianweller if response >20 reboot 19:15:43 <lmacken> threebean: I'm not seeing any in the model? 19:15:46 <ianweller> smooge: basically 19:15:52 <threebean> lmacken: nope. manually created. 19:16:00 <lmacken> :( 19:16:03 <lmacken> on which cols? 19:16:07 <threebean> timestamp 19:16:14 <threebean> maybe the user and package relations too.. I forget. 19:16:26 <nirik> so whatever became of the idea of checking datagrepper messages stored vs logs or whatever to see if we are dropping anything? I guess thats pending daragrepper being fully working? 19:16:40 <threebean> yeah, I've been running that as of earlier this week. 19:16:49 <threebean> zero dropped messages detected so far. 19:16:55 <lmacken> I'd probably index user.name for sure 19:16:55 <threebean> (I'm just checking koji, though). 19:17:03 <nirik> threebean: nice! 19:17:15 <nirik> could we run a check on other stuff too, just to be paranoid? 19:17:18 <pingou> that's nice 19:17:20 <threebean> https://gist.github.com/ralphbean/7204706 19:17:25 <lmacken> threebean: excellent. 19:17:34 <threebean> everyone run that ^^ 19:17:42 <threebean> erm.. please. 19:17:43 <pingou> at the same time ? :) 19:18:31 <threebean> pingou: well, maybe not ;p 19:18:37 <pingou> doh :( 19:18:54 <threebean> I dunno.. it *should* be able to take it, but, as we're saying, datagrepper is feeling sluggish. 19:19:33 <nirik> #topic Applications status / discussion 19:21:31 <smooge> I am not to touch hardware today 19:21:51 <ianweller> threebean: i wonder if the datanommer db is getting deadlocked somewhere 19:22:37 <ianweller> also, surprisingly, that script you posted runs fine on KU EECS fedora machines. apparently the koji client is installed 19:22:41 <abadger1999> ianweller: to test that -- do you have two datanommer frontend machines? do they both get slow at the same time? 19:22:47 <threebean> ianweller: :D 19:22:51 <abadger1999> ianweller: does restarting one make both fast again? 19:23:00 <pingou> threebean: I got one missed 19:23:04 <ianweller> abadger1999: we have two datagrepper frontend machines. i haven't actually done any real testing, so everything i'm saying is just hearsay 19:23:15 <abadger1999> k 19:23:44 <threebean> pingou: hm. did the script output which thing was missed? 19:23:51 <pingou> * For 2013-10-31 19:20:40.236530 fedmsg did not have https://koji.fedoraproject.org/koji/buildinfo?buildID=475069 19:23:57 <threebean> pingou: and.. was it a race condition? 19:24:05 <pingou> threebean: that's all I have 19:24:14 * threebean check datagrepper for that build 19:24:14 <ianweller> threebean: 475071 koji didn't have 19:24:36 <lmacken> we should sync up the model with the db tweaks by hand, like: __table_args__ = (sa.Index('index_name', 'colname'),) 19:24:44 <threebean> +1 19:24:58 <lmacken> because there may be some low-hanging indexable fruit 19:25:51 <nirik> ok, any other applications news? 19:26:10 <nirik> pingou: how's the jenkins working with the new f19? 19:26:28 <pingou> nirik: so far didn't see/hear any problem 19:26:34 <nirik> cool. 19:26:43 <pingou> more a request for a F20 host :) 19:26:51 <pingou> but I'm not sure we have the IP for it 19:27:06 <nirik> we can get some more I think... 19:27:09 <pingou> so I'm thinking replace F18 by F20 when F20 is beta/release 19:27:11 <nirik> just need to reserve them 19:27:21 <pingou> ok, I'll need to see that with you then :) 19:27:31 <nirik> yep. Ping me out of meeting and we can try and do it. 19:27:50 <pingou> not today, but around half november would be good for me 19:27:50 <nirik> #topic Sysadmin status / discussion 19:27:56 <nirik> pingou: sounds good. 19:28:03 <nirik> lets see... on the sysadmin side... 19:28:35 <smooge> Hardware 100 smooge 0 19:28:45 <nirik> abadger1999: want to share any ansiblefest stuff? 19:28:48 <smooge> :) 19:28:53 * pingou takes the magnet from smooge 19:28:57 <nirik> we have our new bladecenter up and I am trying to get iscsi working on it. 19:29:25 <abadger1999> Lets see... I think we could move the fasClient runs from pull based on each host to push based from lockbox01. 19:29:35 <abadger1999> That might help with our nightly fasClient emails 19:30:17 <nirik> abadger1999: that does mean things have to be ssh reachable from lockbox01, but if they aren't a missed fasClient run is likely the least of their problems. 19:30:33 <abadger1999> nirik: yep. 19:30:57 <abadger1999> nirik: If we have things that are permanently not reachable via ssh from lockbox01, ansible won't be able to work with them at all 19:31:03 <nirik> yep. 19:31:04 <abadger1999> we'll have to configure those hosts differently. 19:31:35 <abadger1999> * f13 pointed me at authprogs https://pypi.python.org/pypi/authprogs as a possible better way to control normal users and scm repos on pkgs.fp.o and fedorahosted. 19:31:38 <nirik> we only have 2 of those that I can think of... the sign-vault machines. On those we only enable sshd when we need to push changes. It's off most of the time. 19:31:49 <abadger1999> It looks promising, puiterwijk was going to look into it. 19:31:53 <abadger1999> <nod> 19:31:57 <nirik> cool 19:32:11 <abadger1999> nirik: do we run fasClient on those two machines regularly or infrequently? 19:32:45 <abadger1999> If regularly, we probably should just leave them pull-based. 19:32:46 <nirik> I'd have to look, I think it runs there... but we could do it as needed, there's few people with access. 19:33:09 * croberts is back 19:33:14 <abadger1999> If infrequently, we can just do fasClient runs at the same time as we explicitly are pushing changes to them. 19:33:19 <abadger1999> <nod> 19:33:21 * nirik nods 19:34:34 <nirik> ok, anything else sysadmin wise? 19:34:36 <abadger1999> For those who don't know, there's the ansible-examples github 19:34:44 <pingou> oh cool 19:34:51 <nirik> yeah. 19:35:02 <abadger1999> https://github.com/ansible/ansible-examples 19:35:19 <abadger1999> It's supposed to have examples that might be good starting points. 19:35:20 <pingou> git grep to the rescure! 19:35:23 <pingou> rescue* 19:35:37 <nirik> yeah, git grep is something I use everyday. ;) 19:35:41 <nirik> very handy 19:36:07 <abadger1999> ansibleworks is going to start up a web service that makes uploading, downloading, rating, etc community provided roles easier in a few months. 19:36:17 <abadger1999> (it'lll be called ansible-galaxy) 19:36:36 <abadger1999> that's about all the big exciting stuff :-0 19:36:38 <nirik> should be a nice source of stuff... 19:36:45 <nirik> abadger1999: whats the licensing on that? 19:36:50 <anshprat> nirik: http://tech-blog.flipkart.net/2013/10/hostdb/ - will we benefit from something like this rather than just inventory in pvt git? 19:36:55 <nirik> or can people specify? 19:37:43 <nirik> anshprat: we have talked about inventory software in the past, but never found one that really was that nice... I've not looked at hostdb tho. 19:37:46 <anshprat> its a " tool to help manage data center inventory and write applications around it. - See more at: http://tech-blog.flipkart.net/2013/10/hostdb/#sthash.qyJQYcfn.dpuf" 19:38:02 <abadger1999> nirik: for the exaples in ansible-galaxy? I don't know for sure -- I imagined it would be uploader-specifies an OSS approved license. 19:38:11 <abadger1999> like googlecode/sourceforge. 19:38:19 <nirik> abadger1999: ok, just curious 19:38:35 <nirik> anshprat: can take a look and discuss on list? 19:38:39 <abadger1999> Rather than "unless specified, this is CC-BY" like stackexchange, etc. 19:38:41 <anshprat> nirik: sure 19:38:54 <abadger1999> Probably should ping the ansibleworks guys to see if that's the case, though. 19:39:17 <nirik> abadger1999: we do want to make sure, because we would likely add to our repo and it's public... 19:39:36 <abadger1999> Yeah. 19:40:29 <nirik> #topic Upcoming Tasks/Items 19:40:29 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/ 19:40:37 <nirik> anything anyone wants to schedule or note? 19:40:46 <nirik> I'll note we slipped another week on f20 beta... 19:40:52 <nirik> so, we are frozen another extra week. :( 19:40:53 <pingou> :( 19:40:56 <threebean> :( 19:41:14 <smooge> Jan 1st 19:41:22 <nirik> smooge: of what year? :) 19:41:26 <threebean> smooge: we taking bets? 19:41:34 <anshprat> we have 3 freezes per release I guess ? 19:41:43 <nirik> anshprat: yep. alpha, beta, final. 19:41:55 <nirik> usually they are 2 weeks. 19:42:09 <nirik> but alpha was 3 this time, and beta is 4 now. 19:42:21 <anshprat> so a quarter an year of freezes, atleast.. :! 19:42:40 <nirik> yeah. 19:43:04 <nirik> in a number of ways the freezes are nice tho... forces you to plan things and work on stuff thats not immediately pushing out. 19:43:12 <nirik> just anoying when they get long 19:43:54 <anshprat> yeah.. 19:44:03 <nirik> #topic Open Floor 19:44:10 <nirik> anyone have any items for open floor? 19:44:21 <nirik> questions, comments, ideas, book suggestions? 19:44:42 <anshprat> nirik: the feedback from apprentices.. 19:44:51 <anshprat> any comments / words on those? 19:45:07 <anshprat> (the monthly mail that you sent..) 19:45:15 <nirik> yeah, some. I suppose I should republish out anything from there that's interesting... 19:45:28 <nirik> but we will be doing a new one tomorrow. ;) 19:45:31 <nirik> or... 19:45:41 <nirik> I could mail apprentices and ask/set replies to the list? 19:46:01 <nirik> then everyone could see and comment? or is that too open for feedback? 19:46:11 <pingou> nirik: propose both 19:46:24 <anshprat> yeah, am fine with that.. 19:46:46 <nirik> pingou: yeah, I can... 19:46:47 <croberts> nirik: can i send you an email for a list of the wiki tickets 19:47:00 <nirik> croberts: sure, or I can send you one with them. ;) 19:47:08 <nirik> or we can meet over in #fedora-admin after the meeting... 19:47:59 <croberts> ok sounds good :) 19:48:04 <nirik> #info apprentice feedback mail will optionally go to list next time. 19:48:17 * nirik will close out things in a few if no further comments. 19:48:52 <nirik> thanks for coming everyone! 19:48:55 <nirik> #endmeeting

1 0

Summary/Minutes from today's FPC Meeting (2013-10-31 16:00 - 18:20 UTC)
by James Antill 31 Oct '13

31 Oct '13

====================== #fedora-meeting-1: fpc ====================== Meeting started by abadger1999 at 16:04:46 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-31/fedora-meeting… . Meeting summary --------------- * Roll Call (abadger1999, 16:04:51) * SCLs -- Approval section (abadger1999, 16:08:59) * LINK: https://fedoraproject.org/wiki/User:Toshio/SCL_Guidelines_%28draft% 29#SCL_Approval (RemiFedora, 16:12:15) * LINK: https://fedorahosted.org/fpc/ticket/339 (geppetto, 16:12:33) * SCL Approval section minus SCL Retirement section (will be voted on later) approved (+1:5, 0:0, -1:0) (abadger1999, 16:24:44) * https://fedorahosted.org/fpc/ticket/350 codimension-parser bundling exception. (abadger1999, 17:45:18) * https://fedorahosted.org/fpc/ticket/359 (abadger1999, 17:58:22) * LINK: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-10/fpc.2013-10-10… (geppetto, 17:58:26) Meeting ended at 18:23:43 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * abadger1999 (174) * geppetto (97) * RemiFedora (64) * limburgher (34) * tibbs|w (31) * zodbot (4) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Summary/Minutes for Cloud WG (2013-10-30)
by Matthew Miller 30 Oct '13

30 Oct '13

===================================== #fedora-meeting-1: Cloud (2013-10-30) ===================================== Meeting started by mattdm at 19:00:22 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-30/fedora-meeting… . Meeting summary --------------- * Intro (mattdm, 19:02:02) * Mailing List vs. IRC Meetings (mattdm, 19:05:31) * AGREED: weekly irc meetings to start. (mattdm, 19:08:19) * more like a checkpoint/coordination than a "$topic: DISCUSS" type of meeting (mattdm, 19:10:22) * "$topic: DISCUSS" should be on the mailing list (mattdm, 19:10:36) * ACTION: mattdm will coordinate time for next/ongoing meeting (mattdm, 19:10:53) * Trac Instance (mattdm, 19:11:07) * LINK: https://fedorahosted.org/cloud/ (mattdm, 19:11:23) * adding rbergeron and number80 as trac admins, will add others who want to be bothered with it on request :) (mattdm, 19:14:54) * for example frankieonuonga (mattdm, 19:15:05) * Draft Governance (mattdm, 19:15:53) * LINK: https://fedoraproject.org/wiki/Cloud_WG (mattdm, 19:15:59) * ACTION: mattdm will reorganize 'landing page' aspects of current draft into actual landing page (mattdm, 19:18:03) * IDEA: borrow from https://fedoraproject.org/wiki/Infrastructure (mattdm, 19:18:30) * AGREED: the liaison to fesco will preferably be a member of fesco, but in the case there isn't a fesco member willing to work on the behalf of the cloud WG, a non-fesco member can be appointed liaison (samkottler) (number80, 19:34:24) * AGREED: the liaison to fesco will preferably be a member of fesco, but in the case there isn't a fesco member willing to work on the behalf of the cloud WG, a non-fesco member can be appointed liaison (samkottler) +6 (number80, 19:35:15) * AGREED: one member of the cloud wg will be elected to serve as chair of the group, organizing meetings and driving; other people will step up as needed if chair is temporarily unavailable (+7) (mattdm, 19:47:34) * AGREED: Because continuity is important, Working Group members serve as long as they are able and willing. When a position on the group becomes available, that position will be filled by unanimous consent of the existing members (+7) (number80, 19:58:19) * ACTION: mattdm to draft an update to the governance document and bring it back to the mailing list (mattdm, 20:03:47) * PRD Framework (mattdm, 20:04:13) * LINK: https://fedoraproject.org/wiki/Cloud_PRD (mattdm, 20:04:17) Meeting ended at 20:24:41 UTC. Action Items ------------ * mattdm will coordinate time for next/ongoing meeting * mattdm will reorganize 'landing page' aspects of current draft into actual landing page * mattdm to draft an update to the governance document and bring it back to the mailing list Action Items, by person ----------------------- * mattdm * mattdm will coordinate time for next/ongoing meeting * mattdm will reorganize 'landing page' aspects of current draft into actual landing page * mattdm to draft an update to the governance document and bring it back to the mailing list * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mattdm (161) * rbergeron (93) * samkottler (76) * number80 (76) * frankieonuonga (50) * jzb (28) * red_trela (27) * geppetto (13) * dgilmore (11) * zodbot (10) * jwb (6) * abadger1999 (3) * nirik (2) * sgallagh (1) * orc_emac_ (1) * hguemar (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>

1 0

Summary/Minutes for Wednesday's (today's) FESCo meeting (2013-10-30)
by Bill Nottingham 30 Oct '13

30 Oct '13

=================================== #fedora-meeting: FESCO (2013-10-30) =================================== Meeting started by notting at 18:01:19 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-10-30/fesco.2013-10-30… . Meeting summary --------------- * init process (notting, 18:01:26) * AGREED: meeting stays at 1800UTC until further notice (+:9) (notting, 18:11:21) * #1170 Working Group call for volunteers (notting, 18:11:47) * AGREED: base design WG approved (+:8, -:1) (notting, 18:27:56) * nirik to open a ticket to track working group governance proposals (notting, 18:29:17) * #1185 Enable "-Werror=format-security" by default (notting, 18:29:50) * AGREED: defer pending results of mass rebuild (+;8, -0, 0:0) (notting, 18:32:40) * AGREED: defer pending results of mass rebuild (+;9, -0, 0:0) (notting, 18:33:30) * AGREED: ask gcc to make warning part of -Wall now, defer enabling it as an error until the mass rebuild test is done (+:7, -:0, 0:0) (notting, 18:38:28) * #1186 FESCo liason role in WGs (notting, 18:40:31) * AGREED: require that the fesco liason on a WG is always a member of that WG's decision making body (+:8, 0:0, -:0 (pjones, 18:48:28) * AGREED: WGs can decide how the FESCo liason is selected, including the possibility of asking FESCo to select. (As FESCo is above the WGs, FESCo could ask WGs to re-choose.) (+:8, -:0, 0:0) (notting, 19:03:03) * #1187 Packagers should be not be allowed to ignore RH bugzilla (notting, 19:03:20) * AGREED: let people come to fesco on a package-by-package basis if they think there are package maintenance issues (+:7, -:0, 0:0) (notting, 19:20:04) * if the person filing the ticket has specific issues, he should bring them up, as per: https://fedoraproject.org/wiki/Package_maintainer_responsibilities (pjones, 19:20:41) * Note that handling bugs is part of package maintainership, per https://fedoraproject.org/wiki/Package_maintainer_responsibilities (notting, 19:22:04) * next week's chair (notting, 19:22:36) * abadger1999 to chair next week's meeting (notting, 19:23:14) * Open Floor (notting, 19:23:22) * LINK: http://fedoraproject.org/wiki/Board/Possible_Future_of_Fedora_Governance (old and drafty) (nirik, 19:28:41) Meeting ended at 19:35:04 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * notting (88) * pjones (75) * sgallagh (63) * nirik (61) * abadger1999 (44) * jwb (43) * mattdm (38) * mitr (34) * t8m (22) * Viking-Ice (18) * pknirsch (18) * zodbot (13) * mmaslano (12) * frankieonuonga (3) * handsome_pirate (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Meeting Summary / October 30, 2013
by Máirín Duffy 30 Oct '13

30 Oct '13

Hi folks! Below find a summary of today's meeting. You can also read it in blog format at http://blog.linuxgrrl.com/2013/10/30/fedora-server-working-group-initial-me… . Below the summary, you'll find the meetbot links if you'd like to read the raw logs. Meeting Minutes =============== Here’s a run-down of today’s Server Working Group meeting: Agenda ====== * Meeting frequency and times * Ticket Tracker/Wiki * Governance Charter * Open Floor Meeting Frequency and Times --------------------------- First we talked about how frequently we should meet and at what time. This diverged a bit into other topics (how to handle absences and time zone issues.) We agreed on the following points: * The Server working group will meet on a weekly basis. There wasn’t any dissension about or discussion on this point. * If there is no agenda posted to the mailing list within 24 hours before a meeting is set to start, the meeting is cancelled and Stephen will send out a cancellation notice to the mailing list. Jóhann suggested the cancellation note just so that it’s clear the meeting is not happening. * Stephen will send out an email to the voting members to figure out a time that works for everyone on a weekly basis. It was pointed out that the United States is going to go through another time shift this coming weekend, and we’re coming down off a flurry of conference travel with folks travelling across timezones, so we need to set a time that will be sustainable long-term. * In the case where a voting member can not make a meeting, they can either pre-vote via the mailing list or abstain-by-default. I did raise a concern about unplanned votes taking place due to a disagreement that cropped up during a meeting that an absent member could not forsee to pre-vote on, but we decided keeping things simpler is best, and if that one vote wouldn’t have mattered anyway it is not a big deal. We’ll wait until we run into a situation where the absence becomes a problem to make any policy for it. * During meetings, silence indicates consent. If people disgaree, then that will bring it to a vote. As Kevin pointed out, “I think we should strive to work on consensus, and only vote on things where it’s clear people aren’t going to be convinced to agree.” Ticket Tracker/Wiki ------------------- We then moved on to talk about the tools we will use to conduct business – managing and tracking our progress. Some of the asset types that came up as needing to be managed with tools were: * Working documents (governance doc, PRD) * Agenda items * Decisions * Discussions * Meeting minutes / summaries While Stephen suggested initially that we set up a Trac instance to keep track of agenda items and discussions, several members (Jóhann, David, Simo) had concerns about prematurely setting up Trac before we had determined through experience that we needed it. We collectively decided to table any Trac set up and to use the Fedora wiki to trac agenda items, decisions, and discussions until it became too unwieldy. At that point, we would have the experience to fully understand the requirements of the tool we needed and be able to select a tool based on requirements. Again, the overarching concern here, I believe, was simplicity. I volunteered to start a blog for the group to share meeting minutes and any progress we’ve made (so here you are. :) ) Initially I’m going to make the blog posts here on my personal blog, but I will also set up a group blog for the Server working group on OpenShift and have that subscribed to Planet Fedora. Meeting minutes will also be posted to the server mailing list as well as to the Fedora meeting minutes list. It was very unanimously agreed that the working documents would be stored on the Fedora project wiki, following the lead of the Cloud working group. Governance Charter ------------------ We then moved on to start discussing the governance charter. Jóhann very helpfully put together a Fedora Server working group governance charter draft which we read through and used to direct the discussion. Jóhann’s draft has four main sections: * Membership * Current Members * Making Decisions * Changing These Rules While there was a lot of agreement about the content of the other three sections, there were some concerns and disagreement about the content of the membership section – enough that the discussion was not conclusive and we decided that we should discuss it further on the mailing list and it should be part of the agenda for next week’s meeting. The main point of contention about the membership section was that there are certain slots in Jóhann’s proposal meant to be dedicated to specific teams within Fedora. There were several concerns voiced about this team-based slot approach: * Some teams in Fedora are spread thinly enough that they might not have anyone willing to serve in representation of them. The counter to this concern that Kevin proposed is that the groups would be given ‘first dibs’ at nominating someone to fill their slot, and if they couldn’t then the slot would open up to anybody interested. * It’s not really clear what advantage having someone from each team would provide the group – it was pointed out by both mitr and mclasen that it is easy to reach out to folks on other teams and get help from them, and being a direct member of the working group isn’t necessary to assit the group. * Some of the slots are reserved for people who represent the ‘server community,’ but it isn’t clear how someone would be identified as representing the server community or not. What exactly is the server community? Doesn’t everyone on the working group need to represent the server community? How can you discern if someone is qualified to do that? * Miloslav was concerned about this resulting in the group “having a great planning infrastructure and no one to do the planned work,” and suggested it would be better if the group was made up primarily of ‘do-ers’ who can get things done rather than decision-makers who would need to rely on external volunteers to get the work done. Hopefully we’ll have some discussion about these points and others and clear up what we think the membership section needs to say. Open Floor ---------- We only had about 5 minutes left (and went over by 5 more) after determining the main meat of the governance proposal that we had to work on was the membership section. We threw out different ideas for loose threads of discussion and other issues we thought should be considered for the next meeting’s agenda: * The governance “membership” section – The ‘membership’ section of the Server working group governance draft. * The use cases for the Server product – discussion of this is already happening on the mailing list. These should help inform the product requirements document the team needs to put together for January. * Short-term deliverables and PRD – Kevin suggested that we should start discussions on the team’s short term deliverables and initial PRD work. * General direction of how the product will be made – Simo brought up that we might need to discuss ‘how the sausage gets made,’ e.g., “are we going to suddenly have 4 different rawhides or how to we handle package management.” Jim responded with, “I would hope we’re still working from a common package set, and either putting our changes in the packages or groups.” Simo concluded that, “I’d like we discuss a bit in the agenda what we think is the general direction and the ‘absolutely not’ and the ‘absolutely can’t do without.’” * Mission statement – Stephen suggested, to follow the Workstation group’s lead, that we put together a mission statement (and potentially a vision statement.) I’m going to draft the initial statements and send them to the list for discussion. Meetbot Minutes --------------- Here is the official meetbot meeting minutes with links to the full raw log: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-30/fedoraserverwg… Full set of meetbot links: Meeting ended Wed Oct 30 18:05:15 2013 UTC. Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-30/fedoraserverwg… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-30/fedoraserverwg… Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-30/fedoraserverwg…

1 0

[Fedora-fr-list] Compte rendu de la réunion du mardi 29 oct 2013
by Haïkel 29 Oct '13

29 Oct '13

Bonsoir, les minutes de la réunion de la communauté francophone: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-29/fedora-meeting… Cordialement, H.

1 0

Fedora marketing team meeting minutes, October 28, 2013
by Ruth Suehle 28 Oct '13

28 Oct '13

Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2013-10-28/fedora_marketing… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2013-10-28/fedora_marketing… Log: http://meetbot.fedoraproject.org/fedora-meeting/2013-10-28/fedora_marketing…

1 0

FAmSCo meeting minutes 2013-10-28
by Jiri Eischmann 28 Oct '13

28 Oct '13

Hi, we had another FAmSCo meeting today. 6 out of 7 members attended and the meeting lasted 37 minutes. You can find more in the meeting minutes: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-2/2013-10-28/famsco.2013-10… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-2/2013-10-28/famsco.2013-10… Log: http://meetbot.fedoraproject.org/fedora-meeting-2/2013-10-28/famsco.2013-10… The next meeting will be on Nov 4th. Jiri

1 0

F20 Beta Blocker Bug Review #5.5 Minutes
by Tim Flink 28 Oct '13

28 Oct '13

================================================== #fedora-blocker-review: f20beta-blocker-review-5.5 ================================================== Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-28/f20beta-b… Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-28/f20beta-b… Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-28/f20beta-b… Meeting summary --------------- * Roll Call (tflink, 16:01:48) * Introduction (tflink, 16:09:17) * 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:09:23) * We'll be following the process outlined at: (tflink, 16:09:28) * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (tflink, 16:09:29) * The bugs up for review today are available at: (tflink, 16:09:34) * LINK: http://qa.fedoraproject.org/blockerbugs/current (tflink, 16:09:34) * The criteria for release blocking bugs can be found at: (tflink, 16:09:39) * LINK: https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria (tflink, 16:09:39) * Up for review today, we have: (tflink, 16:09:44) * 4 Proposed Blockers (tflink, 16:10:05) * 14 Accepted Blockers (tflink, 16:10:05) * 4 Proposed Freeze Exceptions (tflink, 16:10:06) * 12 Accepted Freeze Exceptions (tflink, 16:10:06) * (1023554) cannot get autopart to run after a run through custom storage (tflink, 16:11:21) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1023554 (tflink, 16:11:24) * Proposed Blocker, anaconda, ASSIGNED (tflink, 16:11:27) * AGREED: 1023554 - RejectedBlocker (beta) AceptedBlocker (final) AcceptedFreezeException - While this feels like too much of a corner case to block beta, it does violate the final release criterion "The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration.". A tested fix would be considered past freeze (tflink, 16:28:50) * (1021507) DeviceCreateError: ("Can't have overlapping partitions.", 'sda3') (tflink, 16:29:06) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1021507 (tflink, 16:29:09) * Proposed Blocker, anaconda, NEW (tflink, 16:29:12) * AGREED: 1021507 - AcceptedBlocker - Violates the following F20 beta release criterion: "When using the custom partitioning flow, the installer must be able to: Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes ... and remove a planned storage volume from the planned layout" (tflink, 16:44:35) * (1023295) Users are not shown after system start (tflink, 16:44:42) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1023295 (tflink, 16:44:42) * Proposed Blocker, gdm, NEW (tflink, 16:44:42) * AGREED: 1023295 - RejectedBlocker RejectedFreezeException - This appears to be relatively infrequent and doesn't block the user from logging in if they click on "not shown?" in gdm. Rejected as a release blocking bug for F20 beta. (tflink, 16:49:04) * (1023556) Blivet.copy does not update parted disk refs for partitions on hidden disks (tflink, 16:49:34) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1023556 (tflink, 16:49:37) * Proposed Blocker, python-blivet, ASSIGNED (tflink, 16:49:40) * AGREED: 1023556 - AcceptedBlocker - Violates the following F20 beta release criterion: "When using the custom partitioning flow, the installer must be able to ... Correctly interpret, and modify as described below, any disk with a valid ms-dos or gpt disk label and partition table containing ext4 partitions, LVM and/or btrfs volumes, and/or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions" (tflink, 17:01:02) * (1023263) Anaconda fails to select default app groups for selected DE (tflink, 17:05:26) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1023263 (tflink, 17:05:29) * Proposed Freeze Exceptions, anaconda, NEW (tflink, 17:05:32) * AGREED: 1023263 - AcceptedFreezeException - This would be a release blocking bug for a primary DE but not for a secondary DE. A tested fix would be considered past freeze. (tflink, 17:09:44) * (1015755) current version is 0.4.0 (tflink, 17:09:48) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1015755 (tflink, 17:09:52) * Proposed Freeze Exceptions, libbluray, ASSIGNED (tflink, 17:09:55) * AGREED: 1015755 - RejectedFreezeException - New features are not enough justification for pulling fixes past freeze and this fix can wait for beta freeze to end. (tflink, 17:13:16) * (1018565) scanimage detects sm3840 only for root (tflink, 17:13:56) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1018565 (tflink, 17:13:56) * Proposed Freeze Exceptions, sane-backends, ON_QA (tflink, 17:13:57) * AGREED: 1018565 - RejectedFreezeExceptions - This seems unlikely to affect liveimage users and thus, could be fixed by a 0-day update. (tflink, 17:15:40) * (1010474) Unable to register keys with MokManager (tflink, 17:15:45) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1010474 (tflink, 17:15:46) * Proposed Freeze Exceptions, shim, ON_QA (tflink, 17:15:46) * AGREED: 1010474 - AcceptedFreezeException - This is required for secureboot to work and cannot be fixed with an update post-release. A tested fix would be considered after freeze. (tflink, 17:18:40) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1023657 (satellit, 17:19:54) * Open Floor (tflink, 17:22:39) * ACTION: tflink to discuss pungi fix with dgilmore (tflink, 17:23:43) * Next blocker review meeting will be 2013-10-30 @ 16:00 UTC (tflink, 17:28:35) Meeting ended at 17:31:03 UTC. Action Items ------------ * tflink to discuss pungi fix with dgilmore Action Items, by person ----------------------- * tflink * tflink to discuss pungi fix with dgilmore * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * tflink (168) * cmurf (88) * Viking-Ice (69) * dan408 (54) * sgallagh (27) * roshi (27) * akshayvyas (11) * handsome_pirate (8) * zodbot (5) * dlehman (5) * satellit (5) * satellit_e (2) * nirik (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Logs: APAC meeting on October 26, 2013
by Ankur Sinha 25 Oct '13

25 Oct '13

Hi, Minutes from the APAC meeting we had earlier today. Please pay attention to the release tasks at the bottom of the minutes. If you're looking to join a team to help out, this is a really good time to do it. ** Links ** http://meetbot.fedoraproject.org/fedora-meeting/2013-10-26/fedora_apac_meet… http://meetbot.fedoraproject.org/fedora-meeting/2013-10-26/fedora_apac_meet… http://meetbot.fedoraproject.org/fedora-meeting/2013-10-26/fedora_apac_meet… Minutes: > =============================================== > #fedora-meeting: Fedora APAC meeting 2013-10-26 > =============================================== > > > Meeting started by FranciscoD at 04:10:36 UTC. The full logs are > available at > http://meetbot.fedoraproject.org/fedora-meeting/2013-10-26/fedora_apac_meet… > > Meeting summary > --------------- > * Init process (FranciscoD, 04:11:00) > * Tuan sent regrets (FranciscoD, 04:11:53) > * Magie and Engels are running a class today and sent regrets too > (FranciscoD, 04:12:12) > > * Announcements from FAmSCo (FranciscoD, 04:12:28) > * The Fedora CC card holder is probably going to be Kushal. > (FranciscoD, 04:13:16) > * ACTION: zsun stay in touch with gbraad over approval (FranciscoD, > 04:17:51) > > * Fedora 20 release parties (FranciscoD, 04:18:03) > * LINK: http://fedoraproject.org/wiki/F20_release_events > (FranciscoD, 04:18:17) > * : dramsey is already planning a few: > http://fedoraproject.org/wiki/F20_release_events#APAC (FranciscoD, > 04:19:46) > * Basically: 1: create wiki page. 2: plan out, get approximate budget > requirements. 3: file ticket at fedora apac trac. 4: Get approval at > a meeting. 5: Upload event reports/photographs to wiki etc. 6: > Upload receipts in proper PDF formats and get reimbursements > (FranciscoD, 04:21:23) > > * FAD APAC (FranciscoD, 04:23:05) > * Engel + Magie asked me to announce this: "January 17-19, 2014 is > still the best schedule for us to hold FAD APAC here in the > Philippines" (FranciscoD, 04:23:43) > > * LCA (FranciscoD, 04:24:19) > * LINK: http://lca2014.linux.org.au/ is being held here in January > (FranciscoD, 04:24:36) > * hanthana might come down (FranciscoD, 04:24:44) > * ACTION: FranciscoD make event box if people attend the conference > (FranciscoD, 04:25:01) > > * open floor (FranciscoD, 04:25:25) > * FranciscoD cannot go to LCA due to university schedule (bochecha, > 04:25:44) > * LINK: https://fedoraproject.org/wiki/FAD_APAC_2013 (udinnet, > 04:25:48) > * ACTION: udinnet get in touch with Magie + FAD team and see that the > page is updated ;) (FranciscoD, 04:27:55) > * The Flock bidding process 2014 has been open (udinnet, 04:31:18) > * LINK: > http://meetbot.fedoraproject.org/fedora-meeting/2013-10-09/emea_ambassadors… > (udinnet, 04:31:19) > * LINK: https://fedoraproject.org/wiki/Flock_bid_process (udinnet, > 04:31:36) > > * Release tasks that people can help in (FranciscoD, 04:37:11) > * Appdata: if an application you use isn't already in gnome-software, > please consider submitting an appdata file upstream: > https://lists.fedoraproject.org/pipermail/devel/2013-September/188799.html > (FranciscoD, 04:38:07) > * QA tasks: Testing, testdays, karma requests are still on. Please > provide whatever testing you can. (FranciscoD, 04:38:28) > * Marketing tasks: flyers/other marketing collateral is WIP. Please > contact the marketing team if you want to help (FranciscoD, > 04:39:19) > * Docs: release notes + other documentation is also WIP I think. > Please contact the docs team on how to get started. (FranciscoD, > 04:39:41) > * Websites: Web team is readying the website for beta release. Details > here: https://fedorahosted.org/fedora-websites/ticket/235#comment:1 > (FranciscoD, 04:40:30) > * Design: Quite a lot of WIP here: posters/banners/countdown banners > etc. Please contact the design team if you can help. (FranciscoD, > 04:41:10) > * Infra team is always looking for more hands to help out > (FranciscoD, 04:41:34) > * L10N: F20 release notes are ready on transifex.com for translation. > (alick, 04:42:38) > * Fedora Outreach program for women is in progress. Please refer to > https://fedoraproject.org/wiki/Outreach_Program_For_Women_2013 for > more information. (FranciscoD, 04:44:01) > * If anyone needs help with getting started on anything in the > community, please talk to us in the Fedora Join SIG. > https://fedoraproject.org/wiki/Fedora_Join_SIG (FranciscoD, > 04:44:52) > > Meeting ended at 04:45:09 UTC. > > Action Items > ------------ > * zsun stay in touch with gbraad over approval > * FranciscoD make event box if people attend the conference > * udinnet get in touch with Magie + FAD team and see that the page is > updated ;) > > Action Items, by person > ----------------------- > * FranciscoD > * FranciscoD make event box if people attend the conference > * udinnet > * udinnet get in touch with Magie + FAD team and see that the page is > updated ;) > * zsun > * zsun stay in touch with gbraad over approval > * **UNASSIGNED** > * (none) > > People Present (lines said) > --------------------------- > * FranciscoD (96) > * bochecha (25) > * udinnet (24) > * alick (13) > * zodbot (12) > * zsun (10) -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

meetingminutes October 2013