[17:59:51] Hey everyone. [17:59:58] I'll be doing IRC today, as normal. [18:00:00] hi James [18:00:08] hey hey [18:00:43] * greg-g waves [18:01:19] (I'll also be presenting, briefly, during which time AnnaKoval will be IRCing.) [18:01:42] :) [18:01:58] cooperation FTW [18:02:13] <3 [18:03:14] Theoretically the youtube feed will be at https://www.youtube.com/watch?v=ot9rqWOTeeU [18:03:30] bd808: No, it changed. It's now http://youtu.be/RWSwfCFpsGA [18:03:38] bd808: Hence why I removed it from the /topic :-) [18:04:10] * bd808 goes back to lurking quietly [18:04:26] bd808: Sorry for the confusion. [18:04:38] no worries. [18:05:06] I suppose good day then James_F and AnnaKoval :) [18:05:18] Video now starting from our end. [18:05:27] Shout when you get it. [18:05:35] Got it [18:05:40] just did [18:05:41] yay [18:05:42] got it [18:05:45] got video [18:05:46] Excellent. [18:05:59] there's a squiggle on the screen [18:06:04] does anyone else see a squiggle? [18:06:09] now you can't see it because it is white [18:06:10] Thanks, everyone. About 60 seconds on delay. [18:06:41] cndiv: ^^ re squiggle [18:07:06] I've always wanted a mini-me [18:07:08] thanks JohnLewis :) good day to you too [18:07:35] Erik's caused the meeting to descend into giggles. [18:08:07] Erik is a funny man! :) I do love Geoff's images around the office. They make me giggle a lot. [18:08:12] stream... ? [18:08:19] thedj: http://youtu.be/RWSwfCFpsGA per /topic [18:08:27] me too MissGayle ;) [18:08:43] ah then someone tweeted the wrong url [18:09:03] SQUIGGLE ON ERIK'S HEAD [18:09:06] :) [18:09:16] was wondering if I was the only one seeing it :) [18:09:31] thedj: It changed because Google's services sometimes just do that. [18:09:33] greg-g, that is a fascinating comment to walk into the room to.... [18:10:00] hi Maggie_Dennis :) [18:10:03] * halfak waits for the view to change back [18:10:25] Maggie_Dennis: :) :) [18:11:15] "L" [18:11:20] thedj: Tilman or someone else beat me, the right url is tweeted now [18:11:33] jamesofur, HaeB: Thank you! [18:11:59] (Please, everyone shout questions as and when you have them.) [18:12:49] James_F: Will the squiggle be a permanent fixture of the Metrics meetings, moving around to new locations with differen colors and such? [18:13:02] kannada [18:13:05] greg-g: We don't know what the squiggle is, so… :-) [18:13:11] my mothertongue :) [18:13:14] James_F: Yes. I'll take that as a yes. [18:13:15] greg-g, I can print out a tilde on a stick [18:13:20] * James_F chooses to blame Google. [18:13:20] and move it around [18:13:30] mwalker: that'd be ideal, yes. [18:13:32] that squiggle is the weirdest glitch I've ever seen [18:13:57] are we sure it's a software problem and not just something on the camera? [18:14:00] Next we're going to have an update on the Growth team from Steven W. [18:14:18] marcoil: It doesn't look like anything is on the camera here… [18:14:37] it only appears on the camera, not when slides are shown [18:15:37] victorgrigas, marcoil et al: OIT says it's a google thing. and they can't troubleshoot it during the livestream. sorry. :] [18:15:47] For those asking about the squiggle: it's a video artifact that just appeared. We have a really complex video setup, and cannot troubleshoot it now. [18:16:02] AnnaKoval, cndiv: thanks for the info! [18:16:10] ^ ftr that was supposed to be a grin not a smile :\ [18:16:33] np marcoil hth :) [18:16:34] thanks [18:16:37] I don't know if it's Google, if it's the camcorder, if it's the blackmagic box, if it's any related driver, if it's a cable, etc. [18:16:56] hoping it disappears as quickly as it appeared. [18:17:00] black magic sounds suspicious [18:17:16] pixies! [18:17:18] or someone who just drew an L in the software on April 1 and left it there .... hm [18:17:27] Eloquence_: not only is it BlackMagic, it's "BlackMagic Intensity Extreme" - possibly the best product name ever. [18:17:51] everything is better with "Extreme" tacked onto it [18:17:59] blackmagic maybe or it could be the legal interns who mocked up geoff's pictures ;) [18:19:10] Fun figure for getting a sense of the split between wikis: https://commons.wikimedia.org/wiki/File:Distribution_of_newly_registered_users.english_vs_other_wikis.svg [18:19:11] We should design Extreme Visual Editor, and Extreme Flow, and oooh...Extreme HR. [18:19:14] any ideas to making it easier to build these "getting started" tours ? [18:19:25] long term [18:19:33] we should switch to "WhiteMagic Calm Moderate" [18:19:33] James_f: ^ [18:19:43] thedj's Q [18:19:54] halfak: Yes, waiting for questions. [18:20:04] Just wanted to make sure you saw it :) [18:20:06] James_F: thx [18:20:11] thedj: have you done any tour-making? [18:21:04] no, with easier i mostly mean 'more distributed' and thus also easy (not too technical) [18:21:12] now that i think of it :) [18:21:18] * James_F grins. [18:23:04] thedj: I agree with those objectives. I've found it pretty painful to build tours, but do-able (for someone with extremely limited fluency in javascript). [18:23:37] i'm just worried that we are in need of having a professional tech team to build guided tours long term, and that doesn't fully seem sane [18:23:47] non-registered :D [18:23:51] but doing things in a way that is easy to port and modify, and really separate content from code, would be nice. [18:24:04] ragesoss: exactly [18:24:18] MIC! [18:24:20] ty [18:24:41] thedj: yeah, I agree... except that it's not really necessary to have professionals do the development... it's technically less complex than a whole lot of the Lua modules that volunteers have made. [18:24:46] The squiggle is admittedly hilarious. It looks at this point like somebody's trying to highlight Steven Walling's sideburns. :) [18:24:53] but it's not nearly as accessible as writing a Lua module. [18:24:55] ragesoss, we are in the process of improving the API. [18:25:19] I think we can also do more to teach people the ropes once that's done. [18:25:25] The experiment I have designed for the anonymous editor signup CTAs will help us understand whether we are scaring people away. [18:25:25] halfak: By the time you shout that the person will have finished speaking, and also is not on IRC. :-) [18:25:52] James_F, better than not saying anything [18:25:56] have we ever looked into creating an alternative to ip addresses for the anonymous edits? then allowing only the trusted people to do reverse lookup and ban IPs? or is the publication of the IPs the whole point to deter vandalism? [18:26:23] dr0ptp4kt, I don't see how that is different than an account. [18:26:27] dr0ptp4kt: Yes, and no. [18:26:41] e.g. register an account with a randomly generated username and use that to edit. [18:26:51] halfak: but without having to do that step :) [18:27:18] just: have unique strings that aren't IPs, that checkuser can get around [18:27:25] there has been talk of anonymous auto accounts (edits in a session become associated with a random number) [18:27:40] Current Wikipedians need an ID to track vandal activity [18:27:51] e.g. 4 warning rule of thumb. [18:28:10] How do we know we hit 4 warnings unless there is a semi-persistent identifier of most anons. [18:28:15] ^? [18:28:40] halfak: a unique string we create based on ip [18:28:42] halfak: most anon vandal warnings are put on IP talk pages [18:28:50] currently, anyway [18:28:52] greg-g: +1 could do that. [18:28:53] halfak, the idea is it would be persistent but not expose the ID [18:29:02] How would we track the user though? Cookie? [18:29:16] halfak: however we do it now [18:29:19] The user could then just keep dumping the cookie to vandalize [18:29:21] halfak, or could be a hash of the IP or something. [18:29:27] +1 hash of the IP [18:29:27] halfak: we use an IP block [18:29:40] With a reverse mapping stored for checkuser, etc. [18:29:44] I think that's a really interesting solution. [18:29:52] Oh yeah. No dumping checkuser. [18:29:54] Of course, would be very complex, and the main downside is it means regular users can't report anon abuse. [18:30:09] * greg-g nods [18:30:12] But someone told me that isn't done very much. [18:30:30] superm401, that hash would be consistent in the same way that the IP would. [18:30:35] No practical difference there. [18:30:43] Basically we don't currently block IPs on anything other than their IP. [18:30:48] halfak, I know, I'm talking about regular users. [18:30:52] halfak: it's pseudoanonymity [18:30:55] Getting their IP to report abuse to the ISP/school/employer [18:31:03] do the regular users go look at arin/afrinic/apnic, etc.? if they reported a hash, would that be sufficient? [18:31:10] with is one step up from public IP :) [18:31:14] Next up is… me? [18:31:17] dr0ptp4kt, yeah, that's the question, how much it's actually done. [18:31:17] s/with/which/ [18:31:53] is this something that would have a trace in the DB? I could find out how often users without checkuser right report abuse then. [18:31:54] Wait, are we talking about hasing user IP publically facing? [18:31:58] Extreme Visual Editor. [18:32:05] JohnLewis, yes, I think so. [18:32:17] halfak, no, because we're not talking about reporting it on Wikipedia. [18:32:19] i suppose we don't know in practice unless cc'd. if we act as an intermediary or are cc'd commonly, i suppose that provides some insight on report to isps. [18:32:28] haha MissGayle :) [18:32:36] We're talking about User:Foo sees 1.2.3.4 vandalize, so reports to 1.2.3.4's ISP. [18:32:37] beat-a-labs [18:32:46] cscott: :) [18:32:47] superm401, gotcha [18:32:56] so, we'd need a checkuser to do that. [18:32:57] halfak, Foo might note they did so on-wiki, but not always, and not necessarily in a way easy to detect by script. [18:33:09] cscott indeed :) [18:33:10] halfak, or whatever right is deemed appropriate (e.g. admin?) [18:33:23] Yeah... might not need checkuser to check an anon's IP. [18:33:28] Well, I say a firm no to hashing user IPs. While anon reporting may not be much - I myself deal with user IPs quite a bit for spambots and general work, asking a CU for every small task is annoying and will pretty much defeat the point of using it for 'emergency' cases only. [18:33:30] But checking a reg. user IP... [18:34:01] And it's a question whether we want this, or whether it's a good disincentive to anon editing like dr0ptp4kt asked. [18:34:03] JohnLewis, You'd still be able to ident the user by the hash in the same way as the IP [18:34:16] halfak: Fair enough then [18:34:30] ... standing by for questions for James_F if there are any ... [18:34:31] JohnLewis, yeah, it would only affect you if you use their IP to report abuse to their ISP [18:34:37] But you couldn't figure out the city or ISP of the user. [18:34:42] dido sotiriou ? nice :-) [18:35:10] James_F: How has the feedback for VE been lately ? Has the team been getting enough since they went back into beta mode ? [18:35:20] halfak: Proxy checking n stuff requires the raw IP anyway - so that'll be a serious disadvantage unless resolved otherwise. [18:35:48] True, and even just tagging talk pages as {{belongs to school}} or whatever. [18:35:54] thedj i'll ask :) [18:37:14] hey kat :) [18:37:25] why is their a white worm thing on the screen... [18:37:52] Matrix anomaly [18:37:53] thedj did that answer your question? :) [18:38:08] AnnaKoval, still is with stream lag [18:38:27] thx [18:38:40] thedj np :) [18:38:44] jamesofur, that's how you know the NSA is listening [18:39:31] halfak lol ;) [18:39:41] JohnLewis: the proxy checking thing, you're referring to the ability to tell on wiki as a CU it was going through a certain proxy, right? or are you referring to app server back-endy things like X-Forwarded-For and so on? or are you talking about proxies even for non CU policing? [18:40:01] halfak: given who/what we are, they're always listening ;) [18:40:03] or some combination or something else :) [18:40:10] * James_F returns. [18:41:05] :) [18:41:08] Now moving on to Ori and Erik B. talking about Flow and HHVM. [18:41:08] dr0ptp4kt: I'm talking about just using the IP to run common checks on the IP to see if it pings back as a web host, open proxy, mail server etc plus the ability to go to the IP and see if it is running a webserver and what content is there. That stuff really [18:41:13] Well, hopefully moving. :-) [18:41:58] JohnLewis: gota ya. in other words what a non-privileged user could do for policing, primarily, right? [18:42:27] (that is, assuming CUs could do reverse lookups on the hash) [18:43:00] James_F, does/will the feature also support constructions? These are particularly hard to edit usually because you often have to switch between sections to find the original tag. [18:43:26] pajz: Yes, re-use of references is already supported. [18:43:40] lol, any questions :) [18:43:47] dr0ptp4kt: Basically yes but without getting a CU involved like is possible now. Having to go through a middle man really would defeat the ability for the community whom are not the 'content' guys to do what they do which in this case for me, is dealing technical aspects of IPs and identify them. [18:44:10] pajz: This, BTW, is an example of why doing "section editing" right is very hard, because we need to know a bunch of things about the whole page. [18:44:17] HHVM -- catching PHP up to smalltalk80 [18:44:23] JohnLewis: yeah, i got you [18:44:30] cscott: :) [18:44:30] that is, i understand [18:44:53] The problem is that it's really, really hard to automate the tasks that a checkuser does when they're doing their job. [18:45:02] who is the second person talk after ori? [18:45:06] *talking [18:45:13] erik bernhardson [18:45:18] ah, k [18:45:22] thanks [18:45:39] James_F, right. Thanks. [18:46:32] marcoil: http://webpages.charter.net/allanms/popl84.pdf -- it was smalltalk-80, but it was the 1984 implementation of the language. so i was being 4 years too cruel. ;) [18:48:16] "stuck in the iframe" would be a great song title [18:48:37] ^ +1 [18:48:50] Question: when will we see HHVM in production? [18:48:58] cscott: '84 technologies are the far future in most programming practice :P [18:49:12] Stuck in the iframe - New single from the Wikimedia Foundation Engineering Team! :p [18:49:19] ragesoss: Being answered now, I think. [18:49:29] :) [18:49:36] James_F: Do you plan to work on adaptation of the VisualEditor for sister projects like Wikisource in the comming months? [18:49:57] I figured I take a guess and what might not get answered, in case it didn't get answered by the time the video caught up with the office. [18:50:07] Tpt: Not immediately, but it's something we're interested in, of course. [18:50:34] James_F: Ok. I'll be pleased to help for Wikisource [18:50:39] Tpt: So far we're deployed on Wikibooks, Wiktionary, Wikimedia (chapter) and Wikiversity wikis without needing any changes. [18:50:46] woot, scribunto. (meaning luasandbox, presumably?) [18:50:47] Questions about HHVM? [18:50:51] cscott: Yes. [18:51:56] Now a quick update about FDC. [18:51:57] hey, if you need more help porting luasandbox i could probably donate some of my Copious Free Time (tm). [18:52:21] cscott: I think Tim-away is mostly done with it, but… :-) [18:52:25] although i'm more likely to port the v8js extension ;) [18:53:21] James_F: if there was anything specific about an estimated timeframe of when HHVM might be ready to actually use in production, I missed it. [18:53:47] ragesoss: I know the answer. :) [18:53:57] is it secret? [18:53:58] ragesoss: Oh, sorry. Ori said (paraphrasing) "we don't know when it'll be ready; we have to get Lua and other things working first". [18:54:06] ragesoss: I.e. "No.". [18:54:19] cool, thanks. [18:54:19] ragesoss: https://www.mediawiki.org/wiki/HHVM [18:54:44] ragesoss: last i heard there were also some patches they were waiting to get merged upstream, and some packaging issues they were working with distro upstream on. [18:54:45] ragesoss: It's not known when it will be deployed. It's in the early stages. The big task right now is to get it so that you can use Beta Labs on either Zend or HHVM depending on a cookie in your browser. [18:55:00] ragesoss: Once that's done, it'll be easier for the team to estimate how long it will take to adapt HHVM for production. [18:55:02] ragesoss: so the timeframe is not entirely within wmf's control [18:55:27] thanks, all. that's super helpful. [18:56:19] The big selling point, imo, is that HHVM in general speed up on *all* actions for anyone who's logged in. [18:56:32] And also general speed up on anyone that edits, logged in or not. [18:59:46] And now to Sue. [19:01:30] got the squiggle off her face :-) [19:01:44] I have! [19:01:46] Yes! [19:01:52] I still see a squiggle. [19:01:55] Humph. [19:02:39] Can someone link to the page that Sue is referencing? [19:03:24] https://meta.wikimedia.org/wiki/Grants:APG/Proposals/2013-2014_round2/Wikimedia_Foundation/Proposal_form#Basic_information [19:03:51] (I still see it, too) [19:04:00] https://meta.wikimedia.org/wiki/Grants:APG/Proposals/2013-2014_round2/Wikimedia_Foundation/Proposal_form [19:05:40] Thanks Poore5 [19:09:33] Here is the talk page of the WMF annual plan proposal. Some good questions and answers already. But I'm interested in hearing more comments and questions. [19:09:39] https://meta.wikimedia.org/wiki/Grants_talk:APG/Proposals/2013-2014_round2/Wikimedia_Foundation/Proposal_form [19:11:03] wow, bradon eich resigned [19:11:25] brendan eich [19:12:52] What?! [19:13:58] https://blog.mozilla.org/blog/2014/04/03/brendan-eich-steps-down-as-mozilla-ceo/ [19:14:10] oh wow [19:14:29] :| [19:15:14] had to happen, while I personally have been doing a "I just can't get worked up, he lost his battle and I can't hold a grudge that long" thing their board HAD to know this would be an issue (or didn't do it's due diligence) :-/ [19:15:57] clearly the solution is for us to do more blackouts [19:16:12] jamesofur, ref to battle you're referring to? [19:16:40] halfak: Him donating money to anti gay marriage (and specifically Prop 8) causes [19:16:49] lame [19:16:55] thanks [19:17:16] hey, focus on the presentation ;) [19:17:32] * halfak snaps to attention [19:19:06] * James_F grins. [19:19:14] I'm surprised he lasted this long. [19:19:18] (But yes, focus.) [19:19:41] * mwalker is gobsmacked... where in the heck are we going to get the money for 40 additional staff members [19:19:52] bitcoin !!!11 [19:20:11] dogecoin [19:20:13] you mean [19:20:14] We're going to start mining it with our /extra servers/ [19:20:24] :) [19:20:33] yeah, we are going to mine something like 0.00001 in 10 days :-) [19:20:48] we will put it in our app [19:20:52] and mine off all our users [19:21:05] That's what pmtpa will be used for now. [19:21:40] I like YuviPanda's idea. The community will love it even more! [19:21:46] akosiaris: Just need to find people to work for 0.000009125 :p [19:21:59] also nicely pocket warming [19:22:12] indeed. [19:22:17] MIC! [19:22:25] :( [19:23:12] Decrease on desktop, increase on mobile? Interesting.. [19:24:41] have we considered ideas for cooperating with the more outreach type projects that seem to generate a lot of visibility ? [19:25:07] dangerious to mix fun with 'getting money' perhaps, but is less web and more real world on the map ? [19:25:44] who went from 90 to 900? i missed the org quim mentioned [19:25:55] he didn't say [19:25:58] k [19:25:59] but... mozilla? [19:26:13] which technically, MoCo did, not MoFo [19:28:27] Thank you everyone. [19:28:37] Video will be posted to Commons soon. [19:29:02] thanks! [19:29:11] thanks! [19:29:16] James_F: points to sue for those last comments [19:43:27] Attention y'all: The free software advocacy group will be hosting another meeting in here in about 15 minutes [19:43:55] I failed to schedule it, but luckily nobody else is using this time slot [20:00:06] #startmeeting WMF FSAG meeting #2 [20:00:06] Meeting started Thu Apr 3 20:00:06 2014 UTC and is due to finish in 60 minutes. The chair is marktraceur. Information about MeetBot at http://wiki.debian.org/MeetBot. [20:00:06] Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. [20:00:06] The meeting name has been set to 'wmf_fsag_meeting__2' [20:00:14] #link https://office.wikimedia.org/wiki/Free_software_advocacy_group [20:00:21] #link https://office.wikimedia.org/wiki/Free_software_advocacy_group/Meetings/2014-04-03 [20:00:26] #link http://etherpad.wikimedia.org/p/fsag-2014-04-03 [20:00:50] Good afternoon everyone, and welcome to the "wow we're still around" meeting of the WMF Free Software Advocacy Group [20:01:23] I'd like to briefly mention our agenda for the day, which includes a follow-up on videoconf software, a first look at document collaboration, and then some chat about training sessiosn. [20:01:25] * greg-g waves [20:01:27] sessions, even. [20:01:46] I'm your host today, greg-g is my lovely assistant as ever [20:01:51] * greg-g bows [20:01:55] Let's jump in. [20:02:00] #topic Video conferencing [20:02:11] #link https://office.wikimedia.org/wiki/Free_software_advocacy_group/Video_conferencing [20:02:26] Video conferencing was the bulk of our meeting last time, so I'm not going to spend as much time on it today [20:02:47] I did find out a few things about JitMeet, even going so far as to meet up with the person who suggested it to us in Boston [20:03:17] But, as far as I can tell, we're still at roughly the same place with it. [20:03:29] yeah :/ [20:03:47] I would sort of like to experiment with it very briefly to make sure the Etherpads are working now - the guy I talked to seemed to think they would now [20:03:52] #action greg-g to add column on requirements table re scalability [20:04:00] can you #action that, marktraceur [20:04:12] #action greg-g to add column on requirements table re scalability [20:04:36] * greg-g can experiment [20:04:44] Oh, wow, they changed it [20:04:52] And that means it's broken. [20:04:55] hah [20:05:15] So, we'll table that for now. [20:05:24] Chromium isn't supported by Chrome is? [20:05:25] #action marktraceur to make sure that jitmeet's etherpads are working now [20:05:25] wtf [20:05:33] greg-g: I have not had that experience [20:05:38] oh, bad copy/paste [20:05:42] #info jitmeet is down for now for some reason [20:05:51] Next up, BBB [20:06:09] I asked them about WebRTC implementation, and they seem to be going VERRRRRRRRRRRRRY SLOOOOOOOOOOOOWLY. [20:06:10] it works for me [20:06:23] greg-g: Can you link to the meeting? [20:06:30] https://meet.jit.si/uv8ptdbiewylow29 [20:07:07] "Failed to get access to local media." weird [20:07:18] huh [20:07:24] I see myself [20:07:30] Might be my system. [20:07:35] and the etherpad [20:07:47] #info greg-g was able to connect to JitMeet but marktraceur's system gave him errors. [20:07:58] #info BBB WebRTC implementation is coming along too slowly [20:08:44] Next I want to talk about a new option that we haven't gotten to work yet. [20:08:54] Echoplexus. [20:08:55] I got the direct url out of the source: https://etherpad.jitsi.net:9001/p/6ma8pgjsjor_1396555557773 [20:08:58] #link https://chat.echoplex.us/wikimedia [20:09:38] #info marktraceur confirms that something's funky about his camera setup [20:09:58] greg-g, others - if you are able to get video/audio working in echoplexus, that would be useful information. [20:10:05] in echoplex I get [20:10:06] I suspect you won't be able to, though, as we weren't before. [20:10:17] WebRTC failed! [20:10:18] Could not connect to stream [20:10:25] Argh. [20:10:25] wbrtc failed to connect.. [20:10:47] Well, it's an interesting solution because it also has text chat, doodling, and a JSBin equivalent [20:11:19] #action marktraceur to file bugs about video/audio support in echoplexus, or echo support for existing ones [20:11:29] Pgp encryption on the fly is kinda cool [20:11:40] yeah [20:11:42] #info pgp support in echoplexus makes csteipp happy [20:12:18] Now, unless there's something we missed in any of those options, or if someone else has a solution we haven't tried, I'd like to breeze right along to the next item on our list [20:12:35] (I've conspicuously failed to mention chatb.org because I think we've decided it's not worth our time right now) [20:12:52] * greg-g nods [20:13:50] #topic Collaborative document editing [20:13:58] #link https://office.wikimedia.org/wiki/Free_software_advocacy_group/Documents [20:14:27] I think we don't have too much to demo here, everyone is familiar with https://etherpad.wikimedia.org [20:14:34] I agree with Luis that Etherpad won't work for many of the situations [20:15:15] I'm pretty sure there's an export function [20:15:50] But otherwise, yes, there are issues. [20:15:51] yeah, but the lack of annotations and ACL is pretty much a show stopper [20:16:02] annotations/comments [20:16:08] #action marktraceur to add a table to this page like the one on the VC page [20:16:43] The other option I have listed is OwnCloud [20:16:53] #link http://demo.owncloud.org/index.php [20:17:23] If someone could join me in the documents section, in "New Document.odt", I'd like to test the collaboration features [20:17:35] * csteipp resists the p0wnCloud jokes... [20:17:42] http://demo.owncloud.org/index.php/apps/documents#40 specifically [20:18:35] Ooh, it works [20:18:38] Brilliant [20:18:46] I wasn't sure it was real-time [20:18:55] #info OwnCloud does have RTC [20:19:01] I don't get what the color highlighting is supposed to mean.. [20:19:16] I think that someone has the text selected [20:19:41] Ah. And the lines on the left are kinda who created the line? [20:19:45] ish [20:19:49] last edited really [20:19:50] It's a bit slow, but I'm willing to chalk that up to "demo server" for now [20:20:00] We could maybe look into dumping it on a labs instance [20:20:02] no annotations nor chat [20:20:10] greg-g: True. [20:20:19] I assume ACL because owncloud has acls [20:20:22] but can't confirm [20:20:34] hum, unresponsive? [20:20:48] sidenote: after some quick searching, LibreOffice Online still seems to be in vaporware stages? [20:21:02] greg-g: Yeah, I couldn't find anything useful [20:21:07] * greg-g nods [20:21:12] #info LibreOffice's RTC methods are basically vaporware [20:21:30] #info OwnCloud lacks many features of Etherpad, buc has ACL [20:22:07] Doesn't etherpad have an authentication and private pad plugin? [20:22:14] But, apart from the two we've talked about, I'd like there to be more options [20:22:22] So if anyone knows of others, I'd love to add them to the list [20:22:30] (and the table when it is created) [20:22:44] csteipp: rhelmer of Mozilla was working on it, but it's vaporware too IIRC [20:22:53] They decided to build their own by hacking core last I checked [20:23:12] #action marktraceur to ask rhelmer whether EPL's private-pad/auth stuff is still active or if it's abandonware [20:23:50] #info we could use more options than EPL and OC. Anyone with information should add it to the officewiki page. [20:24:54] #info We could also use people adding requirements to the table and lists on the officewiki page [20:25:22] I noted on the etherpad for this meeting that I might like to send out a reminder email about Etherpad Lite, and encourage people to use it instead of Google Docs. [20:25:25] #link https://en.wikipedia.org/wiki/Collaborative_real-time_editor#List_of_current_editors [20:25:37] #chair greg-g [20:25:37] Current chairs: greg-g marktraceur [20:25:48] #link https://en.wikipedia.org/wiki/Collaborative_real-time_editor#List_of_current_editors [20:26:07] But I'm not sure if we have a sufficiently featureful instance for us to do so, because there are a lot of things missing from our requirements list. [20:26:17] Thoughts on that idea, anyone? [20:26:36] #link https://en.wikipedia.org/wiki/Kune_%28software%29 [20:27:03] the etherpad lite encouragement idea? sure [20:27:32] I don't know how people use it in non-engineering depts, but I feel like it has pretty good traction within engineering for meeting note taking [20:27:51] True [20:28:08] greg-g: I wonder if it's such good traction that people use it enough already that I don't need to remind them. [20:28:17] Hey all, have I reached the FSAG discussion? [20:28:23] sorry I'm late, just heard of this one. [20:28:23] cndiv: You have! [20:28:27] welcome sir [20:28:29] woo and hoooo [20:28:42] is this happening in a physical capacity as well? [20:28:46] no [20:28:59] cndiv: Naw, I'm at my desk, greg-g is in Pet a Llama, and csteipp is unknown [20:29:36] Basking in the glow of the google overlords [20:29:40] ok, I'll be right here then. [20:29:40] *nod* [20:30:24] Anyway, I think I'm going to leave things be for now re: EPL and move on to the next thing [20:30:28] Uhhh but first [20:30:33] cndiv: do you know of any other collaborative document editing thingys other than etherpad or OwnCloud? [20:30:46] (that are floss, of course ;) ) [20:30:54] #action someone maybe push things from https://en.wikipedia.org/wiki/Collaborative_real-time_editor#List_of_current_editors to https://office.wikimedia.org/wiki/Free_software_advocacy_group/Documents#Solutions [20:31:16] #action * greg-g can [20:31:23] * greg-g wonders if that'll indent correctly [20:31:32] One more, but I haven't used it. The Apache docofficeorsomething. [20:31:36] Know what I'm talking about? [20:31:39] Let me look that up. [20:31:44] Uhhh...Wave? [20:31:52] (is that a troll now or has it been long enough?) [20:32:24] marktraceur: I don't think it's related to wave. [20:32:26] * greg-g turns off hovercards, totally gets in the way for me [20:33:12] cndiv: I think adding it and investigating can happen asynchronously, if you'd be so kind as to add it to the page, we can come back to it next time. [20:33:32] I'd like to move on if there's nothing else pressing, as it sounds like we are still in the first stages of this investigation [20:33:32] will do [20:33:42] #topic Training sessions [20:33:52] #link https://office.wikimedia.org/wiki/Free_software_advocacy_group [20:33:56] Fail. [20:34:07] #link https://office.wikimedia.org/wiki/Free_software_advocacy_group#Training [20:34:32] cross Bugzilla off that list :P [20:34:42] This was a sort of last-minute addition to our purview, but I think it would be a nice thing to accomplish in the coming month or so [20:34:58] greg-g: Done [20:35:25] I think cndiv successfully-ish led an IRC training session a while back [20:35:48] yeah, it went OK. Lynette and I are actually planning on trying again. [20:35:50] I think holding a MediaWiki session might be a good first step for this group, because it's a system we know really well and don't use as often as we should [20:36:08] Basically it took too long for people to type things, so I'm doing it again with copy/paste methods [20:36:08] I thought that was funny, but you're right [20:36:16] (re MW) [20:36:49] greg-g: It would be interesting to lead a session focused on the functions that people could use but often don't, e.g. special:upload [20:36:50] greg-g: Yeah, it's a big problem, actually. I have folks mention it to me all the time. [20:37:00] * qgil_ asks: how to propose a topic for a next meeting, or to be discussed? [20:37:01] It's better now with VE [20:37:05] Talk pages, too, etc. [20:37:21] qgil_: We'll talk about the next meeting in about 10 minutes, we can raise it then :) [20:37:22] but things like "how do I start a discussion on-wiki that actually attracts attention?" are unknown even to me. [20:37:38] cndiv: Yeah, that's sort of a social problem [20:37:44] yeah [20:37:46] But maybe the CLs could help us with that [20:37:52] CLs? [20:38:02] Community liasons [20:38:16] not a MW training problem, but a "everyone needs to be better about using MW/officewiki in general" problem, which brings us back to the MW trainings on MW features [20:38:22] Yeah. [20:38:44] You'll probably disagree with me but I think it's more of a software than a social problem. People start Loomio discussions and get lots of responses, but that's (IMO) because of things like email alerts and a more straightforward interface. [20:39:03] cndiv: Which is why Flow is around, I suppose [20:39:04] Talk pages, watchlists, and typing colons to respond to people are just totally unfamiliar to our non-tech staff. [20:39:04] also just new hautness [20:39:13] marktraceur: Yeah, I'm looking forward to Flow. [20:39:14] There are other people who are available and willing to do MediaWiki training, such as me. :) [20:39:53] Deskana: Yeah, I think we'll have a few people interested [20:40:02] What about starting with just a mediawiki markup cheet sheet? [20:40:03] also mailing lists. I was surprised at finding people who didn't know we had lists.wikimedia.org... [20:40:14] table: Have we done the "review our use of Loomio after a while" review? if we'll bring it in house or not [20:40:17] * marktraceur notes this on list [20:40:32] greg-g: I think the idea is that Loomio is the stop-gap until Flow is flowing. [20:40:34] * greg-g grumbles about google alias [20:40:57] greg-g: and the developers tell me a priority of theirs in the next year is making Loomio much easier to host yourself. [20:41:21] cndiv: awesome [20:41:37] OK, so [20:42:02] I think priority number one should be giving people the power to affect discussions on wiki [20:42:07] and honestly I think the Flow team might learn a bit more about what they need to build / how well it will work from using Loomio in the meantime. [20:42:18] Because that will include officewiki, mediawiki.org, en.wikipedia, and more [20:42:27] marktraceur: by affect you mean just how to use it? [20:42:35] And giving people power to use MediaWiki will also give them the power to teach and the power to contribute to projects [20:42:38] cndiv: Yeah [20:43:07] marktraceur: Yep, I'm with you there. [20:43:27] Deskana: Latching on to you volunteering here - would you mind emcee-ing the MediaWiki training thing if I found you a few helpers to teach things alongside you? [20:43:35] I'd also happily announce/coordinate again. [20:43:47] marktraceur: Sure. [20:43:50] Sweet. [20:44:09] #action marktraceur to announce mediawiki training session sometime in the next month, Deskana to teach, marktraceur to help teach and recruit teachers [20:44:28] Found that Apache thing. Not a doc editor, it's a conferencing tool: http://openmeetings.apache.org/ [20:44:31] YuviPanda: If I also wanted to plan a mailing list thing for slightly further out, would you mind helping with that? [20:44:31] I'll add it to the list [20:44:32] Just so we're clear, the remit here is specifically MediaWiki and things like wikitext? [20:44:41] Subpages, etc. [20:44:54] Not WMF-specific stuff? [20:44:55] Deskana: Yes, wikitext, talk pages, sub pages, wikilinks (as opposed to external), uploading files [20:44:59] Etc. etc. [20:45:08] Great. We're on the same page then. :) [20:45:22] Righto [20:45:40] I'm going to rush us out of this topic and switch to next-meeting planning, because it sounds like we've got plenty of work to do already [20:45:44] #topic Next meeting [20:45:46] marktraceur: before you do [20:45:49] Agh! [20:45:54] haha hold on :-) [20:46:00] cndiv: It's OK, I can read confusing minutes. What's up? [20:46:05] marktraceur: depends on what help you need :) (I've never done mailman admin stuff, but can help with moderation + just being active) [20:46:14] 'kay, noted YuviPanda [20:46:27] #info YuviPanda would be interested in a mailman tutorial to some extent [20:46:49] I think it's important that we not only tell people the logitics of how to use MW, but how they can actually apply it to their work. For example, Lynette works really hard to document a lot of things she does on Wiki, and asks for comments, but rarely ever gets anything. [20:47:08] The first question she'd have, which I think is a good one, is "how do I foster input and discussion?" [20:47:12] not just how to edit. [20:47:21] ... and I actually don't know the answer to that. [20:47:31] besides "pester people via email to contribute" [20:47:35] getting more people comfortable with using mw, probably [20:47:40] cndiv: Apart from the technical skills surrounding talk pages and onwiki discussion, I think it remains a social problem :0 [20:47:45] :) even [20:47:46] the other side of the equation is the one you want to modify [20:47:57] The mailing list session might be interesting for answering that question though [20:48:00] Anyway [20:48:01] are the rest of you in agreement it's a social, not software problem? [20:48:17] cndiv: I think that's a mischaractization of at least my opinion [20:48:17] qgil_: You had a proposal for the next meeting, I hear [20:48:18] In my work on the conference rooms, I had much more success getting input *with paper taped to the door* than on-wiki. [20:48:27] yes [20:48:40] I want to discuss this idea for WMF employees: [20:48:52] cndiv: getting people more comfortable with using MW (a technical problem) will help solve the social problem of getting more responses better than any nagging or formatting lynette could ever do [20:48:53] IF apple.Laptop is more expensive than linux.Laptop (acquisition, extra software, updates, accessories, lifetime...) [20:49:11] THEN WMF should default to linux.Laptop, and request a reasoning for employees willing something different, and manager approval [20:49:22] greg-g: OK, interested to see the lesson then. [20:49:33] also IF an apple.Laptop owner would _upgrade_ to a linux.Laptop after its end of life [20:49:34] qgil_: So, there's a question of scope for this group that I've bent over backwards to keep very narrow [20:49:34] cndiv: also, comparing to conf room work is kinda not apples to apples because people don't want to go to a wiki page when they're fumbling around with a microphone/login thing [20:49:58] THEN the employee would get a voucher valued in the difference of price / 2 (half for you, half for the WMF) [20:50:05] how does this sound? [20:50:08] greg-g: it wasn't just technical, it was things like 'how should this room be arranged?' or 'what furniture would you like?' [20:50:29] cndiv: same [20:50:30] qgil_: I think asking people to rationalize their choices is wildly out of scope, especially based on the mailing list discussions that led to us being here [20:50:40] no one has time to login to a wiki to give those opinions quickly :) [20:51:08] ok, fair enough, I can discuss this with those who have to give laptops to employees, and those who care about costs [20:51:19] Well, cndiv would be that person largely, I think :) [20:51:23] qgil_: I hate to be a wet blanket, but.. at the moment, Apple stuff is actually *cheaper* than our linux default. Not to mention the support time difference. [20:51:53] cndiv, ok, then even better, considering that my proposal started with an IF :) [20:52:11] I would suggest instead having us focus on making the X1 Carbon Thinkpad (the current default) super-awesome. [20:52:16] stuff like trackapd drivers. [20:52:22] those drive me batty. [20:52:41] qgil_: We'd like to pursue that conversation at a later date, maybe, but right now there are simpler ways to effect change than operating system defaults. [20:53:01] ok, understood, I feel better now that I took this out of my brain :) [20:53:21] 'kay. [20:53:21] Now, scheduling [20:53:25] In two weeks it will be April 17th [20:53:34] This has the benefit of not having a metrics meeting in the works [20:53:55] 12:00 on 2014-04-17 works for me, does it work for other people? [20:55:21] * marktraceur runs an IRC training session for qgil_. :) [20:55:21] wfm [20:55:23] I'm just looking for excuses to talk to you directly marktraceur (and I always fail) :P [20:56:21] wfm2 [20:56:21] marktraceur: That date/time works for me. [20:56:21] * marktraceur nods, understandable [20:56:21] All right, I see only positive notes, so [20:56:28] marktraceur: can you send an invite? (honest question, I don't know if you use google calendar) [20:56:34] #action marktraceur better schedule dat meeting for 2014-04-17 at 12:00 PDT [20:56:43] qgil_, I bought system76 laptops twice in succession ... and it is kind of a mixed bag .. i currently am using one. the good thing is that stuff mostly worked, but the hardware is bulky. i joke around that my badminton smash has improved as a result. [20:56:46] cndiv: I will do so, though my frustration with the status quo abounds. :) [20:56:54] Oh, also [20:56:55] marktraceur: that I assumed :-) [20:57:01] #action marktraceur to explore mailing list for FSAG [20:57:13] We may want a better acronym before sticking it on the mailing list page though [20:57:20] Unless we're stuck with it now [20:57:26] subbu, cndiv gave a sleek Dell XPS in 2012, still fit. [20:57:28] please god no [20:57:47] greg-g: Oh? [20:57:50] (re FSAG) [20:57:55] Ah. [20:58:02] I'm taking suggestions. :) [20:58:09] qgil_: Hope you're still enjoying it. In general I'm *very* open to giving Linux users what they really want. Supporting it is a different story. [20:58:27] II would call it FSFS, just because we can. [20:58:28] marktraceur, are acronyms required? [20:58:41] subbu: Guess not, just thinking of my carpal tunnel [20:58:43] FreedomWiki, WikiFreedom, WikiFree, FreeAsInWiki (FAIW) [20:58:59] Faiw Whaiw [20:59:18] * greg-g has to run, has a call with the GC of CC [20:59:25] greg-g: This may not mesh with some of my longer-term plans, but we'll talk about it later. [20:59:30] kk [20:59:33] For now I'll just not abbreviate it. [20:59:38] All right, good meeting. [20:59:44] thanks! [20:59:48] tah tah! [20:59:48] greg-g: by those acronyms I take it you envision this group as one concerning FREE software, not just Open-Source software? [20:59:53] If there are more conversatings that need to happen, use the wiki! :) [20:59:53] I'm just clarifying. [20:59:58] (I was 16 minutes late, but 44 minutes before last time) [21:00:06] cndiv: They're roughly equivalent [21:00:15] cndiv: FLOSS is already too long of an acronym :) [21:00:26] marktraceur: Oh I know. I'm just wondering where your heads are at. [21:00:43] i like floss as a term. [21:00:47] I don't think anyone is GPL/AGPL only here [21:01:01] * marktraceur is sort of that way for personal projects [21:01:13] you know what I mean [21:01:13] #endmeeting [21:01:13] Meeting ended Thu Apr 3 21:01:13 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) [21:01:13] Minutes: https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-04-03-20.00.html [21:01:13] Minutes (text): https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-04-03-20.00.txt [21:01:13] Minutes (wiki): https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-04-03-20.00.wiki [21:01:14] Log: https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-04-03-20.00.log.html [21:01:16] Lol robla needs me now [21:01:17] BBL [21:01:19] for the WMF [21:02:17] (tah tah)