Wikiversity:Babel
Wikiversity:Babel –
_-_Google_Art_Project_-_edited.jpg)
Contents
- 1 Pywikibot compat will no longer be supported - Please migrate to pywikibot core
- 2 VisualEditor News #3—2015
- 3 HTTPS
- 4 “Paid” contributions amendment: after a year
- 5 Proposal to create PNG thumbnails of static GIF images
- 6 What does a Healthy Community look like to you?
- 7 VisualEditor News #4—2015
- 8 How can we improve Wikimedia grants to support you better?
- 9 Introducing the Wikimedia public policy site
- 10 Open call for Individual Engagement Grants
- 11 Requests to sysops
- 12 Only one week left for Individual Engagement Grant proposals!
- 13 Reimagining WMF grants report
- 14 VisualEditor News #5—2015
- 15 Community Wishlist Survey
- 16 Wikimania 2016 scholarships ambassadors needed
- 17 Harassment consultation
- 18 Your input requested on the proposed #FreeBassel banner campaign
- 19 Community Wishlist Survey
- 20 VisualEditor News #6—2015
- 21 Wikimedia Year of Science
- 22 Wikimania 2016 Scholarships - Deadline soon!
- 23 Proposals for closing projects/Move Beta Wikiversity to Incubator
- 24 2016 WMF Strategy consultation
- 25 Wikiversity_Simple_English
- 26 language links via Wikidata are coming
- 27 Wikidata support is here!
- 28 Data visualizations and maps on Beta Wikiversity
- 29 VisualEditor News #1—2016
- 30 poll until March 31: Proposals for closing projects/Move Beta Wikiversity to Incubator
- 31 Install Extension:Simple Forms
- 32 Open Call for Individual Engagement Grants
- 33 Server switch 2016
- 34 Wikidata: access to the data is coming
- 35 Wikidata: data access is here
- 36 IMPORTANT: Admin activity review
- 37 States of Wikiversities
- 38 Compact Language Links enabled in this wiki today
- 39 Editing News #2—2016
- 40 Open call for Project Grants
- 41 Save/Publish
- 42 RevisionSlider
Pywikibot compat will no longer be supported - Please migrate to pywikibot core[edit]
Sorry for English, I hope someone translates this.
Pywikibot (then "Pywikipediabot") was started back in 2002. In 2007 a new branch (formerly known as "rewrite", now called "core") was started from scratch using the MediaWiki API. The developers of Pywikibot have decided to stop supporting the compat version of Pywikibot due to bad performance and architectural errors that make it hard to update, compared to core. If you are using pywikibot compat it is likely your code will break due to upcoming MediaWiki API changes (e.g. T101524). It is highly recommended you migrate to the core framework. There is a migration guide, and please contact us if you have any problem.
There is an upcoming MediaWiki API breaking change that compat will not be updated for. If your bot's name is in this list, your bot will most likely break.
Thank you,
The Pywikibot development team, 19:30, 5 June 2015 (UTC)
VisualEditor News #3—2015[edit]
Did you know?
When you click on a link to an article, you now see more information:
The link tool has been re-designed:
There are separate tabs for linking to internal and external pages. The user guide has more information about how to use VisualEditor.
Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools and fixed many bugs and changed some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on mediawiki.org. The worklist for April through June is available in Phabricator.
A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.
Recent improvements[edit]
Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.
The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and appropriate icons for disambiguation pages, redirect pages and empty pages (where applicable). Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector. (T98085)
The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter. (T70425)
Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "Add more information" each time they want to add another parameter. (T95696) The team added a new property for TemplateData, "Example", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter. (T53049)
The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.
The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.
Let's work together[edit]
- Share your ideas and ask questions at mw:VisualEditor/Feedback.
- The weekly task triage meetings continue to be open to volunteers, usually on Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker, though. Instead, go to Phabricator and "associate" the VisualEditor Q4 blocker project with the bug.
- If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
- If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
- The team is planning the second VisualEditor-related "translathon" for July. Please follow this task on Phabricator for details and updates! Announcements will follow in due course.
Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
10:44, 13 June 2015 (UTC)
HTTPS[edit]
Hi everyone.
Over the last few years, the Wikimedia Foundation has been working towards enabling HTTPS by default for all users, including unregistered ones, for better privacy and security for both readers and editors. This has taken a long time, as there were different aspects to take into account. Our servers haven't been ready to handle it. The Wikimedia Foundation has had to balance sometimes conflicting goals.
Forced HTTPS has just been implemented on all Wikimedia projects. Some of you might already be aware of this, as a few Wikipedia language versions were converted to HTTPS last week and the then affected communities were notified.
Most of Wikimedia editors shouldn't be affected at all. If you edit as registered user, you've probably already had to log in through HTTPS. We'll keep an eye on this to make sure everything is working as it should. Do get in touch with us if you have any problems after this change or contact me if you have any other questions.
22:00, 19 June 2015 (UTC)
“Paid” contributions amendment: after a year[edit]
First of all, I do acknowledge that I’ve already tried to bring this issue up on English Wikibooks, English Wikiversity, Russian Wikibooks and Russian Wikiversity – mostly to no avail. (The sole exception being Russian Wikibooks, where we formally approved an alternative paid contribution disclosure policy, which is a more or less an exact translation of the one approved earlier at the Wikimedia Commons.)
My concern is that the paid contributions amendment, which was effected little over a year ago, made Wikiversity – all of them at once – an educational resource the students cannot edit.
Now, I have to admit that I’m only familiar with the higher education system currently established in Russia, and have little to no knowledge whatsoever of how these things work worldwide. In Russia, however, a significant fraction of the students enjoy government-funded higher education, with the criterion to retain (or acquire) such funding being, roughly, getting course credits and passing exams. Moreover, depending on the grades, such students are also paid scholarships.
Thus, if a J. Random Student from Russia contributes to Wikiversity, it’s not unlikely that he or she does this to either retain or acquire government funding for the education, or get a scholarship, and thus must disclose his or her affiliation [school] with respect to his or her contributions – per wmf:Terms of Use.
While we at Russian Wikibooks opted to not require such disclosures, we are occasionally getting them anyway. For instance, in b:ru:Special:Diff/118695, the user has disclosed that her intent with her contribution (which was since deleted as not fitting the purpose of Russian Wikibooks) was “to get a course credit.”
My questions are as follows.
- Is it really deemed necessary for the students to disclose their affiliation (school) in the cases like this? If not, what alternative paid contribution disclosure policies could be considered to allow for better privacy of the students contributing to Wikiversities?
- What is the experience with the application of the current disclosure policy at Wikiversities (and other WMF projects)? How often are the required disclosures made? how often the respective edits are found “biased”, or otherwise “undesired”? how often are they used to make community decisions?
- Finally, how often such contributions go undisclosed (with the contributors found to be violating the ToU)?
Hope to learn of your opinion, and thanks in advance.
— Ivan Shmakov (d ▞ c) 19:17, 21 June 2015 (UTC)
Proposal to create PNG thumbnails of static GIF images[edit]
-3-phenyl-cyclohanone.gif)
-3-phenyl-cyclohanone.png)
There is a proposal at the Commons Village Pump requesting feedback about the thumbnails of static GIF images: It states that static GIF files should have their thumbnails created in PNG. The advantages of PNG over GIF would be visible especially with GIF images using an alpha channel. (compare the thumbnails on the side)
This change would affect all wikis, so if you support/oppose or want to give general feedback/concerns, please post them to the proposal page. Thank you. --McZusatz (talk) & MediaWiki message delivery (talk) 08:08, 24 July 2015 (UTC)
What does a Healthy Community look like to you?[edit]
Hi,
The Community Engagement department at the Wikimedia Foundation has launched a new learning campaign. The WMF wants to record community impressions about what makes a healthy online community. Share your views and/or create a drawing and take a chance to win a Wikimania 2016 scholarship! Join the WMF as we begin a conversation about Community Health. Contribute a drawing or answer the questions on the campaign's page.
Why get involved?[edit]
The world is changing. The way we relate to knowledge is transforming. As the next billion people come online, the Wikimedia movement is working to bring more users on the wiki projects. The way we interact and collaborate online are key to building sustainable projects. How accessible are Wikimedia projects to newcomers today? Are we helping each other learn?
Share your views on this matter that affects us all!
We invite everyone to take part in this learning campaign. Wikimedia Foundation will distribute one Wikimania Scholarship 2016 among those participants who are eligible.
More information[edit]
- All participants must have a registered user of at least one month antiquity on any Wikimedia project before the starting date of the campaign.
- All eligible contributions must be done until August 23, 2015 at 23:59 UTC
- Wiki link: Community Health learning campaign
- URL https://meta.wikimedia.org/wiki/Grants:Evaluation/Community_Health_learning_campaign
- Contact: María Cruz / Twitter: Template:@WikiEval #CommunityHealth / email: evalTemplate:@wikimediaTemplate:Dotorg
Happy editing!
MediaWiki message delivery (talk) 23:42, 31 July 2015 (UTC)
VisualEditor News #4—2015[edit]
Read this in another language • Subscription list for this multilingual newsletter
Did you know?
You can add quotations marks before and after a title or phrase with a single click.
Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).
Click the button. VisualEditor will add the quotation marks on either side of the text you selected.
You can read and help translate the user guide, which has more information about how to use VisualEditor.
Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.
Wikimania[edit]
The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.
Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.
For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).
For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).
We published some graphs showing the effect of the event on the Translathon page. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.
Recent improvements[edit]
Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.
Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.
Future changes[edit]
The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.
On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.
Let's work together[edit]
- Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
- Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mediawiki.org if you can help.
- If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
- Please file requests for language-appropriate "Bold" and "Italic" icons for the styling menu in Phabricator.
- The design research team wants to see how real editors work. Please sign up for their research program.
- The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
—Elitre (WMF), 02:40, 15 August 2015 (UTC)
How can we improve Wikimedia grants to support you better?[edit]
Hello,
The Wikimedia Foundation would like your feedback about how we can reimagine Wikimedia Foundation grants, to better support people and ideas in your Wikimedia project. Ways to participate:
- Respond to questions on the discussion page of the idea.
- Join a small group conversation.
- Learn more about this consultation.
Feedback is welcome in any language.
With thanks,
I JethroBT (WMF), m:Community Resources, Wikimedia Foundation.
(Opt-out Instructions) This message was sent by I JethroBT (WMF) through MediaWiki message delivery. 00:18, 19 August 2015 (UTC)
Introducing the Wikimedia public policy site[edit]
Hi all,
We are excited to introduce a new Wikimedia Public Policy site. The site includes resources and position statements on access, copyright, censorship, intermediary liability, and privacy. The site explains how good public policy supports the Wikimedia projects, editors, and mission.
Visit the public policy portal: https://policy.wikimedia.org/
Please help translate the statements on Meta Wiki. You can read more on the Wikimedia blog.
Thanks,
Yana and Stephen (Talk) 18:12, 2 September 2015 (UTC)
(Sent with the Global message delivery system)
Open call for Individual Engagement Grants[edit]
My apologies for posting this message in English. Please help translate it if you can.
Greetings! The Individual Engagement Grants program is accepting proposals until September 29th to fund new tools, community-building processes, and other experimental ideas that enhance the work of Wikimedia volunteers. Whether you need a small or large amount of funds (up to $30,000 USD), Individual Engagement Grants can support you and your team’s project development time in addition to project expenses such as materials, travel, and rental space.
- Submit a grant request
- Get help with your proposal in IdeaLab or an upcoming Hangout session
- Learn from examples of completed Individual Engagement Grants
Thanks,
I JethroBT (WMF), Community Resources, Wikimedia Foundation. 20:52, 4 September 2015 (UTC)
(Opt-out Instructions) This message was sent by I JethroBT (WMF) (talk) through MediaWiki message delivery.
Requests to sysops[edit]
Only one week left for Individual Engagement Grant proposals![edit]
(Apologies for using English below, please help translate if you are able.)
There is still one week left to submit Individual Engagement Grant (IEG) proposals before the September 29th deadline. If you have ideas for new tools, community-building processes, and other experimental projects that enhance the work of Wikimedia volunteers, start your proposal today! Please encourage others who have great ideas to apply as well. Support is available if you want help turning your idea into a grant request.
- Submit a grant request
- Get help with your proposal in IdeaLab
- Learn from examples of completed Individual Engagement Grants
I JethroBT (WMF), Community Resources 21:01, 22 September 2015 (UTC)
Reimagining WMF grants report[edit]
(My apologies for using English here, please help translate if you are able.)
Last month, we asked for community feedback on a proposal to change the structure of WMF grant programs. Thanks to the 200+ people who participated! A report on what we learned and changed based on this consultation is now available.
Come read about the findings and next steps as WMF’s Community Resources team begins to implement changes based on your feedback. Your questions and comments are welcome on the outcomes discussion page.
With thanks, I JethroBT (WMF) 16:56, 28 September 2015 (UTC)
VisualEditor News #5—2015[edit]
Read this in another language • Subscription list for this multilingual newsletter
Did you know?
Click the pencil icon to open the editor for a page. Inside that, use the gear menu in the upper right corner to "Switch to visual editing".
The editing button will remember which editing environment you used last time, and give you the same one next time. The desktop site will be switching to a system similar to this one in the coming months.
You can read and help translate the user guide, which has more information about how to use the visual editor.
Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.
Recent improvements[edit]
Educational features: The first time ever you use the visual editor, it now draws your attention to the Link and ⧼visualeditor-toolbar-cite-label⧽ tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.
Links: It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108, T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558) These "magic links" use a custom link editing tool.
Uploads: Registered editors can now upload images and other media to Commons while editing. Click the new tab in the "Insert Media" tool. You will be guided through the process without having to leave your edit. At the end, the image will be inserted. This tool is limited to one file at a time, owned by the user, and licensed under Commons's standard license. For more complex situations, the tool links to more advanced upload tools. You can also drag the image into the editor. This will be available in the wikitext editor later.
Mobile: Previously, the visual editor was available on the mobile Wikipedia site only on tablets. Now, editors can use it on all devices regardless of size if they wish. (T85630) Edit conflicts were previously broken on the mobile website. Edit conflicts can now be resolved in both wikitext and visual editors. (T111894) Sometimes templates and similar items could not be deleted on the mobile website. Selecting them caused the on-screen keyboard to hide with some browsers. Now there is a new "Delete" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.
Rich editing tools: You can now add and edit sheet music in the visual editor. (T112925) There are separate tabs for advanced options, such as MIDI and Ogg audio files. (T114227, T113354) When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.
On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Special:Preferences.
Future changes[edit]
You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, similar to the system already used on the mobile website. The "Edit" tab will open whichever editing environment you used last time.
Let's work together[edit]
- Share your ideas and ask questions at VisualEditor/Feedback. This feedback page uses Flow for discussions.
- Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
- Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
- The weekly task triage meetings are open to volunteers. Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
—Elitre (WMF), 18:18, 30 October 2015 (UTC)
Community Wishlist Survey[edit]
Hi everyone! Apologies for posting in English. Translations are very welcome.
The Community Tech team at the Wikimedia Foundation is focused on building improved curation and moderation tools for experienced Wikimedia contributors. We're now starting a Community Wishlist Survey to find the most useful projects that we can work on.
For phase 1 of the survey, we're inviting all active contributors to submit brief proposals, explaining the project that you'd like us to work on, and why it's important. Phase 1 will last for 2 weeks. In phase 2, we'll ask you to vote on the proposals. Afterwards, we'll analyze the top 10 proposals and create a prioritized wishlist.
While most of this process will be conducted in English, we're inviting people from any Wikimedia wiki to submit proposals. We'll also invite volunteer translators to help translate proposals into English.
Your proposal should include: the problem that you want to solve, who would benefit, and a proposed solution, if you have one. You can submit your proposal on the Community Wishlist Survey page, using the entry field and the big blue button. We will be accepting proposals for 2 weeks, ending on November 23.
We're looking forward to hearing your ideas!
Wikimania 2016 scholarships ambassadors needed[edit]
Hello! Wikimania 2016 scholarships will soon be open; by the end of the week we'll form the committee and we need your help, see Scholarship committee for details.
If you want to carefully review nearly a thousand applications in January, you might be a perfect committee member. Otherwise, you can volunteer as "ambassador": you will observe all the committee activities, ensure that people from your language or project manage to apply for a scholarship, translate scholarship applications written in your language to English and so on. Ambassadors are allowed to ask for a scholarship, unlike committee members.
Wikimania 2016 scholarships subteam 10:47, 10 November 2015 (UTC)
Harassment consultation[edit]
Please help translate to your language
The Community Advocacy team the Wikimedia Foundation has opened a consultation on the topic of harassment on Meta. The consultation period is intended to run for one month from today, November 16, and end on December 17. Please share your thoughts there on harassment-related issues facing our communities and potential solutions. (Note: this consultation is not intended to evaluate specific cases of harassment, but rather to discuss the problem of harassment itself.)
Your input requested on the proposed #FreeBassel banner campaign[edit]
Your input requested on the proposed #FreeBassel banner campaign
This is a message regarding the proposed 2015 Free Bassel banner. Translations are available.
Hi everyone,
This is to inform all Wikimedia contributors that a straw poll seeking your involvement has just been started on Meta-Wiki.
As some of your might be aware, a small group of Wikimedia volunteers have proposed a banner campaign informing Wikipedia readers about the urgent situation of our fellow Wikipedian, open source software developer and Creative Commons activist, Bassel Khartabil. An exemplary banner and an explanatory page have now been prepared, and translated into about half a dozen languages by volunteer translators.
We are seeking your involvement to decide if the global Wikimedia community approves starting a banner campaign asking Wikipedia readers to call on the Syrian government to release Bassel from prison. We understand that a campaign like this would be unprecedented in Wikipedia's history, which is why we're seeking the widest possible consensus among the community.
Given Bassel's urgent situation and the resulting tight schedule, we ask everyone to get involved with the poll and the discussion to the widest possible extent, and to promote it among your communities as soon as possible.
(Apologies for writing in English; please kindly translate this message into your own language.)
Thank you for your participation!
Posted by the MediaWiki message delivery 21:47, 25 November 2015 (UTC) • Translate • Get help
Community Wishlist Survey[edit]
Hi everyone! Apologies for posting this in English. Translations are very welcome.
We're beginning the second part of the Community Tech team's Community Wishlist Survey, and we're inviting all active contributors to vote on the proposals that have been submitted.
Thanks to you and other Wikimedia contributors, 111 proposals were submitted to the team. We've split the proposals into categories, and now it's time to vote! You can vote for any proposal listed on the pages, using the {{Support}} tag. Feel free to add comments pro or con, but only support votes will be counted. The voting period will be 2 weeks, ending on December 14.
The proposals with the most support votes will be the team's top priority backlog to investigate and address. Thank you for participating, and we're looking forward to hearing what you think!
Community Tech via
MediaWiki message delivery (talk) 14:38, 1 December 2015 (UTC)
VisualEditor News #6—2015[edit]
Did you know?
A new, simpler system for editing will offer a single Edit button. Once the page has opened, you can switch back and forth between visual and wikitext editing.
If you prefer having separate edit buttons, then you can set that option in your preferences, either in a pop-up dialog the next time you open the visual editor, or by going to Special:Preferences and choosing the setting that you want:
The current plan is for the default setting to have the Edit button open the editing environment you used most recently.
You can read and help translate the user guide, which has more information about how to use the visual editor.
Read this in another language • Subscription list for this multilingual newsletter
Since the last newsletter, the visual editor team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.
Recent improvements[edit]
You can switch from the wikitext editor to the visual editor after you start editing. The LaTeX mathematics formula editor has been significantly expanded. (T118616) You can see the formula as you change the LaTeX code. You can click buttons to insert the correct LaTeX code for many symbols.
Future changes[edit]
The single edit tab project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "Edit" tab will open whichever editing environment you used last time. Your last editing choice will be stored as a cookie for logged-out users and as an account preference for logged-in editors. Logged-in editors will be able to set a default editor in the Editing tab of Special:Preferences in the drop-down menu about "Editing mode:".
The visual editor will be offered to all editors at the following Wikipedias in early 2016: Amharic, Buginese, Min Dong, Cree, Manx, Hakka, Armenian, Georgian, Pontic, Serbo-Croatian, Tigrinya, Mingrelian, Zhuang, and Min Nan. (T116523) Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. The developers would like to know how well it works. Please tell them what kind of computer, web browser, and keyboard you are using.
In 2016, the feedback pages for the visual editor on many Wikipedias will be redirected to mediawiki.org. (T92661)
Testing opportunities[edit]
- Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences. Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in). The new system has not been finalized, and your feedback can affect the outcome. The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
- Remember my last editor,
- Always give me the visual editor if possible,
- Always give me the source editor, and
- Show me both editor tabs. (This is the current state for people already using the visual editor. None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
- Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
Elitre (WMF), 00:06, 25 December 2015 (UTC)
Wikimedia Year of Science[edit]
The Wiki Education Foundation is planning a Wikimedia-wide Year of Science 2016. We are just beginning to brain storm ideas for a similar effort at en-wv. Visit v:Wikiversity:Year of Science 2016 if you are interested in participating.
For more information see:
- Wikipedia Year of Science at the Wiki Education Foundation
- w:Wikipedia:Year of Science
- File:Making 2016 the Wikipedia Year of Science.webm Video recording of presentation at WikiConference USA 2015
Please feel free to contact me if you'd like to collaborate on this project in other languages. --mikeu talk 20:50, 30 December 2015 (UTC)
- I've created Wikiversity:Year of Science 2016 to coordinate multilingual activity. --mikeu talk 17:18, 1 January 2016 (UTC)
Wikimania 2016 Scholarships - Deadline soon![edit]
- Please help translate to your language
A reminder - applications for scholarships for Wikimania 2016 in Esino Lario, Italy, are closing soon! Please get your applications in by January 9th. To apply, visit the page below:
Patrick Earley (WMF) via MediaWiki message delivery (talk) 01:49, 5 January 2016 (UTC)
Proposals for closing projects/Move Beta Wikiversity to Incubator[edit]
Re: meta:Proposals for closing projects/Move Beta Wikiversity to Incubator Please see the most recent edit [1] with a summary of "Move for closure." --mikeu talk 16:23, 8 January 2016 (UTC)
2016 WMF Strategy consultation[edit]
- Please help translate to your language
Hello, all.
The Wikimedia Foundation (WMF) has launched a consultation to help create and prioritize WMF strategy beginning July 2016 and for the 12 to 24 months thereafter. This consultation will be open, on Meta, from 18 January to 26 February, after which the Foundation will also use these ideas to help inform its Annual Plan. (More on our timeline can be found on that Meta page.)
Your input is welcome (and greatly desired) at the Meta discussion, 2016 Strategy/Community consultation.
Apologies for English, where this is posted on a non-English project. We thought it was more important to get the consultation translated as much as possible, and good headway has been made there in some languages. There is still much to do, however! We created m:2016 Strategy/Translations to try to help coordinate what needs translation and what progress is being made. :)
If you have questions, please reach out to me on my talk page or on the strategy consultation's talk page or by email to mdennis@wikimedia.org.
I hope you'll join us! Maggie Dennis via MediaWiki message delivery (talk) 19:06, 18 January 2016 (UTC)
Wikiversity_Simple_English[edit]
Requests for new languages/Wikiversity Simple English has just started. It might be of interest to the community here. Please participate in the discussion. --mikeu talk 20:57, 26 January 2016 (UTC)
language links via Wikidata are coming[edit]
Hi everyone :)
I wanted to let you know that Wikiversity is scheduled to receive the first round of Wikidata support on February 23rd. This means you will be able to manage the links between different language versions just in one place (on Wikidata) instead of having to do it in each article. I hope this will help you by reducing some work. If that goes well you'll receive access to the data on Wikidata a while later (date will be scheduled later). If you have any questions please don't hesitate to ask on d:Wikidata:Wikiversity or d:Wikidata:Project chat.
Lydia Pintscher (WMDE) 16:10, 1 February 2016 (UTC)
Wikidata support is here![edit]
Hey everyone :)
As announced earlier you can now manage your links to other languages and projects via Wikidata. I hope this will make your work here easier. If you keep the links in local wiki text they will overwrite what is coming from Wikidata. You can also completely surpress them using the magic word {{noexternallanglinks}}. If you have questions please don't hesitate to ask at d:Wikidata:Wikiversity or d:Wikidata:Project chat.
Welcome to Wikidata!
Cheers Lydia Pintscher (WMDE) 17:22, 24 February 2016 (UTC)
Data visualizations and maps on Beta Wikiversity[edit]
There's a lot of development going on towards making it easy for editors to create and edit data visualizations and maps, which can be used directly on Wikimedia projects. A certain amount of centralization is helpful for this, so the plan seems to be to store these resources on one wiki, probably in a dedicated namespace. Which wiki will be responsible for them is still an open question; previous suggestions include Meta, Commons, Wikidata, and a dedicated new wiki. However, I feel like data visualizations and maps (as well as other similar resources in the same vein), as learning resources that serve a helpful educational purpose on Wikimedia projects and elsewhere, would fit very well here on Wikiversity.
Thoughts on this? Would this kind of content be welcome here on Wikiversity? --Yair rand (talk) 16:50, 25 February 2016 (UTC)
- See also How to deal with open datasets RFC. --Yurik (talk) 17:20, 25 February 2016 (UTC)
-
- This is an exciting development and one of my original motivations for joining Wikiversity when it first formed. I've opened a learning project space at EN.Wikiversity and across several other wikis outside of the Wikimedia sphere to focus a team on this map of this event which will require pulling together a huge amount of people and data. I think that the centralization aspect is fairly well covered in the RFC above. A live example would set an important precedent for whomever has the energy and focus to fully demonstrate the capability in a 'real life' use case. I'm hoping that this project will help catapult v: into its designated purpose. --CQ (talk) 18:38, 27 February 2016 (UTC)
VisualEditor News #1—2016[edit]
Read this in another language • Subscription list for this multilingual newsletter
Did you know?
Among experienced editors, the visual editor's table editing is one of the most popular features.
If you select the top of a column or the end of a row, you can quickly insert and remove columns and rows.
Now, you can also rearrange columns and rows. Click "Move before" or "Move after" to swap the column or row with its neighbor.
You can read and help translate the user guide, which has more information about how to use the visual editor.Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Japanese, Korean, Arabic, Indic, and Han scripts, and improving the single edit tab interface.
Recent changes[edit]
You can switch from the wikitext editor to the visual editor after you start editing. This function is available to nearly all editors at most wikis except the Wiktionaries and Wikisources.
Many local feedback pages for the visual editor have been redirected to mw:VisualEditor/Feedback.
You can now re-arrange columns and rows in tables, as well as copying a row, column or any other selection of cells and pasting it in a new location.
The formula editor has two options: you can choose "Quick edit" to see and change only the LaTeX code, or "Edit" to use the full tool. The full tool offers immediate preview and an extensive list of symbols.
Future changes[edit]
The single edit tab project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "Edit" tab will open whichever editing environment you used last time. Your last editing choice will be stored as an account preference for logged-in editors, and as a cookie for logged-out users. Logged-in editors will have these options in the Editing tab of Special:Preferences:
- Remember my last editor,
- Always give me the visual editor if possible,
- Always give me the source editor, and
- Show me both editor tabs. (This is the state for people using the visual editor now.)
The visual editor uses the same search engine as Special:Search to find links and files. This search will get better at detecting typos and spelling mistakes soon. These improvements to search will appear in the visual editor as well.
The visual editor will be offered to all editors at most "Phase 6" Wikipedias during the next few months. This will affect the following languages, amongst others: Japanese, Korean, Urdu, Persian, Arabic, Tamil, Marathi, Malayalam, Hindi, Bengali, Assamese, Thai, Aramaic.
Let's work together[edit]
- Please try out the newest version of the single edit tab on test2.wikipedia.org. You may need to restore the default preferences (at the bottom of test2wiki:Special:Preferences) to see the initial prompt for options. Were you able to find a preference setting that will work for your own editing? Did you see the large preferences dialog box when you started editing an article there?
- Can you read and type in Korean, Arabic, Japanese, Indic, or Han scripts? Does typing in these languages feels natural in the visual editor? Language engineer David Chan needs to know. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org.
- Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Join the Tech Talk about "Automated citations in Wikipedia: Citoid and the technology behind it" with Sebastian Karcher on 29 February 2016.
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
Elitre (WMF), 19:21, 26 February 2016 (UTC)
poll until March 31: Proposals for closing projects/Move Beta Wikiversity to Incubator[edit]
"This poll is timeboxed and will be open until March 31 and the option will be selected by simple mayority."
Please read What to do with this proposal?, and VOTE. Thank you! ----Erkan Yilmaz uses the Wikiversity:Chat (try) 14:02, 2 March 2016 (UTC)
Install Extension:Simple Forms[edit]
Saluton! I would need a solution which enable to use HTML <select> elements for the course Internaciigo de komputilaj programoj/Pli alt-nivelaj problemoj. Could an admin do that for me? --Psychoslave (talk) 14:49, 10 March 2016 (UTC)
- To install an extension, Phabricator need a vote of the community. You nned to lauch the vote by the explain of the needing extension in betawikiversity. But you need to know that betawikiversity is an incubator, so it will be prefered to activate your wikiversity to as what the community want. Crochet.david (talk) 19:41, 10 March 2016 (UTC)
Open Call for Individual Engagement Grants[edit]
Please help translate to your language:
Greetings! The Individual Engagement Grants (IEG) program is accepting proposals until April 12th to fund new tools, research, outreach efforts, and other experiments that enhance the work of Wikimedia volunteers. Whether you need a small or large amount of funds (up to $30,000 USD), IEGs can support you and your team’s project development time in addition to project expenses such as materials, travel, and rental space.
- Submit a grant request or draft your proposal in IdeaLab
- Get help with your proposal in an upcoming Hangout session
- Learn from examples of completed Individual Engagement Grants
With thanks, I JethroBT (WMF) 15:47, 31 March 2016 (UTC)
Server switch 2016[edit]
The Wikimedia Foundation will be testing its newest data center in Dallas. This will make sure Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to conduct a planned test. This test will show whether they can reliably switch from one data center to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
They will switch all traffic to the new data center on Tuesday, 19 April.
On Thursday, 21 April, they will switch back to the primary data center.
Unfortunately, because of some limitations in MediaWiki, all editing must stop during those two switches. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
- You will not be able to edit for approximately 15 to 30 minutes on Tuesday, 19 April and Thursday, 21 April, starting at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT).
If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
- Background jobs will be slower and some may be dropped.
Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
- There will be a code freeze for the week of 18 April.
No non-essential code deployments will take place.
This test was originally planned to take place on March 22. April 19th and 21st are the new dates. You can read the schedule at wikitech.wikimedia.org. They will post any changes on that schedule. There will be more notifications about this. Please share this information with your community. /User:Whatamidoing (WMF) (talk) 21:07, 17 April 2016 (UTC)
Wikidata: access to the data is coming[edit]
Hi everyone :)
A while ago you received access to the interwiki links from Wikidata. Everything seems to be going well so I'd like to move on to the second stage. You will get access to the actual data in Wikidata like the date of birth of a person. You'll be able to make use of them in your templates via Lua or a new parser function (#property). We'll be enabling this on May 3rd. I hope this will open up great new possibilities for you and make your work easier. If you have questions please come to d:Wikidata:Project chat or d:Wikidata:Wikiversity.
Cheers Lydia Pintscher (WMDE) 09:35, 28 April 2016 (UTC)
Wikidata: data access is here[edit]
Hi everyone :)
We just enabled access to the data on Wikidata for you. This means you can now access data like the number of inhabitants of a city or get a link to a picture for a famous person and much more. You can access the data in two ways - via a parser function and via Lua. How to use it:
- Parser function: {{#property:P36|from=Q183}} to get the capital (Property:P36) from the item about Germany (Q183)
- Lua: see mw:Extension:Wikibase Client/Lua
I hope this will help you do great things here. If you have any questions please don't hesitate to ask. A good place to do that is d:Wikidata:Project chat.
Cheers Lydia Pintscher (WMDE) 08:40, 4 May 2016 (UTC)
IMPORTANT: Admin activity review[edit]
Hello. A policy regarding the removal of "advanced rights" (administrator, bureaucrat, etc. ) was adopted by global community consensus in 2013. According to this policy, the stewards are reviewing administrators' activity on all Wikimedia Foundation wikis with no inactivity policy. To the best of our knowledge, your wiki does not have a formal process for removing "advanced rights" from inactive accounts. This means that the stewards will take care of this according to the admin activity review.
We have determined that the following users meet the inactivity criteria (no edits and no log actions for more than 2 years):
- Ciprian Dorin Craciun (administrator)
These users will receive a notification soon, asking them to start a community discussion if they want to retain some or all of their rights. If the users do not respond, then their advanced rights will be removed by the stewards.
However, if you as a community would like to create your own activity review process superseding the global one, want to make another decision about these inactive rights holders, or already have a policy that we missed, then please notify the stewards on Meta-Wiki so that we know not to proceed with the rights review on your wiki. Thanks, Ajraddatz (müzakirə) 00:18, 24 may 2016 (UTC)
States of Wikiversities[edit]
Hi everyone! Who can update this page States of Wikiversities? --— Green Zero обг 16:49, 5 June 2016 (UTC)
- Usually, Crochet.david does this. Regards, --Vogone (talk) 00:21, 11 June 2016 (UTC)
- I can't, it's not easy to do this manually. Crochet.david (talk) 15:19, 11 June 2016 (UTC)
Compact Language Links enabled in this wiki today[edit]
Please help translate to your language
Compact Language Links has been available as a beta-feature on all Wikimedia wikis since 2014. With compact language links enabled, users are shown a much shorter list of languages on the interlanguage link section of an article (see image). Based on several factors, this shorter list of languages is expected to be more relevant for them and valuable for finding similar content in a language known to them. More information about compact language links can be found in the documentation.
From today onwards, compact language links has been enabled as the default listing of interlanguage links on this wiki. However, using the button at the bottom, you will be able to see a longer list of all the languages the article has been written in. The setting for this compact list can be changed by using the checkbox under User Preferences -> Appearance -> Languages
The compact language links feature has been tested extensively by the Wikimedia Language team, which developed it. However, in case there are any problems or other feedback please let us know on the project talk page. It is to be noted that on some wikis the presence of an existing older gadget that was used for a similar purpose may cause an interference for compact language list. We would like to bring this to the attention of the admins of this wiki. Full details are on this phabricator ticket (in English).
Due to the large scale enablement of this feature, we have had to use MassMessage for this announcement and as a result it is only written in English. We will really appreciate if this message can be translated for other users of this wiki. Thank you. On behalf of the Wikimedia Language team: Runa Bhattacharjee (WMF) (talk) 07:39, 22 June 2016 (UTC)
Editing News #2—2016[edit]
Read this in another language • Subscription list for this multilingual newsletter
It's quick and easy to insert a references list.
Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "Insert" menu and click the "References list" icon (three books).
If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references. Finally, click "Insert" in the dialog to insert the References list. This list will change as you add more footnotes to the page.
You can read and help translate the user guide, which has more information about how to use the visual editor.Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.
Recent changes[edit]
The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.
The single edit tab feature combines the "Edit" and "Edit source" tabs into a single "Edit" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "Editing" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.
Future changes[edit]
The "Save page" button will say "Publish page". This will affect both the visual and wikitext editing systems. More information is available on Meta.
The visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.
The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)
The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.
Let's work together[edit]
- Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.
- Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
m:User:Elitre (WMF), 17:20, 3 July 2016 (UTC)
Open call for Project Grants[edit]
Please help translate to your language:
- Greetings! The Project Grants program is accepting proposals from July 1st to August 2nd to fund new tools, research, offline outreach (including editathon series, workshops, etc), online organizing (including contests), and other experiments that enhance the work of Wikimedia volunteers.
- Whether you need a small or large amount of funds, Project Grants can support you and your team’s project development time in addition to project expenses such as materials, travel, and rental space.
- Submit a grant request or draft your proposal in IdeaLab
- Get help with your proposal in an upcoming Hangout session
- Learn from examples of completed Individual Engagement Grants or Project and Event Grants
- Also accepting candidates to join the Project Grants Committee through July 15.
- With thanks, I JethroBT (WMF) 15:25, 5 July 2016 (UTC)
Save/Publish[edit]
The Editing team is planning to change the name of the “Save page” button to “Publish page” and “Publish changes”. “Publish page” will be used when you create a new page. “Publish changes” will be used when you change an existing page. The names will be consistent in all editing environments.[2][3]
This change will probably happen during the week of 30 August 2016. The change will be announced in Tech News when it happens.
If you are fluent in a language other than English, please check the status of translations at translatewiki.net for “Publish page” and “Publish changes”.
The main reason for this change is to avoid confusion for new editors. Repeated user research studies with new editors have shown that some new editors believed that “Save page” would save a private copy of a new page in their accounts, rather than permanently publishing their changes on the web. It is important for this part of the user interface to be clear, since it is difficult to remove public information after it is published. We believe that the confusion caused by the “Save page” button increases the workload for experienced editors, who have to clean up the information that people unintentionally disclose, and report it to the functionaries and stewards to suppress it. Clarifying what the button does will reduce this problem.
Beyond that, the goal is to make all the wikis and languages more consistent, and some wikis made this change many years ago. The Legal team at the Wikimedia Foundation supports this change. Making the edit interface easier to understand will make it easier to handle licensing and privacy questions that may arise.
Any help pages or other basic documentation about how to edit pages will also need to be updated, on-wiki and elsewhere. On wiki pages, you can use the wikitext codes {{int:Publishpage}} and {{int:Publishchanges}} to display the new labels in the user's preferred language. For the language settings in your account preferences, these wikitext codes produce “Publish page” and “Publish changes”.
Please share this news with community members who teach new editors and with others who may be interested.
Whatamidoing (WMF) (talk) 18:03, 9 August 2016 (UTC)
RevisionSlider[edit]
Birgit Müller (WMDE) 14:56, 12 September 2016 (UTC)
