[02:18] https://lists.ubuntu.com/archives/ubuntu-devel/2016-February/039224.html so I'd guess I hit that. [02:50] Unit193: :D [04:10] Alrighty, I've got the notes mostly in order for a Catfish release this weekend. [04:11] knome: If you'd like, I can go ahead and apply those changes (Noto 9) and proceed from there [04:11] night all [07:28] knome pleia2 - thanks for doing that stuff [07:29] no release announcement though - still .2 [12:35] !team | feature freeze is now in effect: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2016-February/001171.html - https://wiki.ubuntu.com/FeatureFreeze [12:36] I can never seem to team right [12:51] bluesabre, you can't use URLs with factoids [12:51] flocculant, np; and only having announcement for .2 is ok for me too [12:52] bluesabre, i would probably do a quick feedback round on the mailing list before applying the change [12:52] bluesabre, not only because i'd like to hear what others feel about that setting too - with seeing it themself [13:07] ok, the staging site is restricted to logged in users only [13:08] somebody around to test seomthing? [13:08] *something too [15:25] Unit193, first, simply head to http://staging.xubuntu.org/ [15:25] Unit193, are you redirected to the login pagE? [15:26] (don't login yet) [15:26] Yes. [15:26] now go to http://staging.xubuntu.org/contact/ [15:26] are you again redirected to the login page? [15:26] So it'd seem, yes. [15:26] great [15:26] now log in [15:27] or at least try to - i've no idea what happends, but i expect you're able to log in [15:27] -d [15:27] During redirect there was an error, but redirected fine. [15:27] yeah, that's from the openid-launchpad plugin [15:28] so you're now logged in and can see content? [15:28] Nope, logged in and went back to content, with the login button again. [15:28] oh, hmm. [15:28] that was unexpected, but in a good way... [15:29] let me do something quickly [15:29] ok, so try logging in now [15:30] Didn't seem to, but login gave me the option to pass along that I was in 'xubuntu-team' this time (unchecked) [15:31] well check that :) [15:31] and then try logging in again [15:31] that should enable you to actually log in [15:32] Was on contact, figured wouldn't need to. Done. [15:32] oh you was? [15:32] so... let me do a recap [15:33] the first time logged in, could you see content? [15:33] Logging in while trying to get to /contact/ only worked with xubuntu-team. [15:34] great, that's kind of expected [15:34] now that you are in and things seem to work as they should... [15:34] open a tab at http://xubuntu.org/tour/ [15:34] and with the current tab, go to http://staging.xubuntu.org/tour/ [15:35] i believe you notice the difference [15:36] Awwh, can't paste it, have to find and click. [15:36] :D [15:36] about -> feature tour [15:36] Presuming of course you mean the top bar. Yes I did find it. :P [15:36] yeah [15:36] (Exactly where I looked.) [15:38] so... you notice the difference? :P [15:39] Top bar, black? [15:39] noo [15:39] that's the wp admin bar [15:39] Ready to use? [15:39] look at the colored backgrounds [15:39] and notice they don't exist in the staging site really [15:40] which one you prefer (just gut reaction)? [15:42] That's what I was referring to, yep. And, logged in. The green background is fine, but scrolling down to that other one makes me think too much of old style sites. Though, the one without a background isn't aligned properly. [15:42] that's the other thing; [15:42] on the staging site, if you scroll down, there are two different styles [15:43] the blue one is spread to the edge of the content area, the pink is contained in the regular padding [15:43] which one of those you like better (without taking the color into account)? [15:44] Well considering 'get xubuntu', pink I think. [15:44] yeah, let's see where this goes, but i'll likely change things soon [15:45] so one more thing [15:45] compare the contact pages [15:46] how do you feel about that change? (introducing this "highlight" style for all these smaller boxes too, and a red color for important/warning messages) [15:47] Do something with the font? And the warnings is certainly good. [15:47] mm, like what? [15:48] smaller? bigger? [15:48] Everything is a bit condensed, and seems a hair darker. [15:49] yeah, that's because there's more contrast [15:49] and the vertical condensation is intentional; these one-liners would take awfully lot of space if they had the same amount of padding as the larger sections [15:50] but let me try to tweak it to somewhere in the middle [15:50] how about now? [15:50] also changed font color [15:50] that might be too light [15:51] fixed that :P [17:02] knome: works for me - just thought I would mention it [17:02] that release note now being 2 point releases behind [17:03] yep [17:04] also, hello flocculant@staging :P [17:04] who shouldn't be logged in now :) [17:05] * knome shrugs [17:05] somebody who doesn't care about staging? :P [17:05] but since you read the backlog, feel free to comment on the changes too [17:05] not at all - but I'm not logged into it [17:05] you're not? [17:05] nope [17:05] well [17:05] well i got a mail saying you registered :D [17:05] could be - I never really logout anywhere :D [17:06] i don't know if you are "logged in" right now.. [17:06] oic - well I went to look then closed it [17:06] hehe [17:06] fair enough [17:06] aah ok :) [17:07] didn't read the whole back log tbh - got as far as the 'try to login' stuff :D [17:07] hehe [17:07] but good you can [17:07] :) [17:07] basically feel free to mess with the content there as much as you please [17:07] right [17:07] if you want to try new pages or menu structure or anything [17:08] oh [17:08] i will also play around with new css and features there before landing them to production [17:08] so there rather than end up with dead drafts at x.org [17:08] sounds like a good plan [17:08] dead drafts on x.org are ok - if the intention is to publish it at some point [17:09] but if you just want to see how it would look... then staging is probably better [17:09] this because if it's even the intention to publish, it's good to have it ready on x.org [17:09] yep ofc [17:09] if it then happens that we don't publish something... it can simply be deleted :) [17:09] :) [17:10] * knome should fix teh responsive styles for the highlight boxes next [17:10] knome: re pages ... you waiting for dkessel responses? I thought the plan was to start that this week? [17:11] i am waiting, yes [17:11] it looks like we have like 3-5 articles though, so we're not in a rush [17:11] i was preparing to have like 6-8 [17:11] well [17:11] I'd want to see them all published prior to release date - seems a bit silly to not do that [17:12] of course [17:12] uh-oh :) [17:12] dkessel: ha ha ha [17:12] dkessel, ;) [17:12] So that's what you mean with "no rush" :p [17:13] dkessel, you're the biggest blocker at the moment :P [17:13] At least that's consistent with things at work :p [17:14] haha [17:14] lol [17:22] knome: fop upgade in proposed [17:22] wait for it ... [17:22] i am waiting for that too [17:22] does it make fop a distant relative for dkessel? [17:23] I meant wait for me to grab it - reboot *just* to make sure and see if building pdf works [17:24] lol [17:24] Makefile:109: recipe for target 'user-pdf' failed [17:24] it doesn't [17:24] any error if you run the command directly? [17:24] what command? [17:24] err, the one that is in user-pdf :) [17:25] wouldn't have a clue what command or what user-pdf is nor where it might be [17:25] heh [17:25] ok, so basically, go to the user-docs subdir [17:25] then run the following: [17:26] xsltproc --stringparam paper.type A4 --xinclude -o fo/C-A4.fo ../libs-common/xubuntu-docbook-pdf.xsl C/index.xml [17:26] then [17:26] ../scripts/pdf-create.sh C [17:27] yup [17:27] loads ... [17:27] yes, that should create the PDF [17:27] if not, then it should throw an error [17:27] of errors [17:27] lol [17:27] pastebin them [17:28] unless they are the same errors as before [17:29] http://paste.ubuntu.com/15133496/ [17:29] I think more or less the same as before [17:29] ugh [17:30] no, that's something else [17:30] :) [17:31] is it looking for font in the wrong place? [17:32] likely related to the fact that you ran the command directly [17:32] i'd think [17:36] ok - well obviously no idea here [17:36] I did my bit - tested it :p [17:37] can test it later today [17:39] ok [18:15] knome, flocculant : new draft revision of that article is done :p [18:17] thanks for pinging me :D [18:22] dkessel, cool, thanks [18:22] and looks good too [18:24] tried not to write the same as flocculant everywhere :) [18:25] haha [19:03] dkessel: always good to go first :p [19:43] pleia2, you have a minute or two? [20:07] actually, my turn to dash, ttyl [21:20] * pleia2 was out lunching [21:22] best call [21:24] Unit193: don't know if you caught ^^ but fop landed in -proposed and it building pdf still fails [21:25] I kind of saw. [21:25] elsewhere apparently though :) [21:25] k [21:25] I just didn't see/know why. [21:25] well I have no chance then lol [21:27] Well I didn't exactly look, knome seemed on top of it. [21:28] yea [21:32] bluesabre: not really noticing I'm using a different font for the most part [22:10] flocculant, with noto sans 9? [22:11] * pleia2 tired [22:11] knome: but I have a minute or two if you need [22:12] pleia2, ok [22:12] 1) log in to staging.xubuntu.org [22:12] then go see the following things (and compare them to production): [22:12] - the feature tour [22:13] - contact [22:13] - blog front page [22:14] (the sidebar doesn't have all the widgets we want there on the staging stie, but imagine it does) [22:16] * pleia2 looks [22:16] thanks [22:16] the tour/contact page visual changes have already (mostly) been pushed to the repository, the blog front revamp is still only on staging [22:17] knome: yea - set up default here (except window manager) just changed font [22:17] yep [22:17] x.o feature tour still shows color across whole screen, rather than highlight on edge that s.x.o has [22:18] pleia2, yes, isn't the idea of staging that we can plan and work on new features there? [22:18] knome: I guess I don't understand what you're asking me to do :) [22:18] knome: confirm I think the changes are pretty? [22:18] pleia2, i've made these changes; do you like them? [22:18] yeah. [22:18] knome: mmm - actually not keen in hexchat [22:18] oh ok :) [22:18] feature tour is very pretty, yes! [22:18] * pleia2 looks at next on list [22:19] flocculant, i wouldn't know, but i'd also expect an irc client to use a monospace font :P [22:19] the contact page is subtler, but basically it moves the old

markup to the same highlight markup as on the tourpage [22:19] (with a bit less padding for blocks with just one
) [22:20] and the new red warning/important color too :) [22:21] knome: yea but you use a terminal for irc ... [22:22] flocculant, even if i'd use a GUI client (i've done that 15 years ago...) [22:23] yes, contact is nice [22:23] good good [22:23] knome: "blog front page" is /blog ? [22:23] knome: anyway all that aside - I'm not that bothered if we change [22:24] pleia2, yes [22:24] flocculant, me neither - i'll probably just change back to droid though [22:24] I like the old one, it has pretty pictures [22:24] full showing of blog posts ftw [22:24] pleia2, the stacking of the blog posts is a bit ugly [22:24] no likey "read full article" on /blog [22:24] what about showing one full article? [22:24] it's not what people expect [22:24] aha [22:24] no, it should just be a feed of all the full posts [22:24] :) [22:24] like it is now :) [22:25] ok, then i'll try to see how i can improve the stacking there [22:25] that's good feedback [22:25] also put in some pagination links so people can easily navigate [22:25] yeah [22:25] knome: it's probably easier to change I suppose [22:25] would be nice to go back another 5 posts or whatever in history [22:26] pleia2, wordpress pagination means you can go back one page of posts [22:26] pleia2, and then another [22:26] knome: yeah [22:26] pleia2, and another... [22:26] it's a default thing, like on my blog [22:26] but we have no linky for it on ours [22:26] * pleia2 wants to click "older posts" [22:26] that's one of the default implementations i don't link in wordpress [22:26] *like [22:27] but good good, i'll keep this in mind [22:27] hopefully we can land these changes this month [22:27] thanks, nice work! [22:28] btw, Unit193 is our backup all powerful wizard on our dev server now [22:28] :3 [22:28] we should probably write this down somewhere on the wiki under admin things [22:28] yes [22:28] Quite. [22:28] do we want it public or private? [22:28] public [22:28] if latter, put it under /team [22:28] just like social media admins, etc [22:29] OK, I think it's well past time for me to register on the wiki... [22:29] hehe [22:29] Unit193, you did already! [22:29] * Unit193 raises eyebrows. [22:29] i see you in the user list. [22:29] probably can add to http://wiki.xubuntu.org/website/admins [22:30] even if it's not website o_o [22:30] maybe we make a /server/admins [22:30] then we can also make clear what groups exist for specific sites on the server [22:30] (mostly knome for now, but that should evolve) [22:30] i'd probably just put it under website [22:30] it's website related [22:31] or rename website -> web [22:31] bikeshedding, I don't care, just want it written down [22:31] i'm on it [22:34] http://wiki.xubuntu.org/website/admins [22:35] oh, staging [22:36] pleia2, also, we should talk about maintaining static. [22:36] version control is nice, but in this situation it feels a bit moot [22:36] * pleia2 thumbs up [22:36] why? [22:36] (should just move to backups) [22:36] today i wanted to change extras.css [22:37] pushing stuff to CVS, then pulling it from there for a one line change... [22:37] (especially since extras.css is not really static, it's very temporary and dynamic) [22:37] * Unit193 borked on CVS for a sec. [22:37] yes yes VCS:P [22:38] lol cvs [22:38] so maybe the answer is actually another subdomain assets.xubuntu.org [22:38] knome: In the wiki, calendar and irc tabs work for you? [22:38] Unit193, no, neither the work item tabs [22:38] I know it's a pain, but I really don't like steering away from an RCS [22:38] seems like over time it'll be more of a pain [22:39] evening all [22:39] hi bluesabre [22:39] pleia2, i already have a few uncommitted changes in static... :| [22:39] knome: so, try to get some feedback on the ML, -users or -devel? [22:39] hey flocculant [22:39] actually no, only that one [22:39] knome: meh [22:39] that makes my life hard :P [22:40] no no, it's only that one line [22:40] :P [22:40] knome: Did you create my wiki account? [22:40] still, if you get hit by a bus and I want to update/restore the site, I can't [22:40] Unit193, i might have [22:40] ugh. :P [22:40] let me explain [22:40] knome: avoid buses [22:41] i mean i understand your point of view [22:41] and i think it's great for most of the content in static. [22:41] but for extras.css... [22:41] this change is something i'll land to production ASAP [22:41] i have even almost pushed it to the theme repository [22:41] in an ideal world, extras.css is empty [22:42] it's basically my getaway ticket from IS; it allows me to fix things i've foolishly broken in the CSS [22:42] bluesabre: ...I saw that movie. [22:43] so basically it's really a part of the website [22:43] which we just happen to keep in *some* url [22:43] knome: if it's just that one file, maybe it's ok [22:43] Unit193: entirely possible I have not seen referenced movied [22:43] just don't want it to turn into a monster of "just a little edit here and there.." [22:43] then it's a 100 line file that we have no backup of [22:44] pleia2, definitely not; *i* want the VCS stuff for majority of the things too [22:44] it just feels silly to throw one-line fixes via that [22:44] because that's what they are - fixes [22:44] so long as the one liners are included in the next proper update, religiously :) [22:44] i don't introduce new features via extras.css [22:44] of course [22:45] maybe we should put that subdir on .bzrignore [22:45] or move it to another subdir [22:45] or sth. [22:46] break is over, need to get back to actual job now [22:47] yeah [22:47] have fun [22:47] always :) [22:47] also, the ownership for static is elizabeth:elizabeth [22:47] just saying... [22:47] (so i can't even touch the files without sudo, which has clearly been intentional :P) [22:47] :D [22:48] well played [22:48] knome: there's a static group, it's just an oversight [22:48] yeah, until she put me in sudoers ;) [22:48] I am not perfect :) [22:48] :o [22:48] pleia2, or did you pull from a repository? [22:48] just fix up group permissions with sudo [22:48] does that change the perms? [22:48] I don't remember [22:49] * knome considers putting himself in the elizabeth group [22:49] sticky bit should have made it preserve permissions in the subdir, but who knows re: bzr [22:49] yeah.. [22:49] don't be bad [22:49] :P [22:49] :D [22:50] identity theft! [22:50] ok ok, get back to work you slacker >:) [22:50] * pleia2 works! [22:50] (j/k)