User talk:Legoktm

Thank you grat works.--NI201512 06:46, 9 August 2014 (UTC)

Wrong Upload
I fund out I choosed the wrong destination (Mediawiki instead of Wikimedia/Commons), sorry for causing the mess. --Moroder (talk) 22:18, 30 April 2013 (UTC)

Questions about MassMessage prior to full deployment
Hi. I have two possibly related questions:


 * 1) When I go to testwiki:Special:MassMessage currently and try to enter text in the "Page containing list of pages to leave a message on" input, I don't see any autocomplete or suggestions. I thought this was already implemented?
 * 2) Related to 91344, does the Git submodule that's deployed to Wikimedia wikis need to be updated?

Thanks for all your work on the extension. I think we're nearly there. :-) --MZMcBride (talk) 17:48, 24 October 2013 (UTC)


 * I'm guessing this is related to 56070. Is there anything in your JavaScript error console?
 * Yes it would. I wasn't expecting on having it deployed until the next update went out though.
 * :) Legoktm (talk) 18:08, 24 October 2013 (UTC)


 * Aha, thanks for the pointer. Following 56070, input suggestions are working again. I'll leave it to you, Reedy, et al. to figure out when to update the submodule. --MZMcBride (talk) 21:01, 24 October 2013 (UTC)

Thanks for great work on MassMessage
A quick note from a colleague from the Programs team -- thanks for your great work on MassMessage! I've used it twice now and found it simple, slick, and fast. I really appreciated Global Message Delivery, but this is a pretty awesome replacement. So many thanks! :) -- LiAnna Davis (WMF) (talk) 03:08, 16 January 2014 (UTC)
 * Thanks, glad to know you find it helpful! Legoktm (talk) 09:55, 19 January 2014 (UTC)

I am upload.
Thnk your --NI201512 06:49, 9 August 2014 (UTC)

RL2
Hi :) I saw you'd been doing some work on RL2 and was wondering what your overall idea was for where it might end up (or to what extent you were considering taking it). I realise this is a bit of a vague question given the number of ideas and tickets bouncing around, but I've been looking for something to make installing scripts easier for users with little to no js experience and was hoping Gadgets (or rather a future version) might be what I'm looking for.  16:59, 23 August 2014 (UTC)

List of people who owe Legoktm a root beer
As per our conversation in London, I'm starting this section now that the GlobalCssJs extension is ready to be shipped, and intend to revive it for each toy of yours I'll see. Thank you so much for your work.

An important message about renaming users
Dear Legoktm,

I am cross-posting this message to many places to make sure everyone who is a Wikimedia Foundation project bureaucrat receives a copy. If you are a bureaucrat on more than one wiki, you will receive this message on each wiki where you are a bureaucrat.

As you may have seen, work to perform the Wikimedia cluster-wide single-user login finalisation (SUL finalisation) is taking place. This may potentially effect your work as a local bureaucrat, so please read this message carefully.

Why is this happening? As currently stated at the global rename policy, a global account is a name linked to a single user across all Wikimedia wikis, with local accounts unified into a global collection. Previously, the only way to rename a unified user was to individually rename every local account. This was an extremely difficult and time-consuming task, both for stewards and for the users who had to initiate discussions with local bureaucrats (who perform local renames to date) on every wiki with available bureaucrats. The process took a very long time, since it's difficult to coordinate crosswiki renames among the projects and bureaucrats involved in individual projects.

The SUL finalisation will be taking place in stages, and one of the first stages will be to turn off Special:RenameUser locally. This needs to be done as soon as possible, on advice and input from Stewards and engineers for the project, so that no more accounts that are unified globally are broken by a local rename to usurp the global account name. Once this is done, the process of global name unification can begin. The date that has been chosen to turn off local renaming and shift over to entirely global renaming is 15 September 2014, or three weeks time from now. In place of local renames is a new tool, hosted on Meta, that allows for global renames on all wikis where the name is not registered will be deployed.

Your help is greatly needed during this process and going forward in the future if, as a bureaucrat, renaming users is something that you do or have an interest in participating in. The Wikimedia Stewards have set up, and are in charge of, a new community usergroup on Meta in order to share knowledge and work together on renaming accounts globally, called Global renamers. Stewards are in the process of creating documentation to help global renamers to get used to and learn more about global accounts and tools and Meta in general as well as the application format. As transparency is a valuable thing in our movement, the Stewards would like to have at least a brief public application period. If you are an experienced renamer as a local bureaucrat, the process of becoming a part of this group could take as little as 24 hours to complete. You, as a bureaucrat, should be able to apply for the global renamer right on Meta by the requests for global permissions page on 1 September, a week from now.

In the meantime please update your local page where users request renames to reflect this move to global renaming, and if there is a rename request and the user has edited more than one wiki with the name, please send them to the request page for a global rename.

Stewards greatly appreciate the trust local communities have in you and want to make this transition as easy as possible so that the two groups can start working together to ensure everyone has a unique login identity across Wikimedia projects. Completing this project will allow for long-desired universal tools like a global watchlist, global notifications and many, many more features to make work easier.

If you have any questions, comments or concerns about the SUL finalisation, read over the Help:Unified login page on Meta and leave a note on the talk page there, or on the talk page for global renamers. You can also contact me on my talk page on meta if you would like. I'm working as a bridge between Wikimedia Foundation Engineering and Product Development, Wikimedia Stewards, and you to assure that SUL finalisation goes as smoothly as possible; this is a community-driven process and I encourage you to work with the Stewards for our communities.

Thank you for your time. -- Keegan (WMF) talk 18:24, 25 August 2014 (UTC)

--This message was sent using MassMessage. Was there an error? Report it!

Sysop
Hm? John F. Lewis (talk) 00:37, 4 September 2014 (UTC)
 * An edit of yours showed up on my watchlist as unpatrolled... :) Legoktm (talk) 00:59, 4 September 2014 (UTC)

Teahouse COPYING
Hi!

You suggested to add a COPYING file to the Teahouse extension repo. Unfortunately I'm not sure what information to add to it. Most COPYING files that I know contain a licence text. But the Teahouse project by german WMF is just inspired by the Teahouse of english Wikipedia. Should I just give credits to the authors of the WPEN version? Or link to it? I'd really appreciate your help on this.

Thanks in advance, --Osnard (talk) 19:21, 9 September 2014 (UTC)

Database dumps
Hi. Do you know who makes the database dumps? Because  at  is broken. Nirmos (talk) 21:28, 26 February 2015 (UTC)


 * Sorry, false alarm. It worked the third time I downloaded the file. Have a nice day =) Nirmos (talk) 01:57, 27 February 2015 (UTC)
 * Awesome! Legoktm (talk) 07:39, 27 February 2015 (UTC)

Starting conversion of LiquidThreads to Flow at mediawiki.org
(Hi Legoktm. I know that you already know, so I'm just adding this here for completism, and for any of your page-watchers. :)

Hello. I'm sending this to you, because you've been one of the top 50 users of LQT on mediawiki.org over the last 360 days, and I wanted to make sure that you'd seen the announcement at Starting conversion of LiquidThreads to Flow at mediawiki.org. There are links in the topic-summary at the top, for other discussions (wikitech-l and Project:Current_issues), and a link to the planned process and timeline (scheduled to begin April 6, with smaller conversions at first). Please do test Flow out at Talk:Sandbox if you haven't tried it recently, and give any feedback/suggestions/requests at that main discussion location. Much thanks, Quiddity (WMF) (talk) 00:04, 28 March 2015 (UTC)

T91169
Hi!

I'd like to start working on T91169. I've never done anything in PHP, so I'm wondering what testing environment I should use. Do I begin by creating an account at wikitech? Nirmos (talk) 07:33, 16 May 2015 (UTC)

Question on Manual:Extension_registration
Hi Legoktm,

I am currently converting a bunch of extensions for MW 1.25. I have used convertExtensionToRegistration.php and that worked. However, there are two things on Manual:Extension_registration where I am currently unsure what to do:

First, the page tells us to change the extension includes in LocalSettings.php from require_once to wfLoadExtension. This is the point where it starts throwing errors for me (like "class not found" or function not defined). The thing is that my function is defined in the central extension file.

For example, I add wfLoadExtension( 'BugtrackerStatus' ); to LocalSettings and it will tell me that a function, which is defined in extensions/BugtrackerStatus/BugtrackerStatus.php can no longer be found. What is the right way to solve that? Move the functions to another file, maybe into a class and autoload it? Or something else?

The second thing is: Am I right that in LocalSettings.php I should use wfLoadExtension while in the main file of the extension I should add this if ( function_exists( 'wfLoadExtension' ) ) { block, which then for a second time contains a call to wfLoadExtension. Is that correct? Seems duplicated to me...

Cheers! --88.130.99.237 01:19, 28 May 2015 (UTC)


 * Hi!
 * 1. wfLoadExtension skips the PHP entry point entirely, so any code in there will not be loaded. This means any global functions must be converted into static class methods, that are loaded via AutoloadClasses.
 * 2. We tell people to use wfLoadExtension in LocalSettings.php, except there will be people who are still using the old-style require_once and loading the PHP entry point. So we can add a wfloadExtension call inside the entry point. But some people will try using the newer extension version with old MediaWiki core, which is why we need the function_exists check.
 * Does that answer your questions? Legoktm (talk) 00:35, 1 June 2015 (UTC)


 * Yes, it does. It wasn't clear to me, that the old entry point would basically no longer be used at all. I thought that the most central, the main file would not suddenly become kind of superfluous.
 * Alright, I have moved my functions into a class in another file.
 * Thanks for the information! --88.130.86.234 22:20, 2 June 2015 (UTC)

You've got e-mail
Hi Lego, I sent you an e-mail a couple of days ago, not sure you've had the chance to look at it yet. Please do :-) odder (talk) 14:37, 22 June 2015 (UTC)