Wikimedia Foundation Board noticeboard/Archives/2014

Undeclared conflicts of interest

has raised very pertinent questions here, and has now publicly raised the issue for the Wikimedia UK organisation to address at its next board meeting.

I am urging the Wikimedia Foundation board inline with its commitment to its core value of transparency, to instruct employees, contractors and trustees, and the Foundation itself, to publicly declare any current or past paid editing activities, or related unpaid advocacy that may represent a potential conflict of interest, or other conflicts of interest which could bring the Foundation into disrepute, with a public declaration being required regardless of whether any conflict of interest exists. Russavia (talk) 15:46, 9 January 2014 (UTC)

  • Procedural note: Russavia has publicised this discussion on wikimedia-l and IRC with notifications saying "If anyone wishes to support this please feel free to do so on the noticeboard" and "feel free to support it there if you wish". Fluffernutter (talk) 16:28, 9 January 2014 (UTC)
    • And of course, feel free to comment/discuss. Russavia (talk) 16:33, 9 January 2014 (UTC)
I've been asked privately about my own paid projects while I was employed by the Wikimedia Foundation. As I described in a 2012 interview published in the Wikipedia Signpost, I did work do independent paid Wikipedia work in that time. (From memory, I believe the project described there was the only instance; but I will review my notes and follow up if there were others. Due to client agreements, I may not be at liberty to fully disclose specific instances, but I will clearly announce if I worked for other clients in my time at WMF.) But in general: I did discuss this work ahead of time with my immediate supervisor, as well as other senior WMF staff. In addition, I have recently published a statement of ethics on my web site; while it wasn't formalized back in 2010, the principles were the same. -Pete F (talk) 18:55, 9 January 2014 (UTC)
Upon review, I did receive payment on one other project, in which I advised on Wikipedia engagement, during my time at WMF; I believe (but am not 100% certain) that all my work on that project was complete prior to my employment by WMF. -Pete F (talk) 20:56, 9 January 2014 (UTC)
  • I'd second making COI situations more clearly documented, and to do so publicly wherever possible. For a working approach here, see WMUK's declaration of interest page. It would be great to see something similar from the WMF. Thanks. Mike Peel (talk) 19:17, 9 January 2014 (UTC)
    Hello Mike. I like the WMUK approach, and I do think that we want to move towards encouraging and welcoming transparency on all COI issues. To the extent that our publicly-visible entities can set an example for other parts of the movement, we should do so. I'm not sure we need to mandate it (do you at WMUK?) but a declarations of interest page is thoughtful. A user-space infobox listing affiliations might help as well: there is a positive way to describe one's affiliations without calling them "conflicts" while at the same time recognizing that one's contributions may be understood in that context. SJ talk  05:25, 12 January 2014 (UTC)
    Yes, Wikimedia UK do mandate public declarations for any financial or relevant non-financial declaration of interest unless there is a documented rationale given to the board of trustees that it is a private matter of no special public interest and not a reputational risk to the charity; this applies to trustees, employees and contractors and is both retrospective (e.g. an interest with a supplier of the charity from ten years ago, may still be relevant to declare publicly) and forward looking (e.g. a trustee considering being paid by a supplier or partner of the charity should inform the board before entering discussions with the supplier or partner, and would probably accept their resignation). My proposal to WMUK's board of trustees is to make this practice more firmly visible in policy, eliminate some current ambiguities and therefore less subject to whims of interpretation of trustees, with potential for error, as board members change from year to year. As a past Chairperson, I can assure you that any type of financial interest or loyalty related to Wikimedia organizations or projects would require a public declaration of interest. Situations where a declaration might be accepted in confidence to the board of trustees and not made publicly, might be when a partner or close family member had a interest, even then an interest such as the CEO's husband or daughter being a contractor with a supplier of the charity would require a public declaration due to the potential for any later claim that the board of trustees was effectively complicit in a cover-up of an inappropriate conflict of loyalties.
Should a trustee, employee or contractor have failed to make a relevant declaration before taking up their post, then a later declaration to the board of trustees or pubicly, just because circumstances have forced their hand, may not be sufficient for them to retain their position even if the interest might have been considered manageable had they declared it in a timely way. Wikimedia UK now benefits from having a Governance Committee, this avoids the unnecessary stress on the Chairperson to make every final call on actions required resulting from declarations of interest, and means there is straightforward way of assessing declarations where the board may be required to assess its own members.
By the way, in terms of wording, I find it helps to use the term "declaration of interest" and "conflict of loyalties" rather than focussing on "conflict of interest"; this avoids the false thinking that just because a relationship is non-financial or may have been years in the past it no longer needs a public declaration.
Note, the first point of review for declarations of interests and loyalties for employees and contractors is the delegated responsibility of the CEO. If the CEO failed to escalate or review these appropriately with the board of trustees, then the CEO would be considered responsible. This gives some confidence in a situation where the first that trustees hear of a problem is reading about it in the newspapers on the day the employee resigns from their post, they will hold the CEO to account.
SJ, will you make a commitment to take a proposal forward to the board that makes the WMF at least as excellent and thorough as Wikimedia UK is in handling and requiring public declarations of interests for trustees, employees and contractors? This would put to bed a lot of the community's concerns about apparent WMF doublethink which by some has been seen as hypocritical, particularly if, say, it is revealed that trustees are not subject to the same high standards with regard to managing and declaring conflicts of loyalties as employees are seen to be. By the way, should the WMF wish to set up a Governance Committee of a similar type to Wikimedia UK's, I would be happy to put my name forward as someone with a lot of relevant scars. -- (talk) 12:31, 12 January 2014 (UTC)
  • I third the call for transparency re COI, and I think the board needs an official position on undisclosed COIs and paid editing. Currently WMF executive and individual board members are trying to define the threshold, but they have different and conflicting thresholds and terminology. It may be that the board decides each project needs to find its own path in this, as the cost/benefit differs per project. e.g. Paid editing at wikisource doesnt have many negatives. John Vandenberg (talk) 09:17, 11 January 2014 (UTC)
    Currently each project does find its own path in this. What benefit do you see in a Board statement to that effect? SJ talk  06:01, 12 January 2014 (UTC)
  • If I am reading this right, the wmf:conflict of interest policy doesn't apply to staff members. Is there another relevant policy or contract for staff? Sadly WMF contracts with staff are nearly all secret, so we cant know what is or isnt permitted by staff. When the community last asked about the NDA staff had to sign, user:Keegan said he would publish his NDA, unless Legal objected. He didnt publish it. Instead legal uploaded only one snippet of the NDA. I have now asked regarding Non-disparagement clauses at Talk:Non-disclosure agreements#Non-disparagement. It shouldnt be this hard. WMF should be leading the way in transparency. That is far from reality. John Vandenberg (talk) 09:17, 11 January 2014 (UTC)
    Answering both this and the question below: specific questions about policies or contracts you may direct to staff on the wiki, as you have done: they are not questions for the Board.
    The broader question of how we can be more effectively transparent is a good one. I appreciate the specific examples of transparency from chapters and other entities, such as Mike's above. If you have a good example in mind of an org that publishes all of its contracts, I would like to see it. And I understand your frustration, but your spitfire tone when asking for documents may slow down the process: delays in publishing, no less in law than in fiction or code, tend to be tied to the authors' wish to wait to review them One More Time with a critical eye. The less collegial and understanding the audience, the longer that can take. SJ talk  06:01, 12 January 2014 (UTC)
  • Does the WMF have a policy in place forbidding its employees to undertake paid editing? 23:46, 9 January 2014 (UTC)
    • The first question you raise is perfectly valid, from the careful phrasing used by the WMF to date, I have every reason to conclude the answer is no, there is no such employee policy forbidding paid editing. If I were wrong, I am certain that someone would speedily supply a link to prove me wrong. -- (talk) 23:50, 9 January 2014 (UTC)

Invitation to comment about openly licensed media for each Wikimania presentation

I would like to request interested members to comment at the Wikimedia Forum about what can be done to ensure videos/slides are accessible for Wikimania 2014, to know what is going on with backlogs associated with pending reviews across Wikimedia projects, and the enabling of tabs in the language of one's own choice. Thanks. I think I'm done starting threads for the day on meta. Thank you for your time. Biosthmors (talk) 10:21, 24 September 2013 (UTC)

Those other two are in process. I apologize to raise three subjects to your attention when it appears only one is necessary at this point. Thank you. Biosthmors (talk) 13:00, 27 September 2013 (UTC)

Per this email, I'd like to raise the possibility that the Board consider finding a way to make Wikimania 2014 speeches/presentations all recorded and openly licensed for release online. I haven't seen any comments on my concerns yet at the Forum. Also, will the Board be publishing the agenda for the next meeting on this noticeboard? I would like to suggest doing so here. My impression from the WMF Board portal is out of date. Should it be reduced down to something simple, like a disambiguation page, with maybe 8 links? Or should it be redirected here? I don't understand why the board needs both a portal and a noticeboard. If we make the top of the noticeboard act as the portal, then we'll avoid the duplication of effort. Best. Biosthmors (talk) 17:45, 5 October 2013 (UTC)
Hi Biosthmors, that's a good point about combining the portal and the noticeboard... it is difficult to keep pages up to date. As for the meetings, we generally send the agenda out on wikimedia-l and can publish it here as well. It's generally finalize only a couple of weeks before the meeting. As for the wikimania talks... that's not really the board's area; it's something that the local organizers of the conference are responsible for ensuring happens. Thanks! -- phoebe | talk 20:11, 17 October 2013 (UTC)
@Phoebe:, I respectfully think that this is WMF's area. Expecting the Hong Kong Chapter, for example, to organize this is not really realistic when they're already struggling. If the Debian foundation, which has around $100k in revenue, can do this and keep it quite organized and accessible going back for years, I don't see why WMF can't do it. ImperfectlyInformed (talk) 21:13, 31 January 2014 (UTC)
Fair enough, though I said it wasn't the *board's* area -- there's a lot that the WMF does that's not the Board's area, and this is the Board noticeboard. The Board has zero hand in organizing Wikimania; we don't decide the budget, or anything else. That said, I don't really think it's entirely WMF's area either, though if there are ways we can help we should; there's some confusion here over the scope and role the WMF has in organizing Wikimania, which is a collaboratively run but still volunteer-led conference. -- phoebe | talk 19:49, 20 February 2014 (UTC)

Agenda January 31st-February 1st 2014 Board Meeting

Automattic Agreement for Blog Hosting Services

  • I suppose someone has recused and will recuse from any and all discussions on the topic whether private or public, official or unofficial, right? It's not clear to me what the practice is in these cases, do people with COI also leave the room during the discussion?
Yes, Stu has been recused and will continue to not be present for this topic as is our practice. Jan-Bart (talk)
To be clear: this is a very small contract, which would normally never be seen, let alone approved, by the Board. The only reason it was on our agenda was because of the possibility of perceived COI, since Automattic's CFO is on the Board. In general and in this case, people with a COI who would otherwise be in a meeting are recused and excused from the room for related votes.
  • Also, just to check, this is not inconsistent with the current wmf:Privacy policy, is it? The wordpress blog is mentioned at the draft Privacy policy but not in the old one (which however was more specific).

--Nemo 17:46, 31 January 2014 (UTC)

Review and Approval vs. Resolution [on]

Why do some items seem to imply/give for granted their outcome, while others don't? --Nemo 17:46, 31 January 2014 (UTC)

You need to give a bit more context ? What do you mean? Jan-Bart (talk) 18:00, 31 January 2014 (UTC)
Some things have resolutions attached, others are just approved by a vote or straw poll. Resolutions are more formal; and required in a few cases: for instance, any revision of the Bylaws, or appointment of Trustees. In most cases, the choice of whether a decision is a resolution reflects how much prominence we give the decision, whether it shows up in the list of archived Resolutions as opposed to just the meeting minutes, &c.
Issues that may be decided by staff without Board involvement may be reviewed and approved by the Board, but do not usually get their own resolution: for instance, the staff may update the TM policy at their discretion, but ask the Board to review significant changes. Issues that alter past Board resolutions require their own resolution; for instance the decision to allow the WMF to abandon registration of the community logo, since our general counsel felt that past Board guidance could be read to have mandated registration of the logos of all Sister Projects, including Meta. SJ talk  02:20, 8 February 2014 (UTC)

Discussion on Disrupting the Disruptors

I'm curious about this one. Are we getting into spatial weaponry? :) guillom 18:44, 31 January 2014 (UTC)

no, but thanks for the suggestion... The discussion was actually inspired by: Jan-Bart (talk) 19:18, 31 January 2014 (UTC)
On that front... re: "We need a simpler scratch-space to develop new material". We are actively developing this within Wikipedia. It's the new Draft namespace (blog post, Specifications and future ideas). Steven Walling (WMF) • talk 20:04, 31 January 2014 (UTC)
The draft namespace is a lovely idea. I'm excited to see it take shape, & looking forward to all of the wiki-aspects that could be built on top of this. SJ talk  02:20, 8 February 2014 (UTC)
For the record, such as it is, we covered more ground than the newpedia ideas -- it was a broad discussion about disruptive technologies that could/are affecting the future of Wikipedia, and concerns/future directions we have. It was a really good open brainstorming discussion. -- phoebe | talk 19:43, 20 February 2014 (UTC)

Page title

Agenda January 31st-February 1st 2014 Board Meeting should probably be a subpage of the noticeboard? Or a subpage of Wikimedia Foundation Board of Trustees or something. --MZMcBride (talk) 07:06, 2 February 2014 (UTC)

Now a subpage of the meetings page. SJ talk  02:20, 8 February 2014 (UTC)

Discussion on Commons and URAA

Further to our letter regarding the deletion of images from Commons under URAA, we would love to see this subject discussed in the upcoming board meeting. • Yael Meron (WMIL) • 11:01, 6 February 2014 (UTC)

We did discuss it at the (past) board meeting, thank you Yael. A response from the Board will be coming within the next week. SJ talk  02:20, 8 February 2014 (UTC)
reply is now here. -- phoebe | talk 19:42, 20 February 2014 (UTC)

Have you seen how Yann closed the "discussion" on commons:Commons:Massive restoration of deleted images by the URAA?

  Closed as YES. URAA cannot be used as the sole reason for deletion. Deleted files can be restored after a discussion in COM:UDR. Potentially URAA-affected files should be tagged with {{Not-PD-US-URAA}}. Yann (talk) 10:17, 2 April 2014 (UTC)

It seems to me that he must have missed the text "and remove works that are clearly infringing" in this sentence from Legal and Community Advocacy/URAA Statement:

The community should evaluate each potentially affected work using the guidelines issued by the Legal and Community Advocacy Department, as well as the language of the statute itself, and remove works that are clearly infringing.

SamB (talk) 21:52, 4 April 2014 (UTC)

As we said in our statement, "We are not recommending that community members undertake mass deletion of existing content on URAA grounds". Additionally, there is a newer statement than the one you quoted from Legal here that reiterates the point that "WMF does not see a reason to delete content simply because of general concern about the URAA". Yann's closure seems consistent with that principle. -- phoebe | talk 21:29, 15 April 2014 (UTC)
@Phoebe: But Yann seems to be saying we should NEVER delete things just because the URAA has restored their copyright. Isn't that illegal? Are you saying it's okay to break the law? —SamB (talk) 21:53, 15 April 2014 (UTC)
@SamB: hey, I interpreted that as him saying that *concern over potential URAA violation* shouldn't be used as the sole reason to delete stuff, which makes sense -- i.e. just flagging it as potentially URAA-incompatible shouldn't be enough to trigger deletion, which can be quite a disruptive action. URAA is complex, and I am saying preemptive actions (like preemptive deletion) don't seem necessary. It would be worth clarifying on-wiki with Yann if you have concerns about what he was saying, however. -- phoebe | talk 20:13, 16 April 2014 (UTC)
Hi phoebe, I had previously read the WMF statement as not being advice to Commons project administrators. Is the WMF board advising Commons administrators that they can safely refuse to delete URAA breaching material from Commons and can safely undelete images previously deleted on the basis of URAA violations? If so, then this would be a helpful clarification as many contributors seem to read it as a directive and as a result expect and require Commons administrators to take action accordingly. -- (talk) 20:28, 16 April 2014 (UTC)

Resolution specific licensing

We failed to arrive in a conclusion on how to handle cases when a user grant a free license to a limited size version expecting that he still can sell his original high resolution work to make money. We discussed it in detail here, consulted CC and WMF legal; but still struggling to make a concrete decision. Earlier we all thought that a license is applicable for what is shared there; not applicable to a large size version of it even if found elsewhere. The WMDE community had collected 80,000+ files from Bundesarchiv on this assumption. CC's new comments muddled the situation; but still the relevant copyright law is not clear. So what we have to do now. Please advise. (The summary of that discussion is available here.) Jee 05:10, 24 February 2014 (UTC)

This is a good question. I think a fair solution would be to set Commons & community policy on the matter: deciding what our social norm will be. We can explain our community's interpretation of the CC licenses when we discuss with potential grantors. We should also explain to them that there is some disagreement about how to interpret the license; and that in some jurisdictions granting a CC license on a low-res copy may implicitly grant a license in the high-res copy. This hypothetical has not been tested. For the record, I think that the uncertainty alone will be incentive enough for anyone with the budget to pay for a high-res license to do so.
In the spirit of honoring our community's agreements, my personal view is that our projects should not incorporate high-res images where low-resolution versions have been donated under a CC license to benefit our projects, through an agreement with community curators that implied that low-resolution and high-resolution images could be licensed separately, with only low-resolution versions released under a free license. This would change as soon as higher-resolution versions are made similarly available. So for the Bundesarchiv photos, we should remove high-res images unless the archiv donates those explicitly makes those explicitly available under a free license.
I believe all of this can be resolved by the Commons community. SJ talk  06:08, 24 February 2014 (UTC)
Thanks Sj for your opinion. Jee 06:29, 24 February 2014 (UTC)
Very reasonable approach, @Sj at least for things that are covered by copyright. That neatly avoids the need for fancy legal footwork, speculation, etc. I strongly support that approach. (Though I think you mean, "made available under a free license" rather than "donated to us, no?) In a similar case where, for instance, a GLAM donates low-res versions of a public domain image, and then somebody acquires higher resolution versions in any way, it seems fine to upload them over the low-res versions. -Pete F (talk) 21:54, 15 April 2014 (UTC)
It is the norm for those of us managing partnerships with GLAM and helping GLAMs to get Wikimedia related projects funded to avoid promising to only upload limited resolution images when higher versions are available as this is neither a particularly desirable outcome for our mission to preserve human knowledge, nor can we stop volunteers from uploading higher resolution material (whether PD, CC0 or other license), and gives the impression that there are ethical and realistic remunerative reasons for GLAMs to use Commons as a way of promoting their on-line retail business which charges the public for higher resolution versions. If we really wanted to allow this, then we should enable Commons as a front-end for Getty Images as this perfectly fits the same world-view.
This has been thrashed out in the past, so I would rather any detailed discussion be held on Commons where others might notice and contribute rather than on meta with our limited community here. -- (talk) 12:57, 16 April 2014 (UTC)
+1 Fae, plus we should mention that this isn't within the remit of the Board, because it is judgement on how our projects manage their content. Russavia (talk) 13:02, 16 April 2014 (UTC)
True. My good faith assumption was that SJ was not speaking here as a WMF Trustee, but as a regular Commons contributor. It would be good to have the ambiguity removed so we avoid the words of SJ being misrepresented in another place. -- (talk) 13:12, 16 April 2014 (UTC)
Pete: I clarified my comment, thank you. Fae: Thanks for pointing out the recent norms of working with media partners.
As I said above, I believe all of this can (and should) be resolved by the Commons community. Let's have any further discussion there. Regards, SJ talk  21:44, 17 April 2014 (UTC)

Bitcoin Donations

Will the topic of Bitcoin donations be discussed at the upcoming April meeting? Note, I'm asking out of curiosity, not advocacy. -- Seth Finkelstein (talk) 14:01, 20 April 2014 (UTC)

This isn't a Board-level decision. Our fundraising team decides how and what payment methods to accept. I'm sure we will one day have a cleaner process for accepting and auto-converting donations in bitcoin (possible since 2012 via bitpay). SJ talk  19:02, 21 May 2014 (UTC)

Board agenda and minutes

Dear Board members or @Slaporte (WMF):

Please update Board meetings#2014 with the proposed agenda from here and please update WMF Board meetings/2014-01-31 with the completed minutes from here.

Please remember to make updates to the relevant Meta pages each time that you announce agendas or minutes.


--Pine 07:06, 22 April 2014 (UTC)

I guess the board doesn't do a very good job monitoring this board, since Board meetings#2014 was never updated until after the last meeting.--Elvey (talk) 06:48, 6 May 2014 (UTC)
I know our secretary does try to do this. Please feel free to update pages that you notice are lagging, at least with a link to the wmfwiki page (until the day that we merge that wiki into Meta!) SJ talk  19:05, 21 May 2014 (UTC)
Hi Sj, I thought the whole point of removing volunteer admin bits from the WMF wiki was that WMF felt that community admins were being obstructionist so the way to deal with that was to remove all volunteer admin flags on WMF wiki. Wouldn't merging WMF wiki into Meta wiki re-create the same problems that WMF decided were unacceptable on WMF wiki? --Pine 06:32, 22 May 2014 (UTC)
Hello Pine, I don't know what the point of removing those admin bits was; but as far as I can see it was a rough effort to ensure that certain protected pages, such as the main page, were only changed by staff. There was also a slow flame war between the WMF staff member responsible for that wiki and the most active non-staff admin; since the community there was so small, there weren't enough disinterested observers to moderate or cool down that tension. There are more subtle ways to bring about the same result: e.g., a simple policy about pages in a WMF Portal (e.g.: they should only be changed by staff). While there would be some merge-overhead, the current WMFwiki suffers from much more serious problems -- staleness, lack of synchronization with Meta, lack of transclusion and template sharing with Meta, difficulty interacting with translators. SJ talk  14:07, 24 May 2014 (UTC)
By the way, I don't mean that we should get rid of the wmfwiki: a brief summary of the organization and its current work, are well suited to being showcased with a separate logo, navigation bar, and recentchanges. Most entities in our movement have their own site for this. ( I think a better long-term solution is to implement subsites/subwikis, making this sort of customization possible. But that's a different matter. ) But most of the current WMFwiki pages -- resolutions, minutes, meetings, press releases, detailed userpages, &c -- are better suited to meta. Any page that needs constant updating, or whose updating should trigger an update on Meta, likely belongs here in the first place. SJ talk  14:37, 24 May 2014 (UTC)
Thanks, I understand. --Pine 07:26, 25 May 2014 (UTC)

United States non-acceptance of the rule of the shorter term

FYI, [1], in particular the last bullet of the 08:53, 29 June 2014 (UTC) message. --Nemo 08:00, 9 July 2014 (UTC)

Privacy Policy — Information We Collect : proposed disclosure is misleadingly incomplete

The Privacy Policy was discussed at the board meeting last week. I pushed for and gained consensus for language in the new policy that made it clear that the privacy policy would not allow browser sniffing. It was added back in December when this was discussed AT LENGTH at Talk:Privacy_policy/Archives/2013_(2)#Information_We_Collect:_proposed_disclosure_is_misleadingly_incomplete and stayed in the draft for weeks. Then on the last day, it was removed. Now we have a draft privacy policy that does not bar browser sniffing, does not indicate that browser sniffing may take place and yet claims to be maximally informative. That's an untenable situation. That's the bottom line. I've complained about this as Talk:Privacy_policy when I noticed it, and was ignored. I hope the board adopts a new policy that is not misleadingly incomplete. Be honest. --Elvey (talk) 06:48, 6 May 2014 (UTC) (Bump. Hello?) 20:57, 10 May 2014 (UTC))

Belated clarification: I'm talking about the practice of browser sniffing to uniquely identify a reader by collecting as much information about the browser as possible including plugins and fonts. I'm not talking about simple browser sniffing to counteract user agent spoofing or even simpler straightforward use of the User-Agent string (of § 14.43 of RFC 2616/HTTP/1.1).--Elvey (talk) 18:27, 21 May 2014 (UTC)
I'm not sure how you interpret "maximally informative" here. You mean you'd like to see a sentence specifically addressing browser sniffing, or pointing to an FAQ that describes what sorts of browser sniffing may happen and how the resulting information is treated? There is a related section at Talk:Privacy policy (which section should probably be renamed). SJ talk  19:13, 21 May 2014 (UTC)
Sj: Yes, yes. I'm not saying we/you can't revoke the commitment Drdee gave, that browser fingerprinting is incompatible with this Policy. I'm saying that after having read the policy and FAQ, a user should know what browser fingerprinting is (via a link, perhaps), know that WM employs it, and that access is restricted to approved projects and user groups X, Y, Z, only (link to list of existing pages on them ), ... Make sense? I can create a version with suggested edits, AND I'd like to first hear that you're open to incorporating improvements along the lines you asked if I'd like to see. In other words, I'd like to hear that you see a need for improvement. For example, I think that the policy should have one definition for "personal information", but the current draft has three (and there's a fourth here!
I think it should be the policy itself "that describes what sorts of browser sniffing may happen", not a non-binding FAQ. At the moment, neither does. And LVilla thinks browser fingerprinting relies on cookies; it does not, so a discussion of what cookies are kept for how long can't cover sorts of browser fingerprinting may happen. --Elvey (talk) 21:10, 23 May 2014 (UTC)
That makes sense, thank you. LuisV is overseeing this, so I believe he's the one who you should check is open to incorporating these improvements. (The Board reviews and approves major overhauls, and we've already approved this one; we don't approve or review incremental changes such as the one you're proposing, since we have ridiculously talented legal staff to handle that. And I know everyone involved wants the result to be as awesome as possible, so exactly this sort of incremental change may be made over time.) SJ talk  13:47, 24 May 2014 (UTC)
Sj, FYI: LuisV stalled and ultimately failed to respond at all.--Elvey (talk) 07:47, 9 July 2014 (UTC)
User:LVilla (WMF) User:LuisV (WMF) Hello?--Elvey (talk) 19:31, 11 July 2014 (UTC)

Grantmaking committee authority

Note: this is not a time-sensitive request, unlike my other two requests above, but it fits with the theme of WMF trusting its users to make decisions.

Currently, the FDC, GAC, and IEG are considered merely advisory. I feel that the community can be trusted with expanded authority when a grants committee develops consensus. I would ask the Board to approve a policy something like this:

"When a Wikimedia Foundation grantmaking committee of volunteers reaches a consensus against a proposal with at least 4 eligible volunteers having voted and at least 60% of the votes opposed to the proposal, WMF will not override the committee unless a successful appeal is made to the Board. WMF may override a committee consensus recommendation to proceed with a proposal although that override may be appealed by the committee to the Senior Director of Grantmaking, to the Executive Director, or to the Board."

--Pine 08:02, 13 July 2014 (UTC)

Oppose until and unless there's a secure voting scheme. By which I mean a ballot box that can't be stuffed. --Elvey (talk) 23:11, 18 July 2014 (UTC)
Oppose As a grantee, and also as an observer or participant in deliberations about many grants under the GAC's purview, i am generally very impressed with how well things work. Disagreement is a given when decisions around money are made, and should not be interpreted in itself as a reason for structural reform. I have zero experience with the other programs, but I do have faith they are being run in a similarly responsible manner. I see no reason compelling this decision; and even if there are problems, I would prefer to see them explored separately from a proposal for a specific remedy. Even if there are problems that must be solved, there might be other ways to solve them. -Pete F (talk) 01:46, 23 July 2014 (UTC)

Clarify relations among Foundation, Chapters, Thematic Organizations, User Groups and individual volunteers

Sub issues:

  • How to make AffComm more transparent
The affcom is discussing this, but it is pretty open about its processes as far as I can see Jan-Bart (talk) 07:14, 5 August 2014 (UTC)
  • How and when the existence of a chapter can affect the formation of another type of affiliate, such as a user group.
It shouldn't, although it would be good if they work together Jan-Bart (talk) 07:14, 5 August 2014 (UTC)
  • Is there a hierarchy among groups? If so, what is it? If not, why is there an assumption that everything in a territory with a chapter must go through that chapter?
There is no hierarchy and although we would prefer local initiatives to work with the chaper in that area (simply because it usually adds value) but this does not have to be the case. There are many examples of small groups of individuals who are organising themselves to get something done (and sometimes they create a user group) Jan-Bart (talk) 07:14, 5 August 2014 (UTC)
  • If a chapter refuses membership and/or support to people or projects, what are the alternatives?
Reading the information below I get the intent of this question, but a chapter does not have to "provide membership". you can just apply for any user group/thematic org status without their permission. Jan-Bart (talk) 07:14, 5 August 2014 (UTC)
I'm curious what brings you to include bullet #3 -- that sounds like it's very out of sync with how things are supposed to work. Speaking for myself, I have put together a number of events in areas that have formal chapters (England, Canada, DC, NYC) and places with less formal chapters-in-formation (SF, Portland, Boston) without any chapter involvement whatsoever. Are you talking about WMF funding? One of these projects (as you may recall) was WMF funded. If there are cases where a non-chapter-affiliated project has been denied funding on the grounds that they didn't work with the chapter, that should definitely be discussed -- but personally, I'm not aware of any cases like that. -Pete F (talk) 17:54, 31 July 2014 (UTC)
Yes... I thought so too. But there has been a long and sad history between Wikimedia Mexico and wiki work at my campus, currently under the name of Wiki Borregos. [2] Thelmadatter (talk) 19:42, 31 July 2014 (UTC)
Leigh, I'm sorry to hear it, and interested to know more if you want to share. -Pete F (talk) 19:48, 1 August 2014 (UTC)

Suggestion for the Board: Technology Committee

Given recent events on the English, German, and Commons wikis surrounding MediaViewer and the troubled history of WMF product launches, I request that the Board take a more active role in engineering and product development. To do this, I propose that the board establish a Technology Committee. This request is consistent with my understanding that the Board feels that it needs to acquire more technology expertise to provide adequate oversight and guidance for WMF technology initiatives, so I hope that multiple needs can be addressed by this Committee.

  • Tasks and scope:
  • Oversee the design, project management, and testing of software products.
  • Conduct regular reviews of products that are under development
  • Ensure that useful and unbiased statistics from readers and editors are taken into consideration in product design.
  • Consult Wikimedians at important milestones in product development and ensure that their views are carefully considered by WMF.
  • Give final approval to the launch plans for major product changes and new products.
  • Oversee the curation of ideas for new products.
  • Oversee the prioritization of human and financial resources for the software product portfolio.
  • Ensure that deliverables are produced in a timely and cost-effective manner.
  • Other activities
  • Review major contracts for technology-related services, and make recommendations to the Board about major technology contracts.
  • Oversee the distribution, commissioning, major maintenance, and decommissioning of data centers and other high-value hardware.
  • Oversee the creation and implementation of data privacy and security measures.
  • Oversee risk management for technology matters.
  • Oversee the recruiting, selection, evaluation, and compensation of high-importance technology staff
  • Composition:
  • Two Board members. Their committee membership will be renewable once consecutively for a maximum of four consecutive years.
  • One member from a non-Wikimedia Foundation organization that uses MediaWiki or other software created, maintained, or used by the Wikimedia Foundation. This member will be appointed by the Board for a two-year term. Terms will be renewable once consecutively for a maximum of four consecutive years.
  • One member selected by the Funds Dissemination Committee from within its membership for a term of up to two years or until the member's FDC membership ends. Terms will be renewable twice consecutively for a maximum of six consecutive years.
  • Four members from Wikimedia content communities appointed in a community-wide election in a manner similar to Steward elections. These members will be appointed by the Board for two-year terms, with two members appointed or re-appointed each year. Terms will be renewable twice consecutively for a maximum of six consecutive years. For the first round of elections, the two candidates with the most positive votes will receive 2 year terms and the remaining successful candidates will receive 1 year terms.
  • Three members, appointed by the other members of the Committee, who have expertise in one or more of the following areas. These members should be drawn from within the Wikimedia contributor community or be from mission-aligned organizations. The Committee is strongly encouraged to appoint members who have expertise in more than one of these domains and to have at least one expert in each domain on the Committee. These members will be appointed for two-year terms. Terms will be renewable twice consecutively for a maximum of six consecutive years.
  • Technology product management
  • Human resources for technology projects
  • Finance or accounting for technology projects
  • Legal issues that are relevant to projects currently being supervised by the Committee
  • Software user experience or design relevant to projects currently being supervised by the Committee
  • Research or analytics relevant to projects currently being supervised by the Committee

This is a draft proposal and I encourage the Board to use it as a starting point for discussions. I also urge the board to look at the recent discussions about MediaViewer on English Wikiepdia 1 2 3 4, German Wikipedia 5 6, Wikimedia Commons 7, and Wikimedia-l 8 and think about how the Board can prevent this kind of situation from occurring repeatedly.

Thank you, --Pine 08:00, 12 July 2014 (UTC)

  •   Support It sounds like hard work for Tech Committee members, but it would probably act as a great governor in the process and would be likely to push for early types of user testing and user case validation that may provide for a more mellow roll-out of changes. -- (talk) 08:16, 12 July 2014 (UTC)
  • Support: this might be a suitable form of governance for this proposal, already before the Board, and which includes the suggestions that
1. WMF planning address the issue of development of certain complex rendering markup and editing components;
2. WMF liaise actively and effectively with existing editor and reader communities in (1);
3. WMF draw up roadmap for development of complex rendering and editing;
4. WMF liaise actively and effectively with volunteer developer communities to determine required frameworks and work packages;
5. WMF allocate funds and resources to support work packages.

If those proposals were accepted, then here would be an example of an area in which a Technology Committee would be of value in helping the Board support the WMF in its strategic planning, act as a voice for the volunteer community, and constructively challenge and hold to account the coherence of the planning and the progress made in delivery against those plans. Deltahedron (talk) 12:25, 12 July 2014 (UTC)

On a related note:

  • This has not been taken with the relevant product team.
  • I believe that we should not escalate things before a relevant Team looks into them.

--Gryllida 09:45, 13 July 2014 (UTC)

  • ∞ support :/ John Vandenberg (talk) 10:33, 13 July 2014 (UTC)
  • Yes: it does look good to involve the board more closely in tech challenges. Tony (talk) 13:12, 14 July 2014 (UTC)
  • Support the basic concept. Clearly some kind of oversight is needed. —Neotarf (talk) 01:01, 23 July 2014 (UTC)
  •   Comment Something is clearly needed, but I am skeptical that adding a layer of bureaucracy is the best remedy. But the approach to software development in recent years has done great damage to the collegiality of our movement, and something needs to change. -Pete F (talk) 01:49, 23 July 2014 (UTC)
    If you look at this thread, it appears that a layer of bureaucracy, in the form of volunteer advisors, was actually *removed* with this mass desysopping of volunteers. And Sue's subsequent statement "occasionally volunteers have overridden decisions made by staff ... occasionally, those discussions have been extremely time-consuming..." points to some kind of issues with ad hoc volunteer oversight. —Neotarf (talk) 16:17, 23 July 2014 (UTC)
I don't see that specific discussion as being directly relevant, but your comment suggests something to me. It seems to me there are three general philosophies that WMF could theoretically take, to help build and maintain its own understanding of what happens in its various volunteer communities:
  1. Listen to whoever comes to them with problems, ideas, insights, etc.
  2. Create a formal structure, and communication channel, for communities to present problems, ideas, insights, etc.
  3. Build an internal capacity to better observe, listen, and surface problems, ideas, insights, etc.
 #1 is what we've had from the beginning, and I don't think anybody needs to be persuaded that we have long since outgrown the stage where #1 can be effective. #2 seems to be what is proposed here (and has been implemented in various other places in the wikiverse).
I believe that #3 is the way to go. In order to do #3, the organization would have to prioritize this issue in its organizational development and hiring, and to date, it has not done so.
It's impossible for us in the community to compel the organization to do #3. Pushing for #2 is more possible; #2 is a clearly defined intervention, something that could be promoted, campaigned for, established as a popular way forward, and implemented. But I do not believe #2 would be nearly as effective as #3.
This proposal looks to me like the community trying to micromanage the organization. This makes me wonder: in general, when does micromanagement occur? I'm sure this is a phenomenon that has been studied. I'd guess it's something that happens in the absence of clear shared expectations and good lines of communication. If that's the case -- or anything like it -- I'd rather see the underlying issues addressed, than the mere treatment of symptoms. -Pete F (talk) 16:50, 23 July 2014 (UTC)
See w:en:Micromanagement#Causes. The article blames most of micromanagement on the manager's personal psychological problems. The external causes listed (e.g., increased time pressure) are mostly irrelevant to Wikipedia. AFAICT in a brief search, the article is consistent with the literature.
My primary concern with this committee-based approach (which has been suggested by staff before) is that it would not achieve the desired goal. Imagine that the committee approves something that breaks your workflow, or the workflow of any dedicated contributor. Can you imagine our most active, independent contributors saying, "Oh, well, it screws up everything for me, but 'The Committee Approved It', so I guess it's fine after all." My guess is that most editors who are badly affected by a change (even if it actually is an improvement for most people) and currently blame "the WMF" or "the devs" would simply add the new committee to the list of incompetent people who are bent on destroying the projects. WhatamIdoing (talk) 17:31, 23 July 2014 (UTC)
Thanks @WhatamIdoing:, I agree very much with the way you've put it. -Pete F (talk) 20:06, 23 July 2014 (UTC)
According to the Wikimedia Foundation Board Handbook, the Board should Support and advise the Executive Director and senior staff without micromanaging. Assuming that it does this at present, why should it fail to do so with a Technology Committee? Deltahedron (talk) 20:57, 23 July 2014 (UTC)
Sure, there is a big, big, difference between micromanaging and ensuring that Trustees have enacted their duty to hold senior management to account by retaining sufficient oversight of operations. This is written into UK charity law so that trustees are themselves legally liable if charitable funds are misused, or the charity or its employees break the law. I presume US law has similar obligations on trustees. Oversight itself, is often delegated to committees where this has to involve a lot of special reports, such as the annual reports, and many charitable organizations have project or technology oversight committees as part of their governance system (i.e. providing assurance directly to the board of trustees without requiring approval of the Chief Executive). -- (talk) 12:54, 24 July 2014 (UTC)
I believe Pete said that his concern was about core community members trying to micromanage the organization, not that the Board was or would. WhatamIdoing (talk) 19:12, 24 July 2014 (UTC)
Yes, that's right. I want to point out, however -- the section of the Wikipedia article you quote opens listing "doubts about competence" -- which is, I think, the closest thing to my concern, and not necessarily related to anybody's psychological problems. Though "competence" is a harsher word than I would choose, I believe this is the dynamic that's currently at play: the WMF has done a number of things in software deployment that have been poorly received. I believe the best solution is for the WMF to focus on improving its ability to predict how things will play out, and work effectively toward desirable and non-dramatic outcomes (approach #3), not for the community to try to micromanage the WMF's approach (#2). But again, #3 will probably take a major effort on WMF's part. If it doesn't happen, I don't know exactly what the result will be -- but I don't think any of us will like it. -Pete F (talk) 20:38, 24 July 2014 (UTC)
I believe that the phrase "micromanagement, such as detail-orientedness, emotional insecurity, and doubts regarding employees' competence," is meant to be a description of micromanagement. That is, doubting the competence of all your employees is symptomatic of micromanagement, not causative. Similarly, being detail-oriented doesn't cause micromanagement. The ==Symptoms== section emphasizes an inappropriate attention to details as a symptom. WhatamIdoing (talk) 16:59, 25 July 2014 (UTC)
In what way is the proposal to create a Board Technology Committee micromanagement by the community? Is the proposal in itself micromanagement, and if so, of whom? The Board? Or is it the list of proposed members micromanaging the Board? Or is the fear that those core members would use the Committee as a vehicle to micromanage the staff? Oh, and just who are those core members with such a power? Deltahedron (talk) 17:15, 25 July 2014 (UTC)
What Pete originally said was, "This proposal looks to me like the community trying to micromanage the organization." I used "core community members" as a more precise phrase, because (as Pete knows) "the community" doesn't exist: it's "the communities", and there are dozens, if not hundreds, of them, and they sometimes have contradictory goals.
Pete and I both definitely qualify as core community members; we've both made tens of thousands of edits and are regularly active in metapedian and other work that happens with the communities rather than directly in the mainspace. I don't know if you would consider yourself as belonging to that category; at some level, it is a matter of self-identification. In theory, it doesn't matter who the core members are. In practice, only core community members from major projects have any realistic chance of being elected to something like this. WhatamIdoing (talk) 20:43, 28 July 2014 (UTC)
Well, that certainly puts me in my place. Now let me repeat the more important question: In what way would this proposal constitute people like you and PF trying to micromanage the organisation? Deltahedron (talk) 21:45, 28 July 2014 (UTC)
At this point in the discussion, I don't think my concept of "micromanagement" is really so helpful. It seems to me, @Deltahedron:, that we came to some understanding below, and I think that's the more important thing. I'd suggest we just drop the "micromanagement" concept as my failed attempt to communicate something, that I think has now been adequately communicated in other ways.... -Pete F (talk) 23:27, 28 July 2014 (UTC)
Fair enough. Deltahedron (talk) 06:15, 29 July 2014 (UTC)
Deltahedron, you are the only person truly capable of "put[ting] [you] in [your] place". As I said, whether you're in that group is a matter of self-identification. WhatamIdoing (talk) 03:56, 8 August 2014 (UTC)
Well, if it requires ten of thousands of edits and involvement in multiple community activities, then I clearly am not. But the point is not my amour propre, but the position of the numerous contributors across the various projects, the vast majority, who are not "core" in any sense, and would not expect or aspire to be, but who collectively need to be able to have their views and requirements captured, assessed and, hopefully, satisfied. How will WMF, its Board, staff and other structures achieve that? It seems to me that a WMF Technology Committee would be a useful part of achieving that for technical requirements. It can hardly be argued that improvements in this area do not need to be made, can it? Deltahedron (talk) 17:00, 9 August 2014 (UTC)
I do not see 2 (Create a formal structure, and communication channel, for communities to present problems, ideas, insights, etc.) and 3 (Build an internal capacity to better observe, listen, and surface problems, ideas, insights, etc.) as antithetical so much as complementary -- I would say that both are now vitally necessary. It seems to me that formal structures are now inevitable, the current informal arrangements being no longer fit for purpose. It has been pointed out that there are 75,000 active editors on 800+ WMF wikis and thousands of communities in 200+ languages. With the best will in the world, existing staff arrangements, or any plausible increase in their capacity to better observe, listen etc, are not going to be enough. Formal structures are going to be necessary to prevent the staff either sinking under the weight of volunteer expectations or withdrawing into some kind of siege mentality. Deltahedron (talk) 21:23, 24 July 2014 (UTC)
By the way, it would be interesting to hear from supporters of 3 (Build an internal capacity to better observe, listen, and surface problems, ideas, insights, etc.), especially those who believe that 2 is not wanted or needed, as to how they might propose to build this capacity? Deltahedron (talk) 21:38, 24 July 2014 (UTC)

I agree that formal structures are needed; I think the key differences between #2 and #3 are in whether those structures are internal to the WMF or external, and whether they are composed of paid staff or volunteers.

I think there are a lot of ways #3 could be implemented. I may not have enough expertise, and have certainly not devoted the necessary time, to make a strong or specific proposal. That's probably work that's better suited to the Board or the ED anyway. But for the sake of clarifying what I have in mind, I think something like this would be worthwhile:

  • Create a new C-level position (silly "draft" title for the sake of discussion: Chief Collegiality Officer). CCO has primary responsibility for the relationships between the WMF and its various constituencies (readers, regular editors, occasional editors, professors, software developers, etc.) CCO is also responsible for carrying institutional understanding of healthy and unhealthy dynamics within those communities, and developing a practical understanding of what can be done to improve their health.
  • CCO's qualifications have nothing to do with technology; a good candidate might have a background in social justice movements, government, governance of a large university or parks system or similar, organizational development.
  • Reorganize within WMF so that some relevant existing positions report to CCO.
  • CCO has (shared) authority over any action of WMF that can impact relationships with those constituencies: new software features, amendments to TOU and other policies, grant programs, etc.

Like I said -- the bullets above are just a sketch, not a proposal. That's the kind of thing I mean. It's possible the same sort of thing could be achieved without a new hire, but by restructuring the existing organization, redefining responsibilities, etc. I wouldn't rule that possibility out, it may well be the better approach; but it's harder for me to sketch out an idea under that model. -Pete F (talk) 19:36, 25 July 2014 (UTC)

Then we are pretty much in agreement, in that a Chief Officer with a formal remit is to my mind an example of (2), namely a formal structure and a communication channel. To me (3) is about culture, attitude and mindset of WMF staff. I happen to believe that in certain places that needs changing, perhaps a lot, but I don't see how that would happen without being driven from the very top. Deltahedron (talk) 19:44, 25 July 2014 (UTC)
Glad to hear it. I hope this clarifies my position -- I'm not contesting the need for some kind of major change -- far from it; I'm just not confident that the specific proposal put forward here is an effective way to bring it about. -Pete F (talk) 19:49, 25 July 2014 (UTC)
And @Deltahedron: I can see now, the way I defined #2 and #3 was not so great -- I can see how it lead to the misunderstanding. You're right, the stuff I have in mind for #3 absolutely constitutes "formal structures" so I should have defined those better. -Pete F (talk) 19:51, 25 July 2014 (UTC)
It is worth noting that the WMF wmf:staff and contractors include a
Chief Communications Officer, whose "team leads the Foundation's efforts to openly and effectively share information—about the Wikimedia movement, the Wikimedia projects and the Wikimedia Foundation's work itself—with a global audience including volunteer editors, site readers and other stakeholders."
Legal and Community Advocacy team, "charged with carrying forward the Foundation’s goals of advocating for the community"
Community liaison who "help to communicate and facilitate new software (changes)"
There's a lot of aspiration here for collegiality. I wonder whether it's all being harnessed effectively. Deltahedron (talk) 20:12, 25 July 2014 (UTC)
Yes, I agree -- there are a number of positions that have responsibility for pieces of this. I believe organizing them in a way that more clearly establishes responsibilities and accountability, in the interest of improved health throughout the movement, is key to the WMF's continued success. -Pete F (talk) 20:42, 25 July 2014 (UTC)
  • On the putative Chief Collegiality Officer. I would be concerned if the CCO were indeed quite unqualified in technical issues. I would suggest that that the Chief Officers of a high-tech organisation like WMF need to be technically competent at least, in addition to any other qualifications. Otherwise the technical savvy has to come from somewhere -- such as, for example, a Technology Committee ... Deltahedron (talk) 17:58, 26 July 2014 (UTC)
    • "unqualified in tech issues" is not exactly the way I'd put it. The thing is, the Wikimedia vision doesn't fundamentally have anything to do with technology; technology just happens to be one of the best kind of interventions we have to pursue that vision. Running a complex organization with a lot of stakeholders -- say, governing the USA -- involves a lot of technology; but do we expect a presidential candidate to be a programmer? Or do we expect them to have a good enough grasp of technology and management to delgate technical aspects of the position effectively, and work well with the team they hire? I think it's the latter, and I don't see why it should be different for Wikimedia. (I wrote an op-ed piece that talks about this on a general level a few months ago.) Does that make more sense than how I put it before? -Pete F (talk) 00:52, 28 July 2014 (UTC)
An interesting point. But since WMF is, at least at present, engaged in high-tech work as part of its core business, and I am quite clear that all the leader of such an organisation need to understand what it is the organisation is doing. I believe that it is not possible to manage, or lead, abstractly. Deltahedron (talk) 06:18, 29 July 2014 (UTC)

I'm following this discussion with a lot of interest. Several things said are worth to consider and I agree that the current situation is nothing to be proud of nor to be continued without adjustments. However, a german phrase crossed my mind "Und wenn du nicht mehr weiter weißt, dann bilde einen Arbeitskreis". (Something like "And if you don't know how to carry on, create a working group.") . Given that The WMF focuses on product and engineering and wants to accelerate technical improvements (and needs to), how should that kind of committee be structured or supported to avoid being an obstacle in the process? Do you consider to let readers also have a say, or is this the part you assume the WMF to cover with sufficient competence? Creating a committee looks like an easy approach at first sight, but when we think this further, we need to ensure not to create more administrational overload at the same time. Alice Wiegand (talk) 19:32, 29 July 2014 (UTC)

I assume that the Technology Committee would support the Board in its oversight role, rather than being part of any administrative or operational structure. I have worked for, and with, organisations with a Scientific Advisory Committee, and on such Committee. Their work is capable of being constructive, if challenging. The role of such a Committee is not to direct the organisation, or write its strategy, but to help the Board hold the organisation to account technically, to give an informed external view of the way technical work is going onside and outside the organisation, to challenge groupthink, complacency, inefficiency and incompetence; it should have the right to advise, to warn and to be consulted. Deltahedron (talk) 19:30, 31 July 2014 (UTC)

The en wiki arbitration com case on a previous Media Viewer incident is interesting. Its still in workshop phase but there is a very interesting proposal by Newyorkbrad [3]

The WMF (including senior staff and developers) and the English Wikipedia community (and, as interested, other project communities) are strongly urged, as a matter of priority, to develop a protocol for collaboration and cooperative decision-making concerning high-impact software and technical changes and new or modified features (collectively referred to below as "Software Changes") that may substantially affect the Wikipedia experience for editors and readers

To me this strikes the right balance between the WMF and editing communities.--Salix alba (talk) 20:10, 13 August 2014 (UTC)

Not very urgent questions about Teams commitment, related to the above

On an unrelated note I would ideally like this things to be done:

  • To dedicate a separate new team to the documentation process, including localisation of the MediaWiki documentation, as well as any extensions WMF develops;
  • To prevent the WMF engineering from abandoning any extensions it develops, like this one. Maintaining a project is one of the most important phrases of its life-cycle;
  • To prevent any WMF team from making decisions based on purely one-project trials, such as this decision based on results of pilots on 2 Wikipedias but not any other sister projects.

--Gryllida 09:45, 13 July 2014 (UTC)

About the Media Viewer Roll Out

Hi all,

Some of you have asked the Board and its individual members for feedback. Some of us are already in conversation with you or are planning to answer on different pages. This is our general common statement:

The Board supports the decision to protect the Media Viewer roll out. Our platform powers a top-5 website. We need operational protocols that are consistent with this position. This includes making improvements, rather than a tendency towards reverting to the status quo.

At the Board meeting before Wikimania, Lila laid out her strategy to put in place best practices for product development. We will communicate sooner, we will prioritize smarter, we will test more, and we will achieve better outcomes. Her vision is to involve the community at each step of product development, including more structured feedback stages and reviews. We endorse this vision.

We realize that there is concern about the superprotect user right and how it affects power balance and influence on content and administration. We recognize the concern that we need to explain and introduce our measures better. However, stability of the platform is necessary as we seek to improve our sites, and, for that reason, we support the creation of this tool. We also understand that with more robust rollout plans and better staged community feedback - as Lila envisions - the tool should rarely be used. We urge you to focus on specific improvements you'd like to see in the Media Viewer and the roll-out process. Lila intends to incorporate that feedback as she plans to improve Media Viewer and the process for future product roll outs. The Wikimedia Foundation needs to be in a position to make software and configuration changes for which it is responsible. We expect restrictions of MediaWiki code-level editing to be a temporary step to enable us to move forward with improvements. As we say, Media Viewer should be improved; our procedures to date have not yet met the high standards we want to set for ourselves. Lila wants to address both now, and we need to give her the space to do so. She has our full support and confidence as she tackles this tough challenge.Jan-Bart (talk) 18:13, 14 August 2014 (UTC)

Thank You

A big Thank You to the Board for their statement concerning the superprotect-affair. Thank You for disrespecting the communities, thank You for disrespecting the guidelines for Office actions, thank You for arguing personal ("We have trust in Lila, she will save the world") instead of arguing to a concrete case of power abuse without any urgency, thank You for having even the chutzpah of urging the communities, on what they have to focus with their reactions. Thank You for destroying the little plant of regaining trust, that Lila's personal statements on her talk page made growing. --Magiers (talk) 17:10, 14 August 2014 (UTC)

+1. (For a more explicit establishment of why your Board notice is totally off, see e.g. [4]). Sadly, Ca$e (talk) 17:13, 14 August 2014 (UTC)
In addition: "The Board supports the decision to protect the Media Viewer roll out." - this phrasing is totally misleading and indeed suggests that you have been mislead yourself, as it concurs with Lila speaking of merely 2 options regarding the matter. I have established here why this is mistaken. Ca$e (talk) 08:20, 15 August 2014 (UTC) Also, just so that none of you will be able to say haven't heard: you are now for several days seen as producing issues of legal concern, as was pointed out months ago. Ca$e (talk) 12:25, 16 August 2014 (UTC)
+1 (passing to inactivity, as many other editors and sysops already have over this scandal, no more left to say).--Aschmidt (talk) 19:40, 14 August 2014 (UTC)
+1. The Board doesn't even care how much trust has been shattered by their disrespecting the communities. --Leithian (talk) 08:11, 15 August 2014 (UTC)
  • Well, I for one am looking forward to hearing more about this: At the Board meeting before Wikimania, Lila laid out her strategy to put in place best practices for product development. We will communicate sooner, we will prioritize smarter, we will test more, and we will achieve better outcomes. Her vision is to involve the community at each step of product development, including more structured feedback stages and reviews. We endorse this vision. Deltahedron (talk) 17:23, 14 August 2014 (UTC)
+1 - Nice but hollow words. WMF is asking the community to trust Lila's vision while this same community is being bullied by WMF. The trust was broken, many respected editors are leaving and it seems now too late to engage in a fruitful discussion (not certainly before MV is disabled by default). Forgive my skepticism but I don't believe it is really necessary to keep MV enabled in order to make improvements. Alvesgaspar (talk) 11:41, 21 August 2014 (UTC)

Think tank

The Board might consider having its own Think Tank. An area where new, high-level, strategic ideas can be proposed and discussed between the Board and interested members of the community about where WMF project should be going, in very broad and conceptual terms. Very much not a forum for debating the merits of specifical, tactical or historical decisions. Just as some examples, nt necessarily because I think they're good ideas:

  • How should WMF projects interact with MOOCS?
  • WMF should involve itself more in open standards for metadata
  • WMF should commission academic research into its own projects, using its own data

Deltahedron (talk) 06:44, 21 August 2014 (UTC)

Actually, the Strategy Wiki was thought of as an example of such think tank, and, despite all issues, I think it was rather a positive experience.--Ymblanter (talk) 07:20, 21 August 2014 (UTC)
Interesting, I hadn't been aware of that. Would you like to give a brief summary of what the plus and minus points were as you see them? Would it better to revive it or start afresh? Deltahedron (talk) 11:41, 21 August 2014 (UTC)
The minus points were that it was too crowded and nobody had any obligations. For example, in one of the task forces I participated a user volunteered to summarize things on a regular basis, but then disappeared and nobody heard of her again, and the things were not done until I did them, and then some other users joined. Also there were a lot of discussions about nothing, and liquid threads which were installed here did not make things better. Good things were that at the end some things were formulated, and they made it to the 2010(?) strategic plan. I do not think reviving it would work. Instead, one can envivision ofa think tank, possibly on the same basis as many committees here: solicit applications and then select 20-30 users with sufficient commitment and appropriate/diverse background, and in case of inactivity replace the swiftly. (One can also think whether external members would be useful, or it would be just a think tank of the Wikimedia editing community. However, it is useless to start anything like this until the Board /ED clearly expressed interest in creation of such body.--Ymblanter (talk) 12:03, 21 August 2014 (UTC)
Thanks for that. I am indeed suggesting it here as something the Board might wish to initiate. Deltahedron (talk) 12:59, 21 August 2014 (UTC)
An interesting idea, worth considering. Individual pages about strategic topics can be categorized as strategy or initiatives. SJ talk 

Request: clarify policy for on-wiki Office actions

I request that the Board pass a resolution similar to the following.

"The Wikimedia Foundation will almost always execute the decisions made by local communities with regards to whether a particular software feature is activated on their projects. Requests to opt-out of default activation or deactivation of a feature must be renewed every 6 months, otherwise the WMF will set the feature to its default state. WMF fundamentally respects the communities' rights of autonomy and will not impose an office action on the technical operations or features of a wiki unless necessary to maintain the security, privacy, technical stability, or legal status of the site." --Pine 07:45, 13 July 2014 (UTC)

The term 'Office' action in your section title is very inappropriate here. afaics, Erik's action on English Wikipedia is not an 'Office' action. Anyway...
While I would prefer that WMF did pass a resolution something like this, I do support for the 'software developers' and sysadmins being a separate community with their own processes that other communities need to accept, which is where Limits to configuration changes. The problem is with the WMF user acceptance & deploy processes; not the relationship between devs/sysadmins and content communities. For example, I would prefer that the WMF commits to keep one of its own feature in beta until there has been an RFC accepting the feature, and from a software engineering perspective the feature should stay in the 'Beta features' list even after it is flicked to opt-out, so that it doesnt suddenly change to be buried in some user preference panel, and so that the opt-out status can be changed back to opt-in easily in the first few months. Ideally the opt-in/out status is a toggle that the local 'crats or sysops can change. John Vandenberg (talk) 09:52, 13 July 2014 (UTC)
The on/off switch is only a last resort, though one that it's good to have. The problem here, as usual, and as usual without any magic solution available, is our complete inability – in most cases – to have a proper agile software development where the users are involved in building the software since earliest phases. The more something is unwanted and disliked, or fundamentally broken, the more actual users will walk way disgusted from its discussion (hence discussion is dominated by a self-selected and biased pool of persons interested in the project a priori)... until, maybe one or two years later, the result explodes on everyone's face.
The answer the board should have is whether their organisation is able to stop or correct wrong initiatives before throwing millions of dollars at them. (Especially because the millions are spent in staff time, which proportionally adds to interaction and time needed from an already-exhausted community. So each million spent in staff time probably costs multiple millions-worth of volunteer time subtracted from editing work; the gains for such costs must be very clear beforehand.) --Nemo 09:07, 14 July 2014 (UTC)
I second this request, with reference to similar conflict in de.wp, see [5]. At least, I'd like to get a reaction from our trustees indicating that they recognize this as a problem, albeit I understand they don't feel it appropiate to take up position at this juncture. Greetings, --MBq (talk) 08:27, 13 August 2014 (UTC)
Hello MBq: this is indeed a problem and needs clarity (as recent events emphasize). Thanks Pine for your prescience. We did discuss the necessity of improving and clarifying any such changes at our past Board meeting, but no action resulting from this had been put into place in time to affect recent MV (roll|fall)out. I agree with John: our traditional community of devs and sysadmins has its own community process, and does not always accept or implement the results of decisions by content communities... this has its quirks but isn't terribly broken and doesn't need immediate fixing. In contrast, the WMF deployment and evaluation and communication processes need to be thoroughly fixed. John Vandenberg, I would be interested to see a text "something" like the above that you feel captures the separate communities of sw devs and editors.
Self-selection in software design discussions is a problem. Nemo, do you think the suggestions elsewhere of a technical working group, or some other method of identifying a slate of active editors to participate in discussions (particularly about need, motivation, feasibility), would be helpful? SJ talk  07:22, 2 September 2014 (UTC)
Various ideas of this kind are being discussed at Community Engagement (Product)/Process ideas. I myself was involved in putting forward a specific proposal of a similar kind [6], as you know [7], which included the following points:
  1. WMF planning address the issue of development of mathematics and other complex rendering markup and editing components.
  2. WMF liaise actively and effectively with existing editor and reader communities in (1).
  3. WMF draw up roadmap for development of complex rendering and editing.
  4. WMF liaise actively and effectively with volunteer developer communities to determine required frameworks and work packages.
  5. WMF allocate funds and resources to support work packages.
Unfortunately it seems that all of those were rejected -- or at least, no-one has ever told me otherwise. Is that because the WMF Board actively disagrees with them? If so, there's no point in discussing here something the Board has already decided to reject. Deltahedron (talk) 08:50, 2 September 2014 (UTC)
  • I'ld like to pick up the pointour traditional community of devs and sysadmins has its own community process, and does not always accept or implement the results of decisions by content communities... this has its quirks but isn't terribly broken and doesn't need immediate fixing. In my case, and it's the specialised one of mathematics editing and rendering, I have to disagree. The fact that a group of editors felt it necessary to get Jimmy Wales to press our case speaks volumes: that cannot be the appropriate process. Incidentally, this is not about the fact that our suggestions were comprehensively rejected, that's a decision for the Board and ED to make, and they made it. This is about the hoops we had to jump through. Speaking personally, I would say that it is appallingly difficult to find out who makes decisions, where discussions are being held, or what is going on. My inreractions with WMF staff have ranged from constructive engagement, regretful lack of resources, via patronising, condescension and on to deliberate obstruction, childish sulking, outright hostility, personal attacks and dishonesty. This is not a picture of a quirky system, it's a picture of one that is broken. Deltahedron (talk) 09:02, 2 September 2014 (UTC)


Actually I am aghast about the ignorancy and arrogancy represantatives of the foundation are acting right now. The foundation should bear two points in mind:

First, the development of the software has to be done in consensus with the community(s). It can't be devellopped against them. Jimbo was aware of this very early when in 2001 he published his statement of principles, which to my knowledge never was revoked. If we look into it we find the fourth item:

Any changes to the software must be gradual and reversible. We need to make sure that any changes contribute positively to the community, as ultimately determined by the Wikimedia Foundation, in full consultation with the community consensus.

The WMF at the moment is acting against this statement of principles, is is acting against the community consensus. The WMF is harming Wikipedia because of their unprecedented injuring and unsettling the Wikipedia editors.

Second, during the last years Wikimedia was blessed with high amounts of money people from all over the world donated. But people do not donate because of MediaWiki is a nice software ore because of the Website appears neatly but they donate because they think that Wikipedia is helpful (in school, for doing homework, for beingn informed). It is the content which triggers users from all over the world to donate. While I think that Tim Starling et al. are doing good work for Wikipedia, pityfully, they are not the primary reason why people are donating money to the WMF. To make it short: it is the content of Wikipedia which makes up almost all of the salaries of the people employed by the foundation. And the content is produced by us, the editors, not by Lila, Eric, or any other WMF employee. If you are deciding to continually injuring and unsettling us editors you must expect editors will quit, content will wind down in quality and/or actuality, and eventually fundraising shrinks.

Think about that. --Matthiasb (talk) 09:56, 13 August 2014 (UTC)

+1 I totally agree and wish, that the Board seriously reviews the way software changes are developed and introduced into the projects. It's not the first time such problems between the staff and communities occur and this is slowly and seriosly harming the projects, more than gender gaps or "rights to forget" ever could. --Don-kun (talk) 14:51, 13 August 2014 (UTC)
I am increasingly worried about statements made at Wikimania and on-wiki by officials of the Wikimedia Foundation that read as threats to block accounts of those that raise dissenting voices. There is a world of difference between someone who has a legitimate complaint to pursue, compared to deliberate disruption, vandalism or spamming. I hope that the Board of Trustees can make that distinction exceedingly clear. Frankly, in the current increasingly polarized environment, I am concerned that even writing here without expressing any particular opinion on WMF development practices, may result in me having my account blocked or being black-listed as a critic. -- (talk) 15:00, 13 August 2014 (UTC)
Don-kun, you are right. The need to improve how software changes are developed and introduced was one of the first things Lila noted when she joined. It is unfortunate that this conflict arose before those changes could be put in place, as staff have been thinking about ways to fix such rollouts, even as it developed. I hope that we can resolve such things more quickly, and with more humility and mutual respect.
Dissenting voices are not only welcome, they are necessary to a community of critical thought. We experiment, fail, try again, and discover through trial and error, discussion and criticism and debate. Noone sharing complaints is being nor should be accused of disruption, vandalism, or spam. (unless they are deleting pages to make a point, 'spamming' talk pages to the annoyance of those users, &c.) SJ talk  06:56, 4 September 2014 (UTC)
For years, critics, including constructive ones, who did not "deliberately disrupt, vandalize, or spam," have been suppressed, blocked, banned, or marginalized, and those whose personal interests were not affected looked aside and did not intervene to protect whistle-blowers and other minorities. And now the bell tolls for them, and they wonder how this could happen. Structurally, what is happening was totally predictable, even boringly ordinary, as was the ED's first response. To the ED, I suggest: time for the extraordinary. You can do it. Show us. --Abd (talk) 15:33, 13 August 2014 (UTC)
I second the input by Matthiasb. Several critical points have already been voiced adressing individual board members (e.g. Phoebe) and especially also Lila. A very large group of the most active users of english- and german-speaking wikipedia, wikicommons and other projects feel very strongly offended by recent developments. Many see this as a breaking of fundamental principles governing the relationship between WMF and communities in general (among them, #4 and #7 of these). We expect the Board to intervene and work towards a resolution (for immediate steps to take, see [8]), hopefully winning back some of the users that have already left the community WMF had formerly been a part of or announced to do so, should such inacceptable circumstances prevail. Ca$e (talk) 10:45, 14 August 2014 (UTC)
That's like telling "Fuck Off" to the Wiki community. We on Commons are plagued by lots of long standing Wiki Software issues but instead of fixing them they waste money on BS software like media viewer just to be more like Flickr or Facebook. The Software devs mainstay should be the proper functionality of the Wiki Software but not releasing this Alpha Software which often violates Attribution requirements of images and could cause legal issues.--Denniss (talk) 20:38, 14 August 2014 (UTC)

Questions left over from Wikimania Board Q&A

Following are the two questions that were not answered during the Board Q&A at Wikimania. The original page with some more questions and answers can be found at:

=== Fundraising ===100claas since ans ouestions

I'm quite interested in the fundraising situation in the United Kingdom with the Wikimedia Foundation and Wikimedia UK, specifically the board's decision to not renew Wikimedia UK's fundraising agreement, and the loss of approximately $500,000 (at current exchange rates) of Gift Aid funding (a UK Government incentive, explained at Will the Wikimedia Foundation be renewing the fundraising agreement with Wikimedia UK, or will they form an overseas subsidiary in the UK to enable the collection of Gift Aid receipts. Does the board agree that the loss of such a significant sum is regrettable, that its collection must be investigated as a priority, and that such a sum could create significant benefits to the movement around the world.

It seems odd that at all levels the WMF was openly and publicly praising the UK chapter during Wikimania, and yet this nuts and bolts question of why so much of the donor's money is actively thrown away is skipped over. Wikimedians need not just draw their own conclusions, they can read Jon Davies' (WMUK Chief Executive) open letter to Sue Gardner in May 2014. If nothing is ever said by the WMF, then a fundamental lack of trust in WMUK's competence to manage fundraising must still be a core problem, despite the last 3 years of negotiation, expensive consultants and politics, this lack of trust costs the movement $500,000 a year. If a change of management or leadership is needed to resolve this, maybe 3 years is long enough to decide on what action is needed?
Along with many other active Wikimedians who are focused on content creation rather than politics, I could find a huge number of worthy open knowledge projects that would deliver amazing value with these lost funds.
P.S. I did not raise the question and unfortunately I was unable to attend this session, being busy as a Wikimania volunteer on other stuff; my travel for my volunteer days cost £14, which I have yet to be paid, and at that rate you could fund around 250 volunteer years worth of effort from willing unpaid folks like me with this lost money. -- (talk) 13:31, 21 August 2014 (UTC)
Hello Fae, these extra potential funds are important. The WMF this year qualified for Gift Aid [via the UK Fund for Charities, something that was beneficial when we raised sponsorship for Wikimania. I am not certain how this might fit into the donation flow for individual donors, that is something worth clarifying. SJ talk  07:07, 4 September 2014 (UTC)
I suppose I need to declare an interest, in that as a UK taxpayer, WMF failing to collect Gift Aid has probably saved me one or maybe two pence. But having just read the letter referred to above, I find it odd that WMF would not bother to institute a UK-based process, whether it be via WMUK or some other vehicle, that would enable it to more effectively collect donations from the UK and claim the tex refund. Deltahedron (talk) 14:00, 21 August 2014 (UTC)
@Sj: It is possible we might be talking about different things. If the WMF will be able to claim gift aid in the UK, that sounds great, as it will make a huge difference to the impact a donor's money can make, particularly if Wikimedia UK is never to be recognized again as a funds processor for the WMF. Do you have a link to point to where this is explained further? -- (talk) 07:57, 4 September 2014 (UTC)
To be frank, I don't see how this can be quite right. Charities have to be based in the UK, EU, Iceland or Norway to qualify [9] and as far as I know the WMF is not. Deltahedron (talk) 17:19, 4 September 2014 (UTC)
The [UK Fund for Charities channels gifts to validated non-UK based charities. We were able to use their service this year for large Wikimania-related donations. They charge 1% for large gifts, making this an effective way to receive gift aid. However this is not a great solution for individual donors: for gifts under £100, they charge up to 20%, consuming most of the gift aid. This works for small donations as well: they calculate the fee based on total gifts in a year. While they charge £20 of the first £100 donated in a year, this quickly tapers off to 1%. SJ talk  21:33, 8 December 2014 (UTC)


  1. Last year the WMF Board passed what is facetiously known as the Pricasso Resolution/Amendment. To date only 2 images have been deleted from Commons due to this resolution, whilst numerous other images have been kept. Both images deleted are of Jimmy Wales. Part of that resolution states: "Treating any person who has a complaint about how they are portrayed in our projects with patience, kindness, and respect, and encouraging others to do the same." The other day, the WMF published notices that they had received from Google under the "right to be forgotten" program. Included in these notices was an image which was hosted on English Wikipedia (not linking to it here so as to not increase the poor guys Streisand Effect). The article the image was uploaded for was deleted (likely a vanity article), but the image, oddly, remained. Wikipedia is a massive bureaucracy, and the person in question may well not have known how to go about getting the image deleted.
    The WMF's opposition to the EU laws that requires Google to remove some items from its search results in the EU is well known. My question is as follows:
    • 1) Do you think the WMF should have considered the Streisand effect as it relates to this image before it dumped the Google requests into the public domain, which has ended up being reported widely in the media? Can you please also comment on whether that action complies with the Pricasso Resolution; in particular being kind and respectful towards people with complaints about images of themselves.
    • 2) An editor on English Wikipedia placed that image on the "Right to be forgotten" article and then began a discussion on Jimmy Wales' English Wikipedia talk page with a section entitled "Right to remember". He stated: "The photo was up for deletion on Wikipedia. I've put it in the Right to be forgotten article. It should also be moved to Commons and put in a new (?) Category:Right to be forgotten. Perhaps all the other articles should be put in a Wikipedia category, or maybe a List of articles subject to "right to be forgotten" requests. Please remind me if I forget." Jimmy Wales retorted on the actions of this editor: "This strikes me as POINT-y and cruel". Could you please comment on whether the Board agrees with Jimmy's comments and whether the actions of the editor are inline with the Pricasso Resolution.
    • 3) What can the WMF board do so in that future people such as the person who filed a "Request to be forgotten" with Google are afforded the same "patience, kindness, and respect" that the Board extended, and expected the community to extend, to Jimmy Wales in relation to the Pricasso video.
It is hard to answer a question that begins and ends with trolling. SJ 07:07, 4 September 2014 (UTC)
… or you can just do your job and answer the questions. odder (talk) 19:39, 4 September 2014 (UTC)
It is hard to see the substantive question hidden within the mistaken information and rhetorical questions. For faster responses, it would help to reword and restate such things briefly. I will try:
We should take care in publishing this sort of information, to respect the dignity and personal privacy of people who might be affected. RTBF can be problematic when it helps hide information about disasters or crimes or difficult political topics. But in other cases it helps to (imprecisely) identify complaints about project content that the community might normally address and remove. In those cases we should improve the content; and may want to avoid publishing the request to avoid spotlighting it.
A community review could help here: OTRS already has decent practices around dignity and privacy. A queue for reviewing RTBF notices before they are published could help decide whether there is a reason not to do so.
An aside on views and actions: the Board is composed of individuals, and in general has individual views, prominently including Jimmy's. Issues such as "how to handle RTBF notices from Google" are not Board decisions, though individually we share our perspective including potential ways forward. SJ talk  01:19, 24 October 2014 (UTC)

@Sj: we are still waiting for an answer to this question. Any chance you can nudge the board on this issue thanks. Russavia (talk) 16:09, 5 October 2014 (UTC) @Sj:, pinging you here for an answer from the Board in relation to Wikimedia_Foundation_Board_noticeboard#Images. Two months have now passed and the question has gone unanswered. It's a tough question to answer, I know, given that the Board went out of its way to pass the Pricasso Resolution. The Board's silence on the issue of the right to be forgotten images is even worse given that Jimmy himself stated:

Morally, we should treat this as a complaint about our content that Google passed along to us to deal with. There will be more notices from Google and some of them will be worth fighting. This is not one. This is just a pointless image.

And this ties into the Pricasso Resolution directly, where the Board has stated:

Taking human dignity and respect for personal privacy into account when adding or removing information and/or media, especially in articles or images of ephemeral or marginal interest


Treating any person who has a complaint about how they are portrayed in our projects with patience, kindness, and respect, and encouraging others to do the same.

Is it yours, and the Board's, belief that the person in question was treated with patience, kindness and respect, when the WMF made the decision to dump his name into the public domain, knowing full well that the media would jump upon the information and disseminate it more widely.

This is ever so important given that WMF Legal have stated that the WMF will be exploring more legal options to fight what they say is a crude implementation.

I don't know about others, but it is my opinion that on the issue as it relates to this individual, that the WMF is ethically bankrupt, and has acted in a most morally reprehensible way.

Will the Board answer this criticism, or will it, and you, continue to bury your heads in the sand? Russavia (talk) 10:51, 14 October 2014 (UTC)

Replied above. SJ talk 

Split vote

What happens if the board vote on a resolution is split 5 support and 5 oppose? The bylaws state a majority is needed. I'm guessing a split 5:5 vote isnt a majority, and the motion doesnt carry, but would appreciate a board member or their staff assistants confirming that this is the commonly understood interpretation of the board members. John Vandenberg (talk) 21:13, 6 September 2014 (UTC)

Hello John, that is correct: a majority of a quorum is needed, which means 6 votes in favor at a 10-person meeting. SJ talk  00:28, 13 October 2014 (UTC)
I'm in neither of those groups, but a 5-5 split never passes a motion in any organization. Not only does the definition of "majority" always require more than exactly half the votes, but it isn't practical: Imagine that you put up a motion to do A, it receives 5-5 votes, and you declare that the organization must do A because your motion 'passed'. Then I put up a motion saying to do not-A, and it also receives 5-5 votes, and I declare that the organization must do the exact opposite, because my motion 'passed', too.
By the way, to avoid this situation, it's customary in most organizations for the chair to not vote unless the chair's vote is needed as a tiebreaker. This is relevant even when the board has an odd number of members, because you can't guarantee that every board member will be present for every vote. I don't know whether the current WMF board follows this custom. WhatamIdoing (talk) 01:29, 7 September 2014 (UTC)
You wrote that "a 5-5 split never passes a motion in any organization". This is not correct. I would argue that the Swedish parliament is an "organisation", and there the outcome is determined by a lottery if "yes" and "no" both receive exactly the same number of votes, so a 5-5 split vote would sometimes pass. See also sv:Lotteririksdagen. --Stefan2 (talk) 20:30, 7 September 2014 (UTC)
Apart from the technical reality (thanks for the link below :) the Board does not seek to have a unanimous vote, but we try to get a clear majority, if prolonged discussion is unlikely to move us away form 6-4 votes (to 7-3) then we let it rest, but otherwise we will probably continue. As far as I can recall we have never had a 5-5 situation... but I might be wrong... Jan-Bart (talk) 15:48, 3 October 2014 (UTC)

Hi Jan-Bart, after a month you respond, but did not answer my rather simple procedural question.

What happens if the board vote on a resolution is split 5 support and 5 oppose?

Most organisations have procedures in place that cover this precise situation, and situations like it. I have yet to see any link which explains how the WMF board is expected to act when it happens. John Vandenberg (talk) 03:56, 4 October 2014 (UTC)

I thought the answer was clear, we do not have a formal procedure, and so far have not needed one. Jan-Bart (talk) 11:21, 8 October 2014 (UTC)