| knome | Unit193, where's the MP? | 00:56 |
|---|---|---|
| Unit193 | Doesn't exist? :D | 00:57 |
| knome | boo. | 00:57 |
| pleia2 | http://searchenterprisedesktop.techtarget.com/feature/Boot-to-open-source-desktops-with-Linux-on-USB-sticks | 01:33 |
| pleia2 | using xubuntu as an example, how nice :) | 01:33 |
| knome | :) | 01:34 |
| Unit193 | knome: There. | 01:42 |
| Unit193 | Unless I broke it. :D | 01:42 |
| knome | great | 01:43 |
| knome | merged | 01:44 |
| Unit193 | https://code.launchpad.net/xubuntu-docs/+activereviews | 01:46 |
| Unit193 | You didn't even test it. :( | 01:47 |
| knome | hah. | 01:54 |
| knome | ^ cleaned that list up | 01:56 |
| knome | pleia2, note: re the press page: i thought we could keep trusty for now since it's the latest lts, and especially since there is no stuff for utopic yet | 01:57 |
| knome | https://www.youtube.com/watch?v=NxnKv6PcmDU | 02:07 |
| knome | he'd like to have the categories on the left side on whisker. is that currently possible? | 02:07 |
| ali12341 | no | 02:09 |
| ali12341 | if you want the categories on the left, just use a normal cascading menu... | 02:09 |
| knome | one could argue one might want both the search (and other) features from whisker, but the categories on the left | 02:10 |
| ali12341 | moon on a stick... | 02:10 |
| knome | i don't think it's an unreasonable request tbh | 02:11 |
| knome | one thing that he mentions, which has been brought up before, is the default file type abiword saves as | 02:15 |
| knome | could we potentially poke that value for new users, making it something that's more widespreadly readable? | 02:16 |
| skellat | ODT? | 02:21 |
| knome | https://www.youtube.com/watch?v=tkIWArfBq_4 | 02:22 |
| knome | ^ he says USC is not working, but would, if we installed package X | 02:22 |
| knome | skellat, or DOC | 02:22 |
| Unit193 | !info x | 02:22 |
| ubottu | Package x does not exist in utopic | 02:22 |
| Unit193 | Too bad. | 02:23 |
| knome | awwh. | 02:23 |
| knome | ^ and whining about theme colors. | 02:23 |
| ali12341 | ubuntu-sso-client-qt | 02:24 |
| knome | what about actually reading the release announcement before doing a video review | 02:24 |
| knome | and people generally think to seem there needs to be something new for a release to be successful | 02:25 |
| ali12341 | rounded corners not working? | 02:26 |
| ali12341 | window decorations are bitmaps, that is impossible | 02:26 |
| ali12341 | yeah if you want everything to be different in every release, there's ubuntu, kubuntu and ubuntu-gnome | 02:26 |
| Unit193 | Lubuntu and will be a MATE ubuntu too. | 02:28 |
| ali12341 | neither of those are different in every release though | 02:29 |
| knome | so he's half way to the video, and he's mostly been talking about his own modified themes and how themes are broken and how there are still the same bugs | 02:29 |
| knome | maybe we should write a blog article about why everything's not changing every time | 02:29 |
| knome | but maybe they'd just not read it. | 02:30 |
| knome | "so the only thing they did here is to make it worse" | 02:30 |
| knome | hahah. | 02:30 |
| knome | contributions that improve the quality are welcome. | 02:30 |
| ali12341 | i have to agree that there is no reason to upgrade | 02:32 |
| knome | there rarely is a good reason to upgrade from LTS to the next regular version | 02:33 |
| knome | unless you want the later versions of packages | 02:34 |
| knome | but sure, i do understand the point, and i'm not offended by it | 02:34 |
| knome | it just doesn't seem very legit to whine about "no new things" either | 02:34 |
| ali12341 | i agree | 02:34 |
| knome | "and they've introduced some new [bugs] as well" | 02:35 |
| knome | wait, which bugs did we *introduce* ? | 02:35 |
| Unit193 | https://lists.ubuntu.com/archives/ubuntu-devel/2014-October/038516.html is something great to read, though. | 02:35 |
| ali12341 | i think we should drop USC | 02:38 |
| knome | though it was resolved. | 02:38 |
| knome | ali12341, that's been discussed several times, but if you want, you can start the discussion again | 02:40 |
| knome | http://www.reviewstoday.in/2014/10/review-quick-look-at-xubuntu-1410.html | 02:41 |
| knome | come on guys! | 02:41 |
| Unit193 | knome: Not this one: https://launchpad.net/ubuntu/trusty/+source/owncloud | 02:41 |
| knome | we serve the logo that works with your website on the website you took a screenshot and created a crappy JPG from | 02:41 |
| knome | Unit193, fix committed 9 hours ago. now testing, will probably land soon enough | 02:43 |
| ali12341 | i couldn't reproduce any USC bug with missing sso | 02:46 |
| knome | mhm. | 02:47 |
| Unit193 | Ah, still a pity. | 02:56 |
| Unit193 | Wonder what's taking up with the stuff in proposed and NEW. | 03:05 |
| knome | don't know about that but i know i'm going to bed now | 03:16 |
| knome | ttyl and have a nice day | 03:16 |
| Unit193 | Good nighty. | 03:17 |
| skellat | ali12341: I look forward to reviewing your case for dropping U-S-C | 03:20 |
| skellat | Unit193: jriddell did the empty packages earlier for owncloud. The builders have been **very** busy... | 03:21 |
| skellat | And rmadison fails on me...AGAIN! | 03:21 |
| Unit193 | Normally shows as pending. | 03:21 |
| elfy | ochosi: -release team will be expiring soon - can you deal with that, afaik if I'm not in -release then I can't work on the trackers | 08:03 |
| bluesabre | ochosi: I think my membership might be expiring for release and others as well | 09:59 |
| brainwash | hey bluesabre | 10:10 |
| bluesabre | hey brainwash: haven't gotten to the thunar bug/fix yet | 10:10 |
| brainwash | ok | 10:11 |
| brainwash | any news from the sru team? | 10:11 |
| bluesabre | haven't heard anything. What was the last status... still waiting for xfdesktop to land in proposed, and xfce4-weather-plugin to get out of proposed, right? | 10:15 |
| brainwash | yes, exactly | 10:16 |
| slickymasterWork | morning | 10:19 |
| slickymasterWork | saw you ping knome | 10:20 |
| slickymasterWork | s/you/your | 10:20 |
| * qwebirc653355 sighs | 10:24 | |
| qwebirc653355 | knome, also saw that you already bumped version to Vivid | 10:24 |
| === qwebirc653355 is now known as slickymasterWork | ||
| slickymasterWork | there's something I don't get though, https://code.launchpad.net/~jjfrv8/xubuntu-docs/print-server-settings/+merge/222962 | 10:26 |
| slickymasterWork | wasn't this already merged?! | 10:26 |
| slickymasterWork | I thought I had merged it on 2014-06-12 | 10:26 |
| slickymasterWork | what gives? | 10:26 |
| slickymasterWork | knome, Unit193: Element placeholder-2 in namespace '' encountered in guimenuitem, but no template matches. | 10:38 |
| slickymasterWork | in PT ^^ | 10:38 |
| slickymasterWork | I almost 100% sure that I never translated tags | 10:39 |
| slickymasterWork | s/I/I', | 10:39 |
| slickymasterWork | * I'm | 10:39 |
| knome | slickymasterWork, was merged, but not in the right way, so it was left open; i just did the paperwork to get it disappear | 10:46 |
| slickymasterWork | ok, | 10:46 |
| slickymasterWork | I remember that back then I had a few glitches with the merge | 10:47 |
| knome | yep | 10:47 |
| knome | i don't get that error anymore | 10:47 |
| knome | the placeholder-2 one | 10:47 |
| knome | it suddenly just disappeared | 10:47 |
| slickymasterWork | i could almost swear that I never translated tags | 10:47 |
| knome | it's not necessarily linked to that | 10:49 |
| knome | but in the spanish translations, that was the case | 10:49 |
| slickymasterWork | knome do you think I should mail https://launchpad.net/~franciscomol regarding his es translations issues? | 10:49 |
| slickymasterWork | at least to be somewhat preventive | 10:50 |
| brainwash | bluesabre: someone needs to add a comment to the sru report and mention that he tested the trusty-proposed package | 10:50 |
| bluesabre | brainwash: for xfce4-weather-plugin? | 10:50 |
| brainwash | bluesabre: it's not clear which version of xfce4-weather-plugin elfy has tested | 10:50 |
| brainwash | yes | 10:51 |
| knome | slickymasterWork, yeah, that'd be good | 10:51 |
| knome | slickymasterWork, cc or bcc me | 10:51 |
| slickymasterWork | ok, I'll do it | 10:51 |
| bluesabre | brainwash: I think its clear by elfy's setting verification-done | 10:52 |
| brainwash | -> pitti │ brainwash: I asked elfy in #u-quality whether his comment 21 was testing the proposed package | 10:53 |
| bluesabre | added comment | 10:54 |
| bluesabre | I would like to note that while #ubuntu-quality makes sense, it is not mentioned that any sru discussion happens there on https://wiki.ubuntu.com/StableReleaseUpdates | 10:57 |
| bluesabre | added that to my permanently joined channels | 10:58 |
| brainwash | sounds like a good idea | 11:03 |
| ochosi | morning all | 11:10 |
| slickymasterWork | morning ochosi | 11:10 |
| ochosi | hey slickymasterWork | 11:10 |
| ochosi | bluesabre, elfy: looking at the expiry dates now... | 11:10 |
| ochosi | ok, bumped all of us until 15.04 | 11:12 |
| ochosi | any other teams with expiry problems? | 11:12 |
| ochosi | fwiw, if many people of -team can't make it to the meeting on friday, we can re-schedule for sometime next week | 11:44 |
| ochosi | i originally thought a sorta holiday was a good idea, but in case it actually isn't, there's no problem with postponing until after the weekend | 11:44 |
| ochosi | so feel free to let me know | 11:44 |
| ochosi | bbl | 11:45 |
| knome | works for me just as well as any other day | 11:57 |
| ochosi | bluesabre: i know you said you were busy, but i guess with adding some preliminary gtk3.14 support to greybird, it's time to disable its daily builds for trusty as it'll just break the theme for gtk3.10/12 | 12:35 |
| ochosi | (note: the support for checks and radios has already been added, so ppl using the PPA with trusty will notice the breakage. so you could also argue that it's too late already) | 12:35 |
| bluesabre | ochosi: if you can give me the last good commit for, I'll package it up, stop daily uploads, and push the final supported package. | 12:37 |
| bluesabre | Trusty | 12:37 |
| ochosi | that's the last commit 2b5b144fa145f31a6c4500b03fb9a5bcd5d89952 | 12:38 |
| bluesabre | When I get home, ofc | 12:38 |
| ochosi | https://github.com/shimmerproject/Greybird/commit/2b5b144fa145f31a6c4500b03fb9a5bcd5d89952 | 12:38 |
| ochosi | sure, no rush | 12:38 |
| bluesabre | Thanks. | 12:38 |
| slickymasterWork | knome, ping | 12:38 |
| knome | slickymasterWork, pong | 12:38 |
| ochosi | it's actually the pen-ultimate commit | 12:38 |
| knome | ochosi, not the brush-ultimate? | 12:39 |
| slickymasterWork | please comment -> http://pastebin.com/6ZpC1Gdh | 12:39 |
| ochosi | knome: whoa, that was a *bad* one... | 12:39 |
| knome | but of course! | 12:39 |
| knome | ochosi, i didn't you liked frisbeeing | 12:39 |
| knome | (^ another bad one) | 12:39 |
| ochosi | indeed :) | 12:40 |
| bluesabre | ochosi: fountain or ballpoint? | 12:40 |
| ochosi | awwwhh, you're really starting to hurt my feelings... | 12:40 |
| knome | slickymasterWork, i'd just say "Hey Paco, ..." and i would include your name (at least first name) at the end instead/in addition to your nick | 12:40 |
| ochosi | :] | 12:40 |
| slickymasterWork | other than that knome? anything? | 12:41 |
| knome | hmm | 12:41 |
| knome | actually | 12:41 |
| knome | tell him to avoid adding spaces where they do not belong | 12:41 |
| knome | example: | 12:41 |
| slickymasterWork | isn't that included in the data placeholders paragraph? | 12:42 |
| knome | original string: <tag><tag2><placeholder-1/>content</tag2></tag> | 12:42 |
| slickymasterWork | ^^ | 12:42 |
| slickymasterWork | isn't that included in the data placeholders paragraph? | 12:42 |
| knome | translated string: <tag> <tag2> <placeholder-1 /> content </tag2> </tag> | 12:42 |
| knome | is it? | 12:42 |
| knome | let me read again | 12:42 |
| slickymasterWork | knome, Copy these variables and placeholders exactly as you see them.... | 12:43 |
| elfy | brainwash: and it seems perfectly clear to me | 12:43 |
| knome | right, but it's also something he does outsides the tags | 12:43 |
| brainwash | elfy: I did not complain ;) | 12:43 |
| slickymasterWork | ok, | 12:44 |
| elfy | bluesabre: possibly because pitti knows where I'm likely to be found all the time | 12:44 |
| knome | there's practically nothing wrong with that, and it should look the same, but it makes it hard to debug potential problems with the translation | 12:44 |
| slickymasterWork | another thing knome, how do I go about nagging the website responsible :) | 12:44 |
| knome | which website? :P | 12:44 |
| slickymasterWork | there's an outstanding bug in it | 12:44 |
| elfy | ochosi: re meetings - any meeting during my working day - I'm going to be working :) | 12:44 |
| slickymasterWork | xubuntu.org :P | 12:45 |
| bluesabre | ochosi: can you test this patch and see if you notice anything negative? https://bugzilla.xfce.org/show_bug.cgi?id=11107 | 12:45 |
| ubottu | bugzilla.xfce.org bug 11107 in Xfsettingsd "xfsettingsd resets TV mode to NULL on power cycle" [Normal,New] | 12:45 |
| knome | slickymasterWork, just tell me what the bug is, and i'll either 1) fix it, or if it's not a trivial thing 2) ask you to file a bug (against xubuntu-website) | 12:45 |
| slickymasterWork | I was just putting you on knome ;) | 12:46 |
| knome | slickymasterWork, if i'm not around when you'd like to ask it, a bug is always okay | 12:46 |
| bluesabre | Worked for me. Just looking for extra verification | 12:46 |
| knome | aha :P | 12:46 |
| ochosi | bluesabre: ok, will try to test that tonight. i don't have a TV, but i can try my hdmi screen (never had any problems at all with it) | 12:46 |
| slickymasterWork | now seriously in the Internet Relay Chat section of http://xubuntu.org/help/ there's still a mention to XChat | 12:46 |
| knome | so this is the "tease the fellow team member" day :P | 12:46 |
| slickymasterWork | lol | 12:47 |
| slickymasterWork | this is the paragraph in question "To join the community support channel, you can use the link above. To join any of the channels, you can use the XChat IRC client, which is installed by default in Xubuntu. You can find XChat under the Internet category in the applications menu." | 12:47 |
| knome | ta, will go edit | 12:47 |
| bluesabre | ochosi: thanks. If nothing gets worse, I'll apply it to trunk | 12:47 |
| ochosi | bluesabre: yeah, i guess these things will always be a bit of trial and error... | 12:47 |
| slickymasterWork | ok, I'm going to edit the mail an send it, CC'ing you knome | 12:47 |
| slickymasterWork | s/an/and | 12:47 |
| knome | slickymasterWork, done | 12:48 |
| knome | and ta | 12:48 |
| * slickymasterWork bows | 12:48 | |
| knome | and arrows? | 12:49 |
| slickymasterWork | :P | 12:49 |
| slickymasterWork | there's no room anymore for courtesy | 12:50 |
| knome | no | 12:50 |
| slickymasterWork | you sarcastic people ;) | 12:50 |
| knome | this room is too small to bow | 12:50 |
| slickymasterWork | ah ah ah ah | 12:50 |
| knome | you'll just hit your head to tables and such | 12:50 |
| slickymasterWork | watch out knome, XPL is around and will kick us to -off | 12:51 |
| knome | that's ok, he doesn't have the opping rights | 12:51 |
| slickymasterWork | lol | 12:51 |
| davmor2 | slickymasterWork: if there is no room to bow then there isn't a hope in hell of courtesy that what women do when they meet the Queen right ;) | 12:52 |
| elfy | the room's big enough - I just think we're all Giants | 12:52 |
| elfy | apart from pleia2 of course - who's a giant in her own way :) | 12:52 |
| slickymasterWork | lol davmor2 | 12:52 |
| elfy | hi davmor2 | 12:52 |
| knome | elfy, you mean the san francisco giants? :P | 12:52 |
| slickymasterWork | hey elfy | 12:53 |
| davmor2 | elfy: how do | 12:53 |
| slickymasterWork | knome, sent | 12:57 |
| knome | good | 12:58 |
| pleia2 | I think elfy is calling us fat | 15:01 |
| knome | ahaha | 15:06 |
| elfy | pleia2: not at all - I was calling you short :p | 16:15 |
| pleia2 | hehe | 16:15 |
| elfy | :) | 16:15 |
| elfy | was just - you're short - we're not - but *we* are Giants - we are the best team :p | 16:16 |
| davmor2 | pleia2: I wouldn't stand for that, I'd sit instead ;) | 16:17 |
| elfy | davmor2: or we could all sit and pleia2 could stand :) | 16:18 |
| slickymasterWork | lol | 16:19 |
| elfy | as all can tell probably - I'm back :) | 16:19 |
| slickymasterWork | \o/ | 16:19 |
| pleia2 | :) | 16:20 |
| brainwash | bluesabre: "accepted xfdesktop4 [source] (trusty-proposed) [4.11.8-0ubuntu0.1]" | 17:56 |
| brainwash | also, xfce4-weather-plugin is available in -updates now | 17:57 |
| slickymasterWork | he he, and another busted Verocious Velociraptor box :P | 17:59 |
| slickymasterWork | no ending for this fun moments | 17:59 |
| brainwash | so, we need some testers for xfdesktop4 in trusty (-proposed) | 18:01 |
| brainwash | bug 1365965 | 18:01 |
| ubottu | bug 1365965 in xfdesktop4 (Ubuntu Trusty) "[MRE] Please update xfdesktop4 to 4.11.8 in Trusty" [Undecided,Fix committed] https://launchpad.net/bugs/1365965 | 18:01 |
| elfy | brainwash: mail the devel list :) | 18:01 |
| brainwash | don't you already have a template for test calls? :P | 18:02 |
| elfy | no | 18:02 |
| elfy | just write it to the list - it's really not hard at all | 18:02 |
| slickymasterWork | I'll probaly be able to test those tonight, depending on kid being able to go to bed not too late | 18:02 |
| elfy | knome: how do I add vivid core/desktop builds to tracker | 19:22 |
| elfy | I looked in the docs - but the page is blank | 19:22 |
| knome | are there actually builds ready? | 19:22 |
| elfy | yea | 19:22 |
| knome | okay | 19:23 |
| elfy | I assume http://iso.qa.ubuntu.com/admin/config/services/qatracker/builds | 19:23 |
| knome | i'll go through that with you a bit later if that's oki | 19:23 |
| elfy | ok - might be mia though and tomorrow will do if that's ok | 19:23 |
| knome | sounds good | 19:24 |
| elfy | there's not any real rush imo | 19:26 |
| knome | yep | 19:26 |
| knome | elfy, still about? | 20:24 |
| elfy | I is | 20:24 |
| knome | want to go through adding the builds? | 20:25 |
| elfy | yep - please:) | 20:25 |
| knome | ok, let's open the tracker admin | 20:25 |
| knome | an | 20:26 |
| knome | hmm :P | 20:26 |
| knome | tell me when you're ready | 20:26 |
| elfy | yep | 20:26 |
| knome | ok, so go to the "Builds" tab | 20:26 |
| elfy | I'll shout if I've got an issue | 20:26 |
| knome | and scroll down until you see the xubuntu builds | 20:26 |
| knome | there you can see we only have two active builds; desktop builds for trusty daily | 20:27 |
| knome | now we obviously want to create a new build | 20:27 |
| knome | the form is conveniently just after our builds | 20:27 |
| knome | so, the version number is practically YYYYMMDD | 20:27 |
| elfy | aaah | 20:27 |
| knome | so, 20141028 for today | 20:27 |
| knome | milestone is vivid daily | 20:27 |
| knome | or whateever you want to add the build to | 20:28 |
| knome | and finally, | 20:28 |
| knome | check the products you want to add builds for | 20:28 |
| knome | in the "xubuntu" section | 20:28 |
| knome | then hit "add these builds to the tracker" | 20:28 |
| knome | and they should be up and available :) | 20:28 |
| elfy | cool - the version number was were I fell down | 20:29 |
| knome | yep | 20:29 |
| elfy | awesome - thanks :) | 20:29 |
| knome | i don't know why others have 20141024 as the vivid version number | 20:29 |
| elfy | upgrades? | 20:29 |
| knome | right | 20:29 |
| knome | true, my bad :) | 20:29 |
| elfy | I think I did that | 20:29 |
| knome | i don't know what happens after this: | 20:30 |
| elfy | didn't want a version number | 20:30 |
| knome | i guess the builds are just being updated automatically or so | 20:30 |
| elfy | well I can check in a day | 20:30 |
| knome | yep | 20:30 |
| elfy | questions is - do we do core again | 20:30 |
| knome | i'd say yeah, we probably have things to iron out | 20:30 |
| knome | but do we want to do it already, don't know | 20:31 |
| elfy | I think that balloons did something *else* with that so it didn't update daily | 20:31 |
| knome | i guess it doesn't hurt even if somebody ran a core test :) | 20:31 |
| Unit193 | Just don't let them do upgrades. :P | 20:31 |
| knome | :P | 20:31 |
| elfy | I'd rather we did the same thing again - so we get only one core and people just continually add onto that test result page | 20:32 |
| knome | yeah | 20:32 |
| knome | then just add "vivid" as the version number | 20:33 |
| knome | or sth :) | 20:33 |
| elfy | ochosi: adding a couple of easy things to the agenda - but I'll not be there - will need to be sorted though | 20:33 |
| Unit193 | Best time to check, when something big drops, make sure the deps don't get clobbered. | 20:33 |
| elfy | knome: mmm - but milestone will be vivid daily | 20:34 |
| elfy | looking at utopic | 20:34 |
| elfy | yea - think that's right - it stayed on dailiy | 20:34 |
| knome | yep | 20:34 |
| elfy | ok - added it | 20:35 |
| knome | if we want, we can add builds for the other milestones as well | 20:35 |
| elfy | yep | 20:35 |
| knome | nice :) | 20:35 |
| elfy | Unit193: will you be about at the meeting? | 20:36 |
| Unit193 | elfy: No. | 20:37 |
| elfy | okey doke | 20:37 |
| elfy | Unit193: ok - well we (QA) will come up with a plan to deal with core then - you can start that off :p | 20:38 |
| Unit193 | \o/ | 20:39 |
| Unit193 | :P | 20:39 |
| elfy | http://pad.ubuntu.com/vivid-QA-plan | 20:39 |
| * knome tickles Unit193 from the armpits | 20:39 | |
| Unit193 | Really want that hair? | 20:40 |
| knome | ...with a stick | 20:40 |
| Unit193 | Ah good, not too cluttered yet. | 20:40 |
| elfy | yep - almost a virgin pad :) | 20:41 |
| Unit193 | Dev and last QA one got biiiig. | 20:41 |
| knome | elfy, not BT? | 20:41 |
| knome | orange? | 20:42 |
| elfy | make notes on that pad - then once we're sorted I'll get it on blueprint and trello as appropriate | 20:42 |
| elfy | knome: wut? | 20:42 |
| knome | nvm, just very dry puns about virgin/BT/orange/... | 20:42 |
| elfy | Unit193: yea - there are some big pads atm :p | 20:42 |
| elfy | oic :) | 20:42 |
| elfy | Unit193> Best time to check, when something big drops, make sure the deps don't get clobbered. good point - just need someone to watch that, as lead I'll ask someone in particular to watch it :D | 20:44 |
| knome | ^ like Unit193 ? | 20:44 |
| elfy | entirely possible as dkessel is going to be tied up with autopilot I hope :D | 20:45 |
| elfy | knome: thanks by the way :) | 20:49 |
| knome | np :) | 20:49 |
| Unit193 | Anyone tried xfce4-panel's intelligent hiding? | 21:00 |
| elfy | I read about it | 21:01 |
| knome | haha | 21:03 |
| knome | almost tested then :)= | 21:03 |
| Unit193 | I updated the package, because I wanted the option, but I don't use hiding. :P | 21:06 |
| elfy | heh | 21:06 |
| knome | Unit193, elfy: can you cooperate some testing via the ML? | 21:06 |
| Unit193 | -core? | 21:07 |
| knome | intelligent panel hiding | 21:07 |
| elfy | knome: only if we're actually going to get it in 15.04 | 21:07 |
| knome | i don't know if we will... ochosi? | 21:08 |
| knome | anyway, i don't think it's necessarily a bad thing to test it even if it's not included, just see if it works and such | 21:08 |
| knome | so not too much work/effort in testing it, but some brief | 21:09 |
| elfy | knome: well it's not installable without mucking about afaik | 21:09 |
| elfy | and we have enough trouble getting people to test what we really need doing ;) | 21:09 |
| dkessel | elfy: I hope I will be busy with autopilot, yes :) | 21:10 |
| elfy | woohoo | 21:10 |
| elfy | we do need to ensure that if we get anywhere it will be used | 21:10 |
| elfy | I'll catch up with balloons on that next week if possible, don't want effort going into it - if at the end - they won't add it | 21:12 |
| Unit193 | https://launchpad.net/~unit193/+archive/ubuntu/xfce I dropped it in there for myself (and because I got shouted at last time, pinged someone too!) | 21:13 |
| elfy | perhaps that's where I read it :D | 21:14 |
| Unit193 | Yes, I pinged elfy, in case he wanted to copy it over for elfy. :D | 21:14 |
| elfy | I've had a headache - you're making it worse :p | 21:15 |
| slickymaster | it's not my fault now elfy | 21:15 |
| elfy | nope :) | 21:15 |
| knome | elfy elfy elfy elfy elfy elfy elfy elfy elfy | 21:15 |
| dkessel | elfy everywhere | 21:16 |
| elfy | I've had one since I made the fatal mistake of looking at that upgrading stuff in docs lol | 21:16 |
| Unit193 | (And if someone pokes me and wants to try it, I can pop a vivid one up too.) | 21:16 |
| knome | elfy, hahah | 21:16 |
| knome | reminds me i should look at that soonish | 21:16 |
| elfy | Unit193: well ... if *we* decide to look at for this cycle - thenit needs to be in staging | 21:17 |
| knome | or via extras, which is the pre-staging phase | 21:17 |
| Unit193 | Right, and not sure if you/we/he/it/donky plans to look at it this cycle. | 21:17 |
| elfy | knome: mostly it's the top bit, the plaintext, but it would be nice to know how wrong the marked up is | 21:17 |
| Unit193 | Extras isn't right. | 21:17 |
| knome | elfy, yep, i'll try to look at it probably even tonight | 21:18 |
| knome | chances are i won't be going to sleep soon | 21:18 |
| slickymaster | elfy, what mark up is wrong? | 21:18 |
| elfy | I will be | 21:18 |
| Unit193 | I won't be. | 21:18 |
| elfy | slickymaster: no idea - never done it before :) | 21:18 |
| knome | elfy, then you'll get to that in the morning | 21:18 |
| knome | slickymaster, the markup he wrote for the upgrading section | 21:18 |
| * slickymaster haven't saw it yet | 21:19 | |
| knome | don't hammer it either | 21:19 |
| slickymaster | do you have it somewhere elfy? | 21:19 |
| knome | http://pad.ubuntu.com/upgrading | 21:19 |
| knome | but there it is ^ | 21:19 |
| * slickymaster checks it | 21:19 | |
| slickymaster | wow that's a big section | 21:20 |
| knome | elfy, one thing i see is the id's... you can't have spaces :) | 21:21 |
| elfy | it's not all changed | 21:21 |
| knome | fixing that | 21:21 |
| elfy | knome: well as long as the changes are on pad I'll be able to see the diff colours :) | 21:21 |
| knome | yep | 21:22 |
| * knome goes pink | 21:22 | |
| knome | other than that, it seems to look okay | 21:23 |
| slickymaster | and there's some icon entities missing | 21:23 |
| knome | i'll run it through the validator too to ultimately check that | 21:23 |
| elfy | really - didn't do too bad then | 21:23 |
| knome | slickymaster, want to add them? | 21:23 |
| knome | elfy, yep, very good | 21:23 |
| slickymaster | yes, I'll do it | 21:24 |
| slickymaster | kudos elfy | 21:24 |
| knome | elfy, re: content: instead of linking directly to the trackers, i'd probably link somewhere in the website | 21:25 |
| slickymaster | I'll ping you when it's finished knome | 21:25 |
| knome | that is, "QA" under "get involved" or sth | 21:25 |
| knome | slickymaster, yep | 21:25 |
| elfy | Please consider getting involved with reporting usage of development versions and associated packages. | 21:29 |
| knome | yeah. | 21:29 |
| knome | that's better | 21:29 |
| elfy | and then link to contribute/qa | 21:29 |
| knome | yep | 21:31 |
| knome | btw, question: | 21:31 |
| elfy | is what I did right? | 21:31 |
| knome | (yes) | 21:31 |
| knome | do you think it's weird that we basically have: | 21:31 |
| knome | 1) upgrading from LTS->LTS | 21:31 |
| knome | 2) upgrading from a regular release (note: no "to" here, because the target can be either a regular or an LTS release) | 21:31 |
| knome | 2) upgrading to the development version | 21:32 |
| knome | 3^ | 21:32 |
| knome | (and note release VS. version) | 21:32 |
| elfy | hang on a minute | 21:33 |
| elfy | you've changed the 'title' of the first one and it doesn't match the content :) | 21:34 |
| knome | hmm | 21:35 |
| elfy | title is Upgrading from one LTS version to another | 21:35 |
| elfy | BUT change Update to for any new version | 21:35 |
| knome | slickymaster, just checking, are you modifying the docbook markup? | 21:35 |
| elfy | title *was* For LTS versions (unless the next release is LTS): | 21:35 |
| * knome reads agian | 21:35 | |
| knome | *Again | 21:36 |
| slickymaster | yes | 21:38 |
| slickymaster | there are a few tags missing knome | 21:38 |
| knome | elfy, any reason to keep the non-docbook section? | 21:38 |
| elfy | none - now I know the marked up bit is ok | 21:38 |
| knome | slickymaster, i see you've been editing the non-markup version | 21:39 |
| knome | the docbook one is below | 21:39 |
| slickymaster | I'm starting at the top | 21:39 |
| knome | lol | 21:39 |
| knome | ok | 21:39 |
| knome | start at the docbook top | 21:39 |
| * elfy makes it easier | 21:39 | |
| slickymaster | btw what the hell is sudo edit?! | 21:39 |
| elfy | yea - new one on me too :) | 21:40 |
| knome | elfy, that's a horrible color ;) | 21:40 |
| elfy | slickymaster: it edits as sudo with default editor | 21:40 |
| knome | ouch! | 21:40 |
| knome | my eyes are bleeding | 21:40 |
| slickymaster | does it have a space between the sudo and edit» | 21:40 |
| knome | elfy, that's good :) | 21:40 |
| elfy | slickymaster: no space | 21:40 |
| slickymaster | ok | 21:40 |
| Unit193 | Now, s/sudo -i mousepad/pkexec mousepad/ | 21:40 |
| knome | ^ that | 21:40 |
| slickymaster | lol knome | 21:41 |
| slickymaster | really?? | 21:41 |
| elfy | slickymaster: well we do have the policy by default | 21:41 |
| * slickymaster now has sign in the pad | 21:41 | |
| elfy | in new releases | 21:41 |
| slickymaster | a sign | 21:41 |
| slickymaster | knome: but do you want me to drop the tags I added above your SIGN? | 21:42 |
| elfy | what's <literal> ? | 21:43 |
| * slickymaster is way dumb | 21:43 | |
| slickymaster | just now I've noticed what you are talking about knome | 21:43 |
| slickymaster | dumber than the dumbiest guy there is | 21:43 |
| slickymaster | :P | 21:43 |
| * slickymaster kicks himself insanely | 21:44 | |
| knome | elfy, it denotes something that literally read like that on the screen | 21:44 |
| knome | slickymaster, i don't mind if you keep them there :P | 21:44 |
| knome | slickymaster, i was going to remove that text | 21:45 |
| knome | but keep it to copy/paste | 21:45 |
| knome | elfy, reading this now | 21:45 |
| knome | isn't the second subsection just duplicating now? | 21:45 |
| slickymaster | yes, I'll be able to start to think straight in a few seconds | 21:45 |
| elfy | knome: it probably is now - you changed the meaning of the first one ... | 21:46 |
| knome | of course i did! :D | 21:46 |
| knome | the only thing left to explain now is how to make you only upgrade to LTS releaes | 21:47 |
| knome | if you've jumped through regular releases before | 21:47 |
| elfy | of course | 21:47 |
| elfy | but before you started changing it all around it made sense | 21:48 |
| knome | it did make sense | 21:48 |
| knome | but i think it was a bit weird | 21:48 |
| knome | and somewhat repeating | 21:48 |
| knome | i think this is much better; just explain upgrade targetting | 21:49 |
| knome | and we should probably mention the GUI way too | 21:49 |
| elfy | of course it does - because the first bit is the same - when the first bit was different - it didn't repeat | 21:49 |
| elfy | I'm just getting confused now - I'll look tomorrow | 21:50 |
| knome | ok, i'll try to get this in shape and pushed to the branch | 21:50 |
| elfy | yea ok - I can delete all the local stuff | 21:50 |
| knome | yep | 21:50 |
| elfy | cya tomorrow | 21:50 |
| knome | thanks :) | 21:50 |
| slickymaster | knome see my question in the tab | 21:51 |
| knome | resolved | 21:54 |
| knome | slickymaster, not execute because the other option is the GUI way | 21:59 |
| knome | which isn't in the pad yet | 21:59 |
| slickymaster | ok, agree, but do either of doesn't sound right _P | 22:00 |
| knome | let's fix it then | 22:00 |
| slickymaster | give me just a econd to put my son in bed | 22:00 |
| knome | sure, no hurry | 22:00 |
| slickymaster | knome: why not choose one of the following | 22:04 |
| knome | i guess i prefer "do" because ultimately, after you choose one of them, you got to do it as well | 22:10 |
| knome | so choosing is implied whatsoever | 22:11 |
| slickymaster | I', just guided by the sound of the sentence in this case knome | 22:12 |
| slickymaster | *I'm | 22:12 |
| knome | either one works for me | 22:12 |
| knome | let me push that to the actual code now | 22:12 |
| knome | i'll do a test branch so we can see how it looks | 22:12 |
| slickymaster | ping so i can branch it and build it locally | 22:13 |
| knome | 5mins | 22:13 |
| knome | slickymaster, https://code.launchpad.net/~knome/xubuntu-docs/vivid-upgrading | 22:19 |
| slickymaster | on it | 22:20 |
| knome | hmm | 22:20 |
| knome | now the first subsection is duplicating | 22:20 |
| knome | we should drop the first two points from the list | 22:20 |
| knome | agree? | 22:21 |
| knome | and maybe put the second subsection as the first section | 22:21 |
| knome | then we could also possibly drop the note from the currently first subsection | 22:21 |
| slickymaster | let me build them knome :P | 22:22 |
| knome | sure sure... | 22:22 |
| knome | ;) | 22:22 |
| knome | i'm still a man of action.. | 22:22 |
| slickymaster | yeah, my machine is slower than yours | 22:23 |
| knome | and i had the code available earlier than you etc | 22:24 |
| knome | note that i of course testbuilt it before i committed | 22:25 |
| slickymaster | but starting I think that the second paragraph of the upgrading section can be a little confusing for non native english speakers | 22:25 |
| knome | yeah, i was considering moving that to the upgrade path subsection | 22:25 |
| knome | to have a bit more context | 22:25 |
| knome | and then merging the currently first and third paragraphs | 22:25 |
| slickymaster | let me see | 22:26 |
| slickymaster | yes, I agree on that merge | 22:26 |
| slickymaster | it's logical | 22:26 |
| knome | ok, let me do a few simple changes | 22:26 |
| knome | then push again | 22:26 |
| slickymaster | ok | 22:26 |
| knome | Unit193, want to debug why the translation attributions aren't working today? | 22:29 |
| knome | slickymaster, pushed | 22:29 |
| Unit193 | knome: Sure, why aren't they working? | 22:29 |
| knome | >___< | 22:29 |
| slickymaster | one thing knome, he also should reduce the coverage of the hyperlink in the <note><para>If you are not getting an upgrade notification, or aren't seeing the release you are expecting to upgrade to, see <xref linkend="changing-upgrade-path"></xref>.</para></note> </section> | 22:30 |
| knome | oh yeah. | 22:30 |
| knome | duh. | 22:30 |
| slickymaster | ok, I'll wait before I pull it again | 22:31 |
| Unit193 | knome: Not what you meant? :( | 22:31 |
| knome | Unit193, no :D | 22:31 |
| knome | it works locally. | 22:31 |
| Unit193 | Utopic? | 22:31 |
| slickymaster | yes, locally their being built | 22:31 |
| knome | nooo | 22:31 |
| slickymaster | VV | 22:31 |
| slickymaster | V V | 22:32 |
| Unit193 | Well that's another bit of info then. | 22:32 |
| knome | pushed 270 | 22:32 |
| knome | slickymaster, ^ | 22:32 |
| slickymaster | ok | 22:32 |
| slickymaster | second please | 22:32 |
| knome | Unit193, do you think it would be sensible to put the .xml files for the desktop.guide under build or something else that can be bzr-ignored, so you didn't have to do make clean before each push? | 22:33 |
| slickymaster | knome: the hyperlink still covers the section called part of the text | 22:35 |
| knome | there is no way to edit the link content | 22:35 |
| knome | that's the way it is | 22:36 |
| slickymaster | ok | 22:36 |
| knome | the only other sensible option is to drop that note completely | 22:36 |
| Unit193 | knome: If you do that, you have to also edit the buildsystem. :P | 22:36 |
| knome | but i'm not sure if it's better to keep it or not | 22:36 |
| knome | Unit193, well exactly, which is why i asked.. | 22:36 |
| slickymaster | also missing a period in the end of the first item of the Upgrading to the next available release list | 22:36 |
| Unit193 | I don't see anything wrong with make clean... | 22:37 |
| slickymaster | knome: ^~ | 22:37 |
| knome | Unit193, except that then you have to build again after pushing | 22:37 |
| knome | slickymaster, actually, the second point should just get rid of that dot :) | 22:37 |
| slickymaster | that's what I was going to say since the third item also doesn't has it | 22:37 |
| slickymaster | knome: Changing your upgrade path | 22:39 |
| slickymaster | "a user of 14.04 could upgrade to 14.10 or 16.04." | 22:39 |
| knome | let's edit that paragraph in the pad where i just pasted it (at the top9 | 22:39 |
| slickymaster | I'm not sure about the use of could | 22:39 |
| slickymaster | ok | 22:39 |
| knome | opt? | 22:41 |
| slickymaster | as in choose | 22:41 |
| knome | but is that right | 22:42 |
| knome | i mean, | 22:42 |
| knome | the only sensible point to change the upgrade path is when you are running an LTS release | 22:42 |
| knome | i guess it makes sense | 22:42 |
| bluesabre | brainwash: good work | 22:42 |
| slickymaster | but you can always choose knome | 22:43 |
| knome | ;) | 22:43 |
| Unit193 | knome: I suppose feel free to... | 22:43 |
| knome | :P | 22:43 |
| knome | do we need the examples really? | 22:49 |
| knome | maybe | 22:50 |
| knome | let's see how that would look like | 22:50 |
| knome | i'm thinking an image would be so much better | 22:52 |
| knome | but i'm thinking that would be so overkill | 22:52 |
| knome | it would be like the first image ever in our docs ;) | 22:52 |
| knome | the reason why i don't think the examples help much is that the users reading this documentation will proabably have no idea about the release cadence we're having anyway | 22:53 |
| slickymaster | I'm happy with how it is now knome | 22:53 |
| knome | "even.04" doesn't ring their "LTS!!!" bells | 22:54 |
| slickymaster | ok, in the pad | 22:54 |
| knome | see the alternative paragraph | 22:55 |
| slickymaster | hmmm | 22:56 |
| knome | i think it's much more clear for the regular user | 22:56 |
| knome | no version number crap | 22:56 |
| knome | or too technical explanations | 22:56 |
| slickymaster | yeah, agree | 22:56 |
| knome | how would that look? | 22:57 |
| slickymaster | much cleaner | 22:57 |
| slickymaster | way better | 22:57 |
| knome | yeah, let's do this | 22:57 |
| slickymaster | we were just complicating excessively | 22:58 |
| knome | yeah | 22:58 |
| knome | testbuild.. | 22:59 |
| slickymaster | have you pushed it knome | 22:59 |
| knome | soon | 23:00 |
| knome | hmm | 23:00 |
| knome | you know | 23:00 |
| knome | we're going main branch now | 23:00 |
| knome | oops ;) | 23:00 |
| * knome shrugs | 23:00 | |
| knome | it's pretty much ready anyway | 23:00 |
| knome | so get the main branch | 23:00 |
| slickymaster | ok | 23:01 |
| slickymaster | it's seems alright in my pov knome | 23:05 |
| slickymaster | knome, tell me something please | 23:10 |
| Unit193 | Cat starts with the letter "C". | 23:10 |
| slickymaster | whatie Unit193 ?! | 23:10 |
| knome | slickymaster, yes? | 23:11 |
| knome | slickymaster, he told you "something" | 23:11 |
| slickymaster | can I safelly delete this/my branch -> https://code.launchpad.net/~slickymaster/xubuntu-docs/xubuntu-docs | 23:12 |
| slickymaster | since it's all done with | 23:12 |
| knome | sure | 23:12 |
| slickymaster | õr abandoned it | 23:12 |
| slickymaster | ok | 23:12 |
| knome | sergio-br2, connection problems? | 23:12 |
| knome | apparently... | 23:13 |
| slickymaster | like slickymasterWork | 23:13 |
| slickymaster | heheh | 23:13 |
| knome | got to banforward him next if he keeps going in and out | 23:13 |
| slickymaster | don't do that to the Work guy | 23:13 |
| knome | (a friendly banforward, to be lifted once the connection problems are solved) | 23:13 |
| knome | heh, not | 23:13 |
| knome | at least you are saying stuff | 23:13 |
| knome | but just littering the channel with join/quits is meh | 23:14 |
| slickymaster | :P | 23:14 |
| slickymaster | hey knome, maybe we should leave a ping to forestpiskie about his upgrade section already being in the main branch | 23:16 |
| slickymaster | it's done now | 23:16 |
| knome | well done ;) | 23:17 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!