[01:29] newz2000: whenever you return, could you please look at that bug again [01:33] such drama [14:52] did the wiki theme just change? [15:03] AlanBell: earlier this week [15:04] no, it got made default just a few minutes ago [15:05] good that the smilies got fixed before it went live [15:17] oh, it was just a few min ago [16:29] hmm, diff pages are not hilighted any more [16:30] https://wiki.ubuntu.com/UKTeamMeetingAgenda?action=diff&rev2=99&rev1=97 for example === Daker is now known as daker [21:10] drat [21:11] AlanBell: if you see any more bugs would you go ahead and report them on ubuntu-website and tag them as light-wiki? [21:11] ^ anyone can do that actually [21:11] bonus points if you give me a ping here after reporting it [21:33] yeah, will do [21:34] AlanBell: and if you'd like to submit a patch, that would be OK too. ;-) [21:35] newz2000: can we get the code sorted out [21:35] AlanBell: which code? [21:36] https://launchpad.net/ubuntu-website/light-moin-theme ended up being pointed at my branch [21:36] not sure who did that, might have been cjohnston [21:36] which is plainly wrong as the code on the website isn't that code [21:37] yeah, let me see, that is a bit odd [21:37] I don't know what code is live at the moment [21:37] * newz2000 isn't sure either [21:37] I can't really do any sane patching if the trunk doesn't exist [21:38] * cjohnston didnt do anything [21:38] mhall119: maybe? [21:38] it's in my junk! lp:~newz/+junk/light-wiki [21:38] yeah, that is the wrong place too! [21:39] I can't do merge proposals to that [21:40] should I change the owner to ubuntu-website? [21:40] btw, if anything goes wrong, always blame me. That's my job. [21:40] Bug #674130 [21:40] Launchpad bug 674130 in ubuntu-website "Ubuntu wiki : "Page immuable" isn't at the tright place (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/674130 [21:41] maybe I should have pushed it to ~newz/+junk/ubuntu-website/light-wiki ? [21:42] or maybe ~newz/ubuntu-website/light-wiki [21:42] * newz2000 tries that [21:43] well I think it should be to a branch owned by a team or something [21:43] I belive it should be ubuntu-website/light-moin-theme and owned by the commiuunity team [21:43] like https://code.launchpad.net/~ubuntu-website-community/ubuntu-website/light-drupal-theme [21:43] ya [21:44] * newz2000 tries [21:44] created new branch [21:44] hmm [21:45] lp:~ubuntu-website-community/ubuntu-website/light-wiki [21:45] then... [21:45] is it the ubuntu-website/light-moin-theme newz2000 ? [21:46] They have a similar lineage [21:46] https://code.launchpad.net/~ubuntu-website-community doesn't look quite right [21:47] there are other themes for ~ubuntu-website-community [21:47] lp:ubuntu-website/light-moin-theme would be consistent with the others [21:47] refresh [21:47] fixed [21:47] great [21:47] I think atleast [21:48] now it needs the code uploaded to it [21:48] that looks good to me [21:48] I think its there [21:48] it is [21:48] sweet [21:49] bug 635035 is now properly fixed \o/ [21:49] Launchpad bug 635035 in ubuntu-website "light-moin-theme is not on Launchpad (affects: 1) (heat: 4)" [Undecided,Fix released] https://launchpad.net/bugs/635035 [21:49] woo! [21:49] lol [21:50] moin sucks [21:50] did I say that [21:50] If I could just move 6 bugs to "fix completed" at once in launchpad, that would rock [21:50] file a bug [21:51] I've got an api... [21:51] moin without xapian sucks [21:51] yeah, that would help [21:53] I think there are about 600 pages that do a brute force full text search each time they are opened [21:53] If you guys see any wiki bugs that are high priority, definitely mark them as such. [21:54] fairly sure that the save delay is also due to some kind of search going on as it is the same 20 second or so response time [21:54] Next week, say Tuesday or so, I'll do a half day sprint closing them out [21:54] AlanBell: yes, it has to look for users who are subscribed [21:54] thought so [21:54] so how come someone doesn't check the box and turn on xapian? [21:55] people have been bitching about the wiki performance for years [21:55] I can't remember, it may be either we're using a slightly too old version or there was some issue with xapien [21:55] all the moin sucks, lets use mediawiki stuff is just down to performance, not syntax or anything rational [21:56] AlanBell: probably the best way to get this chagned is to push for it leading up to next UDS. I honestly doubt it will happen before then. [21:56] newz2000: who is responsible for uds.ubuntu.com [21:56] cjohnston: it's not you? [21:56] * newz2000 keeps mixing them up... [21:56] and yes, it is an old version as I was talking to the moin developers in #moin about it and 1.6 is totally out of support now [21:57] lol [21:57] no [21:57] Well, the photos imply its' the design team [21:57] did jono ever hand that over to anyone else? [21:57] dunnp... theres bugs being filed on it [21:57] of course if it were thed esign team there would be no purple on it [21:58] have they gone off Aubergine? [21:58] it doesnt follow design standards at all [21:58] true [21:58] AlanBell: no mixing [21:58] AlanBell: aubergine is business = canonical [21:58] cjohnston: that's not quite right either [21:59] more business = more aubergine [21:59] uds isn't Canonical!! [21:59] thats what i was told [21:59] we wanted to change summit to aubergine [21:59] right, that is pure community, no purple [21:59] and the torus pie chart things indicate a mix [21:59] (taht was meant for AlanBell but works for cjohnston's comment too) [22:00] http://design.canonical.com/brand/5.%20Ubuntu%20colour%20palettes%20and%20colour%20landscape.pdf page 53 [22:00] newz2000: Bug #671122 <-- just for you [22:00] Launchpad bug 671122 in ubuntu-website "install an accessible wiki theme (affects: 1) (heat: 14)" [Undecided,New] https://launchpad.net/bugs/671122 [22:01] * newz2000 smacks head [22:01] thank AlanBell for that one [22:01] thank you AlanBell [22:01] yup, I was going to come on to that! [22:04] the light-moin-theme release today didn't go down that well with the low vision users in #ubuntu-accessibility [22:04] small font, grey on grey [22:05] probably the best place to discuss this is on the mailing list [22:05] That way we can get the attention of the designers [22:05] bunging the simple-mente theme in the list of available themes would be good [22:05] AlanBell: is it compatible with 1.6? [22:05] https://lists.canonical.com/archives/ubuntu-website/2010-October/001064.html [22:05] I believe it is compatible with 1.6 [22:06] ok, I'll forward that e-mail to the designers [22:06] * newz2000 wonders how he missed that before [22:06] not many actual theme changes between 1.6 and 1.9 and I think simple mente is a few years old [22:07] http://moinmo.in/ThemeMarket/SimpleMente there is a 1.6 release [22:09] if we can get that installed I can get feedback from users who can set it as their personal default and then I can fix anything wrong with it [22:09] I think I'd rather get light-theme fixed [22:11] well that isn't going to be high contrast [22:12] it would be great to get all the navigation stuff into the light theme [22:16] with http://beta.ubuntu-uk.org/ I started from the default wordpress theme and then made the body text darker and background lighter and size bigger until the verdict in -accessibility was that the text no longer looked fuzzy [22:18] * newz2000 thinking out loud a bit... [22:18] a simple js/css based style switcher could do all of that [22:18] it could [22:19] AlanBell: do you want to propose an additional css style sheet that could be included to increase the contrast, font size and line spacing a bit? [22:20] ok [22:24] so my branch is rather diverged from the trunk at this point, with a bunch of changes that have been manually merged, or won't be merged [22:25] not sure how to realign it [22:25] AlanBell: I do'nt think you can reconcile the two [22:27] hmm, bzr pull and merge or something might do it [22:28] You can give it a shot, but I'd suggest starting with a clean copy of my branch [22:28] What I do is this: [22:28] mkdir project-name [22:28] mv old-branch project-name/old-branch-archive [22:28] cd project-name [22:28] bzr branch new-branch [22:29] That way you can still refer to old-branch if you need [22:29] hmm, merging seems like it will teach me more about bzr though :) [22:30] well, the right way to do that is this... [22:30] bzr branch new-branch new-branch-bug123 [22:30] then work in new-branch-bug123 and when done push it as a merge proposal [22:30] then when approved, merge back into new-branch and push it [22:31] if you merge your branch with mine you'll get a combination of conflicts and things that I won't accept in a merge proposal [22:31] (i.e. purple headings) [22:47] ok, took a fresh branch [22:48] that is a lot of executable images in /light/img [22:49] and css files [22:51] so if I pop together an accessible stylesheet how would that get loaded? [22:51] would it stay loaded as you navigate around the wiki?