[09:43] ubiquity: evand * r3850 ubiquity/ (debian/changelog ubiquity/frontend/kde_components/PartMan.py): [09:43] ubiquity: Fix references to create_label and allow_change_step in the KDE [09:43] ubiquity: frontend's PartMan module (LP: #527932). [10:17] ubiquity: evand * r3851 ubiquity/ (debian/changelog ubiquity/components/ubi-console-setup.py): [10:17] ubiquity: str.split returns a list of one empty string when splitting on an [10:17] ubiquity: empty string. [10:23] partman-base: cjwatson * r183 ubuntu/ (52 files in 5 dirs): merge from Debian 138 [10:23] Error: Debian bug 138 could not be found [10:54] ev: is anyone working on converting ubiquity-slideshow-ubuntu to po4a? translate-toolkit no longer ships po2html (the changelog says it was too badly broken to use), so u-s-u won't build, but I started on the change and it seems fairly complex [11:07] cjwatson: ah, lovely. I'll take care of it. [11:22] ok, cool [11:23] I mostly noticed because the current slides/index.html has been mangled onto a single line, including JavaScript comments, which extend to the end of the line :-) [11:23] ah, yikes [11:26] dear po4a, thanks for not using return codes. No love, Evan. [11:27] you mean for whether something was translated? you probably just want to let it decide that itself ...? [11:28] yeah, good call [11:28] it has a --keep option which is sometimes useful for tuning things [11:29] indeed, though I'm not sure what a reasonable value for that would be. I'm inclined to keep it at 0 for at least the time being, so there's not confusion as to why certain translations are not showing up. [11:30] yeah, or maybe 1, which would mirror the current behaviour (any translations at all => keep it) [11:31] ah, right [11:31] thanks [11:31] ubiquity: cjwatson * r3849 parted-2.1/ (4 files in 2 dirs): [11:31] ubiquity: Automatic update of included source packages: partconf [11:31] ubiquity: 1.32ubuntu1~ppa1, partman-base 135ubuntu5~ppa1. [11:31] anyway I should stop back-seat-driving :-) [11:34] I'm always appreciative of the advice, but I'll interpret that as "I've got other things to do and I'm being polite" ;) [11:35] no, I just remembered how it's really annoying to be trying to do something when people are going "but you could paint it RED" [11:36] haha, fair enough [11:36] ubiquity: cjwatson * r3850 parted-2.1/debian/changelog: releasing version 2.1.29~ppa1 [11:37] mmm optimal address alignment [11:38] I'm still not sure whether partman needs to do anything special to make use of it [11:38] do you have any hardware that cares? [11:39] not to my knowledge [11:39] Scott might, he was asking for it the other week [11:40] I think the default is probably cylinder-alignment [11:40] probably have to hit it with ped_device_get_optimal_aligned_constraint [11:40] or something [11:42] hmm, it would help if we built parted against blkid [11:42] indeed [11:57] ev: what's the status of bug 336751? [11:57] Launchpad bug 336751 in ubiquity ""Starting up the partitioner" uses separate window misleadingly" [Low,Confirmed] https://launchpad.net/bugs/336751 [11:59] if memory serves, michaelforrest doesn't believe it's a bug, and definitely didn't did not like the solution I came up with of providing a transition between pages with a GtkSpinner embedded in the window. [12:00] michaelforrest: is that accurate? [12:01] I think that's a different bug [12:03] having the full page spinner for normal transitions (that are also accompanied by a spinning mouse cursor) is definitely a no-no. This bug you're talking about now is to do with avoiding any new windows being spawned [12:03] I'm not sure what the solution is [12:03] do we need to say 'starting up the partitioner' at all? can't we just spin the mouse cursor like everywhere else and wait for it to appear? (is it in a new window?) [12:04] (by the way, we do have a much nicer idea for this sort of thing in future, but it's not quite designed-up yet!) [12:05] I'll add my comments to the bug, shall I [12:05] ubiquity-slideshow-ubuntu: evand * r215 ubiquity-slideshow-ubuntu/ (debian/changelog slideshows/kubuntu/slides/chat.html): Fix typo in Kubuntu chat slide. [12:05] ev remind me - how long does it take for that window to appear normally? [12:06] or is it proportional to hard drive size / cpu? [12:06] a few seconds [12:06] at most [12:07] do you have a screenshot handy? [12:07] (I can get one - not a big deal if not) [12:07] of what it looks like with the window up? [12:07] partitioner time taken is roughly proportional to the number of partitions [12:07] ok so I've selected "Specify partitions manually" and clicked "Forward" [12:08] it's roughly five times faster in lucid now than in karmic [12:08] I would like the button itself to become disabled and contain the progress bar... [12:08] but I still have a (not completely unreasonable) test case where it takes 15 seconds or so to start up [12:08] obviously when that was a minute plus, it was more of a big deal [12:10] maybe now we could just spin [12:11] I think part of what annoyed mpt is that you get a dialog popping up after some operations in the manual partitioner, not just at startup [12:11] well, maybe not, that's not what his bug says, looking at it [12:11] it annoys me :) [12:12] this came up in the dallas design sprint basically - it's just about avoiding new windows [12:12] michaelforrest: would it make a difference to have the full-page spinner *just* for partitioner startup, not for other page transitions? [12:12] I agree that it is jarring to have it for all page transitions [12:13] cjwatson: that full page thing is just awful and should be forgotten about as soon as possible [12:13] ok [12:13] I have responded to the bug - I hope you think my suggestion makes sense [12:13] I think it came from mpt's comment "So, I suggest that while waiting for the partitioner to launch, the spinner should be centred in the pane" [12:13] yeah .. no :) [12:14] no? [12:14] so I'm saying we change the text of 'Forward' to 'starting partitioner' [12:14] the only query I have there is that it would cause the Forward button to expand very significantly, and push everything else to the left [12:14] wouldn't that look odd? [12:14] michaelforrest, so "Back" should temporarily jump to the left? [12:14] so that it's not too disconcerting that it's taking longer than usual [12:14] mpt: I don't see why not. The decision has been made now- it's not like the user is aiming for the button [12:14] how about instead we show the partitioner page, but put "Starting partitioner..." in its contents? [12:15] cjwatson: I would be happy with that solution too [12:15] and then fill in the proper contents of the page once we know what they should be [12:15] yeah that works for me [12:15] (and spin the mouse cursor, of course) [12:15] michaelforrest, because it would look ugly [12:16] but a full screen blank screen with a spinner in the center is beautiful? [12:16] michaelforrest, no, but it would be less ugly. It's the same as (for example) System Preferences panes when they're slow to load. [12:17] I think we have a solution here now - colin's suggestion is informative and responsive in a way that staying on the same page while waiting won't be [12:17] so it's moot [12:18] ev: what do you think about my temporary-page-contents option? I forget how straightforward that is to implement [12:18] for operations in the manual partitioner, I think now we can probably just ditch the progress dialog there and use a spinner [12:19] cjwatson: manual partitioner operations> we already do [12:19] ok [12:19] I'm obviously behind [12:20] cjwatson: I'm a bit confused, are you saying we should put this "starting partitioner..." message on just the advanced partition page listview as it starts, or would we also be placing it somewhere on the automatic page as it starts? [12:21] I think I mean on the advanced partitioner page as it starts; for the automatic partitioning page, it seems to me that we'd probably be better off with just a spinner [12:21] gotcha [12:21] particularly now that os-prober output will have been cached from earlier on [12:21] (clock-setup runs it) [12:21] okay, so would be it be okay to use the existing spinner and progress message location on the advanced partitioning page for this? [12:22] indeed [12:22] do we have a progress message on the advanced partitioning page, other than in the progress dialog? [12:22] michaelforrest, sure, that sounds fine [12:24] cjwatson: yes, http://people.canonical.com/~evand/tmp/transitions.html - ignore the page transitions, skip straight to the advanced partitioning page [12:24] assuming I correctly understand your question [12:26] ev, maybe you want to suppress the spinner until/unless the next step has taken more than, say, 2 seconds to display -- otherwise the installer might seem slower than it is [12:26] Otherwise, that looks pretty cool [12:26] OK, I'd forgotten that had landed. Modulo mpt's comments, yeah, I think that's fine [12:26] mpt: just to be clear, by spinner we're talking about the spinning mouse cursor, correct? [12:27] so we can display the full list box and all the furniture of that page, and just have that in-page spinner and progress message [12:27] yarp [12:27] ev, no, the GtkSpinner as shown in that Flash [12:28] on the advanced partitioning page? [12:29] commented on the bug; does this match everyone's understanding? [12:31] yes [12:38] ubiquity-slideshow-ubuntu: evand * r216 ubiquity-slideshow-ubuntu/ (4 files in 2 dirs): Move from po2html, which is no longer included in Debian, to po4a. [12:45] speaking of the slideshow, Dylan became an Ubuntu member last night. An attempt to gain per-package upload rights will hopefully follow :) [12:49] cool [13:17] ubiquity-slideshow-ubuntu: evand * r217 ubiquity-slideshow-ubuntu/debian/ (5 files): [13:17] ubiquity-slideshow-ubuntu: Make each slideshow package Replace and Conflict the ubiquity- [13:17] ubiquity-slideshow-ubuntu: slideshow virtual package, to ensure that only one slideshow can be [13:17] ubiquity-slideshow-ubuntu: installed at a time and so we can put all of the files in a single [13:17] ubiquity-slideshow-ubuntu: location (LP: #526483). The upgrade slideshows do the same with the [13:17] ubiquity-slideshow-ubuntu: ubiquity-slideshow-upgrade virtual package. [13:34] ubiquity-slideshow-ubuntu: evand * r218 ubiquity-slideshow-ubuntu/ (debian/changelog update-launchpad-translations.sh): [13:34] ubiquity-slideshow-ubuntu: Update update-launchpad-translations.sh to reflect recent directory [13:34] ubiquity-slideshow-ubuntu: layout changes. [14:01] ubiquity-slideshow-ubuntu: evand * r219 ubiquity-slideshow-ubuntu/ (134 files in 3 dirs): Update translations from Launchpad. [14:14] ubiquity-slideshow-ubuntu: evand * r220 ubiquity-slideshow-ubuntu/ (debian/changelog po/ubuntu/br.po): Remove possibly inappropriate URL from br translation (LP #528465). [14:14] Launchpad bug 528465 in ubuntu-translations "Inappropriate br translation in ubiquity-slideshow-ubuntu" [Undecided,New] https://launchpad.net/bugs/528465 [14:14] ubiquity-slideshow-ubuntu: evand * r221 ubiquity-slideshow-ubuntu/debian/changelog: fix LP format on previous commit [14:26] cool, parted 2.1 at least seems to minimally work with the installer [14:26] awesome [14:38] ubiquity-slideshow-ubuntu: evand * r222 ubiquity-slideshow-ubuntu/debian/changelog: releasing version 15 [14:43] partman-base: cjwatson * r184 ubuntu/debian/ (changelog control): [14:43] partman-base: Build against parted 2.1. We don't use its improved alignment features [14:43] partman-base: yet, but we plan to do so by Lucid. [14:43] ubiquity: evand * r3852 ubiquity/ (debian/changelog ubiquity/frontend/kde_ui.py): [14:43] ubiquity: Update the KDE frontend with the new slideshow location (as of [14:43] ubiquity: ubiquity-slideshow 15). [14:56] michaelforrest: would I be correct in assuming that you'll provide the text for the restricted extras page? Do you know if this is something that Amanda needs to approve before we push it into the archive? [14:57] partman-base: cjwatson * r185 ubuntu/debian/changelog: releasing version 138ubuntu1 [14:58] ev: I am going to brief Roz about it and then yeah, I imaging Amanda will need to approve it too [14:58] ev: however, before anything else, I want a go-ahead from Mark! [14:58] yeah [14:59] I think I'll get it started actually [14:59] we'll never get it done otherwise [14:59] michaelforrest: by the way, the jockey installer integration didn't make it for lucid [14:59] jockey? [14:59] hardware drivers [14:59] that was the thing we needed for my second checkbox to work? [14:59] yes [14:59] wah [14:59] ok [14:59] sorry, it's entirely my fault [15:09] partconf: cjwatson * r835 ubuntu/debian/control: set Vcs-Bzr for Ubuntu [15:10] partconf: cjwatson * r836 ubuntu/debian/changelog: releasing version 1.32ubuntu1 [15:13] cjwatson: is there any way I can see the work that cody sent you? [15:14] cjwatson: the pre-greeter stuff? [15:14] boot a current desktop image, press F6, add " maybe-ubiquity" (no quotes) to the end of the kernel parameters [15:14] ooh ok cool [15:15] that's not quite what Cody sent me since I did a bit of polishing, but what he sent just had the left half of the screen red and the right half blue ;-) [15:15] will yesterday's work? [15:15] so I figured anything was an improvement [15:15] yeah, should do [15:15] I'm not sure both actions are hooked up properly, but you'll get the idea [15:15] I hate the language selector the way it is right now; I don't think a giant drop-down work [15:15] works [15:17] TBH, I had wanted DX to take care of making it look pretty :-/ [15:17] yeah I would think we would be doing that [15:17] do I have to select 'install' or 'try' ubuntu on gfxboot? [15:18] ooh mental. [15:18] (I can see it now) [15:18] yeah the actual spec is to have a language selector first, then the try/install screen [15:18] certainly no giant dropdown [15:18] ok there's no way this is landing in lucid [15:19] oh, it is? https://wiki.ubuntu.com/Lucid/GfxbootUpdate is not that specific [15:19] just says "will include language selection" [15:19] do you have a better spec somewhere else with mockups? I've been asking for visual design bits for this for months :-/ [15:19] (hold on - getting something) [15:20] cjwatson: go here: http://use-case-mapper.canonical.com/specifications/0AU5sFuLRpCpBZGZra2pqY2pfMTAxZ25rcnBnNXY [15:20] that's my spec-in-progress [15:20] can I link to that from the public wiki (even if not everyone can actually see it)? [15:20] you have to have access to the google doc [15:21] I could make the google doc public [15:21] but I don't think it's all public yet [15:21] I don't mind, I just want somewhere to keep the link [15:21] ok that's fine [15:21] I was wondering about this... [15:21] do we really want a greeter [15:21] I mean, if the spec is to provide the option after language selection, why not just start ubiquity, and have it provide that interface [15:21] ev: I would be fine with taht [15:22] *that [15:22] that's fine for installation but doesn't work for the live session [15:22] exiting back to the live session like it does on crash when the "try ubuntu" option is selected [15:22] yeah I thought there was some technical reason we can't [15:22] going through ubiquity just for language selection for the live session seems really weird to me [15:23] cjwatson: maybe weird from a technical perspective— would it make any difference to a normal user though? [15:23] cjwatson: and it sounds like it might make life easier [15:23] i.e. not having to involve dx [15:23] I actually thought I meant that it would look weird [15:23] because it would say "Install" at the top? [15:24] well, the whole interface is oriented towards installation [15:24] and anyone who's done it before (or seen it in one of the many books that has installer screenshots) might recognise that as the installer and panic [15:24] or so it seems to me ... [15:25] I don't think that would necessarily be a problem [15:25] especially if we called the window "Ubuntu" [15:25] instead of "Installer" [15:25] it would just be a language selector and then a 'try or install' screen [15:25] (insert comment about derivative branding here, but ...) [15:26] It's a CD user's first experience [15:26] ok so I think evan is right [15:26] my only concern with what I'm suggesting is going from the live CD desktop back to the installer [15:26] what happens then? [15:27] well, I'm wondering how we approach that. Do we simply restart the session? [15:27] we could still make it controlled by that boot option, so that the "Try Ubuntu" button only appears if you're in the boot flow [15:27] and then going from the live CD desktop to the installer is just starting it in a window, as before [15:27] do you mean going from the installer to the live CD desktop? [15:27] oh right I see [15:27] live CD desktop to the installer, how do we get rid of gnome panel and friends [15:28] don't? [15:28] yeah don't [15:28] oh, cool [15:28] it's cool that you can still do stuff while it's installing [15:28] I like simple solutions [15:28] first thing I liked about ubuntu :) [15:28] hooray [15:28] Mark explicitly asked for that, way back in Montreal [15:28] (er - the summit for DappeR) [15:28] Dapper [15:29] so we're adding the language selector / try+install to ubiquity, and then filtering those screens unless we're in the 'boot flow'? [15:29] the language selector's already there, which saves some work [15:29] I think what ev is suggesting is to add a "Try Ubuntu without installing" button to the language selection screen? [15:29] it wouldn't offer keyboard selection, but that's probably OK since it's accessible in System -> Preferences [15:30] no we'll have a language selection screen on its own, then a try/install screen [15:30] oh [15:30] actually, I'm not suggesting any changes to this particular part of the design spec [15:30] ok, I suppose that's workable, as long as it's conditional so that it only happens when we're in this workflow [15:30] was just suggesting that its implementation did not need a custom gdm greeter [15:30] the design will be the same - we're talking about the implementation [15:31] so happy about that 20px padding, by the way :) [15:31] ev: so you're saying that ubiquity's language page could be the implementation of the language selector in this specification, right? [15:31] michaelforrest: I bet netbook users aren't ;-) [15:31] yes [15:31] yeah I've been trying to test it on a netbook [15:31] with no joy :( [15:31] we were already at the very edge of the screen limits on a number of systems [15:31] that the live CD boots straight into the ubiquity-only session with the new design [15:32] ok, and then an optional plugin on the page after the language selector? [15:32] bingo [15:33] hmm - okay I'm talking to otto again - he is saying 'I hope they didn't make the window bigger instead of making the content smaller' [15:33] (re: padding) [15:33] ...I don't recall the request being phrased in that way [15:33] michaelforrest: BTW (UX spec) how is the user supposed to do advanced partitioning when they haven't set up their keyboard yet? [15:33] no it wasn't [15:34] cjwatson: this is why I asked you for feedback before xmas [15:34] cjwatson: surely you can do it with the mouse [15:34] I am glad you are now looking at it [15:34] unless you have some odd mountpoitns [15:34] mountpoints* [15:34] michaelforrest: before xmas, I was in a deathmarch customer project which was occupying about 200% of my work time - I was literally working 16-hour days for weeks at a stretch [15:34] cjwatson: have a look at http://junction.local/specifications/0AU5sFuLRpCpBZGZra2pqY2pfMTAxZ25rcnBnNXY/use_cases/6_3 [15:34] sure, not a problem [15:34] ev: certainly in general it accepts keyboard input [15:35] fair point [15:35] I have thought about it though, trust me - have a look at use case 6.3 [15:35] michaelforrest: I can't see junction.local :) [15:35] s/junction.local/use-case-mapper.canonical.com/, I think [15:35] oops [15:35] sorry [15:36] I didn't include a keyboard step in the variation (2.b) but I imagined if they REALLY needed to set up the keyboard, then it's in the dropdown [15:36] ah, I see what you mean now [15:36] by the way - I have an interactive mockup of the partition tool now [15:36] michaelforrest: me too :) [15:36] I just need to get it packaged (Adobe Air packaged - not proper packaged ;)) [15:37] very keen to see the differences between ours, as I'm curious if you used any kind of standard selection hints [15:37] and also I think we decided not to throw up gparted after all - unless this clarification changes that? [15:37] I'm also a bit concerned about deferring full locale setup to first boot [15:37] gparted die die die [15:37] the default gnome way of putting a brown background on the item is quite ugly with a green/orange/red box in front of it [15:37] ok if we hate gparted, I can accomodate that :) [15:37] we used to use gparted in the installer, in dapper [15:37] it was a nightmare [15:38] likewise qtparted [15:38] we agreed to replace gparted with throwing up the advanced partitioning page in a window [15:38] at the sprint, if memory serves [15:38] yeah, I think so [15:38] ok — I was just trying to help you only have to maintain one partitioning tool [15:38] though my question was, if the user runs through that, does it skip past the automatic partitioner [15:38] yeah that's right - I need to update the spec [15:38] we only have to maintain one partitioning tool right now :) [15:38] I imagine it would have to [15:38] lol [15:38] gparted maintains itself and we don't involve it in the installer workflow [15:39] so shouldn't gparted just go in the bin and we give people the 'advanced partitioner' then? [15:39] or should I just shut up and not try to understand.. [15:39] (I mean on the desktop) [15:40] so mostly that would sort of be my vote except that the advanced partitioner isn't really set up to be a standalone desktop app [15:40] partman isn't in general [15:40] it has some expectations which hold well during installation, but not so much outside that [15:41] ok so ev - about the window size - if it's already to the limit without the padding, then we need to make the content smaller to accommodate the padding [15:41] gparted and partman both use the same core partitioning backend, but they have different business logic on top of it which is optimised for different purposes [15:43] michaelforrest: uhm, easier said than done. [15:43] ev: sorry that wasn't really clear before - I didn't really think about it - but it was pretty obvious to otto, and he knows about that sort of thing.. [15:43] yeah I imagine so [15:43] but we need to do it [15:43] run a script on the gtk xml? [15:43] sure, I'll see what I can do, but it's going to be difficult to shave 20px off each side, so I'm not making any promises [15:43] to avoid fiddling with glade ? [15:43] there's no absolute positioning or sizing in there [15:44] it's a matter of having too much content [15:44] the text on the user setup page, for example, takes up a lot of space [15:44] I'm sure you can fit it in [15:45] this would be the second or third attempt to squash things down, I think [15:45] from a design perspective, it's a major difference in how professional it looks [15:45] ev there is more than enough space on the user setup page judging from the screenshot I'm looking at [15:46] michaelforrest: the thing is that the notebook format (and general sanity - we don't want to be growing and shrinking the window in the middle) means that the installer grows to the size of the largest page [15:46] hrm, indeed [15:46] I could have sworn that was where it grows though [15:47] cjwatson: yeah I'm aware of that [15:47] I'll look into it and see what I can shave off [15:47] might be horizontal growth on one page and vertical growth on another? I'm not sure how smart gtk is ... [15:47] gtk, smart, hah [15:47] could be worse, could be qtdesigner *shudder* [15:47] but indeed, I'll watch out for that [15:47] thanks [15:47] hahahahaha [15:47] oh god [15:47] NEVER AGAIN [15:48] I am currently writing a spec for a glade-style tool.. [15:48] if I have to build it myself, I will... [15:48] michaelforrest: while I have you here... [15:48] What are your thoughts on the following for the "unable to install restricted extras (dvd, mp3, flash) during install because we didn't have a network connection" scenario. On first boot you get the following window: [15:48] http://people.canonical.com/~evand/tmp/update-notifier-restricted-extras.png [15:48] and if you click run this action now, you get: [15:48] http://people.canonical.com/~evand/tmp/software-center-restricted-extras.png [15:48] This is similar to how incomplete language support is handled. That is, when you do an install with a language that we don't include langpacks for on the CD (because they take up way too much space), you see an update-manager notification that tells you: [15:48] The language support files for your selected language seem to be incomplete. [15:48] You can install the missing components by clicking on "Run this action now" [15:48] and follow the instructions. An active internet connection is required. [15:48] If you would like to do this at a later time, please use "System -> [15:48] Administration -> Language Support" instead. [15:49] cjwatson: if you have any thoughts as well, I'm keen to hear them [15:49] ok the language needs to change a lot [15:49] sure [15:49] it was a quick mock up [15:49] ev: technically I think it's fine, I'll defer to Michael on the design obv. [15:49] I'm more concerned about the workflow [15:50] I would like to unify any post-installation steps into one place if at all possible [15:50] if we don't have a network connection during install, then we need to ask later, and *right now, this release* we only really have one way to do that [15:50] but I would want to talk to mpt / johnlea about how to do this [15:50] independent of future first-boot work [15:50] assuming you're talking about lucid here ... [15:50] yeah, lucid [15:51] ev: I would kinda like to just go ahead and install it in the background silently (ducks) [15:51] (*ducks*) [15:51] I'm keen to get something in place, so Steve Langasek doesn't laugh hysterically at me when I ask to land this. [15:51] well, this is for the case where we don't have a network connection [15:51] and thus cannot do it until post-install, when a network connection is established [15:51] yeah so it's no help popping it up before an internet connection is available [15:52] and as far as installing it in the background, I think Amanda might take issue with that :) [15:52] chrome installed a load of new shit in the background without asking me! crazy. whatever will they do next. [15:52] I can't say I was that impressed ;) [15:52] michaelforrest: ah, indeed, though our current stack makes that difficult unless we're trying to wget http://www.ubuntu.com/am_I_online in a cron job [15:53] so on first network connection, it's gonna check for updates and there's gonna be that {!} icon [15:53] ? [15:53] on first boot, regardless of network connection, the first mentioned window will show up [15:53] is that how it works? or is the update check only on a cron job? [15:53] yeah I don't want anything popping up like that [15:53] but can we roll it into the first update process? [15:53] I think it's a cron job [15:54] I would love to have a way to queue something for the next time apt runs [15:54] We're always going to want to install updates on the first install right? [15:54] I've been wishing for that for about 5 years [15:54] so why can't we make it check for updates on first network connection? [15:54] it would be very handy for language packs [15:54] indeed, I think this very much mirrors the langpack case [15:55] so first time you connect to the network, it automatically starts downloading stuff to make sure that you can't use the network straight away? :-) [15:55] I'd like to just roll everything into that process - language packs, updates, restricted extras [15:55] no - it says 'updates are available - it is recommended that you install these now' [15:55] the "do I have any updates" download is quite big in itself [15:55] really? why? [15:56] downloads all the Packages files ... [15:56] why> because we have a lot of packages in Ubuntu [15:56] which would be very unfortunate if you're on a 3G dongle and it runs [15:56] anyway I think it's a safe assumption that on first boot, the user needs to install updates, so we don't necessarily need to check [15:56] am I wrong? [15:56] no :) [15:57] my concern is basically that we're putting more and more cute things in the way of the user playing with their new toy [15:57] we're not! [15:57] I think updates should be later [15:57] we're making sure the toy is ready before they start trying to play with ti! [15:57] *it! [15:57] lets not confuse updates with what we're trying to do here [15:57] the toy is ready upon installation [15:57] I think it's the wrong language [15:57] not to watch youtube videos [15:57]