User talk:Omotecho/Archive 2

Read-only on Japanese Wikipedia

(Also pinging Marine-Blue.)

Hey, just to make sure it doesn't go under the radar: I put w:ja:Wikipedia:お知らせ#Read-only for a few minutes at 05:00 UTC 14 July, about a brief read-only period on Japanese Wikipedia, but wanted to ping someone here, too, to make sure there aren't other places I should have put it in, especially the piece about the local banner if you want one. /Johan (WMF) (talk) 13:30, 13 July 2020 (UTC)

Announced on jawiki. Thanks for your notice. --Marine-Blue^{talk✿contribs} 17:13, 13 July 2020 (UTC)

Editing news 2020 #4

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

Reply tool

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.")[1]

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

• 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

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)

15:11, 31 August 2020 (UTC)

Growth team newsletter 14

Welcome to the fourteenth newsletter from the Growth team!

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

Success with guidance

The star on this image is the week we deployed "guidance".

We deployed the "Guidance" feature on June 15.

This feature uses the help panel to explain what to do after selecting a suggested edit. For instance, if a newcomer selects a copyedit task, they are guided on what sorts of errors to look for. They can see examples of how to rewrite the text. You can try this feature on test.wikipedia.org. First enable the homepage and the help panel in your preferences there.

Since we launched "Guidance", the data we collected show good results (see image). Now, we see more users completing suggested edits than before Guidance was deployed.

Structured tasks

Design concept for the "add a link" structured task

Structured tasks is a project that aims to break down editing workflows into a series of steps. We hope newcomers can accomplish these tasks easily.

In the previous newsletter, we asked for feedback from community members on the idea. We had a good discussion in six languages with 35 community members (summary here). We have now posted new design mockups. We hope community members can check the mockups out and react to them (in any language). They are posted along with some of the main questions we are thinking about as we continue to refine our plans.

Other technical updates

Mockup of Variant D of the homepage on desktop.

• We are currently working on Variants C and D (adjacent image) of the homepage. The goal is to increase the number of newcomers who start the newcomer tasks workflow. This is the team's main project at the moment.
• We've made it easier to hide the help panel when not needed. [2]
• The welcome survey has a new question for people who created their account: language skills. The goal is to find out how many newcomers know multiple languages, so that we can learn whether it is a good idea to integrate Content Translation as a newcomer task. To make room for this question, we removed one that is not being used. [3]

Community outreach

• We continue to engage with more communities. We recently deployed the Growth features to Persian, Hebrew, and Russian Wikipedias. Learn more about getting the features.
• If your community is having a remote event, and you are interested in hearing from the Growth team, please contact us! We have already participated to two community events online:
  • The Polish Wikiconference (recording on Google Drive)
  • The Celtic Knot 2020 (video available on Youtube).

Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.

09:33, 7 September 2020 (UTC)

We sent you an e-mail

Hello Omotecho/Archive 2,

Really sorry for the inconvenience. This is a gentle note to request that you check your email. We sent you a message titled "The Community Insights survey is coming!". If you have questions, email surveys@wikimedia.org.

You can see my explanation here.

MediaWiki message delivery (talk) 18:45, 25 September 2020 (UTC)

Wiki of functions and Abstract Wikipedia

Thank you again for your help with translating content related to Abstract Wikipedia/Wiki of functions naming contest over the last few weeks. It is welcome.

For Round #2 (starting tomorrow) we're using a gadget that we've recently added localization features into. If you could possibly help with the short request at MediaWiki talk:Gadget-AbstractWikipediaDraggableVoting#How to translate, that would be appreciated! The gadget will be used again in the future, for at least the logo contest which will occur after we've determined the name, so it should be especially worthwhile. Thanks, Quiddity (WMF) (talk) 02:28, 27 October 2020 (UTC)

Growth team updates #15

Welcome to the fifteenth newsletter from the Growth team!

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

Variants C and D deployed

Variant D in Portuguese Wikipedia

Variants C and D are two new arrangements of the newcomer homepage. We hope they will increase the number of users using suggested edits. They both make suggested edits the clear place where newcomers should get started on the page. They have some differences in their workflows, because we want to test which design is better. We deployed these variants on October 19; half of newcomers get each variant. After about 5 weeks, we will analyze the data from the tests. The goal is to determine which variant is helping more newcomers to make more suggested edits. We will identify the better variant and then use it with all newcomers.

Structured tasks: add a link

Concept A for add a link.

As we discussed in previous newsletters, the team is working on our first "structured task": the "add a link" task. After community discussion on design ideas, we ran user tests on the mobile designs. We decided on the design concept we want to use moving forward: Concept A. We're now engineering the backend for this feature. Next, we will be running user tests for desktop designs.

Learn more about the findings.

Community news

• We recently deployed the Growth features to Polish, Portuguese, Swedish and Turkish Wikipedias. 18 wikis now have Growth features. Learn more about getting the features.
• Have you recently checked if all interface messages are translated for your language?

Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.

10:09, 1 November 2020 (UTC)

Community Wishlist Survey 2021: Invitation

The 2021 Community Wishlist Survey is now open! This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on 30 November, or comment on other proposals to help make them better. The communities will vote on the proposals between 8 December and 21 December.

The Community Tech team is focused on tools for experienced Wikimedia editors. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!

SGrabarczuk (WMF)

18:25, 20 November 2020 (UTC)

Growth team updates #16

Welcome to the sixteenth newsletter from the Growth team!

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

Growth features show impact

Newcomer task experiments results

The team recently published our analysis of the impact of newcomer tasks. We are happy to announce that we found that the Growth features, and particularly newcomer tasks, lead to increased editing from newcomers.

In November 2019, the Growth team added the "newcomer tasks" feature to the newcomer homepage. After six months, we collected data from Arabic, Vietnamese, Czech, and Korean Wikipedias. We analyzed the overall impact of the Growth features, including newcomer tasks.

This analysis finds that the Growth features lead to increases in:

• the probability that newcomers make their first article edit (+11.6%)
• the probability that they are retained as editors
• the number of edits they make during their first couple of weeks on the wiki (+22%)

We also find that the quality of their edits, as measured by revert rate, is comparable to that of a control group.

• 
  The number of suggested edits completed by each wiki each week, going from December 2019 to November 2020, with a line for the total.
• 
  The number of distinct users completing suggested edits by each wiki each week, going from December 2019 to November 2020.

Because of these results, we think all Wikipedias should consider implementing these features. Learn more about how to get them.

You can find more details about this experiment on the report page. Please post any feedback or questions on the talk page

General metrics

As of November 2020, across all wikis where the features have been deployed:

• more than 5,000 newcomers have made more than 40,000 edits using Newcomer tasks.
• more than 14,000 questions have been sent to volunteer mentors by more than 11,000 users.
• more than 2,000 questions have been asked on help desks by more than 1,500 users.

Learn more about Growth results here, and please post any feedback or questions on the talk page.

Variants C and D

Variants C and D are two new arrangements of the newcomer homepage. We deployed them in October. After six weeks of these variants being deployed, we can see that they have led to increased interactions with newcomer tasks. Next, we will determine which variant is best and use that for all newcomers.

News for mentors

Mentors are volunteers ready to help newcomers in their first steps. Newcomers can contact them using the mentorship module on their homepage.

A separate list for workshops hosts

During workshops organized by education programs through the communities, workshops hosts like to mentor people they train on wiki. Several wikis requested to have a way to claim their mentees without having other newcomers being randomly being assigned to them. To address this need, a separate list can be created on wiki, for mentors that wish to claim mentees, but prefer not to have random mentees being assigned to them. Learn more about this feature.

Claiming multiple mentees at once

Mentors can use Special:ClaimMentee to claim a newcomer as their mentee. The feature now allows mentors to claim multiple newcomers at once.

Community news

The help panel allows people to post a message to the local help desk while editing. Previously, the tool always posted messages to the bottom of help desks. Wikis are now able to configure it to display new messages at the top of the help desk page. T261714

Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.

14:22, 7 December 2020 (UTC)

Community Wishlist Survey 2021

We invite all registered users to vote on the 2021 Community Wishlist Survey. You can vote from now until 21 December for as many different wishes as you want.

In the Survey, wishes for new and improved tools for experienced editors are collected. After the voting, we will do our best to grant your wishes. We will start with the most popular ones.

We, the Community Tech, are one of the Wikimedia Foundation teams. We create and improve editing and wiki moderation tools. What we work on is decided based on results of the Community Wishlist Survey. Once a year, you can submit wishes. After two weeks, you can vote on the ones that you're most interested in. Next, we choose wishes from the survey to work on. Some of the wishes may be granted by volunteer developers or other teams.

We are waiting for your votes. Thank you!

SGrabarczuk (WMF)

16:09, 11 December 2020 (UTC)

Wiki of Functions followup

Hi there, I'm a researcher for the Wikilambda project. Last month we held a naming contest and I'm following up with those who voted to see if you might be willing to provide some feedback to help guide the project.

This would be a 45 minute conversation about your past experience with other Wikimedia projects and thoughts about the future of this new initiative. I'm hoping to gather a wide range of perspectives so I'd be interested in your opinion regardless of whether you plan to have further involvement.

As a way of saying thanks, the research team is offering a $35 gift card (in your local currency) for participation. We could chat by phone or through a website for audio conferencing.

If you're interested just pick a time slot from this calendar link:
https://wikilambda-voter.youcanbook.me

Hope to hear from you soon!

// jeff (design researcher) (talk) 00:57, 13 January 2021 (UTC)

Editing news 2021 #1

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

Reply tool

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 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.
• We have 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 they start writing than those who use full-page wikitext editing.[4]
• 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.[5] Some of the remaining changes are automatic corrections for Special:LintErrors.
• A large A/B test will start soon.[6] This is part of the process to offer the Reply tool to everyone. During this test, half of all editors at 24 Wikipedias will have the Reply tool automatically enabled, and half will not. You can still turn it on or off for your own account in Special:Preferences.

New discussion tool

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.[7] You can leave feedback in this thread or on the talk page.

Next: Notifications

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 notifications-talk.

–Whatamidoing (WMF) (talk)

18:38, 21 January 2021 (UTC)

Growth team newsletter #17

Welcome to the seventeenth newsletter from the Growth team!

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

Structured tasks

Add a link: the team is continuing to engineer on our first "structured task", which will break down the workflow of adding wikilinks to articles, and assist newcomers with an algorithm to identify words and phrases that could be made into links.

Add an image: even as we build our first structured task, we have been thinking about the next one. "Add an image" is a structured task in which newcomers would be recommended images from Wikimedia Commons to add to unillustrated articles. This is an ambitious idea with many details to consider. We have already learned a lot from community members, and we encourage everyone to look at the project page and join the discussion.

Moving forward: more wikis to get the features

Last November, our team published the analysis of the impact of newcomer tasks. We announced that we found that the Growth features, and particularly newcomer tasks, lead to increased editing from newcomers. Because of these results, we believe all Wikipedias should implement these features.

We have started to contact more wikis to deploy the features, including Wikipedias of all sizes. Bengali Wikipedia recently began using Growth features, and Danish, Thai, Indonesian, and Romanian Wikipedias will be coming soon. Please contact us if you have questions regarding deployment.

We are looking for translators who can help by translating the interface. Translating is done on Translatewiki.net (it requires a different account that your Wikimedia one). Communities that already have the Growth features being deployed are invited to check on the translations. Access translations here.

Variant testing

As mentioned in our previous newsletter, we ran a test of two variants of the newcomer homepage, meant to find a version that increases users completing suggested edits. We have completed the experiment, and learned that one of the variants leads to more edits on desktop while the other leads to more edits on mobile. Therefore, we will deploy the strongest variants for each platform to all newcomers.

News for mentors

Mentor dashboard: we have interviewed mentors from several communities as we plan a mentor dashboard feature, which would help mentors track the progress of their mentees. We encourage all mentors to share their thoughts on tools that would help them.

Magic word for mentors: it is now possible to use a magic word, {{#mentor}}, to display the name of a given newcomer's mentor. This can be used on welcome messages, userboxes, etc.

Help panel questions going to mentors: in most wikis, newcomers using the help panel ask questions to the help desk. On Czech Wikipedia, we have experimented with sending these questions to mentors instead. This simplifies the newcomer experience, and only led to a increase in mentorship questions of about 30%. We tried this in Arabic, Bengali, French and Vietnamese Wikipedias, and we are making it the default experience.

Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.

16:02, 3 March 2021 (UTC)

Thank you, and request

Thank you for your over 63,000 contributions to Meta (wow!), and especially for your ongoing effort assisting with Japanese language translation (cool glossary =) including this announcement I'm signing.

As you know, I'm trying to provide a platform for many communities to discuss the next stage of this project. I wondered if you might be able to help, or refer me to someone who may be available to translate: Universal Code of Conduct/2021 consultations/Discussion into Japanese.

I am also looking for someone who is willing to summarize the input from the community, if you know anyone who is available for this. I noticed the Japanese community had input into the first phase of the Universal Code of Conduct and want to continue this effort. Xeno (WMF) (talk) 01:32, 5 April 2021 (UTC)

I appreciate what the Movement sets its goal for inclusiveness and fair/friendly place we share. If I may point out, Jawiki community seems to have chosen (or its only option has been) to distance from global community; partly the old school has consumed their passion (smaller group and de-functioning votes against them.) Would you mind me to talk about this subject in private message, or I can’t hide feeling it’s like pushing people into a pond without safety measure, crossing my fingers they are good swimmers. That taking me back to the motive we need editors comprehend why UCoC is good for the community. There are many people understated, who had ventured to speak up during Phase 1, but busy taking care of gender gap issues or even aspects involving legal specialty day to day, and those issues are what UCoC covers against bullying and agressive reactions. Egg or hen.

• The good part is that understaffed projects including Wikisource showed interest in UCoC Phase 1, by answering to those questionnaire distributed among ja editors. Phase 1 indicates people are listening, and it reminds me how ja culture in general has long lost “speakers’ corner” settings/mentality, esp in mandatory school system up to college level, even though democracy was introduced in 1868 or enforced in late 1940s.
• Not necessarily a particular language community has gone through I suppose, but ja community underdeveloped its skills to wade through unfriendly conversation/reactions (I admit not fitting 100% but still need training).
• Future: I dream we might gain if a dashboard for initiating ourselves (ja or non-ja) how to technically deal with harsh comments, immunize against unfriendly reactions. In my understanding, bullied people have learnt andccopied terminology and context to keep people away from themselves, and from outside they behave very close to a bully.

My wish is that we will reach friendly space accepting discussions and offering hands, hopefully before 2030 (; . Cheers, -- Omotecho (talk) 03:05, 5 April 2021 (UTC)

Thank you for participation in Ukraine's Cultural Diplomacy Month!

Hi, Omotecho!

Thank you very much for participating in Ukraine's Cultural Diplomacy Month! My apologies for not sending this message sooner – but be assured, your contributions are very valuable!
The organisers welcome you participation. We hope you had fun! Some users faced the notability issues of the suggested articles; we recognise that the list of suggested articles wasn't flawless.
The project is not ended until all worthy participants receive their souvenirs! There will be another message from the organising team soon about this.
Stay safe, we appreciate you being a Wikipedian that you are -- ViraMotorko (WMUA) ^(talk) 09:37, 5 April 2021 (UTC)

Invitation to participate in Universal Code of Conduct survey - WikiWomen's User Group

(You are receiving this message as you signed your interest to participate as part of the WikiWomen's User Group)

Hello, my name is Mervat Salman, a UCoC Facilitator, Trust and Safety team.

As you know, the WMF Board of Trustees ratified the Universal Code of Conduct early in February. That's the beginning; the policy itself cannot be used if the enforcement pathways are not defined. The implementation and enforcement of the UCoC requires the continuous cooperation to define clear definitions of enforcement pathways and processes. This needs to be done in a way that does not contradict with the internal bylaws and codes of conduct currently in place, but rather to support them and complement their deficiencies, if any.

In this phase of the process, we would like to invite you to share your ideas, thoughts and concerns about the UCoC implementation, reporting and enforcement pathways using this survey:

• English
• French
• German

Notice: This survey will be conducted via a third-party service, which may subject it to additional terms. For more information on privacy and data-handling, see the survey privacy statement <https://foundation.wikimedia.org/wiki/UCoC_Affiliates_Survey_Privacy_Statement>.

Should you have any questions or concerns, please do not hesitate to contact msalman-ctr@wikimedia.org.

Best regards,

Mervat (WMF) 17:01, 9 April 2021 (UTC)

Help with tranlstaion

Hello Omotecho,

I hope you are keeping safe amidst the ongoing COVID-19 pandemic that has affected many activities globally. The planning for the Wikipedia Pages Wanting Photos 2021 has begun and we need your help with translating the invitation letter to Japanese. See the English language version. Your help with this translation would be appreciate and as always, thanks for your help and support. T Cells^Talk 22:24, 22 April 2021 (UTC)

Thank you

		WPWP Campaign Barnstar of Diligence
		Thank you so much for the translation support for the Wikipedia Pages Wanting Photos. This is greatly appreciated. T CellsTalk 09:50, 23 April 2021 (UTC)

Category:Wikipedia Pages Wanting Photos

@T Cells:, my humble gratitude for your caring heart and follow-up. Pardon me to add ":" inside category tl, so that bots won’t pick me up on category pages. Please enjoy your fav music, your work is beyond my imagination how far a translation driver could achieve. Take care, cheers, --Omotecho (talk) 04:00, 26 April 2021 (UTC)

I am glad to know you and proud of your work here. Please stay safe my friend. T Cells^Talk 08:08, 26 April 2021 (UTC)

Growth Newsletter #18

Welcome to the eighteenth newsletter from the Growth team!

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

Structured tasks

A screenshot of "add a link" feature in development in beta.

"Add a link" is now being tested in production and is nearing release on our four pilot wikis (Arabic, Czech, Vietnamese, and Bengali Wikipedias). We'll be doing final tests this week and next week, and then plan to deploy to the four wikis either during May 24 week, or May 31 week. After two weeks, we will analyze the initial data to identify any problems or trends. We expect that this feature will engage new kinds of newcomers in easy and successful edits. If things are going well after four weeks, we'll progressively deploy it to the wikis with Growth features.

News for mentors

Mockup of the Mentor dashboard.

• We are currently working on a Mentor dashboard. This special page aims to help mentors be more proactive and be more successful at their role. The first iteration will include a table that shows an overview of the mentors current mentees, a module with their own settings, and a module that will allow them to store their best replies to their mentees questions.
• We've conducted our quarterly audit on Growth's four pilot wikis to see the activity of mentors. It appears that the vast majority of mentors are active.

Community configuration

Community configuration editing form under development

We are working on project to allow communities to manage the configuration of the Growth features on their own. In the past, communities have needed to work directly with the Growth team to set up and alter the features. We plan to put this capability in the hands of administrators, through an easy-to-use form, so that the features can be easily tailored to fit the needs of each community. While we developed it initially for Growth features, we think this approach could have uses in other features as well. We'll be trying this on our pilot wikis in the coming weeks, and then we'll bring it to all Growth wikis soon after. We hope you check out the project page and add any of your thoughts to the talk page.

Scaling

• Growth features are now available on 35 wikis. Here is the list of the most recent ones: Romanian Wikipedia, Danish Wikipedia, Thai Wikipedia, Indonesian Wikipedia, Croatian Wikipedia, Albanian Wikipedia, Esperanto Wikipedia, Hindi Wikipedia, Norwegian Bokmål Wikipedia, Japanese Wikipedia, Telugu Wikipedia, Spanish Wikipedia, Simple English Wikipedia, Malay Wikipedia, Tamil Wikipedia, Greek Wikipedia, Catalan Wikipedia.
• A new group of Wikipedias has been defined for the deployment of Growth features. Please contact us if you have questions about the deployment process, or if your community likes to get the features in advance.
• After discussion with the English Wikipedia community, the Growth features will be tested on a small percentage of new accounts. At the moment, registered users can test the features by turning them on in their preferences.

Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.

15:23, 17 May 2021 (UTC)

翻訳関係

お疲れ様です。Marine-Blueです。

技術ニュースの翻訳を見ていて思いましたが、添えられたリンク先や関連するウェブサイトなどは確認を行っておられますでしょうか。例えばこの差分|ですが、[2]に提示されたウェブサイトを見れば（わかりにくければ機械翻訳にでも突っ込めば）、「今後殆どサポートを行わない」「新機能の追加はない」という事情は概ね読み取れるかと思います。敏捷自体が難解で誤るのは仕方がないことですが、もう少し丁寧に確認を行えば誤訳は減らせるかと思います。よろしくおねがいします。--Marine-Blue^{talk✿contribs} 15:41, 7 June 2021 (UTC)

お疲れさまです。いつも査読をしてくださり感謝しています。さて訳文をどこまで否定形にするかのご指摘としてお返事します。ご指摘のリンク先原文はサービス主催者もレビューサイトでもサポート打ち切りである点は明示されています。ですが、週報の発信者はウィキメディアです。英語で緊急性が高い場合の表現でしょうか。原稿の歯切れの悪さが気になります。バグ報告と処理の場所は不可欠のはずなのに、この程度の表現では楽観的な発信だと誤読していますか？　赤信号であるなら書くべき、「すぐに撤収の手順に入るべし」と示しているでしょうか。リンク先と英文原稿の表現の温度差を感じた内容は3点です。

（1）週報原稿にはウィキメディア技術部門で結論が出ていない、すなわち現在、議論しているが詳細は明かせない部分は書けない。そこでトーンを落として現状を伝えた。 （2）無駄なストレスを現場ボランティアに与えない配慮をした文章である。 （3）続報があると期待。

ただ、これらは執筆者にも確かめるか、せめて編集要約欄に疑問点として示すべきで、私の不名を認めます。自身でPhabricator への報告をしたことはあるものの、この更新終了が開発コミュニティ全体にどれほど深刻か想像が足りませんでした。ボランティアが支える存在としてウィキメディアムーブメントにどれほど深刻な事態であるのか。週報原稿の続報が気になります。果たして傘下に置くなど重い判断が議論されているかどうかは分かりませんが、6月初めにどこまで悲観的情報として発信するのか。執筆者は答えられないとしても、Marine-Blueさんに相談すべきでした。ご指摘の手間をかけてくださったことをきちんと受け止め、今後ともより良い訳に努めたいです。耳の痛いことも拝聴させてください。 Omotecho (talk) 16:48, 7 June 2021 (UTC)

どんな内容にせよ、原文が何を伝えたいのかを読み取って伝えれば良いだけです。（言語の違いから来る細かいニュアンスの違いで意味が多少変わるのは仕方ないとしても）この話は伝えてはならないと翻訳者が勝手に判断してはいけません。そもそも開発チームが可能な限りウィキの利用者に不自由を与えないように対応している（手間取っているケースはありますが）ことは、今まで技術ニュースに触れていれば分かるはずです。大事なのは「原文と同じことを伝えるように務める」それだけです。

ここからは個別ケースの解説となりますが、Phabricatorの一件であれば「Phabricatorの開発が終了したので、今後の対応を考えている」というだけであるはずです。(1)(2)(3)の解釈はいずれも深読みしすぎだと思います。悲観するようなことを書いていて、それをオブラートに包んでいるわけではありません。別にバグ報告の場を無くすわけでもないです。何事もそうですが、開発終了で直ちに不自由を生じるケースというものはほぼありません。一般的に新しい環境へ移行するための十分な時間は与えられます。予告なしに不意打ちで「明日から使えない」と言い出すことはありません。

今回のケースでは、データのエクスポートには対応するとPhabricatorの開発元も正式にアナウンスしていますので、移行が行われるとすれば、おそらく新しいバグ報告のプラットフォームを用意して、Phabricatorの全てのログが引っ越しになるだろうと思います。バグ報告がリンク切れになったり、どこへ行ったか分からなくなる心配もないと思います。

これはご存知でないかもしれませんが、バグ報告のプラットフォーム自体、2014年にBugzillaからPhabricatorに移行した経緯があり、ログも全て移行されました。Bugzillaのバグ報告へのリンクはPhabricatorへのリンクへとリダイレクトされており、Bugzilla時代のバグ報告は全て同じ番号を使ってPhabricatorで参照できるようになっています。--Marine-Blue^{talk✿contribs} 17:25, 8 June 2021 (UTC)

お返事感謝します。丁寧に解説いただいて、原文を読み違えたと反省します。おっしゃるとおりバグジラから移動した前例は知りません。まったくいただけない深読みで、査読で防いでいただき感謝しかありません。危ないところでした、慢心を戒めます。重大な事態ではあるけれど展開も対応も掌握されているのですね。おかげさまで、よくわかりました。--Omotecho (talk) 17:52, 8 June 2021 (UTC)

Help with translation

Hello Omotecho, I am User:T Cells from the Wikipedia Pages Wanting Photos campaign. I'd like to thank you for your translation support in the 2020 edition. The campaign was a huge success and that would not have been possible without your support. The Wikipedia Pages Wanting Photos 2021 starts on the 1st of July and we need your help with the translation of the campaign page and the central banner text.

Direct translation link of CentralNotice banner:

https://meta.wikimedia.org/w/index.php?title=Special:Translate&group=Centralnotice-tgroup-WPWP2021&language=en&action=page&filter=

Direct translation link of WPWP main page

https://meta.wikimedia.org/w/index.php?title=Special:Translate&group=page-Wikipedia+Pages+Wanting+Photos+2021&language=en&action=page&filter=

As always, thanks for your help. T Cells^Talk 12:09, 11 June 2021 (UTC)

Hello, T Cell,

What a wonderful news that the WPWP campaign is just around the corner! I’d jump on the wagon to translate. Happy adding pictures (^0-)—☆. Cheers, Omotecho (talk) 14:58, 11 June 2021 (UTC)

Editing news 2021 #2

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

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)

14:12, 24 June 2021 (UTC)

Thank you for your translation support

Dear Omotecho,

I am User:Ptinphusmia from the Wikipedia Pages Wanting Photos International Team. I want to thank you for your translation support and we are happy to inform you that this year, the campaign will be organized locally by at least 45 Wikimedia affiliates in 40 countries. We have a few days to the start of the campaign (1st of July 2021) and we need your help and support to complete the campaign page. As always, thanks for your help and support. Ptinphusmia (talk) 01:24, 26 June 2021 (UTC)

Hello, Ptinphusmia, congratulations for your hard work to realize the annual event, and my pleasure to assist in translation.

By the way, could you please consider making links as $somesome, a small magic very versatile for organizers/readers as well as translators? IMHO, by doing so you lead your readers to appropriate local language page, if any exists by chance.

I owe you a confession behind this request: without that magic, I feel obliged to open the link and check if /ja page is finished, and, ahem, tendencies are that I end up fixing that page but forget to finish your request (mmm, what a shameful short memory span of mine /:).

Anyway, photo campaigns are my fav, and so thankful your team runs this year which we could add light with photos of places we dream to visit sooner. Please stay safe, and happy weekend to you. Cheers, --Omotecho (talk) 04:31, 26 June 2021 (UTC)

Hello Omotecho, please would you be kind enough to add the link? I do not have enough technical knowledge about translation module Ptinphusmia (talk) 21:23, 28 June 2021 (UTC)

A Diff that shows you two cases I added the prefix to make a link to local language, or here to /ja page.

• The first one added to "List of Wikipedias"; bot has fixed the link into <nowiki>$1</nowiki>, which is appreciated;
• The second one added to "Wikipedia Pages Wanting Photos/Resources". Here I reverted the addition and deleted the prefix later, since the translation target, or "…/Resources" page is not yet pushed for translation thus causing red link.
• You might also notice another case in that Diff, which could apply <nowiki>$somesome</nowiki> trick, or please find the part with interwiki prefix ''<nowiki>:w:ja </nowiki>'' plus local page name as: <nowiki>[[</nowiki>:w:ja:%E7%89%B9%E5%88%A5:%E3%83%AD%E3%82%B0%E3%82%A4%E3%83%B3&returnto=%E3%83%A1%E3%82%A4%E3%83%B3%E3%83%9A%E3%83%BC%E3%82%B8|{{lang-ja|ログイン}}<nowiki>]]</nowiki>. It is to link to a localized page "Special:Log-in/ja''on Jawp, or as visualised on screen as below. (1) If there is no interwiki prefix added, a reader pushes the link in green, redirected to "How to log-in" page on English Wikipedia; (2) then, a new-to-commons-Wikipedia user gives up to continue as we have not shown them the basics of Wikimedia wikis, or they won’t find how to switch to the localized/local language pages to log-in/create account.

# ウィキペディアにログイン

I wish the above samples are good enough to tell you my wishes. Please indicate any part you find unclear, and I am happy explaining. Cheers, Omotecho (talk) 01:12, 29 June 2021 (UTC)

A Community Wishlist Survey update waiting for translation

Hello! Would you be able to translate the newest update about the Community Wishlist Survey 2022? In short: instead of November 2021, the CWS will happen in January 2022. We would also like to make other improvements. We can't do that without having the volunteers' opinions. This is what we ask for in the message.

After the weekend, I'll send this to all Village Pumps, Cafes, Forums, etc. Our team would like as many people as possible not to ignore this message. Let's remove the language barrier.

Thank you! SGrabarczuk (WMF) 01:29, 4 September 2021 (UTC)

#WPWPCampaign2021: Learning and evaluation

Hello Omotecho,

Many thanks for participating in the WPWP campaign.

We are glad about the level of participation, this year and we are excited to inform you that over 900 volunteers around the world added photos to more than 250,000 articles in 298 languages Wikipedia. This year, we surpassed the 2020 edition's milestone by over 170%.

We are in the process of evaluating the WPWP campaign this year and we need your help. We'd love to get your feedback. Your feedback will allow us to better meet your expectations for the campaign in the next editions.

Please complete a brief survey so that we may learn about your participation in the campaign, strengths, challenges and your expectations. This information will enable us to improve the next editions of the Campaign.

Follow this link to the Survey:
https://docs.google.com/forms/d/e/1FAIpQLSeL9BORQ94GtN6mjS4-U77N7-BIuxDGl1cmhwKzKSijc9lrcA/viewform

Or copy and paste the URL below into your internet browser:
https://docs.google.com/forms/d/e/1FAIpQLSeL9BORQ94GtN6mjS4-U77N7-BIuxDGl1cmhwKzKSijc9lrcA/viewform

Thank you in advance for taking this survey.

Kind regards,
Tulsi Bhagat ^{[ contribs | talk ]}
Communication Manager, WPWP Campaign
-- Message sent using MediaWiki message delivery (talk) 12:05, 18 September 2021 (UTC)

Simple Talk

I like your page. 🌸 Sakura emad 💖 (talk) 22:41, 18 September 2021 (UTC)

Invitation to participate in the #SheSaid Campaign 2021

Dear Omotecho,

We are delighted to share with you that the #SheSaid Campaign will be running again this year and you are invited to participate in Oct/Nov 2021.The goal is to celebrate notable women and add more entries on Wikiquote. Please have a look at some of the cool bookmarks we have completed and ready for you to print if you wish to do so. If you would like to have the editable version of the bookmark please contact me at Shoodho , visit some sample of bookmarks here:Bookmarks.For more information, please visit the campaign page here:SheSaid page If you have any questions or query please feel free to contact Islahaddow, Anthere or Shoodho

Kind regards, Shoodho Shoodho (talk) 07:07, 29 September 2021 (UTC)

Nice to meet you

Done-- Nice to meet you, my name is Kanninbukuro. Please forgive me for the rudeness that suddenly hits the conversation page. In addition, I am using Google Translate because I can not speak English as a compliment. Therefore, please understand that it may be difficult to read. I will post in Japanese if necessary, so if it is too difficult to understand, please write so. The reason why I visited this page this time is that I was not used to "meta" and could not find the well end or usage guide in "Wikipedia Japanese version", so I was worried about where to ask a question. As a result of my worries, I thought that it would be easiest to ask the user who is probably Japanese from the user's name, although I'm sorry, so I came up to ask a question. Now, I would like to ask about three questions this time.

1. What kind of work is mainly done in "meta"?
2. Is there any discussion in Japanese in "meta"? If so, what is the impact of having discussions in Japanese instead of English?
3. Does "meta" have a page that corresponds to the well end and usage guidance in "Wikipedia Japanese version"? If so, please let me know where it is.

I would appreciate it if you could tell me the above three points if possible. Please excuse me.--Kanninbukuro (talk) 13:01, 30 September 2021 (UTC)

Growth Newsletter #19

Welcome to the nineteenth newsletter from the Growth team!

The Growth team's objective is to work on software changes that help retain new contributors in Wikimedia projects.

Structured tasks

"Add an image" prototype, showing suggested image for the article

• "Add a link" is the team's first structured task. It uses machine-learning to suggest wikilinks as easy edits for newcomers. It was deployed in May 2021 on four Wikipedias and then in July on eight more Wikipedias after we evaluated the initial results. So far, we've seen a high level of engagement from newcomers. Communities that have the feature suggested valuable ideas for improvement. We'll work on improvements and then contact more communities to deploy it.
• "Add an image" is the team's second structured task, currently in development. It is an editing task that suggests Commons images for unillustrated Wikipedia articles. We have conducted many community discussions and tests. Then, we've decided to build a first prototype. We'll first deploy it only to our pilot Wikipedias, to learn whether newcomers can be successful with the task. The project page contains links to interactive prototypes. We are very interested to hear your thoughts on this idea as we build and test the early versions. These prototypes have already been tested by newcomers, in English and Spanish.

News for mentors

• The Mentor dashboard is available at our pilot wikis: Arabic, Czech, and Bengali Wikipedias. It will soon be available at a few more volunteering wikis, as a test. [8]
• At wikis where the mentor dashboard is deployed, a new filter is available for mentors. Mentors can monitor their mentees' activity in Watchlist and RecentChanges, so they can help support their mentees' work. For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are not listed as mentors [9]

Community configuration

• Communities now have the ability to configure how Growth features behave on their own wikis. At Special:EditGrowthConfig, community members can add a list of volunteer mentors, alter the templates used for suggested edits, update help links, and more. This special page is editable by administrators and interface admins.

Scaling

• We are proud to announce that all Wikipedias now have the Growth features! Thank you to all the community members who helped the team build the features and bring them to their wikis. The only exception is Chinese Wikipedia (zh), for technical reasons. [10]
• The wikis that have Growth features deployed have been part of A/B testing since deployment, in which some newcomers did not receive the new features. Now, all of the newcomers on 280 of the smallest of those Wikipedias have the features. [11][12]
• A test is undergoing at English Wikipedia: 25% of newcomers receive the Growth features. The results from this test will be part of a discussion of how to proceed on that wiki.
• Now that Growth features are available at Wikipedia, the Growth team considers to extend them to other projects. Some Wikisource users have expressed some interest in getting Growth features. There is currently a discussion about implementing them on Wikisource.

News for communities

• Do you have questions about the Growth features? This translatable FAQ contains answers to the most common questions about the Growth team work.
• The Growth features were recently used in a test amongst Latin American donors to give donors the opportunity to learn to edit. You can see the results here.
• Interface translations are important for newcomers. Please help for your language, by translating or copyediting interface translations for the Growth features.
• Help:GettingStarted was a feature developed in 2013, which directed newcomers to articles that needed editing. We recently removed this feature from all wikis, because it has been replaced by the Growth features.

Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.

18:36, 26 October 2021 (UTC)

Re: UCoC/ja

It seems I cannot edit the page on foundation.wiki, probably the text here on Meta was fixed later, since I uploaded the text that I received through a .doc file. If someone can temporarily unblock the page on foundation.wiki, I can take care of updating the page today. Sannita (WMF) (talk) 12:27, 14 December 2021 (UTC)

@Sannita (WMF) hello. And thank you for crisp reply. Regarding UCoC/ja page on the Foundation wiki: Yes, your suggestion to arrange UCoC page unblock sounds very practical to me. in order to put through my request: Shall we remove non-japanese character/symbol from the page title ? As I am a volunteer, very open to request maybe by pinging @PEarley (WMF):. Sannita, anybody on your mind whom I shall contact?

Here follows my view on this matter. It is a sensitive issue among ja Wikipedians IMAHO, maybe momentarily as a Grants and Governance facilitator is reaching out for two weeks now, trying to enhance trusting communication/discussion between local community and WMF. Because the wrong pagetitle is on Foundation wiki, we risk a message ja language is not treated right since May 2021. I am sorry I did not notice it earlier, and I wish correcting it would support any positive endeavor for win-win Grants - and Movement Strategy Implementation, by righting a small bump. FYI, jawp community indicates our Foundation and jawp could enhance more trust, and as a translator, I take that view to my gutts. Cheers, -- Omotecho (talk) 14:55, 14 December 2021 (UTC)

I asked privately to a user if they can edit the page, and they will in the next minutes. The problem should be solved by today. They also told me that they will migrate those pages to the correct system, so that we won't have any more problems with that. :) Sannita (WMF) (talk) 16:55, 14 December 2021 (UTC)

So appreciating you took extra mile towards the solution. Please allow me to have a few days before coming back to the update. Thank you indeed for your dedicated supervision. Cheers, -- Omotecho (talk) 18:16, 14 December 2021 (UTC)

Note

Hey there. I noticed you didn't sign here. (Also, I don't think I know what Termbase is? And maybe it's not just me). TYVM! ;) --Elitre (WMF) (talk) 12:16, 8 February 2022 (UTC)

@Elitre (WMF), hi, and thanks for the reminder. Termbase is at meta, open now for our input (: TYVM (dōmo arigatō.) -- Omotecho (talk) 16:54, 8 February 2022 (UTC)

Call for translators

Hello! You received this message because last year you were involved in translating the page of Ukraine's Cultural Diplomacy Month in your language. The 2022 edition of the competition is going to start in one week, and I would like to ask whether you are interested in translating our landing page for this years' contest? We highly appreciate your volunteer work in this regard, and it would mean the world to us if you helped us with translation this year. If you have any questions, feel free to reach out to me. Sincerely,--ValentynNefedov (WMUA) (talk) 11:58, 10 February 2022 (UTC)

Ukraine's Cultural Diplomacy Month 2022 invitation

Dear Wikipedian!

You received this message because you participated in Ukraine's Cultural Diplomacy Month 2021. Without your contribution, the challenge would not have been so successful.

This year Wikimedia Ukraine, in cooperation with the Ministry of Foreign Affairs of Ukraine and Ukrainian Institute, has launched the second edition of writing challenge "Ukraine's Cultural Diplomacy Month", which lasts from 17 February to 17 March 2022. The campaign is dedicated to famous Ukrainian artists of cinema, music, literature, architecture, design and cultural phenomena of Ukraine that made a contribution to world culture.

I would like to invite you to participate again in this writing challenge! We have updated the list of suggested articles and announced new prizes for contestants to keep interest in different fields of Ukrainian culture. I hope to hear from you soon!-- ValentynNefedov (WMUA) ^(talk) 08:57, 17 February 2022 (UTC)

@ValentynNefedov (WMUA), hi, thank you inviting us, and wish you a marvelous voyage, again ! -- Omotecho (talk) 11:41, 18 February 2022 (UTC)

ご無沙汰してすみません

@Omotechoさん ご無沙汰して申し訳ありません。 ロシア歴史好きのKizhiyaです。Ucocの投票がはじまる3月7日まで、微力ながら校正、意訳をお手伝いします。現在、ユニバーサルな行動規範UCoC/よくある質問を読んでいます。 どこか優先的にとりかかったほうが良い箇所がありましたら、どうぞご教示ください。Kizhiya (talk) 23:05, 27 February 2022 (UTC)

こんにちは、お忙しいところ駆けつけてくださりありがとうございます。感涙です。スレッドを分けました、悪しからず。--Omotecho (talk) 01:53, 28 February 2022 (UTC)

Universal Code of Conductと施行ガイドライン（翻訳）

（このスレッドは広くは運動戦略の理解のために必要な部分の翻訳を話しています。）

一番、気になるのはこのページを通読して用語の矛盾、言い回しの衝突がないかどうかです。ざっとご一読の上「おや？」と思われた箇所はないでしょうか。推敲してもらえませんか？　

1. 大きな問題の時だけ、そのurl欄をコピペして 専用のスレッドに連絡をください。

• これまでの作業の方法は、キーワード単位で串刺し検索して、複数文書の登場箇所を見つけては訳してあります。井戸端で読み取ったキーワードは「研修」「罰則」≒「処分」≒「措置」。善意の利用者も〈不作為〉をすると実効性のある処分を受けるらしいので拒否したい。井戸端のスレッド提議の前提も、翻訳の遅れに負うところが一部どころか多いので焦りました（拒否するのはディベートに誘い込む常套句ではありますが）。グローバルな発言では過去の時点でのスットンキョーな内容もありまして、訳から手が離せなくなくなる。
  

状況を共有

Universal_Code_of_Conduct/全体日程表（Project）（更新の遅れあり）

総索引（情報ボックス、ホットリンクを回避）。テンプレート名はUniversal Code of Conduct/Navbox/ja

ウィキペディアの井戸端で議論と言いますか、意見集約が進んでいます。ご覧になりましたか？　私の編集履歴（利用者ページをモバイルビューで開くと利用者名の上段に胸像＋ノートの罫線のアイコンあり）をご覧になると、その当該スレッドへのリンクがあります。

その場の要点は@Kizhiyaさんも悩まれたメタの敷居の高そうな感じをぬぐい、この際、ローカルで意見を出し合う場を作り、メタヘ持っていくことです。それとメタの関連ページが母語で読めるかはつながっています。「〇〇と聞いたが」など噂で何か考えては発言に実効性がないですものね。

一方で翻訳はどこに的を絞りましょうか。長くなりますが、投稿を分割すると通読しにくいので、爆進。（心の声＝後でまとめページでも作る予感）

下記で★印をつけた付番aからeが気になります。優先順位はどうしましょうか。

• （A）：0：行動規範（理事会の承認分）は、不急。第2フェーズで変わってないと判断。合計30件超の日本語版がある（＝リンクどこ？）　勧告は日本語版の一覧表あり
  :*（コモンズに保存＝* 1ページ版のまとめ（英語版） ）。
  :*メタに「戦略/ウィキメディア運動/2018/推奨事項」＝「勧告」の書き下し文あり。※＝注書き〈日本語への翻訳は優先課題ではなく翻訳管理者の指定する特定の言語版はフランス、ドイツ、ポルトガル、スペイン、ヒンディー語、中国語、アラブ語。〉
  

Keep 理事会が変更・加筆した箇所および注書きの一覧をご参照。ユニバーサルな行動規範/理事会批准の変更記録。規範の本文は、英文ママにしてあります。

• c：a：施行策は、翻訳が済んだか？ユニバーサル行動規範Universal Code of Conduct(UCoC)/施行ガイドライン
• b：円卓会議は、「2021年聞き取り調査/協議」
• a：c：第2次聞き取り調査のまとめは、英語版があるのか？
  :*英語版ウィキペディアは、2021 consultation。
  :*他の言語版（ウィキデータ経由でご参照）
• d：公開申し入れ状は、どこにあるのか？（リンクどこ？）
• e： Done ガイドラインの批准投票のマニュアルは、一次訳終わり。要査読。ユニバーサル行動規範Universal Code of Conduct(UCoC)/施行ガイドライン/投票者向けの情報

これまでのUCoC進行表。

メタつまりグローバルな利用者としての私たちのために全体がどう動いてきたか。それを見通すと、どこが力点かわかるかしら。ちょっと目が回るほど段階が多いので、取りこぼしそう。長いので時系列で現在に近いとこから遡上します。

1. イマココ February 28, 2022時点（E）★^e批准投票前、3月7日から2週3週で〆切。←

1. （D）「会話の時間」始まる＝財団担当とコミュニティの公開討論が2月に2回あり、3月4日に1回予定。参加条件はアカウントがある人←
2. メタの関連文書の翻訳が加速、日本語版ウィキペディアの井戸端で聞き取り進み、メタヘ持ち帰りと回答の循環←
3. 2022年1月（？）始動、日本語版コミュニティで調整役を囲む聞き取り調査が始まる。場所はウィキペディア、@YShibata (WMF)さんのご登場（YSさん、まだ動かないでくださいね、今はよもやま話と思ってお読みください）←
4. 2021年12月（？）、日本語版で用語集班、動き出す。←
5. グローバルでは、言語版ごとに調整役を囲む聞き取り調査始まる。←
6. （C）「待った」がかかる＝グローバルな裁定委員会Arbcomが財団宛の★^d公開申し入れ状を出した、リンクと内容は未確認←下線部を訂正
7. （B2）★^c施行策を利用者コミュニティと調整開始、批准投票が前提？
   * ★^b2021年円卓会議＝ウィキマニア
   * ★^a第2次言語版ごとの聞き取り調査、課題は施行策（UCoC_Enforcement 日本語版はスルー）
8. 理事会の（A）行動規範の承認、すなわち公式文書となるが★^a推敲をする前提？

その前段（2021年）

以下が2021年に時系列順ですみました。

1. （A）第1フェーズ開始＝グローバルに使う行動規範を皆で認めよう。行動規範（UCoCのたたき台）について2021年聞き取り調査→
2. 行動規範の第1次草稿の委員を募集、草稿作りが始まる→
3. 行動規範集の改稿と並行して、勧告（recommendation）を作り公開→
4. 理事会へ（A）規範集を上申→
5. （B1）第2フェーズ開始＝同施行策。草稿委員会の立ち上げ、草稿の作成開始→前述の2022年の工程へ。

（並行して運動憲章（1枚まとめシート）を話し合い起草委員会の選挙と立ち上げ。これがUCoCほかウィキメディア運動全体の冠になる？）英語版はJune 10, 2021から8版。

さらにその前（2018年-2020年）

• 本文、戦略/ウィキメディア運動/2018-20勧告
• テンプレート:2018-20/勧告の最終文書、1ページまとめ版（日本語）2020年1月20日発表「ウィキメディア戦略勧告案」日本語訳。13件の勧告を網羅し一覧性を持たせた。文中のリンク先に、勧告案の本編がある。

---

ここから反省文です。現在の〈知恵〉が混ざらないように注意して訳しているつもりが、心の中でオタンコナスな発言にツッコミを入れているためか、筆が滑って（私情を盛って）いない自信がありません。また例の用語集と並行して手間を省こうと、本文中に「※」で用語を残しています。まったく売り物にならん下書きの状態なのに、読み手に目を瞑ってもらっています（だって査読待ちなんだもの、勝手にそういう想定しました。）

メタへのリンクが全くなくてすみません。救援隊登場に興奮して、あれこれぶち撒けてしまいました。ここで一旦、頭を冷やしてきます。 Omotecho (talk) 01:30, 28 February 2022 (UTC) ／ --見出しを独立。UCoCよくある質問ページ（FAQ）にリンク。Omotecho (talk) 01:53, 28 February 2022 (UTC)。／ 下線部を訂正。--Omotecho (talk) 02:09, 28 February 2022 (UTC) ／ リンクのない箇所に印--Omotecho (talk) 03:39, 28 February 2022 (UTC) ／ リンク1件追加、理事会が行動規範に加えた変更と加筆の一覧。第1フェーズ批准のため。--Omotecho (talk) 05:09, 28 February 2022 (UTC) ／ リンク追加、投票者向けの情報 --Omotecho (talk) 05:46, 28 February 2022 (UTC) ／ リンクを追加、全体日程表、総索引。--Omotecho (talk) 06:45, 28 February 2022 (UTC) --Omotecho (talk) 02:55, 2 March 2022 (UTC) リンク追加（2021年）、憲章、同委員会。

@Omotechoずっと気になっておりました。ほんとうにお一人でお疲れさまです。

状況を共有

時々覗いて、こっそり記事を直すついでに井戸端やお報せもざっと見てはいましたが、状況は大混乱としかまだわかっておりません。とりあえず頭が動かないので、ご指示のとおりFAQを見てみます。

近況　今月来月あたり限定で、機械翻訳ソフトのdeepLが手元にあります♫ Kizhiya (talk) 02:50, 28 February 2022 (UTC)

いやあ、対面でなら簡単な遣り取りも、仮想空間で同じ〈絵〉が見えているか、手でも探れず。なかなか文通みたいでスリリングです。ぜひそのスリルを「よくある質問」でご堪能ください。なるほどなぁと思ったり、見えてなかった景色が開く質問もたくさんあります。

噂の翻訳機能D！　どんなAIもしくは翻訳辞書を使っているんだろう。MT（機械翻訳）は長年の大好物、あれこれ想像してニヤけています。出力させておいて、〈ダメじゃん間違ってるよ〉と独語しながら直す姿は人様には秘密です。

富士の樹海で悲壮な単独迷子だとメロドラマを気取っていたら、貴方様はじめ、ときどき天使が舞い降りてきます。富士山の八合目（投票〆切）はまだ見えるし、おかげさまで勇気の補給をして弱気なりの道を立て直せそうです。多謝。--Omotecho (talk) 03:39, 28 February 2022 (UTC)

UCoC投票に向けての進捗状況報告

@Omotechoさん、お疲れさまです。「よくある質問」いちおう全部チェックしました。機械翻訳やらかし、妙な翻訳など、ご迷惑をおかけしました。原文が。。。次ですが、とりあえず井戸端の議論を見てみます。--Kizhiya (talk) 15:33, 1 March 2022 (UTC)

早速にありがとうございます、勧告は日本語版の一覧表があるのですが、これで正しいのかどうか。2018年からの運動戦略で出てくるものです。PDFの1枚ものです。取り急ぎまして。

• 
  （コモンズに保存＝* 1ページ版のまとめ -- Omotecho (talk) 16:27, 1 March 2022 (UTC)

@Omotechoさん

勧告（推奨）のPDFをありがとうございます。校正作業はUCoC投票関連の書類で行ったほうが良いですよね？　次はOmotechoさんの履歴を拝見しつつ、円卓会議に行くつもりです。問題があればお教えください。また、進捗報告はsandboxのほうにいたします。

それで、明日にでも一度、井戸端のUCoC のスレッドに手伝い募集の文を書いてみます。来てくださった場合、情報集約はsandboxUser talk:Omotecho/sandbox/UCoC E2022 02ということでいかがでしょうか。今日はこれまでで失礼します。--Kizhiya (talk) 17:09, 1 March 2022 (UTC)

> 井戸端のUCoC のスレッドに手伝い募集の文を書いてみます。

どうかご無理のないように、でも、熱烈期待します。（蝿帳ごしにサバ眺める猫状態）

そうですね、サンドボックスでなんでも忌憚なく話しましょう。このページはまとめ用に、情報をあちこちから拾って置きます。今日は運動「戦略」（用語に抵抗のある人もいる様子）が冠のようにいただくはずの「運動憲章」作りの対話とか、1ページまとめとか発見。これは、全体で何階建てなのだろう？　上（理想）から決めてって、実行手段をきめるんじゃないんですねぇ。実態としてすでに存在しているからか？　多→少の方向で作業すりゃあ、なかなか進まないのも運命でしょうか。

　

このページ、そろそろ小見出しで整理するか、せめて表組みの方が見やすいんだけれども、ベタ打ちで足していきます。 --Omotecho (talk) 01:59, 2 March 2022 (UTC)

┌──────┘

• 至急 投票関連の翻訳の手が足りません。mediawikiのExtension:SecurePoll/ja 投票用のアプリの翻訳、どなたか挙手をお願いします。場所はメディアウィキといい、右上のアイコンが赤いひまわり（？ダリア？）です。--Omotecho (talk) 16:12, 6 March 2022 (UTC)

今後の日程表（2022年−2023年）

March 1, 2022時点の見通し

2022年

• 3月4日にオンラインで対話の会、2400開始。司会は組織統括チーム（法務部配下）、参加者はグローバル利用者と財団職員・ボランティア（起草委員、裁定委員？）
• 3月4日〆切（UTC）、暫定信頼安全評価委員の自薦他薦。18:18, 4 March 2022 (UTC)二次募集に気付き再延期可能か問い合わせ中。、当該ページの英語版の更新を確認。なお活動内容は記録あり

2022年、2023年の日程表（UCoC関連）

UCoC施行策			暫定T&S事案評価委員会
日付	内容	備考	日付	内容	備考
* 3月07日– 3月21日	投票、施行策の批准。	対話の時間などコミュニティとの擦り合わせ中。	–3月7日〆切	暫定T&S事案評価委員会の委員自薦	旧〆切3月4日。活動記録あり。
	* 開票結果	→可決、実施　または 　→否決、？？	___	___	__
2023
注

• 運動憲章の起草
• 施行策の見直し・改訂（実施から1年後とする）
  

--Omotecho (talk) 02:55, 2 March 2022 (UTC)／ 追加、評価委員のニ次募集、ニュースレターのリンク。--Omotecho (talk) 18:18, 4 March 2022 (UTC)

--Omotecho (talk) 12:57, 5 March 2022 (UTC) 暫定委員会と並列で進行表。--Omotecho (talk)refタグ修正。

勧告ってなに？

勧告

1. Increase the Sustainability of Our Movement
2. Improve User Experience|
3. Provide for Safety and Inclusion|
4. Ensure Equity in Decision-making
5. Coordinate Across Stakeholders
6. Invest in Skills and Leadership Development
7. Manage Internal Knowledge
8. Identify Topics for Impact
9. Innovate in Free Knowledge
10. Evaluate, Iterate, and Adapt

勧告の旧版と最終版の間で何が変更されたか?（2020年時点） 変更履歴をご参照ください。（<"Strategy/Wikimedia movement/2018-20/Reports/Finalization Change Log (January - April 2020)">）

--Omotecho (talk) 02:55, 2 March 2022 (UTC)

Stefania Turkewich

Hello Omotecho, When you have time could you take a look at this article: en:Stefania Turkewich? If it interests you, could you give it a start in the Japanese Wikipedia with an opening introductory paragraph for the ウクライナの文化外交月間2022 project? Stefania was the first woman composer of classical music in Ukraine. Nicola Mitchell (talk) 21:31, 3 March 2022 (UTC)

@Nicola Mitchell, hi, of course for WiR causes! I see a campaign as well. Good luck, and do you have any list to post on WikiGap/ja at jawiki maybe for UCDM + women? I will post your message and we can discuss here for details. Cheers, Omotecho (talk) 00:26, 4 March 2022 (UTC)

I have nothing further to post at this time. The start of a Japanese article for Stefania would be great! Thank you. Nicola Mitchell (talk) 10:43, 4 March 2022 (UTC)

@Nicola Mitchell, Thank you for replying. Yes, I see. Then about Stefania Turkewich and mention on essay in written/print form Japanese language. Do you happen to find anything on the web or Ukrainian sources that she had encountered any Japanese person, not necessarily among music circle? Any input be very appreciated. FYI, I have searched any academic work or essay on her on databases, including UCOC, or the Library of Congress database. Unfortunately I haven't hit anything yet written in ja language, which I don't mind as a translator to work on an article.

Also, I am not very familiar how I transcribe Ukrainian person name. Would you kindly consider adding IPA phonetic codes on enwiki w:en:Stefania Turkewich article? IMHO that might be a hint for internationalization / localization among translators.

I remain among them with you who wish to add an article locally on UCDM2022, Cheers, a candle 灯明 with a prayer for peace. --Omotecho (talk) 19:09, 5 March 2022 (UTC)

I am unaware of any encounter with any Japanese person that Stefania had. And as I do not know the Japanese language I am of no help with the transcription of names. If you do go ahead with an article, just do the best you can and once the article is in Wikipedia, editors who are familiar with this aspect, upon seeing the article might be able to contribute. Nicola Mitchell (talk) 19:34, 6 March 2022 (UTC)

Well, I am particular about person name, and let me explain that in jawiki we are advised to give IPA phonetics codes to person names, so in Stefania's article, my humble wish is that Russo-confusion of pronouncing person names be prevented. It is an international system, very versatile wiki-wise.

Do you have any Ukrainian-English dictionary to look up phonetics? I am home bound with COVID-19 warning here, very sorry I can't access références at libraries.

I might tell you a cultural aspect in my query: we sometimes suffer with Chinese-confusion involved with our own names, called in wrong manner. Lerner countries attract more interest on the web, so we can't help, or Google translation gives me Stefania's name in our scribing system, but it sounds very Russo to me and I am lost at it.

Please be assured I support your great contribution to revive the due name and position we owe to Stefania: seeing wikidata moved me over 30-ish wikis writes about this international musicologist/performer. Best, -- Omotecho (talk) 01:20, 7 March 2022 (UTC)

I talked to a Japanese editor and was told: "there were and are no faculty where one can specialize Ukrainian language, unlike Russian or Old Church Slavic, it is more difficult for us to learn Ukrainian, especially its pronunciation and phonetic aspects." I myself too know of no dictionary that can help you with the phonetics. If you wish to go ahead with the resources you have at hand, you can always modify the article later when an opportunity might present itself and you can avail yourself of further resources. Wikipedia is malleable, not written in stone, things can be changed later. Also, Wikipedia is a collaborative enterprise, and if you decide to put the article into it, you might be surprised how other editors will appear to be of help. I'm going into the hospital and will be off Wikipedia for a time. I wish you the best with whatever route you decide to take! Nicola Mitchell (talk) 18:24, 7 March 2022 (UTC)

@Nicola Mitchell, good luck with you, too <3 -- Omotecho (talk) 01:29, 8 March 2022 (UTC)