16:30:06 #startmeeting IRC Support SIG 16:30:30 #topic Init Process - whos around for the meeting? 16:30:38 * muep 16:30:45 * onekopaka will sit in 16:32:09 * onekopaka wonders if ianweller will jetpack in here. 16:32:12 * thomasj 16:32:20 nah, too busy :) 16:32:22 * nirik will wait a bit more for folks to wander in. 16:32:26 * LinuxCode  16:32:41 * onekopaka straps ianweller to a chair so he can *enjoy* this meeting. 16:32:43 * LinuxCode stumbles and falls back out 16:34:33 ok, I guess we can go ahead and get started. I didn't have too much on the agenda this week... 16:34:40 #topic weekly stats 16:34:49 as always at http://theglaserfamily.org/ircstats/fedora-weekly.html 16:35:02 looks like LinuxCode is the top of the lines this week. ;) 16:35:12 what ? 16:35:13 LIES 16:35:21 I didnt do it, honestly 16:35:44 ;-p 16:35:49 not too much I see there... pretty typical week. 16:35:49 * thomasj looks at LinuxCode's enter key 16:36:14 thomasj, dont even mention it..... 16:36:19 haha 16:36:24 yeah, less words than thomasj in more lines. ;) You should look at those one word sentences. ;) 16:36:39 exactly =D 16:36:40 its a filthy habit, I cant help it 16:37:00 anyone see anything in the stats they want to bring up? 16:37:03 I write how I think 16:37:15 * LinuxCode looks 16:38:07 apaprt from the fact Id like more sleep ? 16:38:10 lol 16:38:20 nirik, yeah, my op attempt was on fedbot 16:38:22 wouldn't we all? :) 16:39:02 op attempt? 16:39:32 yep, in the stats i have "thomasj was also very polite: 1 ops from him/her." <== fedbot 16:39:41 ah, right. 16:39:49 #topic Hot Support topics 16:39:54 so, a few things: 16:40:15 I think the mirror issues are finally behind us. I will confirm with mmcgrath and ricky and we can then remove it from the topic. 16:40:31 yay 16:40:32 has anyone seen any reports of mirror problems lately? like the last few days? 16:40:39 yeh I noticed that today 16:40:49 I noticed first updates 16:40:51 ;-p 16:40:56 meh 16:41:01 we had some reports today 16:41:08 but, dont know which mirrors 16:41:23 Some might be becaause of the vlc problem 16:41:25 well, there are always some reports... usually broken proxys or pilot error. 16:41:26 maybe all 16:41:32 yah 16:42:07 * Southern_Gentlem 16:42:24 There is another one I wanted to bring up: the epiphany update. It should get fixed in the next push. 16:42:48 good 16:42:58 * thomasj dont use it but anyways good 16:43:00 until it is, x86_64 folks will see it pulling in about a billion i586 deps 16:43:07 yesterday still mirror issues 16:43:11 and other weird things. 16:43:17 yeah 16:43:25 1billion, nice round num,ber ;-p 16:43:28 hehe 16:43:29 Southern_Gentlem: oh? anything specific? 16:44:32 was creating isos with jigdo and was hitting alot of 404s still 16:45:01 but it was getting them in the end? 16:45:09 Southern_Gentlem, my new updates fed through at 12pm UK time 16:45:23 eventually 16:45:25 today 16:45:45 well, keep an eye on it... it should be solved or close to now... 16:47:21 #topic Open Floor 16:47:40 ok, anything anyone has for open floor? ways we can improve things? get more helpers? or move forward? 16:48:20 * LinuxCode cant think of anything 16:49:01 are these meetings weekly? 16:49:01 Nope 16:49:05 yes 16:49:14 yes, every week. 16:49:16 always or mostly the same time? 16:49:22 do we have a wiki page that explains conduct to people ? 16:49:26 always the same time... 16:30UTC. ;) 16:49:40 best ways to help people, etc.. 16:49:41 ok, good to know 16:50:11 * ricky has one thing to mention 16:50:24 LinuxCode: several: https://fedoraproject.org/wiki/Communicate/IRC 16:50:28 LinuxCode, you mean the one you didn't read? http://fedoraproject.org/wiki/IRC_helpers_code_of_conduct 16:50:31 * thomasj hides 16:50:37 yeh that one thomasj 16:50:40 =) 16:50:42 lol 16:50:45 They can always use more work/cleanup if someone would like to step up to do so. 16:50:54 * onekopaka gives LinuxCode a shotgun to shoot thomasj 16:50:57 nirik, if I find some time, I will 16:51:03 still cleaning up ambassadors 16:51:04 * onekopaka didn't load the shotgun =) 16:51:10 * thomasj notes onekopaka on his blacklist 16:51:14 ricky, shoot 16:51:36 thomasj: at least I didn't load it. 16:51:41 ok. Feel free, although if you make big changes best to bring them up at the meeting and get folks approval. 16:51:50 There were recently some threads on fedora-docs-list (such as https://www.redhat.com/archives/fedora-docs-list/2009-July/msg00092.html) about getting simpler short pieces of documentation, maybe even something like a knowledge base 16:51:51 nirik, as always mate 16:51:54 onekopaka, oh true.. /me deletes onekopaka again from it 16:52:11 I was wondering if people from #fedora have a good idea of what kind of those docs would be useful 16:52:22 One example of a really good one I brought up in another thread was the sudo howto for example 16:52:29 ricky: yeah, I think there are def some that would be good for that. 16:52:40 Which I'm happy to say, is the first result for fedora sudo - kudos to the fedorasolved people! 16:52:44 ricky, one sec, let me read 16:52:47 I was hoping someday to setup a kb in supybot, but sadly thats not happened. 16:53:09 Compare that to the first result for fedora apache and you'll see the kind of things that I'm not too happy about as they are now 16:53:14 * onekopaka takes his shotgun from LinuxCode. 16:53:17 s/first result/first few pages of results/ 16:53:27 ahhh, I spoke to sijis about this, good idea 16:53:39 about time too,.... 16:53:59 ricky: one concern is that we need to know what docs are not acceptable for it. 16:54:05 Anyway, there's some docs team interest in it now, so I thought it'd be good for you guys to know about it, since you interact with a lot of users and all :-) 16:54:10 + it must not flood the channel 16:54:21 Yeah, stuff like how to setup flash + mp3 would probably be out 16:54:23 for example, when can we mention rpmfusion? when should we mention non free stuff? 16:54:45 If any of you are on fedora-docs-list, mind bringing that up in the thread? 16:54:46 nirik: in the non-free section. 16:54:47 thats an interesting case, because we explain how to install flash on our wiki currently. ;) 16:54:59 Otherwise I'd be happy to post any questions you have for you and forward you the responses 16:55:02 nirik: Hehe :-) 16:55:03 onekopaka: fedora has no Non free section. ;) 16:55:39 nirik, maybe we should have a think about this until next week 16:55:40 ricky: I think in general it could be a good idea. We need to know what kinds of things are acceptable. 16:55:45 nirik: the docs would need such a thing if you going to show how to use all that non-free stuff. 16:55:51 about potential problems or areas we need covered... 16:56:01 onekopaka: yes, but then that might open us to contributory infringement. ;) 16:56:13 nirik: my understanding is that rpmfusion can be mentioned vaguely, but no specifics about what it has can/should be offered 16:56:18 LinuxCode: yeah, perhaps we could consider it and add comments to the dos people or the ticket? 16:56:32 yep 16:56:40 So who wants to bring the concerns up on the mailing list? I'd be happy to if nobody else is on list 16:56:42 be good if a docs person would tell us what they had in mind too 16:56:43 rdieter: yeah. So we could not have a 'how to install the nvidia non free driver' KB article. 16:56:46 I tend to recommend people to use free solutions, but I guess it's ok to refer people in #fedora to RPM Fusion when they clearly need something from there? 16:56:56 ricky, have they got a proposal document ? 16:57:01 that we could look at ? 16:57:23 nirik: theoretically that one is ok, it gets dicey when the topic covers patented items 16:57:26 LinuxCode: I don't think it has gone that far yet - parts of it are also waiting for the zikula stuff to go forward, but a lot of the documentation work can happe on the wiki right now 16:57:31 preferably on the wiki, so we could add coments 16:57:31 muep, totally 16:57:35 muep: yeah. Free is best, but if they ask specifically for something else we point to rpmfusion. You can of course do as you like, none of the advice in #fedora is offical. ;) 16:57:36 * ricky personally prefers the wiki 16:57:43 i see 16:57:53 was thinking we could then chip in...with comments 16:58:00 as its easy to make an edit 16:58:15 be here in a minute 16:58:18 start without me 16:58:20 thomasj, nirik: good to know :-) 16:58:40 would also be quite hard to enforce otherwise 16:58:49 indeed :) 16:58:50 ricky: thanks for bringing it up. If you could send the current thoughts as feedback and tell them we are interested in figuring something out that would be great. 16:59:02 Sure thing, your feedback is much appreciated! 16:59:13 Anything anyone else has for open floor? 16:59:39 * LinuxCode shakes head 16:59:56 absolutely not. 17:00:10 * nirik will close things out in a few if no one chimes up. 17:00:49 * onekopaka plays the Jeopardy song to make this funny. 17:00:57 ricky and it has been there for years (sudo howto) 17:01:15 #endmeeting