129:
important, but equally important are visual and interaction design best-practices, user experience research, product strategy, quality assurance testing, and data analysis. Staffers will be expected to treat community members as an equal partner on the Flow team and will actively solicit their feedback on design and development ideas. But they won't be under an obligation respond to actively uncivil or bad-faith comments. Users who do not not share the view that discussion on
Knowledge (XXG) can or should be made more accessible to everyone are still free to participate in discussions about Flow, but their feedback will not inform the development process.
149:, who will be invited to test out an early Flow prototype and give feedback. In this session, we will be testing for UI/UX best-practices and newbie friendliness. The second will be an office hours session in #wikimedia-office and will be open to anyone from the editing community who wants to attend. The goal will be to get experienced user feedback on the latest design iterations and workflows, ask some questions, and get a general idea of where sticking points are likely to be, so we can figure out what needs to be addressed before the sandbox release. The outcome of both discussions will be documented and shared.
175:
this process to generate new ideas, challenge assumptions, and raise critical issues that we must fix: that's what the process is there for. As outlined in the ground rules above, anyone is free to comment on our work, but in order for community feedback to be incorporated into the next release, it must come with a rationale for how it will make discussion on
Knowledge (XXG) faster, easier, and better.
31:
199:. We expect this trial period to generate a discussion, and we will make changes to Flow based on that discussion. Documentation will also be added to the Flow talkpage, making transparent the behavioural guidelines we'll be adhering to, and the behavioural guidelines we expect users to adhere to in return.
178:
At the end of this process, we'll discuss with community members whether the first release of Flow is ready to be piloted on a WikiProject discussion space, or whether there are still outstanding issues that need to be fixed before it goes live. Ultimately, it'll be up to WikiProject members to make
174:
will be put on a test wiki (ee-flow.wmflabs.org). Anyone is welcome to test it out and give feedback, though we will personally invite a moderately-sized group of users – those who are actively involved in a WikiProject and/or have expressed interest in collaborating with us on Flow. We fully expect
152:
In addition to these more structured sessions, the Flow team will participate in discussions on the Flow portal talk page and sporadically solicit user feedback on design and feature ideas. Anyone interested in talking with us should follow the Flow portal main page and talk page, or come find us in
128:
For this collaboration to be successful, both the Flow team and the community must commit to a shared set of goals and engage in an open, good-faith dialog about how their ideas further those goals. Neither WMF staff nor the community alone can build a great software product – community knowledge is
107:
Community members (both those who are the target audience of a release and the wider community in general) will be invited to participate in the development process throughout the release cycle: before we release anything to
Knowledge (XXG), and after the first and subsequent releases. Nothing will
103:
The Flow team will deploy slowly and incrementally – on a page-by-page basis at first, and only with the consensus of those using the pages – and will target smaller subsets of the community (WikiProjects) for both release and feedback. This will make it easier to have a focused conversation on the
65:
In the past, we have spent too much time in conflict and not enough in collaboration. When staff and the community fail to work together, we don't just foster hostility and grudges; we all waste time, energy, and resources that could have been better spent improving
Wikimedia projects. We're not
61:
The relationship between the
Wikimedia Foundation and the volunteer community shouldn't be about conflict, or about one side having dominance over the other; it should be collaborative. Both the community and the Foundation share a common goal – to grow and improve the sum of all human knowledge.
187:
The first on-wiki release will be small-scale, in line with the team's principles and motivations. Targets are the discussion spaces of a small number of
Wikiprojects whose members have agreed to a beta trial of Flow. We'll deploy and invite users test it out and use it as they normally would a
114:
Community members who want to see specific changes to Flow commit to acting in good faith, and to engaging in a conversation about how the changes they want will further the goal of making
Knowledge (XXG) discussion easier, faster and more intuitive for everyone.
89:
Users who have taken the time to learn a particular way of doing things on a wiki have some natural resistance to change. They need a clear rationale for change, so they can understand the tradeoffs between maintaining and breaking with the status
218:
If the trial is successful, we will also begin working on a strategy to roll out to other discussion spaces in a similar incremental fashion. Current medium-term (January through March 2014) plans include some or all of the following:
188:
Wikiproject talkpage. Any feedback they might have – good or bad – will be gathered on the Flow portal talkpage. This page will be archived to avoid confusion between older and newer discussions and will
85:
Bringing users into the conversation at the end of the development process makes it hard for their feedback to be incorporated. Ideas gather inertia, particularly when implemented, so it's hard to change
137:
For the remainder of 2013, we've plotted out two, small-scale releases, only one of which is to active projects, along with a set of informal feedback sessions for different user groups.
165:
111:
Staffers commit to responding to good-faith concerns from users, treating them with the same weight as concerns from any other member of the WMF design or development team.
79:
Discussions within the community often don't reach WMF staff, and vice versa. We don't have a good system for communicating with a large, decentralized body of volunteers.
211:
End the trial and temporarily revert back to talkpages (all Flow discussion content will be turned back into free-form wikitext) while we implement any necessary changes
195:
Before this release, the team will produce documentation explaining the software, why specific features and designs were chosen or not chosen, and highlighting that
145:
The first set of interactions with Flow won't be formal releases or active software: they'll be discussions. The first will take place in the WMF office and involve
119:
is not an acceptable position from either the community or the staff side – we should all be encouraging each other to explain our ideas and provide a rationale.
45:
Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as the
70:
promise to learn from the past and experiment with new ways of doing things that offer us a shot at working together better and more efficiently.
46:
259:
108:
be set in stone – we expect Flow to evolve rapidly and significantly based on community feedback at each stage of the process.
214:
Continue in beta, adding more features on a case-by-case basis and giving more WikiProjects the option to opt into Flow
192:
be converted to use Flow, as a way of forcing us to confront deficiencies in the software we expect others to use.
264:
207:
Based on the outcome of the WikiProject release, the Flow team and the community will decide whether we need to:
239:
approaching other language projects and sister projects to trial Flow in a limited opt-in fashion on their wikis
99:
To avoid the problem listed above, we've come up with a simple set of ground rules that both groups can follow:
116:
147:
user experience designers, developers, and anyone interested in open source software or discussion systems
171:
38:
30:
236:
Flow-enabling a sample of articles under the scope of WikProjects that are using and happy with Flow
170:
The first release is a "sandbox" release, in which the set of features that we've identified as the
62:
When conflicts arise, the solution is to come to a consensus that brings us closer to that goal.
82:
Massive, rapid deployments annoy users and overwhelm development teams with feedback all at once.
66:
going to promise that, from now on, everyone will always be in agreement on everything, but we
17:
223:
approaching more
English Knowledge (XXG) WikiProjects about participating in a wider trial
146:
253:
243:
227:
104:
specific needs of community members who are actually using the software.
233:
creating a new beta feature option to Flow-enable a user talk page
25:
166:
Knowledge (XXG):Flow/Community engagement/Sandbox release
37:
This page is currently inactive and is retained for
94:
8:
197:this is just a trial, not a finished product
95:What we'd like to try with the Flow project
7:
246:discussion on Mediawiki.org to Flow
24:
29:
73:
1:
141:Pre-release feedback sessions
230:discussions on mediawiki.org
281:
163:
74:What we've learnt so far
155:#wikimedia-corefeatures
260:Inactive project pages
172:minimum viable product
265:Knowledge (XXG) Flow
18:Knowledge (XXG):Flow
183:Wikiproject release
226:Flow-enabling new
54:
53:
272:
156:
50:
33:
26:
280:
279:
275:
274:
273:
271:
270:
269:
250:
249:
205:
185:
168:
162:
160:Sandbox release
154:
143:
135:
126:
97:
76:
59:
44:
22:
21:
20:
12:
11:
5:
278:
276:
268:
267:
262:
252:
251:
248:
247:
240:
237:
234:
231:
224:
216:
215:
212:
204:
203:Later releases
201:
184:
181:
161:
158:
142:
139:
134:
131:
125:
122:
121:
120:
117:WP:IDONTLIKEIT
112:
109:
105:
96:
93:
92:
91:
87:
83:
80:
75:
72:
58:
55:
52:
51:
43:
34:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
277:
266:
263:
261:
258:
257:
255:
245:
244:Liquidthreads
241:
238:
235:
232:
229:
228:Beta features
225:
222:
221:
220:
213:
210:
209:
208:
202:
200:
198:
193:
191:
182:
180:
176:
173:
167:
159:
157:
150:
148:
140:
138:
132:
130:
123:
118:
113:
110:
106:
102:
101:
100:
88:
84:
81:
78:
77:
71:
69:
63:
56:
48:
42:
40:
35:
32:
28:
27:
19:
217:
206:
196:
194:
189:
186:
177:
169:
151:
144:
136:
133:Release plan
127:
98:
67:
64:
60:
47:village pump
36:
242:converting
254:Categories
179:the call.
164:See also:
124:In summary
57:Background
41:reference.
39:historical
86:course.
153:IRC:
16:<
190:also
90:quo.
68:will
256::
49:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
