Jump to content

User talk:Nicereddy

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Your talk page

[edit]

I have manually blanked it, which is not typically allowed, but the exceptional size of it meant that it's worth the common sense of doing so. You haven't edited in a while so you may not even see this message. Thanks, !dave 21:43, 13 December 2017 (UTC)[reply]

The Signpost: 18 December 2017

[edit]
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 06:27, 18 December 2017 (UTC)[reply]

Wikidata weekly summary #291

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Additional languages for monolingual values got approved by the language committee: ami (Amis), bnn (Bunun), fos (Siraya), ppu (Papora / Hoanya), pwn (Paiwan), pyu (Puyuma), ssf (Thao), trv (Seediq / Taroko), uun (Pazeh) (see gerrit:374052, phab:T144272)
    • More work on caching constraint results so we can enable the constraints checks for all logged-in users by default
    • Fixed a bug when edit links showed up in diff views (phabricator:T181807)
    • Final step towards being able to store statements on Forms of a Lexeme
    • Disabled RDF support for Lexemes as the mapping isn't defined yet (phabricator:T182660)
    • Adding some more smart tracking for Lua usage so we better know which properties from an item are used on a Wikipedia article even when the whole item is loaded (phabricator:T179923)

You can see all open tickets related to Wikidata here.

Wikidata weekly summary #292

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Due to the Christmas and New Year's Eve holidays, no deployment will happen before January 3rd.
    • Monolingual language codes for Old French (fro) and Middle French (frm) added (phabricator:T181823)
    • Finishing touches on storing statements on Forms
    • No longer checking constraints on the property example statements (phabricator:T183267)
    • More work on caching constraint check results so we can roll out constraint checking for all logged in users

Wikidata weekly summary #293

[edit]
Here's your first Wikidata Weekly Summary of the year 2018 (Calendar: Gregorian)!
  • Development
    • Fixed a problem with references in history of items (phab:T182767) Thanks to Matěj Suchánek who helped providing a workaround
    • Make statements on forms persistent for lexicographical data (phab:T163724)
    • Fix a bug that removed the collapse button (phab:T175492)
    • Remove cache constraint check results on purge (phab:T182107)
    • Add sitelinks to hif.wiktionary (phab:T180785)
    • Read constraint check results from cache and check freshness (phab:T182106)
    • Re-label the "Save" links to "Publish" (phab:T161367)

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #294

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development

Wikidata weekly summary #295

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Mahir256
    • Closed request for adminship: Jarekt (as successful)

The Signpost: 16 January 2018

[edit]
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 15:27, 16 January 2018 (UTC)[reply]

Wikidata weekly summary #296

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: Mahir256 (as successful)

Wikidata weekly summary #297

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Constraint violations can now be checked on qualifiers and references (phab:T168532)
    • Implemented usage tracking deduplication to reduce database load (phab:T178079). This should not have any effect on what users see on recent changes and watchlists.
    • Redirects on client wikis that are connected to a Wikidata item can have a tracking category, if set up (phab:T185743). Thanks, Matěj!
    • Improved documentation of the pageterms query module (gerrit:406240). Thanks, Niedzielski!
    • Improved empty "content was:" in deletion logs for entities (phab:T184025)
    • Fixed links to external user pages in recent changes (phab:T183019)
    • Fixed user names beginning with a star sometimes being rendered as a list (phab:T182800)
    • Fixed constraint check results possibly showing up in the wrong language (phab:T185688)
    • Fixed ArticlePlaceholders possibly not showing up in search results (gerrit:406168)
    • Some of the developers attended to the Wikimedia Developer Summit 2018. You can find some notes on the Phabricator board

You can see all open tickets related to Wikidata here.


The Signpost: 5 February 2018

[edit]
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 05:12, 5 February 2018 (UTC)[reply]

Wikidata weekly summary #298

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • We are saddened to report that Polish Wikimedian Krzysztof Machocki (who was also active on Wikidata) died on 31 January 2018, aged 36, after a couple of weeks of illness. Our condolences to his family and friends.
    • Notes of the IRC office hour of January 30th
    • The call for submissions for Wikimania (Cape Town, July 2018) is now open. Deadline is March 18th. Ideas of submissions related to Wikidata can be discussed here
    • Based on community discussions, the ArticlePlaceholder will soon be deployed on Urdu and Estonian Wikipedias.
    • Statistics
      • January 2018 brought us 9,770,248 edits, 445,027 new items were created.
      • The number of users that edited Wikidata per day grew in 2017 from 2439 to 2672 users, 9,6% more compared to 2016. The number of edits by them grew with 18% to 190k edits per day. We also get edited by 542 IP adresses per day, 50% more than in 2016.
      • In 2017, Wikidata got edited by 46 various bots per day, executing 334k edits per day (63% more than in 2016). The most active bot in 2017 was Emijrpbot, who added 18 million edits to Wikidata.
      • 284 million statements now contain references, compared to 67 million at the start of 2017. The average number of statements per item grew from 5 to almost 9. 73 million qualifiers are now used to provide more details for statements, 13 million in early 2017.
    • New tool based on Wikidata: Random TV episodes
  • Development
    • Diffs now show the entity ID in the page title (phab:T181077)
    • Improved handling of translations in the Query Service UI (gerrit:406301, gerrit:406996), thanks to Li Song
    • Continued working on diffs for forms on Lexemes (eg. phab:T186317)
    • Added summaries for edits on representations or grammatical features of a form (phab:T184702)
    • Worked on showing links to Lexemes and statements (phab:T185332)
    • Rolling out fine grain usage tracking on more wikis, so only relevant changes are shown in the watchlist and recent changes (phab:T185032)
    • Improved scalability of fine grain usage tracking (phab:T185693)

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #299

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here.

Wikidata weekly summary #300

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Welcome to the 300th Weekly Summary!

The weekly newsletter was started by Lydia at the very beginning of the Wikidata project, even before the first deployment, to keep the community informed about the developments, the new projects and tools. More than five years later, the newsletter is still there, its content powered by the community, and sent every week all along the years. I wanted to say a warm "thank you!" to each person who helped filling the Weekly Summary <3

Over the past years, as you know, Wikidata has grown a lot. More data, more tools, more editors and reusers, more exciting projects led by the community. The Weekly Summary has evolved with us, and the 300th edition seems a good moment to ask you all your suggestions about the newsletter, how it could continue evolving, and how you would like to improve it.

On that purpose, you can find a feedback page to express all your ideas about the Weekly Summary. We're very interested to know more about your reading habits, the parts you're more or less interested in, the new topics you would like to share with the community. Thanks in advance for filling it.

I stay available anytime to discuss with you, feel free to contact me if you have any question or concern! Cheers, Léa

  • A selection of cool tools on Wikidata

Here are a few tools that are recommended by some Wikidata community members. External websites, gadgets or scripts, they are very useful for Wikidata editors or users!

    • The Wikidata Query Service is an infinite source of amazing data and one of the best ways to explore and use Wikidata. (TweetsFactsAndQueries)
    • QuickStatements is a powerful tool that can edit or add Wikidata item en masse, via a text editor or importing a spreadsheet. (Éder Porto via Facebook)
    • Mix'n'match (manual), which helps us to interlink Wikidata with the rest of the web and the world :-) (Spinster, Siobhan via Twitter)
    • WikiShootMe! allows you to see Wikidata items plotted out on a map and shows you whether they have images or not. (Ham II)
    • Yair Rand's WikidataInfo script adds the QID of the equivalent Wikidata item to the page being viewed (on sister projects), along with its Wikidata label and description. (Andy Mabbett)
    • Recoin measures the degree of completeness of relevant properties of a Wikidata item and suggests any relevant statements that can be added to the item. (Rachmat04)
    • Template:Wikidata list ("Listeria") Self-updating lists on wiki pages, to drive projects and show results. Over 14,000 now live. (Jheald)
    • DuplicateReferences gadget adds a link to copy references and add them to other statements on the same item. (PKM)
    • checkConstraints gadget adds notifications on the interface to easily notice the violation of constraints and help people fixing them (Léa)
    • Resolve authors lists scientific articles with the property author name string (P2093) and groups them on the basis of co-authors and topic, which helps to distinguish people referred to by identical name strings. (Daniel Mietchen)
    • The Wiki Loves Monuments map is powered by Wikidata. You can look for a city and find the monuments around. (Stefano Sabatini via Facebook)
  • Development
    • Fixed incomplete "Label:", "Description:" and "Statement:" entity usage messages in various places (phab:T178090). Thanks, Matěj!
    • Improved violation messages for ranges involving the current date (e. g. “should not be in the future”).
    • Continued work on caching constraint check results.
    • Enabled Lua fine-grained usage tracking for better performance on several more wikis: hywiki, frwiki, svwiki, itwiki, zhwiki, bewiki, nlwiki, glwiki, and Wikimedia Commons (phab:T187265 phab:T186714)
    • Representation and grammatical features of the form can be changed using the UI (WikibaseLexeme) (phab:T173743, phab:T160525)

You can see all open tickets related to Wikidata here.


The Signpost: 20 February 2018

[edit]
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 17:12, 20 February 2018 (UTC)[reply]

Wikidata weekly summary #301

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Make it possible to link to Lexemes and Statements (phab:T1854997)
    • Disabling senses for the first release of Lexemes (phab:T186995)
    • Caching for constraints check

You can see all open tickets related to Wikidata here.


Editing News #1—2018

[edit]

Read this in another language • Subscription list for the English Wikipedia • Subscription list for the multilingual edition

Did you know?

Did you know that you can now use the visual diff tool on any page?

Screenshot showing some changes, in the two-column wikitext diff display

Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.

If you enable the Beta Feature for "⧼visualeditor-preference-visualdiffpage-label⧽", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.

Toggle button showing visual and wikitext options; visual option is selected

Click the toggle button to switch between visual and wikitext diffs.

In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.

Screenshot showing the same changes to an article. Most changes are highlighted with text formatting.

This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence. An arrow indicates that the paragraph changed location.

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 Editing Team has spent most of their time supporting the 2017 wikitext editor mode, which is available inside the visual editor as a Beta Feature, and improving the visual diff tool. Their work board is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.

Recent changes

[edit]
  • The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
  • The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [1]
  • Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [2]
  • The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. This tool has been used at the English Wikipedia for a long time. It is very popular and useful to editors, although it can be tricky for admins to set up. Other wikis can have this service, too. Please read the instructions. You can ask the team to help you enable citoid at your wiki.

Let's work together

[edit]
  • The team is planning a presentation about editing tools for an upcoming Wikimedia Foundation metrics and activities meeting.
  • Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
  • The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. This has already been enabled at the English Wikipedia. If you want columns for a long list of footnotes on this wiki, you can use either <references /> or the plain (no parameters) {{reflist}} template. If you edit a different wiki, you can request multi-column support for your wiki. [3]
  • 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. We will notify you when the next issue is ready for translation. Thank you!

—User:Whatamidoing (WMF) (talk) 23:15, 28 February 2018 (UTC)[reply]

Wikidata weekly summary #302

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Re-enable Wikidata Recent Changes integration on Russian Wikipedia (phab:T179012)
    • Investigate on the size of logging table (phab:T188635)
    • Fix issues with graph vizualisation UI (phab:T186467)
    • Work on results of security review for the deployment of Wikibase-Lexeme (phab:T186726)
    • Enable constraint result caching on Wikidata (phab:T184812)

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #303

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Significantly (on average to 1/4th) reduced the number of changes from Wikidata showing up on the watchlists and recent changes on Wikipedias and the other sister projects. This way changes that do not affect an article should no longer show up. We're still holding off roll-out to Commons, Cebuano, Waray-Waray and Armenian Wikipedia because of scalability concerns.
    • Working on optimizing one of the largest database tables (wb_terms) (phab:T188279)
    • Fixing a bug on how Wikidata changes are shown on Wikipedia (phab:T189320)
    • Continued addressing security review issues for Wikibase-Lexeme extension (phab:T186726)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Final note from Léa: thanks to people who participated to the feedback page! Today's Weekly Summary is already improved thanks to your suggestions. Feel free to add more comments, and feel free to edit the newsletter yourself: all small contributions are welcome :)

Wikidata weekly summary #304

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
  • Development
    • Looking into current Lua usage to see where we can improve the Lua functions we provide (phab:T189506)
    • When there is a constraint violation in a reference, the reference is now automatically expanded to make it more visible (phab:T177970)
    • Looked into issues around notifying the Wikipedias about changes happening on Wikidata (sometimes delayed due to too quick bot editing) (phab:T189772)
    • Fixed some translation issues in the embeded part of the Query Service (phab:T188990)
    • Fixed an issue with usernames being broken for Wikidata changes in watchlist and RC on Wikipedia (phab:T189320)
    • Optimizing a heavily used database table (wb_terms) (phab:T188279)
    • Polishing a lot of things for lexicographical data first deployment
    • Make it possible to remove a Form (phab:T173332)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #305

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: Putnik, Okkn. Welcome on board!
    • Closed request for comments: Former ATE
  • Development
    • New search code for Wikidata merged. You may notice the improvement in the search results output for Wikidata item. However, new code for search is not enabled, only new results format. The search code will be enabled next week.
    • Improving formatting of language and lexical category in diff for Lexemes (phab:T189679)
    • Allow to remove a Form (phab:T189675)
    • Translate the grammatical feature properly on Lexemes (phab:T189143)
    • Investigate and fix a bug on Lexemes when undoing an edit (phab:T187215)
    • Progress on refactoring the table wb_terms (phab:T189777, phab:T188993, phab:T188279)
    • Fixing an error on the caching of the constraint checks (phab:T189842)
    • Improving the performance of a table in the database (phab:T180834)
    • Improving the way we're building dumps (phab:T177550)
    • Investigate on improving Lua functions (phab:T143970)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Signpost issue 4 – 29 March 2018

[edit]
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 18:49, 29 March 2018 (UTC)[reply]

Wikidata weekly summary #306

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • if you're working with Lua modules, you can give input here about new functions
    • you can still fill this page if you encounter a problem with suggester ranking

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #307

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Differences between range constraints now work only if both properties are present (phab:T185480)
    • Work on a new constraint unit which defines which units are alowed for a given property (phab:T164372)
    • Make the Special:ConstraintReport easier to understand (phab:T188728)
    • Work on a Lua function which checks if an item is a subclass of or instance of another item (phab:T179155)
    • Started deleting old autopatrolled from the loggin table (phab:T190447, phab:T184791)
    • More work on setting up permissions for Lexeme (phab:T189480)
    • Fixing a bug about removing the last Lemma (phab:T189185)
    • Disabling the possibility to move a Lexeme (phab:T189481)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #308

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Disable Senses in the API for the initial version of the WikibaseLexeme extension (phab:T187198)
    • Create a new data type to allow linking to Forms (phab:T165579)
    • Fix a bug happening when editing a Form (phab:T187215)
    • Enforce permission checks when editing Lexeme (phab:T189480)
    • Make not possible to remove the last lemma (phab:T189185)
    • Make not possible to move a Lexeme (phab:T189481)
    • Implement “Units” constraint (phab:T164372)
    • More work on the possibility to pick an item's parent in Lua (phab:T179155)
    • Show a thumbnail for image/video/audio properties in statements (phab:T46727)
    • Add “no bounds” constraint (phab:T170610)
    • Make the “difference within range” constraint not requiring “item requires claim” constraint (phab:T185480)
    • New Lua function to test for validity of Wikidata entity IDs (phab:T143970)
    • Include checksums in dumps (phab:T190457)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #309

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Track the number of constraints by type (phab:T191891)
    • Include thumbnails in image statements (phab:T46727)
    • Install Query Service on Factgrid (phab:T189863)
    • Page creation and edit rates (phab:T184948)
    • Implement unit constraint (phab:T164372)
    • Implement no bounds constraint (phab:T170610)
    • Started working on the constraint violation type to restrict to indicate that certain properties can only be used on items or lexemes (phab:T164744)
    • Creating a Docker container for QuickStatements (phab:T192079)
    • Removed hardcoded demo data in Wikibase Lexeme (phab:T188899)
    • New data type for linking to Forms (phab:T165579)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


The Signpost: 26 April 2018

[edit]
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 01:49, 26 April 2018 (UTC)[reply]

Wikidata weekly summary #310

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #311

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #312

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Adminor
  • Development
    • Fix the bug where changes in the watchlist and Recent Changes on Wikipedia should have been shown but were not (phab:T192673)
    • Clarify error message for the merge API (phab:T180296)
    • Add violation type to restrict which entity types a property can be used (phab:T164744)
    • Added a constraint to blacklist values for a property (phab:T183092)
    • Fix a bug showing the wrong alias in the edit summary when editing an alias (phab:T190492)
    • Fix some bugs related to displaying thumbnails in statements (phab:T193880, phab:T192667, phab:T193499)
    • Continue looking into dispatch issues (phab:T194602)
    • Working on adding an integer constraint (phab:T167989)
    • Preparing to deploy WikibaseLexeme extension on Wikimedia cluster (phab:T168260)
    • Making sure that the form ID counter is preserved when clearing the lexeme via the API (phab:T192264)
    • Applying the same validation to the language code of the Lemma and the representation (phab:T191504)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #313

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Past: Europeana Tech Conference (including a lot of Wikidata workshops and discussions)
    • Past:Wikimedia Hackathon 2018, 18-20 May in Barcelona
      • Check the hashtag #wmhack on Twitter to see what has been worked on regarding Wikidata
      • List of the projects that have been demoed during the showcase
    • Next Wikidata IRC office hour: May 29th at 18:00 (UTC+2, Berlin time) on the channel #wikimedia-office
  • Other Noteworthy Stuff
  • Development
    • Hackathon!
    • Work on adding “integer” constraint (phab:T167989)
    • Fix a bug expanding the references with a constraint violation (phab:T193669)
    • Add a "mis" code language to enable uncoded languages in Wikibase Lexeme (phab:T194754)
    • Improve the different language fields in the interface of editing a Lexeme (phab:T191504)
    • Finish work to edit Forms via the web API (phab:T190906)
    • Include special Lexeme IDs (phab:T187060)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


The Signpost: 24 May 2018

[edit]
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 15:18, 24 May 2018 (UTC)[reply]

Wikidata weekly summary #314

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • IRC office hour, on May 29th at 18:00 (UTC+2, Berlin time), on the IRC channel #wikimedia-office. Special topic: Lexemes on Wikidata
  • Development
    • Deployed and activate WikibaseLexeme on wikidata.org so you can now store the first lexicographical data on Wikidata (phab:T191457)
    • Fixing the encoding issues on labels of items linked on Lexemes (phab:T195470, phab:T195359)
    • Fixed an issue that was preventing adding Forms and Lexemes in statements (phab:T195402)
    • Suppressed the browser's autocomplete that covers WikibaseLexeme's suggestion on Special:NewLexeme (phab:T195383, phab:T191526)
    • Worked on a bug about representation overwriting other representation with the same language code (phab:T193636)
    • Changed title of the field of a lemma language to make it less likely for people to add a translation as a second Lemma (phab:T193603)
    • Working on the RDF mapping of WikibaseLexeme (phab:T160260)
    • Working on implementing fulltext search for Lexemes (phab:T189739)
    • Working on showing Lemmas for linked Lexemes instead of just their ID on special pages like Special:AllPages (phab:T195382)
    • Fixing issues that happened after dropping an index from the wb_terms table (phab:T194270, phab:T195642, phab:T195611)
    • Made constraint check result appear directly after adding a new statement (phab:T194247)
    • Working on looking up entities by external identifiers on Special:Search (phab:T99899)
    • Added Docker image to Wikibase website (phab:T189936)
    • Added WikibaseImport script to Docker images to make it easier for people to start their own Wikibase install with some data imported from Wikidata (phab:T192080)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


July 2018

[edit]

Information icon Hello. It appears your talk page is becoming quite lengthy and is in need of archiving. According to Wikipedia's user talk page guidelines; "Large talk pages become difficult to read, strain the limits of older browsers, and load slowly over slow internet connections. As a rule of thumb, archive closed discussions when a talk page exceeds 75 KB or has multiple resolved or stale discussions." - this talk page is 326 KB. See Help:Archiving a talk page for instructions on how to manually archive your talk page, or to arrange for automatic archiving using a bot. If you have any questions, place a {{help me}} notice on your talk page, or go to the help desk. Thank you. --Jax 0677 (talk) 21:16, 18 July 2018 (UTC)[reply]

Editing News #2—2018

[edit]

Read this in another language • Subscription list for this multilingual newsletter • Subscription list on the English Wikipedia

Did you know?

Did you know that you can use the visual editor on a mobile device?

Screenshot showing the location of the pencil icon

Tap on the pencil icon to start editing. The page will probably open in the wikitext editor.

You will see another pencil icon in the toolbar. Tap on that pencil icon to the switch between visual editing and wikitext editing.

Toolbar with menu opened

Remember to publish your changes when you're done.

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 Editing Team has wrapped up most of their work on the 2017 wikitext editor and the visual diff tool. The team has begun investigating the needs of editors who use mobile devices. Their work board is available in Phabricator. Their current priorities are fixing bugs and improving mobile editing.

Recent changes

[edit]

Let's work together

[edit]
  • The Editing team wants to improve visual editing on the mobile website. Please read their ideas and tell the team what you think would help editors who use the mobile site.
  • The Community Wishlist Survey begins next week.
  • 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. We will notify you when the next issue is ready for translation. Thank you!

— Whatamidoing (WMF) (talk) 17:12, 1 November 2018 (UTC)[reply]

ArbCom 2018 election voter message

[edit]

Hello, Nicereddy. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 19 November 2018 (UTC)[reply]

Category:GoldSrc engine games has been nominated for discussion

[edit]

Category:GoldSrc engine games, which you created, has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. ZXCVBNM (TALK) 10:10, 24 June 2019 (UTC)[reply]

Category:GoldSrc engine mods has been nominated for discussion

[edit]

Category:GoldSrc engine mods, which you created, has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. ZXCVBNM (TALK) 10:14, 24 June 2019 (UTC)[reply]

Editing News #1—July 2019

[edit]

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can use the visual editor on a mobile device?

Every article has a pencil icon at the top. Tap on the pencil icon to start editing.

Edit Cards

Toolbar with menu opened

This is what the new Edit Cards for editing links in the mobile visual editor look like. You can try the prototype here: 📲 Try Edit Cards.

Welcome back to the Editing newsletter.

Since the last newsletter, the team has released two new features for the mobile visual editor and has started developing three more. All of this work is part of the team's goal to make editing on mobile web simpler.

Before talking about the team's recent releases, we have a question for you:

Are you willing to try a new way to add and change links?

If you are interested, we would value your input! You can try this new link tool in the mobile visual editor on a separate wiki.

Follow these instructions and share your experience:

📲 Try Edit Cards.

Recent releases

[edit]

The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team has recently launched two new features to improve the mobile visual editor:

  1. Section editing
    • The purpose is to help contributors focus on their edits.
    • The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
  2. Loading overlay
    • The purpose is to smooth the transition between reading and editing.

Section editing and the new loading overlay are now available to everyone using the mobile visual editor.

New and active projects

[edit]

This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.

  • Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now. Go here to see how: 📲Try Edit Cards.
  • Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
  • Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor? We are collaborating with 20 Wikipedias to answer this question.
  • Usability improvements: This project will make the mobile visual editor easier to use.  The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.

Looking ahead

[edit]
  • Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019. They will lead a session about mobile editing in the Community Growth space. Talk to them about how editing can be improved.
  • Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.

Learning more

[edit]

The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.

PPelberg (WMF) (talk) and Whatamidoing (WMF) (talk) 21:25, 15 July 2019 (UTC)[reply]

The WikiProject Video Games Newsletter, Q2 2019

[edit]

The WikiProject Video Games Newsletter
Volume 11, No. 1 — 2nd Quarter, 2019
Previous issue | Index | Next issue

Project At a Glance
As of Q2 2019, the project has:

Content

Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.
(Delivered ~~~~~)

MediaWiki message delivery (talk) 22:10, 15 July 2019 (UTC)[reply]

Proposed deletion of File:Valve Task Force Header 2014.svg

[edit]
Notice

The file File:Valve Task Force Header 2014.svg has been proposed for deletion because of the following concern:

Unused WikiProject logo, task force has since been redirected to WP:VG and is unlikely to be resurrected

While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated files}} notice, but please explain why in your edit summary or on the file's talk page.

Please consider addressing the issues raised. Removing {{proposed deletion/dated files}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and files for discussion allows discussion to reach consensus for deletion. ♠PMC♠ (talk) 19:42, 29 July 2019 (UTC)[reply]

List Help

[edit]

Hello,

I see you fought to Keep articles like List of Games with Gold games and List of Instant Game Collection games (North America) some years ago. I started a List of free Epic Games Store games based on those two articles, which was quickly deleted. I think such deletion was too hasty and incorrect based upon the discovery that 'List of Games with Gold games' and 'List of Instant Game Collection games (North America)' already survived the articles of deletion.Would you be willing to fight Keep for the Epic list on Deletion review?

Thanks

--n64ra (talk) 19:56, 13 August 2019 (UTC)[reply]

WikiProject Video games Newsletter Q3

[edit]

The WikiProject Video Games Newsletter
Volume 11, No. 2 — 3nd Quarter, 2019
Previous issue | Index | Next issue

Project At a Glance
As of Q3 2019, the project has:

Content

Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.
(Delivered ~~~~~)

Editing News #2 – Mobile editing and talk pages – October 2019

[edit]

Read this in another language • Subscription list for this multilingual newsletter

Inside this newsletter, the Editing team talks about their work on the mobile visual editor, on the new talk pages project, and at Wikimania 2019.

Help

[edit]

What talk page interactions do you remember? Is it a story about how someone helped you to learn something new? Is it a story about how someone helped you get involved in a group? Something else? Whatever your story is, we want to hear it!

Please tell us a story about how you used a talk page. Please share a link to a memorable discussion, or describe it on the talk page for this project. The team would value your examples. These examples will help everyone develop a shared understanding of what this project should support and encourage.

Talk Pages

[edit]

The Talk Pages Consultation was a global consultation to define better tools for wiki communication. From February through June 2019, more than 500 volunteers on 20 wikis, across 15 languages and multiple projects, came together with members of the Foundation to create a product direction for a set of discussion tools. The Phase 2 Report of the Talk Page Consultation was published in August. It summarizes the product direction the team has started to work on, which you can read more about here: Talk Page Project project page.

The team needs and wants your help at this early stage. They are starting to develop the first idea. Please add your name to the "Getting involved" section of the project page, if you would like to hear about opportunities to participate.

Mobile visual editor

[edit]

The Editing team is trying to make it simpler to edit on mobile devices. The team is changing the visual editor on mobile. If you have something to say about editing on a mobile device, please leave a message at Talk:VisualEditor on mobile.

Edit Cards

[edit]
What happens when you click on a link. The new Edit Card is bigger and has more options for editing links.

Toolbar

[edit]
The editing toolbar is changing in the mobile visual editor. The old system had two different toolbars. Now, all the buttons are together. Tell the team what you think about the new toolbar.
  • In September, the Editing team updated the mobile visual editor's editing toolbar. Anyone could see these changes in the mobile visual editor.
    • One toolbar: All of the editing tools are located in one toolbar. Previously, the toolbar changed when you clicked on different things.
    • New navigation: The buttons for moving forward and backward in the edit flow have changed.
    • Seamless switching: an improved workflow for switching between the visual and wikitext modes.
  • Feedback: You can try the refreshed toolbar by opening the mobile VisualEditor on a smartphone. Please post your feedback on the Toolbar feedback talk page.

Wikimania

[edit]

The Editing Team attended Wikimania 2019 in Sweden. They led a session on the mobile visual editor and a session on the new talk pages project. They tested two new features in the mobile visual editor with contributors. You can read more about what the team did and learned in the team's report on Wikimania 2019.

Looking ahead

[edit]
  • Talk Pages Project: The team is thinking about the first set of proposed changes. The team will be working with a few communities to pilot those changes. The best way to stay informed is by adding your username to the list on the project page: Getting involved.
  • Testing the mobile visual editor as the default: The Editing team plans to post results before the end of the calendar year. The best way to stay informed is by adding the project page to your watchlist: VisualEditor as mobile default project page.
  • Measuring the impact of Edit Cards: The Editing team hopes to share results in November. This study asks whether the project helped editors add links and citations. The best way to stay informed is by adding the project page to your watchlist: Edit Cards project page.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk) 16:51, 17 October 2019 (UTC)[reply]

Global templates

[edit]

Hi!

I see that you were one of the people who supported the Global-Wiki idea on Meta. It was closed as "consensus", but it's far from being fully implemented. We did get global personal JS and CSS, global user pages, and global preferences, and all of this is excellent. However, we still don't have Global templates, and this is the most important thing.

I am trying to reboot the Global templates project. It's ambitious, but I am trying to make it focused on only templates and modules, and to break it up further into manageable and doable parts.

I wrote this similar proposal: mw:Global templates is the introduction, there are more details in mw:Global templates/Proposed specification, short version, and even more details in mw:Global templates/Proposed specification.

This proposal is a little smaller in scope than meta:Global-Wiki, but I have reasons to think that in this format it has a better chance of actually getting implemented.

I'd love to hear what do you think about it. If you support it, please sign at mw:Global templates/Discuss.

Thank you! --Amir E. Aharoni (talk) 12:22, 3 December 2019 (UTC)[reply]

Nomination of List of Games with Gold games for deletion

[edit]

A discussion is taking place as to whether the article List of Games with Gold games is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Wikipedia:Articles for deletion/List of Games with Gold games (2nd nomination) until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. Masem (t) 16:17, 30 December 2019 (UTC)[reply]

Hello, Nicereddy!
Please chime in over there, apparently, the pretty useful list made by you is going to be deleted( -- pr12402, January, 6, 2020

WikiProject Video games Newsletter Q4 2019

[edit]

The WikiProject Video Games Newsletter
Volume 11, No. 3 — 4th Quarter, 2019
Previous issue | Index | Next issue

Project At a Glance
As of Q4 2019, the project has:

Content

Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.
(Delivered ~~~~~)

WikiProject Video games Newsletter Q1 2020

[edit]

The WikiProject Video Games Newsletter
Volume 12, No. 1 — 1st Quarter, 2020
Previous issue | Index | Next issue

Project At a Glance
As of Q1 2020, the project has:

Content

Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.
(Delivered ~~~~~)

Editing news 2020 #1 – Discussion tools

[edit]

Read this in another language • Subscription list

Screenshot showing what the Reply tool looks like
This early version of the Reply tool automatically signs and indents comments.

The Editing team has been working on the talk pages project. The goal of the talk pages project is to help contributors communicate on wiki more easily. This project is the result of the Talk pages consultation 2019.

Reply tool improved with edit tool buttons
In a future update, the team plans to test a tool for easily linking to another user's name, a rich-text editing option, and other tools.

The team is building a new tool for replying to comments now. This early version can sign and indent comments automatically. Please test the new Reply tool.

  • On 31 March 2020, the new reply tool was offered as a Beta Feature editors at four Wikipedias: Arabic, Dutch, French, and Hungarian. If your community also wants early access to the new tool, contact User:Whatamidoing (WMF).
  • The team is planning some upcoming changes. Please review the proposed design and share your thoughts on the talk page. The team will test features such as:
    • an easy way to mention another editor ("pinging"),
    • a rich-text visual editing option, and
    • other features identified through user testing or recommended by editors.

To hear more about Editing Team updates, please add your name to the "Get involved" section of the project page. You can also watch these pages: the main project page, Updates, Replying, and User testing.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk) 15:45, 13 April 2020 (UTC)[reply]

Editing news 2020 #2 – Quick updates

[edit]

Read this in another language • Subscription list

Mockup of the new reply feature, showing new editing tools
The new features include a toolbar. What do you think should be in the toolbar?

This edition of the Editing newsletter includes information the Wikipedia:Talk pages project, an effort to help contributors communicate on wiki more easily. The central project page is on MediaWiki.org.

– Whatamidoing (WMF) (talk) 18:11, 15 June 2020 (UTC)[reply]

Editing news 2020 #3

[edit]
On 16 March 2020, the 50 millionth edit was made using the visual editor on desktop.

Seven years ago this week, the Editing team made the visual editor available by default to all logged-in editors using the desktop site at the English Wikipedia. Here's what happened since its introduction:

  • The 50 millionth edit using the visual editor on desktop was made this year. More than 10 million edits have been made here at the English Wikipedia.
  • More than 2 million new articles have been created in the visual editor. More than 600,000 of these new articles were created during 2019.
  • Almost 5 million edits on the mobile site have been made with the visual editor. Most of these edits have been made since the Editing team started improving the mobile visual editor in 2018.
  • The proportion of all edits made using the visual editor has been increasing every year.
  • Editors have made more than 7 million edits in the 2017 wikitext editor, including starting 600,000 new articles in it. The 2017 wikitext editor is VisualEditor's built-in wikitext mode. You can enable it in your preferences.
  • On 17 November 2019, the first edit from outer space was made in the mobile visual editor.
  • In 2019, 35% of the edits by newcomers, and half of their first edits, were made using the visual editor. This percentage has been increasing every year since the tool became available.

Whatamidoing (WMF) (talk) 02:06, 3 July 2020 (UTC)[reply]

WikiProject Video games Newsletter Q2 2020

[edit]

The WikiProject Video Games Newsletter
Volume 12, No. 2 — 2nd Quarter, 2020
Previous issue | Index | Next issue

Project At a Glance
As of Q2 2020, the project has:

Content

Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.
(Delivered ~~~~~)

03:23, 5 July 2020 (UTC)

Editing news 2020 #4

[edit]

Read this in another language • Subscription list for this newsletter

Reply tool

[edit]
The number of comments posted with the Reply Tool from March through June 2020. People used the Reply Tool to post over 7,400 comments with the tool.

The Reply tool has been available as a Beta Feature at the Arabic, Dutch, French and Hungarian Wikipedias since 31 March 2020. The first analysis showed positive results.

  • More than 300 editors used the Reply tool at these four Wikipedias. They posted more than 7,400 replies during the study period.
  • Of the people who posted a comment with the Reply tool, about 70% of them used the tool multiple times. About 60% of them used it on multiple days.
  • Comments from Wikipedia editors are positive. One said, أعتقد أن الأداة تقدم فائدة ملحوظة؛ فهي تختصر الوقت لتقديم رد بدلًا من التنقل بالفأرة إلى وصلة تعديل القسم أو الصفحة، التي تكون بعيدة عن التعليق الأخير في الغالب، ويصل المساهم لصندوق التعديل بسرعة باستخدام الأداة. ("I think the tool has a significant impact; it saves time to reply while the classic way is to move with a mouse to the Edit link to edit the section or the page which is generally far away from the comment. And the user reaches to the edit box so quickly to use the Reply tool.")[5]

The Editing team released the Reply tool as a Beta Feature at eight other Wikipedias in early August. Those Wikipedias are in the Chinese, Czech, Georgian, Serbian, Sorani Kurdish, Swedish, Catalan, and Korean languages. If you would like to use the Reply tool at your wiki, please tell User talk:Whatamidoing (WMF).

The Reply tool is still in active development. Per request from the Dutch Wikipedia and other editors, you will be able to customize the edit summary. (The default edit summary is "Reply".) A "ping" feature is available in the Reply tool's visual editing mode. This feature searches for usernames. Per request from the Arabic Wikipedia, each wiki will be able to set its own preferred symbol for pinging editors. Per request from editors at the Japanese and Hungarian Wikipedias, each wiki can define a preferred signature prefix in the page MediaWiki:Discussiontools-signature-prefix. For example, some languages omit spaces before signatures. Other communities want to add a dash or a non-breaking space.

New requirements for user signatures

[edit]
  • The new requirements for custom user signatures began on 6 July 2020. If you try to create a custom signature that does not meet the requirements, you will get an error message.
  • Existing custom signatures that do not meet the new requirements will be unaffected temporarily. Eventually, all custom signatures will need to meet the new requirements. You can check your signature and see lists of active editors whose custom signatures need to be corrected. Volunteers have been contacting editors who need to change their custom signatures. If you need to change your custom signature, then please read the help page.

Next: New discussion tool

[edit]

Next, the team will be working on a tool for quickly and easily starting a new discussion section to a talk page. To follow the development of this new tool, please put the New Discussion Tool project page on your watchlist.

Whatamidoing (WMF) (talk) 18:48, 31 August 2020 (UTC)[reply]

WikiProject Video games Newsletter Q3 2020

[edit]

The WikiProject Video Games Newsletter
Volume 12, No. 3 — 3rd Quarter, 2020
Previous issue | Index | Next issue

Project At a Glance
As of Q3 2020, the project has:

Content

Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.
(Delivered ~~~~~)

MediaWiki message delivery (talk) 02:10, 9 October 2020 (UTC)[reply]

The WikiProject Video Games Newsletter, Q4 2020

[edit]

The WikiProject Video Games Newsletter
Volume 12, No. 4 — 4th Quarter, 2020
Previous issue | Index | Next issue

Project At a Glance
As of Q4 2020, the project has:

Content

Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.
(Delivered 08:33, 4 January 2021 (UTC))

--MediaWiki message delivery (talk) 08:33, 4 January 2021 (UTC)[reply]

Editing news 2021 #1

[edit]

Read this in another language • Subscription list for this newsletter

Reply tool

[edit]
Graph of Reply tool and full-page wikitext edit completion rates
Completion rates for comments made with the Reply tool and full-page wikitext editing. Details and limitations are in this report.

The Reply tool is available at most other Wikipedias.

  • The Reply tool has been deployed as an opt-out preference to all editors at the Arabic, Czech, and Hungarian Wikipedias.
  • It is also available as a Beta Feature at almost all Wikipedias except for the English, Russian, and German-language Wikipedias. If it is not available at your wiki, you can request it by following these simple instructions.

Research notes:

  • As of January 2021, more than 3,500 editors have used the Reply tool to post about 70,000 comments.
  • There is preliminary data from the Arabic, Czech, and Hungarian Wikipedia on the Reply tool. Junior Contributors who use the Reply tool are more likely to publish the comments that they start writing than those who use full-page wikitext editing.[6]
  • The Editing and Parsing teams have significantly reduced the number of edits that affect other parts of the page. About 0.3% of edits did this during the last month.[7] Some of the remaining changes are automatic corrections for Special:LintErrors.
  • A large A/B test will start soon.[8] This is part of the process to offer the Reply tool to everyone. During this test, half of all editors at 24 Wikipedias (not including the English Wikipedia) will have the Reply tool automatically enabled, and half will not. Editors at those Wikipeedias can still turn it on or off for their own accounts in Special:Preferences.

New discussion tool

[edit]
Screenshot of version 1.0 of the New Discussion Tool prototype.

The new tool for starting new discussions (new sections) will join the Discussion tools in Special:Preferences#mw-prefsection-betafeatures at the end of January. You can try the tool for yourself.[9] You can leave feedback in this thread or on the talk page.

Next: Notifications

[edit]

During Talk pages consultation 2019, editors said that it should be easier to know about new activity in conversations they are interested in. The Notifications project is just beginning. What would help you become aware of new comments? What's working with the current system? Which pages at your wiki should the team look at? Please post your advice at mw:Talk:Talk pages project/Notifications.

–Whatamidoing (WMF) (talk) 01:02, 23 January 2021 (UTC)[reply]

The WikiProject Video Games Newsletter, Q1 2021

[edit]

The WikiProject Video Games Newsletter
Volume 13, No. 1 — 1st Quarter, 2021
Previous issue | Index | Next issue

Project At a Glance
As of Q1 2021, the project has:

Content

Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.
(Delivered 13:42, 9 April 2021 (UTC))

-- MediaWiki message delivery (talk) 13:42, 9 April 2021 (UTC)[reply]

Editing news 2021 #2

[edit]

Read this in another language • Subscription list for this newsletter

Junior contributors comment completion rate across all participating Wikipedias
When newcomers had the Reply tool and tried to post on a talk page, they were more successful at posting a comment. (Source)

Earlier this year, the Editing team ran a large study of the Reply Tool. The main goal was to find out whether the Reply Tool helped newer editors communicate on wiki. The second goal was to see whether the comments that newer editors made using the tool needed to be reverted more frequently than comments newer editors made with the existing wikitext page editor.

The key results were:

  • Newer editors who had automatic ("default on") access to the Reply tool were more likely to post a comment on a talk page.
  • The comments that newer editors made with the Reply Tool were also less likely to be reverted than the comments that newer editors made with page editing.

These results give the Editing team confidence that the tool is helpful.

Looking ahead

The team is planning to make the Reply tool available to everyone as an opt-out preference in the coming months. This has already happened at the Arabic, Czech, and Hungarian Wikipedias.

The next step is to resolve a technical challenge. Then, they will deploy the Reply tool first to the Wikipedias that participated in the study. After that, they will deploy it, in stages, to the other Wikipedias and all WMF-hosted wikis.

You can turn on "Discussion Tools" in Beta Features now. After you get the Reply tool, you can change your preferences at any time in Special:Preferences#mw-prefsection-editing-discussion.

–Whatamidoing (WMF) (talk)

00:27, 16 June 2021 (UTC)

ArbCom 2021 Elections voter message

[edit]
Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2021 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:36, 23 November 2021 (UTC)[reply]

Editing newsletter 2022 – #1

[edit]

Read this in another language • Subscription list for the multilingual newsletter • Local subscription list

New editors were more successful with this new tool.

The New topic tool helps editors create new ==Sections== on discussion pages. New editors are more successful with this new tool. You can read the report. Soon, the Editing team will offer this to all editors at most WMF-hosted wikis. You can join the discussion about this tool for the English Wikipedia is at Wikipedia:Village pump (proposals)#Enabling the New Topic Tool by default. You will be able to turn it off in the tool or at Special:Preferences#mw-prefsection-editing-discussion.

The Editing team plans to change the appearance of talk pages. These are separate from the changes made by the mw:Desktop improvements project and will appear in both Vector 2010 and Vector 2022. The goal is to add some information and make discussions look visibly different from encyclopedia articles. You can see some ideas at Wikipedia talk:Talk pages project#Prototype Ready for Feedback.

Whatamidoing (WMF) (talk)

23:14, 30 May 2022 (UTC)

Feedback on Vector (2022) conversation

[edit]
The slides to our latest Wikimania presentation

Hello! As a member of WikiProject Usability, I wanted to draw your attention to a conversation currently underway on WP:VPR (see the beginning of the discussion) around adopting Vector 2022 as the new default skin.

The Web team at the Wikimedia Foundation has been working on Vector 2022 for the past three years, collaborating with the English Wikipedia community as well as other wikis to ensure that the skin performs better qualitatively and quantitatively for readers and communities than the previous Vector skin. The goal of the new skin is to create a more welcoming and easier to use experience for readers and editors across the wiki. For more details, see our new FAQ.

For the past couple of months, we have collected thoughts from the English Wikipedia community on what changes need to be made to the skin prior to it being considered ready for deployment. Our next step would be to start an RfC to assess whether the community considers Vedtor 2022 ready.

Prior to the beginning of the RfC, we wanted to draw your attention to the current conversation and encourage your feedback on the skin.

Our results from Vector 2022 at a glance
  • The sticky header makes it easier to access tools that editors use often. It decreases scrolling to the top of the page by 16%
  • The new table of contents makes it easier to navigate to different sections. Readers and editors jumped between sections 50% more than with the old table of contents
  • The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the wikis we tested on
  • The collapsible sidebar allows readers and editors to choose whether they want to see the main menu or not. Our testing shows that this allows people to better focus on their current task - reading with a collapsed menu, or editing with an open menu
  • The language switching menu makes it possible to switch languages without scrolling
  • The user menu collects all user links in a single place, making it easier to understand what each link does. In testing, 71% of surveyed editors reported positive experiences with the new menu

Thank you, OVasileva (WMF), SGrabarczuk (WMF) (talk) 12:27, 25 August 2022 (UTC)[reply]

Editing news 2022 #2

[edit]

Read this in another language • Subscription list for this multilingual newsletter

Graph showing 90-minute response time without the new tool and 39-minute response time with the tool
The [subscribe] button shortens response times.

The new [subscribe] button notifies people when someone replies to their comments. It helps newcomers get answers to their questions. People reply sooner. You can read the report. The Editing team is turning this tool on for everyone. You will be able to turn it off in your preferences.

–Whatamidoing (WMF) (talk) 00:35, 26 August 2022 (UTC)[reply]

Category:GoldSrc games has been nominated for discussion

[edit]

Category:GoldSrc games has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. Respiciens (talk) 10:36, 13 October 2022 (UTC)[reply]

Editing news 2023 #1

[edit]

Read this in another language • Subscription list for this newsletter

This newsletter includes two key updates about the Editing team's work:

  1. The Editing team will finish adding new features to the Talk pages project and deploy it.
  2. They are beginning a new project, Edit check.

Talk pages project

Screenshot showing the talk page design changes that are currently available as beta features at all Wikimedia wikis. These features include information about the number of people and comments within each discussion.
Some of the upcoming changes

The Editing team is nearly finished with this first phase of the Talk pages project. Nearly all new features are available now in the Beta Feature for Discussion tools.

It will show information about how active a discussion is, such as the date of the most recent comment. There will soon be a new "Add topic" button. You will be able to turn them off at Special:Preferences#mw-prefsection-editing-discussion. Please tell them what you think.

Daily edit completion rate by test group: DiscussionTools (test group) and MobileFrontend overlay (control group)

An A/B test for Discussion tools on the mobile site has finished. Editors were more successful with Discussion tools. The Editing team is enabling these features for all editors on the mobile site.

New Project: Edit Check

The Editing team is beginning a project to help new editors of Wikipedia. It will help people identify some problems before they click "Publish changes". The first tool will encourage people to add references when they add new content. Please watch that page for more information. You can join a conference call on 3 March 2023 to learn more.

–Whatamidoing (WMF) (talk) 18:19, 22 February 2023 (UTC)[reply]

Latest (and most likely final) issue of the WP:VG newsletter

[edit]

The WikiProject Video Games Newsletter
Volume 14, No. 1 — 1st Quarter, 2023
Previous issue | Index

Project At a Glance
As of Q4 2022, the project has:

Content

Project Navigation
To opt-out or sign up to receive future editions of this newsletter, click here to update the distribution list.

Delivered by: MediaWiki message delivery (talk) 09:40, 8 March 2023 (UTC)[reply]

ArbCom 2023 Elections voter message

[edit]

Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:42, 28 November 2023 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Nicereddy&oldid=1187210816"