Jump to content

Talk:Language committee

From Meta, a Wikimedia project coordination wiki
This is an archived version of this page, as edited by Fausta Samaritani (talk | contribs) at 08:45, 19 January 2022 (→‎Approval of Wp/sdc: new section). It may differ significantly from the current version.

Latest comment: 2 years ago by Fausta Samaritani in topic Approval of Wp/sdc

Please add any questions or feedback to the language committee here on this page.

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 3 days and sections whose most recent comment is older than 31 days.

Archives of this page


2007 | 2008 | 2009 | 2010 | 2011 | 2012 | 2013 | 2014
2015 | 2016 | 2017 | 2018 | 2019 | 2020 | 2021 | 2022

See also: Requests for new languages/Archives

Verification of Wikipedia Skolt Sami (Wp/sms)

There was just a proposal appearing on the request of Wikipedia Skolt Sami. Please help check their test wiki and discuss about it. Thank you. iyumu 08:55, 20 December 2021 (UTC)Reply

Approval of Okinawan Wikipedia (wp/ryu)

Hello! The Okinawan wikipedia has been quite active with complete localization, so I think it is time to consider the approval of Okinawan Wikipedia.--John Smith Ri (talk) 07:31, 22 December 2021 (UTC)Reply

It looks good that the most used core messages are translated and the activities of Okinawan Wikipedia on the Incubator show that the test project has been active for 5 months (with 3~5 active editors each month). iyumu 01:58, 27 December 2021 (UTC)Reply
This project, like the other projects shown above, has fake users active. Again, this is clearly not the fault of this project, just some users interfering with the work of langcom. Check the block status of their accounts. Excluding them, this project does not meet the general activity criteria. --Sotiale (talk) 12:17, 27 December 2021 (UTC)Reply
FWIW, I think the main problem is Bosco1122, the potential master of sock accounts on incubator, and their chronic wrong behaviors. I propose to request permanently blocking that user on the second project, so that at least one criteria of community-request global ban may meet. Liuxinyu970226 (talk) 04:02, 28 December 2021 (UTC)Reply
But even excluding those that are sockpuppets of Bosco1122, the last month data did also meet at least 3 (TINKO, Uchinahito and Eiennohoshi). --Liuxinyu970226 (talk) 01:37, 5 January 2022 (UTC)Reply
You know, do you remember a project that was recently approved with only one element, with at least 3 editors at one time? Probably not. --Sotiale (talk) 11:00, 5 January 2022 (UTC)Reply

Appeal

A proposal to reset eowikt got speedily rejected some weeks ago:

https://meta.wikimedia.org/w/index.php?title=Proposals_for_closing_projects%2FDeletion_of_Esperanto_wiktionary&type=revision&diff=22391767&oldid=22389850

> This may be appealed to the closing member or to another
> member of LangCom, who may re-open it if that
> member finds the discussion to be of value

I APPEAL AGAINST THE REJECTION and request the proposal to be reopened.

Arguments:

  • There are indeed 5 oppose votes. However, 4 of them come from accounts from Russia, potentially controlled by less than 4 persons, and in any case obviously collected/invited by a single user "Vami". One oppose is from China.
  • Below in the section "Long comments" there are 2 "hidden support votes":

https://meta.wikimedia.org/w/index.php?title=Proposals_for_closing_projects%2FDeletion_of_Esperanto_wiktionary&type=revision&diff=22376282&oldid=22373397

and

https://meta.wikimedia.org/w/index.php?title=Proposals_for_closing_projects%2FDeletion_of_Esperanto_wiktionary&type=revision&diff=22370261&oldid=22370236

  • The preferred objective of the proposal was changed from "delete" to "reset". The goal is not to eradicate that wiki, but to eradicate the piracy inside it.
  • One neutral vote:

https://meta.wikimedia.org/w/index.php?title=Proposals_for_closing_projects%2FDeletion_of_Esperanto_wiktionary&type=revision&diff=22389850&oldid=22389283

says

> that copyright infringement needs to get urgently solved or else that's
> going to stir up some serious legal trouble which is something noone
> ever wants to be in

The speedy closure of the proposal brings the message "there are no copyright problems on eowikt", and this is very bad. Without reopening the proposal and giving it some more weeks time for discussion, the copyright infringements on eowikt will never get solved. The underlying problem are copyright infringements in that wiki, and they should not be denied by speedily rejecting the request for reset, particularly in the light of the fact that no other solution is in sight. Finally, this rejected request still causes permanent trolling. Please re-open it. Taylor 49 (talk) 02:51, 1 January 2022 (UTC)Reply

Why not file a new one instead? Also, this wiki doesn't seem to have any matters that can result closure. Liuxinyu970226 (talk) 13:35, 1 January 2022 (UTC)Reply
Please do not make such proposals. Creating a new request would not help the user at all, as I am sure you are fully aware. --MF-W 04:17, 2 January 2022 (UTC)Reply
I stand by my previous decision. The creation of the closing proposal was forum-shopping. The message of speedily closing it is not "there are no copyright problems" or whatever, but: The problem needs to be solved in some proper manner, e.g. via the still open RFC, not by opening yet another place of discussion. --MF-W 04:17, 2 January 2022 (UTC)Reply
No, it was NOT "forum-shopping". The second RFC Requests for comment/Resolve massive copyright infringement on Wiktionary in Esperanto in the matter has been out for 7 months with no result. Some other member of the LC please look at this. Taylor 49 (talk) 00:09, 3 January 2022 (UTC)Reply
Taylor, you have used multiple RfCs, SRCU requests, SRM requests, user and project talk pages, and LangCom to seek action on eowikt. I understand that this is very important to you, but aggressively seeking action through nearly a dozen channels isn't going to result in a positive outcome here. Vermont (talk) 01:51, 5 January 2022 (UTC)Reply
This would be difficult to produce anything other than moving the discussion from the RFC to the space on langcom. If it won't yield any groundbreaking results, it's more helpful for you to address issues that are still unresolved in the RFC. --Sotiale (talk) 11:06, 5 January 2022 (UTC)Reply

wiki/Wy/hbs

Hi! I am contacting you based on previous communication...

Would it be possible to incubate a test wiki with content in macrolanguage - polycentric language like ISO 639-3:hbs?
Hopefully with contributors from SH, HR, BS, SR and Montenegrin language.
All of this time there is no established Wy in any of them. Serbian did not advance much in 8 years. Bosnian experiment (with single page) just got deleted...--Zblace (talk) 05:08, 7 January 2022 (UTC) ...UPDATED--Zblace (talk) 19:30, 7 January 2022 (UTC)Reply
@Zblace Serbian Wikivoyage is testing afaik. Liuxinyu970226 (talk) 09:32, 7 January 2022 (UTC)Reply
Good point. I stay corrected and have updated the statement.
I can imagine preference for Serbian would be ekavica and not ijekavica (which is dominant among all others). --Zblace (talk) 09:40, 7 January 2022 (UTC)Reply
I just realized that Wy/SR is incubating since 2013...that is not a good sign. Maybe better to try taking part in joint effort. --Zblace (talk) 12:09, 7 January 2022 (UTC)Reply
Well, due to difficult-to-judge culture relations of former Yugoslavia, I doubt if creating new sh.* or hbs.* projects would have any benefits on Wikimedia Movements. There's also a bad signal that Wy/sr is inactive for at least 5 years. Liuxinyu970226 (talk) 00:21, 9 January 2022 (UTC)Reply
There is nothing to risk as far as I can judge, so why not experiment? --Zblace (talk) 14:24, 9 January 2022 (UTC)Reply
Have you read [1]? Liuxinyu970226 (talk) 06:22, 11 January 2022 (UTC)Reply
User:Zblace: I think you can go ahead and create Requests for new languages/Wikivoyage Serbo-Croatian (or similar), and also an incubator:Wy/hbs, if you wish. The discussion can be more focussed there. --MF-W 13:25, 11 January 2022 (UTC)Reply
I would however say that there are really risks if we allow incubator:Wy/sh or incubator:Wy/hbs to be created, since therefore there will have many more illogical campaigns to say "hey we should merge bswiki, hrwiki, srwiki and cnr testwiki to shwiki" which may result conflicts of interests between administrators of em. Liuxinyu970226 (talk) 05:45, 14 January 2022 (UTC)Reply
What? --MF-W 11:13, 14 January 2022 (UTC)Reply
I'm not sure what means by your "What?", for example, both Bosnia and Herzegovina and Serbia aren't NATO members, while Croatia and Montenegro are NATO members, plus, serbia is still nationally hating NATO so there are in fact conflicts of interests between srwiki and hrwiki adminships. Liuxinyu970226 (talk) 04:02, 15 January 2022 (UTC)Reply
@Verdy p: I thought that this is what you should explain, as you said elsewhere that "sh", a deprecated ISO 639-1 code, is not actually abandoned and still should use in Wikimedia sites? Liuxinyu970226 (talk) 10:24, 10 January 2022 (UTC)Reply

Approval of Angika Wikipedia (Wp/anp)

Angika Wikipedia has been active for a long time. I think it's time to approve and make wikipedia more reachable to Angika speakers. Thanks everyone.—The preceding unsigned comment was added by Propriyam! (talk)

Wp/anp had no active editors throughout 2021. For your project to gain approval, you need active editors. --Sotiale (talk) 08:26, 8 January 2022 (UTC)Reply

Approval of Wp/sdc

Ladies / Gentlemen, I am one of the users who have been trying a number of months to make the Wikipedia in the Sassaresu language (Wp/sdc/ [2] - a variant of the old and respectable Sardinian language) come out of the Incubator. And right, now where we have reached and surpassed the 1,000 pages (1,172 - see: [3] ) and are ready to claim an honorable place for Sassarese, among the regional Wikipedias of Europe. Due to recent editing, Wikipedia in linga sassaresa is now well developed. I thus propose for the Committee to approve its coming out of the Incubator. Please review the project for final approval. Thank. Sincerely yours,--Sirmio Cabinigre 08:45, 19 January 2022 (UTC)Reply