meetingminutes February 2013

meetingminutes@lists.fedoraproject.org

14 participants
30 discussions

Summary/Minutes from today's Fedora Infrastructure meeting (2013-02-28)
by Kevin Fenzi 28 Feb '13

28 Feb '13

============================================ #fedora-meeting: Infrastructure (2013-02-28) ============================================ Meeting started by nirik at 19:00:01 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-02-28/infrastructure.2… . Meeting summary --------------- * welcome to all (nirik, 19:00:01) * New folks introductions and Apprentice tasks. (nirik, 19:02:10) * Applications status / discussion (nirik, 19:03:33) * coprs is back up. One outstanding instance bug being worked. (nirik, 19:04:41) * pkgdb-cli has had some new releases. (nirik, 19:04:50) * fas-openid is going to production in 5 days if no new stoppers found. (nirik, 19:05:13) * fas update planned for later today (nirik, 19:05:28) * fedocal has finished review (nirik, 19:07:42) * Sysadmin status / discussion (nirik, 19:14:37) * Private Cloud status update / discussion (nirik, 19:21:11) * LINK: http://paste.fedoraproject.org/ <- paste your content there, submit and then just paste the url it gives to the channel, then everyone can load it and see it. ;) (nirik, 19:26:51) * Upcoming Tasks/Items (nirik, 19:29:49) * 2013-02-28 end of 4th quarter (nirik, 19:30:03) * 2013-03-01 nag fi-apprentices (nirik, 19:30:03) * 2013-03-07 remove inactive apprentices. (nirik, 19:30:03) * 2013-03-19 to 2013-03-26 - koji update (nirik, 19:30:03) * 2013-03-29 - spring holiday. (nirik, 19:30:03) * 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze (nirik, 19:30:04) * 2013-04-16 F19 alpha release (nirik, 19:30:05) * 2013-05-07 to 2013-05-21 BETA infrastructure freeze (nirik, 19:30:07) * 2013-05-21 F19 beta release (nirik, 19:30:09) * 2013-05-31 end of 1st quarter (nirik, 19:30:11) * 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. (nirik, 19:30:13) * 2013-06-25 F19 FINAL release (nirik, 19:30:15) * 2013-03-05 Maybe FAS-OpenID release (puiterwijk, 19:30:29) * Open Floor (nirik, 19:33:38) * GSoC (nirik, 19:34:32) * LINK: https://fedoraproject.org/wiki/GSOC_2013 (nirik, 19:35:46) * LINK: http://www.youtube.com/watch?v=84aWtseb2-4 (skvidal, 19:43:38) * Open Floor redux (nirik, 19:43:42) * AGREED: daylight savings time is repealed. (nirik, 19:44:47) Meeting ended at 19:49:32 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (123) * skvidal (52) * pingou (42) * brundlfly (28) * puiterwijk (22) * abadger1999 (19) * threebean (15) * mdomsch (9) * G (6) * smooge (6) * cyberworm54 (5) * zodbot (4) * SmootherFrOgZ (4) * relrod (3) * maayke (1) * Adran (1) * rossdylan (1) * lmacken (0) * ricky (0) * dgilmore (0) * CodeBlock (0) -- 19:00:01 <nirik> #startmeeting Infrastructure (2013-02-28) 19:00:01 <zodbot> Meeting started Thu Feb 28 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 <nirik> #topic welcome to all 19:00:01 <nirik> #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean 19:00:01 <zodbot> The meeting name has been set to 'infrastructure' 19:00:01 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean 19:00:05 * abadger1999 here 19:00:10 * puiterwijk around 19:00:18 * Adran is alive 19:00:19 * maayke is here 19:00:26 <smooge> is here 19:00:29 * relrod is here 19:00:31 <relrod> kind of 19:00:40 * mdomsch 19:00:59 * pingou is here 19:01:19 * G is lurking 19:01:43 <abadger1999> G: Hey, welcome! 19:01:46 * skvidal is here 19:01:51 * rossdylan is here 19:01:52 * threebean is here 19:01:52 <nirik> hey G. Long time no see. ;) 19:02:03 <nirik> ok, lets go ahead and get started. 19:02:10 <nirik> #topic New folks introductions and Apprentice tasks. 19:02:23 <nirik> any new folks or apprentice questions or comments? 19:03:19 <nirik> ok then... 19:03:27 <nirik> do chime in anytime with questions or comments. ;) 19:03:33 <nirik> #topic Applications status / discussion 19:03:41 <nirik> Any application / development news? 19:03:47 <skvidal> coprs is back up and running 19:03:51 <pingou> \ó/ 19:03:59 <pingou> pkgdb-cli got a couple of releases 19:04:00 <skvidal> it is building - but still generating some instance-creation errors 19:04:04 <skvidal> which I'm trying to resolve 19:04:06 <puiterwijk> yes, if I do not find any new bugs, I will be declaring FAS-OpenID production-ready in five days from now 19:04:10 <abadger1999> Yay! 19:04:10 <skvidal> as always help on copr devel is quite welcome 19:04:14 <pingou> puiterwijk: cool! 19:04:38 <threebean> skvidal: getting closer to coprs+fedmsg here. phx2 is almost ready to receive. 19:04:41 <nirik> #info coprs is back up. One outstanding instance bug being worked. 19:04:48 <pingou> I worked on the api for the next generation pkgdb this week-end 19:04:48 <skvidal> threebean: great 19:04:50 <nirik> #info pkgdb-cli has had some new releases. 19:04:54 <nirik> puiterwijk: cool! 19:05:08 * cyberworm54 is here sorry 19:05:10 <abadger1999> fas update today. 19:05:13 <nirik> #info fas-openid is going to production in 5 days if no new stoppers found. 19:05:15 * SmootherFrOgZ is around 19:05:26 <pingou> pkgdb2-api got the "abadger1999 approved" stamp 19:05:28 <nirik> #info fas update planned for later today 19:05:43 <nirik> excellent 19:05:49 <abadger1999> I hope to get both a python-fedora nad a pkgdb update into stg sometime next week. 19:05:59 * abadger1999 crosses fingers that that isn't too ambitious :-) 19:06:22 * pingou is late on the jenkins stuff 19:06:36 <pingou> but jenkins has been running fine on the new cloud skvidal :) 19:06:54 <nirik> I've not noticed any issues with our apps from the rhel6.4 updates so far... 19:07:09 * mdomsch has more testing to do on MM1.4. Due to work and spring break, I likely won't get back at it much before 3/18 19:07:11 <skvidal> pingou: we will need to talk about that htis week - as I need to trade out the images it is running under 19:07:17 <skvidal> pingou: err - next week - not this week 19:07:27 <pingou> skvidal: sure 19:07:42 <nirik> #info fedocal has finished review 19:07:53 <nirik> mdomsch: :( anything we can do to help out there? 19:07:58 <pingou> oh yeah, that too thanks to threebean 19:08:10 <threebean> :) 19:08:30 <nirik> so we should look at a stg one soon... 19:08:39 <pingou> yup that would be very nice 19:08:45 <nirik> also, we can add it to the list of things to fedmsg... or is it already? 19:08:55 <mdomsch> nirik: I have 3 items left to check: 19:08:58 <threebean> nope, not on the list. 19:09:14 <nirik> we should make sure it's fedmsg aware before it goes to prod. 19:09:25 <nirik> also, should fas-openid have some fedmsg love? 19:09:26 <mdomsch> a) any changes to the apache config files that I don't have in master 19:09:32 <pingou> but we should stg it before :) 19:09:35 <mdomsch> b) test the database migration once again 19:09:40 <threebean> pingou: cool :) 19:09:47 <mdomsch> 3) test the location= code in the mirrorlists. That is brand new, straightforward, but never exercised 19:09:49 <puiterwijk> nirik: I can't see anything that we should do with fedmsg in fas-openid 19:09:52 <pingou> threebean: "we need to talk" 19:09:55 * mdomsch counts like click and clack 19:10:25 <threebean> "yes, we do" 19:10:33 * pingou scared of threebean 19:10:36 <mdomsch> all 3 can be done on app01.stg where it's installed now 19:10:37 <nirik> mdomsch: if you can send something to the list, we could try and find folks to work on those things... 19:10:38 <threebean> no! 19:10:38 <puiterwijk> threebean: you have any ideas for fedmsg in FAS-OpenID? I'd think not, because of the nature of the details 19:10:41 <mdomsch> k 19:11:16 <threebean> puiterwijk: yeah.. I had some "so and so logged in" message types in the very beginning, but we ended up throwing them out 19:11:25 <abadger1999> puiterwijk: yeah... I think we want to log to syslog but not fedmsg 19:11:37 <puiterwijk> abadger1999: it does log to syslog 19:11:41 * nirik is fine with that, just wanted to bring it up. 19:11:41 * threebean nods 19:12:02 <abadger1999> so that infra admins could review if there was some sort of security issue but not so that $random contributor can see who's logging in to where 19:12:15 <abadger1999> puiterwijk: Cool. 19:12:23 <puiterwijk> abadger1999: yep. it logs who logs in to which account, and which openid they claim, etc 19:12:25 <nirik> the only use case I can think of is: 19:12:51 <nirik> if we wanted to give a badge for using fas-openid X times... so we would need a message: user foo used fas-openid 19:13:28 <nirik> but we can always look at that down the road. 19:13:32 <nirik> there's much lower fruit 19:13:32 * threebean nods 19:13:38 * puiterwijk doesn't know if that's a good idea... 19:13:58 <puiterwijk> it might promote the use, but we do provide info that might be considered private 19:14:07 <puiterwijk> (not sure, just thinking out loud) 19:14:14 <nirik> sure, I would think it wouldn't say anything about what it was used for. but anyhow... 19:14:19 <nirik> any other application news? 19:14:37 <nirik> #topic Sysadmin status / discussion 19:14:43 <nirik> we did mass reboots last night... 19:14:50 <skvidal> and they mostly worked :) 19:14:51 <nirik> things went long sadly for a few reasons. ;( 19:14:59 <skvidal> *cough*log02*cough* 19:15:15 <nirik> I think the lv and guest renaming took a bit more time too. 19:15:19 <abadger1999> nirik, puiterwijk: If we did that badge, I'd store number of times X user logged into fas-openid in its db. then emit that after a set point is met. 19:15:27 <skvidal> nirik: but is fantastic that it got done 19:15:35 <nirik> yes, I agree. 19:15:42 <puiterwijk> abadger1999: yeah, agreed on that. but I don't like to announce every signon 19:15:51 <nirik> anyhow, everything should mostly be upgraded to rhel 6.4, so do shout if you see any problems. 19:16:28 <puiterwijk> also, the lb repo has been added. if anyone finds a host that has haproxy, but doesn't have the rhel6-lb repo, also shout please 19:16:37 <nirik> upcoming I do hope to work on ansible promoting. :) If fires would stay out for a while. 19:16:39 <puiterwijk> (it should be on proxy0* and busmon0*) 19:16:43 * nirik nods. 19:17:29 <skvidal> nirik: question - have we had any progress on fas-clients PUSH? 19:17:39 <nirik> not sure. abadger1999 / SmootherFrOgZ ? 19:17:46 <abadger1999> SmootherFrOgZ: ^ 19:18:01 * abadger1999 guesses SmootherFrOgZ has been working on the fas otp stuff, though. 19:18:15 <nirik> no worries. 19:18:25 <SmootherFrOgZ> skvidal: yeah, I'm working on it. Actually I thinking on rewriting fas-client 19:18:48 <skvidal> SmootherFrOgZ: ok 19:19:11 <SmootherFrOgZ> skvidal: you will be able to fas-client against specific group as well 19:19:18 <nirik> so that would push out via ansible? or fas would push it? 19:19:51 <skvidal> nirik: I was thinking it would generate what a host set needs 19:19:56 <skvidal> and shove it via ansible on change 19:20:01 <SmootherFrOgZ> yeah 19:20:02 <skvidal> that was the idea, I think 19:20:12 * nirik couldn't recal the details. 19:20:15 <nirik> sounds reasonable. 19:20:57 <nirik> ok, any other sysadmin news? 19:21:11 <nirik> #topic Private Cloud status update / discussion 19:21:25 <skvidal> moving persistent instances over to openstack 19:21:27 <skvidal> that's moving apace 19:21:31 <nirik> cool. 19:21:33 <skvidal> and we may have a fix for the resizing issue in qcow 19:21:40 <skvidal> I've not tested it yet - yesterday kinda went sideways 19:21:53 <skvidal> however, it looks promising 19:21:54 <nirik> yeah, hopefully that will work for us. 19:22:03 <skvidal> I'm working on cleaning up the playbooks for them 19:22:09 <nirik> it's a package that does resize in initramfs 19:22:23 <skvidal> and all the keys/access codes needed for openstack are on lockbox 19:22:34 <skvidal> that piece works now for transient and persistent instances 19:22:42 <skvidal> coprs is building there and generating instances as well 19:22:57 <nirik> excellent. 19:23:00 <skvidal> if/when the ec2 tagging api for openstack starts working/existing - we'll take that on 19:23:07 <skvidal> I talked to some folks about setting up a second cinder service 19:23:10 <skvidal> on another server 19:23:14 <skvidal> for having more persistent volume space 19:23:21 <skvidal> and the general answer is 'yes should work, not tried it' 19:23:24 <skvidal> which is quaint :) 19:23:30 <brundlfly> Hi, sorry that I am late but can I still introduce myself? 19:23:33 <nirik> we seem to get that a lot. ;) 19:23:42 <nirik> brundlfly: sure, welcome. ;) Chime right in. 19:23:59 <skvidal> but once I get things off of fed-cloud03 - I think bringing it up as a new compute node and cinder volume server would be a good test for us 19:24:14 <nirik> sounds good . 19:24:21 <brundlfly> My name is Daniel and I am currently a second year University student in 19:24:21 <brundlfly> a Computing and Information systems program. What I can offer is basic 19:24:22 <brundlfly> scripting in Bourne, Bash, and Python. I have more advanced skills in 19:24:22 <brundlfly> Java programming since this is the main language is used in my 19:24:22 <brundlfly> University program. I spend additional time with reading Linux related 19:24:22 <brundlfly> literature such as "The Linux Administration Handbook" and the "Linux 19:24:24 <brundlfly> Programming Interface". The latter inspired me learn the C language so I 19:24:28 <brundlfly> can apply the concepts I have learned and experiment with kernel system 19:24:30 <brundlfly> calls. I also work part time as Technical Support Representative in a 19:24:32 <brundlfly> Cable/Internet Company. 19:24:34 <brundlfly> My goal for the next 3 years is to become a Software Developer with good 19:24:36 <brundlfly> coding practice and a solid foundation in algorithmic computation and 19:24:38 <brundlfly> design patterns. I have a keen interest in the kernel structure and the 19:24:40 <brundlfly> lower level aspect of hard- and software communication. I want to 19:24:42 <brundlfly> contribute to the team that provided me with an operation system that 19:24:44 <brundlfly> gave me possibilities to be as creative as I wanted to be - and that is 19:24:46 <brundlfly> for free. I want to become a valuable member of this community and I 19:24:48 <brundlfly> want to be known for my commitment and skill. I will join the fedora 19:24:50 <brundlfly> meetings on a regular basis to get the big picture of what is going on 19:24:52 <brundlfly> right know. I cannot always attend the meeting since I work and 19:24:54 <brundlfly> day/night shift rotations, but I'll do my best. 19:25:06 * pingou has read this somewhere before :) 19:25:17 <threebean> brundlfly: cool, welcome. 19:25:23 <pingou> welcome brundlfly :) 19:25:29 <brundlfly> thanks you guys 19:25:31 * cyberworm54 waves 19:25:33 <nirik> brundlfly: just FYI, on irc folks typically use pastebins and provide a link. :) 19:25:36 <nirik> but welcome. 19:26:06 <nirik> and if you have questions do ask. ;) 19:26:15 <brundlfly> as soon as I know what a pastebin is I will stop pasting 30 lines into the chat :) 19:26:19 <abadger1999> brundlfly: Are you interested in working on sysadmin stuff or programming (mostly python) stuff? 19:26:23 <brundlfly> IRC is still somewhat new to me 19:26:43 <brundlfly> Both programming and sys admin are my focus 19:26:51 <nirik> http://paste.fedoraproject.org/ <- paste your content there, submit and then just paste the url it gives to the channel, then everyone can load it and see it. ;) 19:27:01 <skvidal> brundlfly: #fedora-apps is a great place - lots of programming tasks that interact with systems stuff 19:28:04 <nirik> brundlfly: cool. Do look at our apprentice program and see if thats something you might be interested in, if so, see me after meeting in #fedora-admin: http://fedoraproject.org/wiki/Infrastructure_Apprentice 19:28:06 <brundlfly> Right know I study the C language to get a better understanding of memory allocation, my plan was to move on to Python (Shouldn't be that hard to switch) since it it very popular in open source 19:28:24 <abadger1999> brundlfly: <nod> You can talk to nirik/skvidal/smooge about straight sysadmin stuff in #fedora-admin and #fedora-noc #fedora-apps and #fedora-admin for more of the apps/programming lmacken. pingou, threebean, puiterwijk, SmootherFrOgZ, and I are all available there. 19:28:25 * nirik nods. python is very popular around here. 19:28:50 <brundlfly> I would like to learn more about the apprentice program 19:29:27 <abadger1999> brundlfly: relrod is currently probably doing the most splitting of his time between sysadmin and apps side. 19:29:28 <nirik> excellent. 19:29:39 <nirik> shall we move on to upcoming items? 19:29:49 <nirik> #topic Upcoming Tasks/Items 19:29:50 <relrod> abadger1999: :) 19:30:01 <nirik> (get ready for info dump) 19:30:03 <nirik> #info 2013-02-28 end of 4th quarter 19:30:03 <nirik> #info 2013-03-01 nag fi-apprentices 19:30:03 <nirik> #info 2013-03-07 remove inactive apprentices. 19:30:03 <nirik> #info 2013-03-19 to 2013-03-26 - koji update 19:30:03 <nirik> #info 2013-03-29 - spring holiday. 19:30:04 <nirik> #info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze 19:30:05 <nirik> #info 2013-04-16 F19 alpha release 19:30:07 <nirik> #info 2013-05-07 to 2013-05-21 BETA infrastructure freeze 19:30:09 <nirik> #info 2013-05-21 F19 beta release 19:30:11 <nirik> #info 2013-05-31 end of 1st quarter 19:30:13 <nirik> #info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. 19:30:15 <nirik> #info 2013-06-25 F19 FINAL release 19:30:17 <nirik> is there anything folks would like to schedule or note? 19:30:26 <abadger1999> threebean, lmacken, and I are going to be at pycon us march 12 through the 21st. network was pretty good last year but of course, we'll all be busy with lots of other stuff so you probably don't want to count to heavily on us for that week and a half 19:30:29 <puiterwijk> #info 2013-03-05 Maybe FAS-OpenID release 19:30:38 * nirik adds those things. 19:31:22 <nirik> anything else pending? 19:31:27 <nirik> well, that we can schedule... ;) 19:31:36 <pingou> fedocal? :) 19:31:38 <threebean> lots of unscheduled good stuff :) 19:31:47 <nirik> yeah, lots of irons in the fire. ;) 19:31:58 <nirik> pingou: I can make a stg anytime, unless you want to wait for ansible... 19:32:28 <pingou> nirik: well my puppett isn't great but if we team up let's go for it 19:32:37 <nirik> sure, it should be pretty simple... 19:32:40 <nirik> I would think 19:32:45 <puiterwijk> pingou: I can help with the puppet part 19:33:00 <puiterwijk> (I already did FAS-OpenID in puppet, which is also flask) 19:33:19 <nirik> cool. 19:33:21 <pingou> it is pretty simple, the rpm and 2 files basically (and generating the DB) 19:33:22 <nirik> we can get it done. ;) 19:33:38 <nirik> #topic Open Floor 19:33:51 <nirik> anyone have anything for open floor? general questions, comments? 19:34:12 <pingou> I found back what I wanted to talk about last week 19:34:15 <pingou> GSoC 19:34:32 <nirik> #topic GSoC 19:34:38 <pingou> Do we want? Do we have ideas? Do we have someone looking at this? 19:34:48 <nirik> There's often lots of ideas related to infrastructure put forth. 19:34:54 <nirik> but some of them are... not things we want. ;) 19:35:20 <nirik> I mentored last year, I think I would prefer to not this year... it was a fair bit of time. 19:35:29 <nirik> but if any others would like to, please do. 19:35:46 <nirik> https://fedoraproject.org/wiki/GSOC_2013 19:35:57 <pingou> last year with abadger1999 we teamed up 19:36:03 <pingou> so that's always an option 19:36:09 * abadger1999 would rather not mentor (at least full time) either. I'll definitely help integrate anyone into infra/answer questions/ review pull requests. 19:36:10 <pingou> and it does reduces the load a bit 19:36:37 <abadger1999> yeah, teaming with pingou was good. 19:36:42 <nirik> we could discuss on list perhaps? and then find out who is interested? 19:36:49 <pingou> +1 19:37:29 <threebean> mizmo might be organizing for Fedora OPW candidates for this summer again too 19:37:30 <nirik> pingou: you want to send an email on that? 19:37:37 <threebean> I think the time slot coincides with GSOC 19:37:45 <pingou> nirik: sure I can do that 19:38:04 <nirik> threebean: ok, good to know. We shouldn't over subscribe ourselves. 19:38:08 * threebean nods 19:38:34 <skvidal> nirik: question for the future 19:38:44 <skvidal> nirik: daylight savings time is coming up soon 19:38:50 <skvidal> what time will this meeting be? 19:39:03 <nirik> good question. 19:39:13 <nirik> I don't personally care. We can move with the time change or not. 19:39:16 <puiterwijk> same time UTC? 19:39:34 <nirik> I'd think sticking to the same time utc would be least confusing 19:39:48 <pingou> I'd go for let's just keep it at the current time 19:39:58 <pingou> there will be one week of confusion, then it's back on track 19:40:21 <puiterwijk> pingou: but the confusion is only for those who change times soon 19:40:36 <pingou> puiterwijk: us :) 19:40:38 <nirik> the only problem with keeping it the same is that it may mess with people's lunch schedules. 19:40:39 * skvidal has no idea what time it is in the next couple of weeks 19:40:42 <nirik> but I'm flexable. 19:40:44 <puiterwijk> pingou: no, we were in December, weren't we? 19:40:48 <smooge> it is already on my lunch 19:41:04 * cyberworm54 missed lunch for the meeting :) 19:41:23 <pingou> puiterwijk: I must miss-knowledge there 19:41:35 <puiterwijk> pingou: I believe our times change in December and June, and US is coming up soon? 19:41:36 <pingou> err lack* 19:41:36 <nirik> so, sticking with same time might be good for folks. ;) 19:41:48 <pingou> puiterwijk: afaik in the US it is one week after us 19:42:02 <puiterwijk> pingou: oh? /me is checking now... 19:42:11 <skvidal> we're march 10th, I think 19:42:12 <nirik> pingou: how does fedocal handle things? ;) 19:42:13 * skvidal googles 19:42:22 <pingou> nirik: all times are stored in UTC 19:42:32 <skvidal> yah march 10th 19:42:43 <nirik> pingou: excellent. 19:42:44 <pingou> nirik: but I must say, I do wonder how that will go :) 19:42:45 <puiterwijk> pingou: you are correct... we change march 31th 19:42:54 <skvidal> for the US - except for AZ and indianna? and parts of NM? and hawaii? 19:43:00 <nirik> right. 19:43:02 * skvidal cannot even remotely recall the ass-brained exceptions 19:43:07 <nirik> not indiana anymore. 19:43:10 * cyberworm54 live in indianapolis... 19:43:15 <pingou> Dr jones 19:43:17 <nirik> just az and hawaii. 19:43:30 <nirik> anyhow. 19:43:35 * puiterwijk hates timezones, and also changing of timezones... 19:43:38 <skvidal> http://www.youtube.com/watch?v=84aWtseb2-4 19:43:40 <skvidal> there you go 19:43:42 <nirik> #topic Open Floor redux 19:43:45 <smooge> oooh a reason to move to hawaii 19:43:49 <skvidal> that explains it in copious details 19:43:52 <nirik> anything further for open floor? 19:43:53 <skvidal> smooge: couldn't you just move to AZ 19:43:58 <nirik> smooge: fudcon hawaii! 19:44:00 <pingou> skvidal: +1000!! 19:44:04 <skvidal> nirik: I'd like to recommend repealing daylight savings time 19:44:05 <smooge> the politics gives me a rash 19:44:05 <pingou> nirik: +1000²! 19:44:20 <skvidal> nirik: could we get that started here? 19:44:28 <nirik> sure, all in favor? :) 19:44:33 <skvidal> aye 19:44:35 <pingou> oeuf corse! 19:44:39 <cyberworm54> yes! 19:44:42 <G> Just a quick re-introduction from myself that I'm thinking of lurking around again :) 19:44:47 <nirik> #agreed daylight savings time is repealed. 19:44:49 <pingou> spot is in as well! 19:44:59 <pingou> nirik: I was voting for the FUDCon in Hawaii 19:45:04 <nirik> G: welcome back, go ahead. 19:45:19 <G> nirik: can we amend the proposal that timezones be repealed? :) 19:45:38 <nirik> when it's high noon there, it's high noon everywhere! :) 19:45:39 <smooge> G is the best guy ever 19:46:18 <smooge> actually G I think you would have been able to answer our problems with the bnfs(old bkoji) storage... 19:46:32 <G> So for those that don't remember me from back in '08/'09-ish my name is Nigel, I'm back out in New Zealand, main interests are in Adminish stuff (although I'm now working on development stuff) 19:46:42 <G> err development stuff = dayjob :) 19:46:46 * pingou remembers G 19:47:31 <G> smooge: hmmm bnfs sounds like a vaguely familiar hostname :) 19:47:35 <nirik> anyhow, welcome back G. 19:47:52 <skvidal> die bnfs, die 19:47:55 <skvidal> oh, sorry 19:47:57 <abadger1999> :-) 19:48:28 <nirik> speaking of bnfs01... it's copying along: 12T 8.0T 3.7T 69% /mnt/kojibackup 19:48:35 <skvidal> yay? 19:48:41 <nirik> yep. yay. 19:48:50 <nirik> ok, if nothing else will close out the meeting in a minute... 19:49:25 <nirik> thanks for coming everyone. 19:49:32 <nirik> #endmeeting

1 0

Summary/Minutes from today's FESCo Meeting (2013-02-27)
by Kevin Fenzi 27 Feb '13

27 Feb '13

=================================== #fedora-meeting: FESCO (2012-02-27) =================================== Meeting started by nirik at 18:00:07 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-02-27/fesco.2013-02-27… . Meeting summary --------------- * init process (nirik, 18:00:07) * #979 Features process proposal: Track features in bugzilla (nirik, 18:02:43) * LINK: https://fedorahosted.org/fesco/ticket/979 (nirik, 18:02:43) * AGREED: FESCo is ok to go with whichever tracker the program manager would like (nirik, 18:11:24) * #1028: tor package concerns (nirik, 18:12:54) * LINK: https://fedorahosted.org/fesco/ticket/1028 (nirik, 18:12:54) * LINK: https://lists.fedoraproject.org/pipermail/devel/2013-February/179163.html (jamielinux, 18:19:11) * LINK: https://fedorahosted.org/fpc/ticket/243 for the record (mitr, 18:22:19) * LINK: https://fedorahosted.org/fesco/ticket/347 (daumas, 18:25:37) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=532373 (pwouters, 18:28:16) * AGREED: remove Enrico from tor maintainership (+6,0,0) (nirik, 18:48:13) * 1091 NRM: Request ownership change for mediawiki (nirik, 18:49:02) * LINK: https://fedorahosted.org/fesco/ticket/1091 (nirik, 18:49:02) * LINK: https://admin.fedoraproject.org/pkgdb/users/packages/athimm?acls=owner are the 27 packages by the way (nirik, 18:53:59) * AGREED: make daumas (mooninite) the maintainer and solicit for co-maintainers for the owner's other packages. (+5,0,0) (nirik, 18:54:44) * next week chair (nirik, 18:55:06) * sgallagh to chair next week (nirik, 18:56:06) * Open floor (nirik, 18:56:10) * ACTION: sgallagh to fix mediawiki119 mistake (sgallagh, 18:58:13) * LINK: https://fedorahosted.org/fesco/ticket/985 (nirik, 19:00:41) * ACTION: abadger1999 to ping on python3 pillow bug (nirik, 19:02:36) Meeting ended at 19:03:39 UTC. Action Items ------------ * sgallagh to fix mediawiki119 mistake * abadger1999 to ping on python3 pillow bug Action Items, by person ----------------------- * abadger1999 * abadger1999 to ping on python3 pillow bug * sgallagh * sgallagh to fix mediawiki119 mistake * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (92) * mitr (40) * pwouters (31) * sgallagh (30) * abadger1999 (26) * pjones (24) * jamielinux (23) * jwb (17) * t8m (11) * zodbot (8) * jreznik (8) * mattdm (6) * daumas (5) * mmaslano (0) * notting (0) -- 18:00:07 <nirik> #startmeeting FESCO (2012-02-27) 18:00:07 <zodbot> Meeting started Wed Feb 27 18:00:07 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:07 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:07 <nirik> #meetingname fesco 18:00:07 <nirik> #chair abadger1999 jwb mitr mmaslano notting nirik pjones t8m sgallagh 18:00:07 <nirik> #topic init process 18:00:07 <zodbot> The meeting name has been set to 'fesco' 18:00:07 <zodbot> Current chairs: abadger1999 jwb mitr mmaslano nirik notting pjones sgallagh t8m 18:00:13 <nirik> who all is around? 18:00:15 <mitr> Hello 18:00:38 <pwouters> (me) 18:01:24 <jamielinux> (me) 18:01:25 <mattdm> (me) 18:01:30 * sgallagh is here 18:01:38 * abadger1999 here 18:01:40 <sgallagh> Apologies if I drop out, I'm on a train 18:01:55 <jwb> i'm here 18:01:58 <pjones> hello. 18:02:36 <nirik> ok, I guess lets go ahead and dive in... 18:02:43 <nirik> #topic #979 Features process proposal: Track features in bugzilla 18:02:43 <nirik> .fesco 979 18:02:43 <nirik> https://fedorahosted.org/fesco/ticket/979 18:02:45 <zodbot> nirik: #979 (Features process proposal: Track features in bugzilla) – FESCo - https://fedorahosted.org/fesco/ticket/979 18:03:17 <nirik> I guess my thought here is to do whatever the program manager would prefer, try it and if it fails, try something else? :) 18:03:42 <mattdm> as the person proposing this idea, yeah, I can get behind that :) 18:03:43 <sgallagh> I can get behind that 18:04:00 <abadger1999> +1 18:04:08 <t8m> hi all, sorru for being late 18:04:10 <mitr> I generally agree with that 18:04:18 <jwb> i'm going to get to the side of it 18:04:22 <sgallagh> Is jreznik in favor of this? 18:04:22 <nirik> I can see advantages and disadvantages to trac or bugzilla. 18:04:37 <nirik> He's prefering trac at the moment. 18:04:45 <mattdm> yep. As I said in the bug, I prefer bugzilla, but I prefer trac to nothing 18:04:51 <sgallagh> worksforme 18:05:10 <sgallagh> mattdm: I think I prefer Trac, honestly. Fedora has more control to tweak it if we need to 18:05:13 <t8m> I actually prefer trac 18:05:38 <mitr> Do we keep this open, or close it and let jreznik come up with a specific proposal, or something else? 18:05:47 <jreznik> sorry for being late 18:05:48 <mattdm> To me, the big advantage of bugzilla is the ability to link *directly* to actual-work bugs 18:05:55 <mitr> (I might be overthinking the "proposal" part) 18:05:57 <nirik> trac has problems, but so does bugzilla. I think we should look at trying something and fail faster. ;) 18:05:58 <pjones> I've never thought trac does a good job - it does a lot of simple things badly, like making urls in titles not clickable 18:06:14 <mattdm> which means that once set up, it's low overhead to keep up-to-date rather than being Yet Another Thing to update 18:06:42 <jreznik> does anybody know anything about that devconf proposal marcela was talking about? 18:06:50 <mitr> jreznik: next week 18:06:52 <sgallagh> mitr: Can we just close it with "agreed with a minor addendum"? 18:07:26 <mitr> sgallagh: any of the three options works for me 18:07:30 <sgallagh> s/Can/Should/ 18:07:35 <jreznik> nirik: well both are not a good tracking tools, trac is more, bz is less but... 18:07:35 <nirik> so, proposal: go with whatever option the program manager would like to try? 18:07:44 <nirik> jreznik: agreed. :( 18:07:59 <t8m> nirik, +1 18:08:05 <jreznik> and I see mattdm's point 18:08:14 <mitr> nirik: +1. Just please make sure this gets announced/incorporated into the planning process 18:08:39 <sgallagh> nirik: +1 18:08:46 <nirik> sure, and perhaps we should dicuss more details on the options, but that doesn't need to be here... 18:09:02 <jreznik> nirik: yep, definitely 18:09:30 * jreznik is not open/closed for any good idea how to track it - wiki is even worst than bz/trac 18:09:58 <jreznik> is open is better and not against any viable option :) 18:10:08 <nirik> so, thats +4 for the proposal? other votes? 18:10:20 <jwb> which proposal? 18:10:25 <nirik> so, proposal: go with whatever option the program manager would like to try? 18:10:33 <jwb> yeah, +1 18:11:12 <jreznik> of course in coop with fesco 18:11:24 <nirik> #agreed FESCo is ok to go with whichever tracker the program manager would like 18:11:46 <pjones> yeah, +1 18:12:03 <nirik> thanks jreznik. I suppose we could discuss the options on list, but there might be a lot of bikeshedding. 18:12:41 <nirik> anyhow, moving on... 18:12:54 <nirik> #topic #1028: tor package concerns 18:12:54 <nirik> .fesco 1028 18:12:54 <nirik> https://fedorahosted.org/fesco/ticket/1028 18:12:55 * mattdm gets out his bikeshed paint 18:12:57 <zodbot> nirik: #1028 (tor package concerns) – FESCo - https://fedorahosted.org/fesco/ticket/1028 18:13:06 <nirik> mattdm: but what colour is it? ;) 18:13:19 <nirik> anyhow, I reopened this because I still have a concern... 18:13:42 <nirik> The maintainer doesn't want to push security impacting updates to stable without karma. 18:13:52 <pwouters> (i can voice an opinion too if that's appropriate) 18:14:02 <nirik> pwouters: sure. 18:14:06 <pjones> pwouters: go ahead. 18:14:18 <pwouters> this has been going on for about 3 years now. in different ways 18:14:21 <nirik> jamielinux: Your input would be welcome too. 18:14:28 <jamielinux> nirik: Great. 18:14:45 <pwouters> i am very close with upstream, and they totally gave up and now strongly recommend not using fedora/epel packages 18:15:06 <nirik> pwouters: is that from them being out of date? or some other issue? 18:15:10 <pwouters> this has gone on against everyone's but a single person's (enrico) interest 18:15:29 <pwouters> out of date, patches that degrade security from upstream's point of view, 18:15:40 <pwouters> weirdness like different init susb systems 18:15:54 <pwouters> there's like 50+ emails in the archive about tor packaging (and actually clamav packaging) 18:16:14 <jamielinux> (e.g. https://lists.fedoraproject.org/pipermail/devel/2013-February/178407.html ) 18:16:28 <pwouters> fesco kind of forced the co-maintainer 18:16:44 <pwouters> who then did work, then the maintainer just revered without talking to the comaintainer 18:16:46 <nirik> For the record, jamielinux is who was added as a tor comaintainer. 18:16:55 <pwouters> so i am dont think the current solution is working 18:17:06 <sgallagh> I'm not sure I'd want to make a general ruling on security updates here, but in the case of the Tor package (whose only reason for existence is to enhance anonymity) I think it might be reasonable to recommend that it push to stable with the timeout 18:17:26 <jwb> frankly, i don't think focusing on tor is going to solve the problem 18:17:34 <jwb> the problem is the maintainer, not the package. 18:17:40 <pjones> yeah :/ 18:17:58 <jamielinux> I was quite disheartened after my changes were all reverted. 18:17:59 <mitr> For updates, I'd be surprised if we were able to come up with a general rule, it'll always involve human judgment. We can just emphasise Fedora's preference to stay with upstream 18:18:04 <pwouters> yes. the comaintainer was supposed to mostly fix the maintainer issue. not the issue of whatever is happening today or tomorrow 18:18:14 <sgallagh> True, should we perhaps send a sternly-worded email about collaborating with comaintainers? 18:18:14 <nirik> FYI, when f16 went eol: 18:18:18 <nirik> 141 https://admin.fedoraproject.org/updates/FEDORA-2012-14654/tor-0.2.2.39-1600… 18:18:21 <nirik> 141 days 18:18:37 <mitr> jamielinux: I have reviewed the commit, and I would have probably reverted it as well. The split version is much better. 18:18:39 <sgallagh> And then revoke his rights if he doesn't shape up? 18:18:57 <mitr> sgallagh: ^^ 18:19:09 <jamielinux> Just for the record, I have just posted a split patch series here: 18:19:11 <jamielinux> https://lists.fedoraproject.org/pipermail/devel/2013-February/179163.html 18:19:21 <jamielinux> I have no doubt that Enrico will revert almost all of them however. 18:19:24 <sgallagh> mitr: Wait, so it wasn't just a revert? I misunderstood the problem, then 18:19:36 <jamielinux> I have not applied any of these in git yet, as I see no point. 18:19:43 <pwouters> mitr: while i agree attacking whitespace could have waited, the whole "non fedora init" style should be ripped out 18:19:50 <mitr> sgallagh: Look at http://pkgs.fedoraproject.org/cgit/tor.git/commit/?id=dcca5c196a47528c40b45… , it shows how large the thing was 18:19:52 <sgallagh> jamielinux: I don't think it's our job to pre-approve your patches. 18:19:56 <mitr> pwouters: yes 18:19:59 <pwouters> it should have been ripped at when it was initng 18:20:07 <jamielinux> sgallagh: No, I wasn't suggesting that. Just posting here for the record. 18:20:11 * sgallagh nods 18:20:19 <nirik> mitr: yeah, although really... it's not that big. I would have been able to view the diff... 18:20:36 <mitr> IMHO all the %{?fedora} conditionalizing should be generally forbidden - just use git branches and merge. 18:20:53 <pwouters> the core issue is, the tor package is for the fedora community, not for enrico. Enrico is mixing this up. He should follow package guidelines. He's refused to comply for over 3 years. 18:20:57 <mitr> OTOH we have asked FPC recently about support for other init systems, and they decided that they don't want to forbid them 18:21:35 <pjones> mitr: yeah, but %{?fedora} is something we've never really taken a strong stance on 18:21:45 <mitr> pjones: And I understand we probably won't. 18:21:47 * nirik notes upstart is now dead/blocked in rawhide 18:21:54 <nirik> and f18 18:21:55 <mitr> Too many people find it more convenient than branches. 18:21:59 <jamielinux> The tor spec contains a tor-upstart package that isn't built, which I assume is fine by our guidelines as I couldn't find any guidance. 18:22:11 <pjones> jamielinux: yeah, I think that's an okay thing to do. 18:22:19 <mitr> https://fedorahosted.org/fpc/ticket/243 for the record 18:22:26 <jamielinux> pjones: Sure, that's what I assumed. 18:22:56 <pwouters> also: tor security updates are vital. and should not be delayed willy nilly 18:23:14 <nirik> anyhow, in the past when we have had issues like this we have selected a mediator... do we want to do that here? Or ask ensc some questions directly? or ? 18:24:33 <pwouters> mediation is good. provided there is an action if it fails 18:24:47 <pwouters> I'm reminded of last time fesco got involved with tor packaging. nothing ended up changing 18:25:02 <pjones> yeah, that's the thing we want to avoid happening again. 18:25:04 * nirik doesn't recall that... I know we have talked about clamav several times. 18:25:26 * mitr finds https://fedorahosted.org/fesco/ticket/347 18:25:28 <pjones> Might be worth having a mediator and expecting that mediator to come to us with resolution or at least strong recommendations within a couple of weeks. 18:25:36 <pwouters> nirik: I met up with upstream at GSoC a few years ago, and filed like 8 bugs needing fixing. 18:25:37 <daumas> https://fedorahosted.org/fesco/ticket/347 18:26:50 <pwouters> i think that ticket is from _after_ I gave up on it all 18:27:06 <mitr> Well, mediator... I kind of think we know what we want to achieve here already, it's just that we don't have (and don't want to set up) guidelines backing it 18:27:07 <nirik> ah yeah. Now I remember that one. 18:27:29 <abadger1999> mitr: what do we want to achieve here? 18:27:38 <pjones> mitr: you're suggesting that somebody else should be maintaining these packages? 18:28:13 <mitr> abadger1999: 1) updates to this specific package going out soon enough to make upstream content, 2) not insisting on packaging peculiarities 18:28:16 <pwouters> https://bugzilla.redhat.com/show_bug.cgi?id=532373 18:28:23 * nirik would like timely updated packages that upstream is happy to recommend to users. 18:28:39 <t8m> nirik, +1 18:28:43 <t8m> me as well 18:28:55 <mitr> pjones: I don't think that's strictly necessary, no. But talk about "mediators" and "cooperation" when we want to say "rip this out" is confusing the issue 18:29:27 * abadger1999 agrees with mitr's sentiment of being clear 18:29:28 <t8m> mitr, in 2) you mean who should not insist? fedora or enrico? 18:29:54 <pwouters> (not in that bz that Roger Dingledine is upstream) 18:29:59 <pwouters> s/not/note 18:30:00 <mitr> Perhaps we might consider overruling FPC on https://fedorahosted.org/fpc/ticket/243 (and/or forbidding upstrart and allowing sysvidinit, since upstrart never existed that much),... 18:30:15 <abadger1999> mitr: Uhmm... 18:30:16 * nirik oddly sees tor was not in the mass rebuild? 18:30:24 <abadger1999> mitr: I'd prefer you didn't go at it in that manner :-) 18:30:30 <mitr> abadger1999: yeah 18:31:08 <mitr> abadger1999: I see the difficulty - it's just that seeing "you can have packaging that nobody else needs" and "we don't like how tor is packaged" is not consistent. 18:31:26 * abadger1999 notes that ensc's method of enabling upstart is definitely.... idiosyncratic. 18:31:31 <mitr> t8m: "allowing the package to remove bits that only make it more complex for comaintainers" 18:31:59 <t8m> mitr, I am still not getting it 18:32:21 <abadger1999> he's not using parallel installable init scripts for different systems... he's using bcond_with/without to make the build conditionalized via command line arguments 18:32:36 <abadger1999> so you'll never get the non-default behaviour in the fedora build system. 18:32:56 <abadger1999> only if you build the package locally with your own set of command line arguments to rpmbuild 18:33:00 <jamielinux> Yes, the tor-upstart package is not built by default. 18:33:12 <jamielinux> Though the spec is horribly lengthy and confusing with all of the custom stuff. 18:33:28 <jamielinux> After my most recent patch series, the length drops from 250 to 150. 18:33:35 <jamielinux> And is *much* easier to grok. 18:33:40 * nirik nods. 18:33:50 <jamielinux> But spec legibility is subjective. 18:33:50 <pwouters> yeah because three years ago there was hell and fire because you needed to install "tor-sysvinit" to get tor. and that fight caused enrico to fix it so "yum install tor" would get the default init system 18:34:00 <pjones> jamielinux: sure, but less is usually more. 18:34:06 <pwouters> but that also took weeks of fighting :/ 18:34:20 <pwouters> again. the specific package detail is not the problem. The maintainer is. 18:34:22 <abadger1999> I think the fpc made a ruling about something similar (macros for use on non-fedora OS's [like suse openbuildsystem]) and said that those macros should not be used.... but that ruling was in the first few years of fedora. 18:34:26 <jwb> again, the problem is basically that you have a primary maintainer treating a package as a fifedom and pissing all over anything anyone else tries 18:34:30 <pjones> But all of this is just a side-show. 18:34:36 <jwb> so focus on the maintainer, not the damn pacakge 18:34:54 <pjones> The problem FESCo needs to address isn't each individual package change that needs to go through - it's the fact that the maintainer is actively stopping things from getting better. 18:34:55 <abadger1999> jamielinux: I think legibility is a huge thing. 18:35:14 <jamielinux> abadger1999: I agree with you 100%. 18:35:30 <nirik> right, so one thing I think we might want to look at documenting/whatever is the fact that packages you maintain are not yours. You are simply a caretaker. You shouldn't treat them as your own thing and reject things that make them easier to hand on to others. 18:35:31 <sgallagh> pjones: And that's supposed to be FESCo's job (I kid) 18:35:32 <abadger1999> jamielinux: the fact that ensc can jsutify reverting the patch solely on the "impossible to review" grounds points at problems in the current spec's readability. 18:35:35 <t8m> either we have the "balls" to kick enrico out of being primary tor maintainer or we should probably accept his "style" in spec unless it is not conflicting the guidelines 18:36:10 <mitr> pjones: I'm not too keen on using that revert as a basis for our decision. 18:36:28 <jwb> mitr, then use the combined history of the maintainer's actions 18:36:30 <pjones> mitr: that's not the only example that's been cited though. 18:36:41 <pjones> and do note that this is a /recurring/ problem. 18:36:44 <pwouters> mitr: how about upstream recommendation that fedora packages for to should not be used? 18:36:47 <jwb> why on earth do we suddenly have tunnel vision when we have to possibly talk to a human about their behavior? 18:36:48 <pwouters> is that a better indication? 18:36:49 <mitr> abadger1999: No, the patch mixes about 8 separate changes; that's problematic regardless of what you are patching 18:37:19 <mitr> pjones: Right, I was reading your comment too narrowly. Sorry 18:37:25 <abadger1999> mitr: It's certainly no worse than a new package review, though. 18:38:02 * nirik notes we are at 24min on this topic. 18:38:04 <jwb> proposal: remove Enrico from tor maintainership 18:38:39 * jamielinux would like to mention he did feel at fault for the massive commit and whitespace changes that weren't fully required, and was kicking himself after. But did feel Enrico didn't handle the situation well either. 18:39:00 <abadger1999> jwb: +1 18:39:08 * nirik is a reluctant +1. 18:39:12 * abadger1999 notes that he's also willing to vote for "lesser" proposals. 18:39:19 * pjones is also a +1 , though wishes it hadn't come this far. 18:39:41 <mitr> 0. I think I'm still looking for a less radical fix, although I can see the case for a +1 18:40:18 <nirik> we could ask him to apply the split out patches, and push security updates stable... 18:40:27 <nirik> but not sure that would fully solve things. 18:40:29 <pjones> mitr: if you have any suggestions for a less radical fix, now is the time. 18:40:48 <pjones> nirik: if we're going to tell him how to maintain the package, what's the point of leaving him in place as maintainer? 18:40:50 <mitr> the best I can think of as a counter-proposal is "FESCo wants tor updates to go out timely enough from now on, and is willing to remove maintainership over this issue" 18:40:57 <mitr> Which is really not great 18:41:10 <sgallagh> I'm still not quite well enough informed to decide. Can someone give me the 30-second explanation of why tor has to see Fedora-specific patches on a regular basis vs. rebasing? Does it go against our stable updates policy in some way? 18:41:10 <nirik> pjones: yeah. 18:41:13 <jamielinux> pjones: I absolutely agree with your second comment. 18:41:27 <jamielinux> pjones: And there is a long history too.. 18:41:52 <nirik> sgallagh: it's not fedora specific. Tor updates, ensc updates the package, it sits in updates-testing. It doesn't get +3 karma, it never goes stable. 18:41:59 <mitr> pjones: Well, "telling others how to maintain the package" is the whole point of packaging guidelines... and what we want never was in them 18:42:15 <pjones> mitr: no, there's a difference between setting guidelines and saying "make these changes". 18:42:16 <nirik> the package itself has lots of issues preventing it from easily being managed by co-maintainers. 18:42:17 <pwouters> i've been involved with a few rounds with this issue. I like being nice and doing another round, but I dont think it will work. enrico showed not the least bit of cooperation willingness in years 18:43:02 <jamielinux> nirik: Yes, making this patch series was a lot more work than I anticipated, with bits of the spec all over the palce. 18:43:29 <jamielinux> nirik: Not that I mind putting in the work to fix the package.. 18:43:40 * sgallagh really doesn't want to be the swing vote on this, but I suppose staying at 0 would be an implicit -1. 18:43:54 <sgallagh> We have a comaintainer who is willing to do the work needed, so I guess I'm a weak +1 18:44:03 <mitr> sgallagh: Give me a minute... 18:44:39 <sgallagh> If enrico later demonstrates he can play well with others, he can always request to be re-added as a comaintainer 18:44:42 * nirik waits for a counterproposal from mitr 18:44:52 <pwouters> actually, I will also go back to Roger at upstream and see about bringing theirs and our packages back togehter, so they can stop shipping rpms and tell people to not use fedora packages 18:45:16 <t8m> I'd be willing to give +1 if there was a clear response (or clear ignorance) from enrico that he is not willing to change his maintenance style of tor even if we remove it from him forcibly if he doesn't 18:45:31 <mitr> After looking at bugzilla a bit more, I'm +1 to the proposal 18:45:47 <mitr> t8m: What swayed me was the CVE bugs in CLOSED/WONTFIX - EOL 18:46:00 <pjones> mitr: yeah, that's incredibly bad. 18:46:13 <nirik> ok, lets see... thats +7? 18:46:45 <jwb> someone points out the CWG arguably exists for things liek this 18:46:51 <jwb> i've yet to see CWG actual exist though 18:46:55 <jwb> so... 18:47:24 <nirik> so, thats +6, and t8m's conditional +1, which I guess is 0 or -1 for the proposal? 18:47:31 <abadger1999> jwb: yeah -- -ENOTIMe on my part and I think this may have progressed beyond CWG already. 18:47:45 <t8m> nirik, rather 0 18:47:49 <nirik> t8m: ok. 18:47:51 <jwb> for the record: i do not take pleasure in proposing this, but i think it needs to be done 18:48:04 <jwb> if i had any thoughts something else would work, i would have proposed that instead 18:48:13 <nirik> #agreed remove Enrico from tor maintainership (+6,0,0) 18:48:25 <nirik> I assume we can orphan it and jamielinux will pick it up? 18:48:44 <jwb> yes 18:48:47 <nirik> jwb: I'm in the same boat. Its a sad state. :( 18:48:51 <nirik> anyhow, moving on then... 18:49:00 * jamielinux would like to thank everyone here for the discussion, input and advice. 18:49:02 <nirik> #topic 1091 NRM: Request ownership change for mediawiki 18:49:02 <nirik> .fesco 1091 18:49:02 <nirik> https://fedorahosted.org/fesco/ticket/1091 18:49:03 <zodbot> nirik: #1091 (NRM: Request ownership change for mediawiki) – FESCo - https://fedorahosted.org/fesco/ticket/1091 18:49:13 <daumas> (I'm mooninite FYI) 18:49:24 <nirik> welcome daumas 18:49:43 <nirik> since the maintainer hasn't responded, I'm fine moving ownership here. 18:49:46 <mitr> I think this is a pretty clear-cut case for the NRM process, just that we didn't handle this on the mailing list. 18:49:55 * mitr apologizes for not reacting there 18:50:09 <nirik> We may want to consider if other of the maintainers packages should also be orphaned or co-maintainers added. 18:50:56 <pjones> I think we should probably solicit co-maintainers for them. 18:51:03 <sgallagh> pjones: +1 18:51:07 <nirik> do we even need a vote on mediawiki? should be pretty clear under the policy. 18:51:12 <pwouters> (not having mediawiki1XX packages strongly recommended) 18:51:27 <nirik> we still likely need them for epel, but yeah. 18:51:35 <mitr> nirik: It needs an explicit ACK from >=1 FESCo member 18:51:45 <sgallagh> mitr: I'll ack it 18:52:07 <mitr> sgallagh: you were faster :) 18:52:09 <daumas> pwouters: could those packages be blocked for fedora only? they were never reviewed for fedora. only epel 18:52:09 <nirik> would someone like to manage soliciting co-maintainers for the other packages of theirs? 18:52:19 <pjones> proposal: make daumas (mooninite) the maintainer and solicit for co-maintainers for the owner's other packages. 18:52:22 <nirik> daumas: most if not all of them should be already 18:52:51 <pjones> (whether we need a vote or not, we're already discussing it and having a record can't hurt) 18:53:17 <sgallagh> daumas: That came up on the mailing list some time ago. They accidentally filtered in from rawhide (which wasn't dead.package like it should have been) 18:53:18 <nirik> sure, +1 18:53:25 <sgallagh> I'm in favor of killing it and blocking the packages 18:53:34 <daumas> nirik, sgallagh: ok thanks 18:53:51 <sgallagh> pjones: +1 18:53:59 <nirik> https://admin.fedoraproject.org/pkgdb/users/packages/athimm?acls=owner are the 27 packages by the way 18:54:00 <mitr> pjones: +1. 18:54:16 <t8m> pjones, +1 18:54:44 <nirik> #agreed make daumas (mooninite) the maintainer and solicit for co-maintainers for the owner's other packages. (+5,0,0) 18:54:51 <nirik> anything else on this topic? 18:54:59 <daumas> thanks for your time, gentlemen 18:55:06 <nirik> #topic next week chair 18:55:15 <nirik> who wants the shiny gavel? 18:55:54 <sgallagh> nirik: I think it's my turn 18:55:54 <nirik> anyone? 18:56:00 <nirik> cool. thanks sgallagh 18:56:06 <nirik> #info sgallagh to chair next week 18:56:10 <nirik> #topic Open floor 18:56:14 <nirik> any items for open floor? 18:56:24 <sgallagh> Can we vote on blocking those mediawikiXXXX packages from Fedora? 18:56:44 <nirik> I don't think there would be any objection. 18:57:00 <pjones> sgallagh: dude, whatever. 18:57:02 <sgallagh> I don't either, but it's good to have a record of decisions 18:57:28 <nirik> all of them are blocked except 119 18:57:31 <nirik> and that was a mistake. ;) 18:57:33 <sgallagh> If no one is objecting, I'll just shut up and go do it 18:57:43 <abadger1999> .whoowns mediawiki119 18:57:43 <zodbot> abadger1999: smooge 18:57:58 <abadger1999> sgallagh: yeah, mistake, just do it. 18:58:13 <sgallagh> #action sgallagh to fix mediawiki119 mistake 18:59:18 <abadger1999> Just a note that any help on this cleanup would be appreciated: https://fedoraproject.org/wiki/User:Toshio/Devendorize_desktop_files#List_o… 18:59:36 <abadger1999> halfway done, but half still to go. 19:00:16 <nirik> abadger1999: I noticed we still have that python-pillow ticket open. 19:00:21 <nirik> does that need to be anymore? 19:00:32 <abadger1999> Hmm.. 19:00:39 <abadger1999> So there is one question around that ticket I think 19:00:41 <nirik> https://fedorahosted.org/fesco/ticket/985 19:00:56 <abadger1999> dmalcolm hasn't responded on the bug against python3 19:00:59 <nirik> ok 19:01:36 <nirik> anything else from anyone? will close out in a minute if not. 19:01:39 <abadger1999> Do we want to ask him what's going on with that in some official capacity? 19:01:55 <nirik> a ping on the bug might be nice. 19:02:08 <abadger1999> k. I'll put on a fesco hat and ask. 19:02:36 <nirik> #action abadger1999 to ping on python3 pillow bug 19:03:36 <nirik> ok, thanks for coming everyone. 19:03:39 <nirik> #endmeeting

1 0

FAmNA Meeting (26 February 2013)
by inode0 26 Feb '13

26 Feb '13

====================== #fedora-meeting: FAmNA ====================== Meeting started by inode0 at 02:01:37 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-02-27/famna.2013-02-27… . Meeting summary --------------- * Roll Call (inode0, 02:01:52) * Announcements (inode0, 02:03:54) * inode0 won't be available for the meeting next week on March 5 - so someone will need to commit to run it (inode0, 02:04:35) * ACTION: chanchito to update ticket 326 with shipping information ASAP (inode0, 02:31:17) * ACTION: chanchito to contact some folks to see about getting more speakers for NELF (inode0, 02:31:42) * ACTION: Someone to pay the $500 sponsorship ASAP (inode0, 02:31:59) * Tickets (let's pretend we set this 30 minutes ago) (inode0, 02:35:52) * Open Floor (inode0, 02:37:31) Meeting ended at 02:50:43 UTC. Action Items ------------ * chanchito to update ticket 326 with shipping information ASAP * chanchito to contact some folks to see about getting more speakers for NELF * Someone to pay the $500 sponsorship ASAP Action Items, by person ----------------------- * chanchito * chanchito to update ticket 326 with shipping information ASAP * chanchito to contact some folks to see about getting more speakers for NELF * **UNASSIGNED** * Someone to pay the $500 sponsorship ASAP People Present (lines said) --------------------------- * chanchito (72) * inode0 (40) * rbergeron (39) * nb (22) * dan4o8 (7) * zodbot (6) * lcameron (1) John

1 0

2013-02-25 - Fedora QA Meeting - recap
by Adam Williamson 26 Feb '13

26 Feb '13

As always, minutes and IRC transcript available on the wiki at https://fedoraproject.org/wiki/QA/Meetings/20130225 Next meeting is scheduled for 2013-03-04 at 1600 UTC in #fedora-meeting. If you have topics you think we should bring up at the meeting, please add them to the Wiki page at https://fedoraproject.org/wiki/QA/Meetings/20130304 . Thanks! TOPIC: Previous meeting follow-up ======================================================================= * adamw to write a second draft (of the automatic blocker proposal) with andre's proposed changes and stronger explanation not to put 'grey area' bugs in the automatic blocker list - this was done[1] * We agreed that second draft is ready to go into production * adamw to draft up changes to the blocker bug meeting SOP for 3-hour hard limit, no-reviews-during-qa-meetings, and a dedicated channel for meetings, send to list for further discussion - this was done[2] * j_dulaney, tflink, viking-ice, jreznik all vote +1 on changes: adamw would like more releng/devel feedback before going to production * viking-ice to discuss the 'smoke test for spins' idea further with nirik and cwickert - not yet done TOPIC: Call for Test Days ======================================================================= * tflink suggests an upgrade test day, but notes issues with timing - we can try to co-ordinate with wwoods to handle that TOPIC: Trac tickets CCed to list ======================================================================= * viking-ice notes the qa trac was originally intended solely as a 'qa task management' thing, not for devel * Everyone agrees in general that having the bugs in QA trac and the discussion spammed to test@ is a bad idea * tflink will weigh various possible responses and make a detailed proposal to the list TOPIC: Open floor ======================================================================= N/A ACTION ITEMS ======================================================================= * adamw to push 'automatic blocker' proposal to production * adamw to try and gather a bit more feedback on blocker process changes this week * viking-ice or adamw to file a trac ticket for the smoke- test-for-spins idea * tflink to take a look at the question of tracking qa tool discussion and bugs/tickets and make a broad proposal about what to do 1. https://lists.fedoraproject.org/pipermail/test/2013-February/113909.html 2. https://lists.fedoraproject.org/pipermail/test/2013-February/113910.html -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

Compte rendu de la réunion du mardi 26 févier 2013
by Kévin Raymond 26 Feb '13

26 Feb '13

Bonsoir à tous, Le CR est disponible : http://meetbot.fedoraproject.org/fedora-meeting-1/2013-02-26/fedora-fr.2013… Cdt -- Kévin Raymond (shaiton) GPG-Key: A5BCB3A2

1 0

FAmSco meeting 2013-02-25 minutes
by Christoph Wickert 25 Feb '13

25 Feb '13

Minutes: http://meetbot.fedoraproject.org/fedora-meeting-2/2013-02-25/famsco.2013-02… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-2/2013-02-25/famsco.2013-02… Log: http://meetbot.fedoraproject.org/fedora-meeting-2/2013-02-25/famsco.2013-02… Meet you again next week Monday March 4th at 17:00 UTC in #fedora-meeting! Regards, Christoph ==================================== #fedora-meeting-2: FAmSCo 2013-02-25 ==================================== Meeting started by cwickert at 17:01:27 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-2/2013-02-25/famsco.2013-02… . Meeting summary --------------- * Roll call (cwickert, 17:01:41) * Clint sent regrets and cannot attend, Jiri is probably not coming either. He worked hard for the Red Hat Developer Conference and took a day of today (cwickert, 17:05:56) * present: aeperezt bckurera cwickert tuanta (cwickert, 17:06:20) * Announcements (cwickert, 17:06:29) * LINK: https://fedorahosted.org/famsco/report/9 (cwickert, 17:07:51) * LINK: https://fedoraproject.org/wiki/FUDCon:Bid_for_Cusco_2013 (tuanta, 17:11:19) * LINK: https://fedoraproject.org/wiki/FUDCon:Bid_for_Managua_2013 (viperboy001, 17:11:26) * LINK: http://fedoraproject.org/wiki/FUDCon:Bid_for_Managua_2013 (tuanta, 17:11:26) * FUDCon LATAM bids (cwickert, 17:24:56) * LINK: http://fedoraproject.org/wiki/FUDCon:Valencia_2012 (wporta, 17:37:01) * FAmSCo recommends Cusco for hosting the FUDCon LATAM 2013 (cwickert, 17:47:58) * FAmSCo dedicates to supporting the efforts of yn1v_neville for a FAD (cwickert, 17:48:38) * LINK: https://fedoraproject.org/wiki/FedoraNi (viperboy001, 17:50:00) * support the Fedora School events of the Fedora Nicaragua community. More info at https://fedoraproject.org/wiki/FedoraNi (cwickert, 17:50:59) * RH Community Credit Card holder for APAC (cwickert, 17:55:11) * ACTION: cwickert to ask KageSenshi if he is willing to manage a credit card (cwickert, 18:08:30) * ACTION: cwickert to send an email to KageSenshi to ask him to hold the community card for APAC (tuanta, 18:10:02) * Open Floor (cwickert, 18:23:21) Meeting ended at 18:28:22 UTC. Action Items ------------ * cwickert to ask KageSenshi if he is willing to manage a credit card * cwickert to send an email to KageSenshi to ask him to hold the community card for APAC Action Items, by person ----------------------- * cwickert * cwickert to ask KageSenshi if he is willing to manage a credit card * cwickert to send an email to KageSenshi to ask him to hold the community card for APAC * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * cwickert (176) * tuanta (71) * aeperezt (54) * viperboy001 (33) * bckurera (26) * wporta (19) * yn1v_neville (16) * nb (15) * zodbot (13) * alexove (7) * yn1v (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Fedora Chinese Meeting Minutes (2013-02-22)
by Alick Zhao 22 Feb '13

22 Feb '13

Hi all, The IRC meeting minutes tonight are available at here[1]. Thanks everyone for attending the meeting. Especially let's thank endle for taking the chair and host the meeting when alick is not available! In the meeting we mainly talked about Fedora translation issues and task. The next IRC meeting will be held on next Friday (2013-03-01). Please come and join the discussion if you can! [1] http://meetbot.fedoraproject.org/fedora-zh/2013-02-22/fedora-zh.2013-02-22-… -- Alick Fedora 18 (Spherical Cow) user https://fedoraproject.org/wiki/User:Alick

1 0

Summary/Minutes from today's Fedora Infrastructure meeting (2013-02-21)
by Kevin Fenzi 21 Feb '13

21 Feb '13

============================================ #fedora-meeting: Infrastructure (2013-02-21) ============================================ Meeting started by nirik at 19:00:01 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-02-21/infrastructure.2… . Meeting summary --------------- * welcome y'all (nirik, 19:00:01) * New folks introductions and Apprentice tasks. (nirik, 19:02:15) * new easyfix tasks welcome, team members are encouraged to try and file tickets for them. (nirik, 19:05:28) * Applications status / discussion (nirik, 19:06:17) * pingou has vastly simplified the pkgdb db. (nirik, 19:07:42) * new pkgdb-cli pushed out as well as copr-cli (nirik, 19:08:16) * fas release being tested in staging, for 2013-02-28 release to prod. (nirik, 19:08:57) * askbot is now sending fedmsg's. (nirik, 19:11:56) * more fas-openid testing welcome. Has worked for those folks that have tried it so far. (nirik, 19:15:29) * fedocal ready for 1.0 tag and review process. (nirik, 19:16:16) * LINK: http://elections-dev.cloud.fedoraproject.org/ (abadger1999, 19:16:30) * testing on new elections version welcome: http://elections-dev.cloud.fedoraproject.org/ (make account in fakefas) (nirik, 19:17:04) * will try out an f18 server for mm3 staging testing and feel out an updates policy, etc. Possibly using snapshots more. (nirik, 19:33:27) * will look at moving fas-openid to prod as soon as is feasable. (nirik, 19:33:46) * feedback on github reviews of all commits welcome. (nirik, 19:39:04) * mirrormanager update to 1.4 soon. (nirik, 19:39:11) * Sysadmin status / discussion (nirik, 19:43:00) * smooge got our bnfs01 server's disks working again. (nirik, 19:43:56) * nagios adjustments in progress (nirik, 19:44:30) * arm boxes will get new net friday hopefully (nirik, 19:45:07) * mass reboot next wed (tenative) for rhel 6.4 upgrades. (nirik, 19:47:52) * Private Cloud status update / discussion (nirik, 19:52:50) * euca cloudlet limping along after upgrade. (nirik, 19:55:11) * work on going to bring openstack cloudlet up to more production (nirik, 19:55:26) * please see skvidal if you want to get involved in our private cloud setup (nirik, 20:01:29) * Upcoming Tasks/Items (nirik, 20:01:33) * 2013-02-28 end of 4th quarter (nirik, 20:01:44) * 2013-03-01 nag fi-apprentices (nirik, 20:01:44) * 2013-03-07 remove inactive apprentices. (nirik, 20:01:44) * 2013-03-19 to 2013-03-26 - koji update (nirik, 20:01:44) * 2013-03-29 - spring holiday. (nirik, 20:01:44) * 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze (nirik, 20:01:46) * 2013-04-16 F19 alpha release (nirik, 20:01:48) * 2013-05-07 to 2013-05-21 BETA infrastructure freeze (nirik, 20:01:50) * 2013-05-21 F19 beta release (nirik, 20:01:52) * 2013-05-31 end of 1st quarter (nirik, 20:01:54) * 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. (nirik, 20:01:56) * 2013-06-25 F19 FINAL release (nirik, 20:01:58) * Open Floor (nirik, 20:02:49) Meeting ended at 20:04:14 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (143) * skvidal (99) * abadger1999 (47) * pingou (24) * abompard (15) * smooge (10) * mdomsch (10) * threebean (6) * zodbot (5) * SmootherFrOgZ (4) * cyberworm54 (4) * lmacken (2) * maayke (1) * ricky (0) * dgilmore (0) * CodeBlock (0) -- 19:00:01 <nirik> #startmeeting Infrastructure (2013-02-21) 19:00:01 <zodbot> Meeting started Thu Feb 21 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:01 <nirik> #topic welcome y'all 19:00:01 <nirik> #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean 19:00:01 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean 19:00:13 * skvidal is here 19:00:15 <nirik> hello everyone. whos around for an infrastructure meeting? 19:00:15 <smooge> not guilty 19:00:23 * cyberworm54 is here 19:00:25 * lmacken 19:00:26 * threebean is kinda here 19:00:28 * maayke is here 19:00:33 * abadger1999 here 19:00:40 * pingou here 19:00:52 * SmootherFrOgZ here 19:02:08 <nirik> ok, I guess lets go ahead and dive in... 19:02:15 <nirik> #topic New folks introductions and Apprentice tasks. 19:02:30 <nirik> any new folks like to introduce themselves? or apprentices with questions or comments? 19:03:04 <cyberworm54> Hi I am an apprentice and hopefully I can learn and contribute as much as I can 19:03:31 <nirik> welcome (back) cyberworm54 19:03:57 <cyberworm54> Thanks! 19:04:01 <nirik> to digress a bit... do folks think our apprentice setup is working well? or is there anything we can do to improve it? 19:04:20 <nirik> I think the biggest problem is new people getting up to speed and finding things they can work on. 19:04:52 <skvidal> nirik: also - we have a fair amount more code-related tasks than general admin tasks that newcomers can get into 19:04:56 <nirik> we are also low on new easyfix tickets, particularly in the sysadmin side. 19:05:02 <nirik> yeah. 19:05:14 <cyberworm54> it is a bit ...confusing but once you get to the docs and actually read it you have a start point 19:05:28 <nirik> #info new easyfix tasks welcome, team members are encouraged to try and file tickets for them. 19:06:06 <nirik> ok, moving on then I guess. 19:06:17 <nirik> #topic Applications status / discussion 19:06:27 <nirik> any application / development news this week or upcoming? 19:06:46 <pingou> I've been doing some cleanup on the pkgdb db scheme 19:06:49 <pingou> before: http://ambre.pingoured.fr/public/pkgdb.png 19:06:57 <pingou> after: http://ambre.pingoured.fr/public/pkgdb2.png 19:07:25 <pingou> that's with the help of abadger1999 :) 19:07:29 <nirik> wow. nice! 19:07:29 <lmacken> nice ☺ 19:07:42 <nirik> #info pingou has vastly simplified the pkgdb db. 19:07:46 * abadger1999 just reviews and makes suggestions to what pingou writes ;-) 19:07:54 <pingou> pushed a new version of pkgdb-cli (waiting to arrive in testing) and pushed upstream a new version of copr-cli 19:08:16 <nirik> #info new pkgdb-cli pushed out as well as copr-cli 19:08:19 <abadger1999> New fas release is finally out the door. Planning to upgrade production on Feb 28. 19:08:29 <pingou> abadger1999 and I have started to think about pkgdb2 basically, schema update is the first step 19:08:56 <abadger1999> pkgdb -- yeah, and pkgdb2 api is probably going to be the second step 19:08:57 <nirik> #info fas release being tested in staging, for 2013-02-28 release to prod. 19:09:19 <abadger1999> as a note for admins -- the fas release that introduced fedmsg introduced a bug that you should know about 19:09:40 <SmootherFrOgZ> btw, there's a bunch of locale fixes in the new fas release 19:09:41 <abadger1999> email verification when people change their email address was broken. 19:09:50 <nirik> thats the one we have in prod, but we have hotfixed it right? 19:10:00 <SmootherFrOgZ> would good to test fas with different languages 19:10:32 <nirik> cool. 19:10:39 <abadger1999> it would change the email when the user first entered the updated email in the form instead of waiting for them to confirm that the received the verification email. 19:10:45 <nirik> I saw in stg that it also has the 'no longer accept just yubikey for password' in. 19:11:37 <threebean> askbot got fedmsg hooks in production this week. there are some new bugs to chase down regarding invalid sigs and busted links.. 19:11:41 <nirik> any other application news? oh... 19:11:56 <nirik> #info askbot is now sending fedmsg's. 19:11:58 <threebean> Latest status -> http://www.fedmsg.com/en/latest/status/ 19:12:08 <skvidal> fedmsg.com? wow 19:12:25 <nirik> Has anyone had a chance to test patrick's fas-openid dev instance? any feedback for him? 19:12:26 <abadger1999> nirik: Hmm... looks like production isn't hotfixed. 19:12:30 <skvidal> threebean: what's the status on fedmsg emitters from outside of the vpn? 19:12:35 <abadger1999> nirik: but next fas release will have the fix. 19:12:40 <nirik> abadger1999: :( I thought we did. ok. 19:12:47 <threebean> skvidal: no material progress yet, but I've been thinking it over. 19:12:50 <abadger1999> Can we wait until Thursday? 19:13:01 <skvidal> threebean: okay thanks 19:13:04 <threebean> skvidal: I have some janitorial work to do.. then that's next on my list. 19:13:21 <skvidal> threebean: that's the limiting factor for adding notices from coprs, I think 19:13:29 <nirik> abadger1999: I suppose 19:14:12 * threebean nods 19:14:18 <abadger1999> I've used fas-openid but not tested it heavily. It has worked and looks nice. puiterwijk has a flask-fas-openid auth plugin that he's tested and converted fedocal, IIRC, to use it. 19:14:41 <nirik> yeah, it's worked for me for a small set of sites I tested. 19:15:22 <pingou> speaking of fedocal, I need to tag 0.1.0 and put it up for review 19:15:29 <nirik> #info more fas-openid testing welcome. Has worked for those folks that have tried it so far. 19:15:41 <pingou> the current feature requests will have to wait for the next release... 19:15:57 <nirik> pingou: yeah. Will be good to get it setup. :) 19:16:15 <abadger1999> Oh, fchiulli has a new version of elections that's ready for some light testing 19:16:16 <nirik> #info fedocal ready for 1.0 tag and review process. 19:16:24 <pingou> abadger1999: oh cool! 19:16:30 <abadger1999> http://elections-dev.cloud.fedoraproject.org/ 19:16:31 <nirik> abadger1999: cool. Is there an instance up? 19:16:34 <nirik> nice. 19:16:44 <skvidal> nirik: should be 19:16:48 <abadger1999> You need to make an account on fakefas in order to try it out. 19:17:04 <nirik> #info testing on new elections version welcome: http://elections-dev.cloud.fedoraproject.org/ (make account in fakefas) 19:17:06 <abadger1999> Please do try it out. 19:17:06 <skvidal> abadger1999: is elections switching to fas-openid, too? 19:17:24 <pingou> abadger1999: and the code is ? 19:17:45 <abadger1999> skvidal: I believe it is using flask-fas right now because flask-fas-openid isn't in a released python-fedora yet. 19:18:03 <abadger1999> pingou: https://github.com/fedora-infra/elections 19:18:14 <skvidal> abadger1999: got it 19:18:19 <pingou> abadger1999: great 19:18:20 <skvidal> abadger1999: thx 19:18:36 <abadger1999> np 19:18:47 <nirik> I have one more application type thing to discuss... dunno if abompard is still awake, but we should discuss mailman3. ;) 19:18:51 <abadger1999> I am all for moving more things over to the flask-fas-openid plugin though. 19:19:15 * nirik is too. 19:19:33 <nirik> anyhow, we are looking at setting up a mailman3 staging to do some more testing and shake things out. 19:19:41 <nirik> however, mailman3 needs python 2.7 19:19:43 <abompard> nirik: yeaj 19:20:06 <nirik> so, it seems: a) rhel6 + a bunch of python rpms we build and maintain against python 2.7 19:20:12 <nirik> or b) fedora 18 instance 19:20:30 <smooge> abadger1999, congrats on election stuff 19:20:38 <abompard> yes, and MM3 really does not work on python 2.6, sadly 19:20:47 * pingou question: which one will be out first: EL7 or MM3? :-p 19:20:55 <nirik> we are starting to have more fedora in our infra (for example, the arm builders are all f18) 19:21:09 <nirik> so, we might want to come up with some policy/process around them. Like when do to updates, etc. 19:21:09 <abadger1999> smooge: thanks. It was all fchiulli though :-) I told him he can be the new owner of the code too :-) 19:21:13 <abompard> I've already rebuilt an application for a non-system python, and it's not much fun 19:21:33 <smooge> bwahahahah 19:21:33 <abompard> as in non-scriptable 19:21:58 <nirik> yeah, it's pain either way... 19:21:59 * abadger1999 thinks fedora boxes are going to be preferable to non-system python. 19:22:07 <pingou> +1 19:22:09 <skvidal> nirik: an idea 19:22:11 <nirik> I'm leaning that way as well. 19:22:16 <abompard> by the way, Debian has a strange but nifty packaging policy for python package that make them work with all the installed versions of python 19:22:21 <smooge> I think we should make a bunch of servers rawhide 19:22:40 <skvidal> abompard: I assume the db /data for mm3 is all separate from where it needs to run, right 19:22:46 <abadger1999> abompard: yeah -- I've looked at the policy but not hte implementation. But every time I've run it by dmalcolm, he's said he doesn't like it. 19:23:04 <abadger1999> abompard: i think some of that might be because he has looked at the implementation :-) 19:23:05 <abompard> abadger1999: understandably, it's symlink-based 19:23:17 <abompard> skvidal: yeah, to some extent 19:23:23 <skvidal> nirik: I wonder if we could have 2 instances - talking to the same db - so we could update f18 to latest - run mm3 on it in r/o mode - to make sure it is working 19:23:27 <abompard> skvidal: it has local spool directories 19:23:30 <skvidal> nirik: then just pass the ip over to the other one 19:23:40 <nirik> in the past we have been shy of fedora instances because of the massive updates flow I think, as well as possible bugs around those updates. I think it's gotten much better in the last few years (I like to think due to the updates policy, but hard to say) 19:23:59 <skvidal> nirik: which is why I was thinking we don't do updates to the RUNNING instance 19:24:07 <skvidal> we just swap out the instance that is in use/has that ip 19:24:08 <abadger1999> ... or less contributors? /me ducks and runs 19:24:16 <nirik> :) 19:24:22 <skvidal> nirik: so we test the 'install' 19:24:24 <nirik> skvidal: right, so a extra level of staging? 19:24:31 <skvidal> nirik: one level, really 19:24:32 <abompard> skvidal: I don't know how MM3 will handle a read-only DB 19:24:37 <skvidal> prod and staging 19:25:02 <nirik> well, right now we are talking about a staging instance only, but yeah, I see what you mean. we could do something along those lines. 19:25:17 <nirik> I also think for some use cases it's not as likely to break... 19:25:36 <nirik> ie, for mailman, postfix and mailman and httpd all need to work, but it doesn't need super leaf nodes right? 19:25:39 <skvidal> abompard: understood 19:26:02 <skvidal> nirik: anyway - just an idea 19:26:04 <skvidal> nirik: ooo - actually 19:26:13 <skvidal> nirik: I just had a second idea that you will either hate or love 19:26:14 <nirik> where as for something like a pyramid app, it would be a much more complex stack 19:26:16 <skvidal> nirik: snapshots 19:26:16 <abompard> skvidal: we may get bugs because of that, not because of the upgrade 19:26:30 <skvidal> nirik: we snapshot the running instance in the cloud 19:26:32 <nirik> yeah, we could do that too. 19:26:32 <skvidal> nirik: upgrade it 19:26:36 <skvidal> and if it dies - roll it out 19:27:04 <abompard> for the moment it will only be low-traffic lists anyway 19:27:22 <abompard> and I must check that, but if MM is not running, I think postfix keeps the message 19:27:30 <abadger1999> skvidal: how would that work in terms of data? would we keep the db and local spool directory separate from the snapshots? 19:27:33 <abompard> and re-delivers when MM starts 19:27:34 <skvidal> abompard: yes 19:27:35 <nirik> FWIW, I run f18 servers at home here, and they have been pretty darn stable. (as they were when f17... earlier releases had more breakage from my standpoint) 19:27:41 <skvidal> err 19:27:41 <skvidal> abadger1999: yes 19:27:44 <abadger1999> Cool. 19:28:11 <skvidal> abadger1999: no reason we can't have a mm3-db server in the cloud :) 19:28:12 * abadger1999 kinda likes that. although possibly he just doesn't know all the corner cases there :-) 19:28:16 <nirik> yeah. I'm sure we could do something with snapshots. 19:28:21 <skvidal> anyway - just an idea 19:28:23 <skvidal> nothing in stone 19:28:27 <nirik> yeah. 19:29:06 <nirik> also, for updates, we may just do them on the same schedule as rhel ones, unless something security comes up in an exposed part... ie, just look at the httpd, etc not the entire machine. 19:29:42 <nirik> anyhow, all to be determined, we can feel out a policy. 19:29:49 <nirik> anything else on the applications side? 19:29:56 <abadger1999> I have two more 19:30:00 <abadger1999> Do we have a schedule for getting fas-openid into production? 19:30:28 <nirik> abadger1999: I think it's ready for stg for sure now... but not sure when prod... 19:30:58 <nirik> I'm fine with rolling it out as fast as we are comfortable with. 19:31:03 <nirik> I'd like to see it get more use. ;) 19:31:04 <abadger1999> I think we're coming along great. But if we're going to start migrating apps to use fas-openid/telling people to use it when developing their apps (like elections), then we need to have a plan for getting it into prod 19:31:09 <abadger1999> <nod> 19:31:19 <abadger1999> nirik: it's setup to replace the current fas urls? 19:31:34 <nirik> abadger1999: not fully sure on that. I think so... 19:31:36 * abadger1999 was wondering if we could deploy it and just not announce it for a few weeks 19:31:46 <nirik> thats a thought. 19:32:22 <abadger1999> alright -- I guess let's talk about htis more on Friday after our classroom session with puiterwijk :-) 19:32:26 <nirik> Oddly I have noticed that for things like askbot you get two different "users" with different urls. 19:32:28 <nirik> yeah 19:33:05 <abadger1999> Other thing is for all the devs here, how's the "review all changes" idea working out? 19:33:27 <nirik> #info will try out an f18 server for mm3 staging testing and feel out an updates policy, etc. Possibly using snapshots more. 19:33:39 <abadger1999> I've liked how it works with pingou, puiterwijk, and SmootherFrogZ for fas, python-fedora, and packagedb. 19:33:46 <nirik> #info will look at moving fas-openid to prod as soon as is feasable. 19:33:55 <skvidal> abompard: how much space do you need on the mm server itself - if you are not storing the db there? 19:33:59 <abadger1999> lmacken: Is it working okay for bodhi and such too? 19:34:07 <abadger1999> anything that's falling through the cracks? 19:34:14 <abompard> skvidal: I need to check that 19:34:21 <nirik> skvidal: if we are doing this as a real staging, we might want to just make a real 'lists01.stg.phx2' virthost instead of cloud? 19:34:26 <pingou> abompard: I defintevely like it 19:34:53 <abadger1999> Do we want to say that certain things are okay to push without review? (making a release would be a candidate...I was going to suggest documentation earlier but pingou found a number of problems with my documentation patch :-) 19:34:53 <pingou> abadger1999: ^ :) 19:34:54 <skvidal> nirik: okay - I didn't know if we wanted to be cloud-er-fic about it or not 19:35:01 <skvidal> nirik: thx 19:35:31 <nirik> skvidal: yeah, I'm open to either, but I think right now until we have less fog in our clouds, a real one might be better for this... but either way 19:35:53 <skvidal> nirik: well - with attached persistent volumes - using one of the qcow imgs is non-harmful 19:35:55 <nirik> abadger1999: I like seeing the extra review. I've not done much reviewing myself. ;) 19:36:06 <abompard> skvidal: not much, a few hudred MB 19:36:08 <skvidal> nirik: but I agree about fog 19:36:17 * abadger1999 notes that threebean is in another meeting but said he still likes the idea but hasn't done it consisstently all the time. So more experimentation with it needed. 19:36:43 * abadger1999 liked that nb reviewed a documentation update the other day :-) 19:37:02 <pingou> I think it can bring us new contributor 19:37:21 <pingou> some of them are easyfix 19:37:31 <pingou> other are bigger and then might need more experienced reviewers 19:37:57 <nirik> yeah 19:38:21 <nirik> welcome mdomsch 19:38:41 <abadger1999> Yeah. I agree. it's nice to have someone else's eyes on the bigger fixes even if they're relatively new too, though. It's better than before where I would have committed it without any review at all. 19:38:49 <mdomsch> better late than never 19:38:51 <nirik> that reminds me, mdomsch was going to look at updating mm in prod to 1.4 on friday... if not then, then sometime soon. ;) 19:39:04 <nirik> #info feedback on github reviews of all commits welcome. 19:39:11 <mdomsch> anyone have any grief with doing a major MM upgrade tomorrow afternoon? 19:39:11 <nirik> #info mirrormanager update to 1.4 soon. 19:39:47 <abadger1999> mdomsch: If you're around in case it goes sideways it would be very nice. 19:39:51 <mdomsch> everything I know I've broken, I've fixed. Now it's time to test in production. :-) 19:39:52 <nirik> I think it should be fine. We can be somewhat paranoid and not touch one of the apps so we have an easy fallback. 19:40:11 <abadger1999> get the fixes in that you've had pending and get us onto a single codebase for development. 19:40:13 <mdomsch> k 19:40:25 <nirik> (until we are sure the others are all working right I mean) 19:40:31 <mdomsch> right 19:40:34 <mdomsch> so bapp02, then app01 19:40:47 * nirik nods. 19:40:48 <mdomsch> and I'll stop the automatic push from bapp02 to app* 19:40:58 <nirik> sounds good. 19:41:00 <mdomsch> until we're comfortable. Worst case, we have slightly stale data for a few hours 19:41:21 * nirik nods. 19:41:28 <abadger1999> instead of "if you're around" it would'vs been clearer for me to say "as long as you're around" :-) 19:41:43 <nirik> mdomsch: you've picked up all the hotfixes into 1.4 right? 19:41:46 <mdomsch> abadger1999: naturally; I'm not around nearly as much 19:41:56 <abadger1999> Yeah. we miss you ;-) 19:42:16 <nirik> abadger1999: +1 :) 19:42:40 <nirik> anyhow, any other application news? or shall we move on? 19:43:00 <nirik> #topic Sysadmin status / discussion 19:43:06 <mdomsch> nirik: yes I pulled them all in while at FUDCon 19:43:17 <nirik> lets see... this week smooge was out at phx2 for a whirlwind tour. 19:43:22 <nirik> mdomsch: cool. 19:43:45 <nirik> #info smooge got out bnfs01 server's disks working again. 19:43:51 <nirik> #undo 19:43:51 <zodbot> Removing item from minutes: <MeetBot.items.Info object at 0x281d8c50> 19:43:56 <nirik> #info smooge got our bnfs01 server's disks working again. 19:44:09 <smooge> kind of sort of 19:44:19 <nirik> I've been tweaking nagios of late... hopefully making it better. 19:44:30 <nirik> #info nagios adjustments in progress 19:44:56 <nirik> We should have net for the rest of the arm boxes friday. 19:45:07 <nirik> #info arm boxes will get new net friday hopefully 19:45:14 <skvidal> I had a discussion with the author of pynag this morning 19:45:49 <nirik> cool. Worth using for a tool for us to runtime manage nagios? 19:45:50 <skvidal> if we have people willing to spend some time - we could easily build a query tool/cli-tool for nagios downtimes/acknowledgements/etc 19:46:07 <nirik> that would be quite handy, IMHO 19:46:12 <skvidal> nirik: it needs some code to make it work - but I think the basic functionality is available 19:46:41 <nirik> for some things the ansible nagios module would do, but for others it would be nice to have a command line. 19:47:15 <nirik> I'd like to look at doing a mass reboot next wed or so... upgrade everything to rhel 6.4. 19:47:17 <SmootherFrOgZ> skvidal: interesting! 19:47:37 <nirik> Might do staging today/tomorrow to let it soak there and see if any of our stuff breaks. ;) 19:47:52 <nirik> #info mass reboot next wed (tenative) for rhel 6.4 upgrades. 19:47:59 <skvidal> nirik: right - I'd like to be able to enhance the ansible nagios module to be more idempotent and 'proper' 19:48:04 <skvidal> nirik: pynag _could_ do that 19:48:17 <nirik> yeah, it looks very bare bones right now. 19:48:35 <nirik> in particular we could use a 'downtime for host and all dependent hosts' type thing 19:48:52 <skvidal> nirik: we could also use a 'give me the state of this host' 19:48:58 <skvidal> without having to go to the webpage 19:49:14 <skvidal> according to palli (a pynag developer) it can read status.dat 19:49:15 <skvidal> from nagios 19:49:18 <smooge> I am looking at lldpd for our PHX2 systems http://vincentbernat.github.com/lldpd/ Mainly to better get an idea of where things are 19:49:20 <skvidal> to determine ACTUAL state 19:49:26 <nirik> finally in the sysamin world, I'd really like to poke ansible more and get it to where we can use it for more hosts. Keep getting sidetracked, but it will happen! :) 19:51:04 <nirik> smooge: another thing we could look at there is http://linux-ha.org/source-doc/assimilation/html/index.html (it uses lldpd type stuff). They are about to have their first release... so very early days. 19:51:33 <smooge> ah cool 19:51:38 <smooge> wiill look at that also 19:51:55 <nirik> oh, on nagios, I set an option: soft_state_dependencies=1 19:52:22 <nirik> this hopefully will help us not get the flurry of notices when a machine is dropping on and off the net, or has too high a load to answer, then answers again. 19:52:50 <nirik> #topic Private Cloud status update / discussion 19:53:01 <nirik> skvidal: want to share your pain where we are with cloudlets? :) 19:53:08 <skvidal> sure 19:53:23 <skvidal> last week I did the euca upgrade and the wheels came right off 19:53:29 <skvidal> and then it plunged over a cliff 19:53:31 <skvidal> into a volcano 19:53:41 <pingou> sounds like a lot of fun 19:53:42 <skvidal> where it was eaten by a volcano monster 19:53:54 <smooge> who was riding a yak 19:53:56 <skvidal> anyway the euca instance is limping along at the moment with not-occasional failures :( 19:54:04 <skvidal> smooge: and the yak had to be shaven 19:54:17 <pingou> brough back some pictures > 19:54:19 <pingou> ? 19:54:21 <skvidal> so... 19:54:35 <skvidal> I've been working on porting our imgs/amis/etc over to openstack 19:54:44 <skvidal> and getting things more production-y in the openstack instance - 19:54:58 <skvidal> I got ssl working around the ec2 api for openstack 19:55:11 <nirik> #info euca cloudlet limping along after upgrade. 19:55:12 <skvidal> working on ssl'ing the other items 19:55:18 <skvidal> for the past couple of days 19:55:26 <nirik> #info work on going to bring openstack cloudlet up to more production 19:55:28 <skvidal> I've been in a fist fight with openstack and qcow images 19:55:33 <skvidal> and resizing disks 19:55:47 <skvidal> I just got confirmation from someone that what we want to do is just not possible at the moment :) 19:55:54 <nirik> lovely. ;( 19:56:10 <skvidal> nirik: not until we get the initramdisk to resize the partitions :( 19:56:17 <skvidal> so - I'm punting on this 19:56:24 <skvidal> I just put in a new ami and kernel/ramdisk combo 19:56:29 <skvidal> that's rhel6.4 latest 19:56:30 <smooge> sometimes that is best 19:56:35 <nirik> yeah. I think that could work, but needs some time to get working right. Hopefully by the cloud-utils maintainer. ;) 19:56:38 <skvidal> and since it is an AMI it resizes the disks 19:56:50 <skvidal> what it DOES NOT DO is follow the kernel on the disk - it uses the one(s) in the cloud 19:56:54 <skvidal> which is suck 19:57:00 <skvidal> but at least it is known/obvious suck 19:57:08 <nirik> but it should also get us moving past it for now. 19:57:11 <skvidal> I've also just built a new qcow from rhel6.4 19:57:27 <skvidal> so for systems that don't need to be on-the-fly made - we can spin them up 19:57:31 <skvidal> growpart the partition 19:57:33 <skvidal> reboot 19:57:35 <skvidal> resize 19:57:37 <skvidal> and go 19:57:47 <skvidal> and i'm working on a playbook to handle all of the above for you 19:57:51 <skvidal> and, yes, it makes me cry inside 19:58:08 <nirik> ;( 19:58:12 <skvidal> that's where we are at the moment 19:58:26 <skvidal> I am making new keys/accounts/tenants/whatever 19:58:35 <skvidal> for our lockbox 'admin' user 19:58:40 <skvidal> for making persistent instances 19:58:53 * nirik nods. 19:58:57 <skvidal> the next step is to start making use of the resource tags in openstack 19:59:02 <skvidal> so we can more easily track all this shit 19:59:15 <skvidal> also I have to make a bunch of volumes and rsycn over all the data from the euca volumes :( 19:59:30 <skvidal> I fully expect that last part to be a giant example of suffering 19:59:46 <nirik> yeah. we should probibly move one set of instances first and sort out if there's any doom 19:59:57 <skvidal> if I sound kinda 'bleah' there's a reason 20:00:02 <skvidal> nirik: I thought I'd start with the fartboard 20:00:07 <nirik> heh. ok 20:00:37 <skvidal> nirik: also - now that we have instance tags - it should be doable to write a simple 'start me up' script using ansible to spin out the instances 20:00:40 <skvidal> and KNOW where they are 20:00:48 <nirik> ok, we are running over time... let me quickly do upcoming and open floor. ;) 20:00:52 <skvidal> sorry 20:00:55 <skvidal> thx 20:00:57 <nirik> thats fine. ;) all good info 20:01:04 <skvidal> one last thing 20:01:08 <skvidal> if anyone wants to get involved 20:01:08 <skvidal> ping me 20:01:29 <nirik> #info please see skvidal if you want to get involved in our private cloud setup 20:01:33 <nirik> #topic Upcoming Tasks/Items 20:01:42 <nirik> (big paste) 20:01:44 <nirik> #info 2013-02-28 end of 4th quarter 20:01:44 <nirik> #info 2013-03-01 nag fi-apprentices 20:01:44 <nirik> #info 2013-03-07 remove inactive apprentices. 20:01:44 <nirik> #info 2013-03-19 to 2013-03-26 - koji update 20:01:44 <nirik> #info 2013-03-29 - spring holiday. 20:01:46 <nirik> #info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze 20:01:48 <nirik> #info 2013-04-16 F19 alpha release 20:01:50 <nirik> #info 2013-05-07 to 2013-05-21 BETA infrastructure freeze 20:01:52 <nirik> #info 2013-05-21 F19 beta release 20:01:54 <nirik> #info 2013-05-31 end of 1st quarter 20:01:56 <nirik> #info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. 20:01:58 <nirik> #info 2013-06-25 F19 FINAL release 20:02:00 <nirik> anything people want to schedule/note etc? 20:02:07 <nirik> I'll add the fas update and the mass reboot. 20:02:20 <abadger1999> Sounds good. 20:02:49 <nirik> #topic Open Floor 20:02:54 <nirik> Anyone have items for open floor? 20:03:32 <pingou> I have a series of blog post 'Fedora-Infra: Did you know?' coming, like once a week for the coming 4 weeks 20:03:32 <nirik> ok. 20:03:42 <skvidal> pingou: wow 20:03:46 <nirik> pingou: awesome. More blog posts would be great. 20:03:49 <pingou> short stuff, speaking about some cool features/ideas 20:03:52 <skvidal> pingou: looking forward to seeing those 20:04:10 <nirik> Thanks for coming everyone. Do continue over on our regular channels. :) 20:04:14 <nirik> #endmeeting

1 0

Summary/Minutes for today's FESCo meeting (2013-02-20)
by Miloslav Trmač 21 Feb '13

21 Feb '13

=================================== #fedora-meeting: FESCO (2013-02-20) =================================== Meeting started by mitr at 18:00:15 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-02-20/fesco.2013-02-20… . Meeting summary --------------- * init process (mitr, 18:00:21) * #988 F19 Feature: System Configuration Shell - https://fedoraproject.org/wiki/Features/SystemConfigurationShell (mitr, 18:07:37) * There was no response to questions from last meeting, closing as decided on February 13 (mitr, 18:08:59) * #1088 F19 Feature: FreeIPA Two Factor Authentication - https://fedoraproject.org/wiki/Features/FreeIPA_Two_Factor_Authentication (mitr, 18:09:04) * AGREED: F19 Feature: FreeIPA Two Factor Authentication is accepted (+7) (mitr, 18:11:51) * #1089 F19 Feature: Kolab 3 - https://fedoraproject.org/wiki/Features/Kolab3 (mitr, 18:11:58) * AGREED: F19 Feature: Kolab 3 is accepted (+8) (mitr, 18:13:03) * #1090 F19 Feature: Scala 2.10 - https://fedoraproject.org/wiki/Features/Scala210 (mitr, 18:13:08) * AGREED: F19 Feature: Scala 2.10 is accepted (+7) (mitr, 18:15:38) * Next week's chair (mitr, 18:15:42) * nirik will chair next week (mitr, 18:16:36) * Open Floor (mitr, 18:16:41) * tor (mitr, 18:18:02) * Will revisit tor after someone has looked at situation in more detail. (mitr, 18:19:30) * New Java packaging guidelines (mitr, 18:22:07) * AGREED: fesco asks that java packages not be converted to the new guidelines for a week as java sig and FPC resolve the problems with xmvn (+6) (mitr, 18:29:28) Meeting ended at 18:33:28 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mitr (45) * abadger1999 (19) * nirik (14) * pjones (11) * zodbot (8) * sochotni (8) * t8m (7) * mmaslano (6) * sgallagh (0) * notting (0) * jwb (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

i18n meeting summary (2013-02-21)
by Akira TAGOH 21 Feb '13

21 Feb '13

===================== #fedora-meeting: i18n ===================== Meeting started by tagoh_ at 06:02:56 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-02-21/i18n.2013-02-21-… . Meeting summary --------------- * agenda and roll call (tagoh_, 06:02:57) * LINK: https://fedoraproject.org/wiki/I18N/Meetings/2013-02-21 (tagoh_, 06:02:58) * Upcoming schedule (tagoh_, 06:07:41) * 2013-03-12 Feature Freeze--Planning & Development Ends (tagoh_, 06:07:41) * 2013-03-12 Branch Fedora 19 from Rawhide (tagoh_, 06:07:41) * 2013-04-02 Branch Freeze (tagoh_, 06:07:41) * 2013-04-02 Software String Freeze (tagoh_, 06:07:41) * 2013-04-02 Alpha Change Deadline (tagoh_, 06:07:42) * Outstanding topics (tagoh_, 06:08:53) * #12: language support installation command (pnemade) (tagoh_, 06:08:54) * LINK: https://fedorahosted.org/i18n/ticket/12 (tagoh_, 06:08:54) * LINK: https://fedoraproject.org/wiki/I18N/Language_Support_Using_Yum (tagoh_, 06:08:54) * LINK: https://fedoraproject.org/wiki/I18N/Language_Support (tagoh_, 06:08:55) * #16: Improving testcases/matrix for i18n test day (tagoh) (tagoh_, 06:13:31) * LINK: https://fedorahosted.org/i18n/ticket/16 (tagoh_, 06:13:31) * ACTION: tagoh_ to create another proposal for new i18n test day page (tagoh_, 06:27:19) * #17: Fedora 19 i18n test day (aalam) (tagoh_, 06:27:25) * LINK: https://fedorahosted.org/i18n/ticket/17 (tagoh_, 06:27:26) * LINK: https://fedoraproject.org/wiki/QA/Fedora_19_test_days (tagoh_, 06:27:55) * #15: F19 Feature: libkkc (ueno) (tagoh_, 06:31:35) * LINK: https://fedorahosted.org/i18n/ticket/15 (tagoh_, 06:31:35) * Open Floor (tagoh_, 06:38:57) Meeting ended at 06:49:27 UTC. Action Items ------------ * tagoh_ to create another proposal for new i18n test day page Action Items, by person ----------------------- * tagoh_ * tagoh_ to create another proposal for new i18n test day page * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * tagoh_ (69) * aalamS (13) * paragan (5) * dueno (3) * zodbot (3) * pravins (2) * anish_ (1) * epico (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 February 2013