Thanks for this clarification. Will this change effect the English version
of Wikipedia as well as Wikimedia Commons?

Jos

2017-03-01 20:03 GMT+01:00 Whatamidoing (WMF)/Sherry Snyder <
[email protected]>:

> Jos, where the button currently says "Save page", it will later say
> "Publish page".  Where it currently says "Save changes", it will later say
> "Publish changes".  (Even if you are blanking the page, when you click that
> button, you are making your version "available to the public", which is
> what "publish" means.)
>
> Gnangarra, in the languages that concern you, how do you currently handle
> descriptions of copyright and free licenses?  For example, how would you
> translate "Works published in the U.S. before 1923 are in the public
> domain" or the statement in the Terms of Use that says that part of the
> mission is to "empower and engage people around the world to collect and
> develop educational content and either publish it under a free license or
> dedicate it to the public domain" ?  The translators should be using the
> same concept for this button.
>
>
>
> On Wed, Mar 1, 2017 at 1:53 AM Martin Poulter <[email protected].
> ac.uk> wrote:
>
>> Personally, I welcome this change. Some trainees just do not pick up that
>> they are changing the live version of the site, even after lengthy
>> explanations and demonstrations: it just goes against their experience of
>> how the web works. Some very, very popular sites have this Save/ Publish
>> distinction. I see that there can be some confusion about "Publish" in
>> draft space, but I think people need to be reminded that creating or
>> altering a draft is making something visible to the public, unlike other
>> platforms in which you can create a "draft".
>>
>> Thanks for the explanation, Sherry.
>>
>> -----Original Message-----
>>
>>
>> Message: 1
>> Date: Tue, 28 Feb 2017 21:50:52 +0000
>> From: "Whatamidoing (WMF)/Sherry Snyder" <[email protected]>
>> To: Wikimedia Education <[email protected]>,
>>         "[email protected]" <[email protected]>
>> Subject: [GLAM] Changes to the 'Save' button
>> Message-ID:
>>         <CABaZQeg-iS2B__TYKimdwh5QefAVr5yNGVg9Qms-
>> [email protected]>
>> Content-Type: text/plain; charset="utf-8"
>>
>> *Nutshell:  The big, blue button will soon say "Publish page" instead of
>> "Save page", because when you click it, the contents get published on the
>> internet.*
>>
>>
>> I apologize for cross-posting this to the GLAM and Education lists:
>>
>> A long-requested change to the "Save" button may finally happen towards
>> the end of March.  This is a button that anyone leading a workshop about
>> editing is going to talk about, so I wanted to make sure that you didn't
>> get surprised by this change.
>>
>> Last year, the WMF looked into an old request to clarify the language on
>> the "Save" button, which confuses some new contributors.  The main problem
>> is that it is unclear whether "Save" means "save a private copy" (as it
>> does on most websites these days) or "irrevocably post this to the
>> internet".  This confusion apparently explains a few unwanted behaviors,
>> such as editors who save the page ("just to be safe") before previewing
>> their changes.
>>
>> There are some other reasons behind to do this:  It creates some
>> inconsistency in the interface, as some things (e.g., Special:Preferences)
>> get saved but kept private, while other things (e.g., normal wiki pages)
>> get saved and immediately published.  It is also difficult to translate the
>> label into some languages, as the word has multiple possible translations
>> in some languages.
>>
>> The plan, therefore, is to change "Save" to "Publish".  Instead of the
>> big blue[1] button saying "Save page" (for a new page) or "Save changes"
>> (when you edit an existing page), the button will instead say "Publish
>> page" or "Publish changes".
>>
>> The upside to this small change is that new contributors will understand
>> that all of their edits go to the public immediately.[2]  The downside is
>> that all of the documentation and help pages is going to be out of date.
>>
>> This plan was announced on the wikis last August, and is tentatively
>> scheduled for sometime in March.  I hope that this extra note will keep you
>> from getting surprised in front of a group and give you enough time to
>> update any handouts that you might be using in the future.
>>
>> Relevant links:
>>
>>    - https://phabricator.wikimedia.org/T131132 – main task (best place to
>>    figure out if this gets postponed again)
>>    - Special:Translations&message=Publishpage
>>    <https://translatewiki.net/w/i.php?title=Special:
>> Translations&namespace=8&message=Publishpage>
>> (translation
>>    status)
>>    - Special:Translations&message=Publishchanges
>>    <https://translatewiki.net/w/i.php?title=Special:
>> Translations&namespace=8&message=Publishchanges>
>> (translation
>>    status)
>>
>>
>>
>> [1] The color of this button in all of the older wikitext editors will be
>> changing this week.  It's going to be big and blue.
>>
>> [2]  This is true even when the wiki is using FlaggedRevisions or
>> PendingChanges, because the un-accepted changes can be seen by the general
>> public from the history page or from &oldid URLs, regardless of whether the
>> revision has been accepted.
>>
>> --
>> Sherry Snyder (WhatamIdoing)
>> Community Liaison, Wikimedia Foundation
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <https://lists.wikimedia.org/pipermail/glam/attachments/
>> 20170228/391868fb/attachment-0001.html>
>>
>> ------------------------------
>>
>> _______________________________________________
>> GLAM mailing list
>> [email protected]
>> https://lists.wikimedia.org/mailman/listinfo/glam
>>
> --
> Sherry Snyder (WhatamIdoing)
> Community Liaison, Wikimedia Foundation
>
> _______________________________________________
> GLAM mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/glam
>
>
_______________________________________________
GLAM mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/glam

Reply via email to