User talk:SVG

E-M@il Welcome on my user talk! [ Add topic]

Question
Please see my question at Extension talk:GlobalUserGroups. —  Waterfox ~talk~ 21:12, 23 December 2010 (UTC)


 * I have answered you. SVG 21:30, 23 December 2010 (UTC)
 * Thanks. See [ my reply]. —  Waterfox ~talk~ 00:26, 24 December 2010 (UTC)

Code review
Thanks for chipping in on code review. I confess I'm a little nervous, though, because I have only seen you mark one "fixme", and lots of "ok", which probably means you're marking "ok" more than you should be. For example, I see you marking things as "resolved" or "ok" after the first "fixme" is addressed. Does that mean you've done a full review yourself, or have you merely verified that the original "fixme" is resovled? If it's the latter, then I'd like to ask you instead mark those as "new", since reviewers may stop reviewing once they've found the first problem. -- RobLa-WMF 21:21, 22 December 2011 (UTC)


 * Hi Rob. Excuse my late reply, I wasn't there. When I mark a revision as ok, every line I've checked. In r105078, I marked it as resolved because it saw to be solved. I wrote for the case that I still wrong "Seems being fixed. Marked it as resolved". I hope it is? Thanks for the advice. In future, I will wait at marking revisions as resolved. Regards, SVG 20:43, 27 December 2011 (UTC)

Anyone can get developer access
Hi, Tim! I saw your comment on someone who was asking for developer access and just wanted to let you know -- ANYONE, including anyone who has never developed for MediaWiki before, can get developer access. I see no reason to raise barriers for this.

Thanks! Sumana Harihareswara, Wikimedia Foundation Volunteer Development Coordinator (talk) 15:40, 9 April 2012 (UTC)


 * You don't know if the requesting user knows what does it mean to develop something. Some users might think they are coding something because they are learning how to work with CSS. You don't know if the user even knows what PHP is. I don't agree with this, the user should at least know how to install and configure a wiki. If you don't want arguments for or against anything, it would be appropriate to remove the Discussion section. Tim (SVG)  15:57, 9 April 2012 (UTC)


 * Tim, thanks for the reminder -- I probably should rename the "discussion" section to something else. (There should be a space for the person granting access to ask questions or give instructions, like "that shell name is taken -- how about these alternatives?")
 * Can you tell me what harm comes from granting developer access to people who are unskilled, new, or confused? I personally don't see the downside, but perhaps you're seeing something I'm not.  Sumana Harihareswara, Wikimedia Foundation Volunteer Development Coordinator (talk) 16:41, 9 April 2012 (UTC)


 * We don't know if an user can be trusted. Users should give a small example of a self-written code. It's okay if there's only a little experience cos little experiences can be expanded by working on some projects. Dcoetzee is a trusted user because he's a sysop at Wikimedia Commons, sure, that's not the problem. I know a putative developer who is just able to copy others' extensions and in cases like this it's not okay if he or she gets access to represent oneself. If the majority thinks your way is the better one, I'll accept this :-) Tim (SVG)  16:59, 9 April 2012 (UTC)
 * So it sounds like your concern is that people might use developer access to plagiarize. Is that the only concern, or is there something else you're worried about?  People can plagiarize whether they have developer access or not, right?  And if we find that someone's been acting in a way contrary to our values, we can cancel their access.
 * I really do want to understand the possible downsides of the wide-open approach to access -- if you have any other concerns, please share them! As you probably understand, the upsides are ENORMOUS.  People who learn with us will tend to stay with us as contributors.  The less gatekeeping we do, the faster the process can move.  And it's more in keeping with our values as a Wikimedia community: inclusivity and a low barrier to entry.  But I do want to hear arguments from the other side. Sumana Harihareswara, Wikimedia Foundation Volunteer Development Coordinator (talk) 17:57, 9 April 2012 (UTC)

Re:Editor / Sichter
Guten Abend, nun ich betreibe selbst einen Wiki und arbeite momentan daran, die Version 1.19.0 stabil zum laufen zu bekommen und nebenbei helfe ich hier natürlich gern bei den nötigen Übersetzungen. Vielen Dank für das erteilte Recht, ich bin zwar nicht ständig aktiv, werde aber weiterhin gelegentliche Übersetzungen tätigen. Gruß Sandro aka Abani79 (talk) 20:11, 3 June 2012 (UTC)


 * Nicht zu danken. Wir freuen uns immer über Helfer, besonders weil ich viele Wiki-Betreiber kenne, die sich hier nur mit Google Übersetzer weiterhelfen zu wissen. Solltest du Probleme mit etwas Spezifischem bei deinem Wiki habe, so kann ich dir vielleicht dabei helfen, wenn du wünschst. Tim (SVG)  20:16, 3 June 2012 (UTC)

Hallo nochmal, es gibt so einige Probleme bei der aktuellen Version, Dateiupload funktioniert seit Umstieg von Version 1.18.3 nicht mehr korrekt und es werden z.B. bei den Letzten Änderungen die Bilder der Pfeile (arrow.png) nicht dargestellt, allerdings habe ich auch jede Menge Erweiterungen installiert, nur um mal ein paar Sachen genannt zu haben. Abani79 (talk) 20:22, 3 June 2012 (UTC)


 * Eine Erweiterung, welche durch Hooks Einfluss auf diese Funktionen nimmt, wäre durchaus denkbar. Sind die Pfeile absolut nicht eingebunden (also nicht im Quelltext des Browsers) oder ist nur die Quelle der Bilder falsch? Tim (SVG)  20:27, 3 June 2012 (UTC)

Guten Tag SVG, zunächst mal eine Frage zu "Hooks", gibt es eigentlich eine kalre Übersetzung dazu, in deutsch wäre es z.B. mit "Haken" übersetzbar, bin mir allerdings nicht ganz sicher, ob man es im englischen genauso meint. In der Tat sind über 10 Erweiterungen installiert, u.a. WikiEditor, der in Version 1.18.3 noch funktionierte (ist noch auf meinem Webspeicher) und nun nicht mehr, ich kopierte ihn ins neue Verzeichnis "wiki" für die Installation von Version 1.19, dennoch wird die Oberfläche nicht geladen, ich könnte mir vorstellen, das die Versionen der vorhandenen Erweiterungen evtl. zu viele Fehler auslösen könnten, bin mir aber nicht sicher. Abani79 (talk) 14:57, 4 June 2012 (UTC)


 * Da „Hook“ ein Fachwort ist (ähnlich wie „Bug“) sollte es nicht verändert werden. Höchstens eine Übersetzung in der Einleitung auf der Seite „Manual:Hooks/de“ in Klammern wäre denkbar. Tim (SVG)  15:02, 4 June 2012 (UTC)

IRC
Just curious, do you use IRC, and if so, what's your IRC nick? I use the Wikimedia channels on a daily basis.--Jasper Deng (talk) 17:24, 8 June 2012 (UTC)


 * You can find me in #mediawiki as Tim_Weyer but I'm mostly not online (should add it to my start script). I'll first have to search for the right commands to log me in etc. Tim (SVG)  17:31, 8 June 2012 (UTC)

Thank you
Hallo SVG. Thanks for flagging me as "autoreviewer". Regards. --Marco Aurelio (talk &bull; meta) 13:22, 29 June 2012 (UTC)


 * I saw your edits and I see no need why we should patrol edits of users who are helping here especially when they are trusted users (stewards, global sysops, global rollbackers, staff members). Thanks for contributing MediaWiki.org! Tim (SVG)  14:51, 29 June 2012 (UTC)

Special:AbuseFilter/17
Is this really necessary? Can't we just use semi-protection? It's also possible to modify the protected page notice to include such a message, without having to out IP addresses.Jasper Deng (talk) 16:40, 9 July 2012 (UTC)


 * Unfortunately, we can't. semi-protection = autoconfirmed users. Many users who request developer access just created their account on MediaWiki.org a few minutes ago. Tim (SVG)  16:45, 9 July 2012 (UTC)

translatewiki:Thread:Support/About_MediaWiki:Changeauthor-explanation-single/en
Can you address this? --Nemo 23:27, 2 September 2012 (UTC)


 * I don't know if I am able to change anything since we use Git (and I am not glad about the new project owner system that denies other developers from editing extensions besides their own extensions). Although it doesn't appear as much work, it's a long time ago I've been worked with Git and I only did so a few times. I use so much time for my workplace, therefore I got to tell you that I am not available during the week but with pleasure on weekends. Is it urgent? If yes, I might find some time during lunchtime at my workplace. Cheers, Tim (SVG)  17:02, 3 September 2012 (UTC)


 * No, it's not urgent, but it needs to be done. I'm sorry to hear about Git and I understand, however I found the Git/Tutorial and such a small change is probably a good one to start with. I managed to make a commit myself thanks to that tutorial, and I had never committed code anywhere before... Thanks, Nemo 17:17, 3 September 2012 (UTC)

Non English MediaWiki functionality
Does Template have the same effect as Vorlage when MediaWiki is set to German? It seems most functions allow for English to be entered, such as category/Kategorie and special pages. It would be useful since I'm adding a lot of stuff from the English Sturmkrieg and it would save a lot of time to not have to change stuff like that; though I do end up erasing huge amounts and rewriting them to avoid getting bogged down with trying to make a translation that would probably be inaccurate. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 03:41, 27 December 2012 (UTC)


 * Yes, Template is equivalent with Vorlage such as Special is equivalent with Spezial. You can use every English namespace title in wikis with other languages. Cheers, Tim (SVG)  14:40, 27 December 2012 (UTC)

MediaWiki:Group-user.css
Hi. Re: MediaWiki:Group-user.css, 47812. :-) --MZMcBride (talk) 06:08, 5 December 2013 (UTC)


 * Hey. Thanks for that notification. I've just commented it. Tim (SVG)  07:08, 5 December 2013 (UTC)

Question
Hello. I want to join to Wikiunity but the page don't load. There are any problem with the wiki? I want to create a wiki in you wiki host. Regards. 190.33.67.43 02:32, 28 June 2014 (UTC)

Hilfe beim Konfigurieren
Hallo Tim, ich brauche Hilfe beim Konfigurieren eines Wikis (das ich betreibe). Einmal war ich im IRC und da war leider keiner anwesend. Ich konnte deine Skypeadresse aus Wikia herausfischen (sorry) und habe dich mal vor einigen Monaten angesprochen. Ich installierte vor einigen Tagen mein eigenes Wiki auf meinem Server. Jetzt stehen noch Konfigurationseinstellungen vor mir, die ich nicht wirklich gut verstehen kann und ich brauche Hilfe. Die anderen Systemadmins, die ich kenne, sind leider wegen ihrem Studium inaktiv. Es würde mich sehr freuen, wenn du mir (oder jemand anders, der deutsch spricht) mir hilft. Meine Skypekontakt gebe ich nur über E-Mail raus. Oder, ich schreibe sie hier bei einer AW / RE auf und danach bitte ich darum, dass die Version unsichtbar gemacht wird, damit mein Name nicht hier steht. LG, Yässinzeldafan (talk) 11:09, 6 October 2014 (UTC)

BatchUserRights
Hello SVG. I hope that this message find you well. I am writting to inquire if you could help us determine in https://phabricator.wikimedia.org/T180668 the license of Extension:BatchUserRights. According to Andre you seem to have some involvement over there? Best regards, &mdash;MarcoAurelio (talk) 12:10, 16 November 2017 (UTC)

2020-05-27@2
Hey here is some help for you for T165128. MediaWiki message delivery (talk) 07:17, 27 May 2020 (UTC)

This page is a simple and guided landing page for new Wikimedia developers. It is part of the Onboarding new developers initiative.

For other options to get involved, see.

Welcome!
You want to work on Wikimedia code and need ideas where to start?

Wikimedia's technical community always welcomes new contributors to our projects.

Become part of a global community and help make access to free knowledge easier for everyone!

Contributing to Wikimedia is a four-step process:


 * 1) Choose a software project
 * 2) Set up your development environment
 * 3) Choose and solve a task (write and test your code)
 * 4) Submit your code changes

Some basics to know
You can skip this section if you are already used to free and open source software culture.

Wikimedia has hundreds of software projects in many different areas. if you want to get an overview.

The maintainers of each software project are pretty free to choose the infrastructure they prefer. In general, basically all software projects have


 * a task tracking tool where software bugs and enhancement requests are reported, managed and discussed. Examples are Wikimedia Phabricator, GitHub, or Sourceforge.
 * a code repository where the source code can be "checked out" to everybody. Examples are Wikimedia Git/Gerrit, GitHub, or Sourceforge.
 * a code review tool where proposed code changes (so-called patches) get discussed and improved. Examples are Wikimedia Git/Gerrit, GitHub, or Sourceforge. Once your proposed patch is good and is merged into the code repository, your code changes will become available to everybody. (You could read more about good practices for code review here.)
 * general places for discussion of the software project and/or for receiving help and support. Those places can be mailing lists or IRC chat channels or wiki pages or other places. The exact places depend on each project. You could also contact specific mentors via "Email this user" on their user pages, but note that "questions asked in private don't help others".

At any point, if you run into problems or need help, please ask. If you want to ask good questions in the right places, we recommend you read the section "Feedback, questions and support".

Choose a software project
This is the recommended way to start. Choose one of the following projects and follow the project's documentation to set up your development environment, choose a task to work on, solve the task, and submit your code changes for review:

''Are you a maintainer and want your project to be included in the list of software projects above? Find out more and join!''

Outreach programs and single tasks
Apart from the recommended software projects above, there are more ways to choose a project or task to work on:

Looking for additional resources?

 * How to become a MediaWiki hacker: For potential new developers who want to specifically work on MediaWiki core or MediaWiki extensions.
 * Developer hub: Resources to more documentation and information for established Wikimedia developers.
 * For real-time communication use on IRC (Internet Relay Chat)
 * There are also several email lists for discussion of Wikimedia software.

Want to contribute something else?

 * How to contribute lists many more ways to contribute, also in non-technical areas.