Hi everyone,
The Community Tech team is happy to announce the top 10 wishes from the
2016 Community Wishlist Survey!
More than 1,100 people participated in the survey this year -- proposing,
discussing and voting on 265 ideas. There was a two-week period in November
to submit and discuss proposals, followed by two weeks of support voting.
The top 10 proposals with the most support votes now become Community
Tech's backlog of projects to evaluate and address.
And here's the top 10:
#1. Global gadgets (91 support votes)
#2. Edit summary length for non-Latin languages (90)
#3. Section heading URLs for non-Latin languages (88)
#4. Global settings (84)
#5. Rewrite Xtools (84)
#6. Wikitext editor syntax highlighting (82)
#7. Warning on unsuccessful login attempts (73)
#8. Automatic archive for new external links (72)
#9. Fix Mr. Z-bot's popular pages report (72)
#10. User rights expiration (70)
You can see the whole list here, with links to proposals and Phabricator
tickets:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Results
So -- who's going to work on all these wishes?
The Community Tech team is responsible for investigating and addressing the
top 10 wishes. If there's a wish in the top 10 that we can't work on,
because it's unfeasible or because another group is working on it, then
we'll explain what's happened.
Community Tech will also pick up some wishes below the top 10 that support
smaller user groups who are doing important work, but don't have the
numbers to vote a proposal all the way up to the top 10. This will apply to
some combination of: campaign and program organizers, GLAM participants,
stewards and CheckUsers, and people working on smaller projects or smaller
languages. We haven't determined which wishes we'll pick up yet; we'll be
talking about these as we get into 2017.
Also, some of these wishes will be granted by volunteer developers; the
Technical Collaboration team will help to connect volunteers with important
wishes that they can work on.
Some of these wishes are or will be on the roadmap for our colleagues on
the WMDE Technical Wishes team, and other Wikimedia Foundation product
teams.
To get updates on our progress:
There are project pages for each of the top 10 wishes, which you can put on
your watchlist. We'll update them as the project progresses. (At time of
writing, these are just skeletons; actual information on each project is
still to come.) Feel free to post questions and suggestions on the project
talk pages:
https://meta.wikimedia.org/wiki/Category:Community_Tech_-_Current_projects
If you're familiar with the Phabricator ticketing system, the main Phab
task for each wish is noted on the Results page. You can subscribe to those
tickets for updates.
We also publish several status reports through the year, to keep people
updated. You can watch the main Community Tech page for updates:
https://meta.wikimedia.org/wiki/Community_Tech
There are more questions and answers on the Wishlist Survey FAQ:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/FAQ
Thanks to everybody who proposed, discussed, debated and voted on ideas in
this year's Wishlist Survey, to everyone who's said nice things to us
recently, and to all people everywhere in time and space, on general
principles.
Danny Horn
Sr Product Manager, Community Tech
Hi all,
Some months ago we started to define a statement of purpose for design at
Wikimedia. We shared our initial iteration and got useful feedback. Based
on that feedback, we have updated a new version:
https://www.mediawiki.org/wiki/Design/Statement_of_purpose
Please, feel free to check the updated version, and provide any suggestion
in the talk page.
If the statement just sounds as a logical, simple, and obvious description
for the purpose of design here, that was the goal. Putting this in writing
has been helpful for designers and people working with us to get into the
same page, and will be useful in the future to achieve the level of support
for design we envision for those areas where we are not there yet.
Thanks to everyone that has contributed to the process.
--
Pau Giner
Senior User Experience Designer
Wikimedia Foundation
Hi all,
We're excited to announce that we've rolled out several updates and
bugfixes for the Commons Android app[1] over the past couple of months.
Some of the major ones include:
- Automatic addition of geocoding template if uploaded image is geotagged
- Category suggestions based on the title entered for the image
- New, more detailed tutorial to educate new contributors on what types of
images should or should not be uploaded (special thanks to Pine for sharing
his Commons educational script which was used as the basis for this)
- Check for whether or not the file already exists on Commons, to prevent
upload of duplicates
Additionally, the kind folks at translatewiki.net are helping us set up a
translation project for our app, so hopefully localization should improve
in the near future.
Thank you all for your support and encouragement thus far! Feedback, bug
reports, and suggestions are always welcome on our GitHub page[2]. :)
[1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons
[2]: https://github.com/commons-app/apps-android-commons/issues/
--
Regards,
Josephine
Hi all!
When developing the Revision Slider extension [1] earlier this year, we (at
Wikimedia Germany) have learned quite some things about making extensions
and gadgets accessible for RTL language users. We have just published the
write up [2] summarizing what we've discovered.
We hope people developing new and existing tools, and in general developers
sensitive to RTL accessibility issues will find these notes interesting
and/or helpful.
Any comments are welcome!
[1] https://www.mediawiki.org/wiki/Extension:RevisionSlider
[2]
https://www.mediawiki.org/wiki/Extension:RevisionSlider/Developing_a_RTL-ac…
Best,
--
Leszek Manicki
Software Developer
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
http://wikimedia.de
Imagine a world, in which every single human being can freely share in the
sum of all knowledge. That‘s our commitment.
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
We are soon going to run out of Google Code-in tasks.
Please mentor small and easy tasks!
https://www.mediawiki.org/wiki/Google_Code-in_2016
Contact us if you need help or have questions!
Some GCI achievements of the last week (week 2 out of 7):
* Newsletter extension again received numerous patches
* Proposals for a redesign of the Romanian Wikipedia's main page
* MobileFrontend hooks documentation got updated
* One Wikispeech logo proposal (student still needs to upload to
Commons)
* A long CREDIT showcase video got split into 'one video per topic'
parts on Commons
* Deprecated "Article::getContent()" calls got replaced in several
MediaWiki extensions
* Wikidata user docs were analyzed and improvements proposed
* In WikiEduDashboard, .erb html templates were converted to .haml
* The RelatedArticles extension received a design fix for the footer
* Updated screencast videos in the Phabricator help on mw.org
* More screenshots on extension pages (Echo, Poem, TemplateSandbox, …)
* Soon in the pageview API: Monthly request stats per article title!
* …and many many more.
Congratulations to all our students and thanks to all our mentors!
Thanks,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Hi all!
Please find below minutes of the last ArchCom meeting
The minutes can be fond at
<https://www.mediawiki.org/wiki/Architecture_committee/2016-12-07>.
See also the ArchCom status page at
<https://www.mediawiki.org/wiki/Architecture_committee/Status> and the RFC board
<https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
People present: Members: Brion, Daniel (chair), Gabriel, Tim. Guest: Victoria
Coleman (CTO)
* Victoria joined to meeting to get an idea of how ArchCom operates
* Victoria will attend ArchCom meetings as much as time allows
* Work on thumbnail API (T66214) is progressing, follow-up meeting to be
announced (Gabriel)
* Web API outage (T151702) is being investigated/evaluated (Gabriel, Tim, Kunal,
and others)
* Code experiments started for using Varnish’s xkey feature in Wikibase
(T152425) (Daniel)
* Victoria suggest to have a regular meeting to review/prioritize technical
debt. ArchCom to be invited.
* Lego’s Deprecation Policy RFC (T146965) to be discussed on December 14.
Fallback: thumb API (T66214).
--
Daniel Kinzler
Senior Software Developer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
Hi all,
Tomorrow evening (18:30–19:30 UTC) I'll be taking Gerrit offline shortly
for a planned upgrade from 2.12.5 to 2.13.3. It shouldn't take the full
hour, but you never know :)
If you play the deployment game regularly, you'll notice I've cancelled[0]
tomorrow's "SF Morning SWAT" window because it overlaps with the time I
picked ;-)
Thanks!
-Chad
[0]
https://wikitech.wikimedia.org/w/index.php?title=Deployments&type=revision&…