18:00:00 #startmeeting FESCO (2012-01-23) 18:00:00 Meeting started Mon Jan 23 18:00:00 2012 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:01 #meetingname fesco 18:00:01 #chair notting nirik mjg59 mmaslano t8m pjones sgallagh mitr limburgher 18:00:01 #topic init process 18:00:01 The meeting name has been set to 'fesco' 18:00:01 Current chairs: limburgher mitr mjg59 mmaslano nirik notting pjones sgallagh t8m 18:00:04 hello. 18:00:10 Afternoon 18:00:11 Hello 18:00:11 * notting is here. have to leave in 55 mins, though 18:00:24 Hello 18:00:30 we have a pile of features, then another pile of features. ;) 18:01:00 hi 18:01:08 nirik: Don't forget about the avalanche of features too 18:01:17 sgallagh: oh, there might be some features too. ;) 18:01:23 ok, lets go ahead and dive in. 18:01:27 yeah. and for some reason when those get filed, the urls for the part that's useful to read aren't links. *really* annoying. 18:01:36 from last week: 18:01:39 #topic sponsor request - sdake 18:01:40 .fesco 724 18:01:41 nirik: #724 (sponsor request - sdake) – FESCo - https://fedorahosted.org/fesco/ticket/724 18:01:45 we tabled this last week. 18:01:51 further thoughts now? 18:02:09 Any new package reviews since last week? 18:02:11 Hi 18:02:59 some more in progress I think... 18:03:00 * nirik looks 18:03:34 2 more finished reviews, 3 more in progress. 18:04:38 Sounds like he's committed to the job 18:04:38 * nirik is +1 now. Not a vast number of reviews, but they all seem good to me, and we need more folks helping in the could space with sponsoring. 18:04:46 * sgallagh agrees. +1 18:04:48 yeah, +1 18:04:49 I am +1 as well 18:04:50 +1 18:05:22 sure, +1 18:05:51 #agreed sponsorship is approved. 18:06:05 #topic F17 Feature: DIET - https://fedoraproject.org/wiki/Features/F17_DIET 18:06:05 .fesco 751 18:06:07 nirik: #751 (F17 Feature: DIET - https://fedoraproject.org/wiki/Features/F17_DIET) – FESCo - https://fedorahosted.org/fesco/ticket/751 18:06:20 +1 18:06:22 +1 18:06:33 sure, +1 18:06:40 +1 18:06:55 +1 18:07:05 Fedora on a diet 18:07:16 moderately concerned about the name overlap with the old pseudo-libc and utils, but sure, +1 18:07:16 +1 18:07:32 notting: does anybody but us remember that? ;) 18:07:36 also: diet + corba? 18:07:39 odd combination 18:07:46 notting, :D 18:07:57 * nirik remembers it. man, must be old. 18:07:59 +1 18:08:04 #agreed Feature is approved 18:08:25 #topic F17 Feature: Rework Live CD - https://fedoraproject.org/wiki/Anaconda/Features/ReworkLiveCD 18:08:26 .fesco 752 18:08:27 nirik: #752 (F17 Feature: Rework Live CD - https://fedoraproject.org/wiki/Anaconda/Features/ReworkLiveCD) – FESCo - https://fedorahosted.org/fesco/ticket/752 18:08:41 so, one concern I have here is making live images in koji... 18:08:52 Note that this requires running virt guests as part of rel-eng processes 18:08:55 hey, just in time :) 18:09:15 yep. ;) 18:09:23 mitr: but it also gets us off of the old hacky way to do it, which has always been pretty awful. 18:09:26 so, yeah, it's nice to be able to do live composes in koji... 18:10:09 pjones: I'm fine with it as a matter of principle, just wondering whether rel-eng will be able to use it 18:10:21 can't koji already do live composes? 18:10:27 yeah, I understand. Guess that's a question for rel-eng. 18:10:40 notting: yes, with the current process. not this new process, AFAIK 18:10:45 As far as the feature goes, I'm fine with it 18:10:59 Implementation details may always prevent something we approve from happening 18:11:07 I am fine with the feature +1 18:11:07 I'm not sure this qualifies as a Feature 18:11:11 This sounds more like a process. 18:11:19 *process change 18:11:37 I like moving it all into the same place, I don't like the requirement on libvirt instances. ;( 18:11:40 I guess I don't understand what this adds to Fedora that is worth putting in release notes, etc. 18:11:45 sgallagh: nevertheless in light of no dramatic overhaul of the feature process having occurred, people are still effectively being encouraged to make this sort of thing a Feature. 18:12:04 pjones: I'm not sure it matches up even with the current flawed feature process 18:12:10 Right, having the code is awesome, I don't know about advertising the code if it isn't used 18:12:32 sgallagh: I'm not sure anything does. It's sortof beside the point. 18:12:52 mitr: If it's not used then it won't reach 100%. Or am I misunderstanding you? 18:12:59 * limburgher is here Sorry I'm late, $DAYJOB 18:13:05 I'm +0 on this. 18:13:19 mjg59: integrating the code into rel-eng processes isn't in scope AFAICS 18:13:21 this would also seem to preclude building live images for certain secondary arches 18:13:35 I guess I am ok with the feature, but would want to -1 it if we don't use it in rel-eng to produce things... because if we still use the old method, but advertise the new to users it could cause doom. 18:13:45 mitr: The fallback is to carry on using python-imgcreate 18:13:59 mitr: So if we carry on doing that then the feature isn't complete 18:14:06 mjg59: oh, right 18:14:26 notting: as in, some arches don't have virt at all? 18:14:33 mitr: yep 18:14:36 bcl? 18:14:51 nirik: I'm leaning more towards -1 for this release and work it in tightly to f18 18:14:52 that's what qemu-sh4 is for ;) 18:14:53 proposal: +1 to feature, but drop if not able to be used by releng. Ask feature owners to work with rel-eng to come up with a solution? 18:14:56 hmm, reading... 18:15:23 nirik, that seems like reasonable proposal 18:15:25 * mitr would be +1 to proposal 18:15:25 nirik: I like your proposal, +1 18:15:27 pjones: the horror 18:15:27 Seems kind of late to make that sort of change anyway. Especially since it needs to be finished in time to build the alphas 18:15:36 I'm going with -1 after more thought. 18:15:54 note: you can also use it w/o virt if you are running it from the same release as you are targeting. 18:16:06 Well, I don't think we should -1 out of hand just because we don't know what rel-eng things. We should ask rel-eng instead. 18:16:09 so for secondary arches w/o virt that is an option. 18:16:13 bcl: in a mock/chroot? 18:16:13 bcl: hm, that might simplify things 18:16:32 not in mock. mock and loops don't always work right. 18:16:33 * nirik nods. that might make things doable for the koji plugin. 18:17:06 hum, bummer then. 18:17:13 i am +1 to the idea of the feature, but final completion really does depend on rel-eng 18:17:23 yeah, I'm +1 as well. 18:17:33 +1 on the assumption that if it's not finished then it's not a feature, but that's true of everything isn't it? 18:17:56 mjg59: yes. 18:18:10 well, I was suggesting we add a requirement on it... 18:18:16 that it be used by rel-eng. 18:18:17 * sgallagh remains -1 for F17 18:18:37 nirik: that's already implicitly there though 18:18:43 notting / pjones / mjg59: is that +1 to my proposal? or just the feature as itself? 18:18:56 +1 to the feature 18:18:58 pjones: it is? 18:18:59 just to the feature 18:19:05 I don't see it on the feature page anywhere. 18:19:23 Contingency Plan 18:19:23 Continue to use python-imgcreate 18:19:52 I think it is a separate decision as to whether releng uses it for live media. 18:19:53 but it doesn't have a requirement that we produce our live images with it. 18:19:59 hence the word "implicitly", yes. the contingency plan clearly assumes that rolling it out is part of it. 18:20:09 If we use python-imgcreate then we're on the contingency plan 18:20:17 And if we're on the contingency plan then the feature isn't complete 18:20:22 There's also the 3rd part spins guys who make lots of live stuff. 18:20:50 bcl: so you're saying the feature is really just the availability of it, then? 18:21:01 right. 18:21:06 yes 18:21:16 okay. 18:21:32 I would prefer that it had more testing by spins before being used by releng. 18:21:52 I'd like to avoid the "I downloaded the desktop ks file and make a live with livemedia-creator and it has diffferent bugs from the official media that can be downloaded" 18:22:00 But I think it is a good Feature because it finally gives us a way to make correct images instead of chroot+yum images. 18:22:34 nirik: I think we've already got that 18:22:40 so, we are -1, +4 to feature + rel-eng requirement, and +1 to the feature as is? 18:22:56 nirik: just the fact that you might get updates applied causes that. 18:22:56 pjones: how so? 18:23:48 if you enable them, but you could also change the ks file, etc, etc. I am talking about reproducing the official media... doing one method then asking users to use another is likely to cause confusion and more bugs. I guess it's not the end of the world... 18:24:22 really it should have less. since it uses anaconda :) 18:24:48 * nirik agrees it's the way to go, but just isn't sure we should advertise it before we are using it. 18:25:36 so, where are we then? other votes? thoughts? 18:26:03 nirik: but how do we get the testing bcl wants to have before it goes into rel-eng if the message we're sending is to not use it? ;) 18:26:19 sure there is that... 18:26:23 pjones: Spins, not official releases. 18:26:49 sgallagh: we have official spin releases, no? 18:26:59 proposal: could we add into ticket condition -> speak with releng about it? 18:27:04 * sgallagh shuts up 18:27:29 would folks revote noting if they are ok with the feature as is, or require us to be using it for official live media first? 18:28:18 +1 as is 18:28:46 -1 For F17 18:28:57 +1, but would like to see rel-eng using it or at least a way for them to do so down the road. 18:29:09 i guess i'm -1 as is - concerned about the fact that it requires kickstart changes 18:29:11 I'm still +1 as is as well 18:29:20 +1 and debate with rel-eng 18:29:21 +1 if used by rel-eng (in everything or even in a single small part) 18:29:24 +1 as is, though rel-eng soonish. 18:29:26 I really don't care about the rel-eng requirement although it would be clearly nice to have a word from them if they'll be able to use it 18:29:28 so +1 18:30:18 Alternatively, +1 as is, if the release notes (which are empty currently) explicitly describe the current status 18:30:45 * nirik tries to count votes. 18:31:09 I'm all for explaining the current status in the relnotes 18:31:10 -2, +3 (with releng) and +4 as is I think. 18:31:43 anyone want to change votes? ;) 18:31:56 hm. 18:32:19 Perhaps it would be prudent not to have a multiple-choice here? 18:32:25 if it gets re-defined in the (!releng) case from "here is the new way to build images" to "here is a new way to build images that we're working on...", yes? 18:32:50 sgallagh: open to suggestion. ;) 18:33:43 ok, how about: 18:33:58 proposal: table, ask rel-eng folks for input and revisit next week. ;) 18:34:04 +1 18:34:04 nirik: +1 18:34:07 (when you can't decide, defer!) 18:34:20 nirik, +1 18:34:27 +1 18:34:34 +1 18:34:39 +1 18:34:47 sure, why not. 18:34:55 Who will take that action item? bcl: can you do so? 18:35:17 #agreed will ask rel-eng for input and revisit next week. 18:35:18 err, which? 18:35:45 talk to rel-eng about this and see if there's a way for them to use this to compose offical images. 18:35:45 (ie, talk to dgilmore) 18:35:57 sure. 18:36:07 #action bcl to talk with rel-eng. 18:36:09 thanks 18:36:18 #topic F17 Feature: ABRT Backtrace Deduplication - https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication 18:36:18 .fesco 754 18:36:22 nirik: #754 (F17 Feature: ABRT Backtrace Deduplication - https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication) – FESCo - https://fedorahosted.org/fesco/ticket/754 18:36:26 +1. less dupes good. 18:36:33 +1 18:36:36 +1 18:36:41 +1 18:36:41 doesn't it already do this? +1 anyway 18:36:44 +1 18:36:45 +1 18:36:51 it does, but this is a new and shiny method I gather. 18:37:10 #agreed feature is approved. 18:37:10 +1 18:37:14 I feel like I should -1 anything that involves a retrace server. 18:37:37 [btw, can I add an agenda item please?] 18:37:39 yeah, sadly thats the path we are on tho. 18:37:50 dmalcolm: sure, can it wait for open floor at the end? 18:37:57 nirik: sure, thanks 18:38:01 #topic F17 Feature: Font Configuration Tool - https://fedoraproject.org/wiki/Features/FontConfigurationTool 18:38:01 .fesco 755 18:38:04 nirik: #755 (F17 Feature: Font Configuration Tool - https://fedoraproject.org/wiki/Features/FontConfigurationTool) – FESCo - https://fedorahosted.org/fesco/ticket/755 18:38:20 pjones: what's the concern? privacy, HW availability, something else? AFAICS this feature does not depend on doing the retrace 18:38:46 +1 to font cfg tools - ideally should be provided by the desktops directly, but having a desktop-independent fontconfig-only tool can't hurt 18:38:50 mitr: no, it just makes use of it. but we should have gone the route of making debuginfo better available on the client end for various reason, privacy included. 18:39:12 +1 to this feature, we could use more good font tools. Hope it's done in time. 18:39:15 +1 to the feature 18:39:18 +1 18:39:19 This is just making the tool available, right - not the default? 18:39:20 +1 18:39:21 sure, +1 18:39:22 mitr: well, it gives users a way to botch theiir own config 18:39:32 mitr: I agree to +1, but I'd like to lobby the devs to make it into an API for easier integration with native desktop environments 18:39:36 yeah, just advertising the tool as I read it. 18:39:41 +1 18:40:01 hey, someone who may have an opinion on this :) 18:40:16 notting: ? 18:40:23 if he's really here. ;) 18:40:37 nim-nim: as a font person, any comments on https://fedoraproject.org/wiki/Features/FontConfigurationTool ? 18:41:33 #agreed feature is approved. 18:41:42 * nirik guesses he's not really around. 18:42:17 #topic F17 Feature: English Typing Booster - https://fedoraproject.org/wiki/Features/english-typing-booster 18:42:18 .fesco 756 18:42:20 nirik: #756 (F17 Feature: English Typing Booster - https://fedoraproject.org/wiki/Features/english-typing-booster) – FESCo - https://fedorahosted.org/fesco/ticket/756 18:42:27 * notting votes -1 to the prior feature, for the record 18:42:57 +1 18:43:03 "Create dictionary tables from wikipedia dumps for English." hm. 18:43:06 I read through this and I couldn't find a clear vision of how this works from upstream 18:43:38 i *think* that should be OK from a licensing standpoint 18:43:45 Why not use existing dicts? 18:44:00 notting: WP is CC-BY, correct? 18:44:07 sgallagh: CC-BY-SA 18:44:09 "Since the suggestions come from a validated word dictionary database, the selected words always give 100% accurate spelling." 18:44:09 They'd need to give credit somewhere. 18:44:13 I am +1 - if this is not on by default which I suppose it isn't 18:44:18 sgallagh: I'm not sure what you mean - AFAICS it's just one more input method that can be manually enable. I didn't find any screenshots/videos either :) 18:44:29 I actually had a conversation about this last week 18:44:33 the experience to set up in how-to-test looks icky 18:44:37 mitr: Right, I missed the word 'ibus' on my first read 18:44:46 Summary: The copyright status of the output of a model trained on a given text is unclear 18:44:47 I wasn't sure if this was supposed to work at the console too 18:44:56 limburgher: I wondered as well, but I'm not interested in micromanaging that 18:45:18 So if the training text is CC-BY-SA, there is an argument that anything you typed with it would have to follow those terms 18:45:42 mitr: Yeah. As long as the licensing is ok. . . 18:45:59 So I'm +1, but would just note that the licensing does need to be checked carefully 18:46:02 mjg59: that's an odd interpretation 18:46:09 I don't see why adding such new package is a feature but it's +1 18:46:22 I don't think wordlist created of a text is a derived work of that text if the text is sufficiently large. 18:46:23 * nirik is +1 I guess. 18:46:39 mjg59: but I think what you're saying is that no amount of checking will actually tell us where we stand? 18:46:43 I'm -1 while there are legal considerations. Send it to legal@ first 18:46:52 * notting agrees with sgallagh. -1 18:46:59 pjones: well, switching to /usr/share/dict/words solves that problem 18:47:02 If this only looks at the context of the single word, I suspect it's fine 18:47:17 If it starts producing predictions based on previous words then things get a little more confusing 18:47:40 mjg59: https://fedorahosted.org/english-typing-booster/browser/english-typing-booster/tables/english-dict.txt (3M download) - single words AFICS 18:47:42 For instance, if choosing the best prediction each time results in it tending to generate the original work... 18:47:55 * nirik notes his +1 was on the assumption that legal was ok 18:48:24 nirik: I think it should be vetted before we give any tacit approvals 18:48:41 mjg59: haha 18:48:42 sgallagh: 18:48:52 Ok - single words so I guess it's probably ok 18:48:58 Although the words list does claim to be GPLv3 18:49:02 I really do not think there is any legal trouble with wordlists 18:49:11 mjg59: well, that's obviously wrong 18:49:13 so +1 18:49:19 so, I see +4, -2 ? 18:49:36 +1 to the feature, and unrelatedly I think it should have some legal checking 18:49:39 mjg59: and i'm not sure if it's even valid 18:49:45 I'm +1 to the feature. 18:49:55 notting: Yeah, quite 18:49:56 +1 to mjg59 18:50:09 +1 if it's legit. 18:50:15 but yeah, it's clear we need to do some legal homework on this one 18:50:35 pjones: s/we/feature owners/? 18:50:35 * notting remains -1 until legal homework done 18:51:04 *shrug* i'm willing to undertake that *with* the feature owners 18:51:36 ok, I think thats +6, -2.. 18:51:42 notting: please do? :) 18:51:48 mitr: notting, obviously. 18:52:15 #agreed feature is approved. 18:52:34 do we want to leave some kind of tracking in place for the legal aspect? 18:53:01 nirik: What do you propose? File a BZ? 18:53:06 notting: I'm not sure it's the cleanest approach possible but they're trying to make fontconfig work in in the real world 18:53:26 sgallagh: perhaps we leave the ticket open and revisit it in our meetings ? 18:54:04 worksforme 18:54:19 ok, so thats the end of the features that were on our initial agenda... 18:54:26 but then we got a pile more. 18:54:38 do we want to look at them today? defer to next week? or look at a subset? 18:55:10 notting: as opposed to the previous wishful thinking (someday someone will create a perfect font set with no overlaps that fontconfig can handle automatically without config) 18:55:10 I think we should look at them today 18:55:23 * nirik is fine to look at them today. 18:55:26 I think we should hit as many as we can in the next, say, hour 18:55:32 we can always defer on ones we want more info on 18:55:36 yes 18:56:07 Today, please - the work won't go away if we defer 18:56:37 Perhaps there is an uncontroversial set that we could block vote on? 18:56:37 ok. i have to head out, i can vote in tickets later 18:56:49 notting: have fun. 18:57:16 notting: fontconfig worst weakness is that it only manipulates complete fonts, and since they all overlap in non-obvious way it's not possible to create a single order everyone likes as keithp thought 18:57:37 pjones / mjg59 / limburgher: shall we try and go on? or you guys want to postpone? 18:58:07 May as well go on 18:58:28 notting: and no one has stepped up to do the clean thing (enhance fontconfig so it can work on font subsets that can be defined in non-overlappy way) 18:58:33 Go on. 18:58:40 we're still at quorum, so may as well make an attempt with an eye on deferring quickly if consensus isn't clearly reachable. 18:58:50 ok, onward. 18:58:51 #topic #758 F17 Feature : Eclipse Juno - https://fedoraproject.org/wiki/Features/EclipseJuno 18:58:52 .fesco 758 18:58:53 nirik: #758 (F17 Feature : Eclipse Juno - https://fedoraproject.org/wiki/Features/EclipseJuno) – FESCo - https://fedorahosted.org/fesco/ticket/758 18:59:17 +1 18:59:24 sure, +1 18:59:26 notting: as far as I understand the i18n feature is to let users reorder fontconfig prefs any way they like, since a perfect distro order is not possible 18:59:34 +1 18:59:40 Is this filing early? 18:59:56 It's claiming that the upstream will be released in June 19:00:02 this seems like their timeline is f18 not f17 19:00:04 That seems rather too late for F17 19:00:06 +1 19:00:08 sgallagh: they want to ship a prerelease 19:00:09 -1 19:00:22 -1 that's what rawhide is for 19:00:26 "Upstream has asked that we clearly communicate that we will be shipping a pre-release in Fedora (due to timing) and will be updating to their final version as soon as it is released. " 19:00:38 I do not like shipping prereleases in the final GA releases of Fedora 19:00:42 +1 - if this is agreed with upstream, why not 19:00:59 sgallagh: Maintainers get to make judgement calls on whether they think something will be sufficiently stable 19:00:59 t8m: We ship a prerelease of GNOME practically the entire development cycle 19:00:59 yeah, I don't much like sticking a prerelease in f17 and then updating to a final (plausibly quite different) version in an update. 19:01:00 -1 19:01:06 t8m: There is definitely precendent for that strategy, though. 19:01:11 mitr, I don't like it either 19:01:16 It works for Firefox. 19:01:27 (GNOME, KDE< and firefox have all done it) 19:01:34 As long as the expectation is that changes will be minimal, I'm fine with this 19:01:41 abadger1999, I know 19:01:47 Generally their final releases are going to happen before Fedora's GA 19:01:51 yup 19:01:54 we're always screwed 19:02:00 either early (this case) or late (4 months) 19:02:07 We're talking about at least a month of additional work here. 19:02:13 I pushed for early this time 19:02:16 Not including slippage 19:02:20 yeah, some upstreams just don't align with our release cycle. 19:02:23 honestly, 99% of upstream is done by April 19:02:30 they have serious ramp-downs 19:02:33 and they don't slip 19:02:34 nirik: Of course, but they should wait for the next bus 19:02:34 guaranteed 19:02:36 overholt_: so we're really talking about very minimal changes? 19:02:39 pjones, yup 19:03:04 I count +5 anyway... 19:03:06 The schedule says API freeze on March 16, i.e. before our Beta 19:03:15 yup 19:03:19 okay, I can be convinced then. 19:03:21 Personally, I rely on Eclipse rather a lot. I'm leery of having a prerelease in F17 19:03:32 no point in holding something up on process formalities if the real changes are already done. 19:03:45 pjones: If we vote it down, it gets backed out 19:04:01 sgallagh: I'm familiar with how voting works, yes. 19:04:09 sgallagh: Er. 19:04:12 I don't want to do an update post-release 19:04:15 sgallagh: No, if we vote it down, it's not a feature. 19:04:19 * nirik counts votes. 19:04:30 sgallagh: We could separately have a discussion on whether to overrule the maintainer 19:04:32 nirik: given overholt_'s input I'm +1 as well. 19:05:03 Obviously I've been outvoted, but I'm -1 (I think this will bite us) 19:05:18 sgallagh, I'd like to work with you personally as an active user to ensure it doesn't 19:05:22 mjg59: I assumed he meant backed out as a feature, not from the distro, but on re-read I see what you're saying. 19:05:30 either way, it seems to be approved, n'est pas? 19:05:37 I think thats +6, -2 ? 19:05:52 #agreed feature is approved 19:06:02 thanks 19:06:18 #topic #759 F17 Feature: Opa - https://fedoraproject.org/wiki/Features/Opa09 19:06:18 .fesco 759 19:06:20 nirik: #759 (F17 Feature: Opa - https://fedoraproject.org/wiki/Features/Opa09) – FESCo - https://fedorahosted.org/fesco/ticket/759 19:06:24 overholt_: Well, I'll be testing the new release, absolutely :) 19:06:32 +1 19:06:39 But I'm wary of it being stable enough for Fedora in general 19:06:49 +1 19:06:55 +1 19:07:01 sgallagh: that was a joke, right? 19:07:02 +1 19:07:03 +1 Looks straightforward to me 19:07:14 (Do things built with Opa end up under AGPLv3 as well?) 19:07:23 +1 19:07:26 +1 19:07:32 I sure would think not. 19:07:33 pjones: You're such a cynic :) 19:08:30 #agreed feature is approved 19:08:34 nirik: Seems a slightly odd license to choose in that case, but I don't think it makes any practical difference 19:08:57 yeah 19:09:18 mjg59: Better ask that question of spot if you're concerned/want it documented in Fedora. 19:10:06 #topic #760 F17 Feature: Internationalization support for additional Indian languages - http://fedoraproject.org/wiki/Features/Additional_Indic_Langs 19:10:07 .fesco 760 19:10:08 nirik: #760 (F17 Feature: Internationalization support for additional Indian languages - http://fedoraproject.org/wiki/Features/Additional_Indic_Langs) – FESCo - https://fedorahosted.org/fesco/ticket/760 19:10:15 Sure +1 19:10:16 +1 19:10:17 might be good to ask that on the package review (which is still open) 19:10:25 +1 19:10:25 +1 19:10:29 +1 19:10:29 22 official languages is absurd, even for a country the size of India. +1. 19:10:41 +1 19:10:49 #agreed feature is approved 19:10:50 +1 19:11:12 #topic #761 F17 Feature: DNSSEC on workstations - https://fedoraproject.org/wiki/Features/DNSSEC_on_workstations 19:11:12 .fesco 761 19:11:14 nirik: #761 (F17 Feature: DNSSEC on workstations - https://fedoraproject.org/wiki/Features/DNSSEC_on_workstations) – FESCo - https://fedorahosted.org/fesco/ticket/761 19:11:15 pjones, you mean something like European Union? 19:11:41 t8m: not a country. 19:11:52 t8m: as they seem hellbent on proving right now. 19:12:12