17:00:23 #startmeeting FESCo meeting 20091204 17:00:24 Meeting started Fri Dec 4 17:00:23 2009 UTC. The chair is notting. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:32 Present. 17:00:36 yo 17:00:37 #chair dgilmore dwmw2 notting nirik sharkcz jds2001 j-rod sk 17:00:37 vidal Kevin_Kofler 17:00:37 Current chairs: dgilmore dwmw2 j-rod jds2001 nirik notting sharkcz sk 17:00:38 * sharkcz is here 17:00:43 * nirik is here. 17:00:44 #meetingname fesco 17:00:44 The meeting name has been set to 'fesco' 17:01:04 Your chair line got cut off... 17:01:09 #chair dgilmore dwmw2 notting nirik sharkcz jds2001 j-rod skvidal Kevin_Kofler 17:01:09 Current chairs: Kevin_Kofler dgilmore dwmw2 j-rod jds2001 nirik notting sharkcz sk skvidal 17:01:24 that's 4. anyone else? 17:01:31 dwmw2: have internets? 17:02:17 do we have any tickets with votes from nonpresent folks? 17:02:50 * dwmw2 here 17:02:51 no 17:03:04 someone stole my phone line, but BT put another one in 17:03:34 ok, that's quorum 17:04:11 first topic *was* linville provenpackager, but that was handled last meeting. i'll close out the ticket 17:04:23 #action notting will close out ticket 274 17:04:38 #topic F13 schedule 17:04:46 .fesco 281 17:04:47 notting: #281 (Approve Fedora 13 Schedule) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/281 17:05:11 * nirik kills his browser... trying to change component on a bug sent it to lalaland. 17:05:39 John Poelstra set this up after some long discussions with rel-eng. It's what's currently reflected in Releases/13/Schedule on the wiki as well 17:05:52 That'd put the F13 release at May 11. 17:06:18 right. I'm ok with the plan I guess. It's anoying that we have to move around for otheros releases... but such is life. 17:06:18 yes. there was a conflict with the release of ubuntu $next, that would make staging it at our original planned date impossible 17:06:54 another short schedule is a thought, but if we slip for any reason we would have to slip like 4 weeks. ;( 17:07:23 It's the big problem: if we release differently from Ubuntu, everyone complains that we're not in sync with upstream projects, if we release together with them, the mirrors complain that we're swamping them. 17:07:41 Can't make everyone happy. 17:08:01 * notting is +1 to the schedule as posted 17:08:04 yeah. One thing that might help: we could decide tenative schedules further out. 17:08:26 +1 also from me 17:09:31 Kevin_Kofler: dwmw2: ? 17:09:48 +1 17:10:06 Well, I think releasing before Ubuntu might be better for marketing than after them, but it'd leave us no room to slip without going back to causing the mirrors trouble. 17:10:10 So that's not a good plan. 17:10:18 Thus +1 to the plan with the May 11 release. 17:10:32 ok 17:10:39 #agreed F13 schedule as proposed is accepted. 17:11:37 rest of the agenda is features. 17:11:51 #topic Feature Intellij IDEA 17:11:56 .fesco 272 17:11:57 notting: #272 (Intellij IDEA - https://fedoraproject.org/wiki/Features/IntelliJ_IDEA) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/272 17:12:11 (sorry, delivery. back in ~2 minutes) 17:12:33 where were we on this? we discussed it last time. 17:13:13 * nirik was a weak +1 on it before. It's nice that we show fedora gets things first and helps a company open source. 17:13:43 I think we wanted an assurance that it wasn't crippleware 17:13:44 The picture with the monkeys as "users" is surely meant as a joke, but it comes out outright insulting. 17:13:50 I was also a weak +1 17:14:06 (on the feature page) 17:14:07 Kevin_Kofler: I thought the monkeys were java developers? 17:14:15 yeah, I thought we got such an assurance... 17:14:28 * nirik looks around, doesn't see lkundrak. 17:14:58 Well, the feature list from upstream, which compares it to the proprietary "Enterprise Edition", looked a lot like crippleware. 17:14:58 => "lkundrak is now known as miniperl" 17:15:30 miniperl: ping 17:15:35 Kevin_Kofler: but you could probably say the same thing about MySQL, right? 17:15:39 Kevin_Kofler: I agree the monkey picture is not a good idea. 17:15:54 http://www.jetbrains.com/idea/nextversion/editions_comparison_matrix.html 17:15:56 (unless it's some sort of upstream mascot thing) 17:16:27 (in which case its still a bad idea, just not ours. ;) 17:16:35 nirik: thankfully, that appears to be a feature owner put that there, not the upstream 17:16:44 what's wrong with monkeys anyway? 17:16:50 * dwmw2 likes monkeys 17:16:53 there's some responses to our questions on the discussion page 17:17:05 it's better than the reasoning behind bonobo :) 17:18:10 well, the commercial version has more features, but does that make the free one crippleware? 17:19:12 I guess intent matters. 17:19:31 The big issue is that these things 1. demotivate people from implementing the missing features (as they're being intentionally withheld) and 2. they're likely to be rejected if someone contributes them (again, as withholding them is intentional). 17:19:32 oh crud 17:19:37 right, and I am +1 for the feature 17:19:38 Nov 20 12:37:51 #agreed IntelliJ IDEA feature is accepted for F13 17:19:43 So those features will most likely never be added. 17:19:48 trac wasn't updated. :) 17:20:03 #action this was already accepted at the 2009-11-20 meeting 17:20:05 notting: I think this was reconsidered after that #agreed line. 17:20:06 * nirik goes to get more coffee 17:20:17 notting: I thought it was unaccepted after that? 17:20:37 not according to the agenda 17:21:08 Such a crippleware project is not a healthy Free Software project. 17:21:53 And I'm worried that advertising this will drive people to the proprietary edition instead of to what we package. 17:21:54 sharkcz: boo 17:21:56 it's not great, but we ship plenty of unhealthy things. in any case, since it wasn't un-accepted, i'd like to move onto the rest of the agenda for now 17:22:13 Kevin_Kofler: would be interested in how you think this compares to mysql, if you are against this and not mysql. 17:22:40 I'm not sure about how MySQL behaves there. 17:22:47 #topic Feature - Better Hostname 17:22:52 miniperl: hi, IDEA is again on the agenda, but it looks like trac wasn;t updated 17:22:56 .fesco 278 17:22:57 notting: #278 (Better Hostname - https://fedoraproject.org/wiki/Features/BetterHostname) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/278 17:23:21 this was considered, *not* accepted, and questions added to the discussion page 17:23:23 Kevin_Kofler: I think similarly; free software Community Edition, proprietary Enterprise Server. 17:23:47 but there haven't been any updates to the questions. i vote to defer this? 17:23:48 But I haven't seen how these differ feature-wise, so I can't really form an opinion. 17:24:00 But the discussion has moved on. 17:24:56 notting: +1 17:25:49 The only question that got answered was mine (and they basically said "KDE is free to talk to this over D-Bus", but nothing about acceptance from KDE upstream). 17:26:37 The other 3 questions got no answer. 17:28:39 the feature in-page got updated to be called 'Better Computer Names'; the page wasn't renamed 17:29:34 i suppose if anyone here is still -1 on the feature, it's also deferred 17:30:25 ... opinions? 17:30:28 * sharkcz is still +1 17:30:31 * nirik wasn't opposed to it, just wanted to know questions were answered and integration was considered. 17:30:35 Just to be clear on this, FESCo failing to adopt a feature doesn't prevent anyone from implementing the feature, right? 17:30:42 I'm for deferring it. 17:31:18 mjg59: right. Just doesn't get touted in press, etc. 17:31:21 mjg59: Well, it depends, if something is really a bad idea, we can outright forbid it. But by default, if we vote "not a feature", it's just not an advertised feature. 17:32:10 In general, we try not to tell maintainers what they can or cannot implement. 17:32:16 They should know best. 17:32:23 mjg59: in general, yes. there's been one or two where we've said "don't do that period", or "you need to go work with these other people". those were usually people outside of SIG asking to make changes to SIG 's spin. 17:32:53 my main concern was the sharing name... ie change your computer name to 'Secure Files'. I'm not sure how that ended up answered. 17:33:21 #action discussion on Better Hostname/Computer Name is deferred pending answers to questions on the discussion page 17:33:35 #topic Feature - User Account Dialog 17:33:38 .fesco 279 17:33:39 notting: #279 (User Account Dialog - https://fedoraproject.org/wiki/Features/UserAccountDialog) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/279 17:34:00 at last meeting, this was deferred with 4 +1, a couple of 0, and a -1 17:34:20 dgilmore added a question to the discussion page, which Matthias answered 17:34:22 * nirik is still +1, although sad that the gdm part will be minimal 17:35:09 dgilmore and skvidal aren't here. Kevin_Kofler was -1, dwmw2 had no vote earlier. 17:35:13 Kevin_Kofler: dwmw2: opinions? 17:35:30 (+1 votes from prior meeting: myself, nirik, jds2001, sharkcz) 17:36:28 sorry, SIGWENCH 17:36:30 So this has been clarified to primarily target the GNOME spin. 17:37:10 and local authentication? Or does it attempt to cope with ldap/AD/etc.? 17:37:11 I'm still a bit worried about the implications of Anaconda or firstboot trying to use this (it might end up sucked onto other spins as unwanted dependencies). 17:37:51 But I'm +1 if we can be sure that they're not going to break the KDE spin. 17:38:06 yeah, if done sanely, it seems reasonable 17:38:09 +1 17:38:28 ok. 17:38:37 #action User Account Dialog feature has been accepted for F13 17:38:56 #topic Feature - Copy/Paste Just Works 17:38:59 .fesco 286 17:39:00 notting: #286 (Copy/Paste Just Works - https://fedoraproject.org/wiki/Features/CopyPasteJustWorks) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/286 17:39:39 This one is about GNOME getting a feature KDE has had for years. 17:39:49 Kevin_Kofler: turns out gnome has it too. ;) 17:40:04 * notting is -1 to this, based on the opinions of people who know way more about X11/clipboards/etc than me 17:40:17 what's this about a familiar Ctrl-V sequence? 17:40:20 yeah, I don't know if I just stopped closing applications years ago but I haven't noticed a problem here in awhile 17:40:22 it's the middle button, dammit 17:40:37 it does still happen 17:40:42 Has this feature been run through the GNOME maintainers / "Desktop Team" yet? 17:40:48 I think gnome is supposed to do this already, and if it doesn't its a bug... 17:40:58 I select something in gitk, hit CtrlC and then try to paste it into the terminal I was running gitk from, and it's gone 17:41:05 I don't think we're in a business of approving features against the will of the responsible team/SIG. 17:41:05 Kevin_Kofler: that's who I asked. owen says if this doesn't work now, it's a bug, and it is very likely to break apps 17:41:20 Kevin_Kofler: and someone on the discussion page mentioned it broke inkscape 17:41:23 There was also an issue where firefox in particular didn't work with this. I think I was told it was a security thing (?!) 17:41:30 right, so -1 based on that. Ask the feature submitter to work with others to make sure it works? 17:42:39 dwmw2: sharkcz: opinions? 17:42:40 -1 to this feature and we should also make it clear that this cannot be implemented without approval from the spin maintainers. 17:42:50 -1 17:42:59 I'm kind of dubious about it 17:43:01 well, it certainly can be packaged, of course. 17:43:11 but not as default on the spin without the spin maintainer's approval. 17:43:15 yeah 17:43:20 Yeah. 17:43:57 -1 then, I suppose 17:44:30 #action CopyPasteJustWorks is not approved as a feature for Fedora 12. FESCo suggests the submitter work with the Desktop spin maintainers on this issue. 17:45:03 That would be 13, not 12. :-) 17:45:18 #action correction: Fedora 13 17:45:31 * nirik notes you can do #undo for just the previous thing 17:45:37 mjg59: so, that above would be one of those exceptions to the rule mentioned above 17:45:49 #topic Feature - Upstart 0.6.x 17:45:56 .fesco 287 17:45:57 notting: #287 (Upstart 0.6.x - https://fedoraproject.org/wiki/Features/Upstart0.6.0) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/287 17:46:25 * notting is +1 to this, as his name's on it 17:46:47 +1, tracking upstream is a good thing and I don't see any obvious drawbacks. 17:46:57 +1 here as well. 17:47:24 +1 17:47:24 how far out is 1.0? 17:47:31 sadmac: ? 17:47:33 Since when is updating to the current upstream a "fedora feature"? 17:47:40 when it's not even a major version bump 17:47:43 dwmw2: when it changes the job location and format slightly 17:48:01 notting: how's that different to an soname bump? 17:48:04 notting: hard to say. F-15 ish my guess 17:48:05 dwmw2: so we can tout we use the latest wizz bang upstart? 17:48:27 When it's the first thing which runs on the system, plays an important part in system startup, can help reduce startup times etc. 17:48:30 dwmw2: we've done features for latest upstream in the past (there's one for netbeans coming up later in the meeting) 17:48:39 so other maintainers can see if they should use the new dbus/service features? 17:48:56 ok, +1 then I suppose 17:49:07 We also systematically have GNOME 2.n and KDE 4.n as features. 17:49:20 well, that's a major user-visible component. 17:49:25 nirik: moving system scripts to native upstart is *not* encouraged yet 17:49:27 Well, should really be 2.2*n for GNOME, to be pedantic. ;-) 17:49:50 Kevin_Kofler: well, 3 will be on etoo :) 17:49:54 notting: yeah, might note that in an admon or something on the page? 17:49:54 ok 17:50:00 nirik: good idea 17:50:08 #action Upstart 0.6.x has been accepted as a Fedora 13 feature 17:50:24 #topic Feature - NetBeans 6.8 17:50:28 .fesco 288 17:50:28 notting: #288 (NetBeans 6.8 - https://fedoraproject.org/wiki/Features/NetBeans_6.8) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/288 17:51:02 we did a netbeans 6.7.1 feature for f12. this appears to be the followup 17:51:18 yeah, so is this really a feature? 17:51:36 Once again the "Just an update?" debate... 17:51:38 I guess it depends on how popular netbeans is... I do see users asking for it/using it in #fedora somewhat regularly. 17:51:51 nirik: we appear to have painted ourselves into a corner by approving the last one 17:52:09 yeah. 17:52:29 so +1, lets add it as a nice bullet point for people looking for it, and move on. ;) 17:52:44 +1 here too, can't hurt to advertise this. 17:52:49 +1 17:52:51 * notting is +1 17:53:48 dwmw2? 17:54:13 +1 17:54:30 #action NetBeans 6.8 feature has been approved for Fedora 13 17:54:45 #topic Feature - RPM 4.8 17:54:48 .fesco 289 17:54:49 notting: #289 (RPM 4.8 - https://fedoraproject.org/wiki/Features/RPM4.8) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/289 17:55:19 * notting is +1. newer/better/faster rpm is always good. 17:55:32 yeah, +1 here. 17:55:32 right :-) +1 17:55:45 good to see upstream moving along... and we should tout that 17:55:53 +1, new RPM is a good thing and certainly central enough to advertise. 17:57:17 dwmw2? 17:57:33 I suppose so 17:57:33 +1 17:57:58 #action RPM 4.8 has been accepted as a Fedora 13 feature 17:58:11 #topic Feature - Rollback with BTRFS 17:58:15 (Hi, this one is josef/me.) 17:58:16 .fesco 290 17:58:17 notting: #290 (Rollback with BTRFS - https://fedoraproject.org/wiki/Features/SystemRollbackWithBtrfs) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/290 17:58:21 last one! 17:58:29 * josef starts paying attention again 17:59:04 so, should we tout a feature that requires something we aren't using by default? 17:59:04 this is a neat idea. the '0%' worries me. 17:59:26 notting: josef e-mailed patches about 30 minutes ago :) 17:59:34 (for the btrfs side) 17:59:35 yeah no longer 0% :) 17:59:37 the concept worries me. Rolling back the _whole_ fs 17:59:41 more like 20% 17:59:49 dwmw2: Yeah. 18:00:11 cjb: how does one expire snapshots so they get space back? 18:00:17 Doing such whole-filesystem snapshots per default in yum (even if it's just by default for the users of an experimental filesystem) doesn't sound that great to me. 18:00:23 notting: you can just delete hte snapshot 18:00:26 notting: I think we would have yum keep no more than (say) five. 18:00:33 josef: can you? 18:00:34 but it's policy. 18:00:36 yeah 18:00:41 I didn't think that had been implemented yet :) 18:00:43 I can see shipping such a yum plugin, but it should not be installed or enabled by default. 18:00:49 dwmw2: yes, that went into Linus' tree in September. 18:00:51 yeah it went into 2.6.32 18:00:52 ah, ok 18:01:02 Kevin_Kofler: but why? 18:01:04 Kevin_Kofler: a plugin is all we're proposing 18:01:17 Kevin_Kofler: I mean, what's bad about taking snapshots? 18:01:32 * nirik wonders if work shouldn't happen on this, and then later when we switch to btrfs for default also tout this/make this a feature. 18:01:36 I think it's a cool plugin, but I'm not sure it's a feature -- not until we're using btrfs by default 18:01:40 Updating the system is not really a related action to taking a whole-system snapshot. 18:02:07 cjb: you yum update, get a bunch of emails, edit a file, then roll back... your email and files are back to the previous versions? 18:02:07 It might even confuse users into thinking the snapshot is just about the RPMs. 18:02:35 nirik: thats why you subvolume everything out intelligently 18:02:41 put your /home on a different subvolume 18:02:47 nirik: it's up to you. since btrfs is optional (and hidden behind a boot arg), you decided in anaconda whether you wanted /home to be the same or separate to /. 18:02:48 josef: what about /var? 18:02:50 given our current quorum, we can't approve (or disapprove) it now unless those of us here are unanimous. (i'm not saying we should stop discussion) 18:02:55 nirik: same idea 18:03:16 so have a /var/log and a /var/spool/ and a /var/lib seperate? 18:03:35 if you so choose 18:03:42 by the way, there was an LWN article about this; it isn't mentioned on the feature page: http://lwn.net/Articles/362500/ 18:03:44 you could rollback only one of your subvolumes 18:03:46 and not the others 18:04:04 course i guess that would mess up your rpm lib if you didnt rollback /var/lib/ 18:04:10 * nirik again thinks this is cool... but shouldn't it wait until btrfs is default? 18:04:24 * sharkcz likes the idea too 18:04:43 * nirik also notes 'yum history' in the package update/downgrade space. 18:04:44 I agree that this requires some pretty big documentation. But no-one will be using btrfs without knowing that they're experimenting, and no-one will be forced to perform a rollback unless they choose to explicitly. 18:04:47 yeah we can wait to advertise it when its made default, the work is still going to be done now 18:05:09 well, if we're waiting to advertise, then it would be a fedora $later feature 18:05:24 cjb: I'm worried that if we make this a f13 feature, it will appear on docs/media/etc and people will go: "cool. how do I use this" and will get confused because they didn't install with btrfs. 18:05:33 i'm doing the work now and it will be in F13 18:06:03 did we have a "Feature" for presto when it was still optional? 18:06:08 nirik: that's reasonable. they can, at that point, use the btrfs-convert tool to go from ext[34] to btrfs, if they want. 18:06:50 notting: yeah, I think we did. 18:07:21 I suppose we could mark this a "Tech Preview" feature or something to indicate it's not default/requires some setup 18:08:13 btw, as mentioned on the feature page, our primary target is actually Fedora developers running Rawhide. 18:08:49 (or rather, Fedora developers who would not be willing to run Rawhide under normal circumstances, but are happier to if they have a handy "go back to yesterday" button.) 18:09:32 so I agree the advertising to users vs. developers should be somehow different. 18:09:52 yeah, there are different sections of release notes and such for them... 18:09:58 ah, that's good 18:10:07 but some of the talking points and such are just bullet lists... 18:11:22 I guess if we make sure we communicate it well I would be ok with this being a feature. (for developers, tech preview, etc) 18:12:26 so, should we take a vote? 18:13:34 sure. 18:14:09 +1 18:14:26 +1 (with the advertising priviso) 18:14:49 * notting is +1 18:16:26 dwmw2 / Kevin_Kofler ? 18:16:51 +1 18:17:37 +1, I guess it can be useful to some folks, so we can as well advertise it. 18:17:54 #agreed Rollback with BTRFS has been approved as a F13 feature 18:18:39 that's it for the agenda 18:18:43 #topic Open floor 18:18:52 Did you guys do the FPC stuff? 18:18:58 no! 18:18:59 oops. 18:19:07 forgot to enter a ticket 18:19:18 spot did create a ticket. 18:19:32 not seeing it 18:19:56 .fesco 285 18:19:57 sharkcz: #285 (Fedora Packaging Committee items for ratification (2009-12-02)) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/285 18:20:07 that could be because i'm blind 18:20:11 #topic FPC report 18:20:29 #topc RPM handling of pkgconfig requires 18:20:54 * notting is +1 18:20:54 It's all just tweaks to keep up with the current state of the various components. 18:21:10 +1 18:21:25 +1 18:21:25 yeah, +1 on that. 18:21:37 No need to explicitly require what RPM already handles. 18:22:10 Honestly this was probably a "just do it" kind of thing, but... 18:22:21 dwmw2: want to make it official? 18:22:37 +1 18:22:59 #agreed pkgconfig guideline change approved 18:23:09 #topic Emacs Packaging 18:23:42 all greek to me 18:23:46 In F12+, emacs grew some rpm macros that let us add a bit more sanity to the packaging. 18:24:12 The only changes are to use those macros and to remove unneeded stuff from the templates (like buildroot). 18:24:22 OK, that sounds sane. 18:24:23 yeah, +1 on that as well. 18:24:23 +1 18:24:30 given that description, +1 18:24:30 +1 18:24:33 +1 18:24:57 #agreed Emacs guideline change approved 18:24:58 It cuts out about ten lines of cut-n-paste crap. 18:25:30 #topic PHP guidelines revised 18:25:31 Simplifying things is always a good thing. :-) 18:27:00 Small nitpick: why "%if %{?php_zend_api}0" and not the more common "%if 0%{?php_zend_api}" idiom? 18:27:00 All of this is minor. I'm not so up on PHP, but it clarifies a couple of things related to file placement and explicitly addresses what you need to do on EPEL versus what you can do with current Fedora. 18:27:10 (It doesn't make any real difference though.) 18:27:23 * notting is +1 18:27:40 Here too, this just seems to document current macros. 18:27:42 +1 18:27:42 We could probably go over the guidelines for consistency with idioms like that. 18:27:47 +1 18:27:53 yeah, +1 18:28:16 dwmw2? 18:28:33 +1 18:29:17 #agreed PHP guideline revision approved. 18:29:22 ok, now back to... 18:29:25 #topic Open floor 18:29:29 anything else? 18:29:39 Thanks. 18:29:52 no problem, my bad for missing it in the ticket list. 18:30:09 I switched over to using the more common %if 0%{foo} idiom. 18:30:32 Spot's planning to write up and announce a whole pile of backlogged guideline changes at fudcon. 18:32:19 if no one speaks up, i'll end the meeting in 1 minute 18:32:52 Nothing more from me. 18:33:02 ... meeting will end in 30 18:33:36 #endmeeting