[00:02] mhall119: same here :( [00:04] mhall119: the thing that's really sad about it is the changes i usually need to make are fairly trivial. not the kind of thing i should have to spend 10 minutes logging in on :/ [00:10] at least we can still edit it, the help.ubuntu.com/community is entirely locked down to edits until we can figure out some way to handle the spam [00:10] * pleia2 needs to chase down some loose ends there [00:11] yikes wow i didn't know that [00:11] i assume there's an rt ticket? [00:11] wxl: there was an rt ticket to shut down the spam, which lead to a full lockdown (except admins) [00:11] IS suggested we create a group of trusted editors, and only they can edit it [00:12] but the idea of maintaining such a list makes my stomach ache, and I don't yet know what else they can offer us [00:12] (plus such a list defeats half the point of a wiki) [00:19] pleia2: i guess i've never had an edit at it. what wiki software did it use? [00:20] wxl: same as wiki.ubuntu.com, moinmoin [00:20] pleia2: then how the heck did it have a problem with spam and the wiki doesn't? [00:22] wxl: if you look at 2016-01-06 under https://wiki.ubuntu.com/RecentChanges?max_days=14 the wiki.ubuntu.com one DID get a little bit of an attack, but it's nothing like the thousands of pages created on the help wiki over the holidays [00:22] as far as I can tell with the help wiki, wrong place, wrong time? :) [00:22] this is all a recent development [00:23] madness. [00:23] did the spam involve registering a lp account, too???? [00:23] the worst part is that actual people have trouble logging in, but not bots ;) [00:23] yep [00:23] ridiculous amount of work for probably very little return [00:24] we should require 2fa by default on sso logins [00:24] probably assumed it wasn't being watched [00:24] i've been using 2fa for quite a while and been pleased [00:25] other projects beyond ubuntu use the SSO, since it used to be *launchpad* SSO, not ubuntu-branded and some projects unrelated to ubuntu hosted stuff there (perhaps most notably, openstack) [00:25] so requiring 2fa doesn't just impact us [00:26] hm [00:27] well maybe we could require 2fa set-up for all users, make it a requirement to complete authentication on the wiki, and leave it as a user-selectable option for other sites [00:29] yeah, I'll have to collect these ideas somewhere so I can have a fruitful discussion with IS [00:30] well you can always put it in the ticket [00:30] yeah, could do [00:30] but if canonical hosting for our loco is any judge, most things on rt get kind of ignored XD [00:30] probably better to approach the right person or persons if you know where to find them [00:30] I usually submit the ticket and follow up in channel, but lately all my requests have been going through quickly [00:31] no need for follow up! [00:31] wow i wish that would happen for me [00:31] we've been waiting for the aforementioned hosting for almost a year [00:31] this is obviously a more complicated situation though, so it probably gets pushed to the "this is hard, do later" pile [00:31] and honestly i don't think our request is very hard [00:31] yikes, the ticket is still active? [00:31] though i guess it does require a wordpress install (read: security hole) [00:31] yep [00:31] let me dig it up [00:31] that sounds like an oversight [00:32] i've talked to people about it before including IS folks [00:32] crazy :( [00:32] also before i was on LC, jose was really helpful with trying to push it through [00:32] xubuntu.org runs on wordpress hosted by canonical, no big deal [00:32] anyway, I have a meeting to run to [00:32] have a good evening :) [00:32] pleia2: i was talking about wordpress in a way that i think only a sysadmin would understand XD [00:32] k bai [00:33] USING wordpress is easy [00:33] SECURING wordpress is a whoooole different beast [00:36] pleia2: should you have some interest in the subject, this is the ticket regarding our loco's hosted site https://rt.ubuntu.com/Ticket/Display.html?id=25072 and actually it's been more than a year! that makes our ticket one of the NEWEST ones in the loco queue. oldest was open 8 years ago. so i'll just be patient :O [07:33] good morning [07:36] Morning dholbach :) [07:36] hey popey [07:37] I am not going to be around for at least the first half of the Q&A this afternoon unfortunately. Need to pick kids up from school today. [07:38] popey: who did last week's? [07:38] dunno, not me. [07:38] hence raising it because it's my turn [07:39] mhall119 did with davidcalle [07:39] ok [07:39] I'll ping Nick and dpm later on [07:39] kk, off to drop the kids off at school now.. brb [07:40] see you! [08:31] * popey returns [08:33] balloons, dpm: it looks like it's us for the Q&A later on [08:34] sounds good [08:45] Morning o/ [08:58] pip pip [10:41] balloons, davidcalle, dpm, mhall119, popey: we should probably get another biweekly update out by the end of the week [10:42] good point [10:52] dpm: ping [10:59] hola jose [10:59] dpm: todo bien? [11:00] todo bien, a punto para ubucon summit? :) [11:06] yep! queria preguntarte si necesitaban una mano con algo [11:09] jose, gracias :) sí, te envío una lista por correo, estaba a punto de crearla [11:09] genial [11:10] statusupdate-bot: !update [11:10] * Fixing stuff [11:10] * Fixing more stuff [11:10] * Beer! [11:10] lol [11:11] dholbach, dpm: here is our biweekly update ^ :p [11:11] haha [11:11] the last one is a wishlist item, isn't it? [11:12] dpm, nope, there is a dedicated meeting [11:32] jose, primer mail enviado :) [11:37] woot woot [11:40] wait, what. [11:40] popey: that was weird. [11:40] You just approved someone onto the etherpad team and they just deactivated themselves. [11:40] also, i mistakenly added them to another team and immediately revoked them [11:41] * nigelb hands popey a jug of warm tea [11:41] Er, *kettle* [11:41] No wait, it's a pot of tea. [11:42] yeah, dunno what they're up to [12:03] jose, ok, segundo y ultimo mail enviado [12:17] dpm: respondo ni bien regrese, tengo que correr para algunas cosas [12:18] jose, genial, gracias! [14:06] balloons, dpm: so it'll be the 3 of us? [14:06] (for the Q&A?) [14:06] dholbach, I'm up for it [14:06] yep, me too :) [14:06] cool [14:07] dholbach, do you mind starting with the announcements? [14:07] can do [14:07] great, thanks [14:14] sounds fun! [14:15] balloons: does that mean you're part of it or not? :) [14:15] if yes, I'd include you in the announcement [14:15] dholbach, if you'll have me, of course ;-) [14:15] ok cool :) [14:45] ok done [15:32] mhall119, call? [15:43] School run.. biab [15:51] we ready dholbach? [15:51] balloons: yep [15:55] balloons: you're just on Freenode it seems [15:55] blargh [15:56] my bouncer likes to dc without saying [17:02] all right my friends - I call it a day - see you all tomorrow! :-) === JoseeAntonioR is now known as jose [23:13] wxl: btw, I am a sysadmin for my Actual Job, so I do know a fair amount about how to secure websites, and I wasn't speaking just as a user of wordpress ;) [23:13] pleia2: i know. that's why i said that XD [23:13] wxl: in xubuntu we have to get all our plugin and theme patches cleared by IS when we submit them, but the turnaround is pretty quick these days [23:13] so they do spend time in security review, but not long for us [23:13] well that's good [23:14] * pleia2 nods [23:14] as to the queue for loco teams, I don't know what's up with that, and probably something the LC should look into [23:14] if Canonical can't reasonably serve LoCos in *less than a year* then it's probably worth cutting the cord and admitting it's not something they realistically offer [23:15] that at least would reduce the expectation, and give them leave to find alternate hosting [23:16] true true [23:16] so who should we approach about that? [23:16] someone on the community team here [23:16] what are we talking about? [23:16] knome: web hosting for locos, wxl submitted a ticket for a wordpress blog a year ago, still not done [23:16] right [23:16] knome: and it's apparently the youngest in the loco queue [23:16] so /o\ [23:16] pleia2: and mine is one of the newest in the IS loco queue [23:17] yeah [23:17] that [23:17] mhm [23:17] knome: so someone on the council shoudl talk to canonical and see if it's reasonable to still say we CAN handle supporting the locos [23:17] at least in terms of IS [23:17] i don't know if it could help, but i have recently pushed this community theme to github: https://github.com/knomepasi/ubuntu-community-wordpress-theme [23:18] so maybe they would have easier time with the requests if people just used a few centralized themes and didn't ask this and that [23:18] well that's certainly a problem [23:18] the california loco (private hosting) uses some version of the unified theme [23:18] unified theme? [23:18] from like 100 years ago [23:18] this is from like this year :) [23:18] there was some community theme [23:18] yeah, old as mammoths [23:19] yeah [23:19] https://raw.githubusercontent.com/knomepasi/ubuntu-community-wordpress-theme/master/screenshot.png [23:19] well i'll try to remember to send out an email to the cc and we'll go from there [23:19] but our site is essentially a splash page, so even wordpress is overkill ;) [23:19] "we'll install wordpress and add stuff to it later" [23:19] mhmm [23:19] actually, i am on this channel because i've been meaning to ask about people testing that new theme [23:20] so wxl, if you haven't decided on a theme and want to give that a run... [23:20] knome: maybe an email to the mailing list too? [23:20] pleia2, on the todo [23:20] cool [23:21] with this theme, you can even change the logo from the wp admin, so no need for anybody to ask for another theme upload separately [23:21] knome: i'd email the loco-contacts list, too [23:21] wxl, once we have ironed out the biggest bumps, yeah [23:23] what i'd like to know now if there is something that is obviously wrong so i can fix it before people have been spreading the non-production-ready theme all over the internet [23:23] at which point it is almost as useful as the age-old community theme [23:24] i also wouldn't mind if this theme inspired others to contribute to it [23:26] it's also on my todo to talk with balloons to probably get the google code-in participants try this theme out as well [23:26] and since you can change colors and stuff from the admin too, it might be a good fit for both ubuntu gnome and ubuntu studio who are seeking for a new wordpress theme [23:28] wxl, so instead of asking me to email everybody, would you like to take some time yourself to see if the theme works for you? [23:28] knome: well, once my ticket gets taken care of, perhaps in a few years, sure. [23:28] LE sigh [23:29] i'll ask somebody else then. [23:29] thanks for the support! [23:29] wxl is a busy person ;) [23:29] an i'm not? [23:29] it's not that i'm busy [23:29] not everyone can help [23:29] i just have nothing to test it on [23:29] fortunately, i'm not the one who needs the wordpress theme [23:30] ok here's how we'll do it [23:30] you fly to canonical [23:30] rough up the head of IS a bit [23:30] then my ticket gets approved [23:30] then i try your theme [23:30] easy! [23:30] wxl: if you want to test it, you could just use virtualbox or something [23:30] yeah i guess i could [23:31] but ANYONE can do that :) [23:31] well, if you had read what i said, you'd know i wanted to fix things before it's uploaded on the IS servers so i didn't need to request for updates [23:31] yes, but so far no one is helping knome test it [23:31] so he needs folks to test in non-production environments [23:31] it's fine, i'll ask somebody else [23:31] preferably *not* on the internet, so in VMs [23:31] i am running it in a staging server on the internet as well [23:32] i could probably juju my way to a wordpress theme huh? :) [23:32] i think you are overthinking it [23:32] just set up wordpress anywhere with a web server and push the theme there [23:32] you can probably juju the web server, but not the theme really [23:33] but it's in git, so you only need to git pull [23:33] so i'll let you know when i get a vm set up [23:33] sure, thanks [23:34] admittedly this in between work but [23:35] there's no rush [23:35] you don't need to do it today