18:00:01 #startmeeting proventesters (2011-09-28) 18:00:01 Meeting started Wed Sep 28 18:00:01 2011 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:01 #meetingname proventesters 18:00:01 The meeting name has been set to 'proventesters' 18:00:01 #topic init process/agenda/why are we here? 18:00:13 hello proventesters... anyone around to meet up? 18:00:18 * tflink is around 18:02:10 * Southern_Gentlem 18:03:32 smaller crowd today. ;) 18:03:37 * nirik will wait another minute or two 18:03:40 * adamw kinda here 18:03:57 but poking efi stuff on my main box. 18:05:03 ok, lets go ahead and dive in... might make it a short meeting. 18:05:10 #topic Stats/Info 18:05:29 tflink: you had generated some stats about which updates were still in updates-testing and for how long? 18:06:11 yeah, crude output is at http://tflink.fedorapeople.org/testing_stats/ 18:07:08 did you get that from looking at the db? or ? 18:07:21 grabbing data from bodhi 18:07:23 I wonder if we could ask lmacken to adjust the reports bodhi sends out to include that info? 18:08:06 I just grabbed all the packages in testing and filtered out all the ones that were critpath and hadn't requested push to stable yet 18:08:29 Dunno how handy it would be, but it might shame people seeing how many days there... 18:08:50 Southern_Gentlem: I failed to propose a list for the testable stuff last week. ;( I'll try and do so this week... 18:09:13 tflink: there is also an API for that, /critpath?unapproved=True&release=F16 18:09:35 lmacken: ah, didn't realize that. I was just using fedora.client 18:10:11 tflink: ah yeah, I need to expose that in the BodhiClient 18:10:32 lmacken: how hard would it be to add 'N days' in front of each entry in the 'have yet to be approved' 18:10:50 lmacken: but I don't think that would get the the same data 18:10:50 nirik: not hard at all 18:11:05 I was interested in all non-pushed updates, not just the unapproved ones 18:11:45 tflink: ah, ok. 'unapproved' just implies status!=stable 18:11:49 or do we assume that its the maintainer's responsibility to request push to stable once it's approved 18:11:55 but it should really be request!='stable' 18:12:04 lmacken: oh, I assumed it was the critpath_approved data 18:12:07 tflink: depends on if autokarma is enabled 18:13:05 tflink: ah yeah, it does use that data as well 18:14:24 I guess that the first question is if this data is useful 18:14:54 I kind of think it is... 18:15:03 but it's hard to say what will motivate people. 18:15:04 * tflink hasn't had the chance to check, but has suspicions that there might be old non-obsoleted but replaced builds in those lists 18:15:31 it's useful, but I think we need to do a better job of making it obvious what needs testing on the web interface, which is what I've been working on lately 18:16:13 ok. 18:16:18 http://lewk.org/img/bodhi-20-frontpage.png 18:16:23 I can keep those lists updated and make them easier to read in the mean time 18:16:58 lmacken: how far out is the mythical 2.0? ;) 18:17:17 nirik: I'm not quite sure yet, but I've been making a lot of progress lately. 18:17:31 I already have db migration written, and my next step is working on form generation & validation 18:19:12 cool. Wonder if doing some kind of 'these things need done before we can release' checklist would be good. 18:19:43 yeah, I'll make an effort to keep the bodhi2 wiki page up to date 18:19:59 cool. 18:20:01 nirik: probably but not sure if bodhi is the best place for that 18:20:12 unless there are plans that I don't know about 18:20:31 place for which? release checklist? or the days in testing? 18:20:37 release checklist 18:20:56 yeah, wiki page or bodhi's trac would be the place for that. 18:21:09 with the recent efi mess, that's on my list of things to think about once things calm down a bit 18:21:28 sounds good. 18:21:38 #topic Outreach 18:21:56 So, how can we get more testers and proventesters? anyone have any ideas we can brainstorm? 18:23:28 * nirik will try and gather ideas. 18:23:32 perhaps we can come up with some ways. 18:23:50 #topic Open Floor 18:24:07 sorry, distracted trying to get a test run 18:24:10 Folks are a bit busy today... so anything for open floor? or shall we call it a quick meeting. 18:24:19 yeah, me too... busy week. ;( 18:26:11 * tflink is tempted to say quick meeting 18:26:24 I have a couple of ideas on the outreach idea at some point, though 18:26:41 yeah, I have a few... not sure how well they would pan out, but might be worth trying. 18:26:57 anyhow, yeah, lets call it a quick meeting... 18:27:01 and try next week. ;) 18:27:13 as long as we don't slip again :-/ 18:27:20 yeah. 18:27:26 ok, thanks for coming folks! 18:27:30 #endmeeting