Talk:Terms of use/Archives/2012-01

Latest comment: 12 years ago by Geoffbrigham in topic practical example

Customised version of the summary for each project

addressed

This follows from the discussion above re adding an intro to the summary but it's a slightly different proposal so I'm putting it in a separate section.

The English language terms of use is carefully crafted to apply to all the projects. Even if some projects have a translation nevertheless it is the english original which applies.

Given this perhaps we should encourage the language editions to just translate the summary - not the entire Terms of use. While we are about it we could customise the summary to refer to the project where it is linked from by name instead of saying 'project'.

  • Contribute to and edit English Wikipedia and our other projects.
  • Terms of use - you adhere to the Terms of use and to the policies of English Wikipedia and our other projects.

(and should 'adhere to the' be changed to 'comply with these'?)

The bit in italics being customised to suit--Filceolaire 20:41, 23 December 2011 (UTC)

Personally, I think it's important that the full document be translated for various communities. Even if the English document is the official version, it's better than not giving them access to the document at all, I think.
Even if translation were limited to the summary, I'm not sure specificity is a good idea. Looking at English projects along, we have Wikibooks, Wikiversity, Wikinews, Wikiquote, Simple English Wikipedia, Wikispecies, and the multilingual Meta and Commons. (I've probably forgotten somebody; sorry!) Singling out Wikipedia might make some of those other communities feel marginalized, I fear. --Maggie Dennis (WMF) 20:59, 23 December 2011 (UTC)
That's right. There is no reason to single out English wikipedia. Seb az86556 21:01, 23 December 2011 (UTC)
What I meant was that each project should have their own customised version of the summary with the words shown in italics above changed to match the project. Filceolaire 00:07, 24 December 2011 (UTC)
There is an argument, previously articulated, that each Project should have the right to modify the human-readable version according to the needs of that Project. To be honest, I don't like that idea, since I prefer uniformity, and I'm afraid we could confuse people if we use different language on different Projects to say the same thing. I frankly think that the human-readable version is the most important part of this TOS process, so I would want us to be extremely careful about changing its language to avoid mistakes and confusion. That said, I will not go down in flames over this issue. :) If, through community consensus, we decide to modify the human-readable version for each Project, I propose we allow the Projects to do so on their own after the Board passes the TOS. Also, if we were to do this, I would like to have the right to review for any legal flaws. (Just being a lawyer here.  :) ) Thanks Filceolaire and others for your comments. Geoffbrigham 22:17, 24 December 2011 (UTC)
All I'm suggesting is that the name of the project be included.
Imagine a user on one of our sites - say English Wikiversity. They click on the Terms of use link and get taken to a page headed Wikimedia Foundation. What's that? Who are they? Where are the TOU for Wikiversity?
Including a placeholder for $PROJECT_NAME_HERE to be inserted into the human readable version doesn't seem unreasonable.
Add "$PROJECT_NAME_HERE is a Wikimedia Foundation (WMF) project." at the start. (On this wiki this would become:META WIKI is a Wikimedia Foundation (WMF) project.)
Then change Part of our mission is to: to Part of the WMF mission is to: and most of the confusion will be gone.Filceolaire 23:56, 24 December 2011 (UTC)
OK ... I see that. Let's hear what others say, but I can see this working. Geoffbrigham 14:26, 25 December 2011 (UTC)
I don't think this is an important change, but I have no objection, particularly if it can be handled via some sort of metasyntactic variable so that it's never necessary for the local community to manually change anything. I believe that {{SITENAME}} might be the right variable for this purpose. WhatamIdoing 01:25, 29 December 2011 (UTC)
Currently, the Terms of Use are centrally located. If a project wants to create its own summary and include its name, I wouldn't see that as an issue. But if you press "Terms of Use" (or "terms of use") on Meta or on English Wikipedia or Commons or Wikiversity, you wind up at the same page. WhatamIdoing undoubtedly will know better than I if it is technically feasible to change the display of a page on the Wikimedia Foundation wiki according to its referring project, but if it does not adjust for that, I'm afraid this may not be useful to most projects as they will probably not be creating summaries of their own. --Maggie Dennis (WMF) 19:40, 29 December 2011 (UTC)
Most projects do not use English so most projects will be creating a translation of the summary into their own language (even Simple Wikipedia may want to do this). It is probably worth making a translation of the TOU summary into the language of the Wiki an essential part of the localisation to be done before a project gets out of the incubator. So a solution will have to be discovered for these which can then be applied to the English language projects. Filceolaire 21:17, 29 December 2011 (UTC)
Let me make sure that I'm following you: most languages have multiple projects; does each project need its own summary? For instance, do the ~8 projects that use Spanish as their sole language each need to host their own summaries in order to display their project's name in the header? Or are they able to share one Spanish summary? Do multilingual projects like Wikiversity Babel, Commons, Meta, MediaWiki, etc. need to host copies of the summary in multiple languages, so that they can be personalized to their project? Currently, documents are hosted on Foundation Wiki, with all languages being hosted there and users able to view by language rather than project. For instance, the privacy policy carries a bar across the top with listings of every language in which it is currently published. While including the name of the project that referred the user may be a nicety, I think unless it can be done automatically we seem to be talking about a lot of redundant labor. --Maggie Dennis (WMF) 21:31, 29 December 2011 (UTC)
Yes. I am proposing that each language edition of each 'Project' have it's own summary of the TOU so that when you click on the link on the bottom of the page or below the edit box, you get a summary that is customised for the project you are on. There may even be a case for including a summary of (or a link to) the project policies (the 5 pillars for Wikipedias for example) so the poor bastard who finds himself on this page can find the info he wants. Filceolaire 11:46, 30 December 2011 (UTC)
While making the policies more easily accessible sounds like a good idea, I suspect that there would be some opposition to having our Terms of Use summary include summaries of local policies, as we would definitely lose uniformity. Beyond that, local hosting would create a small amount of extra work for some projects (the French Wikipedia, Wiktionary, Wikiquote, Wikibooks and Wikisource can easily share a summary if the only value is putting their own name on the top) but a tremendous amount of extra work for others (we currently have about ~280 languages with active projects; that's a lot of summary translations for, say, Meta, Commons, MediaWikia, Srategy Wiki, Wikiversity Babel and other international projects to try to host! :) We haven't been able to reach full translation even on the Wikimedia Foundation wiki.) I wonder if the easier way to get the local policies front and center for users is to propose a uniform kind of "five pillars" page under some title or the other and perhaps include a link to it in the text below "save page" that begins "If you do not want your writing to be edited and redistributed at will...." or as a standard link in the toolbar on the left of the page. --Maggie Dennis (WMF) 12:49, 30 December 2011 (UTC)
I'm wondering if we could solve some of the issues by simply taking out the words "Wikimedia Foundation" in the title of the "human-readable" version. Let's just label it "Terms of Use." (Maggie, can you make that change?) That way, the summary is adaptable to all sites without a confusing title that includes a bizarre organization (WMF). The more I think about it, the more I think the summary should stay uniform, but I also think we can make that decision later. If certain projects want to change the summary, they can run their proposed changes by WMF and we can consider at that time. We would need to put something into the Board resolution however that would allow those modifications without Board approval. Geoffbrigham 18:03, 30 December 2011 (UTC)
Will do. --Maggie Dennis (WMF) 18:57, 30 December 2011 (UTC)

That will still leave this clause in the summary:

Terms of Use — You adhere to the Terms of Use and to the policies for each project.

Perhaps this could be rewritten as

Project policies - In addition to these Terms of Use you also comply with the policies
which have been developed by our community of volunteers for the various Projects and for their
 different languages editions.

Filceolaire 14:35, 31 December 2011 (UTC)

Strikes me as too bulky. How about: "Terms of Use and Policies - You adhere to the Terms of Use and to the policies applicable to the relevant Project edition."
If you agree, I will ask Maggie to make this change. Cheers. Geoffbrigham 23:34, 31 December 2011 (UTC)
It seems bulky to me too but this summary is aimed at the noob who doesn't know any other project exists apart from the project where he clicked on the link to this page. Up to this point, as far as he or she can tell these are the TOU for that project. This clause is meant to tell him or her that these Terms of use are just a part of what he or she needs to comply with.
I put "Project Policies" in the heading because this clause is about them.
I put "In addition to these TOU" to make it clear that the TOU referred to in this clause is this very document - otherwise that isn't clear.
I mentioned the policies are developed by volunteers to make clear how the policies are different from the TOU
I put "Projects and their different language editions" because "Projects" are not mentioned elsewhere in the summary and I wanted to be clear what we are referring to. I'm assume you use "project edition" to refer to a Wiki which has it's own policies but that is not clear or obvious. Filceolaire 05:19, 1 January 2012 (UTC)
OK. I want to keep it simple and limited to one bullet point, but I see your points. It doesn't do everything, but how about this:
"Terms of Use and Policies - You adhere to the below Terms of Use and to the community policies written for the particular site that you visit."
Geoffbrigham 04:17, 3 January 2012 (UTC)
How about
"Site Policies - You comply with these Terms of Use and with the community policies of any of our sites that you visit and contribute to."
Filceolaire 16:18, 3 January 2012 (UTC)
Something like this would handle the concern above:
Follow policies — You follow these Terms of Use, and Community Policies for our individual projects, when visiting our sites or participating in our communities.
But the whole "Local policies" thing seems a big problem and we have to avoid it this way. See below. FT2 (Talk | email) 17:11, 3 January 2012 (UTC)
OK, this is the text I will ask Maggie to insert:
"Terms of Use and Policies - You adhere to the below Terms of Use and to the applicable community policies when you visit our sites or participate in our communities."
To let everyone know, we have finalized the document. All other comments are post-deadline, so, in fairness to those who participated within the comment period, I would like to bring this to a close. Many thanks. Geoffbrigham 13:37, 4 January 2012 (UTC)
I proposed a couple of times above that we change "adhere to" to "comply with" but you didn't respond. Is there a reason not to change this?
Remember this is the human readable version to be translated into 280 languages. If we use "adhere" then some of these translations will end up with the policies glued to the users.
and that's my last comment!Filceolaire 17:00, 4 January 2012 (UTC)
If you promise it is your last comment, I will change to "comply with."  ;- Many thanks, Filceolaire. You were a great value in this discussion. You saw things that my tired eyes would have never caught or my weak mind would have never thought of. Cheers. Geoffbrigham 23:56, 4 January 2012 (UTC)
. :) Filceolaire 01:27, 5 January 2012 (UTC)

Second concern in this area

The whole thing about "You must adhere to TOU and any local project policies" (however it's worded) raises a second, much more serious, concern. Responsible users will probably ask (and others will surely wonder) "where are the policies". Anyone who knows a project like English Wikipedia know how badly and immediately this might overwhelm or confuse a newcomer and put them off before their first edit. I guess many other projects are the same.

While short versions exist, newcomers almost inevitably meet some point they didn't know about, often badly. There's no hope of fixing this in the short term. So although we want to, we realistically can't say "follow community policies" in the summary because if asked we can't necessarily list what those are.

I think there's a way round it that's better in all ways. At least, pragmatically. The basic premise of Wiki is that if a user acts sensibly they should be able to learn local policies piecemeal (eg from other users when they get it wrong). So maybe try this as an alternative approach which needs refining and shortening, but in principle it's at least much more workable and points newcomers the right direction:

Follow policies — You follow these Terms of Use. In addition, [when visiting our sites or participating in our communities,] you carefully note any comments from other users explaining our other Policies, and try to follow them.

FT2 (Talk | email) 16:43, 3 January 2012 (UTC)

I think what we've got is okay. No, we can't feasibly provide links to the local community's policies when we're on a page at a different website. But we can let them know that local policies exist, and let them use the local resources (e.g., search tools and welcome messages) at each project to find them. WhatamIdoing 22:11, 3 January 2012 (UTC)
Saying "You must follow" something that we can't explain when asked is a dead end. Our policies ("complex undefinable walls of text") also form a major deterrent for newcomers, even before we put them in a summary that newcomers are asked to agree to.
It's much better to say "If users say a policy exists, take careful note", which has exactly the effect we want, and is also completely reasonable. It means as they edit, they aren't encumbered or told "learn all this first". If they get told something's not okay, we don't allow that, that's when they need to know the relevant policy - it covers all policies, of any kind, that they knock into. As soon as they need to know something in a policy, it's very likely a user will tell them.
Follow TOU and heed what others tell you. That's all we actually need to ask of them, and it's so much easier. FT2 (Talk | email) 00:02, 4 January 2012 (UTC)
I'm fine with the present language. We tell users that they "should" follow the policies (Overview), and we explain enforcement mechanisms if they don't (Section 10). We also see similar language in other user agreements. See, e.g., eBay ("When using particular services on our sites, you are subject to any posted policies or rules applicable to services you use through the sites, which may be posted from time to time. All such policies or rules are hereby incorporated into this User Agreement."); Yahoo ("when using particular Yahoo! owned or operated services, you and Yahoo! shall be subject to any posted guidelines or rules applicable to such services, which may be posted and modified from time to time"). Finally, though I appreciate their thoughtfulness, these comments are beyond deadline. It would be unfair to those following the conversation previously to change the document significantly at this time. Geoffbrigham 14:07, 4 January 2012 (UTC)
FT2, we can "explain when asked". What we can't do is provide a single, magic link in this document that will take the user to the complete list of all relevant (and only relevant) policies. They'll actually have to go to the trouble of asking if they want an explanation.
Besides: how many times have you seen a user assert nonsense and claim it's a policy? If you want an example, check the recent archives on this page, where the user is pretending that his persistent block evasion is okay, because he doesn't believe that the block was legitimate in the first place. "Trust that 100% of other users know what they're talking about" is IMO a bad idea. WhatamIdoing 17:10, 4 January 2012 (UTC)
I don't think we can explain. For this purpose, I'm going to be a good-faith newcomer. I read the TOU summary. (Most newcomers won't read the full document, which is fine as long as they accept they are bound by it). It says I must comply with TOU - fine - and project policies. So I ask "what are project policies".
What's your answer to me? A wall of text that scares me off? A statement that you can't explain but I'll find out when I bang into them? A simplified version that when I find one of 10,000 other policies or arcane rules I feel aggrieved you didn't tell me? Links to a list of policies that I go "oh my god, I can't read that"? It just doesn't work.
Now take a step back. Forget we're drafting TOU here. Go back to wiki-basics in the hypothetical golden days when there were 20 policies 1/2 a page long (I think that was about January 16 2001!) and "use commonsense and enjoy contributing" was the golden rule of wiki. The rule then – and unlike many rules, this one hasn't changed at all in 11 years – is that we invite users to edit in good faith without worrying, and if they happen to do something wrong, we'll tell them. At that point we expect them to take the point on board, be it "avoid original research" or "don't make personal attacks", whatever it is.
Even in en:wp, the wiki with the most intricate and inchoate rules of all, TOU forbid the core "wrongs". There is literally nothing a user can do, if they are complying with TOU, that would get them a summary block/ban without at least a warning saying "that's not okay, please don't do that, this is the policy we have". So let's take advantage of that and think laterally.
The aim is they comply with policies. Rather than say "comply with policies" which is what we want but doesn't help them (newcomers can't check out all policies, they will often be disheartened and give up if they try, and they have no idea how they work in practice), why not tell them comply with TOU (which deals with the egregious "instant ban" things like vandalism, harassment, malware, illegal material, privacy breach, copyvios, etc), and from then on, just heed what other users tell them and try to follow policies when they are told about them. That achieves the exact end we're after - anything that's a problem is either in TOU or they'll get a user post saying what they need to take note of for future. if they don't hit a problem they don't yet need to know our policy. For example, a user who doesn't post copyvios or doesn't make personal attacks anyway might enjoy reading copyright or NPA policy but is in compliance with these policies even if they never read them. That user, posting a copyvio or making an attack, and warned about it, that's the point they need to know there's a policy and take heed. Until then, why burden them with the policies we have that may never matter to them (and if they do they'll hear about it at the time anyway).
Hence my logic. FT2 (Talk | email) 17:55, 4 January 2012 (UTC)
It's not that complicated, even on the English Wikipedia. The new user says, "What are the policies?" And we reply, "All the policies are listed in en:Category:Wikipedia policy." We might go on to suggest a trip through en:Wikipedia:Introduction or the like, but once you're on a specific project/edition, identifying the actual policies is very easy. WhatamIdoing 16:48, 6 January 2012 (UTC)
Please, just tell me you understand how offputting and singularly unhelpful that link would be...? FT2 (Talk | email) 15:28, 7 January 2012 (UTC)
In case someone really explicitly asks, that is the helpful and comprehensive answer. If I go to a restaurant and ask for their nutritional information, I expect to be handed a complete table with all the values and percentages; otherwise I wouldn't ask. I certainly wouldn't want to hear "oh, yeah, I think there's, uhh, let's see, some fat in it, and probably some sugar, but why don't you just try it and see what happens?" Seb az86556 18:04, 7 January 2012 (UTC)
We're discussing blocks and bans here; that example is closer to discussing style or simple content edits. If you were going to visit some country and there was a warning at the border Be aware you must follow our laws here. Some laws could result in you being executed, paying unlimited fines, or having your possessions confiscated, you'd be very unhappy with a "why not just try it" answer. If you asked for details and were handed a convoluted 500 page "legal code" which seems to have an incredible range of topics, new stuff added or appear at random and lacked a clear summary, would you be reassured and as likely to visit? Not I.
By contrast change the notice to Please follow these basic points (TOU) and if you are told an action of yours is against our laws, please pay attention, it's much easier.
That said I can live with Geoff's wording. Just responding here to clarify the difference, in case this discussion (currently left open) resumes. FT2 (Talk | email) 17:13, 12 January 2012 (UTC)
Sorry Geoff. I'm back again. I went back to check exactly what the Terms of use say about project policies.
The Summary says:
Terms of Use and Policies — You adhere to the below Terms of Use and to the applicable community
policies when you visit our sites or participate in our communities.
Section 11 Resolutions and project policies says
The Wikimedia Foundation Board of Trustees releases official policies from time to time.
Some of these policies may be mandatory for a particular Project or Project edition, and,
when they are, you agree to abide by them as applicable.
I can't find anything outside the summary about the "community policies" (i.e. developed by the comunity; not the policies imposed by board resolutions. I think section 11 needs to be expanded a bit so that, at the very least, it covers the same ground as the summary. I would like FT2's proposed wording included too.
Please follow these basic points (TOU) and if you are told an action of yours is against
our laws, please pay attention.
or maybe this should be in section 4. Filceolaire 17:25, 21 January 2012 (UTC)

I think we are fine with our present draft (which is with the Board). Remember that the summary is not binding and is meant as simply a high-level guide. The summary only refers to "applicable" community policies. We mention the importance of community policies in the Overview section and Section 10. For example, we say in the Overview section: "The community undertakes the critical function of creating and enforcing policies for the specific Project editions (such as the different language editions for the Wikipedia Project or the Wikimedia Commons multi-lingual edition)." In Section 10 we say: "The Wikimedia community and its members may also take action when so allowed by the community or Foundation policies applicable to the specific Project edition, including but not limited to warning, investigating, blocking, or banning users who violate those policies." Section 11 is intended to be restricted to Board resolutions (i.e., Foundation policies). So I think asking in the summary that the user adhere to the TOS and "applicable" community policies captures our points at a high level. Every year or so, we may wish to consider amendments to the TOS, and, if we find this is not working, we always can put it on that list of things to change. Thanks for the discussion. Geoffbrigham 11:42, 30 January 2012 (UTC)

practical example

On the English Wikipedia we have a practical example being raised as to how the terms of Use will change policy making. en:Wikipedia_talk:Follow the_principle_of_least_astonishment#If_you reject_the_Resolution.2C_you_are in violation_of_WMF.27s_.28future.29_Terms_of_Use.2C_and_thus_you_may_be_banned. I think I know the answer. But please could we have clarification from the WMF as to whether these terms of use mean that we will have to accept Foundation policy decisions without discussion, and whether editors will be banned for breaching such Foundation policy, for not enforcing it or for arguing against it? Thanks. WereSpielChequers 13:54, 11 January 2012 (UTC)

http://en.wikipedia.org/w/index.php?title=Wikipedia:Follow_the_principle_of_least_astonishment&action=history – Disclaimer: The WMF didn't have a hand in crafting en:Wikipedia:Follow_the_principle_of_least_astonishment. In fact, the page appears to have been crafted by users partial to a related conflict. --Michaeldsuarez 15:31, 11 January 2012 (UTC)
IMO—and I realize that WSC is hoping for a response from a WMF staff member—it's clear in the TOU that:
  • all users need to comply with all relevant Board resolutions, including the POLA-related resolution,
  • the WMF staff has far better things to do with their time than to ban people over routine disputes (see "The community has the primary role in creating and enforcing policies applying to the different Project editions" and "We rarely intervene" and "We reserve the right to exercise our enforcement discretion with respect to the above terms", etc.), and
  • the WMF's focus is on "especially problematic users", which group is never going to include people like WSC, anyone involved in isolated incidents, or people making good-faith suggestions about how to improve or interpret the Foundation-level policies (even if the suggestion for "improving" a policy is "getting rid of it entirely").
People at en.wiki are likely to call this particular Board resolution "business as usual", by the way, since en.wiki is already generally anti-shock images and pro-educational value. The complaints about it appear to be specific to the one local dispute (which IMO the Board resolution doesn't prescribe any particular solution to, the hopes of the pro-POLA side notwithstanding), and the outrage of a very small number of users who suddenly discovered that the Board actually has the power to create policies for the Board's websites (as they have in multiple instances, usually dealing with serious legal issues).
I'd also like to second what Michael says: The particular proposed guideline (which is a surprisingly advice-free advice page) that WSC links to isn't the Board resolution. There is no requirement to support that particular proposal, and you will not find my name among its supporters. In fact, given its practically advice-free content, I'm not sure how anyone could either "comply with" or "violate" that page in practice. WhatamIdoing 18:16, 11 January 2012 (UTC)
Why are u so sincere, that u (and especially u) are allowed to talk in the name of the WMF? Did anybody give u the specific right to do so?--Angel54 5 20:04, 19 January 2012 (UTC)
I do not speak in the name of the WMF. WhatamIdoing 20:51, 21 January 2012 (UTC)
I think WhatamIdoing's points are useful in understanding this issue. Section 11 is the section that addresses Board resolutions. As explained in that Section, "[s]ome of these policies may be mandatory for a particular Project or Project edition, and, when they are, you agree to abide by them as applicable." However, in practice, the Board - which includes representatives from the community - is careful in its use of mandatory language in their resolutions, seeking instead consideration of certain factors by the community (without mandating adherence to them). See, e.g., BLP resolution ("urges the global Wikimedia community") & Images of identifiable people resolution ("urges the global Wikimedia community"). In the Overview section and Section 10, we emphasize (as pointed out by WhatamIdoing) that the community - not WMF - has the primary enforcement role. Section 10 says, for example: "The community has the primary role in creating and enforcing policies applying to the different Project editions." I believe this language indicates that we are not proposing a change in present practice; legally, WMF has always had the right to enforce policies, but, as a matter of practice, WMF leaves the daily management and enforcement to the community, given the importance and value of the community's expertise, judgment and wisdom. Section 10 in the TOS indeed solidifies the primary role of the community in the creation and enforcement of the policies. Geoffbrigham 12:09, 30 January 2012 (UTC)

The terms of use are now before the WMF Board of Trustees for consideration

After an internal review, WMF staff will be proposing no additional changes or amendments to the proposed terms of use. I therefore recommended that the Board replace the present terms of use with the proposed terms of use. That recommendation was forwarded to the Board today for consideration. Many thanks again for everyone's hard work on this project. Geoffbrigham 23:50, 24 January 2012 (UTC)

Communication sent to Board

 

Background

For more than 140 days, the Wikimedia community reviewed, drafted, and redrafted the terms of use with more than 200 edits modifying the original proposal. While accumulating 19,000 page views, community members offered comments, edits, and rewrites. Complete or partial translations appeared in 20+ languages. With over 4500 lines of text and as many words as Steinbeck’s classic “The Grapes of Wrath,” discussion helped ensure a thoughtful process. These proposed terms of use are intended to replace our present version. It is not commonly known that our present terms are nothing more than a licensing agreement, not traditional terms of use. The new proposed terms of use represent a step forward and a more comprehensive view of the Wikimedia projects. Among other things, they provide for:

  • Better understanding: The proposed agreement includes an easy-to-read template summary to help facilitate understanding of the terms.
  • Stronger security: The proposed agreement prohibits a number of actions – like installing malware – that could compromise our systems. We thought we should be clear as to what is unacceptable in this area, though most of these restrictions will not be surprising or represent any real change in practice.
  • Clearer roles: We have heard a number of community members asking for guidance, so we set out clearly the roles and responsibilities of the community, including editors and contributors. The proposed agreement also seeks to provide guidelines to help users avoid trouble.
  • More community feedback: With this version, and with each major revision afterwards, we want the community to be involved. So the proposed agreement gives users at least a 30-day comment period before a major revision goes into effect (with Board approval). There is a 3-day exception for urgent legal and administrative changes.
  • Clearer free licensing: We feel our present agreement is somewhat confusing on the free licensing requirements. The proposed agreement attempts to explain more clearly those requirements for editors (without changing existing practices).
  • More tools against harassment, threats, stalking, vandalism, and other long-term issues: The proposed agreement would make clear that such acts are prohibited. Novel for us, the agreement raises the possibility of a global ban for extreme cross-wiki violations, a need that we have heard expressed from a number of community members. While the global ban is authorized by the terms of use, it will be implemented by community policy.
  • Better legal protection: The proposed agreement incorporates legal sections that are commonly used to help safeguard a site like ours, such as better explanation of our hosting status as well as disclaimers and limitations on liability for the Foundation.

More detailed reasons why we are proposing updated terms of use are set out here. Suffice it to say, we are consistent with other like-minded organizations, which have incorporated similar agreements, including Internet Archives, Creative Commons, Mozilla Firefox, Open Source Initiative,Project Gutenberg, Linux Foundation, Stack Exchange, WikiSpaces, and Word Press.com.

Specifically, in its more than 320 printed pages of discussions, the community raised, discussed, and resolved more than 120 issues. There were many substantive and editorial changes that greatly improved the document. Much language was deleted or tightened at community request. As part of this process, the community addressed a number of interesting topics, such as:

  • Whether we should emphasize that the community (not WMF) is primarily responsible for enforcing policy: We agreed to underscore this primary responsibility of the community to avoid any confusion.
  • Whether we should include an indemnification clause to the benefit of WMF: We chose to delete it in light of community concerns.
  • Whether we should adopt a “human-readable” version to facilitate understanding: We agreed to incorporate such a summary.
  • Whether we should expressly prohibit linking to certain sites: We chose not to, deleting earlier language unacceptable to the community.
  • Whether we should require civility and politeness: With varying views, we decided to “encourage” it.
  • Whether the WMF should provide resources to support forks: We chose not to address this now, though we agreed to highlight the discussion to the Board for its consideration. *Please find the most relevant discussions on forking here and here.
  • Whether we should emphasize the independent roles of chapters: We chose to do so.
  • Whether we should increase the liability limitation for WMF from $100 to $1000: We answered affirmatively.
  • Whether we should provide for additional comment time after the posting of translations in three key languages: We said “yes” to address international community concerns.

Needless to say, this project would have been impossible without the hard work and expertise of our community. Through their tireless effort, the community mentored important and deep discussions on critical subjects for Wikimedia. The process forced us to think about issues that we had never addressed directly. In short, the value of collaboration quickly became obvious. Its magic created a document many times better than the original.

Many thanks to Philippe, Maggie, Steven, Michelle, Kelly, Matt, and others at WMF for their hard work on this project.

Proposed Resolution

As General Counsel of the Wikimedia Foundation, I hereby propose the following resolution for approval by the Board of Trustees of the Wikimedia Foundation: Resolved, that, upon recommendation of the General Counsel of the Wikimedia Foundation and upon review and consideration of the extensive community discussions on the subject, the Board of Trustees hereby approves to substitute the current terms of use, which is presently found here, with the proposed terms of use, which is presently found here.

If the Board would find it useful, I will be happy to discuss the proposed terms of use in detail during its February meetings. I do request approval of the new proposed terms of use at those meetings if the schedule of the Board so allows.

Regards,

Geoff

Geoffrey Brigham
General Counsel
Wikimedia Foundation

Preserved from automated archival. --Maggie Dennis (WMF) (talk)
Return to "Terms of use/Archives/2012-01" page.