- 1 The LocalisationUpdate extension has gone live
- 2 The Wikimedia Developer Summit wants you
- 3 Developer Wishlist Survey: propose your ideas
- 4 Developer Wishlist Survey: Vote for Proposals
- 5 New notification when a page is connected to Wikidata
The LocalisationUpdate extension has gone live[editar código]
The LocalisationUpdate extension is now enabled for all Wikimedia projects. From now on new localisations that become available in SVN will become available to your project within *** hours. Your localisations get into SVN from translatewiki.net typically within a day and at worst in two days. This is a huge improvement from the old practice where the localisations became available with new software. This could take weeks, even months.
The localisations done by our community at translatewiki.net are committed to SVN typically every day. When the system messages in English are the same as the local messages, they will now be inserted in a file and are available for use in all our projects in a timely manner
What this means for you[editar código]
Local messages have an impact on the performance of our system. It is best when messages are as much as possible part of the system messages. In order to remove unnecessary duplication, all the messages that have a local localisation and are exactly the same as the system message will be removed. What we ask you to do is to compare and proof read the messages in translatewiki.net and the local messages. You can then either remove local messages when the translatewiki.net message is to be preferred or, you can update the message at translatewiki.net.
Messages that are specific to your project will have to stay as they are. You do want to check if the format and the variables of the message are still the same.
Why localise at translatewiki.net[editar código]
When you localise at translatewiki.net, your messages will be used in all Wikimedia projects and eventually in all MediaWiki based projects. This is how we provide the standard support for your language. When messages change, at translatewiki.net you will be prompted to revisit your translations. Localising is more efficient because we have innovated the process to make you more efficient; there is text explaining about messages and we have applied AJAX technology to reduce the number of clicks you have to make.
The Wikimedia Developer Summit wants you[editar código]
The Wikimedia Developer Summit is the annual meeting to push the evolution of MediaWiki and other technologies supporting the Wikimedia movement. The next edition will be held in San Francisco on January 9–11, 2017.
We welcome all Wikimedia technical contributors, third party developers, and users of MediaWiki and the Wikimedia APIs. We specifically want to increase the participation of volunteer developers and other contributors dealing with extensions, apps, tools, bots, gadgets, and templates.
- Monday, October 24: last day to request travel sponsorship. Applying takes less than five minutes.
- Monday, October 31: last day to propose an activity. Bring the topics you care about!
More information: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit
Subscribe to weekly updates: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4MKramer (WMF) (talk) 19:07 14 oct 2016 (UTC)
Developer Wishlist Survey: propose your ideas[editar código]
At the Wikimedia Developer Summit, we decided to organize a Developer Wishlist Survey, and here we go:
The Wikimedia technical community seeks input from developers for developers, to create a high-profile list of desired improvements. The scope of the survey includes the MediaWiki platform (core software, APIs, developer environment, enablers for extensions, gadgets, templates, bots, dumps), the Wikimedia server infrastructure, the contribution process, and documentation.
The best part: we want to have the results published by Wednesday, February 15. Yes, in a month, to have a higher chance to influence the Wikimedia Foundation annual plan FY 2017-18.
There's no time to lose. Propose your ideas before the end of January, either by pushing existing tasks in Phabricator or by creating new ones. You can find instructions on the wiki page. Questions and feedback are welcome especially on the related Talk page.The voting phase is expected to start on February 6 (tentative). Watch this space (or even better, the wiki page) - SSethi_(WMF) January 21st, 2017 3:07 AM (UTC)
Developer Wishlist Survey: Vote for Proposals[editar código]
Almost two weeks ago, the Technical Collaboration team invited proposals for the first edition of the Developer Wishlist survey!
We collected around 77 proposals that were marked as suitable for the developer wishlist and met the defined scope and criteria. These proposals fall into the following nine categories: Frontend, Backend, Code Contribution (Process, Guidelines), Extensions, Technical Debt, Developer Environment, Documentation, Tools (Phabricator, Gerrit) and Community Engagement.
Voting phase starts now and will run until February 14th, 23:59 UTC. Click here on a category and show support for the proposals you care for most. Use the 'Vote' and 'Endorse' buttons next to a proposal to do so.
What happens next?
Proposals that will gather most votes will be included in the final results which will be published on Wednesday, February 15th. These proposals will also be considered in the Wikimedia Foundation’s annual plan FY 2017-18 - SSethi_(WMF) (talk) 04:41, 6 February 2017 (UTC)
New notification when a page is connected to Wikidata[editar código]
(Por favor, ayuda a traducir a tu idioma)
The Wikidata development team is about to deploy a new feature on all Wikipedias. It is a new type of notification (via Echo, the notification system you see at the top right of your wiki when you are logged in), that will inform the creator of a page, when this page is connected to a Wikidata item.
You may know that Wikidata provides a centralized system for all the interwikilinks. When a new page is created, it should be connected to the corresponding Wikidata item, by modifying this Wikidata item. With this new notification, editors creating pages will be informed when another editor connects this page to Wikidata.
This feature will be deployed on May 30th on all the Wikipedias, excepting English, French and German. This feature will be disable by default for existing editors, and enabled by default for new editors.
This is the first step of the deployments, the Wikipedias and other Wikimedia projects will follow in the next months.
If you have any question, suggestion, please let me know by pinging me. You can also follow and leave a comment on the Phabricator ticket.
Thanks go to Matěj Suchánek who developed this feature!