User talk:Legoktm

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

Contents

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 gerrit: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)

1. I'm guessing this is related to bugzilla:56070. Is there anything in your JavaScript error console?
2. Yes it would. I wasn't expecting on having it deployed until the next update went out though.

<meta />:) Legoktm (talk) 18:08, 24 October 2013 (UTC)

Aha, thanks for the pointer. Following bugzilla:56070#c16, 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. onei 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.

• 

  Cheers! --User:Elitre (WMF)

• 

  Anybody who has earned a beer from Elitre probably deserves more than one beer :P CristianCantoro

• 

  You actually deserve more than one from me ;) Sannita

• 

  I owe you a LOT of root beer. (Also, future bribes ;) Quiddity

• 

  With ice cream! Thank you! User:WhatamIdoing

• 

  I have a complaint. I think you're behind the global user page work, so I'll need to send more beers your way, but you haven't redeemed the previous ones yet. --User:Elitre (WMF)

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)

Random acts of CR barnstar

I hereby award you this random acts of code review barnstar for being the second most active +2'er that we know of! Nobody is able to keep count of the number of people, repositories and formerly-hopeless causes which were smashed by your review. Nemo 23:21, 3 February 2015 (UTC)

Database dumps

Hi. Do you know who makes the database dumps? Because svwiki-20150224-pages-meta-current.xml.bz2 at [1] 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,[2] 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)

phab:T91169

Hi!

I'd like to start working on phab: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#Migrating

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#Migrating 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)

A new This is Barnstar! for you

	The This is Barnstar!
	The new award for those who rock. --Ricordisamoa 04:24, 10 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)

A beer for you!

Good job and keep up. :) Alangi derick (talk) 16:03, 13 November 2015 (UTC)

Manual:Eval.php

Sorry. I thought it was a more up to date description and that's why i marked that as outdated.

Manual merge

I just manually merged the two accounts at this request. MBisanz ^talk 13:11, 18 January 2016 (UTC)

Skinned-knuckles award

	Skinned-knuckles
	Sometimes we need to put our finger into a dyke. Sometimes we need to pull them out. And sometimes they act all on their own. Whichever it was … Thanks to the honesty of your fingers. — billinghurst sDrewth 09:18, 20 February 2016 (UTC)

I'm not sure if this is about the same subject but I really got a lot out of your blog entry. I had no idea of the state of the situation at work. I hope something changes for the better. Liz (talk) 20:00, 20 February 2016 (UTC)

Please provide feedback on suggested improvements to the Code of Conduct

Thanks to everyone who’s helped work on the Code of Conduct so far.

People have brought up issues they feel were missed when working on "Unacceptable behavior" and "Report a problem". Consultants have also suggested changes in these same sections.

These are important sections, so please take a look at the proposed changes. I apologize that this feedback arrived later than planned, but I think this will create a better document.

If you prefer to give your opinion privately, feedback via e-mail is welcome at conduct-discussionwikimedia.org.

Thanks. Mattflaschen-WMF via MediaWiki message delivery (talk) 04:18, 24 February 2016 (UTC)

A barnstar for you!

	The Special Barnstar
	Thanks a bunch for dealing with the code changes I recently uploaded. I always like your friendly help with things like this. This barnstar is just a small sign of appreciation. [[kgh]] (talk) 14:09, 24 March 2016 (UTC)

Some stroopwafels for you!

I've been doing my annual review stuff and realized how much I miss working closely with you. I thought I'd throw some stroopwafels your way as a way of saying thanks for all the cool stuff you've worked on without me this year. BDavis (WMF) (talk) 22:07, 3 May 2016 (UTC)

💕 Legoktm (talk) 21:54, 6 May 2016 (UTC)

Project:Requests

A few permissions requests are open at the request page. Music1201 (talk) 04:37, 11 July 2016 (UTC)

I have replied on the page. Music1201 (talk) 22:42, 13 July 2016 (UTC)

FRSbot questions

Hi, a question at en:User talk:Jimbo Wales#Still unanswered FRS question originally came up in February when we tried to ping you, and Harej tried again a few days ago with no luck either. I see you're more active here than on enwiki so I'm hoping you will see this and respond there, please. EllenCT (talk) 17:34, 24 July 2016 (UTC)

Thanks very much. Could you please help with the followup questions about the effective request distribution algorithm, the transparency of the database, and how much you would charge for documenting the whole system? I would love to get it to be able to pass independent third party audits. EllenCT (talk) 15:58, 27 July 2016 (UTC)

Those followup questions have been archived to en:User_talk:Jimbo Wales/Archive 209#Still unanswered FRS question. I am still very much interested in the answers. Did anyone re-write the bot after User:Harej? EllenCT (talk) 10:20, 28 July 2016 (UTC)

Any further thoughts on the questions? EllenCT (talk) 16:22, 12 August 2016 (UTC)

A barnstar for you!

	The Translator Barnstar
	1 Israa boubnane (talk) 09:42, 26 July 2016 (UTC)

إليك هذا أوهذه القط

 هل أحببتم هذا قط بريئ وجريئ وممتع

Israa boubnane (talk) 09:46, 26 July 2016 (UTC)

RecentChangesOption

Delivering a message here :P - Jack Phoenix would like you to ping her about RecentChangesOption whenever you have the time so that she can talk about the extension with you. SamanthaNguyen (talk) 02:42, 2 August 2016 (UTC)

A cookie for you!

hlo

A Little Help Finding Direction

Hey there. Thanks for the thanks on the Manual:Extension.json/Schema page! Quick question, as I haven't had contact with anyone else in the community, if you have a minute:

• Who should I talk to about potentially tweaking the way article URL redirects work? Example:
• https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:runJobs.php gets turned into https://www.mediawiki.org/wiki/Manual:runJobs.php
• It would be nice if we/you/them/us stopped generating apparently antiquated URLs and then having to redirect to the new page. I am willing to work on such an tweak.

- Timmay911 (talk) 04:57, 17 January 2017 (UTC)

Hi, and welcome :) Those URLs aren't antiquated, the redirect is kind of a hack around caching. Basically Special:MyLanguage redirects you to the version in your language, which for most of us is the canonical English source page. If you change your language and it's been translate to that language, Special:MyLanguage will redirect you to a different page. Legoktm (talk) 07:10, 17 January 2017 (UTC)

Ahhh... I gotcha. There seems to be a lot of "hacks"... :) I'm reading as much as I can about everything in MW. I'd like to contribute in more ways than just updating tables, but I'm not sure what my skills are best suited for. Can you point me in the right direction? Timmay911 (talk) 01:53, 18 January 2017 (UTC)

Looking for Consultant

Sorry about misplacing this earlier...

I'm interested in hiring someone to work on an extension allows comments or counterarguments associated with a specific passage of the main article to be created and displayed in a sidebar. Some details are available at github. Would you be interested? Or would you have a recommendation of who might be qualified with the experience and time for a project like this? Trig12 (talk) 17:43, 19 February 2017 (UTC)

Sorry, I'm not interested. Legoktm (talk) 04:44, 20 February 2017 (UTC)

Adding Extension PlantUML to packagist

I am the maintainer of https://www.mediawiki.org/wiki/Extension:PlantUML I'd like to add composer support for it and was pointed here from Composer/For_extensions. What do I have to do? --WolfgangFahl (talk) 18:51, 7 March 2017 (UTC)

Linter

Hi. Do you plan to extend the install of the Linter extension on more projects? I was wondering if we could have it on Meta. If further deployments are to be scheduled then I'll wait until them. If not, please advice if a request to have this enabled on Meta would be approved. Best regards, MarcoAurelio (talk) 15:54, 16 March 2017 (UTC)

Yes that is the plan, however we are doing a staggered rollout to ensure the performance is acceptable and that we don't overload the servers. Meta-Wiki is classified as a "large" wiki so it'll probably be in one of the later deployments. Legoktm (talk) 05:01, 17 March 2017 (UTC)

Heyyy friend Legoktm! :D

Hello. I like ur posts! could you please do me a favor? 😀 My Friend Taher is in a contest and he needs some help. He´s participating in Wiki loves africa contest and he would definitely appreciate if you vote for his photo if you like it.

PHOTO 28 .

Would you please go to this link: https://commons.m.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2016/Community_Prize_Selection and please click "Edit sign" next to the letter of *PHOTO 28* below, and then add "striked text PedroPinto (talk) 22:27, 6 April 2017 (UTC)" at the end of the pragraph and click save.

Thank you much.

Extension registration wall of sadness

Hey, I noted that Extension registration wall of sadness notes Extension:OrphanedTalkPages as not being converted to extension registration. That's sad :(, especially considering it never used the old system. Am I missing something? OrphanedTalkPages is 1.25+ only since it only uses extension.json. —Mainframe98 _talk 08:16, 24 August 2017 (UTC)

Yeah, it's buggy. Giant git repos + NFS doesn't work well together. I've rewritten that part (gerrit:374095) and once I deploy that in a few days it'll show OrphanedTalkPages as being converted. Legoktm (talk) 06:56, 28 August 2017 (UTC)

A goat for you!

Libraryupgrader++

Greg (WMF) (talk) 06:21, 31 August 2017 (UTC)

extreg-wos not listing a converted extension

Hi. I was looking for some work at <https://tools.wmflabs.org/extreg-wos/> and found that Extension:ChangeAuthor is listed as not converted, however it does have an extension.json file. Is it because there's no Phabricator ticket or because there's no empty PHP entry point for that extension? Thanks. —MarcoAurelio (talk) 17:16, 12 January 2018 (UTC)

For some reason, that extension doesn't appear to have a Phabricator/Diffusion mirror? <https://phabricator.wikimedia.org/r/p/mediawiki/extensions/ChangeAuthor;browse/master/> is a broken link. I recently gave up on having the extreg-wos tool maintain git checkouts because it just was not working with the Toolforge NFS set up. Instead it now scrapes Phabricator to see if extension.json exists. So if the mirror can be added, extreg-wos should pick up that it's been converted. Legoktm (talk) 18:49, 12 January 2018 (UTC)

I see. The only reference that Phabricator had was an old SVN copy. I've created <https://phabricator.wikimedia.org/diffusion/ECHT/> that mirrors the Gerrit repo now. Thanks. —MarcoAurelio (talk) 08:18, 13 January 2018 (UTC)

I've also did some maintenance on the wiki page. Hope that's alright. Regards, —MarcoAurelio (talk) 08:19, 13 January 2018 (UTC)

DeleteBatch or Delete Batch?

Hi and sorry to disturb you again. I'd like to inquire about <https://gerrit.wikimedia.org/r/#/c/405906/2/extension.json>. Kghbln suggest that we rename back Extension:DeleteBatch to Delete Batch, but I don't see it clear why we should. Some more discussion is happening here. I think I remember that, in a similar case, you adviced against doing so. I'm not sure and I just want to do the right thing so if you could please share your advice I'd appreciate it. Thank you, —MarcoAurelio (talk) 17:13, 24 January 2018 (UTC)

Left comments in both places :) Legoktm (talk) 19:57, 24 January 2018 (UTC)

A cheeseburger for you!

For your wonderful GSoC 2013 proposal :) Alangi Derick (talk) 19:02, 25 February 2018 (UTC)

Share your experience and feedback as a Wikimedian in this global survey

Hello! The Wikimedia Foundation is asking for your feedback in a survey. We want to know how well we are supporting your work on and off wiki, and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation. You have been randomly selected to take this survey as we would like to hear from your Wikimedia community. The survey is available in various languages and will take between 20 and 40 minutes.

Take the survey now!

You can find more information about this survey on the project page and see how your feedback helps the Wikimedia Foundation support editors like you. This survey is hosted by a third-party service and governed by this privacy statement (in English). Please visit our frequently asked questions page to find more information about this survey. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email through the EmailUser feature to WMF Surveys to remove you from the list.

Thank you!

WMF Surveys, 18:36, 29 March 2018 (UTC)

Reminder: Share your feedback in this Wikimedia survey

Every response for this survey can help the Wikimedia Foundation improve your experience on the Wikimedia projects. So far, we have heard from just 29% of Wikimedia contributors. The survey is available in various languages and will take between 20 and 40 minutes to be completed. Take the survey now.

If you have already taken the survey, we are sorry you've received this reminder. We have design the survey to make it impossible to identify which users have taken the survey, so we have to send reminders to everyone. If you wish to opt-out of the next reminder or any other survey, send an email through EmailUser feature to WMF Surveys. You can also send any questions you have to this user email. Learn more about this survey on the project page. This survey is hosted by a third-party service and governed by this Wikimedia Foundation privacy statement. Thanks!

WMF Surveys, 01:34, 13 April 2018 (UTC)

Your feedback matters: Final reminder to take the global Wikimedia survey

Hello! This is a final reminder that the Wikimedia Foundation survey will close on 23 April, 2018 (07:00 UTC). The survey is available in various languages and will take between 20 and 40 minutes. Take the survey now.

If you already took the survey - thank you! We will not bother you again. We have designed the survey to make it impossible to identify which users have taken the survey, so we have to send reminders to everyone. To opt-out of future surveys, send an email through EmailUser feature to WMF Surveys. You can also send any questions you have to this user email. Learn more about this survey on the project page. This survey is hosted by a third-party service and governed by this Wikimedia Foundation privacy statement.

WMF Surveys, 00:43, 20 April 2018 (UTC)

Are composer.json best practices still up to date?

Since you created this page: Is Manual:composer.json best practices still up to date and something extension developers should follow, or superseded by extension.json? --MGChecker (talk) 23:04, 8 August 2018 (UTC)

Interwiki mapping for codesearch?

G'day mate. Do you see that there could be value for interwiki mapping for codesearch? Or do you reckon that most work there will either not result in links, or maybe that is more specific to say that linking is unlikely to be from within the WMF wikis. — billinghurst sDrewth 12:47, 7 October 2018 (UTC)

SpamBlacklist 2.0

(Pinging @Jackmcbarn: as well)

Hey Legoktm, I was thinking of completely revamping Extension:SpamBlacklist by ripping off Extension:AbuseFilter almost in its entirety, the only difference being that the abuse filters (aka blacklist) would be checked against a whitelist, as the current SpamBlacklist does. So there would be both a Special:SpamBlacklist and a Special:SpamWhitelist, both of which would look pretty much the same as the current Special:AbuseFilter.

The database tables too would have pretty much the same structure as AbuseFilter's, with spam_blacklist_history, spam_whitelist_history, etc. tables (unless both lists are going to be stored in the same table, and there's just going to be a sb_type field, that's 0 for blacklist and 1 for whitelist).

But now I'm thinking, is it possible that AbuseFilter and SpamBlacklist could/should just be combined into one extension, to reduce the amount of code duplication? E.g., Special:AbuseFilter could serve as the Special:SpamBlacklist, and then there would also be a Special:SpamWhitelist to override that?

It sounds like people want pretty much the same features in the new SpamBlacklist that AbuseFilter has. Thanks, Setian~mw (talk) 20:53, 22 February 2019 (UTC)