跳转到内容

维基百科:互助客栈/消息/存档/2021年6月

添加链接
维基百科，自由的百科全书

Wikidata weekly summary #471

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • You can now add a title to a query visualisation by adding #title:YourTitle to your SPARQL code (phab:T225883, example query with a title)
    • Added a new constraints type to indicate that a certain Property should only be used on Lexemes of a certain language (phab:T200689)
    • Working on not checking the format constraints via SPARQL to take that load off the SPARQL endpoint and make it technically better (phab:T176312)
    • Working on making the API-Sandbox not suggest edits to real Items (phab:T219215)


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.

《中文维基百科站务案例集·存废复核案例集·2021年卷》1-5月快报

下述选编自《中文维基百科站务案例集·存废复核案例集·2021年卷》的案例，可能对最频繁出现的站务处理具有参考或指导作用：

号 案号 案名 案情要点 裁定结果 裁判管理员
1 2021年1月存废复核第11号 重定向页面《脚异味》、《足部异味》、《臭的脚》存废复核案 批量建立的口语重定向是否适用快速删除方针准则G3 维持原决：删除 KirkLU
4 2021年1月存废复核第23号 模板页面《2017年香港播出之动画》存废复核案 出于站务维护清理需要的模板删除提请是否满足删除方针理由第9项的要求 推翻原决：删除 Wong128hk
6 2021年2月存废复核第8号 图片《吉林省标准地图 1：450万政区版.jpg》、模板页面《PRC-StandardMap》存废复核案 中华人民共和国政府测绘地理信息行政主管部门向社会公布的公益性地图是否满足“知识共享 署名-相同方式共享 3.0”协议 维持原决：删除 AT
8 2021年2月存废复核第32号 条目页面《台风夏浪 (2019年)》存废复核案 利用特定手段观测或特定年份的风力最大值是否是关注度(气旋)指引准则第2项所指的“相关气象纪录” 维持原决：保留 KirkLU
9 2021年2月存废复核第33号 重定向页面《新莱茵报。民主派机关报》存废复核案 有可靠来源使用但显著错误的别名重定向是否适用快速删除方针准则R3 推翻原决：恢复 Techyan
11 2021年3月存废复核第14号 条目页面《上海民族党》存废复核案 行文引文高度类似但有新来源的原关注度不足条目是否适用快速删除方针准则G5 发还：存废讨论 Antigng
12 2021年3月存废复核第175号 图片《Microsoft Visual Studio Code 1.53.2 zh CN.png》存废复核案 基于开源代码的专有软件的界面截图是否是自由版权的 推翻原决：恢复 虫虫飞
13 2021年5月存废复核第26号 条目页面《马玉灵》存废复核案 关注度(人物)指引收录条件第6项的“主要演员”如何认定 推翻原决：删除 KirkLU
15 2021年5月存废复核第40号 条目页面《陈俊龙 Dr.Leon Chen》存废复核案 快速删除方针准则G11中所规定的“宣传内容”应如何认定 维持原决：删除 Wcam

要旨：

  • 存复集 卷2021 1号：大量口语重定向可适用WP:G3处理。（原存档于[2021]DRV-01/06-11{RDRT}）
  • 存复集 卷2021 4号：出于善意整理目的提删模板时，可视情况从宽适用删除方针理由第9项。（原存档于[2021]DRV-01/10-23{TPLT}）
  • 存复集 卷2021 6号：中华人民共和国政府有关部门公布的公益性地图不满足“知识共享 署名-相同方式共享 3.0”协议（原存档于[2021]DRV-02/03-8{FILE}）
  • 存复集 卷2021 8号：基于特定观测手段、特定年份界定的纪录不认为是关注度(气旋)指引准则第1项所指的“相关气象纪录”。（原存档于[2021]DRV-02/14-32{ATCL}）
  • 存复集 卷2021 9号：有可靠来源使用但显著错误的别名重定向不适用WP:R3（原存档于[2021]DRV-02/15-33{RDRT}）
  • 存复集 卷2021 11号：由于内容的细微变化（如，补充可能足以证明关注度的来源），原有的删除理据已经明显消除或已经不充分的，不适用G5。（原存档于[2021]DRV-03/04-14{ATCL}）
  • 存复集 卷2021 12号：基于开源代码的专有软件的界面截图并不自然具有自由版权，需综合考虑该专有软件的版权协议决定；但截图所含元素不超过原创性门槛（threshold of originality）时，截图仍然为自由版权（原存档于[2021]DRV-03/29-175{FILE}）
  • 存复集 卷2021 13号：关注度(人物)指引收录条件第6项的“主要演员”应根据方针优先参照“各影视颁奖礼最佳男/女主角的提名的分量”处理。（原存档于[2021]DRV-05/09-26{ATCL}）
  • 存复集 卷2021 15号：是否“页面只作宣传之用”应从页面的内容客观上实现了宣传的效果和页面的主要编辑主观上具有进行宣传的意图或动机两方面考虑。（原存档于[2021]DRV-05/14-40{ATCL}）

以上。--Kirk # 2021年6月8日 (二) 13:38 (UTC)

@KirkLU：“有可靠来源使用但显著错误的别名重定向是否适用快速删除方针准则G3”？#9不是“显著错误的别名重定向”。可能是我理解错了。题外话：我个人对这里所列出的涉及版权的诸多判例的结果并不满意，并应当在某些方面慎引以往判例。--Techyan（留言） 2021年6月8日 (二) 13:52 (UTC)
是关于R3，已更正。Wikipedia:存废复核请求/存档/2021年2月#新莱茵报。民主派机关报这个我是这么理解的：
  • 方针规定R3的第四种情形是“标题中使用非常见的错别字”；
  • 实务中我操作采用的是（见此第五章）“标题中含有错误使用的标点符号的，参考适用情形四”；
  • “新莱茵报。民主派机关报”这个句号和规范汉语的句号用法冲突，正常翻译的话应该用冒号或者破折号一类的。
  • 不过有可靠来源翻译如此，才得出保留的结论。--Kirk # 2021年6月8日 (二) 14:00 (UTC)
@Techyan：忘ping。--Kirk # 2021年6月8日 (二) 14:01 (UTC)
不过无论如何，这些也不是方针，所以可以灵活使用，如果有什么很极端的情况，应该可以逐个处理。--Kirk # 2021年6月8日 (二) 14:05 (UTC)
看报纸的配图，那个位置的确本来就是个句号。翻译时，将其直接翻译成中文句号似乎并没有太多不妥。即使是在西文，这个地方按常理也应该使用冒号。并且也如我在DRV里面所说，英语维基用的是冒号，但德语维基是句号。因此我不认为这算“明显错误”，而是正常用法。--Techyan（留言） 2021年6月8日 (二) 15:08 (UTC)
@Techyan：这方面我是这样考虑的：
  1. 西文（德文）句号和中文句号功用并非对应，只有在表示句子结束等中外文句号功用一致的情况下，“.”才对应翻译成“。”，否则有违格式手册所参考的各种标点规范的要旨；（如果举例没错的话）这跟日文的顿号不会直接原封不动纳入译文，而是视情况转为中文逗号也是相似的；
  2. 西文（德文）句号起类似分隔注释功能时，就不应当与中文句号（“。”）挂钩，因为中文句号并不起到这类作用；且中文语境也不是截然不存在西文点号，这一点在类似《文后参考文献著录规则》（GB/T 7714-2015）一类的标准中可以得到证实；
  3. 最后，也许不构成理由，但这个句号看着就感觉像是错的；如果不是有可靠来源这样翻译的话，直觉上也不会有这种选择。
一言以蔽之，即——正确的标点转化，是功用对应而不是形式（点号的名称）对应，所以考虑是明显用错。--Kirk # 2021年6月10日 (四) 12:22 (UTC)
  • @KirkLU：我看了一眼Commons的存废讨论，“File:Microsoft Visual Studio Code 1.53.2 zh CN.png”最终的保留理由实际上是因为美国的原创性门槛很低，这样的图文排版不足以达到原创性。解读为“基于开源代码的专有软件的界面截图考虑为自由版权”恐怕欠妥。--DreamerBlue（留言） 2021年6月10日 (四) 03:39 (UTC)
    @DreamerBlue：谢谢指正，这是个大错误，看完commons发现其实我刚好说反了。已变更为“基于开源代码的专有软件的界面截图并不自然具有自由版权，需综合考虑该专有软件的版权协议决定；但截图所含元素不超过原创性门槛（threshold of originality）时，截图仍然为自由版权”。--Kirk # 2021年6月10日 (四) 12:28 (UTC)

This Month in GLAM: May 2021



Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Universal Code of Conduct News – Issue 1

Universal Code of Conduct News
Issue 1, June 2021Read the full newsletter

Welcome to the first issue of Universal Code of Conduct News! This newsletter will help Wikimedians stay involved with the development of the new code, and will distribute relevant news, research, and upcoming events related to the UCoC.

Please note, this is the first issue of UCoC Newsletter which is delivered to all subscribers and projects as an announcement of the initiative. If you want the future issues delivered to your talk page, village pumps, or any specific pages you find appropriate, you need to subscribe here.

You can help us by translating the newsletter issues in your languages to spread the news and create awareness of the new conduct to keep our beloved community safe for all of us. Please add your name here if you want to be informed of the draft issue to translate beforehand. Your participation is valued and appreciated.

  • Affiliate consultations – Wikimedia affiliates of all sizes and types were invited to participate in the UCoC affiliate consultation throughout March and April 2021. (continue reading)
  • 2021 key consultations – The Wikimedia Foundation held enforcement key questions consultations in April and May 2021 to request input about UCoC enforcement from the broader Wikimedia community. (continue reading)
  • Roundtable discussions – The UCoC facilitation team hosted two 90-minute-long public roundtable discussions in May 2021 to discuss UCoC key enforcement questions. More conversations are scheduled. (continue reading)
  • Phase 2 drafting committee – The drafting committee for the phase 2 of the UCoC started their work on 12 May 2021. Read more about their work. (continue reading)
  • Diff blogs – The UCoC facilitators wrote several blog posts based on interesting findings and insights from each community during local project consultation that took place in the 1st quarter of 2021. (continue reading)

--MediaWiki message delivery（留言） 2021年6月11日 (五) 23:05 (UTC)

Wikidata weekly summary #472

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Wikidata Community/Diversity 2021 Survey has been published. The results are meant to serve as a baseline to see how the community might (not) change in the future.
    • WikidataCon 2021: A sustainable future for Wikidata. Information about "the conference theme, its three-day program structure and a special project on diversity taking place before the conference itself".
    • The call for candidates for 2021 Wikimedia Foundation Board elections has begun on June 9. The last date to apply is June 29, 2021.
  • Development
    • Working on no longer using the Query Service to evaluate Constraints Checks regular expressions (this should make our checks faster and allow for further improvements) (phab:T176312)
    • Changing the rate limits for assigning Item IDs further, which should result in even fewer Q-IDs being skipped in the future (phab:T284538)
    • Finalizing the concepts for a tool to help work on mismatches between Wikidata's data and other databases/websites/...

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.

《维基百科政策简报》2021年5月号

维 基 百 科 政 策 简 报
— 每月一期，掌握政策脉动 —

过去一个月（2021年5月1日至2021年5月31日）内，中文维基百科之重要人事及政策变动大致如下，个别项目基本依变动或施行时间先后排序：

人事动态 人事动态

方针与指引重要变动 方针与指引重要变动：重大的方针与指引修订。过去一个月内，互助客栈方针区共有方针与指引相关新提案25项，另有7项方针与指引相关提案获得通过：

  1. 《命名常规（化学）》：规范化学物质条目名称，避免未经社群讨论的移动。（讨论纪录）
  2. 《命名常规》暨《非条目页面命名方针》：建立页面命名一致性的通用（普遍性）规定。（讨论纪录）
  3. 《快速删除方针》：将维基专题命名空间纳入G14准则条文中（讨论纪录），后调整R2准则条文，禁止建立跨计画与维基专题命名空间的捷径重定向（讨论纪录）；相关模组一并修订。
  4. 《格式手册（两岸四地用语）》：调整〈国籍〉一节中标示人物（前）国籍的规定。（讨论纪录）
  5. 《标志指引》：在〈上传非自由标志〉一节中新增关于可缩放向量图形（SVG）非自由标志的规定，禁止使用自行制作或来自第三方网站的向量图形。（讨论纪录）
  6. 《COVID-19条目共识》：规范条目标题、内文中对严重急性呼吸道症候群冠状病毒2型（SARS-CoV-2）变种的称呼，并规范重定向页面标题中含对SARS-CoV-2变种称呼者的处理。（讨论纪录）

其他方针与指引杂项修订 其他方针与指引杂项修订，包括未于互助客栈方针区讨论而进行之小修改、方针与指引之相应修订或事实性修订等。请核查此等修订，若有需要，可提案至互助客栈方针区复议。

其他重要社群动态 其他重要社群动态：此处列出的动态虽不一定与正式方针或指引有关，惟对维基百科之社群或站务运作有一定影响。

Wikidata weekly summary #473

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Interlanguage links now work for multilingual Wikisource. phab:T275958
    • User:Nikki/LexemeEntitySuggester.js now supports searching for senses for the translation property.
    • The call for candidates for 2021 Wikimedia Foundation Board elections has begun on June 9. The last date to apply is June 29, 2021.
    • Since the beginning of the month, phabricator tickets about language codes (and names of languages) were reviewed and triaged to better reflect their content and current status. Some work was done to better identify the steps for such changes, highlight and address bottlenecks and system issues. Patches for a few codes were contributed and are being released. Phabricator "Language codes" workboard provides an overview, phab:T284856 attempts to identify maintenance steps and phab:T284276 determine turn-around times. phab:T284808 should finally close a gap in termbox language handeling. A way to better address some or all aspects of changes of language codes applicable to Wikipedia editions still needs to be found. Don't hesitate to request the addition or update of language names (e.g. the name of Dutch in Danish) or missing language codes, notably for monolingual strings (see Help:Monolingual text languages).

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.

This Month in Education: June 2021

This Month in Education

Volume 10 • Issue 6 • June 2021

Contents • Headlines • Subscribe

In This Issue

The visual editor

本主题或以下段落文字，移动自Wikipedia:互助客栈/其他。执行人：LightyearsTalk·Sign#维猫报 2021年6月15日 (二) 15:31 (UTC)。

Hello, all. 请帮助翻译至您的语言.

My teammate @Trizek (WMF) works with the mw:Growth team, and he tells me that the Chinese Wikipedia can have Growth's tools for new editors (see mw:Growth/Feature summary). At most Wikipedias, new editors use the visual editor for their first few edits. The visual editor is still in Special:参数设置#mw-prefsection-betafeatures (the mw:Beta Features system) here.

Years ago, the visual editor was not very good with the language/script variants. It has improved – but unfortunately, I don't read or type in Chinese. Do you all think that the visual editor is a good option for new editors here? Does it work reliably? Please let me know what you think.

--Whatamidoing (WMF)（留言） 2021年6月14日 (一) 22:25 (UTC)

大家好。 我的同事@Trizek (WMF)在mw:Growth小组工作，他告诉我中文维基百科的新手编辑可以使用Growth的工具（参见mw:Growth/Feature summary）。在很多语言版本的维基百科中，新编辑都是使用可视化编辑器进行他们一开始的几次编辑。可视化编辑器的开关依旧在Special:参数设置#mw-prefsection-betafeatures (mw:Beta Features system) 中。

几年前，可视化编辑器在语言和脚本的变种中工作的并不是很好。但该问题现已得到改善——但很不幸，我不能用中文读或写。请问你们大家都觉得对中文维基的新手编辑来说可视化编辑器是个好的选择吗？可视化编辑器的工作是否可靠？请让我知道你们的想法。

翻译：LightyearsTalk·Sign#维猫报 2021年6月15日 (二) 02:14 (UTC)

Server switch

Read this message in another language • 请帮助翻译至您的语言

The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that 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 do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. 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 up to an hour on Tuesday, 29 June 2021. The test will start at 14:00 UTC (07:00 PDT, 10:00 EDT, 15:00 WEST/BST, 16:00 CEST, 19:30 IST, 23:00 JST, and in New Zealand at 02:00 NZST on Wednesday 30 June).
  • 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 code freezes for the week of June 28. Non-essential code deployments will not happen.
This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. A banner will be displayed on all wikis 30 minutes before this operation happens. Please share this information with your community.

SGrabarczuk (WMF) 2021年6月27日 (日) 01:19 (UTC)

简而言之，从本月二十九号下午两点（UTC时间）开始，一个小时内将不能进行编辑。--安忆Talk 2021年6月27日 (日) 03:10 (UTC)
在某些必要的情况下他们会推迟上述时间。具体以时间表和提前半小时在网页顶部显示的中央通知为准。--安忆Talk 2021年6月27日 (日) 03:26 (UTC)

The Signpost: 27 June 2021

News, reports and features from the English Wikipedia's weekly journal about Wikipedia and Wikimedia
Read this Signpost in full · Single-page · Unsubscribe · Global message delivery 2021年6月27日 (日) 20:17 (UTC)

Wikidata weekly summary #474

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Mismatch Finder: We started building the foundation of the place that will store the mismatches between Wikidata and other databases/catalogs/...
    • Continued work on migrating the checks of regular expressions for constraints from SPARQL to a better solution to take that load off of the SPARQL endpoint (phab:T176312)
    • Made it possible to show language links from multilingual Wikisource to the other language versions of Wikisource (phab:T275958)
    • Added a new constraint type to indicate that a certain Property should only be used on Lexemes with a specific language (phab:T200689)
    • Fixed a weird issue with suggesters popping back up when they shouldn't (phab:T284219)
    • Invalid data will not be handled better in RDF outputs (phab:T285131)
    • Working on lowering the rate limit at which a misbehaving bot can waste new Item IDs to further reduce the percentage of skipped Item IDs (phab:T284538)
    • Working on not suggesting real Item IDs in the API sandbox to avoid accidental edits by people who think it is not making real edits (phab:T219215)
    • Working on reducing the time it takes between entering a value in a new statement and being able to save the statement (phab:T281669)
    • Improved documentation of the usage tracking aspects in API help pages. Usage tracking is an internal mechanism to track which article on Wikipedia etc uses which data from an Item on Wikidata. (phab:T283040)
    • Language codes for monolingual strings "gsw-fr", "ykg", "wya", "osa-latn" were made available: Alsatian, Tundra Yukaghir, Wendat, Osage (phab:T262922, phab:T252198, phab:T283364, phab:T265297)
    • The English name for language code "crh" and the Swedish name for "fa" were corrected (phab:T240350, phab:T281702)
    • Lexeme language codes ha-arab, sux-latn, sux-xsux, gsg, tlh-piqd, tlh-latn, bfi, pwn, enm were added. That is Hausa in Arabic script, Sumerian in cuneiform and Latin-script, German Sign Language, Klingon in pIqaD and Latin script, British Sign Language, Paiwan and Middle English. (phab:T282512, phab:T279557)
    • It was determined that language codes can be activated for Wikidata while being blocked for use on Incubator (phab:T273705), this to avoid projects such as a "British English Wikipedia"
    • Language code "es-419" for Latin American Spanish has been available for labels and descriptions for quite some time (phab:T230786)
    • A possibly confusing Russian mis-translation of the name of the language code for "multiple languages" (mul) is being reviewed (phab:T245927)
    • "en-simple:" can be used instead of "simple:" to link to Simple Wikipedia. Query Services outputs "en-simple", not "simple" for sitelinks to Simple Wikipedia (phab:T283149).
    • There was some discussion about the creation of a language code "en-in" for monolingual strings, but "en-in" as interface language seems to be preferred (phab:T212313)

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 #474

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Mismatch Finder: We started building the foundation of the place that will store the mismatches between Wikidata and other databases/catalogs/...
    • Continued work on migrating the checks of regular expressions for constraints from SPARQL to a better solution to take that load off of the SPARQL endpoint (phab:T176312)
    • Made it possible to show language links from multilingual Wikisource to the other language versions of Wikisource (phab:T275958)
    • Added a new constraint type to indicate that a certain Property should only be used on Lexemes with a specific language (phab:T200689)
    • Fixed a weird issue with suggesters popping back up when they shouldn't (phab:T284219)
    • Invalid data will not be handled better in RDF outputs (phab:T285131)
    • Working on lowering the rate limit at which a misbehaving bot can waste new Item IDs to further reduce the percentage of skipped Item IDs (phab:T284538)
    • Working on not suggesting real Item IDs in the API sandbox to avoid accidental edits by people who think it is not making real edits (phab:T219215)
    • Working on reducing the time it takes between entering a value in a new statement and being able to save the statement (phab:T281669)
    • Improved documentation of the usage tracking aspects in API help pages. Usage tracking is an internal mechanism to track which article on Wikipedia etc uses which data from an Item on Wikidata. (phab:T283040)
    • Language codes for monolingual strings "gsw-fr", "ykg", "wya", "osa-latn" were made available: Alsatian, Tundra Yukaghir, Wendat, Osage (phab:T262922, phab:T252198, phab:T283364, phab:T265297)
    • The English name for language code "crh" and the Swedish name for "fa" were corrected (phab:T240350, phab:T281702)
    • Lexeme language codes ha-arab, sux-latn, sux-xsux, gsg, tlh-piqd, tlh-latn, bfi, pwn, enm were added. That is Hausa in Arabic script, Sumerian in cuneiform and Latin-script, German Sign Language, Klingon in pIqaD and Latin script, British Sign Language, Paiwan and Middle English. (phab:T282512, phab:T279557)
    • It was determined that language codes can be activated for Wikidata while being blocked for use on Incubator (phab:T273705), this to avoid projects such as a "British English Wikipedia"
    • Language code "es-419" for Latin American Spanish has been available for labels and descriptions for quite some time (phab:T230786)
    • A possibly confusing Russian mis-translation of the name of the language code for "multiple languages" (mul) is being reviewed (phab:T245927)
    • "en-simple:" can be used instead of "simple:" to link to Simple Wikipedia. Query Services outputs "en-simple", not "simple" for sitelinks to Simple Wikipedia (phab:T283149).
    • There was some discussion about the creation of a language code "en-in" for monolingual strings, but "en-in" as interface language seems to be preferred (phab:T212313)

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.


检索自“https://zh.wikipedia.org/w/index.php?title=Wikipedia:互助客栈/消息/存档/2021年6月&oldid=66492751”