From Test-Scratch-Wiki

Welcome to the main talk page for the Test Scratch Wiki!
Before starting a new discussion, please look at the archives to see if your question has been answered before.

Archives List (oldest first)

How to edit on the Scratch Wiki

We recommend that before you create your question, you read these tips to editing on the Scratch Wiki.

  • Sign your posts with four tildes (~~~~) after your post.
  • To do various text formatting, follow the following rules, rather than using any other text-editing methods:
  • Put new text under old text.
  • Always remember to be polite and respectful, assume good faith, and be welcoming, while following the Scratch Community Guidelines.


Hi everyone! Welcome to the Test Wiki, the home of many future wikis!

If anything still needs to be done, please put it below!

To Do List:


  1. Finish and polish the "Introduction to the Test Wiki" page: link (When done, please contact ErnieParke via English talk page)
  2. Once the confirm account extension, and the "Introduction to the Test Wiki" pages are done, invite all wiki volunteers to the wiki. This will be a critical time!
  3. Maybe add more support/help pages to the Wiki?
  4. Discuss organization and possible problems that might be faced.
  5. Reorganize the main page to be more useful/organized.

Specific People

  1. jvvg: Set up the confirm accounts extension.
  2. ErnieParke: Transfer all English Wiki images and templates to the Test Wiki. I am looking into doing that via Pywikibot.
  3. DACH Wiki: Update

ErnieParke (talk) 22:18, 20 October 2015 (MEST)

Thank you very much for your help to create this wiki Ernie! Mtwoll (talk) 22:51, 20 October 2015 (MEST)
It's my pleasure. I want to see what this Wiki will turn into. ErnieParke (talk) 03:56, 21 October 2015 (MEST)
Awesome, thank you for all your work :3 - LiFaytheGoblin (talk) 14:13, 21 October 2015 (MEST)
For the ToDo: should be updated! - LiFaytheGoblin (talk) 14:15, 21 October 2015 (MEST)
Feel free to add on to the To-Do list LiFay! :) ErnieParke (talk) 15:39, 21 October 2015 (MEST)

Coming soon

Pretty soon, this Wiki is going to receive the ConfirmAccounts extension. I plan on using this Wiki to test various features and receive community feedback before deploying them to the language-specific Wikis (after I test for bugs and stuff on my own server, of course). Stay tuned for more as I have time! Jvvg (talk) 03:40, 21 October 2015 (MEST)

I'm looking forward to it! BTW: Can you technically help LiFay to translate the parts of the ConfirmAccounts-Plugin texts in the DACH-Scratch-Wiki that can't be translated on the wiki-side? There are some German texts that we want to change, but we don't know where to do it. I think there are some files that only can be translated with FTP-connection, or am I wrong about that? Mtwoll (talk) 20:20, 24 October 2015 (MEST)


Can you install WikiEditor extension? It is a really good tool. --JayceeMinecraft (talk) 22:01, 21 October 2015 (MEST)

Is it relay important? Could you give some arguments why we need it? ("It is a really good tool" is no argument). Why did you give no links to the Plugin? Which wikis use it? Perhaps it is relay a good idea to install that Plugin...I don't know...I only know that every plugin we add could cause dangers of php-injection that we already had at the German scratch-wiki: It was lots of work to get rid of it. So I would say: Just add really established PlugIns that are used in Wikipedia or the other scratch-wikis. And: Deciding to install a PlugIn can be a long process... I think there is much work to do here before the process will be finished. Mtwoll (talk) 20:09, 24 October 2015 (MEST)

First Test for building separate language spaces

I made first tests for building separate language spaces, by copying some articles of the existing wikis here, but changing them by "replace" in an editor so, as when they were articles of "new language test wikis" here.

If we start to create the international test wiki, we (or the native speakers of that language) can follow the path of "best practice" we explored by experimenting with that method: So e.G. Italian would use language space "it", Spain would use the language space "es", french would use the language-space "fr" and so on.

First Examples

Please enlarge the existing and add more examples to find out what is the best method. Later we could perhaps use bots for that transfer...

Replacements made for transferring to test wiki

Example: [:de:]] to [[:test:]]:

  • reaplace [[ by [[:de
    • so all german articles are in a separate "de:"-namespace
  • replace {{ by {{/de
    • so all german templates are in a separate ":template/de"-namespace

To do so for Indonesian just replace "de" with "id" and so on.

Advantages of the method

  • We have exact rules for the language communities how to build up their wiki
  • The transferring in both directions could be automatic by bots: You can transfer an existing wiki complete to "test wiki" for having examples and you can transfer an wiki from "test wiki" to the "real wiki", when it is ready to be established in reality

Questions to be answered

(I already wrote down some arguments, please add your thoughts an arguments)

  • Is the replace-method explained above relay the right choice?
    • There is no "real choice" concerning the templates, because there seem to be only one option for the ":template"-namespace, so you only can divide this namespace by "/" not by ":", else the templates wouldn't work with parameters and so on
    • There could be the alternative to divide the article namespaces by "/" instead of ":" That has disadvantages for searching (because you can search in a separate ":"-namespace but not in an "/"-separated room.
  • should English articles use the "en"-namespace of the test-wiki or should they use the base namespace without "en"
    • Advantage: English is the "original wiki", perhaps it's easier to handle it special: It also would be easier to copy English articles here as a template for translation
    • Disadvantage: Why handle English language other than other languages, that's not stringently and gives an wrong example at the test wiki
  • should English templates use the "en"-namespace of the test-wiki or should they use the base namespace without "en"
    • Advantage: see "articles" + it's much easier to build "copytranslate" English articles when you don't have to care for the templates at the beginning: Just let the templates English and care for the translation of the article first. Just after the language-community has a lot of articles they can try to think about templates.
  • How to deal with Interwiki-Links
    • We could try to create two Interwiki-link-methods per language for the test-wiki: One could be directed to the corresponding article in the test-wiki, the other one could be directed to the corresponding article in wiki of that language (if it already exist): If possible we could use [[:de:de:Articlename]] to connect to the real wiki and [[:de:de:de:Articlename]] to the test-wiki, because [[de:Articlename]] is already used for the language-space of the original article.

What do you think?

Mtwoll (talk) 17:26, 24 October 2015 (MEST)

1). Is the replace-method explained above relay the right choice?
I'm not sure what you're talking about here, to be truthful...
2). should English articles use the "en"-namespace of the test-wiki or should they use the base namespace without "en"
I would say en: is best for English wiki articles to act as an example for other languages. Only pages that are not for one wiki only should use their base name (without "en" "ru" ect...)
3). How to deal with Interwiki-Links
Why would we even need to interwiki to the test wiki? I can see why we might move some de, id, en articles over for testing purposes, but wouldn't we remove them afterwards? I don't see any purpose to them...
ErnieParke (talk) 02:38, 25 October 2015 (MET)

1) With "replacement method" I mean the set of rules described in #Replacements made for transferring to test wiki

2) I completely agree!

3) You are right: If we have no Interwiki we don't have any decisions to be made about it. Also, if we use "en:Articlename" as a normal articlename and not a Intwerwiki-Link to the english wiki, it's not possible to use Interwiki in the traditional way. But if we have no Interwiki here, we also loose some big advantages, like easy referring to the other wikis (not only in artcles but also in discussions and technically pages)! e.g. I planed to transfer [[:de:Scratch-Wiki:Watch]] here (I think here is a better place than in the DACH-Scratch-wiki) and that would not work without Interwiki. You can't write [[:en:userErnieParke]] here: I don't like this state. And perhaps we make this state non-"undoable" by switching to the concept I described in #Replacements made for transferring to test wiki . Perhaps someone has an idea to solve that? (talk) 07:14, 25 October 2015 (MET)

Ideas who could help to create a wiki-farm

Her is a copy of a discussion with user:jvvg about who could help to create a wiki-farm that I think is interesting enough to be continued here with all of you:

I just saw that there is a group if wiki-developers trying actually solve this issue, see Perhaps we should join them? Browsing through the members of that group I found an interesting entry: .He works for Brikimedia a wiki-farm about LEGO and speaks English, German and French! As you surly know there are some connections between LEGO and Scratch and en:user:Lightnin even moved from Scratch Team to LEGO (see . So it's possible that they could help us with setting up a scratch wiki farm. Should we try to get in contact? <scratchsig>MartinWollenweber</scratchsig> 05:33, 1 October 2015 (UTC)

I probably don't have the time to join that project, but if you or anyone else wants to join or use their code, that would be awesome. However, I doubt that simply because someone works with LEGO means that he knows Lightnin. LEGO is a pretty big company (however, it is still certainly possible).<scratchsig>jvvg</scratchsig> 11:56, 1 October 2015 (UTC)
Your right Lightnin and GeorgeBarnick must not know each other only because they both work for LEGO, but LEGO sponsored the Livelong Kindergarten (Mitch Resnick is even called the "LEGO Professor") and both worked also intensive with Mediawiki, so it could be useful for them (and also for us) to know each other. <scratchsig>MartinWollenweber</scratchsig> 23:05, 1 October 2015 (UTC)
True. I don't really know enough about this to provide any decent advice.<scratchsig>jvvg</scratchsig> 00:42, 2 October 2015 (UTC)
I think I will followup this idea, if I got the time and tell you here <scratchsig>MartinWollenweber</scratchsig> 15:40, 7 October 2015 (UTC)

Interwiki Bot Mass Edit Warning

Tomorrow, in the morning (anytime 10-12 EST) and possibly afternoon ( anytime 3pm - 9 pm) I will be running Interwikibot to move all english wiki template and images to here. ErnieParke (talk) 03:15, 25 October 2015 (MET)

Generally: Great! But: By doing first experiments with manual copying from the "real wikis" to this "test wiki" I found out that we have to think, discuss and make decisions about Automatic replacements when transferring articles and templates between "real wikis" and this "test wiki".
With the English wiki it's somewhat easier, because the "base language" of this "test wiki" is also English. With Wikis of other languages it's more difficult, because they have also many "mediawiki syntactic"-words that are translated, e.g. [[File:Scratch logo.png|right]] could be [[Datei:Scratch logo.png|rechts]] in the German DACH-scratch-wiki (using the "wikis-base-language" for Mediawiki-syntax is optional, alternative you also could use English, but in DACH-wiki we use German language for that).
But also concerning transferring the English wiki here there are some decisions to be made (and I think we didn't experiment enough until now, to have a complete picture) : Most important is, if English templates shall have a separate namespace (not a real ":"-namespace, else templates would not work, but the "/"-namespace (I hope you understand #Questions to be answered even with my bad knowledge of English ;-). In the moment I tent to "no namespace for English templates". Perhaps you do some manual experiments yourself and define a written set of replacement rules here: I'm also very keen on the result of your "bot-based-mass-transfer", but perhaps we could avoid problems if we experiment and think a little bit more before doing something that has no easy "undo"... Mtwoll (talk) 06:54, 25 October 2015 (MET)
Cookies help us deliver our services. By using our services, you agree to our use of cookies.