This is an archive of past discussions with User:Tom Morris. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Students worked on new datatype to capture mathematical expressions (phabricator:T67397)
Updated property suggester data to give you more up-to-date suggestions when adding new statements
Pages in the module namespace now also get interwiki links (phabricator:T123234)
Reduced number of resource loader modules to improve performance (phabricator:T123233)
Started experimenting with showing an image in the header area (phabricator:T119493)
Fixed a bug where the query text would be moved off the screen on the query service website (phabricator:T120196)
Worked on the remaining blocker for taking the in other projects sidebar out of beta. We need to link to the Commons category and not gallery for articles without frying the servers (phabricator:T94989)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
You will be able to find or mark bugs and suggestions in Phabricator that are specific for your language or wiki. [1]
Notifications have been upgraded with more detailed and easier-to-access information. See the documentation. Cross-wiki notifications will be available soon on the two test wikis. [2]
Changes this week
The visual editor uses the TemplateData extension to make editing templates easier. You will now get a warning when you edit a TemplateData form and leave it without saving. [3]
MediaWiki will get a new authentication and authorization system called AuthManager. This is planned to happen in a month or two. Some bots will need to change how they log in. Two new and more stable authentication methods will be available now: Owner-only OAuth credentials and bot passwords. You can read more about the change. [4]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 19 January. It will be on non-Wikipedia wikis and some Wikipedias from 20 January. It will be on all Wikipedias from 21 January (calendar).
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 19 January at 20:00 (UTC). See how to join.
You can join the next meeting with the Architecture committee. The topic this week is governance model. The meeting will be on 20 January at 22:00 (UTC). See how to join.
Hello there! Happy to be writing this newsletter once more. This month:
What comes next
Some good news: the Wikimedia Foundation has renewed WikiProject X. This means we can continue focusing on making WikiProjects better.
During our first round of work, we created a prototype WikiProject based on two ideas: (1) WikiProjects should clearly present things for people to do, and (2) The content of WikiProjects should be automated as much as possible. We launched pilots, and for the most part it works. But this approach will not work for the long term. While it makes certain aspects of running a WikiProject easier, it makes the maintenance aspects harder.
We are working on a major overhaul that will address these issues. New features will include:
Creating WikiProjects by simply filling out a form, choosing which reports you want to generate for your project. This will work with existing bots in addition to the Reports Bot reports. (Of course, you can also have sections curated by humans.)
One-click button to join a WikiProject, with optional notifications.
Be able to define your WikiProject's scope within the WikiProject itself by listing relevant pages and categories, eliminating the need to tag every talk page with a banner. (You will still be allowed to do that, of course. It just won't be required.)
The end goal is a collaboration tool that can be used by WikiProjects but also by any edit-a-thon or group of people that want to coordinate on improving articles. Though implemented as an extension, the underlying content will be wikitext, meaning that you can continue to use categories, templates, and other features as you normally would.
This will take a lot of work, and we are just getting started. What would you like to see? I invite you to discuss on our talk page.
Note: All columns in this table are sortable, allowing you to rearrange the table so the articles most interesting to you are shown at the top. All images have mouse-over popups with more information. For more information about the columns and categories, please consult the documentation and please get in touch on SuggestBot's talk page with any questions you might have.
SuggestBot picks articles in a number of ways based on other articles you've edited, including straight text similarity, following wikilinks, and matching your editing patterns against those of other Wikipedians. It tries to recommend only articles that other Wikipedians have marked as needing work. We appreciate that you have signed up to receive suggestions regularly; your contributions make Wikipedia better — thanks for helping!
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
You can now follow when pages are added or removed from a category on German Wikipedia. The plan is to add it to Wikimedia Commons and other Wikipedias this week. [5][6]
Administrators can hide individual entries of a page with RevisionDelete. There is now a button to choose "all", "none" or "inverse" in Special:Log. The article history will get the same buttons soon. Wikis that have done this locally with JavaScript will be able to remove that code. [7]
Changes this week
You will be able to see the references when you preview a section you are editing. This will happen even if there is no <references /> tag in that section. [8]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 26 January. It will be on non-Wikipedia wikis and some Wikipedias from 27 January. It will be on all wikis from 28 January (calendar).
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 26 January at 20:00 (UTC). See how to join.
Future changes
There is now an extension called ArticlePlaceholder. It can automatically generate content on Wikipedia with data from Wikidata if there is no Wikipedia article. It will have a tag to remind the reader it is not an article and ask the reader to create one. The developer is now looking for smaller Wikipedias that want to try the extension. [9]
The OTRS system will be upgraded. The plan is to do this on 3 February at 08:00 (UTC). It will probably take 6 to 8 hours. OTRS will be down during the upgrade. [10]
Users will soon be automatically congratulated when they reach some edit count milestones. [11]
Changes in how authentication in MediaWiki is handled are being rolled out (and more coming). [12] Ordinary users and gadgets / user scripts should not be affected but bots may need to be adjusted. pywikibot already supports [13] OAuth authentication, though bot operators need to set that up for their bot.
Investigated language support in MediaWiki and Wikibase to allow more languages in monolingual text and disallow some non-sense for label/descriptions/aliases (phabricator:T78006)
Fixed missing license info and broken links for Wikibase libraries on Special:Version
Working on improving scoring of search results on Wikidata, on Special:Search
Preparing to take the "in other projects" sidebar out of beta features, with the Wikimedia Commons link going to the Commons category (phabricator:T103102, phabricator:T94989)
Amir and Aaron are turning ORES into an extension to make it easier for you to spot bad edits \o/
Final touches on putting identifiers into their own section (phabricator:T117421)
Switching the in other languages box to be expanded by default for new people (phabricator:T92387)
More experimenting with adding an image to the header area (phabricator:T119493)
The article describes a term used in critical circles, usually linked to marxist thinking, but not exclusively. It is already quoted in the first paragraph that it comes from a critical perspective, not widely used still by the general population, although increasingly used in Spain, specially in LGBTI movements. Even if it is linked to pink money, it does not refer to the same thing (the same happens with purchasing power, isn't the same as capitalism), as it links not only western capitalist economy with LGBT issues, but also with sociology.
Although I also consider YouTube references are usually not the best ones, three of them are part of an academic conference about Pink Capitalism given by spanish LGBTI activists and academic researchers, and the other one is a news item from the Spanish Television, so in this case I think they may be appropriate. In any case, these references are usually together with other ones that complete the paragraphs. I can check them in case they are alone to supplement the references with another article or book chapter.
About merging the article with a wider one about LGBTI economy, I don't think it would fit. The point is that Pink capitalism is used to refer to the processes written in the article. However, another article called LGBTI economy or LGBTI capitalism would be very interesting, incorporating other points of view, and maybe including a subpart with an abstract about pink capitalism.
Finally, just another thing. The article is not an original research. It all come from the quoted sources, intralinks and external links. It is true that is a translation from Spanish and perhaps it is difficult for English speakers to access that information. Also, there are some wikipages in Spanish that may contain some information that is not possible to link in English as those pages do not exist.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Problems
Sites with a wikimedia.org address were by mistake redirected to the Wikimedia Foundation wiki on 26 January. This included Meta and Wikimedia Commons. The mistake was fixed after an hour. [14]
Some users had problems logging in and out around 22 January. Bots also had problems and edit previews did not work properly. This was because of problems related to the new component SessionManager. It was undone on 23 January. [15][16]
Because of new problems with SessionManager the latest version of MediaWiki was removed from the Wikimedia wikis again on 31 January. The new version this week will be without SessionManager. [17]
Changes this week
The page history will get a help link. This will go to Help:Page history on Meta. Wikis can exchange it for a link to their local pages. [18]
Notifications will only show part of a page name if it is very long. You will also have another way to mark notifications as read. [19][20]
The Universal Language Selector input methods are now available with the visual editor. This means many who write in non-Latin scripts can now use the visual editor. [21]
The visual editor will now give you more tools to edit tables. You can move rows and columns in a table and copy parts of tables to make new ones. You can also copy and paste more than one cell at the same time. [22][23][24]
The visual editor has a new warning message when you leave a page you are editing without saving. Non-English wikis might need to translate it. [25][26]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 2 February. It will be on non-Wikipedia wikis and some Wikipedias from 3 February. It will be on all wikis from 4 February (calendar).
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 2 February at 20:00 (UTC). See how to join.
The rest.wikimedia.org domain will be shut down. This is planned to happen in March. You should use /api/rest_v1/ at each individual project domain instead. [27]
