Incubator:Import requests

From Wikimedia Incubator

Archive Archives


See /Archive

Requests for importing of closed projects belong to the page Incubator:Coordination for importing closed projects‎.

Here you can request importing pages with the full history from another Wikipedia/Wiktionary etc. to translate them into your test language.

Imports from the following wikis can be done by every administrator:

From other wikis only import users can import.

A log of import actions is at Special:Log/import.

Requests here[edit source]

Example: Please import en:Example to Wp/de/Beispiel. ~~~~

Wy/ja[edit source]

Please import Wikitravel data dump. This is the database dump / back up of Wikitravel in all languages, including Japanese. Download here. The file is compressed using 7zip.--Other languages (talk) 09:53, 11 July 2020 (UTC)[reply]

User:Tmv: what do you think of this request? --MF-W {a, b} 12:22, 12 July 2020 (UTC)[reply]
@MF-Warburg: I guess that the problem is that we have no policy on importing. Therefore, we should discuss and create a policy on this subject. We'll keep you updated on the situation. Once the policy is in place, we'll be able to decide what to do.
I will also inform Wikitravel community on the discussion. I have an account there.--Tmv (talk|Contributions) 07:57, 13 July 2020 (UTC)[reply]
Symbol information blue.svg report - Wy/ja/Wikivoyage:ウィキトラベルからのインポート--Tmv 03:17, 28 July 2020 (UTC)[reply]
Hi, I'm the one who created the data dump. If the decision is made to import Wikitravel's content (which I support) I can create an updated version of the backup.
User:Tmv: I read the import policy you wrote and that's not going to work... I can't account for those criteria when importing. My suggestion is to import everything, that's what was done when we imported the other Wikitravel languages. The articles come with the entire history preserved so there won't be any copyright issues. Acer (talk) 00:03, 31 July 2020 (UTC)[reply]
@Acer: Thanks for the comments. Let me ask you a question. I'm in favor of importing all the pages, but what about the articles that already exist in Wikivoyage? I'm not familiar with importing from Wikitravel so I don't know. Could you please enlighten me?--Tmv (talk|Contributions) 23:33, 31 July 2020 (UTC)[reply]
@User:MF-Warburg What's the plan here? Import directly to ja.wikivoyage? Or to the incubator? Is this going to get fast tracked like the original imports?
@User:Tmv Let's see what MF-Warbug says. If we can import directly to ja.wikivoyage then we could just import everything there and after that you can replace Wikitravel pages with the ones here from the Incubator very easily if you want. It's not a problem Acer (talk) 15:31, 1 August 2020 (UTC)[reply]
How many pages would this be? Also, do you really want to import pages from 2016? --MF-W {a, b} 16:50, 1 August 2020 (UTC)[reply]
5810 articles (18272 total pages). And no, not from 2016. Japanese Wikitravel is still active, I can generate a new, up-to-date, datadump. Acer (talk) 19:51, 1 August 2020 (UTC)[reply]
I am active in Wy/ja. If we can get a new data-dump that reflects the pages in the present Wikitravel, we should do that, I think. The data dump in 2016 must have gotten old. --Atmark-chan <T/C> 10:17, 2 August 2020 (UTC)[reply]
It's outdated in the 2016 dump data. If you import that dump data, it's hard to fix it.So I think you should make sure the dump data is up to date.The revision process is easy and you can use your time for other tasks.-- Object*tofu (Benutzer / erzählen) 11:31, 2 August 2020 (UTC)[reply]
Yes, I will create a new updated data dump (August/2020) Acer (talk)

Let me make the following suggestion. We do not fast-track Wikivoyage versions anymore. However, Wy/ja is sufficiently active to be approved. Importing more than 5000 pages into Incubator, only for them to be exported shortly afterwards again, would make no sense. I have now proposed approving Wy/ja in Langcom, and when the wiki exists, you, the community, can import the articles you want, saving the need for adding prefixes etc. --MF-W {a, b} 15:25, 2 August 2020 (UTC)[reply]

Great, thank you. But wouldn't it be better to have the data dump used as the basis for creating the Wiki? It's much easier to add in the Incubator pages afterwards than the other way around, given the size differences. Remember how we did it for Finnish Wikivoyage? (and here) Acer (talk) 16:16, 2 August 2020 (UTC)[reply]
But the community here is working on their own pages. That should be the basis. Wikitravel forking is second. --MF-W {a, b} 20:18, 2 August 2020 (UTC)[reply]
Sorry.I don't know Langcom.What is it?-- Object*tofu (Benutzer / erzählen) 10:56, 3 August 2020 (UTC)[reply]
@Object*tofu see meta:Language committee--Tmv 01:18, 4 August 2020 (UTC)[reply]
Comment Comment The work necessary for Wikivoyage to become independent is not finished. We are not in a position to become independent any time soon. --Tmv 01:26, 4 August 2020 (UTC)[reply]
What does that mean? What are you still planning to do? --MF-W {a, b} 01:42, 4 August 2020 (UTC)[reply]
I will continue to work on it. But it will take some time to prepare the page import. Because the translation is not finished in translatewiki. It's difficult to finish it quickly because of the volume. If you can wait for me, I will finish it, but I still need time. --Tmv 02:06, 4 August 2020 (UTC)[reply]
see [1]--Tmv 02:13, 4 August 2020 (UTC)[reply]
If you first want to completely translate the interface, that's fine of course. But for Langcom, it would be ok to already approve the project as it is. I mean, jawiki or jawiktionary are also functioning without a completely translated interface. --MF-W {a, b} 02:29, 4 August 2020 (UTC)[reply]
Comment Comment Let me ask a question. The contents of the technical messages that should be translated to Japanese are common among the all Japanese language projects? If they are, probably we don't need to translate the all contents because "jawiki or jawiktionary are also functioning without a completely translated interface," like MF-Warburg said. --Atmark-chan <T/C> 10:21, 4 August 2020 (UTC)[reply]
Comment Comment It's true that translation work is not mandatory. I don't know if the message is the same for all sites. But if translation is not mandatory, I am very much in favor of independence. --Tmv (talk|Contributions) 11:06, 4 August 2020 (UTC)[reply]
Symbol support vote.svg Strong Support I want independence from Incubator very much, too, if we can. --Atmark-chan <T/C> 11:41, 4 August 2020 (UTC)[reply]
I'm all for independence, but the site icon is still an old one. --Tmv (talk|Contributions) 07:12, 5 August 2020 (UTC)[reply]
Comment Comment Isn't it OK to use the English logo Wikivoyage-Logo-v3-en.svg instead temporarily? I want to use new Japanese logo if we can, but if we can't, the English logo is better than the old Japanese logo. English logo is also used in RUWY. If we create new Japanese logo after independence, reflection of the new logo may take time and effort, but it's better than we can't independent until creation of the new logo. --Atmark-chan <T/C> 11:07, 5 August 2020 (UTC)[reply]
P.S. P.S. I have tried to create a new Japanese logo, but I don't finish it now. We have discussed about it here. --Atmark-chan <T/C> 11:13, 5 August 2020 (UTC)[reply]
Comment Comment MF-Warburg made a suggestion on approval at Langcom; you have objections to that based on the language proposal policy, please tell us here on this page in the next seven days.

But I think so the policy needs to be adjusted before Independence...-- Object*tofu (Benutzer / erzählen) 11:50, 5 August 2020 (UTC)[reply]

For the record, that is here. But I also read everything here. --MF-W {a, b} 12:34, 5 August 2020 (UTC)[reply]
We've worked hard to create a policy so far. I'm concerned about the lack of content on the page explaining how to edit it, but I think it's okay. I'm all for independence; the meta page was edited by me: meta:Special:Diff/20342060--Tmv (talk|Contributions) 22:05, 5 August 2020 (UTC)[reply]

Question Question I have some question. First, will legal documents, for example, documents about license, in the new wiki be created by the foundation? Second, where can we request alias of the namespaces? --Atmark-chan <T/C> 18:08, 6 August 2020 (UTC)[reply]

No. - At m:Requests_for_new_languages/Wikivoyage_Japanese, currently. --MF-W {a, b} 11:17, 12 August 2020 (UTC)[reply]

As the discussion died down, I will mark this as X mark.svg Not done for now. --MF-W {a, b} 11:49, 28 March 2022 (UTC)[reply]

Wikitravel datadump[edit source]

@User:Tmv @User:Atmark-chan @User:Object*tofu @User:GZWDer

The updated datadump is ready.

@User:MF-Warburg Your plan to let the community import by themselves after Ja/Wy has been created is not going to work. The dump is too big. There are 9814 mainspace articles. Special:Import is limited to batches of 100 pages at most. This needs to be done by someone with shell access using importDump.php. Then there's over 4000 images that need to be uploaded to Commons. This is going to be an involved process. If we don't import the dump at creation-time it's going to be nightmare to do it later... Assuming that's even feasible. Acer (talk) 05:51, 14 August 2020 (UTC)[reply]

@Acer: Thanks, we have an agreement on importing on Wikitravel as well. see [2]--Tmv (talk|Contributions) 07:06, 14 August 2020 (UTC)[reply]
I don't think this is a good idea. The wiki is going to be created based on the Incubator activity, and with the Incubator pages. We are not creating the wiki primarily as a fork of Wikitravel, though their pages can be integrated. In order to not to get confused between two large import processes, I would prefer if first the import from Incubator gets done. That was the initial reason why I proposed to first get the project to its own wiki, and then to see about what can be done to integrate the Wikitravel content.
Then afterwards, other pages can be imported, according to what the community actually wants. That can surely also be done in a separate phabricator task for a server-side import later on. For example, surely there will be duplicates in articles, but also categories and templates, between the dump and the test-project. They can't just be overwritten, the community should decide what it wants to do in these cases. --MF-W {a, b} 08:20, 14 August 2020 (UTC)[reply]
Is it possible to import the dump first and then the Wikivoyage articles, avoiding overwritings by renaming the article names? --Tmv (talk|Contributions) 09:48, 14 August 2020 (UTC)[reply]
@User:Tmv Yes. I think that would be the best way. @User:MF-Warburg It's not two large imports. It's a big one and a small one. Ja/Wy here on Incubator has 922 pages total (all namespaces). The dump is way bigger. It's much easier to incorporate the few hundred pages here afterwards than the other way around. The XML file by itself is over 3gigs (without images). Its unwieldy and hard to work with, to pick and choose from that is not practical. At all. Acer (talk) 10:43, 14 August 2020 (UTC)[reply]
It is also very unwieldy to throw such a large number of pages at the community at once. What's the motivation here? --MF-W {a, b} 11:43, 14 August 2020 (UTC)[reply]
My general motivation is to preserve all the work that's been done writing those 9000+ articles from obliteration when Wikitravel inevitably goes under. If you mean why I'm defending a particular way of going about this, it's because I know it works. That's how we imported all the original Wikivoyage projects back in 2012. A backup was made, imported and the projects launched. Then in 2016 we did the same thing again for Finnish Wikivoyage, this time there were also Incubator pages. We imported the backup, launched the site, then added the Incubator pages afterwards. You say it's unwieldy to throw so many pages at a new project but once its up and running its very easy to delete/archive anything that is unwanted. Whats very hard to do is to work with large XML files offline. I had to cut it up in chunks just to do some basic editing. No one is going to comb trough a huge file like that to pick and choose what to import or not. But none of this really matters, its up to the community to decide what to do and I believe they've spoken in favor of importing. Acer (talk) 22:14, 14 August 2020 (UTC)[reply]
I'm going to ask the Japanese community for their opinion. --Tmv (talk|Contributions) 01:33, 15 August 2020 (UTC)[reply]
@Acer Sorry, we also made a page like Help:Wy/ja/目次. Were those counted on page 992 as well? --Tmv (talk|Contributions) 21:04, 14 August 2020 (UTC)[reply]
Yes, those are counted. See here. These are the page numbers by namespace:
Ja/Wy Incubator
Namespace Number
Mainspace 321
Talk 43
Mediawiki 1
Mediawiki talk 2
Template 287
Template talk 10
Help 18
Help talk 1
Category 173
Category talk 1
Module 64
Module talk 2
Total 922
Acer (talk) 22:14, 14 August 2020 (UTC)[reply]

(outdent) Comment Comment Sorry, I cannot agree to importing the all pages (not page-by-page) in mainspace from JAWT.

If we do that, we will have to modify a lot of template tranclusions, upload a lot of files to Commons (and modify names of a lot of files as needed), and so on, with too much time and effort.

In the first place, importing from WT means that not only imformation but also custom comes from WT into WY. In other languages, WT community itself moved to WY so it wasn't a problem that custom of WT came into WY. But JAWY started to grow it own custom already. I fear that the custom of JAWY that has grown for several years may be broken by importing from JAWT.

Letting custom of JAWT come into JAWY makes JAWY something like a archiving site of JAWT; we have little manpower for letting the pages are adjusted to JAWY. Inevitably, page quantity will talk and custom of JAWY must be absorbed to custom of JAWT. To grow a WY that be similar to WT cause that people flow to not JAWY but JAWT; JAWT must be better than a archiving site of JAWT. We should seek and grow good of JAWY itself. To be able to grow up freely is a good point of new project. --Atmark-chan <T/C> 17:16, 15 August 2020 (UTC)[reply]

As the discussion died down, I will mark this as X mark.svg Not done for now. --MF-W {a, b} 11:49, 28 March 2022 (UTC)[reply]

Wp/sro[edit source]

Please import the page sc:Mogoresu ([3]) from sc:wikipedia to the wiki project in Campadinese (Wp/sro). Grazie--Fausta Samaritani (talk) 10:59, 30 March 2022 (UTC)[reply]

Done: Wp/sro/Mogoresu. --MF-W {a, b} 23:30, 30 March 2022 (UTC)[reply]
Please import the page sc:Casteddu/campidanesu ([4]) from sc:wikipedia to the wiki project in Campadinese (Wp/sro). Grazie--Fausta Samaritani (talk) 07:38, 4 April 2022 (UTC)[reply]