=== emgent is now known as emg === emgent is now known as \emgent === \emgent is now known as emgent === Varka_ is now known as Varka === bmk789 is now known as bmk789_sick_bed === bigon is now known as bigon` === j_ack_ is now known as j_ack === czessi_ is now known as Czessi [07:26] word === ogra1 is now known as ogra === ubotu changed the topic of #ubuntu-meeting to: Current meeting: MOTU Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 23 Jan 20:00 UTC: Edubuntu meeting | 23 Jan 22:30 UTC: Forum Council | 30 Jan 12:00 UTC: Edubuntu meeting === asac_ is now known as asac [11:59] * persia encourages someone to volunteer to chair the meeting [12:00] o/ Hi, guys. [12:00] Hi [12:00] heya [12:00] hi all [12:00] Greetings all. [12:01] soren: does "o/" mean you volunteered? :) [12:01] * soren runs away, screaming. [12:01] if not and nobody else wants to, I can do it [12:01] hey sistpoty|work [12:01] hi dholbach [12:02] ok, let's get started [12:02] #startmeeting [12:02] Meeting started at 12:02. The chair is dholbach. [12:02] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [12:02] we have an agenda: https://wiki.ubuntu.com/MOTU/Meetings [12:02] first up is persia [12:02] [TOPIC] REVU Day scheduling: Should REVU Days be held on the 4th and 11th of February, or should we stop sooner so as to provide time for the archive admins to process NEW? Also, any suggestions for a last push? It would be unfortunate to have a package be all ready on REVU and not make the archive due to too few reviewers [12:02] New Topic: REVU Day scheduling: Should REVU Days be held on the 4th and 11th of February, or should we stop sooner so as to provide time for the archive admins to process NEW? Also, any suggestions for a last push? It would be unfortunate to have a package be all ready on REVU and not make the archive due to too few reviewers [12:02] In the Gutsy cycle, there was some confusion about whether the deadline for new packages meant the last date on which a package could be uploaded to NEW without a freeze exception, or the last day the archive admins would process a package without a freeze exception. [12:02] My memory of earlier discussions this cycle was that we had agreed that FeatureFreeze was the last day the archive admins would be expected to process source NEW without a freeze exception. [12:02] Based on that understanding, I wonder if we oughtn't have 27 January be the last REVU day, perhaps with some specific packages for which a MOTU has explicit interest, or are needed for a Feature goal receiving attention thereafter, but no scheduled general REVU days. [12:02] Also, there are a fair number of packages still in their final REVU cycles. If anyone has any ideas about how to best grab those we want for hardy in time for FeatureFreeze, please share. [12:03] persia: What do you suggest as deadline? [12:03] FF is the 16th, if memory serve? [12:03] serves? [12:03] soren: 14th [12:03] Happy Valentines Day :) [12:03] Ok. I think 27th is too conservative. [12:04] 14th I think. I'm not sure we should impose a deadline, but from informal discussions I understood the archive admins wanted a couple weeks. [12:04] Feb 4th should be plenty of time for NEW processing. [12:05] I think 4th should be fine, especially given that exceptions can still be granted by motu-uvf (motu-ff? :)) [12:05] 4th sounds good. [12:05] 4th is fine with me. [12:05] [AGREED] Feb 4th is deadline for uploading NEW packages. [12:05] AGREED received: Feb 4th is deadline for uploading NEW packages. [12:05] Err. No. [12:06] February 4th is the last regularly scheduled REVU day. [12:06] 4th looks good. Maybe ask a confirmation to archive admin? [12:06] 13:05:20 < soren> pitti: How does Feb 4th sounds as a (soft) deadline for submitting new packages? That leaves 10 days for NEW processing before FF. [12:06] 13:05:59 < pitti> soren: sounds ok (although the current policy already accounts for processing the backlog) [12:06] soren :) [12:07] ok... persia: what would you like to see as a deadline? [12:07] 4th as a soft deadline is probably sensible. That still leaves time to work out the last few issues that might be raised, and if there's "urgent" stuff, it can still make it. [12:07] dholbach: I don't think the deadline is ours to propose, but rather an archive-admin decision. [12:07] Opinions? [12:08] * sistpoty|work agrees with persia [12:08] Well, the deadline we propse it the deadline before which people should submit their stuff if they expect it to be reviewed before FF. [12:09] It's not exactly the deadline for uploading the packages. [12:09] soren: so you want rather a "we won't review packages uploaded after " deadline? [12:09] (newly uploaded packages even) [12:09] soren: Ah. I thought you were talking about deadline for upload to the archive. For upload to REVU, I think 3rd Feb (for inclusion in 4th Feb REVU day) is perfectly sensible. [12:09] I'm happy to have the last REVU day on Feb 4th and our "soft deadline" shortly afterwards [12:10] to guarantee the archive admins have enough time [12:10] sistpoty|work: Something like that, yes :) [12:10] Also, I think any MOTU interested in a specific package should be free to ignore that deadline for further review, as long as it doesn't annoy the archive-admins. [12:10] soren: sounds good :) [12:10] OK... what do we agree on now? [12:11] * persia thinks we agree that packages not submitted for the 4th February REVU day do not have a guarantee of review for inclusion in hardy. [12:11] how big is the revu backlog atm? [12:11] persia: that's good enough [12:11] sistpoty|work: Only two or three packages that didn't get hit in the last REVU day, and about 25-30 that will be part of the next. [12:11] [AGREED] packages not submitted for the 4th February REVU day do not have a guarantee of review for inclusion in hardy [12:11] AGREED received: packages not submitted for the 4th February REVU day do not have a guarantee of review for inclusion in hardy [12:12] persia: ah, ok [12:12] regarding "Also, there are a fair number of packages still in their final REVU cycles. If anyone has any ideas about how to best grab those we want for hardy in time for FeatureFreeze, please share." - do you think it'd help to have blog entries with a list of those packages to raise interest? [12:12] Anyone have any ideas about how to encourage more reviewers for the next three REVU days? Lots of packages are close, but it needs more eyes. [12:13] Unfortunately, I won't be around for the january 27th day [12:13] But will do my best to attempt to help with the others [12:13] dholbach: Depends on the goal. If the goal is to advertise packages interesting to the blogger, sure. If the goal is to list things, I think the blogger reviewing everything would be more useful. [12:14] we can also post the list of packages that are 'nearly there' to ubuntu-motu@ and ubuntu-devel@ [12:15] there are a lot of people who don't scan REVU regularly [12:15] That sounds sane. I'll post a list of packages needing review at the start of the next REVU day. [12:15] Any other ideas? [12:16] * pochu waves [12:16] that's a great start [12:17] * persia cedes the topic, based on discussion having come to a close [12:17] you're right... a blog might probably not adress the right people [12:19] ok... sorry I was distracted by another question [12:19] moving on [12:19] [TOPIC] Other business [12:19] New Topic: Other business [12:19] is there any other business? [12:19] going once [12:19] twice [12:19] [TOPIC] agree on date and time of next meeting [12:19] New Topic: agree on date and time of next meeting [12:20] * persia proposes 2008 February 1st 20:00 UTC [12:20] any opinions on date and time? [12:20] * dholbach will probably not make it [12:21] DktrKranz: any opinion on date and time of the next MOTU meeting? (2008 February 1st 20:00 UTC :-)) [12:21] Sounds good for me [12:22] (and proably will attend ...) [12:22] ok... in absence of andbody complaining.... :-) [12:22] [AGREED] Next MOTU Meeting is going to be 2008 February 1st 20:00 UTC [12:22] AGREED received: Next MOTU Meeting is going to be 2008 February 1st 20:00 UTC [12:22] Meeting adjourned - thanks a lot everybody! :) [12:23] #endmeeting [12:23] Meeting finished at 12:23. [12:23] Who is doing minutes? [12:23] How about announcements for the next meeting? [12:23] http://kryten.incognitus.net/mootbot/meetings/ubuntu-meeting.20080118_1202.html [12:23] I'll do the announcement [12:23] * DktrKranz kicks at himself for being late. [12:23] * dholbach hugs DktrKranz [12:23] DktrKranz: Since you have to read the logs anyway, maybe you want to do minutes? [12:24] My next car will have wings, I swear!!! [12:24] DktrKranz: be sure to post pictures! :) [12:24] persia, sure. [12:24] excellent - thanks a lot :) [12:24] * dholbach hugs persia and DktrKranz :) [12:24] dholbach, can you remind me where mootbot shortlogs are? [12:25] hi all [12:25] DktrKranz: if you click on the meeting times it'll take you to the log (http://kryten.incognitus.net/mootbot/meetings/ubuntu-meeting.log.20080118_1202.html) [12:25] thanks [12:25] DktrKranz, http://www.gyrotec.de/ [12:25] they are pretty cheap :) [12:25] DktrKranz: Also, ignore the first "AGREED". [12:26] ogra: Those are too stubby to properly be called wings [12:26] ogra, nice one. I need to check if Italy permits them, and no more traffic issues \o/ [12:26] persia, it flies (with 200km/h) [12:27] ogra: Yes. I admit it's a flying car. I'm just being pedantic and complaining that it's not a car with wings. [12:27] germany permits them (eastern german police uses them for traffic control) [12:27] When I last lived in the united states, they were permitted for unlicensed use. [12:27] its not a helicopter .... it doesnt crash if you switch off the engine ;) [12:28] Is it euro4? So I haven't to pay pollution taxes :) [12:28] heh [12:29] * sistpoty|work is off again, continue with working [12:29] cya === bigon` is now known as bigon === ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 23 Jan 20:00 UTC: Edubuntu meeting | 23 Jan 22:30 UTC: Forum Council | 30 Jan 12:00 UTC: Edubuntu meeting === Hobbsee_ is now known as Hobbsee === bigon is now known as bigon` === bigon` is now known as bigon === ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 23 Jan 20:00 UTC: Edubuntu meeting | 23 Jan 22:30 UTC: Forum Council | 30 Jan 12:00 UTC: Edubuntu meeting | 01 Feb 20:00 UTC: MOTU === \sh_away is now known as \sh === Pricey is now known as PriceChild === bigon is now known as bigon` === bigon` is now known as bigon === illovae_ is now known as illovae === mvo__ is now known as mvo === bigon is now known as bigon` === bigon` is now known as bigon === bigon is now known as bigon` === bigon` is now known as bigon === cjwatson_ is now known as cjwatson === bigon is now known as bigon` === bigon` is now known as bigon === bigon is now known as bigon` === bigon` is now known as bigon === doko_ is now known as doko