21:00:14 #startmeeting EPEL Meeting 21:00:23 #topic Init Process / Roll Call 21:00:30 who all is around for an epel meeting. 21:00:35 * jds2001 21:00:47 #info 21:01:35 * nirik will wait a few more for more folks to show up. 21:01:50 itamarjp: that just notes an information for the log... not info about the meeting. ;) 21:02:47 here 21:03:24 I guess we can go ahead and start in... 21:03:31 #topic Blocking packages already in RHEL 21:03:47 So, ricky was kind enough to run a script and find some packages in both epel and rhel. ;( 21:04:05 any where we'er favored? 21:04:07 is there any reason we shouldn't just go block them all asap and remove them from epel? 21:04:20 i.e. our evr is higher? 21:04:45 in rhel4 only one I see: 21:04:53 perl-TimeDate 21:05:26 well the issues are : were they tech-previews and now not 21:05:41 in rhel5: perl-Net-Telnet and python-setuptools 21:05:55 im not entirely sure that it matters if they were tech-preview or not. 21:05:58 looking more closely tho, some of the list doesn't seem right 21:05:59 the script shows against RHEL5 in RHN and that will show stuff they don't support any more 21:06:00 or maybe still are. 21:06:32 so the issue with tech-previews or some other items is that RHEL-5.1 might have had it but 5.2+ might not 21:06:43 i dont think anything has ever been dropped, has it? 21:06:57 is there any way we can identify such things? 21:06:59 just moved from tech-preview to supported. or forever tech-preview. 21:07:20 either way, it's included in the distro. 21:07:22 I check against CentOS myself :) 21:07:36 if its not in 5.4 its no longer supported :) 21:08:03 basically the usual check is release notes or looking in the .src.rpms 21:08:10 * ricky is here 21:08:19 hey ricky. ;) 21:08:47 ricky: I see in your version check that trowsers is listed in both, but only the rhel version is listed? 21:08:52 Ah, so centos could be a good place to check 21:09:36 Interesting, I must have done something wrong with the script I used 21:10:10 I can take care of filing bugs on the 2 packages with duplicate files ownership... unless someone else would like to do that? 21:10:38 There definitely seems to be an EL-5 branch for trousers, but now that I search for it, I only see the one from Red Hat. 21:10:46 then for the rest we need a final list of what we are going to remove, post to the list and maintainers and watch for screams and then remove them. 21:11:21 yes. it would be good to see if it was something like "They said they were moving it to EPEL" 21:11:33 which in some ways is positive for EPEL :) 21:12:30 * Jeff_S pokes his head in late 21:12:36 sorry, had a phone meeting 21:12:58 welcome Jeff_S 21:13:53 so, does someone want to take lead on the list of packages we need to nuke? 21:15:04 I will 21:15:18 excellent. 21:15:36 #action smooge will generate a list of packages that overlap that we should block/remove. 21:15:49 I will have it by next meeting 21:15:50 #action nirik will file bugs on the packages that have conflicts with files in rhel packages. 21:16:04 Anything else on this? or shall we move on? 21:16:41 #topic Incompatible version upgrades process/guidelines 21:16:44 smooge: My (pretty simplistic) scripts are in ~ricky/epeltest on puppet1 if you're interested - we can hopefully get them in a repo somewhere and polish them up 21:17:00 ok thanks 21:17:18 so, we had a meeting a few weeks back where it seemed the consensus was to just announce them, try and notify people and then just do it. 21:17:22 is that still the case? 21:17:54 if so, I think we should come up with a guideline on how to notify people, what to do when, etc. 21:18:43 or do we need more discussion on what we want to do? 21:18:44 I believe so 21:18:56 that seems reasonable (the draft guidelines part) 21:18:58 I believe that the method you said is what we agreed on 21:19:00 nirik: seemed to me like we're all in agreement 21:19:03 slow typer 21:19:35 would someone like to write that up? I had a proposed one on the mailing list. 21:19:55 or would you like me to try and do so. 21:20:07 sure, i can take a stab at it 21:20:19 cool. 21:20:30 by the way, thankyou jds2001 for doing an epel blog 21:20:49 #action jds2001 will write up an incompatible upgrades policy draft on the wiki 21:20:53 np. hope it made sense :) 21:22:00 shall we move along then? 21:22:19 yes please :) 21:22:23 #topic EPEL roadmap - where do we go from here? 21:22:42 I stuck this on the list... does anyone have pie in the sky dreams for epel we could work toward? 21:22:42 to drink beer :) 21:22:46 EVERY PACKAGE IN EPELE!!!! 21:22:53 what do we want in a shiny utopia of ideal epel? 21:23:05 jds2001: a fine plan. ;) 21:23:20 no bugs ;) 21:23:23 smooge: yeah, that would be cool. If might even be close to possible on rhel6 for a short time. 21:23:45 yeah, killing all bugs would be nice too. 21:23:47 i somehow doubt it :) 21:23:48 I would like EPEL to be a base set of packages outside of RHEL that sites could use to install other packages 21:23:53 better inter-op with ie. centos-extras, dag, etc. would be nice for users 21:24:41 Jeff_S I wish for that too.. but in the end it boils down to the politics of the CLA or not 21:24:47 BTW, we currently have 138 EPEL bugs. 21:25:10 so, how can we move toward all or any of these goals? 21:25:28 nirik: the only one I have an easy solution for is jds2001 suggestion 21:25:29 * jds2001 was supposed to investigate using python-fedora to get viable list of bug 21:25:50 * jds2001 failed there 21:26:00 sounds like we need to start paying more attention to bugs and/or driving more people to help with them 21:26:05 well Jeff_S's goal would probably be to keep interacting with the other groups at conferences and outside to see if there is any common ground. 21:26:38 smooge: the common ground is there, and the users typically just want things to work. it's not easy to make that happen though if it's possible at all 21:26:40 my goal was more of a joke, but I think that when EL-6 comes out we will be able to have a "Testing" with lots of stuff in it 21:26:41 I see the centos folks are talking about a review/guidelines for extra packages on the devel list. 21:26:56 * jds2001 is now officially broke sense i moved to NYC :) 21:27:06 the conference-going budget is slashed :D 21:27:08 jds2001: eww 21:27:25 ! 21:27:27 Jeff_S: eww what? 21:27:31 @ 21:27:34 # 21:27:35 inode0: feel free to jump in. 21:28:01 Is anyone from EPEL going to the Summit? If not I'd be happy to proxy for EPEL to try to gather information. 21:28:15 * jds2001 is not going :( 21:28:19 * jds2001 sad cookie. 21:28:21 jds2001: ewww not having $$ 21:28:30 inode0: I'm not 21:28:30 * nirik is not gonna be there. ;( 21:29:12 Just asking people, "do you use EPEL?" might be interesting. 21:29:41 I won't be going to the summit 21:29:49 yeah, that would be great if you could do some informal polling 21:30:11 this summit seems more like a "Who is going?" versus "Who isnt" 21:30:47 yeah, first one in 3 years i've missed 21:31:48 inode0: if you're willing to ask around and let us know what people say that would be great. ;) 21:32:11 shall we move on then? 21:32:31 i may go one day 21:32:39 #action inode0 will be at the summit and ask folks about EPEL for us. 21:33:06 #topic Open Floor 21:33:13 any items for open floor from anyone? 21:33:48 not for me 21:33:55 nor I 21:34:20 * nirik will close out the meeting in 60sec if nothing comes up. 21:35:11 thanks everyone 21:35:19 that was fast 21:35:21 #endmeeting