User talk:01tonythomas


Thanks. I too was wondering why there was a lot of abuse filter problems.

Welcome to!

Yes, welcome! This site is dedicated to documenting the MediaWiki software, the software behind many wikis, including that of Wikipedia and the Wikimedia Foundation projects.
Please, take a look at the following pages. They might prove useful to you as a newcomer here:

If you have any questions, please ask me on my talk page. Once again, welcome, and I hope you quickly feel comfortable here, and find this site useful documentation of the MediaWiki software.

Thanks! Wiki13 talk 16:03, 19 February 2014 (UTC)Reply[reply]


Sorry for nominating your userpage and getting you locked. At first sight your user page really looked like the ones most spam bots make. Therefore I want to apologize that this happened to you. Even tough that this happened I want to welcome you to I'm going to place a welcome template with some useful links. Kind regards, Wiki13 talk 16:02, 19 February 2014 (UTC)Reply[reply]

Join the GSoC & OPW IRC meeting[edit]

Hi! The community bonding period is over, and you should have started working on your project. In addition to the strict work, you are required to report frequently, see the details at the GSoC or OPW pages.

The Engineering Community team is organizing a Q&A session for all participants (mentors included) tomorrow Tuesday at #wikimedia-office connect, see Engineering Community Team/Meetings/2014-05-20. See you there!--Qgil (talk) 21:57, 19 May 2014 (UTC)Reply[reply]

I will be there. Was a bit busy with my exams, which will get over tomorrow! - Tony


Hi, I'm having a problem with Extension:Mailgun. When I run composer update, it's not pulling in a Mailgun.php to the Mailgun directory. Any thoughts on how to deal with this situation? Thanks. LibertyAlerts (talk) 01:09, 7 April 2016 (UTC)Reply[reply]

Okey. So, you need to extract the extension to mediawiki/extensions/ and then, $ cd Mailgun $ composer update . It works for me here, so can you check if you have composer installed locally in your machine, and is allowed to pull ? I will submit a change to upgrade the same to V2.0 soon, as its available here though ( )01tonythomas (talk) 04:45, 7 April 2016 (UTC)Reply[reply]

This is the result I'm getting: [~/www/commons/w/extensions]# tar xvf Mailgun-REL1_26-ba62192.tar.gz 
Mailgun/.gitreview [~/www/commons/w/extensions]# cd Mailgun [~/www/commons/w/extensions/Mailgun]# ls
./   composer.json   gitinfo.json  MailgunHooks.php
../  extension.json  .gitreview    version [~/www/commons/w/extensions/Mailgun]# composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
  - Installing symfony/event-dispatcher (v2.8.4)
    Loading from cache

  - Installing guzzle/guzzle (v3.9.3)
    Loading from cache

  - Installing mailgun/mailgun-php (v1.7.2)
    Loading from cache

symfony/event-dispatcher suggests installing symfony/dependency-injection ()
symfony/event-dispatcher suggests installing symfony/http-kernel ()
guzzle/guzzle suggests installing guzzlehttp/guzzle (Guzzle 5 has moved to a new package name. The package you have installed, Guzzle 3, is deprecated.)
Writing lock file
Generating autoload files [~/www/commons/w/extensions/Mailgun]# ls
./   composer.json  extension.json  .gitreview        vendor/
../  composer.lock  gitinfo.json    MailgunHooks.php  version [~/www/commons/w/extensions/Mailgun]#

LibertyAlerts (talk) 23:56, 7 April 2016 (UTC)Reply[reply]

looks like you are getting the composer pulling in the correct Mailgun version perfectly ? The mailgun code will be pulled to
01tonythomas (talk) 03:59, 8 April 2016 (UTC)Reply[reply]
Actually's it's here. [~/www/commons/w/extensions/Mailgun/vendor/mailgun/mailgun-php]# ls
./            composer.json  phpunit.xml.dist      src/
../           error_log             tests/  .gitignore  .travis.yml [~/www/commons/w/extensions/Mailgun/vendor/mailgun/mailgun-php]# ls
./            composer.json  phpunit.xml.dist      src/
../           error_log             tests/  .gitignore  .travis.yml [~/www/commons/w/extensions/Mailgun/vendor/mailgun/mailgun-php]# cd src [~/www/commons/w/extensions/Mailgun/vendor/mailgun/mailgun-php/src]# ls
./  ../  Mailgun/ [~/www/commons/w/extensions/Mailgun/vendor/mailgun/mailgun-php/src]# cd Mailgun/ [~/www/commons/w/extensions/Mailgun/vendor/mailgun/mailgun-php/src/Mailgun]# ls
./  ../  Connection/  Constants/  Lists/  Mailgun.php  Messages/ [~/www/commons/w/extensions/Mailgun/vendor/mailgun/mailgun-php/src/Mailgun]#

So what do I do then? I tried recursively copying the contents of that folder into ~/www/commons/w/extensions/Mailgun but it's now failing silently. What about the MailgunDomain in Mailgun/extension.json; is that the same as the API Base URL, e.g. ""? Thanks. LibertyAlerts (talk) 10:17, 8 April 2016 (UTC)Reply[reply]

Few things you need to know is that composer update should happen after you have downloaded the Mailgun extension to extensions/. Please dont worry about anything in vendor/ as they are external dependencies pulled by composer ( even mailgun-php is ). MailgunDomain should be in your case. Welcome.01tonythomas (talk) 13:42, 8 April 2016 (UTC)Reply[reply]
Part of the problem is that when it fails, it fails silently (no error message). LibertyAlerts (talk) 14:28, 9 April 2016 (UTC)Reply[reply]
Fails silently == the composer update fails silently ?
No, I mean when the email doesn't send. It gives a message saying that the email was sent, but it doesn't actually send. What I ended up doing was disabling the Mailgun extension and using $wgSMTP to get email working on my wiki. Thanks, LibertyAlerts (talk) 12:29, 16 April 2016 (UTC)Reply[reply]
Hmm, thats strange. Did you check the Mailgun logs, to see if the email actually came out of your server, and hit the API ? 01tonythomas (talk) 17:25, 16 April 2016 (UTC)Reply[reply]

A barnstar for you![edit]

The Brilliant Idea Barnstar
:) Jithinrajtk (talk) 04:29, 9 July 2016 (UTC)Reply[reply]

A barnstar for you![edit]

The Technical Barnstar
Thanks for writing that script to export Google Code-In tasks from Phabricator into a CSV file. That's really helpful. Whatamidoing (WMF) (talk) 19:12, 29 November 2016 (UTC)Reply[reply]
Thank you. It was fun, and sadly Andre had to run over it again as we do not have a specific `mentor` field yet in our bug tracker, and GCI wants it. 01tonythomas (talk) 08:35, 30 November 2016 (UTC)Reply[reply]

Outreachy Round 15: Interested in becoming a mentor / featuring a project?[edit]

I'm contacting you, as your project is featured on the New Developers page! :) Would you be interested in mentoring a project in the Outreachy Round 15? If so, here is what you might be interested in learning about:

  1. Get an overview of the selection process, and your responsibilities before, during, and after the program
  2. Create a task, or modify an existing one on Phabricator. Make sure it includes: Project title, description (summary in 8-10 lines), skills required (Phabricator tags are welcome), mentors (required two), micro tasks (link to Phabricator task that must be completed to become a strong candidate).*
  3. Tag the task with #Outreach-Programs-Projects and #Outreachy-Round-15 on Phabricator.

Learn more about the accepted projects from previous round. - SSethi (WMF) (talk) 13:19, 28 August 2017 (UTC)Reply[reply]

Seeking help in beginning with MediaWiki extensions[edit]

Hi Tony, Actually, I aspire to be selected as an Outreachy intern in this round. I just wanted some help in beginning with MediaWiki extensions, can you help me with some beginner issues so that I can get familiar with this area of MediaWiki? That would be a really great help. Thanks :) --MaroonPixel (talk) 14:24, 25 September 2018 (UTC)Reply[reply]

Sure. What kind of help do you want ? First step would be to of course figure out some *easy* bugs to work on (assuming you have a working local wiki). 01tonythomas (talk) 14:33, 25 September 2018 (UTC)Reply[reply]

A barnstar for you![edit]

The Surreal Barnstar
Thank you for mentoring an Outreachy project this summer! You're awesome! ^>^ Pavithraes (talk) 19:26, 15 September 2020 (UTC)Reply[reply]

Support for Wikimedia Hackathon 2023/Satellite events[edit]

The Malayalam Wikipedia community is interested in hosting a Satellite event during the upcoming Wikimedia Hackathon 2023 in Kerala in July. They are seeking guidance and training from experienced Wikimedia attendees, specifically in technical aspects. Participants who share this interest will be invited to attend the event. Let me know your opinion or suggestions. Akbarali (talk) 10:56, 27 February 2023 (UTC)Reply[reply]

Thanks @Akbarali. Sadly, I missed this message :-(. How did it go? Looking forward to the Wikimedia Hackathon 2023 in Greece. 01tonythomas (talk) 11:42, 20 April 2023 (UTC)Reply[reply]