359:
the scenes of
Knowledge (XXG), or about a particular editor whose nefariousness has really rubbed them the wrong way, but whom the rest of humanity really couldn't care less about. While those grievances may be fully justified, presenting them in a way that it becomes something the ordinary person in the street will care about is often impossible and always hard. It really means divesting oneself from any vestiges of the Knowledge (XXG) mindset, and looking at the big picture, with outsider's eyes. If it's all the same to the casual Knowledge (XXG) reader, it doesn't matter.
321:<plipp> Well, I mean for example things like the pawn symbol insertions and not being able to handle various templates. Those are things that authentic experienced editors would see but UsabilityRUs testers off the street would never catch on to. if you are releasing a new smartphone app, it makes sense to do usability testing with people off the street <gnubeard> are we releasing a new smartfone app? :)
252:<jorm> We have several types of usability tests. some use 3rd parties. we have a stack of tests and reports that were done at wikimania with "real editors". though, when testing usability, that doesn't mean much. either the software is usable or it is not. if it is only "usable" to a select group of people - people who are trained in it, perhaps - then it is not "usable" software. it's esoteric.
314:<gnubeard> Eloquence: That's exactly right. My experience with the Gecko layout engine, and building that team, the edge cases are mind blowing. 70 languages, hundreds of styles and elements, all different on all browsers, now make it all come together and look the same everywhere??! really really hard. Big big brains have to tackle that problem. way bigger than mine. (think
374:
battle in which the WMF really are fighting for themselves and their own salaries, because large portions of the unpaid volunteer community don't actually care whether readers read their content on wikipedia.org or elsewhere. They believe and signed up to the idea that reuse by others – commercial or non-commercial – is not just fine, but actually what the whole project is about.
339:<Eloquence> plipp, fortunately we have plenty of willing beta testers, too, who do lots of reporting of edge cases. but we stretch people's patience when we push things out too quickly, as we did with VE. we need to take our time to get the complex projects (VE/Flow) right. that's why I'm OK slowing down the deployment targets on these.
373:
3. If anyone still doubted it, it is now more clear than ever from Damon's comments that the WMF fears that their page views will be stolen by re-users of their content who produce a more visually appealing and up-to-date reader interface. (Jan-Bart's denial can be written off as bullshit.) This is a
354:
Well, here Damon may have a point. It's very difficult to put across criticism of the type we're trying to formulate here without coming across to the casual passer-by as angry, obsessed, nit-picking cranks. (Especially if there is a whiff of truth to that characterisation, from a complete outsider's
154:
A: you are right to ask that, because I am drawing on comparisons with other big corporate projects... What I want to see is a better connection between those in WMF who are making product changes (which can be anyone, really) and see how they are prioritizing. If those prioritizations do not include
149:
Q (from pajz): Many of the goals you mention are, I feel, "relative" in the sense that you are drawing up a comparison with (other) big players on the internet. However, a
Knowledge (XXG) article is written by volunteer authors — it is not the result of an algorithm. How do you want to make sure that
399:
I think the major point of controversy between the WMF and the community nowadays is that at least the German editors usually do not contribute to
Knowledge (XXG) because it is a 'top-5 website'. We are not at all interested in that. We are only interested in quality, not something like the Alexa or
395:
Damon did not respond to that. Indeed, unfortunately he left the channel even without saying goodbye properly. However, Damon referred to an earlier remark of mine. I then elaborated on my impression of the IRC hour and left the channel because it was 11 p.m. local time. The term 'kidding' referred
158:
What if no mobile app store anywhere contained any application to see
Knowledge (XXG)? Make no mistake: They are figuring out how to do that. I've been in the conversations! An example: The day Steve Jobs died I was in a meeting with Andy Rubin, yes Andy Rubin, and he rejected allowing Firefox as a
358:
And sometimes, even in criticising
Knowledge (XXG), a good few people here think like Wikipedians (and that is, well, because a fair number are, or have been, Wikipedians), yelling for example about unfairly applied Knowledge (XXG) rules that mean diddly-squat to anyone who has never looked behind
172:
Q (from aschmidt): Over the past hour i have read a lot of kidding by the way, i have read a lot about
Mozilla as it was, but nothing has really touched the questions that matter to the community. Sorry to say that. Not even the serious question asked by pajz has been addressed adequately. We have
249:<Eloquence> We've done limited user testing for years, and the first formal user studies in labs many years ago. but we started building a proper in-house UX research team a few months ago and are now doing more and more testing directly in partnership with product teams on an ongoing basis
71:
Also, our talent base here is fantastic. However, the question I'm left asking: How are we going to build the sum of all knowledge with only seven engineers (not an actual number, but not off by an order, fer sure)? Seven mobile engineers? Not enough. it took me 150 engineers to build
Firefox for
112:
I want everyone to keep this in mind: If we don't move faster and better than google, apple, and microsoft (and their ilk and kin), they will consume us and we will go away. It's that simple. So, that means our engineering processes must be as efficient as possible. We must measure and move with
390:
Over the past hour I have read a lot of kidding by the way, I have read a lot about
Mozilla as it was, but nothing has really touched the questions that matter to the community. Sorry to say that. Not even the serious question asked by pajz has been addressed adequately. We have read and edited
369:
2. Their VP of
Engineering feels they don't have enough staff – and not enough top talent. No argument from this site on the latter assertion at least; as for the former one, one might agree with it if these hordes of talented engineers were to produce at some point in the future something that
75:
I see us having to scale to a size that enables us to compete with the engineering shops that are trying to kill us. That means we need to double down on recruiting top talent, and steal the engineers from the sources they use... because... well... they are REALLY GOOD.
139:
I'm not saying it should or shouldn't be relative, but the quality of the posts is similar to other sites that attempt to do what they do. Many have come and gone on my watch at
Mozilla. Nothing ever comes of them if you build the right product and keep your promises.
324:<plipp> no, no, just an example of when an outside agency would make sense. an outside agency would still make sense if they have access to authentic experienced editors, but as I understand those companies they pride themselves on the naivety of their testers
135:
On Wikipediocracy: and, well, this may hurt a little, but the writing there is amateur and abrasive. Not something that I would enjoy reading. And also, the arguments are so specific to WMF and attacking individuals that I don't think it will be relevant long term.
27:
84:
A: Any company that wants to sell knowledge. For example, I find it ironic that the WMF office is over Kaplan. I believe Kaplan is trying to kill us. They want to take over the schools because they sell educational content. and we are their biggest threat.
277:
For example, with FirefoxOS, we sent an ARMY of people to the regions where we *suspected* we would launch, years in advance, in order to do testing on the ground *first*... Get the users requirements *first* from them... *in person* by going house to
116:
Right now, we're number one because the big players in the space (all the ones I mentioned) still respect us. They believe in us. But, if we ship shitty software, that won't last very long, or if we *don't change* we will last an even shorter time.
336:<plipp> I think it would much more likely lead to editor community harmony! The only thing dying would be the hordes of angry editors with torches and pitchforks. And they wouldn't die, they would transform into enthusiastic supporters.
290:<gnubeard> Eloquence: yep. it's hard. And the usability aspects I'm talking about... aren't down to pixel perfect.. you can't do that upfront. pixel perfect takes rigor. crazy rigor. And the iPhone has subpixels. So, it's twice as hard.
365:
1. WMF consider themselves a technology and grantmaking operation (okay, this was clearly known to many people before, but I hadn't seen it stated as definitely as Erik Möller stated it the other day). I wonder how clear it is to the public.
183:
if we can't adapt to the market environment fast enough, we won't have users who are interested in us. sure, we've been around for a while. But make no mistake, software rots. How many desktop apps do you use that are ten or more years old?
97:
Q: (from harej): What is the difference between Engineering and Product, now that they are two separate departments? It sounds like "Engineering" is focusing on software stuff, but I thought that would be Product, since our main product is
102:
A: Product's job is to guarantee we are building the right products. Guarantee means a lot of things, but it means, specifically that they must tell us when we are winning and why. Product should be in the seat next to engineers.
385:
I just would like to add that my statement before I left the channel was not cited in the logfile in full. I do not know whether my Adium truncated the line, so I would like to quote it in full according to my log. It read:
162:
So, on hiring, I don't see how we are going to build the sum of all knowledge with what we have now. I don't think it's just about writing an encyclopedia. It's about making sure somone can READ and EDIT the encyclopedia.
311:<Eloquence> plipp, a problem with VE is that it has to deal with millions of articles and edge cases. usability testing works typically with smaller samples of users, so you'll only discover some edge cases
400:
the Google rank of the website. It is a feature of nonprofit organisations that such things do not matter. As long as the WMF does not understand this we won't get along. —Aschmidt 11:55 am, 10/10/14 (UTC−7)
370:
actually is awesome, to use that beloved word. So expect the donations drive to continue, and several hundred software engineers to be added to the employee roster if there is enough money to pay for them.
67:
A: The most urgent issue seems to be software quality and shipping what we say we are going to ship, on time. However, this urgency is compounded by the fact that we must be able to compete in mobile.
126:
Q (from Seth_Finkelstein): Have you read the site wikipediocracy.com? If so, what do you think of it? In general, how do you plan to deal with the sometimes very harsh criticism leveled at WMF actions?
396:
to the somewhat chaotic course of the hour which was rather hard to follow for non-native English speakers, as Ziko also had pointed out at some point. I did not mean to say that Damon was kidding.
302:
usability errors aren't the problem with VE. It's fatally flawed as it is now. I still think it's the right product, just not even to the point where we're really talking about usablility problems.
63:
Q (from ori): Now that you've had a chance to get acquainted with the Foundation, what problems seem most urgent to you, and do you have any early thoughts about how you're planning to tackle them?
214:
Q (from marxarelli): How do you plan to keep our development goals congruent with our stated product goals and, perhaps more importantly, our product goals congruent with what our community wants?
150:
your engineerings team's strive for more efficiency and prompter implementation will not alienate people contributing content who are often rather skeptical of significant changes to the site?
109:
But, again, the biggest challenge will be how do we innovate in mobile. We have to be where our users are, and we don't have a place for our mobile users to go yet. and we can't get to them.
38:
Interview with new Wikimedia Foundation VP of Engineering Damon Sicore ("gnubeard"), via IRC on October 9, 2014. Edited and posted to Wikipediocracy by WPO user "Thracia" on October 10.
265:... y-testing/ style tests using actual editors. instead of maybe just some third party agency grabbing people off the street and pretending they are equivalent to experienced editors
391:
wikipedia since 2001. This hour was about what the WMF intends to change or not, and I'm afraid we have not heard anything consistent and new in this respect. Good night to you all.
293:<plipp> I'm wondering if anyone can think about problems with VE that wouldn't have been caught with formal usability tests using authentic experienced editors
221:
As for the community goals, I need to understand our touchpoints with the community now. When I ask these questions here, I don't get the answers I'm looking for.
106:
And, really, while there is a org split between the two, they should be interacting constantly. Engineering will be focused on ops, processes, testing, quality.
246:<plipp> I saw in the logs that someone says the Foundation contracts usability testing with an outside agency, but I wonder whether they use real editors
355:
perspective.) And I think he's right that this is a problem many criticism blogs struggle with, and that keeps them marginalised. Too much inside baseball.
53:"As usual, a lot of the content is noises off from unfunny idiots, but I've tried to sift out a few interesting answers (apologies if I've sifted badly)."
173:
read and edited wikipedia since 2001. This hour was about what the WMF intends to change or not, and I'm afraid we have not heard anything consistent an
132:
A: I've read wikipediocracy.com. Most of it. I can't imagine an executive joining WMF without reading it. I actually appreciate the fact that it exists.
193:
Q (from hasher): By mean of changing Software Quality, do you have any idea to share already? I am wondering how we could better work with our users.
230:
And to close, a bit of raw conversation involving Damon, Erik, Jorm and onlookers (slightly edited/reordered for noise/sense, my emphases) —Thracia
274:
Usability testing is super important. However, I think that getting the usability right before you build the product is a better way to do it.
382:
Thanks for summarising the IRC office hour and for re-posting the text here. The new page has been mentioned on German Knowledge (XXG).
258:<plipp> jorm: Usability isn't a binary thing. You can measure it as a continuum, for example as a floating point speedup factor
88:
We will be slowly absorbed behind other systems that present our information unless we build products that our users want to use.
287:<Eloquence> I've had some bad experiences w/ premature field research but agree it could be super valuable if done right
284:<gnubeard> Before we designed the phone, we extracted the intentions and activities out of the community first.
261:<plipp> It seems to me that most of the problems with VE and Media Viewer would likely have been caught with
197:
A: some projects in WMF don't have a no regression policy, for example. Some projects have little to no testing.
113:
intent. Measuring means efficacy of product changes as well as performance, perceived efficiency, and security.
205:
A: Right. If it isn't measured, it doesn't exist. (don't take that all the way... but you get what I mean).
177:
A: aschmidt seemed to think I was kidding. I'm serious about everything I said. In no way am I kidding.
46:
281:<Eloquence> gnubeard, really interested in learning more about how you scaled that stuff @ moz
237:<plipp> Did my question about formal usability get answered at the Engineering office hour?
180:
And, to repeat what I plan to change: Software Quality, shipping what we say we are going to ship.
155:
our constituents, then I know that we may be going in the wrong direction. almost certainly.
42:
218:
A: Dev goals congruent with product is easy. That just means we talk. That I can do.
26:
17:
268:<Eloquence> plipp, testing with different personas consistently helps, yes.
330:<plipp> beats me, but it's my suggestion and I'm sticking to it :)
243:<Eloquence> more of a product question really, so I can take that one
262:
255:<matanya> No one was born with the knowledge to edit a wiki jorm
201:
Q (from ottomata, Qcoder00): No regression policy? and thus no metrics?
362:
Some interesting news has come out of the past few days' discussions.
25:
72:
Android. And that was moving as fast as humanly possible.
30:
WMF VP Engineering Damon Sicore as he appeared in 2012.
315:
305:These are tablestakes problems (i.e., load time).
271:<gnubeard> I want to add a few points, too.
159:browser... we had to fight!!! That is our threat.
402:Moved here from talk. Edited for style by T.D.
350:A reply on WPO by Andreas Kolbe/HRIP7/Jayen466
333:<gnubeard> Even if it means our death?
8:
296:<Eloquence> heh :) yes, plenty
80:Q (from greg-g): Who's trying to kill us?
378:A note on the quotation of my statement
263:http://www.usabilityfirst.com/usability
7:
308:<matanya> load days you mean
24:
327:<gnubeard> Why aren't we?
1:
51:Editorial note by Thracia:
417:
346:‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡
342:‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡
299:<gnubeard> plipp:
240:<gnubeard> Nope.
393:
34:
388:
29:
316:http://dbaron.org/
35:
403:
33:
408:
401:
31:
416:
415:
411:
410:
409:
407:
406:
405:
380:
352:
234:
228:
225:xxxxxxxxxxxxxx
224:
212:
209:xxxxxxxxxxxxxx
208:
191:
188:xxxxxxxxxxxxxx
187:
170:
167:xxxxxxxxxxxxxx
166:
147:
144:xxxxxxxxxxxxxx
143:
124:
121:xxxxxxxxxxxxxx
120:
95:
92:xxxxxxxxxxxxxx
91:
61:
59:
57:
22:
21:
20:
12:
11:
5:
414:
412:
379:
376:
351:
348:
47:Labs text link
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
413:
404:
397:
392:
387:
383:
377:
375:
371:
367:
363:
360:
356:
349:
347:
345:
340:
337:
334:
331:
328:
325:
322:
319:
317:
312:
309:
306:
304:
303:
297:
294:
291:
288:
285:
282:
279:
276:
275:
269:
266:
264:
259:
256:
253:
250:
247:
244:
241:
238:
235:
232:
231:
226:
222:
219:
216:
215:
210:
206:
203:
202:
198:
195:
194:
189:
185:
181:
178:
175:
174:
168:
164:
160:
156:
152:
151:
145:
141:
137:
133:
130:
128:
127:
122:
118:
114:
110:
107:
104:
100:
99:
93:
89:
86:
82:
81:
77:
73:
69:
65:
64:
58:
55:
54:
49:
48:
44:
40:
39:
28:
19:
398:
394:
389:
384:
381:
372:
368:
364:
361:
357:
353:
343:
341:
338:
335:
332:
329:
326:
323:
320:
313:
310:
307:
301:
300:
298:
295:
292:
289:
286:
283:
280:
273:
272:
270:
267:
260:
257:
254:
251:
248:
245:
242:
239:
236:
233:
229:
227:
223:
220:
217:
213:
211:
207:
204:
200:
199:
196:
192:
190:
186:
182:
179:
176:
171:
169:
165:
161:
157:
153:
148:
146:
142:
138:
134:
131:
129:
125:
123:
119:
115:
111:
108:
105:
101:
96:
94:
90:
87:
83:
79:
78:
74:
70:
66:
62:
60:
56:
52:
50:
41:
37:
36:
18:User:Carrite
98:MediaWiki?
32:(Commons.)
43:Meta link
344:E N D
16:<
45:|||
318:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
