Hello all,
just a reminder: the call for participation for "Fantastic MediaWikis and How to Maintain Them", a one-day track at the Wikimedia Hackathon in Vienna, ends today. So if you intend to submit a presentation, please add yourself to this list:
https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/Fantastic_Me…
All the best,
Markus (User:Mglaser)
MediaWiki Stakeholders' Group
-----Ursprüngliche Nachricht-----
Von: Wikitech-l [mailto:wikitech-l-bounces@lists.wikimedia.org] Im Auftrag von Markus Glaser
Gesendet: Montag, 20. März 2017 15:30
An: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Betreff: [Wikitech-l] Fantastic MediaWikis - Track at Wikimedia Hackathon - CfP
[This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]
Hello everyone,
"Fantastic MediaWikis and How to Maintain Them" is a one-day conference track designed for people who work with the open source software MediaWiki in their organisation, company or business [1]. The conference track is curated by the MediaWiki Stakeholders Group and hosted by Wikimedia Austria.
The track is part of Wikimedia's biggest annual tech-event, the Wikimedia Hackathon [2]: For three days each year, about 200 developers come together to improve MediaWiki. Among the participants are coders from the Wikimedia Foundation as well as volunteers from all over the world.
We're using this opportunity to connect the people who work with MediaWiki in their enterprise, company, or organisation to the people who actually develop the code. We invite all MediaWiki stakeholders - power-users, maintainers, and service providers, who have a professional or semi-professional interest in the software - to join us for a day full of MediaWiki knowledge and networking!
This is a call for participation. We are specifically looking for contributions of your experience in running MediaWikis. These include but are not confined to:
* Use Cases. Tell us how and why you use MediaWiki in a specific area or to solve a specific problem.
* Best Practices. Talk about the most effective way you have found to use particular MediaWiki features.
* Enhancements. Have you improved MediaWiki to fit your needs? Show us your solution.
* Challenges. How can we all add to MediaWiki functionality? Do you have specific ideas you want to collaborate on?
Share your experience and submit a presentation here:
https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/Fantastic_Me…
Important dates:
* 20th March 2017: Call for Participation opens
* 5th April 2017: Submission deadline
* 10th April 2017: Notification of acceptance
* 19th - 21st May 2017: Vienna Hackathon
We are looking forward to your submissions!
Best,
Markus (User:Mglaser)
MediaWiki Stakeholders' Group
[1] https://www.wikimedia.at/hackathon/fantastic-mediawikis/
[2] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2017
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hello everyone,
I am pleased to share with you the news about the formation of the latest team in the Technology department, the MediaWiki Platform team![1]
The MediaWiki Platform team will be tasked with leading maintenance and improvements related to the core MediaWiki platform codebase. That includes encouraging future development of the MediaWiki platform and addressing the technical debt that has accumulated during the 15-year history of MediaWiki.
MediaWiki is an amazing, powerful, and complex open-source software platform. The number and variety of extensions, and the wide variety of communities who have adopted MediaWiki as their method for knowledge collection and dissemination, are a testament to its strength as a software platform.
Like any significant codebase with a long development history, there are remnants of design choices and experiments that are no longer in use, and some areas of code are in need of modernization. However, at its core is a large amount of highly functional, secure, performant code, capable of supporting a robust platform through the use of extensions and hooks. There is also a great amount of flexibility to adapt to new requirements.
This team will have a more focused purpose than the previous MediaWiki Core team.[2]. While the previous team was at times spread too thin, many areas are now covered by dedicated teams like Security and Performance. The new MediaWiki Platform team will center their efforts on the core codebase. The team will also have a dedicated Product Manager who will be creating the platform roadmap in collaboration with the team, the Architecture Committee and the MediaWiki user community.
Specific goals for this team are to:
* Assist and encourage development of features for MediaWiki by providing developers with a strong core.
* Undertake feature development work which is primarily architectural in nature.
* Facilitate the development and publication of MediaWiki's roadmap to assist coordination between internal and external users.
* Maintain and promote guidelines and standards for the MediaWiki core.
I am thrilled that Tim Starling has agreed to lead the team, reporting directly to me. He will be joined by Brion Vibber, Kunal Mehta and Brad Jorsch. The team officially launches on Monday April 3, and will complete the hiring and onboarding of additional team members in the coming months. Their initial workplan will include core support for multi content revisions for the Structured Data on Commons project and will be discussed in more detail during the upcoming consultation for the Wikimedia Foundation 2017-2018 annual plan.
I am excited by this latest evolution in the structure of the Foundation's Engineering group. We will continue to learn from our collective knowledge and expertise, and make adjustments to our composition and plans. I appreciate the input provided by many in the community that helped inform this decision. I also want to thank the members of the Wikimedia Foundation's Product, Technology, and Community Engagement departments who were involved in this process. In particular, I would like to thank Toby Negrin, Adam Baso, and Trevor Parscal - whose support was critical in bringing this plan together.
Join me in welcoming and celebrating our new team!
Victoria
[1] https://www.mediawiki.org/wiki/MediaWiki_Platform_team <https://www.mediawiki.org/wiki/MediaWiki_Platform_team>
[2] https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team <https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team>
Hi all,
I have been trying to add certain rate limiting actions for my extension's
API and noticed that it doesn't work with $wgMainCacheType set to CACHE_NONE
This is because User::pingLimiter()
uses ObjectCache::getLocalClusterInstance() to store the current rate limit
counts.
Is this the expected behavior? Looks pretty deceitful to me
as $wgMainCacheType is assumed to define the cache type but is actually
disabling a core functionality like rate limiting and maybe few others?
Regards,
Nischay Nahata
Hello,
I've found that running forceSearchIndex.php with --skipLinks
--indexOnSkip options is only processing about 1000-1500 pages and then
stopping. It's not due to error or anything because I can set --fromId
and run it again and it does another batch. I've tried setting --limit
and --batchSize and all sorts but nothing allows it to do more than this
amount at a time.... anyone have any idea what might be going on here?
(It's happening on both MW 1.27 with Elastic Search 1.75 and MW 1.28
with elastic 2.4.4)
Thanks,
Aran
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2017-03): 332
Active users (any activity) in (2017-03): 891
Task authors in (2017-03): 503
Users who have closed tasks in (2017-03): 274
Projects which had at least one task moved from one column to another on
their workboard in (2017-03): 294
Tasks created in (2017-03): 2645
Tasks closed in (2017-03): 2417
Open and stalled tasks in total: 34232
Median age in days of open tasks by priority:
Unbreak now: 0
Needs Triage: 262
High: 443
Normal: 638
Low: 909
Lowest: 844
(How long tasks have been open, not how long they have had that priority)
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on iridium at Sat Apr 1 00:00:14 UTC 2017)
# TL;DR
You can now write Selenium tests in Node.js! Learn more about it at
https://www.mediawiki.org/wiki/Selenium/Node.js
# Introduction
Five years ago we introduced browser tests using Selenium and a Ruby based
stack. It has worked great for some teams, and not so great for others.
Last year we talked to people from several teams and ran a survey[0]. The
outcome is a preference toward using a language developers are familiar
with: JavaScript/Node.Js.
After several months of research and development, we are proud to announce
support for writing tests in Node.js. We have decided to use
WebdriverIO[1]. It is already available in MediaWiki core and supports
running tests for extensions.
You can give it a try in MediaWiki-Vagrant[2]:
vagrant up
vagrant ssh
sudo apt-get install chromedriver
export PATH=$PATH:/usr/lib/chromium
cd /vagrant/mediawiki
xvfb-run npm run selenium
# Documentation
Extensive details are available on the landing page:
https://www.mediawiki.org/wiki/Selenium/Node.js
# Future
We plan to replace the majority of Selenium tests written in Ruby with
tests in Node.js in the next 6 months. We can not force anybody to rewrite
existing tests, but we will offer documentation and pairing sessions for
teams that need help. After 6 months, teams that want to continue using
Ruby framework will be able to do so, but without support from Release
Engineering team.
I have submitted a skill share session for Wikimedia Hackathon 2017 in
Vienna[3]. If you would like to pair on Selenium tests in person, that
would be a great time.
The list of short term actions is in task T139740[4].
# Thanks
I would like to thank several people for reviews, advice and code:
Jean-Rene Branaa, Dan Duvall, Antoine Musso, Jon Robson, Timo Tijhof.
(Names are sorted alphabetically by last name. Apologies to people I have
forgot.)
# References
[0] https://www.mediawiki.org/wiki/Browser_testing_user_satisfaction_survey
[1] http://webdriver.io/
[2] https://www.mediawiki.org/wiki/Selenium/Node.js/Inside_MediaWiki-Vagrant
[3] https://phabricator.wikimedia.org/T159945
[4] https://phabricator.wikimedia.org/T139740
Željko Filipin
Hello,
Sorry if this is cutting it close to the deadline, but I’m interested in doing a GSOC project over the summer to implement multiple watchlists for users.
What I have in mind is first, deliver a minimum viable product where users can add/remove/change custom watchlists. If time permits, it can be integrated into other components, such as notifications, a way to add pages into custom watch lists from the page itself, the API etc.
I’m looking for potential mentors. In particular, someone who knows how to get around Mediawiki’s codebase and can help me guide coding and development. If there is any interest let me know!
Thanks,
Techman224
Task: https://phabricator.wikimedia.org/T3492